Develop Bugs

One Plus 3 no OS, no USB Debug, locked Bootloader, not rooted and stock recovery

My One Plus 3 managed to delete its own Operating System, USB Debugging wasnt enabled, the Bootloader is not unlocked, its not rooted either and I dont have a custom recovery like TWRP installed. I tried to flash it wtih the adb console commands but it stops at some percentage and the device says that the installation failed (tried this with cm, oxygen and pacman). I tried to install TWRP over fastboot but cant manage it because USB Debugging isnt activated. I dont know what to do and need help
PS: Hope this Post is in the right thread

SolomonOdonkah said:
My One Plus 3 managed to delete its own Operating System, USB Debugging wasnt enabled, the Bootloader is not unlocked, its not rooted either and I dont have a custom recovery like TWRP installed. I tried to flash it wtih the adb console commands but it stops at some percentage and the device says that the installation failed (tried this with cm, oxygen and pacman). I tried to install TWRP over fastboot but cant manage it because USB Debugging isnt activated. I dont know what to do and need help
PS: Hope this Post is in the right thread
Click to expand...
Click to collapse
bro, do you even google?
http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700

bombaglad said:
bro, do you even google?
http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
Click to expand...
Click to collapse
I did but didn't found that thread, but thanks mate

SolomonOdonkah said:
I did but didn't found that thread, but thanks mate
Click to expand...
Click to collapse
that is literally the first thing on the list if you google "oneplus 3 unbrick" but i'm glad i helped, that thread saved my ass several times already

[Softbrick] Every ROM stuck in Bootloop

Hello,
I really dont know what to do anymore.
No matter which ROM I flash, I always get stuck in a bootloop. I always wait 20-25 for a boot, but it doesnt pass the bootanimation.
Here is what happened:
My PC didnt recognize my phone anymore even though I didnt change any driver settings or something like that. Same with other PCs, not even showing up in device manager at all. So I thought I messed up some settings in my phone, thats why I wiped data, system, cache, internal store, then pushed a new ROM to my phone via USB OTG, but it doesnt boot at all. Phone still doesnt get recognized by any pc, not even in TWRP or bootloader.
Here are the things I tried so far:
- Ressurrection Remix (latest 3 versions) with OpenGapps
- Lineage OS with DynamicGapps
- both of them without any gapps
- OMNI Rom with DynamicGapps
I also did a factory reset before every flash. After 20 minutes of bootloop I also tried a 2nd boot for 20 minutes...nothing.
Since I cant access my phone from PC I cant flash stock ROM (or is it possible to flash it via TWRP?). I guess I just wiped something that I shouldnt have wiped. Does anyone have an idea what else I could try?

I had something similar happen to my 5x a while back. After fiddling with drivers/device manager etc, I found this on net which actually worked for me:
Solution 5 – Uninstall Android drivers if PC not recognizing phone
Sometimes you might not have the latest drivers, or your drivers might not be properly installed, so in order to fix issues with Android devices and Windows 10, it’s advised that you uninstall your Android drivers. To do so, follow these steps:
Connect your Android device to your computer and open Device Manager.
In Device Manager locate your Android device. Usually it’s located in Other Devices or in Portable devices section, but the location might be different on your computer.
Right click the device and choose Uninstall.
uninstall-driver
After the drivers have been uninstalled, disconnect your Android device.
Reconnect it again, and wait for Windows 10 to install its drivers again.
Check if your Android device is now recognized.
---------- Post added at 06:09 PM ---------- Previous post was at 06:06 PM ----------
Above post fixed my driver/PC not recognizing phone issue. As far as your bootloop issue, I'm assuming your bootloader is still unlocked, right? If so, and if above fix works where PC recognizes phone, try flashing google factory images via fastboot commands.

