Related
Hi everyone,
I tried using a script which automated the install for the the custom recovery, but I started to get messages that it ran out of disk space (I can't link to the file due to my noob status). I probably should have come here first before using that script, but such as life..
I have no important data on the phone, if I lose it all that's ok.
It rebooted and my p500 waits with the following
"Fastboot mode started"
"udc_start()"
It also gives some info when USB is connected ie.
"- suspend -"
"- reset -"
Do I have a paperweight?
thanks and sorry for the newb post ..
edit: so I found this : http://forum.xda-developers.com/showthread.php?t=1003790 and
http://forum.xda-developers.com/showthread.php?t=875881
and have gotten it to the yellow emergency mode, not sure how to flash it from here though.
edit2: dling the stock firmware from http://forum.xda-developers.com/showthread.php?t=1073827
edit3: there's this as well.. http://forum.xda-developers.com/showthread.php?t=1088046 If I try this method, will it screw up again from too little free disk space?
I'm to drunk to guide our give you the link to fix it but I will tell you, you can fix it just hold on we will help you ; ) and we don't by the time I wake up I will help you its ok ))
Sent from my LG-P500 using XDA Premium App
dislplin01 said:
I'm to drunk to guide our give you the link to fix it but I will tell you, you can fix it just hold on we will help you ; ) and we don't by the time I wake up I will help you its ok ))
Sent from my LG-P500 using XDA Premium App
Click to expand...
Click to collapse
thank you very much, I appreciate it haha
Your phone has booted in fastboot mode. Go to development section and read a tutorial how to recover from fastboot.
Sent from my LG-P500 using XDA Premium App
setTopbox said:
thank you very much, I appreciate it haha
Click to expand...
Click to collapse
Then did u unbricked now
Mahesh
go here....
http://forum.xda-developers.com/showthread.php?t=1088046
or here
http://forum.xda-developers.com/showthread.php?p=13813493
How to install Android SDK /ADB
http://lgoptimusonep500.blogspot.com/2011/01/how-to-install-android-sdk-adb.html
dislplin01 said:
I'm to drunk to guide our give you the link to fix it but I will tell you, you can fix it just hold on we will help you ; ) and we don't by the time I wake up I will help you its ok ))
Sent from my LG-P500 using XDA Premium App
Click to expand...
Click to collapse
Most honest post I've seen on the entire forum.
Sent from my Kyocera Echo.
mvgadagi said:
Then did u unbricked now
Mahesh
Click to expand...
Click to collapse
I got the phone working again - thanks! I guess it's not a great idea to install the custom recovery
with low disk space?
setTopbox said:
I got the phone working again - thanks! I guess it's not a great idea to install the custom recovery
with low disk space?
Click to expand...
Click to collapse
Hmmm. Well, should not matter? /recovery uses a separate partition. Perhaps you flashed a corrupt (incomplete) image?
well if u ever wish to install recovery just download rom manger from market (latest) and install recovery from rom manger option make sure u hav eusb debugging enabled. it works easy
shhbz said:
well if u ever wish to install recovery just download rom manger from market (latest) and install recovery from rom manger option make sure u hav eusb debugging enabled. it works easy
Click to expand...
Click to collapse
Erm... reading all the posts about fastboot after using ROM Manager for this, I guess I would rather stick with the custom script using flash_image.
doktornotor said:
Hmmm. Well, should not matter? /recovery uses a separate partition. Perhaps you flashed a corrupt (incomplete) image?
Click to expand...
Click to collapse
hmm, I'm not sure (when I dl'd the file I did compare the hash as per instructions). I used the following instructions:
manast.com/2011/05/07/how-to-install-custom-recovery-on-lg-optimus-one-p500
I then went into a terminal emulator, and ran "sh /sdcard/rf.sh". At that point the output of the script started to say "disk full" (and then it reboot into the fastboot prompt).
setTopbox said:
I then went into a terminal emulator, and ran "sh /sdcard/rf.sh". At that point the output of the script started to say "disk full" (and then it reboot into the fastboot prompt).
Click to expand...
Click to collapse
No idea about that script. Using flash_image and never had any issue with "disk full", frankly the message does not make sense. All you need is to copy the recovery image to SD and run as root:
Code:
# flash_image recovery /sdcard/recovery.img
Done.
doktornotor said:
No idea about that script. Using flash_image and never had any issue with "disk full", frankly the message does not make sense. All you need is to copy the recovery image to SD and run as root:
Code:
# flash_image recovery /sdcard/recovery.img
Done.
Click to expand...
Click to collapse
I'm getting permission denied when trying to use flash_image. Gingerbreak says the device is rooted, and the terminal does ask for superuser permission when i open it (su works in the terminal). I also tried chmod 755 flash_image but that didn't work either.
the permissions for flash_image are r-xr-x any thoughts ?
edit: apparently the sdcard is mounted with -noexecute ? So I tried copying flash_image to / but it's read only. Is there somewhere where I can execute this?
This rf.sh script seems most notorious, I too went into fastboot after that. Doktornotor's method worked (in fact I think he/she was the one who bailed me out back then as well).
If you got into fastboot, most probably you have a rooted phone.
To use flash_image you need to get the flash_image.sh on the root of your sd card. Search the forum for Amon-Ra custom recovery, and you shall find this file in that thread (it is required for Amon ra setup). Log in to your adb console, and use fastboot to push the new image in the recovery partition.
Unless your recovery.img or flash_image.sh is corrupted, it will work for sure.
Keep in mind, fastboot is a very powerfull tool, if you can access it, you're safe.
Cheers,
Alex
did you get out??
just flash stock firmware with kdz worked for me bro
Buddy,
You do not need to flash anything with KDZ. The ROM is fine nothing happened to it. All your issue is with the recovery being flashed wrongly for some reason.
I had the same issue just yesterday and I managed to flash the recovery through fastboot.
What you need to do is:
1. Install android SDK from Google.
2. Connect the phone while it is on fastboot.
3. If your windows does not find the fastboot drivers online, use the drivers in this link:
http://www.megaupload.com/?d=39ZR16W1
4. extract the .zip file that you copied to your SD. The one that contains the recovery.
5. Copy the recover.img (or whatever the name of the .img file in the .zip file) to the folder inside the android sdk where fastboot.exe is located (I think its the tools folder)
6. Copy the adbwinapi.dll file from the android SDK\platform-tools\ to the folder containing fastboot.
7. issue the command (and replace recovery.img with the .img file name you have):
fastboot flash recovery recovery.img
fastboot reboot
Dr.Alani said:
Buddy,
You do not need to flash anything with KDZ. The ROM is fine nothing happened to it. All your issue is with the recovery being flashed wrongly for some reason.
I had the same issue just yesterday and I managed to flash the recovery through fastboot.
What you need to do is:
1. Install android SDK from Google.
2. Connect the phone while it is on fastboot.
3. If your windows does not find the fastboot drivers online, use the drivers in this link:
http://www.megaupload.com/?d=39ZR16W1
4. extract the .zip file that you copied to your SD. The one that contains the recovery.
5. Copy the recover.img (or whatever the name of the .img file in the .zip file) to the folder inside the android sdk where fastboot.exe is located (I think its the tools folder)
6. Copy the adbwinapi.dll file from the android SDK\platform-tools\ to the folder containing fastboot.
7. issue the command (and replace recovery.img with the .img file name you have):
fastboot flash recovery recovery.img
fastboot reboot
Click to expand...
Click to collapse
I appreciate the information. When I'm in adb, su won't allow me to gain root access on the phone. The phone itself is rooted using gingerbreak though.
setTopbox said:
I appreciate the information. When I'm in adb, su won't allow me to gain root access on the phone. The phone itself is rooted using gingerbreak though.
Click to expand...
Click to collapse
I do not see how you need to use adb.
Sent from my LG-P500 using XDA App
So there it is. It incorporates two workarounds:
gr_init() called twice to fix the black screen problem
small kernel patch to allow param.ko to update params.blk inside /mnt/.lfs before rebooting
This is very preliminary work. I can not provide any guarantee it will not brick your device or cause a rift in the space-time continuum (it hasn't bricked mine or caused a rift but that's statistically insignificant).
I recommend you flash this recovery with dd and not Odin/heimdall after rooting with the system.img method (see http://forum.xda-developers.com/showthread.php?t=2104638), but be careful with the partition number (for example if you forget the number 2 and type mmcblk0p1 you will end up rewriting your partition table, thus bricking your device).
Before flashing anything, consider making a backup of the original recovery partition (other partitions can be backed up as well: EFS, modemfs, etc. see http://forum.xda-developers.com/showthread.php?t=2032642)
Code:
dd if=/dev/block/mmcblk0p21 of=/sdcard/backup-recovery.img
Then install CWM:
Code:
dd if=/sdcard/recovery-clockwork-6.0.2.7-golden-2.img of=/dev/block/mmcblk0p21
or if you copied the file on the external sd:
Code:
dd if=/storage/extSdCard/recovery-clockwork-6.0.2.7-golden-2.img of=/dev/block/mmcblk0p21
Update: version 2 that works with both internal and external sdcard. If you want to use the external SD, it must be formated with one FAT32 partition (mmcblk1p1). Make sure to repartition/reformat your SD if this is not the case! This can be done in the systems parameters of the phone, or alternatively under Windows/Linux.
Here is an Odin flashable package made by spawk (thanks to him): http://forum.xda-developers.com/showpost.php?p=36962108&postcount=59 Contrary to the method above, flashing with Odin (or Heimdall) will increase your download count!
To reboot into recovery, you can either :
- use the vol-up + home + power combo, but it does not work on all phones (reason unknown)
- with stock, use ROM Manager to reboot into recovery
- with CM10, well simply select recovery when rebooting
- with adb enabled, run "adb reboot recovery"
If your current system fails to boot, and you need to get into recovery, and the three-button combo does not work, you can always reflash a known working system.img and use one of the methods above.
Adb sideloading does not seem to work. Need to investigate why
so just flash it? thats it? and we will have working display?
Can u provide more info? Becuase i think some users will not understand the procedure
Men can you provide the device tree and your changes on kernel so I can merge them on my repos?
Enviado desde mi GT-I8190 usando Tapatalk 2
OliverG96 said:
Men can you provide the device tree and your changes on kernel so I can merge them on my repos?
Click to expand...
Click to collapse
There are no kernel changes. I just used GT-I8190_JB_Opensource_Update1.zip with the golden_defconfig
You need to update graphics.c and android_reboot.c (attached). I will upload the device tree a bit later, need to clean it up first.
xd.bx said:
There are no kernel changes. I just used GT-I8190_JB_Opensource_Update1.zip with the golden_defconfig
You need to update graphics.c and android_reboot.c (attached). I will upload the device tree a bit later, need to clean it up first.
Click to expand...
Click to collapse
Thanks, I'll merge this on my repos, if you want we can work together on cm10
Enviado desde mi GT-I8190 usando Tapatalk 2
It gives me No such file or directory
1.)You need to make a good procedure to the first post. this is chaos.
what do u mean by updating graphics.c..... replacing by new one? and the other file location?
2.) What do u mean by : be careful with the partition number (for example if you forget the number 2 you will end up rewriting your partition table, thus bricking your device).
Shapeshift said:
You need to make a good procedure to the first post. this is chaos.
what do u mean by updating graphics.c..... replacing by new one? and the other file location?
Click to expand...
Click to collapse
There's a board define to specify a different graphics.c Just using it and copying the correct graphics.c will work...
Enviado desde mi GT-I8190 usando Tapatalk 2
and android reboot.c where do i copy both files.
Never mind I did it. However I've got an Error mounting /sdcard!
Shapeshift said:
and android reboot.c where do i copy both files.
Click to expand...
Click to collapse
I'm gonna push to cm gerrit the workaround to keeep android_reboot.c inside device tree
Enviado desde mi GT-I8190 usando Tapatalk 2
OliverG96 said:
Thanks, I'll merge this on my repos, if you want we can work together on cm10
Click to expand...
Click to collapse
I'd be glad to work with you on this, especially considering that you already are a cm developer (I'm not really used to gerrit)
Can i honestly ask you to make a procedure? like steps or something. i am not good at cwm and things
I am asking you : how to update graphics.c and android reboot.c ? plz help asap
Shapeshift said:
Can i honestly ask you to make a procedure? like steps or something. i am not good at cwm and things
Click to expand...
Click to collapse
Sure. First you need to root your phone with the system.img method you'll find in other threads.
Next, uncompress and copy the recovery.img on your SD card, which is then to be inserted in the phone.
Then you enable must adb debugging in the system preferences, and with the Android SDK installed on your PC, run "adb shell". If it says adb: command not found you'll have to find where the adb binary is, and use the full path (such as, "C:\Program Files\android-sdk\platform-tools\adb.exe" but that's an example, you must find what the proper path is).
Next after having run "adb shell" you enter "su" to obtain root privileges (you will get a warning prompt. simply answer yes). Finally, run "dd if=/sdcard/recovery-clockwork-6.0.2.7-golden.img of=/dev/block/mmcblk0p21" to install CWM, and then you can reboot into CWM after exiting the shell (use the "exit" command twice) with the command "adb reboot recovery".
Now regarding the two C files I posted, it is a matter of copying them into your CM10 tree.
graphics.c goes into bootable/recovery/minui/ (however it is better to use the BoardConfig to setup a device-specific graphics.c)
android-boot.c goes into system/core/libcutils/
This will only get you so far, you'll need for instance Oliver's device tree to compile golden.
hm. i have already adb and i have specified path in windows for it. so i can run it everywhere. my device is rooted and i have only one more question for you. Do i need external sd? cant i put it onto internal sd?
Shapeshift said:
hm. i have already adb and i have specified path in windows for it. so i can run it everywhere. my device is rooted and i have only one more question for you. Do i need external sd? cant i put it onto internal sd?
Click to expand...
Click to collapse
Yes, sure. Or use /tmp/ to store it temporarily (the file will go away after the next boot)
So I just found out something really cool, the stock (prebuilt) j4fs.ko and param.ko modules can be loaded along a 3.0.31 kernel built from source, which means it will be possible to simply use them instead of this android_boot ugly hack.
ok i have installed cwm. but it cant mount sdcard. try to fix. nothing is mountable. cant mount sdcard as well as backup folder
Just posting here to say a big thank you to all of you devs!
:good:
PS: And a small (silly) question:
as i 'm not using a pre-rooted ROM. What if I made an ODIN flashable tar.md5 of the original *.img? Wouldnt it work?
I have about 30 of these phones and people have been asking me how I get SuperSU on them:
https://youtu.be/qkik4q5ERaU
NitroKoS said:
I have about 30 of these phones and people have been asking me how I get SuperSU on them:
https://youtu.be/qkik4q5ERaU
Click to expand...
Click to collapse
In the video, you said Kingroot 4.5
There is new:
Kingroot V5.0.4 should I get it instead?
Handsome Jack said:
In the video, you said Kingroot 4.5
There is new:
Kingroot V5.0.4 should I get it instead?
Click to expand...
Click to collapse
Successfully rooted the Alcatel Streak with KingRoot. But my cell phone won't boot after I applied the KingRoot/SuperSu replacement.
Here is thread on requesting ROM to recover from the issue. Obviously another person had same issue as I did:
https://forum.xda-developers.com/android/help/requesting-alcatel-4060-o-cricket-stock-t3578896
I have uploaded all the partition dd image at mediafire.com excepect /system witch is big file and i have low bandwidth
Note, the recovery image is compressed zip us unzip before dd back
kdm6389 said:
I have uploaded all the partition dd image at mediafire excepect /system witch is big file and i have low bandwidth
Note, the recovery image is compressed zip us unzip before dd back
Click to expand...
Click to collapse
I see many dd files with one particular zip file in mediafire. How can I use these files to flash my Alcatel Streak ROM? I have never done this before and I am newbie here.
Thanks,
jxzz said:
I see many dd files with one particular zip file in mediafire. How can I use these files to flash my Alcatel Streak ROM? I have never done this before and I am newbie here.
Thanks,
Click to expand...
Click to collapse
You need "adb"
use following cmd to replace using,
adb shell
su
dd if=/sdcard/backup/pationno.img of=/the/pation/where/you/want/to/restore
beware!
dd is very lethal in wrong hand, I recommend not use until you are knowing what are you doing, we dont have any TWRP so to save your device.
kdm6389 said:
You need "adb"
use following cmd to replace using,
adb shell
su
dd if=/sdcard/backup/pationno.img of=/the/pation/where/you/want/to/restore
beware!
dd is very lethal in wrong hand, I recommend not use until you are knowing what are you doing, we dont have any TWRP so to save your device.
Click to expand...
Click to collapse
I am quite comfortable handling linux command line shells. However, since my Alcatel Streak phone is stuck at boot, not sure how I can get the adb shell?
After several rounds of factory reset, cache reset, no mater what, the phone simply won't boot and it is stuck with "google " or "android" welcome picture.
I noticed a a guideline of using cygwin in windows PC to run dd for backing up the phone partition image. Is it possible that I copy all your dd files into a cygwin in window 10 PC, then use USB cable to move the files into the phone or flash the phone?
jxzz said:
I am quite comfortable handling linux command line shells. However, since my Alcatel Streak phone is stuck at boot, not sure how I can get the adb shell?
After several rounds of factory reset, cache reset, no mater what, the phone simply won't boot and it is stuck with "google " or "android" welcome picture.
I noticed a a guideline of using cygwin in windows PC to run dd for backing up the phone partition image. Is it possible that I copy all your dd files into a cygwin in window 10 PC, then use USB cable to move the files into the phone or flash the phone?
Click to expand...
Click to collapse
nothing will work unless u have /system image, or working ROM.zip,
Since you have corrupted /system, and your model is different then mine is pop445
i did not uploaded /system bc its wqy more size then recovery
kdm6389 said:
nothing will work unless u have /system image, or working ROM.zip,
Since you have corrupted /system, and your model is different then mine is pop445
i did not uploaded /system bc its wqy more size then recovery
Click to expand...
Click to collapse
Thanks for the information. I searched the web and found many stock ROM for download for many Alcatel models except this model.
Alcatel Streak (model 40600) is dedicated for Cricket and it appears that neither Cricket nor Alcatel releases the ROM for this model.
jxzz said:
Thanks for the information. I searched the web and found many stock ROM for download for many Alcatel models except this model.
Alcatel Streak (model 40600) is dedicated for Cricket and it appears that neither Cricket nor Alcatel releases the ROM for this model.
Click to expand...
Click to collapse
share the stock ROM
I have figured out a way to root easier, I have flashed twrp (with some graphical issues... Working on it) flashed Xposed framework on it, and got native tethering working.
This thread is obsolete now,
for rooting read https://forum.xda-developers.com/android/general/super-guide-alcatel-one-touch-4060a-t3621525
Latest Stock ROM we have | https://forum.xda-developers.com/showpost.php?p=74529924&postcount=205
Instructions:
https://jolla.com/sailfishxinstall/
Download:
http://images.devaamo.fi/sfe/suzu/
thanks to all the guys that worked on this port.
Kernel source:
https://github.com/mer-hybris/android_kernel_sony_msm
This make_ext4fs works for flashing on macOS
For some reason with this build the system-icons vanish for me after restarting the device once :/
I had much better results using this build.
Also by default (at least with the image I linked) only two of the 6 cpu-cores are enabled. To fix that one must add this under the init-section of the /init.loire.pwr.rc file and reboot (All credit for this go to abranson from the #sailfishos-porters irc).
Thanks for this port! are you planning to continue building for Xperia X or is a test build before official release?
Enviado desde mi F5121 mediante Tapatalk
keep going till then, also ive updated the above link
how flash it?
FuLiterary said:
how flash it?
Click to expand...
Click to collapse
read the first post
FuLiterary said:
how flash it?
Click to expand...
Click to collapse
make sure when you are flashing sailfish support only F5121 and does not support sdxc
Hello, friend! I am a Chinese user, I do not understand the tutorial, there is no mor
Jozinek said:
so only Linux or MacOS too?
Click to expand...
Click to collapse
Flashing works on macOS too. You just need to use the make_ext4fs I linked instead of the one linked on top.
janeliang34 said:
Hello, friend! I am a Chinese user, I do not understand the tutorial, there is no mor
Click to expand...
Click to collapse
extract the tar, open a terminal inside the extracted folder and run ./flash.sh
One question. Zip file with AOSP should be moved intact or only vendor folder from inside it?
Seems it has to be whole .zip.
Jozinek said:
i never make something like this in MacOS (i have Macbook Air, but also with Windows), can you write step by step how to make it. This is something totally new for me (i flashed hundreds of XPERIA smartphones, i have Emma tool, but never try this...)
Click to expand...
Click to collapse
Sure thing
First of all your bootloader needs to be unlocked. I'm assuming you already did that but if not you should read about backuping your drm-keys because otherwise they can't be recovered after unlocking your bootloader unless you do that.
If you don't have fastboot installed yet follow this guide.
After that download the first file linked at the top of this thread.
Unpack the archive (if you can't open it I recommend "the unarchiver" from the app-store).
Place both this file and the zip from the third link at the top in the unpacked folder (in the path where the flash.sh is). Don't unpack the .zip file!
After that open a terminal and navigate to your unpacked folder (if you don't know how to do that google for "terminal tutorial mac").
Run
Code:
chmod +x flash.sh
chmod +x make_ext4fs
to mark the flash-script and the make_ext4fs-file as executable.
Boot your device into fastboot mode (hold volume up while it's turned off and plug in your usb-cable) and finally run
Code:
./flash.sh
to install sailfishOS on the device.
If there is a "hybris-recovery.img" file in the directory (can't quite remember if that's the case with this build) also run
Code:
fastboot flash recovery hybris-recovery.img
to install a sailfishOS specific recovery.
After that you can reboot your device and enjoy Sailfish OS
@Jozinek
You didn't unpack the .tar.bz, inside are all files needed to flash. Than You have to move make_ext4fs, AOSP.zip and flash.fs into created (by unpacking) folder and start/cd Terminal there.
Jozinek said:
Edit3 - it worked now, it was bad make_ext4fs, thanks all of you
Click to expand...
Click to collapse
So that means you are doing a review on YouTube, right?
Friend, is there a tutorial for Windows installation? To be more detailed, this is my first contact
janeliang34 said:
Friend, is there a tutorial for Windows installation? To be more detailed, this is my first contact
Click to expand...
Click to collapse
Right now there is no windows support. The final build (which will be officially sold by Jolla) will make windows-installation possible.
If you know your way around cygwin you could probably get it to flash using windows (other than the flash.sh script there's nothing *nix-exclusive).
Is the rom stable enough for daily use ? and is Alien Dalvik available in this rom to run Android apps ?
no android dalvik or any software that needs license, this version is just community version like aosp without play store.
when flashing there's error make_ext4fs: no such file or directory, when i use the second one there's error: wrong exec format
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.