I was running Eternity version 116 for a long time, and decided i should upgrade to a more recent rev. I tried flashing v236 (and 238 and various versions in between) and all appears to go well, I get a message for successfully installing, but on first reboot, I get stuck on the splash screen. While I haven't tried many ROMs, I always wipe first. I am currently running Bamf Forever. But for whatever reason, I just can't get Eternity to load. Any suggestions? Thanks!
If you wiped data first and didn't get a bad download (if you've tried multiple versions, that would be very unlikely) then there really wouldn't be a logical reason for it not to work. All I can tell you is that it takes a long time (5 minutes maybe) to boot up the first time you flash a new ROM, I think it's because it zipaligns your apps. Hope you figure it out, if you find out what the problem was, let me know.
I've let it boot up for hours, but it never gets past the splash screen.
are you wiping data/cache/dalvik
Bigandrewgold said:
are you wiping data/cache/dalvik
Click to expand...
Click to collapse
Yes, wiping everything. I don't seem to have a problem installing other ROMs, just Eternity.
disregard. i got 216 to work. i don't know wtf was going on. but i'm happy now.
Glad you got it working. There have been some significant changes since 216 that makes it worth your time to upgrade to R238.
I figured out what the problem was. turns out all i needed to do was update CWM. now all versions flash fine. I was using a 3.0 version of CWM.
(delete)
Dougmeister said:
I had Android 4.1.1 installed on a rooted Sprint Galaxy S3 with ClockworkMod. Someone recommended TWRP, so I installed it and used the backup feature, thinking I was completely covered if my foray into ROM flashing on the SGS3 went awry.
So I booted to TWRP, did a "Wipe Data/Factory Reset", and installed the "Blazer" ROM; didn't like it. So I TWRP'ed again, wiped it and flashed CyanogenMod 10.1. Didn't like it either. So I went back into TWRP, did the "Wipe Data/Factory Reset" again, and restored my backup.
When it finished rebooting, it was good for like 20 seconds. I left it on the "lock" screen, and the date reverted back to Dec 24th at some ungodly hour (4 am?). It wouldn't unlock. After less than a minute, it reboots. It kept doing this.
I had a hard time getting back *into* TWRP. I kept getting this weird picture of the battery (?) and the phone kept buzzing every 10 seconds or so. The battery had at least 30% charge. Eventually, by taking the battery out, I was able to get back into TWRP.
Tried it again 2 or 3 more times with the same result. This last time, I immediately got off the lock screen and let it "sit". It has been stable (no lockups or reboots) for a few minutes now.
Any idea what's going on?
(If I'm leaving out important information, I apologize. Please let me know and I'll add it.)
Click to expand...
Click to collapse
Sprint ??? this is I9300 forum .
jje
I'm using the up-to-date version of TWRP 2.5.0.2. I followed the instructions to flash Hyperdrive exactly (3x wipes, wipes, install, rebooting, etc). My phone works after the first reboot, but after I reboot the second time after 10 minutes my phone consistently bootloops every time after that. Does anyone have any idea what's going on?
I'm running the RLS3 right now because I was tired of being afraid to reboot my phone lol. It's pretty stable, the only problem is that I find I can't make a nandroid backup- the data partition is ludicrously large at 2 TB, and I can't figure out why.
Anyone have any ideas? Thank you!
sup0man said:
I'm using the up-to-date version of TWRP 2.5.0.2. I followed the instructions to flash Hyperdrive exactly (3x wipes, wipes, install, rebooting, etc). My phone works after the first reboot, but after I reboot the second time after 10 minutes my phone consistently bootloops every time after that. Does anyone have any idea what's going on?
I'm running the RLS3 right now because I was tired of being afraid to reboot my phone lol. It's pretty stable, the only problem is that I find I can't make a nandroid backup- the data partition is ludicrously large at 2 TB, and I can't figure out why.
Anyone have any ideas? Thank you!
Click to expand...
Click to collapse
You can try and switch the kernel and see if the problem still there. I would go with KT Kernel http://forum.xda-developers.com/showthread.php?t=2294083
make sure you use the touchwiz based kernel.
Problem occur in stock fw(3.2.4), Nexus 2.01 and even after rollback to .3.1.0
My HDX when lying on the table goes on and off every minute(clock resets to 0:00 after each reboot), but when I start to use it, it's working fine without auto reboot...
At first when I flashed Nexus everything was ok but then I was busy and haven't used my tab for few weeks and now I have this annoying problem.
Because of this battery goes low very fast.
Is this hardware or software problem?
Hope for your help.
Clock reset to 0.00 is normal with your Nexus Rom after reboot; when wifi is on while you reboot time setting is ok...
It has been fixed with 2.05
I would install and use stock for a day to try if the problems still are there...
(maybe 13.3.2.3, because after that you can install TWRP and a custom rom straight away...; but disable OTA or disable wifi while on stock, otherwise you will get an update)
Maybe a complete new installation (stock -> twrp -> custom rom) will fix it
futzmaster said:
Clock reset to 0.00 is normal with your Nexus Rom after reboot; when wifi is on while you reboot time setting is ok...
It has been fixed with 2.05
I would install and use stock for a day to try if the problems still are there...
(maybe 13.3.2.3, because after that you can install TWRP and a custom rom straight away...; but disable OTA or disable wifi while on stock, otherwise you will get an update)
Maybe a complete new installation (stock -> twrp -> custom rom) will fix it
Click to expand...
Click to collapse
I'm now on 13.3.2.3.2 and problem is still there... I get clock reset on stock fw not nexus, is this normal too?
I also did factory reset...
Long shot - try a forced shutdown via long press of power button. On rare occasions I have found this corrects device weirdness. Really should have the same effect as soft powering off but for some reason it seems to work. Worst case you've lost 2-3 min trying.
Also check if same behavior occurs while booted into recovery. If so almost certainly a hardware issue, possibly when CPUs throttle down or some other 'idle' state kicks in.
Davey126 said:
Long shot - try a forced shutdown via long press of power button. On rare occasions I have found this corrects device weirdness. Really should have the same effect as soft powering off but for some reason it seems to work. Worst case you've lost 2-3 min trying.
Also check if same behavior occurs while booted into recovery. If so almost certainly a hardware issue, possibly when CPUs throttle down or some other 'idle' state kicks in.
Click to expand...
Click to collapse
Did hardware reset, unfortunately without success...
What do you mean with "booted into recovery"? Fastboot or another fw slot with safestrap?
Flashed cm11 and still got this issue! I'm done...
I think you don't need to test custom roms yet...
Your goal should be to have a clean stock rom with no errors.... (no safestrap and stock custom recovery)
If you still have errors you need to contact amazon anyway i guess....
futzmaster said:
I think you don't need to test custom roms yet...
Your goal should be to have a clean stock rom with no errors.... (no safestrap and stock custom recovery)
If you still have errors you need to contact amazon anyway i guess....
Click to expand...
Click to collapse
alright, what's the steps to recover to clean stock from twrp with cm11?
I don't know what's wrong with this phone, but once it's rooted it will eventually enter a boot loop after some restarts or power on/off cycles. You can boot to recovery or fastboot, but no matter what you do there, the only way to fix the bootloop is flashing the stock boot and recovery partitions and formating data from there. The phone will reset to factory and boot up normally, but you will loose all your config, apps, etc. It's a pain in the a** to setup everything all over again every few days. Every time you have to restart your phone is like playing russian roulette, you never know when the boot loop will happen, but it will come up sooner or later no matter what you do. I have performed a lot of tests just rooting and without touching a single thing in config or apps, after some restart cycles it boot loops.
I'm fed up with it because it's so unreliable, it may work fine if you use it stock but I personally need root. I have ended up being so afraid of restarts that I have not powered it off or restarted since a month.
By the way this is my first One Plus and I don't know if this issue happens with other models from the brand.
This is just my experience and my advise.
Even i am a nord 2 owner and currently i am running custom os android 12 , even before this i had no probs like this with root.....
I bricked my device while installing gsi but that was different...
[RECOVERY][UNOFFICIAL] TWRP 3.6.0_11-0 for OnePlus Nord 2 5G [denniz]
Team Win Recovery Project 3.x, or TWRP 3.x for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven...
forum.xda-developers.com
Fastboot reboot recovery
Do this, then flash latest magisk....
You'll be good
satanishere16 said:
Even i am a nord 2 owner and currently i am running custom os android 12 , even before this i had no probs like this with root.....
I bricked my device while installing gsi but that was different...
[RECOVERY][UNOFFICIAL] TWRP 3.6.0_11-0 for OnePlus Nord 2 5G [denniz]
Team Win Recovery Project 3.x, or TWRP 3.x for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven...
forum.xda-developers.com
Fastboot reboot recovery
Do this, then flash latest magisk....
You'll be good
Click to expand...
Click to collapse
Indeed that's what I tried first because I usually solved boot loops with that method in other phones in the past. But with this one that trick does not work, I tried with several magisk versions before trying other things that didn't work either such as restoring a nandroid backup with TWRP or wiping everything and formatting data on TWRP. The only thing that worked was the method I described in OP, which I found in other thread in this forum. I have read reports about other people suffering the same problems, so I know I'm not alone.
By the way it seems to happen only with stock ROM. Which custom ROM are you using?
Regards
Pixel experience android 12....
Dev tab
Hi,
I can confirm that I had the same problem as you to root 3 One Plus Nord 2 (DN2103) from different friends wishing to stay on OxygenOS.
The root works fine and then totally randomly the OnePlus animation keeps looping after a reboot.
By doing a "fastboot -w" it starts again correctly but obviously with a loss of data.
Recently I got a Nord 2 from a friend for testing and it turns out that using the latest version of Magisk Canary, the root seems to remain after several reboots but to be tested over several months.
I've also seen here owners of European Nord 2 who confirm that root works well with Magisk Canary.
Edit : After about 10 reboots, the phone went back to bootloop.
Yes it's really exhausting root this phone. I tried custom roms without any problems with Magisk but stock is broken somehow. I need to use stock because of video recording quality. I have now Magisk 24.3 but didn't really restart it yet because of this. You shoud backup all data before restart . You can use data format in twrp, that works too.
Sperafico said:
Hi,
I can confirm that I had the same problem as you to root 3 One Plus Nord 2 (DN2103) from different friends wishing to stay on OxygenOS.
The root works fine and then totally randomly the OnePlus animation keeps looping after a reboot.
By doing a "fastboot -w" it starts again correctly but obviously with a loss of data.
Recently I got a Nord 2 from a friend for testing and it turns out that using the latest version of Magisk Canary, the root seems to remain after several reboots but to be tested over several months.
I've also seen here owners of European Nord 2 who confirm that root works well with Magisk Canary.
Click to expand...
Click to collapse
Thank you very much. Next time I will try switching to magisk canary channel. I'm on stable and sticking to 24.1 because the last time I updated from that version to 24.3 I got into a boot loop.
8vasa8 said:
Yes it's really exhausting root this phone. I tried custom roms without any problems with Magisk but stock is broken somehow. I need to use stock because of video recording quality. I have now Magisk 24.3 but didn't really restart it yet because of this. You shoud backup all data before restart . You can use data format in twrp, that works too.
Click to expand...
Click to collapse
Thanks for your answer. In my case the first thing I tried was flashing magisk again, then restoring a full nandroid backup with twrp, and then formatting data in twrp, but none of these steps worked.
I also heard about this problem being solved in custom ROMs but I haven't found any that fit my needs or any that has everything working, so I prefer to keep on rooted stock.
#metoo . We need devs to look into this problem. Been using rooted Android phone for years but now it s***s without root on Nord 2.
As long as you use an untouched stock rom (or after modding re-flashed by OnePlus servicepoint, rebooted into stock recovery, wipe all and re-flash stock, in a OnePlus store), root works fine on stock rom. Every attempt different than above will fail one day or another. I decided not to take OTAs because too many things can go wrong / turn unstable.
The phone is my daily driver, also for work. But I am rooted with Magism 24.3 (stable) and have various modules running including LSPosed, Shamiko, USNF, and in LSPosed GravityBox, XprivacyLua pro and a few more.
Works awesomely. Just don't touch things afterwords. In that case, yes, the phone sucks. Big time.
Xatanu said:
I don't know what's wrong with this phone, but once it's rooted it will eventually enter a boot loop after some restarts or power on/off cycles. You can boot to recovery or fastboot, but no matter what you do there, the only way to fix the bootloop is flashing the stock boot and recovery partitions and formating data from there. The phone will reset to factory and boot up normally, but you will loose all your config, apps, etc. It's a pain in the a** to setup everything all over again every few days. Every time you have to restart your phone is like playing russian roulette, you never know when the boot loop will happen, but it will come up sooner or later no matter what you do. I have performed a lot of tests just rooting and without touching a single thing in config or apps, after some restart cycles it boot loops.
I'm fed up with it because it's so unreliable, it may work fine if you use it stock but I personally need root. I have ended up being so afraid of restarts that I have not powered it off or restarted since a month.
By the way this is my first One Plus and I don't know if this issue happens with other models from the brand.
This is just my experience and my advise.
Click to expand...
Click to collapse
shoud what can i do any bramhastra or something ?
Look basically i am nerd and i agree that so apart from root i have question that installing TWRP and Custom Rom,is that working correctly with no issues? particularly pixelos
[email protected] said:
Look basically i am nerd and i agree that so apart from root i have question that installing TWRP and Custom Rom,is that working correctly with no issues? particularly pixelos
Click to expand...
Click to collapse
TWRP and custom roms works without issue. Even root is working with custom.
NANDroid does NOT work on stock rom! TWRP does, but no NANDroids possible.
Unfortunately I agree...
I spent so much time because of manipulations that I am used to doing, and which leads to a boot loop and a brick of the phone immediately afterwards.
The only solution I had was to flash the rom, which of course leads to a total reset each time and a considerable waste of time.
This is my 3rd and last OnePlus phone that I buy, I'm sick of all my lost data and hours spent just getting it started.
Oh my oneplus nord 2 is now in final bootloop. Cant make anything work, just keeps rebooting when plugging in power so $350 down the drain. Would not recommend..
Why down the drain? It's not 1 year old, so Oneplus will renew firmware under warrantee.
Xatanu said:
I don't know what's wrong with this phone, but once it's rooted it will eventually enter a boot loop after some restarts or power on/off cycles. You can boot to recovery or fastboot, but no matter what you do there, the only way to fix the bootloop is flashing the stock boot and recovery partitions and formating data from there. The phone will reset to factory and boot up normally, but you will loose all your config, apps, etc. It's a pain in the a** to setup everything all over again every few days. Every time you have to restart your phone is like playing russian roulette, you never know when the boot loop will happen, but it will come up sooner or later no matter what you do. I have performed a lot of tests just rooting and without touching a single thing in config or apps, after some restart cycles it boot loops.
I'm fed up with it because it's so unreliable, it may work fine if you use it stock but I personally need root. I have ended up being so afraid of restarts that I have not powered it off or restarted since a month.
By the way this is my first One Plus and I don't know if this issue happens with other models from the brand.
This is just my experience and my advise.
Click to expand...
Click to collapse
U r wrong
I'm not sure if it's just a coincidence, but for me, it always happens after about a week or two of ignoreing "you have an update available" popup. I thought maybe it modified the boot image, like magisk, to run at the next startup.
I agree that this is very annoying. If I didn't need Google Pay, I'd just install another rom.
Like said. Have your device Factory-flashed by OnePlus, REBOOT to stock recovery, do a FULL WIPE and FACTORY FLASH stock AGAIN! Only with the official OnePlus tool and software.
Only this way all your old fiddling around is erased. If you ROOT then, all will be fine. Of course, neglect further updates, but the device will work fine. Mine is in this state, heavily tweaked (Magisk, Zygisk, USNF, GravityBox, etc. etc. and it runs stable for over 10 weeks without any hickup.