jrotert said:
I had something similar happen to my 5x a while back. After fiddling with drivers/device manager etc, I found this on net which actually worked for me:
Solution 5 – Uninstall Android drivers if PC not recognizing phone
Sometimes you might not have the latest drivers, or your drivers might not be properly installed, so in order to fix issues with Android devices and Windows 10, it’s advised that you uninstall your Android drivers. To do so, follow these steps:
Connect your Android device to your computer and open Device Manager.
In Device Manager locate your Android device. Usually it’s located in Other Devices or in Portable devices section, but the location might be different on your computer.
Right click the device and choose Uninstall.
uninstall-driver
After the drivers have been uninstalled, disconnect your Android device.
Reconnect it again, and wait for Windows 10 to install its drivers again.
Check if your Android device is now recognized.
---------- Post added at 06:09 PM ---------- Previous post was at 06:06 PM ----------
Above post fixed my driver/PC not recognizing phone issue. As far as your bootloop issue, I'm assuming your bootloader is still unlocked, right? If so, and if above fix works where PC recognizes phone, try flashing google factory images via fastboot commands.
Click to expand...
Click to collapse
Since it doesnt show up in device manager, I cant uninstall the driver there.
I also tried it on a new PC that did never get in touch with an android phone - nothing. Not even a sound when I plug it in. The phone is just charging, thats it.

Have you tried using a different cable?

Keksdroid said:
Hello,
I really dont know what to do anymore.
No matter which ROM I flash, I always get stuck in a bootloop. I always wait 20-25 for a boot, but it doesnt pass the bootanimation.
Here is what happened:
My PC didnt recognize my phone anymore even though I didnt change any driver settings or something like that. Same with other PCs, not even showing up in device manager at all. So I thought I messed up some settings in my phone, thats why I wiped data, system, cache, internal store, then pushed a new ROM to my phone via USB OTG, but it doesnt boot at all. Phone still doesnt get recognized by any pc, not even in TWRP or bootloader.
Here are the things I tried so far:
- Ressurrection Remix (latest 3 versions) with OpenGapps
- Lineage OS with DynamicGapps
- both of them without any gapps
- OMNI Rom with DynamicGapps
I also did a factory reset before every flash. After 20 minutes of bootloop I also tried a 2nd boot for 20 minutes...nothing.
Since I cant access my phone from PC I cant flash stock ROM (or is it possible to flash it via TWRP?). I guess I just wiped something that I shouldnt have wiped. Does anyone have an idea what else I could try?
Click to expand...
Click to collapse
try Wug's Nexus Root Toolkit he is able to flash phone in bootloop

panicbear said:
Have you tried using a different cable?
Click to expand...
Click to collapse
I dont have any other cable, but maybe I should get a new one just to test. The cable I have is just 3 months old and was high quality....
pincher65 said:
try Wug's Nexus Root Toolkit he is able to flash phone in bootloop
Click to expand...
Click to collapse
Yeah I always used that tool in the past. But since my PC doesnt recognize the phone at all, not even in fastboot mode, that doesnt help me. I really need a solution that works just with TWRP...
Edit: Just an idea from my side. Would it work if someone, who just cleaned flashed, makes an nandroid backup, which I just restore with TWRP?

what radio at you installed? 7.1.1 02.2017 for TWRP

pincher65 said:
what radio at you installed? 7.1.1 02.2017 for TWRP
Click to expand...
Click to collapse
Radio is m8994f-2.6.36.2.20 - flashed it in December.
For TWRP?? Can I flash the stock zim through TWRP?

Keksdroid said:
For TWRP?? Can I flash the stock zim through TWRP?
Click to expand...
Click to collapse
yes. also PixelROM has full img

pincher65 said:
yes. also PixelROM has full img
Click to expand...
Click to collapse
Okay I will try that. I guess I will loose TWRP when I flash it?!

Keksdroid said:
Okay I will try that. I guess I will loose TWRP when I flash it?!
Click to expand...
Click to collapse
No.

pincher65 said:
No.
Click to expand...
Click to collapse
So I tried the stock rom and pixel rom, both when I try to flash them I get the Error message "Zip file is corrupt". There is no md5sum to check if its really corrupt...

Keksdroid said:
So I tried the stock rom and pixel rom, both when I try to flash them I get the Error message "Zip file is corrupt". There is no md5sum to check if its really corrupt...
Click to expand...
Click to collapse
disable check md5sum in setting TWRP.

pincher65 said:
disable check md5sum in setting TWRP.
Click to expand...
Click to collapse
Either way I'm blind, or I dont have that setting...

Keksdroid said:
Either way I'm blind, or I dont have that setting...
Click to expand...
Click to collapse
sorry, I have inattentively read the previous post. redownload zip if doesn't help, then your recovery is damaged and it is necessary to look for a way to connect him to PC

