Try out my new Linux flash tool called Thor - https://forum.xda-developers.com/t/dev-thor-flash-utility-the-new-samsung-flash-tool.4597355, which has all the features of this tool + extras, like the usual Windows Odin ones which are missing in this leaked tool: F. Reset Time, NAND Erase All (aka just erase userdata), EFS Clear and bootloader update.
Samsung's Odin on Linux is no longer a dream! This is an official version leaked from Samsung.
WARNING! Don't DM me stupid questions, I'm not tech support and I'm not going to teach you linux.
Here's the output you get from
Code:
odin -h
Code:
Usage : odin4 [args...]
Odin4 downloader. odin4 version 1.2.1-dc05e3ea
-v SHOW VERSION
-w Show License
-b Add Bootloader file
-a Add AP image file
-c Add CP image file
-s Add CSC file
-u Add UMS file
-e Set Nand erase option
-V Home binary validation check with pit file
--reboot Reboot into normal mode
--redownload Reboot into download mode if it possible (not working in normal case)
-d Set a device path (detect automatically without this option)
-l Show downloadable devices path
IMPORTANT : You must set up your system to detect your device on LINUX host.
create this file: /etc/udev/rules.d/51-android.rules
to add a line to the file:
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666", GROUP="plugdev"
(http://developer.android.com/tools/device.html)
And you maybe need to unload a module cdc_acm before downloading. (This is only needed for older kernels.)
$sudo rmmod cdc_acm
OR
echo "blacklist cdc_acm" > /etc/modprobe.d/cdc_acm-blacklist.conf
Example :
$odin4 -b BL_XXXX.tar.md5 -a AP_XXXX.tar.md5 -c CP_XXXX.tar.md5 -s CSC_XXXX.tar.md5
Example (Select One Device):
$odin4 -l
PATH_OF_DEVICE_A
PATH_OF_DEVICE_B
$odin4 -b BL_XXXX.tar.md5 -a AP_XXXX.tar.md5 -c CP_XXXX.tar.md5 -s CSC_XXXX.tar.md5 -d PATH_OF_DEVICE_A
Odin Community : http://mobilerndhub.sec.samsung.net/hub/site/odin/
You can even verify that's the real one by comparing it's code with the Windows Odin.
For some reason some method names were left unmodified.
Have a nice day!
It is in the archive attached. XDA doesn't allow for no-extension files to be uploaded.
Thanks mate!
OMFG! You are a godsend!!! I was skeptical at first when I saw this post, wondering how I never saw this before today... However, I just tried it out and it worked 100% and quickly!
I have tried every other linux solution and every last one came up bust until now. Thanks again!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello! Can you to public source code? And port Odin for Linux for ARM. It's only for x86
NikitaSav said:
Hello! Can you to public source code? And port Odin for Linux for ARM. It's only for x86
Click to expand...
Click to collapse
This is official odin from the LAP$US Samsung leak. I didn't find it's source code as the executable itself was used in some sort of CI.
TheAirBlow said:
This is official odin from the LAP$US Samsung leak. I didn't find it's source code as the executable itself was used in some sort of CI.
Click to expand...
Click to collapse
That is, it turns out that you just took the source code from there, downloaded a compiler that can make a binary for Linux and compiled it?
NikitaSav said:
That is, it turns out that you just took the source code from there, downloaded a compiler that can make a binary for Linux and compiled it?
Click to expand...
Click to collapse
I said that there was no source code and it was executable only. Is it that hard to understand?
It's legit! Thanks a lot!
ragarcia87 said:
OMFG! You are a godsend!!! I was skeptical at first when I saw this post, wondering how I never saw this before today... However, I just tried it out and it worked 100% and quickly!
I have tried every other linux solution and every last one came up bust until now. Thanks again!
View attachment 5743797
Click to expand...
Click to collapse
What is the command you executed before this? Please tell clearly. I want to flash TWRP.
mark86v1 said:
What is the command you executed before this? Please tell clearly. I want to flash TWRP.
Click to expand...
Click to collapse
There was no command executed before this. That was the only command executed. I first copied the executable to my local bin folder in PATH and then ran that command.
ragarcia87 said:
There was no command executed before this. That was the only command executed. I first copied the executable to my local bin folder in PATH and then ran that command.
Click to expand...
Click to collapse
Does the phone have to be in download mode?
mark86v1 said:
Does the phone have to be in download mode?
Click to expand...
Click to collapse
Yes, gotta be in download mode before you can use Odin to flash recovery
ragarcia87 said:
Yes, gotta be in download mode before you can use Odin to flash recovery
Click to expand...
Click to collapse
Thanks for the info mate, I have already unlocked the bootloader but when I use the hardware key combinations for download mode, it's not working. Phone is directly re-starting. Any idea?
mark86v1 said:
Thanks for the info mate, I have already unlocked the bootloader but when I use the hardware key combinations for download mode, it's not working. Phone is directly re-starting. Any idea?
Click to expand...
Click to collapse
Try using adb. Use adb reboot download
ragarcia87 said:
Try using adb. Use adb reboot download
Click to expand...
Click to collapse
Sure thanks mate. Will try this.
ragarcia87 said:
Try using adb. Use adb reboot download
Click to expand...
Click to collapse
Tried the same. In the terminal, it came success but the phone is stuck at ODIN MODE (SVB FAIL). Even after restarting it is stuck in download mode.
mark86v1 said:
Tried the same. In the terminal, it came success but the phone is stuck at ODIN MODE (SVB FAIL). Even after restarting it is stuck in download mode.
Click to expand...
Click to collapse
Verification is on for some reason?
TheAirBlow said:
Verification is on for some reason?
Click to expand...
Click to collapse
Code:
ODIN MODE (SVB FAIL)!
recovery: No footer detected. (0)
recovery: Error verifying vbmeta Image: invalid vbmeta header (6)
VBMETA A127FXXU..., 527...
These are the messages showing up. Any help?
I somehow got rid of the above error and flashed BL, AP, CP, CSC files using Linux ODIN. Now can anyone guide me with the steps to install TWRP correctly, install lineage os and root my phone. It would be really helpful.
Related
I can only get the flashtool to recognize my phone is flash mode, anyone can chime in if they want to
HOW-TO
Open terminal alt+ctrl+T
Copy and paste each line separately
sudo add-apt-repository ppa:ferramroberto/java
sudo apt-get update
sudo apt-get install sun-java6-jre sun-java6-plugin sun-java6-fonts
Then download the flashtool
http://androxyde.github.com/Flashtool/
Extract the file and save it in your home folder
Now you need to make a udev rule
Go in terminal and hit SHIFT+CTRL+T
2 tabs should be opened
Type
sudo gedit /etc/udev/rules.d/51-flashtool.rules
then go to the other terminal tab and type
lsusb
you should see a line that looks like this
Bus 001 Device 011: ID 0fce:612e Sony Ericsson Mobile Communications AB
copy the bold and italicized print into this line
SUBSYSTEM=="usb", ACTION=="add", SYSFS{idVendor}=="0fce", SYSFS{idProduct}=="####", MODE="0777"
Save that line into the rules file
Go to the flashtool folder
Click on the flashtool file
And run it but not in terminal
hi,
I got Macbuntu 10.10 here.
Downloaded & extracted flashtool 0.6.7
have java installed
have libusb-1.0 installed
how do I add the rule =>
(terminal?)
/etc/udev :
SUBSYSTEM=="usb", ACTION=="add", SYSFS{idVendor}=="0fce", SYSFS{idProduct}=="*", MODE="0777"
and then?
any help would be nice..
you will be in terminal, sorry im never on here. the command gedit will open the file where needed to make the rule
I'll redo install and take screenshots as I go
Jedidiah55 said:
you will be in terminal, sorry im never on here. the command gedit will open the file where needed to make the rule
I'll redo install and take screenshots as I go
Click to expand...
Click to collapse
that would be nice
I added this
SUBSYSTEM=="usb", ACTION=="add", SYSFS{idVendor}=="0fce", SYSFS{idProduct}=="615a", MODE="0777"
Click to expand...
Click to collapse
from lsusb
Bus 001 Device 005: ID 0fce:615a Sony Ericsson Mobile Communications AB
Click to expand...
Click to collapse
but I still get.
libusb couldn't open USB device /dev/bus/usb/001/007: Permission denied.
libusb requires write access to USB device nodes.
Click to expand...
Click to collapse
??
leona said:
I added this
from lsusb
but I still get.
??
Click to expand...
Click to collapse
Use sudo
leona said:
I added this
from lsusb
but I still get.
??
Click to expand...
Click to collapse
Oddly a restart seemed to cure it, even after I did restart a udev service, it needed to restart the PC.
Edit: Hum maybe not, just plugged phone while switched on and it seemed fine.
Went to do a firmware flash and it gave me the
Code:
libusb couldn't open USB device /dev/bus/usb/001/012: Permission denied.
libusb requires write access to USB device nodes.
Again
sorry ive been busy lately, job change, engine swaps, moving, buying new car, buried some family, etc.
ive also update to 12.4 ubuntu so ill see what i can do
Jedidiah55 said:
sorry ive been busy lately, job change, engine swaps, moving, buying new car, buried some family, etc.
ive also update to 12.4 ubuntu so ill see what i can do
Click to expand...
Click to collapse
Gosh you have been busy, I'm still on 10.04 LTS at the moment, as I have not got around to update my machine yet, as I can not stand the new UI.
I did the firmware flash in the end but using sudo as Mister J suggested which worked, but it would be nice to have it work it properly.
leona said:
Oddly a restart seemed to cure it, even after I did restart a udev service, it needed to restart the PC.
Edit: Hum maybe not, just plugged phone while switched on and it seemed fine.
Went to do a firmware flash and it gave me the
Code:
libusb couldn't open USB device /dev/bus/usb/001/012: Permission denied.
libusb requires write access to USB device nodes.
Again
Click to expand...
Click to collapse
Try opening up a terminal and typing:
"sudo nautilus"
Then, go to /dev/usb/001/012 and Right clicking on the file.
Click on the Permissions tab and change the drop down menu to read and write.
Like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
help
followed the steps as you mentioned. But when i click on the flashtool script file nothing is happening.
pls help
M4ST3R-V said:
followed the steps as you mentioned. But when i click on the flashtool script file nothing is happening.
pls help
Click to expand...
Click to collapse
Open terminal and run flashtool and you'll see what is wrong
Sent from my Xperia X10 using xda app-developers app
thank you
Tof37 said:
Open terminal and run flashtool and you'll see what is wrong
Sent from my Xperia X10 using xda app-developers app
Click to expand...
Click to collapse
thanks for the tip. Yes i Opened it in terminal with sudo su permission and got the error. lsusb version error was the probem and there was a and additional update to the latestet version searched a lot to find it. this solved most of this :good:
good, but work only in root users.
because flashtool do not recognize, my x10? i can only flash. is a problem of linux version?
can i use with xperia Neo V?
Sorry for stupid question,but i don't know very well Ubuntu!
Thank you! Will come in handy later!
linux mint xfce 17 (ubuntu 14)
Hi, would be this guide work on my system too? I am newbee in linux. Help me please.
Sory, my phone is Elephone P9, MTK6592
help
sudo apt-get install sun-java6-jre sun-java6-plugin sun-java6-fonts
hi when i type this
show me in terminal this message:
E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.
please help me
hi. when i write this:
sudo apt-get update
terminal show me this text!
E: Could not get lock /var/lib/apt/lists/lock - open (11: Resource temporarily unavailable)
E: Unable to lock directory /var/lib/apt/lists/
E: Could not get lock /var/lib/dpkg/lock - open (11: Resource temporarily unavailable)
E: Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?
this is true?
I got this error everytime i run FlashTool as root.
I can run FlashTool if i run it as normal user, but the access to phones are denied by system ._.
Please help me
First:
Warning! This is only for A70B/A70IT2 Honeycomb model, It won't work on Froyo model!
Here is a package that enables unofficially SDE menu in recovery and install a rooted stock firmware with busybox and SuperUser.Apk
Pre-Requisite:
- Adb must be enabled on tablet and PC driver+adb command must be working. You can test on pc with "adb shell", it should give you a '$' prompt. If you don't have this, first make it work. There are multiple links around to help if needed.
Instructions:
- Unzip files on your pc in adb.exe directory.
- Launch enable_sde.bat on your pc. It's better to do it in a cmd.exe window, you'll be able to copy-paste log here if anything goes wrong.
- Follow instructions in the cmd window. Basically, script reboots tablet multiple times, you have to press enter when tablet is completely booted each time.
- Congratulation, your device is sde enabled and has a rooted sde firmware. Please read below for more information.
Upgrades:
If you already installed a first version and enabled sde already, here is how to install new rooted firmware:
- Optional: flash updated stock firmware. I always recommend to match stock firmware, it avoids dalvik-cache rebuilds and bootloaders may have been updated in new firmwares.
- Boot rooted firmware. You should be running rooted firmware if you want upgrade script to work. To be sure of that, you should see SuperUser app in your apps menu.
- Unzip files on your pc in adb.exe directory
- Launch upgrade.bat (or upgrade.sh for linux)
- Tablet reboots at the end to rooted firmware and should be upgraded to new version.
SDE information:
1) What is SDE?
SDE (Special Developer Edition) is basically a dual boot mechanism. It allows us to dual boot Archos stock firmware and our custom ones.
2) How does it work ?
I won't give much details on how to use it, I should do a separate topic about this one someday. Until then, here is some basic information:
- At the end of this script, you are booted with sde firmware, superuser should be in your start menu and you should be root with adb or any root app.
- If you reboot or boot, press volume up while booting, it will display the dual boot menu. Select "Developer Edition", it will start the rooted build (check here point 9 to see how it looks).
- If you missed volume key or don't do anything during reboot, you will go back to unrooted stock firmware. You have to press the volume up key during boot to get the boot menu.
- Warning: booting stock firmware is harmless except that you will loose your SuperUser.apk preferences. As it's not part of stock firmware, Android clears it.
- You can boot straight to rooted firmware by deleting the stock firmware kernel in recovery. Check here, do point 4,5, and on screen 6, select "Remove Android Kernel". Make sure that you have properly working SDE firmware before doing that. If you want to re-enable back stock firmware, just flash it from recovery again.
Downloads:
3.2.80 can be downloaded here: Mirror 1 (Mediafire), Mirror 2 (Sendspace).
3.2.81 can be downloaded here: Mirror 1 (SendSpace) (bat fixed)
Sorry, Mediafire no longer let me upload without signup, if you know one good upload location without registration and allowing more than 200 MB, let me know.
*reserved*
Registered just to say thank you!
Worked like a charm, and no problems using the shell script (I run Arch Linux)
Keep up the good work!
Thanks
I mean real thanks
Sent from my ARCHOS 70it2 using xda premium
EDIT:
Beautiful man, beautiful. Works splendidly
Thanks again
LeTama
Have a beer or two on me, 84G89322WT2139701.
Thanks again for your Rom.
Hi mrew42,
Thanks a lot! Much appreciated!
Tomorrow, my 70b return at home
I testing that !
but my 70bit2 is with 3.2.81
Letama, can you may be make the same for 3.2.81?
Yes, it will come soon...
3.2.81 is up and instructions on first post updated if you upgrade.
Great
http://www.jbmm.fr/?p=27601
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
cajl said:
Great
Click to expand...
Click to collapse
Nice job! Thanks for the article on jbmm!
Thanks, will try it out soon.
Thanks letama, this is just what I wanted. Awsome work!
I think there is an error in upgrade.bat and enable_sde.bat for 3.2.81.
The line that reads:
adb push android_32.ext4.update /media/
should read:
adb push android_32.ext4.update /data/media/
Also, upgrade.bat is missing the line that says:
adb shell rm /data/local.prop
Keep up the good work and thanks again.
ColinTaylor said:
I think there is an error in upgrade.bat and enable_sde.bat for 3.2.81.
The line that reads:
adb push android_32.ext4.update /media/
should read:
adb push android_32.ext4.update /data/media/
Click to expand...
Click to collapse
Ah! Right! Thanks for pointing it, I'll fix that and re-upload when I find time to do it.
Also, upgrade.bat is missing the line that says:
adb shell rm /data/local.prop
Click to expand...
Click to collapse
Yes, this is normal, this one is only needed when enabling sde first time. local.prop is coming from temp root and won't be there anymore.
I finally had time to try it out tonight, all seemed to be installed fine, but I don't see the Superuser in the apps list... I can boot into developers fw menu though. Did I miss something or should I just try to reinstall the SDE again by running that bat file again?
No, as ColinTaylor said, there is a typo in script, you just need to push the ext4.update at root of storage.
Just type this command in the directory you unzipped the files:
Code:
adb push android_32.ext4.update /data/media/
then boot sde.
Hello
As i have read your post about how to root 3.2.81, the instructions seems to confuse me, but what do you mean by adb? im sorry im kinda new at this ,please let me know thanks!
hello, first of all thanks for your work.
I am having some problems with the upgrade file.
it says that it cannot stat 'zImage':no such file or directory
and secondly it cannot open the kernel file (no such file or directory) mkf lashimage failed.
could you please provide some help with this?
thanks!
lozano.markp said:
Hello
As i have read your post about how to root 3.2.81, the instructions seems to confuse me, but what do you mean by adb? im sorry im kinda new at this ,please let me know thanks!
Click to expand...
Click to collapse
adb is a developer tool from android sdk that let you execute commands on your tablet from your PC. You have to install android sdk to get it, you need to enable it on the tablet and have a proper driver.
hi, guys I want to root my grand 2 LTE SM-G7105 I am running running android kitkat 4.4.2 I tried the following things which totally failed:
CF auto root which was for sm-g7102 and got bricked.
towelroot saying device is not supported.
framaroot failed totally.
please help me.
qasim799 said:
hi, guys I want to root my grand 2 LTE SM-G7105 I am running running android kitkat 4.4.2 I tried the following things which totally failed:
CF auto root which was for sm-g7102 and got bricked.
towelroot saying device is not supported.
framaroot failed totally.
please help me.
Click to expand...
Click to collapse
the same for me there's no root possibility now we have just to wait for CWM for SM-G7105
maxx35000 said:
the same for me there's no root possibility now we have just to wait for CWM for SM-G7105
Click to expand...
Click to collapse
i don't think that cwm would be ported to this phone cause most of the devs have sm-g7102.Well we can make cwm if you are interested.
qasim799 said:
i don't think that cwm would be ported to this phone cause most of the devs have sm-g7102.Well we can make cwm if you are interested.
Click to expand...
Click to collapse
why not,
i try to learn how to do it
let's have a try
maxx35000 said:
why not,
i try to learn how to do it
let's have a try
Click to expand...
Click to collapse
here is all information I got while trying to port cwm but failed everytime you can help me.
1-I tried builder.clockworkmod.com tool it is easy tool to port recovery in just one click but there's an error 404 everytime i try it.
2-so secondly we can port sm-g7102 cwm to this phones as they have same CPU,harwares etc.
here to extract recovery.img http://boot-repacker.blogspot.com/ and you can find stock recovery.img in firmware and sm-g7102 cwm in development section.
3-third method most tough and tricky:
we can build cwm from source for this we need ubuntu (I have ubuntu in my pc).
here's some useful links:http://xda-university.com/as-a-developer/getting-started-building-android-from-source
http://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html
qasim799 said:
here is all information I got while trying to port cwm but failed everytime you can help me.
1-I tried builder.clockworkmod.com tool it is easy tool to port recovery in just one click but there's an error 404 everytime i try it.
2-so secondly we can port sm-g7102 cwm to this phones as they have same CPU,harwares etc.
here to extract recovery.img http://boot-repacker.blogspot.com/ and you can find stock recovery.img in firmware and sm-g7102 cwm in development section.
3-third method most tough and tricky:
we can build cwm from source for this we need ubuntu (I have ubuntu in my pc).
here's some useful links:http://xda-university.com/as-a-developer/getting-started-building-android-from-source
http://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html
Click to expand...
Click to collapse
ok ilook for this tonight
qasim799 said:
here is all information I got while trying to port cwm but failed everytime you can help me.
1-I tried builder.clockworkmod.com tool it is easy tool to port recovery in just one click but there's an error 404 everytime i try it.
2-so secondly we can port sm-g7102 cwm to this phones as they have same CPU,harwares etc.
here to extract recovery.img http://boot-repacker.blogspot.com/ and you can find stock recovery.img in firmware and sm-g7102 cwm in development section.
3-third method most tough and tricky:
we can build cwm from source for this we need ubuntu (I have ubuntu in my pc).
here's some useful links:http://xda-university.com/as-a-developer/getting-started-building-android-from-source
http://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html
Click to expand...
Click to collapse
You can't use CWM Builder on a Samsung.
But make sure, just in case.
Which version of towelroot you tried ? Try using v1
I tried towel root v1 it stucks and on v3 it says your phone is not supported.I heard about modstrings can you help me getting right string for my phone.
qasim799 said:
I tried towel root v1 it stucks and on v3 it says your phone is not supported.I heard about modstrings can you help me getting right string for my phone.
Click to expand...
Click to collapse
So y not make a pre rooted firmware ?
Sent from my SM-G7102 using Tapatalk 2
Yeah that's a good idea .so I have firmware how to make it pre-rooted guide me kindly.
qasim799 said:
Yeah that's a good idea .so I have firmware how to make it pre-rooted guide me kindly.
Click to expand...
Click to collapse
you can try this
http://forum.xda-developers.com/showthread.php?t=2665283
I tried but failed only way left is cwm
What exactly fail can you explain me ,
have you make flashable pre-rooted one ?
what exactly the problem with it ?
When you flash it the phone boot correctly ?
i am trying to install Vbox with ubuntu on my pc to help you
maxx35000 said:
What exactly fail can you explain me ,
have you make flashable pre-rooted one ?
what exactly the problem with it ?
When you flash it the phone boot correctly ?
i am trying to install Vbox with ubuntu on my pc to help you
Click to expand...
Click to collapse
the problem is in step 5 (Create temp folder and mount it.)( mkdir temp)
(sudo mount -o loop system.img.ext4 temp) this command is invalid and ubuntu terminal is giving error please specify filesystem then i changed the command and tried "sudo mount ext4 -o loop system.img.ext4 temp but it failed again.I'm just stuck on it.please help
qasim799 said:
the problem is in step 5 (Create temp folder and mount it.)( mkdir temp)
(sudo mount -o loop system.img.ext4 temp) this command is invalid and ubuntu terminal is giving error please specify filesystem then i changed the command and tried "sudo mount ext4 -o loop system.img.ext4 temp but it failed again.I'm just stuck on it.please help
Click to expand...
Click to collapse
ok i am a the part 8) Convert newsys.img to samsung system.img format. but i have an error see on the screanshot iF someone knows the problem please help me thank's
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Your ubuntu terminal is not rooted.you need a rooted ubuntu google it.
The sign $ at last of every command changes into # sign.
Also which version of ubuntu you are using??
qasim799 said:
Your ubuntu terminal is not rooted.you need a rooted ubuntu google it.
The sign $ at last of every command changes into # sign.
Also which version of ubuntu you are using??
Click to expand...
Click to collapse
i use 13.04 but i use Sudo command and it work
ok so i've root ubuntu and now i have some new issue ^^
"[email protected]:/home/maxx35000/test# ./mkuserimg.sh -s temp system.img ext4 tempdir 2048M
bash: ./mkuserimg.sh: Permission denied
[email protected]:/home/maxx35000/test# "
maxx35000 said:
i use 13.04 but i use Sudo command and it work
ok so i've root ubuntu and now i have some new issue ^^
"[email protected]:/home/maxx35000/test# ./mkuserimg.sh -s temp system.img ext4 tempdir 2048M
bash: ./mkuserimg.sh: Permission denied
[email protected]:/home/maxx35000/test# "
Click to expand...
Click to collapse
Make sure that ./mkuserimg.sh is placed correctly in directory in which your files are placed. Try chmod 777 ./mkuserimg.sh as mentioned in the guide it sets permissions
qasim799 said:
Make sure that ./mkuserimg.sh is placed correctly in directory in which you are working if fails again then redownload new version os ./mkuserimg.sh and place it in your directory.
Click to expand...
Click to collapse
yes first i try new vertion of ubuntu and let's start again
This is a test root method for the G4. It is based off of the original root method for rooting LG devices. The original method showed modified in the boot loader but it didn't have su. This a modified script to push su correctly and the su used by the H815.
Note: On the H815 If you would like root all you have to do is unlock boot loader, flash twrp for G4 then flash the supersu.zip
WARNING: USE AT YOUR OWN RISK!!
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this ROM
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
Click to expand...
Click to collapse
This is a new method that i discovered. Instead of rooting we are just going to flash TWRP then we can root through the recovery. I have tested this on my G3 and i can confirm that you are able to flash recoveries through download mode.
The Recovery used in this is TWRP for H815 and I am not sure of how compatible it is with other variants but if it gives you root then its worth testing.
Files:LGG4_rFLASH.zip
Drivers:HERE
Step 1: Enable USB Debugging
Step 2: Download G4 Flasher and unzip, Also Install Drivers
Step 3: In unzipped folder open a new command prompt window (Shift+Right click)
Step 4: Run this command
adb.exe push recovery.img /data/local/tmp/
Click to expand...
Click to collapse
Step 5: Enter Download Mode (Hold Volume Up While plugging in Usb Cable)
Step 6: Check Device Manager> Serial Port (Windows) and make sure your Phones COM is set to 41, if not then change it. After changing it you may have to unplug usb, pull battery and then reboot into download mode.
Step 7: Open a new Command prompt window just like before. in the folder you extracted.
Step 8: Run this Command
Send_Command.exe \\.\COM41
Click to expand...
Click to collapse
.
Step 9: Run this to Backup your current recovery
dd if=/dev/block/platform/f9824900.sdhci/by-name/recovery of=/data/local/tmp/recoverybak.img
Click to expand...
Click to collapse
Step 10: It will now show a # then run this
dd if=/dev/zero of=/dev/block/platform/f9824900.sdhci/by-name/recovery
Click to expand...
Click to collapse
Step 11: Then run this
dd if=/data/local/tmp/recovery.img of=/dev/block/platform/f9824900.sdhci/by-name/recovery
Click to expand...
Click to collapse
Step 12: Pull battery and try to boot into recovery
Step 13: Flash Supersu.zip
Note:: to restore original Recovery all you have to do is pull it
adb pull /data/local/tmp/recoverybak.img \
Rename it recovery.img (you might have to delete or rename the one that was extracted from the zip earlier because the can only be one recovery.img in a folder )
then rinse and repeat all the steps
I've got a Verizon version coming tomorrow. Can't wait to give this a try. Thanks.
Edit - Just tried to download the root zip, and I got a message that it's infected with a virus.
cant download G4_Rootbeta1.zip
her it is
hytin said:
cant download G4_Rootbeta1.zip
Click to expand...
Click to collapse
This is the error we get when attempting to download it:
Code:
Sorry, this file is infected with a virus
Only the owner is allowed to download infected files.
EDIT: See my post below for a copy of the ZIP
i think i found a way will upload it later
Does anyone tried this method on the T-Mobile G4 H811?
I was able to use a web-based ZIP extractor to extract then compress it. I have done no scanning for viruses, I simply extracted and repackaged the files.
G4_Rootbeta1
ZIP - https://www.dropbox.com/s/wmbz005aqs52r9j/G4_Rootbeta1.zip?dl=0
7z - https://www.dropbox.com/s/tnmnbak62zdrgu6/G4_Rootbeta1.7z?dl=0
hytin said:
cant download G4_Rootbeta1.zip
Click to expand...
Click to collapse
New link... I uploaded to drop box. Google drive acts funny when it come to certain files.
geoff5093 said:
This is the error we get when attempting to download it:
Code:
Sorry, this file is infected with a virus
Only the owner is allowed to download infected files.
EDIT: See my post below for a copy of the ZIP
Click to expand...
Click to collapse
New link available
do we still need to enable oem unlock?
Sent from my LG-H815 using Tapatalk 2
deejay6901 said:
do we still need to enable oem unlock?
Sent from my LG-H815 using Tapatalk 2
Click to expand...
Click to collapse
I think I am unlock is only for unlocking the boot loader not rooting
So I tried this on the H811 (T-Mobile) version.
Everything worked just as described UNTIL the part where I needed to run the root script.
After I paste the SH command, it thinks for a moment, and returns me to the # line...
Not sure how to continue from here, but will be happy to be a guinea pig if someone can tell me what to try.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
madhouze said:
So I tried this on the H811 (T-Mobile) version.
Everything worked just as described UNTIL the part where I needed to run the root script.
After I paste the SH command, it thinks for a moment, and returns me to the # line...
Not sure how to continue from here, but will be happy to be a guinea pig if someone can tell me what to try.
Click to expand...
Click to collapse
Same here on H815 ?!
My Bootloader ist Locked. Is that the reason ??? Do i have to unlock it ?
it´s for the G3 on 5.02 not lollipop 5.1
hytin said:
it´s for the G3 on 5.02 not lollipop 5.1
Click to expand...
Click to collapse
This is modified for g4
Masta_Gee81 said:
Same here on H815 ?!
My Bootloader ist Locked. Is that the reason ??? Do i have to unlock it ?
Click to expand...
Click to collapse
Try doing the command without dummy1
Hi macdaddie87
Thanks for your job! :good:
Looking forward to people with Verizon giving this a shot first!
macdaddie87 said:
Try doing the command without dummy1
Click to expand...
Click to collapse
Same result . Nothing happens ?
this is my input : sh /data/local/tmp/root_g4.sh/data/local/tmp/UPDATE-SuperSU-v2.46.zip /data/local/tmp/busybox
it stays on # nothing more?!
looks like device is not attaching when connected to download mode even if adb.exe devices is executed
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Disclaimer : This thread is ONLY for developers/Users who wish to run GNU/Linux on their device and improve the port . PC is required to flash the images. Read from available documentation given .
ALPHA BUILDS!
Calls work only on ubuntu touch as of now:
Ubuntu touch
For testing images : https://forums.ubports.com/topic/3702/yu-black-garlic scroll to Install section
For fixing recording without much hasssle ,
connect to internet,
Code:
sudo mount -o remount,rw /
, enter root passwd
then,
Code:
sudo apt-get update && sudo umount /lib/udev/rules.d/70-android.rules && sudo umount /usr/share/apparmor/hardware/graphics.d/apparmor-easyprof-ubuntu_android && sudo umount /usr/share/apparmor/hardware/video.d/apparmor-easyprof-ubuntu_android && sudo apt-mark hold qtubuntu-android && sudo ubports-qa install xenial_-_gst-droid
accept ,
reboot
Code:
wget https://static.peat-network.xyz/junk/ubports/com.ubuntu.camera_3.1.1+gstdroid2_armhf.click && pkcon install-local --allow-untrusted com.ubuntu.camera_3.1.1+gstdroid2_armhf.click
Multirom config : noughatmultirom.zip . twrp (not my favorite , works with ubuntu touch only as primary rom,secondaries are noughat)
KDE Plasma Mobile
Haven't built images for it in a while.. Maybe after ubports porting is done in freetime.
Status of the port : https://github.com/Halium/projectmanagement/issues/123
Manifest : https://github.com/Halium/halium-devices/pull/146/commits/75a85c86b8abae5bfba322c907bc431f2a49548b
System and hybris-boot : FOLDER
Pick the latest rootfs from the Plasma mobile website also in docs
Type of Rootfs to use : Plasma-edge-caf rootfs (armhf)
Installation guide: http://docs.halium.org/en/latest/po...sma-mobile.html#install-rootfs-and-system-img
The ubuntu folder isn't working
Xpl0it_U said:
The ubuntu folder isn't working
Click to expand...
Click to collapse
Replaced broken link
Ok, thanks
can't boot it, stuck at bootlogo, can telnet to the phone tho
Xpl0it_U said:
can't boot it, stuck at bootlogo, can telnet to the phone tho
Click to expand...
Click to collapse
Which rootfs one did you use?
The port is past the telnet stage .. seems like rootfs is not properly extracted , has everything run correctly with halium-install?
pbteja said:
Which rootfs one did you use?
Click to expand...
Click to collapse
ubuntu xenial armhf
Xpl0it_U said:
ubuntu xenial armhf
Click to expand...
Click to collapse
And the recovery needs to have insecure adb, use this: https://www.androidfilehost.com/?fid=6006931924117909377 or treble twrp both allow adb debugging in recovery mode
pbteja said:
And the recovery needs to have insecure adb, use this: https://www.androidfilehost.com/?fid=6006931924117909377 or treble twrp both allow adb debugging in recovery mode
Click to expand...
Click to collapse
ok, i'll try it tommorrow
alright, it worked, is there any way to get or port anbox to this phone?
btw needs some optimization, this is slow af sometimes
Xpl0it_U said:
alright, it worked, is there any way to get or port anbox to this phone?
btw needs some optimization, this is slow af sometimes
Click to expand...
Click to collapse
Anbox: https://gist.github.com/Vince1171/69cdcb2e90f2c70e3ee24de93da8caac
Bugginess is due to services crashing in the background and also its not 64bit rootfs primarily media-hub and location that 'might' get fixed when somebody gets apparmor working...
Thanks for the guide, any way to fix those crashes?
Xpl0it_U said:
Thanks for the guide, any way to fix those crashes?
Click to expand...
Click to collapse
Yeah everything should work eventually, its mostly app-armor, the system expects it and its not in kernel ... so things can be fixed in linuxy way ofc through terminal for example gps is a permission issue (idk why) but have to dip into sources and rebuild the system and make our own device adaptation
I think I found something that could help with apparmor:
http://www.mardy.it/blog/2019/07/notes-on-porting-the-samsung-j3-to-halium-+-ubports.html
Scroll where it says "building the kernel", it mentions something about enabling apparmor
Xpl0it_U said:
I think I found something that could help with apparmor:
http://www.mardy.it/blog/2019/07/notes-on-porting-the-samsung-j3-to-halium-+-ubports.html
Scroll where it says "building the kernel", it mentions something about enabling apparmor
Click to expand...
Click to collapse
Hello, apparmor has been fixed... so far
No camera and no mtp usb , no flashlight , rest of hardware works
The build has some bugs like can't change volume during calls and similar small things that matter for daily use case... and then there is an overall slowness of the os ...
I'm doing multiple builds everyday trying to fix camera , if you want to try and use the latest build i can upload it for you
That would be cool, the only thing that changes is the hybris-boot.img, right?
Xpl0it_U said:
That would be cool, the only thing that changes is the hybris-boot.img, right?
Click to expand...
Click to collapse
Yes and system image as well, bunch of vendor libs have been added
pbteja said:
Yes and system image as well, bunch of vendor libs have been added
Click to expand...
Click to collapse
Aight, if there's a tutorial of how to update the device tree and the kernel and build it so you don't have to upload it would be better (if it doesn't take too much to build)
deleted
I have the same specs, so I'll try future builds, as It's faster than downloading