Database Users

Help! Brick?

K, I'm trying to fix my friends verizon note 3, it's stuck in dl mode with the error "Firmware upgrade encountered an issue. Please use software Repair assistant & try again". Phone will NOT connect to kies, I get an error saying "This phone is not supported". My version of kies does see my att n3 just fine though. I can connect to odin it looks like. Cannot boot into recovery, it just boots into dl mode with the error message. Unknown how the phone got in this state.

9wire said:
K, I'm trying to fix my friends verizon note 3, it's stuck in dl mode with the error "Firmware upgrade encountered an issue. Please use software Repair assistant & try again". Phone will NOT connect to kies, I get an error saying "This phone is not supported". My version of kies does see my att n3 just fine though. I can connect to odin it looks like. Cannot boot into recovery, it just boots into dl mode with the error message. Unknown how the phone got in this state.
Click to expand...
Click to collapse
If your in download mode and can get odin to recognize the phone then get the mje tar and Odin back to stock.

Harleydroid said:
If your in download mode and can get odin to recognize the phone then get the mje tar and Odin back to stock.
Click to expand...
Click to collapse
Does it matter which one? No idea what's on the phone.

9wire said:
Does it matter which one? No idea what's on the phone.
Click to expand...
Click to collapse
Is the phone on 4.3 or 4.4.2 right now? If 4.4.2 which one? The full odin sxtp leak or the rooted leaked build by Beanstown?
Edit. I see your not sure what's on the phone now.

No idea. Installed the pit file and can get into recovery and download now but wont boot. Phone hasn't booted since I got it. Here's what I have...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

9wire said:
No idea. Installed the pit file and can get into recovery and download now but wont boot. Phone hasn't booted since I got it. Here's what I have...
Click to expand...
Click to collapse
Yeah I'd try the mje tar located here
http://forum.xda-developers.com/showthread.php?t=2528707
[Firmware][Guide][Q&A] FIRMWARE MIRROR / OTA & ROOT GUIDE / TECHNICAL Q&A
If it works then you can root and do the build by Beans and flash the firmware to get on rooted 4.4.2

downloading mj7 from here, I'm just in the dark about what I have on the phone, it just needs to be stock non-rooted. Didn't know if flashing the .tar would break it if I have a different firmware. I don't know how to find out if the phone won"t boot.
http://forum.xda-developers.com/showthread.php?t=2524572

9wire said:
downloading mj7 from here, I'm just in the dark about what I have on the phone, it just needs to be stock non-rooted. Didn't know if flashing the .tar would break it if I have a different firmware. I don't know how to find out if the phone won"t boot.
http://forum.xda-developers.com/showthread.php?t=2524572
Click to expand...
Click to collapse
No do the MJE tar

Dev host not working for me. Tried to dl several things this afternoon and nothing is working. Had to odin my n2 back to stock so I can sell it.

DL'ing now. Appreciate your time, sir. We'll see what happens.

9wire said:
DL'ing now. Appreciate your time, sir. We'll see what happens.
Click to expand...
Click to collapse
Cool let me know. It should work fine. The only reason it wouldn't is if it was on the unrooted 4.4.2 build.

Harleydroid said:
Cool let me know. It should work fine. The only reason it wouldn't is if it was on the unrooted 4.4.2 build.
Click to expand...
Click to collapse
Whut? Could it be? Ha ha, back from the dead. Only took about 6 hours total. Messed with kies for almost 3 hours before I gave up. Downloaded 2 versions of kies twice, drivers multiple times, 2 .tar files, tried 6 different usb cords...
Thanks for your help @Harleydroid, much appreciated.

Ans a screenie of my slightly modded att n3 for your perusal and enjoyment.

Galaxy J5 (2017) stuck in recovrey mode.

Hi. During the update to Android 10 the phone turned off and after switching on it goes into recovery mode.
The phone is not mine and this description was provided to me by the owner of the phone. I was unable to see the phone directly because of the quarantine, so as a first solution I thought about a restore via odin. Has anyone had this problem? And is there a less drastic way than Odin to solve? Because the owner has some data that he would prefer not to lose.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

How did you get android 10 on j530f?
I get the same messages when I enter recovery but I'm able to get out. You could use odin to reflash the firmware but keep all the data.

You won't be able to do a thing with Odin if the device doesn't have an unlocked bootloader and USB debugging enabled which I doubt it has seeing as it's a stock update that was attempted.
What happens to the device once plugged into a PC? Is the data corrupt or is the device recognized and files can be seen?

I have the same problem with almost the same recovery messsges. It also says dm verity failed. Odin and samsung 300k tool both dont work.

