So I came back to official MIUI after 1 month of using LineageOS. And I just found out that the device certification for the device was uncertified. Is it because of the bootloader being unlocked?
EDIT: Tried to reflash the phone using MiFlash, got an error due to repartitioning of the storage. Is there any way to return everything to its stock values?
You will have to first flash the stock recovery via TWRP..
Stock recovery link below:
http://en.miui.com/forum.php?mod=at...xNDE2MTA0NHw2MjM2NzEyMTl8MjU0MDg=&ck=f7e6c025
I used fastboot ROM (aroung 1GB) and flashed via MiFlash.. All worked well and now I'm again back to AICP
Related
Hi,
I've just tried and failed to install the "cm-12-20150218-NIGHTLY-nicki" ROM on my phone. Specs are:
Official Android 4.3 Firmware
Model: C1904
Timeline:
Unlocked bootloader according to instructions at http://forum.xda-developers.com/showthread.php?t=2484428
Phone then got stuck in official boot animation (the colourful one)
Didn't bother flashing the "Elixer" kernel as suggested in above thread
Used fastboot to flash the boot.img from the CM zip file
Booted to recovery
Wiped data & cache
Flashed CM & GApps from external SD card
Restarted phone
Phone showed big Android robot animation and then went back to CyanogenMod Recovery
Looking at logs showed "Cannot load volume /misc" error
Found a forum post saying this thread helped with the above error: http://forum.xda-developers.com/xperia-m/development/cwm-twrp-recoveries-cm12-lollipop-t2979752
Tried flashing TWRP recovery (http://forum.xda-developers.com/xpe...very-cwm-twrp-recoveries-custom-roms-t3016507) within CyanogenMod Recovery, but it said the file integrity was bad or something
Used "fastboot flash boot FOTAKernel.img" to flash the above, which worked
Tried to wipe data from within TWRP, but got "failed to mount /data" errors
So the phone is now in a state where:
I can only boot into TWRP
I can't use ADB since the program on the computer won't detect the phone
Fastboot still works
I can't boot into Android
Something seems wrong with "/data"
Any ideas about where to go from here?
I was able to use Flashtool to flash the official firmware back on and boot into it as normal. After doing that and restarting the procedure to install CM12 2015-02-19, this time it installed just fine.
Although I still got errors about "Cannot load volume /misc". Hopefully they don't matter...
Now you have CM12 installed and it is working?
Had the same errors when I tried to flash CM12. Flashing CM11 worked fine but I could not get CM12 to boot...
xa.fr said:
Now you have CM12 installed and it is working?
Had the same errors when I tried to flash CM12. Flashing CM11 worked fine but I could not get CM12 to boot...
Click to expand...
Click to collapse
Yeah; it's installed and working fine. When I flashed the official firmware, (Android 4.3) I told Flashtool to flash everything including the kernel. That seemed to put the phone back into a good state, which allowed me to install CM12.
I'm not sure what caused the problem in my case. Maybe it was unlocking the boot loader.
So a few days back something happened to my SD card and all of a sudden a day later after it hung, both rom and recovery got deleted. Even the SD card is wiped. I had RR 7.1 with twrp installed. I can access fastboot and tried installing the 4.3 firmware for India, but I get an error 'bundle doesn't match device' from flashtool. Even tried using xperifirm and generated a custom IN firmware, and it didn't work, same error. Currently only the default Android recovery is present on the device. Also, there's a aerror at the bottom of the recovery '/misc/ not found'.
Any clue what to do from here on?
nvm, fixed it using 2016 version of flashtool. idk how to close the thread.
So my phone has been lagging a whole lot using the stock rom and I have decided that I'll try a custom rom to see if that changes anything. So I came here and saw this forum:
"https://forum.xda-developers.com/xa1/development/half-gsi-oreo-8-1-t3902259"
I thought I'll try and so I unlocked my bootloader, only to have my phone be reset (not a problem, everything was backed up). It also boots with a warning "Device unlocked and can't be trusted".
Then I went on to download TWRP using this link in that post: "https://mega.nz/#!FQFXCYSY!DgxQRkaY1Eqq3B0fZLEQBNzUs0Zj80L6IzSHxdorQ3A" which is the TWRP 3.3.0.0 V2 IS FOR ALL USERS.
I didn't want to flash in the event it was the wrong recovery so I tried booting into it, fastboot boot recovery.img
It flashed, everything was ok and now the phone doesn't boot. It stayed in a boot loop. I went ahead and flashed recovery this time, no luck. Downloaded a recovery.img from another website and it didn't allow me to boot to android or recovery.
Is there a way to save my phone, I can't get another phone until August due to contract. It can still boot to fastboot and gets stuck when trying to boot to android. It being able to boot to fastboot makes me think theres a chance to flash a stock rom or any custom recovery and rom to get the phone working again. Any help? Thanks!
Darth343 said:
So my phone has been lagging a whole lot using the stock rom and I have decided that I'll try a custom rom to see if that changes anything. So I came here and saw this forum:
"https://forum.xda-developers.com/xa1/development/half-gsi-oreo-8-1-t3902259"
I thought I'll try and so I unlocked my bootloader, only to have my phone be reset (not a problem, everything was backed up). It also boots with a warning "Device unlocked and can't be trusted".
Then I went on to download TWRP using this link in that post: "https://mega.nz/#!FQFXCYSY!DgxQRkaY1Eqq3B0fZLEQBNzUs0Zj80L6IzSHxdorQ3A" which is the TWRP 3.3.0.0 V2 IS FOR ALL USERS.
I didn't want to flash in the event it was the wrong recovery so I tried booting into it, fastboot boot recovery.img
It flashed, everything was ok and now the phone doesn't boot. It stayed in a boot loop. I went ahead and flashed recovery this time, no luck. Downloaded a recovery.img from another website and it didn't allow me to boot to android or recovery.
Is there a way to save my phone, I can't get another phone until August due to contract. It can still boot to fastboot and gets stuck when trying to boot to android. It being able to boot to fastboot makes me think theres a chance to flash a stock rom or any custom recovery and rom to get the phone working again. Any help? Thanks!
Click to expand...
Click to collapse
OK use the boot.img and recovery.img made by @janjan HERE. Under the heading ¨Downloads¨ see ¨Xperia XA1¨ and download the KERNEL + RECOVERY the boot.img and recovery.img are compatible with the G3121-G3112-G3125-G3116-G3123 devices on the applicable firmware.
Flash BOTH using fastboot. The boot.img is patched to allow TWRP to boot which it will never do using the stock boot.
If you wish to go back to stock then simply use FlashTool to flash the stock fotakernel.sin and boot.sin contained in the firmware for your device.
Does it works becouse I boot my g3116 from flashtool camand was
Fastboot boot boot.img and then also it's stuck into bootloader
A couple months ago I once tried to install Magisk on RMX1991 by following official guide (on non-rooted phones), [Magisk 20.4, stock ROM C14, TWRP 3.3.1-19]. It failed and went into "the current image(boot/recovery) have been destroyed and cannot boot" screen, but I managed to restore to stock ROM and stock recovery. Today, I went for another attempt since new version of stock ROM and TWRP have been released [Magisk 20.4, stock ROM C17, TWRP 3.4.0], it failed and went into the same screen again.
I believed that someone must had installed Magisk on their X2 successfully, what steps did you followed to be able to achieve that?
How did you managed to restore the stock after the "the current image(boot/recovery) have been destroyed and cannot boot" screen?
AldRezaine said:
How did you managed to restore the stock after the "the current image(boot/recovery) have been destroyed and cannot boot" screen?
Click to expand...
Click to collapse
I had exactly the same issue, so I followed this guide:
https://forum.xda-developers.com/realme-x2/how-to/to-stock-rom-howto-t4014773
My phone was bootloader unlocked, with custom recovery flashed, and bootlooped. I downloaded the stock recovery image from the thread above (second post contains dl links), and flashed it using fastboot. I now lost TWRP but got the stock recovery back. I downloaded the latest original rom for my china edition RMX1991, and put it on an sd card (internal storage is also fine)
Latest RMX1991 china:
https://www.realme.com/cn/support/software-update
Latest RMX1993 EU:
https://www.realme.com/eu/support/software-update
Full original rom repo:
https://realmeupdater.com/downloads/archive/
You can't flash these with TWRP, but since we have the original recovery back in place we can now flash it. After installing the rom, do a wipe from recovery and you should be good.
After that, I started experimenting with lineageos again, and indeed confirmed that installing magisk 7.3 or 7.2 cause a bootloop, and using their magisk uninstaller makes the phone usable again.. I'm very interested if someone knows how to get magisk to run properly on the X2
Steps I followed to get root:
Unlocked bootloader
Flashed twrp
Rebooted device. (this step is important, or else you'll get stuck in bootloop)
Booted back into twrp again.
Flashed latest magisk
Reboot.
I have the Oneplus 7t. Been using the global fastboot zips to bring the phone back to stock after experimenting with custom ROMS/kernels.
This time, after flashing the msm xr rom I went back to stock using 10.0.6 global fastboot rom. everything looks good while the flash all script is running and then it reboot and sits at the bootloader screen. I cannot get past the bootloader screen. Someone please help.
I can access recovery mode and fastboot. When in fastboot I run fastboot devices and everything checks out. I run the flash all script and everything runs fine. I reboot and its stuck at the bootloader screen. What gives?
EDIT: Figured it out. I used the wrong flash script for the wrong ROM. So the incorrect rom was only flashed to one slot. I used the Resurrection Remix ROM and used the flash script for it and the ROM flash to both slots. Then I downloaded the global 10.0.6 fastboot stock rom and when I start the flash all script, it identified my filesystem instead of saying "Unknown File system type, RAW".
Now I am successfully booted back into stock ROM.