Related
So I've unlocked the bootloader, rooted and flashed CWM.
I've also made a backup with titaniumbackup.
How do I go about installing a ROM? I'm confused because I read in some places that you need to wipe cache (davik? What is this?) then wipe everything else on the current ROM, then install the custom ROM, but do I do this through CMD or natively on the Nexus 7 with ROM manager?
What are the steps to do this properly?
Try this, questions just ask
You need a recovery first like 4ext you put that on then you copy the ROM onto the sd from your PC and enter into recovery then you install the zip file and factory reset in the same place wipe cash and that other cache you mentioned keep forgetting name of it
Lizardwithhat said:
You need a recovery first like 4ext you put that on then you copy the ROM onto the sd from your PC and enter into recovery then you install the zip file and factory reset in the same place wipe cash and that other cache you mentioned keep forgetting name of it
Click to expand...
Click to collapse
I have CWM recovery, wait so I factory reset in recovery before I install the zip, and wipe cache after? Which order?
UnixxinU said:
I have CWM recovery, wait so I factory reset in recovery before I install the zip, and wipe cache after? Which order?
Click to expand...
Click to collapse
in cwm do a factory reset and then clear cache of that install rom (.zip) from sd card
The very first ROM I tried to flash was a version of CarbonRom. I was unsuccessful, as i got the installation aborted message. I then tried a couple of other lesser know ones, with the same luck. Lastly I tried CM 10.1, and with that, i had success. It was the only one that would work so far. Yesterday, I downloaded DU 4.2.2, and A new nightly version of Carbon (Specifically for my phone) With no luck of installation. Am i doing something wrong with these? Is there a different method of flashing i'm missing?
what is the procedure you take to install?
I usually go this route:
1) Boot into whatever recovery you have
2) Wipe Cache/Davlik
3) Install custom ROM
4) run a factory reset
5) Reboot
snibe said:
what is the procedure you take to install?
I usually go this route:
1) Boot into whatever recovery you have
2) Wipe Cache/Davlik
3) Install custom ROM
4) run a factory reset
5) Reboot
Click to expand...
Click to collapse
I have Philz custom recovery which based on cwm version 6.0.3.7 which when you tap wipe data you will then have the option to clean install for new ROM.
jmxc23 said:
I have Philz custom recovery which based on cwm version 6.0.3.7 which when you tap wipe data you will then have the option to clean install for new ROM.
Click to expand...
Click to collapse
Sorry for not replying earlier, i never got a notification. I'm using the most recent version of CWM. My usual order is :
1. Boot into recovery
2. Factory Reset
3. Clear Cache Partition
4. Wipe Dalvik
5. Format /system
6. Mount /system
7. Flash new ROM
Bcaraway14 said:
Sorry for not replying earlier, i never got a notification. I'm using the most recent version of CWM. My usual order is :
1. Boot into recovery
2. Factory Reset
3. Clear Cache Partition
4. Wipe Dalvik
5. Format /system
6. Mount /system
7. Flash new ROM
Click to expand...
Click to collapse
well we now have 3 custom recoveries to choose from I like the newer one since I can install a new ROM in fewer steps.
i would do a factory reset after you flash your rom too, can't hurt.
of course on updating the same ROM, I only Wipe Cache/Davlik and that's it.
Bad download? Does the md5 match?
after making sure you wiped everything make sure the download itself was proper I am running it flawless right now
Hi,
First, I followed the instructions in this guide: http://forum.xda-developers.com/showthread.php?t=2507905
I installed the CWM recovery and then flashed the CM11-20131228 nightly and then the recommended Google Apps that are linked at their wiki: http://wiki.cyanogenmod.org/w/Gapps#Downloads (I took the 20131208 ones)
Now my phone is stuck in the boot screen with the circle spinning around the cyanogenmod logo (I can boot the bootloader and recovery but when I try to boot CM11 it’s stuck) and I dont know how to get to a working cm11 rom. The guide said that the first boot with a new rom takes longer than usual because the phone rebuilds caches and so on but I think it should not take more than half an hour...
What I already tried is:
- Wiping the chaches with the CWM recovery an then booting cm11 -> still just the arrow spinning around the logo
- Wiping the caches with recovery and then re-flashing the same zip without flashing the google apps afterwards -> did not work
- Wiping and then pushing the newer cm11 nightly via adb so that I could try this one -> recovery did not find the pushed zip on my scdard
- Wiping, then tried to install the new nightly via adb sideload -> cmd prompt said it was send properly and as far as I can say the phone installed it but I was still stuck on that bootscreen ...
- I even restored to the stock 4.4.2 factory image and then flashed the cwm recovery, than wiped caches and then installed the latest cm11 nightly an then the google apps but I still can not get past the boot animation
What am I doing wrong and how can I get past the boot screen?
You talk about wiping caches but are you wiping data too?
Oh, yes. I just didnt mention it. I always did the three steps from the guide:
wipe data/factory reset
wipe cache partition
advanced > wipe dalvik cache
BopItXtremeII said:
Oh, yes. I just didnt mention it. I always did the three steps from the guide:
wipe data/factory reset
wipe cache partition
advanced > wipe dalvik cache
Click to expand...
Click to collapse
So you get the bootloop only when trying to install CM and when you flashed the factory image, it booted up fine?
Sent from my Nexus 5
Exactly.
I install the factory image with method 1 from this guide: http://forum.xda-developers.com/showthread.php?t=2513701 and then flash CWM recovery to install CM (factory reset + wipe cache + wipe dalvik cache + install cm-zip + install gapps-zip) and then there is the bootloop.
BopItXtremeII said:
Exactly.
I install the factory image with method 1 from this guide: http://forum.xda-developers.com/showthread.php?t=2513701 and then flash CWM recovery to install CM (factory reset + wipe cache + wipe dalvik cache + install cm-zip + install gapps-zip) and then there is the bootloop.
Click to expand...
Click to collapse
Did you check the md5 of the cm download?
BopItXtremeII said:
Exactly.
I install the factory image with method 1 from this guide: http://forum.xda-developers.com/showthread.php?t=2513701 and then flash CWM recovery to install CM (factory reset + wipe cache + wipe dalvik cache + install cm-zip + install gapps-zip) and then there is the bootloop.
Click to expand...
Click to collapse
Sometimes formatting all of the partitions (except the sd card) works.
Sent from my Nexus 5
jd1639 said:
Did you check the md5 of the cm download?
Click to expand...
Click to collapse
The md5 sum is the same as on the download page.
PhilipTD said:
Sometimes formatting all of the partitions (except the sd card) works.
Sent from my Nexus 5
Click to expand...
Click to collapse
Which partitions? boot, cache, recovery and system? Sorry, I'm new to android... And what do I have to install on these partitions after erasing them?
BopItXtremeII said:
The md5 sum is the same as on the download page.
Which partitions? boot, cache, recovery and system? Sorry, I'm new to android... And what do I have to install on these partitions after erasing them?
Click to expand...
Click to collapse
Flash the boot.img and reboot
Then see
Sent from my LT26i using xda premium
BopItXtremeII said:
The md5 sum is the same as on the download page.
Which partitions? boot, cache, recovery and system? Sorry, I'm new to android... And what do I have to install on these partitions after erasing them?
Click to expand...
Click to collapse
Wipe system, data, dalvik, and cache
jd1639 said:
Wipe system, data, dalvik, and cache
Click to expand...
Click to collapse
^^^^^^Precisely^^^^^^
Sent from my Nexus 5
I got another problem now ... The last thing I did was flashing the stock rom. Now I want to flash the latest CM nightly (20131229) but fastboot does not let me install cwm recovery and says
Code:
FAILED <remote: partition table doesn't exist>
I flashed the whole stock rom again but the error still occurs... I have to wipe the partitions after I installed CM, right?
BopItXtremeII said:
I got another problem now ... The last thing I did was flashing the stock rom. Now I want to flash the latest CM nightly (20131229) but fastboot does not let me install cwm recovery and says
Code:
FAILED <remote: partition table doesn't exist>
I flashed the whole stock rom again but the error still occurs... I have to wipe the partitions after I installed CM, right?
Click to expand...
Click to collapse
Are you using
fastboot flash recovery recovery.img
Where recovery.img is the cwm image file
jd1639 said:
Are you using
fastboot flash recovery recovery.img
Where recovery.img is the cwm image file
Click to expand...
Click to collapse
I use this command. But I missed a c in recovery so fastboot did not find the partition named "reovery" >_< Ok, CWM is installed. Now I have to install CM11 an then wipe the 4 partitions you mentioned with cwm? Wheres the option to wipe system, I just find the other 3.
BopItXtremeII said:
I use this command. But I missed a c in recovery so fastboot did not find the partition named "reovery" >_< Ok, CWM is installed. Now I have to install CM11 an then wipe the 4 partitions you mentioned with cwm? Wheres the option to wipe system, I just find the other 3.
Click to expand...
Click to collapse
I'm cwm just do the other 3
So I installed CM + Gapps and then wiped data, cache and dalvik cache with CWM. Now Im waiting for 8 minutes for the bootscreen to go away, but think it didnt work. By the way, if I wipe the system partition, I delete CM, dont I? I dont understand how that will help booting into CM.
BopItXtremeII said:
So I installed CM + Gapps and then wiped data, cache and dalvik cache with CWM. Now Im waiting for 8 minutes for the bootscreen to go away, but think it didnt work. By the way, if I wipe the system partition, I delete CM, dont I? I dont understand how that will help booting into CM.
Click to expand...
Click to collapse
Wipe before the install.
So,
1 Put rom zip on phone internal storage
2 Wipe partitions except internal storage
3 Flash rom
4 Flash GApps
5 Reboot
Sent from my Nexus 5
BopItXtremeII said:
So I installed CM + Gapps and then wiped data, cache and dalvik cache with CWM. Now Im waiting for 8 minutes for the bootscreen to go away, but think it didnt work. By the way, if I wipe the system partition, I delete CM, dont I? I dont understand how that will help booting into CM.
Click to expand...
Click to collapse
8 minutes is too long. You have some other problem. Do any other roms work? Wiping system in twrp does not wipe the internal sd card. That's why you didn't find it in cwm.
PhilipTD said:
Wipe before the install.
So,
1 Put rom zip on phone internal storage
2 Wipe partitions except internal storage
3 Flash rom
4 Flash GApps
5 Reboot
Sent from my Nexus 5
Click to expand...
Click to collapse
Thats what I did.
jd1639 said:
8 minutes is too long. You have some other problem. Do any other roms work? Wiping system in twrp does not wipe the internal sd card. That's why you didn't find it in cwm.
Click to expand...
Click to collapse
I will try the AOKP nightly and post the results. Is it okay to just wipe data, cache and dalvik cache before installing the aokp zip or is it better to flash the stock rom before flashing aokp?
No need to flash stock, just do the wipes
im installing custom rom in my micromax a120.. i format dalvik cache, cache and mounts/storage to. then rom not installing it stuck on logo screen. i tried to flash stock rom but its also stuck on logo screen. please help me out.
ankurgiri65 said:
im installing custom rom in my micromax a120.. i format dalvik cache, cache and mounts/storage to. then rom not installing it stuck on logo screen. i tried to flash stock rom but its also stuck on logo screen. please help me out.
Click to expand...
Click to collapse
Hello and welcome to XDA-developers!
You have to do all required steps to flash custom/stock ROM.
1. Factory reset
2. Wipe System, Data, Cache/dalvik
3. Flash ROM
4. Reboot
FSadino said:
Hello and welcome to XDA-developers!
You have to do all required steps to flash custom/stock ROM.
1. Factory reset
2. Wipe System, Data, Cache/dalvik
3. Flash ROM
4. Reboot
Click to expand...
Click to collapse
i tried but not working....
Hello everybody,
I bought a Oneplus 7 Pro a few days ago and I'm preparing it for my daily usage. It's my fourth Android smartphone, and the third Oneplus. So far, I managed to flash everyone of them, with no major issues.
And then, the Oneplus 7 Pro suddenly appeared
I used this tutorial to unlock the bootloader and flash the custom recovery.
From my understanding, the custom recovery is flashed in the Recovery Ramdisk and available for both A & B slots.
For now, I have A and B slots with stock OSS, unlocked bootloader, custom recovery and Magisk. All of this is working.
There began my problems. I want to flash a custom ROM without Gapps and I fail to do it. All instructions around ROM threads seems different to me, I don't get the thing about A & B slots, when I flash one rom, it boots as usual on the stock ROM, if I flash both slots, It causes bootloops and if I manage to launch the recovery, my internal storage isn't detected and I can't restore any backup.
I already used MSMDownload to restore the phone completely once.
Can somebody explain to my dumb person how to do it proprely ? Thanks in advance ! :fingers-crossed:
TL;DR : I fail to flash a custom ROM and make it work.
Yes I had same issues when rooted, it means you lost root. You can try tool all in one to flash recovery and magesik via fastboot. If that doesn't restore your access, on twrp you will have to type in format, then mount, then add rom to storage(this method wipes everything beware)
djhulk2 said:
Yes I had same issues when rooted, it means you lost root. You can try tool all in one to flash recovery and magesik via fastboot. If that doesn't restore your access, on twrp you will have to type in format, then mount, then add rom to storage(this method wipes everything beware)
Click to expand...
Click to collapse
For now, my phone is working nicely. But that's the process of flashing a new ROM that fails. Recovery and Magisk are already and working.
Factory reset
Flash rom
Flash twrp installer
Reboot recovery
Format data
Reboot system
i boot all roms with these steps
WesTD said:
Factory reset
Flash rom
Flash twrp installer
Reboot recovery
Format data
Reboot system
i boot all roms with these steps
Click to expand...
Click to collapse
Thanks, I will try.
When you flash the ROM, does TWRP tell you that if you want to continue you need to reboot recovery ? If so, do you ? Do you reboot recovery on the same slot, or do you flash both ?
draentor said:
Thanks, I will try.
When you flash the ROM, does TWRP tell you that if you want to continue you need to reboot recovery ? If so, do you ? Do you reboot recovery on the same slot, or do you flash both ?
Click to expand...
Click to collapse
Nope, it doesnt tell you anything. Just reboot recovery from reboot menu. Don't touch the slot options
Thanks for your advices.
I'm trying right now, here's my steps :
- Wipe Data, Cache, Dalvik Cache (the standard Factory Reset)
- Install ROM : TWRP logs show that he's flashing on inactive slot A, then B. After that logs said " To flash additional zips, please reboot recovery to switch to the updated slot ". I'm going back on the menu
- Install TWRP Installer like previously
- Reboot Recovery : TWRP ask me if I want to install the TWRP App, I dismiss. After reboot of the recovery, it asks if I want to keep System Read Only, I swipe to allow modifications
- Wipe Data : Can't do it because TWRP is unable to mount storage. And after further investigations, I'm now on slot A, not B as before.
- Reboot recovery to slot B
- Wipe Data on slot B
- Reboot system
And It still booting on the stock Oxygen OS Rom, not the custom one installed before. I'm lost
The problem is that you are not performing factory reset.
Wipe data is not enough,you gotta go to wipe-format data-enter yes and swipe.
That is why you are getting bootloops and twrp unable to mount storage problem.
A/B is pretty simple.
You got two slots for many partitions like system vendor boot and all,but a single data partition.
Flash a rom from one slot,it always gets flashed to the other slot no matter what.So next time you reboot to recovery or system it's gonna be on the other slot.So here is the problem..one rom cannot decrypt data which was initially encrypted by another rom..so you gotta perform a data format instead of wipe.Thats it.
draentor said:
Thanks for your advices.
I'm trying right now, here's my steps :
- Wipe Data, Cache, Dalvik Cache (the standard Factory Reset)
- Install ROM : TWRP logs show that he's flashing on inactive slot A, then B. After that logs said " To flash additional zips, please reboot recovery to switch to the updated slot ". I'm going back on the menu
- Install TWRP Installer like previously
- Reboot Recovery : TWRP ask me if I want to install the TWRP App, I dismiss. After reboot of the recovery, it asks if I want to keep System Read Only, I swipe to allow modifications
- Wipe Data : Can't do it because TWRP is unable to mount storage. And after further investigations, I'm now on slot A, not B as before.
- Reboot recovery to slot B
- Wipe Data on slot B
- Reboot system
And It still booting on the stock Oxygen OS Rom, not the custom one installed before. I'm lost
Click to expand...
Click to collapse
lol i wrote all steps but you didn't do all of them. Use swipe to wipe for factory reset and you didn't format data
Joker123## said:
The problem is that you are not performing factory reset.
Wipe data is not enough,you gotta go to wipe-format data-enter yes and swipe.
That is why you are getting bootloops and twrp unable to mount storage problem.
A/B is pretty simple.
You got two slots for many partitions like system vendor boot and all,but a single data partition.
Flash a rom from one slot,it always gets flashed to the other slot no matter what.So next time you reboot to recovery or system it's gonna be on the other slot.So here is the problem..one rom cannot decrypt data which was initially encrypted by another rom..so you gotta perform a data format instead of wipe.Thats it.
Click to expand...
Click to collapse
Thanks for the explanation !
WesTD said:
lol i wrote all steps but you didn't do all of them. Use swipe to wipe for factory reset and you didn't format data
Click to expand...
Click to collapse
Well yes, I didn't understood the difference between Wipe and Format Data.
So let's resume :
Unlock Bootloader
Advanced -> Install Recovery Ramdisk : Install TWRP
Install -> Flash TWRP Installer
Install -> Flash Magisk
Reboot -> System : Reboot on stock OxygenOS Rooted
Then
Wipe -> Factory Reset : Wipe Data, Cache and Dalvik Cache, that means you just have to swipe on TWRP.
Install -> Flash ROM : Use the install function and install the ROM
Install -> Flash TWRP Installer : Don't reboot, go back and install as the previous step
Reboot -> Recovery : Reboot TWRP and it automatically load the other slot
Wipe -> Format Data : Click and type yes
Reboot -> System : Just reboot and it should load the installed ROM
is wiping internal storage compulsory?
aaryan45 said:
is wiping internal storage compulsory?
Click to expand...
Click to collapse
How would you do it ? This is an open discussion, I can't find one and only way of doing it
aaryan45 said:
is wiping internal storage compulsory?
Click to expand...
Click to collapse
Not wiping.. formatting..that is compulsory if your current data is encrypted
After multiple tries to verify the process :
Wipe -> Factory Reset + : Wipe Data, System, Cache and Dalvik Cache
Install -> Flash ROM : Use the install function and install the ROM
Install -> Flash TWRP Installer : Don't reboot, go back and install as the previous step
Reboot -> Recovery : Reboot TWRP and it automatically load the other slot
Wipe -> Format Data : Click and type yes
Reboot -> System : Just reboot and it should load the installed ROM
Install -> Magisk
Reboot -> System
Install -> Whathever you want
Reboot -> System
It worked !