myusernamesucks said:
I have the same problem with almost the same recovery messsges. It also says dm verity failed. Odin and samsung 300k tool both dont work.
Click to expand...
Click to collapse
Hi,
can you give some details what has happened?
I think you have to install TWRP. Otherwise you have no chance to debug anything...

Emelin.2004 said:
How did you get android 10 on j530f?
I get the same messages when I enter recovery but I'm able to get out. You could use odin to reflash the firmware but keep all the data.
Click to expand...
Click to collapse
I don't know how the phone has Android 10, as I said "The phone is not mine and this description was provided to me by the owner of the phone", sorry.
garylawwd said:
You won't be able to do a thing with Odin if the device doesn't have an unlocked bootloader and USB debugging enabled which I doubt it has seeing as it's a stock update that was attempted.
What happens to the device once plugged into a PC? Is the data corrupt or is the device recognized and files can be seen?
Click to expand...
Click to collapse
Not even to flash a stock firmware? It seems strange to me, in the past I have often used odin on my S2 also for the stock ROM.
The device always reboot in recovery, I don't think the PC can see it.
jaggedN said:
Hi,
can you give some details what has happened?
I think you have to install TWRP. Otherwise you have no chance to debug anything...
Click to expand...
Click to collapse
Hi, the details were given to me by another person, the only thing that I (and this person knows) is that the phone during an update has turned off and reboots in the attached image window.
Thanks for the tips, I will report it to the person concerned, hoping that he can install the twrp.

TheNightmare97 said:
I don't know how the phone has Android 10, as I said "The phone is not mine and this description was provided to me by the owner of the phone", sorry.
Not even to flash a stock firmware? It seems strange to me, in the past I have often used odin on my S2 also for the stock ROM.
The device always reboot in recovery, I don't think the PC can see it.
Hi, the details were given to me by another person, the only thing that I (and this person knows) is that the phone during an update has turned off and reboots in the attached image window.
Thanks for the tips, I will report it to the person concerned, hoping that he can install the twrp.
Click to expand...
Click to collapse
Put the j5ylte update onto sd card.
Get the update from updato or sammobile or somewhere.
Then reboot stock recovery and apply update from sd card. Or sideload it using adb on a computer. Not very complicated at all

Install the stock rom like i described here: https://forum.xda-developers.com/galaxy-j5/help/to-stock-rom-t4099857

jaggedN said:
Hi,
can you give some details what has happened?
I think you have to install TWRP. Otherwise you have no chance to debug anything...
Click to expand...
Click to collapse
I cant even access download mode neither can I apply an update from SD card. It says dm-verity failed. System is completely stock. I didn't modify anything.

SOLVED | Trying to root Galaxy S8

Im trying to root my Samsung Galaxy S8 but im stuck on a step in this guide.
Following the steps in the guide, it was all going well and fairly quick until this...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I can't install TWRP for some reason, the download link in the guide leads to a site with multiple downloads of TWRP, but none of them (4) seem to work.
Am I missing something, please help.
Maybe the guide didn't mention something or maybe an update to my phone made this guide outdated.
If you need additional information, ask.
Thanks to hainguyenthao for helping me get root.

Try a newer version of TWRP: https://dl.twrp.me/dreamlte/
It could possibly be a driver issue, but since the device is detected by Odin, then I don't think that drivers will fix it.
Also, make sure of course that this is the Samsung Exynos model and not the Qualcomm model with the Snapdragon CPU.

NTGDeveloper said:
Try a newer version of TWRP: https://dl.twrp.me/dreamlte/
It could possibly be a driver issue, but since the device is detected by Odin, then I don't think that drivers will fix it.
Also, make sure of course that this is the Samsung Exynos model and not the Qualcomm model with the Snapdragon CPU.
Click to expand...
Click to collapse
Thanks for the quick reply.
How do I make sure it's Exynos and not Snapdragon?

Nvm, I downloaded CPU-Z and it reports it's Samsung Exynos Octa 8895

NTGDeveloper said:
Try a newer version of TWRP: https://dl.twrp.me/dreamlte/
It could possibly be a driver issue, but since the device is detected by Odin, then I don't think that drivers will fix it.
Also, make sure of course that this is the Samsung Exynos model and not the Qualcomm model with the Snapdragon CPU.
Click to expand...
Click to collapse
Version 3.5.0_9-0 of TWRP doesn't work, same error

Install latest Odin not patched. Then flash it in download mode.

