[Q] Can't update CM11 - Xperia Z Q&A, Help & Troubleshooting

Hi guys,
I'm new to Sony devices and rooting/flashing procedures.
I run CWM recovery 6.0.4.7 and CM11 with the included Kernel 3.4.0-g14fe8eb
As the title says: when I try to flash a cm11 rom, other than the one I'm currently on (2014-03-01), I end up in a bootloop (CM arrow doesn't stop spinning). When I try to restore a backup via recovery, I end up with a missing IMEI and thus a not working mobile radio. My procedure to fix this is: full wipe, flash the current nightly.
To me it doesn't make any sense that the IMEI is missing after a restore (when I created the backup everything was fine). What is the correct procedure to update to the next nightly?
Best regards,
bumbum

Related

Can't install Cyanogen ! Always boot loop

Hi! When i install cyanogenmod, i always got problems.
Example 1:
-Cm installed and boot
-Tomorrow big problem (no network)
-reflash stock rom
-Boot loop
-Go to recovery and flash again
-Boot loop
-Need to flash official rom with nvflash and reroot
Example2:
- Cm installed, block at lg logo
- Rewipe and reflash from cwm
- flash stock rom
- Boot loop
-Retry
-Boot loop
-Reflash official and reroot.
- Reinstal redownloaded cm
- Block lg logo
......
-Flash stock
-Boot loop
How can i flash stock to cm, cm to stock in freedom without bootloop like on a htc device ?(i never had this problem on the htc desire)
Sent from my LG-P990 using XDA App
This is NOT development-related.
You are supposed to post this in the "General" Section or "Q&A" Section.
alvinm93 said:
How can i flash stock to cm, cm to stock in freedom without bootloop like on a htc device ?(i never had this problem on the htc desire)
Click to expand...
Click to collapse
CM7 has ext4 partition. Stock rom no.
Use Paul's back2ext3 tool to convert to ext3 (see here).
no network issue is because the cm7 have a different ril than the stock rom, and if you flash a new rom via cwm, the baseband remain intact, so the baseband and the rom ril module is not match, cause the no network issue.
if you want to go back the stock use the nandroid restore or nvfalsh instead of a simple cwm update.
you should see this thread before flashing
Code:
http://forum.xda-developers.com/showthread.php?t=1058254]
and for network, you should flash ril with your current baseband. you can use get rill app. don't use GB baseband use froyo baseband
Thanks a lot for your answers! I did not know CM use ext4. And for RIL i've flashed 0725 baseband, cyanogen says that it is the baseband recommended, but in GetRil it's appear "The ril and baseband do not correspond" and i've downloaded another who "correspond", now i think that is the problem.

[Q] Recovery doesn't "stick"?!

Hello guys,
I would like to flash a different version of CWM onto my N7000 but somehow it does not stick.
I currently run AOKP 4.1.2 and it has 6.0.1.5 as CWM which always gives you the md5 generation error when you do a nandroid backup.
I've installed Rom Manager and downloaded a different version of CWM and tried to install it both with Rom manager and also in CWM itself.
On the first boot after I flash some other recovery like the one from rom Manager (6.0.1.2) it actually loads the new recovery and lets me do a sucessful nandroid for example, but when i reboot into recovery another time the old recovery is back.
When I flash a new rom though, the CWM does get permanently replaced. I flashed a different rom which came with CWM 6.0.2.8 and then I permanently had that version. (same behaviour when I tried to overwrite it with the 6.0.1.2, wouldnt stick).
I even tried just partially restoring the nandroid and leaving boot out, but then phone will get stuck on boot.
Is there any way to permanently flash a recovery to the note without overwriting the whole boot.img? CWM and Rom Manager do not seem to be able. Maybe Heimdall or ODIN? Been so long since I had to use them..
Hope someone knows whats goin on with the recoveries.?!
because the recovery is in the kernel. to change recovery, you need to change the kernel. MD5 error is a known bug in AOKP.
you can use this
https://play.google.com/store/apps/...wsMSwxLDIxMiwiY29tLmgzcjN0MWMub25uYW5kYnVwIl0.
to make a nandroid backup on AOKP roms
nokiamodeln91 said:
because the recovery is in the kernel. to change recovery, you need to change the kernel. MD5 error is a known bug in AOKP.
you can use this
https://play.google.com/store/apps/...wsMSwxLDIxMiwiY29tLmgzcjN0MWMub25uYW5kYnVwIl0.
to make a nandroid backup on AOKP roms
Click to expand...
Click to collapse
thanks man, yea i got some tools installed that should be able to do a nandroid from running system, was just wondering if there is a way to permanently switch the recovery - it is sometimes booted, right after flash but then its gone - so there must be a way to stop the restore or?
Or are there any custom aokp kernels out there for the n7000? usually they only support TW or CM as far as I saw, or only older versions.

