Related
I am on Liquid Smooth 2.9 (4.2.2) and using TWRP 2.6.3.0 phone is an i747m 32GB model. I tried upgrading to LS2.10 which is 4.3. Installed ROM OK but after first reboot phone froze on the Samsung logo. It wouldn't even get the the boot animation. I tried several methods of flashing as requested but to no avail. Today I tried the latest nightly of Carbon ROM which is 4.3.1 and encountered the same issue. I tried rebooting after flashing GAPPS and it just froze at the Samsung logo without going to boot animation. I did flash the latest bootloader in between while trying to diagnose as well.
Does anyone have any suggestions or similar situations? I would really like to upgrade to a 4.3 ROM but seem to have hit a hurdle...
Thanks in advance.
So I've had a little time to try some other things. I've verified the MD5sum of all files trying to flash. All are good. I've tried installing the latest nightly of Carbon ROM after doing a full wipe of all internal. I haven't formatted my external yet. Flashed ROM and phone boots fine. I've tried flashing GAPPS both during initial flash, after initial flash and not at all. In every case the phone boots fine after the initial flash and functions perfectly. It will not boot a second time at all. In all cases so far on reboot it just stays on the Samsung logo screen and I've left it for about a half hour just to make sure it isn't that I'm not waiting long enough. I hold the power button for 8 seconds and then boot into recovery. I've tried doing a factory reset and rebooting. No go. I've tried refreshing the ROM and it still won't boot after. I haven't taken a logcat yet as I just haven't had time but I'm really confused why multiple ROM's. I've currently restored back to 4.2.2 liquidsmooth 2.9.
I'm really hoping someone has a suggestion or that they've come across this before.
Galloway said:
So I've had a little time to try some other things. I've verified the MD5sum of all files trying to flash. All are good. I've tried installing the latest nightly of Carbon ROM after doing a full wipe of all internal. I haven't formatted my external yet. Flashed ROM and phone boots fine. I've tried flashing GAPPS both during initial flash, after initial flash and not at all. In every case the phone boots fine after the initial flash and functions perfectly. It will not boot a second time at all. In all cases so far on reboot it just stays on the Samsung logo screen and I've left it for about a half hour just to make sure it isn't that I'm not waiting long enough. I hold the power button for 8 seconds and then boot into recovery. I've tried doing a factory reset and rebooting. No go. I've tried refreshing the ROM and it still won't boot after. I haven't taken a logcat yet as I just haven't had time but I'm really confused why multiple ROM's. I've currently restored back to 4.2.2 liquidsmooth 2.9.
I'm really hoping someone has a suggestion or that they've come across this before.
Click to expand...
Click to collapse
When you flash the ROM, are you wiping dalvik cache as well as wiping all data/ factory reset and cache?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I have the same, CM10.2, Quantum. First boot is ok. but after reboot phone freeze on samsung logo and recovery TWRP 2.6.3.0 needs password. I cant make any wipes, cant restore backup - needs password. Update last bootloader, before flashing made wipe /system /data /cache /dalvik, after - wipe /cache /dalvik /data againe - nothing, second boot only logo,
Could some one tell me, what I do wrong?
gluk1470 said:
I have the same, CM10.2, Quantum. First boot is ok. but after reboot phone freeze on samsung logo and recovery TWRP 2.6.3.0 needs password. I cant make any wipes, cant restore backup - needs password. Update last bootloader, before flashing made wipe /system /data /cache /dalvik, after - wipe /cache /dalvik /data againe - nothing, second boot only logo,
Could some one tell me, what I do wrong?
Click to expand...
Click to collapse
At least it's not just me....unfortunately I don't have much time lately so I haven't been able to try experimenting. I noticed you are using TWRP as well....I may try flashing CWM if I get a sec and see if the results are the same. Also if the same happens and I have enough time I'll try and grab a logcat. If I don't have time it's called wipe and restore from a backup.
And yes Dalvik + cache are always wiped anytime I flash anything as a minimum. With this issue I have been doing an entire internal format. I have tried just wiping cache and Dalvik when it occurs as well as fixing permissions but still doesn't boot. Wish I had more time latrely to narrow it down.
Yes, its work. I flashed stock ROM 4.1.2, then root device, flash CWM 6.0.2.3 (no touch) and flash Quantum 2.20. But I think, problem not in recovery or device. Problem in Titanium Backup, I used it to restore some system apps and accounts, now I restored only call log and SMS.
I have now tried flashing with TWRP and pulling SD card before initial boot to eliminate an SD card issue. I've set to not install backups from Google as precaution. Still the same result of frozen at Samsung logo.
I've then flashed the newest CWM non-touch and wiped all with flash. The result was even worse. This time it wouldn't even boot the first time for initial setup it just hangs at the Samsung logo.
This is starting to get frustrating just due to the fact of me not having a huge amount of time to dedicate to isolating the issue. I need to get a logcat but I am not usually near a computer to ADB to it when it is not booting. If I have time this weekend I'll try and get a logcat to post up.
CWM broke it real good! LOL! Anyways I couldn't even get my backups to restore. I tried taking a logcat while it was frozen but was not able to get an ADB connection in order to even get a logcat. I managed to push a fresh copy of Liquidsmooth 2.9 to the SD card and install it. Then flashed TWRP back. Then restored my back up. What a tedious task to still be scratching my head as to why multiple 4.3 ROM's won't boot on the second boot after flashing...
It's been resolved! As per an awesome person on Carbon's G+ thread don't flash the ROM from external SD .Only flash it from internal storage!
Background:
1. Was on the latest Resurrection Remix. Made a Backup with TWRP.
2. Went back to stock [MTC20F] using this.
3. Updated to 7.0 using this threads 7.0 OTA.
4. Made a Backup in TWRP.
I restored the backup from point 1, but now my phone won't boot anymore.
It shows the boot animation for about 1 second. Goes black and reboots.
I tried restoring to 6.0.1 using the method in point 2 -> same problem.
Tried restoring to 7.0.0 using the same method -> same problem.
After that, I tried restoring from both of my TWRP backups. Neither of them get any further.
So, no matter what I do I cant get past the first second of the boot animation.
I'm out of ideas, any help is greatly appreciated!
TWRP version 3.0.2.1
MiePx3 said:
Background:
1. Was on the latest Resurrection Remix. Made a Backup with TWRP.
2. Went back to stock [MTC20F] using this.
3. Updated to 7.0 using this threads 7.0 OTA.
4. Made a Backup in TWRP.
I restored the backup from point 1, but now my phone won't boot anymore.
It shows the boot animation for about 1 second. Goes black and reboots.
I tried restoring to 6.0.1 using the method in point 2 -> same problem.
Tried restoring to 7.0.0 using the same method -> same problem.
After that, I tried restoring from both of my TWRP backups. Neither of them get any further.
So, no matter what I do I cant get past the first second of the boot animation.
I'm out of ideas, any help is greatly appreciated!
TWRP version 3.0.2.1
Click to expand...
Click to collapse
Did you boot into recovery and do a factory reset in there. Sometimes that works.
jsgraphicart said:
Did you boot into recovery and do a factory reset in there. Sometimes that works.
Click to expand...
Click to collapse
Yep, every time I try to restore something I wipe everything. Also tried to lock and unlock the bootloader. No Luck.
Also tried wipe and erasing every partition possible, flashing an older 6.0.1 build.
Am I SOL? I tried anything google would give me....
Hey, I'm currently in the very same situation. Was on 6.0.1 stock rooted, applied 7.0 OTA using the beta program. Then for various reasons wanted to roll back to where I was with 6.0.1, but now the device just constantly reboots. I have wiped everything I can, tried to flash the factory images multiple times, but nothing seems to do the trick.
same problem here
i was on rooted android n preview 5 with twrp recovery and root, i applied 7.0 ota and then it bricked
now it starts up till bootscreen with the 4 coloured dots it freezes and goes in a bootloop but fastboot and recovery working fine
flashed a factory image wiped everything tried diffrent things restored a twrp backup but nothing
now im going to try to flash 7.0 ota again
Also in the same situation :crying:. Gets to the boot animation for 1 second then freezes and restarts.
Updated to 7.0 and got stuck in a bootloop.
Then tried restoring my TWRP backup to no avail.
Then tried flashing 6.0.1 factory image and still no luck.
Done factory resets, wiped system, data partitions etc, and still same problem.
If anyone has any other ideas that would be greatly appreciated!
this is what i tried so far
-wiped and restored 3 diffrent backups
-full wipe and flashed diffrent roms
-flashed factory image 6.0 and 6.0.1
-flashed 7.0 ota zip in twrp (extracted and flashed system.img and vendor.img )
-flashed factory image and used stock recovery to flash 7.0 ota.zip trough ADB sideload
i think im going to relock the bootloader and just send it back to google for a repair
I'm on the same situation
32 hours after updating to final 7.0 from stock dp5 the device turned off and stuck on boot animation
it seems like google did something wrong...
Looks like some people with the 6P are having the same issue as well. Still no fix either.
http://forum.xda-developers.com/nexus-6p/help/botched-nougat-install-phone-boot-loop-t3445709
I've had the same problem. I was coming from from a Pure Nexus install and thought i'd have a look at 7 so I made a full backup in TWRP then installed the lastest TWRP (twrp-3.0.2-1-bullhead). Then did a full wipe all bar internal storage and flashed radio/bootloader zip and Stock+ rom from the tupac4u thread which worked fine. Upon deciding there were a few dealbreakers for me I decided to go back to PN. So I booted back into TWRP, wiped again and restored the previously made backup. that's when I was getting the boot to 4 dots and reboot bootloop. I tried everything flashing various MM roms, and flashing 7 again, different roms / vendor images / full wipes including int storage, all via TWRP and ADB to no avail.
Though this evening I decided to go to an even earlier version of TWRP (twrp-3.0.0-1-bullhead) and try everything again. I flashed that and tried the repair filesystem on all the partitons I could, one of them gave an error I can't remember what it was. After doing that I did a full wipe and restored my PN backup, everything ticked. I then rebooted with everything crossed and it worked, it booted without any problems! (apart from the fact i'd forgot to remove the pin security before backing up so had to reflash anyway! which also worked). I can't be sure which part of that fixed it but if it helps anyone else that's great!
People with this problem - Does flashing new Factory Image 7.0.0 (NRD90M) fix something?
Just curious.
zeesyl said:
People with this problem - Does flashing new factory image 7.0.0 (NRD90M) fix something?
Just curious.
Click to expand...
Click to collapse
Nope, changed nothing in my case at least. At this point I'm just going to use the warranty card to get out of this mess, as nothing seems to revive the device.
MiePx3 said:
Background:
1. Was on the latest Resurrection Remix. Made a Backup with TWRP.
2. Went back to stock [MTC20F] using this.
3. Updated to 7.0 using this threads 7.0 OTA.
4. Made a Backup in TWRP.
I restored the backup from point 1, but now my phone won't boot anymore.
It shows the boot animation for about 1 second. Goes black and reboots.
I tried restoring to 6.0.1 using the method in point 2 -> same problem.
Tried restoring to 7.0.0 using the same method -> same problem.
After that, I tried restoring from both of my TWRP backups. Neither of them get any further.
So, no matter what I do I cant get past the first second of the boot animation.
I'm out of ideas, any help is greatly appreciated!
TWRP version 3.0.2.1
Click to expand...
Click to collapse
Type fastboot -w flash falsh vendor vendor.img then restore from your twrp backups
neaznc021 said:
OMG I finally got mine to work
I'll note down the exact steps , most of which may or may not be relevant
1) Flashed MTC20F using TWRP 3.0.2-1
2) Booted into recovery and wiped everything and the partitions
- Add - Booted back into twrp 3.0.2-1 and then swiped to allow modifications
3) Then fastboot flashed TWRP 3.0.2-0
4) Restored my backup ( except recovery)
5) Still got stuck in the google screen.
Now the next parts are a bit weird
6) Booted into TWRP, flashed vendor.img from pure nexus rom
7) wiped everything except internal storage
8) Flashed vendor.img, pure nexus rom and gapps and then flashed vendor.img again
9) Rebooted and it worked
Let me know if it worked for you guys or if you need any more help
Click to expand...
Click to collapse
this worked for me
neree said:
Nope, changed nothing in my case at least. At this point I'm just going to use the warranty card to get out of this mess, as nothing seems to revive the device.
Click to expand...
Click to collapse
Did that yesterday (With my N6P), will see what will come out of it. (Service guys said, that ''Oh, it's nothing serious, tomorrow (today) you will get your phone back (hopefully in working condition)''. I'm not so sure about that
(EDIT: Before I took my phone to warranty service, I flashed latest MM factory image and locked bootloader, maybe it was unnecessary, but I wanted to be sure, that phone looks fresh, maybe it was a big mistake.)
I had the same Bootloop issue, and it's all because of TWRP 3.0.2-1 !!! I have just reverted back to TWRP 3.0.2-0, and my backup restored just fine. There's no point for all that flashing. Just revert the TWRP.
Oh my... Guess what? My backup is corrupted...
Edit: maybe this can help, before bricking with full factory image, I flashed bootloader, radio, boot, vendor, system, Elementalx and supersu, wiped data and booted and work.
But I had problems with suspersu installed as systemless (it didn't work), so I flashed factory image. And bootlooped.
So, I'd say that what's causing issue is userdata, recovery or cache.
Guys, a bit of help.
I clean flashed the new OOS 4.0, coming from the 30dez RR-N Unoff by Eliminator.
That worked, but encrypted my system. I couldn't access the recovery, was asking for a pass.
So I formatted everything, and now trying to go back to RR 5.7.4 M. I tried Eliminators and Takers builds. Both are stuck at the RR logo.
I flashed 3.2.8 firmware, followed by
ROM
Nano 6.0 Open Gapps
Ex Kernel 0.39(CM)
SuperSU 2.79
Xposed v87
TB
Followed this for both the Official and Unofficial build.
Both stuck at the RR logo.
Do I need the modified .28 TWRP?
I wanted xposed, so I wanted to downgrade back to M
Tried something
Flashed the modified TWRP, and tried flashing OOS 3.2.8 and SuperSU 2.79
Getting this error now
Code:
Encryption Unsuccessful
Encryption was interrupted and can't complete. As a result, the data on your phone is no longer accessible
To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google Account.
Here, there is a button to reset the phone, but pressing that does nothing. Pressing the power button gives me the options of powering off the device, rebooting, and taking a screenshot.
I went into fastboot then and did a fastboot erase userdata.
Then I booted into TWRP and did a format all, typed yes(that keeps changing the data partition to F2FS, so I changed it to exFat)
I flashed OOS 3.2.8 again, followed by SU again.
Got the same Encryption Unsuccessful message again, with the same option to reset the phone, which is not working.
Tried the 3.2.4 firmware, and then I flashed OOS 3.2.8 along with SU 2.79 again, in the hopes that if it boots properly, I will clean flash BJRR 5.7.4.
First I got error 7.
Formatted everything again and flashed again
Still getting the Encryption Unsuccessful message.
What to do?
I'll try flashing BJRR M directly this time.
I think the issue was after installing the new OOS 4.0 update, it encrypted my phone, and I flashed stuff before unencrypting it, I thought format option in TWRP would remove encryption.
Help please.
Its been 15 mins, BJRR 5.7.4 still stuck at the RR logo.
gro0vr said:
Guys, a bit of help.
Help please.
Its been 15 mins, BJRR 5.7.4 still stuck at the RR logo.
Click to expand...
Click to collapse
Flash 4.0 full rom, reboot
flash modified twrp, change /data to ext4
wipe /data, cache, dalvik
reboot
you are now 100% stock with working twrp and /data partition
BTW with encrypted issue.
Wipe Userdata with Fastboot
Go back to Twrp flash rom and directly flash SuperSU
You should be decrypted currently we can't encrypt because of TWRP.
atulclassic said:
Flash 4.0 full rom, reboot
flash modified twrp, change /data to ext4
wipe /data, cache, dalvik
reboot
you are now 100% stock with working twrp and /data partition
Click to expand...
Click to collapse
Thanks for getting back.
I already flashed the modified TWRP through fastboot. Will I need to flash that again after installing 4.0 ROM?
I will try this and get back to you.
Puddi_Puddin said:
BTW with encrypted issue.
Wipe Userdata with Fastboot
Go back to Twrp flash rom and directly flash SuperSU
You should be decrypted currently we can't encrypt because of TWRP.
Click to expand...
Click to collapse
I tried fastboot erase userdata.
the command completed successfully, but on OOS 3.2.8, it still showed the Encryption Interrupted error.
I will try flashing OOS 4.0 and get back.
If I want to downgrade from OOS 4.0, how will that work? Do I just wipe everything after flashing the OOS 4.0, then flash RR 5.7.4 or OOS 3.2.8?
atulclassic said:
Flash 4.0 full rom, reboot
flash modified twrp, change /data to ext4
wipe /data, cache, dalvik
reboot
you are now 100% stock with working twrp and /data partition
Click to expand...
Click to collapse
Flashed 4.0 after formatting everything.
Rebooted.
Changed /data to extfat by mistake.
Wiped /data, cache, dalvik
Rebooted in OOS 4.0
Got the Encryption Interrupted message again, but this time pressing the reset phone button worked, and took me to TWRP.
Booting to sysyem again took me to TWRP again.
Noticed everything had been deleted.
Formatted everything again
Installed 4.0
Reboot
Installed the modified twrp again via fastboot(already flashed it, so I skipped it during the first time I flashed 4.0)
Changed /data to ext4 correctly this time.
Wiped /data, cache, dalvik
Rebooted.
Again came back to twrp
Now, when I install 4.0, and change /data to ext4, it deletes everything, and I am reboot back to twrp even if I select reboot to system in TWRP.
Since I can't have 4.0 with /data on ext4, I tried to install RR 5.7.4.
Same result, keeps sending me back to recovery.
gro0vr said:
Flashed 4.0 after formatting everything.
Rebooted.
Changed /data to extfat by mistake.
Wiped /data, cache, dalvik
Rebooted in OOS 4.0
Got the Encryption Interrupted message again, but this time pressing the reset phone button worked, and took me to TWRP.
Booting to sysyem again took me to TWRP again.
Noticed everything had been deleted.
Formatted everything again
Installed 4.0
Reboot
Installed the modified twrp again via fastboot(already flashed it, so I skipped it during the first time I flashed 4.0)
Changed /data to ext4 correctly this time.
Wiped /data, cache, dalvik
Rebooted.
Again came back to twrp
Now, when I install 4.0, and change /data to ext4, it deletes everything, and I am reboot back to twrp even if I select reboot to system in TWRP.
Since I can't have 4.0 with /data on ext4, I tried to install RR 5.7.4.
Same result, keeps sending me back to recovery.
Click to expand...
Click to collapse
Yes.. Flash stock recovery if it boots flash TWRP back. Its a mess it really is..
Puddi_Puddin said:
Yes.. Flash stock recovery if it boots flash TWRP back. Its a mess it really is..
Click to expand...
Click to collapse
I'll try flashing the stock recovery.
Could you tell me what are the stock formats of /system partition? ExFat or Ext4?.
/Data keeps changing to F2FS, what should I change that to? exfat or Ext4?
Also, what should I change cache to? Its currently at exfat.
gro0vr said:
I'll try flashing the stock recovery.
Could you tell me what are the stock formats of /system partition? ExFat or Ext4?.
/Data keeps changing to F2FS, what should I change that to? exfat or Ext4?
Also, what should I change cache to? Its currently at exfat.
Click to expand...
Click to collapse
Ext4 is default. Don't change cache.. Only Data.
IT BOOTED!!!
Puddi_Puddin said:
Ext4 is default. Don't change cache.. Only Data.
Click to expand...
Click to collapse
Thanks. Just booted.
Atulclassic told me /data was ext4, was wondering about /system.
It just booted.
I followed both your advice, flashed stock recovery, then relocked the bootloader.
Then tried pushing ota via adb. That didn't work
Said loading failed.
So I unlocked the bootloader again, flashed modified TWRP
Flashed OOS 3.2.8
Just that, didn't flash SuperSU or anything else.
Just booted into the setup page.
Thanks a ton for helping me out.
I encrypted my phone under security settings menu. It finished encryption process just fine, rebooted, asked for my pattern and then just got stuck on boot animation. I let it sit on boot animation for at least 45 minutes yet no success.
Here is the TWRP recovery log. https://pastebin.com/3BLnGdVw
I noticed some I/O errors show up regarding some apps but it's hard to see why they would be causing errors.
I'm using the latest RR ROM by Eliminater with TWRP 3.1.0-x by blu_spark v26. Also OB16 rom+fw.
Cache and data partitions use F2FS, system is EXT4.
Edit: Kind of fixed it by reflashing everything and flashing SuperSU instead of Magisk that was included with RR by Eliminater. Had no luck installing Magisk in any way. Still feels like something is wrong so further testing is needed, I'll edit when I find something out.
karliyo said:
I encrypted my phone under security settings menu. It finished encryption process just fine, rebooted, asked for my pattern and then just got stuck on boot animation. I let it sit on boot animation for at least 45 minutes yet no success.
Here is the TWRP recovery log. https://pastebin.com/3BLnGdVw
I noticed some I/O errors show up regarding some apps but it's hard to see why they would be causing errors.
I'm using the latest RR ROM by Eliminater with TWRP 3.1.0-x by blu_spark v26. Also OB16 rom+fw.
Cache and data partitions use F2FS, system is EXT4.
Edit: Kind of fixed it by reflashing everything and flashing SuperSU instead of Magisk that was included with RR by Eliminater. Had no luck installing Magisk in any way. Still feels like something is wrong so further testing is needed, I'll edit when I find something out.
Click to expand...
Click to collapse
Yep dont do that stuff, done it once and my phone magically didn't boot..
karliyo said:
I encrypted my phone under security settings menu. It finished encryption process just fine, rebooted, asked for my pattern and then just got stuck on boot animation. I let it sit on boot animation for at least 45 minutes yet no success.
Here is the TWRP recovery log. https://pastebin.com/3BLnGdVw
I noticed some I/O errors show up regarding some apps but it's hard to see why they would be causing errors.
I'm using the latest RR ROM by Eliminater with TWRP 3.1.0-x by blu_spark v26. Also OB16 rom+fw.
Cache and data partitions use F2FS, system is EXT4.
Edit: Kind of fixed it by reflashing everything and flashing SuperSU instead of Magisk that was included with RR by Eliminater. Had no luck installing Magisk in any way. Still feels like something is wrong so further testing is needed, I'll edit when I find something out.
Click to expand...
Click to collapse
The real trouble is the mine: I've done encryption with a custom rom (Dirty Unicorns v11.3) and I achieved your same result: bootloop.
You've to keep OxygenOS encryption, is much simple:
1) Reflash the firmware with a factory reset without Magisk (because it prevents forced encryption);
2) After first startup, reboot in bootloader and flash again TWRP;
3) Go in TWRP for a full wipe, then flash your desider rom.
4) Et voilà, encryption still remains (because it's upper to /data, /system and /cache);
5) Now you can install Magisk, because encryption is already enabled.
I would add that 3rd-party encryption get you in troubles when you switch back to OOS (99% sure that recovery can't decrypt).
Stay with stock encryption, or remove it via fastboot format userdata.
So here is my problem:
My OnePlus 5T is stuck in a bootloop. The device was stock when it started, and is now back to the latest stock ROM.
In between I tried serval custom ROM's and a custom kernel to solve my bootloop issue. Flashing other ROM's, kernels or recovery's didn't do it. The device still is in a bootloop. It goes as far as the boot logo, then freezes and then reboots. Sometimes I can acces the operating system, but that only lasts for a few seconds before it also freezes and reboots.
Is there anyone who can possibly help me with this issue?
Thanks in advance.
u may have to wipe system, data, and both caches also u may have to format data (will wipe internal storage, so make backup to PC or OTG) and install a clean official Oxygen OS from their site, do u have TWRP?
also if you have overlays from substratum can cause issues if u have not wiped system and data.
Bradl79 said:
u may have to wipe system, data, and both caches also u may have to format data (will wipe internal storage, so make backup to PC or OTG) and install a clean official Oxygen OS from their site, do u have TWRP?
also if you have overlays from substratum can cause issues if u have not wiped system and data.
Click to expand...
Click to collapse
Thanks for the reply.
I have wiped system, data and both caches and formatted data. I clean installed the lastes build of oxygen(5.1.2).
Unfortunatly this still gives the same result. The phone crashes on boot. For now I have tried these OS:
Oxygen OS: Gets stuck on boot logo
TheOne5TOS: Gets stuck on boot logo and goes back in TWRP.
Android Open Source Project Extended: Loads OS. crashes after a while. Gives me a black screen with a purple notification light.
For TWRP I use Blu Spark for the 5T
Added: I don't use substratum
Try the unbrick tool. Its my last resort and always works if u can get it into dl mode.
Woodrow256 said:
Try the unbrick tool. Its my last resort and always works if u can get it into dl mode.
Click to expand...
Click to collapse
I tried the unbrick tool. Connected the phone and downloaded the stock firmware. But this gets the same result as previously. It loops.
It's a hardware issue, u need to contact oneplus, someone else had that issue too, not sure the outcome though