Database Develop

[Q] 1,31 , no rom or adb

So basically the only thing working in fastboot
somehow i have managed to wipe everything off of my device so there is no rom installed what so ever...which means i am unable to turn on usb debugging to get adb working. I am also on 1.31 so the RUU method will not work. i am able to flash whatever recovery or Superuser i wish and root/unroot as i please.
the only solution i can think of would be to flash a signed stock zip using "fastboot update signedstock.zip" but the ones i found here -http://forum.xda-developers.com/showthread.php?t=2368907 dont seem to work. i get errors like no "boot.img" or "does not contain android-info.txt"
any suggestions?
thanks for your time

shadowtdt09 said:
So basically the only thing working in fastboot
somehow i have managed to wipe everything off of my device so there is no rom installed what so ever...which means i am unable to turn on usb debugging to get adb working. I am also on 1.31 so the RUU method will not work. i am able to flash whatever recovery or Superuser i wish and root/unroot as i please.
the only solution i can think of would be to flash a signed stock zip using "fastboot update signedstock.zip" but the ones i found here -http://forum.xda-developers.com/showthread.php?t=2368907 dont seem to work. i get errors like no "boot.img" or "does not contain android-info.txt"
any suggestions?
thanks for your time
Click to expand...
Click to collapse
Guide in General on how to downgrade. You'll be fine.
http://forum.xda-developers.com/showthread.php?t=2390821

Indirect said:
Guide in General on how to downgrade. You'll be fine.
http://forum.xda-developers.com/showthread.php?t=2390821
Click to expand...
Click to collapse
i have tried that for cwm recovery but that requires adb and usb debugging...which i dont have
i have also just tried it with the htc recovery where the screen just shows the HTC logo but "adb devices" says no devices are connected

shadowtdt09 said:
i have tried that for cwm recovery but that requires adb and usb debugging...which i dont have
i have also just tried it with the htc recovery where the screen just shows the HTC logo but "adb devices" says no devices are connected
Click to expand...
Click to collapse
Then oh well? There is no other way to fix it than using TWRP / CWM and adb / fastboot.

Indirect said:
Then oh well? There is no other way to fix it than using TWRP / CWM and adb / fastboot.
Click to expand...
Click to collapse
There are no signed stock zips out there that i can use fastboot update .zip ?

shadowtdt09 said:
There are no signed stock zips out there that i can use fastboot update .zip ?
Click to expand...
Click to collapse
http://teamviewer.com/download
Get that, pm me your id and password and I'll fix your phone. Have nothing better to do for a half hour anyway.

Indirect said:
http://teamviewer.com/download
Get that, pm me your id and password and I'll fix your phone. Have nothing better to do for a half hour anyway.
Click to expand...
Click to collapse
you're a hell of a man indirect!

Aldo101t said:
you're a hell of a man indirect!
Click to expand...
Click to collapse
Tis the benefit of having no job. Easily able to help everyone out if I'm bored.

shadowtdt09 said:
So basically the only thing working in fastboot
somehow i have managed to wipe everything off of my device so there is no rom installed what so ever...which means i am unable to turn on usb debugging to get adb working. I am also on 1.31 so the RUU method will not work. i am able to flash whatever recovery or Superuser i wish and root/unroot as i please.
the only solution i can think of would be to flash a signed stock zip using "fastboot update signedstock.zip" but the ones i found here -http://forum.xda-developers.com/showthread.php?t=2368907 dont seem to work. i get errors like no "boot.img" or "does not contain android-info.txt"
any suggestions?
thanks for your time
Click to expand...
Click to collapse
just a fyi you can use fastboot to flash a rom if you put it in the same folder as the platform tools folder of your sdk, All roms have a android-info.txt file that's how android knows how to flash what to the particular partition.
you can flash any zip file from fastboot as long as it has the android-info file
fastboot flash zip nameofzip.zip

Fixed his phone and found out he is in my area. Pretty small world.

Indirect said:
Fixed his phone and found out he is in my area. Pretty small world.
Click to expand...
Click to collapse
I'm in fort myers

ktu84l UpDater

