Related
Hello all!
First off I would just like to say thank you, thank you, thank you. I have been a long time lurker on these forums (since the evo) and have gotten a lot of useful information from here. Now to my issue. I have had no phone for two weeks now, and have been doing search after search. I upgraded my phone to 4.3 (it was mk2) and rooted it via motochopper. So my dumbass tried to flash a custom rom with kn0x0ut and it failed. The phone rebooted and now will boot up to the samsung custom screen. You can hear the att boot up sound but no image. I can get into odin mode and stock recovery. When I am in odin it says:
ODIN MODE
PRODUCT NAME: SGH-I337
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMC BURST MODE enabled
I have tried sideloading the stock MJ9 and MK2 files to no avail. I really hope somebody can help me, I don't know how much longer i can go without a phone. Thanks guys and Merry Christmas!!!
yea sounds like bricked you cant flash roms on 4.3 yet take it to best buy that has a samsung center and just tell them samsung sent you here because my phone all of a sudden was acting up and they will flash it back to factory for you thats what i had to do
gtj0 said:
OK, If you're stuck with an incomplete flash, here are some steps you can try to get to MJ9...
These instructions assume you started with MJ6.
First, make sure you can boot into recovery. If not, download and apply the MJ6 recovery.
recovery-mj6.tar.md5
It should apply without error. If not, report the failure.
Download and extract the following files...
mf3-emergency-part-1.tar.md5.7z
mf3-emergency-part-2.tar.md5.7z
If you don't already have it, download the mf3-mj9 update file...
update-mf3-mj9.zip
Start Odin, connect your phone and boot into Download mode.
Flash mf3-emergency-part-1.tar.md5 which contains modem.bin, NON-HLOS.bin and system.img.ext4.
The flash of system.img.ext4 WILL FAIL at the end. That's OK.
Reboot the phone back into Download mode and restart Odin.
Flash mf3-emergency-part-2.tar.md5 which contains cache.img.ext4.
The flash WILL FAIL at the end. That's OK.
The phone should now reboot to recovery by itself and apply a small update. If it fails, stop and report.
The phone should now reboot to a black screen with the pulsing notification LED.
Reboot into recovery mode and flash update-mf3-mj9.zip. I recommend sideloading instead of flashing from sdcard because the sdcard method reboots the phone whether the update was successful or not and you lose the error messages.
Reboot the phone and let it initialize.
You should now have MJ9.
Click to expand...
Click to collapse
download the above files except update-mf3-mj9.zip and replace with MF3>MK2 from this thread
http://forum.xda-developers.com/showthread.php?t=2573080
Hashcode has a Beta safesatrap for MK2 Safestrap-JFLTEATT-3.70-B01 if you want to flash anything to a rom slot or stock slot and make a backup (does not work with EXFAT formatted sd yet)
http://forum.xda-developers.com/showthread.php?t=2448925
dolph8886 said:
download the above files except update-mf3-mj9.zip and replace with MF3>MK2 from this thread
http://forum.xda-developers.com/showthread.php?t=2573080
Hashcode has a Beta safesatrap for MK2 Safestrap-JFLTEATT-3.70-B01 if you want to flash anything to a rom slot or stock slot and make a backup (does not work with EXFAT formatted sd yet)
http://forum.xda-developers.com/showthread.php?t=2448925
Click to expand...
Click to collapse
I was on MK2 using the 3.7 beta of SS when I couldn't get it to boot anymore. Tried the modified method outlined above, everything worked except after step 7, it never rebooted to recovery on it's own and installed a small update. Decided to try Kies, says it can do emergency firmware recovery but it hasn't worked yet. Any help would be appreciated as I'm not sure I can get the handset replaced since I got it at Walmart.
It may not automatically reboot into recovery, just make it.
if you do not already know this (i am not saying you don't)
holding the power button for 10? seconds will reboot phone or using the file in post below
http://forum.xda-developers.com/showpost.php?p=48621760&postcount=18
hold volume up and power the phone on to boot into stock recovery
have android sdk and files above ready
choose option to sideload update from adb
open terminal on computer and
adb sideload "update.zip"
without quotes
here are basically the same instructions just a bit different
sl1200md3 said:
Back on AT&T STOCK MK2 from a bricked TWRP'd install. I had to do the following:
1) Phone into download mode
2) Flash mf3-emergency-part-1.tar.md5 via Odin v1.85
3) Force Reboot
4) Flash mf3-emergency-part-2.tar.md5
5) Unplug phone / Reset Odin / plug phone back in
6) Flash recovery-mj6.tar.md5
7) Force Reboot in Odin using this file http://forum.xda-developers.com/showthread.php?t=1766399 Thanks kevinpc :good:
8) Manually enter recovery
9) ADB Sideload the file: update-mf3-mj9.zip found here: http://forum.xda-developers.com/showpost.php?p=47604388&postcount=152
10) ADB Sideload the file: update-MJ9-MK2.zip found here: https://docs.google.com/file/d/0B2iXrnZBB-MVYkYwNkYzU2FJaFk/edit
11) Reboot
Won't be flashing TWRP via Goo Manager again any time soon.
:good::good::good:
Click to expand...
Click to collapse
dolph8886 said:
It may not automatically reboot into recovery, just make it.
if you do not already know this (i am not saying you don't)
holding the power button for 10? seconds will reboot phone or using the file in post below
http://forum.xda-developers.com/showpost.php?p=48621760&postcount=18
hold volume up and power the phone on to boot into stock recovery
have android sdk and files above ready
choose option to sideload update from adb
open terminal on computer and
adb sideload "update.zip"
without quotes
here are basically the same instructions just a bit different
Click to expand...
Click to collapse
You sir, are amazing. What you posted was just different enough from what I had previously tried to work. I'm now booting and on MK2, thanks a million man!
FINALLY
dolph8886 said:
download the above files except update-mf3-mj9.zip and replace with MF3>MK2 from this thread
http://forum.xda-developers.com/showthread.php?t=2573080
Hashcode has a Beta safesatrap for MK2 Safestrap-JFLTEATT-3.70-B01 if you want to flash anything to a rom slot or stock slot and make a backup (does not work with EXFAT formatted sd yet)
http://forum.xda-developers.com/showthread.php?t=2448925
Click to expand...
Click to collapse
FINALLY LONG SEARCH OVER FOR THIS FIX JUST ONE QUESTION WILL THE RECOVERY FAIL AS WELL?
tonyc0642 said:
You sir, are amazing. What you posted was just different enough from what I had previously tried to work. I'm now booting and on MK2, thanks a million man!
Click to expand...
Click to collapse
hi i have the exact same problem....i dont know how to start adb on windows 7...arrgh...
Thanks to the everyone for this
It saved my ass..I put the zips on a sd and installed.Back on mk2 and rooted.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
I tried the above mentioned but after I flash the second file and reboot, it goes into kies , no recovery mode. Odin is still available. Also thanks for all the quick responses fellas yall are the best.
***UPDATE*** flashed the recovery but the sideload failed. Tried to turn it on and the Samsung lolgo came on, then went black. After a a few minutes the phone pops up on the computer and I can access the internal phone memory and the sd card.
I am really not sure, I believe that it will work if you do this process again.
No Idea if this makes any difference but, pay close attention to the process at least until the sideloading of the update.
Do not let the device attempt to boot with this firmware mismatch as this may cause issues. (This is the only conclusion I can come to as this process does work)
If the device automatically reboots then press and hold volume up to enter recovery or volume down to enter download mode.
If manual reboot or powering on then press and hold volume up or down respectively then press power until the device starts and release power button to avoid a reset.
SOLVED!!!
Thank you so much @dolph8886!!!1 You are the BEST!!! :good: :victory: :highfive:
This helped me, fixed my softbrick, hope this helps! Remember to thank the author if it works
http://forum.xda-developers.com/showthread.php?t=2621279
ok here it goes i tried to flash twrp using goo but now i have no stock recovery can someone help me please im on mk2 running 4.3 and rooted
So I've been running a rooted Note 3 for a while. When the Note 3 Kitkat update came out, I updated it via Odin as OTA update was not available since I was rooted.
All the posts I read had mentioned that updating to 4.4.2 from 4.3 would erase all my data but after updating via odin all my data was in place. I had only lost root which I rooted again though CF Auto Root.
The problem now is that when I try to install CWM (via Odin) or TWRP (via Goo or Odin), it goes through the installation but then the phone goes into a boot loop of sorts..It's NOT the normal boot loop which gets stuck on the Samsung logo.
What happens is that the phone vibrates twice (with a 1 sec interval in between), then the Samsung Note 3 N-9005 screen appears with "Booting Recovery..." on the top left and within a sec it goes blank and then back to 2 vibrates and the screen come on to show Samsung Note 3 N-9005.
The only way I found to fix this was a battery pull and then turning on the device holding the power, home and down vol key to boot into recovery and then flashing CF Auto Root again.
I don't know why am I not able to install any of these recoveries. I've made sure I try to install the latest versions of them which are Kitkat compatible.
Anyone else with this problem or a solution?
Can a Cache and data wipe fix this? But the problem again being I won't be able to backup my ROM since i can't get these recoveries to install!
There is a script in official firmware that checks for official recovery and if it finds a custom one it tries to overwrite with official one. If i remember correct it's called install-recovery. sh
PhilZ recovery handles it automatically.
It's impossibe to flash anything other than the leaked 4.4.2 stock because you flashed your bootloader to kitkat, no you MUST stay on sammy 4.4.2 till the devs found a solution for this. Thats why you have to read carefully be4 you flash.
silentvisitor said:
There is a script in official firmware that checks for official recovery and if it finds a custom one it tries to overwrite with official one. If i remember correct it's called install-recovery. sh
PhilZ recovery handles it automatically.
Click to expand...
Click to collapse
No luck!
I tried PhilZ recovery from the below link.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/hltexx
What are my other options?
sid8907 said:
No luck!
I tried PhilZ recovery from the below link.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/hltexx
What are my other options?
Click to expand...
Click to collapse
This one seems to be the only one working with 4.4.2 right now.
Possible solution
The way I can suggest is to create a little update.zip file with little updater-script to remove install-recovery.sh file from device (just one line needed).
Ok, I found a zip which I am attaching below. You(or anyone) may review the script before flashing.
Place this on your external (or internal) sdcard.
In ODIN don't check Auto reboot
Flash Recovery. Remove phone when it says PASS.
Remove battery. Start in Recovery mode by pressing buttons.
You should now be in new Recovery.
Flash that zip file.
Reboot.
You should be good.
The Auto Reboot for some reason is faded out. Tried different versions of Odin and also tried to open it with the phone connected/disconnected.
I am out of ideas.
I would suggest you to wait for someone to come up with working solution. Being too adventurous with ODIN could brick your device.
sid8907 said:
The Auto Reboot for some reason is faded out. Tried different versions of Odin and also tried to open it with the phone connected/disconnected.
Click to expand...
Click to collapse
Clear out all your ODIN caches etc, delete all files and keep 1.85.
Flash this (only working recovery on 4.4.2) via PDA in ODIN, If it doesn't reboot auto after saying PASS or RESET.. just turn phone off, reboot into recovery and it'll be fine.
EDIT: Just re-read, Re flash your Stock 4.4.2 (Use XEO not the leaked one!) and then start again
Thanks!
Maybe a little off topic, but is there a way to install CM11 on Stock 4.4.2 on the Note 3?
I've been reading Samsung is out with a new bootloader so there is no way round this?
radicalisto said:
Clear out all your ODIN caches etc, delete all files and keep 1.85.
Flash this (only working recovery on 4.4.2) via PDA in ODIN, If it doesn't reboot auto after saying PASS or RESET.. just turn phone off, reboot into recovery and it'll be fine.
EDIT: Just re-read, Re flash your Stock 4.4.2 (Use XEO not the leaked one!) and then start again
Click to expand...
Click to collapse
Thanks!!
sid8907 said:
Thanks!
Maybe a little off topic, but is there a way to install CM11 on Stock 4.4.2 on the Note 3?
I've been reading Samsung is out with a new bootloader so there is no way round this?
Click to expand...
Click to collapse
You may have to do a little reading but I believe CM11 is now working on the KK bootloader...
sid8907 said:
So I've been running a rooted Note 3 for a while. When the Note 3 Kitkat update came out, I updated it via Odin as OTA update was not available since I was rooted.
All the posts I read had mentioned that updating to 4.4.2 from 4.3 would erase all my data but after updating via odin all my data was in place. I had only lost root which I rooted again though CF Auto Root.
The problem now is that when I try to install CWM (via Odin) or TWRP (via Goo or Odin), it goes through the installation but then the phone goes into a boot loop of sorts..It's NOT the normal boot loop which gets stuck on the Samsung logo.
What happens is that the phone vibrates twice (with a 1 sec interval in between), then the Samsung Note 3 N-9005 screen appears with "Booting Recovery..." on the top left and within a sec it goes blank and then back to 2 vibrates and the screen come on to show Samsung Note 3 N-9005.
The only way I found to fix this was a battery pull and then turning on the device holding the power, home and down vol key to boot into recovery and then flashing CF Auto Root again.
I don't know why am I not able to install any of these recoveries. I've made sure I try to install the latest versions of them which are Kitkat compatible.
Anyone else with this problem or a solution?
Can a Cache and data wipe fix this? But the problem again being I won't be able to backup my ROM since i can't get these recoveries to install!
Click to expand...
Click to collapse
here's the link for twrp for ya'll http://forum.xda-developers.com/showpost.php?p=50333147&postcount=398
sid8907 said:
So I've been running a rooted Note 3 for a while. When the Note 3 Kitkat update came out, I updated it via Odin as OTA update was not available since I was rooted.
All the posts I read had mentioned that updating to 4.4.2 from 4.3 would erase all my data but after updating via odin all my data was in place. I had only lost root which I rooted again though CF Auto Root.
The problem now is that when I try to install CWM (via Odin) or TWRP (via Goo or Odin), it goes through the installation but then the phone goes into a boot loop of sorts..It's NOT the normal boot loop which gets stuck on the Samsung logo.
What happens is that the phone vibrates twice (with a 1 sec interval in between), then the Samsung Note 3 N-9005 screen appears with "Booting Recovery..." on the top left and within a sec it goes blank and then back to 2 vibrates and the screen come on to show Samsung Note 3 N-9005.
The only way I found to fix this was a battery pull and then turning on the device holding the power, home and down vol key to boot into recovery and then flashing CF Auto Root again.
I don't know why am I not able to install any of these recoveries. I've made sure I try to install the latest versions of them which are Kitkat compatible.
Anyone else with this problem or a solution?
Can a Cache and data wipe fix this? But the problem again being I won't be able to backup my ROM since i can't get these recoveries to install!
Click to expand...
Click to collapse
jp.26 said:
here's the link for twrp for ya'll http://forum.xda-developers.com/showpost.php?p=50333147&postcount=398
Click to expand...
Click to collapse
so.... yeah i just updated my bootloader to 4.4.2 and this drove me literally insane. ive been working on it for 4 hours now. i encountered so many problems with installing the bootloader. exact same problem as SID8907. i gotta tell you tho.... you worked some magic my friend. i tried almost everything. then i came across your link. i was like why not? so i flashed the img in odin..... anddddd :drumroll pleaseeeeee:: IT WORKED. ahhh....... so much frustration and the problem is solved!!! thank you so much JP.26 :good::laugh:
is there any word on how to fix this been looking for hours tmobile note beast dont want to put any roots down on my phone before i find a way to flash cm or a non bloated note rom would be nice.
I'll that I've managed is to root and flash twrp I found a way to turn cwm recovery into a tar file and flash through odin. But i just get into a boot loop with cwm due to the boot loader I presume but tarp works fine I just can't flash cm11. I get boot loop every time
Sent from my SM-N900T using XDA Premium 4 mobile app
im sorry but im confused here... does this all simply mean that there is not yet a working cwm for 4.4.2 yet? and that while we can root, there is no working recovery for this version?
I'm not sure myself tarp works but I can't flash cm11
Sent from my SM-N900T using Tapatalk
Phillz cwm Dev edition I think that's the name works its a themed touch cwm. This works great but still can't flash cm so gayyyy
Sent from my SM-N900T using Tapatalk
I was wondering what happened to the cmw too.
The modded cmw by Chenglu is the only one working that I know of.
Link to thread: http://forum.xda-developers.com/showthread.php?t=2454079
all.
I have an i9505 on 3 UK that has been rooted for over 6 months. I've been running the excellent TW based Echo Rom but wanted to try an ASOP rom but quickly wanted to revert.
I tried to restore my Nandroid but this failed and screwed up the phone (dont ask)so back to ODIN and i flashed back to stock 4.4.2 firmware for the UK via Sammobile (NG8)
Now back to square 1 so attempted to reroot with CF Autoroot again via ODIN. all show pass and i get the black screen on the phone with the red android logo and line stating stock recovery restored. I then used ODIN to flash Philz recovery again shown as Pass, however when i try to get into recovery i get some small white text on the bkack background that is there too briefly to read before the phone reboots as normal.
The Su superuser app is there but states the Su binary is outdated and the phone has no root access.
Ive read a few methods to get round this but they all seem to follow the same process ive tried a few times now.
The Rom for Echoe is auto root so id have thought if i could get to recovery somehow i could just flash this ?
Any one any views or have i screwed up for good ? .
You will be fine.
If you want to flash a custom rom anyway the shortest way would be to just flash the custom recovery. You don't need root for that.
Uncheck auto-reboot before you flash the recovery and it should work.
Lennyz1988 said:
You will be fine.
If you want to flash a custom rom anyway the shortest way would be to just flash the custom recovery. You don't need root for that.
Uncheck auto-reboot before you flash the recovery and it should work.
Click to expand...
Click to collapse
so i reflashed Philz recovery and unchecked auto reboot. This then gives me PASS in ODIN. I guess then i unplug and try and activate recovery - but still nothing...it just boots up normally ?
robinta said:
so i reflashed Philz recovery and unchecked auto reboot. This then gives me PASS in ODIN. I guess then i unplug and try and activate recovery - but still nothing...it just boots up normally ?
Click to expand...
Click to collapse
What is the model descriped when you are in download mode?
What is the exact version of Philz you are trying to flash?
Lennyz1988 said:
What is the model descriped when you are in download mode?
What is the exact version of Philz you are trying to flash?
Click to expand...
Click to collapse
GTI9505...(Bootloader i9505xxegng8)
Originally I tried philz_touch_5.15.8-i9505.tar.md5
and then updated to philz_touch_6.23.9-i9505.tar.md5 with no avail.
Try redownloading it. If you say that if passes, then it should just work.
If it still fails then try TWRP. Uncheck auto-reboot before flashing.
Could it be connected to me flashing a generic unlocked UK firmware on a 3 UK handset ?
That's sorted it ! Flashed CWM recovery and am now running Echoes v28.
Thanks for the help. I was really panicking for a while.
I wont be changing roms for a while but I guess if I did I won't lose root ?
Hey everyone,
I'm sorry for the poor formatting, I've gone a day already without sleep. I decided to install Biggins onto my Note 3 from MJE. So I flashed the NC4 firmware as asked. It Passed in Odin 3.09, and then the phone never booted.
Okay...
So here I'm about to eat my shoes because I'm tired and I do stupid things when I'm tired.
I realize by now I've probably lost Safestrap Recovery, so I boot into regular recovery, I guess Samsung Recovery mode (said manual mode). I thought "Oh, Well I'll just wipe everything here and install it then." I did realize there's a reason Safestrap Recovery is there and that's to install the ROM onto the certain Stock Rom slot like it says too - after I wiped it all.
I've spent hours on this, and it might be the sleep deprivation at it's work here. Not sure what else to do. When I enter recovery I see a dead No Command droid laying down. In red at the top it says Android system recovery, KOT49H.N900VVRUCNC4
I'm very aggravated at this and about ready to throw a temper tantrum mixed with irresponsibility and booze.
What do I do? Is this something simple I'm not getting or something difficult?
Need to start from scratch. Download NC4 firmware and flash in Odin. Then re-root, safestrap, and flash rom.
Odin the NC4 full tar again. Then as soon as you're done, go into the factory recovery and do the factory reset and you're phone will boot. Then you can re-root, safestrap, etc
It probably was an accident but this goes in the Q & A section. Hope you get up and running.
I agree that you need to Odin the FULL NC4 Tar file. Since you've wiped Safestrap off your phone, you need to enter "Download" mode and NOT the stock recovery mode.
To enter download mode, start with the phone powered off. You may need to do a battery pull as a last resort. Then, with the phone powered off, simultaneously press the volume down, home and power buttons. Release all the buttons when the Warning! screen appears. Then press the volume up button to confirm you want to boot into "Download" mode.
Once there, you can now launch Odin on your computer and connect your phone via USB to your computer. Since it sounds like you've already flashed via Odin, you should already have the USB drivers installed.
Flash the full NC4 Tar file, let it reboot and you'll be back to stock. Root via Towelroot, install Busybox, reboot, then reinstall Safestrap.
Good luck!!
Matthewbe said:
Hey everyone,
I'm sorry for the poor formatting, I've gone a day already without sleep. I decided to install Biggins onto my Note 3 from MJE. So I flashed the NC4 firmware as asked. It Passed in Odin 3.09, and then the phone never booted.
Okay...
So here I'm about to eat my shoes because I'm tired and I do stupid things when I'm tired.
I realize by now I've probably lost Safestrap Recovery, so I boot into regular recovery, I guess Samsung Recovery mode (said manual mode). I thought "Oh, Well I'll just wipe everything here and install it then." I did realize there's a reason Safestrap Recovery is there and that's to install the ROM onto the certain Stock Rom slot like it says too - after I wiped it all.
I've spent hours on this, and it might be the sleep deprivation at it's work here. Not sure what else to do. When I enter recovery I see a dead No Command droid laying down. In red at the top it says Android system recovery, KOT49H.N900VVRUCNC4
I'm very aggravated at this and about ready to throw a temper tantrum mixed with irresponsibility and booze.
What do I do? Is this something simple I'm not getting or something difficult?
Click to expand...
Click to collapse
Don't forget to breath, you'll be OK, Samsung makes a tuff phone!
same exact thing
winlinand said:
Don't forget to breath, you'll be OK, Samsung makes a tuff phone!
Click to expand...
Click to collapse
Same this is happening to me. i tried reflashing firmware with odin 1.85, i haven't been able to find 3.09 anywhere. i'm wondering that was the problem.
i used these instyructions
[ROM/ROOT][N900VVRUCNC4][4.4.2] Stock Root DeOdex [06/18/14] NC2/NC4/DevEd COMPATIBLE ★ Insecure Modules/Selinux Permissive ON NC4 Bootloader!!
New to the S4 - did a search and could not find a similar problem as mine...
My friend gave me his S4 and told me it is rooted - which it is. However, there seems to be no recovery on the phone. When I try power-vol up-home, I get the blue recovery note at the top, but then the phone just continues to boot into the system (MF9). I used Odin to go back to stock and then attempted to boot into recovery - no luck. I rooted the phone again via CF Auto Root and tried to install a custom recovery via Odin and TWRP Manager - still no luck. Anyone have any ideas/suggestions? I appreciate the help.
Bumping this up to the top for one more run through...thanks everyone.
Sixbowmans said:
Bumping this up to the top for one more run through...thanks everyone.
Click to expand...
Click to collapse
Maybe go in to Odin mode and flash latest stock making sure to unchecked the auto reboot option. When it finishes flashing unplug and pull the battery, let it boot it'll take a while (took mine about 10-15 minutes). You'll then be on latest stock with latest bootloader and recovery. From there you can go back to Odin mode and flash TWRP. Once again making sure to not auto reboot.
Just to be safe back up apps and msic and picture etc on samsung kies and then do a full recovery delete everything and install the latest firmware then try cf auto root again or if you have trouble with that rhen use kingoroot and then flash twrp or phils recovory and get a rom. If that doesnt work just get cyanogenmod installer which installs root and a stock rom.
Sent from my SM-N910V using XDA Free mobile app
mattzeller said:
Maybe go in to Odin mode and flash latest stock making sure to unchecked the auto reboot option. When it finishes flashing unplug and pull the battery, let it boot it'll take a while (took mine about 10-15 minutes). You'll then be on latest stock with latest bootloader and recovery. From there you can go back to Odin mode and flash TWRP. Once again making sure to not auto reboot.
Click to expand...
Click to collapse
Thanks mattzeller. Your suggestion took me back to my Evo days. I took out the sd card, flashed with Odin, pulled the battery, rebooted the system, and then was also able to boot into recovery.