So I've tried pretty much all "compatible" GSI images for this phone (Samsung J2 Core SM-J260y/ds, Android Go 8.1) which according to the treble info app is an arm32-binder64 a-only device, but always fails when it comes to flashing the system.img
I followed this tutorial. I somehow managed to "install" A10 vanilla, but it won't boot, somehow stuck at a black screen.
this device has no TWRP that's why I'm resorting to using ODIN.
Any help or input would be great.
Thanks in advance!
Try Heimdall
just install heimdall on your machine and open cmd (if your using windows) or a terminal (Linux/Mac)
And Type
heimdall flash --SYSTEM "YOUR IMAGE.IMG"
Sinshro said:
Try Heimdall
just install heimdall on your machine and open cmd (if your using windows) or a terminal (Linux/Mac)
And Type
heimdall flash --SYSTEM "YOUR IMAGE.IMG"
Click to expand...
Click to collapse
Yeah, I tried setting up Heimdall and I can't seem to get past the installing the drives stage, it doesn't detect the "Samsung composite device".
apbucaneg said:
Yeah, I tried setting up Heimdall and I can't seem to get past the installing the drives stage, it doesn't detect the "Samsung composite device".
Click to expand...
Click to collapse
oh yeah just install ubuntu windows has some driver issues
Sinshro said:
oh yeah just install ubuntu windows has some driver issues
Click to expand...
Click to collapse
can't install ubuntu, it's a company laptop, thanks for your tips though, much appreciated
apbucaneg said:
can't install ubuntu, it's a company laptop, thanks for your tips though, much appreciated
Click to expand...
Click to collapse
You can use a virtual machine and connect the phone to it
Sinshro said:
You can use a virtual machine and connect the phone to it
Click to expand...
Click to collapse
I would install virtual machine if I have admin rights on my company laptop
apbucaneg said:
I would install virtual machine if I have admin rights on my company laptop
Click to expand...
Click to collapse
oh okay then your better off using your friend's laptop or somethin
apbucaneg said:
So I've tried pretty much all "compatible" GSI images for this phone (Samsung J2 Core SM-J260y/ds, Android Go 8.1) which according to the treble info app is an arm32-binder64 a-only device, but always fails when it comes to flashing the system.img
I followed this tutorial. I somehow managed to "install" A10 vanilla, but it won't boot, somehow stuck at a black screen.
this device has no TWRP that's why I'm resorting to using ODIN.
Any help or input would be great.
Thanks in advance!
Click to expand...
Click to collapse
are you using a modded version of Odin ?
3mel said:
are you using a modded version of Odin ?
Click to expand...
Click to collapse
No.
apbucaneg said:
No.
Click to expand...
Click to collapse
if there's a link to a version of Odin in the guide thread use that Odin instead.
Related
I DO NOT want to use my computer with any command stuff.
My bootloader is unlocked and i have stock recovery.
I tried with all the driver stuff very very confusing. My phone is not even showing up anymore on my computer.
(TOO complicated)
Why can't i just do the same thing with other Samsung Phones-Drag root into system storage then just flash.Easy.
+Maguro+
My recovery shows an android with a red triangle...
no.
Zepius said:
no.
Click to expand...
Click to collapse
AWWW
why did they make it sooo hard
In your case I would say just go get a toolkit and use that. There is no way, where you are at, to root your device. You NEED to flash a custom recovery which cannot be done on anything other than a computer to root your device.
Go here: http://forum.xda-developers.com/showthread.php?t=1614827
The toolkit includes device drivers and will do basically anything you need it to do.
miketoasty said:
In your case I would say just go get a toolkit and use that. There is no way, where you are at, to root your device. You NEED to flash a custom recovery which cannot be done on anything other than a computer to root your device.
Go here: http://forum.xda-developers.com/showthread.php?t=1614827
The toolkit includes device drivers and will do basically anything you need it to do.
Click to expand...
Click to collapse
I tried- i did unlocked the bootloader yesterday(took me ages)
then i tried today to install recovery then it says "waiting for device"
CAN i use odin to do it?
fayosi said:
AWWW
why did they make it sooo hard
Click to expand...
Click to collapse
It's really not that hard, actually only a couple commands and pushing some buttons on your phone.
*Plug In Phone*
adb reboot bootloader
fastboot oem unlock
*Volume up* *Power Button*
adb reboot bootloader
fastboot flash recovery Recovery.img
*Volume Down* *Volume Down* *Power Button*
Install Zip from SD Card - SuperSU.zip.
Reboot.
Done. Takes at most 10 minutes.
fayosi said:
CAN i use odin to do it?
Click to expand...
Click to collapse
Odin isn't used on Nexus devices (as far as I know.) They use the Android standard, which is fastboot.
fastboot oem unlock
That's the command to unlock your bootloader. Be aware, it'll wipe your phone (security measure.)
spencer88 said:
Odin isn't used on Nexus devices (as far as I know.) They use the Android standard, which is fastboot.
fastboot oem unlock
That's the command to unlock your bootloader. Be aware, it'll wipe your phone (security measure.)
Click to expand...
Click to collapse
ODIN actually is built into the device, but I think is actually more complicated than just using fastboot.
-waiting for device-
fayosi said:
-waiting for device-
Click to expand...
Click to collapse
Sounds like you don't have the Fastboot drivers set up.
http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735
PM me your email address and I'll help you out!
May the problem be because my laptop is running windows 8.
3rdstring said:
Sounds like you don't have the Fastboot drivers set up.
http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735
Click to expand...
Click to collapse
Not that again... It took me like 3hrs to find all the drivers and infromation to unlock my bootloader.Its soo hard the tool kit does not really work for me.
EDIT: um actually that guide you linked seems to be different with screen shot help, im going to try that one instead. THANKS
fayosi said:
Not that again... It took me like 3hrs to find all the drivers and infromation to unlock my bootloader.Its soo hard the tool kit does not really work for me.
EDIT: um actually that guide you linked seems to be different with screen shot help, im going to try that one instead. THANKS
Click to expand...
Click to collapse
Not sure that guide will help you with Windows 8 though... I guess it doesn't hurt to try.
Twrp or clockwork????
efrant said:
Not sure that guide will help you with Windows 8 though... I guess it doesn't hurt to try.
Click to expand...
Click to collapse
Do I Temporarily flash CWM then root it or
have it permanently installed first??
fayosi said:
Do I Temporarily flash CWM then root it or
have it permanently installed first??
Click to expand...
Click to collapse
If that's all you want to do is root & leave your device on stock you can just temporarily boot a custom recovery & flash the super user.
Nooo
3rdstring said:
If that's all you want to do is root & leave your device on stock you can just temporarily boot a custom recovery & flash the super user.
Click to expand...
Click to collapse
I'd thought i had done it but then it said the dreaded waiting for device:crying::crying::crying::crying::crying::
fayosi said:
I'd thought i had done it but then it said the dreaded waiting for device:crying::crying::crying::crying::crying::
Click to expand...
Click to collapse
I didn't think "NASA Leading Engineers" gave up so easy
Hi guys. I've got a problem..... I tried flashing CWM 6.0.3.4 to my Wonder, I open Odin, I choose files (Ancora.ops and CWM), Odin recognises my phone, but when I press "Start", the program gets stuck at "<1> setup connection..."
I tried changing USB cable, port, even Odin (I tried 4.43 - 4.38 and 3.98), but nothing has changed..... I am running Windows XP, and I have installed only Samsung USB Drivers, without Kies. But, as said before, Odin recognises my Wonder..... even tried on another XP computer, and have the same result...... please help me
ayesse said:
Hi guys. I've got a problem..... I tried flashing CWM 6.0.3.4 to my Wonder, I open Odin, I choose files (Ancora.ops and CWM), Odin recognises my phone, but when I press "Start", the program gets stuck at "<1> setup connection..."
I tried changing USB cable, port, even Odin (I tried 4.43 - 4.38 and 3.98), but nothing has changed..... I am running Windows XP, and I have installed only Samsung USB Drivers, without Kies. But, as said before, Odin recognises my Wonder..... even tried on another XP computer, and have the same result...... please help me
Click to expand...
Click to collapse
guide for flashing via odin. follow it carefully/ correctly Link
another way is via terminal emulator. dl link and guide
dec0der said:
guide for flashing via odin. follow it carefully/ correctly Link
another way is via terminal emulator. dl link and guide
Click to expand...
Click to collapse
I followed the Odin guide step by step, but I can't solve the problem..... BTW, my Wonder is unrooted, so I can't install CWM via terminal
ayesse said:
I followed the Odin guide step by step, but I can't solve the problem..... BTW, my Wonder is unrooted, so I can't install CWM via terminal
Click to expand...
Click to collapse
are you using stock or custom rom? can you provide a screenshot?
dec0der said:
are you using stock or custom rom? can you provide a screenshot?
Click to expand...
Click to collapse
Lol bro he's unrooted and trying to flash cwm. Don't you think it's pretty obvious he's using stock rom?
Bro, you have to root it first, only then you should flash CWM. Because you can't root using cwm. Anyway, root first then flash via terminal emulator. Should work.
Sent from my MB860 using xda app-developers app
iDelta said:
Lol bro he's unrooted and trying to flash cwm. Don't you think it's pretty obvious he's using stock rom?
Bro, you have to root it first, only then you should flash CWM. Because you can't root using cwm. Anyway, root first then flash via terminal emulator. Should work.
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
OOOOOH F*CKKKKK! LAWLZ! honestly, i never thought of that, my bad
oh sorry guys, I haven't told you.... I want to install CWM because I wanna install Cyanogenmod 10 to get rid of this ****ty stock rom
ayesse said:
oh sorry guys, I haven't told you.... I want to install CWM because I wanna install Cyanogenmod 10 to get rid of this ****ty stock rom
Click to expand...
Click to collapse
Pull out the battery for a few seconds and try to flash via odin again?
ayesse said:
oh sorry guys, I haven't told you.... I want to install CWM because I wanna install Cyanogenmod 10 to get rid of this ****ty stock rom
Click to expand...
Click to collapse
*sigh!
just follow this steps:
1. root ur phone- guide HERE
2. install cwm- guide HERE
3. install desired custom rom (pristine)- guide (HERE)
Note:
*Don't forget to check md5 checksum of downloaded files b4 flashing.
*Follow instructions carefully/ correctly.
solved flashing on another Win7 laptop.... thanks for your replies
how can i boot a kernel from ram, or otherwise run a kernel without flashing it. I need to integrate some drivers into the kernel but i am petrified of bricking my phone.
Yes, yes, Odin or heimdall for flashing, I get Odin covers fastboot flash, but is there a fastboot boot function?
tooandrew said:
how can i boot a kernel from ram, or otherwise run a kernel without flashing it. I need to integrate some drivers into the kernel but i am petrified of bricking my phone.
Yes, yes, Odin or heimdall for flashing, I get Odin covers fastboot flash, but is there a fastboot boot function?
Click to expand...
Click to collapse
Kdevelop + linux plugins
xxSTARBUCKSxx said:
Kdevelop + linux plugins
Click to expand...
Click to collapse
Thank you, I'll Google that.
Edit: it's not clear what I'm supposed to do with this software in order to fastboot a kernel
xxSTARBUCKSxx said:
Kdevelop + linux plugins
Click to expand...
Click to collapse
A bit more info would be quite helpful and much
Appreciated. Thanks for your help.
tooandrew said:
A bit more info would be quite helpful and much
Appreciated. Thanks for your help.
Click to expand...
Click to collapse
I apologize for the lack of info. Id first read up on fastboot and even see if the command lines even exist for what you want to do (searching any and all pertaining to kernels) That will tell you if you can proceed in the direction you want to go whether it be from positive or negative results in searching your desired criteria.
xxSTARBUCKSxx said:
I apologize for the lack of info. Id first read up on fastboot and even see if the command lines even exist for what you want to do (searching any and all pertaining to kernels) That will tell you if you can proceed in the direction you want to go whether it be from positive or negative results in searching your desired criteria.
Click to expand...
Click to collapse
Fastboot commands work just fine for what I need to do, but from what I understand fastboot is not integrated into samsung's download mode. Fastboot boot is the command I need, is there at least an emulator for the note 4 that I can use to test a kernel without flashing?
tooandrew said:
Fastboot commands work just fine for what I need to do, but from what I understand fastboot is not integrated into samsung's download mode. Fastboot boot is the command I need, is there at least an emulator for the note 4 that I can use to test a kernel without flashing?
Click to expand...
Click to collapse
Can you not test kernels on Android Emulator?
xxSTARBUCKSxx said:
Can you not test kernels on Android Emulator?
Click to expand...
Click to collapse
from what I've been able to figure out, no. You mean the one built into android studio?
tooandrew said:
from what I've been able to figure out, no. You mean the one built into android studio?
Click to expand...
Click to collapse
http://forum.xda-developers.com/not...nt/kernel-tutorial-custom-kernel-101-t2938813
Ok was messing about with viper without doing a backup...
Phone is now messed up, i can get to twrp but can not sideload (its not working) how else can i get a file to the phone?
I did a factory reset but it will not work due to the viper install error.
Will they fix if its been rooted?
So gutted loved the phone so far
lost recovery now asking for password.
Phone is a brick
Try to download this here: Link
And then flash factory image.
I did try that tool but was crashing on my pc windows 10.
Any tips m8
adb push can work (in fastboot) ?
All sorted now thanks mate
Daredevil76 said:
adb push can work (in fastboot) ?
Click to expand...
Click to collapse
TheLoverMan said:
All sorted now thanks mate
Click to expand...
Click to collapse
Can you post how you did it please?
I've tried sideloading but it gets stuck.
Push seems to work but I don't see the file afterwards...
http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
Method 2 is the secure solution.
Best Regards.
Wynztech said:
http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
Method 2 is the secure solution.
Best Regards.
Click to expand...
Click to collapse
I'm actually on linux.
Is it safe to assume it performs a fastboot flash? (and try that manually?)
edit: I'm thinking of flashing the stock room.
phinicota said:
I'm actually on linux.
Is it safe to assume it performs a fastboot flash? (and try that manually?)
Click to expand...
Click to collapse
Read the tuto dude. it works for me when i was bricked my phone. Need Windows. Remember to try method 2, it is all in one, the program makes all work.
Best Regards.
I'm attempting to re-flash the Samsung Galaxy S9 (SM-G960F) partitions from the official firmware.
Most partitions work, but the “VENDOR” partition fails part-way through.
Heimdall reports “ERROR: Failed to send file part packet!” and the session aborts.
According to the device this is because “SYSTEM REV. CHECK FAIL. DEVICE:13, BINARY:12 (VENDOR)”
In this state the device refuses to start at all; powering on the device leads instantly to a graphical message:
> An error has occurred while updating the device software.
> Use the Emergency recovery function in the Smart Switch PC software.
I don't use Windows at all, so don't have that software. How can I use Heimdall to flash the full Vendor partition without error?
herbicide said:
I'm attempting to re-flash the Samsung Galaxy S9 (SM-G960F) partitions from the official firmware.
Most partitions work, but the “VENDOR” partition fails part-way through.
Heimdall reports “ERROR: Failed to send file part packet!” and the session aborts.
According to the device this is because “SYSTEM REV. CHECK FAIL. DEVICE:13, BINARY:12 (VENDOR)”
In this state the device refuses to start at all; powering on the device leads instantly to a graphical message:
> An error has occurred while updating the device software.
> Use the Emergency recovery function in the Smart Switch PC software.
I don't use Windows at all, so don't have that software. How can I use Heimdall to flash the full Vendor partition without error?
Click to expand...
Click to collapse
Sorry ... I would get a Windows PC, install Samsung drivers and Odin, then flash stock firmware files (if really needed with pit file for re-partitioning) to the phone.
Just for repairing the device. Then you can give the windows PC back to your friend.
Thanks for the reply:
It_ler said:
[…] flash stock firmware files (if really needed with pit file for re-partitioning) to the phone.
Click to expand...
Click to collapse
When I tried that earlier, the device aborted the flash process and displayed the message
SYSTEM REV. CHECK FAIL. DEVICE:13, BINARY:12 (VENDOR)
Click to expand...
Click to collapse
I think Odin running on Windows will simply do the same thing; what would be different if I tried again?
herbicide said:
Thanks for the reply:
When I tried that earlier, the device aborted the flash process and displayed the message
I think Odin running on Windows will simply do the same thing; what would be different if I tried again?
Click to expand...
Click to collapse
IDK about Heimdall, but there are patched versions of Odin available with which you can skip some file version validations.
And with Odin you can explicitly flash a pit file to re-partition the internal storage.
It_ler said:
[…] there are patched versions of Odin available with which you can skip some file version validations.
Click to expand...
Click to collapse
Oh, that sounds useful. Where can I find that patched Odin?
herbicide said:
Oh, that sounds useful. Where can I find that patched Odin?
Click to expand...
Click to collapse
There are several versions available, such as here:
Patched Odin 3.13.1
For those looking for a modified, modded, or patched odin that is a newer build than all the fake and renamed prince comsy 3.12.3 versions floating around. I patch recent Odin versions to offer similar functionality to the princecomsy; in that...
forum.xda-developers.com
Be careful to flash only files that are compatible with your exact device model.
It_ler said:
Be careful to flash only files that are compatible with your exact device model.
Click to expand...
Click to collapse
One thing I wonder is whether I already attempted to flash the wrong firmware.
If that's what I did, have I actually made the problem worse? Or will flashing the correct firmware work anyway?
SYSTEM REV. CHECK FAIL. DEVICE:13, BINARY:12 (VENDOR)
Click to expand...
Click to collapse
this means, the firmware you'll install is to old.
you can't downgrade your device.
search for frija or samfirm reborn (both windows) here in xda to get an actually Firmware, use binary nature.
MikeT. said:
this means, the firmware you'll install is to old.
you can't downgrade your device.
Click to expand...
Click to collapse
Ah, that makes sense. And if I simply flash a newer firmware now, the earlier failure does not matter. Right?
MikeT. said:
search for frija or samfirm reborn (both windows) here in xda to get an actually Firmware, use binary nature.
Click to expand...
Click to collapse
I have found a firmware that appears to match, at https://samfw.com/firmware/SM-G960F/XSA/G960FXXUFFUC6
any reason why that is a bad choice?