Hello everyone,
I tried to flash TWRP on my Z3 play today and got stuck on the TWRP logo screen. Since I am a noob, i will try to give a detailed describtion of what i have done so far.
I started by going into debuggingn mode and unlocking to bootloader following the guide unlock-bootloader-moto-z3-play from getdroidtips
This worked as far as i can tell. Today I wanted to get TWRP running as this seemed like the next step to take. Again i followed the getdroidtips guide twrp-recovery-moto-z3-play/ which linkes to flash-twrp-recovery-android. Here I didnt install Odin and Android Kies, because these seem to be Samsung-specific? I followed all other steps and arrived at the command line "fastboot flash recovery recovery.img" which didnt work, but gave the error message "invalid partition name recovery". After googling a bit I found that "fastboot boot recovery.img" should boot TWRP and that I could procced from there. At first it looked as if TWRP would actually boot, but then it got stuck in the logo screen and is sitting at that for an hour now.
Did I brick my phone? And can I fix this somehow?
Any help would be greatly appreciated.
Thank you.
Dunsinan said:
Hello everyone,
I tried to flash TWRP on my Z3 play today and got stuck on the TWRP logo screen. Since I am a noob, i will try to give a detailed describtion of what i have done so far.
I started by going into debuggingn mode and unlocking to bootloader following the guide unlock-bootloader-moto-z3-play from getdroidtips
This worked as far as i can tell. Today I wanted to get TWRP running as this seemed like the next step to take. Again i followed the getdroidtips guide twrp-recovery-moto-z3-play/ which linkes to flash-twrp-recovery-android. Here I didnt install Odin and Android Kies, because these seem to be Samsung-specific? I followed all other steps and arrived at the command line "fastboot flash recovery recovery.img" which didnt work, but gave the error message "invalid partition name recovery". After googling a bit I found that "fastboot boot recovery.img" should boot TWRP and that I could procced from there. At first it looked as if TWRP would actually boot, but then it got stuck in the logo screen and is sitting at that for an hour now.
Did I brick my phone? And can I fix this somehow?
Any help would be greatly appreciated.
Thank you.
Click to expand...
Click to collapse
Just like the Google search you used, there's a search here on XDA. Your problem has been addressed many times.
Instead of creating a new Topic/thread, ideally you could've and should've first searched the TWRP Z3 thread. Then asked questions about TWRP in The TWRP thread.
kewlzter said:
Just like the Google search you used, there's a search here on XDA. Your problem has been addressed many times.
Instead of creating a new Topic/thread, ideally you could've and should've first searched the TWRP Z3 thread. Then asked questions about TWRP in The TWRP thread.
Click to expand...
Click to collapse
Oh, I am sorry if this is a duplicate. I searched the forum before and didnt find my problem. I will look again.
Thanks for the quick response
Dunsinan said:
Oh, I am sorry if this is a duplicate. I searched the forum before and didnt find my problem. I will look again.
Thanks for the quick response
Click to expand...
Click to collapse
Did you find the solution?
hint: 3.3.1.0
Okay, I am an idiot.
Thanks to your hint I figured out that I had to use TWRP 3.3.1.0 to not get stuck. This worked, but I accidentaly flashed TWRP to boot instead of recovery.
When i tried to flash to recovery i got: "Invalid partition name recovery"
What can I do now?
Dunsinan said:
Okay, I am an idiot.
Thanks to your hint I figured out that I had to use TWRP 3.3.1.0 to not get stuck. This worked, but I accidentaly flashed TWRP to boot instead of recovery.
When i tried to flash to recovery i got: "Invalid partition name recovery"
What can I do now?
Click to expand...
Click to collapse
That's not an accident, that's a mistake!
I'm sure there are a number of things you can do. But messing with Boot partition is the best way to brick your phone.
have you tried to use LMSA to start over.
or
Boot TWRP, use one of the backups you made. Restoring boot?
or
ADB flash boot, from firmware sideload folder.
I used LMSA to go back to stock android. Now it boots normal again.
Okay, so how do I get TWRP to work? I am hestitant to try on my own again.
Last time i tried to flash twrp to recovery i got a "invalid partition name recovery" error message.
Dunsinan said:
I used LMSA to go back to stock android. Now it boots normal again.
Okay, so how do I get TWRP to work? I am hestitant to try on my own again.
Last time i tried to flash twrp to recovery i got a "invalid partition name recovery" error message.
Click to expand...
Click to collapse
Do you just try things without any research? have you not considered reading the very short thread associated with TWRP and this device?
That's the correct place to both look for your answers, and ask for clarification.
Related
I followed the video tutorial and when I flash recovery, then proceed to boot into recovery it fails to boot into recovery, it just flashes then boots like normal when I perm root. I don't know what's going on. I tried the clear cache command with no response.
I have searched and didn't find anything.
Anyone able to help please?
It is most likely you did something wrong when you flashed the recovery img, just follow the tuto again and make sure to follow each step.
Here is a guide made by mike: http://forum.xda-developers.com/showthread.php?t=2265618
I have done that. Tried a few times. I am fairly "in the know" with rooting ect, but I just can't figure this out.
Disable fast boot
Sent from my PadFone 2 using Tapatalk 4 Beta
Did you reboot after flashing the recovery or did you just go straight into it? I had the same problem and what fixed it is rebooting after flashing the recovery 'fastboot flash recovery recovery.img'.
samflorin said:
Disable fast boot
Sent from my PadFone 2 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Tried that.
TarekElsakka said:
Did you reboot after flashing the recovery or did you just go straight into it? I had the same problem and what fixed it is rebooting after flashing the recovery 'fastboot flash recovery recovery.img'.
Click to expand...
Click to collapse
Tried that to.
When I press perm root, it just reboots normal like recovery doesn't even exist.
Have you tried flashing stock recovery and trying to boot in it? I know that doesn't fix anything, I am just curious if your device will actually boot into any recovery state at all. I have read on XDA about some devices not being able to boot into recovery for some reason.
Here's the stock recovery, just in case: http://forum.xda-developers.com/showthread.php?p=38504123
Okay give me a shot at that.
I noticed after flashing recovery, mine doesn't tampered like it should?
The stock recovery says it's not available anymore.
If it doesn't say TAMPERED then the recovery must have not been flashed to begin with and that is why it's not booting into it. Which recovery are you trying to install? I use TWRP 2.5.0 and I flashed it with fastboot then restarted and it booted fine. My device is S-ON, by the way, and running Trickdroid 7.5.
US Developer Edition Recovery: http://d-h.st/b5g
T-Mobile Recovery: https://www.dropbox.com/s/hvs38223dfrzsny/recovery_tmobile.img
I am not sure if either one will work with your device since I am guessing it's international? But they might be worth a shot.
Never mind, I found the stock international recovery for you: https://dl.dropboxusercontent.com/u/22045273/htc1-stock-recovery.img it was on page 4 of the thread. Give it a go.
I flashed the stock recovery and it still boots like there is no recovery there. and it doesn't say "tampered"
This is crap
EDIT: Yeah I figured it's not being flashed since it's not tampered, but no matter what I try it won't flash.
I'm navigating to the folder: CD C:\One_All-In-One_Kit_v\Data\Recoveries then typing fastboot flash recovery recovery.img and it doesn't work.
It says it's flashed ect, but doesn't boot into it, nore show tampered.
This is very weird and unfortunately I do not know the solution to that. I do not use the All-In-One-Kit, actually, but just a mini-SDK with fastboot files inside. I use shift + right click and "open command prompt window here" rather than navigate to the location, it's just much easier that way. Can you try flashing the latest TWRP recovery?
aussiesausage said:
I followed the video tutorial and when I flash recovery, then proceed to boot into recovery it fails to boot into recovery, it just flashes then boots like normal when I perm root. I don't know what's going on. I tried the clear cache command with no response.
I have searched and didn't find anything.
Anyone able to help please?
Click to expand...
Click to collapse
Are you under s-off ?
tash2013 said:
Are you under s-off ?
Click to expand...
Click to collapse
Nope S-ON
I just downloaded TWRP and flashed it ( fastboot flash recovery recovery.img ) it said all the jabber, like it worked, rebooted and still no "tampered" just reboots like nothing ever happen.
I give up.
Would ADB be any better?
Ugh man that's horrible. I honestly do feel your frustration because I have faced similar situations with my HTC devices (One X and One) countless times, and it sucks because you know the correct steps yet it's not working. I sure hope someone knowledgeable about this can come in and help you. Best of luck.
EDIT: I have only used ADB to sideload a ROM but I don't know about flashing recoveries. If you know how to do it, then why not? It's worth a shot for sure.
EDIT #2: And if you're not familiar with ADB, this article should get you started: http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/
Make sure you follow all the steps to the word and also install HTC Sync Manager for the proper drivers to be loaded.
I know right, driving me nuts.
I've never done adb to flash a recovery before but don't know if I would want to be the pidgeon to try lol
aussiesausage said:
Nope S-ON
I just downloaded TWRP and flashed it ( fastboot flash recovery recovery.img ) it said all the jabber, like it worked, rebooted and still no "tampered" just reboots like nothing ever happen.
I give up.
Click to expand...
Click to collapse
Try reboot to system (OS), then power off , then go to bootloader -> try enter to recovery again
tash2013 said:
Try reboot to system (OS), then power off , then go to bootloader -> try enter to recovery again
Click to expand...
Click to collapse
Tried that, no go.
Also checked the drivers, re-installed no go.
I am quite up there with adb, but not with flashing recovery with a HTC device lol.
There seems to be another method for flashing recoveries besides fastboot.
http://androidforums.com/cdma-evo-3...lash-recovery-image-via-fastboot-sd-card.html
This is an HTC Evo section but it could work for the One as well, although I am not sure of it. I have done some Googling and I did not come across any articles/threads saying that it is possible to flash a recovery using ADB, so that might not be possible.
Hi Guys,
I stupidly did not realise my device (XT1072) was a different slightly different model to the moto g 2014.
I unlocked the bootloader and installed TWRP, then tried to install Cyanogenmod 12.1, this failed giving an error "Error executing updater binary in zip" Which I guess is due to it being a different model, right? After receiving this error I did some googling and found on a few sites that I should wipe data, system, cache & dalvik cache to resolve this. I did this and tried to flash it again, with the same error. Now my phone is stuck on the "warning bootloader unlocked screen" I can boot into fastboot mode, but is there any official Motorola images for my device anywhere? I have had a look online and cant find anything. :crying:
Any help would be much appreciated.
Thanks
Format system is completely wipe previous android version,
You need a custom ROM (I'm assuming you have custom recovery for your device model)
Or fastboot a original image for you're device
Hi
ohmygoddude said:
Hi Guys,
I stupidly did not realise my device (XT1072) was a different slightly different model to the moto g 2014.
I unlocked the bootloader and installed TWRP, then tried to install Cyanogenmod 12.1, this failed giving an error "Error executing updater binary in zip" Which I guess is due to it being a different model, right? After receiving this error I did some googling and found on a few sites that I should wipe data, system, cache & dalvik cache to resolve this. I did this and tried to flash it again, with the same error. Now my phone is stuck on the "warning bootloader unlocked screen" I can boot into fastboot mode, but is there any official Motorola images for my device anywhere? I have had a look online and cant find anything. :crying:
Any help would be much appreciated.
Thanks
Click to expand...
Click to collapse
Hi,
I am facing exactly the same problem here. Could you please let me know if you find any solution!!! please
Thanks
omarhowlader said:
Hi,
I am facing exactly the same problem here. Could you please let me know if you find any solution!!! please
Thanks
Click to expand...
Click to collapse
You might want to take a look at this thread: http://forum.xda-developers.com/mot...e-restore-moto-e-2015-stock-firmware-t3054303
omarhowlader said:
Hi,
I am facing exactly the same problem here. Could you please let me know if you find any solution!!! please
Thanks
Click to expand...
Click to collapse
Hi,
I too faced this issue. I've seen this error mostly with the Team Win Recoveries(TWRP). Switch to philiz recovery touch.
Still no luck
kishorebvs said:
Hi,
I too faced this issue. I've seen this error mostly with the Team Win Recoveries(TWRP). Switch to philiz recovery touch.
Click to expand...
Click to collapse
Hi,
Thank you for your reply. I also tried with CWM_Touch_Titan_v2 recovery image. But when I tried to flash the stock rom RETGBALL_XT1072_5.0.2_LXB22.46-28_cid7_subsidy-DEFAULT_CFC.xml using mfastboot method, it shows on the phone screen "image too large".
As you have faced the same problem, would you be kind enough to give a step by step instruction to solve the issue. My phone is just stuck to unlocked bootloader warning screen for days.
My phone is Moto g XT1072 4G LTE.
Your help could save my days...
Thanks.
omarhowlader said:
Hi,
Thank you for your reply. I also tried with CWM_Touch_Titan_v2 recovery image. But when I tried to flash the stock rom RETGBALL_XT1072_5.0.2_LXB22.46-28_cid7_subsidy-DEFAULT_CFC.xml using mfastboot method, it shows on the phone screen "image too large".
As you have faced the same problem, would you be kind enough to give a step by step instruction to solve the issue. My phone is just stuck to unlocked bootloader warning screen for days.
My phone is Moto g XT1072 4G LTE.
Your help could save my days...
Thanks.
Click to expand...
Click to collapse
Why are u flashing an xml file? XML files are not rom files
The link provided above by mic_he has step by step instructions to restore phone back to stock
Your phone is not bricked. You deleted your system so there is no os to boot. The link should restore you back to stock
mic_he said:
You might want to take a look at this thread: http://forum.xda-developers.com/mot...e-restore-moto-e-2015-stock-firmware-t3054303
Click to expand...
Click to collapse
Thank you,
I have tried those instruction earlier. when I enter "mfastboot flash bootloader bootloader.img" is says "Bootloader preflash validation failed" and when I enter "mfastboot flash system system.img_sparsechunk.0" onthe phone screen is says "Image too large". After going through all the steps when I reboot, it does not ever get past unlocked bootloader warning screen.
I really do not know which other option to try??
---------- Post added at 07:30 PM ---------- Previous post was at 07:26 PM ----------
Moto G User said:
Why are u flashing an xml file? XML files are not rom files
The link provided above by mic_he has step by step instructions to restore phone back to stock
Your phone is not bricked. You deleted your system so there is no os to boot. The link should restore you back to stock
Click to expand...
Click to collapse
I could not find any zip file of the stock rom. I downloaded the stock rom from that link but I am having error as i posted earlier.
Thanks
ohmygoddude said:
Hi Guys,
I stupidly did not realise my device (XT1072) was a different slightly different model to the moto g 2014.
I unlocked the bootloader and installed TWRP, then tried to install Cyanogenmod 12.1, this failed giving an error "Error executing updater binary in zip" Which I guess is due to it being a different model, right? After receiving this error I did some googling and found on a few sites that I should wipe data, system, cache & dalvik cache to resolve this. I did this and tried to flash it again, with the same error. Now my phone is stuck on the "warning bootloader unlocked screen" I can boot into fastboot mode, but is there any official Motorola images for my device anywhere? I have had a look online and cant find anything. :crying:
Any help would be much appreciated.
Thanks
Click to expand...
Click to collapse
Unmounting system before flashing usually stops that problem. What I like to do is wipe data, system, cache & dalvik then reboot to recovery before flashing the rom.
Sent from my GT-P5210 using Tapatalk
could you solve the problem with the XT1072?
hello sir! could you solve the problem with thw XT1072? Can you give me some instructions? cheers
It works!!!!! I could restore my system back with these steps!
Here´s the info
http://forum.xda-developers.com/mot...e-restore-moto-e-2015-stock-firmware-t3054303
I followed the steps and when I was triyng to Flash each of the partitions in sequence using mfastboot get an error
I get an error with one of the files, (don´t remember now but I think was with the mfastboot flash logo logo.bin line
This give me an error, try to fix it and i couldn´t so I continue with the other files in the order listed and when the process was finished the phone was working again!!!!
Enter twrp recovery
Wipe system data cache dalvik
Put any rom like cm in microsd card or usb
And flash it using twrp
ohmygoddude said:
Hi Guys,
I stupidly did not realise my device (XT1072) was a different slightly different model to the moto g 2014.
I unlocked the bootloader and installed TWRP, then tried to install Cyanogenmod 12.1, this failed giving an error "Error executing updater binary in zip" Which I guess is due to it being a different model, right? After receiving this error I did some googling and found on a few sites that I should wipe data, system, cache & dalvik cache to resolve this. I did this and tried to flash it again, with the same error. Now my phone is stuck on the "warning bootloader unlocked screen" I can boot into fastboot mode, but is there any official Motorola images for my device anywhere? I have had a look online and cant find anything. :crying:
Any help would be much appreciated.
Thanks
Click to expand...
Click to collapse
Hi, I have facing this problem too on my XT1063. My phone do boot to system but all the app are getting FCs, so I decided to flash another ROM like usual and All of this give me that "Error executing updater binary in zip", so I trie to wipe AND format all partition from TWRP and FASTBOOT with no success. Via Fastboot says: "File system type raw not supported." So I cant change to a new ROM, I cannot even flash other recovery....
So if you guys find a solution of this problem very users like me will be very thankful.
Hi all,
This is my first post here. Even though i follow some threads on this forum, I've never posted cause i never needed to. All my questions were generally answered in the threads.
However, I believe I've run into a unique problem.
Yesterday, I started rooting my phone using this tutorial: htconeroot.com/ htc-one-root/ how-to-root-htc-one-windowsmaclinux
And i got pretty far. In half an hour, I had successfully unlocked the bootloader, flashed the recovery program (TWRP) and copied the SuperSU zip file into the storage memory. Now as the tutorial suggested, I opened my phone and in the recovery mode, I flashed the SuperSU file. After i got the message saying 'Operation completed successfully". I wiped the Dalvik and the cache and then rebooted the system.
This where things go wrong. After rebooting, the HTC logo shows up along with the "powered by android" logo. Then the screen goes blank i.e. the screen is black but the backlit is on.
I've been trying to fix this by searching on threads, on YouTube, asking friends but I've gotten nowhere. So PLEASE any help would be appreciated.
hamza.ar said:
Hi all,
This is my first post here. Even though i follow some threads on this forum, I've never posted cause i never needed to. All my questions were generally answered in the threads.
However, I believe I've run into a unique problem.
Yesterday, I started rooting my phone using this tutorial: htconeroot.com/ htc-one-root/ how-to-root-htc-one-windowsmaclinux
And i got pretty far. In half an hour, I had successfully unlocked the bootloader, flashed the recovery program (TWRP) and copied the SuperSU zip file into the storage memory. Now as the tutorial suggested, I opened my phone and in the recovery mode, I flashed the SuperSU file. After i got the message saying 'Operation completed successfully". I wiped the Dalvik and the cache and then rebooted the system.
This where things go wrong. After rebooting, the HTC logo shows up along with the "powered by android" logo. Then the screen goes blank i.e. the screen is black but the backlit is on.
I've been trying to fix this by searching on threads, on YouTube, asking friends but I've gotten nowhere. So PLEASE any help would be appreciated.
Click to expand...
Click to collapse
post a link of the TWRP version you have used and the supersu.zip version.
alray said:
post a link of the TWRP version you have used and the supersu.zip version.
Click to expand...
Click to collapse
twrp: openrecovery-twrp-2.6.3.0-m7
Super SU: UPDATE-SuperSU-v2.46
hamza.ar said:
twrp: openrecovery-twrp-2.6.3.0-m7
Super SU: UPDATE-SuperSU-v2.46
Click to expand...
Click to collapse
TWRP 2.6.3.0 is really outdated. Flash 2.8.6.0 and try again using supersu 2.46
alray said:
TWRP 2.6.3.0 is really outdated. Flash 2.8.6.0 and try again using supersu 2.46
Click to expand...
Click to collapse
WOW i had almost given up and was gonna get a new phone. I just tried this AND IT WORKED!!!
Thanks a lot man. Sorry if this was kind of a noob question anyway
Hey everyone!
I have bricked a smartphone for the first time in my life and I'm kinda nervous. So any help is greatly appreciated!
Here is what I did....
I first unlocked the bootloader according to Sony's instructions. It seems to have worked according to adb's positive response.
I then installed TWRP according to this guide:
android.gs/install-twrp-recovery-on-sony-xperia-z3
After typing "fastboot reboot" my phone got into a boot-loop. It switches on, vibrates twice (briefly), shows the Sony logo and then starts again.
I tried entering TWRP recovery. What happens with that is, the TWRP logo shows up, then it seems to go into a recovery boot loop. So no joy there.
I poot the phone into fastboot mode again and tried "fastboot format cache" and "fastboot format userdata" but adb replied with this error: Formatting is not supported for filesystem with type ' '.
I am pretty worried and right now all I want is for my phone to boot properly again.
The model is D6603. I had the current firmware on it, 5.1.1, 23.4.A.0.546.
Once again, thanks to anyone who tries to help me here, I'm at the end of my rope.
You are posting in the Xperia Z4/Z3+ forum.
There is no official TWRP for your device.
I would first check if there exists a better TWRP here on xda (for example in the forum for your device or search TWRP).
Another approach might be the official Dual Recovery for your D6603:
http://forum.xda-developers.com/showthread.php?t=2261606
If that fails reflash your stock ROM with Androxyde's flashtool and start over with Dual Recovery.
DHGE said:
You are posting in the Xperia Z4/Z3+ forum.
There is no official TWRP for your device.
I would first check if there exists a better TWRP here on xda (for example in the forum for your device or search TWRP).
Another approach might be the official Dual Recovery for your D6603:
http://forum.xda-developers.com/showthread.php?t=2261606
If that fails reflash your stock ROM with Androxyde's flashtool and start over with Dual Recovery.
Click to expand...
Click to collapse
Thanks DHGE!
It was pretty late and I guess I wasn't looking right. Sorry for chosing the wrong forum - I'll know better next time.
Thanks for your suggestion, but I couldn't quite follow the tutorial on installing the Dual Recovery (they wrote something about a file called install.bat, but there were only install.sh in the package I downloaded), so I decided to try downloading th stock firmware and flash it with Flashtool. On the second try it worked and my phone is no longer bricked!
Now I will read up a bit here in these forums - because what I really just wanted, was to root my phone.
Thanks again!
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)