[Q] Very wierd problem while restoring nandroid backup : loosing all user data.

Hi Devs.
I am using Cocore kernal and my mobile is rooted. I have cwm 6. I took backup of my stock rom and after that i moved to Cm11. I installed few apps on cm11 after that i took backup of cm11 also. After That I have installed PACROM and i have backup of that rom also.
Now I have Nandroid backup of all three ROMs( STOCK, CM and PAC)
Then i have decided to restore my stock ROM . Everything went well but when it started it start without any user data and start in start up wizard with message goole.process fail and i got stuck in setting wizard.
After that i tried to restore CM and This time CM start as new rom without gapps and user data but works very fine.
Finally I try to restore pac and it comes out with same result as CM.
Now whenever i restore my backup it restore only rom but no user data or apps.
After that i tried many solution.
I have found one problem in recovery that failed to mount preload
I have fixed the permission but unable to mount preload .
I found one wierd solution to restore stock with data. : First i restore it in CWM after that i reboot my device in download mode and i flash stock JB via odin on my device and suddenly my stock rom start working with all user data
But this solution works with only stock backup and i don't want to restore stock every time via odin.
So please help me to solve this problem.
androiddoctor said:
Hi Devs.
I am using Cocore kernal and my mobile is rooted. I have cwm 6. I took backup of my stock rom and after that i moved to Cm11. I installed few apps on cm11 after that i took backup of cm11 also. After That I have installed PACROM and i have backup of that rom also.
Now I have Nandroid backup of all three ROMs( STOCK, CM and PAC)
Then i have decided to restore my stock ROM . Everything went well but when it started it start without any user data and start in start up wizard with message goole.process fail and i got stuck in setting wizard.
After that i tried to restore CM and This time CM start as new rom without gapps and user data but works very fine.
Finally I try to restore pac and it comes out with same result as CM.
Now whenever i restore my backup it restore only rom but no user data or apps.
After that i tried many solution.
I have found one problem in recovery that failed to mount preload
I have fixed the permission but unable to mount preload .
I found one wierd solution to restore stock with data. : First i restore it in CWM after that i reboot my device in download mode and i flash stock JB via odin on my device and suddenly my stock rom start working with all user data
But this solution works with only stock backup and i don't want to restore stock every time via odin.
So please help me to solve this problem.
Click to expand...
Click to collapse
When you want to go back from CM 11 and 10.2 to previous version of Android you must either to format Prelaod parition, or flash stock JB. On those two versions developers are using that partition as SWAP, so it is has differend format and can't be used for files that should be there on previous versions.
Solution 1: http://forum.xda-developers.com/showthread.php?t=2612540
Solution 2: What you did, flash stock JB from Odin.

[Q] Stock Android Backup