Your bootloader must be unlocked to use this. If your bootloader is not already unlocked, unlocking it will wipe your data and this method is not recommended.
This is a modified factory image that will not erase your user data or custom recovery. This can be used even if you’re rooted and with modified system files, xposed framework, or custom recovery. Once installed you will lose root, just flash supersu in your custom recovery. Xposed should still be on your device so just go into the app and re-install it. For any modified system files, you will have to re-modify those.
This is intended for those on the stock rom, rooted, and with a custom recovery. It’ll work if you have a custom rom but will put the stock system on.
I am not responsible for anything you do to your device so flash at your own risk. Always backup before doing any significant changes to your device. I would recommend off your device in case something happens
.
To use, download the modified factory image here https://mega.co.nz/#!AAATiKpI!PJbBgroM6PB7tTAs_TanCOrlzAeqBq0PEupNyvU72pEl Use 7-zip or winrar to extract the files.
Supersu by chainfire can be found here, CWM / TWRP / MobileODIN installable ZIP: http://download.chainfire.eu/supersu
Boot into the bootloader. From a cmd window opened where the flash-all file is just type flash-all. You can use shift, right click on the occam-ktu85l-Modified folder to open a command window in the correct folder. ADB/FASTBOOT must be intalled on your PC.
You can also just double click on the flash-all.bat
This is tested on a windows machine; however it should work on a Mac too, flash the flash-all.sh.

jd1639 said:
Your bootloader must be unlocked to use this. If your bootloader is not already unlocked, unlocking it will wipe your data and this method is not recommended.
This is a modified factory image that will not erase your user data or custom recovery. This can be used even if you’re rooted and with modified system files, xposed framework, or custom recovery. Once installed you will lose root, just flash supersu in your custom recovery. Xposed should still be on your device so just go into the app and re-install it. For any modified system files, you will have to re-modify those.
This is intended for those on the stock rom, rooted, and with a custom recovery. It’ll work if you have a custom rom but will put the stock system on.
I am not responsible for anything you do to your device so flash at your own risk. Always backup before doing any significant changes to your device. I would recommend off your device in case something happens
.
To use, download the modified factory image here http://d-h.st/Uql Use 7-zip or winrar to extract the files.
Mirror https://mega.co.nz/#!0Zoi3DoL!OXm5H6HBzwGd8PEPlNfTQphcSAoM4zN8MG5LX3YzK7g
Supersu by chainfire can be found here, CWM / TWRP / MobileODIN installable ZIP: http://download.chainfire.eu/supersu
Boot into the bootloader. From a cmd window opened where the flash-all file is just type flash-all. You can use shift, right click on the occam-ktu85l-Modified folder to open a command window in the correct folder.
You can also just double click on the flash-all.bat
This is tested on a windows machine; however it should work on a Mac too, flash the flash-all.sh.
Click to expand...
Click to collapse
folder image-occam-ktu84l.zip has recovery.img,this stock recovery?

pincher65 said:
folder image-occam-ktu84l.zip has recovery.img,this stock recovery?
Click to expand...
Click to collapse
Yes it's stock. Sorry about that it has been corrected
Sent from my Nexus 5 using XDA Free mobile app

i have error:
"archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt"

szakalq said:
i have error:
"archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt"
Click to expand...
Click to collapse
That's weird. Try this and please let me know if it works https://mega.co.nz/#!AAATiKpI!PJbBgroM6PB7tTAs_TanCOrlzAeqBq0PEupNyvU72pE

jd1639 said:
That's weird. Try this and please let me know if it works https://mega.co.nz/#!AAATiKpI!PJbBgroM6PB7tTAs_TanCOrlzAeqBq0PEupNyvU72pE
Click to expand...
Click to collapse
This worked for me! Thanks
Sent from my Nexus 4 using Tapatalk

jd1639 said:
That's weird. Try this and please let me know if it works https://mega.co.nz/#!AAATiKpI!PJbBgroM6PB7tTAs_TanCOrlzAeqBq0PEupNyvU72pE
Click to expand...
Click to collapse
Now everything is fine, thank you

i downloaded occam-ktu84l-MODIFIED , connected Nexus 4 on my ubuntu in fastboot and ran script flash-all.sh but nothing happens , just < waiting for device > is shown.
can i install this zip it from custom recovery?

mrYogii said:
i downloaded occam-ktu84l-MODIFIED , connected Nexus 4 on my ubuntu in fastboot and ran script flash-all.sh but nothing happens, just waiting for device is shown.
can i install this zip it from custom recovery?
Click to expand...
Click to collapse
install drivers adb/fastboot, enable usb debug?http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312

pincher65 said:
install drivers adb/fastboot, enable usb debug?http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
Click to expand...
Click to collapse
all is set , adb devices gives device id

mrYogii said:
all is set , adb devices gives device id
Click to expand...
Click to collapse
adb? You needed fastboot mode

