I've installed lineage 14.1 then I want to go back to the stock rom
but when I but it on the SD card and use the force update it cannot be done
give me installing filed
what can I do.plz?
Related
Hey guys. I have a slight problem.
I have MIUI as the rom on my phone. I then used bootmanager to install CM7 to my SD Card (slot 1). Then I installed gapps on to slot 1 as well (without any wipes). Then I booted in CM7. It booted up fine except now I have no gapps or any of the apps I had installed in MIUI except for the ones that come with CM7. I don't have Boot Manager or any way to install it. I tried restarting my phone too No go. Help me out guys!
Edit:
I have figured out how to get back to your phone rom. If you should get stuck in an SD card rom so you cannot get back to the phone rom using boot manager then just do a few steps:
1. Reboot to recovery
2. Choose Flash Zip from SD Card
3. Go to BootManager/phone rom folder
4. Flash update.zip (No need to wipe anything beforehand)
It should flash successfully. It went really quick for me too. I'm not sure of that was because of MIUI's size or because it was already installed.
I don't know why gapps didn't install, I'm pretty sure I flashed it correctly. Any help there?
I had the gapps flashing issue when I tried CM7 on my Desire S using the same method if that helps at all?
Hi all.
I got a refurbished Samsung Galaxy S2 (unlocked) that had Stock Android 4.0 (I think it maybe have been rooted before).
I wanted to upgrade it to at least the official Jellybean from Samsung or to a Kit Kat ROM.
So I downloaded CyanogenMod 11- the latest build for Galaxy S2, and GApps 4.4.2 zip.
I copied them onto the internal SD card of the phone, booted into Recovery, wiped the phone, partition and dalvik cache, and went to installing the CM 11 zip.
But then it couldn't access the internal SD card. My phone was bricked essentially.
I searched the web amd found out that the card needs to be formatted to FAT-32. but the computer didn't recognize the phone at this point.
So I put the ROM on an external microSD, and tried to flash from Recovery, but it wasn't able to install: "E: Error in '...zip' (Status 7) Installation Aborted".
So I then downloaded an old CM 9 ROM, booted into Odin Recovery, and it flashed it successfully.
The problem is A. The phone doesn't seem to have Kit Kat, but rather Jellybean I think. B. It gets stuck, and the keyboard doesn't work, which makes it unusable. C. If I remove the microSD from the phone, it can't boot into the OS.
After all that mess, bottom line is that I want to install on the internal SD card either Stock Samsung Jellybean or later (whatever there is) or a custom Kit Kat Rom, and to use a recent and stable ROM (CM 11?).
Do I need to format the phone to FAT-32? I'm a bit scared to format it at this point.
From what I read a bit, it may be that I need to install a different bootloader. If so, how do I do this?
I'm a newbie to all of this, and I would greatly appreciate if you can help me doing this easily without wrecking my phone.
Thanks!
Update: I installed the wrong GApps zip, that's why the keyboard doesn't work. Now it's working, running Android ICS 4.0.4.
Now my questions are: A. How to install latest Stock Samsung Jelly Bean or newer version of CyanagenMod for Kit Kat? B. How to install it on the internal card?
I was on Color OS 2.1.3
Decided I wanted to try a 5.1.1 custom rom.
Ununified back to default. Installed TWRP and created a backup.
Wiped installed Paranoid Android 5.1.1 this seemed to be working fine untill.
Couldn't copy new files onto the SD card (So could not add Gapps)
Got the 'Could not connect to camera' error.
So then I tried to install Omni 5.1.1 Although no I can't
Copy Files.
Restore the backed up Coloros
I do have color os 1.2.7 and 2.1.3 on external SD although then I use TWRP to install these I starts up and then just gets stuck in a reboot loop.
Anyone got a suggestion of how I can hard rest my phone back to color os?
Thanks!
I had the same issue after restoring backup of coloros from twrp. Only solution is to flash stock recovery and then flash coloros. Use the newer recovery which is named recovery_4_4.img. It also supports partitioning.
Sent from my X9006 using Tapatalk
Try to flash the stock recovery, then flash this ROM
community.oppo.com/en/forum.php?mod=viewthread&tid=42690&extra=
Hello, So i recently decided to move back to stock os as i think the push notification bug is fixed (Is it ?) . So then i yesterday downloaded the rom http://forum.xda-developers.com/fire-phone/development/safestrap-v4-flashable-stock-image-t3150531. I downloaded the latest version 4.6.6.1 US Version. I remember i rooted the phone from 4.6.6 does it matter ? So i decided to check the rom before actually wiping all my data so i created rom-slot-1 and tried to install the stock os in it. It gave me a error ''Failed to update binary through zip'' i can not decide is it problem with non-stock rom or is it with the rom. There are 3 rom types on that rom page. I dont know what could be the problem. Does the rom vary with the model of the phone ? if yes then how can i know my model of the phone ?
Thanks
The Fire OS partitions are too big, so they will never fit into the manually created slots, which is a good thing because they prevent an installation that would be useless anyway.
You can install ROMs to slot1 but they won't work correctly (connectivity, etc.), so don't even waste time on trying...
Just backup your existing OS via TWRP through Safestrap and proceed with a clean install of Fire OS:
TWRP backup of "old" OS
wipe data, cache & dalvik
flash the CleanSystemPartition zip
flash the Fire OS zip right after
flash other things of your choosing, like SuperSU, etc.
Paras5 said:
Hello, So i recently decided to move back to stock os as i think the push notification bug is fixed (Is it ?) . So then i yesterday downloaded the rom http://forum.xda-developers.com/fire-phone/development/safestrap-v4-flashable-stock-image-t3150531. I downloaded the latest version 4.6.6.1 US Version. I remember i rooted the phone from 4.6.6 does it matter ? So i decided to check the rom before actually wiping all my data so i created rom-slot-1 and tried to install the stock os in it. It gave me a error ''Failed to update binary through zip'' i can not decide is it problem with non-stock rom or is it with the rom. There are 3 rom types on that rom page. I dont know what could be the problem. Does the rom vary with the model of the phone ? if yes then how can i know my model of the phone ?
Thanks
Click to expand...
Click to collapse
And no... The notification push bug isn't fixed -,-
I rooted my phone yesterday fine and made a backup of my oxygen OS (original rom).
I am definitely successfully unlocked and rooted, and TWRP newest version is running.
I have tried so much to get a new rom running correctly I have tried both resurrection remix official and unofficial:
https://forum.xda-developers.com/on...evelopment/op3-3t-resurrection-remix-t3754941
I have also tried official paranoid android, but every time it starts up I get two issues the first is the error saying "android.media has stopped" the more serious being the fact that no matter which rom I flash it always begins force restarting over and over again, I get into the OS fine, have a scroll around and around every 2 mins or so it just force reboots, then it comes back and is fine for 2 mins then same again.
It has happened with the official and unofficial versions of resurrection remix and also happens exactly the same with paranoid android. I have no idea what else to try at this point.
The process I have been using for flashing is this:
1. Boot into TWRP recovery
2. Wipe everything but internal storage.
3. Install my rom.
4. Reboot.
5. Starts up successfully and then falls back into the standard boot loop and the android.media error.
I have also tried it with GAPPS which was throwing some setup wizard has stopped error, so for now I am just attempting to get an actual rom running without constantly restarting.
Any help is massively appreciated, I am tech savvy, hence why this is annoying me even more.
Thanks,
Kieran
Have you tried going back to the latest official Oxygen OS (Stable or OB)?
jeffrey268 said:
Have you tried going back to the latest official Oxygen OS (Stable or OB)?
Click to expand...
Click to collapse
My backup is the original oxygen and this restores fine and works fine just as soon as I try to flash a new rom it just keeps restarting every few minutes, I dont really know what else to try.
Also to add I sometimes see this issue when I attempt to flash certain roms..... 'assert failed: op3.verify_modem("2017-11-16") == 1'
Use the recommended firmware by the rom. Also you can't flash most roms without Gapps.
1. Flash proper firmware
2. Flash the rom
3. Flash Gapps or something similar.
4. Flash any additional kernel (optional).
5. Flash SuperSU or Magisk.
The assert failed littery tells you that you use using the wrong modem // firmware.
my first question which custom Rom you installed every Rom developer say it is stable but only few has been stable as rock . i tried everything but settled with AICP Rom. and then try to use GAPP as ARM64 android 8.1
u have first install Rom and then GAPP then magisk or Superuser anything which u refer
https://forum.xda-developers.com/on...e-development/wip-official-aicp-13-0-t3713637
this is the Rom which i use it . .they are stable and also update it weekly thrice ..
if u like it you can install this ROM