Okay, another update
Of course I'll provide download links again
DOWNLOAD LINKS:
DropBox
Google Drive
OneDrive
---------------
HOW TO INSTALL:
In case your update installation fails for whatever reason you have to go back to a stock state. We'll first downgrade the watch to an older version (since those are the only IMG files I currently have).
Go to THIS PAGE and download the files (Here's a backup-upload in case they're down - OneDrive Backup)
Boot into bootloader mode (reboot watch > once logo shows up swipe from left upper to right lower corner)
Connect to PC, open CMD in the folder with those files and type "fastboot flash recovery recovery_6.0.1_MEC23G.img", "fastboot flash boot boot_6.0.1_MEC23G.img" and "fastboot flash system system_6.0.1_MEC23G.img"
Reboot to system and either let the watch update itself 2 times (far easier) or...
... boot to recovery and sideload the 2 ZIP-files yourself (you need to update to MWD48B (OneDrive Backup) first, then M1D63H (OneDrive Backup)!)
Anyways, I hope this helped a bit!
Currently trying to pull .img-files for those who still have their LG G Watch so installation will be easier and faster.
EpicLPer said:
Currently trying to pull .img-files for those who still have their LG G Watch so installation will be easier and faster.
Click to expand...
Click to collapse
Install TWRP and from console/adb shell write
Code:
[STRIKE]echo "mmcblk0" > /sys/devices/virtual/android_usb/android0/f_mass_storage/lun/file[/STRIKE]
You'll have access to all patitions on your watch.
ab123321 said:
Install TWRP and from console/adb shell write
Code:
echo "mmcblk0" > /sys/devices/virtual/android_usb/android0/f_mass_storage/lun/file
You'll have access to all patitions on your watch.
Click to expand...
Click to collapse
What will this do exactly? I already managed to pull images with DD, but this also sounds interesting
EpicLPer said:
What will this do exactly? I already managed to pull images with DD, but this also sounds interesting
Click to expand...
Click to collapse
It forces kernel to connect flash-memory (mmcblk0) in your watch to your PC as a disk. So, You'll see partitions as drives.
Then, you'll be able to dd them directly on your PC (if you use Linux, of course)
ab123321 said:
It forces kernel to connect flash-memory (mmcblk0) in your watch to your PC as a disk. So, You'll see partitions as drives.
Then, you'll be able to dd them directly on your PC (if you use Linux, of course)
Click to expand...
Click to collapse
Hm, that sounds quite easier hehe, the TWRP dd way was nice too but I'll try this, thanks!
ab123321 said:
Install TWRP and from console/adb shell write
Code:
echo "mmcblk0" > /sys/devices/virtual/android_usb/android0/f_mass_storage/lun/file
You'll have access to all patitions on your watch.
Click to expand...
Click to collapse
Hm, "sh: write error: No such file or directory"
Oh, because "lun" is the actual file, lun is not a directory.
Edit 2: No, wait what... TWRPs file manager shows me this is a file, not a directory, ADB however tells me this is a directory and not a file??? WTF
EpicLPer said:
Hm, "sh: write error: No such file or directory"
Oh, because "lun" is the actual file, lun is not a directory.
Edit 2: No, wait what... TWRPs file manager shows me this is a file, not a directory, ADB however tells me this is a directory and not a file??? WTF
Click to expand...
Click to collapse
Stolen from Watch R thread fixed:
Code:
cd /sys/devices/virtual/android_usb/android0
echo 0 > enable && echo "adb,mass_storage" > functions && echo "/dev/block/mmcblk0" > f_mass_storage/lun/file && echo 1 > enable
Related
Facts:
Laptop connected to my phone uses Ubuntu linux
Unlocked my Amaze successfully
I have the RecoveryInstallerForNoobs2.0
I have chmod'ed all the pertient files to be executable
With phone in fastboot mode, doing 'sudo ./fastboot devices' returns the serial number
Problem:
'sudo ./Flash.sh' returns the following output:
./Flash.sh: 1: adb: not found
: not found 2:
Additional facts:
I am a n00b and I am aware my life's output at age 32 is dismal
I have read the "read first for linux..." thread, "how to root" thread and the "faq before posting" thread
I have searched the site but possibly not hard enough, ergo my own impudent thread
What to do??
Is debug on in your phones settings?
Sent by accident from my Amaze using Tapatalk
Double0EK said:
Is debug on in your phones settings?
Sent by accident from my Amaze using Tapatalk
Click to expand...
Click to collapse
what he said turn on debugging on your phone. also make sure the zip file is unzipped into a folder
Debugging is on in the settings and the recovery for noobs zip is unzipped.
I flashed mine manually using the fastboot command...
But I only know how to do it with a windows machine.
Put the recovery.img in your AndroidSDK/tools folder , open cmd , cd to the tools folder and type "fastboot flash recovery recovery.img" being if you renamed it to recovery.img..(if it wasn't renamed then you need to type the name of the recovery img.)
Sent by accident from my Amaze using Tapatalk
ryurage said:
Debugging is on in the settings and the recovery for noobs zip is unzipped.
Click to expand...
Click to collapse
don't go to fastboot, the script should automatically kill and restart the adb shell...just turn on your phone and run flash.sh... if that doesn't work Rename the shellscript from flash.sh to flash.command, then associate it with Terminal.app
let me know if those work, if not, I've got some other tricks but it's a little bit more complicated.
@seansk, I renamed the file and tried it with the same resulted output:
./flash.command: 1: adb: not found
: not foundmand: 2:
Btw, I run the flash script one of two ways, 1. sudo ./flash.command or 2. bash flash.command
I could be wrong but I think the issue possibly lies in the script:
adb kill-serveradb reboot bootloaderfastboot flash recovery recovery-cwm-ruby-5.0.2.7.imgfastboot rebootexit
Perhaps adb has to be in my PATH? I'm open to other suggestions too.
One more thought, assuming the adb daemon is shut down, maybe this command would do it: 'sudo ./fastboot flash recovery recovery-cwm-ruby-5.0.2.7.img'?
hmm that thing has been up for months...I've only had two people having trouble and havn't heard back from the other guy...so I hope there's nothing wrong with the scrip...I will look into it again...unfortuantely my vitual machine for mac is down right now, don't know when I'll get it back up and running...
try these
1)To start the shell-script 'file.sh':
sh file.sh
bash file.sh
2)Another option is set executable permission using chmod command:
chmod +x file.sh
Now run .sh file as follows:
./file.sh
ultimately if you have a windows computer it would be much easier...or if you can also here's the new recovery from xboarder I havn't updated this zip file yet... you can edit the recovery script to change the name to this file name: recovery-cwm-ruby-5.5.0.4.img
if all else fails follow the second method here from xboarder (you need an sd card): http://forum.xda-developers.com/showthread.php?t=1316855
Download file to your computer
2. make sure its named PH85IMG.zip
3. Copy to sdcard (external one) then restart your phone in fastboot, by holding down the volume down and power.
4. Wait for it to say do you want to update (press volume up)
5. Press power button to reboot
6. Reboot Phone into recovery as normal and enjoy clockworkmod recovery with fixed charging and sdcard
hi
im very new in the forum thats my first post
i tried to install an app that required a rebbot in my gt-i9300, i rebooted and i got an pop-up window said that factory mode has crashed.
i searched for days in the internet and i found this thread: http://forum.xda-developers.com/showthread.php?t=1762204&page=53
i did all but my galaxy says that its unable to chmod /efs/FactoryApp/factorymode: no such file or directory
then i realised that i have no efs directory and that i can download one from here http://forum.xda-developers.com/showthread.php?t=888193
so' my question is,
if i will flash it with odin, will the error will dissapear?
and if the answer is yes,
i understand that some people flash it because they have no imei and the phone dont recognize their sim card.
and my fear it can happen to me if ill flash it
some help please?
What app did you try installing?
slaphead20 said:
What app did you try installing?
Click to expand...
Click to collapse
the swapsd app.
but theres no matter what app i installed
i just want to know if i can install the efs directory without problems
so please help me everyone!
You have a backed up EFS on your phone ???
jje
JJEgan said:
You have a backed up EFS on your phone ???
jje
Click to expand...
Click to collapse
yes i have a backup named efs.tar in my root directory
can i restore the folder from it?
arimal199 said:
yes i have a backup named efs.tar in my root directory
can i restore the folder from it?
Click to expand...
Click to collapse
Well, obviously you can. That's what an efs backup is for
Copy the tar file to your PC and download the Android SDK.
Once the Android SDK is installed, open up a command prompt.
Once you're in the command prompt, CD to the directory where the ADB executables and libraries are.
Usually it's here:
Code:
cd C:\android-sdk\platform-tools\
Once you're in the directory where the files are, unpack the TAR file and type the following code:
Code:
adb start-server
adb push <path-to-your-unpacked-TARfile> /efs/
adb kill-server
If you need further assistance, feel free to PM or email me
Hope I could help!
Lg
familyguy59 said:
Well, obviously you can. That's what an efs backup is for
Copy the tar file to your PC and download the Android SDK.
Once the Android SDK is installed, open up a command prompt.
Once you're in the command prompt, CD to the directory where the ADB executables and libraries are.
Usually it's here:
Code:
cd C:\android-sdk\platform-tools\
Once you're in the directory where the files are, unpack the TAR file and type the following code:
Code:
adb start-server
adb push <path-to-your-unpacked-TARfile> /efs/
adb kill-server
If you need further assistance, feel free to PM or email me
Hope I could help!
Lg
Click to expand...
Click to collapse
wow
thanks man ill try it
arimal199 said:
wow
thanks man ill try it
Click to expand...
Click to collapse
oh i forgot
my pc doesnt recognize my galaxy
maybe i can go to someone that already has a adb and see if he can fix it
but really thanks
I believe you'll also need to change files owners and access rights for it to work.
Edit : if you don't have any efs folder, I think your efs partition might not be mounted. Type "mount" in a terminal emulator and check if a line refers to /efs (that should be block 3)
arimal199 said:
oh i forgot
my pc doesnt recognize my galaxy
maybe i can go to someone that already has a adb and see if he can fix it
but really thanks
Click to expand...
Click to collapse
Check out the links in my description. (Win8 help - ADB etc. etc. ...) that works with Windows Vista, 7 and 8. If you need the ADB binaries, in that same thread, you can donate a bit of money to me and I'll license you a program (Always with updated binaries) that installs ADB and fastboot to your system's root. With the click of a button
Lg
Edit: You can also download my universal Android tool kit and with the next update, all the Samsung Galaxy S III variants will be supported and you can easily backup/restore your /efs partition from there (With the Pro version, that is)
spocky12 said:
I believe you'll also need to change files owners and access rights for it to work.
Edit : if you don't have any efs folder, I think your efs partition might not be mounted. Type "mount" in a terminal emulator and check if a line refers to /efs (that should be block 3)
Click to expand...
Click to collapse
i looked in mounts and storage in cwm and saw that efs is not mounted.
can i mount it and it will work?
arimal199 said:
i looked in mounts and storage in cwm and saw that efs is not mounted.
can i mount it and it will work?
Click to expand...
Click to collapse
no i understood' i wasnt at factory mode at all!
all the time i had imei and call function , the only problem was that factory test has stopped.
so, i downloaded titanum backup pro and turned factory test app off.
now my galaxy went back to normal all works as well!
thanks for trying to help guys!
Whats fastboot? Cause i wanna install a rom for goophone i5 and im using Android Ultimate Toolbox pro and i dont have any recovery on the phone cause i cant flash it, and whenever i try to flash a recovery image with Toolbox it says i need to be fastbooted... Give me a hand please
HeavenKinder said:
Whats fastboot? Cause i wanna install a rom for goophone i5 and im using Android Ultimate Toolbox pro and i dont have any recovery on the phone cause i cant flash it, and whenever i try to flash a recovery image with Toolbox it says i need to be fastbooted... Give me a hand please
Click to expand...
Click to collapse
Fastboot is a command line utility used to modify and interact with the Android filesystem through USB on your computer. You can easily download and setup ADB (Android Debugging Bridge) and Fastboot using this utility found here http://forum.xda-developers.com/showthread.php?p=42407269. You will also need to make sure you've installed the USB drivers for your device in order for fastboot to function properly. To access fastboot run the following command from command line (Make sure USB debugging is enabled in developer settings first):
Code:
adb reboot bootloader
You can then flash your recovery image with the command:
Code:
fastboot flash recovery recovery.img
Let me know if you still have questions.
Sent from my SCH-I535 using XDA Premium 4 mobile app
shimp208 said:
Fastboot is a command line utility used to modify and interact with the Android filesystem through USB on your computer. You can easily download and setup ADB (Android Debugging Bridge) and Fastboot using this utility found here http://forum.xda-developers.com/showthread.php?p=42407269. You will also need to make sure you've installed the USB drivers for your device in order for fastboot to function properly. To access fastboot run the following command from command line (Make sure USB debugging is enabled in developer settings first):
Code:
adb reboot bootloader
You can then flash your recovery image with the command:
Code:
fastboot flash recovery recovery.img
Let me know if you still have questions.
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ok so i did the recovery command and it says waiting for device, what do i need to do?
Now if i try to fastboot using that comand it says:
ADB server is didn't ACK
*failed to start daemon*
error:
And if i write the comand to fast bood and then use Android Ultimate toolbox to flash the recovery image it just sits at waiting for device and if i cancel it and do it again it just says i need to fastboot...
if you want to flash recovery so use mobile uncle tools android app !
work on chinees device good
anabhi said:
if you want to flash recovery so use mobile uncle tools android app !
work on chinees device good
Click to expand...
Click to collapse
When i try to use MobileUncletools and i flash the recovery image, it asks if i want to boot into the new recovery, it turns off the phone, and when it turns it back on it just freezes in the apple logo
Ok so if i try to boot into fastboot with ADB and then go to Android ultimate tools pro to flash recovery, it says the device isnt in fastboot...
bump
HeavenKinder said:
Ok so if i try to boot into fastboot with ADB and then go to Android ultimate tools pro to flash recovery, it says the device isnt in fastboot...
Click to expand...
Click to collapse
You can also flash recovery from ADB shell as root by running the command (Make sure that the recovery image your using is meant for your device, and is placed on your internal storage):
Code:
cat /mnt/sdcard/recovery.img > /dev/block/{path-to-recovery-partition-block}
shimp208 said:
You can also flash recovery from ADB shell as root by running the command (Make sure that the recovery image your using is meant for your device, and is placed on your internal storage):
Code:
cat /mnt/sdcard/recovery.img > /dev/block/{path-to-recovery-partition-block}
Click to expand...
Click to collapse
Can you give me an example please? cause i tried it and it said:
"the filename, directory name, or volume label syntax is incorrect.
bump
Bump
HeavenKinder said:
Can you give me an example please? cause i tried it and it said:
"the filename, directory name, or volume label syntax is incorrect.
Click to expand...
Click to collapse
For example if I wanted to flash a recovery on my Nexus 10 without using fastboot just using adb shell I would run a command similar to this one:
Code:
cat /mnt/sdcard/clockworkmodrecovery.img > /dev/block/mmcblk0p4
If you can provide me with output of your recovery log file by going to /cache/recovery/log I can tell you which partition is your recovery partition that you need to flash.
shimp208 said:
For example if I wanted to flash a recovery on my Nexus 10 without using fastboot just using adb shell I would run a command similar to this one:
Code:
cat /mnt/sdcard/clockworkmodrecovery.img > /dev/block/mmcblk0p4
If you can provide me with output of your recovery log file by going to /cache/recovery/log I can tell you which partition is your recovery partition that you need to flash.
Click to expand...
Click to collapse
Wheres the cache file?
HeavenKinder said:
Wheres the cache file?
Click to expand...
Click to collapse
The /cache directory is located in the root (/) directory you can access the /cache directory and subsequent directories using any root file browser such as this one. You should then be able to get to recovery/log file and view it's contents.
shimp208 said:
The /cache directory is located in the root (/) directory you can access the /cache directory and subsequent directories using any root file browser such as this one. You should then be able to get to recovery/log file and view it's contents.
Click to expand...
Click to collapse
But if i don't have Google Play on the phone, how can i install the application? Do i have to search a way to flash it into the device?
HeavenKinder said:
But if i don't have Google Play on the phone, how can i install the application? Do i have to search a way to flash it into the device?
Click to expand...
Click to collapse
You can also use ADB shell to access the file contents by navigating to the /cache/recovery/log directory and looking at the output. Running the following command should show the output of the recovery log:
Code:
cat /cache/recovery/log
shimp208 said:
You can also use ADB shell to access the file contents by navigating to the /cache/recovery/log directory and looking at the output. Running the following command should show the output of the recovery log:
Code:
cat /cache/recovery/log
Click to expand...
Click to collapse
'cat' is not recognized as an internal or external command, operable program or batch file
HeavenKinder said:
'cat' is not recognized as an internal or external command, operable program or batch file
Click to expand...
Click to collapse
Make sure you run the command from ADB shell. For example first navigate to the directory where you have a ADB and Fastboot setup on your computer then open a command prompt window from that directory and run the following commands:
Code:
adb shell
cat /cache/recovery/log
shimp208 said:
Make sure you run the command from ADB shell. For example first navigate to the directory where you have a ADB and Fastboot setup on your computer then open a command prompt window from that directory and run the following commands:
Code:
adb shell
cat /cache/recovery/log
Click to expand...
Click to collapse
No such file or directory...
What You Need?
1. Your Mobile [Rooted]
2. Computer
3. USB Cable
How?
if you need PARAM.bin file that means you know how things work, so i'm not gonna explain every little step.
1. Make folder on your desktop and Open 2 command line programme windows in that directory.
2. choose one window and run this commands
adb shell
su
dd if=/dev/block/platform/13540000.dwmmc0/by-name/PARAM of=/sdcard/PARAM.bin bs=4096
Block Path in above dd command can be different in your device. if you failed to open renamed zip file, you need to Find Correct Block and replace that in dd command
3. goto second command line window and run
adb pull /sdcard/PARAM.bin
4. To Extract Files from bin Just rename .bin file to zip (param.bin.zip)
Done.
Thanks,but how do i extract this file?
already tried with "tar xf " but gives me nothing
AndroidSamsungFreak said:
Thanks,but how do i extract this file?
already tried with "tar xf " but gives me nothing
Click to expand...
Click to collapse
same problem with me
AndroidSamsungFreak said:
Thanks,but how do i extract this file?
already tried with "tar xf " but gives me nothing
Click to expand...
Click to collapse
Just rename it to zip (param.bin.zip)
wings110 said:
same problem with me
Click to expand...
Click to collapse
Just rename it to zip (param.bin.zip)
AUPMA said:
Just rename it to zip (param.bin.zip)
Click to expand...
Click to collapse
my device is g9300 cpu is 820 rename zip can not be opened
wings110 said:
my device is g9300 cpu is 820 rename zip can not be opened
Click to expand...
Click to collapse
Seems Like your block is different. So you need to Find Correct block and replace that on dd command
Samsung A50 booting on logo
AUPMA said:
What You Need?
1. Your Mobile [Rooted]
2. Computer
3. USB Cable
How?
if you need PARAM.bin file that means you know how things work, so i'm not gonna explain every little step.
1. Make folder on your desktop and Open 2 command line programme windows in that directory.
2. choose one window and run this commands
adb shell
su
dd if=/dev/block/platform/13540000.dwmmc0/by-name/PARAM of=/sdcard/PARAM.bin bs=4096
Block Path in above dd command can be different in your device. if you failed to open renamed zip file, you need to Find Correct Block and replace that in dd command
3. goto second command line window and run
adb pull /sdcard/PARAM.bin
4. To Extract Files from bin Just rename .bin file to zip (param.bin.zip)
Done.
Click to expand...
Click to collapse
hello sir i have Samsung galaxy A50 (505F)my phone was ok and i kept it on my bed after using and went to do some work when i came back & saw my phone was restarting automatically whereas no body touched it, it does not happened before then i thought its ok maybe some reason it happen but after restarting my phone its continuously booting on Samsung logo and some strange lines are coming behind the logo every time its not getting on properly only restarting, so after that i tried soft rest even hard rest\wipe data factory rest but same issue is there and i tried software with latest stock firmware with latest and different version of Odin its just stuck on CM software not starting even i tried combination file but stuck on boot i tried PIT file also it passed but nothing is happened
(Bootloader lock by OEM) And In
Recovery Mode on top
BIN MODE (By Param) (not sure BIN or Something else because of curved screen)
Cause: BL:Recovery Mode Set by Key,
Even i visit to Samsung service center and they tried to do software but unable to do and they just simply said it will change the board but i know its some kind of software issue and i'm not able to spend so much money in this situation :crying: please give me some solution i want to share some pictures of my device with you please give me your mail Id so i can share with you please help and give some solution
Note:-there is not any third party app installed in my device still it happen....please give me solution
I think this does not work anymore with the latest Android 10 Updates.
Funciona en Android 10 para S9+ Snapdragon? Alguien lo probó?No logro sacar el paran.bin, ayuda porfa.
AUPMA said:
Seems Like your block is different. So you need to Find Correct block and replace that on dd command
Click to expand...
Click to collapse
my parab file is mmcblk0p12. it did not open with tar or zip. i aleardy use custom rom, there's any chance install custom rom by some how encrypt the file so i can not open it. did i should reflash the stock rom then try change the logo image?
my phone is j5
Huawei, again, wew.
At the moment, charging offline while on GSI, reboots the phone to the OS.
So, let's simply fix that by:
Downloading this zip;
Pushing it by any means* in the path /vendor/etc/charger (please don't create duplicates path like /vendor/etc/charger/charger, make sure you do it correctly)
Execute:
Code:
ln -s /vendor/etc/charger /system/etc/charger
*You can actually use adb within OS:
adb root
adb remount
adb pushor you can mount all partitions within TWRP Mount option, and just push the dir via adb.
Peace.
Dil3mm4 said:
Huawei, again, wew.
At the moment, charging offline while on GSI, reboots the phone to the OS.
So, let's simply fix that by:
Downloading this zip;
Pushing it by any means* in the path /vendor/etc/charger (please don't create duplicates path like /vendor/etc/charger/charger, make sure you do it correctly)
Execute:
*You can actually use adb within OS:
adb root
adb remount
adb push
or you can mount all partitions within TWRP Mount option, and just push the dir via adb.
Peace.
Click to expand...
Click to collapse
Error pushing on adb, Doesn't work on mate 9,will appreciate if you provide more instructions for installation.
Thank you!
The partitions are mostly to small partitioned... On honor 9 lite i used product partition instead...
Its not forever... every dirty flash on system or updating vendor security patch level will drop it. A magisk module dont work cause its mounted to late...
Darkest-Dark said:
The partitions are mostly to small partitioned... On honor 9 lite i used product partition instead...
Its not forever... every dirty flash on system or updating vendor security patch level will drop it. A magisk module dont work cause its mounted to late...
Click to expand...
Click to collapse
"Nothing lasts forever and we both know hearts can change"
-Guns 'N' Roses
Anyways, yeah, updates on vendor will wipe this "hack".
But, better than nothing
No need for this if you wipe data with stock recovery and then flash ROM + GApps, and then factory reset in stock recovery. My phone chargea fine in "offline mode."
Dil3mm4 said:
"Nothing lasts forever and we both know hearts can change"
-Guns 'N' Roses
Anyways, yeah, updates on vendor will wipe this "hack".
But, better than nothing
Click to expand...
Click to collapse
Directly modifying /system/etc/charger also seems to be effective.Could you make it into a magisk module?
Ccboxes said:
Directly modifying /system/etc/charger also seems to be effective.Could you make it into a magisk module?
Click to expand...
Click to collapse
Here's your answer. Read the thread first.
Darkest-Dark said:
A magisk module dont work cause its mounted to late...
Click to expand...
Click to collapse
Thanks for this Fix. Works awesome on Mate 10 lite with RR Official.
I installed on other way cause ADB provided to many Error Messages.
Downloaded ZIP
Extraxted ZIP File
Copied the extracted Folder to /vendor/etc/ with Root Explorer. (Asked me to mount as R/W. Says YES)
This Takes some minutes.
Rebooted to TWRP, mounted system and vendor
Opened the TWRP Terminal and executed the Command
ln -s /vendor/etc/charger /system/etc/charger
Done and works awesome Thank you Dil3mm4 !
Dil3mm4 said:
Huawei, again, wew.
At the moment, charging offline while on GSI, reboots the phone to the OS.
So, let's simply fix that by:
Downloading this zip;
Pushing it by any means* in the path /vendor/etc/charger (please don't create duplicates path like /vendor/etc/charger/charger, make sure you do it correctly)
Execute:
Code:
ln -s /vendor/etc/charger /system/etc/charger
*You can actually use adb within OS:
adb root
adb remount
adb pushor you can mount all partitions within TWRP Mount option, and just push the dir via adb.
Peace.
Click to expand...
Click to collapse
Hey,
I did everything like destriben, but it did not work for my Mediapad M5,
it still boots up when I wanted to change while my device is powered off.
anyone to tell me how i can use this on aosp 8,1 treble rom ? i am new on huawei, treble rom ... thanks
leap_ahead said:
anyone to tell me how i can use this on aosp 8,1 treble rom ? i am new on huawei, treble rom ... thanks
Click to expand...
Click to collapse
anyone ?
leap_ahead said:
anyone ?
Click to expand...
Click to collapse
Dude, there is this new term called reading the thread, i know it's a bit hard to take in at first, but you'll get the hang of it. If you can't read, then you shouldn't be here.
This cause reboot constantly.
i've p8 lite 2017 (Pra-LX1) with GSI 8.1
crayonicle said:
Dude, there is this new term called reading the thread, i know it's a bit hard to take in at first, but you'll get the hang of it. If you can't read, then you shouldn't be here.
Click to expand...
Click to collapse
I read the instruction.but many user and me have problem with this,
so its not my false
leap_ahead said:
I read the instruction.but many user and me have problem with this,
so its not my false
Click to expand...
Click to collapse
if many users, including you, that have this problem, then all of you should read the thread, again and again until you understand
the instructions are very clear on what to do.
Everytime we flash a new system image this command has to be executed, right @Dil3mm4?
Will it work if @phhusson includes the "ln" command to the script rw-system.sh, after identifying the device as an Huawei device?
that`s good
I have already post a second variant of tutorial. Works 100% and its easy.
TUT 2:
Downloaded ZIP
Extraxted ZIP File
Copied the extracted Folder to /vendor/etc/ with Root Explorer. (Asked me to mount as R/W. Says YES)
This Takes some minutes.
Rebooted to TWRP, mounted system and vendor
Opened the TWRP Terminal and executed the Command
ln -s /vendor/etc/charger /system/etc/charger
Reboot and done
Copkiller2010 said:
I have already post a second variant of tutorial. Works 100% and its easy.
TUT 2:
Downloaded ZIP
Extraxted ZIP File
Copied the extracted Folder to /vendor/etc/ with Root Explorer. (Asked me to mount as R/W. Says YES)
This Takes some minutes.
Rebooted to TWRP, mounted system and vendor
Opened the TWRP Terminal and executed the Command
ln -s /vendor/etc/charger /system/etc/charger
Reboot and done
Click to expand...
Click to collapse
same things done but not working, huawei p20 lite android 10
I have this offline charging problem also in my Lenovo s5.