Related
My friend gave me his Nexus 4 to fix, for some unknown reason it does not boot. It earlier worked fine and was running Stock 5.1.
So I tried to fix it by loading the latest Factory Image from Google's website. I downloaded the latest build. extracted it, and followed the instructions given on their website. I was able to successfully install the OS by using the Flash-All script. The phone rebooted once the flashing process got over.
But the phone never booted, it got stuck on the circles flying around boot animation. I did the entire process again and waited for 45 minutes but it still did not boot. I went in the Stock Recovery and wiped the Cache and did a factory reset and still the same. I even tried locking and unlocking the bootloader again but still no result.
After doing all this I decided to install CyanogenMod 12.1 Snapshot, so I downloaded the latest version of TWRP and installed it. Booted into TWRP.
Wiped Dalvik, Cache, Data and System. Flashed the ROM, the ROM installed successfully. But now even CM12.1 won't boot!
How am I supposed to make this phone boot?
Please help me.
Thanks in Advanced.
Same problem
cyborgmanu said:
My friend gave me his Nexus 4 to fix, for some unknown reason it does not boot. It earlier worked fine and was running Stock 5.1.
So I tried to fix it by loading the latest Factory Image from Google's website. I downloaded the latest build. extracted it, and followed the instructions given on their website. I was able to successfully install the OS by using the Flash-All script. The phone rebooted once the flashing process got over.
But the phone never booted, it got stuck on the circles flying around boot animation. I did the entire process again and waited for 45 minutes but it still did not boot. I went in the Stock Recovery and wiped the Cache and did a factory reset and still the same. I even tried locking and unlocking the bootloader again but still no result.
After doing all this I decided to install CyanogenMod 12.1 Snapshot, so I downloaded the latest version of TWRP and installed it. Booted into TWRP.
Wiped Dalvik, Cache, Data and System. Flashed the ROM, the ROM installed successfully. But now even CM12.1 won't boot!
How am I supposed to make this phone boot?
Please help me.
Thanks in Advanced.
Click to expand...
Click to collapse
I have the same problem, and I am trying to download factory 4.4.4 image.
guys help us plz.
mose_nd said:
I have the same problem, and I am trying to download factory 4.4.4 image.
guys help us plz.
Click to expand...
Click to collapse
I also posted this is the Nexus 4 Community on Google Plus. I am going to try out what they said.
Here is the link:
https://plus.google.com/117172821556811787798/posts/dzVorg3JSUw
SOLVED!
mose_nd said:
I have the same problem, and I am trying to download factory 4.4.4 image.
guys help us plz.
Click to expand...
Click to collapse
Hey I fixed it! It finally booted up.
You need to use the first Factory Image, that is, the Android 4.2.2 Jelly Bean Factory Image.
Once you have flashed the image, the phone will boot up quickly - Mine booted in around 5 minutes I guess.
Here is the link - https://dl.google.com/dl/android/aosp/occam-jdq39-factory-345dc199.tgz
Hi,
I have a rooted OP5, running 5.1.7 and TWRP. I used Oxygen Updater to download the new android 9 ROM. I tried to install via TWRP, but got an error about zip compatability & a treble problem. I found a thread stating that I needed a newer TWRP to fix the treble problem, so I installed TWRP_3.2.3-Pie_siankatabg_OP5 , which said it had Pie support, from here:
https://androidfilehost.com/?fid=1322778262903996029
That worked fine, but when I tried to flash the 9 ROM, I got still got the same error. Another post said to remove compatibility.zip from the ROM zip. I did that, and it now installed, but it wouldn't boot. Re-flashing 5.1.7 booted fine. I tried another TWRP - twrp-3.2.3-0-20181227-codeworkx-nocompatcheck-cheeseburger from here:
https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
That installs, and boots to system, but won't boot to recovery, so I can't install the 9 ROM.
Any ideas where I go from here to upgrade to 9?
Thanks!
richstant said:
Hi,
I have a rooted OP5, running 5.1.7 and TWRP. I used Oxygen Updater to download the new android 9 ROM. I tried to install via TWRP, but got an error about zip compatability & a treble problem. I found a thread stating that I needed a newer TWRP to fix the treble problem, so I installed TWRP_3.2.3-Pie_siankatabg_OP5 , which said it had Pie support, from here:
https://androidfilehost.com/?fid=1322778262903996029
That worked fine, but when I tried to flash the 9 ROM, I got still got the same error. Another post said to remove compatibility.zip from the ROM zip. I did that, and it now installed, but it wouldn't boot. Re-flashing 5.1.7 booted fine. I tried another TWRP - twrp-3.2.3-0-20181227-codeworkx-nocompatcheck-cheeseburger from here:
https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
That installs, and boots to system, but won't boot to recovery, so I can't install the 9 ROM.
Any ideas where I go from here to upgrade to 9?
Thanks!
Click to expand...
Click to collapse
Hi, I got Pie to install with TWRP_3.2.3-Pie_siankatabg_OP5 on my device.
Go to this link:
https://forum.xda-developers.com/showpost.php?p=78523940&postcount=13
And follow my post on the part where it says:
" Notes for the Pie update: "
Let us know if those steps work for you. The firmware is linked to on there, pre-modified. Try flashing that pre-modified zip and see if your device boots.
richstant said:
Hi,
I have a rooted OP5, running 5.1.7 and TWRP. I used Oxygen Updater to download the new android 9 ROM. I tried to install via TWRP, but got an error about zip compatability & a treble problem. I found a thread stating that I needed a newer TWRP to fix the treble problem, so I installed TWRP_3.2.3-Pie_siankatabg_OP5 , which said it had Pie support, from here:
https://androidfilehost.com/?fid=1322778262903996029
That worked fine, but when I tried to flash the 9 ROM, I got still got the same error. Another post said to remove compatibility.zip from the ROM zip. I did that, and it now installed, but it wouldn't boot. Re-flashing 5.1.7 booted fine. I tried another TWRP - twrp-3.2.3-0-20181227-codeworkx-nocompatcheck-cheeseburger from here:
https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
That installs, and boots to system, but won't boot to recovery, so I can't install the 9 ROM.
Any ideas where I go from here to upgrade to 9?
Thanks!
Click to expand...
Click to collapse
It sounds like you did not follow the detailed flashing instructions in the first post here: https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Is your device storage encrypted or decrypted? Have you flashed magisk? Have you used an older magisk(your end link leads to my post where I mention that)? Have you downloaded the rom file without compatibility.zip or did you removed it on your own?
strongst said:
It sounds like you did not follow the detailed flashing instructions in the first post here: https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Is your device storage encrypted or decrypted? Have you flashed magisk? Have you used an older magisk(your end link leads to my post where I mention that)? Have you downloaded the rom file without compatibility.zip or did you removed it on your own?
Click to expand...
Click to collapse
Thanks for the links both, but still no go. I was on Magisck 17.1, uninstalled Magisk with the latest uninstaller, flashed the ROM with compatability.zip already removed. Same result as before - I get the oneplus logo, then it just reboots instead of starting the system. I've only wiped cache & dalvik, I don't really want to wipe more than that if I can help it - it is worth trying a system/vendor/data wipe? I recovered by flashing back to 5.1.7 (also updated to Magisk 18 while I was at it).
Any more ideas? One thing I find a little weird is that I'm on the @siankatabg TWRP, when I tried either the bluespark & codeworx TWPR, I couldn't get into recovery with either, I just got a blank screen with a LED staying on light blue. Only the siankatabg recovery works. Surely any of them should work? Does this point to a problem?
I'm not sure what you mean by encrypted or not - I get messages about unencrypting when going into recovery, which I assume means I am encrypted?
THanks!
richstant said:
Thanks for the links both, but still no go. I was on Magisck 17.1, uninstalled Magisk with the latest uninstaller, flashed the ROM with compatability.zip already removed. Same result as before - I get the oneplus logo, then it just reboots instead of starting the system. I've only wiped cache & dalvik, I don't really want to wipe more than that if I can help it - it is worth trying a system/vendor/data wipe? I recovered by flashing back to 5.1.7 (also updated to Magisk 18 while I was at it).
Any more ideas? One thing I find a little weird is that I'm on the @siankatabg TWRP, when I tried either the bluespark & codeworx TWPR, I couldn't get into recovery with either, I just got a blank screen with a LED staying on light blue. Only the siankatabg recovery works. Surely any of them should work? Does this point to a problem?
I'm not sure what you mean by encrypted or not - I get messages about unencrypting when going into recovery, which I assume means I am encrypted?
THanks!
Click to expand...
Click to collapse
Maybe try backing your device up, and then locking the bootloader. Try updating with stock recovery on a locked bootloader. If that works, you can then unlock the bootloader and copy your data back
richstant said:
Thanks for the links both, but still no go. I was on Magisck 17.1, uninstalled Magisk with the latest uninstaller, flashed the ROM with compatability.zip already removed. Same result as before - I get the oneplus logo, then it just reboots instead of starting the system. I've only wiped cache & dalvik, I don't really want to wipe more than that if I can help it - it is worth trying a system/vendor/data wipe? I recovered by flashing back to 5.1.7 (also updated to Magisk 18 while I was at it).
Any more ideas? One thing I find a little weird is that I'm on the @siankatabg TWRP, when I tried either the bluespark & codeworx TWPR, I couldn't get into recovery with either, I just got a blank screen with a LED staying on light blue. Only the siankatabg recovery works. Surely any of them should work? Does this point to a problem?
I'm not sure what you mean by encrypted or not - I get messages about unencrypting when going into recovery, which I assume means I am encrypted?
THanks!
Click to expand...
Click to collapse
Please use an older recovery like twrp-3.2.3-0-20181031-codeworkx-cheeseburger.img the actual pie recoveries require pie firmware(mentioned in last post of blue spark thread for example).
strongst said:
Please use an older recovery like twrp-3.2.3-0-20181031-codeworkx-cheeseburger.img the actual pie recoveries require pie firmware(mentioned in last post of blue spark thread for example).
Click to expand...
Click to collapse
OK, I understand now - if I use an older TWRP, or the siankatabg version, it works fine. I can then flash the Pie ROM, however it still won't boot - I get the oneplus logo, then it just reboots. However having done the Pie flash, I can then flash the more recent TWRPs (codeworx or Bluespark), and can now get into recovery fine. However Pie still won't boot - I've even tried re-flashing the Pie ROM from within the newer TWRPs, but the result is the same - it gets to the oneplus logo, then reboots. At this stage I guess wiping system/vendor/data is the only way forwards?
*Edit* - OK, so wiping everything fixed the issue, I'm now on Pie. Flashing Magisk didn't work when flashing the ROM, but I'll try again once it's finished downloading all my apps etc.
Firstly, my phone isn't hard-bricked. I'm able to load different versions of the TWRP recovery and access Fastboot without any problems. I'm also pretty comfortable using adb to push, sideload, access fastboot, recovery , etc. so please feel free to throw out any suggestions that might help me resolve my issue. (Note:I'm unable to find the stock recovery on OnePlus's support page anymore, I recall they always had the option to download the stock recovery just below the download option for the stock ROM, so I haven't been able to try sideloading after formatting with the stock recovery.)
My OnePlus 5 was running stock Oreo and I'd been meaning to upgrade to Lineage 16.0 (Pie) or any other Pie ROM really. I booted into TWRP (3.2.3-0 - Oreo firmware) and wiped everything other than USB storage and formatted data too as my previous Oreo installation was encrypted. Then, I downloaded codeworkxx's 9.0.3 firmware for OnePlus 5 and pushed it to my phone using adb. I flashed the firmware successfully, rebooted into Bootloader/fastboot; and flashed the Android Pie version of TWRP recovery ( https://sourceforge.net/projects/cheeseburgerdumplings/files/16.0/cheeseburger/ ) and was able to successfully boot back into the recovery. Since then, I've tried to flash multiple different Pie ROMs (Pixel Experience, Lineage 16.0, stock OOS official build - 9.0.3 , Beta OOS build OpenBeta26) (clean flashing always) but always ended up with a bootloop with the boot animations in all the ROMs. I've even tried flashing them with Magisk-v18.0 but that doesn't help either. I've waited for 15 min with each boot for the different ROM's (ending up in bootloops) and on rebooting back to TWRP, I've always found that irrespective of ROMs, the only folder that's created in Internal Storage is 'obb' and it is an empty folder. I've even tried sideloading OOS 9.0.3 (official build) via TWRP and that still ends up in a bootloop with the obb folder in Internal Storage being the only thing created. Also, flashing the boot.img recovery in the stock ROM zip files leads to a blank screen with a white LED that tries to install Qualcom drivers, so I just reflashed TWRP and am back to where I started.
That pretty much sums up my problem here. Kindly throw suggestions at me to help fix my problem' I've searched the forums but most of the bootloop issues I've found and read are about unsuccessful firmware flashes (not the case with me as I've explained above) or dirty flashes (again, not the case with me as I always cleanflash).
Thanks!
You should be focusing on getting stock OOS back on before trying custom rom. Have you tried rolling back to 5.1.7 Oreo? Sometime it better to go back to square 1 and try again.
Z-Blade said:
You should be focusing on getting stock OOS back on before trying custom rom. Have you tried rolling back to 5.1.7 Oreo? Sometime it better to go back to square 1 and try again.
Click to expand...
Click to collapse
Thank you for replying!
I successfully flashed the 5.1.7 firmware and Oreo-TWRP-recovery and was able to install Lineage OS 15.1 and boot it up properly. I'm unable to find a link for previous versions of OOS to test whether or not 5.1.7 would work. Do you know where I can find a link?
Thanks again!
BigTurboSkipper said:
Thank you for replying!
I successfully flashed the 5.1.7 firmware and Oreo-TWRP-recovery and was able to install Lineage OS 15.1 and boot it up properly. I'm unable to find a link for previous versions of OOS to test whether or not 5.1.7 would work. Do you know where I can find a link?
Thanks again!
Click to expand...
Click to collapse
It's within the guides section https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-mirrors-official-oxygen-os-t3628190
strongst said:
It's within the guides section https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-mirrors-official-oxygen-os-t3628190
Click to expand...
Click to collapse
Thanks!
So the Lineage 15.1 flash worked fine but OOS 5.1.7 still leaves me with a bootloop and the obb folder as detailed in my first post. I'm unsure as to how to proceed.
BigTurboSkipper said:
Thanks!
So the Lineage 15.1 flash worked fine but OOS 5.1.7 still leaves me with a bootloop and the obb folder as detailed in my first post. I'm unsure as to how to proceed.
Click to expand...
Click to collapse
What was your LAST stock oxygenOS version that was installed your device prior to 5.1.7?
strongst said:
What was your LAST stock oxygenOS version that was installed your device prior to 5.1.7?
Click to expand...
Click to collapse
I can't recall exactly, but it was most probably OB23/24 (Oreo)
BigTurboSkipper said:
I can't recall exactly, but it was most probably OB23/24 (Oreo)
Click to expand...
Click to collapse
Can you please try to flash 5.1.4 stock oxygenOS rom and the 5.1.7 after it, then magisk and reboot to the os?
Make sure you have an old Oreo compatible recovery like this https://drive.google.com/file/d/1DrEMydZfQxC_eWx1W-OlASo8H7okXNTQ/view?usp=drivesdk
strongst said:
Can you please try to flash 5.1.4 stock oxygenOS rom and the 5.1.7 after it, then magisk and reboot to the os?
Make sure you have an old Oreo compatible recovery like this https://drive.google.com/file/d/1DrEMydZfQxC_eWx1W-OlASo8H7okXNTQ/view?usp=drivesdk
Click to expand...
Click to collapse
Successfully flashed but still results in a bootloop
BigTurboSkipper said:
Thanks!
So the Lineage 15.1 flash worked fine but OOS 5.1.7 still leaves me with a bootloop and the obb folder as detailed in my first post. I'm unsure as to how to proceed.
Click to expand...
Click to collapse
Lineage 15.1 (official) boots successfully but without radios working... I tried reflashing Firmware-5.1.7 but that does not help; not sure how to fix this. Could it be a firmware issue with installing Pie ROMs? But then again, OOS Oreo doesn't boot either - still ends up in a bootloop
My only suggestion ...
BigTurboSkipper said:
Lineage 15.1 (official) boots successfully but without radios working... I tried reflashing Firmware-5.1.7 but that does not help; not sure how to fix this. Could it be a firmware issue with installing Pie ROMs? But then again, OOS Oreo doesn't boot either - still ends up in a bootloop
Click to expand...
Click to collapse
Greetings! I got your private message, but I haven't read it yet. Sorry, very busy today. However, I can make the following suggestion to get your device back into original working order.
Have a look at this link on xda. It's for an unbrick tool, which I've used numerous times with great success.
https://forum.xda-developers.com/oneplus-5/how-to/unbrick-tool-oneplus-5-t3648169
This tool will put your device back into its original condition, with original OOS.
Let me know if it works for you.
Peter
BigTurboSkipper said:
Lineage 15.1 (official) boots successfully but without radios working... I tried reflashing Firmware-5.1.7 but that does not help; not sure how to fix this. Could it be a firmware issue with installing Pie ROMs? But then again, OOS Oreo doesn't boot either - still ends up in a bootloop
Click to expand...
Click to collapse
OxygenOS also needs a formatted internal storage, otherwise bootloop will pop up
strongst said:
OxygenOS also needs a formatted internal storage, otherwise bootloop will pop up
Click to expand...
Click to collapse
Definitely! I've always been clean flashing ROMs (Wiping Internal Storage, Data, System, Dalvik Cache, Cache + Wiping/Formatting Data to factory reset ) for each trial!
BigTurboSkipper said:
Definitely! I've always been clean flashing ROMs (Wiping Internal Storage, Data, System, Dalvik Cache, Cache + Wiping/Formatting Data to factory reset ) for each trial!
Click to expand...
Click to collapse
Wiping system, data, cache, Installing 5.1.4, then magisk, then format internal storage, then boot os should not cause a bootloop
What's your twrp recovery? Did you tried mine?
strongst said:
Wiping system, data, cache, Installing 5.1.4, then magisk, then format internal storage, then boot os should not cause a bootloop
What's your twrp recovery? Did you tried mine?
Click to expand...
Click to collapse
That's exactly what I'm doing. I've tried using codeworkxx 's versions, blu_spark TWRP versions and yours too!
PeterGuru said:
Greetings! I got your private message, but I haven't read it yet. Sorry, very busy today. However, I can make the following suggestion to get your device back into original working order.
Have a look at this link on xda. It's for an unbrick tool, which I've used numerous times with great success.
https://forum.xda-developers.com/oneplus-5/how-to/unbrick-tool-oneplus-5-t3648169
This tool will put your device back into its original condition, with original OOS.
Let me know if it works for you.
Peter
Click to expand...
Click to collapse
Thank you for replying!
The tool doesn't detect my device whatsoever - I have system-wide adb & fastboot set up (to use from any folder or path) yet the device is not detected in fastboot mode or recovery mode.
How do you use it?
Thanks!
BigTurboSkipper said:
Thank you for replying!
The tool doesn't detect my device whatsoever - I have system-wide adb & fastboot set up (to use from any folder or path) yet the device is not detected in fastboot mode or recovery mode.
How do you use it?
Thanks!
Click to expand...
Click to collapse
You need to put your device into MSM Download mode. It's simple. Power off your device. Press and hold the Volume UP key for about 8-10 seconds and, while continuing to hold the Volume UP key, plug in your device to your computer via USB. Open the MSM Tool and press Start.
That's it.
It takes about 3-5 minutes for the tool to complete the unbrick process.
Peter
Thank you! I was able to successfully use the unbrick tool to reset to OOS 4.5.8 Nougat. I'm going to try stepping all the way up to Pie now!
I seem to have hard bricked my 9T after flashing the MIUI 11 rom from xiaomi.eu. I think culprit is a totally botched/corrupted boot loader and I have no idea how it happened. I've tried reflashing back to stock through stock image .bat files, but no dice. It flashed everything but the device still refuses to boot past the MI screen. If I try to boot into TWRP, my device gets stuck at the TWRP splash screen, no matter which version it is. Does anyone know what I can do or try at this point? Thanks.
So do I, first time I successfully instal first beta v25 miui 11, and than when the v26 comes, stupidly, i flash it from twrp, it tells me that i succeed installing that zip, and than i wipe art and cache and reboot system, but what next i know, my phone brick, i can not instal anyrom, from mi flash tool, or from anywhere. I did everything and still can not fix the problem.
Anyway, you still can enterin TWRP UI, after waiting about 10 to 30 minutes, because after intalling that rom, automatically your data format change from ext4 to f2fs, and twrp will need a lot of time to read your disk.
But, even after doing anything in twrp, still can not make my phone successfully boot into system.
And theres moun I/O error everytime i tried to wipe everything, or fix disk, or change disk format. Everything... and i just dont know what to do anymore.
So may be you can wait patiently until you can entering twrp ui, and please lemme know if you know how to fix this problem
Soapy! said:
I seem to have hard bricked my 9T after flashing the MIUI 11 rom from xiaomi.eu. I think culprit is a totally botched/corrupted boot loader and I have no idea how it happened. I've tried reflashing back to stock through stock image .bat files, but no dice. It flashed everything but the device still refuses to boot past the MI screen. If I try to boot into TWRP, my device gets stuck at the TWRP splash screen, no matter which version it is. Does anyone know what I can do or try at this point? Thanks.
Click to expand...
Click to collapse
i have experience that, then i flash the twrp chinese version and it works.
@flamedrops which one if i may know? I tried 3.3.1-0916-redmi_k20-CN and still not work ?
Soapy! said:
I seem to have hard bricked my 9T after flashing the MIUI 11 rom from xiaomi.eu. I think culprit is a totally botched/corrupted boot loader and I have no idea how it happened. I've tried reflashing back to stock through stock image .bat files, but no dice. It flashed everything but the device still refuses to boot past the MI screen. If I try to boot into TWRP, my device gets stuck at the TWRP splash screen, no matter which version it is. Does anyone know what I can do or try at this point? Thanks.
Click to expand...
Click to collapse
I got exactly the same problem after installing miui 11rom. Installing firmware via fastboot was unsuccessful. God, help us ...
---------- Post added at 07:44 AM ---------- Previous post was at 07:33 AM ----------
Arif Ferdian said:
So do I, first time I successfully instal first beta v25 miui 11, and than when the v26 comes, stupidly, i flash it from twrp, it tells me that i succeed installing that zip, and than i wipe art and cache and reboot system, but what next i know, my phone brick, i can not instal anyrom, from mi flash tool, or from anywhere. I did everything and still can not fix the problem.
Anyway, you still can enterin TWRP UI, after waiting about 10 to 30 minutes, because after intalling that rom, automatically your data format change from ext4 to f2fs, and twrp will need a lot of time to read your disk.
But, even after doing anything in twrp, still can not make my phone successfully boot into system.
And theres moun I/O error everytime i tried to wipe everything, or fix disk, or change disk format. Everything... and i just dont know what to do anymore.
So may be you can wait patiently until you can entering twrp ui, and please lemme know if you know how to fix this problem
Click to expand...
Click to collapse
Just the exact same problem as mine. If you know anything about how to solve this problem, please tell us.
I had the same problem with a miui 10 weekly beta but unfortunately I wasn't able to fix it but lucky me my phone was still in a return period so I returned it back to Amazon and got my money back since then I have always stayed away from beta ROMs . I tried everything but it wasn't booting pass the mi logo as you said
flamedrops said:
i have experience that, then i flash the twrp chinese version and it works.
Click to expand...
Click to collapse
Benfatica said:
I had the same problem with a miui 10 weekly beta but unfortunately I wasn't able to fix it but lucky me my phone was still in a return period so I returned it back to Amazon and got my money back since then I have always stayed away from beta ROMs . I tried everything but it wasn't booting pass the mi logo as you said
Click to expand...
Click to collapse
Ahhhh yes, i was thinking to using my guaranteed card, as i still can relock bootliader with mi flash tools, already trying anything for couples day with zero result, and im giving up hahaha
Arif Ferdian said:
Ahhhh yes, i was thinking to using my guaranteed card, as i still can relock bootliader with mi flash tools, already trying anything for couples day with zero result, and im giving up hahaha
Click to expand...
Click to collapse
did you really reboot it using adb reboot twrp? and reboot system on twrp using twrp cn version?
Yap @flamedrops i already do, and even tried all the TWRP version that exist, and also reflash many Rom, from stock, eu, ct, aosp, miui 11 25, miui 11 26, i flash from adb sideload, from twrp via usb otg, via miflash tool,
I flash boot.img, etc
Still no result.
Already tried everything that i could thinking about
flamedrops said:
did you really reboot it using adb reboot twrp? and reboot system on twrp using twrp cn version?
Click to expand...
Click to collapse
This LR. TEAM is twrp cn version right? And in fact, this version hardly booting to twrp ui version after this problem, easier to entering twrp ui with the ugly themed greek version
Arif Ferdian said:
This LR. TEAM is twrp cn version right? And in fact, this version hardly booting to twrp ui version after this problem, easier to entering twrp ui with the ugly themed greek version
Click to expand...
Click to collapse
ok, yes thats it. have you tried to flash magisk?
@flamedrops not yet, i never tried to flash magisk yet, ill tried next time i could pass twrp splash screen
flamedrops said:
i have experience that, then i flash the twrp chinese version and it works.
Click to expand...
Click to collapse
Can you list your steps to fix this? My data and cache partitions are 0kb and i get i/o errors too.
I have persist problems after installing muiu 11 over the los16.
Thinking about relock it and sens it back to aliexpress seller.
@mvha just go into fastboot mode, and flash persist.img from stock fastboot rom,
With command : fastboot flash persist persist.img
Thats all
Arif Ferdian said:
So do I, first time I successfully instal first beta v25 miui 11, and than when the v26 comes, stupidly, i flash it from twrp, it tells me that i succeed installing that zip, and than i wipe art and cache and reboot system, but what next i know, my phone brick, i can not instal anyrom, from mi flash tool, or from anywhere. I did everything and still can not fix the problem.
Anyway, you still can enterin TWRP UI, after waiting about 10 to 30 minutes, because after intalling that rom, automatically your data format change from ext4 to f2fs, and twrp will need a lot of time to read your disk.
But, even after doing anything in twrp, still can not make my phone successfully boot into system.
And theres moun I/O error everytime i tried to wipe everything, or fix disk, or change disk format. Everything... and i just dont know what to do anymore.
So may be you can wait patiently until you can entering twrp ui, and please lemme know if you know how to fix this problem
Click to expand...
Click to collapse
This makes sense as I remember trying to boot into stock recovery early in the morning. I woke up and it finally booted, but the recovery was in Chinese. I will give 4PDA TWRP about an hour and see what I can do. Thanks.
Soapy! said:
This makes sense as I remember trying to boot into stock recovery early in the morning. I woke up and it finally booted, but the recovery was in Chinese. I will give 4PDA TWRP about an hour and see what I can do. Thanks.
Click to expand...
Click to collapse
If you can not use 4pda, i suggest u to use greek one, thats twrp version the must successfully booting in my experiences
I am thankful that I saw this before updating to newest miui 11
flamedrops said:
ok, yes thats it. have you tried to flash magisk?
Click to expand...
Click to collapse
Can not flash magisk, etc hahahhahaa
Arif Ferdian said:
If you can not use 4pda, i suggest u to use greek one, thats twrp version the must successfully booting in my experiences
Click to expand...
Click to collapse
After you used the Greek twrp did you manage to solve the problem?
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.