jd1639 said:
That's weird. Try this and please let me know if it works https://mega.co.nz/#!AAATiKpI!PJbBgroM6PB7tTAs_TanCOrlzAeqBq0PEupNyvU72pE
Click to expand...
Click to collapse
hi, this works for me also, thanks a lot, plz update OP for others also.

Flashed successful as well as new radio however flashing superuser though recovery does nothing... How to fix?

jd1639 said:
That's weird. Try this and please let me know if it works https://mega.co.nz/#!AAATiKpI!PJbBgroM6PB7tTAs_TanCOrlzAeqBq0PEupNyvU72pE
Click to expand...
Click to collapse
works great! thanks!

Worked great! all though i had to flash one-by-one cause i dont know how to use adb :cyclops:

my situation
Hello guys
I have tried to enter the adb commands into the command prompt but it says they are unrecognised and I dont know exactly why the adb will not fucntionhttp://forum.xda-developers.com/images/smilies/confused.gif. I think I may have disabled USB debuging by mistake before I had the bootloop.
BTW does this stock image work for the NEXUS 7 device

Gloftking said:
Hello guys
I have tried to enter the adb commands into the command prompt but it says they are unrecognised and I dont know exactly why the adb will not fucntionhttp://forum.xda-developers.com/images/smilies/confused.gif. I think I may have disabled USB debuging by mistake before I had the bootloop.
BTW does this stock image work for the NEXUS 7 device
Click to expand...
Click to collapse
First, it will not work on the n7. Just double click on the flash-all.bat file. Easier than entering any commands, they're fastboot commands by the way
Sent from my Nexus 5 using XDA Free mobile app

?
if it cannot work on the nexus 7 then for me there isnt much point. isnt there anything else that will be able to fix that

Gloftking said:
if it cannot work on the nexus 7 then for me there isnt much point. isnt there anything else that will be able to fix that
Click to expand...
Click to collapse
Then what are you doing in the n4 forum? Go to the n7 forum
Sent from my Nexus 5 using XDA Free mobile app

?
could you tell me were that is?

Nexus 6 stuck at google screen , Need Assistance.

So i tried flashing the factory image onto my rooted nexus 6 device manually , but while doing so i couldnt get the system.img to load as it kept saying "unable to allocate byte 1176........bytes" something like that. So i read about this error on some forums and they suggested to erase system , cache , userdata and then try flashing the stock image. Upon doing so it gave the same error and unable to load sys.img file.
Now , im stuck at the splash screen with stock recovery and bootloader working fine.
Im aware that my phone is bricked please advise what can i do to fix this issue.???
Thank you

I take it you placed the system.img in the platform-tools folder an you typed fastboot flash system system.img in cmd.
Sent from my Nexus 10 using XDA Free mobile app

faraz90 said:
So i tried flashing the factory image onto my rooted nexus 6 device manually , but while doing so i couldnt get the system.img to load as it kept saying "unable to allocate byte 1176........bytes" something like that. So i read about this error on some forums and they suggested to erase system , cache , userdata and then try flashing the stock image. Upon doing so it gave the same error and unable to load sys.img file.
Now , im stuck at the splash screen with stock recovery and bootloader working fine.
Im aware that my phone is bricked please advise what can i do to fix this issue.???
Thank you
Click to expand...
Click to collapse
First thing, do NOT lock your bootloader. Are you trying to use flash all? If so, do not. Flash the images separately.

Evolution_Tech said:
First thing, do NOT lock your bootloader. Are you trying to use flash all? If so, do not. Flash the images separately.
Click to expand...
Click to collapse
gee2012 said:
I take it you placed the system.img in the platform-tools folder an you typed fastboot flash system system.img in cmd.
Sent from my Nexus 10 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the quick reply.
Yes i did place is it under the platform tools folder and tried flashing separately as per the instructions given to flash manually.
I know that i should not lock the bootloader.
Im currently trying to flash using the toolkit "flash stock + unroot" and chose the current status "Softbricked/ bootloop in the bootloader mode.
Is this the right option or should i stop it ?
Thanks again for assistance.

faraz90 said:
Thanks for the quick reply.
Yes i did place is it under the platform tools folder and tried flashing separately as per the instructions given to flash manually.
I know that i should not lock the bootloader.
Im currently trying to flash using the toolkit "flash stock + unroot" and chose the current status "Softbricked/ bootloop in the bootloader mode.
Is this the right option or should i stop it ?
Thanks again for assistance.
Click to expand...
Click to collapse
the right option would be to flash the factory image the right way, via fastboot, and while in your bootloader.