Problem solved. Got a new USB cable today, it worked now. Flashed stock image, it finally booted.
But wow, the old cable is already broken after 3 months...well it still charges very fast, but thats it.

Need Some Clarifications

Hi all,
After reading many posts i got a little confused and i'm not getting any result. Please help.
What i want?: Flash stock rom and later consider rooting, and flashing haden or lineagos. (already found guidance but..)
The issue?: It doesn't get recognized through USB with my PC. (drivers installed, cable connected but...)
My questions? (correct me if wished):
1) In Odin mode (which i enter) is the usb port enabled by default? or it depends on the phone configuration.
2) In recovery mode i still cannot see the phone through the USB so is it open by default on stock recovery?
3) Finally can i flash stock rom i downloaded from sammobile through SD card? i found that to be my last resort but i think odin actual proper way or not?
I first thought it was the cable...since is not the original but it seems not be the case...which leads me to think its the phone's usb port....but with the cable i can charge the phone although i cannot see it through my PC.
So bottom line if the answer to my questions are that is always open (accesible through usb port) then it HAS to be the cable right?
If last quesiton is possible then i will conclude my searchings to be ended for now.
Thanks to all the posts within this tree.

Findings
Is it normal that when boot to bootloader from stock recovery the ADB console keeps <waiting for device> while phone actually boots normaly?
I found that bootloader booting is accesible through fastboot independently from USB debugging option...
I'm considering buying official usb cable but store guy confirmed it works for data/power uses...

There definitely is a way to flash stock via TWRP, i once did that myself. However you need a dedicated tool on the PC to create a flashable zip, because the firmware can't be flashed by itself
Edit: i saw that you have FRP-lock enabled. Search for a guide on how to disable it and try again

verdugon said:
Is it normal that when boot to bootloader from stock recovery the ADB console keeps <waiting for device> while phone actually boots normaly?
I found that bootloader booting is accesible through fastboot independently from USB debugging option...
I'm considering buying official usb cable but store guy confirmed it works for data/power uses...
Click to expand...
Click to collapse
Are you on Samsung? If so, they don't have fastboot. Nor can you boot to bootloader. Do
Do you have the drivers installed? I have yet to see an unofficial cable not work for data transfer. Excepting damaged ones.

Light at the end of the tunnel!!!
PMFRTT said:
There definitely is a way to flash stock via TWRP, i once did that myself. However you need a dedicated tool on the PC to create a flashable zip, because the firmware can't be flashed by itself
Edit: i saw that you have FRP-lock enabled. Search for a guide on how to disable it and try again
Click to expand...
Click to collapse
Thanks PMFRTT!! I finally disabled FRP-lock and phone is usable again. I now will try to unlock OEM bootloader and enable USB debugging to see what happens. Thanks

Light at the end of the tunnel!!!
SnowFuhrer said:
Are you on Samsung? If so, they don't have fastboot. Nor can you boot to bootloader. Do
Do you have the drivers installed? I have yet to see an unofficial cable not work for data transfer. Excepting damaged ones.
Click to expand...
Click to collapse
Thanks @SnowFuhrer for your reply.
To answer your question yes its SMSUNG. I didn't know about that Thx.
The cable is brand knew but i noticed now that the phone is usable that is claims its on slow charge...may be my PC is quite old now....
Like i said i will try to unlock bootloader and make it accesible to odin to later see what to do.

verdugon said:
Thanks @SnowFuhrer for your reply.
To answer your question yes its SMSUNG. I didn't know about that Thx.
The cable is brand knew but i noticed now that the phone is usable that is claims its on slow charge...may be my PC is quite old now....
Like i said i will try to unlock bootloader and make it accesible to odin to later see what to do.
Click to expand...
Click to collapse
And to unlock the bootloader, just enable OEM unlock in the dev settings and it's ready to flash twrp. I remember when I got my Samsung and I was trying to fastboot unlock it lol.

Thanks to both of you! I will keep the thread on just in case...anyway may be it helps someone else.

verdugon said:
Thanks PMFRTT!! I finally disabled FRP-lock and phone is usable again. I now will try to unlock OEM bootloader and enable USB debugging to see what happens. Thanks
Click to expand...
Click to collapse
Good luck! Let me know how it went.

