Hello,
I have been trying to make my Samsung Galaxy Note 3 with Lineage OS boot automatically when the charger is connected instead of booting to the battery charging screen.
Since its a Samsung phone it doesn't have fastboot... it has ODIN instead. So using fastboot no-charge oem cant be done. from what i have googled.
I have also tried locating a file called "lpm" in /system/bin but lineage OS doesn't have that file, since i think its Samsung specific.
Lastly i tried adding the lpm service, and modifying the boot.img > init.rc to add the service to the "on charge" event. I found that the Samsung official ROM has a service configured like this:
Code:
service lpm /system/bin/lpm
class charger
critical
so i copy pasted this into the init.rc file of lineage OS and then created the file "lpm" under /system/bin and edit it to this:
Code:
#!/system/bin/sh
/system/bin/reboot
This didn't work, and i cant find a way to see if the file is being executed at all.
My question is, does anyone know how to make lineage OS boot automatically, from being powered off, instead of going to the battery charging boot screen?
Thanks Oliver
oliver92 said:
Hello,
I have been trying to make my Samsung Galaxy Note 3 with Lineage OS boot automatically when the charger is connected instead of booting to the battery charging screen.
Since its a Samsung phone it doesn't have fastboot... it has ODIN instead. So using fastboot no-charge oem cant be done. from what i have googled.
I have also tried locating a file called "lpm" in /system/bin but lineage OS doesn't have that file, since i think its Samsung specific.
Lastly i tried adding the lpm service, and modifying the boot.img > init.rc to add the service to the "on charge" event. I found that the Samsung official ROM has a service configured like this:
Code:
service lpm /system/bin/lpm
class charger
critical
so i copy pasted this into the init.rc file of lineage OS and then created the file "lpm" under /system/bin and edit it to this:
Code:
#!/system/bin/sh
/system/bin/reboot
This didn't work, and i cant find a way to see if the file is being executed at all.
My question is, does anyone know how to make lineage OS boot automatically, from being powered off, instead of going to the battery charging boot screen?
Thanks Oliver
Click to expand...
Click to collapse
Hi,
did you ever get this to work? I'm trying to do the same on a huawei pra-lx1 ...
tiagofalves said:
Hi,
did you ever get this to work? I'm trying to do the same on a huawei pra-lx1 ...
Click to expand...
Click to collapse
You guys solved this? I've been trying to figure this out too.
If you go to system folder, then bin folder, there is a file sysinit. Inside it reads:
#! /system/bin/sh
export PATH=/sbin: /system/sbin: /system/bin: /system/xbin
for i in /system/etc/init.d/*; do
if [ -x $i ]; then
/system/bin/log -t sysinit Running $i
fi
done
Do you think this is about booting?
guys is this still open?
I would like to make my i9300 auto boot the same way. cant find the lpm file.
thank you
For whom it may concern, a way to autoboot a device on lineage is to edit the init.rc file in boot.img. I tried this on a motorola motoG 4g. In /init.rc there is a section titled charger. While on charger, you have to add class stop charger trigger late init.
# Healthd can trigger a full boot from charger mode by signaling this
# property when the power button is held.
on property:sys.boot_from_charger_mode=1
class_stop charger
trigger late-init
on charger
class_start charger
++ class_stop charger
++ trigger late-init
The same init.rc I found on Samsaung Galaxy S2 with lines 14.1, so there is a chance here as well.
Experience sharing
Peenoyako said:
You guys solved this? I've been trying to figure this out too.
Click to expand...
Click to collapse
Almost no other methods were successful on MIUI 10 Redmi Note 4x (Snapdragon) , which is already bootloader unlocked, rooted condition.
However after updation of
(1) existing TWRP_3.2.1-5_mido was updated with [Mido][Material][Twrp-Treble][3.2.1-10].zip to facilitate wiping
(ii) Total wipe was carried out from above latest twrp (wipe>Advance wipe>selected all like Delvik / ART Cache, System, Vendor, Data, Internal Storage and Cache>swiped to wipe
(now only 2 things left on phone fastboot and recovery
(iii) Installed lineage 15.1 (mido_lineage-15.1-20180807-nightly-mido-signed.zip) and gapps (mido_open_gapps-arm64-8.1-nano-20180812.zip)
rebooted and initial steps of phone setup was completed
Rebooted to TWRP and installed addonsu-15.1-arm64-signed.zip to root it. It may be noted for this type , root to be enabled at developer options.
(iv)LOS Boot image was extracted through TWRP (Backup> select boot > swiped to Backup , it backed up the boot file at TWRP folder on external SD card. The name of file is boot.emmc.win (64MB)
(v) I have renamed the file to boot and type to img (boot.img)
(vi) i have extracted the contents of the above boot.img with the help of Android.Image.Kitchen.v3.4-Win32 [we have to copy the above boot.img (it should should have word boot in the name and img type to be get recognized by the program ) to Android.Image.Kitchen.v3.4-Win32 folder ] on windows 10 pro 64bit
(vii) i have modified the init.rc at "on chrager" , after modification (including existing+added looks like below)
on charger
class_start charger
class_stop charger
trigger late-init
(viii) repacked it with the same windows program Android.Image.Kitchen.v3.4-Win32 , it will be repacked in the same directory with a name" image-new.img "
(xi) Transferred it to the phone and installed it with TWRP (install>install image> select above "image-new.img" >select boot > swiped to install
Now the phone is booting automatically, if charger is connected (success).
But further work is needed to address important / critical situation like the phone is switched off while use (e.g. while talking on phone with some one while walking little away from office or home or excessive use due excessive follow ups, we will keep it on charging but there is some possibility to forget for considerable amount of time. To avoid this, if the phone is boot up in auto after some 2 or 3 % of charge (like iphones) it will be great. Further if some body wants shutdown and charge it (or it can be kept in silence also), simply charger may be connected before shutdown and it should not wake up in auto.
Most of the credit goes to many netgens , it is only the experience sharing without any responsibility since if not understood properly , if not done planned way, carefully, accurately relevant to phone make , model , model no , sub no , sub spec as applicable , within no time data loss and / or phone bricking may happen.
Another Experience sharing with Redmi Note 4 ( 4x )Snapdragon Auto Boot on Charger
knreddy said:
Almost no other methods were successful on MIUI 10 Redmi Note 4x (Snapdragon) , which is already bootloader unlocked, rooted condition.
However after updation of
(1) existing TWRP_3.2.1-5_mido was updated with [Mido][Material][Twrp-Treble][3.2.1-10].zip to facilitate wiping
(ii) Total wipe was carried out from above latest twrp (wipe>Advance wipe>selected all like Delvik / ART Cache, System, Vendor, Data, Internal Storage and Cache>swiped to wipe
(now only 2 things left on phone fastboot and recovery
(iii) Installed lineage 15.1 (mido_lineage-15.1-20180807-nightly-mido-signed.zip) and gapps (mido_open_gapps-arm64-8.1-nano-20180812.zip)
rebooted and initial steps of phone setup was completed
Rebooted to TWRP and installed addonsu-15.1-arm64-signed.zip to root it. It may be noted for this type , root to be enabled at developer options.
(iv)LOS Boot image was extracted through TWRP (Backup> select boot > swiped to Backup , it backed up the boot file at TWRP folder on external SD card. The name of file is boot.emmc.win (64MB)
(v) I have renamed the file to boot and type to img (boot.img)
(vi) i have extracted the contents of the above boot.img with the help of Android.Image.Kitchen.v3.4-Win32 [we have to copy the above boot.img (it should should have word boot in the name and img type to be get recognized by the program ) to Android.Image.Kitchen.v3.4-Win32 folder ] on windows 10 pro 64bit
(vii) i have modified the init.rc at "on chrager" , after modification (including existing+added looks like below)
on charger
class_start charger
class_stop charger
trigger late-init
(viii) repacked it with the same windows program Android.Image.Kitchen.v3.4-Win32 , it will be repacked in the same directory with a name" image-new.img "
(xi) Transferred it to the phone and installed it with TWRP (install>install image> select above "image-new.img" >select boot > swiped to install
Now the phone is booting automatically, if charger is connected (success).
But further work is needed to address important / critical situation like the phone is switched off while use (e.g. while talking on phone with some one while walking little away from office or home or excessive use due excessive follow ups, we will keep it on charging but there is some possibility to forget for considerable amount of time. To avoid this, if the phone is boot up in auto after some 2 or 3 % of charge (like iphones) it will be great. Further if some body wants shutdown and charge it (or it can be kept in silence also), simply charger may be connected before shutdown and it should not wake up in auto.
Most of the credit goes to many netgens , it is only the experience sharing without any responsibility since if not understood properly , if not done planned way, carefully, accurately relevant to phone make , model , model no , sub no , sub spec as applicable , within no time data loss and / or phone bricking may happen.
Click to expand...
Click to collapse
The above procedure is successful on the following ROM (similar to LOS15.1 , used magisk 16.7 or higher for rooting)
xiaomi.eu_multi_HMNote4X_8.12.20_v10-7.0.zip
downloaded from
https://excellmedia.dl.sourceforge..../xiaomi.eu_multi_HMNote4X_8.12.20_v10-7.0.zip
knreddy said:
Almost no other methods were successful on MIUI 10 Redmi Note 4x (Snapdragon) , which is already bootloader unlocked, rooted condition.
However after updation of
(1) existing TWRP_3.2.1-5_mido was updated with [Mido][Material][Twrp-Treble][3.2.1-10].zip to facilitate wiping
(ii) Total wipe was carried out from above latest twrp (wipe>Advance wipe>selected all like Delvik / ART Cache, System, Vendor, Data, Internal Storage and Cache>swiped to wipe
(now only 2 things left on phone fastboot and recovery
(iii) Installed lineage 15.1 (mido_lineage-15.1-20180807-nightly-mido-signed.zip) and gapps (mido_open_gapps-arm64-8.1-nano-20180812.zip)
rebooted and initial steps of phone setup was completed
Rebooted to TWRP and installed addonsu-15.1-arm64-signed.zip to root it. It may be noted for this type , root to be enabled at developer options.
(iv)LOS Boot image was extracted through TWRP (Backup> select boot > swiped to Backup , it backed up the boot file at TWRP folder on external SD card. The name of file is boot.emmc.win (64MB)
(v) I have renamed the file to boot and type to img (boot.img)
(vi) i have extracted the contents of the above boot.img with the help of Android.Image.Kitchen.v3.4-Win32 [we have to copy the above boot.img (it should should have word boot in the name and img type to be get recognized by the program ) to Android.Image.Kitchen.v3.4-Win32 folder ] on windows 10 pro 64bit
(vii) i have modified the init.rc at "on chrager" , after modification (including existing+added looks like below)
on charger
class_start charger
class_stop charger
trigger late-init
(viii) repacked it with the same windows program Android.Image.Kitchen.v3.4-Win32 , it will be repacked in the same directory with a name" image-new.img "
(xi) Transferred it to the phone and installed it with TWRP (install>install image> select above "image-new.img" >select boot > swiped to install
Now the phone is booting automatically, if charger is connected (success).
But further work is needed to address important / critical situation like the phone is switched off while use (e.g. while talking on phone with some one while walking little away from office or home or excessive use due excessive follow ups, we will keep it on charging but there is some possibility to forget for considerable amount of time. To avoid this, if the phone is boot up in auto after some 2 or 3 % of charge (like iphones) it will be great. Further if some body wants shutdown and charge it (or it can be kept in silence also), simply charger may be connected before shutdown and it should not wake up in auto.
Most of the credit goes to many netgens , it is only the experience sharing without any responsibility since if not understood properly , if not done planned way, carefully, accurately relevant to phone make , model , model no , sub no , sub spec as applicable , within no time data loss and / or phone bricking may happen.
Click to expand...
Click to collapse
Thanks for this but my nose bled from reading this. I'm not really good in programming stuff. Hopefully you or somebody could post a video in youtube for the step by step process. I might understand this with visual instructions. If this does work then you've done a great job finding a solution for this.
I tried editing init.rc and another method below, both do turn on with usb power, but get stuck in the boot animation. It seems it doesn't complete loading. Unplugged the power, and reboot the tablet, and it will turn on normal and get past the boot screen.
The other method I tried, we know "on charge" loads up /sbin/charger. So I changed that file with
Code:
#!/system/bin/sh
#Skip offline charge and start device if enough juice on battery. If low on battery do offline charge
CAPACITY=$(cat /sys/class/power_supply/battery/capacity)
MIN_CAPACITY=15
echo $CAPACITY
if [ $((CAPACITY)) -gt $MIN_CAPACITY ]
then
/system/bin/reboot
fi
/system/sbin/charger_orig
Same thing. Boots up on usb power, but gets stuck in the lineage boot animation.
OK so I got it to work.
1. Extracted Boot image through TWRP (Backup> select boot > swiped to Backup)
2. Rename boot.emmc.win to boot.img
3. Copy boot.img to the root dir of the program Android.Image.Kitchen, and run "unpackimg.bat"
4. Open up folder /ramdisk/sbin/ and rename "charger" to "charger_orig"
4. Create "charger" and put in
Code:
#!/system/bin/sh
#Skip offline charge and start device if enough juice on battery. If low on battery do offline charge
CAPACITY=$(cat /sys/class/power_supply/battery/capacity)
MIN_CAPACITY=5
if [ $CAPACITY -gt $MIN_CAPACITY ]
then
sleep 1
/system/bin/reboot
fi
/sbin/charger_orig
4. Go back to the root of Android.Image.Kitchen and run "repackimg.bat"
5. Take "image-new.img" and copy to phone
5. Install img with TWRP (install>install image> select above "image-new.img" >select boot > swiped to install)
MolsonB said:
OK so I got it to work.
1. Extracted Boot image through TWRP (Backup> select boot > swiped to Backup)
2. Rename boot.emmc.win to boot.img
3. Copy boot.img to the root dir of the program Android.Image.Kitchen, and run "unpackimg.bat"
4. Open up folder /ramdisk/sbin/ and rename "charger" to "charger_orig"
4. Create "charger" and put in
Code:
#!/system/bin/sh
#Skip offline charge and start device if enough juice on battery. If low on battery do offline charge
CAPACITY=$(cat /sys/class/power_supply/battery/capacity)
MIN_CAPACITY=5
if [ $CAPACITY -gt $MIN_CAPACITY ]
then
sleep 1
/system/bin/reboot
fi
/sbin/charger_orig
4. Go back to the root of Android.Image.Kitchen and run "repackimg.bat"
5. Take "image-new.img" and copy to phone
5. Install img with TWRP (install>install image> select above "image-new.img" >select boot > swiped to install)
Click to expand...
Click to collapse
Hey,
I tried to open charger file on Windows 10 (with SublimeText & Notepad++) but always get weird characters.. So I have a fear that when I create the new charger file it won't work, as it is not encoded the same.. Maybe you can attach the new charger file..? Thanks you very much..
Caught in bootloop, is rooting mandatory?
knreddy said:
Almost no other methods were successful on MIUI 10 Redmi Note 4x (Snapdragon) , which is already bootloader unlocked, rooted condition.
However after updation of
(1) existing TWRP_3.2.1-5_mido was updated with [Mido][Material][Twrp-Treble][3.2.1-10].zip to facilitate wiping
(ii) Total wipe was carried out from above latest twrp (wipe>Advance wipe>selected all like Delvik / ART Cache, System, Vendor, Data, Internal Storage and Cache>swiped to wipe
(now only 2 things left on phone fastboot and recovery
(iii) Installed lineage 15.1 (mido_lineage-15.1-20180807-nightly-mido-signed.zip) and gapps (mido_open_gapps-arm64-8.1-nano-20180812.zip)
rebooted and initial steps of phone setup was completed
Rebooted to TWRP and installed addonsu-15.1-arm64-signed.zip to root it. It may be noted for this type , root to be enabled at developer options.
(iv)LOS Boot image was extracted through TWRP (Backup> select boot > swiped to Backup , it backed up the boot file at TWRP folder on external SD card. The name of file is boot.emmc.win (64MB)
(v) I have renamed the file to boot and type to img (boot.img)
(vi) i have extracted the contents of the above boot.img with the help of Android.Image.Kitchen.v3.4-Win32 [we have to copy the above boot.img (it should should have word boot in the name and img type to be get recognized by the program ) to Android.Image.Kitchen.v3.4-Win32 folder ] on windows 10 pro 64bit
(vii) i have modified the init.rc at "on chrager" , after modification (including existing+added looks like below)
on charger
class_start charger
class_stop charger
trigger late-init
(viii) repacked it with the same windows program Android.Image.Kitchen.v3.4-Win32 , it will be repacked in the same directory with a name" image-new.img "
(xi) Transferred it to the phone and installed it with TWRP (install>install image> select above "image-new.img" >select boot > swiped to install
Now the phone is booting automatically, if charger is connected (success).
But further work is needed to address important / critical situation like the phone is switched off while use (e.g. while talking on phone with some one while walking little away from office or home or excessive use due excessive follow ups, we will keep it on charging but there is some possibility to forget for considerable amount of time. To avoid this, if the phone is boot up in auto after some 2 or 3 % of charge (like iphones) it will be great. Further if some body wants shutdown and charge it (or it can be kept in silence also), simply charger may be connected before shutdown and it should not wake up in auto.
Most of the credit goes to many netgens , it is only the experience sharing without any responsibility since if not understood properly , if not done planned way, carefully, accurately relevant to phone make , model , model no , sub no , sub spec as applicable , within no time data loss and / or phone bricking may happen.
Click to expand...
Click to collapse
Hey man, I've done everything you said except rooting part. System now stuck at bootloader. Why is rooting needed here? Do you think rooting will fix the issue?
Update: Successful, with another method!! Copied reboot file from system/bin to and paste to /ramdisk/sbin/ and rename "charger". Remove or rename the original charger file. Device will boot and then reboot to normal!
xxxwatari said:
Hey man, I've done everything you said except rooting part. System now stuck at bootloader. Why is rooting needed here? Do you think rooting will fix the issue?
Update: Successful, with another method!! Copied reboot file from system/bin to and paste to /ramdisk/sbin/ and rename "charger". Remove or rename the original charger file. Device will boot and then reboot to normal!
Click to expand...
Click to collapse
what file you copy? reboot? and you paste reboot into ramdisk/sbin? rename charger to charger_old? rename reboot to charger?
is it right?
ahhl said:
what file you copy? reboot? and you paste reboot into ramdisk/sbin? rename charger to charger_old? rename reboot to charger?
is it right?
Click to expand...
Click to collapse
Yes, there is a file named `reboot` in system/bin to and paste to /ramdisk/sbin/ where you can see `charger` file. You can rename the original `charger` file to anything or even delete it. Rename `reboot` to `charger` so when you plug in, the device triggers reboot instead of charging display. But it takes much longer for boot to complete this way
My boot.emmc.win file is empty after unpacking? any tips.
MolsonB said:
OK so I got it to work.
1. Extracted Boot image through TWRP (Backup> select boot > swiped to Backup)
2. Rename boot.emmc.win to boot.img
3. Copy boot.img to the root dir of the program Android.Image.Kitchen, and run "unpackimg.bat"
4. Open up folder /ramdisk/sbin/ and rename "charger" to "charger_orig"
4. Create "charger" and put in
Code:
#!/system/bin/sh
#Skip offline charge and start device if enough juice on battery. If low on battery do offline charge
CAPACITY=$(cat /sys/class/power_supply/battery/capacity)
MIN_CAPACITY=5
if [ $CAPACITY -gt $MIN_CAPACITY ]
then
sleep 1
/system/bin/reboot
fi
/sbin/charger_orig
4. Go back to the root of Android.Image.Kitchen and run "repackimg.bat"
5. Take "image-new.img" and copy to phone
5. Install img with TWRP (install>install image> select above "image-new.img" >select boot > swiped to install)
Click to expand...
Click to collapse
Did you used Magisk for this to root your device?
Auto shutdown of phone on disconnection of charger plug ( for Car) etc
knreddy said:
The above procedure is successful on the following ROM (similar to LOS15.1 , used magisk 16.7 or higher for rooting)
xiaomi.eu_multi_HMNote4X_8.12.20_v10-7.0.zip
downloaded from
https://excellmedia.dl.sourceforge..../xiaomi.eu_multi_HMNote4X_8.12.20_v10-7.0.zip
Click to expand...
Click to collapse
https://forum.xda-developers.com/android/apps-games/app-automate-t2870633/post80126909#post80126909
MolsonB said:
OK so I got it to work.
1. Extracted Boot image through TWRP (Backup> select boot > swiped to Backup)
2. Rename boot.emmc.win to boot.img
3. Copy boot.img to the root dir of the program Android.Image.Kitchen, and run "unpackimg.bat"
4. Open up folder /ramdisk/sbin/ and rename "charger" to "charger_orig"
4. Create "charger" and put in
Code:
#!/system/bin/sh
#Skip offline charge and start device if enough juice on battery. If low on battery do offline charge
CAPACITY=$(cat /sys/class/power_supply/battery/capacity)
MIN_CAPACITY=5
if [ $CAPACITY -gt $MIN_CAPACITY ]
then
sleep 1
/system/bin/reboot
fi
/sbin/charger_orig
4. Go back to the root of Android.Image.Kitchen and run "repackimg.bat"
5. Take "image-new.img" and copy to phone
5. Install img with TWRP (install>install image> select above "image-new.img" >select boot > swiped to install)
Click to expand...
Click to collapse
Doesn't seem to work on pie.. Or maybe im missing some things
jprimero15 said:
Doesn't seem to work on pie.. Or maybe im missing some things
Click to expand...
Click to collapse
Maybe the tool you're using is older than Pie?
Related
There are some noob tutorial around, but none of them specifically says
anything about 4.5.141 unless you dig quite some pages at the end of the
threads. This post is not going to be a complete guide or tutorial, nor it is
going to be a detailed how-to. It will be a breif how-to that tells you what
works on 4.5.141 and give you some confidence when rooting and unlocking
4.5.141.
Before flashing a new rom on your stock atrix, you should understand the risks
of losing data, voided warranty, malfunction of the new rom, or even get your
phone hard bricked. if you were worried, and still are worried after reading
many XDA threads, a new rom is not for you. The stock ROM is not that bad.
Enough talk, let's get to the point of how to get CM7.2RC2 running on your
phone.
Table of Contents
1 PRE-CONDITIONS
2 BRIEF PROCESS
3 DETAILS
1 PRE-CONDITIONS
Atrix phone.
Stock rom running 4.5.141, stock bootloader.
If you have rooted your phone, or have unlocked your bootloader, just skip
the corresponding step.
If you are running versions below 4.5.141, there are ready-made scripts to
do things.
I myself use an SD card, but I don't think it's necessary to flash
CM7.2RC2 or gapps. (Please correct me if I'm wrong.)
Windows OS.
Motorola only offers phone drivers to Windows OS.
Internet access.
You will need to download files from some file sharing websites.
USB Cable.
For connecting your phone to Windows PC and run commands.
Know how to run a command line application in Windows.
I won't tell you how to use unzip, cmd.exe, and cd commands. I won't tell
you about PATH, directorys and file names. If you are looking for a
word-by-word tutorial, stop now.
2 BRIEF PROCESS
Download CM7.2RC2 zip file and gapps.
Backup important user data.
Root your phone so that you can run Titan Backup.
Backup all your data, including app data that you wish to keep.
Unlock bootloader.
[Root again &] flash recovery. //read why I root again in details.
Flash rom and gapps.
Config CM7.2, restore app data.
3 DETAILS
Before I start, I need to say I only own an AT&T atrix, other atrix could have
some differences, please read the threads that I refer to to get more
information.
Download CM7.2RC2 zip file and gapps.
CM7.2RC2
http://download.cyanogenmod.com/?device=olympus
download update-cm-7.2.0-RC2-olympus-signed.zip
gapps
http://wiki.cyanogenmod.com/wiki/Latest_Version/Google_Apps
download the one for CyanogenMod 7.
Store CM7.2RC2 to your internal storage.
Store gapps to your SD card. [I don't know why.]
Store them to both place if you are unsure. [That's what I did.]
On stock rom, internal storage is mounted at mnt/sdcard, SD card is
mounted at mnt/sdcard-ext.
# Could someone tell me why where to store the zip file matters?
# I see Romracer's Recovery can flash zip file in either place.
Back up important user data.
Everyone has different things to back up.
My list includes:
Contacts.
App settings & data
if the app support "backup to SD card" alike function, do it.
if the app support syncing, do it.
this includes syncing all items on google account.
for other apps, you may use Titan Backup later to backup data.
bookmarks.
ssh keys stored on phone.
icons on Home screen.
a list of installed apps.
Photos/Camrecords.
Musics
PDFs
network and VPN settings
I purposely do not mention apps I am using to avoid advertising.
Root your phone so that you can run Titan Backup.
I don't think rooting your phone is necessary at this stage, but I did it
in order to use Titan Backup. If you have nothing worth backing up, you may
skip this. (Please tell me if I'm wrong here.)
[install Motorola USB drivers]
http://www.motorola.com/Support/US-EN/Support-Homepage/Software_and_Drivers/USB-and-PC-Charging-Drivers
download the all-in-one driver and install it.
[download the tools and preinstall.img file.]
http://hotfile.com/dl/147091460/bb5f4c5/moto-fastboot-win32.7z.html
download the 7z file, and unzip it using winrar or 7-zip.
7-zip is free software, google it for download.
boot to fastboot mode.
Power off your phone. hold Volume Down, press Power.
when the screen show fastboot, press Volume Up to enter fastboot mode.
(Press Volume Down will cycle all mode choices, press Volume Up selects the
mode that is shown on the screen.)
flash preinstall, reboot.
unzip the 7z file you downloaded, start cmd.exe and go to that dir.
connect phone to Windows PC using usb cable.
run these commands:
Code:
moto-fastboot flash preinstall preinstall.img
moto-fastboot reboot
replace /system/bin/su with /preinstall/su and set permission to 6755.
when phone is fully rebooted, enable USB debugging.
Settings > Application > Development > USB debugging
Disconnect and reconnect the cable if windows does not find your phone.
run these commands:
Code:
adb shell
/preinstall/dosu
/bin/mount /system -o remount,rw
cp /preinstall/su /system/bin/su
chmod 6755 /system/bin/su
PATH=/system/bin:$PATH pm install /preinstall/Superuser.apk
exit
exit
Notes:
If "adb shell" fails, try disconnect and reconnect cable.
On success, it shows "$" on a new line.
when running "/preinstall/dosu", you can ignore this error:
"bash: groups: command not found".
done.
now you are rooted, you can disconnect USB cable if you wish.
Backup all your data, including app data that you wish to keep.
More backups won't hurt. Now it's time to backup all your apps and files.
Now that you are rooted, you can install Titan Backup and backup the
non-system apps. Back up other apps as you wish. I'm completely new to
Titan Backup. I only used it to backup non-system apps, for the purpose of
restoring app data later.
Note that CM7.2RC2 is based on android 2.3.7, while 4.5.141 is based on
android 2.3.6. I did not try to restore 2.3.6 stock app data to 2.3.7
myself to avoid any possible error.
If for some reason, Titan Backup told you you are not rooted, just do the
root step again. It does no harm to your phone.
Unlock bootloader.
[install motorola USB drivers]
if you haven't done this. Do it now. see download link at step 3.
[download RSD, fastboot, and the small 1MB SBF file.]
moto-fastboot is included in the 7z file in step 3.
RSDLite and the 1MB SBF file download:
http://forum.xda-developers.com/showthread.php?t=1136261
scroll to the "Unlock:" section.
"Unlocker only SBFs - These small 1mb SBF files will get your phone ready
to fasboot oem unlock. They are the files most people should use."
Notice that the 1MB SBF file is different for ATT and other atrix.
Choose the correct version.
Power off atrix. take out microSD card and sim card. [not sure why]
Flash the small SBF file using RSD Lite.
Unzip the downloaded small SBF file.
Install RSDLite.
Boot phone to RSD mode. Connect USB cable. Run RSD Lite on Windows PC,
select the unzipped .sbf file, press Start.
[I guess you know how to boot to different modes now. But just in case,
first Power off your phone, hold Volume Down and press Power, when screen
show "fastboot", press Volume Down to cycle between choices, when it show
"RSD", press Volume Up to confirm.]
The phone will disconnect and connect again and may goto other modes
automatically. Watch the progress shown in RSDLite window.
Here is a side story: while I'm flash this, the phone switch to fastboot
mode automatically, when RSDLite is waiting for the phone to go to BP
pass ?? mode, at progress 98%. I didn't notice it is still waiting for
the phone, when I see it goes to fastboot, I just run the fastboot oem
unlock command in the next step, and the phone get unlocked successfully,
then I reboot it with fastboot reboot. But when the reboot finished, the
phone asks me to setup moto blur and google account. apps and user
configs are gone. But I don't care, becaue I have all important things
backed up. I just skipped most of the setup because I'm going to flash a
new ROM. So it looks like the phone did a factory reset after the
unlock. I also lost root after this. Could someone tell me is this
expected behavior of a normal unlock, or is this a consequence that I
failed to let RSDLite work to the full 100% progress?
Do fastboot oem unlock.
Boot phone to fastboot mode. connect USB cable.
Switch to the dir that contains moto-fastboot, then run these commands:
Code:
moto-fastboot oem unlock //It will print your device ID.
moto-fastboot oem unlock <your-device-ID>
moto-fastboot reboot
Done.
When your phone reboot, you will notice the unlocked red text on motorola
screen.
I hope you did not get a factory reset. But if it did, don't panic.
[Root again &] flash recovery.
I definitely do not want to root again here, but my phone looks as if it
has got a factory reset when I was unlocking the bootloader. And I lose
root as a result. I could just go ahead and flash recovery, but it turns
out I need to delete a file in /system partition before I can boot into
Romracer's Recovery. To delete that file, I need root.
[download Romracer's Recovery]
http://forum.xda-developers.com/showthread.php?t=1204500
You can download any of the recovery file listed there under "ALL USERS".
To root again, just redo step 3.
Rename (or delete) /system/etc/install-recovery.sh using a root file
manager.
When you are fully rebooted, install a root file manager (for example, ES
file explorer), and rename /system/etc/install-recovery.sh to
install-recovery.sh.bak
Until you rename or delete this file, you can't boot into the recovery
you are going to flash. Because the recovery file will be replaced when
the phone boots.
flash recovery.
If you downloaded zip file, unzip it.
Then copy img file to the dir that contains moto-fastboot.exe.
Boot phone to fastboot mode, connect phone to Windows PC, go to
moto-fastboot dir, run these commands:
Code:
moto-fastboot erase recovery
moto-fastboot flash recovery recovery-atrix5.img
moto-fastboot reboot
Flash rom and gapps.
Preparation
If your battery is low, replace battery now. There is no stop and resume
support when making a backup or flashing a new ROM.
If you have taken out microSD card and sim card when unlocking
bootloader, you should put it back now.
Boot into recovery mode.
Inside recovery, press Volume Up and Volume Down to go up and down.
Press Menu soft key to confirm.
Do a backup.
Go to Backup & Restore and create a backup.
You will be asked whether to include webtop in the backup.
If you do, expect the backup to take a long time. (~30 minutes)
Flash CM7.2RC2 and gapps.
In recovery menu, choose install zip file from SD card.
Locate the CM7.2 zip file, and confirm flash.
When done, you need to wipe some data/cache, confirm wipe in each step:
wipe data/factory reset
wipe cache partition
Advanced > wipe Dalvik Cache
When asked whether to include sdcard-ext, I chose yes.
Done.
You are ready to reboot the CM7.2RC2.
Config CM7.2, restore app data.
Some configs you may want to tweak:
Home Screen > Menu > More > Wallpaper
CM settings > Display Settings > Screen-off animation > off
Display > Brightness > [auto]
Display > Animation > none
Date & Time > Select time zone
Sound > Phone ringtone
Sound > Notification ringtone
Sound > Haptic feedback > off //vibrate when pressing soft keys
CM settings > Sounds > Mute camera shutter
CM settings > Input > Long-press menu > soft keyboard
Some first impressions of built-in apps and the CM7.2 ROM.
The Motorola stock quickoffice is gone. you might want to instal Adobe
Reader for PDFs.
Stock gallery is unusable, it's worse than Motorola stock Gallery. Just
use Quickpic and set your image/photo directories.
ADWLauncher has 3 icons in the stock, you can change it to 5 icons.
ADWLauncher > UI Settings > Main Dock Style > 5 Icons
Now you can go ahead and install apps you use from Market(Google Play).
You can restore user app backups from Titan Backup.
Enjoy CM7.2
All credit goes to XDA members, CyanogenMod team and Motorola Corp for the mod, tools, files and drivers that they developed and released. Without them this how-to won't be possible.
This code is translated from org-mode text to html then to BBCode, I'm sorry if the formatting looks a bit alien.
Thank you for your great work (not found the thank button). I think this tread may be added to the top, found it only accidentally
Great thread for noobs! Bump so it doesnt get lost. Thanks for your time writing this.
HELPPP
So i bought an atrix 4g and i cant root because im on 2.3.6 4.5.141 and cant root i unlocked bootloader but cant root I dont know why i do everything step by step on root but i dont know why Command Prompt wont let me It says something like "Moto" is not recognized as an internal or external command something like that--
jesusitox12 said:
So i bought an atrix 4g and i cant root because im on 2.3.6 4.5.141 and cant root i unlocked bootloader but cant root I dont know why i do everything step by step on root but i dont know why Command Prompt wont let me It says something like "Moto" is not recognized as an internal or external command something like that--
Click to expand...
Click to collapse
Isn't the proper command "moto-fastboot" ?
MB860, CM7.2.0, Faux 026b1 1Ghz
jesusitox12 said:
So i bought an atrix 4g and i cant root because im on 2.3.6 4.5.141 and cant root i unlocked bootloader but cant root I dont know why i do everything step by step on root but i dont know why Command Prompt wont let me It says something like "Moto" is not recognized as an internal or external command something like that--
Click to expand...
Click to collapse
perhaps after you unzipped the moto-fastboot stuff you didn't direct your command prompt to the directory?
or missing the path to it in system variables or something?
i remember i just have the directory with moto-fastboot in flash drive which i just navigate to in command prompt just to be able to run the moto-fastboot command
hope that helps?
How To Install Firefox OS on a nexus 4 and dual boot.
XDA-Developers member pureexe has created an Image that will help you to port Firefox OS to your Google Nexus 4. Here is the list of what works and what doesn’t works:
What Works:
– Wi-Fi
– Data
– Phone Calls
– Contact Import
– GPS
– SMS/MMS
-Some Sensors (Light+Gyroscope+Acceleration)
-ADB
Does NOT Work:
– Camera
-MTP/PTP
– A lot of other things
How To Flash
Step 1: First connect your device to PC (desktop/laptop) via USB and make sure that USB debugging enabled on your device.
Step 2: Now to be on safe side create a Nandroid backup from recovery its because if something goes wrong then you can easily backup all your data.
Step 3: After creating backup, now download the ROM (FFOS_mako_********.zip) file and place these files on the SD card of the phone.
Step 4: Now switch off the phone and boot the phone into Recovery mode.
Step 5: Assuming you are in the Recovery mode and now you have to wipe the full data on your device. To do this, you have to click on “Wipe Data/Factory Reset” option. As soon as you click on “Wipe Data/Factory Reset” option a new screen pop-up where you have to click on “Yes” option.
Step 6: After wiping out all the data on your device you have to wipe the cache & the dalvik cache also.
Step 7: Now go to “install zip from SD card” option and click on “select zip from SD card”. After selecting the option “select zip from SD card” you have to choose the ROM file.
Step 8: After performing all the correctly in step 7 you have to clear the cache and & dalvik cache again.
Step 9: Now, go to “Install zip from SD card” option and click on “Select zip from SD card”. After selecting the option “Select zip from SD card”, you have to choose the optional file like home app or server module
Step 10 : Assuming you have performed all the steps correctly, now simply reboot your device and it will boot into Firefox OS.
Click to expand...
Click to collapse
How to dual boot: ONLY FOR GALAXY S2
Warning: This procedure doesn't really work anymore. It only works with Android 4 (Ice Cream Sandwich) and Siyah Kernel v 5.0.1. Later versions of either won't work. Consider this guide archived, and use it at your own risk.
If you want to test B2G from time to time but continue using Android as your main OS and you have a Samsung Galaxy S2, you can choose to install B2G in a separate partition (which is already present on the phone) and choose where to boot into when your device starts.
Prerequisites
In order to dual boot Android and B2G, you have to meet these prerequisites:
You have to have built B2G for the Galaxy S2
You have to download the Siyah kernel v. 5.0.1 for the Galaxy S2
You need the tool simg2img, that you get automatically if you build B2G following the guide on MDN
You need the heimdall tool, best if version 1.3.1 as you may encounter problems with version 1.3.2
One-time operations
There are several operations to do in order to get a working dual boot. The following ones need to be done the first time only.
In order to use heimdall without requiring root access, you should create a file called android.rules (the portion of the name before the .rules extension is arbitrary) and place it in /etc/udev/rules.d. The file should contain a line line the following:
Code:
SUBSYSTEM=="usb", ATTRS{idVendor}=="04e8", MODE="0666"
In order to activate this rule, you should restart udev:
Code:
sudo service udev restart
and then unplug and replug in the phone. The above rule will also allow adb to access the SGS2 without requiring root privlidges.
Flashing the Siyah kernel
The Siyah kernel is mandatory for the dual boot, because it is this kernel that manages it. Once you have downloaded and decompressed the tar file, you'll be left with a file named zImage. In order to flash it on your phone you have to follow these steps:
Switch off your phone
Reboot in download mode (press together volume down + home + power buttons and then, when asked, volume up button)
Use heimdall to flash the kernel with the following command (your phone needs to be connected to your PC):
heimdall flash --kernel /path/to/zImage
Once the kernel is flashed the phone will reboot.
Preparing the B2G rom environment
Once you've installed the Siyah kernel, it's time to use its functions to prepare the environment to install your B2G image in the secondary partition. Follow these steps:
Switch off your phone
Reboot in recovery mode (press together volume up + home + power buttons)
In the CWMR Touch interface, go to dual-boot options -> Wipe 2ndROM data/cache -> Yes - Wipe. This operation will take some time
Once the operation is finished, select Go Back and then reboot system now to reboot your phone. If you check, inside the internal SD card of your phone you'll now have a .secondrom directory with inside two files named cache.img and data.img.
B2G update operations
The following operations need to be done every time you build a new version of B2G.
In order to simplify command line instructions, it's advised to copy all needed files in a same folder of your choice. These are the files that need to be copied inside the folder:
Code:
simg2img, found in B2G/out/target/product/galaxys2/system/bin/
system.img, found in B2G/out/target/product/galaxys2/
userdata.img, found in B2G/out/target/product/galaxys2/
Once you have all the files in one place, do the following:
Create a data.img file out of the sparse file userdata.img. You can do it with the following command:
Code:
simg2img userdata.img data.img
Put the data.img file on your phone's .secondrom folder. You can do this either by enabling file storage mode on your phone and connecting it to your PC or, if you have USB Debug active, you can use adb:
adb push /path/to/data.img /sdcard/.secondrom/data.img
Switch off your phone
Reboot in download mode (press together volume down + home + power buttons and then, when asked, volume up button)
Use heimdall to flash B2G firmware inside the second partition:
heimdall flash --hidden system.img
Once the flash is finished, your phone will reboot and at boot time you can boot into your second rom (the B2G one) by pressing the home button during the bootloader countdown. If everything has gone right, once you've finished booting B2G you'll have a black screen on your phone. You now have to install Gaia.
Note: Depending on how you want to test B2G, you may not want to put a new data.img file on the phone every time you update B2G, as it will wipe all of your preferences, installed applications and in general pretty much everything you've done while using B2G.
Boot operations
The following operations need to be done every time you boot inside B2G.
Unfortunately, there's no simple way to put Gaia inside the system.img B2G image, and it get lost when you switch off your phone, so you'll need to install Gaia again every time you boot inside B2G. To install Gaia, type the following on a console after you've booted your phone inside B2G (so you have a black screen) and have connected your phone to your PC:
cd B2G/gaia
GAIA_DOMAIN=foo.org make install-gaia
After the upload of Gaia is completed, on your phone's screen the B2G interface will appear.
Click to expand...
Click to collapse
Dual Boot With Nexus 4 :
Original Link Here
Text Steps :
-Download FFOS.zip file
-Go to TWRP recovery
-Go to advanced, MultiROM, add ROM
-Select android, and don't share kernel
-Select next, then select zip file
-Select the FFOS.zip file
-After that go to list ROMs, pick FFOS, select flash zip, and flash the addons you want
-Reboot to multiboot
-Select FFOS and boot it
-Wait about 2 minutes
-You're now booted to FFOS
BTW FFOS stands for firefox OS
Downloads :
FFOS image Here
Contributors + Complier
pureexefor image and steps
Mozilla (for Dual Boot 1)
Riro Zizo for dual boot 2
Me, for putting all this stuff together!
@Apph3x
I have two version of porting
- Base Jellybean 4.3
- Base Kitkat
i know Base Kitkat is bad but working fine on base Jellybean 4.3
on jellybean everything working except MTP
Please read this post http://forum.xda-developers.com/showpost.php?p=44451567&postcount=2
Thanks
@pureexe I know but I'm sparse on time will update soon. The image is your latest 1 tho ;D thanks for original guide
Updated
Removed by owner
vvvvvvvvvvvvvvvv
Updated
UPDATE BASE LAYER 4.3
What Works:
- Wi-Fi
- Data
- Phone Calls
- Bluetooth
- Camera (Rear Camera & Front Camera)
- Video Record
- GPS
- SMS/MMS
- MUSIC (Mp3 & ogg decoder working)
- USB tethering
- WIFI tethering
- Video HQ decoder
- Sensor (Light+Gyroscope+Acceleration)
- ADB
- A lot of thing
Does NOT Work:
-MTP/PTP
Download
http://forum.xda-developers.com/devd...ct/dl/?id=3793
I Replaced the build.prop on my rooted Google nexus 6p running Android 7.0 with the build.prop file from the pixel to run Google Assistant.The phone is now stuck on the Google logo during boot,PLEASE HELP.
Did you make a backup copy of the file before replacing it, are you rooted, and have TWRP installed?
If so, reboot to recovery, use TWRP Terminal function to copy the backup of the build.prop to the modified one.
dratsablive said:
Did you make a backup copy of the file before replacing it, are you rooted, and have TWRP installed?
If so, reboot to recovery, use TWRP Terminal function to copy the backup of the build.prop to the modified one.
Click to expand...
Click to collapse
I did not make a back up but I am rooted and have Twrp installed.What can i do from here?
If you can boot to bootloader you should be able to replace the file with a standard one.
Alden1227 said:
I Replaced the build.prop on my rooted Google nexus 6p running Android 7.0 with the build.prop file from the pixel to run Google Assistant.The phone is now stuck on the Google logo during boot,PLEASE HELP.
Click to expand...
Click to collapse
same here please help.....freaking out
1. The build.prop contains the settings for a specific build for a specific phone. You can't just replace it from another build, not to mention another phone. Well, I guess, you already know this.
2. You should know exactly which build you were on. Exactly. Then:
* What I would do, is download the factory image from https://developers.google.com/android/nexus/images#angler
o Extract it, extract the image-angler-...zip, and mount the system.img, find the build.prop and adb push it to the phone.
o Reboot
* But you can also ask somebody who has the exact build as you do, and ask for the build.prop. Then push it to the phone.
Either restore from backup or edit the buildprop (if possible) I guess.
You only needed to edit 2 lines in the buildprop though, why replace the whole thing?
Alden1227 said:
I did not make a back up but I am rooted and have Twrp installed.What can i do from here?
Click to expand...
Click to collapse
First thing's first. Since you didn't just edit your build.prop, but replaced it with another, try setting permissions.
Step 1: Boot to TWRP > Mount > Select "System"
Step 2: Advanced > File Manager
Step 3: Navigate to /system/build.prop
Step 4: Select "chmod" and type "644" (don't include quotation marks)
Reboot and see if it works. If the permissions weren't right and you didn't change them, you'd most likely be in a boot loop. If this doesn't work you can just flash your system.img again. It won't wipe your internal storage, data (installed apps, etc.) If you have custom host files for ad blocking, you may need to apply them again.
If that does not work;
I'm going to assume you were on stock Nougat. Download the factory image (same build you were on before) and unzip the file. You'll end up with a folder with another zip archive in it. Unzip that as well. Inside you'll find a file named "system.img"
Move that system.img file to your ADB/fastboot folder. Shift+Right Click that folder and select "Open command window here"
Hold volume down + power to boot into the bootloader. Connect the phone to the PC and in the command prompt, type "fastboot devices" (no quotes again. ) It should show your devices serial number. If it does, perfect. If not, check your ADB/fastboot installation.
Once you get fastboot to show your serial number all you need to do is type;
Code:
fastboot flash system system.img
That should do it. If you need any more help, just reply back.
Edit: @istperson, AFAIK, you cannot pick out files from a .img file like that. When I right click it on my system and choose mount it tells me the image file is corrupted. Tried downloading again and hashes match. Windows 10. I use 7zip as well, and that can't open it either. Is there another program to use or is something whacky on my end? Wouldn't doubt it. Just took a Win10 update yesterday and it's been acting up on me all day. :/
RoyJ said:
Edit: @istperson, AFAIK, you cannot pick out files from a .img file like that. When I right click it on my system and choose mount it tells me the image file is corrupted. Tried downloading again and hashes match. Windows 10. I use 7zip as well, and that can't open it either. Is there another program to use or is something whacky on my end? Wouldn't doubt it. Just took a Win10 update yesterday and it's been acting up on me all day. :/
Click to expand...
Click to collapse
It's a sparse image, you have to convert it to normal mage with simg2img. Then you can mount it normally.
istperson said:
It's a sparse image, you have to convert it to normal mage with simg2img. Then you can mount it normally.
Click to expand...
Click to collapse
Awesome, thanks!
Fixed the issue
frreak said:
same here please help.....freaking out
Click to expand...
Click to collapse
I got mine to work by flashing Android 7.0
same thing happened to me.... stuck on google even after flashing stock....
dadoc04 said:
same thing happened to me.... stuck on google even after flashing stock....
Click to expand...
Click to collapse
Flash stock boot, system and vendor img files.
Sent from my Pixel XL using XDA-Developers mobile app
Same thing happened to me at first (though I did not use the build prop from a Pixel). I just dirty flashed my ROM (Octo N) and it then got passed the Google screen and loaded with no problem. I updated my build prop manually in order to get Google Assistant to work, and it's been working great ever since.
RoyJ said:
First thing's first. Since you didn't just edit your build.prop, but replaced it with another, try setting permissions.
Step 1: Boot to TWRP > Mount > Select "System"
Step 2: Advanced > File Manager
Step 3: Navigate to /system/build.prop
Step 4: Select "chmod" and type "644" (don't include quotation marks)
Reboot and see if it works. If the permissions weren't right and you didn't change them, you'd most likely be in a boot loop. If this doesn't work you can just flash your system.img again. It won't wipe your internal storage, data (installed apps, etc.) If you have custom host files for ad blocking, you may need to apply them again.
If that does not work;
I'm going to assume you were on stock Nougat. Download the factory image (same build you were on before) and unzip the file. You'll end up with a folder with another zip archive in it. Unzip that as well. Inside you'll find a file named "system.img"
Move that system.img file to your ADB/fastboot folder. Shift+Right Click that folder and select "Open command window here"
Hold volume down + power to boot into the bootloader. Connect the phone to the PC and in the command prompt, type "fastboot devices" (no quotes again. ) It should show your devices serial number. If it does, perfect. If not, check your ADB/fastboot installation.
Once you get fastboot to show your serial number all you need to do is type;
That should do it. If you need any more help, just reply back.
Edit: @istperson, AFAIK, you cannot pick out files from a .img file like that. When I right click it on my system and choose mount it tells me the image file is corrupted. Tried downloading again and hashes match. Windows 10. I use 7zip as well, and that can't open it either. Is there another program to use or is something whacky on my end? Wouldn't doubt it. Just took a Win10 update yesterday and it's been acting up on me all day. :/
Click to expand...
Click to collapse
Chmod 755 worked too
Hi,
I would like install at the Samsung SM-A515F the Lineage OS and the TWRP. I found only TWRP for the SM-A50. And the flashing dose not work for this phone.
I has try it with Heimdall and Odin.
The recovery I had downloaed from this Page:
https://www.droidthunder.com/install-twrp-recovery-on-galaxy-a51/
Need help or better information, if there exist an TWRP and lineage for this device.
Regards tiptel170
No need to flash twrp,u can flash aosp rom or even gsi with the help of odin only.Go to s10 page
sankhauaa said:
No need to flash twrp,u can flash aosp rom or even gsi with the help of odin only.Go to s10 page
Click to expand...
Click to collapse
s 10 page? which one is that? can u please provide the link?
Go here for odin flash method without twrp
sankhauaa said:
No need to flash twrp,u can flash aosp rom or even gsi with the help of odin only.Go to s10 page
Click to expand...
Click to collapse
sankhauaa said:
Go here for odin flash method without twrp
Click to expand...
Click to collapse
so does this method work for lineage os on A515F too?
After the long searching in the web, I found this:
A515F-TWRP
Link: https://firmware.gem-flash.com
After paying, you can download this TRWP. No idea, if this works. Maybe some one, will be use it.
ibtsam3301 said:
so does this method work for lineage os on A515F too?
Click to expand...
Click to collapse
I m not tried. But someone in this a51 group tried.Its working. But not so easy .
---------- Post added at 09:11 AM ---------- Previous post was at 09:09 AM ----------
tiptel170 said:
After the long searching in the web, I found this:
A515F-TWRP
Link: https://firmware.gem-flash.com
After paying, you can download this TRWP. No idea, if this works. Maybe some one, will be use it.
Click to expand...
Click to collapse
Don't pay.Its fake
tiptel170 said:
After the long searching in the web, I found this:
A515F-TWRP
Link: https://firmware.gem-flash.com
After paying, you can download this TRWP. No idea, if this works. Maybe some one, will be use it.
Click to expand...
Click to collapse
of course it would be fake
How can I open the img-files in the Linux desktop?
Found here this link, for the Magisk in the A515F:
https://forum.xda-developers.com/ga...w-to-root-samsung-a51-sm-a515f-t4032389/page2
I'll found this:
1. https://www.androlite.com/2020/01/twrp-root-samsung-galaxy-a51.html
2. https://appslova.com/install-twrp-on-samsung-galaxy-a51/
This links look likes good, because, my phone will not start or the heimdall goes into the error (likes in de page one, the screenshots ).
I found this, and I used basic from this page: https://forum.xda-developers.com/showpost.php?p=82241115&postcount=70
My first steps to install the lineage os 17 on the SM-A515F
Lineage: https://sourceforge.net/projects/andyyan-gsi/
All commands in the linux terminal, the path please use your own paths you like it!
Unpack lineage****.xz:
unxz lineage*.xz
1) Extract the AP_file.tar.md5 from your firmware.zip file using 7zip
2) Extract the super.img.lz4 file from the AP_file.tar.md5 file using 7zip
3) Put super.img.lz4 file in LZ4 folder and run in CMD the command
lz4 -d super.img.lz4 superLZ4.img
4) Put superLZ4.img file in Simg2img folder and run in CMD the command
chmod 777 ~/bin/otatools/bin/simg2img
~/bin/otatools/bin/simg2img superLZ4.img superSIMG.img
In Linux OR Bash shell:
1) Put superSIMG.img in otatools/bin folder and extract it in Linux terminal using the command
chomd 777 ~/bin/otatools/bin/lpunpack
~/bin/otatools/bin/lpunpack --slot=0 superSIMG.img ~/1
2) Put, in the folder where you extracted superSIMG.img, the GSI file you downloaded and rename it to system.img. Now you should have odm.img, system.img, vendor.img and product.img files in the same folder.
You may also need to delete/remane the original system.img file before renaming the GSI file.
3) Now you’re going to make a brand new super.img file containing all 4 files of the previous step. This is a critical and tricky step. Run Linux terminal and type:
chomd 777 ~/bin/otatools/bin/lpmake
~/bin/otatools/bin/lpmake ~/bin/otatools/bin/lpmake --metadata-size 65536 --super-name super --metadata-slots 2 --device super:4294967296 --group main:4293513600 --partition system:readonly:1959841792:main --image system=./system.img --partition vendor:readonly:680239104:main --image vendor=./vendor.img --partition odm:readonly:4349952:main --image odm=./odm.img --sparse --output ./super.img
4) Make an tar file:
tar -H ustar -c super.img > lineageos17.1_SMA515F.tar
5) Goto Windows -> Odin -> AP, put the file lineageos17.1_SMA515F.tar in to the AP-slot -> Start
This is what I has done:
But, by the compiling, I got this error:
Code:
lpmake I 07-15 20:18:20 92568 92568 builder.cpp:1012] [liblp]Partition system will resize from 0 bytes to 1959841792 bytes
lpmake I 07-15 20:18:20 92568 92568 builder.cpp:1012] [liblp]Partition vendor will resize from 0 bytes to 680239104 bytes
lpmake I 07-15 20:18:20 92568 92568 builder.cpp:1012] [liblp]Partition odm will resize from 0 bytes to 4349952 bytes
Invalid sparse file format at header magic
Invalid sparse file format at header magic
And the phone is into the boot-loop, it will not starting the system.
Any help please...
Update:
System requirements:
- Fedora 32 with current kernel
- VirtualBox 6.1 with USB support
- Windows 7
- ODIN 3.14
Enable Root:
I) On mobile phone
1. carry out firmware update
1.1 Set up device, WITHOUT Google Accounts, WITHOUT security settings, set up WLAN only
1.2 Settings -> Phone info -> Software information -> Build number (press 7x )
1.3 Settings -> developer option -> enable OEM unlocking and USB debugging
2. copy the files from the root directory to the external SD card
2.1 Install MagiskManager
2.2 Starting MagiskManager
2.3 Installing Magisk Select
II) In the Fedora area
3. unpack the boot.img from the AP***.tar, on the PC
3.1 lz4 -d boot.img.lz4 boot.img
3.2 Copy the boot.img to the SD card from the phone
4. patching the boot.img in MagikMager
4.1 Select the boot.img, wait until "Done" appears.
4.2 Then copy the magisk_patch.img to the workstation (Fedora)
5.1 Rename the original boot.img to boot_original.img
5.2 renaming magisk_patch.img to boot.img
5.3 Transfer the new boot.img to the PC for the ODIN or HEIMDALL
5.4 Convert the boot.img to boot.tar: tar -H ustar -c boot.img > boot.tar (here for ODIN)
III) Virtual environment Win7
6.1 Copy the boot.tar from the Fedora workstation to the Odin directory of Win7
6.2 Open the boot.tar in the AP slot, Auto Reboot must be off
6.3 Press Vol + & Vol - simultaneously and plug in the USB cable (On SM-A515F), then click on "Start" in the ODIN.
IV) On the Mobile Phone
7.1 If ready, restart with Vol - & Hold PWR for more than 7 sec
7.2 Putting the device into recovery mode (switch off, press vol up and pwr simultaneously, Samsunglog appears, release pwr again)
7.3 Wipe your data: Wiped data/factury reset
Note: Device makes a boot loop for the first time - is normal. The first start takes quite long, be patient!
7.4 Settings -> Phone info -> Software information -> Build number (press 7x )
7.5 Settings -> Developer option -> Enable OEM unlock, USB debugging and system auto update to OFF
7.6 Installing and starting MagiskManger
The device will restart once!
Check it: Whether root is present
Fedora workstation:
Call Terminal, enter adb shell followed by su
If everything went well, the MagiskManager should answer the phone and ask for authorization.
These steps works well with the firmware: SM-A515F R58N60BLPAZ
Where are the exactly steps for installing the TWRP?
I has installed the TWRP-10.0(A51).zip with the heimdall and the phone will not booting. And I'm not entering the TWRP. And finally I has reinstalled the revcovery.img (heimdall) from the APxxxx.zip file, and the phone starting normally.
All things with the AOSP10 etc, I has tried and the other steps for an alternative system will not work on this phone.
Thanks God, the root is now working. And I have to work with the ugly Samsung system.
tiptel170 said:
Update:
System requirements:
- Fedora 32 with current kernel
- VirtualBox 6.1 with USB support
- Windows 7
- ODIN 3.14
Enable Root:
I) On mobile phone
1. carry out firmware update
1.1 Set up device, WITHOUT Google Accounts, WITHOUT security settings, set up WLAN only
1.2 Settings -> Phone info -> Software information -> Build number (press 7x )
1.3 Settings -> developer option -> enable OEM unlocking and USB debugging
2. copy the files from the root directory to the external SD card
2.1 Install MagiskManager
2.2 Starting MagiskManager
2.3 Installing Magisk Select
II) In the Fedora area
3. unpack the boot.img from the AP***.tar, on the PC
3.1 lz4 -d boot.img.lz4 boot.img
3.2 Copy the boot.img to the SD card from the phone
4. patching the boot.img in MagikMager
4.1 Select the boot.img, wait until "Done" appears.
4.2 Then copy the magisk_patch.img to the workstation (Fedora)
5.1 Rename the original boot.img to boot_original.img
5.2 renaming magisk_patch.img to boot.img
5.3 Transfer the new boot.img to the PC for the ODIN or HEIMDALL
5.4 Convert the boot.img to boot.tar: tar -H ustar -c boot.img > boot.tar (here for ODIN)
III) Virtual environment Win7
6.1 Copy the boot.tar from the Fedora workstation to the Odin directory of Win7
6.2 Open the boot.tar in the AP slot, Auto Reboot must be off
6.3 Press Vol + & Vol - simultaneously and plug in the USB cable (On SM-A515F), then click on "Start" in the ODIN.
IV) On the Mobile Phone
7.1 If ready, restart with Vol - & Hold PWR for more than 7 sec
7.2 Putting the device into recovery mode (switch off, press vol up and pwr simultaneously, Samsunglog appears, release pwr again)
7.3 Wipe your data: Wiped data/factury reset
Note: Device makes a boot loop for the first time - is normal. The first start takes quite long, be patient!
7.4 Settings -> Phone info -> Software information -> Build number (press 7x )
7.5 Settings -> Developer option -> Enable OEM unlock, USB debugging and system auto update to OFF
7.6 Installing and starting MagiskManger
The device will restart once!
Check it: Whether root is present
Fedora workstation:
Call Terminal, enter adb shell followed by su
If everything went well, the MagiskManager should answer the phone and ask for authorization.
These steps works well with the firmware: SM-A515F R58N60BLPAZ
Where are the exactly steps for installing the TWRP?
I has installed the TWRP-10.0(A51).zip with the heimdall and the phone will not booting. And I'm not entering the TWRP. And finally I has reinstalled the revcovery.img (heimdall) from the APxxxx.zip file, and the phone starting normally.
All things with the AOSP10 etc, I has tried and the other steps for an alternative system will not work on this phone.
Thanks God, the root is now working. And I have to work with the ugly Samsung system.
Click to expand...
Click to collapse
It is work ???
GreggBorowski said:
It is work ???
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------
These steps works well with the firmware: SM-A515F R58N60BLPAZ
Where are the exactly steps for installing the TWRP?
I has installed the TWRP-10.0(A51).zip with the heimdall and the phone will not booting. And I'm not entering the TWRP. And finally I has reinstalled the revcovery.img (heimdall) from the APxxxx.zip file, and the phone starting normally.
All things with the AOSP10 etc, I has tried and the other steps for an alternative system will not work on this phone.
Thanks God, the root is now working. And I have to work with the ugly Samsung system.
sankhauaa said:
I m not tried. But someone in this a51 group tried.Its working. But not so easy .
---------- Post added at 09:11 AM ---------- Previous post was at 09:09 AM ----------
Don't pay.Its fake
Click to expand...
Click to collapse
sar please send me a51 group
Mehran` said:
sar please send me a51 group
Click to expand...
Click to collapse
Go to s10 page
sankhauaa said:
Go here for odin flash method without twrp
Click to expand...
Click to collapse
Not working. I has done step by step in this guide.
ibtsam3301 said:
so does this method work for lineage os on A515F too?
Click to expand...
Click to collapse
No. Withe manipulation from the vbmeta.img, the system is unwilling to start. It gos in to the bootloader, with error-codes. Like in first thread I describe. Olny the SAMSUNG original system works with the kernel modification for the MagiskManager.
I saw black for the future, there will be exist an custom rom for this device.
I have no idea, what can I do for this device. But I use and spend a lot of time for modification, without an good result. Has anyone an idea what can I do? But it look likes, it has an great secure system intern for not using an customer rom. This is my intention.
Greetings,
i did go through dual-booting linux on our device kind of process and spend a bit of time, trying to figure out the correct steps.
Was not easy, for a newbie like me, i dont know much about linux itself, most of the inscrutions are written in "foreing language" for me, so here is more of a detailed guide.
This guide is only for installation on the SDCARD, i did not try out internal storage
!!! Im not responsible for anything that happens during/using these steps, you and only you are responsible to what happens, use with caution !!!
Requirements:
Unlocked bootloader: https://forum.xda-developers.com/t/...6c-boot-for-asus-memo-pad-7-me176c-x.3780225/
Installed TWRP: https://forum.xda-developers.com/t/...p-3-3-1-for-asus-memo-pad-7-me176c-x.3745190/
Both of these guides are made step by step, so there should be no questions about this
First of all, go to https://images.postmarketos.org/bpo/v22.12/asus-me176c/ , there are 3 different types of UI, the kernel itself should be the same, but i dont know for sure myself
Phosh - very well working on our device, missing a bit of RAM to launch firefox stable for example
Plasma-mobile - i found this one was very hardware heavy, it takes quite alot of more storage aswell, i do not recommend this for our device
Sxmo - this one did boot up just fine, but i wasnt able to get more testing as my hardware inputs were not recognized by the software, i do not recommend this one
There are multiple software version, i did try only the latest one
Possible to try out the lower (outdated) versions yourself
After downloading these files, you should have 2 of the .xz archives, unpack them somewhere, i did put them into the same folder, but thats just my own preference
After unpacking them, you should have
XXX-asus-me176c-bootpart.img
XXX-asus-me176c.img
XXX are reference to date of the build
To have ourself things easier, we will rename both of these build and leave only the "asus-me176c.img/asus-me176c-bootpart.img", you can leave them named as theyre, but it will take you a bit more time in the terminal
After that, we will move one of our images (the non-bootpart one) to the internal storage of the device.
Make sure, to have enough space available. I have the 8GB version and it was kind of struggle for me to install the plasma-mobile version.
I did also try moving that file to USB-OTG and SDCARD, but i had some problems with USB-OTG in TWRP and SDCARD gets wiped when you install the OS.
So, please, use internal storage for the file, the OS IS NOT GOING TO GET INSTALLED ON YOUR INTERNAL STORAGE IN THIS WAY, WE ARE GOING TO INSTALL IT ON A SDCARD.
After moving our file to the internal memory, we will go and reboot our tablet to fastboot mode
when powered off, press volume down + power on, release power when screen lights up
in the custom bootloader menu, using volume keys (power one does not work), we select Fastboot (power down to move and power up to select)
Our phone should boot into fastboot mode, we go and connect our phone to the computer
after connecting the phone, we go to the folder where our xxx asus-bootpart.img is located, go ahead and SHIFT+RIGHTCLICK on empy space in the folder, select Open a terminal/powershell window here
in the terminal/powershell we type in command " fastboot flash APD asus-me176c.img "
let the command process, after its done, go and type in " fastboot reboot-bootloader "
our phone gets rebooted into the bootloader, with volume keys once again, select RECOVERY
when our device gets booted to TWRP, go to Mount -> Tick ESP
anywhere on your PC, open up the default text editor, paste in:
title postmarketOS
volume 80868086-8086-8086-8086-000000000007
linux /vmlinuz-edge
initrd /intel-ucode.img
initrd /initramfs
# Comment this out to get more output on screen while booting
options console=null
this text is only used for the latest version of the OS, for lower versions, please follow https://wiki.postmarketos.org/wiki/ASUS_MeMO_Pad_7_(asus-me176c)
select the file type as "every files" instead of text document
name it pmos.conf and save it anywhere you like
at your computer, download MiniDiskPartition tool, or other partition tool
partition your sdcard using the selected tool
i have 32GB sdcard, i did partition my sdcard roughly 8GB with FAT32 for file sharing between android/linux/windows and the rest with EXT4 for the Linux itself
i believe the partition size for Linux doesnt matter aslong as its over 4GB, the installation itself should resize the partition on sdcard itself, depending on how it needs, BUT im still not 100% how this works
connect your phone to the computer
in TWRP go to MOUNT and tick ESP
in the folder where you saved the pmos.conf, open up a terminal (once again SHIFT+RIGHTLICK and open terminal/powershell here)
type in " adb push pmos.conf /esp/loader/entries/ " , press enter
in TWRP go to Advanced and go to Terminal
type in " df "
then you should see your partitions, we are looking for one that belongs to /external_sd/ , usually dev/block/mmcblkX0Y (X and Y are not specified), it should have it written at the end
mine was " /dev/block/mmcblk0p1 " YOURS CAN BE DIFFERENT! in the original guide, they specify, it can be also SDXY (XY belongs to any number)
after we find our partition that belongs to /external_sd/ , we go into the terminal in TWRP and type in:
dd if=/PATHTOYOURIMGFILE/ of=/PATHTOYOUREXTERNALSDCARDPARTITION/ bs=4m
i did have the IMG file in my internal storage, therefore my command was:
dd if=/sdcard/asus-me176c.img of=/dev/block/mmcblk0p1 bs=4m
make sure to use the bs=4m instead of bs=4M (as specified in the original guide), otherwise you will get "illegal number" error
after this, you should wait! The file is 1,6 - 2,4 GB, it takes time
your result should appear in the terminal
if your installation was succesfull, you can go in TWRP to REBOOT and select BOOTLOADER
you should have postmarketOS option available in the bootloader boot options, select it
you should boot your postmarketOS now
if you didnt, you probably didnt follow the guide correctly, read the steps once again
if you couldnt install the postmarketOS and youre sure you did follow the steps correctly, contact me on XDA (preferably make a comment under this thread)
Original thread:
ASUS MeMO Pad 7 (asus-me176c) - postmarketOS
wiki.postmarketos.org