Hi all,
since Kitkat Factory Images have been released, I'm going to flash it over my current CM10.2.
If I use the flash_all script included in the package, will I lose my current CWM and/or the Root?
Moreover, will the phone be automatically totally erased, including the (virtual) SD-Card? I would like so... to have a really fresh install.
Thank you.
Related
Hello,
if i flash stock 4.4 does all my data get lost?
Will i then still be able too boot 4.3 CustomROMs with Multiboot?
Thanks in advance
If you use the flash-all.bat all data will get lost, including all your media, but I dont know if there's already a working Multiboot recovery for kitkat.
Hi everyone,
I'm planning on upgrading my Nexus 4 to KitKat.
Currently I'm using PA 3.69 (4.2.2) with Franco Kernel and CWM Recovery.
1. What files do I need to flash for the upgrade, possibly with links? (I'm going for Purity ROM)
2. In what order should I do the flashing process?
3. Should I upgrade CWM before flashing, and if yes, which is the latest version that supports 4.4 and how does upgrading work?
Thanks in advance
If you want to install stock KK, you can download the factory Occam images and install via fastboot.
If you want to install a custom rom, you may need to update your recovery to the latest version and flash a KK rom that includes an updated radio and boot img.
So you think I can:
1. Upgrade CWM to 6.0.4.5 here: http://forum.xda-developers.com/showthread.php?t=2198942
2. Flash this: http://forum.xda-developers.com/showthread.php?t=2545838, since it includes Bootloader and Radio.
3. Flash this: http://forum.xda-developers.com/showthread.php?t=2281607 (Purity ROM)
4. Flash any desired Kernel (e.g. Franco) and use Titanium backup to restore my apps?
U just have to download the Rom. Install it. Set it up. Then boot back into recovery and install the kernel
I don't think u have to update CWM. So just steps 3 and 4
I'm asking cause I am coming from 4.2.2 with old radio and bootloader and I want the most up-to-date ones.
And I am sure that just flashing the rom will cause problems... What do I need to wipe prior to flashing?
BarbaxX said:
I'm asking cause I am coming from 4.2.2 with old radio and bootloader and I want the most up-to-date ones.
And I am sure that just flashing the rom will cause problems... What do I need to wipe prior to flashing?
Click to expand...
Click to collapse
I checked the links. Your method seems to be OK.
As for wiping, you need to wipe data, cache and dalvik cache from the recovery when you flash the Purity Rom
Everything has worked flawlessly. Thanks!
Hello guys.
I want to downgrade my defy+ from CM11 to stock android.
Before update the recovery and install CM11 i made a backup with CWM and now i want to restore this backup.
How can i do this? Can i install CWM using the kitkat on my phone?
Sorry for the dumb question, but I'm afraid of doing something wrong.
lucashs said:
Hello guys.
I want to downgrade my defy+ from CM11 to stock android.
Before update the recovery and install CM11 i made a backup with CWM and now i want to restore this backup.
How can i do this? Can i install CWM using the kitkat on my phone?
Sorry for the dumb question, but I'm afraid of doing something wrong.
Click to expand...
Click to collapse
I have discovered that I need it too because my phone is loked and, to enter my carrier unlock code, i need to restore my backup made with CWM.
Looking for the same.
Yesterday i have installed 2ndInit to get back CWM recovery and restore my original stock ROM image.
Android can not complete the full boot, showing the intro of my carrier during a hour while loading Android.
Reinstalled TWRP and recovered my CM11 backup.
I will try again and, if not suceded, i will flash my carrier SBF to unlock my phone.
I will inform any news about CWM restore stock ROM.
TicoDePano said:
Yesterday i have installed 2ndInit to get back CWM recovery and restore my original stock ROM image.
Android can not complete the full boot, showing the intro of my carrier during a hour while loading Android.
Reinstalled TWRP and recovered my CM11 backup.
I will try again and, if not suceded, i will flash my carrier SBF to unlock my phone.
I will inform any news about CWM restore stock ROM.
Click to expand...
Click to collapse
I think this happens because the roms use different file systems
Try the Aroma Wiper to change the file system:
http://forum.xda-developers.com/showthread.php?t=2202674
I'll try this, but now i'm without time, then i report if it work.
I got my phone working.
http://forum.xda-developers.com/motorola-defy/help/tim-brasil-signal-cm11-t2824983#post54683596
About revert to stock ROM, only doing a factory reset to format my data partition fix the boot (I did not try AROMA or safewipe.zip).
I do not tried to restore data from my stock dump after got my phone working because it was not my objective, but i think that it is possible and simple after get it working.
Thanks.
Hi All,
Just wondering what's going on with my phone - it's a Galaxy Note 4 SM-N910G with Optus Australia.
Here's the situation:
I rooted my phone using Chainfire method from 5.1.1 Optus firmware.
Then, I installed TWRP, backed up all partitions (INCLUDING EFS).
After that, installed Cyanogenmod. Holy damn, I need to go back to stock...
so...
I booted back into TWRP
I reset phone as usually would to restore/install ROM.
I restored firmware backup in TWRP.
Reboot to system
-- BOOTLOOP --
happens every time i try to restore, and the only way I can use my phone right now is to reflash Cyanogenmod 12.1 nightlies onto it - which have problems (such as I cannot reboot with CM12.1 because if I do after installing it, the phone app breaks and I cannot get past anything because of toast message "com.android.phone" has stopped..., so then only way to get it to work again is to reflash CM12.1 again - this happens about twice daily...)
-- -- PLEASE HELP!
What happens to TWRP backups that mean i cannot restore my stock backup without it bootlooping? and why can devs not post a clean stock flashable ZIP copy of stock firmwares? Its great having all these mods, but how about something that doesn't require umpteen thousand bloody applications to reflash your phone with? Whatever happened to a simple ZIP? when I see ZIPs, devs see thanks buttons being pushed!
-- THANKS
MrDhark32 said:
Hi All,
Just wondering what's going on with my phone - it's a Galaxy Note 4 SM-N910G with Optus Australia.
Here's the situation:
I rooted my phone using Chainfire method from 5.1.1 Optus firmware.
Then, I installed TWRP, backed up all partitions (INCLUDING EFS).
After that, installed Cyanogenmod. Holy damn, I need to go back to stock...
so...
I booted back into TWRP
I reset phone as usually would to restore/install ROM.
I restored firmware backup in TWRP.
Reboot to system
-- BOOTLOOP --
happens every time i try to restore, and the only way I can use my phone right now is to reflash Cyanogenmod 12.1 nightlies onto it - which have problems (such as I cannot reboot with CM12.1 because if I do after installing it, the phone app breaks and I cannot get past anything because of toast message "com.android.phone" has stopped..., so then only way to get it to work again is to reflash CM12.1 again - this happens about twice daily...)
-- -- PLEASE HELP!
What happens to TWRP backups that mean i cannot restore my stock backup without it bootlooping? and why can devs not post a clean stock flashable ZIP copy of stock firmwares? Its great having all these mods, but how about something that doesn't require umpteen thousand bloody applications to reflash your phone with? Whatever happened to a simple ZIP? when I see ZIPs, devs see thanks buttons being pushed!
-- THANKS
Click to expand...
Click to collapse
This http://forum.xda-developers.com/note-4/help/n910c-to-stock-rom-cm13-t3321132 :good:
One possible solution is to flash the appropriate stock rom via odin. After booting, install twrp and root your phone. After this you can restore your previously saved stock rom via twrp.
MrDhark32 said:
Hi All,
Just wondering what's going on with my phone - it's a Galaxy Note 4 SM-N910G with Optus Australia.
Here's the situation:
I rooted my phone using Chainfire method from 5.1.1 Optus firmware.
Then, I installed TWRP, backed up all partitions (INCLUDING EFS).
After that, installed Cyanogenmod. Holy damn, I need to go back to stock...
so...
I booted back into TWRP
I reset phone as usually would to restore/install ROM.
I restored firmware backup in TWRP.
Reboot to system
-- BOOTLOOP --
happens every time i try to restore, and the only way I can use my phone right now is to reflash Cyanogenmod 12.1 nightlies onto it - which have problems (such as I cannot reboot with CM12.1 because if I do after installing it, the phone app breaks and I cannot get past anything because of toast message "com.android.phone" has stopped..., so then only way to get it to work again is to reflash CM12.1 again - this happens about twice daily...)
-- -- PLEASE HELP!
What happens to TWRP backups that mean i cannot restore my stock backup without it bootlooping? and why can devs not post a clean stock flashable ZIP copy of stock firmwares? Its great having all these mods, but how about something that doesn't require umpteen thousand bloody applications to reflash your phone with? Whatever happened to a simple ZIP? when I see ZIPs, devs see thanks buttons being pushed!
-- THANKS
Click to expand...
Click to collapse
Sorry no help from me but I have a similar problem. At some point mine quit booting to TWRP and I got a huge OTA update a few days ago and every time I try to boot into recovery it ends up in Stock Recovery only after going to little android saying installing updates(it fails & eventually goes to stock recovery.) I did a reset and still have 5.1.1 installed and still have the same behavior.
I have the professional version of the unified toolkit and it says if it is still booting into stock recovery select options 7, 3 which I did but it didn't fix the problem. I think what's getting me is it thinks there are still system updates to install.
Okay, please bear with me as i am new to this flashing custom ROM's game.
I got a intl Galaxy s4 (gti9505) a month back. After reading a lot, i flashed TWRP, and installed a custom ROM (Lineage Optimized 14.1) It runs absurdly great, and i dont think i'll need to replace this OS. BUT if i need to downgrade for whatever reason (im sure i will soft-brick the phone soon, because im testing a lot.) I have some questions:
- Some posts says i can flash back to 5.0 and upper, because the bootloader is the same (???)
- Some posts says i cant flash back to anything below my actual OS (android 7.1) (?????)
- Some posts says i cant flash STOCK ROMS because the bootloader is different. (???????)
- Could i HARD BRICK the phone, wrongly installing stuff via TWRP? or is TWRP functional "forever?''
- I did a big ass backup of android 5.0 before, when i installed TWRP. Can i reflash back to this, at any time?
I'd like to avoid any kind of brick, so help is very much appreciated. Thank you very much for helping a fellow android fan :good:
You can always flash the latest stock ROM to the phone using Odin. There is no stock ROM beyond 5.01 as far as I know.
Yes, you can hard brick the phone by flashing files through TWRP.
How did you create the 5.0 backup?
Thank you. +1 :good:
I did the backup via twrp, i think it was nandroid or something.
One last little question. What happens if i flash, say a custom ROM that is android 6.0 on TWRP right now (Doing the correct stuff and wiping what is needed). Will it Softbrick?
if yes, could you tell me why?
neru21 said:
Thank you. +1 :good:
I did the backup via twrp, i think it was nandroid or something.
One last little question. What happens if i flash, say a custom ROM that is android 6.0 on TWRP right now (Doing the correct stuff and wiping what is needed). Will it Softbrick?
if yes, could you tell me why?
Click to expand...
Click to collapse
It should not softbrick if you are flashing a custom ROM that is designed for your phone's model #.
If it does softbrick, there are two major causes: a full wipe of the data and cache partitions is required before installing the ROM or a full wipe of the phone (system, data, cache) using recovery is required before installing the custom ROM.