simms22 said:
the right option would be to flash the factory image the right way, via fastboot, and while in your bootloader.
Click to expand...
Click to collapse
you mean it flashing it manually by placing the factory image in the platform tools folder ?
I tried that multiple times but it gave me the "could not allocate 721539744 bytes error: cannot load 'system.img" error :/

faraz90 said:
you mean it flashing it manually by placing the factory image in the platform tools folder ?
I tried that multiple times but it gave me the "could not allocate 721539744 bytes error: cannot load 'system.img" error :/
Click to expand...
Click to collapse
If your Android SDK is more than 6 months old, you may need to update it. Google updated fastboot to allow flashing these very large files.

faraz90 said:
you mean it flashing it manually by placing the factory image in the platform tools folder ?
Click to expand...
Click to collapse
No, by using fastboot commands.. The location of the images you flash is irrelevant.
faraz90 said:
I tried that multiple times but it gave me the "could not allocate 721539744 bytes error: cannot load 'system.img" error :/
Click to expand...
Click to collapse
Either there is a problem with the system.img (redownload) or there is a problem with the flash memory on your device.
You could flash a custom recovery and use that to flash a zipped ROM to see.if that makes any difference.

faraz90 said:
you mean it flashing it manually by placing the factory image in the platform tools folder ?
I tried that multiple times but it gave me the "could not allocate 721539744 bytes error: cannot load 'system.img" error :/
Click to expand...
Click to collapse
if you are using the flash-all, dont, as that gives many people problems as of lately. instead, you want to unzip and flash each partition separately.

Here is a detailled guide http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701 for how to flash a image, use method 2. Its the same for the N6 as for the N5.

simms22 said:
if you are using the flash-all, dont, as that gives many people problems as of lately. instead, you want to unzip and flash each partition separately.
Click to expand...
Click to collapse
gee2012 said:
Here is a detailled guide http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701 for how to flash a image, use method 2. Its the same for the N6 as for the N5.
Click to expand...
Click to collapse
I think he has already used fast boot to flash the system.img

rootSU said:
I think he has already used fast boot to flash the system.img
Click to expand...
Click to collapse
Maybe he used the wrong command like: fastboot flash system.img or something similar. If the img`s are in the correct folder and the commands are good it shouldn`t be a problem

I agree with @rootSU flash TWRP, flash factory zip from here:
http://forum.xda-developers.com/showthread.php?t=3066052

gee2012 said:
Maybe he used the wrong command like: fastboot flash system.img or something similar. If the img`s are in the correct folder and the commands are good it shouldn`t be a problem
Click to expand...
Click to collapse
Nope. He used the correct commands. There is no correct folder.

Evolution_Tech said:
I agree with @rootSU flash TWRP, flash factory zip from here:
http://forum.xda-developers.com/showthread.php?t=3066052
Click to expand...
Click to collapse
thanks a bunch. I have a few questions which could be noobish yet i would like to know.
- how can i flash the custom recovery when i cant place the files under the internal storage as my phone doesn't show when i connect it to the PC ?
- just like that im downloading the zip file but i would like to first access the internal storage to place the files under the root or is there a way around to do this ?
Thanks

faraz90 said:
thanks a bunch. I have a few questions which could be noobish yet i would like to know.
- how can i flash the custom recovery when i cant place the files under the internal storage as my phone doesn't show when i connect it to the PC ?
- just like that im downloading the zip file but i would like to first access the internal storage to place the files under the root or is there a way around to do this ?
Thanks
Click to expand...
Click to collapse
Flash TWRP, reboot to bootloader, select recovery mode, enter TWRP, mount MTP.

Evolution_Tech said:
Flash TWRP, reboot to bootloader, select recovery mode, enter TWRP, mount MTP.
Click to expand...
Click to collapse
You Sir, are a lifesaver. It worked!
Although for the sake of better understanding why do you think I wasn't able to flash the system image manually via fastboot ? having tried multiple times with correct fastboot commands :S
Thanks all for the help!

faraz90 said:
You Sir, are a lifesaver. It worked!
Although for the sake of better understanding why do you think I wasn't able to flash the system image manually via fastboot ? having tried multiple times with correct fastboot commands :S
Thanks all for the help!
Click to expand...
Click to collapse
*ahem*

rootSU said:
*ahem*
Click to expand...
Click to collapse
haha ofcourse thanks alot to you for suggesting that idea

