Hello guys,
I'm now on a custom ROM but I'd like to get back to the stock CM11s ROM.
However I couldn't find how to flash it with the recovery without losing my internal storage so I'd like to know if there is a way ?
(All I found was the factory image which needs to flash with fastboot so I'll loose all my date.)
Thank you.
There is a stock rooted version of 44S by Calkulin in the development section that you can flash like any other ROM.
Transmitted via Bacon
Related
Hi... im currently running
CROMi-X v5.2.2, which is based on rom 10.6.1.27.5 with twrp 2.5.0.0 and my bootloader says is the one that came with us10.6.1.15.3-20130416...
To install omni kitkat, im been asked to have the latest bootloader, to avoid screwing up im planning on insalling the latest stock from asus...
However, each time i install a stock through twrp or cwr, the new image not only updates the bootloader and deletes all my data, but rewrites my recovery, for which then i have too reupload using fastboot to upload the recovery...
Is there any way to make sure i dont loose the recovery after flashing a stock firmware... or a way to flash the recovery from the recovery before rebooting after flashing the stock?
Thanks everyone!
mertonv said:
Hi... im currently running
CROMi-X v5.2.2, which is based on rom 10.6.1.27.5 with twrp 2.5.0.0 and my bootloader says is the one that came with us10.6.1.15.3-20130416...
To install omni kitkat, im been asked to have the latest bootloader, to avoid screwing up im planning on insalling the latest stock from asus...
However, each time i install a stock through twrp or cwr, the new image not only updates the bootloader and deletes all my data, but rewrites my recovery, for which then i have too reupload using fastboot to upload the recovery...
Is there any way to make sure i dont loose the recovery after flashing a stock firmware... or a way to flash the recovery from the recovery before rebooting after flashing the stock?
Thanks everyone!
Click to expand...
Click to collapse
Flashing the stock ROM reverts the tablet back to stock, so the recovery must go. Luckily, the bootloader you are on is compatible with the KitKat recovery (10.6.1.15.3) so you shouldnt have to flash the stock ROM at all. If you were on 10.6.1.8, you would have had to upgrade.
cmendonc2 said:
Flashing the stock ROM reverts the tablet back to stock, so the recovery must go. Luckily, the bootloader you are on is compatible with the KitKat recovery (10.6.1.15.3) so you shouldnt have to flash the stock ROM at all. If you were on 10.6.1.8, you would have had to upgrade.
Click to expand...
Click to collapse
Thanks, then guess i only need to flash the kitkat twrp...
Asked the same question about my bootloader at the omni thread to be sure, if they say that it works too, will go ahead and give it a try
Hey guys, I've seen this issue before yet I've tried everything in a few threads now but have no idea what is happening,I have tried using search function yet no solution has fixed my problem.
Problem:
When installing custom ROMs the installation goes fine. I put the ROM on the sdcard, follow instructions for flashing e.g wipe data/cache etc and then flash GAPPS. However I get stuck on the boot logo of every ROM. I've tried both TWRP and CWM recoveries, both with no luck. Also tried not flashing GAPPS and just trying to flash the ROM to no avail.
Current state of phone:
The phone is currently running stock firmware via downloading factory image and flashing in boot-loader : stock boot, recovery, system image etc
The phone works fine when rooted on stock firmware. E.g no custom rom yet rooted.
Could really do with some help guys, any ideas?
muqy said:
Hey guys, I've seen this issue before yet I've tried everything in a few threads now but have no idea what is happening,I have tried using search function yet no solution has fixed my problem.
Problem:
When installing custom ROMs the installation goes fine. I put the ROM on the sdcard, follow instructions for flashing e.g wipe data/cache etc and then flash GAPPS. However I get stuck on the boot logo of every ROM. I've tried both TWRP and CWM recoveries, both with no luck. Also tried not flashing GAPPS and just trying to flash the ROM to no avail.
Current state of phone:
The phone is currently running stock firmware via downloading factory image and flashing in boot-loader : stock boot, recovery, system image etc
The phone works fine when rooted on stock firmware. E.g no custom rom yet rooted.
Could really do with some help guys, any ideas?
Click to expand...
Click to collapse
same problem simple solution another user informed me of.
simply donwgrade to 4.3 JB stock rom through fastboot. Then you are able to flash a custm rom from the 4.3 stock rom.
Its crazy i have to do this but it worked for me, now im running the xperience rom which is a rom based on 4.4.2 kk.
the 4.3 android stock firmwares are linked somewhere in the FAQ's as well as the guide to ffastboot lash it.
peace.
chairsz said:
same problem simple solution another user informed me of.
simply donwgrade to 4.3 JB stock rom through fastboot. Then you are able to flash a custm rom from the 4.3 stock rom.
Its crazy i have to do this but it worked for me, now im running the xperience rom which is a rom based on 4.4.2 kk.
the 4.3 android stock firmwares are linked somewhere in the FAQ's as well as the guide to ffastboot lash it.
peace.
Click to expand...
Click to collapse
Hey man, worked a charm thanks!
For users who may have the same problem:
After flashing 4.3 onto the device it did NOT boot.
- However I then went into the bootloader flashed custom recovery, I used cwm.
- Then I went into recovery, used adb to push the rom and gapps onto sdcard
- Full wipe and then installed rom. Then installed gapps
Working fine.
Cheers chairsz :good::good:
i am not overly familiar with many things regarding different kernels and how to work with them, so i was wishing a few questions that i had could be clarified by someone who knows:
1. when a kernel is flashed? i mean except for the times when we flash kernel.zips via recovery, is it flashed whenever we install a custom rom? or is it flashed with bootloaders when we flash firmware?
2. I am using CM12 official nightly and facing camera frizz issues. I came across a post in the official CM12 thread where they said flashing a modified kernel supposedly fixed this problem. Now my question is, after flashing a custom kernel, is there any way to go back to the stock one? by stock i mean either the one i was on right before flashing the custom kernel or stock moto g kernel provided by motorola?
that also begets the question, can kernels be backed up like roms using recovery?
gearguy365 said:
i am not overly familiar with many things regarding different kernels and how to work with them, so i was wishing a few questions that i had could be clarified by someone who knows:
1. when a kernel is flashed? i mean except for the times when we flash kernel.zips via recovery, is it flashed whenever we install a custom rom? or is it flashed with bootloaders when we flash firmware?
2. I am using CM12 official nightly and facing camera frizz issues. I came across a post in the official CM12 thread where they said flashing a modified kernel supposedly fixed this problem. Now my question is, after flashing a custom kernel, is there any way to go back to the stock one? by stock i mean either the one i was on right before flashing the custom kernel or stock moto g kernel provided by motorola?
that also begets the question, can kernels be backed up like roms using recovery?
Click to expand...
Click to collapse
1. The kernel is first flashed when you install a ROM. You are supposed to flash a custom kernel after flashing a ROM otherwise the rom zip will overwrite it. It doesn't matter if you install it in the recovery or the boot loader.
2. To go back to the stock kernel just take it from the zip of the ROM and flash in the bootloader
where can i find the kernel inside the rom zip?
and if i want the stock motorola kernel that comes with factory firmwares
how can i collect that?
A ROM.zip contains the system folder and a boot.img
The kernel is in the boot.img
So if u flash a different kernel and still facing problems then flash the ROM again.
mistercheese said:
A ROM.zip contains the system folder and a boot.img
The kernel is in the boot.img
So if u flash a different kernel and still facing problems then flash the ROM again.
Click to expand...
Click to collapse
flashing only the boot.img of a rom wont bring back the default kernel?
and is there any way to make a flashable zip of a kernel from that particualr boot.img?cause all the kernels i see (like donkey kang/customized cm12 kernel) there are all distributed in .zip format.....
Hi All,
Background:
Installed TWRP recovery to downgrade to KitKat from Android ver 5.0.2 / COS 12.0 YNg1TAS17L
( I guess the changes in lollipop made me to do so).
But after installing TWRP, for some reason or other I did nothing and now the issue is the OTA are not getting installed. From other similar thread I know that we can download the OTA zip and install through TWRP and I am not looking to get into that...as I am giving this device to my family.
Help Required:
1) Is there a way to uninstall TWRP and go back to stock recovery without losing any data?
( Is it as simple as flashing recovery image from the Stock ROM?)
2) Using the OnePlus tool kit can we flash the stock ROM which will also restore the stock recovery?
(If so is it possible to flash the latest ROM 5.1.1 or CM12.1)
I just need guidance here with steps on what will be the best and safe approach without frying up my device.
Please suggest
droidfry said:
Hi All,
Background:
Installed TWRP recovery to downgrade to KitKat from Android ver 5.0.2 / COS 12.0 YNg1TAS17L
( I guess the changes in lollipop made me to do so).
But after installing TWRP, for some reason or other I did nothing and now the issue is the OTA are not getting installed. From other similar thread I know that we can download the OTA zip and install through TWRP and I am not looking to get into that...as I am giving this device to my family.
Help Required:
1) Is there a way to uninstall TWRP and go back to stock recovery without losing any data?
( Is it as simple as flashing recovery image from the Stock ROM?)
2) Using the OnePlus tool kit can we flash the stock ROM which will also restore the stock recovery?
(If so is it possible to flash the latest ROM 5.1.1 or CM12.1)
I just need guidance here with steps on what will be the best and safe approach without frying up my device.
Please suggest
Click to expand...
Click to collapse
Numerous other threads on the same subject... I don't understand why you are not ready to flash the OTA through TWRP but you are through stock recovery... It's the same thing... Don't use toolkit, they are the ones, in 99% of the cases, that "fry" your phone... As soon as TWRP is installed no OTA will automatically, you will have to flash them manually.
Hello everybody! I have a problem: I wanted to install custom ROM via Safestrap 3.71. I made all the wipe. But at the end of the installation, I get an error: set_metadata_recursive some changes failed. And so in each ROM. After that, ROM does not load: black screen after the logo Samung Custom. How to deal with this?
[R]ainbow[D]ash said:
Hello everybody! I have a problem: I wanted to install custom ROM via Safestrap 3.71. I made all the wipe. But at the end of the installation, I get an error: set_metadata_recursive some changes failed. And so in each ROM. After that, ROM does not load: black screen after the logo Samung Custom. How to deal with this?
Click to expand...
Click to collapse
Was it a true custom ROM? Or was it a modified stock ROM?
If it was a custom ROM such as Cyanogenmod or LineageOS, that's the problem.
Safestrap is intended to be used with modified stock ROMs that are based on stock kernel, not CM, AOSP or Lineage based ROMs.
Typically, Safestrap is used on devices with locked bootloader, these devices can't use CM, AOSP or Lineage based ROMs, these ROMs are built to be flashed via custom recovery such as TWRP.
If you have an unlocked bootloader and you want to use custom ROMs then you'll have to flash TWRP then use TWRP to flash the ROM.
If your device does not have an unlocked bootloader but you want to use Safestrap then you need to install TouchWiz(TW)/stock based ROMs.
There is a difference.
Also, when using Safestrap, you have to leave the stock rom in one slot and place the new ROM in a different slot. You can't overwrite the existing stock ROM with the new ROM, that causes issues and the device won't boot.
You will probably have to flash your stock firmware via Odin and start over with root and flashing.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
Was it a true custom ROM? Or was it a modified stock ROM?
If it was a custom ROM such as Cyanogenmod or LineageOS, that's the problem.
Safestrap is intended to be used with modified stock ROMs that are based on stock kernel, not CM, AOSP or Lineage based ROMs.
Typically, Safestrap is used on devices with locked bootloader, these devices can't use CM, AOSP or Lineage based ROMs, these ROMs are built to be flashed via custom recovery such as TWRP.
If you have an unlocked bootloader and you want to use custom ROMs then you'll have to flash TWRP then use TWRP to flash the ROM.
If your device does not have an unlocked bootloader but you want to use Safestrap then you need to install TouchWiz(TW)/stock based ROMs.
There is a difference.
Also, when using Safestrap, you have to leave the stock rom in one slot and place the new ROM in a different slot. You can't overwrite the existing stock ROM with the new ROM, that causes issues and the device won't boot.
You will probably have to flash your stock firmware via Odin and start over with root and flashing.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
I was flashing the modified ROM on the stock kernel. I put in the recovery on slot-rom1. I tried to flash: CarHD, KushanROM, GOLDENEYE and Omega. And still it does not work out
[R]ainbow[D]ash said:
I was flashing the modified ROM on the stock kernel. I put in the recovery on slot-rom1. I tried to flash: CarHD, KushanROM, GOLDENEYE and Omega. And still it does not work out
Click to expand...
Click to collapse
Do you still have your original stock ROM in one of the slots? Or did you overwrite it? If you overwrite it, you messed up. As stated earlier, you'll probably have to flash the original stock firmware via Odin.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
Do you still have your original stock ROM in one of the slots? Or did you overwrite it? If you overwrite it, you messed up. As stated earlier, you'll probably have to flash the original stock firmware via Odin.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
The stock slot remained intact. But if I take the kernel from OC3, then the device will also not boot up and the recovery will become non-working.
Send me the stock ROM for flashed the custom ROM through the Safestrap. And send me the version of the Safestrap for custom ROM
I understood what the problem is. I installed another ROM NB1 and it all worked for me.