My device is SM-N976N (Korean variant of Note 10+ 5G with Exynos)
I've unlocked bootloader, disabled OEM Lock, succesfully installed latest TWRP, wiped everything it need, and tried to install latest PE+ (A13) via TWRP.
At first, it shows 'Google' and go to G logo and tiny status bar beneath. But that's it. It does not boot and just stuck at that thing.
I tried almost everything in google, XDA, or other community. I tried to use 'Format data' in TWRP, reinstall another version of TWRP, install another custom kernel, reinstall old PE (A12)
but it is not fixed at all.
Is there anyone who can help with it? I'm almost dying because of it.
---2023.03.03 Solved----
I just installed PixelOS recovery on my phone and install PE+ via PixelOS recovery. And it finally went through.
Maybe PE is not stable with TWRP in Galaxy smartphones.
DUERANG said:
My device is SM-N976N (Korean variant of Note 10+ 5G with Exynos)
I've unlocked bootloader, disabled OEM Lock, succesfully installed latest TWRP, wiped everything it need, and tried to install latest PE+ (A13) via TWRP.
At first, it shows 'Google' and go to G logo and tiny status bar beneath. But that's it. It does not boot and just stuck at that thing.
I tried almost everything in google, XDA, or other community. I tried to use 'Format data' in TWRP, reinstall another version of TWRP, install another custom kernel, reinstall old PE (A12)
but it is not fixed at all.
Is there anyone who can help with it? I'm almost dying because of it.
Click to expand...
Click to collapse
I think they're all recommend to install there rom with an AOSP-base recovery (i.e lineage recovery, pixel recovery).
Triplest said:
I think they're all recommend to install there rom with an AOSP-base recovery (i.e lineage recovery, pixel recovery).
Click to expand...
Click to collapse
I think you're right. I just installed PixelOS recovery on my phone and reinstall PE+ again. And it booted successfully. Thanks for your advice!
Ur welcome!
Developers always give an OP, which contains there owe instruction.
Try to read carefully before go with something up. Unless you know of what are you doing.
Be strong!
Related
I wiped the phone clean and tried to flash the new version of AEX But, it showed Error 7.
Tried looking for fix for Error 7 on internet, it didn't work for AEX5.6, 5.5, 5.4.
5.3 installs normally.
But felt like needed something new.
Went on the forums to find Xtended ROM. Flashed it.
After flashing it tried flashing Nano GAPPS.. Didn't work.
Tried to system reboot and thought I can later work it out.
ROM is all fine... But, later when I got to recovery mode.
(Problem begins)
I realised I lost TWRP.
And the recovery that's there wouldn't allow me to flash anything.
It looks more like CWM recovery but with less options.
It doesn't even have a advanced wipe!
Now I'm stuck with a non rooted phone, without Google bare minimum functionalities.
Am I alone? Help me out!
UKWZ7 said:
I wiped the phone clean and tried to flash the new version of AEX But, it showed Error 7.
Tried looking for fix for Error 7 on internet, it didn't work for AEX5.6, 5.5, 5.4.
5.3 installs normally.
But felt like needed something new.
Went on the forums to find Xtended ROM. Flashed it.
After flashing it tried flashing Nano GAPPS.. Didn't work.
Tried to system reboot and thought I can later work it out.
ROM is all fine... But, later when I got to recovery mode.
(Problem begins)
I realised I lost TWRP.
And the recovery that's there wouldn't allow me to flash anything.
It looks more like CWM recovery but with less options.
It doesn't even have a advanced wipe!
Now I'm stuck with a non rooted phone, without Google bare minimum functionalities.
Am I alone? Help me out!
Click to expand...
Click to collapse
For aex issue did you flash factory2vendor zip before flashing rom?
You will have to install twrp image using PC. Like the first time you did when you were unlocking bootloader
Flash zui using qfil or miflash.
If bootloader is unlocked still. You can directly flash twrp.
If not first unlock your bootloader and then flash twrp.
For treble rom like aex5.5 you need to flash factory2vendor.zip and then flash twrp with treble support.
For info on flashing and link visit aex5.5 rom page.
Hi.
I dont know where to start.
My redmi 5a had the last original software miui 11 based (android 8.1). Then I successfully unlocked the bootloader some days ago and somehow managed to install nitrogenOS (android 11 based).
Then I tried to flash another custom rom and everything went bad. I cant boot into any os anymore. I get stuck at the boot screen with the android logo and after some time it starts again and again...
I already tried to install a custom oreo recover firmware, which works, so I could start twrp again. But then every os I tried to install does not work. Fastboot works.
I am very confused now and dont know what to do next
Since you have bootloader already unlocked you can use Mi Flash (Xiaomi's own flash tool) to flash a stock ROM back to you device. This usually help, but of course, it will make you lose the custom ROM installed and the recovery.
Also, pay attention while flashing with this tool. There is an option at the bottom of the program that locks the bootloader again. If you don't want that you have to change this options every time you close the program.
OK, I started XiaomiTool V2 (on linux) and choose the option, that my device is bricked. I then have to choose my model (Redmi 5a riva) and start in fastboot. Now the tool starts to download and install the following rom to recover the smartphone:
riva_global_images_V11.0.2.0.OCKMIXM_20191106.0000.00_8.1_global_605da3d46d.tgz
But it does not work. The smartphone starts and I can see the start screen (powered by android). After some seconds there is a white screen with the words: just a sec. Then the smartphone starts again and it repeats again and again...
Nobody an idea?
sylvio2000 said:
OK, I started XiaomiTool V2 (on linux) and choose the option, that my device is bricked. I then have to choose my model (Redmi 5a riva) and start in fastboot. Now the tool starts to download and install the following rom to recover the smartphone:
riva_global_images_V11.0.2.0.OCKMIXM_20191106.0000.00_8.1_global_605da3d46d.tgz
But it does not work. The smartphone starts and I can see the start screen (powered by android). After some seconds there is a white screen with the words: just a sec. Then the smartphone starts again and it repeats again and again...
Click to expand...
Click to collapse
This has happened to me before. From the name of the image that XiaomiTool download and installed I can assume it is an more recent ROM. (since it has 2019 and 8.1 Global in it)
Do not let XiaomiTool download and install a ROM. Download a older Stock ROM yourself and make XiaomiTool install the ROM that you have download.
As I said previously. Try to download the original Stock ROM that came with your phone when you bought. BEFORE ANY official updates from Xiaomi. This have worked for me.
Hi.
Thanks It works now. I have installed the stock rom.
Is there a guide to get from stock rom (nougat) to custom rom?
sylvio2000 said:
Hi.
Thanks It works now. I have installed the stock rom.
Is there a guide to get from stock rom (nougat) to custom rom?
Click to expand...
Click to collapse
So firstly you need a recovery image (TWRP, PBRP, OF, Batik Recovery) to replace MIUI Recovery. flash it via fastboot with adb (you can do it right?).
After that reboot and push the button to recovery and remember make backup firstly or you can ignore it and yeah do it own your risk.
wipe or advanced wipe Cache, Data, System, Dalvik, Vendor.
and then install the CUSROM, and GApps.
and yeah only that to install CUSROM i know
Hello, I have a redmi note 8. I have successfully installed pitchblack recovery but it fails whenever I try to wipe data. Even when I tried installing pixel experience (it showed successful) when I would reboot it, it says no os installed. When I rebooted it, it's just stuck on a boot loop. It also wouldn't even install evo-x rom at all. I absolutely know nothing about technology so I badly need your help.
HeptapodP said:
Hello, I have a redmi note 8. I have successfully installed pitchblack recovery but it fails whenever I try to wipe data. Even when I tried installing pixel experience (it showed successful) when I would reboot it, it says no os installed. When I rebooted it, it's just stuck on a boot loop. It also wouldn't even install evo-x rom at all. I absolutely know nothing about technology so I badly need your help.
Click to expand...
Click to collapse
Install OrangeFox recovery
reboot to recovery
clean flash the rom you want
flash DFE
format data
reboot
Hi everyone, I have an HTC One M8. I wanted to root it but something went wrong and now it is stuck on the white screen with the ONE logo. I correctly unlocked the bootloader and installed twrp. I had downloaded SuperSU on my pc (flashing it with TWRP should have been the following and last step), but after I installed TWRP, before rebooting, it asked me to install SuperSU and I said yes, thinking it would save time. Now I can enter bootloader, I can enter TWRP, but that's it. I tried to install a couple of 0P6BIMG packages, but it always says that the image size is too big. Any help? Thanks.
Download stock ROM, install it from TWRP. If you get errors, try flashing through fastboot (if you can access it)
0purple said:
Download stock ROM, install it from TWRP. If you get errors, try flashing through fastboot (if you can access it)
Click to expand...
Click to collapse
I tried a few, different sizes, I don't know which one to chose, they're all 0P6BIMG, from 1,2Gb to 1,6Gb. Which one should I choose?
This is what TWRP gave me when I tried to install Lineage OS. Also, can you provide a link for the custom rom since all those I tried didn't work?
I`m sorry, I won`t be able to help here. Try researching
Solved. If it can be of any help, apparently the twrp was corrupted and couldn't flash any rom. I changed twrp (3.5) and flashed lineage 17.1. All fine, just keep in mind lineage 17.1 is not friend with Magisk 20.4, but gets along well with 20.3.
Hello,
Just after unlocked the bootloader, I flashed Orange Fox recovery and tried to install the last Pixel Experience, but I was stuck on boot animation.
Same for previous Pixel Experience rom.
Then, I tried LineageOS 19.1, and successfully booter on it. But, I got screen that said "Your data may be corrupter" and can't do anything but reboot into recovery.
I'm out of option, now... Did I forgot something ?
PS: I also tried to flash Chikori Kernel but I got error "New image is larger than targeted partition"
shim80 said:
Hello,
Just after unlocked the bootloader, I flashed Orange Fox recovery and tried to install the last Pixel Experience, but I was stuck on boot animation.
Same for previous Pixel Experience rom.
Then, I tried LineageOS 19.1, and successfully booter on it. But, I got screen that said "Your data may be corrupter" and can't do anything but reboot into recovery.
I'm out of option, now... Did I forgot something ?
PS: I also tried to flash Chikori Kernel but I got error "New image is larger than targeted partition"
Click to expand...
Click to collapse
Try to flash V12.5.3.0.QFLCNXM with Twrp/O.f (TWRP is newer than this OF.)
then
reboot Twrp/O.F
Wipe/format data type yes
reboot Twrp/O.F
Flash rom
Sometimes the flashing of the recovery ROM does not work with the Twrp/O.F in this case use Miflash with a fastboot rom.
If you're still trying to figure this one out, I think I know how to solve your issue installing LOS.
You most likely used TWRP v3.70, am I right?
You should use TWRP v3.61 coz that was the last stable version that worked, the only thing is that you might need to find another custom recovery other than the official TWRP after installing an Android 12 custom ROM like LOS 19.1.
Lineage OS has their own recovery so you'd probably need to use that if you want to update it.
Same issue with me. yesterday. Though mine is fixed.
My workaround was: I installed the official 12.5.3 MIUI using OrangeFox. After boot, I tried installing PixelExperience using Pixel recovery. There I got successfully installed a custom ROM. Alhough I am not sure if the mounting/encryption of Internal SD is the cause.