Related
I am currently using bootloader 10.4.4.25 and cannot install the latest cm 11
And I am using CWR 6.0.4
Can anyone advise how can I update the bootloader so I can install cm11?
Thanks
Download the latest Asus firmware, unzip the file once resulting in another zip.
Copy that zip to your tabet and flash it in CWM (that you have everything you care about backed up off the tablet goes without saying, right?). That will get you onto the latest bootloader but also wipe your custom recovery.
Boot into fastboot, flash a CM11 compatible recovery.
Reboot
Boot into recovery, do a factory wipe and then flash the rom.
Thanks for the advise. I am downoading the latest firmware from ASUS website and will install it.
I am not sure how to flash a CM11 compatible recovery from fastboot. Can you give more details please? Shoudl I follow the root instruction from the ROM post and re-root the machine again?
Thanks in advance
berndblb said:
Download the latest Asus firmware, unzip the file once resulting in another zip.
Copy that zip to your tabet and flash it in CWM (that you have everything you care about backed up off the tablet goes without saying, right?). That will get you onto the latest bootloader but also wipe your custom recovery.
Boot into fastboot, flash a CM11 compatible recovery.
Reboot
Boot into recovery, do a factory wipe and then flash the rom.
Click to expand...
Click to collapse
Hallo,
I have a problem. I flashed newest TWRP 2.8.7.1 (I also tried 2.8.7.0) onmy Mi4C and installed some ROMS (sMiUI, Decato, CM12.1) but even if flash of TWRPs and installation of ROMS was successful without error, the device is always booting into Recovery/TWRP.
So problem is that device is not starting into system!
- I tried with power button reset
- I tried with "reboot to system"
- I tried with battery removal!
- I also tried new installation of TWRP and/or several ROMS. (e.g. sideloading ADP is also working)
- I also made some (full) WIPEs / Fix Permissions
but it is always starting only to TWRP.
After device is starting, MUI-symbol appears for 5-10 seconds and then TWRP is loading, but not ROM.
What can I do? Maybe installation a new Kernel or something?
thanks in advance,
Jimmy
jjeans said:
Hallo,
I have a problem. I flashed newest TWRP 2.8.7.1 (I also tried 2.8.7.0) onmy Mi4C and installed some ROMS (sMiUI, Decato, CM12.1) but even if flash of TWRPs and installation of ROMS was successful without error, the device is always booting into Recovery/TWRP.
So problem is that device is not starting into system!
- I tried with power button reset
- I tried with "reboot to system"
- I tried with battery removal!
- I also tried new installation of TWRP and/or several ROMS. (e.g. sideloading ADP is also working)
- I also made some (full) WIPEs / Fix Permissions
but it is always starting only to TWRP.
After device is starting, MUI-symbol appears for 5-10 seconds and then TWRP is loading, but not ROM.
What can I do? Maybe installation a new Kernel or something?
thanks in advance,
Jimmy
Click to expand...
Click to collapse
Download fastboot rom and flash it
thank you that worked..
but I have still the problem when I flash several versions of TWRP, that a reboot/start of the system will always end up within the recovery.
Only a a reflash of fastboot rom helps, but then I have the old mi recovery that does not work for other ROMs :/
a strange behaviour.
So I can flash TWRP, but it is not possible to boot into the system...
Without a newer TWRP that can "boot into system" I cannot use Custom ROMS
jjeans said:
thank you that worked..
but I have still the problem when I flash several versions of TWRP, that a reboot/start of the system will always end up within the recovery.
Only a a reflash of fastboot rom helps, but then I have the old mi recovery that does not work for other ROMs :/
a strange behaviour.
So I can flash TWRP, but it is not possible to boot into the system...
Without a newer TWRP that can "boot into system" I cannot use Custom ROMS
Click to expand...
Click to collapse
How do you flash recovery tell me the procedure?
Talha7866 said:
How do you flash recovery tell me the procedure?
Click to expand...
Click to collapse
Hallo,
I used some manuals for flashing.
e.g.
en.miui.com/thread-166465-1-1.html
gammerson.com/2015/10/install-twrp-recovery-mi4c-root-it.html
+ some manuals from decuro rom and sMiUI Rom
In summary:
1. Pre steps: Download USB & Adb drivers / Download TWRP Recovery 2.8.7.0 for Xiaomi Mi4C / I also tried 2.8.7.1
2. Flashing: Boot phone into fastboot --> Connect phone with USB (I tried before and after boot to fastboot) --> CMD --> "fastboot flash recovery" <recovery-name>.img
3. After successful flash of 40-50 MB TWRP recovery I tried CMD "fastboot reboot" / I tried also without reboot command (with Vol+ & Power) / I tried also only with power button
Always system boots to TWRP recovery.
When I choose ROM afterwards with new TWRP recovery and flash it, it says successful installed, but reboot does not start to ROM
At the moment I always do fastboot rom reflash, that old system will come back and work. Flashing ROMS with old system (via updater app and old Miui recovery) is not working, it is always update error, even if I rename ROM to "update.zip".
What I never did rooting the phone, so flashify says "device not rooted". I do not know If I have to root, I assume not. I do not want root, because I will use a company app that needs an unrooted phone.
thanks,
Jimmy
jjeans said:
Hallo,
I used some manuals for flashing.
e.g.
en.miui.com/thread-166465-1-1.html
gammerson.com/2015/10/install-twrp-recovery-mi4c-root-it.html
+ some manuals from decuro rom and sMiUI Rom
In summary:
1. Pre steps: Download USB & Adb drivers / Download TWRP Recovery 2.8.7.0 for Xiaomi Mi4C / I also tried 2.8.7.1
2. Flashing: Boot phone into fastboot --> Connect phone with USB (I tried before and after boot to fastboot) --> CMD --> "fastboot flash recovery" <recovery-name>.img
3. After successful flash of 40-50 MB TWRP recovery I tried CMD "fastboot reboot" / I tried also without reboot command (with Vol+ & Power) / I tried also only with power button
Always system boots to TWRP recovery.
When I choose ROM afterwards with new TWRP recovery and flash it, it says successful installed, but reboot does not start to ROM
At the moment I always do fastboot rom reflash, that old system will come back and work. Flashing ROMS with old system (via updater app and old Miui recovery) is not working, it is always update error, even if I rename ROM to "update.zip".
What I never did rooting the phone, so flashify says "device not rooted". I do not know If I have to root, I assume not. I do not want root, because I will use a company app that needs an unrooted phone.
thanks,
Jimmy
Click to expand...
Click to collapse
I have had the same issue, and read somewhere that it is because you tried flashing a rom in stock recovery and failed, that causes recovery bootloop. I was in same position other than i erased most og my partitions except recovery, and then installed fastboot rom, and it was all good again. Not saying ypu should erase any partitions! Rather not try and flash anything in stock recovery ever.
zhart said:
I have had the same issue, and read somewhere that it is because you tried flashing a rom in stock recovery and failed, that causes recovery bootloop. I was in same position other than i erased most og my partitions except recovery, and then installed fastboot rom, and it was all good again. Not saying ypu should erase any partitions! Rather not try and flash anything in stock recovery ever.
Click to expand...
Click to collapse
Thank you for your answer.
So I can do:
1. Wipe all data (it is the only option in recovery)
2. Re-flash fastboot rom
3. Try again to flash new recovery & install custom ROM
Is that correct?
What partition can I securely erase? and how? because erase is only possible with newer Recovery.
jjeans said:
Thank you for your answer.
So I can do:
1. Wipe all data (it is the only option in recovery)
2. Re-flash fastboot rom
3. Try again to flash new recovery & install custom ROM
Is that correct?
What partition can I securely erase? and how? because erase is only possible with newer Recovery.
Click to expand...
Click to collapse
I would clean install fastboot rom, and then install the latest recovery, and try to install a rom. All from buttom so you know exactly what you have done
I accidentaly erased my partitions with fastboot. Data, boot, and internal ? I think. Would not recomend it.
Sorry, what exaclty is a fastboot rom and where do i get it?
zhart said:
I would clean install fastboot rom, and then install the latest recovery, and try to install a rom. All from buttom so you know exactly what you have done
I accidentaly erased my partitions with fastboot. Data, boot, and internal ? I think. Would not recomend it.
Click to expand...
Click to collapse
I don't know what happens all the time.
Currently I used MiFlash to make a clean fastboot install. I choosed in MiFlash "flash_all.bat" to do it. (flash_all.bat means everything was reinstalled, also recovery.img). Afterwards everything was normal, MiRecovery 2.x and Mi4C MiUI 7 chinese version was installed without error. But after manual flashing TWRP with "fastboot flash recovery xxx", the recovery loop was again! :/
So AGAIN I made a clean fastboot install again with MiFlash application, but this time I REPLACED the recovery.img with the newest TWRP (renamed to recovery.img) within the fastboot rom installation folder "images". I could see that MiFlash flashed THIS! recovery.img, but after that again the old Mi Recovery was on the device and no TWRP. But why? I replaced the original recovery.img file! How can that happen?
The flash_all.bat included flashing recovery and I could confirm it during the fastboot flash. Strange.
I used fastboot rom libra_images_V7.0.16.0.LXKCNCI_20151104.0000.4_5.1_cn
MiFlash newest version and I tried with 2 TWRP versions (one from decuro and one from sMiUI)
Maybe my phone has a problem with flahing recoverys in general I don't know.
jjeans said:
Maybe my phone has a problem with flahing recoverys in general I don't know.
Click to expand...
Click to collapse
it sound very strange i did all these steps and my phone was all good after it. is it the newest recovery? the one with material theme and touch fix you are using? if not, then thats the only difference between your procedure and mine :/
i hope you can fix it
Edit: I can see that i have the following fastboot roms downloaded, so i used one of these:
libra_images_V7.0.6.0.LXKCNCI_20150917.0000.1_5.1_cn_4dd76a55cb.tgz
or libra_images_V7.0.15.0.LXKCNCI_20151104.0000.4_5.1_cn_f6e955ee14.tgz
What I would do, is fastboot original ROM, reboot to recovery, factory reset, recboot to fastboot to re-flash TWRP and then command "fastboot boot recovery" to get to TWRP and install your ROM.
Didn't has this pb on Mi4c, but had it a few times on Nexus5.
Hope this helps...
Hello, don't know if applicable. I've read on mi forums that dev Roms need dev recovery, that's different from twrp for stock rom.....
guegangster said:
What I would do, is fastboot original ROM, reboot to recovery, factory reset, recboot to fastboot to re-flash TWRP and then command "fastboot boot recovery" to get to TWRP and install your ROM.
Didn't has this pb on Mi4c, but had it a few times on Nexus5.
Hope this helps...
Click to expand...
Click to collapse
Hallo,
thank you, that worked for me finally
I have now used another TWRP 2.8.7.1 with touch-issue, but that is now no problem.
I flashed also xiaomi.eu rom, for now seems to be stable and cleaned.
strange everything, but now it is fixed.
BR,
Jimmy
Hi,
I have a note 3 still on official 4.4.2 but rooted. Since a few days my battery starts draining fast. Maybe it's time to update. Or is it not profitable for such an old device to upgrade to whatever the latest version is?
What is the latest official version for the note 3? And what is the best way to get that? Just unroot and use the update from the system?
You could use a different kernel or try a custom ROM.
Well a few years ago I was change roms constantly on different phones. That was 3 years ago. Now I am not into roms anymore just need a stable phone. Besides I have really no clue how the room installing these days work. Just install from zip in recovery?
Can I do that safe from 4.4.2?
efjbdejong said:
Well a few years ago I was change roms constantly on different phones. That was 3 years ago. Now I am not into roms anymore just need a stable phone. Besides I have really no clue how the room installing these days work. Just install from zip in recovery?
Can I do that safe from 4.4.2?
Click to expand...
Click to collapse
Yes, but you would have to update your bootloader and modem through Odin first for Lollipop and Marshmallow based ROMs to work and boot on your phone.
Running Kitkat bootloader won't make your phone bootup on Lollipop and or Marshmallow based ROMs.
You need a custom recovery of course before flashing a ROM ; TWRP , CWM or PhilZ
(TWRP Method)
Factory Reset your Phone.
Clear Dalvik Cache, System, Cache, Data.
Do not select Internal Storage and Micro SD card, if you do, storage on both internal and external storage would be erased.
I recommend using TWRP 2.8.7.0 as the latest version which is the 3.0.2.0 does not support Aroma Installer.
After you have Factory reset and cleared dalvik cache, system, cache and data.
Now do this
1) Boot into recovery
2) Flash ROM
Done.
With SuperSU ;
1) Boot into recovery
2) Flash ROM
3) Flash SuperSU
LitDesign said:
Yes, but you would have to update your bootloader and modem through Odin first for Lollipop and Marshmallow based ROMs to work and boot on your phone.
Running Kitkat bootloader won't make your phone bootup on Lollipop and or Marshmallow based ROMs.
You need a custom recovery of course before flashing a ROM ; TWRP , CWM or PhilZ
(TWRP Method)
Factory Reset your Phone.
Clear Dalvik Cache, System, Cache, Data.
Do not select Internal Storage and Micro SD card, if you do, storage on both internal and external storage would be erased.
I recommend using TWRP 2.8.7.0 as the latest version which is the 3.0.2.0 does not support Aroma Installer.
After you have Factory reset and cleared dalvik cache, system, cache and data.
Now do this
1) Boot into recovery
2) Flash ROM
Done.
With SuperSU ;
1) Boot into recovery
2) Flash ROM
3) Flash SuperSU
Click to expand...
Click to collapse
OK the so I have to flash 2 times the same rom? Which is the best rom that comes closed to an official untouched one?
I don't understand how to flash the bootloader. Is that installing from recovery? Using install from zip?
For installing bootloader and modem you have to flash with odin.
If you search google then you can find the method how to do it and for bootloader and modem search any latest version of custom rom.you will find the links.
Sent from my SM-G935F using Tapatalk
OK so first flash bootloader and modem in Odin. So my rom is still 4.4.2. After that.
Then flash a recovery. Still phone is on 4.4.2
Then flash a rom. ....
Anyone?
efjbdejong said:
Anyone?
Click to expand...
Click to collapse
In my opinion i would say flash lollipop firmware first before you should root it all by odin
efjbdejong said:
OK so first flash bootloader and modem in Odin. So my rom is still 4.4.2. After that.
Then flash a recovery. Still phone is on 4.4.2
Then flash a rom. ....
Click to expand...
Click to collapse
Flash bootloader and modem on Odin, it doesn't matter whether you are on Kitkat.
SM-N9005 bootloader and modem :
https://idlekernel.com/flash-tools/firmware/hlte_SM-N9005XX/N9005XXUGPOK2/
Steps before installing a ROM:
1) Download both bootloader and modem from the link given above.
2) Switch off your Phone
3) Boot phone into Download mode by pressing home button and volume down button
4) Connect phone to computer
5) Open up Odin
6) Click on BL and select BL_N9005XXUGPOK2_BOOTLOADER
7) Click on CP and select CP_N9005XXUGPOK2_MODEM
8) Click Start
-----------------------------------------------
Once done, here's how to install a ROM
You have to download a ROM and STORE IT INTO YOUR PHONE before doing this
1) Download TWRP 2.8.7.0
2) Connect phone to computer
3) Open up Odin
4) Click AP, browse to where you have stored the TWRP file/zip and click on it
5) Press Start
6) Switch off Phone and boot into recovery mode by pressing ; Power button, volume up, home button at the same time. Hold it till you feel the phone vibrates twice.
7) Wipe Dalvik Cache, System, Cache, Data and FACTORY RESET.
DO NOT SELECT INTERNAL STORAGE AND MICRO SD CARD.
8) Flash ROM
9) Reboot
-----------------------------------------------
Installing a ROM depends, if it doesnt have GAPPS you have to download it.
If it doesn't comes in with SUPERSU you have to download it. Example ;
Flash ROM
Flash GAPPS
Flash SUPERSU
efjbdejong said:
OK so first flash bootloader and modem in Odin. So my rom is still 4.4.2. After that.
Then flash a recovery. Still phone is on 4.4.2
Then flash a rom. ....
Click to expand...
Click to collapse
Don't forget to backup ur whole nandroid before do anything n save it to ur drive computer, trust me
U can use twrp/cwm or flashfire
Stay on 4.4.2, reset to factory, backup first, your battery will be even worst on Lillipop or Marshmellow.
Get a new battery
Just update to 5.0.1, if you still have issues, flash a rom. Also this should've been posted in the Q&A section, or a search would've worked.
Ok I updated now to lollipop thru kies. All went well. Thinking about upgrading to Marshmallow.
Hello Android developers and enthusiasts,
I've been installing ROM since 2011 so I would not call myself a n00b however I seemingly cannot install an Android 10 ROM without issues. So this is a plea for help and advice!
I know you need to have OOS installed before you install a custom ROM so I use Auto Flash ROM to install OOS with Android 9 via System Update. I then boot and set up phone, install update, reboot and then install the OOS android 10 via the System Update. I then have a OOS installed with Android 10.
Why would I use such an elaborate method you may ask? Well, I tried to download latest OOS from OnePlus site and wipe phone and then install OOS but that fails (didn't record the error I'm afraid).
I then download all the ROM + dependencies on an USB stick and use fastboot to flash Mauronofrio TWRP. I then follow the steps in the ROM instructions. For EvolutionX these were:
First Time Install / Clean Flash
- Have OOS 10.3 flashed to both slots!!
- Boot to recovery
- Flash BUILD.zip (TWRP built-in)
- Wipe Cache
- Format data
- Reboot to recovery (optional)
- Flash Magisk.zip (optional)
- Reboot to system & #KeepEvolving
Click to expand...
Click to collapse
I followed these to the letter but when i rebooted system I got a snapdragon error and it wouldn't even boot into TWRP until I used fastboot to flash boot into TWRP. I also tried HavocROM and same happened.
I did manage to install Syberia using above method but I didn't like the ROM that much unfortunately.
Finally, I've also read up a lot on Slot A and B but it still is not very clear to me. I think I understand it but what happens does not confirm my theories
I therefore have some questions:
- Should I be able to wipe my phone and install OOS on a wiped phone and then install a custom ROM?
- When I install ROM and it says "Reboot Recovery" and then install ROM again. But if I check what slot is being used the reboot doesn't seem to change the slot. My assumption was that booting recovery was to install ROM in the other slot. Is that correct?
Any other tips you can give me?
Again, I like to stress I am not new to installing custom ROMs so I am a bit disappointed that this is causing me such grief.
Following some answers I will retry tomorrow so I can give some more details if needed. For now, appreciate any help.
roel1976 said:
Hello Android developers and enthusiasts,
I've been installing ROM since 2011 so I would not call myself a n00b however I seemingly cannot install an Android 10 ROM without issues. So this is a plea for help and advice!
I know you need to have OOS installed before you install a custom ROM so I use Auto Flash ROM to install OOS with Android 9 via System Update. I then boot and set up phone, install update, reboot and then install the OOS android 10 via the System Update. I then have a OOS installed with Android 10.
Why would I use such an elaborate method you may ask? Well, I tried to download latest OOS from OnePlus site and wipe phone and then install OOS but that fails (didn't record the error I'm afraid).
I then download all the ROM + dependencies on an USB stick and use fastboot to flash Mauronofrio TWRP. I then follow the steps in the ROM instructions. For EvolutionX these were:
I followed these to the letter but when i rebooted system I got a snapdragon error and it wouldn't even boot into TWRP until I used fastboot to flash boot into TWRP. I also tried HavocROM and same happened.
I did manage to install Syberia using above method but I didn't like the ROM that much unfortunately.
Finally, I've also read up a lot on Slot A and B but it still is not very clear to me. I think I understand it but what happens does not confirm my theories
I therefore have some questions:
- Should I be able to wipe my phone and install OOS on a wiped phone and then install a custom ROM?
- When I install ROM and it says "Reboot Recovery" and then install ROM again. But if I check what slot is being used the reboot doesn't seem to change the slot. My assumption was that booting recovery was to install ROM in the other slot. Is that correct?
Any other tips you can give me?
Again, I like to stress I am not new to installing custom ROMs so I am a bit disappointed that this is causing me such grief.
Following some answers I will retry tomorrow so I can give some more details if needed. For now, appreciate any help.
Click to expand...
Click to collapse
Hi!
I had this exact same problem a couple months ago. Rebooting to recovery used to change slots for me, but then it stopped.
What you can do is change active slot manually on Reboot section. By doing this, you don't even have to reboot to recovery in other to flash the other slot (altough I do it just to be safe).
And remember: the rom is flashed on the inactive slot, so after the final flash you gotta change slots one more time.
When you flash one ROM on top of another different ROM, particularly OOS to custom, always wipe data and not format data, because some custom ROMs do not support being unencrypted in the first time and then encrypt on the first boot. So do it like this:
Flash OOS
Flash TWRP
Reboot recovery
Flash OOS
Flash TWRP
Reboot system
Complete initial setup
Reboot to recovery
Wipe (not format) data
Flash custom ROM (start here for dirty flashing ROM update)
Flash TWRP
Reboot recovery
Flash custom ROM
Flash TWRP
Reboot recovery
Flash Magisk
Reboot system
I don't like built-in TWRP in custom ROMs. I always use @mauronofrio's TWRP. So regardless if the custom ROM I'm using has TWRP built-in or not, I always use the method above. I didn't have a problem with installing ROMs using his TWRP. Slots always switch when flashing ROM.
Thanks for the info, it really helps.
One question: in your experience can you wipe your phone and then installl OOS on the wiped phone?
So I just booted into TWRP, did standard wipe action: Data, Cache, and Dalvik. I then try to flash the latest OOS zip and I then get this error:
Error applying update: 7 (ErrorCode::kInstallDeviceOpenError)
Updater process ended withL ERROR: 1.
Error installing zip file: '/usbstorage/00, INSTALL/OnePlus6Oxygen_22_OTA_044_all_2002220042_a46425f1bfe43d2.zip
FIXED: I was using TWRP 3.3.1.11 and I then found out there was a newer version: 3.3.1.18 which you can get here: https://sourceforge.net/projects/mauronofrio-twrp/files/Enchilada/
I am now able to install OOS from scratch (ie wiped phone).
remewer said:
When you flash one ROM on top of another different ROM, particularly OOS to custom, always wipe data and not format data, because some custom ROMs do not support being unencrypted in the first time and then encrypt on the first boot. So do it like this:
Flash OOS
Flash TWRP
Reboot recovery
Flash OOS
Flash TWRP
Reboot system
Complete initial setup
Reboot to recovery
Wipe (not format) data
Flash custom ROM (start here for dirty flashing ROM update)
Flash TWRP
Reboot recovery
Flash custom ROM
Flash TWRP
Reboot recovery
Flash Magisk
Reboot system
I don't like built-in TWRP in custom ROMs. I always use @mauronofrio's TWRP. So regardless if the custom ROM I'm using has TWRP built-in or not, I always use the method above. I didn't have a problem with installing ROMs using his TWRP. Slots always switch when flashing ROM.
Click to expand...
Click to collapse
I tried this method and everytime I can't seem to flash oos onto the other slot because when it reboots to recovery the folder is encrypted so I can't see which file is the zip. How do I flash the seccond OOS if it shows up encrypted in TWRP.
I have a OnePLus 6 with the latest OOS now because I got into boot loop and i used a flash-all.bat to get back to stock. I also use maronofrio's twrp because that works.
harshybar said:
I tried this method and everytime I can't seem to flash oos onto the other slot because when it reboots to recovery the folder is encrypted so I can't see which file is the zip. How do I flash the seccond OOS if it shows up encrypted in TWRP.
I have a OnePLus 6 with the latest OOS now because I got into boot loop and i used a flash-all.bat to get back to stock. I also use maronofrio's twrp because that works.
Click to expand...
Click to collapse
If you can boot OOS fine, try to do a local update so that both slots have OOS. Then try to flash a custom ROM again using the method I've mentioned.
remewer said:
If you can boot OOS fine, try to do a local update so that both slots have OOS. Then try to flash a custom ROM again using the method I've mentioned.
Click to expand...
Click to collapse
When you say local update you mean while I am running the rom, go to settings then do update from local source?
harshybar said:
When you say local update you mean while I am running the rom, go to settings then do update from local source?
Click to expand...
Click to collapse
Exactly
GuestD2559 said:
When you flash one ROM on top of another different ROM, particularly OOS to custom, always wipe data and not format data, because some custom ROMs do not support being unencrypted in the first time and then encrypt on the first boot. So do it like this:
Flash OOS
Flash TWRP
Reboot recovery
Flash OOS
Flash TWRP
Reboot system
Complete initial setup
Reboot to recovery
Wipe (not format) data
Flash custom ROM (start here for dirty flashing ROM update)
Flash TWRP
Reboot recovery
Flash custom ROM
Flash TWRP
Reboot recovery
Flash Magisk
Reboot system
I don't like built-in TWRP in custom ROMs. I always use @mauronofrio's TWRP. So regardless if the custom ROM I'm using has TWRP built-in or not, I always use the method above. I didn't have a problem with installing ROMs using his TWRP. Slots always switch when flashing ROM.
Click to expand...
Click to collapse
@Cypher_01, Try this guide. This worked for me. I did not reinstall Nikgapps. Maybe that's where the problem lies? Don't forget to change the update slot at the end before you restart.
Guys!!! what the hell!
i did everyting was written in here. Bootloader unlock, everything ok, flashed twrp, flash vbeta.img then flash any rom but the phone never boot! still go always and alwasy again to recovery!!!
What am i missing?
Format data in twrp.then reboot
I've done everything. Format everything ecc but nothing has changed...still no boot and recovery immediately.
I've tried to put the stock recovery again and it boots (i flashed of course via twpr the c.01 RUI ozip file before). I really can't understand.
I've tried to root the phone but again problem. I put the twrp recovery again (on the C.01 stock rom) then flashed magisk 20.1 or the latest. Everything ok, rebooted and....it says the boot img is corrupted, write or go to the service support! So i entered again in fastboot and flashed a new boot.img. No boot but can enter recovery. Put again the twrp, flashed stock rom again, put stock recovery, format data and now eveyrhing ok. Why so hard to even root???
Did you check format data on right bottom of twrp.this is not same as the wiping data
i made all format.
another curious stuff is. I put twrp, vbeta img . Reboot in twrp. ok. I reboot phone, go to RUI then i try to go again in recovery and .....no more twrp! but stock one! twrp has been replaced! why!!!!!?
Correct,Stock rom will replace twrp to stock recovery.but custom rom not changing recovery
I was doing the same mistake.
You must Format Data after flashing Rom and if on reboot to system it says Os not installed then first reboot to recovery.
waqar bukhari said:
I was doing the same mistake.
You must Format Data after flashing Rom and if on reboot to system it says Os not installed then first reboot to recovery.
Click to expand...
Click to collapse
uhm ok.
So basically - Flash twrp - go to twrp - flash rom (pixel experience for example) - format data - and then reboot to recovery again?? what's the point sorry
oh man i missed up the format stuff.
Thank you very much. I made it. After format data then i insalled the pixel experience rom via adb sideload now it started let's see hows it the modding rom world on this device!
I followed all those steps. My phone boots, stays on Lineage logo for 4-5 minutes and then it reboots back to orange recovery. Any idea? Thanks!