Hello,
I've been trying to post on the PitchBlack thread (it's on development forum!) and I do not have access to it. I've tried to flash the rom for more than 6 times now and can't get it to work.
I've followed the instructions exactly laid out :
1. Wiped everything (including system/cache/dalvik) and reset the phone
2. I flash the zip, it loads, I setup the phone, everything is fine.
As per the instructions we must restart the phone after going to menu>settings and then flash the settings.zip. Which I did too, but it ends up in a bootloop to me no matter how I do it. (it first says "Android is upgrading" for a second before it restarts on a boot-loop)
At my 6th try, I didn't flash the settings.zip and continued using the phone, but it restarted on its own and ended up in a boot-loop too. I've verified both files and the MD5 is correct.
I'm really out of ideas and would highly appreciate if someone could give me the right pointers here..
Regards.
Related
First post here,
So i just trying to flash my first rom, and i think i may have bricked my phone. I was using goomanager, and was attempting to flash Codename Android ROM. I have unrooted my phone, downloaded and installed the latest TWRP, backed up my phone, and then tried to flash. However, my phone has been stuck on the loading screen for about 30 minutes now (the screen with the multicolored X that comes up when powering up the phone) Nothing else is working, and im not sure what to do from here.....any suggestions?
Skootter said:
First post here,
So i just trying to flash my first rom, and i think i may have bricked my phone. I was using goomanager, and was attempting to flash Codename Android ROM. I have unrooted my phone, downloaded and installed the latest TWRP, backed up my phone, and then tried to flash. However, my phone has been stuck on the loading screen for about 30 minutes now (the screen with the multicolored X that comes up when powering up the phone) Nothing else is working, and im not sure what to do from here.....any suggestions?
Click to expand...
Click to collapse
huh..so, you ignore every other first post of the threads and install instructions, then you come in here crying that you're in a bootloop. Just reboot to recovery, wipe data/factory reset, reflash rom+gapps, done. no need to wipe caches or anything.
And go educate yourself.
http://forum.xda-developers.com/showthread.php?t=1812959 - read this, FIRST
http://forum.xda-developers.com/showthread.php?t=1626895 - read this, SECOND
Hey guys I'm new to android. I researched about rooting and I thought I'd give it a go. I followed a step by step instructions for my specific model and I originally used Odin3 1.85. I flashed it and it passed but when I booted up the phone again using power up/home/power buttons it began a system update but then it errored and gave me options to:
Reboot now
Apply update from ADB
wipe data/factory reset
Wipe cache partition
So I researched more and was told that my specific phone (Canadian Telus note 4) worked when flashed with Odin 3.07. So I downloaded that version and when I tried to flash, it got stuck at "setup processing". And now every time I try to go into download mode, it goes to recovery booting which then gives me the same options that I listed above. I don't know how to go back to the regular download mode. I tried removing the battery from a minute and putting it back in and still no luck. When I went to check if my software is up to date it gives me an error because I attempted to root my phone. So I guess since I've already gone that far I might as well root it properly. I assume I've voided my warranty already. Anyway sorry for the long explanation but like I said I'm very new to android operating systems and I'm trying to understand the termology and the whole rooting process. In short I'm not sure what to do from the recovery screen
This has been resolved!!!
I honestly can't recreate my solution other than fiddling with the system partition and after many failed attempts of stock recovery
===================
Greetings fellow modders.
For whatver the reason, I can't seem to load up the beanstalk 7 rom. I followed the directions:
Flash instructions:
Download the ROM
Download ARM64 OpenGApps for Android 7.1: Download
Push the files to your SD-Card
Reboot to TWRP
Wipe system, data, cache and ART cache
Flash the ROM
Flash the GApps
Reboot to your system
Unfortunately for me, the system gets suck at the loading screen. [BeanStalk 7]
I've went back into TWRP, restarted the instructions... same result. I have the distinct feeling that I'm doing something wrong here, and I'm too retarded to figure it out.
However, I win the golden retard award for not making a backup prior to flashing.
The bootloader confirms Unlocked and S-Off
I don't know what I'm doing wrong. I attempted to deploy a stock image, but TWRP is telling me it's corrupt. If it's relevant, I'm on a Verizon Device.
I figure the only solution is finding a path forward. Oh esteemed peers of the modding community, will you take pity?
=====
Actions taken
- 1st round as instructed; boot stalled; went into download mode then recovery mode
-2nd round; wiped then reinstalled; boot stalled; rebooted into bootloader then recovery mode;
- 3rd round; went into format data, typed yes; went into advanced wipe, selected Dalvik / ART Cache, system, cache, data, internal storage; proceeded with reinstall; boot stalled; went back to recovery mode
- 4th round same as 3rd round, just installed beanstalk; boot stalled, decided to leave it running for at least a few hours hoping it would finally load; boot still stuck; loaded into bootloader and powered off device.
- 5th round; same as 4th round, however removed SD Card during initial system boot.
- 6th round; awaiting instruction before potentially causing more damage
"Unfortunately for me, the system gets suck at the loading screen. [BeanStalk 7]"
How long does it get stuck? Did you give it a good 10 minutes without interrupting the process?
comstockload said:
"Unfortunately for me, the system gets suck at the loading screen. [BeanStalk 7]"
How long does it get stuck? Did you give it a good 10 minutes without interrupting the process?
Click to expand...
Click to collapse
I've left it running for at least an hour or so....
Has anyone else have success flashing it on marsh mellow firmware. I assume you are on that firmware
sjpritch25 said:
Has anyone else have success flashing it on marsh mellow firmware. I assume you are on that firmware
Click to expand...
Click to collapse
Yes, I was flashing from Marshmallow
Prior to flashing, I did review the ROM thread https://forum.xda-developers.com/htc-10/development/rom-beanstalk-7-t3522224 and while there were some hiccups, the majority of others was able to successfully flash (speculative from their comments on bugs etc); due to my "junior member status", I am unable to post to that thread.
Hey guys,
So I've been trying for days to get a custom Ron installed on N975F.
Right now I'm on completely reflashed stock Rom. With stock recovery et al. No root.
I am able to flash Magisk with Odin. No trouble. And my phone continues as usual without issue.
However, once I install TWRP, no matter where or how I install it, once I restart my phone it will boot past the warnings without issue, then go to the screen that just says "SAMSUNG" and the phone will never actually boot up.
I can still boot into TWRP recovery without issue, but system itself will never boot, it will just sit on the "SAMSUNG" screen forever.
In fact, it seems like as long as TWRP is installed to recovery, my system will never boot with any Rom. It can be fixed by reinstalling stock recovery, or by reflashing stock in it's entirety (which I have now done before I try again).
Has anyone got any ideas why this might be occurring or how I can address it? I saw some threads about 'rollback protection' but it seems like that is for people who are not even able to boot into TWRP, or get stuck on the first "Samsung Note 10+", screen rather than the system booting "SAMSUNG" screen.
KiwiNote+ said:
Hey guys,
So I've been trying for days to get a custom Ron installed on N975F.
Right now I'm on completely reflashed stock Rom. With stock recovery et al. No root.
I am able to flash Magisk with Odin. No trouble. And my phone continues as usual without issue.
However, once I install TWRP, no matter where or how I install it, once I restart my phone it will boot past the warnings without issue, then go to the screen that just says "SAMSUNG" and the phone will never actually boot up.
I can still boot into TWRP recovery without issue, but system itself will never boot, it will just sit on the "SAMSUNG" screen forever.
In fact, it seems like as long as TWRP is installed to recovery, my system will never boot with any Rom. It can be fixed by reinstalling stock recovery, or by reflashing stock in it's entirety (which I have now done before I try again).
Has anyone got any ideas why this might be occurring or how I can address it? I saw some threads about 'rollback protection' but it seems like that is for people who are not even able to boot into TWRP, or get stuck on the first "Samsung Note 10+", screen rather than the system booting "SAMSUNG" screen.
Click to expand...
Click to collapse
i am guessing try ADB commands see this link! https://www.koskila.net/how-to-use-twrp-to-flash-an-android-device-that-refuses-to-boot-to-twrp/
Many N975 users have reported this issue and I have forwarded concerned to ian as well. What I believe is formatting on latest (last few) twrp causing issue.
If you have N975/N976 then, visit xda My rom thread - Download area - you will find a folder "for stock rom & bootlooped device" download instructions and follow it, I have wrote guide with or without flashing my rom
Edit :
here is direct link, you will find all required file
https://www.mediafire.com/#0urfw8g1gx630
This guide is stop solution to root/root with twrp/fix Samsung roll back bootloop everything. And yes you don't needs to patch anything yourself, all files available are ready to use
Hi Dr Ketan,
Thanks for the response.
I actually solved the issue simply by using the version of TWRP and following the install instructions on your basic "How to Root and Install TWRP" for Note 10+ guide.
So I think this is a problem relating to Ian's latest TWRP. TWRP linked from your thread
is working fine (but leads to issue with Camera in GSI/Lineage OS ROMs).
I will have a look at your special guide relating to Samsung logo/rollback stuff and see if it will allow me to install latest TWRP from Ian and bypass these issues! Thank you.
KiwiNote+ said:
Hi Dr Ketan,
Thanks for the response.
I actually solved the issue simply by using the version of TWRP and following the install instructions on your basic "How to Root and Install TWRP" for Note 10+ guide.
So I think this is a problem relating to Ian's latest TWRP. TWRP linked from your thread
is working fine (but leads to issue with Camera in GSI/Lineage OS ROMs).
I will have a look at your special guide relating to Samsung logo/rollback stuff and see if it will allow me to install latest TWRP from Ian and bypass these issues! Thank you.
Click to expand...
Click to collapse
Yes, As I said issue is related to newer TWRP only. If you use old TWRP, camera will not work. My above link guide is for latest base and you can get latest TWRP only (Included package are having latest available TWRP & Kernel)
Hi all,
I'm coming back to Android after an absence and would like to run Lineage on a new US unlocked 9P. I followed the directions in the Lineage OS website and unfortunately the phone now is stuck in a constant animation of the blue circle moving left over the arc, and there isn't much I think I will be able to do about it until the battery runs out.
Here's what I did as per the directions:
-got and installed adb and fastboot from the Windows zips from Google
-added the install location to the path enviro variable
-installed the Universal ADB driver from Github
-activated USB debugging and OEM unlocking on the phone
-got the phone repeatedly into fastboot mode but then got stuck since 'fastboot devices' didn't show anything
-got bailed out by another thread here that one needs to check for updates with phone connected and Win will download the relevant USB drivers. Thanks!
-unlocked the bootloader
-downloaded and flashed the 18.1-20210803 recovery img
-sideloaded the copy-partitions 20210323 zip and it got stuck at 47% just like the website said
-did the factory reset
-sideloaded the the LOS 2020210803 zip to the phone and rebooted
When I rebooted it just plays the animation I mentioned at the beginning, so it looks like it's stuck in a permaloop.
I should mentioned that after I flashed recovery and booted into the normal Oxygen mode it would take much longer to boot so perhaps there was something already creating the loop.
I am grateful for any assistance.
Thanks,
How long have you left it? First install of Lineage spins for ages
I think I left it for an hour or so. Thanks for the info - I just turned it on and will let it spin for a while and see what happens.
I let it run until the battery died. I fully recharged it and am letting it run again. Same result of blue circle tracing arc to the left.
Success!
I tried to install the prior version (0720) which was then rejected for being too old. I wiped the storage and then tried 0803 again and it installed. I turned it on, the circle moved for a while and then the Lineage logo came up. I just finished setup, and it looks beautiful.
So far so good!
lexcimer said:
Success!
I tried to install the prior version (0720) which was then rejected for being too old. I wiped the storage and then tried 0803 again and it installed. I turned it on, the circle moved for a while and then the Lineage logo came up. I just finished setup, and it looks beautiful.
So far so good!
Click to expand...
Click to collapse
Everytime you flash a new rom you need to wipe data after
Anytime that happens you just go back into recovery and wipe data a few times and it should work after that.
It would've been due to encryption. Each time you flash a new rom you need to wipe userdata which removes your lock and also removes encryption. If you try to install a rom without doing this first, the rom cannot access that partition, because it doesn't yet know the unlock code/pattern, which is why it just gets stuck trying to do so.
Thank you to the 3 posters above, and I appreciate DJ Sub's explanation, makes sense in hindsight and I'll keep it in mind for the future.
PS - I'm glad to be back to the Android modding community, it's refreshing to be able to steer what OS my phone is running
I had the same problem (also a couple of different boot loop problems) when flashing LineageOS.
I did many things, so can't say for sure which one helped me to fix that, but the things I did were:
Restore from boot loop via MSM tool flashing EU image.
Updating that OxygeneOS to the latest using internal updater.
Repeating the LOS installation process several times in different conditions to isolate the source of the problem. I was changing LineageOS package, OpenGapps package, etc.
One of the problems I've found was that latest OpenGapps package (July 28th if I'm correct) was causing the boot loop on first start (very similar to what you're describing):
Phone tries to boot showing the LOS animation.
It goes for several minutes.
Then the phone vibrates, reboots and it continues from the start.
If I'm not mistaken, it was fixed by using the version from July 24th. The latest package also were removed from the OpenGapps page later AFAIR.
Second problem was after the successful boot. The phone was rebooting from the first setup wizard, booting to recovery (or some other partition) and proposing to make a factory reset.
Not sure which of my steps solved this, but I was updating back to the last LOS package watching closely that I'm flashing the same slot on each step and also making sure that slots are properly copied from one to another with the corresponding script.
Even in the most stable setup I was probably having some setup wizard loop problems, so I was skipping account setup steps and doing that manually later.
I'd say that installing LOS on OnePlus 9 Pro was most difficult and problematic installation in my experience and I did that a lot previously: HTC Wildfire S, THL 5000, Zuk Z1, Xiaomi Mi 5s, Xiaomi Mi 9T (Redmi K20) and several other devices.