Recently I had installed oxygen os 3.1.2 for oneplus one.
As I didn't like it I tried switching back to tugapower but it stated "error status 7". Thought it might be some system configuration so wiped all system and deleted rom to install new one. But again same issue persists. Then I tried flashing new twrp image thinking it might solve the issue but got " error status 1". Now I am stuck in 1+ logo and can't boot to recovery and my device won't turn on. Please help
zcross10 said:
Recently I had installed oxygen os 3.1.2 for oneplus one.
As I didn't like it I tried switching back to tugapower but it stated "error status 7". Thought it might be some system configuration so wiped all system and deleted rom to install new one. But again same issue persists. Then I tried flashing new twrp image thinking it might solve the issue but got " error status 1". Now I am stuck in 1+ logo and can't boot to recovery and my device won't turn on. Please help
Click to expand...
Click to collapse
First reflash twrp, then perform a full wipe and try reinstalling the rom. By the way, you posted this in the wrong forum, but whatever.
Posted in wrong section.
Related
So, I recently installed TWRP on my SM-T813. I then flashed LineageOS 14.1 successfully, but didn't like it, so I reflashed stock ROM. Everything was working fine, until I tried to install SuperSU on my stock ROM.
Now, my tablet is stuck into booting recovery mode, and cannot boot into the ROM (although Download Mode is still usable, more on that later). Upon trying to reflash the backup again, and attempting to reboot, TWRP states "No OS installed!" SO I tried reflashing the LineageOS ROM, same thing. Upon trying to restore a firmware with Odin, I get an error saying "SW REV CHECK FAIL aboot Fused 2 Binary 1." After finding no answers, I delved into my SD card and found that I had flashed the WRONG version of SuperSU, although it had been cleared when reformatting with TWRP. I then tried using the CORRECT SuperSU, and I am still stuck in recovery bootloop.
Can someone analyze what's going on and see what the problem is?
(SM-T813 - USA)
Lucarje said:
So, I recently installed TWRP on my SM-T813. I then flashed LineageOS 14.1 successfully, but didn't like it, so I reflashed stock ROM. Everything was working fine, until I tried to install SuperSU on my stock ROM.
Now, my tablet is stuck into booting recovery mode, and cannot boot into the ROM (although Download Mode is still usable, more on that later). Upon trying to reflash the backup again, and attempting to reboot, TWRP states "No OS installed!" SO I tried reflashing the LineageOS ROM, same thing. Upon trying to restore a firmware with Odin, I get an error saying "SW REV CHECK FAIL aboot Fused 2 Binary 1." After finding no answers, I delved into my SD card and found that I had flashed the WRONG version of SuperSU, although it had been cleared when reformatting with TWRP. I then tried using the CORRECT SuperSU, and I am still stuck in recovery bootloop.
Can someone analyze what's going on and see what the problem is?
(SM-T813 - USA)
Click to expand...
Click to collapse
This has been posted a million times all over the forum. A quick search here or Google would have revealed the answer
You need to flash a revision 2 firmware. So that would be something like t813xxu2 in the firmware build number.
Sorry for being late with reply. Your advice helped me fix my tablet! Thanks so much!
My Mi 8 got bricked by the latest MIUI update. I installed the software update from settings and clicked reboot and it booted straight to TWRP (more on that in a bit). I tried rebooting to system but it just went straight back to TWRP. I have unlocked the bootloader and also rooted my phone but as I kept the stock ROM I wouldn't think this would break it. In hindsight, after doing a bit of looking around it seems like people tend to reflash stock.img before updating or something when they've rooted their phone? Wish I'd known that before I clicked update.
I tried flashing a different ROM but when I go to reboot it just says "no OS installed. Are you sure you want to reboot?" and just goes into bootloop stuck on the Mi logo
using fastboot adb tools I can boot it into TWRP (has never worked using the volume and power buttons) and flashing ROMs seems to go okay but reboot says no OS installed and it bootloops, as I said.
I've tried flashing the latest MIUI build for my device, pixel experience, lineage OS and all of them yield the same results. Happy to answer any questions and try out any suggestions that anyone has. I'm really quite desperate!
SOLUTION: I flashed the stock firmware using the xiaomi mi flash tool. This fixed pretty much everything apart from now the camera doesn't work lol
What twrp you are using?
dimitrisverlis said:
what twrp you are using?
Click to expand...
Click to collapse
twrp-3.2.1-0611
Wipe everything, FORMAT data and update xiaomi firmware.
I was on latest stock PIE. First I tried to flash HEX kernel over stock PIE, but this resulted into bootloop.
Then I tried to flash, AICP and CRDROID, for both, it says, "error applying update: 7(errorcode::kinstalldeviceoppenerror) updater process ended with error 1".
Need help here ASAP. As I unable to boot to system right now. Using TWRP : 3.3.1 as TWRP 3.2.3 gets only black screen.
shivamg95 said:
I was on latest stock PIE. First I tried to flash HEX kernel over stock PIE, but this resulted into bootloop.
Then I tried to flash, AICP and CRDROID, for both, it says, "error applying update: 7(errorcode::kinstalldeviceoppenerror) updater process ended with error 1".
Need help here ASAP. As I unable to boot to system right now. Using TWRP : 3.3.1 as TWRP 3.2.3 gets only black screen.
Click to expand...
Click to collapse
I think Thats because of TWRP 3.3.1 version cuz this version got some issues for installing or updating roms.
Maharram said:
I think Thats because of TWRP 3.3.1 version cuz this version got some issues for installing or updating roms.
Click to expand...
Click to collapse
Any suggestion regarding which twrp should I use?
shivamg95 said:
Any suggestion regarding which twrp should I use?
Click to expand...
Click to collapse
I have tried pitch black and team win recovery project and everytime i get black screen. Im using fastboot to flash anything but idk u can flash hex kernel with fastboot or not. Just ask it from the hex kernel thread
literally just been messing with the exact same problem - try the pitch black recovery twrp - i cant find the link, have a look, if not come back here and I make available via dropbox or something. Everything failed with the error you get, i tried with this version and pixel rom installing !!!
Hi all,
I have a rooted redmit note 9 that was running the stock rom (EU version i believe as i am UK based) perfectly well for several months until today when then latest over the air update installed and my phone is now stuck in a bootloop where i can only access the custom PBRP recovery (installed from when i rooted previously). I can also access fastboot. I have tried wiping all data and cache etc, i have tried reflashing the magisk patched stock rom that previously worked, i have also tried flashing vbmeta that i flashed previously but still no luck. This is my only phone so I really need to get it working again.
I was about to try re-flashing the stock rom with SP tool but it tells me the scatter file is invalid.
Not sure what else to try now. I also note that when i PBRP loads up it always asks for a password however i dont have a password on the device.
Please could someone suggest something i could try?
ajadamjones87 said:
Hi all,
I have a rooted redmit note 9 that was running the stock rom (EU version i believe as i am UK based) perfectly well for several months until today when then latest over the air update installed and my phone is now stuck in a bootloop where i can only access the custom PBRP recovery (installed from when i rooted previously). I can also access fastboot. I have tried wiping all data and cache etc, i have tried reflashing the magisk patched stock rom that previously worked, i have also tried flashing vbmeta that i flashed previously but still no luck. This is my only phone so I really need to get it working again.
I was about to try re-flashing the stock rom with SP tool but it tells me the scatter file is invalid.
Not sure what else to try now. I also note that when i PBRP loads up it always asks for a password however i dont have a password on the device.
Please could someone suggest something i could try?
Click to expand...
Click to collapse
your devices is encrypted try flash other custom rom first then try revert to stock hope it help u out
Thanks very much for your response. Based on your advice i tried to flash the latest Kraken 11 Vanilla rom from this fourm, however after installing via TWRP now i can't even get into recovery anymore, just goes straight to fastboot.
Any other suggestions please?
I have now managed to get back in to TWRP and tried flashing lineage latest rom but still i am stuck in a boot loop taking me to fastboot this time.
Please can someone help suggest hwo i can get my phone working agian. At this point i dont care which rom i end up (custom or stock) with as long as i can get it to function again
If your device is rooted, you can NOT update the system using the OTA (over-the-air), or the device will be stucked in bootloop.
If your device is rooted, you need to update the system MANUALLY, using the fastboot or spflashtool.
I suggest to update the system using the fastboot.
Now, you need to flash the whole MIUI again, except userdata and you will have your device back.
For anyone with a asimilar problem i eventually managed to fix my issue by using miflash tool version 20180528 and flashing merlin_eea_global_images_V12.0.10.0.QJOEUXM_20210413.0000.00_10.0_eea_c4a9d5d7fc fastboot version which i downloaded from the xiami site.
I had to try this multiple times because the extraction of the file did not seem to be correct on the first attempts.
Hi, I got a situation here. I had to reinstall the rom in my Note 7 Pro after nearly 2 years from teh last time I had to do it.
Unfortunately, I had no idea that the new Magisk version can't be flashed by custom recoveries anymore. I simply flashed my rom using Orange Fox, restarted to the system, used the cell for 2 days, installed everything I needed, and yesterday I downloaded the latest 24310 Magisk version, flashed it using my custom recovery, and restarted in the system again.
Magisk greeted me with a message that it needed extra setup to be fully functional. I restarted in recovery, nothing happened, restarted to system, Maghisk still stuck in the need extra setup to be functional. I resolved to uninstall it using the app, got an error message in the console, tried restoring images, another error. Tried to reboot to recovery to try to reflash magisk, no more recovey, gone. Used adb to reflash recovery, rebooted to it, now I have a message that says Error opening: 'data/adb/magisk' (operation not permitted). Tried to use the Orange Fox option to remove Magisk, got some error messages Error opening: 'data/adb/magisk' (operation not permitted), but it said it was done. Tried to reboot, stuck in boot loop, back in recovery, dirty flashed my actual ROM, still stuck in boot load.
Any way to delete this locked magisk folder to try to completely remove magisk and try to reinstall it the correct way now? Or the only solution is a complete reinstallation of the ROM formatting all partitions? I haven't tried it yet because after 2 years of doing this procedure I barely remember how to do a clean install correctly.
Blackdragonbird said:
Hi, I got a situation here. I had to reinstall the rom in my Note 7 Pro after nearly 2 years from teh last time I had to do it.
Unfortunately, I had no idea that the new Magisk version can't be flashed by custom recoveries anymore. I simply flashed my rom using Orange Fox, restarted to the system, used the cell for 2 days, installed everything I needed, and yesterday I downloaded the latest 24310 Magisk version, flashed it using my custom recovery, and restarted in the system again.
Magisk greeted me with a message that it needed extra setup to be fully functional. I restarted in recovery, nothing happened, restarted to system, Maghisk still stuck in the need extra setup to be functional. I resolved to uninstall it using the app, got an error message in the console, tried restoring images, another error. Tried to reboot to recovery to try to reflash magisk, no more recovey, gone. Used adb to reflash recovery, rebooted to it, now I have a message that says Error opening: 'data/adb/magisk' (operation not permitted). Tried to use the Orange Fox option to remove Magisk, got some error messages Error opening: 'data/adb/magisk' (operation not permitted), but it said it was done. Tried to reboot, stuck in boot loop, back in recovery, dirty flashed my actual ROM, still stuck in boot load.
Any way to delete this locked magisk folder to try to completely remove magisk and try to reinstall it the correct way now? Or the only solution is a complete reinstallation of the ROM formatting all partitions? I haven't tried it yet because after 2 years of doing this procedure I barely remember how to do a clean install correctly.
Click to expand...
Click to collapse
Reflash the stock unrooted boot.img of your room in bootloader. Use adb
Fastboot flash boot boot.img
Similar problem here...
I tried reflashing stock recovery and stock boot.img - now whenever I reboot it just boots into recovery! I don't seem to be able to boot into system any more...
Any ideas?
I'm running AOSIP on a Xiami Mix Mi 3 - I hadn't updated to the latest Magisk in quite some time (since before the app could do it automatically). I have to use the recovery method.
Steps I took are:
Get recovery.zip from my ROM, patched it through the app, then flashed through fastboot. I rebooted while holding down the up arrow to reboot into recovery, then released for the phone to boot.
I got an error after booting that said "there's an internal error with your device" - and it was super buggy, couldn't tap the screen, super slow to load stuff, etc.... I figured it was a magisk issue, so tried to reflash recovery and boot... Not I'm stuck booting into recovery!
Help.
Edit: so - I think it turns out I have one of those RARE xiaomi devices that DOES have ramdisk even though the app doesn't detect it... Go figure. A clean install of the ROM, followed by patching the BOOT image rather than the recovery image - and we're up and running.