Related
Hi
While flashing CM13 on my redmi 1s, I did a clean install, meaning wiping everything, and then when I went to flash CM13, TWRP just reboots the moment I swipe to install. This happens with any .zip file.
I installed CWM using fastboot, and that gives me the same problem. The moment I try to flash/install anything using a recovery, that recovery reboots and doesn't flash anything. My device is now useless since it doesn't have an OS installed and no way of doing so..
From what I can tell the system partition is bad because when I boot into recovery it isnt mounted
When I take out the battery now it just goes straight to the fastboot screen. I can take it into recovery but it goes to fastboot by default
Please help
Hi dude,
i guess you have checked the integrity of your cm13 ROM file and (winrar>test archive) , your best bet would be flashing a fastbootrom and then come back to cm. Head over to miui and download latest fastboot rom applicable to you.
And its usual booting into fastboot when there is no OS installed atleast for our device so chill dont loose hopes..!
vbvn said:
Hi dude,
i guess you have checked the integrity of your cm13 ROM file and (winrar>test archive) , your best bet would be flashing a fastbootrom and then come back to cm. Head over to miui and download latest fastboot rom applicable to you.
And its usual booting into fastboot when there is no OS installed atleast for our device so chill dont loose hopes..!
Click to expand...
Click to collapse
Flashing the fastboot rom doesn't work.. My recovery is broken too, because I can't flash anything.. In either MiRecovery 2.0.1, CWM or twrp.. When I flash the MIUI rom via fastboot it just boots into recovery..
EDIT, I just got it into MIUI but the 4.3 version from china, without Google, and I can't download google via the MI market. So i'm downloading an international version now and will try to flash using MiFlash.
Does anyone know how I can fix the recovery? It still won't flash anything and reboots the moment I try to.
So I have 2 questions:
1- how to root MIUI? Magisk work fine? Just flash it through TWRP? I used Magisk in a Nexus 6P with stock rom, don't know if it's the same with MIUI.
2- I see that there's some AOSP roms, flashing those roms is just copy the rom and gapps to the internal memory and flash Through TWRP normally?
Thanks.
1. Yes
2. Yep. Of course you will have to wipe in advance. Firmware flashing is also recommended. All info is in the XDA thread's of the roms..
So flash the lastest firmware then the rom right?
_Drifter_ said:
So flash the lastest firmware then the rom right?
Click to expand...
Click to collapse
Yep, update to the latest miui first, then you're good to go.
The best thing before installing a custom rom is to format your data completely and then reboot into recovery mode
So, using the lastest MIUI, formated data on TWRP and flashing the lastest Lineage with Open Gapps, this happend: ROM flashed, Splash screen then the phone rebooted and go right to TWRP. Tried RR Rom from Andy personal build but the gapps are giving me force closed on Google Service.
Any ideas?
Hey. I have a rooted with TWRP installed OnePlus 5T on OOS v5.1.1
I've been receiving the 5.1.3 upgrade for a while now and have decided to update. Can i dirty flash the package or do i need to wipe system and data? I'm guessing the root will not be retained and i will have to root again but will the TWRP recovery stay intact? Thanks for your answers
I guess you would be able dirty flash.
You have to flash the twrp and magisk root again. If you are going to flash latest Open Beta 11, you have to flash Beta 10 before to retain data.
XeniX_Force said:
Hey. I have a rooted with TWRP installed OnePlus 5T on OOS v5.1.1
I've been receiving the 5.1.3 upgrade for a while now and have decided to update. Can i dirty flash the package or do i need to wipe system and data? I'm guessing the root will not be retained and i will have to root again but will the TWRP recovery stay intact? Thanks for your answers
Click to expand...
Click to collapse
I have switched from 5.1.3 to beta11 like;
1- download the rom you want to install from oneplus site.
2- also download the stock recovery image from oneplus site.
3- put both files into the phone.
4- flash the stock recovery you downloaded.
5- boot into stock recovery and install the downloaded rom without wiping or formating anything.
6- enjoy your new rom with all your apps and data.
After the above steps you can install custom recovery and magisk again.
I also highly recommend to take a full backup of your phone .
Sent from my OnePlus 5T using XDA Labs
llvllaster said:
I have switched from 5.1.3 to beta11 like;
1- download the rom you want to install from oneplus site.
2- also download the stock recovery image from oneplus site.
3- put both files into the phone.
4- flash the stock recovery you downloaded.
5- boot into stock recovery and install the downloaded rom without wiping or formating anything.
6- enjoy your new rom with all your apps and data.
After the above steps you can install custom recovery and magisk again.
I also highly recommend to take a full backup of your phone .
Click to expand...
Click to collapse
Why was stock recovery flashed? Can the Rom not be installed using TWRP?
XeniX_Force said:
Why was stock recovery flashed? Can the Rom not be installed using TWRP?
Click to expand...
Click to collapse
Well, i always got an error with twrp. No OS installed or something like that. Tried also a dirty flash with twrp and phone was not able to boot. So i found the way with stock recovery.
Sent from my OnePlus 5T using XDA Labs
llvllaster said:
Well, i always got an error with twrp. No OS installed or something like that. Tried also a dirty flash with twrp and phone was not able to boot. So i found the way with stock recovery.
Sent from my OnePlus 5T using XDA Labs
Click to expand...
Click to collapse
Rom can be flashed with Blu Spark treble TWRP V8.78not normal TWRP. And after you flash reboot to recovery then flash magisk 15.3 and no verity V2 or version 3 if your not encrypted either work, I used V2 just fine.
If you try to flash magisk right after rom it will probably give you an error. Reboot only to recovery BEFORE letting the rom boot or you loose recovery, then magisk will flash, 15.3 is the least grievous version after a successful boot upgrading to 16.4 is easy.
16.6 has been giving people grief also.
I tried bliss rom pie on realme2pro.Here is some screenshot link-
https://imgur.com/rBKNRQQ
https://imgur.com/Q7g68mR
https://imgur.com/bEKYvS8
https://imgur.com/nDkrhiH
https://imgur.com/mddj5yk
https://imgur.com/xfN23Yp
Anyone tried yet?please try and let me know is it suitable for our realme2pro or not.
bliss rom gsi pie arm64 a only
link- https://www.xda-developers.com/bliss-roms-android-pie-gsi-project-treble-release/
it booted fine
Is fp working in this and the gcam??
No brother,fp not working
I tried A only using TWRP (latest version), but it just hangs at the realme logo then reboots back to recovery.
Note: even though I flashed the img to the system partition it complained no OS was installed.
Prior to that I had done a factory wipe and then a system wipe.
https://forum.xda-developers.com/pr.../rom-blissroms-9-0-official-4-4-2019-t3918303
11.7 A-Only Build with Gapps built in
11.8 A-Only Build Stock (without Gapps)
Both versions failed!
Many a times brother due to vendoe problem this loop happens. When this loop happens try to boot to recovery and flash vendor.img and you will be able to boot to rom
Step For Flashing-
1.latest twrp or r2x2 recovery
2.then backup
3.wipe system,vendor.userdata,cache,delvik cache for clean install
4.flash vendor zip first link- https://androidfilehost.com/?fid=1395089523397931146
5.unpack sytem image flash to system link- https://androidfilehost.com/?fid=1395089523397933944
6.wipe cache and delvik cache
7.Swipe to reboot
8.wait for few minutes it booted to bliss rom
caution-
latest system color os a.17 build vendor not worked
flash only linked vendor zip from above
then you good to go
best of luck
galibalmasanick said:
Step For Flashing-
1.latest twrp or r2x2 recovery
2.then backup
3.wipe system,vendor.userdata,cache,delvik cache for clean install
4.flash vendor zip first link- https://androidfilehost.com/?fid=1395089523397931146
5.unpack sytem image flash to system link- https://androidfilehost.com/?fid=1395089523397933944
6.wipe cache and delvik cache
7.Swipe to reboot
8.wait for few minutes it booted to bliss rom
caution-
latest system color os a.17 build vendor not worked
flash only linked vendor zip from above
then you good to go
best of luck
Click to expand...
Click to collapse
The same problem persists. It loads the REALME logo, and immediately reboots into the Bootloader.
Is vendor.zip flashed using TWRP Install? Or does it have to be flashed to "boot"?
vendor only flashable from twrp recovery
batflashholmes said:
The same problem persists. It loads the REALME logo, and immediately reboots into the Bootloader.
Click to expand...
Click to collapse
whats the variants phone are you using?
4/64 or 128ufs
indian or others
are you flashing inside any mode?
just flash vendor zip & bliss img to system and reboot,wait some time
Got it to work after flashing vendor.img
Does this require a device specific kernel to already be installed from a previous ROM? When I checked the kernel in my Realme 2 Pro it was the same kernel as what is used by device specific ROMs: 4.4.78-perf+
Can I flash a different kernel from here?
https://github.com/BlissRoms-Kernels
i am not responsible for that,you may try but recommend-no,thanks a lot
galibalmasanick said:
whats the variants phone are you using?
4/64 or 128ufs
indian or others
are you flashing inside any mode?
just flash vendor zip & bliss img to system and reboot,wait some time
Click to expand...
Click to collapse
I use a 4/64 model. Indian itself.
I did not flash inside any mode (that I know of at least).
I ended up bricking my phone completely somehow. It would show the RealMe logo, and then boot up into a blank white screen with an input bar, and keyboard. But nothing else. It refused to boot into the bootloader as well, saying that there was some error.
Also, I had tried flashing the vendor zip first, and then the bliss img. Whenever I did that though, it would show "No OS installed. Do you want to continue?"
Thanks for trying it but this isn't working on your device & I am also sorry, plz try stable rom from xda or stock rom that can be best for you,best of luck ?
Hey guys. Until the RR dev makes a thread, this will continue to stay in Discussion. I am NOT the dev for RR. So wanted to get the rom more exposure.
Rom: https://sourceforge.net/projects/resurrectionremix-ten/files/instantnoodlep/
Kernel source: https://github.com/luk1337/android_kernel_oneplus_sm8250
Changelog: https://get.resurrectionremix.com/ten/changelog/Changelog.txt
Be on OOS 10(both slots)(local upgrade last OOS 10 for slot b)
Flash twrp both slots(https://downloads.sourceforge.net/p...=cfhcable&r=https://forum.xda-developers.com/)
Flash rom
Reboot twrp
Wipe userdata(always a must when switching between OOS and custom)
(Optional) install kernel and magisk
Reboot
**UPDATE** this flash instructions work. I use these and ONLY these instructions. If you have a better way, good for you, but if you can't get it to boot, use these.
***UPDATE 2*** if you have installed Android 11 prior to installing this rom, you must msm back to OOS 10 and local upgrade OOS 10 again to slot b and only use Android 10 recovery
Nice one. :good:
Is twrp ok to wipe now? Or would we need stock to do so?
If the latter then may be worth booting twrp and retaining stock recovery to wipe.
Good to see a ROM thread for this.
Excellent.
My thanks to the dev too, it's appreciated.
dladz said:
Nice one. :good:
Is twrp ok to wipe now? Or would we need stock to do so?
If the latter then may be worth booting twrp and retaining stock recovery to wipe.
Good to see a ROM thread for this.
Excellent.
My thanks to the dev too, it's appreciated.
Click to expand...
Click to collapse
I've had no issues using latest twrp
jamescable said:
I've had no issues using latest twrp
Click to expand...
Click to collapse
Does it have oos cam?
areyouanand said:
Does it have oos cam?
Click to expand...
Click to collapse
Honestly, don't know. I don't use OOS can, but I don't think so
jamescable said:
Hey guys. Until the RR dev makes a thread, this will continue to stay in Discussion. I am NOT the dev for RR. So wanted to get the rom more exposure.
Rom: https://get.resurrectionremix.com/?dir=ten/instantnoodlep
Kernel source: https://github.com/luk1337/android_kernel_oneplus_sm8250
Be on OOS
Flash twrp both slots
Flash rom
Reboot twrp
Wipe userdata(always a must when switching between OOS and custom)
(Optional) install kernel and magisk
Reboot
Click to expand...
Click to collapse
Why to boot to twrp after flashing the rom?
We can just boot the twrp( not flash it)
Flash rom
Flash magisk ( optional)
Format data
Reboot
It should be mentioned that these builds are blind builds. The Dev doesn't own the device.
Kollachi said:
It should be mentioned that these builds are blind builds. The Dev doesn't own the device.
Click to expand...
Click to collapse
Correct but doesn't matter. I tested first few builds before they were released and now alots of people used them. They aren't beta or alpha but stable. So? What's your point?
cultofluna said:
Why to boot to twrp after flashing the rom?
We can just boot the twrp( not flash it)
Flash rom
Flash magisk ( optional)
Format data
Reboot
Click to expand...
Click to collapse
8pro has a recovery partition. So unless you flash a rom that overwrites twrp with another recovery (stock OOS, etc) then twrp will remain after rom flash
jamescable said:
Correct but doesn't matter. I tested first few builds before they were released and now alots of people used them. They aren't beta or alpha but stable. So? What's your point?
Click to expand...
Click to collapse
It's simple. If people run into issues or whatever he can't probably fix it. It was the same with treskmod for example.
Kollachi said:
It's simple. If people run into issues or whatever he can't probably fix it. It was the same with treskmod for example.
Click to expand...
Click to collapse
[Mod Edit] Telegram link removed.
jamescable said:
[Mod Edit] Telegram link removed.
Click to expand...
Click to collapse
He is blind building from latest los source that's all. Respect him for doing that, but it's not 100% guarantee for a fully working rom.
jamescable said:
8pro has a recovery partition. So unless you flash a rom that overwrites twrp with another recovery (stock OOS, etc) then twrp will remain after rom flash
Click to expand...
Click to collapse
This is something that i already know...
Questions are...
1. why to boot to twrp after flashing the rom( useless step)
2. Why to flash twrp on both slots and not inly boot it
cultofluna said:
This is something that i already know...
Questions are...
1. why to boot to twrp after flashing the rom( useless step)
2. Why to flash twrp on both slots and not inly boot it
Click to expand...
Click to collapse
1. Is NOT useless. That is for clean flashing which is ALWAYS recommend by every dev. When you dirty flash, it's at your own peril.
And 2. Once again. The OnePlus 8 pro has a recovery partition. So twrp does not get overwritten when you flash a rom. Like on 7 pro, we had to flash twrp after every rom flash. Not needed on 8 pro.
cultofluna said:
This is something that i already know...
Questions are...
1. why to boot to twrp after flashing the rom( useless step)
2. Why to flash twrp on both slots and not inly boot it
Click to expand...
Click to collapse
1. I think he meant to say reboot to recovery and not boot the twrp.img.
2. Yes you can boot twrp only. That's what im doing since OP7. But you will need to do this everytime you wanna flash something with twrp.
jamescable said:
1. Is NOT useless. That is for clean flashing which is ALWAYS recommend by every dev. When you dirty flash, it's at your own peril.
And 2. Once again. The OnePlus 8 pro has a recovery partition. So twrp does not get overwritten when you flash a rom. Like on 7 pro, we had to flash twrp after every rom flash. Not needed on 8 pro.
Click to expand...
Click to collapse
On your flashing instructions you said. "flash twrp on both slots"
So im asking one more time,... why not just to boot the twrp img on fastboot and flash the rom...
What is this about recovery partition ... everybody knows that the 8 pro has a separate recovery partition
EDIT..Reboot to twrp after flashing the Rom is useless...
I insist. .dont needed
cultofluna said:
On your flashing instructions you said. "flash twrp on both slots"
So im asking one more time,... why not just to boot the twrp img on fastboot and flash the rom...
What is this about recovery partition ... everybody knows that the 8 pro has a separate recovery partition
EDIT..Reboot to twrp after flashing the Rom is useless...
I insist. .dont needed
Click to expand...
Click to collapse
It's in the pic I uploaded. Even the twrp dev said to flash it. So you won't have to fastboot boot anymore. Once you flash it. It's on your phone and won't go away when you reboot recovery
Every phone used to have a boot(kernel) partition, system partition, modem/radio partition, bootloader, userdata, and a few other INCLUDING recovery partition. Recently, the recovery was missing but now it's back. So we no longer have to have to boot twrp but flash it
Hello everyone, I need help installing this rom please, I have the latest TWRP 3.4.0-14-Mauronofrio installed in both slots, latest stable OOS in both slots, I have an IN2025 and for some reason I get this error with TWRP. Thanks in advance guys.
oscarmaldonado said:
Hello everyone, I need help installing this rom please, I have the latest TWRP 3.4.0-14-Mauronofrio installed in both slots, latest stable OOS in both slots, I have an IN2025 and for some reason I get this error with TWRP. Thanks in advance guys.
Click to expand...
Click to collapse
That is strange. I also have 2025. Try moving the rom to phone instead of usb device. Since this is an updated twrp may be an issue. However. I did NOT have OOS installed on both slots. I flashed latest OOS full rom, used OOS recovery to wipe data. Booted and then flashed twrp to both slots, flashed RR, reboot recovery and flashed magisk