Related
Sorry if it is a silly question. I am new to installing new ROM and flashing stuff. I have come across the thread on TWRP recovery where it says that to install it, we have to flash it from other recoveries(i.e. CWM or AmonRA). What if I have none of these? Should I install one of them at first place and then proceed to flash TWRP or, there is some other way out? Thanks.
flash_image, Flash Image GUI, fastboot, another recovery, LGMDP.exe for unrooted phones. Read the sticky threads.
Sent from my LG-P500 using XDA App
dr.notor said:
flash_image, Flash Image GUI, fastboot, another recovery, LGMDP.exe for unrooted phones. Read the sticky threads.
Sent from my LG-P500 using XDA App
Click to expand...
Click to collapse
Thanks Sir for your quick response. Will go through it.....
developer++ said:
Sorry if it is a silly question. I am new to installing new ROM and flashing stuff. I have come across the thread on TWRP recovery where it says that to install it, we have to flash it from other recoveries(i.e. CWM or AmonRA). What if I have none of these? Should I install one of them at first place and then proceed to flash TWRP or, there is some other way out? Thanks.
Click to expand...
Click to collapse
root using gingerbreak,download latest rom manger and install clockwork recovery from there - if want to change reovery to twrp just flash from clockowrk recovery after it gets installed
this may help u http://forum.xda-developers.com/showthread.php?t=1038338
make sure usb debugging is enabled while installing custom recovery from rom manger ,make sure u download the latest rom manger from market
welcome to world of custom rom
shhbz said:
root using gingerbreak,download latest rom manger and install clockwork recovery from there - if want to change reovery to twrp just flash from clockowrk recovery after it gets installed
this may help u http://forum.xda-developers.com/showthread.php?t=1038338
make sure usb debugging is enabled while installing custom recovery from rom manger ,make sure u download the latest rom manger from market
welcome to world of custom rom
Click to expand...
Click to collapse
Thanks for the info. Was really a nice descriptive guide for newbies.
One more question. I am on stock froyo 2.2.2 and have flashed TWRP recovery which creates partition in ext4 only. Now I have also flashed Darktremor A2SD which fails to move dalvik to sd card which I assume is because of the ext4 partition that is not recognised by the stock rom. Am I correct with my assumption?
Is flashing another rom is the only way out? If yes, how should I move the existing apps from my stock rom to the new row. Thanks.
Code:
cat /proc/filesystems
will tell you what your kernel supports.
shhbz said:
root using gingerbreak,download latest rom manger and install clockwork recovery from there - if want to change reovery to twrp just flash from clockowrk recovery after it gets installed
this may help u http://forum.xda-developers.com/showthread.php?t=1038338
make sure usb debugging is enabled while installing custom recovery from rom manger ,make sure u download the latest rom manger from market
welcome to world of custom rom
Click to expand...
Click to collapse
This method is not quite OK for me. Did anyone try to actually install that recovery using "Phone Terminal Emulator method"?
I mean this.
adb shell
su (it will ask for root permission in your phone screen just allow)
mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
cat /sdcard/flash_image > /system/bin/flash_image
chmod 755 /system/bin/flash_image
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak (you will get an error just proceed)
mount -o remount,ro -t yaffs2 /dev/block/mtdblock1 /system
flash_image recovery /sdcard/LGp500-recovery-v12.img (note just name the blue marked as the same as your custom recovery name and should end with .img)
Click to expand...
Click to collapse
Martin "skunk" Rotter said:
This method is not quite OK for me. Did anyone try to actually install that recovery using "Phone Terminal Emulator method"?
I mean this.
Click to expand...
Click to collapse
Click the link in my signature. There are 3 perfectly working methods to flash recovery. Dunno what the problem really is.
Well, if course i know these methods and i used it many times. Maybe author of this (extremely interesting and incredibly looking) recovery could mention these methods in his thread. I think that only "flash this ZIP via your CWM"-like tutorial is not enough for some users and then they are confused -> and then new threads like this are created.
Martin "skunk" Rotter said:
Well, if course i know these methods and i used it many times. Maybe author of this (extremely interesting and incredibly looking) recovery could mention these methods in his thread. I think that only "flash this ZIP via your CWM"-like tutorial is not enough for some users and then they are confused -> and then new threads like this are created.
Click to expand...
Click to collapse
That thread is a development thread for that particular recovery. There is absolutely no difference when flashing this or another recovery (like AmonRa or CWM.) So, there are enough howtos here (mentioned in the sticky thread that noone reads) to cover flashing recovery.
Development section is for development, not for repeating redundant stuff over and over again.
I get it, but obvíously developer++ doesn't.
Martin "skunk" Rotter said:
This method is not quite OK for me. Did anyone try to actually install that recovery using "Phone Terminal Emulator method"?
I mean this.
Click to expand...
Click to collapse
well that an outdated mwthod and a lengthy procedure so why not use rom manger and get the latest clockwork recovery and easily shift to whichever recovery u are wiling to use
shhbz said:
well that an outdated mwthod and a lengthy procedure so why not use rom manger and get the latest clockwork recovery and easily shift to whichever recovery u are wiling to use
Click to expand...
Click to collapse
There is nothing outdated about the method. And why not use ROM Manager? Because ROM Manager absolutely lacks any sanity checks when flashing recovery. It will happily download incomplete *.img (happens a LOT esp. on 2G/3G) and flash it, making your phone stuck with fastboot.
I have mentioned numerous times that they should distribute a signed ZIP with recovery contained and check the ZIP before flashing. (Even the ZIP format itself has a CRC checks built in if you are too lazy to bother with manifests.)
There are tons of complaints from people all over the board about ROM Manager half-bricking their phones, I am really stunned by the bad design of the feature and lack of action to fix it.
shhbz said:
well that an outdated mwthod and a lengthy procedure so why not use rom manger and get the latest clockwork recovery and easily shift to whichever recovery u are wiling to use
Click to expand...
Click to collapse
Well, but don't you see that problem?
get the latest clockwork recovery and easily shift to whichever recovery u are wiling to use
Click to expand...
Click to collapse
Why this? Some say usual recovery installation methods will work and you say to use this (weird) method. Then you can't wonder, why creator of this thread is confused.
dr.notor said:
There is nothing outdated about the method. And why not use ROM Manager? Because ROM Manager absolutely lacks any sanity checks when flashing recovery. It will happily download incomplete *.img (happens a LOT esp. on 2G/3G) and flash it, making your phone stuck with fastboot.
I have mentioned numerous times that they should distribute a signed ZIP with recovery contained and check the ZIP before flashing. (Even the ZIP format itself has a CRC checks built in if you are too lazy to bother with manifests.)
There are tons of complaints from people all over the board about ROM Manager half-bricking their phones, I am really stunned by the bad design of the feature and lack of action to fix it.
Click to expand...
Click to collapse
yes the problem was there of phone getting into fastboot mode ,but i beieve the problem was later solved and then it worked fine as many users dont follow instruction carefully which land them into probs.yes i do agree on ur internet connection part if that lacks than they need to use adb to get it done.
since,many users are not able to use adb and stuff just bcoz they cannot configure it properly.
so they have these option to do it the easiest way if they are not able to configure adb to work properly.
shhbz said:
yes the problem was there of phone getting into fastboot mode ,but i beieve the problem was later solved and then it worked fine as many users dont follow instruction carefully which land them into probs.yes i do agree on ur internet connection part if that lacks than they need to use adb to get it done.
Click to expand...
Click to collapse
I do not believe they ever changed the ROM Manager design in the way suggested. The problem is with lack of sanity checks, do not blame users for their sucky internet connection.
Martin "skunk" Rotter said:
Well, but don't you see that problem?
Why this? Some say usual recovery installation methods will work and you say to use this (weird) method. Then you can't wonder, why creator of this thread is confused.
Click to expand...
Click to collapse
It depends on the users choice what they choose as we started with thunderg recovery than came the clockwork method and now the twrp method.
there are various threads and discussion on the first two method .
go and read threads as i said is a matter of choice which way u want it to get it done.
so make ur choice in which u are comfortable and confident.
dr.notor said:
Code:
cat /proc/filesystems
will tell you what your kernel supports.
Click to expand...
Click to collapse
the above command gives me the following output:
Code:
cat /proc/filesystems
nodev sysfs
nodev rootfs
nodev bdev
nodev proc
nodev tmpfs
nodev debugfs
nodev sockfs
nodev pipefs
nodev anon_inodefs
nodev rpc_pipefs
nodev inotifyfs
nodev devpts
ext3
ext2
nodev ramfs
vfat
nodev nfs
yaffs
yaffs2
as seen my kernel does not support ext4.
dr.notor said:
Click the link in my signature. There are 3 perfectly working methods to flash recovery. Dunno what the problem really is.
Click to expand...
Click to collapse
Yes, I have been following links from your signature. They are perfectly ok. But the situation I got into was that I flashed TWRP recovery and created a ext4 partition which was the only format supported by TWRP. Then I flashed Darktremor A2SD but it was unable to mount the ext4 partition as such was unable to move dalvik to sd.
Martin "skunk" Rotter said:
Well, if course i know these methods and i used it many times. Maybe author of this (extremely interesting and incredibly looking) recovery could mention these methods in his thread. I think that only "flash this ZIP via your CWM"-like tutorial is not enough for some users and then they are confused -> and then new threads like this are created.
Click to expand...
Click to collapse
Yes, I too think an additional info about the other ways to install recovery as stated by dr.notor would be very much helpful.
And as for creating new threads I sincerely apologize if I have a made a mistake here.
Flash the correct franco kernel, it supports ext4 just fine. (v1 versions are for CM7 6.6.x and stock(-based) GB ROMs only!)
I have the same issue as reported here: http://forum.xda-developers.com/showpost.php?p=64003605&postcount=108
I can't see the former poster got an reply, but is there a way to fix this? TWRP reports it cannot mount system due to it being read-only. Unchecking read-only on system mount within TWRP does not work.
ksjoet said:
I have the same issue as reported here: http://forum.xda-developers.com/showpost.php?p=64003605&postcount=108
I can't see the former poster got an reply, but is there a way to fix this? TWRP reports it cannot mount system due to it being read-only. Unchecking read-only on system mount within TWRP does not work.
Click to expand...
Click to collapse
I'm sure it's fixable, but it needs some device-specific knowlegde. The thing here is that the Z4T's TWRP build is a custom one by AndroPlus with the help of dl12345. I have asked them for help in the AndroPlus kernel thread.
I'm looking into possible workarounds. Maybe we can backup/restore using adb, or boot another custom recovery from fastboot that does the job.
Hey everyone,
A few days ago, I decided to downgrade from AICP 11 back to 10 (Android 6.0.1 to 5.1.1), wiped everything but internal storage. When flashing, I got an error, saying that the /vendor partition was missing, and indeed, while it existed, I could only mount it forcefully, because the device was busy.
This lead to a complete wipe, as after a reboot, TWRP asked for an encryption password, which I didn't set. Here, I did a factory reset & wiped everything. After that, I tried flashing again (5.1.1), but after it was completed, I got a line, which said "Couldn't unmount /system", which is true, as it's already unmounted. But when I mount it, all the files that are supposed to be installed seem to be there.
When I reboot the device, it gets stuck on the Google logo.
Frankly, I'm afraid to even flash back to stock, so I was hoping that someone more experienced could help me out.
It should be noted, that I still have access to fastboot, and TWRP.
Thanks in advance,
DecentM
How did you force mount /vendor?
Can you clarify where you are seeing these problems? (TWRP or within Android)
Do you have any nandroid backups to test and see if they work?
dmantilal said:
How did you force mount /vendor?
Can you clarify where you are seeing these problems? (TWRP or within Android)
Do you have any nandroid backups to test and see if they work?
Click to expand...
Click to collapse
I used mount -f and umount -f in the TWRP terminal
I see all these problems in TWRP, since I can't boot/get past the initial Google logo.
I do have a nandroid backuip on my laptop (as I had to wipe the tablet clean), but that's currently unavailable for me to use, I'll reply back when I tried it.
I doubt it will work, because it just extracts data to a predefined path, which seems like the same thing an installer zip does.
DecentM said:
I used mount -f and umount -f in the TWRP terminal
I see all these problems in TWRP, since I can't boot/get past the initial Google logo.
I do have a nandroid backuip on my laptop (as I had to wipe the tablet clean), but that's currently unavailable for me to use, I'll reply back when I tried it.
I doubt it will work, because it just extracts data to a predefined path, which seems like the same thing an installer zip does.
Click to expand...
Click to collapse
Why did you need /vendor mounted in TWRP?
I thought flashing used dd (command) or similar to copy the *.img file to the partition (or, more accurately, the block device). If /vendor is mounted during *.img copy, that would most likely cause errors.
dmantilal said:
Why did you need /vendor mounted in TWRP?
I thought flashing used dd (command) or similar to copy the *.img file to the partition (or, more accurately, the block device). If /vendor is mounted during *.img copy, that would most likely cause errors.
Click to expand...
Click to collapse
I mounted it, because when I initially restored the 5.1.1 rom, I got an error, saying that the /vendor partition wasn't mounted.
DecentM said:
I mounted it, because when I initially restored the 5.1.1 rom, I got an error, saying that the /vendor partition wasn't mounted.
Click to expand...
Click to collapse
You are sure it was complaining about "unmounted", rather than "mounted"?
Do these roms include a vendor.img? You may need to flash the stock 5.1.1 vendor.img.
Either way, unless you mkfs'ed or resize2fs'ed the partitions, they should be fine. Full wipe & go.
dmantilal said:
You are sure it was complaining about "unmounted", rather than "mounted"?
Do these roms include a vendor.img? You may need to flash the stock 5.1.1 vendor.img.
Either way, unless you mkfs'ed or resize2fs'ed the partitions, they should be fine. Full wipe & go.
Click to expand...
Click to collapse
I'm not sure.
I already did a full wipe, but it still had issues. I'll try again tomorrow, and report back on how it went.
DecentM said:
I'm not sure.
I already did a full wipe, but it still had issues. I'll try again tomorrow, and report back how it went.
Click to expand...
Click to collapse
Having a mismatched vendor.img could be your problem.
No ROM I know of includes a vendor.img. I think it is a legal issue, like including GApps with a ROM.
dmantilal said:
Having a mismatched vendor.img could be your problem.
No ROM I know of includes a vendor.img. I think it is a legal issue, like including GApps with a ROM.
Click to expand...
Click to collapse
I don't think that the issue is with the vendor image anymore, but with the partitions in general. I always had a mismatched vendor image, as it only results in a modal box after boot.
My problem is again, with the /system partition not being visible to flashable zip files.
Mismatched vendor.img can also cause bootloops and other quirks like battery-charge percentage inaccuracies.
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.
Can I boot to the root filesystem using fastboot and edit the file from there?
I wanted to edit:
/etc/mkshrc
xracerx123 said:
Can I boot to the root filesystem using fastboot and edit the file from there?
I wanted to edit:
/etc/mkshrc
Click to expand...
Click to collapse
It is generally not possible to perform file changes through fastboot/bootloader. To do so, you need to have a runtime environment such as TWRP. Bootloader/fastboot generally only handles partition images.
V0latyle said:
It is generally not possible to perform file changes through fastboot/bootloader. To do so, you need to have a runtime environment such as TWRP. Bootloader/fastboot generally only handles partition images.
Click to expand...
Click to collapse
Unable to edit /etc/mkshrc
I just tried to add variables on Android /etc/mkshrc file but I get an error: Read-only file system Further, I have tried to use adb remount, but it says inaccessible or not found. I tried to use the following: mount -o remount,rw /...
forum.xda-developers.com
Do refer to the above thread, it is sort of related to this topic.
Is it possible, to edit right on the /etc itself? without going through twrp?
Is there any tools that can help?
xracerx123 said:
Unable to edit /etc/mkshrc
I just tried to add variables on Android /etc/mkshrc file but I get an error: Read-only file system Further, I have tried to use adb remount, but it says inaccessible or not found. I tried to use the following: mount -o remount,rw /...
forum.xda-developers.com
Do refer to the above thread, it is sort of related to this topic.
Click to expand...
Click to collapse
It mentions using ADB, which can only be used either through system or recovery.
xracerx123 said:
Is it possible, to edit right on the /etc itself? without going through twrp?
Click to expand...
Click to collapse
Not through bootloader or fastboot. You can dump an image, edit it, and reflash it, but this would all be much more complicated than using TWRP, which would allow you to mount the partition as r+w so you can effect the edit you want.
xracerx123 said:
Is there any tools that can help?
Click to expand...
Click to collapse
Yes...TWRP.
V0latyle said:
It mentions using ADB, which can only be used either through system or recovery.
Not through bootloader or fastboot. You can dump an image, edit it, and reflash it, but this would all be much more complicated than using TWRP, which would allow you to mount the partition as r+w so you can effect the edit you want.
Yes...TWRP.
Click to expand...
Click to collapse
I am using Pixel 6A, currently there is no TWRP. https://twrp.me/Devices/
xracerx123 said:
I am using Pixel 6A, currently there is no TWRP. https://twrp.me/Devices/
Click to expand...
Click to collapse
Details like this are beneficial when asking questions.
The short answer to your original question is no, what you want to do is not possible.
is your bootloader even unlockable?
https://www.xda-developers.com/how-to-unlock-bootloader-root-magisk-google-pixel-6a
xracerx123 said:
I am using Pixel 6A, currently there is no TWRP.
Click to expand...
Click to collapse
but there is Evolution X custom recovery at least
https://forum.xda-developers.com/t/4514881