So, I've just unlocked the bootloader on my Z1. Followed the instructions on the Sony website and it went off without a hitch. I then followed the instructions on the Cyanogenmod website to install the boot.img from the ROM file. This also seemed to to proceed without issue and I was able to boot the phone into recovery mode.
Unfortunately it all went wrong from here as whenever I install a ROM, I can't seem to get the phone to boot up, it hangs at the boot animation. I've tried various different ROMs and they all do the same thing. I've tried installing various stock ROMs and flashing the FTF file but that doesn't work either. I've even tried restoring it using the PC Companion software but it won't do anything because it says the software is modified and won't update it.
I don't suppose anyone would have any ideas? Perhaps someone with a more technical knowledge of such things?
What program are you using to flash the FTF files?
Are you using the ones for your model?
Did you buy your phone used or was it new?
Try this to get CM on the Z1
There is no official stable build on the CM website.
Also, if you flash other ROMS whilst you have a CM kernel, you will get a bootloop unless the Roms are based on that kernel.
Follow the links in the thread I gave you to download a CM11 build (Android 4.4) and then you can just flash the update.zip in recovery.
Job done.
Seems odd, that even flashing FTF files didn't help... Weird stuff.
Try flashing Cyanogenmod again, but performing full data wipe.
Does the cm boot animation hang and like not move or just spin forever and is actually moving?
Poesini said:
What program are you using to flash the FTF files?
Are you using the ones for your model?
Did you buy your phone used or was it new?
Click to expand...
Click to collapse
I bought it brand new, was using Flashtool. I was using the correct ones for my model (C6903).
gregbradley said:
Try this to get CM on the Z1
There is no official stable build on the CM website.
Also, if you flash other ROMS whilst you have a CM kernel, you will get a bootloop unless the Roms are based on that kernel.
Follow the links in the thread I gave you to download a CM11 build (Android 4.4) and then you can just flash the update.zip in recovery.
Job done.
Click to expand...
Click to collapse
Think I've already tried that, but I'll give it another try.
SquiffyGrain6 said:
Seems odd, that even flashing FTF files didn't help... Weird stuff.
Try flashing Cyanogenmod again, but performing full data wipe.
Does the cm boot animation hang and like not move or just spin forever and is actually moving?
Click to expand...
Click to collapse
CM and some other ROMs don't hang, it just carries on animating indefinitely.
I have noticed that recovery seems to have some issues though. When I do a wipe on CWM, it says "error mounting \data" and something else as well.
You can try manually flashing /data
Do you know how to install TWRP recovery?
I remember writing a guide of formatting the partitions manually (adb shell) via mkfs.f2fs (in that case, f2fs), but it can be done the same way with mkfs.ext4
If you have problems with /data partition you definitely should wipe it. As suggested above, the manual method might work the best for you, and it is as follows:
Boot into recovery and make sure you have adb working and your computer recognizes your device. Then use this commands, pressing enter at the end of each line. I remember using them myself, so this should work:
adb shell
recovery --wipe_data
Notice double - in the second line. Write precisely as above and after that reboot. With a little bit of luck your phone will boot into Cyanogen.
If that method doesn't work (I really don't know, but I'm sure this would work better), try this one:
http://forum.xda-developers.com/showpost.php?p=51517202&postcount=542
And change every part that says f2fs to ext4, so it gets like this:
Go to recovery (TWRP) and then go to command input:
cd /dev/block/platform/msm_sdcc.1/by-name/
mkfs.ext4 -l cache cache
mkfs.ext4 -l data userdata
mkfs.ext4 -l system system
Now set in advanced settings to "rm -rf instead of wipe" and then wipe data and internal storage
Related
i'm running the ''stable'' version of cm 5.0.8, amon recovery, blah blah blah. i was browsing the internet today when all of a sudden my phone starts saying that android process acore was force closing. this happened about 5 times before i decided to reboot the phone. when i went to reboot, i got stuck on the g1 screen......greeeaaaaaaat. so i go into recovery, find my nandroid backup and press home to restore it. currently my phone screen consists of an HTC logo and a never-ending stream of periods. usually it only takes about 4 or 5 lines for my phone to restore a nadroid backup. what should i do?
Besides wipe/reinstall?
You can try the more advance manual install (simple if you are used to a Linux commandline).. copy the nandroid backup to your computer and run:
Code:
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase boot
fastboot flash userdata data.img
(Data.img is part of the nandroid backup)
Now rebuild system:
Return to recovery: wipe dalvik cache and flash cm5.0.8 + gapps
If you have nandroid+ext you can restore that by erasing the ext partition and using tar to extract the backup before booting cm.
Also make sure you are running the latest ra-recovery the older ones have an issue with the missing /system/sd directory unless you manually created it..
first off, thanks sooo much for the speedy reply. this forum and the members here are AWESOME. back to business, the nandroid backup never did finish, so i took a huge risk and pulled the battery, and rebooted. and voila it magically works now EXCEPT i booted to the registration screen saying "UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable.'' thats a helluva lot better than a brick i guess, just annoying as ****. so im guessing to wipe the data partititon i have to go into recovery and select ''wipe''?
update;oh, im also getting a force close error with gapps now. which im guessing means that i need to flash a new gapps package via recovery?
I had the same issue. Apparently it's a dalvik-cache issue. Check this link for the solution:
http://goo.gl/s7tr (off-site link to Cyanogen forum)
well i got the uid message to go away by rebooting to recovery and slecting "fix uid mismatches''. gapps isnt acting up anymore (although i could not find the gapps zip file...help?!), but now im missing some apps and everytime i try to download something from market it just fails.
BuddhaTeh1337 said:
but now im missing some apps
Click to expand...
Click to collapse
You could try reflashing Gapps
theartar said:
You could try reflashing Gapps
Click to expand...
Click to collapse
where could i find the latest gapps update? and that flashes the same way as themes and ROMs correct?
Update; ok well i just flashed CM again, did a factory reset/wipe and i am STILL looking for gapps to flash...
update 2; found it. just have to flash now.
I know you already found it, but for future reference I always grab it off the Cyanogen site. Here's a direct link: http://kanged.net/mirror/download.php?file=gapps-ds-ERE36B-signed.zip
Flash CM, don't reboot, then Gapps, then reboot. Good luck.
theartar said:
I know you already found it, but for future reference I always grab it off the Cyanogen site. Here's a direct link: http://kanged.net/mirror/download.php?file=gapps-ds-ERE36B-signed.zip
Flash CM, don't reboot, then Gapps, then reboot. Good luck.
Click to expand...
Click to collapse
yup, thats the exact one i installed. all my apps are still there EXCEPT maps.....which wont install for some reason now......i just fixed UID mismatches via recovery and hoping that fixes it.
Update; it did.
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!
Hello All,
I am on stock v4.1.2, flashed myself.
Now I want to move on to custom ROM.
My current stock ROM is rooted, and I have also unlocked my bootloader.
Now when I want to install custom ROM, I need to flash CWM, and when I do (tried v6.2.8 and v6.0.3.1), and install any ROM, my WiFi becomes unresponsive (failed to turn on). When I flash V20A back, everything turns normal.
I also gone through http://forum.xda-developers.com/showthread.php?t=2180138&page=43, and install the unsecure boot image after installing CWM 6028, but this make my custom rom hang on startup (on bootload screen).
Kindly help me out.
I have search a lot in the P880 forum, and didn't find any help regarding to this problem.
[email protected] said:
Hello All,
I am on stock v4.1.2, flashed myself.
Now I want to move on to custom ROM.
My current stock ROM is rooted, and I have also unlocked my bootloader.
Now when I want to install custom ROM, I need to flash CWM, and when I do (tried v6.2.8 and v6.0.3.1), and install any ROM, my WiFi becomes unresponsive (failed to turn on). When I flash V20A back, everything turns normal.
I also gone through http://forum.xda-developers.com/showthread.php?t=2180138&page=43, and install the unsecure boot image after installing CWM 6028, but this make my custom rom hang on startup (on bootload screen).
Kindly help me out.
I have search a lot in the P880 forum, and didn't find any help regarding to this problem.
Click to expand...
Click to collapse
i dont understand what the recovery has to do with the wifi. recovery is just an interface to easy install something, copy paste , edit , change permissions , etc , things we do using adb commands. it is just an environment. its something else u are doing wrong there.
<EDIT> yea i saw the thread on your link. others seem to have same problem but with the unsecure boot. why do u need unsecure boot if the bootloader is unlocked ? just install teamwin recovery or cwm recovery and the rom u want.
kessaras said:
i dont understand what the recovery has to do with the wifi. recovery is just an interface to easy install something, copy paste , edit , change permissions , etc , things we do using adb commands. it is just an environment. its something else u are doing wrong there.
<EDIT> yea i saw the thread on your link. others seem to have same problem but with the unsecure boot. why do u need unsecure boot if the bootloader is unlocked ? just install teamwin recovery or cwm recovery and the rom u want.
Click to expand...
Click to collapse
Well, I did. And it all went fine, and I am able to install various custom ROMs, and after I install custom ROM, my WiFi becomes unresponsive. I am completely at lost. I also tried MIUI v5 which is non-CM10.2 based, and it also showed the same issue.
Here are my steps to install a custom ROM.
- Currently I am on my V20A stock ROM.
- Root the stock ROM using the All-In-One-Toolkit v1.4.1
- Flush the CWM 6031 using ADB as
Code:
su
cat /mnt/sdcard/recovery.img > /dev/block/mmcblk0p1
sync
- After reboot, my device has the CWM.
- Copy custom ROM zip files to my device, and reboot to recovery
- Wipe out by data and cache
- Install ROM
thats it
And when I boot into the new custom ROM, my WiFi do not work.
Please help.
[email protected] said:
Well, I did. And it all went fine, and I am able to install various custom ROMs, and after I install custom ROM, my WiFi becomes unresponsive. I am completely at lost. I also tried MIUI v5 which is non-CM10.2 based, and it also showed the same issue.
Here are my steps to install a custom ROM.
- Currently I am on my V20A stock ROM.
- Root the stock ROM using the All-In-One-Toolkit v1.4.1
- Flush the CWM 6031 using ADB as
Code:
su
cat /mnt/sdcard/recovery.img > /dev/block/mmcblk0p1
sync
- After reboot, my device has the CWM.
- Copy custom ROM zip files to my device, and reboot to recovery
- Wipe out by data and cache
- Install ROM
thats it
And when I boot into the new custom ROM, my WiFi do not work.
Please help.
Click to expand...
Click to collapse
not exactly.
And here are my steps to install a custom ROM (if currently I am on my V20A stock ROM)
1. Root the stock ROM using the All-In-One-Toolkit v1.4.1
2. Unlock bootloader using All-In-One-Toolkit v1.4.1 or manually like this.
3. Flash the CWM 6.0.4.5 or 6.0.4.4 or TeamWin Recovery
4. Reboot the device in recovery.
5. Enter ADB sideload and install custom rom or using ADB bootloader or using ADB copy the rom in sd card and use install in recovery.
6. Wipe data and cache and reboot system.
<<STEPS DESCRIBED IN HELP SECTION - FREQUENTLY ASKED QUESTIONS>> ( by the way those must be updated too )
kessaras said:
not exactly.
And here are my steps to install a custom ROM (if currently I am on my V20A stock ROM)
1. Root the stock ROM using the All-In-One-Toolkit v1.4.1
2. Unlock bootloader using All-In-One-Toolkit v1.4.1 or manually like this.
3. Flash the CWM 6.0.4.5 or 6.0.4.4 or TeamWin Recovery
4. Reboot the device in recovery.
5. Enter ADB sideload and install custom rom or using ADB bootloader or using ADB copy the rom in sd card and use install in recovery.
6. Wipe data and cache and reboot system.
<<STEPS DESCRIBED IN HELP SECTION - FREQUENTLY ASKED QUESTIONS>> ( by the way those must be updated too )
Click to expand...
Click to collapse
I did wipe the data and cache after installing the custom ROM. But the result is the same; No WiFi response.
However, I always copy my custom ROMs by mounting my phone through USB to my Win8 laptop, and then copy the ROM file through windows explorer. And then install the ROM from the CWN recovery. Thus do not use ADB for copying files, or installing custom ROM as mentioned above. If this is the main issue reason, then advice.
Also I haven't tried TWRP till yet. Will do now. Till then, what else I can do.
Thanks for the quick replies.
i dont know what else you may doing wrong then. one was the insecure boot which is useless since u have unlocked the bootloader and the other that u had flash older version of cwm recovery. maybe compatibility issue with that version of cwm rec ? test and see.
format system also, when installing a new rom, not just data, cache & dalvik
kessaras said:
i dont know what else you may doing wrong then. one was the insecure boot which is useless since u have unlocked the bootloader and the other that u had flash older version of cwm recovery. maybe compatibility issue with that version of cwm rec ? test and see.
Click to expand...
Click to collapse
One piece of detail I missed to mentioned in my case previously was that, I unlocked my phone using the method mentioned in the thread http://forum.xda-developers.com/showthread.php?t=2263627 as I was unable to unlock using the official method.
After I unlock my bootloader, I have flashed V20A KDZ several times, and each time the SW Upd mode show me that my bootloader status is unlocked. Thus after first attempt of unlocking, I never came across need to unlocked my bootloader again as each time when I do the KDZ flash, I get the bootloader status as unlocked. And after each flash of KDZ, I was able to install CWM and custom ROMs, and boot into them successfully.
Is this something causing the issue?
[email protected] said:
One piece of detail I missed to mentioned in my case previously was that, I unlocked my phone using the method mentioned in the thread http://forum.xda-developers.com/showthread.php?t=2263627 as I was unable to unlock using the official method.
After I unlock my bootloader, I have flashed V20A KDZ several times, and each time the SW Upd mode show me that my bootloader status is unlocked. Thus after first attempt of unlocking, I never came across need to unlocked my bootloader again as each time when I do the KDZ flash, I get the bootloader status as unlocked. And after each flash of KDZ, I was able to install CWM and custom ROMs, and boot into them successfully.
Is this something causing the issue?
Click to expand...
Click to collapse
Now, I have repeated using CWM 6.0.4.5 and TWRP, and no breakthrough .... Starting to lose hope ... Help !!!
sorry , personally i dont know what else u may doing wrong there . and no it doesnt matter which way u unlock the phone, but since u unlock it , it stays that way until u lock it.
at least stock rom is working fine ? if that works fine there, then just install only custom kernel, do your tweaks, install another launcher and then delete the default, etc. u can do any modification u like to the stock one to make it look and work the way u want it.
kessaras said:
sorry , personally i dont know what else u may doing wrong there . and no it doesnt matter which way u unlock the phone, but since u unlock it , it stays that way until u lock it.
at least stock rom is working fine ? if that works fine there, then just install only custom kernel, do your tweaks, install another launcher and then delete the default, etc. u can do any modification u like to the stock one to make it look and work the way u want it.
Click to expand...
Click to collapse
Does it help if I installed a custom kernel on my custom ROM (with WiFi issue). My understanding is that the WiFi driver is compiled inside the kernel. So changing the kernel might reduce the issue. What do you think? If yes, then kindly advice me on which kernel should I install on my till now custom ROM MIUI v5 http://en.miui.com/download-79.html.
[email protected] said:
Does it help if I installed a custom kernel on my custom ROM (with WiFi issue). My understanding is that the WiFi driver is compiled inside the kernel. So changing the kernel might reduce the issue. What do you think? If yes, then kindly advice me on which kernel should I install on my till now custom ROM MIUI v5 http://en.miui.com/download-79.html.
Click to expand...
Click to collapse
a developer would never release a rom in public with wifi issues by default and since i have already tested all roms available before i end up to one, i can say that they all worked , but only had small bugs on homescreen. really i dont know what you are doing wrong and not even a teamviewer connection wouldnt help in this case. but on stock your phone works fine ? only in a custom rom u have this issue ?
<<EDIT>> did you also do a full format before going to another rom ? there is a choice in teamwin recovery ( dont know if its in cwm also ) to format data. careful i dont mean to wipe everything you see because you will remove the recovery too and u will have to flash it back. the format option deletes everything besides the recovery. if you dont format before you go to a totally different rom, then you maybe have issues. especially when going from stock to custom, differences are huge. you must format before flashing. and dont forget the gapps, if they are not inluded in rom. ( in your case miui there must have them inside, because i see its 256 mb+)
kessaras said:
a developer would never release a rom in public with wifi issues by default and since i have already tested all roms available before i end up to one, i can say that they all worked , but only had small bugs on homescreen. really i dont know what you are doing wrong and not even a teamviewer connection wouldnt help in this case. but on stock your phone works fine ? only in a custom rom u have this issue ?
<<EDIT>> did you also do a full format before going to another rom ? there is a choice in teamwin recovery ( dont know if its in cwm also ) to format data. careful i dont mean to wipe everything you see because you will remove the recovery too and u will have to flash it back. the format option deletes everything besides the recovery. if you dont format before you go to a totally different rom, then you maybe have issues. especially when going from stock to custom, differences are huge. you must format before flashing. and dont forget the gapps, if they are not inluded in rom. ( in your case miui there must have them inside, because i see its 256 mb+)
Click to expand...
Click to collapse
YES. When I flashed stock V20A, I never had issues with Wifi. Its when I install custom ROM, and any custom ROM.
So I suppose, either there is something wrong in my installing method, or in my stock ROM that won't allow WiFi to work on any custom ROM. But how much influential will be the stock ROM if it is being replaced by a custom ROM?
Well, I haven't formated before I install any custom ROM, as it was not instructed in the forums. But I will do that now, and let you know the results shortly.
Thanks again for the replies.
[email protected] said:
Well, I haven't formated before I install any custom ROM, as it was not instructed in the forums.
Click to expand...
Click to collapse
yea some informations are always missing from the instructions generally , but this is a developer forum , so it doesnt always include informations that are 100% well known to be done. So format and install again and tell me if its everything ok.
kessaras said:
yea some informations are always missing from the instructions generally , but this is a developer forum , so it doesnt always include informations that are 100% well known to be done. So format and install again and tell me if its everything ok.
Click to expand...
Click to collapse
Can you direct me how to install a custom ROM using ADB? Since when I format my /data, all of my custom roms that I copied will get deleted. So the only remaining option is to copy them using ADB.
[email protected] said:
Can you direct me how to install a custom ROM using ADB? Since when I format my /data, all of my custom roms that I copied will get deleted. So the only remaining option is to copy them using ADB.
Click to expand...
Click to collapse
What?????
Why would wiping your /data folder on internal storage delete your custom ROMs? Surely you keep them on your external SD-Card?
[email protected] said:
Can you direct me how to install a custom ROM using ADB? Since when I format my /data, all of my custom roms that I copied will get deleted. So the only remaining option is to copy them using ADB.
Click to expand...
Click to collapse
you dont need to copy it . u can open adb sideload from recovery and on pc use command : adb sideload [path/filename of rom.zip]
SimonTS said:
What?????
Why would wiping your /data folder on internal storage delete your custom ROMs? Surely you keep them on your external SD-Card?
Click to expand...
Click to collapse
So you are saying that, I copy them to external_sd, and then do the data format. Ok ... Will do and let you know.
BTW, I also found V20B. I will start with this stock rom instead of V20A. This might improves some thing.
[email protected] said:
So you are saying that, I copy them to external_sd, and then do the data format. Ok ... Will do and let you know.
BTW, I also found V20B. I will start with this stock rom instead of V20A. This might improves some thing.
Click to expand...
Click to collapse
AT LAST .... FIXED ...
I did two things, V20B, and format /system, /data before installing new ROM. So my steps were:
1) Flush V20B instead of V20A
2) After rooting, and installed CWM 6044 touch, copy custom ROM MIUI to external SDCARD
3) Reboot into recovery, and format /system, /data, and /cache partitions
4) Install custom ROM from external SDCARD
5) Wipe data and cache
6) Reboot into the new world
:good: formatting did the work sorry i didnt think of it earlier.
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 think I've messed up my MI3 a bit to much.
After trying out 15+ ROMs, partitioning with several methods,
swapping CWM & TWRP just to see what will happen,
my MI3 finally "gave the ghost" as we say in good dutch.
I have some idea of what's wrong, but haven't the ghusto to sort it out any more.
Most probable is a few wrong partion sizes allowing me only
to install the last working recovery (CWM).
Anyway, to cut a long story short,
is there any way to COMPLETELY do an original factory reset,
including removing all partions and creating new ones with the right sizes
with an original (MIUI ?) factory ROM installation ?
Alternative ideas are welcome.
Yes, (I think) flashing the original ROM, MIUI, it will restore everything to factory (including the kernel, partitions, etc). Using the official tool is the easiest way http://en.miui.com/thread-92720-1-1.html
ChazyTheBest said:
Yes, (I think) flashing the original ROM, MIUI, it will restore everything to factory (including the kernel, partitions, etc). Using the official tool is the easiest way http://en.miui.com/thread-92720-1-1.html
Click to expand...
Click to collapse
Thanks Chazy,
but .. been there ... done that ... phone not recognised
Inonotting said:
Thanks Chazy,
but .. been there ... done that ... phone not recognised
Click to expand...
Click to collapse
Did you try connecting your phone in fastboot mode? It starts a window where you can flash the latest stable or developer rom.
I just did it and my phone is restored to factory, everything working. It should work, no matter what genocide you did to your phone lol :laugh:
I tried fastboot already, had some errors.
Can't seem to find any fastboot roms anymore, I only have
cancro_images_V6.1.2.0.KXDCNBJ_4.4_cn_2cbb2e76e8.tgz
I'll try again sometime this week.
I seem to recall that fastboot had some problems with my partitioning also.
You mean errors while flashing with fastboot? It should fix the partitions... I flashed the zip to extend to 1.2GB and installed the cm12.1 with stuxnet kernel but it seems there are some problems and it's not booting. So I used the mi manager, connected the usb in fastboot mode and it reverted and installed miui room without errors.
Try the developer room, if you have problems downloading it (with the mi manager, they're having server problems) go to the folder where it downloads (C:\Xiaomi\... can't remember) and open the .cfg file (using notepad) and copy the url link and open it in firefox or chrome, it should download the file at full speed. Delete the two files in the folder and move from downloads the new file. Disconnect the phone and connected it again in fastboot mode, choose the developer room and it should flash it, fixing partitions. (ram usage is a bit improved since the other old stable, getting 1.1/1.2GB uninstalling crapware and system apps like ant hal service, etc)
I'm using the last developer room and there are no problems, everything smooth, stable and good performance (with a new cool interface and themes). Still waiting for 5.1.1 though
Nope, just a message,
"Can not install" or something like that, no explanation
Inonotting said:
Nope, just a message,
"Can not install" or something like that, no explanation
Click to expand...
Click to collapse
Solved :
forum.xda-developers.com/xiaomi-mi-3/general/mi3-bricked-t3195574
I used The Dork Knight Rises' partitioning method, back to stock, then back to extended :
forum.xda-developers.com/xiaomi-mi-3/general/extremely-useful-flashable-zips-t3080860/