Heimdall-Note 2 -stock VRALJB - Verizon Samsung Galaxy Note II

I am new to linux (Ubuntu) and I am trying to use Heimdall to flash stock firmware. I have tried Heimdall 1.3.1 and 1.3.2 with no luck. I get an error message that says the VRALJB.tar is missing the firmware.xml? Can anyone help me through the process of Heimdall? This is the last step to being rid of windows for good

Related

failed install of rom; clockwork mod loop (stuck on a mac for now)

okay, so i tried to install CM7 test build 8 onto my phone. the install got up till checking BML/MTD and then failed. i was already on test build 7. anyhows, clockwork said the rom failed to install and then rebooted. now the phone is stuck in a loop of booting into clockwork and then aborting an install.
i would normally have just started up ODIN and flashed down to stock DJ05 or EB01 and then do the lovely root process; but alas i sent my PC into HP today for repair and stuck using a Macbook for a week or two. (no one else in my family uses PC anymore; iPad and Mac family now...sigh)
does anyone know of a way to fix this? i'd like to avoid going back to my old droid 1 (so laggy).
I'm not familiar with the Mac, but take a look @ Heimdall...... I can't post a link for it, but a google search for Heimdall Galaxy S will take you to their website. There are some guides to using it online. I am running Ubuntu linux and usually use this instead of odin.
You will have to unpack the files and put them where they need to go manually.
In my experience lately, I have found that using the atlas 2.2 pit file with the DI01 files works the best. Whenever I use another package, it gives me errors on boot. Push them to your phone, let it boot completely. Then extract the modem and recovery that you want and push that to your phone. Reboot into the recovery immediately and flash the ROM/kernel of your liking.
Eric

[Q] Are there any Odin or Heimdall packages of cyogenmod for the player 4.0?

Long story short,
Even using a custom recovery I am unable to flash any rom Execpt stock, or a modified stock rom (using Etherealrom 2.4 right now)
And I was wondering if anyone has a dump from odin or Heimdall that I could use to try to flash CM to my device, weather it's cm9 or cm10,
it may help, as from there I may be able to flash other roms.
I'm not sure what wrong with my device, but even when returning to stock, my lock screen fails to engage with a 100% stock Heimdall / odin image,
Even ones I've used in the past with no problems. but everything else seems to work fine.
And be fore you ask,
yes I have tried the manual flashing steps shown on the cm9/10/11 pages,
yes, I have tried using the TerraSilent usa kernal (multiple versions)
yes, I have tired doing a full restore of the image, even with re-partitioning from a pit file
yes, I used the preflash before trying to install cm9/10/11, and tried the various toggles
yes, in the past I was able to flash cm9, but I was on stock for a while, then when trying to switch back, this happened.
yes, I have checked my EMS partition, and even tried manually rebuilding it,
The only way I can flash anything, including sock, and modified stock roms, is from my PC, via odin, or Heimdall
So I was wondering if someone with the USA galaxy player 4 could do a dump for me, and include the pit file,
so I could attempt to get CM installed that way?

[Q] S3 Heimdall Flashing Problem

