Hi, I just bought a second hand OP3, the version installed was the last Open BETA 26.
So everything was working properly but when I reset it the phone was extremly laggy, even the bootamination.
And when the phone booted-up it was very laggy and after some seconds it crash (freeze and turn off after few seconds).
I tried a lot of flashs :
- ADB slideload (impossible to flash a firmware, sometimes the command don't work and when it works it stops after 47% or 97/94%
- The ultimate flash for bricked devices (https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/), the flash worked, but the freeze problem was still here even if the version flashed was OxygenOS 3.1.2
- From this firmware I managed to flash OxygenOS 4.5.1 (the last stable one) with ADB Slideload and same problem again.
- I tried to lock / unlock the bootloader but changed nothing, I even tried to flash TWRP to flash a custom rom but impossible to find a working version.
Now I need the help of XDA Gods !
Sorry for my bad english :silly:
The worst case scenario here is that you have a bad case of corrupted or broken storage (by 'storage' I mean the entirety of the phone's NAND storage) — have you tried wiping /data (labeled as Internal Storage in TWRP) or switching its filesystem back and forth (so, for example, if you have F2FS you'd need to switch to EXT4).
I'd say you might want to start backing up whatever data left in the phone.
try turning off advanced 4g mode. I have the same problem when flashing oos (cpu usage at 50%+ when idle) and this helped me.
F4uzan said:
The worst case scenario here is that you have a bad case of corrupted or broken storage (by 'storage' I mean the entirety of the phone's NAND storage) — have you tried wiping /data (labeled as Internal Storage in TWRP) or switching its filesystem back and forth (so, for example, if you have F2FS you'd need to switch to EXT4).
I'd say you might want to start backing up whatever data left in the phone.
Click to expand...
Click to collapse
Thanks for your answer, I didn't find a working version of TWRP to test (every TWRP i tried was black screen or stuck on TWRP logo) but I already tried full wipes from stock recovery (very very many times), I will try all TWRP avaliables and try your method.
But now I think the problem is the worst case that you said :/
hellcat50 said:
try turning off advanced 4g mode. I have the same problem when flashing oos (cpu usage at 50%+ when idle) and this helped me.
Click to expand...
Click to collapse
Thx i'll try if the phone don't freeze before I access settings^^
where is exacly this option ?
Bryandu13 said:
Thanks for your answer, I didn't find a working version of TWRP to test (every TWRP i tried was black screen or stuck on TWRP logo) but I already tried full wipes from stock recovery (very very many times), I will try all TWRP avaliables and try your method.
But now I think the problem is the worst case that you said :/
Click to expand...
Click to collapse
Definitely try all available TWRP and see if any of them works. If the storage actually broke, it'd be pretty catastrophic and would be hard to recover or manually fix.
F4uzan said:
Definitely try all available TWRP and see if any of them works. If the storage actually broke, it'd be pretty catastrophic and would be hard to recover or manually fix.
Click to expand...
Click to collapse
Okay i'll focus on it ! Thanks !
Bryandu13 said:
Okay i'll focus on it ! Thanks !
Click to expand...
Click to collapse
https://forum.xda-developers.com/devdb/project/dl/?id=27068
the twrp i recommned
Bryandu13 said:
Thx i'll try if the phone don't freeze before I access settings^^
where is exacly this option ?
Click to expand...
Click to collapse
It is where you can set up apn and switch data roaming
I have the exact same problem
Changing the data format doesnt work for me.
Skinpipe said:
https://forum.xda-developers.com/devdb/project/dl/?id=27068
the twrp i recommned
Click to expand...
Click to collapse
Thanks, this TWRP works !
F4uzan said:
Definitely try all available TWRP and see if any of them works. If the storage actually broke, it'd be pretty catastrophic and would be hard to recover or manually fix.
Click to expand...
Click to collapse
I tried change everything to EXT4 (only DATA wasn't EXT4 but "emmc") but it doesn't worked
zainhateszayn said:
Changing the data format doesnt work for me.
Click to expand...
Click to collapse
That's sad :/
I hope we'll find a solution
Bryandu13 said:
I tried change everything to EXT4 (only DATA wasn't EXT4 but "emmc") but it doesn't worked
Click to expand...
Click to collapse
Unbrick guide method 2 doesn't work? I'll say start contacting Oneplus.
Puddi_Puddin said:
Unbrick guide method 2 doesn't work? I'll say start contacting Oneplus.
Click to expand...
Click to collapse
Yes, it don't work...
I don't know about conctacting OnePlus because it's a second hand model without bill, only the box.
Now I noticed that is was possible to flash any OxygenOS ROM or any OxygenOS based ROM with TWRP (the problem is still here) but impossible to get a booting AOSP based or any no-OxygenOS based ROM.
I'm trying to get the bill to get the help from OnePlus customer service.
So my phone is dead right ? We can't even find a motherboard on internet :/
Can you try
"fastboot format userdata"
"fastboot format cache",
"fastboot format system",
" fastboot erase recovery"
"fastboot reboot bootloader"
commands than flashing Oxygen recovery w/fastboot than flashing open beta 26 with Oxygen recovery? This may help.
qhsusb_bulk said:
Can you try
"fastboot format userdata"
"fastboot format cache",
"fastboot format system",
" fastboot erase recovery"
"fastboot reboot bootloader"
commands than flashing Oxygen recovery w/fastboot than flashing open beta 26 with Oxygen recovery? This may help.
Click to expand...
Click to collapse
Thanks I will try, but I don't understand your last sentence "commands than flashing Oxygen recovery w/fastboot than flashing open beta 26 with Oxygen recovery?"
Bryandu13 said:
Thanks I will try, but I don't understand your last sentence "commands than flashing Oxygen recovery w/fastboot than flashing open beta 26 with Oxygen recovery?"
Click to expand...
Click to collapse
It is your choice, you can copy zip with TWRP then flash Oxygen recovery via fastboot or just sideload it with ADB.
Related
Hello guys,
As stated in the title, I can not boot into recovery since I flashed CM 14.1. I already tried reflashing TWRP, booting TWRP via fastboot, using another, more recent TWRP image.
This is rather urgent, since, although I can boot CM 14.1 without any problem, I forgot to do a Titanium Backup of two apps, so I have to restore a nandroid backup to get those back, which is kind of hard, without access to TWRP. Using TWRP Explorer is out of question, since that, as far as I know, does not work with encrypted backups.
Flashing via Flashify does not work either.
I just tried with the most recent CM Recovery, that does work, but that does not really help, since that won't restore TWRP Backups..
Greetings
jcgruenhage
delete
Just flash twrp again!?
Flash the twrp in the following link https://www.androidfilehost.com/? using flashify from play store .This helped me
daleski75 said:
Just flash twrp again!?
Click to expand...
Click to collapse
That did not work, at least not with the official TWRP. Flashing this TWRP gave me TWRP back, but now restoring the Backup somehow did not work as expected, the old CM 14.1 unofficial build that is in that backup won't boot.
I'll try only restoring the data part onto the official build, is there anything else you can recommend? Another firmware? Something?
Oh and by the way, thank you, for helping here and for you CM 14.1 builds, somehow I couldn't build CM 14.1 and 14, so having your builds was really helpful.
What version of OOS was you on prior to flashing CM14.1?
daleski75 said:
What version of OOS was you on prior to flashing CM14.1?
Click to expand...
Click to collapse
Directly upon receiving my OP3 I flashed CM13, that was in August, so 3.2.4 I guess, and I flashed the firmware of 3.2.6 before flashing Takers and your CM14 and later 14.1 builds.
TWRP behaves funny, the progress of restoring Data is already at 138%, 6800MB of 4899MB, the calculation is not taking compression into account I guess?
LOOOL, I have booted into the official CM14.1 with the old data, no fc or anything, but my pattern does not work anymore. same pattern as before, won't be accepted.
Never seen that issue before what happens if you reboot into the bootloader and then connect the phone to your pc and type fastboot boot <name of recovery> does it boot up?
Of course replace the < > with the name of the img file.
daleski75 said:
Never seen that issue before what happens if you reboot into the bootloader and then connect the phone to your pc and type fastboot boot <name of recovery> does it boot up?
Of course replace the < > with the name of the img file.
Click to expand...
Click to collapse
Yes, TWRP works now, but the backed up unofficial CM 14.1 does not boot.
But, only this TWRP works, booting the official TWRP does not work.
I could probably just use the TWRP file manager to extract the few files from the data partition that I need, but this is a workaround and not a fix, and that is not desired in most cases. Fixing it is hard without someone that still has a broken system.
jcgruenhage said:
Yes, TWRP works now, but the backed up unofficial CM 14.1 does not boot.
But, only this TWRP works, booting the official TWRP does not work.
I could probably just use the TWRP file manager to extract the few files from the data partition that I need, but this is a workaround and not a fix, and that is not desired in most cases. Fixing it is hard without someone that still has a broken system.
Click to expand...
Click to collapse
Yup thats the one I am using as well.
daleski75 said:
Yup thats the one I am using as well.
Click to expand...
Click to collapse
Do you know how one would debug something like that? I have nothing but the splash screen in the beginning and then a black screen
I will just flash CM 14.1 and manually extract my OTP tokens from the data backup, so I don't really need to debug that, but it would probably help determine the cause and properly fix it for the future.
Ask for the link
daleski75 said:
Yup thats the one I am using as well.
Click to expand...
Click to collapse
May I ask which one? the link is dead ...
I am having the same problem, i can't boot into recovery and cant find a way to flash it.
Can someone explain me how to?
ChrisDiM said:
I am having the same problem, i can't boot into recovery and cant find a way to flash it.
Can someone explain me how to?
Click to expand...
Click to collapse
Sorry to hear that. You have to use Qualcomm Drivers to reset your cellphone
Same issue here. Whenever I try to boot into recovery it just goes straight back to the bootloader/fastboot.
**** me, what do I do?
I try "fastboot format userdata" but after i have the same problem with TWRP-3.0.2-1.28
jackalsin said:
Sorry to hear that. You have to use Qualcomm Drivers to reset your cellphone
Click to expand...
Click to collapse
I just found a guide to reset my phone using Qualcomm but my phone doesn't show up on device manager + since this morning my op3 doesn't start up anymore and doesn't react when i plug the charger in.
ChrisDiM said:
I just found a guide to reset my phone using Qualcomm but my phone doesn't show up on device manager + since this morning my op3 doesn't start up anymore and doesn't react when i plug the charger in.
Click to expand...
Click to collapse
Hold power button for at least a minute. It's what I did and fixed it.
DevSquad said:
Hold power button for at least a minute. It's what I did and fixed it.
Click to expand...
Click to collapse
after doing this it showed the OP logo for a few seconds and shut off again :/
Its really a bad moment for me because i had to call a lot a people today and now i can't even start up my phone
ChrisDiM said:
after doing this it showed the OP logo for a few seconds and shut off again :/
Its really a bad moment for me because i had to call a lot a people today and now i can't even start up my phone
Click to expand...
Click to collapse
Can you get into fastboot?
If so, you can sideload a working TWRP via there.
After installing oos beta 8 nougats I made encryption and I made pin code but after restarting the phone when I write the pin code it gives me wrong pin and also gives me wrong pin when trying to open twrp , any solution please??
eid_elageeb said:
After installing oos beta 8 nougats I made encryption and I made pin code but after restarting the phone when I write the pin code it gives me wrong pin and also gives me wrong pin when trying to open twrp , any solution please??
Click to expand...
Click to collapse
You need modified TWRP 3.0.2-28 to get TWRP working with Beta 8. I had the same issue witrh my installation.
Also you need to make sure to remove your lock screen, then you will be able to use TWRP
strumaticjoker2 said:
Also you need to make sure to remove your lock screen, then you will be able to use TWRP
Click to expand...
Click to collapse
even without protection, twrp asking pw, need to erase use data and system.
I solved the problem by using oneplus 3 toolkit " Force Decryption Device" option and it works well, Thank you for your help guys
eid_elageeb said:
I solved the problem by using oneplus 3 toolkit " Force Decryption Device" option and it works well, Thank you for your help guys
Click to expand...
Click to collapse
I got the same issue, cannot decrypt the internal storage.
I am using TWRP3.0.2.1-28
What is your action, just run "Force Decryption Device" by using Toolkit v.3.6
and what recovery are you using ?
Thx
yiphoming said:
I got the same issue, cannot decrypt the internal storage.
I am using TWRP3.0.2.1-28
What is your action, just run "Force Decryption Device" by using Toolkit v.3.6
and what recovery are you using ?
Thx
Click to expand...
Click to collapse
First I flash the stock recovery by toolkit and then make force decryption device and then I flash twrp 3.0.2.1-28 and It works, but you should to know that everything on your phone will be erased
eid_elageeb said:
First I flash the stock recovery by toolkit and then make force decryption device and then I flash twrp 3.0.2.1-28 and It works, but you should to know that everything on your phone will be erased
Click to expand...
Click to collapse
No luck, can erase the storage, but it is still in encrypted.
yiphoming said:
No luck, can erase the storage, but it is still in encrypted.
Click to expand...
Click to collapse
I'm using latest modified TWRP 3.0.2-28 + OOS Beta 8. I have a protected lockscreen (fingerprint / pin) and pin is needed to start the device.
I flashed TWRP, wiped everything and changed "DATA" filesystem to "F2FS" and flashed the rom (clean installation)
I have full acces when using TWRP.
No need to force decryption or anything...
LS.xD said:
I'm using latest modified TWRP 3.0.2-28 + OOS Beta 8. I have a protected lockscreen (fingerprint / pin) and pin is needed to start the device.
I flashed TWRP, wiped everything and changed "DATA" filesystem to "F2FS" and flashed the rom (clean installation)
I have full acces when using TWRP.
No need to force decryption or anything...
Click to expand...
Click to collapse
It doesn't work though, if you installed dirty and just upgraded from MM. TWRP keeps asking for password and doesn't accept it, even if I change to password (else using PIN) in the system.
rarog said:
It doesn't work though, if you installed dirty and just upgraded from MM. TWRP keeps asking for password and doesn't accept it, even if I change to password (else using PIN) in the system.
Click to expand...
Click to collapse
I came from OOS 3.2.8 running already with F2FS and did a dirty flash to the Nougat Beta.
All with the -1.28 TWRP and have no issues going into TWRP and it accepts my pin.
AcmE85 said:
I came from OOS 3.2.8 running already with F2FS and did a dirty flash to the Nougat Beta.
All with the -1.28 TWRP and have no issues going into TWRP and it accepts my pin.
Click to expand...
Click to collapse
This is the way I went, just yet being on ext4. Could it be a difference, if you flash or if you just boot TWRP? I'm only booting instead of flashing, so I retain my recovery, as I didn't see the new Oxygen recovery for OOS4 in the wild yet.
rarog said:
This is the way I went, just yet being on ext4. Could it be a difference, if you flash or if you just boot TWRP? I'm only booting instead of flashing, so I retain my recovery, as I didn't see the new Oxygen recovery for OOS4 in the wild yet.
Click to expand...
Click to collapse
You probably need an older version for ext4. The last one working on ext4 when I did the switch to f2fs was -1.25 if I remember correctly.
After the switch to f2fs I had to flash 1.28 or the recovery wouldn't accept my pin anymore.
LS.xD said:
I'm using latest modified TWRP 3.0.2-28 + OOS Beta 8. I have a protected lockscreen (fingerprint / pin) and pin is needed to start the device.
I flashed TWRP, wiped everything and changed "DATA" filesystem to "F2FS" and flashed the rom (clean installation)
I have full acces when using TWRP.
No need to force decryption or anything...
Click to expand...
Click to collapse
Do you also get the dm-verity bootscreen?
AcmE85 said:
You probably need an older version for ext4. The last one working on ext4 when I did the switch to f2fs was -1.25 if I remember correctly.
After the switch to f2fs I had to flash 1.28 or the recovery wouldn't accept my pin anymore.
Click to expand...
Click to collapse
Hm... Interesting, do you have a link? And perhaps a link to a thread with all the available versions? I searched, but found only several tutorial threads with just one or another version linked, no thread for specific modified version.
AcmE85 said:
Do you also get the dm-verity bootscreen?
Click to expand...
Click to collapse
As far as I know - no.
When would this error message pop up?
LS.xD said:
As far as I know - no.
When would this error message pop up?
Click to expand...
Click to collapse
Right at boot before or after the screen which shows that the bootloader is unlocked.
AcmE85 said:
Right at boot before or after the screen which shows that the bootloader is unlocked.
Click to expand...
Click to collapse
No such error message for me
LS.xD said:
No such error message for me
Click to expand...
Click to collapse
Did you flash SuperSU?
AcmE85 said:
Did you flash SuperSU?
Click to expand...
Click to collapse
Yes, 2.78 SR5
I have done format userdata in fastboot but my phone still shows up as encrypted. Flashed 3.0.2-1.28 and I still get a password screen when booting to recovery. Not really sure what else I can do.
No matter how many resets I just can't boot into my recovery or the OS. If I try to reboot the system all that happens is the TWRP splash screen pops up, hangs there for a while, reboots to the splash screen again and repeats. Is this a brick? The most I can do is get into fastboot mode. Please, any advice would be very much appreciated. I feel like a total dipstick. The ROM I'm on is Resurrection Remix official N and the TWRP version is 3.1.1-0. This combo was never an issue before.
showofdeth said:
No matter how many resets I just can't boot into my recovery or the OS. If I try to reboot the system all that happens is the TWRP splash screen pops up, hangs there for a while, reboots to the splash screen again and repeats. Is this a brick? The most I can do is get into fastboot mode. Please, any advice would be very much appreciated. I feel like a total dipstick. The ROM I'm on is Resurrection Remix official N and the TWRP version is 3.1.1-0. This combo was never an issue before.
Click to expand...
Click to collapse
Use the unbrick guide method 2. Make sure you follow ALL steps otherwise it will not work..
Feel free to ask any questions!
First, go in FastBoot mode & reflash recovery from PC.
null0seven said:
First, go in FastBoot mode & reflash recovery from PC.
Click to expand...
Click to collapse
Tried that using different TWRP versions but it didn't work. My issue still persisted.
Puddi_Puddin said:
Use the unbrick guide method 2. Make sure you follow ALL steps otherwise it will not work..
Feel free to ask any questions!
Click to expand...
Click to collapse
Thanks but that that seemed a bit daunting so after MUCH searching I found a thread with a very simple fix. In fastboot type the command "fastboot format cache" and "fastboot format user data". I lost all my stuff but I'm up and running again.
However, I have a new issue. "system" is taking up 29gb of space. What's that about?
showofdeth said:
Thanks but that that seemed a bit daunting so after MUCH searching I found a thread with a very simple fix. In fastboot type the command "fastboot format cache" and "fastboot format user data". I lost all my data but I'm up and running again.
However, I have a new issue. "system" is taking up 29gb of space. What's that about?
Click to expand...
Click to collapse
Try the latest OOS 4.2.5.. It had some fixes
Puddi_Puddin said:
Try the latest OOS 4.2.5.. It had some fixes
Click to expand...
Click to collapse
I like OOS and all but I like the customisation of RR more. Cheers though.
You did even better. Now you have a Clean phone, because you wipe it all.
It's from your rom. I'm on Oos 4.1.5. Look at mine.
null0seven said:
You did even better. Now you have a Clean phone, because you wipe it all.
It's from your rom. I'm on Oos 4.1.5. Look at mine.
Click to expand...
Click to collapse
Can you install oos through TWRP? Maybe as recommended it may fix my storage issue.
How else ?
Never did Fastboot sideload.
I instal any rom ONLY in TWRP.
showofdeth said:
No matter how many resets I just can't boot into my recovery or the OS. If I try to reboot the system all that happens is the TWRP splash screen pops up, hangs there for a while, reboots to the splash screen again and repeats. Is this a brick? The most I can do is get into fastboot mode. Please, any advice would be very much appreciated. I feel like a total dipstick. The ROM I'm on is Resurrection Remix official N and the TWRP version is 3.1.1-0. This combo was never an issue before.
Click to expand...
Click to collapse
showofdeth said:
Tried that using different TWRP versions but it didn't work. My issue still persisted.
Click to expand...
Click to collapse
At this point I'm sure it's a firmware related issue.
Download and install latest one here: https://forum.xda-developers.com/oneplus-3/how-to/radio-modem-collection-flashable-zips-t3468628
Stable or Open Beta, doesn't matter.
Then... what TWRP have you tried? For custom roms is highly recommended the blu_spark variant.
Because the stock TWRP is good only for OOS-based firmware, with other configurations it may not boot up at all.
showofdeth said:
Thanks but that that seemed a bit daunting so after MUCH searching I found a thread with a very simple fix. In fastboot type the command "fastboot format cache" and "fastboot format user data". I lost all my stuff but I'm up and running again.
However, I have a new issue. "system" is taking up 29gb of space. What's that about?
Click to expand...
Click to collapse
What have you done? ?
Two theories:
1) You've done encryption via custom rom.
2) After formatting /data via fastboot commands, you've not installed and booted up once latest OOS rom.
Until doing that, device will read 25 GB of free space, both in recovery and system.
I don't know the reason of that trouble.
So you have to:
1) Install latest OOS firmware (via TWRP / adb sideload);
2) Bootup once the system: be sure to choose a pattern required at bootup, for the rest skip wizard as fast as possible;
3) Install latest TWRP blu_spark via fastboot command;
4) From recovery, wipe everything and flash Resurrection Remix.
Tell me if you solve ?
Simone98RC said:
At this point I'm sure it's a firmware related issue.
Download and install latest one here: https://forum.xda-developers.com/oneplus-3/how-to/radio-modem-collection-flashable-zips-t3468628
Stable or Open Beta, doesn't matter.
Then... what TWRP have you tried? For custom roms is highly recommended the blu_spark variant.
Because the stock TWRP is good only for OOS-based firmware, with other configurations it may not boot up at all.
What have you done?
Two theories:
1) You've done encryption via custom rom.
2) After formatting /data via fastboot commands, you've not installed and booted up once latest OOS rom.
Until doing that, device will read 25 GB of free space, both in recovery and system.
I don't know the reason of that trouble.
So you have to:
1) Install latest OOS firmware (via TWRP / adb sideload);
2) Bootup once the system: be sure to choose a pattern required at bootup, for the rest skip wizard as fast as possible;
3) Install latest TWRP blu_spark via fastboot command;
4) From recovery, wipe everything and flash Resurrection Remix.
Tell me if you solve
Click to expand...
Click to collapse
I've fixed everything. Flashed a OOS based ROM then did a factory wipe in TWRP and then installed a new RR ROM. Panic over. Sorted.
I have a oneplus 3 with Oxygen Os 5.0.1 with the bootloader unlocked and twrp 3.2.1 installed. After flashing an erroneous zip my device went into bootloop in TWRP every time I rebooted it returned to TWRP.
To try to solve it I format my device, the bootloop disappeared but now when I start the system it appears the logo of oneplus loads the system but it appears in black screen. The system I think works because I can take screenshots even if it appears in black and if I press the power button if the option to turn off or restart appears.
Some solution for this problem thanks for your help!
BlackDeath XVI said:
I have a oneplus 3 with Oxygen Os 5.0.1 with the bootloader unlocked and twrp 3.2.1 installed. After flashing an erroneous zip my device went into bootloop in TWRP every time I rebooted it returned to TWRP.
To try to solve it I format my device, the bootloop disappeared but now when I start the system it appears the logo of oneplus loads the system but it appears in black screen. The system I think works because I can take screenshots even if it appears in black and if I press the power button if the option to turn off or restart appears.
Some solution for this problem thanks for your help!
Click to expand...
Click to collapse
You will have to reflash the device. Screenshot is built into the kernel so that means nothing. Just reflash the device from scratch and start from the beginning.
zelendel said:
You will have to reflash the device. Screenshot is built into the kernel so that means nothing. Just reflash the device from scratch and start from the beginning.
Click to expand...
Click to collapse
and how i do it that it's the question? thx for the info!
BlackDeath XVI said:
and how i do it that it's the question? thx for the info!
Click to expand...
Click to collapse
By doing the research. If you had TWRP on your device then you should know what you are doing. If not and you just watched some stupid videos. Then do some research and learn what you are doing.
BlackDeath XVI said:
and how i do it that it's the question? thx for the info!
Click to expand...
Click to collapse
Wipe system, reflash OOS, or if you are, using a custom rom reflash the rom en gapps and this solves 99% of your issues. Next time backup boot and system before flashing stuff.
Puddi_Puddin said:
Wipe system, reflash OOS, or if you are, using a custom rom reflash the rom en gapps and this solves 99% of your issues. Next time backup boot and system before flashing stuff.
Click to expand...
Click to collapse
the problem is that I do not have any rom in my internal memory and my device Oneplus 3 does not have sd card.I tried to load it with adb sideload but I can not have any problem with my adb. Thanks for your help, we appreciate a lot
BlackDeath XVI said:
the problem is that I do not have any rom in my internal memory and my device Oneplus 3 does not have sd card.I tried to load it with adb sideload but I can not have any problem with my adb. Thanks for your help, we appreciate a lot
Click to expand...
Click to collapse
Install proper drivers. If you are using Win 10, it is a good idea to disable driving signing before attempting to install proper drivers. You should be able to flash through adb.
BlackDeath XVI said:
the problem is that I do not have any rom in my internal memory and my device Oneplus 3 does not have sd card.I tried to load it with adb sideload but I can not have any problem with my adb. Thanks for your help, we appreciate a lot
Click to expand...
Click to collapse
Use "adb push filename directory" so. Adb push rom.zip /sdcard/ and then the file will be pushed to the folder /sdcard/.
Hey, I just unlocked my bootloader after waiting for the 7 days today I wanted to install the MIUI EU, and i follow the steps that they have on their website, installed and boot into recovery mode TWRP format data, and install the ROM that i downloaded, after that the wipe on the cache. When i rebooted my phone he didn't boot and was stuck on POCO screen. After 1 hour it was stuck on that, I decided to try and flash stock firmware with miflash tool, did the steps and after 604 seconds it shows success on the result but it doesn't boot the same thing stuck on POCO screen.
You need to Format data. Not cache.
Then the phone will boot up just fine.
Go, do it again.
Try to flash it using miflash again.
Then Boot TWRP, then flash it again + ( FORMAT DATA)
laid1995 said:
Boot TWRP, then install it again.
Click to expand...
Click to collapse
I'm facing the issue that I cannot access the internal storage to flash the ROM now or paste it again
Don't freak out. Your phone is fine. As long as you can boot into Fastboot. Then you are fine.
skullgnik said:
I'm facing the issue that I cannot access the internal storage to flash the ROM now or paste it again
Click to expand...
Click to collapse
Try otg.
laid1995 said:
Try otg.
Click to expand...
Click to collapse
otg? sorry, I'm kinda new to this situation. I've flashed many custom ROMs before but have never had an issue. Yes, my phone can boot into Fastboot without a problem. Right now I'm downloading a different version of the stock firmware (IDK i think it could fix the not booting problem after the miflash tool) if it works i will leave it with the stock firmware if not i will try to find a solution to fix the issue of not accessing the internal storage on twrp
skullgnik said:
otg? sorry, I'm kinda new to this situation. I've flashed many custom ROMs before but have never had an issue. Yes, my phone can boot into Fastboot without a problem. Right now I'm downloading a different version of the stock firmware (IDK i think it could fix the not booting problem after the miflash tool) if it works i will leave it with the stock firmware if not i will try to find a solution to fix the issue of not accessing the internal storage on twrp
Click to expand...
Click to collapse
I had the same issue before. Just reflash the stock (be aware, don't select "Wipe data and lock")
When the phone boots up. Flash twrp or just boot it. Then flash Xiaomi EU then FORMAT DATA.
Everything will be just fine.
laid1995 said:
I had the same issue before. Just reflash the stock (be aware, don't select "Wipe data and lock")
When the phone boots up. Flash twrp or just boot it. Then flash Xiaomi EU then FORMAT DATA.
Everything will be just fine.
Click to expand...
Click to collapse
What option should I select then?
skullgnik said:
What option should I select then?
Click to expand...
Click to collapse
Please tell me you didn't select " wipe and lock " before !
i did
laid1995 said:
Please tell me you didn't select " wipe and lock " before
Click to expand...
Click to collapse
skullgnik said:
i did
Click to expand...
Click to collapse
welp...... Try unlocking the bootloader again
Do as he says. Hopefully it gets unlocked.
laid1995 said:
Do as he says. Hopefully it gets unlocked.
Click to expand...
Click to collapse
I already booted with another stock firmware, i just re-downloaded and it worked guess for now i will stick with the stock one. Thank you both for the help!
You're welcome.
As you wish, just try, at least to unlock bootloader since you're still fresh. As to make sure that it can be unlocked.
skullgnik said:
I already booted with another stock firmware, i just re-downloaded and it worked guess for now i will stick with the stock one. Thank you both for the help!
Click to expand...
Click to collapse
you don't have to use memeui, official EvolutionX just released today!
JustAnAverageGuy_19 said:
you don't have to use memeui, official EvolutionX just released today!
Click to expand...
Click to collapse
I will think later this day about installing a custom ROM. but I don't hate miui as much as people usually hate, I find some things extremely useful I just don't like some UI esthetics i prefer the minimalist look of pure android. But some things like the cloning apps are very handy to me. Some bugs that are present atm on custom ROMs for this device like the double-tap to wake up are very negative to me because I have always used that feature since 2014 and I'm extremely used to it.