My bl unlocked and rooted firestick 2 (tank) bricked itself?

Like the title says my firestick 2nd gen has been unlocked and rooted for a while now but yesterday it randomly rebooted into twrp and then rebooted since then it won't go past the Amazon logo.
I've tried adb, I tried redoing the bootloader unlock process to recover my device but it's stuck on waiting for boot rom even though lsusb shows mediatek phone like it's supposed to. How can I unbrick my firestick?

MysticFTW said:
Like the title says my firestick 2nd gen has been unlocked and rooted for a while now but yesterday it randomly rebooted into twrp and then rebooted since then it won't go past the Amazon logo.
I've tried adb, I tried redoing the bootloader unlock process to recover my device but it's stuck on waiting for boot rom even though lsusb shows mediatek phone like it's supposed to. How can I unbrick my firestick?
Click to expand...
Click to collapse
my guess is you took a OTA..... You need a OTG and reinstall, then block. Just guessing though.. You dont have the right drivers if your script doesnt see it. If you are unlocked you should still have TWRP and shouldnt need to do the process again... Have you tried a OTG and boot into recovery script?

my guess is you took a OTA..... You need a OTG and reinstall, then block. Just guessing though.. You dont have the right drivers if your script doesnt see it. If you are unlocked you should still have TWRP and shouldnt need to do the process again... Have you tried a OTG and boot into recovery script?
Click to expand...
Click to collapse
If By otg you mean an otg cable, how would that help me? Is there a recovery script that I can run?

MysticFTW said:
If By otg you mean an otg cable, how would that help me? Is there a recovery script that I can run?
Click to expand...
Click to collapse
See post 3 of the unlock thread.
https://forum.xda-developers.com/fire-tv/development/unlock-fire-tv-stick-2nd-gen-tank-t3907002

See post 3 of the unlock thread.
https://forum.xda-developers.com/fir...-tank-t3907002
Click to expand...
Click to collapse
I read the post but The problem is I can't get to twrp, unless you're saying getting an otg cable and plugging in a mouse/keyboard will force it to got into recovery/twrp. Is there a script I can run on windows or Linux that will boot into recovery? I tried the recovery script included in the unlocking tutorial but it's stuck on waiting for preloader.

Even if you can get to twrp do what Michajin says. The same happened to my Fire tv stick 2 and that's the way I fixed it.
See post 3 of the unlock thread.
https://forum.xda-developers.com/fir...-tank-t3907002.

Even if you can get to twrp do what Michajin says. The same happened to my Fire tv stick 2 and that's the way I fixed it.
See post 3 of the unlock thread.
https://forum.xda-developers.com/fir...-tank-t3907002
Click to expand...
Click to collapse
Are you saying if I get an otg cable and plug in mouse and keyboard then while it's stuck at Amazon logo I can force it to go to twrp?

MysticFTW said:
Are you saying if I get an otg cable and plug in mouse and keyboard then while it's stuck at Amazon logo I can force it to go to twrp?
Click to expand...
Click to collapse
did you solve it?

Question Phone bricked trying to update December patch

Hey guys, so I used googles flash tool to update December patch and it keeps failing at writing to phone 1 of 11.
It's now in a bootloop but can access fastboot.
Ive tried to completely reset the phone manually using adb but it fails. It just doesn't work and aborts basically the phone rejects all data transmission.
What am I doing wrong or can I get a more detailed way to reset the phone completely.
-Edit-
I was also rooted and was following the guide for rooted December 12.
The main error is
(Error reading sparse file)

