Database Develop

[Q] HTC One (AT&T) Factory Restore Help

Hi,
I was just installing the CM 10.1 ROM and I received the error "Unfortunately, the process com.android.phone has stopped". After this, I tried to reinstall the stock boot.img I got from Android Revolution and I seem to have lost everything on the phone. When connected via USB, the phone folders are normally shown, but now they aren't. As well, when trying to boot, I get stuck at the HTC logo screen. I tried fastboot flash boot boot.img but I keep receiving the error that the device can't be detected and/or the partition "boot.img" can't be found. I did cd c:\Root (my rooting folder) beforehand and boot.img is in there. How do I factory reset as in reinstall original OS with HTC Sense 5 UI on it so that everything went back to when I took it out of the box? If there's a way to do it via TWRP which I have installed, I would love to know how.

JacksonS918 said:
Hi,
I was just installing the CM 10.1 ROM and I received the error "Unfortunately, the process com.android.phone has stopped". After this, I tried to reinstall the stock boot.img I got from Android Revolution and I seem to have lost everything on the phone. When connected via USB, the phone folders are normally shown, but now they aren't. As well, when trying to boot, I get stuck at the HTC logo screen. I tried fastboot flash boot boot.img but I keep receiving the error that the device can't be detected and/or the partition "boot.img" can't be found. I did cd c:\Root (my rooting folder) beforehand and boot.img is in there. How do I factory reset as in reinstall original OS with HTC Sense 5 UI on it so that everything went back to when I took it out of the box? If there's a way to do it via TWRP which I have installed, I would love to know how.
Click to expand...
Click to collapse
if you get the ruu.zip for you device your can use all in one toolkit to flash it

skinsfanbdh said:
if you get the ruu.zip for you device your can use all in one toolkit to flash it
Click to expand...
Click to collapse
The problem is there is no ruu for AT&T

JacksonS918 said:
The problem is there is no ruu for AT&T
Click to expand...
Click to collapse
can you get to bootloader?

skinsfanbdh said:
can you get to bootloader?
Click to expand...
Click to collapse
Yes and I can get into recovery and start the boot, but I get stuck at the load screen. How do I flash the T-Mobile ruu.zip? (Pretty much the same as AT&T)

JacksonS918 said:
Yes and I can get into recovery and start the boot, but I get stuck at the load screen. How do I flash the T-Mobile ruu.zip? (Pretty much the same as AT&T)
Click to expand...
Click to collapse
what are you trying to flash?

skinsfanbdh said:
what are you trying to flash?
Click to expand...
Click to collapse
m7ul-jb-crc-3.4.10-24b0b2a.tar.gz is the file name of the file I downloaded from the Dev site.

JacksonS918 said:
m7ul-jb-crc-3.4.10-24b0b2a.tar.gz is the file name of the file I downloaded from the Dev site.
Click to expand...
Click to collapse
i dont think you can flash that type of file. download a rom that is in zip format then flash it or you might be able to use all in one toolkit to push the file u you have to the phone.
but i recommend getting a zip file that is proven to work for you device

skinsfanbdh said:
i dont think you can flash that type of file. download a rom that is in zip format then flash it or you might be able to use all in one toolkit to push the file u you have to the phone.
but i recommend getting a zip file that is proven to work for you device
Click to expand...
Click to collapse
Where would I go to get said zip file?

JacksonS918 said:
Where would I go to get said zip file?
Click to expand...
Click to collapse
the development section. i believe the most popular one for your device is cleanROM

skinsfanbdh said:
the development section. i believe the most popular one for your device is cleanROM
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2224752 <- I tried installing the odexed .zip but it isn't loading.

JacksonS918 said:
http://forum.xda-developers.com/showthread.php?t=2224752 <- I tried installing the odexed .zip but it isn't loading.
Click to expand...
Click to collapse
whats it doing exactly

skinsfanbdh said:
whats it doing exactly
Click to expand...
Click to collapse
It's stuck at the HTC quietly brilliant screen. When hooked up to my PC, the device shows that it's completely empty and has no OS. The phone will not boot at all.

what are you trying to flash from recovery

skinsfanbdh said:
what are you trying to flash from recovery
Click to expand...
Click to collapse
The T-Mobile RUU Kit supplied from the dev site.

JacksonS918 said:
The T-Mobile RUU Kit supplied from the dev site.
Click to expand...
Click to collapse
im not sure but i dont think you can flash those. i think you may have to use adb and push the rom to the phone