Ukasi said:
Install latest Odin not patched. Then flash it in download mode.
Click to expand...
Click to collapse
First, can you tell me where I can download a safe (no malware/virus download) version?
Second, what exactly is download mode and how do I make sure im using it?

Ukasi said:
Install latest Odin not patched. Then flash it in download mode.
Click to expand...
Click to collapse
I ended up just researching a bit about it and doing it...
It seems to have worked
But then following the instruction "Now, boot your device into the TWRP Recovery by pressing and holding the VOLUME UP, BIXBY KEY, and POWER BUTTON." led to what I believe is a default recovery which makes me think it didn't work despite it saying it's a pass.

GamerNameHere said:
First, can you tell me where I can download a safe (no malware/virus download) version?
Second, what exactly is download mode and how do I make sure im using it?
Click to expand...
Click to collapse
VOLUME DOWN + BIXBY + POWER to get Download (Odin Mode) by these combo.

Ukasi said:
VOLUME DOWN + BIXBY + POWER to get Download (Odin Mode) by these combo.
Click to expand...
Click to collapse
Thanks but I figured it out and end result didn't seem to work.
I feel like the guide is missing something, because it says to open the windows powershell but then never touches on that again. Similar to the No dm-verity download, I don't see it anywhere mentioned where or why to use it.

Issue solved thanks to hainguyenthao.

GamerNameHere said:
Im trying to root my Samsung Galaxy S8 but im stuck on a step in this guide.
Following the steps in the guide, it was all going well and fairly quick until this...
View attachment 5227965
I can't install TWRP for some reason, the download link in the guide leads to a site with multiple downloads of TWRP, but none of them (4) seem to work.
Am I missing something, please help.
Maybe the guide didn't mention something or maybe an update to my phone made this guide outdated.
If you need additional information, ask.
Thanks to hainguyenthao for helping me get root.
Click to expand...
Click to collapse
Before continuimg to fail what contry are you in as samsung have made changes that stop certain contries to be rooted

Why didn't you share your solution? Or did I miss the Point?

Bought a Samsung Tab A SM-T387V, apparently has doordash on it, how can I wipe it and use it as a normal tablet?

EDIT 2022-06-30: FOUND A RELIABLE SOLUTION FOR MY NEW T307U TABLET! May work for other models! https://forum.xda-developers.com/t/...e-it-as-a-normal-tablet.4316969/post-87091297
Original post from 2021-08-09 below:
Following this thread to no avail: https://forum.xda-developers.com/t/doordash-knox-customized-tablet-unable-to-remove.3890522/
Setup requires an internet connection, at which point it sets up MobiControl:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My friend's an IT so he set up Meraki for me which I can enroll in instead of MobiControl, but a minute later this pops up:
I still have access to the settings but cannot enable USB Debugging.
I flashed a combination file which got me to the "factory binary" where I can unlock OEM and enable USB Debugging, but I don't know where to go from here:
I flashed a stock ROM, but that doesn't get rid of doordash and MobiControl during setup.
Please help!

Which Android version did you flash? Did you finally get rid of MobiControl?

