hi.. I was on omni rom before i updated. I had a problem with omni rom, I had an error, process stopped working. i tried reinstalling omni rom, wiping everything but still problem persisted. I tired also slimkat rom but still same problem so I decided to flash stock rom. I flashed the .757 update and after flashing I cannot register a network. Z1 can search my network but when i try to register it takes forever. i tried also downgrading to the first rom out of the box which is .290 but I am having baseband unknown problem. i tried to flash other stock rom but still same problem. I also tried to flash iHackers 4.1, followed the steps but still i cannot register a network. Baseband and IMEI are both available. Is there any way to fix my z1
I also tried fixing via SUS, still same problem, can look for network but cannot register. Basing on the box SI my rom is CUS HK which is the same stock ROM that I used but still had the problem. please help...
bjo12 said:
hi.. I was on omni rom before i updated. I had a problem with omni rom, I had an error, process stopped working. i tried reinstalling omni rom, wiping everything but still problem persisted. I tired also slimkat rom but still same problem so I decided to flash stock rom. I flashed the .757 update and after flashing I cannot register a network. Z1 can search my network but when i try to register it takes forever. i tried also downgrading to the first rom out of the box which is .290 but I am having baseband unknown problem. i tried to flash other stock rom but still same problem. I also tried to flash iHackers 4.1, followed the steps but still i cannot register a network. Baseband and IMEI are both available. Is there any way to fix my z1
I also tried fixing via SUS, still same problem, can look for network but cannot register. Basing on the box SI my rom is CUS HK which is the same stock ROM that I used but still had the problem. please help...
Click to expand...
Click to collapse
Sounds like you've lost your IMEI number.
Dial *#06# and see if it shows up all zeros, I bet it does.
I'm looking to downgrade mine from Kitkat back to 4.3 and I've gathered that if you go further back, and you did, you could lose your IMEI.
I don't know how to fix this myself, but I'm still looking and learning.
Have a look at this thread and see if it helps --> http://forum.xda-developers.com/showthread.php?t=2628185
Second post down gives NUT's .ftf to use to downgrade without losing IMEI, but I don't know if it will restore yours. Might be worth a try. Have a read, and hope it points you in the right direction.
---------- Post added at 05:41 PM ---------- Previous post was at 04:44 PM ----------
Try flashing a completely stock .757 ftf including kernel, that should restore your IMEI, and flash everything.
Hope you sort it
Not .757, but .534. You'll get your imei back and try going back to .757 from there. I can't tell you how to fix that from nothing as I downgraded to .534 and restored a backup of .757. Try some other .534 ftfs if yours doesn't work. There's one version of the ftf that messes up your imei.
Don't get too scared mate, it happened for me too!
Wysłane z mojego C6903 przy użyciu Tapatalka
I dont think flashing NU'T's .534 alone will restore IMEI, but I could be wrong, I'm no expert.
Flashing a firmware before .290 seems result in loss of IMEI, so looks like the best way to go is to go back to the ROM you were using originally that had IMEI showing.
@op - If you reinstall OMNI rom does your IMEI come back??
If the OP is wanting to get onto KitKat .757, and was on OMNI rom previously, I'd probably flash the stock .290, or .136 ftf completely.
That firmware should in theory work, and restore IMEI, then I'd look at updating to .757.
If I'm wrong, sorry, and someone please correct.
Many thanks.
Thanks for the replies.
Actually I already did some research and flashed every ROM available even NUT's. I downgraded to .534 had bootloop. flashing .757 restores my IMEI and baseband but sadly doesn't fix the signal registration problem that I have. I have both IMEI and baseband. My IMEI is same as I have with the box so I really do not know why I cannot register a network. I have flashed back to .290 as it was FW when i unboxed it but it removes my baseband even if I choose to exclude baseband when flashing through flashtool. Anyway, I have again .757 and relocked bootloader because I sent it for warranty. Now my problem is can they know if I flashed custom ROM coz we all know it voids warranty.. hehe..
When I reinstall OMNI I cannot get it to boot properly because I always have Process is not responding error and then reboots continuously
Ah, right.
What's the status of the TA partition? Was it backed up, and restored when you relocked the bootloader?
As far as I've read, restoring TA and relocking should be okay for warranty purposes. The only thing I've wondered about is you usually have to unlock via the Sony website, so they must know you requested the unlock key.
If the bootloader is locked with a restored TA partition, they cannot prove that you actually used it tho, so should be fine.
If you didn't backup, then restore the TA, then they may know.
As for the signal issue, had you tried another sim card to see if that worked?
MickieH said:
Ah, right.
What's the status of the TA partition? Was it backed up, and restored when you relocked the bootloader?
As far as I've read, restoring TA and relocking should be okay for warranty purposes. The only thing I've wondered about is you usually have to unlock via the Sony website, so they must know you requested the unlock key.
If the bootloader is locked with a restored TA partition, they cannot prove that you actually used it tho, so should be fine.
If you didn't backup, then restore the TA, then they may know.
As for the signal issue, had you tried another sim card to see if that worked?
Click to expand...
Click to collapse
TA partition was not backed up because of my excitement to flash custom ROM!! Hahaha so It's really my mistake for not doing so... :cyclops:
Anyway I tried sending it for warranty purpose and now after waiting for weeks already I was updated with the status. I was told that the main board was replaced and now my phone is being prep to be shipped and returned hopefully I will receive it tomorrow. Now my question is if the board was replaced does it mean that it will have a new set of DRM keys and others? If not will flashing again a Custom Rom bring the same problem? hehe.. Because I am thinking of flashing custom ROM again once I have it.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
So I have my Z1 back, actually not my actual Z1 but a brand new replacement. =)
Time to back up everything now! =)
bjo12 said:
TA partition was not backed up because of my excitement to flash custom ROM!! Hahaha so It's really my mistake for not doing so... :cyclops:
Anyway I tried sending it for warranty purpose and now after waiting for weeks already I was updated with the status. I was told that the main board was replaced and now my phone is being prep to be shipped and returned hopefully I will receive it tomorrow. Now my question is if the board was replaced does it mean that it will have a new set of DRM keys and others? If not will flashing again a Custom Rom bring the same problem? hehe.. Because I am thinking of flashing custom ROM again once I have it.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
So I have my Z1 back, actually not my actual Z1 but a brand new replacement. =)
Time to back up everything now! =)
Click to expand...
Click to collapse
Lol, yes, and the TA partition
Nice one getting a new handset :good:
Related
I was trying to flash the new 4.3 Rom and somehow I have managed to make the sim card unfunctional. even after going back to 4.2.2 the phone always says that the sim card is invalid. I have a TA Partition backup.
I really need the phone. Thats what you get when you are playing around.
Why is the sim functionality gone? Anyone experienced the same?
Ok its because I lost the IMEI number. Nice one some people on the board had the trouble too after upgrading.
Had the same problem rerolling to older versions.. but i think its the regional code from the file.
Flash a version near/from your region and the sim card will work properly again.
Nepturion said:
Had the same problem rerolling to older versions.. but i think its the regional code from the file.
Flash a version near/from your region and the sim card will work properly again.
Click to expand...
Click to collapse
yes I rolled back to 4.2.2 but failed restoring the IMEI do I have to flash the whole ftf file again?
FiremakerP said:
I was trying to flash the new 4.3 Rom and somehow I have managed to make the sim card unfunctional. even after going back to 4.2.2 the phone always says that the sim card is invalid. I have a TA Partition backup.
I really need the phone. Thats what you get when you are playing around.
Why is the sim functionality gone? Anyone experienced the same?
Ok its because I lost the IMEI number. Nice one some people on the board had the trouble too after upgrading.
Click to expand...
Click to collapse
It also happened to mine while I'm trying to root on 4.3. I downgraded to 534 after unsuccessful of rooting on 4.3. Then I lost IMEI and showed sim card is invalid. Fortunately I made my original 270 ftf for back up. I flashed 270 again and I got back IMEI and working sim card. I also found in other thread that if you want to downgrade 4.2.2 from 4.3 you need to flash exclude baseband. If not you will get that IMEI and sim card error. Try to update 4.3 and downgrade 4.2.2 exclude baseband if you don't have original back up like me. Good luck !!! :good:
hololodilolo said:
It also happened to mine while I'm trying to root on 4.3. I downgraded to 534 after unsuccessful of rooting on 4.3. Then I lost IMEI and showed sim card is invalid. Fortunately I made my original 270 ftf for back up. I flashed 270 again and I got back IMEI and working sim card. I also found in other thread that if you want to downgrade 4.2.2 from 4.3 you need to flash exclude baseband. If not you will get that IMEI and sim card error. Try to update 4.3 and downgrade 4.2.2 exclude baseband if you don't have original back up like me. Good luck !!! :good:
Click to expand...
Click to collapse
You a need a functional TA backup to do it.
Downgrade to the version where you did the TA backup through FTF then you can see your IMEI again.
Ok I'm running 4.2.2 I want to know is there a way to back up my phone my bootloader is locked.
I have root but I didn't install custom recovery. I want to try 4.3 but I want to make sure I can come back to 4.2.2 without loosing imei.thanks
FiremakerP said:
You a need a functional TA backup to do it.
Downgrade to the version where you did the TA backup through FTF then you can see your IMEI again.
Click to expand...
Click to collapse
Thank you for your advice but in my case I didn't need to backup and restore TA to get back IMEI and working sim card. I'm just flash my stock 4.2.2 ftf that I backup before and everything is working fine now (both IMEI and sim).
---------- Post added at 05:50 PM ---------- Previous post was at 05:47 PM ----------
adamo86 said:
Ok I'm running 4.2.2 I want to know is there a way to back up my phone my bootloader is locked.
I have root but I didn't install custom recovery. I want to try 4.3 but I want to make sure I can come back to 4.2.2 without loosing imei.thanks
Click to expand...
Click to collapse
As per reply from 4.3 rooting thread, you can downgrad 4.2.2 from 4.3 without losing imei but you need to exclude baseband when you flash 4.2.2. :highfive:
hololodilolo said:
Thank you for your advice but in my case I didn't need to backup and restore TA to get back IMEI and working sim card. I'm just flash my stock 4.2.2 ftf that I backup before and everything is working fine now (both IMEI and sim).
---------- Post added at 05:50 PM ---------- Previous post was at 05:47 PM ----------
As per reply from 4.3 rooting thread, you can downgrad 4.2.2 from 4.3 without losing imei but you need to exclude baseband when you flash 4.2.2. :highfive:
Click to expand...
Click to collapse
Do I need to exclude kernel aswell when downgrading from 4.3.also do I select everything in flashtool in the section where it displays system,TA, kernel etc.lastly do I need to tick final verification? Thanks
adamo86 said:
Do I need to exclude kernel aswell when downgrading from 4.3.also do I select everything in flashtool in the section where it displays system,TA, kernel etc.lastly do I need to tick final verification? Thanks
Click to expand...
Click to collapse
It should be ok with just exclude baseband. If not wipe all data on phone.
hololodilolo said:
It should be ok with just exclude baseband. If not wipe all data on phone.
Click to expand...
Click to collapse
I tried to downgrade to 257 I used flashtool it flashed but remained on 4.3.now I can't use flashtool everytime I select a ftf it says can't open. Is it because it's a custom rom.please help.I tried different ftf even a 4.3 stock ftf.
adamo86 said:
I tried to downgrade to 257 I used flashtool it flashed but remained on 4.3.now I can't use flashtool everytime I select a ftf it says can't open. Is it because it's a custom rom.please help.I tried different ftf even a 4.3 stock ftf.
Click to expand...
Click to collapse
Try to restart your computer. If not OK, uninstall and reinstall flashtool. Try to redownload ftf as well. Good luck buddy.
I've also encountered the same problem after having downgraded from 4.3 to 4.22 with the intention of installing a custom rom.
I got so far as flashing a generic uk 4.22 ftf, rooting, backing up ta partition and trying to install dual recovery for LB but after a few attempts only TWRP would install and not CWM which is what I needed to install the rom and so decided to go back to stock and try again some other time.
Only now I have this Invalid Sim message and can't find a way to get my phone working as a phone again, this thread has mentioned a number of fixes but as I had to flash an old ftf first in order to root and continue, my backup ta was done after this problem surfaced and I do not have a copy of my original ftf so it would seem that what you guys tried won't work for me, anybody have any ideas?
Any help would be greatly appreciated...
DylanNeil said:
Only now I have this Invalid Sim message and can't find a way to get my phone working as a phone again, this thread has mentioned a number of fixes but as I had to flash an old ftf first in order to root and continue, my backup ta was done after this problem surfaced and I do not have a copy of my original ftf so it would seem that what you guys tried won't work for me, anybody have any ideas?
Any help would be greatly appreciated...
Click to expand...
Click to collapse
If you don't have your original FTF doesn't matter, download from here http://forum.xda-developers.com/showthread.php?t=2469191 the unbranded generic FTF and flash it to stock. Your phone will working back fine.
eclyptos said:
If you don't have your original FTF doesn't matter, download from here http://forum.xda-developers.com/showthread.php?t=2469191 the unbranded generic FTF and flash it to stock. Your phone will working back fine.
Click to expand...
Click to collapse
That did the trick, ta very much. Still having the same problem when I try to downgrade again though, I am going from .290 to .257 (I read somewhere that you have to go via .257 to reach the rooting promised land of .534) but still get the Invalid Card notice. I have done full factory resets, enabled USB Debug, ticked unkown sources, excluded baseband and not but no joy.
Seems a bit odd to me but there must be something I am missing... any ideas? All my firmware is generic UK btw.
If you are doing this to reach the .290 rooted like here http://forum.xda-developers.com/showthread.php?t=2572988 doesn't matter too, because you will update anyway so if you get some issues in downgrade state forget about that and complete the process. The update to .290 should fix them. Are you getting this problem on rooted .290?
I am trying to install the Criskelo rom ( http://forum.xda-developers.com/showthread.php?t=2560068 ) I got as far as installing dual recovery but I could only get TWRP working not CWM so stopped there and back tracked thinking I was doing something wrong. Not sure if the issue I have now would be fixed upon installing the rom, couldn't figure out why CWM wouldn't install and as the Invalid Card was the only other known issue I figured something went wrong in the downgrade process and have been working at that since...
DylanNeil said:
I am trying to install the Criskelo rom ( http://forum.xda-developers.com/showthread.php?t=2560068 ) I got as far as installing dual recovery but I could only get TWRP working not CWM so stopped there and back tracked thinking I was doing something wrong. Not sure if the issue I have now would be fixed upon installing the rom, couldn't figure out why CWM wouldn't install and as the Invalid Card was the only other known issue I figured something went wrong in the downgrade process and have been working at that since...
Click to expand...
Click to collapse
The update kernel of the Criskelo it's a .290 so probably it will fix this issue but if you flashed the recovery and you get only TWRP working and not CWM i don't know how this happen. There is 1 way to boot in TWRP and another one to boot in CWM.
network for sim with another carrier(airtel) but no network for my sim card(aircel)
hey guys please help ... after flashing a custom ROM vibeui 1.5(root+gapps) from needrom, I couldn't find network for my sim card.. but the signal bars are full if I insert a sim of another carrier... please help me guys...
I have searched countless of Forums and gone through Google alot and i still havnt found a solution yet, but coming from Stock Rom C6903_14.2.A.0.290 with Unlocked Bootloader and flashing PAC Man Rom in CWM succesful, but as soon as i get into the Rom, theres no Signal and i also checked my IMEI and it just says 0000000000...?? Is there anyway to restore the IMEI number to get the signal back somehow, or do i restore a Baseband or TA from another Stock Rom to get the signal/IMEI back..???
failbed said:
I have searched countless of Forums and gone through Google alot and i still havnt found a solution yet, but coming from Stock Rom C6903_14.2.A.0.290 with Unlocked Bootloader and flashing PAC Man Rom in CWM succesful, but as soon as i get into the Rom, theres no Signal and i also checked my IMEI and it just says 0000000000...?? Is there anyway to restore the IMEI number to get the signal back somehow, or do i restore a Baseband or TA from another Stock Rom to get the signal/IMEI back..???
Click to expand...
Click to collapse
My Xperia Z1 encountered the same problem after flashing C6903 14.1.G.1.534 Generic UK 1276-0875_R9A. The IMEI was changed to 00000000000000.
Here is the solution: Flashing C6903 14.2.A.0.290 Generic AU 1277-0078_R2B via Flashtool will restore IMEI (I got back IMEI)
http://forum.xda-developers.com/showthread.php?t=2469191
https://mega.co.nz/#!78x2yQaD!Plck0j1PkxnKI8hv2cBjcCiZE0FkkAM16FyQ5bgAbFg
tthaz777 said:
My Xperia Z1 encountered the same problem after flashing C6903 14.1.G.1.534 Generic UK 1276-0875_R9A. The IMEI was changed to 00000000000000.
Here is the solution: Flashing C6903 14.2.A.0.290 Generic AU 1277-0078_R2B via Flashtool will restore IMEI (I got back IMEI)
http://forum.xda-developers.com/showthread.php?t=2469191
https://mega.co.nz/#!78x2yQaD!Plck0j1PkxnKI8hv2cBjcCiZE0FkkAM16FyQ5bgAbFg
Click to expand...
Click to collapse
If you use flashtool to flash 4.3 ftf you will get problems like not having signal after flashing previous version (4.2) and the solution that worked for me is to reinstall software using SUS. After that I was able to get signal when flashing 4.2
Regards,
~J2C
Hi all,
Same problem here : upgrade to .290 and install the PAC ROM, the install is ok but no IMEI (so no connectivity). Is anyone know how to solve without losing the rom.
If I flash the original/stock ftf, it works again, but it's not the PAC ROM, so 1 win for 1 loss.
Thanks
Android 4.3 obviously changes something in the phone so that if you jump to another version it won't get signal or IMEI.
Anyway, the solution is simple.
Flash 290 and then 257. You'll get the signal and IMEI. If you want, you can go to 534 from 257 and then flash any ROM you want.
P.S: you don't have to flash 534, but you can do it if you want.
@Just2Cause
I unlock my BL so if I downgrade to 257, the camera will work or it will have the same "bug" as the 4.2 FW. after flashing to 257, do I need to stay on a 4.2 FW to keep the IMEI or can I flash the PAC ROM (which use a 4.3 FW) ?
Also, when I did the upgrade to .290 I use the sony companion app and it gave me no probleme (IMEI, call, sms was ok) it's specifically the PAC ROM that reset the IMEI. So I wonder what differs at low-level between the stock .290 and the PAC ROM, that can affect the IMEI
Tks
Download any .ftf (GENERIC is recommended) flash it using flashtool, and download the .ftf kernel for that specific ROM that you have flashed and flash it also using flashtool. i had the same problem downgrading from .290 to .534 i forgot to flash the kernel for .534 so i was stuck with IMEI 000000000.
Cheers
nicolas2b said:
@Just2Cause
I unlock my BL so if I downgrade to 257, the camera will work or it will have the same "bug" as the 4.2 FW. after flashing to 257, do I need to stay on a 4.2 FW to keep the IMEI or can I flash the PAC ROM (which use a 4.3 FW) ?
Also, when I did the upgrade to .290 I use the sony companion app and it gave me no probleme (IMEI, call, sms was ok) it's specifically the PAC ROM that reset the IMEI. So I wonder what differs at low-level between the stock .290 and the PAC ROM, that can affect the IMEI
Tks
Click to expand...
Click to collapse
It's not the PAC ROM that resets your IMEI, I also got same problem when I downgraded from 290 to 534.
I'm afraid that you will lose camera (not sure, just maybe) after downgrading you will be able to install PAC ROM without any problem.
There must be something in Sony 4.3 firmware that needs to be ported to other ROMS so the camera gets fixed.
I got it working!
IDK if you guys have figured it out yourselves but here is what I did...
After unlocking my bootloader on .290 I flashed the latest nightly build of PAC-man. Same as you guys My IMEI number was 000000000.
So what I did was flash [NUT]'s .534 ftf for downgrading to 4.2.2 (found here: http://nut.xperia-files.com/files/C6903_14.1.G.1.534_[NUT].ftf.torrent) which brought back my IMEI number!
From there I rooted my phone again, flashed the boot.img for recovery, flashed the latest build of PAC-man and tada! Everything is working.
Flash the latest firmware(.757), flash doomlord's advanced stock kernel(not the main one), flash the rom of your choice from there that includes kernel (like PAC) and now it REALLY is working.
534 nut for c6902
JDGG1993 said:
IDK if you guys have figured it out yourselves but here is what I did...
After unlocking my bootloader on .290 I flashed the latest nightly build of PAC-man. Same as you guys My IMEI number was 000000000.
So what I did was flash [NUT]'s .534 ftf for downgrading to 4.2.2 (found here: http://nut.xperia-files.com/files/C6903_14.1.G.1.534_[NUT].ftf.torrent) which brought back my IMEI number!
From there I rooted my phone again, flashed the boot.img for recovery, flashed the latest build of PAC-man and tada! Everything is working.
Click to expand...
Click to collapse
On nut.xperia-files.com there is no 534 rom for c6902 its only have c6903
Is it fine if i flash C6903_14.1.G.1.534_nut to my c6902...
I also have the problem with network. Not with this particular build, but with all AOSP roms. "Formatting boot, system, cache, data, and everything you see" will help my phone not recognizing (or invalid) sim? Are there network drivers I can flash from zip? Sorry for asking this, but I don't want to flash again and spend 3+hours figuring stuff out and then finding out later I can't call.. I need network to work as calling is what makes my device a phone, not a tablet. Help would really be appreciated.
I've used...
-LiquidsmoothBETA3 kitkat
-Paranoid Android BETA7
-Slimkat
-AOKP kitkat
My current rom in use: 14.3.A.0.757 (NUT). I start the process by flashing 14.1.G.1.534 (NUT) then adding root (Bin4ry) and dual recovery (NUT) before going to AOSP roms.
Model number - C6903
Sim card - Tmobile pre-pay.
Quote from a Thread in XDA:
01. if u are coming from stock to AOSP then Downgrade to 4.2 .534 FW having Root and a Recovery ( but i think if u downgraded to 4.3 .290 FW then also it will do the trick )
02. Follow the instruction in OP with the recommended instructions - "After 5th point in Recovery go to mounts and storage and then Format boot, format system, format catche, format data, format everything u see.. Except SDcard1 (ofc).. And then move to 6th point."
If u flash .757 before coming to PA or any other AOSP ROM's then u might have trouble
As u have already done Step 01 then do a Clean reflash again with step 02.. hopefully it will solve ur problems
Click to expand...
Click to collapse
Flashing from .757 gave me a bootloop. There are no more links to .290. Hmm...
Hello,
I recently bricked my Z1 and just got it back from warranty repaired. It is a C6906 that they upgraded to 4.3 (.290) however it is branded to BELL and I wish to flash the unbranded generic so I don't have as much bloatware/fast updates.
Since I do not wish to brick the device again and go through this again and so I am looking for advice to do this in a way that is guaranteed. With flashtool if I flash "C6906 14.2.A.0.290 Generic CA 1276-7484_R2B" would I have any issues at all? Just load up Flashtool - select the ftf and just use the default settings and plug in the Z1 while holding down the volume button.
I used the latest Flashtool v0.9.13, connected to PC, let install windows the drivers, selected the Unbranded Stock ftf, wiped all data, appslog, cache, all the rest unchecked and I performed the flash. All fine and the phone working well. I don't know why you had problems or why you bricked the phone but there is no advice to give you because it's simply. So even if all it's clear no guarantee and it's up to you. I don't think is the FTF faulty.
eclyptos said:
I used the latest Flashtool v0.9.13, connected to PC, let install windows the drivers, selected the Unbranded Stock ftf, wiped all data, appslog, cache, all the rest unchecked and I performed the flash. All fine and the phone working well. I don't know why you had problems or why you bricked the phone but there is no advice to give you because it's simply. So even if all it's clear no guarantee and it's up to you. I don't think is the FTF faulty.
Click to expand...
Click to collapse
This is separate from how I bricked it (using custom rom), I did this previously with a older version and just not on .290 and I am wondering if there is any issues (IMEI etc) doing it .290 to .290, thats all. I just don't want to make a mistake.
magwart said:
This is separate from how I bricked it (using custom rom), I did this previously with a older version and just not on .290 and I am wondering if there is any issues (IMEI etc) doing it .290 to .290, thats all. I just don't want to make a mistake.
Click to expand...
Click to collapse
Ok, so you bricked the phone with custon rom, now I understand. In this case there is no any issues flashing .290 unbranded on .290 branded. IMEI is lost only when jumping .257 and downgrade directly to .534. It's more "safe" flash .290 on .290. Go flash now.
eclyptos said:
Ok, so you bricked the phone with custon rom, now I understand. In this case there is no any issues flashing .290 unbranded on .290 branded. IMEI is lost only when jumping .257 and downgrade directly to .534. It's more "safe" flash .290 on .290. Go flash now.
Click to expand...
Click to collapse
Thanks. I don't suppose there is any working root for 4.3 yet, is there for the C9606?
Edit: Successfully flashed. Thanks again.
magwart said:
Thanks. I don't suppose there is any working root for 4.3 yet, is there for the C9606?
Click to expand...
Click to collapse
No direct root, like Vroot or 360, for .290 at the moment, just a method to get full root for Locked Bootladers. To do that you have to downgrade, root, install recovery then update to .290 again, a bit longer to get root on your phone, sure this method working for C6902/3 but should work for C6906 too, just check.
Would I be able to go from 290 branded to the new 136 intended without issue? I already bricked one device trying to root and I'm just trying to make sure lol
akusokuzan said:
Would I be able to go from 290 branded to the new 136 intended without issue? I already bricked one device trying to root and I'm just trying to make sure lol
Click to expand...
Click to collapse
Probably because when you bricked your phone was the time when some issues was not discovered yet in do that, and this confirm the fact on the thread now is wrote "How not brick your phone" . BTW, the risk to brick the phone is in downgrading so if you want just to upgrade without Root this way should be more "safe" and you will be able to do it without any issue.
eclyptos said:
Probably because when you bricked your phone was the time when some issues was not discovered yet in do that, and this confirm the fact on the thread now is wrote "How not brick your phone" . BTW, the risk to brick the phone is in downgrading so if you want just to upgrade without Root this way should be more "safe" and you will be able to do it without any issue.
Click to expand...
Click to collapse
Lol yeah, when I was trying to update with root, it didn't go so hot. That thread wasn't stickied until after the debacle. Sounds good though, thanks!
Hi guys this is my first post here so be gentle! I'm trying to get cyanogen mod on my Z1.
I have followed the guides on this forum, my appreciation to all involved here great job!
I downgraded to 4.2.2 from 4.3. I then rooted my the phone. I then unlocked the bootloader.
All went ok. I then downloaded C6903_14.2.A.0.290_1276-0875_Generic UK.ftf and flashed it. The phone then wouldn't turn back on.
So I downloaded C6903 14.1.G.1.534 EE UK 1276-2219_R9A (I'm on EE) and flashed that and I got the phone working again.
I then flashed DoomKernal to get CWM. DoomKernal went fine.
Somewhere along the line I think I got confused and thought DoomKernal would give me CWM and I flashed C6903_14.2.A.0.290_1276-0875_Generic UK.ftf again to upgrade back to 4.3.
Same problem...Phone wouldn't turn on so I repeated the EE branded 4.2.2 flash.
Now DoomKernal seems to be taken off. So my questions are as followed:
Do i need DoomKernal to get CWM?
Do i need to be on 4.4 before I install Cyanogen mod or can I do it straight from 4.2.2 with DoomKernal?
If I'm being a total noob I apologize!
Thanks.
Wizber said:
Hi guys this is my first post here so be gentle! I'm trying to get cyanogen mod on my Z1.
I have followed the guides on this forum, my appreciation to all involved here great job!
I downgraded to 4.2.2 from 4.3. I then rooted my the phone. I then unlocked the bootloader.
All went ok. I then downloaded C6903_14.2.A.0.290_1276-0875_Generic UK.ftf and flashed it. The phone then wouldn't turn back on.
So I downloaded C6903 14.1.G.1.534 EE UK 1276-2219_R9A (I'm on EE) and flashed that and I got the phone working again.
I then flashed DoomKernal to get CWM. DoomKernal went fine.
Somewhere along the line I think I got confused and thought DoomKernal would give me CWM and I flashed C6903_14.2.A.0.290_1276-0875_Generic UK.ftf again to upgrade back to 4.3.
Same problem...Phone wouldn't turn on so I repeated the EE branded 4.2.2 flash.
Now DoomKernal seems to be taken off. So my questions are as followed:
Do i need DoomKernal to get CWM?
Do i need to be on 4.4 before I install Cyanogen mod or can I do it straight from 4.2.2 with DoomKernal?
If I'm being a total noob I apologize!
Thanks.
Click to expand...
Click to collapse
Accidently gave you a thank lol
I actually don't know about branded phone, but I can tell you that your step has gone wrong. You will always lose root
if you flash a sock ftf file.
So you are saying you unlocked bootloader on the 534 rom? Your camera is probably dead now, check it if you can boot.
Unlocking bootloader before getting on 4.3 or 4.4 will result in disabling the camera. You did it now anyway, I can't help you. Maybe flash 4.4 now and see if your camera works again.
Flashing cyanogen is not about root but unlock bootloader, people would recommend you to root first becoz you will be able to do TA back up with root
(TA backup is a way to backup drm key, so you can restore it in the future and restore locked bootloader exclusive feature like X reality and better quality camera. Seems you don't know what I'm talking about and already unlocked the bootloader before you even ever heard about TA. Sorry can't help you to save this part, you may continue anyway)
So on 4.4, you may have to unlock the bootloader again since the bootloader itself maybe relocked itself when you flash a sock ftf file. ( doesn't mean you restored DRM key is back)
So maybe unlock it again and start to flash cm.
Personally I wouldnt recommend a newbie in Android to unlock bl so fast since it's too easy to mess up serious things up and it's not so easy for turning back. Well you started messing them up anyway, continue then
Thanks for the reply.
I did do a TA back up before I unlocked the bootloader....If i restore from this will it get the camera working?
I have tried to flash Cyanogen mod but it fails error 7. It thinks my Z1 is a Togari (Z ultra) which it isnt cant find anything on this!
Ok so, i'll try and get on 4.4...
I have a UK Z1 C6903.
Can I flash to C6903 14.3.A.0.681 Global 1277-2880_R5C (this is 4.4 right?)
OR does it have to be a UK one I cant seem to find a uk 4.4?
So after a bit of stress and the phone getting stuck in bootloop I have installed 4.4.2 using .681 commercial.
I hope it will be smooth sailing now to install cyanogen mod
Oh and the camera works again!
Wizber said:
Thanks for the reply.
I did do a TA back up before I unlocked the bootloader....If i restore from this will it get the camera working?
I have tried to flash Cyanogen mod but it fails error 7. It thinks my Z1 is a Togari (Z ultra) which it isnt cant find anything on this!
Ok so, i'll try and get on 4.4...
I have a UK Z1 C6903.
Can I flash to C6903 14.3.A.0.681 Global 1277-2880_R5C (this is 4.4 right?)
OR does it have to be a UK one I cant seem to find a uk 4.4?
Click to expand...
Click to collapse
happy to hear that u actually did TA backup
any 4.4 should be fine
after that install doomlord advanced stock kernel v2 i think
Hi,
I was trying to install the deodexed version of 4.4.2 Stock rom for my C6903
But it stuck at SONY logo,
so i flashed the older 4.2.2 FTF (C6903_14.1.G.1.534_1276-4314_R2A.ftf)
And now my phone is SIMLOCKED what the hell.
It did not have a simlock before, because in Belgium they don't do that.
Is there a way to get rid of it without unlocking bootloader to get full control of device kernel and ****...
FYI - I have a TA Backup of a working 4.2.2 and also of a working 4.4.2, might that help me getting rid of the simlock?
Thanks in advice
So now i did restore the TA Backup i had for 4.2.2
And guess what my imei number is gone,
and still no network ...
IMEI will come back if you flash a 4.3 or 4.4 FTF
SIMLOCK should have nothing to do with flashing FTFs
Try and flash a FTF from your original phone and try again
gregbradley said:
IMEI will come back if you flash a 4.3 or 4.4 FTF
SIMLOCK should have nothing to do with flashing FTFs
Try and flash a FTF from your original phone and try again
Click to expand...
Click to collapse
YES my sim is working again.
Thanks you for the support.
But one question left, always if my phone reboots i need to do the setup wizard again, set language and...
And the language also changes, i set it to dutch but on restart its back to english and i get the setup wizard?
Weird.
Xadaverth said:
But one question left, always if my phone reboots i need to do the setup wizard again, set language and...
And the language also changes, i set it to dutch but on restart its back to english and i get the setup wizard?
Weird.
Click to expand...
Click to collapse
I had the same problem, it happen when you flash a different FTF for your region, I updated to 4.3 and it disappear.
...btw if you execute a Factory Reset maybe it will fix the problem.