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.
Hey everyone,
so I have an issue, I hate taking care of other peoples devices, but my dad asked me to root his Optimus 4x for him, so I did.. or at least I gave it a try.
I unlocked the bootloader, rooted it and tried to instal a custom recovery, with no success.
the OS the device had is 4.1.2 JB, and I tried to flash the ICS recovery, which caused a permanent bootloop.
luckily (I guess?) I can access the recovery (which is STOCK for some odd reason) but the device never boots back up when I restart it. I tried to wipe everything that the stock recovery allows me to, no success either. I tried to use the LG tool, I put the IMEI and hoped for the best - nope, it didnt help either. it kept on saying the device has disconnected.
SO I figured the way to go would be an adb flash of the right recovery and then flashing a custom ROM, but I cant push the recovery image to the sdcard, it says there's no such directory. this is the command I used:
adb push recovery.img /sdcard/recovery.img
I tried various combinations and at this point I'm kinda lost and confused. Perhaps some more-experienced people could give me a hand? I've spent 6 hours figuring this out
EDIT:
the only way of turning the device off is pulling the battery, I can use adb, and I tried to flash the wrong recovery accidently.
thanks
Pawelss said:
Hey everyone,
so I have an issue, I hate taking care of other peoples devices, but my dad asked me to root his Optimus 4x for him, so I did.. or at least I gave it a try.
I unlocked the bootloader, rooted it and tried to instal a custom recovery, with no success.
the OS the device had is 4.1.2 JB, and I tried to flash the ICS recovery, which caused a permanent bootloop.
luckily (I guess?) I can access the recovery (which is STOCK for some odd reason) but the device never boots back up when I restart it. I tried to wipe everything that the stock recovery allows me to, no success either. I tried to use the LG tool, I put the IMEI and hoped for the best - nope, it didnt help either. it kept on saying the device has disconnected.
SO I figured the way to go would be an adb flash of the right recovery and then flashing a custom ROM, but I cant push the recovery image to the sdcard, it says there's no such directory. this is the command I used:
adb push recovery.img /sdcard/recovery.img
I tried various combinations and at this point I'm kinda lost and confused. Perhaps some more-experienced people could give me a hand? I've spent 6 hours figuring this out
EDIT:
the only way of turning the device off is pulling the battery, I can use adb, and I tried to flash the wrong recovery accidently.
thanks
Click to expand...
Click to collapse
try to flash stock rom using KDZ method (http://forum.xda-developers.com/showthread.php?t=2069723), that lets your device like new, and then try to start again, I recommend you to use lg p880 toolkit look into download section (http://forum.xda-developers.com/showthread.php?t=2230934), and you can download CWM 6.0.4.5 and replace the recovery in files folder of p880 toolkit and get the latest recovery that allows you to instal the most recent ROM
Le'mme guess, you didn't even think about unlocking bootloader, amaright?
Rudjgaard said:
Le'mme guess, you didn't even think about unlocking bootloader, amaright?
Click to expand...
Click to collapse
Pawelss said:
I unlocked the bootloader, rooted it and tried to instal a custom recovery, with no success.
Click to expand...
Click to collapse
I bloody hope he did or do you think he's just lying to us for the fun of it?
donkanmcklaus said:
try to flash stock rom using KDZ method (http://forum.xda-developers.com/showthread.php?t=2069723), that lets your device like new, and then try to start again, I recommend you to use lg p880 toolkit look into download section (http://forum.xda-developers.com/showthread.php?t=2230934), and you can download CWM 6.0.4.5 and replace the recovery in files folder of p880 toolkit and get the latest recovery that allows you to instal the most recent ROM
Click to expand...
Click to collapse
Thanks for your suggestion, I'll try it once I'm home.
Rudjgaard said:
Le'mme guess, you didn't even think about unlocking bootloader, amaright?
Click to expand...
Click to collapse
No. As stated in the first post, I did in fact unlock the bootloader. I also confirmed it in the secret menu and it said "Unlock" which as I presume means the bootloader is unlocked.
SimonTS said:
I bloody hope he did or do you think he's just lying to us for the fun of it?
Click to expand...
Click to collapse
No, there's no reason for me to laugh the secret menu confirmed it too.
Thanks for your replies, I hope it works
I'm sorry i missed the first line, what got me was when you said you flashed recovery but it was still the same
The adb command to flash recovery is
1) adb reboot oem-unlock
2) fastboot flash recovery /path/toyour/recovery.img (not adb because you must use fastboot when in bootloader)
Rudjgaard said:
I'm sorry i missed the first line, what got me was when you said you flashed recovery but it was still the same
The adb command to flash recovery is
1) adb reboot oem-unlock
2) fastboot flash recovery /path/toyour/recovery.img (not adb because you must use fastboot when in bootloader)
Click to expand...
Click to collapse
hey, thanks for your reply.
I assume the /path/toyour/recovery.img is a path on the phone, the thing is I cant copy it to the internal storage with adb for some odd, unknown reason (well the reason is the directory doesnt exist). I'll try to return to stock first, and I'll post the result.
thank you again
EDIT:
SOOO I managed to fix it and get it all to work the device boots up normally again thank you VERY much for all your kind help. I love you guys!!
My apologies if this has already been posted. I've been looking all morning but haven't seen anyone with the same issue.
Unlock bootloader: no problem.
Flash TWRP: I downloaded from http://teamw.in/project/twrp2/275, and I got an error about partition size mismatch, but that's ok, right?
But when I try to enter recovery, all I get is the warning screen that my phone is unlocked. The drivers are certainly installed correctly, and fastboot is working fine. I just can't get into recovery to flash a ROM!
Restoring to 4.4.4 stock worked like a charm.
http://forum.xda-developers.com/mot...dows-tool-moto-g-2014-xt1064-restore-t2957167
I've re-enabled USB debugging. Do I dare try to flash a custom recovery again?
Pandae said:
Do I dare try to flash a custom recovery again?
Click to expand...
Click to collapse
You can use Flashify to make a backup of your current recovery and to flash TWRP.img. should work like a charm.
But Flashify requires root, I see? The reason I'm trying to flash a custom recovery is so I can root in the first place.
Pandae said:
But Flashify requires root, I see? The reason I'm trying to flash a custom recovery is so I can root in the first place.
Click to expand...
Click to collapse
You're right. Latest motorola driver and [TOOL]Minimal ADB and Fastboot will do the trick.
Sorry, I should have clarified that when flashing TWRP, I've already been using fastboot.exe from a command line (and administrator level), with the drivers correctly installed. That's how I was able to unlock in the first place.
I did try it with the version of Fastboot you linked to (what I have works peachy for my Nexus 7), still the same thing. I can't boot into recovery and only get stuck at the Motorola unlocked warning.
Pandae said:
I can't boot into recovery and only get stuck at the Motorola unlocked warning.
Click to expand...
Click to collapse
Oh. Sorry. Can you post the output (terminal & device) of
Code:
fastboot devices
fastboot flash recovery NAME_OF_RECOVERY.img
I'd done "fastboot devices" already to verify, and it returns the serial number, though as I said it's clearly working since I was able to unlock as well as flash recovery. I'm flashing "TWRP2801-titan-motog-2014.img" that I downloaded from the TWRP site, and fastboot gives the standard messages about size and success (and my phone gives the size mismatch error).
It's so strange to me. I've flashed a custom recovery dozens of times on both generations of my Nexus 7s, but I've never seen this.
Pandae said:
It's so strange to me.
Click to expand...
Click to collapse
Yeah......have to meditate about that problem....... is your battery low? Fastboot mode of the device gives me all sorts of problems if it detects low battery
I had been using fastboot at 100% (literally finished a full charge) and 84%, but thanks for the continued attempts at explanation.
Oh, did you check the md5 checksum of your download?
Ah, good thought! I rarely do, but I did just now...and they're the same. It's crazy, isn't it?
Pandae said:
Ah, good thought! I rarely do, but I did just now...and they're the same. It's crazy, isn't it?
Click to expand...
Click to collapse
If you are willing to risk it, try a fresh download and try again. I've flashed TWRP more than 20 times by now and never recieved an error whatsoever. It basically the easiest thing to do.
Incase you are stuck again, don't reflash the entire stock rom. Just flash the recovery.img from the stock rom files.
OR
Try this:
HOW TO ROOT MOTO G 2014 with Temporary Custom Recovery
Cheers
I've flashed a custom recovery many a time and have helped people through it, though on Nexus 7s.
Now shall I compound the mystery? I didn't think yet to use ADB to make my phone reboot to recovery. I had assumed recovery wasn't working. So here we go, after booting into Android:
adb reboot devices: my phone's there.
adb reboot recovery: TWRP's working?! And now root is complete!
It doesn't make sense to me why I can't get into recovery from the bootloader, but I can get into it with the simple ADB command. But I appreciate all the help, thanks!
Pandae said:
It doesn't make sense to me why I can't get into recovery from the bootloader
Click to expand...
Click to collapse
A little workaround:
Install Android Terminal Emulator
Add "Term shortcut" widget.
In "Arguments" enter
Code:
su -c reboot recovery
Hello mates,
I just want to switch back to stock firmware just downloaded the B133 maybe i will upgrade to EMUI.3.0 manually but i have twrp installed how can i flash the stock firmware? which is not in zip file its dload/update.app
can someone please guide me?
.
Thanks and blessing
Farrukh
FarrukhQadri said:
Hello mates,
I just want to switch back to stock firmware just downloaded the B133 maybe i will upgrade to EMUI.3.0 manually but i have twrp installed how can i flash the stock firmware? which is not in zip file its dload/update.app
can someone please guide me?
.
Thanks and blessing
Farrukh
Click to expand...
Click to collapse
Hello,
You must first install stock recovery in order to manually update through Updater > Local update, and yes update.app must be in the dload folder on the SD card. (connect your device to your PC, install adb, reboot it to bootloader using 'adb reboot bootloader', put 'recovery.img' into the same folder as adb, execute 'fastboot flash recovery recovery.img', then do 'fastboot reboot', once your device is fully booted go to the Updater app, and do a local update.)
B609 Stock recovery - Download here
Best regards,
James
Daentrod said:
Hello,
You must first install stock recovery in order to manually update through Updater > Local update, and yes update.app must be in the dload folder on the SD card. (connect your device to your PC, install adb, reboot it to bootloader using 'adb reboot bootloader', put 'recovery.img' into the same folder as adb, execute 'fastboot flash recovery recovery.img', then do 'fastboot reboot', once your device is fully booted go to the Updater app, and do a local update.)
B609 Stock recovery - Download here
Best regards,
James
Click to expand...
Click to collapse
Thanks a lot i will do it tonight
FarrukhQadri said:
Thanks a lot i will do it tonight
Click to expand...
Click to collapse
when i execute the adb reboot boat loader command my device won't gets into boat loader but it reboot i tried rebooting into boat loader by flashify app it shows a screen fastboot rescue mode. (phone is unlocked)
i can flash the recovery.
whats wrong ??
FarrukhQadri said:
when i execute the adb reboot boat loader command my device won't gets into boat loader but it reboot i tried rebooting into boat loader by flashify app it shows a screen fastboot rescue mode. (phone is unlocked)
i can flash the recovery.
whats wrong ??
Click to expand...
Click to collapse
That is exactly what you need - adb reboot bootloader (<- it's one word!) gets the phone into fastboot mode (same as flashify). From here you can flash the recovery. On the PC, run fastboot flash recovery <path-to-stock-recovery>. This will get you the stock recovery on the phone. Now you can use the 3 button method to flash the stock ROM.
g4b3rm4n said:
That is exactly what you need - adb reboot bootloader (<- it's one word!) gets the phone into fastboot mode (same as flashify). From here you can flash the recovery. On the PC, run fastboot flash recovery <path-to-stock-recovery>. This will get you the stock recovery on the phone. Now you can use the 3 button method to flash the stock ROM.
Click to expand...
Click to collapse
Can you please guide me a bit more actually now my device is not booting into recovery neither into system its stuck on logo and not going ahead. so should i follow these steps only flash stock recovery in fastboot then flash stock rom?
my phone is stuck on logo and it remains on the logo screen for a couple of seconds then it reboots itself automatically and keep doing the same..
Thanks
FarrukhQadri said:
Can you please guide me a bit more actually now my device is not booting into recovery neither into system its stuck on logo and not going ahead. so should i follow these steps only flash stock recovery in fastboot then flash stock rom?
my phone is stuck on logo and it remains on the logo screen for a couple of seconds then it reboots itself automatically and keep doing the same..
Thanks
Click to expand...
Click to collapse
You must get it into fastboot mode. If the phone restarts and does not boot into the OS, then it's a huge problem. You may try to restore the phone with HiSuite, but my bet is that you'd better get it to a service - you probably flashed the wrong bootloader.
You might have luck with the recovery though - hold down VOLUME UP and POWER when turning the device on. This might get you ADB, so you might boot into fastboot mode.
g4b3rm4n said:
You must get it into fastboot mode. If the phone restarts and does not boot into the OS, then it's a huge problem. You may try to restore the phone with HiSuite, but my bet is that you'd better get it to a service - you probably flashed the wrong bootloader.
You might have luck with the recovery though - hold down VOLUME UP and POWER when turning the device on. This might get you ADB, so you might boot into fastboot mode.
Click to expand...
Click to collapse
Let me have a try i will get back to you. i had this problem with my previous phone but this time its getting so long i'm worried of it, yes my bad i have flashed a wrong kernel mistakenly it was on the phone so i flashed the wrong file.
FarrukhQadri said:
Let me have a try i will get back to you. i had this problem with my previous phone but this time its getting so long i'm worried of it, yes my bad i have flashed a wrong kernel mistakenly it was on the phone so i flashed the wrong file.
Click to expand...
Click to collapse
You are right i have to get it to service its not working at all cant even find in fastboot neither in recovery .. this goes so expensive
Press power, volume-down and connect device to PC simultaneously. You will get into fastboot mode. Flash boot image and recovery image that was exactly from your firmware version.
Kostyan_nsk said:
Press power, volume-down and connect device to PC simultaneously. You will get into fastboot mode. Flash boot image and recovery image that was exactly from your firmware version.
Click to expand...
Click to collapse
can you please share drivers link? i have booted into fastboot and adb installed already but it cant find my device ..
Resolved
Thank you Everyone for helping and guiding issue is resolved your help is always appreciated...
how?
FarrukhQadri said:
Thank you Everyone for helping and guiding issue is resolved your help is always appreciated...
Click to expand...
Click to collapse
How?
jefpcbr said:
How?
Click to expand...
Click to collapse
THAT HOW , FORGET some crap TWRP ! it is no use with huawei devices !
Simona Simmy said:
THAT HOW , FORGET some crap TWRP ! it is no use with huawei devices !
Click to expand...
Click to collapse
but i think twrp is better than cwn
FarrukhQadri said:
but i think twrp is better than cwn
Click to expand...
Click to collapse
What ? In waht way god..
Same purpose .. no better at all it will destroy your phone soon..
killed my phone
Daentrod said:
Hello,
You must first install stock recovery in order to manually update through Updater > Local update, and yes update.app must be in the dload folder on the SD card. (connect your device to your PC, install adb, reboot it to bootloader using 'adb reboot bootloader', put 'recovery.img' into the same folder as adb, execute 'fastboot flash recovery recovery.img', then do 'fastboot reboot', once your device is fully booted go to the Updater app, and do a local update.)
Best regards,
James
Click to expand...
Click to collapse
Hi.
This killed my mobile.
Now I can't boot in, I i can have is the bootloader screen saying ur phone is locked
Please someone help.
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)