Related
Guys. I'm a rookie at this so please don't get annoyed with me, any assistance would be greatly appreciated......
I've read 9000 pages on google and every youtube video and I can't figure this out. I think I either didn't root or did something wrong.....If I didn't root correctly, then help me.
-I unlocked my Nexus One. The unlocked lock shows on start-up.
-I tried flashing Amon_RA 1.6.2
-In Fastboot....Recover......And I get the Android with the exclaimation point in the white triangle.....
I'm sure you laughing at me or just annoyed. But I want to load Cyanogen 5.0.4 which I have saved on my SD card but every time I try to recover, I get the Android with Exclamation point in triangle screen. I pull the battery and my phone loads up as normal.
Please walk me through this with some help......
flash superboot...
http://android.modaco.com/content/g...erd79-epe54b-superboot-rooting-the-nexus-one/
do you have super user permisions aswell,
u can also use adb
adb reboot recovery
This is my first time.....What does that mean or how do I do it? I'm lost and just fried at trying to figure this out......
Ahh... It was just like yesterday when I was in your shoes... People do tend to get annoyed over "noob" questions!
Read this as it will help with many questions.
http://forum.xda-developers.com/showthread.php?t=619153
When I tried Superboot.....The command prompt just stays at "sending 'boot' (2074kb). How long do I wait?
superboot gives you root,
then flash recovery
then flash cyanogen's rom
look for the thread about "stock to sense for noobs"
then do everything except flash the sense rom, just flash Cyanogen's rom
you've started fastboot on the phone, yeah?
Rename recovery image to recovery.img
Put on C:/
fastboot boot recovery C:/recovery.img
Then in bootloader screen select recovery
In recovery with same recovery.img on root of sdcard
adb shell
mount -a
flash_image recovery sdcard/recovery.img
reboot recovery
That should do it for you.
I was unlocked and rooted and ready to install CM7. I followed all the instructions in the Official Atrix CM7 OP to the T, but when it rebooted, I got stuck on the boot screen with "unlocked" and the red M logo.
I tried to repeat the process several times and ended kind of giving up, factory wiping, and then trying to restore my backup. It appeared to restore successfully, but when I rebooted the phone now wont boot at all. I can't even get it into recovery. No combination or order of button presses or battery pulls / usb plugins will turn it on. I just have a green light like it's charging but nothing is working.
Is it possible to brick your phone even after you have been successfully unlocked and rooted just while you are trying to install CM7?
Please help. I am really desperate here. . .
jimjenkins said:
I was unlocked and rooted and ready to install CM7. I followed all the instructions in the Official Atrix CM7 OP to the T, but when it rebooted, I got stuck on the boot screen with "unlocked" and the red M logo.
I tried to repeat the process several times and ended kind of giving up, factory wiping, and then trying to restore my backup. It appeared to restore successfully, but when I rebooted the phone now wont boot at all. I can't even get it into recovery. No combination or order of button presses or battery pulls / usb plugins will turn it on. I just have a green light like it's charging but nothing is working.
Is it possible to brick your phone even after you have been successfully unlocked and rooted just while you are trying to install CM7?
Please help. I am really desperate here. . .
Click to expand...
Click to collapse
are you using the right recovery? romracer or rom manager!
i am using the tenfar CWM included in the Atrix 4G Automatic Unlock script package. will this not work?
if not, how do I replace it with the right recovery if I cant even get into the phone?
jimjenkins said:
i am using the tenfar CWM included in the Atrix 4G Automatic Unlock script package. will this not work?
if not, how do I replace it with the right recovery if I cant even get into the phone?
Click to expand...
Click to collapse
no, that the old recovery you can use the rom manager if you have , or romracer latest recovery you can find that in the development section, also ther was instruction in the cm7 thread.
you should have left it alone at the M boot screen because it takes about 5-10min to boot after unlock and flash...
everything you do now will have to be through fastboot DO NOT SBF FLASH ANYTHING!!!
Go here to use Fastboot
then download the system.img and boot.img from here
use fastboot to push the boot.img and system.img to your phone
if it gets stuck at the M boot screen let it sit for at least 10min
EDIT: get Romracer recovery from here and push that through to your phone through fastboot
Yeah youre going to have to fastboot wipe recovery then fastboot flash recovery recovery.img
Just download rom racers and rename it..recovery.img
Sent from my GT-I9100 using xda premium
Great. Sorry to be such a noob, but do I decompress the CWM-recovery-atrix5.zip file and push the recovery.img file that's inside it? or push the CWM-recovery-atrix5.zip itself?
Also - every time I am able to get my phone into fastboot mode, it says my battery is too weak to flash anything. I cant seem to get the battery to charge enough to execute any fastboot commands. Any way around this? a powered usb hub?
jimjenkins said:
Great. Sorry to be such a noob, but do I decompress the CWM-recovery-atrix5.zip file and push the recovery.img file that's inside it? or push the CWM-recovery-atrix5.zip itself?
Also - every time I am able to get my phone into fastboot mode, it says my battery is too weak to flash anything. I cant seem to get the battery to charge enough to execute any fastboot commands. Any way around this? a powered usb hub?
Click to expand...
Click to collapse
If you can borrow another Atrix user's battery, or take yours to an AT&T store and see if they can charge it for you.
If you're able to get back into recovery then you can just flash the zip.
If not, you'll need to extract the recovery.img to use it with fastboot, or just download it directly from the OP in romracer's thread. (The left hand link is just the .img, the right hand side is the CWM .zip) Then place it in the same directory as fastboot.
So I can literally flash a different recovery from within another?
jimjenkins said:
So I can literally flash a different recovery from within another?
Click to expand...
Click to collapse
yes but it MUST be working proper first ! its ok to use rom managers cwm but i just prefer the otherone alawys have but n e way there are only 2 that are current (uptodate )
thoughs 2 and with romracers you can. chose
a color that you like not just blue
Sent from my MB860 using xda premium
Its the recovery from tenfar CWM. When I can get it into recovery it seems to be working - with the obvious exception of successfully installing CM7
So I can flash romracer recovery from inside tenfar recovery?
sorry if im being redundant - just dont want to screw it up!
thanks
Just download rom racers cwm. Img, head into fastboot and then fastboot flash recovery recovery-****** (whatever yer recovery image color u chose is)
Sent from my MB860 using Tapatalk
I was able after a full day of leaving the phone plugged in, to charge it up. Then I flashed the rom racer recovery, rebooted into recovery (new version), installed CM7, installed gapps, and voila! A working CM7 Atrix. thank you soo soo much guys.
Can't boot android/recovery
ClearFire said:
you should have left it alone at the M boot screen because it takes about 5-10min to boot after unlock and flash...
everything you do now will have to be through fastboot DO NOT SBF FLASH ANYTHING!!!
Go here to use Fastboot
then download the system.img and boot.img from here
use fastboot to push the boot.img and system.img to your phone
if it gets stuck at the M boot screen let it sit for at least 10min
EDIT: get Romracer recovery from here and push that through to your phone through fastboot
Click to expand...
Click to collapse
Please help!!!
The phone stuck in boot screen and overheat, then restart.
In recovery mode is just black screen.
Phone has Neutrino 2.6GT+ ROM whit Clemsyn's OC kernel 1.6GHz and it has unlocked bootloader.
Can I change the kernel without booting in os or recovery?
This problem show after I was extracting very big zip file and phone overheat.
firecode95 said:
Please help!!!
The phone stuck in boot screen and overheat, then restart.
In recovery mode is just black screen.
Phone has Neutrino 2.6GT+ ROM whit Clemsyn's OC kernel 1.6GHz and it has unlocked bootloader.
Can I change the kernel without booting in os or recovery?
This problem show after I was extracting very big zip file and phone overheat.
Click to expand...
Click to collapse
I am actually having this same problem.
My warranty-replacement (unrelated ear-piece failure) had 2.3.6 pre-installed. Thinking little of it, I unlocked the BL and rooted the phone as usual. After this, I tried to install a couple of the ROM's (Neutrino and Morrisoft) which I was most happy with on my previous Atrix.
After flashing either Neutrino or Morrislee's ROM, the phone hung on the M screen. Waiting approximately 30 minutes with no change, I pulled the battery.
When trying to enter recovery mode, the phone would state, "entering recovery mode..." Then go black.
I ended up using RSDLite and sbf flashing the stock 2.3.6 sbf file back to the phone. Then, I had to re-unlock the bootloader and re-root.
This never happened up to, and including 2.3.4, but did twice last night on these ROM's using 2.3.6, and I've flashed many ROM's and Kernels.
It happened to a lesser extent when trying to flash Clemsyn's stock enhanced kernel to the stock ROM, as I was able to enter recovery mode. Entering recovery mode, it would give errors: mounting cache, mounting system errors, and errors to accessing recovery and recovery log files.
Restore recovery would fail in this state, giving me the above errors as well.
Trying to mount the cache and system in recovery would fail. Trying to format cache and system then mounting these could occur temporarily, but would revert back to unmounted when a restore was attempted.
For these problems I pushed a recovery through fastboot.
Just one word: Fastboot. See if Fastboot works and flash everything from there. Or, as Alterna suggested, flash through RSDLite, but that a little dangerous and can brick your phone if you don't know what you are doing. Hope it helps.
Problem sloved!!!
Alterna said:
My warranty-replacement (unrelated ear-piece failure) had 2.3.6 pre-installed. Thinking little of it, I unlocked the BL and rooted the phone as usual. After this, I tried to install a couple of the ROM's (Neutrino and Morrisoft) which I was most happy with on my previous Atrix.
After flashing either Neutrino or Morrislee's ROM, the phone hung on the M screen. Waiting approximately 30 minutes with no change, I pulled the battery.
When trying to enter recovery mode, the phone would state, "entering recovery mode..." Then go black.
I ended up using RSDLite and sbf flashing the stock 2.3.6 sbf file back to the phone. Then, I had to re-unlock the bootloader and re-root.
This never happened up to, and including 2.3.4, but did twice last night on these ROM's using 2.3.6, and I've flashed many ROM's and Kernels.
It happened to a lesser extent when trying to flash Clemsyn's stock enhanced kernel to the stock ROM, as I was able to enter recovery mode. Entering recovery mode, it would give errors: mounting cache, mounting system errors, and errors to accessing recovery and recovery log files.
Restore recovery would fail in this state, giving me the above errors as well.
Trying to mount the cache and system in recovery would fail. Trying to format cache and system then mounting these could occur temporarily, but would revert back to unmounted when a restore was attempted.
For these problems I pushed a recovery through fastboot.
Click to expand...
Click to collapse
My problem like that and I use automated unlock tool to recover recovery, this recovery show some errors but I successfully flash cwm touch and reinstall Nutrition 2.6GT+
Hello folks,
To start, the tablet is an a500. It's running the ICS bootloader V8 with Thor's 1.7.3 recovery.
On my Nexus S, I was able to mount the device as USB mass storage from the recovery, drop a new rom on it from the computer and flash as usual. I can't do that with the a500 because it gives me the "Unable to write to ums lunfile" error. Thinking back, the recovery has always given me this error, but I've gotten around it by successfully mounting it from the booted tablet instead of from the recovery - I can't do that this time because booting hangs on the Tegra Owners screen and doesn't continue any further.
Things I'm wondering about
-Am I on the right recovery for the V8 bootloader? this indicates that I should switch to this
-Can someone point me to how to properly flash recoveries/roms via adb/fastboot?
-What can I do to be able to mount the a500 through the recovery?
I've tried to do some more research and I think my data might be pooched again. A few posts mentioned that formatting the data enabled them to mount their tablet as a USB device to load roms onto it. When I was still running the HC bootloader, I was able to successfully format the data using the hardware reset (power, volume+, screen lock). I'm trying to do that again, but it just boots straight into the V8 bootloader.
1) rotate lock set to the locked position
2) hold volume+
3) hold power until tablet vibrates, then release power and switch the rotate lock to the unlocked position
... but instead of giving the Formatting Data text, it boots straight into the bootloader menu. BLAST!
Wermut said:
Hello folks,
To start, the tablet is an a500. It's running the ICS bootloader V8 with Thor's 1.7.3 recovery.
On my Nexus S, I was able to mount the device as USB mass storage from the recovery, drop a new rom on it from the computer and flash as usual. I can't do that with the a500 because it gives me the "Unable to write to ums lunfile" error. Thinking back, the recovery has always given me this error, but I've gotten around it by successfully mounting it from the booted tablet instead of from the recovery - I can't do that this time because booting hangs on the Tegra Owners screen and doesn't continue any further.
Things I'm wondering about
-Am I on the right recovery for the V8 bootloader? this indicates that I should switch to this
-Can someone point me to how to properly flash recoveries/roms via adb/fastboot?
-What can I do to be able to mount the a500 through the recovery?
I've tried to do some more research and I think my data might be pooched again. A few posts mentioned that formatting the data enabled them to mount their tablet as a USB device to load roms onto it. When I was still running the HC bootloader, I was able to successfully format the data using the hardware reset (power, volume+, screen lock). I'm trying to do that again, but it just boots straight into the V8 bootloader.
1) rotate lock set to the locked position
2) hold volume+
3) hold power until tablet vibrates, then release power and switch the rotate lock to the unlocked position
... but instead of giving the Formatting Data text, it boots straight into the bootloader menu. BLAST!
Click to expand...
Click to collapse
Hard reset will not work this way on v8, u need to use fastboot...
Boot to fastboot pwr/vol UP
Connect to pc via micro USB cable
Open cmd prompt type:
fastboot devices
U should see a ?
Type:
fastboot erase userdata
fastboot erase cache
fastboot reboot
It might pay to reflash your recovery while you're there
Grab your chosen recovery
(I used cwm1.7.3 that came in civatos nvflash v8 pckge and renamed it recovery.img)
and copy it to the fastboot folder
Fastboot erase recovery
Fastboot flash recovery recovery.img
Fastboot reboot
Yes, v8/cwm 1.7.3 should work fine, not sure why u have errors mounting....someone else maybe able to help with that...
good luck
dibb
Sent from my A500 using Tapatalk 2
This is a super helpful post. Many thanks!
I'll try this in the next couple of days and report back.
Hello Dibb, thanks again for trying to help.
Using fastboot, I successfully:
-erased user data
-erased cache
-erased recovery
-reflashed the 1.7.3 recovery.
I didn't have any luck mounting the tablet in windows, so I tried the above steps again, but this time flashing the TWRP 2.1.3.
The recovery booted OK, so I know I did that correctly, but still no luck mounting.
Next, I tried redoing the bootloader/recovery using Blackthund3r's A500 APX Flashing utility back to the Bundle 17 (A500 and A501 BL v8 / Thor Recovery 1.7.3, ICS Unlocked / Skrilax Bootloader v8 and Thor Recovery 1.7.3 for the A500 and A501) to maybe get a fresh start. I rebooted into the recovery, but still no luck mounting the tablet.
I think I need to try pushing a rom straight onto the tablet using either fastboot or adb, but I'm not sure how to do it. I did some research and came up with the following cmd code:
fastboot flash boot boot.img
All of the roms that I've ever downloaded come in zips that you flash straight from the recovery, they're not .img files. Is there a way to push zips onto the SD card using adb/fastboot? I see a boot.img inside these zips, but I feel that if I flash that after extracting it from the rom zip, I'm not going to be getting any gapps or any of the other potentially important stuff in that zip. Do you mind explaining that, and maybe including some more awesome instructions on how to push a rom onto the tablet from windows, without having to mount the SD?
Thanks in advance!
K, lets back up a bit.....a quick question first
Are u just wanting to flash a custom rom via recovery?
As long as you have the unlocked bootloader (which you do) just flash via "install from zip" option from either
internal or external storage.....or am I missing something?
Sent from my A500 using Tapatalk 2
Yep, that`s exactly what I want to do.
My problem is that there's nothing on the internal disk (I have no SD card for the a500) and I can't put anything on the SD card because it won't mount to show up in windows for me to drag a zip onto it.
Roger that then
And no card reader either I take it?
Edit: what rom are u running right now
That's right, no card reader either. I do have a USB key, maybe I can put a new rom on that and mount the usb key in recovery?
I'm not sure what rom I'm on right now, it's been so long since the tablet successfully booted into a rom. The last one I think was Thor's JB v17 from tegraowners.
Yeh try the USB key first....
I didn't realise you couldn't boot your OS, thought you meant the recovery screen, no matter...
do you have your cpuid backed up somewhere....anywhere....pleeeaasssee say you do!!!
I'm just writing up a post now in case the USB key won't work...
Yep, I've got the CPUID, drivers, sdk, adb and fastboot work too.
I'm going to try the USB key method.
Wermut said:
Yep, I've got the CPUID, drivers, sdk, adb and fastboot work too.
I'm going to try the USB key method.
Click to expand...
Click to collapse
Awsum that's great:highfive::good:
adb push name-of-your-rom.zip /sdcard
I'm sure you will still need to mount it tho but this is not my speciality.....
If the key won't mount I'd strongly suggest you download timmydeans v4 - it does not require an sdcard. http://www.mediafire.com/download.php?fo4wqjeald4s3rj
This will downgrade you back to stock HC3.2.1 which is pre-rooted and comes with cwm....this will wipe everything and reset yr tab, that will deal with yr boot issue - and hopefully the mount issues too....
Holy**** the USB key worked, just installed CM10-FLEX_V6Supercharged_Rev2.3c.
Lets hope I don't have any SOD issues, which is what led me to upgrading my bootloader, which is what started all of this!
I searched the rom that you have in your sig, (I suppose you think it's pretty stable?), but I didn't manage to find it. Throw a link? Does it come with a kernel?
Thanks so much!!
Phew!!
Ive been using the v6 supercharge cm10 JB rom for a week or so and its fantastic http://forum.xda-developers.com/showthread.php?t=1935582
The one in my sig is ics but u know us tinkerers we have to have the latest and greatest.lol...
I never go too far from civato's roms - I'm a big fan! So can't offer feedback for anything else....
You should have no probs with SOD...mainly an issue with hc bootloader/ics rom and not wiping....thing of the past these days!
Well I'm pleased you got sorted without too many probs - happy tabbing
rgds dibb
Sent from my A500 using Tapatalk 2
I rooted through cyanogenmod method, then unrooted (went back to stock 2.2.1) with the stock P15100.zip. I had another hardware issue with my phone (microphone failing) and thought it could be software. The mic was still broken and I wanted to root again so went through cyanogen method again flashing CWM. I was able to reboot once into recovery to flash synth's ICS. When I try to fully reboot, then reboot into recovery again, I got bootloop for a minute, then eventually booted into the rom. I tried flashing 4ext and same issue. I tried flashing CWM again from app and still have the issue. I'm just guessing recovery is corrupted and it needs to be formatted and re-flashed? Anyone know how to format recovery via adb and then push cwm or 4ext?
Any help much is appreciated.
You can flash a recovery through terminal emulator. As I recall, the commands are:
su
flash_image recovery recoveryname.img
Sounds like you might be having bigger issues, though. I hope your recovery partition isn't going kaput.
Jack_R1 might have an idea.
Man, Jack_R1 is still around these parts? But as for OP, definitely sounds like your recovery is corrupt. What you want to do is if you have any fastboot/ADB knowledge is you're going to want to download the recovery.img of your choice, name it "recovery.img" then place it in your ADB folder, plug your phone in in Fastboot mode and then type in the following commands:
Code:
Fastboot devices
it should show you a number followed by "fastboot" after this type
Code:
fastboot delete recovery
it should spew out how long it took followed by "recovery deleted" or something like that.
lastly you're going to flash the recovery that you downloaded. Type
Code:
fastboot flash recovery recovery.img
That should do it! PM me if you need any other help
Yes, I still visit here
OP, what phone do you have? You're writing a wrong name for PD15IMG.
In any case, if you indeed have PD15IMG - find "root for S-OFF users" thread in Development, get the PD15IMG with CWM from there, flash it just like you flashed return-to-stock package, and boot into recovery. If it doesn't work - it means that it's not the recovery that's corrupted.
And I suspect that you're just not understanding correctly what your phone does, and/or not actually booting into recovery.
Nicgraner said:
Man, Jack_R1 is still around these parts? But as for OP, definitely sounds like your recovery is corrupt. What you want to do is if you have any fastboot/ADB knowledge is you're going to want to download the recovery.img of your choice, name it "recovery.img" then place it in your ADB folder, plug your phone in in Fastboot mode and then type in the following commands:
Code:
Fastboot devices
it should show you a number followed by "fastboot" after this type
Code:
fastboot delete recovery
it should spew out how long it took followed by "recovery deleted" or something like that.
lastly you're going to flash the recovery that you downloaded. Type
Code:
fastboot flash recovery recovery.img
That should do it! PM me if you need any other help
Click to expand...
Click to collapse
I have used adb a bit (for root with cyanogen method). I'm guessing that the delete command will reformat the recovery partition? I'll give this a go when I get home and get back to ya. Thanks for the reply! Is there a way to download the 4ext recovery img file?
Edit:
I downloaded the CWM touch img and connected to the phone in fastboot. Was able to follow your instructions, but the command is erase not delete. When I put in the delete command it came up with the instructions and was able to figure it out. Flashed recovery and I can now boot into recovery every time from fastboot, terminal, adb, and from power prompt in rom! BOOYAH! Thanks a ton!
Jack_R1 said:
Yes, I still visit here
OP, what phone do you have? You're writing a wrong name for PD15IMG.
In any case, if you indeed have PD15IMG - find "root for S-OFF users" thread in Development, get the PD15IMG with CWM from there, flash it just like you flashed return-to-stock package, and boot into recovery. If it doesn't work - it means that it's not the recovery that's corrupted.
And I suspect that you're just not understanding correctly what your phone does, and/or not actually booting into recovery.
Click to expand...
Click to collapse
Hey Jack,
I have HTC Glacier. Was a typo for the PD15IMG name. I think I have a decent understanding of the phone, and most likely have a corrupted recovery partition. Seems that instead of just flashing a recovery over a recovery, I may need to reformat the partition and then flash? I'll try flashing the file you suggest and report back. If it is not the recovery that is corrupted, what else could be the issue? Possibly an issue with the bootloader not allowing the phone to boot into recovery? Thanks for the reply.
Flashing recovery isn't copying a file. When you flash IMG through bootloader, it is flashed just like what it is - a complete image. Formatting the partition doesn't do anything, since it has no "format" - the image flashed by the bootloader contains both the structure and the data, just like a CD/DVD image does, for example.
The possible options I can think of are:
1) Your recovery partition is physically bad - unlikely.
2) Your bootloader is corrupted - could possibly lead to you being unable to enter recovery.
3) Something that prevents your phone from entering recovery - i.e. a stuck button or something - or you're doing it wrong. I'm afraid that what you're describing as "phone bootloops for a minute and then boots a ROM" isn't really a bootloop - because these phones can't get out of bootloop on their own, if booting failed once - it'll fail always. Logcat can confirm this. I believe it's just the ROM that's booting normally when you try to enter recovery, so, in this case, since you didn't specify how exactly you're trying to enter recovery - it seems like you're either doing it wrong, or when you try to enter recovery you're not getting there.
To help people help you, please write down the exact way you're using when trying to enter recovery, and if you know more than one way - try them all (from bootloader, by adb reboot recovery, directly booting without flashing by "fastboot boot", etc). And post your HBOOT version.
Jack_R1 said:
Flashing recovery isn't copying a file. When you flash IMG through bootloader, it is flashed just like what it is - a complete image. Formatting the partition doesn't do anything, since it has no "format" - the image flashed by the bootloader contains both the structure and the data, just like a CD/DVD image does, for example.
The possible options I can think of are:
1) Your recovery partition is physically bad - unlikely.
2) Your bootloader is corrupted - could possibly lead to you being unable to enter recovery.
3) Something that prevents your phone from entering recovery - i.e. a stuck button or something - or you're doing it wrong. I'm afraid that what you're describing as "phone bootloops for a minute and then boots a ROM" isn't really a bootloop - because these phones can't get out of bootloop on their own, if booting failed once - it'll fail always. Logcat can confirm this. I believe it's just the ROM that's booting normally when you try to enter recovery, so, in this case, since you didn't specify how exactly you're trying to enter recovery - it seems like you're either doing it wrong, or when you try to enter recovery you're not getting there.
To help people help you, please write down the exact way you're using when trying to enter recovery, and if you know more than one way - try them all (from bootloader, by adb reboot recovery, directly booting without flashing by "fastboot boot", etc). And post your HBOOT version.
Click to expand...
Click to collapse
Sorry if I wasn't more descriptive. I really appreciate your help and everything you have done for this community. Seems the recovery was corrupted by the 4ext app. I was able to extract the recovery.img from the 4ext download and was able to flash it via fastboot. Everything boots properly now. HBoot is 0.85.2007 FYI. Thanks again!
---EDIT, FIXED IT ALREADY, MORE INFO BELOW---
Dear members,
A little background; The installation of the latest Oxygen os (zip on storage - > twrp flash) failed.
I thought it was a good idea to wipe everything and reboot to start fresh.
Upon reboot I was unable to enter TWRP, only fastboot was possible.
When I flash twrp (by neither clockworkx or the bluex) the flash is successful but I cant boot into the recovery, also not by directly using fastboot boot recovery.img. When booting into recovery I get a black screen with only a white led.
So I decided to give the stock recovery a try and that one does boot up however I cant flash anything. When I use adb sideload it loads the file fine but then it errors with no error message.
I am getting suspicious that my internal memory is now corrupt so I am willing to give this msmtool a try which I have never touched so I would really appreciate some guidance. Anyone with any ideas? Thanks a lot in advance.
Other things I have tried:
I tried to flash the stock boot.img from the oxygen os using fastboot but it doesnt seem to be the problem.
---FIXED:---
Thanks to the wonderful documentation found at : /oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706
I was able to fix it. If you are in the same pickle head over to his thread and thank him.