I used PE for 3 months since January and yesterday I decided to update to the latest version.
I wiped everything in OrangeFox recovery, copied the ROM from my PC to the smartphone and then installed it.
But the system doesn't load, it just stuck on the Google loading animation. I tried Ten and Ten Plus editions, installed the latest version of OrangeFox, but it always ends up with bootloop.
Tried formatting data?
BerkiZ said:
I used PE for 3 months since January and yesterday I decided to update to the latest version.
I wiped everything in OrangeFox recovery, copied the ROM from my PC to the smartphone and then installed it.
But the system doesn't load, it just stuck on the Google loading animation. I tried Ten and Ten Plus editions, installed the latest version of OrangeFox, but it always ends up with bootloop.
Click to expand...
Click to collapse
Magisk? Uninstall.
Work? Use an older version like 19
Related
Hi all,
I was running the official Google 5.1.1 version until this morning. I now did an oem unlock using fastboot and installed the latest twrp recovery 3.0.0, and finally copied overy CM-13 nightly (and Chroma-2016-02 for testing purposes) using adb.
Flashing itself work flawless, there is no warning or error message, but when hitting "Reboot" within twrp the Google logo shows up for a few seconds and it directly boots into twrp again. This is with both, CM-13 and the latest Chroma.
So I basically cannot get my Nexus-4 bootet regulary any more.
Any ideas what the problem might be?
Any help is welcome,
regards, mistersixt.
Mmmh, strange, I did a factory installation (latest 5.1.1 from Google) and started the same thing from scratch ... and guess what... the system is booting fine now.
No idea why it did not work on my first attempt .
Regards, mistersixt.
mistersixt said:
Hi all,
I was running the official Google 5.1.1 version until this morning. I now did an oem unlock using fastboot and installed the latest twrp recovery 3.0.0, and finally copied overy CM-13 nightly (and Chroma-2016-02 for testing purposes) using adb.
Flashing itself work flawless, there is no warning or error message, but when hitting "Reboot" within twrp the Google logo shows up for a few seconds and it directly boots into twrp again. This is with both, CM-13 and the latest Chroma.
So I basically cannot get my Nexus-4 bootet regulary any more.
Any ideas what the problem might be?
Any help is welcome,
regards, mistersixt.
Click to expand...
Click to collapse
Same here. Running stock until today, wanted to see a different ROM, flashed TWRP 3.0.0, it refused to boot anything else. Tried to flash DU, then tried Chroma. Did a full wipe, then an advanced wipe selecting everything, then a full format, same thing. Installed TWRP 2.8.7, same thing. Finally installed latest stock, it is now booting, optimizing apps. I don't know if installing a custom rom will work or not yet.
Edit: Yeap, after flashing stock 5.1.1 and installing TWRP 3 again, the phone is now booting into DU.
First time I did a wipe with TWRP, it complained that it couldn't mount /data. Since this is the first time doing it, I assumed it was normal. After going through a full format, it didn't complain about data anymore, but it did complain about something to do with /dev/zero and another file under /dev/. I assume it was trying to dd /dev/zero to a file under /dev/ that didn't exist.
+1
Done the whole process from scratch again and worked like a charm
Hello, same story here.
First I:
- unlocked bootloader
- flashed TWRP (last version)
- flashed Chroma and Gapps
- reboot
=> I consistently rebooted on TWRP. No way to properly install the ROM. No error message at all.
Then I found this thread, and did as described:
- flashed the latest stock ROM
- flashed TWRP again (took me ages to manage to do this: TWRP would not install. I don't know how I finally did it, but at some point it suddenly worked. Probably a driver problem)
- flashed Chroma and Gapps again
Bingo, this time it worked! I don't know why it didn't work the first time. Could it be linked to the bootloader unlock thing?
I installed TWRP 3.1.1 using the ODIN patched version and was successful. I had let the system boot into the samsung original stock from where you see "HI" then I rebooted it into TWRP to attempt flashing and I got the /data partition couldn't be wiped. So I ran some of the other repair functions in TWRP and that appear to have fixed it. I then flashed with the latest LineageOS, Gsap, and Magistk20. When it boots up the LineageOS I'm stuck on the Lineage Splash screen. I've let it run over night and it has't changed anything. Any advice?
I recommend trying to wipe the system and reinstall LineageOS with flashing Magisk. If the same problem occurs. Just wipe the system and flash LineageOS without installing Magisk.
secretwolf98 said:
I recommend trying to wipe the system and reinstall LineageOS with flashing Magisk. If the same problem occurs. Just wipe the system and flash LineageOS without installing Magisk.
Click to expand...
Click to collapse
Here's how I think I fixed it.
booted into TWRP
advanced wipe, Factory reset
booted it into TWRP
Flashed the LineageOS
boot into LineageOS
boot it into TWRP
flashed the Gapps.
I'm up and running now. I tried different iterations and It really bothered me because it worked fine on another one. I was also at time flashing it with SuperSU and other times with Magisk. It didn't matter which one I used it got stuck on the LineageOS splash screen.
dizzymon said:
Here's how I think I fixed it.
booted into TWRP
advanced wipe, Factory reset
booted it into TWRP
Flashed the LineageOS
boot into LineageOS
boot it into TWRP
flashed the Gapps.
I'm up and running now. I tried different iterations and It really bothered me because it worked fine on another one. I was also at time flashing it with SuperSU and other times with Magisk. It didn't matter which one I used it got stuck on the LineageOS splash screen.
Click to expand...
Click to collapse
By the way, it's called the boot animation. The splash screen is like the Samsung screen that says powered by Android.
Possible corrupted file
secretwolf98 said:
By the way, it's called the boot animation. The splash screen is like the Samsung screen that says powered by Android.
Click to expand...
Click to collapse
So far you're quite correct I personally have three SM-T580's and they all seem to work just a little bit different. Might I suggest doing an MD5 Sumcheck? The device shouldn't be getting into a bootloop unless there was something wrong with the files, or the device.
Hello everyone, I'm trying to flash Havoc os 3.0 alongside with BitGaps, but it always ends up in a bootloop (I always wait one hour in the "android" boot screen). My device is the A205G with Android 10. I successfully flashed TWRP using the guide posted here in xda (also flashed magisk), then I flashed Havoc and BitGaps (wiping dalvik, cache, data and system first and then doing a factory reset), but ended up in a bootloop after rebooting to system. In a second try after reinstalling Android 10 stock rom I followed the steps shown in a youtube video (can't post link since I'm a new user) with no luck (still getting a bootloop). In a third try I just flashed the stock rom, then flashed twrp with odin and tried to flash Havoc without flashing Magisk at any moment, still bootloop. Any ideas or suggestions on what could be wrong? I've only flashed one device before with a custom rom so I'm not an expert in this area, any help will be appreciated.
Downgrade phone to Android 9, later flash twrp, then install system and Gapps.
GamingMichu said:
Downgrade phone to Android 9, later flash twrp, then install system and Gapps.
Click to expand...
Click to collapse
Thank you so much! Worked perfectly.
No problem bro. If you have problems, write to me, I will try to help.
I was using Pixel Experience Rom from the past couple of months. I wanted to check out Paranoid OS. I downloaded pa quartz 4 from the official site. I booted to my OrangeFox recovery and wiped everything. Enables MTP and copied the rom to my phone. I installed the rom zip, the logs showed, 'system image patched unconditionally' and 'vendor image patched unconditionally'.
Then everything was successful.
I rebooted my phone, and the redmi logo showed for 5 seconds and then there is only black screen!
I wiped everything again and tried, but same!!! Can anyone help me?
Nithin Sai said:
I was using Pixel Experience Rom from the past couple of months. I wanted to check out Paranoid OS. I downloaded pa quartz 4 from the official site. I booted to my OrangeFox recovery and wiped everything. Enables MTP and copied the rom to my phone. I installed the rom zip, the logs showed, 'system image patched unconditionally' and 'vendor image patched unconditionally'.
Then everything was successful.
I rebooted my phone, and the redmi logo showed for 5 seconds and then there is only black screen!
I wiped everything again and tried, but same!!! Can anyone help me?
Click to expand...
Click to collapse
You need to format /data partition
Hi, months ago I successfully installed Evolution X (juice) on my phone. Yesterday I say a new version so I've tried an update/dirty flash, unfortunately my device no longer boot to system, I can only boot to recovery or fastboot.
After some investigation it seems the latest version (uploaded on 2022-06-24 from this link this link) is based on android 12 and I was on android 11 before the update (uploaded on 2021-05-03 from the same link). I've tried to reflash the old version but no luck, the system automatically reboot to recovery. is there a way to get my phone up and running without wiping data? thanks.