[Q] Looking for help. Cant boot phone, recovery nor use adb commands.

Hej guys. I really hope that you can help me with my problem
Have been trying for 2 days and looking at post but haven't been able to get it fixed.
Here goes.
I have been playing around with custom roms on my htc one for a while now.
Then when i was about to install a new custom rom, i first wiped my phone.
I properly wiped something that should not be wiped, because i ended up with no os and no custom rom zip file that i could install in twrp.
I then tryed sideloading revolutions, and it seemed to work because it ended up booting on the phone and i could select what programs too install with it... but halfway through it stoped and rebooted.
now i cant even get into recovery anymore, and booting the phone only gets it to htc briliant logo. Then it restarts and tryes going into recovery, but it cant, and ends up just restarting over and over again.
Tryed flashing cwm and twrp again, but still cant get into recovery.
adb dont fint my device, and i have tryed all drivers i could find.
Tryed using a RUU, but it fails. Properly because its not the right one, but cant fint one that fits.
Sooo... i think im in a real pickle right now.
my radio is :4a.14.3250.13
hboot: 1.44.0000
Thinking about going back with my phone, but with the warranty gone i dont know if they'll even look at it.
Hoping for some advise, or some ideas on what to do.
-dealba

fastboot erase cache in terminal or with all in one toolkit

Arh thanks for your reply.
Cant belive i dident try that.
but it worked, im now able to get into twrp.
It says that i have 0 mb internal storage?
should i try to flash twrp again or what should my aproach be ?

dealba said:
Arh thanks for your reply.
Cant belive i dident try that.
but it worked, im now able to get into twrp.
It says that i have 0 mb internal storage?
should i try to flash twrp again or what should my aproach be ?
Click to expand...
Click to collapse
try reboot recovery if that doesnt work install cwm non touch. i love twrp but i had the same issue with it and i havent had it with cwm

skinsfanbdh said:
try reboot recovery if that doesnt work install cwm non touch. i love twrp but i had the same issue with it and i havent had it with cwm
Click to expand...
Click to collapse
Okay thanks
So i tryed installing cwm the non touch version. but it says the same thing as twrp.
And that is that it cant mount /sdcard/

dealba said:
Okay thanks
So i tryed installing cwm the non touch version. but it says the same thing as twrp.
And that is that it cant mount /sdcard/
Click to expand...
Click to collapse
i dont think that is a problem. im not absolutely sure about that but what is the next step you trying to accomplish

skinsfanbdh said:
i dont think that is a problem. im not absolutely sure about that but what is the next step you trying to accomplish
Click to expand...
Click to collapse
Well, im really just trying to get an os flashed back on the phone so i can boot it, either by another custom rom or a stock rom.
But since i cant use adb commands, how do i get a new rom on there?

dealba said:
Well, im really just trying to get an os flashed back on the phone so i can boot it, either by another custom rom or a stock rom.
But since i cant use adb commands, how do i get a new rom on there?
Click to expand...
Click to collapse
you on a windows computer?

dealba said:
Well, im really just trying to get an os flashed back on the phone so i can boot it, either by another custom rom or a stock rom.
But since i cant use adb commands, how do i get a new rom on there?
Click to expand...
Click to collapse
i have had the same problem. what i did is in twrp recovery go to wipe --- format data --- type yes (WARNING you will lose all your files)

skinsfanbdh said:
you on a windows computer?
Click to expand...
Click to collapse
Yes, im running windows

dealba said:
Yes, im running windows
Click to expand...
Click to collapse
download all in one toolkit if you havent already its easy to use and easier for me to tell you what to do. plus i dont know how well you know adb and fastboot commands

rambo12345 said:
i have had the same problem. what i did is in twrp recovery go to wipe --- format data --- type yes (WARNING you will lose all your files)
Click to expand...
Click to collapse
okay thanks, now i can see my sdcard.
But still wondering how to get a rom on it so i can flash from twrp..

dealba said:
okay thanks, now i can see my sdcard.
But still wondering how to get a rom on it so i can flash from twrp..
Click to expand...
Click to collapse
adb sideload
its an option in the all in one tool kit but its easier or you can type the command

skinsfanbdh said:
download all in one toolkit if you havent already its easy to use and easier for me to tell you what to do. plus i dont know how well you know adb and fastboot commands
Click to expand...
Click to collapse
I got the toolkit now
got a 5 min post restriction so little slow on replying

