Just installed TWRP and installed supersu by mistake on reboot... - Nexus 6 Q&A, Help & Troubleshooting

SO I just installed TWRP and went to reboot and mistakenly hit install supersu. Now the phone just keeps rebooting to the teamwin logo over and over.

sevron said:
SO I just installed TWRP and went to reboot and mistakenly hit install supersu. Now the phone just keeps rebooting to the teamwin logo over and over.
Click to expand...
Click to collapse
need more details on what ur trying to do. did u not flash a rom/kernel or anything

the_rooter said:
need more details on what ur trying to do. did u not flash a rom/kernel or anything
Click to expand...
Click to collapse
I'm still on the stock rom/kernel. All I did was unlock and flash twrp.

sevron said:
I'm still on the stock rom/kernel. All I did was unlock and flash twrp.
Click to expand...
Click to collapse
wipe dalvik and cache if u can

the_rooter said:
wipe dalvik and cache if u can
Click to expand...
Click to collapse
Can I do that if I can't get into recovery? I can only get to fastboot atm.

sevron said:
Can I do that if I can't get into recovery? I can only get to fastboot atm.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2225405

ADB doesn't list the device while it's in fastboot mode anymore. Is there anyways to get around that so I can actually reflash the stock recovery/system so I can get a working phone again or what?
I'm an idiot, was using the wrong usb cable lol. Trying to go through my wireless headsets hub.

sevron said:
ADB doesn't list the device while it's in fastboot mode anymore. Is there anyways to get around that so I can actually reflash the stock recovery/system so I can get a working phone again or what?
I'm an idiot, was using the wrong usb cable lol. Trying to go through my wireless headsets hub.
Click to expand...
Click to collapse
no, but fastboot does. just reflash stock using fastboot.

Thank you, I was trying to use adb to flash like an idiot -_- It's fastboot devices that sees it...
fastboot erase cache fixes it.

Related

