I just got my new OP3, I rooted it and flash Cm 14.1. Everything was working fine until I added a 6x6 pattern password which I forgot. Search around a bit and looked like the only option was to factory reset. I went to twrp and wipe into factory reset. Afterwards I reboot system only to find that I'm stuck at the Oneplus logo screen, it wouldn't load into lock screen. I have tried flashing lastest stock rom as well as OS 3.2.7 which was the one I used in conjunction with Cm 14.1.
No idea how to fix this. I can use recovery mode and fastboot, but I just can't get pass that logo during reboot.
Any help would be great. Thanks in advance.
try wiping the dalvik cache and data and everything else and clean install the ROM
Tried wipe
anup807 said:
try wiping the dalvik cache and data and everything else and clean install the ROM
Click to expand...
Click to collapse
I wiped everything but the internal storage. I am quite new, what is clean install?
Check this thread out: http://forum.xda-developers.com/oneplus-3/how-to/guide-downgrade-to-mm-flashing-ob8-t3511161
If all else fails, and you're fine with losing your data, pictures, etc. Reformat your phone. I had a similar problem when trying to go back to Android M from N. I ended up booting in fastboot and running the commands:
fastboot format:ext4 cache
fastboot format:ext4 data
fastboot format:ext4 system
Then from here you could either side load a ROM or boot into twrp and transfer your ROMs to flash. That's how I fixed my softbrick lol. There might be another way but that worked for me.
---------- Post added at 04:26 AM ---------- Previous post was at 04:25 AM ----------
Darrentay said:
I wiped everything but the internal storage. I am quite new, what is clean install?
Click to expand...
Click to collapse
Wiping all partitions except for internal storage then flashing a ROM is considered a clean flash.
Thanks
jon52491 said:
Check this thread out: http://forum.xda-developers.com/oneplus-3/how-to/guide-downgrade-to-mm-flashing-ob8-t3511161
If all else fails, and you're fine with losing your data, pictures, etc. Reformat your phone. I had a similar problem when trying to go back to Android M from N. I ended up booting in fastboot and running the commands:
fastboot format:ext4 cache
fastboot format:ext4 data
fastboot format:ext4 system
Then from here you could either side load a ROM or boot into twrp and transfer your ROMs to flash. That's how I fixed my softbrick lol. There might be another way but that worked for me.
---------- Post added at 04:26 AM ---------- Previous post was at 04:25 AM ----------
Wiping all partitions except for internal storage then flashing a ROM is considered a clean flash.
Click to expand...
Click to collapse
Well in that case, I have clean flash multiple times with different ROM, but I'm still stuck at the logo once I try to reboot. I also tried to flash Os 3.2.7 and Cm 14.1 again but i got no results. Attempting to reformat I guess? I have no data since its a new phone, so I don't mind losing stuff.
Okay sounds good! Before you reformat through fastboot, try booting into twrp and reformatting the partitions through there. TWRP>wipe>advance wipe>cache>change file system>ext4
Repeat the steps for the data and system partitions as well. Then from there transfer a 6.0 ROM and flash it over with the correct Gapps.
Sent from my ONEPLUS A3000 using Tapatalk
Darrentay said:
I just got my new OP3, I rooted it and flash Cm 14.1. Everything was working fine until I added a 6x6 pattern password which I forgot. Search around a bit and looked like the only option was to factory reset. I went to twrp and wipe into factory reset. Afterwards I reboot system only to find that I'm stuck at the Oneplus logo screen, it wouldn't load into lock screen. I have tried flashing lastest stock rom as well as OS 3.2.7 which was the one I used in conjunction with Cm 14.1.
No idea how to fix this. I can use recovery mode and fastboot, but I just can't get pass that logo during reboot.
Any help would be great. Thanks in advance.
Click to expand...
Click to collapse
http://forum.xda-developers.com/one...ashing-ob8-t3511161/post69994625#post69994625
Try this method. It worked flawlessly for me.
Download the official ROM from oneplus Website. Support-->Downloads.
http://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_3.2.8/
official recovery:
http://oneplusroms.s3.amazonaws.com...694615&Signature=1Momnxm8gHWw03D401Oof5YxnE4=
anup807 said:
http://forum.xda-developers.com/one...ashing-ob8-t3511161/post69994625#post69994625
Try this method. It worked flawlessly for me.
Download the official ROM from oneplus Website. Support-->Downloads.
http://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_3.2.8/
official recovery:
http://oneplusroms.s3.amazonaws.com...694615&Signature=1Momnxm8gHWw03D401Oof5YxnE4=
Click to expand...
Click to collapse
I notice something interesting after flashing 3.2.8, when I try to reboot system, it says no OS installed.
Darrentay said:
I notice something interesting after flashing 3.2.8, when I try to reboot system, it says no OS installed.
Click to expand...
Click to collapse
Really Strange. I think its the problem with the system partition format and encryption.
Anyway best solution now is to contact Oneplus tech support.
They'll hard reset your phone and restore it with stock firmware.
Partitions are probably corrupt or on f2fs. Check each partition and make sure it's set to ext4. If it won't allow you to do that in twrp, use the command "fastboot format:ext4 nameofpartition". After that you should be able to flash over a marshmallow ROM.
Sent from my ONEPLUS A3000 using Tapatalk
Have you tried changing / updating the twrp recovery. Newer roms require the unofficial one.
v.konvict said:
Have you tried changing / updating the twrp recovery. Newer roms require the unofficial one.
Click to expand...
Click to collapse
I can't solve the problem so I contacted Oneplus. They use remote access to help wipe everything and reinstall drivers. Thanks for the help though.
Related
HI everyone
I made a mistake yesterday, I flashed a wrong kernel ( the F4ktion dedicated to the CM11 versions while I was 10.2 (I didnt pay attention to the mention JB).
The phone rebooted and stucked on the samsung logo. Then, screen slowly turning gray.
Having access to the download mode, I flashed the bml4 rom stock (probably the main mistake) but this time the phone was stuck on the second samsung logo without turning gray.
Last point, it is impossible for me to get to recovery mode, download fashion meanwhile is still accessible.
Is there a solution?
Thanks
I'd download a stock image of the firmware, install it using Odin and download mode, then flash TWRP recovery, format everything, and install the original firmware again using Odin. That way, you'd make sure your phone is completely clean of errors. Also, is format the micro sd as exFat.
Hope it helps
maquille said:
HI everyone
I made a mistake yesterday, I flashed a wrong kernel ( the F4ktion dedicated to the CM11 versions while I was 10.2 (I didnt pay attention to the mention JB).
The phone rebooted and stucked on the samsung logo. Then, screen slowly turning gray.
Having access to the download mode, I flashed the bml4 rom stock (probably the main mistake) but this time the phone was stuck on the second samsung logo without turning gray.
Last point, it is impossible for me to get to recovery mode, download fashion meanwhile is still accessible.
Is there a solution?
Thanks
Click to expand...
Click to collapse
You didn't need to ODIN the stock ROM back. You could've just reflash the correct kernel and wipe cache/davilk and it should work. What I would recommend you do know is flash a custom recovery and do a complete wipe than ODIN again.
---------- Post added at 02:56 PM ---------- Previous post was at 02:54 PM ----------
jorgeealdunate said:
I'd download a stock image of the firmware, install it using Odin and download mode, then flash TWRP recovery, format everything, and install the original firmware again using Odin. That way, you'd make sure your phone is completely clean of errors. Also, is format the micro sd as exFat.
Hope it helps
Click to expand...
Click to collapse
I don't get it, why format the MicroSD card as exFAT? FAT32 works just fine unless you have a 32GB+ card.
Hi
Thank's for your answers.
I'd like to keep the data on my sd card, so I have done the wipe cache and dalvik but still the same problems.
In your opinion, flash the cyanogen rom be able to fix this problem or isnt recommended?
If you have other opinions so I do not reset everything I'm interested. (Flash of good kernel, flash of f4ktion?..)
Otherwise I will resolve to do the full wipe.
You could try getting a stock kernel and flash it using Odin. I'd that doesn't work, i think you should full wipeand reinstall the firmware. I think you could also flash am original firmware image without wiping and that could fix the errors.
maquille said:
Hi
Thank's for your answers.
I'd like to keep the data on my sd card, so I have done the wipe cache and dalvik but still the same problems.
In your opinion, flash the cyanogen rom be able to fix this problem or isnt recommended?
If you have other opinions so I do not reset everything I'm interested. (Flash of good kernel, flash of f4ktion?..)
Otherwise I will resolve to do the full wipe.
Click to expand...
Click to collapse
If you wiped davilk/cache and still doesn't work, it looks like you have to do a full wipe - no other ways around.
Just to clarify, you want to keep data on the internal storage or SD card? Full wipe does not wipe SD card unless you specifically tells it to.
TNCS said:
If you wiped davilk/cache and still doesn't work, it looks like you have to do a full wipe - no other ways around.
Just to clarify, you want to keep data on the internal storage or SD card? Full wipe does not wipe SD card unless you specifically tells it to.
Click to expand...
Click to collapse
Internal storage...and flash a cyanogen rom couldnt be a solution?
You still will need to flash a custom recovery first.
Than, if you want, you can install Cyanogen of course, it comes with kernel and all..
Just be sure that you are ready to switch the whole ROM
maquille said:
Internal storage...and flash a cyanogen rom couldnt be a solution?
Click to expand...
Click to collapse
With a soft brick like stuck at boot animation, generally no. You need to do a clean wipe.
hi everyone! Firstly thank you for your help. so I resolved to do a complete wipe with relocation of a stock rom and it worked.
Envoyé de mon GT-I9195 en utilisant Tapatalk
Hey guys,
So last night I accidentally wiped internal storage in TWRP. I guess that messed up my partitions or something, I don't know. Anyway, I can still access recovery, and I've tried to do a restore (one that I made back when I was on stock 4.4.2 I think) but after that it tries to boot, gets to "Android is upgrading... Optimizing app Y of X." and once that operation completes it shows the lockscreen for about a tenth of a second, and the phone reboots.
I'm stumped. Anyone know what can I do?
Sorry if this has been asked a hundred times. For some reason the search function in the forums isn't working for me. And I've been looking for a solution all morning.
EDIT: FYI when I tried the restore I did only System and Data and not Boot, because I was afraid that'd cause more problems.
Did you try restoring and performing a factory wipe before booting the newly-restored ROM?
It seems that Marshmallow based roms aren't working, but Lollipop ones will boot. Not sure why as I didn't have any problem with the same MM roms in the past.
More info:
MM roms wont flash in TWRP; after the failed attempt, TWRP says system cannot be mounted until I either wipe or install a 12.1 rom.
Tried to install a stock rom (4.4.2) and it failed in TWRP. Just says "Error Flashing"
Are you performing a full wipe (system, Dalvik, cache, data) before installing or restoring a ROM? Is the phone running the latest version of TWRP?
audit13 said:
Are you performing a full wipe (system, Dalvik, cache, data) before installing or restoring a ROM? Is the phone running the latest version of TWRP?
Click to expand...
Click to collapse
Yes to full wipe. TWRP is 2.8.7.0, so yeah I think it's the newest? Not 100% sure.
Wiping internal storage should not affect the partitions. I'm not sure that TWRP even has the ability to change partitions.
Yes, 2.8.7.0 is the latester version of TWRP.
If you are on the nj2 bootloader, try flashing this in TWRP: http://forum.xda-developers.com/galaxy-s3-att/general/rooted-ucufnj1-stock-rom-t2985006
Welp, seems to be all good now. Not sure if I really did anything to fix it or not. I tried to install a stock ROM but it wouldn't boot (stuck on Samsung logo) but after that my CM13 ROM installed properly again. The one CM13 ROM I have still wont install at all - maybe that file became corrupt or something? Not sure if that's even possible.
Either way I'm all fixed up. Thanks for all your help.
Cheers
Glad you got it sorted out. If you do figure out what you did to get it working, post your answer as it may help others that are in a similar situation.
Something is going on with my phone that doesn't let me flash anything. I was on CM14 with TWRP 3.0.2-22. I did an advanced wipe and I think I selected "system" there. I didn't really see it until I started the wipe. Now I can't boot into anything because I wiped the rom and am stuck without being able to flash anything.
Some things I tried:
When I flash the official CM14, it starts the flashing process, but doesn't get past that system flashing.
Flashing an OxygenOS-based rom (OP3Lite 2.4.2) got stuck on "extracting system."
Restoring a CM13 nandroid backup I had from before I installed CM14 finished restoring, but the phone won't boot into Android.
I ran out of ideas. How can I restore my phone?
I did an advanced wipe and I think I selected "system" there. I didn't really see it until I started the wipe.
Click to expand...
Click to collapse
That's fine, you need to wipe system to flash a new ROM.
When I flash the official CM14, it starts the flashing process, but doesn't get past that system flashing.
Flashing an OxygenOS-based rom (OP3Lite 2.4.2) got stuck on "extracting system."
Click to expand...
Click to collapse
How long does it stay stuck? Most ROMs take a lot of time in flashing system because it involves unpacking and flashing firmware. Depends on the installer, really.
Restoring a CM13 nandroid backup I had from before I installed CM14 finished restoring, but the phone won't boot into Android.
Click to expand...
Click to collapse
Can you remember if you also selected System partition when making backups? If you did, try restoring after wiping System, data and cache.
mharis05 said:
That's fine, you need to wipe system to flash a new ROM.
Click to expand...
Click to collapse
What I've to see?
Wiping /system on OnePlus 3 is unreccomended, since many ROMs need a OxygenOS base already installed.
If you wipe system, before flashing anything you've to restore OOS (both Stock and Community Edition are good).
If you forget that, you'll see a graceful Error 7
Simone98RC said:
What I've to see?
Wiping /system on OnePlus 3 is unreccomended, since many ROMs need a OxygenOS base already installed.
If you wipe system, before flashing anything you've to restore OOS (both Stock and Community Edition are good).
If you forget that, you'll see a graceful Error 7
Click to expand...
Click to collapse
That is wrong in any form. There is no rom that needs oos system to be present before flashing. And its not recommended to (dirty flash over a stock rom when switching to a custom rom)
---------- Post added at 02:19 AM ---------- Previous post was at 02:16 AM ----------
android_fury said:
Something is going on with my phone that doesn't let me flash anything. I was on CM14 with TWRP 3.0.2-22. I did an advanced wipe and I think I selected "system" there. I didn't really see it until I started the wipe. Now I can't boot into anything because I wiped the rom and am stuck without being able to flash anything.
Some things I tried:
When I flash the official CM14, it starts the flashing process, but doesn't get past that system flashing.
Flashing an OxygenOS-based rom (OP3Lite 2.4.2) got stuck on "extracting system."
Restoring a CM13 nandroid backup I had from before I installed CM14 finished restoring, but the phone won't boot into Android.
I ran out of ideas. How can I restore my phone?
Click to expand...
Click to collapse
Did you allow modifications in twrp ? Try to mount system in recovery before flashing / restoring
I ended up fixing it. I went to TWRP to do a regular wipe and saw the option to format partitions. I formatted system and it allowed me to reinstall roms. I flashed CM13 and CM14 with no issues. Thank you all for the suggestions.
Sent from my ONEPLUS A3000 using XDA-Developers mobile app
Hi! I went into the latest TWRP recovery with unlocked bootloader, and I wiped system, cache, dalvik and data. Then I flashed the proper vendor image, the ROM zip, Gapps and then Elemental X kernel. However, when I reboot, it just boots me into TWRP recovery. I have tried wiping dalvik cache and cache. I then tried restoring a nandroid, but it just got stuck on the Google screen. Didn't even get to the colored dots screen. I ended up flashing factory image, but I would like to get my Nandroids working and this ROM. Please help! Thanks
I'm no expert but I think it might be happening because of encryption. Did you disable encryption before doing all this stuff?
Aman301582 said:
I'm no expert but I think it might be happening because of encryption. Did you disable encryption before doing all this stuff?
Click to expand...
Click to collapse
Encryption in stock Android? As far as I know, I can't turn it off. It says that the device is encrypted in settings. I think nougat forces encryption.
Unless maybe there's a patched kernel that can do that?
NateDev473 said:
Encryption in stock Android? As far as I know, I can't turn it off. It says that the device is encrypted in settings. I think nougat forces encryption.
Unless maybe there's a patched kernel that can do that?
Click to expand...
Click to collapse
I dont think is your problem , im encrypted and never have issues with twrp! Never!! What version of twrp you running? Theres an unofficial kicking around that is much better than official! Maybe you got a bad download! I would redownload all, find and download unofficial twrp 3.0.2.3 I believe. Let your phone boot before you flash custom kernel, thats always worked great for me. The latest official twrps 3022 and 3021 both have nandroid restore issues as well efs restore issues that could ruin your day
Format data and system (format, not wipe) and try installing it again. Should work
OK, thanks
neth15 said:
Format data and system (format, not wipe) and try installing it again. Should work
Click to expand...
Click to collapse
Only data and system? Not cache and dalvik like the purenexus install guide says?
NateDev473 said:
Only data and system? Not cache and dalvik like the purenexus install guide says?
Click to expand...
Click to collapse
Ofc wipe all partitions, but these two also format.
neth15 said:
Ofc wipe all partitions, but these two also format.
Click to expand...
Click to collapse
What's the difference between wipe and format? On TWRP there is only WIPE for all partitions, but a format data button.
NateDev473 said:
What's the difference between wipe and format?
Click to expand...
Click to collapse
Wipe just deletes all data on the partition. Format makes the partition again, therefore it removes encryption, repairs potential problems etc. Format data has dedicated button in TWRP, for formatting System go to Advanced Wipe, check system, tap on Partition details, check EXT4 and perform format.
neth15 said:
Wipe just deletes all data on the partition. Format makes the partition again, therefore it removes encryption, repairs potential problems etc. Format data has dedicated button in TWRP, for formatting System go to Advanced Wipe, check system, tap on Partition details, check EXT4 and perform format.
Click to expand...
Click to collapse
There is no Partition details button. Just fix partition or something like that.
NateDev473 said:
There is no Partition details button. Just fix partition or something like that.
Click to expand...
Click to collapse
Repair or Change filesystem? Yeah, it should be that.
neth15 said:
Repair or Change filesystem? Yeah, it should be that.
Click to expand...
Click to collapse
OK, I will do that. Thanks Just to clarify, I format data and system, and wipe cache and dalvik?
A Thought
Dunno if this will help, but whenever I flash a ROM/kernel combo, I always flash the ROM/gapps, boot up with whatever kernel is included in ROM to make sure it boots properly, and then after successful boot flash EX kernel through TWRP.
OK, so I formatted DATA and SYSTEM, and I wiped CACHE and DALVIK. I then flashed the proper vendor image, pushing it to the device with adb push, and then adb sideload for the pure nexus ROM. It's currently installing. Then, I will adb sideload the gapps ZIP file. Then I'll reboot and see if it worked
EDIT: It just said "No OS installed"
EDIT 2: Just flashed the ROM again, and it is showing the boot animation. This time I did not do Gapps. I also wiped and formatted everything again. Hope all goes well.
EDIT 3: The ROM booted fine. Glad all is working now
NateDev473 said:
OK, so I formatted DATA and SYSTEM, and I wiped CACHE and DALVIK. I then flashed the proper vendor image, pushing it to the device with adb push, and then adb sideload for the pure nexus ROM. It's currently installing. Then, I will adb sideload the gapps ZIP file. Then I'll reboot and see if it worked
EDIT: It just said "No OS installed"
EDIT 2: Just flashed the ROM again, and it is showing the boot animation. This time I did not do Gapps. I also wiped and formatted everything again. Hope all goes well.
EDIT 3: The ROM booted fine. Glad all is working now
Click to expand...
Click to collapse
Good job You're welcome
neth15 said:
Good job You're welcome
Click to expand...
Click to collapse
So I had flashed the ROM with no Google Apps or anything, just the ROM. But when I add a Google Account, I can't because it says Google Play Services has stopped. I just noticed that the build number is one of a Nexus 6P, and the vendor image is different, the one I manually flashed.
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