Database Develop

[SOLVED] Stuck on X - HELP!?

ADDING THE LINK HERE NOW : https://www.dropbox.com/s/it4ji9mlohfgagf/NexusOne-rescue-tools.zip
And please, a THANKS would be great if this helped you.
For some reason the phone one day just didn't boot. Was stuck on X logo.
We have tried alot... can't get into recovery, so flashed custom recovery, both RA and CWM... can't get into any of them, just stuck on X.
The phone was stock, and unrooted.
We managed to unlock bootloader via fastboot and root it.
Tried the PASSIMG.ZIP method - not working.
Any ideas?
.... please? =(
EDIT: Problem solved! Send me a PM if you're in the same seat, and i could send you all the files you need.
Oh, all you need is your FASTBOOT to work, no need for ADB, since it didn't work for me either.
EDIT #2:
The reason is that i have a file (ADB, and all the *.img's) needed on my server, and don't wanna post the link here so that's why i have done it thru PM.
But i'll update the first post and just delete the link, so when anyone needs it they can PM me.
So far (2012-02-10) 14 phones confirmed back up running, including mine. Got 2 unconfirmed, and just sent 5 PM's to guys with the same problem.
*** PM ME FOR THE LINK TO THE *.ZIP ***
Unzip, open an command promt, and:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash radio radio.img
fastboot flash system system.img
do the commands in that order, and when you are done reboot the phone
and see if it boots.
if NOT: keep on flashing ONLY the boot.img again and again until it
boots. it seems like the boot partition is corrupted and may need alot
of flashing until it works.
i think i flashed like 100 times before it booted. =)
There is also another recovery in that zip... RA's recovery. You can also try that one, no harm done!
Once you get it to boot, you will have FroYo 2.2 installed.
If you got it to boot with recovery.img just let android update to latest (2.3.7?)
If you have RA's recovery, just flash back recovery.img or you wont be able to upgrade to 2.3.7 "the stock way"

Can you boot without sd card?
Maybe Hardware--

rugmankc said:
Can you boot without sd card?
Maybe Hardware--
Click to expand...
Click to collapse
Sorry, no. Not booting when i remove sdcard either.
:/

May be hardware

rugmankc said:
May be hardware
Click to expand...
Click to collapse
How do i find out?
When we searched yesterday (google), we found some ppl who had fixed it, now i can't find those pages again..
So anyone here who knows what to try?

I've been in a similar situation before and just kept fastboot flashing system, recovery, and boot, and eventually I recovered the phone...

I assume since you mentioned that you unlocked the bootloader, that you can get into fastboot? If so, flash a custom recovery (I'd recommend CWM since it includes an option to wipe the system partition) and boot into it.
Code:
fastboot flash recovery "c:\location\to\recovery.img
fastboot boot recovery "c:\location\to\recovery.img
If you can get that far, wipe your /system partition and do a factory reset. Then install CM7 (or whatever ROM you want) and gapps.

bassmadrigal said:
I assume since you mentioned that you unlocked the bootloader, that you can get into fastboot? If so, flash a custom recovery (I'd recommend CWM since it includes an option to wipe the system partition) and boot into it.
Code:
fastboot flash recovery "c:\location\to\recovery.img
fastboot boot recovery "c:\location\to\recovery.img
If you can get that far, wipe your /system partition and do a factory reset. Then install CM7 (or whatever ROM you want) and gapps.
Click to expand...
Click to collapse
Thanks!
But we have tried to fastboot system.img, boot.img and recovery.img
Still stuck on X.
Is that code any different perhaps?
I can't try that now, that's why i ask instead of try it =)

All the commands that I posted are supposed to do is install a custom recovery and then boot into it. From recovery, you need to wipe your device by wiping the /system partition and doing a Factory Reset/Data Wipe. Then install whatever ROM you want to.
I've never tried using fastboot to install the system image, so I can't comment on that at all.

O M G!!!
i actually got the phone up and running!! everything is working now, i'm just too awesome
If anyone is interested, i could find out what i did, and which files i flashed, etc etc.

Just an update:
(mostly to bump this)
3 more ppl who had the same problem has now got this fixed

Woa, check your PM

Check you inbox buddy! Tack på förhand

mrBira said:
Just an update:
(mostly to bump this)
3 more ppl who had the same problem has now got this fixed
Click to expand...
Click to collapse
Is it an illegal method, or is there another reason why a fix like this you're only sharing by PM instead of posting it here? I sent you a PM over 24hrs ago and haven't heard back yet. I would think making one helpful post would be much easier than getting irritated at replying to each of 10-100+ PMs

NismoDrift240 said:
Is it an illegal method, or is there another reason why a fix like this you're only sharing by PM instead of posting it here? I sent you a PM over 24hrs ago and haven't heard back yet. I would think making one helpful post would be much easier than getting irritated at replying to each of 10-100+ PMs
Click to expand...
Click to collapse
HEHEH... illegal
No, ofc not (is there any way to fix a phone that's not legal?).
The reason is that i have a file (ADB, and all the *.img's) needed on my server, and don't wanna post the link here so that's why i have done it thru PM.
But i'll update the first post and just delete the link, so when anyone needs it they can PM me.
So far 14 phones confirmed back up running, including mine. Got 2 unconfirmed, and just sent 5 PM's to guys with the same problem.

mrBira said:
HEHEH... illegal
No, ofc not (is there any way to fix a phone that's not legal?).
The reason is that i have a file (ADB, and all the *.img's) needed on my server, and don't wanna post the link here so that's why i have done it thru PM.
But i'll update the first post and just delete the link, so when anyone needs it they can PM me.
So far 14 phones confirmed back up running, including mine. Got 2 unconfirmed, and just sent 5 PM's to guys with the same problem.
Click to expand...
Click to collapse
That makes perfect sense, I'm the same way. Thanks for getting back to me, here's to hoping I make 15...

same prob.
I sent you a PM, bro. Get back to me as soon as you can! Thanks!

Nexus One recovery boot error
PM sent. Thank you for your assistance.

i would like to know how to you solve the problem

No recovery for unrooted fones
first root ur phone using passimg.img
and fastboot flash bootloard oem unlock etc
and then try to flash a recovery using
fastboot flash recovery recovery.img
then u r done
Thank if it helps u

[Q] How To Root HTC One Google Edition?

Hi everyone I'm an experienced rooter and am having trouble finding a method to root the Google Play Edition HTC One. Can anyone link me to a method or let me know how to do it?

If you have the HTC ge ...I asumme since you're experienced you have knowledge of adb and fastboot...if so all it takes is fastboot oem unlock
Then flash recovery of your choice and so on

Nxxx said:
Hi everyone I'm an experienced rooter and am having trouble finding a method to root the Google Play Edition HTC One. Can anyone link me to a method or let me know how to do it?
Click to expand...
Click to collapse
I've mine unlocked with "fastboot oem unlock", but I'm not able to root the phone. In fact, I think I've lost my stock recovery, I didn't check it before unlock, so I'm not even sure if the recovery had been missing before the phone was unlocked. When I try to boot into recovery now, all I get is an android robot on its belly with a red warning triangle on it. I also can't boot/flash custom recovery either, adb seems the phone just fine, but it tries to push the recovery, the phone just freeze up.
Someone else on android central forum also has his stock recovery missing right out of the box, getting the same belly-up robot as mine, very strange.

mickey4mice said:
I've mine unlocked with "fastboot oem unlock", but I'm not able to root the phone. In fact, I think I've lost my stock recovery, I didn't check it before unlock, so I'm not even sure if the recovery had been missing before the phone was unlocked. When I try to boot into recovery now, all I get is an android robot on its belly with a red warning triangle on it. I also can't boot/flash custom recovery either, adb seems the phone just fine, but it tries to push the recovery, the phone just freeze up.
Someone else on android central forum also has his stock recovery missing right out of the box, getting the same belly-up robot as mine, very strange.
Click to expand...
Click to collapse
I unlocked bootoader on mine using fastboot oem unlock. I just flashed twrp image and then installed SuperSU.
I wanted to unroot and that gave me trouble. Used recovery and factory images I found laying around the forums. Still don't know if I did it right.

mdandashly said:
I unlocked bootoader on mine using fastboot oem unlock. I just flashed twrp image and then installed SuperSU.
I wanted to unroot and that gave me trouble. Used recovery and factory images I found laying around the forums. Still don't know if I did it right.
Click to expand...
Click to collapse
can you post the link to stock recovery you found? I couldn't flash the stock recovery image I found on the forum, says "different signature".

mickey4mice said:
can you post the link to stock recovery you found? I couldn't flash the stock recovery image I found on the forum, says "different signature".
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2358781
Got it from this post. I also used to stock factory image from that post as well.
I'm frustrated because my battery life is pretty bad and when I check stats, the kernel is consuming 25% of battery. Any idea what gives?

mdandashly said:
I unlocked bootoader on mine using fastboot oem unlock. I just flashed twrp image and then installed SuperSU.
I wanted to unroot and that gave me trouble. Used recovery and factory images I found laying around the forums. Still don't know if I did it right.
Click to expand...
Click to collapse
Also, did you get "FAILED (status read failed (Too many links))" when unlock? Mine unlocked just fine but I don't if that error msg at the end of the process effected anything else.

mickey4mice said:
Also, did you get "FAILED (status read failed (Too many links))" when unlock? Mine unlocked just fine but I don't if that error msg at the end of the process effected anything else.
Click to expand...
Click to collapse
Yeah it may have said failed. But everything seems to have worked. I'm just trying to get back to stock bc I may need to RMA.

You do know the Android on it's back is the stock recovery?...

EddyOS said:
You do know the Android on it's back is the stock recovery?...
Click to expand...
Click to collapse
Yeah, but mine is the belly-up android without any menu or means to get into recovery menu. Maybe I missed something?
---------- Post added at 08:32 PM ---------- Previous post was at 08:17 PM ----------
mickey4mice said:
Yeah, but mine is the belly-up android without any menu or means to get into recovery menu. Maybe I missed something?
Click to expand...
Click to collapse
Arrrhhh...never mind. I finally brought up the recovery menu by pressing the power+vol up/down buttons REALLY REALLY HARD! I tried this combo for 3 days without success, I think the vol up button is finally loosening up, weird I don't have any problem using it on the phone, just in the recovery mode.

Stock recovery really doesn't have anything you can do In it

a box of kittens said:
Stock recovery really doesn't have anything you can do In it
Click to expand...
Click to collapse
Yes, but all I need is gain root and keep stock for OTA, don't want to flash back and forth every time an update comes in.
Sideloading CWM "fastboot boot recovery-clockwork-touch-6.0.3.1-m7.img" isn't working for me, keep stuck on downloading...nothing happens.

mickey4mice said:
Yes, but all I need is gain root and keep stock for OTA, don't want to flash back andrth every time an update comes in.
Sideloading CWM "fastboot boot recovery-clockwork-touch-6.0.3.1-m7.img" isn't working for me, keep stuck on downloading...nothing happens.
Click to expand...
Click to collapse
A bit confused on what command you're trying...do you want to flash cwm? Then " fastboot flash recovery recovery.img"

a box of kittens said:
A bit confused on what command you're trying...do you want to flash cwm? Then " fastboot flash recovery recovery.img"
Click to expand...
Click to collapse
I don't want to permanently flash a custom recovery like CWM, only want to sideload it to flash SuperSU and gain root. The command I use is "fastboot boot recovery.img" where recovery.img being the name of CWM. Don't know why it's not working though.

mickey4mice said:
Yeah, but mine is the belly-up android without any menu or means to get into recovery menu. Maybe I missed something?.
Click to expand...
Click to collapse
Yes, that's the stock recovery. You then have to press power + volume up (in the case of the Nexus 4, for example). You have to manually flash CWM as you would for the normal One
e.g. fastboot flash recovery recovery.img
You apparently can no longer 'boot' into CWM - you have to flash it

[Q] Bricked Nexus 6 PLEASE HELP!!

Trying to sell my Nexus 6 I believe I bricked it. After rooting the device I used Chainfire 3d program and it made me stuck on google sign. I tried literally everything. I can boot into teamwin TWR recovery. I tried factory resetting wiping cache and delvic. Problem is my bootloader is coming up locked. Tried using fastboot many times to flash everything back keep getting remote failure. Need help, is it possible im just screwed at this point. Ive used about everything it is just stuck saying Google. PLEASE HELP!!!!

chainfires 3d program hasnt worked on a nexus in years. and you do need to boot back up to enable unlocking the bootloader in the developer options. have you tried wiping data in twrp recovery?

zacrivera24 said:
Trying to sell my Nexus 6 I believe I bricked it. After rooting the device I used Chainfire 3d program and it made me stuck on google sign. I tried literally everything. I can boot into teamwin TWR recovery. I tried factory resetting wiping cache and delvic. Problem is my bootloader is coming up locked. Tried using fastboot many times to flash everything back keep getting remote failure. Need help, is it possible im just screwed at this point. Ive used about everything it is just stuck saying Google. PLEASE HELP!!!!
Click to expand...
Click to collapse
Relax, deep breath. You need to use fastboot from bootloader. Issue these commands:
fastboot format cache
fastboot format userdata
That should get you into TWRP and from there you can transfer a ROM to internal, flash it and go from there.

Evolution_Freak said:
Relax, deep breath. You need to use fastboot from bootloader. Issue these commands:
fastboot format cache
fastboot format userdata
That should get you into TWRP and from there you can transfer a ROM to internal, flash it and go from there.
Click to expand...
Click to collapse
well, he wrote that he can boot into twrp recovery already. wiping data should fix his use of chainfires app. but flashing a new rom would do the same

simms22 said:
well, he wrote that he can boot into twrp recovery already. wiping data should fix his use of chainfires app. but flashing a new rom would do the same
Click to expand...
Click to collapse
Yeah, guess I missed that part.

Evolution_Freak said:
Yeah, guess I missed that part.
Click to expand...
Click to collapse
thinking about it now.. with the bootloader locked, would twrp let you flash anything?

simms22 said:
thinking about it now.. with the bootloader locked, would twrp let you flash anything?
Click to expand...
Click to collapse
Yes, it has been done to fix the soft brick I thought we were dealing with here. Only if TWRP is installed though.

Doesn't chainfire 3d modify system? I though it did. May need to flash a rom zip after a factory reset.

rootSU said:
Doesn't chainfire 3d modify system? I though it did. May need to flash a rom zip after a factory reset.
Click to expand...
Click to collapse
honestly, i dont remember. its been about 3-4 years since last thinking of that app. if it does, a rom flash would be needed.

Unable to flash custom recovery on Marshmallow

Hi. I'm on Marshmallow and whenever I try to install recovery via fastboot, I go down to recovery and boot it, but it always goes to the battery charging logo and reboots.
Any ideas on how to solve this?
Thanks!

Sesamechicken said:
Hi. I'm on Marshmallow and whenever I try to install recovery via fastboot, I go down to recovery and boot it, but it always goes to the battery charging logo and reboots.
Any ideas on how to solve this?
Thanks!
Click to expand...
Click to collapse
Is your bootloader unlocked?
Are you flashing recovery like this:
fastboot flash recovery twrp-3.0.2-1-victara.img
Then booting into recovery right away?

Yes my bootloader is unlocked and yes that's exactly how I flash it (except I named it recovery)
And yes, I boot into recovery right away via the bootloader options.

Gus Ghanem said:
Is your bootloader unlocked?
Are you flashing recovery like this:
fastboot flash recovery twrp-3.0.2-1-victara.img
Then booting into recovery right away?
Click to expand...
Click to collapse
Forgot to quote sorry

Sesamechicken said:
Yes my bootloader is unlocked and yes that's exactly how I flash it (except I named it recovery)
And yes, I boot into recovery right away via the bootloader options.
Click to expand...
Click to collapse
What is the phone booting into? Stock?
If you have the latest stock firmware files, try:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash recovery recovery.img
Only use TWRP or Cyanogen Recovery, they are the only ones supported.

Gus Ghanem said:
What is the phone booting into? Stock?
If you have the latest stock firmware files, try:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash recovery recovery.img
Only use TWRP or Cyanogen Recovery, they are the only ones supported.
Click to expand...
Click to collapse
OK I will try that. Stock marshmallow right?
I was on complete stock and used windroid to unlock bootloader and I was aware of the problem whilst installing custom recovery.
Am I able to flash SuperSU via flash boot since that's mainly what I'm looking for?
Thanks
Sent from my XT1095 using XDA-Developers mobile app

Sesamechicken said:
OK I will try that. Stock marshmallow right?
I was on complete stock and used windroid to unlock bootloader and I was aware of the problem whilst installing custom recovery.
Am I able to flash SuperSU via flash boot since that's mainly what I'm looking for?
Thanks
Sent from my XT1095 using XDA-Developers mobile app
Click to expand...
Click to collapse
Make sure you never downgrade the bootloader or partition table, so yes, use the latest Android 6.0 MarshMallow firmware, in case something gets corrupted and you need to reflash the partition table and/or bootloader, or even the full stock firmware, so you can start again.
Flashing SuperSU is always risky, and I've never done it; I only use CM's built-in Root Access.

Gus Ghanem said:
Make sure you never downgrade the bootloader or partition table, so yes, use the latest Android 6.0 MarshMallow firmware, in case something gets corrupted and you need to reflash the partition table and/or bootloader, or even the full stock firmware, so you can start again.
Flashing SuperSU is always risky, and I've never done it; I only use CM's built-in Root Access.
Click to expand...
Click to collapse
Just tried that to no avail.
Is there anyway to root without having a custom recovery?

Sesamechicken said:
Just tried that to no avail.
Is there anyway to root without having a custom recovery?
Click to expand...
Click to collapse
I really don't know, as I only have the one phone, and don't want to take any risks with, I never looked into rooting, and never needed it anyway. But if I ever need the odd root access, CyanogenMod does it for me.
There are apps like King Root, which I've never used:
https://kingroot.net/
TRY AT YOUR OWN RISK.

Gus Ghanem said:
I really don't know, as I only have the one phone, and don't want to take any risks with, I never looked into rooting, and never needed it anyway. But if I ever need the odd root access, CyanogenMod does it for me.
There are apps like King Root, which I've never used:
https://kingroot.net/
TRY AT YOUR OWN RISK.
Click to expand...
Click to collapse
Ok, so I tried the Kingroot method and it took out my wifi and cellular network (doesn't turn on).
So I flashed the system files in the marshmallow and now my system doesn't boot. xD!
One question: is there any single marshmallow system zip file I could flash in one go to increase chances of resurrection? What's annoying is that I can't seem to get custom recovery working.
Thanks

Gus Ghanem said:
I really don't know, as I only have the one phone, and don't want to take any risks with, I never looked into rooting, and never needed it anyway. But if I ever need the odd root access, CyanogenMod does it for me.
There are apps like King Root, which I've never used:
https://kingroot.net/
TRY AT YOUR OWN RISK.
Click to expand...
Click to collapse
Nevermind! I am so f****ng stupid!!!!
I NEVER ACTUALLY SELECTED USING UP VOLUME I ALWAYS CLICKED THE POWER BUTTON WHICH REBOOTED. I AM ACTUALLY SO STUPID.
Thanks anyways!

Sesamechicken said:
Ok, so I tried the Kingroot method and it took out my wifi and cellular network (doesn't turn on).
So I flashed the system files in the marshmallow and now my system doesn't boot. xD!
One question: is there any single marshmallow system zip file I could flash in one go to increase chances of resurrection? What's annoying is that I can't seem to get custom recovery working.
Thanks
Click to expand...
Click to collapse
Since we don't know for sure what's causing it not to boot, might as well flash the whole fimware, I think you can paste all the commands at once, or create a batch file in the firmware folder, flash.bat, shift+right-click, open command window here... type flash.bat
Or you can use RSD Lite
If/when you lose signal/data/wifi you can try flashing just the modems from stock:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn

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)