Related
I'm trying to flash stock firmware to my Atrix HD but for some odd reason it doesn't let me.
I'm using MythTools.
I tried using RSDLite but no luck.
been trying to figure it out for 3 hours...
bylithium said:
I'm trying to flash stock firmware to my Atrix HD but for some odd reason it doesn't let me.
I'm using MythTools.
I tried using RSDLite but no luck.
been trying to figure it out for 3 hours...
Click to expand...
Click to collapse
did u create a nandroid backup of stock rom ?
Are you running a stock recovery? Unlocked bootloader? What ROM were you running before? I'm not sure if the answer to these 3 items could cause a problem but more information is usually better than less.
What errors are you getting when try to flash?
audit13 said:
Are you running a stock recovery? Unlocked bootloader? What ROM were you running before? I'm not sure if the answer to these 3 items could cause a problem but more information is usually better than less.
What errors are you getting when try to flash?
Click to expand...
Click to collapse
Custom recovery, Unlocked bootloader, beanstal/kitstalk.
for some odd reason when I was flashing through myth tools it asked which boot logo to use and selected the bootlogo after i selected, nothing else happened.
bylithium said:
Custom recovery, Unlocked bootloader, beanstal/kitstalk.
for some odd reason when I was flashing through myth tools it asked which boot logo to use and selected the bootlogo after i selected, nothing else happened.
Click to expand...
Click to collapse
I had a very similar situation. Are you running Myth Tools as an Administrator? Is your phone detected in fastboot?
audit13 said:
I had a very similar situation. Are you running Myth Tools as an Administrator? Is your phone detected in fastboot?
Click to expand...
Click to collapse
I don't think I was running as Administrator...
I'm not sure about that...but i'll check when my phone reaches 50%, it's at 20%.
Myth Tools will run and unzip the stock firmware even if there is no phone detected. Just before you choose the boot logo, run a separate command prompt window to determine whether your phone is detected in fastboot mode by typing "fastboot devices" from the adb directory.
audit13 said:
Myth Tools will run and unzip the stock firmware even if there is no phone detected. Just before you choose the boot logo, run a separate command prompt window to determine whether your phone is detected in fastboot mode by typing "fastboot devices" from the adb directory.
Click to expand...
Click to collapse
Ok so my phone was detected before selecting the boot logo and also ran myth tools as administrator.
bylithium said:
Ok so my phone was detected before selecting the boot logo and also ran myth tools as administrator.
Click to expand...
Click to collapse
Does the flashing proceed? Mine starts with 10/100, 20/100, etc.
audit13 said:
Myth Tools will run and unzip the stock firmware even if there is no phone detected. Just before you choose the boot logo, run a separate command prompt window to determine whether your phone is detected in fastboot mode by typing "fastboot devices" from the adb directory.
Click to expand...
Click to collapse
looks it still didn't work. after flashing i rebooted my phonoe, and the bootlogo was beanstalk/kitstalk.
audit13 said:
Does the flashing proceed? Mine starts with 10/100, 20/100, etc.
Click to expand...
Click to collapse
yes...boot logo is still the same as the custom rom i'm running.
bylithium said:
looks it still didn't work. after flashing i rebooted my phonoe, and the bootlogo was beanstalk/kitstalk.
Click to expand...
Click to collapse
Does the phone boot at all? Do you have a nandroid backup of a stock OS? Did you try flashing a retail mexico or retail bell?
audit13 said:
Does the phone boot at all? Do you have a nandroid backup of a stock OS? Did you try flashing a retail mexico or retail bell?
Click to expand...
Click to collapse
Does not boot at all, I believe I do but it's on my sd card, sadly, it's at my moms house in which is an hour away from town. Nope, just tried flashing att.
It seems that your phone is not actually being flashed even though the flash process appears complete.
After flashing with Myth, immediately boot the phone into recovery and wipe cache, data, and Dalvik. After wiping, try booting the phone into the OS.
audit13 said:
It seems that your phone is not actually being flashed even though the flash process appears complete.
After flashing with Myth, immediately boot the phone into recovery and wipe cache, data, and Dalvik. After wiping, try booting the phone into the OS.
Click to expand...
Click to collapse
still no luck.
audit13 said:
It seems that your phone is not actually being flashed even though the flash process appears complete.
After flashing with Myth, immediately boot the phone into recovery and wipe cache, data, and Dalvik. After wiping, try booting the phone into the OS.
Click to expand...
Click to collapse
should i try flashing ics? or would the problem still persist?
At this point, all I can suggest is re-downloading the stock ATT ROM or try the Mexico Retail. Your phone is not of much use since it doesn't have a working ROM. I've never tried an ICS ROM on an AHD because my phone came with 4.1.2.
audit13 said:
At this point, all I can suggest is re-downloading the stock ATT ROM or try the Mexico Retail. Your phone is not of much use since it doesn't have a working ROM. I've never tried an ICS ROM on an AHD because my phone came with 4.1.2.
Click to expand...
Click to collapse
I still haven't fixed my problem just yet. I forgot that I did a nandroid backup on my brothers phone (atrix hd) may i possibly use his backup and restore it on mine?
bylithium said:
I still haven't fixed my problem just yet. I forgot that I did a nandroid backup on my brothers phone (atrix hd) may i possibly use his backup and restore it on mine?
Click to expand...
Click to collapse
Yes, you can try it. You may get an md5 error which can be fixed.
audit13 said:
Yes, you can try it. You may get an md5 error which can be fixed.
Click to expand...
Click to collapse
Didn't get an md5 error but philz is telling me "Can't mount /data".
Since pepole have no knolege of what they are doing and kind of blame me for it i will not provide the images anymore.
Please lock this thread.
Thank you so much!
Question: Do we have to flash the stock recovery after flashing the rooted system image? I prefer to have TWRP recovery anyways.
akarol said:
Thank you so much!
Question: Do we have to flash the stock recovery after flashing the rooted system image? I prefer to have TWRP recovery anyways.
Click to expand...
Click to collapse
worst case just reflash TWRP =]
akarol said:
Thank you so much!
Question: Do we have to flash the stock recovery after flashing the rooted system image? I prefer to have TWRP recovery anyways.
Click to expand...
Click to collapse
You can use whatever recovery you would like, the system image does not affect the recovery in any way.
Thanks - flashed your bootloader files which got me out of a never ending boot animation issue
j32olger said:
Thanks - flashed your bootloader files which got me out of a never ending boot animation issue
Click to expand...
Click to collapse
The bootloop have nothing to do with my bootloader files, they are completley stock from the ota file!
If you installing the new bootloader files on older roms you are asking for troubles.
Boot the watch in bootloader mode and flash the files as described and you watch will work.
Af if it bootlooping run a "Fastboot -w" after flashing.
Greetings, Is the newly released OTA compatible with your rom?
drmcatchr said:
Greetings, Is the newly released OTA compatible with your rom?
Click to expand...
Click to collapse
No ota files will only work with stock untouched rom.
bunny0007 said:
No ota files will only work with stock untouched rom.
Click to expand...
Click to collapse
Are you planning on releasing a pre-rootet image of the latest ota?
Would be greatly appreciated!
2k4ever said:
Are you planning on releasing a pre-rootet image of the latest ota?
Would be greatly appreciated!
Click to expand...
Click to collapse
Have added it today.
I tried this using the update (LCA44B) and now the watch doesn't even turn on. No LG logo or anything.
GuiyeC said:
I tried this using the update (LCA44B) and now the watch doesn't even turn on. No LG logo or anything.
Click to expand...
Click to collapse
And you did follow the instuctions?7
Flash bootloader stuff
Flash system image
Flash boot image
Have testet it serval times without errors.
bunny0007 said:
And you did follow the instuctions?7
Flash bootloader stuff
Flash system image
Flash boot image
Have testet it serval times without errors.
Click to expand...
Click to collapse
Yep, just like in the steps, the thing did show a FAILED (anti-rollback) when flashing the 'aboot'. I just used everything that was on the zip, now the watch doesn't even show the LG logo, I've tried plugging it on and off and keeping the reset button pressed for a while. I really don't know what else to try.
I'm waiting for it to run out of battery, but I don't even know if it's "on".
GuiyeC said:
Yep, just like in the steps, the thing did show a FAILED (anti-rollback) when flashing the 'aboot'. I just used everything that was on the zip, now the watch doesn't even show the LG logo, I've tried plugging it on and off and keeping the reset button pressed for a while. I really don't know what else to try.
I'm waiting for it to run out of battery, but I don't even know if it's "on".
Click to expand...
Click to collapse
Did just ran it on my own watch and everything working.
If you aboot fails flashing your watch might have another problem, i assume that your watch have an unlocked bootloader??
bunny0007 said:
Did just ran it on my own watch and everything working.
If you aboot fails flashing your watch might have another problem, i assume that your watch have an unlocked bootloader??
Click to expand...
Click to collapse
Yes, it had the boot loader unlocked, and I can't try again flashing the aboot because I can't get it to recovery mode or fast boot mode or anything.
Who can I get the images from?
bunny0007 said:
Since pepole have no knolege of what they are doing and kind of blame me for it i will not provide the images anymore.
Please lock this thread.
Click to expand...
Click to collapse
By people, do you mean 1 person ???
Pretty unfair for other, isn't it ?
I am looking for bootloader files for the G Watch R to flash over what I believe to be a corrupt bootloader on my device. It will only boot when on the charging stand, and so far I have only been able to get it to boot to 5.0.1 successfully. Once the device tries to pull down the OTA update it reboots and proceeds to run the update and then it fails and powers off.
Currently I can access fastboot and I can get it to boot a stock recovery and twrp with the 5.0.1 boot.img flashed to my device.
Can anyone who has downloaded the original package from this thread PM me the files? I need to reflash my bootloader files to attempt to fix a booting issue with my watch. Any help would be appreciated and I will not hold anyone accountable if I hard brick my device.
fnj00 said:
Can anyone who has downloaded the original package from this thread PM me the files? I need to reflash my bootloader files to attempt to fix a booting issue with my watch. Any help would be appreciated and I will not hold anyone accountable if I hard brick my device.
Click to expand...
Click to collapse
Hi there ,
Why don't you try this one ??
http://forum.xda-developers.com/g-w...edroid-r-urbane-port-v1-0-0-june-6th-t3128850
Hi to everyone,
I have a huge problem, my only phone, is kinda messed up.
I have a Moto G (2nd gen) 4G XT1072, and i wiped everything after rooting and installing the recovery.
Here's comes the problem, when I try to flash ANY firmware, it fails.
When I try to install cyano it pops out that I have a titan not a thea, that is wrong, because xt1072 is thea
When I try to restore original firmware with msfastboot the phone says something about the image, something link the image is too big
I don't know what to do now guys, i feel so lost :/
Help me please
Edit: I've tried even this with minimal adb and fastboot:
http://forum.xda-developers.com/mot...dows-tool-moto-g-2015-xt1072-restore-t3124915
still getting image is too large as output as soon it start to flash system.img_sparsechunk.0
Re edit: Solved
I've installed the wrong type or recovery
Extract a boot.img from a rom and do fastboot flash boot boot.img
RolanDroid said:
Extract a boot.img from a rom and do fastboot flash boot boot.img
Click to expand...
Click to collapse
Done, the command works, but if I reboot in normal mode, it doesn't work
I used cyano 13.0
Kere03 said:
Done, the command works, but if I reboot in normal mode, it doesn't work
I used cyano 13.0
Click to expand...
Click to collapse
Flash thea twrp from bootloader mode
Fastboot flash recovery recoveryname.img
RolanDroid said:
Flash thea twrp from bootloader mode
Fastboot flash recovery recoveryname.img
Click to expand...
Click to collapse
Ok, done, then?
Kere03 said:
Ok, done, then?
Click to expand...
Click to collapse
Reboot your device?
RolanDroid said:
Reboot your device?
Click to expand...
Click to collapse
There's no OS, so the phone is still on "warning bootloader unlocked"
Kere03 said:
There's no OS, so the phone is still on "warning bootloader unlocked"
Click to expand...
Click to collapse
Reboot into recovery,full wipe everything and flash a rom
Kere03 said:
Hi to everyone,
I have a huge problem, my only phone, is kinda messed up.
I have a Moto G (2nd gen) 4G XT1072, and i wiped everything after rooting and installing the recovery.
Here's comes the problem, when I try to flash ANY firmware, it fails.
When I try to install cyano it pops out that I have a titan not a thea, that is wrong, because xt1072 is thea
When I try to restore original firmware with msfastboot the phone says something about the image, something link the image is too big
I don't know what to do now guys, i feel so lost :/
Help me please
Edit: I've tried even this with minimal adb and fastboot:
http://forum.xda-developers.com/mot...dows-tool-moto-g-2015-xt1072-restore-t3124915
still getting image is too large as output as soon it start to flash system.img_sparsechunk.0
Click to expand...
Click to collapse
It's because you flashed titan TWRP. Use this: http://forum.xda-developers.com/mot...recovery-twrp-2-8-6-0-touch-recovery-t3088800
RolanDroid said:
Reboot into recovery,full wipe everything and flash a rom
Click to expand...
Click to collapse
Booteng into TWRP recovery, wiped everything except sd card, tried to install the rom that you have in the signature and the phone says that:
"This package is for device: thea, thea_umtsds, thea_ds,XT1072, XT1078,XT1079; this device is titan.
E: Error executing updater binary in zip....
Error flashing sdcard/romname
Kere03 said:
Booteng into TWRP recovery, wiped everything except sd card, tried to install the rom that you have in the signature and the phone says that:
"This package is for device: thea, thea_umtsds, thea_ds,XT1072, XT1078,XT1079; this device is titan.
E: Error executing updater binary in zip....
Error flashing sdcard/romname
Click to expand...
Click to collapse
Wtf? You have flashed TWRP for thea?
LuK1337 said:
It's because you flashed titan TWRP. Use this: http://forum.xda-developers.com/mot...recovery-twrp-2-8-6-0-touch-recovery-t3088800
Click to expand...
Click to collapse
RolanDroid said:
Wtf? You have flashed TWRP for thea?
Click to expand...
Click to collapse
Yep, i was using the wrong one, **** me, i'm so dumb, thanks guys..
Kere03 said:
Yep, i was using the wrong one, **** me, i'm so dumb, thanks guys..
Click to expand...
Click to collapse
so it's booted now? Great
RolanDroid said:
so it's booted now? Great
Click to expand...
Click to collapse
Yes, it's booting and starting the apps, thanks again bro
Kere03 said:
Yes, it's booting and starting the apps, thanks again bro
Click to expand...
Click to collapse
Np
Hello all, I just purchased a Moto X 2014 off craigslist, I'm not 100% sure which it is, how would I find out if its x1095 or x10xx etc ?
Andromendous said:
Hello all, I just purchased a Moto X 2014 off craigslist, I'm not 100% sure which it is, how would I find out if its x1095 or x10xx etc ?
Click to expand...
Click to collapse
Put it into bootloader mode:
fastboot getvar all
Copy and save all the info into a Notepad file for future reference.
gus ghanem said:
put it into bootloader mode:
Fastboot getvar all
copy and save all the info into a notepad file for future reference.
Click to expand...
Click to collapse
thank you very much! Looks like its xt1095!
Gus Ghanem said:
Put it into bootloader mode:
fastboot getvar all
Copy and save all the info into a Notepad file for future reference.
Click to expand...
Click to collapse
hmm.... just tried flashing twrp, and it says "mismatched recovery size", i tryed booting into recovery and the screen just goes blank and stays that way. I press power and it just reboots into the OS
Andromendous said:
hmm.... just tried flashing twrp, and it says "mismatched recovery size", i tryed booting into recovery and the screen just goes blank and stays that way. I press power and it just reboots into the OS
Click to expand...
Click to collapse
You checked that the bootloader is unlocked? Yes, you will get the mismatch error because you're flashing a non-stock file, it's normal, and it's ok, TWRP will still flash and boot, but you have to boot into recovery straight after you flash it. Use the latest TWRP 3.1.1
https://twrp.me/motorola/motorolamotox2014.html
If the bootloader is already unlocked, update the phone first, so that you have the latest bootloader version.
fastboot flash recovery twrp-3.1.1-0-victara.img
Gus Ghanem said:
You checked that the bootloader is unlocked? Yes, you will get the mismatch error because you're flashing a non-stock file, it's normal, and it's ok, TWRP will still flash and boot, but you have to boot into recovery straight after you flash it. Use the latest TWRP 3.1.1
https://twrp.me/motorola/motorolamotox2014.html
If the bootloader is already unlocked, update the phone first, so that you have the latest bootloader version.
fastboot flash recovery twrp-3.1.1-0-victara.img
Click to expand...
Click to collapse
ok thanks for the help. I figured it out. I dont know if this phone is just weird, or if I was entering fastboot mode wrong, but I've flashed a few roms now, one being pure nexus, for some reason I cant get magisk to work right, (I really just need netflix) I flashed rom,gapps, magisk and when it boots up there is no app for it, I tried flashing magisk again and the app gets install but netflix wont show up in the app store?
Andromendous said:
ok thanks for the help. I figured it out. I dont know if this phone is just weird, or if I was entering fastboot mode wrong, but I've flashed a few roms now, one being pure nexus, for some reason I cant get magisk to work right, (I really just need netflix) I flashed rom,gapps, magisk and when it boots up there is no app for it, I tried flashing magisk again and the app gets install but netflix wont show up in the app store?
Click to expand...
Click to collapse
I don't use either Magisk or Netflix, so I'm not familiar with them, but you can try the Netflix APK:
https://www.apkmirror.com/apk/netflix-inc/
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)