dealba said:
I got the toolkit now
got a 5 min post restriction so little slow on replying
Click to expand...
Click to collapse
i think it it will be over after 3 more posts. plug your phone in. then open all in one toolkit and select adb sideload then just follow the on screen instructions

skinsfanbdh said:
i think it it will be over after 3 more posts. plug your phone in. then open all in one toolkit and select adb sideload then just follow the on screen instructions
Click to expand...
Click to collapse
Okay, did the side loader, and used android revolutions rom. It installed and and after staying on boot animation a few minnuts it started.
Thank you so much for your help, really appreciate it

dealba said:
Okay, did the side loader, and used android revolutions rom. It installed and and after staying on boot animation a few minnuts it started.
Thank you so much for your help, really appreciate it
Click to expand...
Click to collapse
no problem. have fun:victory:

skinsfanbdh said:
fastboot erase cache in terminal or with all in one toolkit
Click to expand...
Click to collapse
So I'll try here first. I am having the same issue, I can't get the device to boot into recovery, no matter if I clear the cache, or flash either one of twrp or CWM.
I unlocked the bootloader, I think used the all in one toolkit to flash the recovery. When that didn't work, I erased the cache and manually flashed the recovery, and it said it pushed successfully.
I am at a loss, I have no idea what to try next, any help would be appreciated.
******Finally got it, I had to disable Fast Boot in the Power options in Settings******