XDA.Samsung said:
Which Android version didn't you flash? Did you finally get rid of MobiControl?
Click to expand...
Click to collapse
I solved this. Basically, I accidentally bricked the tablet, which I assume is what caused Samsung Knox to fail and thus Mobi Control didn't try installing on a fresh flash of Android 8.1. Fuller story below:
After 3 days straight of trying to reset the tablet, including flashing the combo file, trying anything I can think of, re-flashing the stock rom and seeing if the problem is gone, I finally fixed it.
What ended up happening was, while re-flashing the stock rom on my 4th attempt, I flashed the AP but not one of the other things (I guess CP?) which resulted in the tablet getting bricked.
Long story short, I held both volume buttons and power to boot into a blue download mode (as opposed to a black one via holding power down + volume and selecting download mode, since the volume down + power nor the volume up + power combos weren't working) and flashed the stock rom to it properly.
Upon setup, I was still required to set up wi-fi, but it didn't attempt to install mobicontrol! I've been using the tablet normally since. Who would have known accidentally bricking the tablet was all I needed to do!

genesisboy4 said:
I solved this. Basically, I accidentally bricked the tablet, which I assume is what caused Samsung Knox to fail and thus Mobi Control didn't try installing on a fresh flash of Android 8.1. Fuller story below:
After 3 days straight of trying to reset the tablet, including flashing the combo file, trying anything I can think of, re-flashing the stock rom and seeing if the problem is gone, I finally fixed it.
What ended up happening was, while re-flashing the stock rom on my 4th attempt, I flashed the AP but not one of the other things (I guess CP?) which resulted in the tablet getting bricked.
Long story short, I held both volume buttons and power to boot into a blue download mode (as opposed to a black one via holding power down + volume and selecting download mode, since the volume down + power nor the volume up + power combos weren't working) and flashed the stock rom to it properly.
Upon setup, I was still required to set up wi-fi, but it didn't attempt to install mobicontrol! I've been using the tablet normally since. Who would have known accidentally bricking the tablet was all I needed to do!
Click to expand...
Click to collapse
Good to know. Congratulation. Does it still show secured by knox on boot screen?

I had no luck. I can't flash anything, got error "MDM mode, can't download ".

XDA.Samsung said:
Good to know. Congratulation. Does it still show secured by knox on boot screen?
Click to expand...
Click to collapse
Yes, it does.
XDA.Samsung said:
I had no luck. I can't flash anything, got error "MDM mode, can't download ".
Click to expand...
Click to collapse
Make sure you're using the right version of odin for your tablet and you're flashing the right version of android.

genesisboy4 said:
Yes, it does.
Make sure you're using the right version of odin for your tablet and you're flashing the right version of android.
Click to expand...
Click to collapse
Which version of Odin did you use?

XDA.Samsung said:
Which version of Odin did you use?
Click to expand...
Click to collapse
Odin3_v3.13.3

genesisboy4 said:
Odin3_v3.13.3
Click to expand...
Click to collapse
After tried 5 versions of Odin, include 2 different v3.13.3, finally got a good news. I can flash T387v firmware Andriod 8.1 and 9. But the bad news is I cannot brick it, no matter flashed only AP or BL. I tried to flash with T387W or T387T firmware, I got PIT error messages.
Which version of firmware were you using?

XDA.Samsung said:
After tried 5 versions of Odin, include 2 different v3.13.3, finally got a good news. I can flash T387v firmware Andriod 8.1 and 9. But the bad news is I cannot brick it, no matter flashed only AP or BL. I tried to flash with T387W or T387T firmware, I got PIT error messages.
Which version of firmware were you using?
Click to expand...
Click to collapse
I think I installed android version SM-T387V_1_20200520121029_yelpqjg66y_fac.

genesisboy4 said:
I think I installed android version SM-T387V_1_20200520121029_yelpqjg66y_fac.
Click to expand...
Click to collapse
Thank you. It looks like it's Android 9. Did you update it to Android 10?

XDA.Samsung said:
Thank you. It looks like it's Android 9. Did you update it to Android 10?
Click to expand...
Click to collapse
It's Android 8.1. If that file I mentioned is 9, then it's not the one I flashed, but was instead on my to-do list of troubleshooting steps. I was going to try flashing Android 9 and 10 but I got it working with 8.1 so I'm keeping it on that. Plus, the newer the android, the more secure Samsung Knox will be, so it will be harder breaking it.

Any idea where you downloaded it from? I cant seem to find a link.

quiqsilverr said:
Any idea where you downloaded it from? I cant seem to find a link.
Click to expand...
Click to collapse
Android 10: https://samfrew.com/download/Galaxy__Tab__A__/1hjk/VZW/T387VVRU3CUI2/T387VVZW3CUI2/

"The fact that it has MobiControl installed suggests it's a company device, and is therefore administered by that company's IT department. It's probably going to be difficult to remove MobiControl unless you talk to that IT department about it."
The above is a quote I found regarding Knox and the MobiControl app. Which tells me that this thread, although likely unintentional, is violating XDA Forum Rule #9:
9. Don't get us into trouble.
Don't post copyrighted materials or do other things which will obviously lead to legal trouble. If you wouldn't do it on your own homepage, you probably shouldn't do it here either. This does not mean that we agree with everything that the software piracy lobby try to impose on us. It simply means that you cannot break any laws here, since we'll end up dealing with the legal hassle caused by you. Please use common sense: respect the forum, its users and those that write great code.
Click to expand...
Click to collapse
XDA does not wish to be held liable for circumventing device security regardless of intent of the user, which is why I'm closing this thread.
-Regards: Badger50

I bricked my phone [Samsung A40]

Hello guys,
I have tried several wrong root firmwares for my SM-A405FN smartphone. I thought it was A30 so I tried flashing custom roms for A30.
And I got "This phone is not running Samsung's official" error which it loops and enter in download mode everytime.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
then I flashed the WRONG stock rom for A30, despicte the fact I have A40.
The problem here, was that I couldn't flash anything due to some misterious "could not connect error".
After that appeared on the screen some information about the PIT,on the download mode.
I tried also flashing the firmware for the PIT, which it actual repartions the phone, and it runned succesefully. But I ended with this error:
"Error validating footer (6)
..tom recovery
Meta a405fnxxu4cv62, 54217902R"
My question it's if you know how to recuperate back my phone?
Next, I'm gonna try flashing my stock rom, preferably for Ver 9.0 / Pie Version. Then working on a solution for the problem above. And after that how to bypassing "Not running official Samsung".

Cristishor201 said:
....
I tried also flashing the firmware for the PIT,......
Click to expand...
Click to collapse
at 1st I don't own that device but several other Samsungs
Which FW was that? the right one?
Where from did you get it?
Do you have multiple part stock ROM (AP, BL, CSC, CP all as separate files)?
Download mode still working?
Odin still recognises the phone?
Flashing the firmware for pit doesn't work to repartition it.
Pit file has to be extracted from CSC file and placed in Odin separatly and "repartion" box checked.

UPDATE1:
I tried to upload stock with Odin, but I encountered an error.
Then I restarted the phone, and I got this message:
And I found on youtube & here on xda, that I have to use Smart Switch, old version.
Now I can not find the Serial Number, on the box... and I might have to uncover the back of the phone.

@Cristishor201 to me it seems there is no (stable) usb connection if at all.
Doesn't COM field in Odin turn blue when you connect it to PC?
Tried other cables or USB ports?
Btw to let me get a notification put a @ before my name

bmwdroid said:
at 1st I don't own that device but several other Samsungs
Which FW was that? the right one?
Where from did you get it?
Do you have multiple part stock ROM (AP, BL, CSC, CP all as separate files)?
Download mode still working?
Odin still recognises the phone?
Flashing the firmware for pit doesn't work to repartition it.
Pit file has to be extracted from CSC file and placed in Odin separatly and "repartion" box checked.
Click to expand...
Click to collapse
@bmwdroid:
1. I didn't used the right FirmWare from the begining. I used recovery for A30 instead A40
2. I got the stock from updato.com
3. yes, I do. I even have an CSC and a CSC_HOME
4. now download mode is no longer working...
5. yes, Odin still recognise the phone.
bmwdroid said:
@Cristishor201 to me it seems there is no (stable) usb connection if at all.
Doesn't COM field in Odin turn blue when you connect it to PC?
Tried other cables or USB ports?
Btw to let me get a notification put a @ before my name
Click to expand...
Click to collapse
6. Yes, it turns blue and it says COM8.
7. Only his cable. Is the only one C type cable.
do you think that I shall find the serial number on the back of plastic inside phone ? or do you know a work around without serial number ?

Cristishor201 said:
@bmwdroid:
1. I didn't used the right FirmWare.....
Click to expand...
Click to collapse
I understood that
Cristishor201 said:
... I used recovery for A30 instead A40
Click to expand...
Click to collapse
You mean TWRP? I thought you've flashed wrong firmware not wrong recovery.
Cristishor201 said:
2. I got the stock from updato.com
Click to expand...
Click to collapse
Solid source although I prefer SamFirm_Reborn_0.3.6.3
Cristishor201 said:
3. yes, I do. I even have an CSC and a CSC_HOME
Click to expand...
Click to collapse
Use CSC only for now, HOME only for keeping data when updating the correct firmware
Cristishor201 said:
4. now download mode is no longer working...
5. yes, Odin still recognise the phone.
6. Yes, it turns blue and it says COM8.
Click to expand...
Click to collapse
Download mode gotta be working when Odin recognises the phone.
I think you mean something else.
Cristishor201 said:
7. Only his cable. Is the only one C type cable.
do you think that I shall find the serial number on the back of plastic inside phone ? or do you know a work around without serial number ?
Click to expand...
Click to collapse
I've no idea. It former times the numbers where there.
If you haven't kept the box, no. But what will the number be good for?
On my other Samsungs with not detachable batteries it's printed on the back although very hard to read.

Double post

bmwdroid said:
If you haven't kept the box, no. But what will the number be good for?
Click to expand...
Click to collapse
At using Smart Switch, it asks me for the model, and serial number

sebbialsvikk said:
I found a way you wouldn't expect. Run odin, flash a recovery, flash stock rom, and you good to go. Odin acctually find the device. .
Click to expand...
Click to collapse
I was able to return to Download mode, by flashing the twrp (the right one).
But it still fails..

@bmwdroid​After I changed the cable, and flashed the latest stock (EMUI 11, instead EMUI 9), I did pass that error, and get repaired.
It get started with the initial installation steps.