faraz90 said:
Although for the sake of better understanding why do you think I wasn't able to flash the system image manually via fastboot ? having tried multiple times with correct fastboot commands :S
!
Click to expand...
Click to collapse
Possibly because your Android SDK tools are out of date(specifically fastboot).

[help] Locked bootloader, and stuck in bootloop with TWRP installed.

So I just bought a new phone and was getting ready to reset my Nexus 6 back to stock and relock the bootloader. Using Wugs toolkit I for some inexplicable reason relocked the bootloader before going stock. I got myself stuck in a boot loop but was eventually able to get into TWRP. Since I cannot unlock the bootloader without checking the box in the SW I want to flash a rom there but sdcard cannot mount in twrp and I am stuck. What should I attempt next or should I rma with Moto?

Bigsam411 said:
So I just bought a new phone and was getting ready to reset my Nexus 6 back to stock and relock the bootloader. Using Wugs toolkit I for some inexplicable reason relocked the bootloader before going stock. I got myself stuck in a boot loop but was eventually able to get into TWRP. Since I cannot unlock the bootloader without checking the box in the SW I want to flash a rom there but sdcard cannot mount in twrp and I am stuck. What should I attempt next or should I rma with Moto?
Click to expand...
Click to collapse
You must use fastboot commands.
fastboot format cache
fastboot format userdata
Then you can transfer a ROM from your PC and flash.

The_Merovingian said:
You must use fastboot commands.
fastboot format cache
fastboot format userdata
Then you can transfer a ROM from your PC and flash.
Click to expand...
Click to collapse
How can I transfer a rom to the phone? adb sideload in twrp does not seem to work and It will not mount storage.

Bigsam411 said:
How can I transfer a rom to the phone? adb sideload in twrp does not seem to work and It will not mount storage.
Click to expand...
Click to collapse
After issuing the fastboot commands I provided, MTP transfer should work.
Simply boot to TWRP after formatting from bootloader. Connect to PC, and you should see your device detected. Drag and drop the ROM in your internal storage.

Bigsam411 said:
How can I transfer a rom to the phone? adb sideload in twrp does not seem to work and It will not mount storage.
Click to expand...
Click to collapse
Should show as standard device storage like MTP. Not under adb. Should show as a drive.

The_Merovingian said:
After issuing the fastboot commands I provided, MTP transfer should work.
Simply boot to TWRP after formatting from bootloader. Connect to PC, and you should see your device detected. Drag and drop the ROM in your internal storage.
Click to expand...
Click to collapse
My phone shows up in windows Explorer but I cannot move anything over to it. I am in TWRP and cannot see the storage partition.

prdog1 said:
Should show as standard device storage like MTP. Not under adb. Should show as a drive.
Click to expand...
Click to collapse
It does show up but I am unable to transfer anything to it.

Bigsam411 said:
It does show up but I am unable to transfer anything to it.
Click to expand...
Click to collapse
Did you use the fastboot commands?

Bigsam411 said:
It does show up but I am unable to transfer anything to it.
Click to expand...
Click to collapse
Have seen this before. Try unplugging and plug back in. There is some way to access it. Never had to do it.

The_Merovingian said:
Did you use the fastboot commands?
Click to expand...
Click to collapse
I had previously tried those before opening this thread, then I tried them again just now. I attached the output from command prompt.

Ok I am now able to get to a point to where I can flash a rom and not get any errors (at least no visible ones) but I still get stuck at the boot screen with the colored dots animation. Is there a specific rom I should try to install?

Bigsam411 said:
Ok I am now able to get to a point to where I can flash a rom and not get any errors (at least no visible ones) but I still get stuck at the boot screen with the colored dots animation. Is there a specific rom I should try to install?
Click to expand...
Click to collapse
If want pure stock deodexed this is based on latest factory image. Wipe everything and flash per the OP.
http://forum.xda-developers.com/nexus-6/development/n6-shamu-lmy48i-deodexed-rooted-v1-0-08-t3176117

prdog1 said:
If want pure stock deodexed this is based on latest factory image. Wipe everything and flash per the OP.
http://forum.xda-developers.com/nexus-6/development/n6-shamu-lmy48i-deodexed-rooted-v1-0-08-t3176117
Click to expand...
Click to collapse
Thanks, I ended up finding a file that could be flashed via an adb command in twrp which let me issue the fastboot oem unlock command and I then flashed stock through twrp. I think I got it working now.

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)