Hlo Everyone,
I Am a Newbie To Custom Android Roms on Galaxy S Advance .I am on Stock JB with Cocore Kernel And Twrp . I Want To ask if i make a nandroid backup of stock android and try to install other custom rom ,can i revert back to stock jb via backup in case problem arises ...
I had tried this on a different phone but at that time it said md5 sum mismatch .
So Simply I am asking u can i revert back to stock jb via twrp recovery ...
Waiting for reply From GS Advance users ...
SultanRTS said:
Hlo Everyone,
I Am a Newbie To Custom Android Roms on Galaxy S Advance .I am on Stock JB with Cocore Kernel And Twrp . I Want To ask if i make a nandroid backup of stock android and try to install other custom rom ,can i revert back to stock jb via backup in case problem arises ...
I had tried this on a different phone but at that time it said md5 sum mismatch .
So Simply I am asking u can i revert back to stock jb via twrp recovery ...
Waiting for reply From GS Advance users ...
Click to expand...
Click to collapse
That mismatch happen because of bad backup I think. You can if you are on other stock based or on CM10.1. For CM10.2 and CM11 ROMs you must repartiton preload partition to be able to do that. HOW.
SultanRTS said:
Hlo Everyone,
I Am a Newbie To Custom Android Roms on Galaxy S Advance .I am on Stock JB with Cocore Kernel And Twrp . I Want To ask if i make a nandroid backup of stock android and try to install other custom rom ,can i revert back to stock jb via backup in case problem arises ...
I had tried this on a different phone but at that time it said md5 sum mismatch .
So Simply I am asking u can i revert back to stock jb via twrp recovery ...
Waiting for reply From GS Advance users ...
Click to expand...
Click to collapse
It is possible.
that md5 sum mismatch you had on different phone was most probably related to corrupted backup file - not related with current ROM installed as long as backup is not cross recovery (CWM / TWRP).
I have lost one backup same way due to corrupted files.
To be sure that it will work you can try to restore backup just after it was created - if it will work, then it should work later on.
if you will be trying CM11 revert procedure is a bit more tricky (as /preload partition is used differently than in stock):
it might need odin flash of stock, install CoCore, restore backup
EDIT ... or faster way presented by shut_down ;]
th3cr0w said:
It is possible.
that md5 sum mismatch you had on different phone was most probably related to corrupted backup file - not related with current ROM installed as long as backup is not cross recovery (CWM / TWRP).
I have lost one backup same way due to corrupted files.
To be sure that it will work you can try to restore backup just after it was created - if it will work, then it should work later on.
if you will be trying CM11 revert procedure is a bit more tricky (as /preload partition is used differently than in stock):
it might need odin flash of stock, install CoCore, restore backup
EDIT ... or faster way presented by shut_down ;]
Click to expand...
Click to collapse
I had tried this on galaxy fit ,but there also i got same problem and i had to use odin to get stock back ... i don't want to go over the same pls help me.my phone is hanging a lot and i cant stay on stock so pls help me
To be sure it is not corrupted backup file you can perform restore backup just after it was created.
If it is corrupted due to some reason it will not work from the beginning.
If it go smooth you are sure that you got correct backup - just store it some place safe (not on crappy SD that might go corrupt over time or sth ...)
At that point it is safe to assume it will work as system restore point from any custom ROM back to state of when it was made (official JB with cocore and all your apps / contacts / messages / etc already in place) - with exception of CM10.2 and CM11 ROMS (and those that are based on them) as explained already - those ROMs would need one extra step before reverting (but it is still possible, just not as straight forward as on other ROMs)

[i9000] CM11 (4.4.4) Baseband Unknown, Wi-Fi Grayed out, No sim service

