Hello, my name is Marc-Yvan from Douala, Cameroon and I will tell you the whole story about how I successfully unbrick my Android Tablet. My aim is to share with you some tips about how to recover from a desperate situation of having an unusable tablet.
How I hard-bricked my Tablet:
First of all, let me tell you how I hard-bricked my beloved tablet after trying to unlock it from its original network lock. I got this tablet from a relative who live in USA but it was unfortunately network locked to the AT&T network. So I tried to unlock it by multiple means (by myself). I found a cracked software called “Octopus for Samsung” who was said able to unlock any kind of Samsung phones/tablet. When I tried to unlock my Tablet, the software starts the work and then told me that the device will turn off and turn on after a short time. But the Tablet did not turn on anymore and I spend 02 months trying to bring it back from the grave.
Definition:
Let me explain to you what is called a hard-bricked smartphone/tablet. It’s simply a smartphone/tablet which is unusable, doesn’t turn on (desperate black screen) and doesn’t react to any stimulation. But you have to know that these hard-bricked devices are displayed as unrecognized devices when plugged onto a computer. So a hard-bricked device is not a physically damaged device but is a sort of hardly logically damaged device which cannot boot at all and is not recognized by common flash tools such as Odin, etc.
How I unbricked my tablet:
Lucky Context (GOD’s help):
Fortunately, GOD helps me by guiding me through this situation in order to recover from it in a miraculous manner. I will explain it to you in a couple of points:
1- My Tablet was rooted before the incident. I did it by using an application found in play store: “Kingroot.apk”.
2- My Tablet was equipped with some tools like “Es explorer” and “Terminal Emulator”. You will understand how it fortunately helped me before the incident.
3- The real hand of GOD: In my quest of finding a mean to network unlock my tablet, I tried a method which was asking to save some partitions of the eMMC (A kind of processor memory. Sorry but I’m not an expert ). So I saved it to the memory of my Tablet and then transfered it to a folder in my computer (By using command lines with “Terminal Emulator”). This actually helped me after to revive my tablet.
Advice N° 1 (Prevention)
Before trying to explore the whole abilities of your Tablet by flashing it or trying to network unlock it; Do a backup of the primary boot partition of your eMMC by executing this command in the “Terminal Emulator” of your rooted device:
cat /dev/block/mmcblk0> sdcard/mmcblk0.img
Be careful, this command could save the life of your beloved Tablet. This command will actually copy the primary boot partition of your eMMC in a disk image which has the same name. So you have to keep that disk image in a safe place such as your computer or an external removable disk.
Advice N° 2 (Resolution)
The Story:
In my desperate actions trying to revive my hard-bricked tablet, I read tremendous forum posts and tried countless methods. Which lead me to install a new OS in my computer. It was actually Linux Ubuntu 16.4. I found a method which told me to try to write some kind of partitions images down to an SDCard to boot my Tablet with. But the partitions images proposed by the method didn’t succeed in recovering my Tablet. So some days later, when I turn on my computer, I fortunately found a file opened; it was the primary boot partition image file of my tablet that I saved before the incident (The real hand of GOD). So I decided (Inspired by the Holy Spirit) to try the previous method with the original boot partition image file of my tablet.
The Tip:
You will need an SDCard with a correct format (FAT32) and size (16Gb or 32Gb). You will also need to work in a Linux command line terminal. To write the boot partition image in your SDCard you will have to execute this command line:
sudo dd if=mmcblk0.img of=/dev/sdb bs=1024k status=progress
Note: The sd card may not be sdb though. In order to confirm, before writing, browse to /Dev and look at the properties of sdb to ensure it is in fact there (it might be sda, sdb, sdc, etc...). You can also try to unplug and then plug the SDCard to see the changes.
The Last Step (Eureka!!!)
The last step is just to insert the SDCard into the slot of your Hard-Bricked device, Turn it on and then feel its vibration that will let you know that your mission is completed. Your device is alive again.
Conclusion
The only conclusion that I can give is to NEVER GIVE UP when you are trying to solve a problem. You can be closer to the solution than you think.
Good Luck!
What are the chances you would upload the boot partition for me?
I hard bricked mine also, but unfortunately I didn't make a backup. Would you be kind enough to upload the bin file you dumped? I've looked everywhere and no one seems to have an emmc dump of this thing. lol
Related
I really need some help please! I think I may have done something very bad. I have a tmobile mytouch 3g. I was trying to update from cyanogenmod 4.2.1.9. I was using a darkstar theme from ringer nation.
Here’s where I think i screwed myself. I am fairly new to all this stuff so I was trying to find a guide on how to update the mod and instead of doing it properly by adding the files to the sd card, doing a wipe, and then installing everything. I instead messed up and did an install of sapping.nbh and basically followed all the directions to originally root the phone. Including formatting the sd card and everything. When I realized that i was doing this all wrong I was still able to load my os and everything seemed ok. I was getting a sd card error that said that the card was blank or had an unsupported file system, but I was able to mount it so, I erased everything off the card and then put the cyanogen update and the drc83_base file and attempted to load into recovery and do the update.
I loaded into and did a wipe. I attempted to follow the instructions on upgrading from the cyogen page. (God I wish I had found that page first) But after I did the wipe and I attempt to Apply any from SD I get “error: sd card is not mounted”
When I attempt to reboot the phone it goes to the tmobile mytouch logo, THEN it goes to my them logo from Ringer Nation, then it just goes to a black screen I let it sit there for like 5 minutes to see what would happen, but nothing. So I took out the battery and sim. I can get into recovery though so I hope that someone can help me figure out where to go from there.I thought that since I had done a wipe that the theme would have been deleted as well? This is weird.
I did do a nandroid backup before. Hopefully that will prove to be helpful. Sorry for the long post, but I wanted to dump as much useful information about this problem so that hopefully someone will be able to help! BTW I'm using a mac with the latest snow leopard software.
As I am desperate for help, please reach out to me via aim – icolinirie or via email
Thank you in advance for everything. This is a great community, and all of Cyanogen’s work is greatly appreciated!!
EDIT: I really need some help! Here's some more information. I have a Magic 32B. Its running Cyanogenmod v1.4 + JF Recovery.
From what I have gathered I need to adp into my phone in order to get it to mount. Anyone know how to do this on a mac. I am trying, but I don't fully understand. I have created the .bash_profile from terminal and typed the following "export PATH=${PATH}:/Users/itunes/Documents/android-sdk-mac_86/tools" which is the path to the tools file in the sdk. I am just stuck at this point. I don't know what to do from here.
Hi I quote.
Install SDK utilities you need to connect your PC to your phone
You can download the full SDK from the Android Developer website for your platform
http://developer.android.com/sdk/index.html
You'll need to download the SDK appropriate for your platform and extract it into a directory somewhere. I'm going to assume you're using Windows here and suggest you extract it into a folder called
C:\AndroidSDK\
on your hard disk. You can put it anywhere you like really, but if you do you'll need to substitute it for the folder above.
Add the tools directory to your system path for easy access
In Windows it's easy to add the Android SDK Tools directory to your system path. Doing this lets you use the Android SDK tools anywhere and makes it easier for you.
On Windows XP: Go to Control Panel->System, Choose the 'Advanced' tab and then click 'Environment Variables' To do this on Vista/Windows7: Simply go to Control Panel->System and choose 'Advanced System Settings' and then 'Environment Variables'
Now that you've got here locate Path under System Variables and click Edit, then add the following to the end of the string displayed:
;C:\AndroidSDK\tools\
Then click OK until you get out of the menus.
Now that you've done this you should be able to bring up a command shell and type 'adb' and it should run straight away without needing to change path.
Please note that you can skip this step completely if you find it too complicated - however you will need to CD to the ?AndroidSDK\tools every time you open up a command prompt so it's worthwhile doing. I'm going to assume you have made the change above in all further examples as it gets too complicated really. If you're not confident in a DOS shell, I'd suggest you do a little bit of reading up on basic navigation in DOS first.
Enable Debugging mode on the phone before connecting to PC and installing the ADB driver
Menu > Settings > Applications > Developement > USB Debugging
Install the USB drivers correctly - check using "adb devices".
If you have already connected your phone to your computer before then the USB drivers are probably already loaded. If you're lucky then typing 'adb devices' in a command prompt will produce something like:
C:\AndroidSDK>adb devices
List of devices attached
XXXXXXXXXXXX device
Where XXXXXXXXXXXX is the serial number of your phone. If it doesn't produce that line, then you need to check Device Manager and ensure the device drivers for your phone were installed correctly.
If you are having issues installing the ADB driver, you need to connect your phone then go into Device Manager and check the ADB device properties. Check the following property and it'll look something like:
Device Instance Id: USB\VID_0BB4&PID_0C02&MI_01\7&293A7D0D&0&0001
To fix the driver installation problem, you need to edit the driver's .ini file and change all the references of 0C03 to 0C02, or 0C02 to 0C03 if your device property states your Device Id is 0C03.
Note: After flashing a new ROM, your Device Id may change again to either 0C03 or remain as 0C02. So you need to update the .ini file again as above to refelect the change and re-install the driver. Another known way to fix the above issue is to download and install HTC Sync - this seems to install the correct drivers.
How to use ADB
ADB stands for Android Debugging Bridge - it's a useful way of talking to your handset while it's running. ADB provides commands for copying files to and from your phone, installing packages and debugging your Android applications.
Useful commands include:
adb devices - lists which devices are currently attached to your computer
adb install <packagename.apk> - lets you install an Android application on your phone
adb remount - Remounts your system in write mode - this lets you alter system files on your phone using ADB
adb push <localfile> <location on your phone> - lets you upload files to your phones filesystem
adb pull <location on your phone> <localfile> - lets you download files off your phones filesystem
adb logcat - starts dumping debugging information from your handset to the console - useful for debugging your apps
adb shell <command> - drops you into a basic linux command shell on your phone with no parameters, or lets you run commands directly
How to use Fastboot
Fastboot is another boot method and is used to drop the phone into a safe mode to load/flash alternate roms. You need USB debugging turned on before you can use Fastboot mode - so I'd recommend you do this first (under Settings->Applications->Development->USB Debugging). You will also need to power off your phone first (hold down Power and select Power Off) and then hold down the Back+Power Buttons to start the phone in Fastboot mode. You will need your USB cable connected to be able to issue any commands and assuming your drivers are correct you should be able to issue:
C:\AndroidSDK>fastboot devices
List of devices attached
XXXXXXXXXXXX fastboot
Other commands in this mode include - we'll cover these below in subsequent sections.
fastboot boot <filename> - boots a rom stored on your pc specified by the filename
fastboot flash <partition> <filename> - flashes a rom stored on your pc, partition can be one of {boot, recovery, system, userdata}
fastboot binaries for mac and linux can be found here.
3. Learn how to use fastboot and boot a recovery rom
Download a recovery rom for your device
There are several different recovery roms available for the HTC Magic devices.
Amon_RA has created several nice recovery roms available from http://forum.xda-developers.com/showthread.php?t=530492 and get the Recovery Rom appropriate for your device - these recovery roms have Nandroid Backup and Nandroid Restore and are perfect for the average user.
You can also use Cyanogen's 1.3.1 Recovery ROM available for: PVT32A devices and PVT32B devices - this rom has some additional options for partitioning your SD card for ?Apps2SD/Swapper/etc.
Fastboot the recovery rom
Fastbooting a rom doesn't write anything to your device - it just loads it directly from your PC - so it's a completely safe way of fixing/recovering/backing up your existing rom. To fastboot a rom you need to first drop your phone into Fastboot mode and check that it's working. Now drop into a command shell and make sure the recovery image you're wanting to load is in the same directory that you're running this in. If it's called something other than recovery-rom.img then substitute that instead.
C:\AndroidSDK> fastboot boot recovery-rom.img
If you are having problems changing the directory in the command prompt, just make a copy of the command prompt .exe itself, and place it in the folder that contains the recovery rom, then run the above command.
And once again, if you have a perfected SPL which does not allow remote fastboot, you will have to fix it first.
Use the Recovery Rom to Backup your current ROM with Nandroid
Once you've booted to a recovery rom - you can use the Nandroid Backup option. If you get a 'cannot mount /dev/mkblkxxx error' when you do this then check your microSD card is inserted correctly and if so, wait a few seconds for it to register to the recovery rom correctly. If at first you don't succeed, try, try again (sdcard can take a few seconds to mount!)
You do not need to be a rocket scientist to do this.
you can use the ADB to put in recovery again by fast boot
http://forum.xda-developers.com/showthread.php?t=530492
Hey! First off Thanks for the reply! I really appreciate someone chiming in to throw some advice my way! But while reading your thread you described the instructions for windows. In this case I have a macbook pro running snow leopard.
I did download the android sdk to my documents folder and I understand that I need to execute some scripts from the terminal on my mac to get things running. But I really dont know what those scripts are or what exactly to do.
I can get into the recovery mode on the MyTouch by holding power and home when powering on. So do I open the console from the recovery screen on the mytouch and then run the scripts on the terminal from my macbook? And which scripts should I run to get the sd card mounted onto my desktop (that is what I'm trying to do). Im not too sure what to do from there either. I want to get the phone back to stock android 1.5 os so that I can root again. My sd card has to be corrupted because it keeps giving me an error saying that it wont mount when I try to do a fix file systems or try anything from that menu. What to do??
What!
can you get in the recovery?
Yeah I can get into cyanogen v1.4 recovery. I'm just stuck from there.
Ok ok If I understand this correctly then you are not briced. you do not have any imag on your phone.
if you do not have anything nadroid recovery on sdcard you must enter a new ROM on the sdcard and flash it
remember full wipe.!
Yes this is what I believe I must do. But I need to either find a way to mount my SD card from the phone while it is in recovery mode (cyanogen v1.4). That's my problem.. I wish there was an easier way to get it mounted onto my mac from the recovery screen. I think I'm just going to go to best buy tomorrow and get a micro sd card reader and maybe another sd card just in case.
Once I have done that though. What files should I put onto the sd card in order to flash it back to original factory android 1.5.
What do you think?
Good idea
I have never used cyanogen v1.4 recovery
I use the recovery-RA-sapphire-v1.5.2H.img and ther you can use USB togle in recovery mode, You must go to the store to buy the adapter that fits on your Mac, I have two adapters for your Mac, you can borrow
Yeah that's the plan for tomorrow. Thanks for the offer man. But I'm in Los Angeles, Ca LOL!! Where are you?
icolinirie said:
Yeah that's the plan for tomorrow. Thanks for the offer man. But I'm in Los Angeles, Ca LOL!! Where are you?
Click to expand...
Click to collapse
Bergen . norway.
http://maps.google.no/maps?f=s&utm_...o-google-gm&utm_medium=ha&utm_term=google map
OMG! WOW! Looks like a beautiful place! LA is a concrete jungle but beautiful in its own respects. Bergen looks like a very comfortable place! I enjoy finding out about these things. Maybe someday I'll visit. I'd definitely love to!
icolinirie said:
OMG! WOW! Looks like a beautiful place! LA is a concrete jungle but beautiful in its own respects. Bergen looks like a very comfortable place! I enjoy finding out about these things. Maybe someday I'll visit. I'd definitely love to!
Click to expand...
Click to collapse
it is sick cold. I'll take one picture out the window
I've been scouring different forums for nearly a month now and can't find a solution that works for my situation. I resisted posting here, hoping to find the info on my own without any luck. I have a handful (6) of these generic MK809III Rockchip 3188 based sticks, with 4.4.2 KitKat. All identical. I have no idea which Chinese manufacturer assembled them. Four of them work perfectly. Two of them have been corrupted by me. I inadvertently wiped out the build.prop files. The files are there, but they are empty. (I know this because the last one I botched, I could see the file in the open editor with no content, as a read-only. The moment I closed the screen... that was it.
Using the "hold the pin in hole, then power up, wait 5 or 10 seconds, then release the pin" method of recovery (sorry, I don't know the proper name) does boot it into recovery mode, but the screen shows this:
Failed to mount /mnt/external_sd (No such device)
Failed to mount /mnt/external_sd (No such device)
Failed to mount /mnt/external_sd (No such device)
one_data_if_exist->can't find databk partition
Formatting /data...
Formatting /cache...
Booting...
--- then, a stuck boot animation.
My problem, is that I cannot connect to these via USB to do anything to them. My system tools are:
Linux Ubuntu 14.04 LTS workstation
RK_Flashtool_1.7
Android Studio
Latest Android tools sdk
Other tools available to me: A Mac (running Yosemite OSx)
Notes:
- Adb drivers, I assume, are correct, because I can access the working stick computer via ADB
- The RKFlashtool will not recognize any of the corrupted units, or show that it is even connected
- Obviously, I cannot set the "Connect to PC" flag without the OS booted
- In a terminal window, adb does not show the usb device as being connected
- I do not have a back up for any of these. I tried, but both Clockwork and TWRP would not recognize the unit to permit a backup. The working units are recognized as: "gxt_dongle_3188".
I really need some advice. I must be overlooking something, I admit to being somewhat new to Android. I wish it were possible to backup one of the working units, and install it on the corrupt units. But no backup app was installed in the boot loader of the corrupted units (that I'm aware of).
Thanks for your time!
Judging from the lack of responses, this problem must have a lot of people as perplexed as I am. I really thought someone here might have an idea.
Hi,
i have this tablet, it's a little bit long story, but i'll try to make it short as possible.
So - as You can see from title, when i try to turn on the tablet, it says this message: "Secure boot: Image LNX checksum fail"
I can't connect it to PC even through USB-USB, i don't have any computer that was connected to it before this, so i don't even have UID. In computer doesn't show anything, i tried a lot of manuals to recover it from that, but almost nothing worked, when i try to put the update.zip on the SD card, it says the same.
I would like to recover that tablet (it's not mine), bit it seems i can't do that. Can anybody help me? There are a lot of threads, although a lot of dead links.
So? Is there still some chance?
you need to run itsmagic on it
search with google to find it and instructions
I found tutorial here on XDA devs, but it seems i need to connect device to computer and be able to communicate with device? Or it's not necessary? In that thread isn't exact tutorial, just "copy itsmagic to /data or /cache" - what does that mean? To ROM zip? Or just create a directory?
Also i need UID to unbrick my device later, but i can't obtain it now, so.. Maybe i could brick my device and not restore?
I'm writing this in android development section because this is only section for both models, i hope this is not a problem.
Also i want to say thanks to sataccount from gsmhosting, he found working map at the end.
This guide is for hard bricked phones, where bootloader is destroyed and there is no any tools which recognize phone.
When you connect phones without bootloader Windows detects them as exynos7420 in other devices in device manager.
All this is achieved using trial/error method and I still don't know real sboot map and where is what in sboot.bin.
What i found till now is that sboot consist from this parts:
1. fwbl1 bl1
2. bl2 bl2
3. el3_mon el3
4. bootloader bootloader
5. tzsw tzsw
I repaired my g925a and have files only for this model, but i will try to explain how to prepair files for any other model.
We have to use same version of bootloader which was previosly in phone, or if you are unsure use latest sboot.bin.
Download tools: http://www.mediafire.com/file/sg5m2ti3k6a63z5/USB_Down_Load_32bit.zip
In folder USB_DownLoad_Tool there is a folder Disk1
Connect phone and hold power button.
Windows will detect exynos7420 device, install Driver:
click manually,
com and lpt ports,
have disk,
point to data1 folder.
Don't run setup from Data1 folder!!!
Now we have to copy
WinDNWApi.dll
WinDNWApi.lib
in:
c:\Program Files\SAMSUNG\Exynos USB Driver\Drivers\
Probably there is no this folder, just create it and copy 2 files.
Don't copy WinDNWApi.dat as it is written in original manual, this file is for older exynos chip and procedure will not work, everything works without this file (it only has maps for 5250 and some other cpu)
Now we have to create boot files.
Download sboot.bin for your device, as i wrote best to find same bootloader which was in device before brick.
In some hex editor create 4 files (i'm using frhed, just click copy, enter offset, new file, paste, save and over again for all four files) with this map (again thanks to sataccount):
Novi1.bin 0..0x1FFF (size 0x2000 or 8192 )
Novi_2.bin 0x2000..0x31FFF (size 0x30000 or 196608)
Novi_3.bin 0x32000..0x3dfff (size 0xC000 or 49152)
Novi4.bin 0x3E000..10EFFF (size 0xD1000 or 856064)
This is all without tzsw. If phone still does not enter to odin mod, make last file from 0x3E000 to the end of the file (18F10F) and try again.
Start multiuploader.exe
Connect phone and hold power button.
Browse and find SH-usb-booting.cfg (in attached file proba folder, that is where you will probably prepare all boot files)
click start and phone will enter odin mode.
Start odin and flash sboot and everything else.
First of all thanx this is a real sharing is caring thing.I'm seeing a way to downgrade bootloader here as tzsw gets separated well this can be done by daring dev who can take risks.
I'm not sure about downgrading.
When i tried to repair my phone, first i tried with 5.1 sboot (eng and normal). It hangs on second file. It checks somethings before start to load real bootloader. Maybe to fill whole device with zeros with dd command (deleting pit can be enough, but also maybe it ignores PIT and read some specific bytes on sda) and then restoring phone as it is just builded in factory. Of course first to make backup of EFS etc...
Even with downgraded sboot, i'm not sure can we use 6.0 and 7.0 roms?
Best way is someone with IDA knowledge to find bytes for unlocking and we can write them to sboot with dd if="something" of =/dev/sdb bs=xx count=xy
At least it is now repairable if it is bricked after that
Good find, thanks.
How did you break the bootloader (sboot) anyway?
Dd if=sboot_from_925f of=/dev/block/sdb
I had engineering boot (kernel) with adb root access. And after that phone is dead.
On 925a sboot is on sdb (just sdb without numbers), cm.bin on sdc. Probably same on all variants.
Hi
I'm not sure I understood the hex files creation step.
Start byte : 0
End byte : 0x1FFF
Size : 8192 for Novi1.bin for example
Right ?
Yes, that's it
Just compare with my files if unsure.
OK Thanks
Congrats for this amazing guide
G928c dont know version inside.
I tried 7.0 but tool hang after novi1 transfer.
with android 6 sboot all 4 files transfer succeed but no download mode
if I do 0x3E000 to the end of the file, tool hang after 1st file.
according to customer 7.0 was inside before brick.
ok I tried different 7.0 which take me to on display usb recovery mode.
but phone not detected by pc after reset by keys now phone completely dead.
no exynos mode, no download mode nothing.
PC not sensing phone anymore.
Did you restore exynos mode?
Try to add tzsw ( novi4 should be from 0x3E000 to the end of sboot.bin).
yes I open phone and re-insert battery. Now exynos mode.
(novi4 should be from 0x3E000 to the end of sboot.bin) give me USB Recovery Mode. but as previous post no detection.
do sboot contain tzsw ?
if so what is address for tzsw ?
tzsw is from 10F000 to the end of file. But you added it and phone loaded when you made novi4 from 0x3E000 to the end of sboot.bin.
I think it is still problem with different sboot version, it must be same as version previously in phone. Try few more sboot bin.
You don't have to pull out battery, just press volume down and power for more then 20 seconds, it is same like you reinsert battery.
I reconfirmed version form client and he said he is sure about 7.0 version.
this variant have only 3 files of 7.0 and I tried all sboot from 3 available versions.
zogu said:
You don't have to pull out battery, just press volume down and power for more then 20 seconds, it is same like you reinsert battery.
Click to expand...
Click to collapse
yes this is the way but in my condition not reset after 30sec and I feel phone heat too. thats why I decide to open phone.
Phone enter download mode and pc does not detect it, it is really strange, like it hangs after entering mode. Maybe is phone (flash memory) broken?
try with jig cable, maybe this can help, it is only idea i have...
zogu said:
Phone enter download mode and pc does not detect it, it is really strange, like it hangs after entering mode. Maybe is phone (flash memory) broken?
try with jig cable, maybe this can help, it is only idea i have...
Click to expand...
Click to collapse
I also think this can be memory issue.
tried all possible ways but no success.
device returned to customer.
anyways thanks for this guide and your quick response.
:good:
I dd over sdb, BOTA0 BOTA1 RECOVERY CACHE and SYSTEM, am i sol on this one? Phone doesnt get detected by pc. Even tried unplugging the battery. For those curious why...I found out theres a partiton flag set on all of those partitions. Its SYSMAGIC X , X being a number. Lowering that number on the system by dd' ing sda18 and rebooting, results in a fw error, binary 3 device 4. Aka phone thinks system installed is lower then what it really is. I know u cant downgrade the bootloader using your method, but if u dump sdb, and edit the sysmagic line in a hex editor, dd it back. It will now be corrupt, I wonder if you can now downgrade to the version we faked. Anyone care to give it a trytry?
how i open multidownloder it giving massage mfc110u.dll missing when i try to install it said opreating sysytem not supported i have window 7 32 bit sp1 but its not working
jhony352 said:
how i open multidownloder it giving massage mfc110u.dll missing when i try to install it said opreating sysytem not supported i have window 7 32 bit sp1 but its not working
Click to expand...
Click to collapse
It worked for me on win 7 32 bit...
Try to reinstall Visual C++ redistributable 2012
https://www.microsoft.com/en-us/download/details.aspx?id=30679
cfg file for s6 sm-g920p
thx its working
Please can you help me from where i can download cfg file for S6 sm-g920p i have sboot.bin file it is in bin format and this file is not open and work in mfc multidownloader
Hey guys,
I build a new pc, first new build in 20 years.
I’m using an ASUs tug gaming x670e plus WiFi motherboard with and 7800x3d cpu.
I’m stuck with the windows installation from usb.
First attempt I used a SanDisk 8gb stick and windows media creator. That’s right load, but looking back that was probably because of bios settings.
second attempt I used a leef 16gb stick. Art the verify stage at 99% it failed.
Third attempt save stick same method created the usb successfully. Had to pay around a lot with bios settings to get the stick seen as bootable. But during the windows installation it reported a file inaccessible or missing. Soo I put the stick in another machine to check but the file in question was there.
Soo I tried again, but now it cannot start up from the usb stick.
I’m in progress of creating an iso usb using the 8gb SanDisk drive, but I think I’m missing something significant.
I’ve attached my bios settings for booting.
If anyone can give some clarification, that would be greatly appreciated! If I can’t die this tonight I’ll bring it in a shop this weekend (just for a windows installation, sigh)
This... happy hunting.
Make a cloned copy of the disk once loaded and configured but before adding data, antivirus or trashware with Acronis to a spare hdd for easy OS restore.
*Redundantly backup critical data, first*
Separate data drives + OS drive are best plus the backup drives that are physically and electronically isolated from each other and the PC.
Managed to get an install.
Had to change a few bios settings (apparently one of the videos I watched for the right bios settings was the exact opposite of what was needed). Agassi used an iso stick.
That seemed to do the trick.
Thanks for the suggestions. It’s much appreciated.
I managed to get things installed. My issues were a combination of bad luck with my usb drives (and how the bootable stick was generated), as well as some poor advice on YouTube that told me the opposite of what was needed.
I also had problems obtaining an activation key legally, but that got resolved as well, so I finally managed to get my pc up and running.
Thanks again for the suggestions!