I just see that twrp_3.3.1-1_J610x_28719.img is named recovery.img so you must adapt the command…
as twrp_3.3.1-1_J610x_28719.img does not exist in the directory
./heimdall flash --RECOVERY recovery.img --no-reboot
1 Like
./heimdall flash --RECOVERY.img --no-reboot
this ? or minuscule recovery ?
i see you wrote it for me thanks lm trying again…
–RECOVERY is the targeted /partition of the device,
when recovery.img is the partition image you need to flash into it
AhAh !
No such file in directory
what am i doing wrong im in the same terminal…
/heimdall flash --RECOVERY recovery.img --no-reboot
bash: /heimdall: No such file or directory
i have edited adding the missing dot at the beggining
1 Like
Samsung started faster than me but i still have a STATUS CHECKING so l try again… now l see the real timing…
Wow !!
Now l more/less know what is coming next but is it just like for any phone ?
Its just with twrp we tried so many things with the other post concerning a Nexus 5X ?
Im feeling lucky so l try this one
Made by You @Piero
And here l encounter something not quite…
And on my computer
Now l noticed l have access to the phone through the computer…
Would a clic glide of the e/zip in the phone’ s folder work ?
It is number 8 of the tutorial l thought l could try this way as l see in comments someone has succeded this way…
Failed error 255
I recall its the same error that happened with adb sideload…
Just to show l copied the e/zip in the phone storage
Hello
From what l read error 255 is either an outdated twrp or an invalid e/Os/Zip …
Which one is it ?
Hi
I now got this V3 RMM and flash it how ?
with Heimdal ? Post speaks of Odin…
Heimdall or Odin, or fastboot, all do the same job.
when recovery-e or TWRP or Orange-fox all do the “same” job (even if TWRP offer advanced features, it have problem with recent android because of the /data partition encryption…)
the V3 RMM bypass zip is to install from the phone internal storage or SDcard Using the TWRP “install feature” as a preparation step before
- rebooting to recovery, then wipe the needed /partitions, (/system, /cache, /davilc-cache)
- rebooting to recovery, then format /data,
- rebooting to recovery, then install /e/
Hello…
it should work l know but it does not…
I have installed the RMM and it has worked but when l try the e/zip l get the same error 255
my phone is exactly this
samsung SM J610 FN
then l thought maybe its not the right Rom… so l tried this one
Samsung Galaxy J6 2018 (j6lte) for /e/OS-R 1.20
e-1.20-r-20240224-UNOFFICIAL-j6lte.zip
https://sourceforge.net/projects/eosbuildsronnz98/files/SamsungSmartphones/e-1.20-r-20240224-UNOFFICIAL-j6lte.zip/download
same ERR 255
You may have to redo the entire sequence : flash stock firmware + flash TWRP + install RMM_Bypass_v3_corsicanu reboot to recovery etc…etc…
What about lineage OS ?
It sucks it does not have an app lounge and Gapps defeats the purpose il my opinion but ld rather not to go through hell again…
At this point l spent hours trying…
You can have a try to instal /e/ or LineageOS following the instructions from your first post :
Installation
- If you’re on oreo, flash Latest OneUI .
- Download the latest build.
- Reboot to recovery. Will Flash on only arm64 recovery such Orange Fox or other
- Flash the latest build.
- Optional: Flash GApps for Google Services [prefer arm64 Pico] and Magisk for root.
- Reboot
OrangeFox is recommanded isntead of TWRP (you can install OrangeFox using TWRP)
Nah l just installed with that twrp thas ok… it worked surprisingly and l found Aurora instead of gogol play store…
I wanted e/OS but it would not and the idea of doing it all over again made me want to beat my head on the wall…
1 Like
Now if you can run Lineage, you should run /e/…
as it is builded from the same code base…
So, now that you get lineage working,
you can first try to simply reboot into recovery mode and install /e/ over Lineage (what is called “dirty-flash” = without any sort of wipe or format)
nope it did not work…
Error 255 forever !
1 Like
“Dirty flashing” is a method of updating the Android operating system (OS) without wiping any data stored on the device. The term “dirty” refers to the fact that the existing data is not wiped before the update is installed, as opposed to a “clean” flash, which would erase all data before installing the new ROM. Dirty flashing is done for the convenience of the user, as it allows them to keep their personal files and settings intact after the update.
“Clean flashing” including Factory reset > Format data / factory reset via Custom Recovery is the safer way if a CustomROM is to be installed over another CustomROM, even if the code base is Open Source LineageOS, as is the case here.
1 Like
Also, OrangeFox Recovery is recommended.
it is an improved TWRP like recovery-manager.