I'm trying to flash a SM-A300FU, donwloaded heimdall for windows, put the device in download mode, plug it to the computer, fire up zadig, but here's nothing with the samsung or gadget word in the device list when I enable showing all devices.
Are there clear instruction on how to get the device detected by zadig to install the driver ?
Guides linked on the 2017/2018 system i want to flash link to 2010 guides where the heimdall GUI is so old it is not the same.
I just want to flash TWRP to have something familiar to work with.
With Odin, putting the tar file with the recovery image in AP and clicking start doesn't yield any results. (Completed with succeed 0, failled 0)
Magissia said:
I'm trying to flash a SM-A300FU, donwloaded heimdall for windows, put the device in download mode, plug it to the computer, fire up zadig, but here's nothing with the samsung or gadget word in the device list when I enable showing all devices.
Are there clear instruction on how to get the device detected by zadig to install the driver ?
Guides linked on the 2017/2018 system i want to flash link to 2010 guides where the heimdall GUI is so old it is not the same.
I just want to flash TWRP to have something familiar to work with.
With Odin, putting the tar file with the recovery image in AP and clicking start doesn't yield any results. (Completed with succeed 0, failled 0)
Click to expand...
Click to collapse
Did you turn on USB debugging in developer options? If you did and it is still not detecting, it might be a hardware problem.
Related
So I was trying to flash the ICS alpha and it cut short and went to a bootloop and would not go into recovery via button presses or adb commands.
Here's what I did...
- Put phone into download only mode and with s1_odin_20100512 pit and T959UVJFD.tar tried to flash with Odin. It repeatedly kept getting stuck on different parts of the flash, so I gave up and tried Heimdall.
- Now with Heimdall, I use the same packages and get a firmware.xml error. For the life of my I can't find a Heimdall package for Vibrant back to stock, nor do I even know how any of that works...
Would really appreciate any help I can get trying to get this phone back! It gets to download mode no problem each time... is there hope?
If I were you I would try to:
1. Download any CM7 ROM and put it on external SD card (I hope you have one, or perhaps you have already on your phone any ROM that can be installed via recovery, but doesn't require stock ROM)
2. flash kernel with CWM via heimdall
3. to be sure wipe system and cache
4. Install respective ROM via recovery
It helped me many times after bad flash. Perhaps after that you could odin it to stock without problems.
amburator said:
If I were you I would try to:
1. Download any CM7 ROM and put it on external SD card (I hope you have one, or perhaps you have already on your phone any ROM that can be installed via recovery, but doesn't require stock ROM)
2. flash kernel with CWM via heimdall
3. to be sure wipe system and cache
4. Install respective ROM via recovery
It helped me many times after bad flash. Perhaps after that you could odin it to stock without problems.
Click to expand...
Click to collapse
could you be super duper helpful and provide me a download for flashing kernel with CWM via heimdall? no luck so far
I was using this: http://goo.gl/g9rc9
from this thread: http://forum.xda-developers.com/showthread.php?t=967861&highlight=overstock
You'll have to pull out file 'zImage' from zip file.
Edit: what I meant is you'll have to load zImage to heimdall. It's in the first folder in zip file. Do not put whole folder in heimdall, only singe file: zImage.
amburator said:
I was using this: http://goo.gl/g9rc9
from this thread: http://forum.xda-developers.com/showthread.php?t=967861&highlight=overstock
You'll have to pull out file 'zImage' from zip file.
Edit: what I meant is you'll have to load zImage to heimdall. It's in the first folder in zip file. Do not put whole folder in heimdall, only singe file: zImage.
Click to expand...
Click to collapse
I'm using Heimdall 1.3. I've extracted the zImage and packed it into a .tar and loaded it into Heimdall but I get a firmware.xml missing error... any ideas?
Thanks so much for your help.
EDIT: Nevermind, figured out how to do it. Now I'm getting a ERROR: Failed to received response. Searching google tells me I should install libusb drivers, gonna try that.
Have you used heimdall before? If you haven't you have to do this first:
Put your USB cable in another USB slot in your PC, after that follow instructions from heimdall's readme file:
Driver Installation Instructions:
1. Put your Samsung Galaxy S into download mode and plug it in.
2. Run zadig.exe included in the Drivers subdirectory.
3. From the menu chose Options -> List All Devices.
4. From the USB Device list chose "Samsung USB Composite DEvice".
5. Press "Install Driver", click "Yes" to the prompt and if you receive
a message about being unable to verify the publisher of the driver
click "Install this driver software anyway".
6. Done
Now the kernel. You must not put zImage into any package. The file goes into heimdall as it is. When you open heimdall, press "browse" right to the Kernel (zImage) field and locate "zImage". After that press start.
That's the procedure that helped me to install CM7 and ICS ROMs without having to go back to stock. I hope it will help you.
One more note: when you use ODIN put the usb cable in the first USB slot, if you want to use heimdall, use the second USB slot.
amburator said:
Have you used heimdall before? If you haven't you have to do this first:
Put your USB cable in another USB slot in your PC, after that follow instructions from heimdall's readme file:
Driver Installation Instructions:
1. Put your Samsung Galaxy S into download mode and plug it in.
2. Run zadig.exe included in the Drivers subdirectory.
3. From the menu chose Options -> List All Devices.
4. From the USB Device list chose "Samsung USB Composite DEvice".
5. Press "Install Driver", click "Yes" to the prompt and if you receive
a message about being unable to verify the publisher of the driver
click "Install this driver software anyway".
6. Done
Now the kernel. You must not put zImage into any package. The file goes into heimdall as it is. When you open heimdall, press "browse" right to the Kernel (zImage) field and locate "zImage". After that press start.
That's the procedure that helped me to install CM7 and ICS ROMs without having to go back to stock. I hope it will help you.
One more note: when you use ODIN put the usb cable in the first USB slot, if you want to use heimdall, use the second USB slot.
Click to expand...
Click to collapse
First off, thank you so much for your help. This is my first time using Heimdall, just got done finishing the README.
Here's where I'm at... I figured out what you just said a few minutes before you sent it, haha.
Oh, important side note.. I'm on a MAC. I think I'm experiencing a driver issue right now, given this:
-------------------------------------------------------
Initialising connection...
Detecting device...
Manufacturer: "SAMSUNG"
Product: "Gadget Serial"
length: 18
device class: 2
S/N: 0
VIDID: 04E8:6601
bcdDevice: 021B
iMan:iProd:iSer: 1:2:0
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
ERROR: libusb error 1032320 whilst receiving packet.
ERROR: Failed to confirm end of PIT file transfer!
PIT upload failed!
Ending session...
Rebooting device...
-------------------------------------------------------
Thoughts? I reinstalled Heimdall and went to customize and tried just the libusb package. I'm going to restart and try diff USB port now.
Fuuuuuck yeah, I got it. Thanks SO much for your help. How can I ever repay you?
EDIT: To be helpful to any googlers in the future - it was fixed by reinstalling libusb from the Heimdall 1.3 installer, restarting, and repeatedly trying alternate usb ports and putting it into download mode over and over again.
Sorry, I presumed you're on windows pc. I have no experience with mac.
What I know for sure, on windows heimdall won't work until you install those drivers.
Good luck anyway!
Edit: now I've seen your new post. Good news regarding drivers.
Now the kernel and ROM
Ask if you got stuck somewhere.
amburator said:
Sorry, I presumed you're on windows pc. I have no experience with mac.
What I know for sure, on windows heimdall won't work until you install those drivers.
Good luck anyway!
Edit: now I've seen your new post. Good news regarding drivers.
Now the kernel and ROM
Ask if you got stuck somewhere.
Click to expand...
Click to collapse
I found a package on the forms but was getting a firmware.xml error. Manually downloaded/created PIT file from phone, then extracted package, and loaded up each component (modem, param, kernel, etc) indivudally and flashed without a hitch. Huzzah!
Allright!
Congrats!
Hello,
I just got the OTA message for 4.4 and tried to install it but I got a bootloop. After clearing the cache and performing a factory reset in TWRP (which got installed through Nexus Toolkit) it still didn't work. Someone told me to perform a complete format through TWRP which I did (hindsight, I know) and now TWRP says I have no OS installed, adb won't see my device (I have the drivers installed) and when I go into the bootloader (which says FASTBOOT MODE) fastboot still won't recognize the device (nothing shows up on my PC either but that can be normal).
I'm at my wit's end here, is there anyone who can help me?
You need to realize that if you want to install OTA, you need to use stock recovery. Even though it is possible to flash through TWRP, it can still run into problems. Especially when you made root modifications to your device.
You don't have to do a full wipe for everything. There is a method to flash factory firmware without wiping data (link in my signature). After that if it still don't boot due to existing data, boot into a custom recovery and do a factory reset without wiping the internal storage.
But since you have custom recovery already, just go into the Development section, find a stock KitKat rom, download it and sideload it using TWRP (which is enabled it in the Advance menu).
eksasol said:
You need to realize that if you want to install OTA, you need to use stock recovery. Even though it is possible to flash through TWRP, it can still run into problems. Especially when you made root modifications to your device.
You don't have to do a full wipe for everything. There is a method to flash factory firmware without wiping data (link in my signature).
But since you have custom recovery already, just go into the Development section, find a stock KitKat rom, download it and sideload it using TWRP (which is enabled it in the Advance menu).
Click to expand...
Click to collapse
Yes I've tried that but I don't know how to sideload it. adb doesn't see my device, fastboot doesn't either and windows doesn't recognize the device (although I have the adb naked drivers installed).
fverswijver said:
Yes I've tried that but I don't know how to sideload it. adb doesn't see my device, fastboot doesn't either and windows doesn't recognize the device (although I have the adb naked drivers installed).
Click to expand...
Click to collapse
If it is connected adb should see your device while in TWRP. Fastboot only work in fastboot mode (bootloader screen), not in recoveries. If you have the UND installed then they both should work, if not it wasn't installed correctly. If you are using Windows 8 you need to disable driver signature before you can install UND (search google for that).
You could also make a bootable Ubuntu flashdrive, and use the ADB/Fastboot for Ubuntu link in my signature to install them.
eksasol said:
If it is connected adb should see your device while in TWRP. Fastboot only work in fastboot mode (bootloader screen)
Click to expand...
Click to collapse
I tried both. ADB devices gives me an empty line and fastboot devices (when in bootloader screen) gives me nothing at all. I've tested 2 different computers (both windows 7 x64) and it still won't detect it. When in TWRP windows tries to detect my device but it says "Unknown Device" and gives the yellow triangle.
fverswijver said:
Yes I've tried that but I don't know how to sideload it. adb doesn't see my device, fastboot doesn't either and windows doesn't recognize the device (although I have the adb naked drivers installed).
Click to expand...
Click to collapse
You might have to point the drivers to your phone. If you go into device manager, see if your Nexus 4 has an error. If it does, right click it, and then update the driver. Do a manual install, and point it to the .ini file for the driver
fverswijver said:
I tried both. ADB devices gives me an empty line and fastboot devices (when in bootloader screen) gives me nothing at all. I've tested 2 different computers (both windows 7 x64) and it still won't detect it. When in TWRP windows tries to detect my device but it says "Unknown Device" and gives the yellow triangle.
Click to expand...
Click to collapse
Fix your drivers, uninstall them and select the checkbox to delete the driver files, search Google on how to disable driver signature and try reinstalling the driver again.
or
Make a bootable Ubuntu flashdrive, and use the ADB/Fastboot for Ubuntu link in my signature to install them.
eksasol said:
Make a bootable Ubuntu flashdrive, and use the ADB/Fastboot for Ubuntu link in my signature to install them.
Click to expand...
Click to collapse
I did this and still the same, adb gives an empty list and fastboot gives nothing.
fverswijver said:
I did this and still the same, adb gives an empty list and fastboot gives nothing.
Click to expand...
Click to collapse
Try using a different cable and on different computers.
eksasol said:
Try using a different cable and on different computers.
Click to expand...
Click to collapse
I've tried 3 different computers, 2 different OSes and 3 different cables. Nothing seems to work. I'm really starting to panic now.
fverswijver said:
I've tried 3 different computers, 2 different OSes and 3 different cables. Nothing seems to work. I'm really starting to panic now.
Click to expand...
Click to collapse
Just to clarify, see attachment for the correct name of the device if UND is installed correctly.
If you tried it with Ubuntu, make sure you do the 1st step from here also:
http://bernaerts.dyndns.org/linux/74-ubuntu/245-ubuntu-precise-install-android-sdk
Same here
i installed the ota update normally with twrp installed everything went fine but im kind of disappointed in this update:/
eksasol said:
Just to clarify, see attachment for the correct name of the device if UND is installed correctly.
Click to expand...
Click to collapse
These are my findings:
Ubuntu:
- Bootloader (fastboot)
-- running lsusb in Ubuntu shows no device
- TWRP (adb)
-- running lsusb shows no device
Windows 7 (3 different computers)
- Bootloader (fastboot)
-- Windows gives the following popup, no device listed in Device Manager
- TWRP (adb)
-- Windows gives the same popup as on fastboot and this appears in the Device Manager:
fverswijver said:
These are my findings:
Ubuntu:
- Bootloader (fastboot)
-- running lsusb in Ubuntu shows no device
- TWRP (adb)
-- running lsusb shows no device
Windows 7 (3 different computers)
- Bootloader (fastboot)
-- Windows gives the following popup, no device listed in Device Manager
- TWRP (adb)
-- Windows gives the same popup as on fastboot and this appears in the Device Manager:
Click to expand...
Click to collapse
Is file transfering working atleast? If it is, then it's a software problem. If it isn't, then it could be a hardware problem, you can try replacing the USB charging board for the phone. Also some roms with corrupt files can cause this issues, so try a different roms if you haven't.
File transfer used to work but atm I'm unable to even connect it to a computer so I can't actually transfer any files. If I could I would flash a rom but no files = no flashing.
fverswijver said:
File transfer used to work but atm I'm unable to even connect it to a computer so I can't actually transfer any files. If I could I would flash a rom but no files = no flashing.
Click to expand...
Click to collapse
Get one of these: http://www.ebay.com/sch/i.html?_nkw=nexus+4+usb+charging+port+replacement&_sacat=0
If it don't work, then use the phone as a door stopper.
hey guys, I'm having the same problem here but with a Nexus 5 now.
Its been over a month and I've kind of gave up over the situation.
I couldn't resist to write a comment on the thread, since it appears to be the same problem as mine.
long story short, I decided to order an USB charging port to replace the one on the phone (as my last attempt).
Otherwise I will consider using the device as a door stopper.
Do not despair! Check this out: http://highonandroid.com/android-ro...r-android-in-a-bootloop-with-no-os-using-adb/
http://highonandroid.com/android-roms/how-to-copy-files-over-to-your-android-in-a-bootloop-with-no-os-using-adb/
i installed nokia xl rom into my device un fortunately i wipe the os and later i copy a rom file into my sd card and tried to flash tjat but it showing unable to open the zip. iam stuck with my company logo on the screen. twrp cannot open the zip and flash the rom. please help me in this issue.
thanks in advance
My phone has no OS. Factory reset is unavailable to my knowledge (attempted volume up and power).
I can go into fastboot and TWRP, but I can't seem to install the stock OS nor Lineage OS. In fastbootmode, I see the following
Product name - AILSA_II
Variant - MTP eMMC
Bootloader version -
Baseband Version -
Serial Number 9e28c2da
Secure Boot - enabled
Device State - unlocked
Click to expand...
Click to collapse
I cannot use ADB commands. My phone isn't listed under ADB devices. EDL does not work. However in Fastboot mode, MiFlash recognizes a device 9e28c2da. Whenever I try to flash a full EDL however, miflash brings up errors saying it cannot find script and it cannot find file.
When attempting to install in TWRP, I get the respective errors "Invalid zip file format!" for "A2017U_B19-NOUGAT_FULL-EDL.zip" when I try to install the stock. When I try to install Lineage, I get "E3004L This package is for device: ailsa_ii,axon7; this device is ."
I am able to successful install A7LOSv1_UniversalBootStack.zip as well as the UniversalBootstack by DrakenFX. I then install OreoModem.zip after that, but the phone won't let me install any OS afterwards.
Am I trying to install the wrong arrangement of files? What can I do to get an OS back on my phone?
Firstly it sounds like the drivers need an update.
Try updating the USB drivers and try Zadig drivers as well.
Your PC/laptop should see your phone as ...
"Qualcomm HS-USB QDLoader 9008"
In the device manager on Windows. If you are using Miflash it should see it as Com 4 or similar.
Make sure you have the correct Edl package for your phone eg: A2017G, A2017U or A2017.
Extract the Edl package using WinZip or Winrar and take note of the folder name and location.
Boot your phone into Edl mode, via button, adb command or using the Edl tool by @djkuz
Open Miflash tap refresh, if it sees com4 or similar you are good to go.
Tap the browse button and pick the Edl package location on your PC/laptop and then tap flash.
The flash will take a few minutes and when done you will get a green flash success.
Unplug your phone and press and hold the power button till it boots.
Hope this helps
If you get stuck,
I have an Edl help page here >
https://forum.xda-developers.com/axon-7/help/bad-flash-help-page-axon-7-t3839700
There are many others on XDA too
Hi Guys
So my current goal is to root my galaxy S10+ (SM-G975F) running exynos with android 11. I've seen many methods that are supposed to work for android 11, some more complicated than the others.
The method I chose to stick with, is to enter bootloader through adb using cmd on my computer and to flash twrp that way. (Bootloader is unlocked already)
After that I should be able to install magisk via twrp to complete the root access.
My inital thought was to flash twrp via odin, because odin did recognize my phone after entering bootloader. The problem was that after flashing twrp with odin and performing vol down + power then bixby + vol up + power which normally makes you enter twrp, I got stuck in a bootloop. After that I had to flash the stock ROM via Odin to "repair" my phone.
From what I've read this is due to the vbmeta protection mechanism, that you need to deactivate to avoid bootlooping.
So I heard that you can extract the boot.img file from the official firmware and edit the file with HxD Binary editor to replace a bitcode's value with a series of 0's. Unfortunately I couldn't find that specific code in boot.img.
So the remaining option was to manually flash vbmeta.img and to disable verity verification via cmd.
This is where the big problem lies, my PC does not recognize the device as soon as I enter Download mode. I tried every possible fix I could find online, they all revolve around installing certain drivers and applying them to the device in the device manager. Apparently the device needs to appear in the device manager under "other devices" with a yellow triangle then you can manually select a driver to install. Unfortunately as soon as I enter Download mode (Via cmd command or manually) my device totally disappears from the pc. Only Odin still recognises it somehow.
I installed official android device drivers, specific drivers for bootloader etc.
Every online guide about solving this problem needs you to locate the device and to apply certain drivers to it, but nothing appears for me.
I hope somebody can help me
Format data?
What your twrp version ? your twrp version must be version support 11.
You cant flash Magisk via TWRP. It doesn't work, Install the magisk App
Wrong place to ask this stuff
I'm trying to flash Magisk custom boot.img using fastboot but it will never detect the device, tried everything in the first page of Google with different searches, nothing works. Tried downloading Samsung developer drivers from here, tried this tool while in fastboot and then while the device is booted normally, tried this 15 second ADB installer tool to install Google adb and fastboot drivers, tried Kies, tried uninstalling all the relevant devices and using the Windows default ones, tried another laptop, another USB cable, another USB port, many videos and articles but still nothing. When I run fastboot devices, it doesn't show me anything, adb devices works just fine and shows the device when booted normally, of course I run fastboot devices when I'm in fastload but nothing shows up.
My device is SM-N910C treltexx EGY EXynos5433, tried all this mainly on Windows 11 but also tried with the Samsung developer drivers on a Windows 10 device.
I have WSA installed with hyper-V and Virtual Machine Platform installed on 11, could this be a problem? Also I noticed that when I run adb reboot fastboot, the device just restarts, the same when I choose Run fastboot in recovery mode, the only way for me to get to fastboot is pressing power +home +volume down. Also Odin recognizes the device in fastboot just fine.
So how to solve this? Or is there a method to flash Magisk's boot.img without fastboot? Or an alternative that does its job?
With further research I managed to do it with Odin. Took the patched file and renamed it to boot.img, used 7z to make a tar archive out of it. Loaded it in Odin as an AP and it worked! I have been using Magisk 24.3 all along because there is an issue with 25.0 that makes it stuck on the logo screen on rooted Galaxy Note 4 devices.
Still, is there a way to use fastboot on this device?
samsung galaxy note 4 (snapdragon and exynos) won't have fastboot mode, sorry.