How do you copy update.zip from external to internal SD?
Sorry if it's a total no-brainer, but how do I manually copy a recovery zip to the internal update.zip? Can I do this from my phone (which is stuck in a bootloop: see below)? Or do I have to use ADB with my computer?
Turbojugend said:
So I'll try here first. I am having the same issue, I can't get the device to boot into recovery, no matter if I clear the cache, or flash either one of twrp or CWM.
I unlocked the bootloader, I think used the all in one toolkit to flash the recovery. When that didn't work, I erased the cache and manually flashed the recovery, and it said it pushed successfully.
I am at a loss, I have no idea what to try next, any help would be appreciated.
******Finally got it, I had to disable Fast Boot in the Power options in Settings******
Click to expand...
Click to collapse
My situation:
Using Open Recovery I tried to install CM7 with custom kernel on my XT720
It gave an error: "assert failed: write_raw_image... Status 7" As I was looking that up, my phone blackscreened. After a while I pulled the battery.
Then on startup it went into a bootloop after a picture of a broken screen saying "2ndboot kernel restart in progress." (Presumably the kernel wasn't properly applied?)
Trying to boot into bootloader says battery is too low.
Phone will only turn on when plugged into outlet.
What I think I need to do:
- Copy a good update from my external SD over the bad update.zip on the internal SD, and apply the update to reset the kernel, etc.
- Open Recovery could do this, if I could load it.
- I could load Openrecovery if I could get the bootloader to run,
- I could get the bootloader to run if my battery would charge

Updating and restoring to stock issues

I have an HTC One by T-Mobile, Our update was released Monday. I tried to update but when it rebooted it went to install and failed to install, I looked up some information that say usually the cause of the failed install for software system updates is because of an unlocked bootloader and custom recovery. So I've tried to restore to factory OEM settings but every time it fails to up restore to the factory update as well. I'm at a loss here and no Idea what to do. I can flash any custom roms I want and those seem to work and flash just fine but If I try anything else like reverting to OEM stock it doesn't work. Anyone have any Ideas?
Before anyone asks, I've tried doing a RRU restore from desktop and .Zip on my phone and neither work. Both fail.

TaintedCross said:
I have an HTC One by T-Mobile, Our update was released Monday. I tried to update but when it rebooted it went to install and failed to install, I looked up some information that say usually the cause of the failed install for software system updates is because of an unlocked bootloader and custom recovery. So I've tried to restore to factory OEM settings but every time it fails to up restore to the factory update as well. I'm at a loss here and no Idea what to do. I can flash any custom roms I want and those seem to work and flash just fine but If I try anything else like reverting to OEM stock it doesn't work. Anyone have any Ideas?
Before anyone asks, I've tried doing a RRU restore from desktop and .Zip on my phone and neither work. Both fail.
Click to expand...
Click to collapse
Get s-off and restore any RUU.. After restore, better get s-off before you update, you won't be able to get it after the update.
Sent from my iPod touch using Tapatalk

TaintedCross said:
I have an HTC One by T-Mobile, Our update was released Monday. I tried to update but when it rebooted it went to install and failed to install, I looked up some information that say usually the cause of the failed install for software system updates is because of an unlocked bootloader and custom recovery. So I've tried to restore to factory OEM settings but every time it fails to up restore to the factory update as well. I'm at a loss here and no Idea what to do. I can flash any custom roms I want and those seem to work and flash just fine but If I try anything else like reverting to OEM stock it doesn't work. Anyone have any Ideas?
Before anyone asks, I've tried doing a RRU restore from desktop and .Zip on my phone and neither work. Both fail.
Click to expand...
Click to collapse
you need to flash the stock recovery and lock your bootloader to be able to do the update.

[email protected] said:
you need to flash the stock recovery and lock your bootloader to be able to do the update.
Click to expand...
Click to collapse
I'm pretty sure you don't need to relock the bootloader for OTAs, you do however need 100% stock ROM and (a very close) stock recovery for that ROM.

nkk71 said:
I'm pretty sure you don't need to relock the bootloader for OTAs, you do however need 100% stock ROM and (a very close) stock recovery for that ROM.
Click to expand...
Click to collapse
i stand corrected.
a stock recovery will do

[email protected] said:
i stand corrected.
a stock recovery will do
Click to expand...
Click to collapse
Only for OTAs, to run a full RUU exe, I do think the bootloader has to be locked/relocked

nkk71 said:
Only for OTAs, to run a full RUU exe, I do think the bootloader has to be locked/relocked
Click to expand...
Click to collapse
Not going to matter anyway, I accidently wiped my whole OS. I've tried using adb Sideload but it wont detect my device.

TaintedCross said:
Not going to matter anyway, I accidently wiped my whole OS. I've tried using adb Sideload but it wont detect my device.
Click to expand...
Click to collapse
Restart your computer, also update to latest HTC drivers and adb sdk.
Alternate method, use an OTG cable with a USB stick with a ROM.ZIP on it, and mount "external sdcard" (or whatever it's called) in custom recovery.

nkk71 said:
Restart your computer, also update to latest HTC drivers and adb sdk.
Alternate method, use an OTG cable with a USB stick with a ROM.ZIP on it, and mount "external sdcard" (or whatever it's called) in custom recovery.
Click to expand...
Click to collapse
I have restarted like 20 times, still doesn't detect it. And I don't have an OTG cable

TaintedCross said:
I have restarted like 20 times, still doesn't detect it. And I don't have an OTG cable
Click to expand...
Click to collapse
Does fastboot work?
Sent from my HTC One using Tapatalk

nkk71 said:
Does fastboot work?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I can boot into fastboot on my phone but I've no idea what to do from there.
Edit: HELLS YEAH! I got it! lol had to relock bootloader using fastboot and then go back into fastboot on my phone and run the RUU.exe and it worked this time! SOOO freaking stoked and happy! I've been up for 7 hours straight trying to fix this!

Nice. Please update the thread and put SOLVED
Sent from my HTC One using xda app-developers app

[Q] I done screwed up big time - the mystery of the unflashable recovery

Back story: Verizon Moto X, unlocked bootloader via China Middleman, running Eclipse ROM 4.4.2, TWRP 2.7.0.0 recovery
Objective: wipe everything and flash back to a (rooted) stock for device retail
Why I'm screwed: everything is wiped - phone has no OS, recovery, etc. It simply hangs out on the Motorola M at boot and doesn't move. fastboot loads and will flash recovery (seemingly successfully) but rebooting to recovery always gets stuck at the logo
How I got there:
1. Backed up with TWRP, then flashed new recovery CWM (the one here) and backed up again. Saved both folders of nandroid backups to my PC (yay)
2. Flashed back to TWRP (but this time the new one v2.8.0.1 here, which I downloaded and flashed via that fancy new TWRP app [I selected the "ghost" model]) clicked about every type of wipe option I could get my grubby little fingers on, then adb pushed the ROM and kernel/radio combo from here.
3. Attempted to flash the new ROM via TWRP. It failed. something about an "Error executing updater binary in zip". I sighed, said "meh", googled the problem a bit and figured I'd reboot the recovery and try again. This is where things get weird.
4. Phone hangs out at boot logo (that kaleidoscope "M"). Fine, I accidentally did a normal boot, and there's no OS installed. I go into fastboot and boot to recovery. SAME SCREEN. TWRP has apparently disappeared. No matter. I go into fastboot and flash it again, then boot to recovery. SAME SCREEN. Flash back to CWM. SAME SCREEN. Back to TWRP one more time just for giggles? SAME SCREEN.
No idea where to go from here. Anyone have any idea how this happened and what my options are at this point? Is there a way to manually flash a ROM via fastboot? Restore either my CWM or TWRP nandroid backups without access to the recovery? Any guidance would be appreciated.
Attachments:
a) boot logo I'm stuck on
b) command line log of commands from flashing recoveries

From fastboot, flash your recovery and then use the volume down button to highlight recovery and then volume up button to enter into recovery.

VerneVerne said:
From fastboot, flash your recovery and then use the volume down button to highlight recovery and then volume up button to enter into recovery.
Click to expand...
Click to collapse
Perhaps I didn't make that clear - that's exactly what I've been doing.

PHP:
gerodive said:
Back story: Verizon Moto X, unlocked bootloader via China Middleman
Click to expand...
Click to collapse
That is what I have.
gerodive said:
No idea where to go from here. Anyone have any idea how this happened and what my options are at this point? Is there a way to manually flash a ROM via fastboot?
Click to expand...
Click to collapse
Well I wiped my system partition when I must have been drunk or something b/c I still can't believe I did it. But I did. Then from bootloader mode, I ran the command mfastboot flash system system.img from a command shell on my PC using the system image from the sbf that my bootloader was currently on (in my case, it was 4.4.4). All was good.
Then I could restore my nandroids by moving them to my phone from my PC.

Wansanta said:
PHP:
That is what I have.
Well I wiped my system partition when I must have been drunk or something b/c I still can't believe I did it. But I did. Then from bootloader mode, I ran the command mfastboot flash system system.img from a command shell on my PC using the system image from the sbf that my bootloader was currently on (in my case, it was 4.4.4). All was good.
Then I could restore my nandroids by moving them to my phone from my PC.
Click to expand...
Click to collapse
Could you elaborate a little more on this? How do I get the system.img file to flash? I'm guessing my bootloader would be on the 4.4.2 one since that was what Eclipse was on, but is there any way to check? Deleting the system partition was definitely what I did. Also, why mfastboot as opposed to just fastboot?

gerodive said:
Could you elaborate a little more on this? How do I get the system.img file to flash?
Click to expand...
Click to collapse
mfastboot flash system system.img
gerodive said:
I'm guessing my bootloader would be on the 4.4.2 one since that was what Eclipse was on, but is there any way to check?
Click to expand...
Click to collapse
In bootloader mode it will tell you on the second line. 30:B7 is the 4.4.4 bootloader version.
gerodive said:
Deleting the system partition was definitely what I did.
Click to expand...
Click to collapse
As long as you can get into bootloader mode you can flash it back.
gerodive said:
Also, why mfastboot as opposed to just fastboot?
Click to expand...
Click to collapse
because the moto x system images are too large to flash with fastboot, you have to use mfastboot.

gerodive said:
Back story: Verizon Moto X, unlocked bootloader via China Middleman, running Eclipse ROM 4.2.2, TWRP 2.7.0.0 recovery
Click to expand...
Click to collapse
gerodive said:
I'm guessing my bootloader would be on the 4.4.2 one since that was what Eclipse was on, but is there any way to check?
Click to expand...
Click to collapse
4.2.2 or 4.4.2?

nhizzat said:
4.2.2 or 4.4.2?
Click to expand...
Click to collapse
yeah he really needs to check b/c it really matters what version of the bootloader he is on.

Flashing the 4.4.2 system.img (and boot.img just for good measure) worked! I was then able to boot normally and then upgraded to 4.4.4. Oh happy day. Thanks for the help everyone.

Sorry, meant 4.4.2.

gerodive said:
Flashing the 4.4.2 system.img (and boot.img just for good measure) worked! I was then able to boot normally and then upgraded to 4.4.4. Oh happy day. Thanks for the help everyone.
Click to expand...
Click to collapse
So glad!! If you are unlocked, as long as you can get into a functioning bootloader mode and have access to the sbf for your version of the OS you haven't bricked.
I about near had a heart attack when I deleted my system, but no biggie to restore it. I think I only paid $35 to unlock b/c I did it straight through tao bao, but it was the best $35 I have spent in a long time. I drop $35 every time I go for sushi, so I can't imagine not paying to unlock if you have the option.

Stuck in Oneplus logo. Can't access recovery. Fastboot working.

Hi everyone.
I was trying to flash Nitrogen OS. First I flashed the latest firmware, then the actual rom and then GAPPS. After that my mobile got stuck in Oneplus logo without being able to go into recovery mode.
I tried using fastboot to flash the files in this thread(https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306) which worked once, but even after that I can't surpass the logo screen.
I've been trying to look for information but I can't find anything.
To clarify:
- I already tried erasing userdata and cache from fastboot
-I already tried flashing recovery images from twrp, stock and bluspark
Thanks in advance guys.

Pavononer23 said:
Hi everyone.
I was trying to flash Nitrogen OS. First I flashed the latest firmware, then the actual rom and then GAPPS. After that my mobile got stuck in Oneplus logo without being able to go into recovery mode.
I tried using fastboot to flash the files in this thread(https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306) which worked once, but even after that I can't surpass the logo screen.
I've been trying to look for information but I can't find anything.
Thanks in advance guys.
Click to expand...
Click to collapse
Which TWRP are you using? Which firmware are you flashing? You can't access recovery at all? I've run into plenty of bricks like this and I'm usually able to get back to recovery by forcing the device off (vol up + power hold) and rebooting back to recovery. and if that doesn't work I can at least get to the bootloader and re-flash a recovery file.

rykanator said:
Which TWRP are you using? Which firmware are you flashing? You can't access recovery at all? I've run into plenty of bricks like this and I'm usually able to get back to recovery by forcing the device off (vol up + power hold) and rebooting back to recovery. and if that doesn't work I can at least get to the bootloader and re-flash a recovery file.
Click to expand...
Click to collapse
I was using last bluspark recovery. I was flashing OB21 when everything happened.
There is no way I can access to recovery. I tried reflashing the stock recovery from that unbricking thread with all the other things through fastboot and I can't boot into recovery at all. It is the first time I face this error so I am lost.

Pavononer23 said:
I was using last bluspark recovery. I was flashing OB21 when everything happened.
There is no way I can access to recovery. I tried reflashing the stock recovery from that unbricking thread with all the other things through fastboot and I can't boot into recovery at all. It is the first time I face this error so I am lost.
Click to expand...
Click to collapse
can you boot into the bootloader/fastboot?

rykanator said:
can you boot into the bootloader/fastboot?
Click to expand...
Click to collapse
Yes I can

Pavononer23 said:
Yes I can
Click to expand...
Click to collapse
okay, well what I would do is boot into the bootloader, and then reflash the blu_spark recovery via adb so you can boot into it. then wipe everything and restart. but this time I would try the OB 20 firmware and not the 21. when I was on NOS I used that one and it worked just fine. I'm not sure if it made a difference, but I flashed the firmware both right before and right after flashing NOS

rykanator said:
okay, well what I would do is boot into the bootloader, and then reflash the blu_spark recovery via adb so you can boot into it. then wipe everything and restart. but this time I would try the OB 20 firmware and not the 21. when I was on NOS I used that one and it worked just fine. I'm not sure if it made a difference, but I flashed the firmware both right before and right after flashing NOS
Click to expand...
Click to collapse
It doesnt recognize my device through adb and I don't know why. If that worked I would have tried to sideload some firmware, but when I do adb devices it doesn't appear

Pavononer23 said:
It doesnt recognize my device through adb and I don't know why. If that worked I would have tried to sideload some firmware, but when I do adb devices it doesn't appear
Click to expand...
Click to collapse
idk if it'll recognize as an adb device if it's in the bootloader. maybe try fastboot devices? sorry, I'm just spitballin here

rykanator said:
idk if it'll recognize as an adb device if it's in the bootloader. maybe try fastboot devices? sorry, I'm just spitballin here
Click to expand...
Click to collapse
Somehow fastboot devices does send me that my device is there but adb devices no, I will try looking into that to see if that works. Thanks for the help anyway

Pavononer23 said:
Somehow fastboot devices does send me that my device is there but adb devices no, I will try looking into that to see if that works. Thanks for the help anyway
Click to expand...
Click to collapse
yeah! try fastboot flash recovery "recovery file name".img
make sure that recovery img file is in the platform-tools file (or wherever your adb files are) and see if that works!

rykanator said:
yeah! try fastboot flash recovery "recovery file name".img
make sure that recovery img file is in the platform-tools file (or wherever your adb files are) and see if that works!
Click to expand...
Click to collapse
It is not working, I think I lost my Oneplus 3t...

Pavononer23 said:
It is not working, I think I lost my Oneplus 3t...
Click to expand...
Click to collapse
I mean idk if you wanna do this, but you could always try to "format userdata", then flash the stock recovery, and then sideload OOS. but you would lose all of your data in your internal storage, and it's still not a guarantee. there are some posts about doing a full wipe and starting from scratch. I'd look into those. Best of luck reviving your OP3T

Pavononer23 said:
It is not working, I think I lost my Oneplus 3t...
Click to expand...
Click to collapse
just a tip, try posting the output instead of "it's not working",
so the devs here might be able to analyze the problem..

nicknacknuke said:
just a tip, try posting the output instead of "it's not working",
so the devs here might be able to analyze the problem..
Click to expand...
Click to collapse
I already post a lot of information on the first post:
Mobile not passing the first time Oneplus logo appears.
Only fastboot is working, not adb, not recovery.
I already tried flashing other recoveries and the stock one->Can't pass Oneplus logo anyway
Tried formatting userdata through fastboot and flashing the .img files from my first post->Not working

Then just do the Qualcomm restore and unlock, boot to fastboot and flash the latest TWRP. Then boot into TWRP and format cache partitions, system and data and then adb sideload using this option under TWRP advanced to flash firmware zip, NitrogenOS zip and then 8.1 Gapps and try booting to see if same thing happens again. You are using the NitrogenOS stock kernel and not some other?

pitrus- said:
Then just do the Qualcomm restore and unlock, boot to fastboot and flash the latest TWRP. Then boot into TWRP and format cache partitions, system and data and then adb sideload using this option under TWRP advanced to flash firmware zip, NitrogenOS zip and then 8.1 Gapps and try booting to see if same thing happens again. You are using the NitrogenOS stock kernel and not some other?
Click to expand...
Click to collapse
What do you mean by the Qualcomm restor and unlock? I already tried the flashing of latest TWRP and it did not work.
I was coming from Validus last beta but did a previous factory reset and that stuff.
Thank you for the answer

Pavononer23 said:
What do you mean by the Qualcomm restor and unlock? I already tried the flashing of latest TWRP and it did not work.
I was coming from Validus last beta but did a previous factory reset and that stuff.
Thank you for the answer
Click to expand...
Click to collapse
What he meant is probably unbrick tool - https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Try flashing official firmware with it and then try again by flashing TWRP and flashing Nitrogen.

przemcio510 said:
What he meant is probably unbrick tool - https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Try flashing official firmware with it and then try again by flashing TWRP and flashing Nitrogen.
Click to expand...
Click to collapse
I can't install the drivers:
-First, stupid Windows policy saying that its driver is the best one available.
-Second, choosing from a disk to avoid one saying that the driver is not a x64 one.

Pavononer23 said:
I already post a lot of information on the first post:
Mobile not passing the first time Oneplus logo appears.
Only fastboot is working, not adb, not recovery.
I already tried flashing other recoveries and the stock one->Can't pass Oneplus logo anyway
Tried formatting userdata through fastboot and flashing the .img files from my first post->Not working
Click to expand...
Click to collapse
None of that answer what he actually asked, which is: what was the output (error message, result, etc.) when you tried to flash TWRP?
Did it flash successfully, but still can't boot to TWRP? Or else, what was the exact error message?
In general, when asking for help and giving status, be specific as possible, and give as many details as possible. Saying you "tried xxx" or "it did not work" is not specific enough.
Seems silly, but I've seen a lot of times where it's as simple as the user not using the correct command or entering the right file name.

redpoint73 said:
None of that answer what he actually asked, which is: what was the output (error message, result, etc.) when you tried to flash TWRP?
Did it flash successfully, but still can't boot to TWRP? Or else, what was the exact error message?
In general, when asking for help and giving status, be specific as possible, and give as many details as possible. Saying you "tried xxx" or "it did not work" is not specific enough.
Seems silly, but I've seen a lot of times where it's as simple as the user not using the correct command or entering the right file name.
Click to expand...
Click to collapse
There were no errors when flashing TWRP. When I tried rebooting using fastboot(fastboot boot recovery.img) it got stuck in the message saying booting up... and the only thing that changed was that my phone left the bootloader screen to a screen with the Oneplus logo and a fastboot mode message under it.
The command I used was fastboot flash recovery recovery.img(Name of the actual recovery file)