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 There,
Just wondering if anyone had any ideas why my phone refuses to co-operate!
Basically, after getting bored of the stock rom when I first got my phone, I somehow managed to install a CM based rom. That worked, but I got bored of the fact that the camera never seemed to work right, and some apps didn't work/ were graphically buggy. Assuming it was just a badly ported graphics driver or whatever, I found a way, using FlashTool, to revert to the stock rom (C6603_10.3.1.A.0.244_Generic UK to be precise). I wasn't sure exactly what it did, but it was back how it used to be. sorted.
So, since kitkat made it's way to the XZ, I thought I'd try one of those roms, being the curious bugger that I am. The process I ended up going with eventually was:
>Downgrading Kernel to a lower version because the root explot wouldn't work on 10.3.1.A.0.244
>Rooting using "DooMLoRD_Easy-Rooting-Toolkit_v18"
>Upgrading kernel to one that would accept a recovery
>Installing TWRP
>Booting into recovery, CWM appeared instead. Strange, I thought. Oddly, mount USB wouldn't work at all, so I had to boot the phone back up to transfer the kitkat rom over
>Trying to flash the rom gave me an error number 7
>Boot Loop, at which point I just flashed 10.3.1.A.0.244 again.
I've tried this twice now, first with DooM Kernel, and then once with a different one. Neither CWM or TWRP have worked properly. Any help? Or am I just cursed?
Cheers
Tried this again, did literally everything I could think of and still no dice. Help? Have I somehow forced my phone to be on stock software forever?
If you dont unlock your bootloader, you can not use any kind of custom kernel.
That means aosp or aokp based firmwares can not run over locked bootloader.
Locked bootloader checks sign of kernel, if not certificated you will stuck on bootloop.
If you want to use any kind of custom rom... basicly.
1. Backup ta partition. " so you can revert any time you want."
2. Copy firmware zip file tou your internal or external sdcard.
3. Flash custom kernel. "Most of kernel have recovery option build in".
4. Boot in recovery mod. "Mostly press volume down while booting"
5. Insall custom rom.
6.a wipe dalvik-cache
6.b factory reset
Old setting might work or not with new rom. So first try to wipe dalvik- cache. If you stuck on boot loop or any kind of problem, just boot in recovery again and run factory reset.
Sent from my C6603 using Tapatalk
eryen said:
If you dont unlock your bootloader, you can not use any kind of custom kernel.
That means aosp or aokp based firmwares can not run over locked bootloader.
Locked bootloader checks sign of kernel, if not certificated you will stuck on bootloop.
If you want to use any kind of custom rom... basicly.
1. Backup ta partition. " so you can revert any time you want."
2. Copy firmware zip file tou your internal or external sdcard.
3. Flash custom kernel. "Most of kernel have recovery option build in".
4. Boot in recovery mod. "Mostly press volume down while booting"
5. Insall custom rom.
6.a wipe dalvik-cache
6.b factory reset
Old setting might work or not with new rom. So first try to wipe dalvik- cache. If you stuck on boot loop or any kind of problem, just boot in recovery again and run factory reset.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
Hey, thanks for your reply!
I had unlocked the bootloader when I first got the phone and just assumed it would be permanent. Would flashing it back to stock firmware re-lock the bootloader?
But yes, assuming my boot loader is still unlocked ( I have tried to check and it doesn't seem to be locked) I have been through those steps basically. I am fine to flash a kernel with a recovery but the recovery never works properly/ at all. I can root the phone no problem though.
Best to extract the boot.img from the zip file of the ROM you want to flash, and flash that first. Then flash the ROM from its recovery.
Sent from my C6603 using xda app-developers app
shoey63 said:
Best to extract the boot.img from the zip file of the ROM you want to flash, and flash that first. Then flash the ROM from its recovery.
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
Cheers, I'll give that a go - I was under the impression that you weren't supposed to flash kernels that weren't designed for the currently installed ROM though? It just seems that any kernel I flash isn't working properly so I didn't think doing that would play any nicer with the phone
SuburbanKnight said:
Cheers, I'll give that a go - I was under the impression that you weren't supposed to flash kernels that weren't designed for the currently installed ROM though? It just seems that any kernel I flash isn't working properly so I didn't think doing that would play any nicer with the phone
Click to expand...
Click to collapse
You're not actually going to boot into your current rom after flashing the kernel.
Flash the kernel via fastboot, then boot into recovery and flash the rom.
All this should be covered in the installation instructions of whatever rom you're trying to flash in any case....
Sent from my C6603 using Tapatalk
Well, that seems to have done it! Thanks very much for your help.
So, I guess the moral here is that if you're on stock and need a recovery to flash a new ROM, always use the boot.img from the ROM you'll be using.
Thanks again - I'd never seen that said before but quite possibly I wasn't paying attention!
Hi everybody,
just got an old yet effective SGS and I wanted root and get rid of touchwizz and all the crap from my carrier
I was unable to boot into DL mode, i tried everything, so I had to do it with adb reboot
I never had to use Odin to do my hacking with android so i'm not used to it but short story : I rename my rom.zip into rom rom.tar, it failed and all I have is this now :
https://www.dropbox.com/s/wk42jbmp33a3ftu/IMG_20140715_152917.jpg
Also I need to unsimlock, flashing a new rom will also do the trick right ?
thanks
What you just did is bricking your phone. It it was a zip file you need to install it from the recovery. Renaming it is not the way it works. I'm not sure if now you can fix it. Sorry, man
Sent from my GT-I9000 using XDA Premium 4 mobile app
Do you know what I can at least try?
If you can get into download mode:
Follow sections 2 and 3 in this guide.
If you can't:
Follow this guide and after that do what I sails to do if you have download mode.
Does 3-button-combo not work to get into the download mode?
(power & home & volume down)
tetakpatalked from Nexus 7 flo
so i tried the resistance thing but i was unable to find all of the part required so i bought one of these already done solution thingy
It worked, I'm now able to boot into DL mode
I also succesfully install a random 2.x rom from an unknown european carrier, no root, lots of crap installed, and simlocked
How do i get from that to my CM 11 rom ? (this time it's in .tar format via 7zip ^^')
I tried via Odin in PDA it says fail right away
what can I do ?
thanks fr all the answers guys
@Idealith simlock has nothing to do with the firmware.
You need now any root kernel for that firmware, it has to be compatible with the intiframs of your 2.x version and it will give you a custom recovery.
There you can flash first CM10.2 to get the modified partition sizes and KK ready recovery and after that you can flash CM11
IMHO, the new Mackay ICS 2014 rom based on CM9 is a lot faster than any KitKat and works better on the i9000
tetakpatalked from N7100
my question about the rom still applies cause this one is awful
but with what does it have to do then ?
EDIT : my browser didn't render the end of your answer
I'm afraid i'm not following though :/
I got my 2.3 rom to stop crashing
and I once boot into recovery mod idk how ..
I selected the 10.2 CM rom but it started rebooting over and over again
I'm really not following everything that is happening over here :/
Idealith said:
I got my 2.3 rom to stop crashing
and I once boot into recovery mod idk how ..
I selected the 10.2 CM rom but it started rebooting over and over again
I'm really not following everything that is happening over here :/
Click to expand...
Click to collapse
Hey, could you tell me which country you are at? I could then take a few steps to help you
PFFFFFFFFFFFFFFFFTTT, sent from my i9000
I am currently in France
last news : been able to reboot into CWM, I selected the mackay cm 9 based rom, it rebooted halfway thrugh only to reboot in TWRP (idk how, are both installed or is twrp in the rom too ???)
so i tried from twrp wiping everything before and it wen through, then on bot it told me it needed to factory reset, it never worker though
so now i can boot into CWM but can't access my sd card ...
thanks
Idealith said:
I am currently in France
last news : been able to reboot into CWM, I selected the mackay cm 9 based rom, it rebooted halfway thrugh only to reboot in TWRP (idk how, are both installed or is twrp in the rom too ???)
so i tried from twrp wiping everything before and it wen through, then on bot it told me it needed to factory reset, it never worker though
so now i can boot into CWM but can't access my sd card ...
thanks
Click to expand...
Click to collapse
It was perfectly normal behavior, as after flashing the zip from CM, it will in firat step upgrade your recovery to TWRP 2.2.2.0
As you have wiped already before, it would be perfectly fine to just flash the rom.zip in the new TWRP recovery, and your gapps right afterwards. The recovery upgrade is totally common on the i9000 as first step.
The i9000 can easily be unbricked by flashing a stock image with Odin.
tetakpatalked from Nexus 7 flo
tetakpatak said:
It was perfectly normal behavior, as after flashing the zip from CM, it will in firat step upgrade your recovery to TWRP 2.2.2.0
As you have wiped already before, it would be perfectly fine to just flash the rom.zip in the new TWRP recovery, and your gapps right afterwards. The recovery upgrade is totally common on the i9000 as first step.
The i9000 can easily be unbricked by flashing a stock image with Odin.
tetakpatalked from Nexus 7 flo
Click to expand...
Click to collapse
I suppose my phone has been unbricked I made a 2.3 stock rom work
What i do now :
I flash the stock rom, go back to DL mode, flash the recovery, take the battery off, boot back in recovery, wipe everything ( do I really have to wipe system and all ?), select the ROM, nd once I'm in TWRP i reselect than same ROM
for the cm9 based mackay one it keep rebooting over and over again
for CM 10.2 it says the encryption failed and I need to factory reset, then nothing works
Idealith said:
I suppose my phone has been unbricked I made a 2.3 stock rom work
What i do now :
I flash the stock rom, go back to DL mode, flash the recovery, take the battery off, boot back in recovery, wipe everything ( do I really have to wipe system and all ?), select the ROM, nd once I'm in TWRP i reselect than same ROM
for the cm9 based mackay one it keep rebooting over and over again
for CM 10.2 it says the encryption failed and I need to factory reset, then nothing works
Click to expand...
Click to collapse
Yes, that would be correct procedure. To install CM9 you will have to format data, cache and dalvik cache.
If you have never had a JVU or JVZ firmware installed, it is likely that you still have a Froyo bootloader which could be reason of the problems with Android 4.xx
tetakpatalked from N7100
tetakpatak said:
Yes, that would be correct procedure. To install CM9 you will have to format data, cache and dalvik cache.
If you have never had a JVU or JVZ firmware installed, it is likely that you still have a Froyo bootloader which could be reason of the problems with Android 4.xx
tetakpatalked from N7100
Click to expand...
Click to collapse
and how do i get that bootloader set up ?
Idealith said:
and how do i get that bootloader set up ?
Click to expand...
Click to collapse
Either by flashing a whole JVU or JVZ stock firmware, or by flashing a bootloader only.
Check my sticky thread here under the same section (help & troubleshooting), I have described whole the procedure in the OP. I have even attached the files and also video is there: http://forum.xda-developers.com/showthread.php?t=2444308
Right point would be to do it first.
tetakpatalked from N7100
tetakpatak said:
Either by flashing a whole JVU or JVZ stock firmware, or by flashing a bootloader only.
Check my sticky thread here under the same section (help & troubleshooting), I have described whole the procedure in the OP. I have even attached the files and also video is there: http://forum.xda-developers.com/showthread.php?t=2444308
Right point would be to do it first.
tetakpatalked from N7100
Click to expand...
Click to collapse
thanks you so much i have now CM 10.2 running
would you know by any chance how to un simlock it ?
Idealith said:
thanks you so much i have now CM 10.2 running
would you know by any chance how to un simlock it ?
Click to expand...
Click to collapse
Ask your carrier, I assume the phone contract isn't new anymore (or expired) so you'll get unlock code for free. Here in Europe one can obtain the unlock code after 2 years for free.
Otherwise you can ask one of the online unlock services, it costs usually around 15-20$ to get the code
tetakpatalked from N7100
Idealith said:
so i tried the resistance thing but i was unable to find all of the part required so i bought one of these already done solution thingy
It worked, I'm now able to boot into DL mode
I also succesfully install a random 2.x rom from an unknown european carrier, no root, lots of crap installed, and simlocked
How do i get from that to my CM 11 rom ? (this time it's in .tar format via 7zip ^^')
I tried via Odin in PDA it says fail right away
what can I do ?
thanks fr all the answers guys
Click to expand...
Click to collapse
I'm glad that the JIG helped you (I know I'm late )
danielbe said:
I'm glad that the JIG helped you (I know I'm late )
Click to expand...
Click to collapse
yeah that worked like a charm
it was a good idea to buy it, i would have use the resistors so much
is there a more xda way to unlock it ? my carrier wants me to send the phone and have it unlock, they won't just provide the code :/
I was curious about installing custom roms so i decided to try. I successfully had rooted my phone and unlocked the bootloader and i just needed CWM recovery so that I could install CM11 custom rom. I didn't put the custom rom on my phone because I'd figure I would do it after installing CWM but after flashing CWM, I couldn't even go into my stock rom! I tried everything from formatting the cache to the data, I even have TWRP flashed as well but no luck there. I don't want to mess with my phone anymore because I am quite frankly, scared. So all I want to do is remove CWM and TWRP recovery, and flash my stock rom. Oh, and I tried to flash the stock rom with flashtool, that didn't work either
Thanks for the help!
UPDATE: I DOWNLOAD ALL THE DRIVERS FOR FLASHTOOL AND TRIED INSTALLING MY STOCK ROM THROUGH FLASH BOOT AND IT WORKED! SO FAR SO GOOD.
UPDATE 2: ITS WORKING. ALL I DID WAS LOCK MY BOOTLOADER WITH FLASHTOOL AND FLASHED THE STOCK ROM!
I think you could mount the usb storage from CWM, so you could copy the rom you wanted and install it? You could have saved a lot of hassle loool
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