[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

[RESOLVED] Bricked m7ul

Hello guys, I really messed up my phone.
I was trying to relock, and unroot my phone but it didnt go as planned.
Long story short, I cannot flash ANYTHING through CWM or TWRP (latest versions) and none of my files shows up in either of these recoveries. When i push a file through adb i get an error code on both. I believe that CWM said it cannot mount E:/SD Card.
I also have nothing to bootup to (bootloop)
I really need my phone and any help would be greatly appreciated!
mymonkeyballs said:
Hello guys, I really messed up my phone.
I was trying to relock, and unroot my phone but it didnt go as planned.
Long story short, I cannot flash ANYTHING through CWM or TWRP (latest versions) and none of my files shows up in either of these recoveries. When i push a file through adb i get an error code on both. I believe that CWM said it cannot mount E:/SD Card.
I also have nothing to bootup to (bootloop)
I really need my phone and any help would be greatly appreciated!
There will be a cash reward for the person to help me get this working. (paypal)
Click to expand...
Click to collapse
Just calm down buddy... This is the second thread you've made so far. Now I'm going to help you and I dont want any of your money. I just want you to agree on one term and that is to not make another thread about this.
That sucks balls MyMonkeyBalls..
Yeah, has happened to me too, I had to send in to get fixed, been 3 weeks so far.
Have a read over the forums for mine and others same issue, there are tips on how to fix but this is becoming very common at the moment, I can not offer any suggestions because everything i did did not work
Good luck
Tw1tchy said:
Just calm down buddy... This is the second thread you've made so far. Now I'm going to help you and I dont want any of your money. I just want you to agree on one term and that is to not make another thread about this.
Click to expand...
Click to collapse
Sorry bro , just freaking out. Agreed.
twerg said:
That sucks balls MyMonkeyBalls..
Click to expand...
Click to collapse
LOL!!
anyways...
what build of CM10.2 was it (example: cm-10.2-20130809-UNOFFICIAL-m7ul.zip)?
Kernel?
Firmware? (or Hboot#)
Do you have nandroid?
have you tried to go to stock?
S-OFF?
locked/relocked/unlocked?
logcats? (twrp or cwm)
ATT, TMO, Sprint, GPE, etc?
Any other info?
Tw1tchy said:
LOL!!
anyways...
what build of CM10.2 was it (example: cm-10.2-20130809-UNOFFICIAL-m7ul.zip)?
Kernel?
Firmware? (or Hboot#)
Do you have nandroid?
have you tried to go to stock?
S-OFF?
locked/relocked/unlocked?
logcats? (twrp or cwm)
ATT, TMO, Sprint, GPE, etc?
Any other info?
Click to expand...
Click to collapse
cm-10.2-20130815-UNOFFICIAL-m7ul_doubleTap.zip
Kernel that came with the ROM
1.44.0000
I dont believe I have a nandroid anymore, if i do it would be TWRP's.
I cant get back to stock
S-On
Unlocked
No
Bell (unlocked)
Nothing is showing up in Twrp or CWM its like i have nothing installed on my device. I have a constant bootloop with the cm10.2 boot animation.
I believe it all started going crazy when i tried to go back to stock and wipe the data (i did a factory reset from hboot as well as cwm)
mymonkeyballs said:
cm-10.2-20130815-UNOFFICIAL-m7ul_doubleTap.zip
Kernel that came with the ROM
1.44.0000
I dont believe I have a nandroid anymore, if i do it would be TWRP's.
I cant get back to stock
S-On
Unlocked
No
Bell (unlocked)
Nothing is showing up in Twrp or CWM its like i have nothing installed on my device. I have a constant bootloop with the cm10.2 boot animation.
Click to expand...
Click to collapse
Before LC's CM10.2 were you running a 4.1.2 rom?
Tw1tchy said:
Before LC's CM10.2 were you running a 4.1.2 rom?
Click to expand...
Click to collapse
No. 4.2.2
mymonkeyballs said:
No. 4.2.2
Click to expand...
Click to collapse
Okay well that rules out the simple.
Now lets see if i understand the situation correctly. If you try to boot into system all you get is a CM bootloop and custom recovery's show an empty sdcard? You say adb commands dont work but have you tried fastboot commands in fastboot mode yet?
Try:
fastboot devices
fastboot erase cache
fastboot reboot-recovery
Dude - he's done a factory reset from the bootloader which has wiped his virtual sd card. You basically need to format it back into a fat32 partition so the adb side load will work.
Sent from my HTC One using XDA Premium 4 mobile app
Tw1tchy said:
Okay well that rules out the simple.
Now lets see if i understand the situation correctly. If you try to boot into system all you get is a CM bootloop and custom recovery's show an empty sdcard? You say adb commands dont work but have you tried fastboot commands in fastboot mode yet?
Try:
fastboot devices
fastboot erase cache
fastboot reboot-recovery
Click to expand...
Click to collapse
Yes. Fastboot commands work but doesnt resolve my issue.
thejosh86 said:
Dude - he's done a factory reset from the bootloader which has wiped his virtual sd card. You basically need to format it back into a fat32 partition so the adb side load will work.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
So what do I have to do sorry
I've done this before a long time ago now myself and was able to fix it because I could still boot into my rom and windows would offer to format it for me.
There used to be a guide in the One XL forum with a step by step even a youtube how to fix it - just trying to find it now.
Edit: Okay found it - full props to XsMagical for this fix.
Youtube is here: http://www.youtube.com/watch?v=H-vf5eHV3_s&feature=youtu.be
Original XDA Post here: http://forum.xda-developers.com/showthread.php?t=1942605
It's for a One XL but the principle is the same as they both use Virtual SD Cards.
Make sure you're in the bootloader go into fastboot
Download the stock recovery from this link: https://www.dropbox.com/s/v7byetxqc2ogzqq/recovery144.img
Make sure the downloaded image is in the same folder as your fastboot.
fastboot flash recovery recovery144.img
fastboot erase cache
fastboot reboot-bootloader
Go into bootloader and then choose Factory Reset - let that finish running
Go into fastboot
fastboot flash recovery <custom recovery>.img
fastboot erase cache
fastboot reboot-bootloader
Now you can go into recovery and try sideloading a rom and then flashing it.
thejosh86 said:
I've done this before a long time ago now myself and was able to fix it because I could still boot into my rom and windows would offer to format it for me.
There used to be a guide in the One XL forum with a step by step even a youtube how to fix it - just trying to find it now.
Click to expand...
Click to collapse
I would highly appreciate that. Thanks bro
thejosh86 said:
I've done this before a long time ago now myself and was able to fix it because I could still boot into my rom and windows would offer to format it for me.
There used to be a guide in the One XL forum with a step by step even a youtube how to fix it - just trying to find it now.
Edit: Okay found it - full props to XsMagical for this fix.
Youtube is here: http://www.youtube.com/watch?v=H-vf5eHV3_s&feature=youtu.be
It's for a One XL but the principle is the same as they both use Virtual SD Cards.
Make sure you're in the bootloader go into fastboot
Download the stock recovery from this link: https://www.dropbox.com/s/v7byetxqc2ogzqq/recovery144.img
Make sure the downloaded image is in the same folder as your fastboot.
fastboot flash recovery recovery144.img
fastboot erase cache
fastboot reboot-bootloader
Go into bootloader and then choose Factory Reset - let that finish running
Go into fastboot
fastboot flash recovery <custom recovery>.img
fastboot erase cache
fastboot reboot-bootloader
Now you can go into recovery and try sideloading a rom and then flashing it.
Click to expand...
Click to collapse
Thanks ! Testing it now. Will update.
thejosh86 said:
I've done this before a long time ago now myself and was able to fix it because I could still boot into my rom and windows would offer to format it for me.
There used to be a guide in the One XL forum with a step by step even a youtube how to fix it - just trying to find it now.
Edit: Okay found it - full props to XsMagical for this fix.
Youtube is here: http://www.youtube.com/watch?v=H-vf5eHV3_s&feature=youtu.be
Original XDA Post here: http://forum.xda-developers.com/showthread.php?t=1942605
It's for a One XL but the principle is the same as they both use Virtual SD Cards.
Make sure you're in the bootloader go into fastboot
Download the stock recovery from this link: https://www.dropbox.com/s/v7byetxqc2ogzqq/recovery144.img
Make sure the downloaded image is in the same folder as your fastboot.
fastboot flash recovery recovery144.img
fastboot erase cache
fastboot reboot-bootloader
Go into bootloader and then choose Factory Reset - let that finish running
Go into fastboot
fastboot flash recovery <custom recovery>.img
fastboot erase cache
fastboot reboot-bootloader
Now you can go into recovery and try sideloading a rom and then flashing it.
Click to expand...
Click to collapse
HALLELUJAH !! She is working ! Words cannot describe how happy i am ! i thought i was done! THANK YOU!
hahaha no worries mate, it's all part of the learning process.
Now just remember when you've got a custom recovery you don't need to use the factory reset in bootloader!
We saved mymonkeyballs =D
Sent from my One using xda app-developers app
thejosh86 said:
I've done this before a long time ago now myself and was able to fix it because I could still boot into my rom and windows would offer to format it for me.
There used to be a guide in the One XL forum with a step by step even a youtube how to fix it - just trying to find it now.
Edit: Okay found it - full props to XsMagical for this fix.
Youtube is here: http://www.youtube.com/watch?v=H-vf5eHV3_s&feature=youtu.be
Original XDA Post here: http://forum.xda-developers.com/showthread.php?t=1942605
It's for a One XL but the principle is the same as they both use Virtual SD Cards.
Make sure you're in the bootloader go into fastboot
Download the stock recovery from this link: https://www.dropbox.com/s/v7byetxqc2ogzqq/recovery144.img
Make sure the downloaded image is in the same folder as your fastboot.
fastboot flash recovery recovery144.img
fastboot erase cache
fastboot reboot-bootloader
Go into bootloader and then choose Factory Reset - let that finish running
Go into fastboot
fastboot flash recovery <custom recovery>.img
fastboot erase cache
fastboot reboot-bootloader
Now you can go into recovery and try sideloading a rom and then flashing it.
Click to expand...
Click to collapse
thejosh86 said:
hahaha no worries mate, it's all part of the learning process.
Now just remember when you've got a custom recovery you don't need to use the factory reset in bootloader!
Click to expand...
Click to collapse
Haha, that was kinda stupid now that i look back on it. I cannot say thank you enough!
mymonkeyballs said:
Haha, that was kinda stupid now that i look back on it. I cannot say thank you enough!
Click to expand...
Click to collapse
Hey dude, don't forget to put [Resolved] in the thread title.

[Q] Unlocked bootloader, Install Philz CWM using fastboot method?

I've unlocked the bootloader. Now I want to install a CWM variant recovery. There seems to be some conflicting information on this procedure. I just wanted to check on the proper procedure.
I use the fastboot method and flash the zip or the img?
Thanks for any tips.
I've flashed the img, when I type abd reboot recovery I get device not found.
LOLz
Should I run abd.exe again or do I need USB debugging authorization?
BlackJin10dan said:
I've unlocked the bootloader. Now I want to install a CWM variant recovery. There seems to be some conflicting information on this procedure. I just wanted to check on the proper procedure.
I use the fastboot method and flash the zip or the img?
Thanks for any tips.
Click to expand...
Click to collapse
Where exactly are you getting the information on installing a custom recovery?
You'll need to be in the Bootloader under Fastboot. It should say Fastboot USB when you connect the phone to the USB cable connected to the computer.
Issue the following command: fastboot flash recovery your_recovery_image.img
In my case, it was fastboot flash recovery philz_touch_6.26.6-m8spr.img
skizzled said:
Where exactly are you getting the information on installing a custom recovery?
You'll need to be in the Bootloader under Fastboot. It should say Fastboot USB when you connect the phone to the USB cable connected to the computer.
Issue the following command: fastboot flash recovery your_recovery_image.img
In my case, it was fastboot flash recovery philz_touch_6.26.6-m8spr.img
Click to expand...
Click to collapse
That's what I did. Now I am ready for the SuperSU.zip Any suggestions?
BlackJin10dan said:
That's what I did. Now I am ready for the SuperSU.zip Any suggestions?
Click to expand...
Click to collapse
Honestly, I don't remember exactly how I did the whole SuperSU thing. I think I just let the recovery install it.
Now, I'm using a custom ROM that has root built in, which is the easiest method.
Check this thread:
http://forum.xda-developers.com/showthread.php?t=1538053
skizzled said:
Honestly, I don't remember exactly how I did the whole SuperSU thing. I think I just let the recovery install it.
Now, I'm using a custom ROM that has root built in, which is the easiest method.
Check this thread:
http://forum.xda-developers.com/showthread.php?t=1538053
Click to expand...
Click to collapse
Thank you. I'll check the recovery.
The recovery will handle all cache wipes? Or not necessary?
BlackJin10dan said:
The recovery will handle all cache wipes? Or not necessary?
Click to expand...
Click to collapse
Some ROMs do their own spring cleaning when you flash them.
Though, you can clear the cache using the recovery. I always have.
There are also zips that you can flash that will handle the cleaning as well but I don't know if they can be used on the M8 as I haven't bothered with any of them yet.
skizzled said:
Some ROMs do their own spring cleaning when you flash them.
Though, you can clear the cache using the recovery. I always have.
There are also zips that you can flash that will handle the cleaning as well but I don't know if they can be used on the M8 as I haven't bothered with any of them yet.
Click to expand...
Click to collapse
Thanks again. Wish me luck!

[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.

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)

Categories

Resources