Hey guys, seems that the latest builds of CM11 (4.4.4) have the same problems on my phone.
Country: Romania (Europe)
- I have an i9000 with CWM Recovery 6.0.4.7
- I'm trying to flash CM11 4.4.4 (last i tried: cm-11-20140729-NIGHTLY-galaxysmtd) from CM11 4.4.2 (cm-11-2014-02-28--NIGHTLY-galaxysmtd -> XXJVU)
- I did WipeData/FactoryReset, Wipe Cache, Wipe DalvikCache and Format /System, after that I flashed "cm-11-20140729-NIGHTLY-galaxysmtd" (CM11-4.4.4), and flashed GAPPS for 4.4.2 (i tried with 4.4.3 too), and reboot (i get no errors)
- The ROM boots up and everything seems to be okay besides the fact that i have no sim service (no signal bars, or pin code pop-up checker at startup), at "About Phone" i get "Baseband version Unknown", Wi-Fi is grayed and it's freezed ("Turning Wi-Fi on..." forever), Bluetooth it's not grayed out, but once i enable it, the "on" button goes gray and it does nothing, also when i go to "About Phone" -> "Status", the Settings app crashes.
I tried to flash a stock radio/modem (XXJVT, XXJVU) in hope that would fix the problem but no change.
I tried to do another wipedata/factoryreset, wipe cache, wipe dalvik after installing the rom and gapps and cleared the data and cache for "Settings" app and others but still with no succes in fixing something.
I tried the M8 build and other close nightlies, all seem to have the same problem.
If i flash my old rom back, everything is working perfect.
HELP! Any solutions to this?
Thank you guys in advance!
I had the same problem yesterday. Try to re-install the ROM. If it still doesn't work then flash a stock ROM (JW4) with Odin and then install 4.4.4 again. The last one worked for me.
kalpetros said:
I had the same problem yesterday. Try to re-install the ROM. If it still doesn't work then flash a stock ROM (JW4) with Odin and then install 4.4.4 again. The last one worked for me.
Click to expand...
Click to collapse
After you flashed the stock firmware (JW4 aka GingerBread 2.3.6) what and how did you flash a recovery that is able to install CM11 4.4.4 Roms?
EDIT (FIXED IT):
This solved the issues that i talked about in the main post
I was on CM11 4.4.2, entered recovery and did full wipe
- I flashed stock firmware for i9000 Sweden (JW4 Gingerbread 2.3.6) via Odin
- I flashed root for it wich included a cwm recovery 3.0.0.x
- Entered the recovery which the root installed and did a full wipe
- Flashed directly "cm-11-20140729-NIGHTLY-galaxysmtd", after which the phone rebooted in a different cwm recovery (6.0.5.0) and installed the rom and rebooted again
- After reboot, the phone booted directly in the new cwm recovery 6.0.5.0, and i did a full wipe
- Flashed again "cm-11-20140729-NIGHTLY-galaxysmtd" and "gapps-kk-20140606" and now the rom (cm11 4.4.4) works perfect with no more problems
Thanks to kalpetros that initiated me in solving my problem with his solving solution (http://forum.xda-developers.com/member.php?u=5359865)
MihaiDani93 said:
After you flashed the stock firmware (JW4 aka GingerBread 2.3.6) what and how did you flashed a recovery that is able ti install CM11 4.4.4 Roms?
Click to expand...
Click to collapse
CM10.2 contains such recovery. On your place I would flash stock JVU to get for sure last Gingerbread bootloader (JWx don't contain it). As your system and data partitions have been resized you MUST flash together with firmware also the PIT file 512 and enable repartition in Odin, use version 1.82 or 1.83 for that and run it as administrator.
Safer way for not to loose IMEI anymore is to upgrade stepwise (GB,ICS,JB,KK) so first CM9, then CM10.2, then CM11
tetakpatalked from N7100
tetakpatak said:
CM10.2 contains such recovery. On your place I would flash stock JVU to get for sure last Gingerbread bootloader (JWx don't contain it). As your system and data partitions have been resized you MUST flash together with firmware also the PIT file 512 and enable repartition in Odin, use version 1.82 or 1.83 for that and run it as administrator.
Safer way for not to loose IMEI anymore is to upgrade stepwise (GB,ICS,JB,KK) so first CM9, then CM10.2, then CM11
tetakpatalked from N7100
Click to expand...
Click to collapse
I didn't lost the imei (or so i think). I just had no service, no enabled sim. (no "imei lost" warning messages)

Categories

Resources