Why did you use the flash tool? General recommendation is, as long as you're running stock, just use the full OTA packages.
For the flash tool to be usable you need to OEM unlock your phone (while it's in a working state!).
If you can access fastboot you should be able to access recovery as well, where you can flash the full OTA, which should fix your issue.

fonix232 said:
Why did you use the flash tool? General recommendation is, as long as you're running stock, just use the full OTA packages.
For the flash tool to be usable you need to OEM unlock your phone (while it's in a working state!).
If you can access fastboot you should be able to access recovery as well, where you can flash the full OTA, which should fix your issue.
Click to expand...
Click to collapse
Because I'm rooted and recovery doesn't work.
I should have just done it manually instead of the flash tool method published here.
I just don't get why the system image isn't flashing now, the bootloader and radio flash work, but not the actual update. It's the correct version and all.

If the online flash tool isn't working for you, download the factory image from google's website and use the flash-all.bat to flash the device. Ensure that you modify the flash-all.bat file to not wipe data before running. This can be done by modifying one line in the file. Which is the following:
Code:
fastboot -w update image-raven-....zip
to
Code:
fastboot update --disable-verity --disable-verification image-raven-....zip
When flashing ensure that phone is in bootloader first.

So I got it to work after several hours. Literally just worked after trying another Google USB cable that was USB c to USB c, or maybe it worked cause of something else. Not sure, I don't like how finicky pixels have become. I discovered it's sometimes a luck thing when it wants to flash or not according to many people when searching the internet for solutions.

So i got a lil problem. i updated the pixel 6 pro to december update but upon booting up it says your phone is corrupted and sits at the google bootup screen. i can still use fastboot and whatnot but every img i tried i get the same message and it sits again?

holla420 said:
So i got a lil problem. i updated the pixel 6 pro to december update but upon booting up it says your phone is corrupted and sits at the google bootup screen. i can still use fastboot and whatnot but every img i tried i get the same message and it sits again?
Click to expand...
Click to collapse
edit---
first try this method that was posted - sometimes you can save your phone this way. if that doesn't work: you can download the factory image and remove the "-w" command in the flash-all.bat file (save it properly) - this will prevent wiping your phone. you'll need adb/fastboot tool and drivers. if you need help with this just reply.
if that doesn't work, you can go this route (but it will wipe your phone) you can use the "flash" link on the factory image page here. if you press the "flash" link in blue, it will take you to the correct build at flash.android.com (click on the build version 12.0.0 (SD1A.210817.037, Nov 2021) - that's the one that worked for me.

ok the problem im havin is it sstill sayinbg courrpt. it cant be trusted and may not work

holla420 said:
ok the problem im havin is it sstill sayinbg courrpt. it cant be trusted and may not work
Click to expand...
Click to collapse
What method did you use to update? Are you rooted? If so, what version of Magisk did you use?

V0latyle said:
What method did you use to update? Are you rooted? If so, what version of Magisk did you use?
Click to expand...
Click to collapse
no root, just unlocked bootloader i manually installed using adb

holla420 said:
no root, just unlocked bootloader i manually installed using adb
Click to expand...
Click to collapse
Use the Android Flash Tool to flash the latest December update. Don't check any of the boxes.

ayye thanks this method worked

holla420 said:
ok the problem im havin is it sstill sayinbg courrpt. it cant be trusted and may not work
Click to expand...
Click to collapse
You'll always get this message upon reboot once the bootloader is unlock.
It's normal, and you can disregard it entirely (unless you want the absolutely most secure device possible, then you should lock the bootloader, and this message will go away)

Az Biker said:
You'll always get this message upon reboot once the bootloader is unlock.
It's normal, and you can disregard it entirely (unless you want the absolutely most secure device possible, then you should lock the bootloader, and this message will go away)
Click to expand...
Click to collapse
oh i know but this was a different message. it was in red and wouldnt boot pass the bootup screen,

coilbio said:
So I got it to work after several hours. Literally just worked after trying another Google USB cable that was USB c to USB c, or maybe it worked cause of something else. Not sure, I don't like how finicky pixels have become. I discovered it's sometimes a luck thing when it wants to flash or not according to many people when searching the internet for solutions.
Click to expand...
Click to collapse
sounds like a user error; if it's fixed you might want to update your first post with solutions in case others have similar issues.

coilbio said:
So I got it to work after several hours. Literally just worked after trying another Google USB cable that was USB c to USB c, or maybe it worked cause of something else. Not sure, I don't like how finicky pixels have become. I discovered it's sometimes a luck thing when it wants to flash or not according to many people when searching the internet for solutions.
Click to expand...
Click to collapse
There are definitely better and worse USB-C cables. I've successfully fully flashed my P6P connected to a powered USB-A (3.2 Gen 2) Hub in one room through a USB extension cable 10-15 feet from my computer in another room. The hub and the extension cable are reasonably "robust", and I've found them reliable, but they're not particularly reputable name brands by any means. The USB-A -> USB-C cable I have connected to that hub is from my old HTC 10, too.