Hey Guys.
So I am working on a Linux Machine ( Ubuntu 14.04 LTS 64 bit ) and I am trying to use Heimdall ( tried Ver 1.3.1 and 1.4 ) to restore a Semi-Bricked 32 GB Galaxy S3 ( GT-I9300 ) to the 4.1.2 JB Stock FW. The phone is able to go into download mode and into it's stock recovery mode. But it doesn't go any further than the white " Samsung Galaxy SIII " Boot Screen Logo upon normal Startup.
When I try to flash the FW files, I get an error on the Radio (modem.bin), the Bootloader (sboot.bin) and the TGSW (tg.bin) part. The Error is as follows : ERROR: Failed to confirm end of file transfer sequence!
I have been searching for Days but I haven't got a workaround. I can't use Odin since I have got no Windows Machine around me. Is there any solution to the above problem ?? =(
mashah1220 said:
Hey Guys.
So I am working on a Linux Machine ( Ubuntu 14.04 LTS 64 bit ) and I am trying to use Heimdall ( tried Ver 1.3.1 and 1.4 ) to restore a Semi-Bricked 32 GB Galaxy S3 ( GT-I9300 ) to the 4.1.2 JB Stock FW. The phone is able to go into download mode and into it's stock recovery mode. But it doesn't go any further than the white " Samsung Galaxy SIII " Boot Screen Logo upon normal Startup.
When I try to flash the FW files, I get an error on the Radio (modem.bin), the Bootloader (sboot.bin) and the TGSW (tg.bin) part. The Error is as follows : ERROR: Failed to confirm end of file transfer sequence!
I have been searching for Days but I haven't got a workaround. I can't use Odin since I have got no Windows Machine around me. Is there any solution to the above problem ?? =(
Click to expand...
Click to collapse
First thing first I haven't a clue about Heimdall or Linix Machine!!
Now thats out of the way have you tried to flash a custom recovery like CM,PhilZ etc with Heimdall I suppose it can do that if it can flash stock fimware? The thinking I have is if you can get a custom recovery on your phone and then flash a custom rom then you maybe able to get your phone to boot.
Wait I here you say that's not stock firmware! Well my reasoning is if you can get your phone to boot then on Playstore is a app called Mobile Odin where you can flash actual stock firmware from your phone.
Like i said don't know anything about the software you are using but I thought I would suggest the above..
Link to mobile odin >> https://play.google.com/store/apps/details?id=eu.chainfire.mobileodin.pro&hl=en <<

Flashing stock without Odin?

I have an old SM-T825 that's been running Nougat and which was previously rooted. After some recent flash attempts that I did incorrectly, I am no longer able to boot into the OS. I'm using TWRP, and even when I reformat /data and then boot directly to System, the setup procedure repeatedly fails with errors which say that Google Play Services has stopped. Therefore, I can never get fully into the OS.
I want to install a newer version of the OS, if possible, and I prefer not to have to use Odin, since I don't have easy access to a Windows machine. If I can't install a newer OS, then the 7.0 ROM is fine.
Also, I intend to root the ROM once I have it installed.
I can flash items via TWRP, so I'm wondering if I can flash a stock ROM (the latest supported version) via TWRP instead of via Odin.
If so, I assume that the stock ROMs on the Samsung site cannot be used, because those are only good for Odin flashes ... correct?
If what I want to do is possible, where is a reliable location for a TWRP-flashable stock SM-T825 ROM? ... and I'm also willing to go with non-stock, if the ROM is reliable.
If this isn't possible via TWRP, is there a way to flash stock or a usable ROM via some sort of Linux software?
Thanks in advance.
.​
There is an Odin for Linux.
J.Michael said:
There is an Odin for Linux.
Click to expand...
Click to collapse
Thank you. Samsung mentions something called jOdin3 which is supposedly cross-platform, but all download and access references for jOdin3 that I have found are dead links.
You might also be referring to a piece of software called heimdall, which does indeed run under linux.
Howver, the heimdall package is more complicated to install and use than Odin, unfortunately, and I have not had success with it in the past. But maybe a more up-to-date version of heimdall will work better, and I will look for this.
UPDATE: I found a version of jOdin3 which runs under linux. It needs heimdall under the covers ...
https://forum.xda-developers.com/android/general/utility-odin-linux-jodin3-casual-t3777030
... and I got the latest heimdall here ...
git clone https://gitlab.com/BenjaminDobell/Heimdall.git
.​
If you have a working TWRP, I think you're ahead of the game. I was under the impression that the advantage of Odin was that you didn't have to have something special installed on the phone. You have something special.
Also, my Samsung Tablet has a recovery menu with an item "Apply update from sdcard". I've been trying to find out what form of update is accepted. I'm guessing it's the .zip file I'm supposed to get from somewhere like sammobile.com, but that's just a guess.

Bricked - stuck at "GT-I5500 SAMSUNG" screen

I have a bricked phone, I don't even remember what I was doing to brick it. Probably installing some cyanogen version.
When it turns on, it first shows a black screen with "GT-I5500" large on the middle, with the SAMSUNG logo on the bottom, and stays there.
What could I try to unbrick it?
Thanks!
I installed JOdin (I have a Mac) and Heimdall (latest nightly build, since I run on a macOS High Sierra 10.13.6)
I found ROMS and etc here: https drive dort google dot com/drive/folders/1y3rvsNnveFkuRtC_We8hLMqmDAepaQ7b?usp=sharing
So I tried to flash using these settings:
PDA = JellyBread v4.5.zip (https drive dot google dot com/file/d/14ofWkgio7go406Y16FtkAn4bJ1B3w_DX/view?usp=sharing)
PIT = Europa_v1.0.ops (https drive dot google dot com/file/d/1WvZ5FAfjlM-AjSjrrRHrtkOrAe42XjVb/view?usp=sharing)
When I hit start, I get an error message saying that "The PIT file was corrupt. We cannot continue without a PIT file". JOdin attempts to get one, but it fails too.
Running JOdin from the terminal I see it trying to run "heimdall download-pit --output <filename>", so I tried to do it myself and this is what I get as output (resulted in a 0 bytes output file):
Code:
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
libusbx: error [get_endpoints] error getting pipe information for pipe 1: unknown error
libusbx: error [darwin_set_interface_altsetting] could not build endpoint table
ERROR: Setting up interface failed!
Releasing device interface...
I wonder if someone here could please provide me with a PIT file for gt-i5500?
(Sorry for the weird links... new user restrictions ¯\_(ツ)_/¯ )
paulera888 said:
I installed JOdin (I have a Mac) and Heimdall (latest nightly build, since I run on a macOS High Sierra 10.13.6)
I found ROMS and etc here: https drive dort google dot com/drive/folders/1y3rvsNnveFkuRtC_We8hLMqmDAepaQ7b?usp=sharing
So I tried to flash using these settings:
PDA = JellyBread v4.5.zip (https drive dot google dot com/file/d/14ofWkgio7go406Y16FtkAn4bJ1B3w_DX/view?usp=sharing)
PIT = Europa_v1.0.ops (https drive dot google dot com/file/d/1WvZ5FAfjlM-AjSjrrRHrtkOrAe42XjVb/view?usp=sharing)
When I hit start, I get an error message saying that "The PIT file was corrupt. We cannot continue without a PIT file". JOdin attempts to get one, but it fails too.
Running JOdin from the terminal I see it trying to run "heimdall download-pit --output <filename>", so I tried to do it myself and this is what I get as output (resulted in a 0 bytes output file):
Code:
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
libusbx: error [get_endpoints] error getting pipe information for pipe 1: unknown error
libusbx: error [darwin_set_interface_altsetting] could not build endpoint table
ERROR: Setting up interface failed!
Releasing device interface...
I wonder if someone here could please provide me with a PIT file for gt-i5500?
(Sorry for the weird links... new user restrictions ¯\_(ツ)_/¯ )
Click to expand...
Click to collapse
Hey, I'm the creator of the ROM collection thread, I can help you out with this. First off, can you get into Download Mode? I assume you can, since you're trying to use Odin. This is good, that means you can recover the brick. Next, I think JOdin will never work with this phone. This phone is very, very, finicky about the drivers and Odin version used. It seems to require a specific version to work, the one I linked - 4.28. As you can see here by XDA user Rickav, who tried to use newer Odin and Windows, it just doesn't work. We now know that this phone refuses to work with any Windows version newer than Windows 7, when Rickav reported that Win 10 was not able to work with the phone, but was successful with Win 7. If Win 10 doesn't work, MacOS has practically no chances of working.
So, you absolutely need to use either Windows XP, Vista, or 7 to be able to flash this phone in Download mode. Since you're on a Mac, you have a couple of options. The first is to use Boot Camp to dual boot Windows. This is optimal, but you may not like to do this, for various reasons. If you do not want to use Boot Camp, a virtual machine is also an option. You can download VirtualBox for free, and install Windows there. I would suggest using Windows 7 32-bit, or Windows XP, for maximum compatibility. If you do not know how to use VirtualBox, look up some tutorials, it's pretty easy to use. Then, when you have Windows installed in the VM, you can install the Odin 4.28 and and the Samsung USB Drivers from the backups thread.
When you have your VM (or dual boot, if you choose this) set up with the required software, you can start to recover the phone. I have found the most stable ROM is CM 7.2 (Android 2.3.7), so I would suggest flashing this. To use CM, you will first need a custom recovery. So, your first step is to use Odin to flash the ClockworkMod tar in the backups thread. Use Odin 4.28 (in backup thread), with the included ops file. After this, flash the AMSS-I5500LUYJPE.tar baseband, this is needed for custom ROMs to boot (otherwise, the custom ROM may bootloop) Next, go to the Philz Touch Recovery thread, and download 6.57.2. Put this zip on an sd card, insert sd into phone, boot into ClockworkMod, and flash the Philz Touch zip. This will overwrite the Clockwork recovery with Philz Touch. Philz is an improved version of Clockwork, and is also required to flash newer ROMs like CM 11. Once you have done this and have Philz Touch, download CM 7.2, put on sd, and boot into Philz. Go to wipe, and select prepare for new rom option, it will automatically wipe system, data, and cache. Next, flash the CM7.2 zip, and reboot. That should be it, and your phone should boot.
Sanras said:
Hey, I'm the creator of the ROM collection thread, I can help you out with this. First off, can you get into Download Mode? I assume you can, since you're trying to use Odin. This is good, that means you can recover the brick. Next, I think JOdin will never work with this phone. This phone is very, very, finicky about the drivers and Odin version used. It seems to require a specific version to work, the one I linked - 4.28. As you can see here by XDA user Rickav, who tried to use newer Odin and Windows, it just doesn't work. We now know that this phone refuses to work with any Windows version newer than Windows 7, when Rickav reported that Win 10 was not able to work with the phone, but was successful with Win 7. If Win 10 doesn't work, MacOS has practically no chances of working.
So, you absolutely need to use either Windows XP, Vista, or 7 to be able to flash this phone in Download mode. Since you're on a Mac, you have a couple of options. The first is to use Boot Camp to dual boot Windows. This is optimal, but you may not like to do this, for various reasons. If you do not want to use Boot Camp, a virtual machine is also an option. You can download VirtualBox for free, and install Windows there. I would suggest using Windows 7 32-bit, or Windows XP, for maximum compatibility. If you do not know how to use VirtualBox, look up some tutorials, it's pretty easy to use. Then, when you have Windows installed in the VM, you can install the Odin 4.28 and and the Samsung USB Drivers from the backups thread.
When you have your VM (or dual boot, if you choose this) set up with the required software, you can start to recover the phone. I have found the most stable ROM is CM 7.2 (Android 2.3.7), so I would suggest flashing this. To use CM, you will first need a custom recovery. So, your first step is to use Odin to flash the ClockworkMod tar in the backups thread. Use Odin 4.28 (in backup thread), with the included ops file. After this, flash the AMSS-I5500LUYJPE.tar baseband, this is needed for custom ROMs to boot (otherwise, the custom ROM may bootloop) Next, go to the Philz Touch Recovery thread, and download 6.57.2. Put this zip on an sd card, insert sd into phone, boot into ClockworkMod, and flash the Philz Touch zip. This will overwrite the Clockwork recovery with Philz Touch. Philz is an improved version of Clockwork, and is also required to flash newer ROMs like CM 11. Once you have done this and have Philz Touch, download CM 7.2, put on sd, and boot into Philz. Go to wipe, and select prepare for new rom option, it will automatically wipe system, data, and cache. Next, flash the CM7.2 zip, and reboot. That should be it, and your phone should boot.
Click to expand...
Click to collapse
Friend, thank you so much for your reply, I appreciate your effort in putting all those considerations and details together. You are a star! I will try it out with a VM and come back here with the results.
Sanras said:
r dual boot, if you choose this) set up with the required software, you can start to recover the phone. I have found the most stable ROM is CM 7.2 (Android 2.3.7), so I would suggest flashing this. To use CM, you will first need a cu
Click to expand...
Click to collapse
Sanras said:
Hey, I'm the creator of the ROM collection thread, I can help you out with this. First off, can you get into Download Mode? I assume you can, since you're trying to use Odin. This is good, that means you can recover the brick. Next, I think JOdin will never work with this phone. This phone is very, very, finicky about the drivers and Odin version used. It seems to require a specific version to work, the one I linked - 4.28. As you can see here by XDA user Rickav, who tried to use newer Odin and Windows, it just doesn't work. We now know that this phone refuses to work with any Windows version newer than Windows 7, when Rickav reported that Win 10 was not able to work with the phone, but was successful with Win 7. If Win 10 doesn't work, MacOS has practically no chances of working.
So, you absolutely need to use either Windows XP, Vista, or 7 to be able to flash this phone in Download mode. Since you're on a Mac, you have a couple of options. The first is to use Boot Camp to dual boot Windows. This is optimal, but you may not like to do this, for various reasons. If you do not want to use Boot Camp, a virtual machine is also an option. You can download VirtualBox for free, and install Windows there. I would suggest using Windows 7 32-bit, or Windows XP, for maximum compatibility. If you do not know how to use VirtualBox, look up some tutorials, it's pretty easy to use. Then, when you have Windows installed in the VM, you can install the Odin 4.28 and and the Samsung USB Drivers from the backups thread.
When you have your VM (or dual boot, if you choose this) set up with the required software, you can start to recover the phone. I have found the most stable ROM is CM 7.2 (Android 2.3.7), so I would suggest flashing this. To use CM, you will first need a custom recovery. So, your first step is to use Odin to flash the ClockworkMod tar in the backups thread. Use Odin 4.28 (in backup thread), with the included ops file. After this, flash the AMSS-I5500LUYJPE.tar baseband, this is needed for custom ROMs to boot (otherwise, the custom ROM may bootloop) Next, go to the Philz Touch Recovery thread, and download 6.57.2. Put this zip on an sd card, insert sd into phone, boot into ClockworkMod, and flash the Philz Touch zip. This will overwrite the Clockwork recovery with Philz Touch. Philz is an improved version of Clockwork, and is also required to flash newer ROMs like CM 11. Once you have done this and have Philz Touch, download CM 7.2, put on sd, and boot into Philz. Go to wipe, and select prepare for new rom option, it will automatically wipe system, data, and cache. Next, flash the CM7.2 zip, and reboot. That should be it, and your phone should boot.
Click to expand...
Click to collapse
Following your instructions and some other posts, I managed to get my GT-I5500 back to life; yay! I will leave some links and comments for those who might bump into this in the future. Thanks a lot
For some reason, I was not managing to boot the phone in recovery mode (it just kept stuck at the logo screen). In a nutshell, what I did was:
* Put CyanogenMod's zip in the sd card, card into the phone
* Using Odin, I flashed Clockworkmod into the phone, it rebooted into CWM's interface
* Wipe cache and user data
* Instal CyanogenMod from sdcard
* Happy days
These links were of great help:
Install Windows XP in VirtualBox (ready to use Virtual HD)
https://www.makeuseof.com/tag/download-windows-xp-for-free-and-legally-straight-from-microsoft-si/
VirtualBox extension to enable enable USB 2.0
https://www.techrepublic.com/article/how-to-enable-usb-in-virtualbox/
Actions sequence to get Odin to identify and interact properly with the phone
https://forum.xda-developers.com/t/...with-windows-as-virtualboxs-guest-os.1391189/
Install ClockworkMod Bootloader and Cyanogen 7 ROM to Samsung G5 I5500
https://forum.xda-developers.com/t/...d-cyanogen-7-rom-to-samsung-g5-i5500.1416190/
The "backup thread" with all the stuff for Galaxy 5 GT-I5500
https://forum.xda-developers.com/t/...rom-collection-for-galaxy-5-gt-i5500.3917603/
my gt-i5500 europe has the same error but i connect it to odin and my pc says that it doesn't recognize it and it shows the error code 10 can someone help me
progatillo said:
my gt-i5500 europe has the same error but i connect it to odin and my pc says that it doesn't recognize it and it shows the error code 10 can someone help me
Click to expand...
Click to collapse
First of all, are you using Windows XP, and the drivers +Odin from the backup thread? From what I remember, new versions of Windows don't seen to work with it, so you'll need to either setup a Virtual Machine or dig up an old of that you can run xp on.
Sanras said:
First of all, are you using Windows XP, and the drivers +Odin from the backup thread? From what I remember, new versions of Windows don't seen to work with it, so you'll need to either setup a Virtual Machine or dig up an old of that you can run xp on.
Click to expand...
Click to collapse
No i'm using Windows 10
progatillo said:
No i'm using Windows 10
Click to expand...
Click to collapse
Try using a Windows XP VM. Pass through the phone when it is in odin mode to the XP machine, then try to flash it using the XP VM and the drivers+odin provided.

Categories

Resources