Related
How do i fix this, i dont know what is wrong. CM12 wont flash, even though it is on te device.
Mention your current recovery (PhilZ/ TWRP) and version.
sharkymyn said:
Mention your current recovery (PhilZ/ TWRP) and version.
Click to expand...
Click to collapse
It is TWRP recovery v. 2.8.5
sharkymyn said:
Mention your current recovery (PhilZ/ TWRP) and version.
Click to expand...
Click to collapse
Thanks for the reply, but i fixed it, I just formatted the data again, then copied cm12 onto the phone, flashed it, then it booted up!
unable to mount system after deleting os accidentally
pliz help
Even I am having the same problem. When I flash it says " E unable to mount "/system" I gather from googling that it is malformed partition issue. But I am not able to find fixes for it. Please help
I think the problem was with the Cm 12.1 zip. I installed another rom.zip file (Blisspop rom) and it is working fine now.
can someone please upload the stock "install-recovery.sh"?
It's located in /system/etc.
I forgot to backup it, while rooting the device.
I need it for the OTA updates.
thanks
@vel_tins
Do not flash the ota if you are rooted, you might get bootloop. Full unroot your device before attempting to update. Anyhow, the ota will most likely fail since you already modified your system partition. Your best option is to unroot your device and capture the ota link, modify the ota updater-script and remove the lines that are showing "unexpected contents" errors. The original "install-recovery.sh" is still there, supersu renamed it to something like "/system/etc/install-recovery_original.sh". Keep in mind, you might loose your custom recovery if you renamed it back to "install-recovery.sh".
Well, OTA was a pain in the a**.
Because I had no stock "install-recovery.sh", I've edited the updater-script and removed all the matching entries.
Executed a full un-root.
Tried to flash the modified update.zip via TWRP, but failed because TWRP couldn't mount partitions with this name scheme:
Code:
"/dev/block/platform/[B]7824900.sdhci/by-name/system[/B]", "/system",
(will investigate later, any ideas?)
Because too lazy to modify the updater-script again,
I've booted into fastboot and loaded my "modded" stock recovery, which accepts also self-signed .zips.
Flashing worked well, but on reboot, I got a nice bootloop because of the formerly installed Xposed framework.
Had to restore from a Nandroid Backup and after reboot, I removed Xposed completely.
Eventually, I was able to flash the OTA and got back a working device...
Gosh...
^^
??
vel_tins said:
Well, OTA was a pain in the a**.
Because I had no stock "install-recovery.sh", I've edited the updater-script and removed all the matching entries.
Executed a full un-root.
Tried to flash the modified update.zip via TWRP, but failed because TWRP couldn't mount partitions with this name scheme:
Code:
"/dev/block/platform/[B]7824900.sdhci/by-name/system[/B]", "/system",
(will investigate later, any ideas?)
Because too lazy to modify the updater-script again,
I've booted into fastboot and loaded my "modded" stock recovery, which accepts also self-signed .zips.
Flashing worked well, but on reboot, I got a nice bootloop because of the formerly installed Xposed framework.
Had to restore from a Nandroid Backup and after reboot, I removed Xposed completely.
Eventually, I was able to flash the OTA and got back a working device...
Gosh...
Click to expand...
Click to collapse
If you still have the original OTA zip, can you please post it for future reference?
As for TWRP mounting /dev/block/platform/7824900.sdhci/by-name/system, what error message did you get? Try running "ls -l /dev/block/platform/7824900.sdhci/by-name/" in both normal Android and TWRP, then compare the results.
pawitp said:
If you still have the original OTA zip, can you please post it for future reference?
Click to expand...
Click to collapse
No problem
pawitp said:
As for TWRP mounting /dev/block/platform/7824900.sdhci/by-name/system, what error message did you get? Try running "ls -l /dev/block/platform/7824900.sdhci/by-name/" in both normal Android and TWRP, then compare the results.
Click to expand...
Click to collapse
Stock and Cyanogen recovery are working with this partition naming scheme.
But in TWRP, I get the following error message:
Code:
ls: /dev/block/platform/7824900.sdhci/by-name: No such file or directory
For TWRP I have to use the following syntax in recovery.fstab:
Code:
/cache ext4 /dev/block/mmcblk0p29
/system ext4 /dev/block/mmcblk0p25
/data ext4 /dev/block/mmcblk0p31 length=-16384
.........etc.
vel_tins said:
No problem
Stock and Cyanogen recovery are working with this partition naming scheme.
But in TWRP, I get the following error message:
Code:
ls: /dev/block/platform/7824900.sdhci/by-name: No such file or directory
For TWRP I have to use the following syntax in recovery.fstab:
Code:
/cache ext4 /dev/block/mmcblk0p29
/system ext4 /dev/block/mmcblk0p25
/data ext4 /dev/block/mmcblk0p31 length=-16384
.........etc.
Click to expand...
Click to collapse
On TWRP, try running "find /dev/block/platform" and see if anything is created there.
The directory should have been populated by init. See https://android.googlesource.com/pl...0ab94b7d5a888f0b6920b156e5c6a075fa0741a^!/#F0.
That code should also be in TWRP, but something might have prevented it from working properly on this device. You might find some clues in dmesg or TWRP's logs.
Well, eventually I've got it.
In TWRP, the naming is a little bit different from stock or Cyanogen recovery.
I had to change:
Code:
/dev/block/platform/[COLOR="Red"]7824900.sdhci[/COLOR]/by-name/cache <--- STOCK
to
/dev/block/platform/[COLOR="Blue"]soc.0[/COLOR]/by-name/cache <--- TWRP
However, the "/dev/block/mmcblk0p" naming worked also in TWRP, so this was only a minor issue.
vel_tins said:
Well, eventually I've got it.
In TWRP, the naming is a little bit different from stock or Cyanogen recovery.
I had to change:
Code:
/dev/block/platform/[COLOR="Red"]7824900.sdhci[/COLOR]/by-name/cache <--- STOCK
to
/dev/block/platform/[COLOR="Blue"]soc.0[/COLOR]/by-name/cache <--- TWRP
However, the "/dev/block/mmcblk0p" naming worked also in TWRP, so this was only a minor issue.
Click to expand...
Click to collapse
IMO, you should fix TWRP so that it has the same naming convention. Otherwise OTA packages using the "stock" naming convention can't be flashed on TWRP.
Personally, I prefer the "by-name" mapping rather than the "/dev/block/mmcblk0p" because it is harder to make mistakes if you use a name. With numbers, if a wrong number is typed, then you might end up flashing the wrong partition and bricking the device.
EDIT: It might have something to do with the "system/core" repository you've used to build your recovery. Which Android tree did you use to build Cyanogen Recovery and which one did you use to build TWRP?
vel_tins said:
Well, OTA was a pain in the a**.
Because I had no stock "install-recovery.sh", I've edited the updater-script and removed all the matching entries.
Executed a full un-root.
Tried to flash the modified update.zip via TWRP, but failed because TWRP couldn't mount partitions with this name scheme:
Code:
"/dev/block/platform/[B]7824900.sdhci/by-name/system[/B]", "/system",
(will investigate later, any ideas?)
Because too lazy to modify the updater-script again,
I've booted into fastboot and loaded my "modded" stock recovery, which accepts also self-signed .zips.
Flashing worked well, but on reboot, I got a nice bootloop because of the formerly installed Xposed framework.
Had to restore from a Nandroid Backup and after reboot, I removed Xposed completely.
Eventually, I was able to flash the OTA and got back a working device...
Gosh...
Click to expand...
Click to collapse
Hi sir ,
Please share to us , how you do this , because I have status 7. Install-recovery.sh problem
I have stock recovery , and I'm only make a root for my device by kingroot .
Please share update.zip file and tel me how to make ota update
pawitp said:
IMO, you should fix TWRP so that it has the same naming convention. Otherwise OTA packages using the "stock" naming convention can't be flashed on TWRP.
Click to expand...
Click to collapse
Exactly this is the point...
pawitp said:
EDIT: It might have something to do with the "system/core" repository you've used to build your recovery. Which Android tree did you use to build Cyanogen Recovery and which one did you use to build TWRP?
Click to expand...
Click to collapse
I have to correct myself, Cyanogen has exactly the same problem.
I've used the latest CM 12.1 and Omnirom source trees to build TWRP, but with the same result.
TWRP/Cyanogen only detects "soc.0" instead of "7824900.sdhci" and that will break compatibility with OTA packages (Until you patch "updater-script").
So how you made this ota update after all ?
theeteempire said:
So how you made this ota update after all ?
Click to expand...
Click to collapse
OTA doesn't work with rooted devices.
Do a full un-root and try again.
vel_tins said:
OTA doesn't work with rooted devices.
Do a full un-root and try again.
Click to expand...
Click to collapse
I did it , full unroot , I couldn't update even that with full-unroot , I used kingroot for root ,
Also error status 7 , install-recovery. Sh shown on the update after full-unroot my device !!!
can you help me please !!!!!
theeteempire said:
....I used kingroot for root ,
Also error status 7 , install-recovery. Sh shown on the update after full-unroot my device...
Click to expand...
Click to collapse
I would strongly suggest, to open an new thread, because I guess a lot more people will or had run into these issues.
I don't know what Kingsoft (never used it) has modified/replaced, so in your case I would search for a stock "install-recovery.sh" and replace the modified.
Everything else would be too complicated. (You have read my post on the first page).
vel_tins said:
I would strongly suggest, to open an new thread, because I guess a lot more people will or had run into these issues.
I don't know what Kingsoft (never used it) has modified/replaced, so in your case I would search for a stock "install-recovery.sh" and replace the modified.
Everything else would be too complicated. (You have read my post on the first page).
Click to expand...
Click to collapse
So I need the stock install-recovery. Sh ,.
Are you have it ?
vel_tins said:
Exactly this is the point...
I have to correct myself, Cyanogen has exactly the same problem.
I've used the latest CM 12.1 and Omnirom source trees to build TWRP, but with the same result.
TWRP/Cyanogen only detects "soc.0" instead of "7824900.sdhci" and that will break compatibility with OTA packages (Until you patch "updater-script").
Click to expand...
Click to collapse
This is just a guess. Try adding "TARGET_PLATFORM_DEVICE_BASE := /devices/soc.0/" to BoardConfig.mk.
If you know C, you might want to try mucking around in system/core/init/devices.c and see why it's behaving that way.
pawitp said:
This is just a guess. Try adding "TARGET_PLATFORM_DEVICE_BASE := /devices/soc.0/" to BoardConfig.mk.
.....
Click to expand...
Click to collapse
Seems to work, thanks!
PS: A google search for "TARGET_PLATFORM_DEVICE_BASE" threw only six results, so it doesn't seem to be a very popular flag.
vel_tins said:
Seems to work, thanks!
PS: A google search for "TARGET_PLATFORM_DEVICE_BASE" threw only six results, so it doesn't seem to be a very popular flag.
Click to expand...
Click to collapse
From my experience, you can't rely too much on Google for ROM development. I've found the flag by reading the source file I've previously mentioned.
Sent from my Nexus 4 using XDA Free mobile app
Hi guys, I have got a very urgent problem right now, and hope someone can help me out...I am currently using a HTC One M7, and I used the TWRP recovery and the official bootloader or something rooted my phone, the reason why I need root it is that i need a app move into the system apps which may be easier in using it. And after I moved the app into the system apps using Root Explorer and then reboot my phone, the app just disappeared. After tried many times...I think it is because of the twrp just wipe it... do u guys have a method to solve this problem?...really...pls help me out!!
luvu4evermore said:
Hi guys, I have got a very urgent problem right now, and hope someone can help me out...I am currently using a HTC One M7, and I used the TWRP recovery and the official bootloader or something rooted my phone, the reason why I need root it is that i need a app move into the system apps which may be easier in using it. And after I moved the app into the system apps using Root Explorer and then reboot my phone, the app just disappeared. After tried many times...I think it is because of the twrp just wipe it... do u guys have a method to solve this problem?...really...pls help me out!!
Click to expand...
Click to collapse
This is not a twrp issue, /system partition is write-protected by the stock kernel, every changes made in the /system partition will be reverted after a reboot. If you want to be able to write to /system when booted in the rom, you'll need a custom kernel with write-protection disabled (pretty much all custom kernels here have this). The other option is to make the changes you want in your /system partition before the stock kernel boots, so using the embedded file manager of twrp recovery for example.
If you want to use a custom kernel, you must choose one that works with your rom type and version. For example, ElementalX kernel will only works for Sense or GPE rom (stock or custom). The version of ElementalX required depends on your android version so newer doesn't mean better, you need the right one. Flashing a custom recovery is done using twrp recovery. When installing the custom kernel, you can choose the features you want to be installed so if you don't want a specific feature that the kernel offers, its not a problem. The write-protection is removed by default.
If using the twrp file manger, boot in twrp select "advanced" ---> "file manager"
Then to move a file, select it (tap on it) then it will open another menu. Select "move" then select the location you want to move it to. There is also a chmod menu to edit the files permissions.
alray said:
This is not a twrp issue, /system partition is write-protected by the stock kernel, every changes made in the /system partition will be reverted after a reboot. If you want to be able to write to /system when booted in the rom, you'll need a custom kernel with write-protection disabled (pretty much all custom kernels here have this). The other option is to make the changes you want in your /system partition before the stock kernel boots, so using the embedded file manager of twrp recovery for example.
Click to expand...
Click to collapse
Oh, thanks for answering me~ uh, can u be more specific about how to do that? about the kernel thing? I never did this before and actually this is just my second time to root a phone and try to move an app into system app (as last time i did so there is no such a problem...) Also, about the twrp recovery file manager, tried that one yesterday, and it did not show the " app" folder under the system one, which means i just cannot move it using the twrp file manager...
luvu4evermore said:
Oh, thanks for answering me~ uh, can u be more specific about how to do that? about the kernel thing? I never did this before and actually this is just my second time to root a phone and try to move an app into system app (as last time i did so there is no such a problem...) Also, about the twrp recovery file manager, tried that one yesterday, and it did not show the " app" folder under the system one, which means i just cannot move it using the twrp file manager...
Click to expand...
Click to collapse
see my post above (edited while you were replying)
You can also use aroma file manager within twrp recovery
here a nice xda-video about both twrp file manger and aroma file manager
alray said:
see my post above (edited while you were replying)
You can also use aroma file manager within twrp recovery
here a nice xda-video about both twrp file manger and aroma file manager
Click to expand...
Click to collapse
OMFG!!! Finally I made it! I watched the video and find out that I did not mount the permission to the TWRP file manager! Thank you so much!!!
luvu4evermore said:
OMFG!!! Finally I made it! I watched the video and find out that I did not mount the permission to the TWRP file manager! Thank you so much!!!
Click to expand...
Click to collapse
Yep sorry, should have mentioned that, you always have to mount the partition you want to access when using a recovery. Some are mounted by default, but /system isn't.
alray said:
Yep sorry, should have mentioned that, you always have to mount the partition you want to access to when using a recovery.
Click to expand...
Click to collapse
Nah, still thanks a lot,
luvu4evermore said:
Nah, still thanks a lot,
Click to expand...
Click to collapse
you're welcome :good:
Hello,
My Device: Oneplus 3T
I have installed multirom on my mobile with Resurrection and MIUI installed ROMs. Although i insert the correct pattern, some how both the OS not accepting the pattern after reboot and my phone is locked . Please help me to unlock/reset the pattern.
Note: I have TWRP 3.0.3 (Multirom) installed in my device and the phone is rooted.
Amitshahc said:
Hello,
My Device: Oneplus 3T
I have installed multirom on my mobile with Resurrection and MIUI installed ROMs. Although i insert the correct pattern, some how both the OS not accepting the pattern after reboot and my phone is locked . Please help me to unlock/reset the pattern.
Note: I have TWRP 3.0.3 (Multirom) installed in my device and the phone is rooted.
Click to expand...
Click to collapse
Boot into TWRP and go to the file manager under advanced. From here cd to data/system/ and delete the 2 .key extension files along with the lockscreen.db files. This will remove your lockscreen from your primary rom. You can do the same with secondary. This is a known MultiROM bug and a quick search in the thread would have provided you with the answer.
cmbdom said:
Boot into TWRP and go to the file manager under advanced. From here cd to data/system/ and delete the 2 .key extension files along with the lockscreen.db files. This will remove your lockscreen from your primary rom. You can do the same with secondary. This is a known MultiROM bug and a quick search in the thread would have provided you with the answer.
Click to expand...
Click to collapse
Thanks for your reply, but i already found those solutions and tried too.
But still the Resurrection OS is locked. while the internal OS which points to MIUI is unlocked and not asking anything. should i reinstall the 2nd OS of Resurrection?
Now there are no .key files or lockscreen.db files in /data/system.
Amitshahc said:
Thanks for your reply, but i already found those solutions and tried too.
But still the Resurrection OS is locked. while the internal OS which points to MIUI is unlocked and not asking anything. should i reinstall the 2nd OS of Resurrection?
Now there are no .key files or lockscreen.db files in /data/system.
Click to expand...
Click to collapse
You now need to travel to your secondary rom's install location (ex. Internal Storage). I'd assume you installed it to the userdata partition so travel to sdcard/MultiROM/ then continue to data/system/. If it is not in this location then take a quick Google search for the partition you installed it to.
cmbdom said:
You now need to travel to your secondary rom's install location (ex. Internal Storage). I'd assume you installed it to the userdata partition so travel to sdcard/MultiROM/ then continue to data/system/. If it is not in this location then take a quick Google search for the partition you installed it to.
Click to expand...
Click to collapse
Thanks, this seems something would have worked if I didn't had deleted and reinstalled the OS. sorry I can't wait so reinstalled it. I will try to follow this next time if I face the same issue. thanks...
cmbdom said:
You now need to travel to your secondary rom's install location (ex. Internal Storage). I'd assume you installed it to the userdata partition so travel to sdcard/MultiROM/ then continue to data/system/. If it is not in this location then take a quick Google search for the partition you installed it to.
Click to expand...
Click to collapse
[Solved] :good:
Thanks, this one really worked for me.. the path was sdcard/multirom/roms and then data/system.
Amitshahc said:
[Solved] :good:
Thanks, this one really worked for me.. the path was sdcard/multirom/roms and then data/system.
Click to expand...
Click to collapse
This happens whenever you set a lockscreen pattern while using MultiROM on any of the installed ROMs.
First, I should point out that I'm just a user, not a developer or hacker. I'm posting this because I don't know where else to ask for help.
This will most likely look like the post of an idiot. But, oh, well, I did manage to mess up my phone, which means I am an idiot. So here it goes: I had 16.0 installed and I tried to install 14.0 from TWRP recovery mode. Basically, Magisk hide wasn't working very well so I wanted to see if it worked with an older version. Now my phone is stuck in a boot loop. It just shows "Samsung Galaxy S8 powered by Android" then restarts. I can boot into TWRP and connect the phone to the PC to access the storage this way, but I can't boot into the OS. Is there any way I can fix this, preferably without losing my data?
I tried flashing the official uninstaller, but I get the message "Update process ended with ERROR: 1"
Here's what the log says about the uninstaller:
Mounting /system, /vendor
-Device platform: arm64
cp: can't stat '/dev/tmp/install/arm64/.': No such file or directory
! Cannot find /data/adb/magisk
Updater process ended with ERROR: 1
I:Install took 1 second(s).
Error installing zip file '/sdcard/Download/Magisk-uninstaller-20180429.zip'
Updating partition details...
I: Data backup size is 32943MB, free: 2620MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
...done
I:Set page: 'flash_done'
I: operation_end - status=1
I looked at the contents of the zip on my computer, and it doesn't have an arm64 folder. So the uninstaller doesn't work on arm64 phones?
Update: I managed to uninstall Magisk using a compatible uninstaller, but the phone still doesn't boot into the OS.
Update 2: if I have to flash the stock ROM, I'm planning to do the next thing: back up my data partition to an external hard drive with TWRP. After I flash the ROM and wipe everything, I want to reinstall TWRP and restore that backup. Would this cause any issues?
Yes, there's an issue on 64-bit devices with the latest available uninstaller. Use the next to last, here: https://github.com/topjohnwu/Magisk/releases/download/v16.3/Magisk-uninstaller-20180328.zip
Thanks. I've just left home and I'll be away for two days. I didn't take the S8 with me, so I won't be able to try any more fixes until Sunday. But I'll check then and update my post if there are any more issues.
Didgeridoohan said:
Yes, there's an issue on 64-bit devices with the latest available uninstaller. Use the next to last, here:
Click to expand...
Click to collapse
I managed to uninstall Magisk with that zip, but the phone still doesn't boot into Android.
vladone97 said:
I managed to uninstall Magisk with that zip, but the phone still doesn't boot into Android.
Click to expand...
Click to collapse
In that case, restoring the stock boot image manually might work. If not, a complete restoration of your device's stock setup might be necessary.
Your device's forum is likely the best place to get further help.
Didgeridoohan said:
In that case, restoring the stock boot image manually might work. If not, a complete restoration of your device's stock setup might be necessary.
Your device's forum is likely the best place to get further help.
Click to expand...
Click to collapse
I tried flashing the stock boot image and it still doesn't work. Stock restoration it is then.
Didgeridoohan said:
In that case, restoring the stock boot image manually might work. If not, a complete restoration of your device's stock setup might be necessary.
Your device's forum is likely the best place to get further help.
Click to expand...
Click to collapse
One more question, though: I backed up my data partition to an external hard drive with TWRP. After I flash the stock ROM and wipe my data, I want to reinstall TWRP and restore that backup. Would this work or would it cause problems?
vladone97 said:
One more question, though: I backed up my data partition to an external hard drive with TWRP. After I flash the stock ROM and wipe my data, I want to reinstall TWRP and restore that backup. Would this work or would it cause problems?
Click to expand...
Click to collapse
If you get your device up and running after the wipe and reinstall, you could always try restoring the backup. If it works, it works, and if it doesn't you can just wipe /data again.
Didgeridoohan said:
If you get your device up and running after the wipe and reinstall, you could always try restoring the backup. If it works, it works, and if it doesn't you can just wipe /data again.
Click to expand...
Click to collapse
Is there any other partition I should back up? That is, aside from the internal storage, which I've already taken care of.
vladone97 said:
Is there any other partition I should back up? That is, aside from the internal storage, which I've already taken care of.
Click to expand...
Click to collapse
Not if you're flashing back to stock anyways. Sounds like something is borked anyways so restoring anything might cause problems (including data). I would just start over. It's just data. Apps can be re installed. Contacts re sync.
I would start fresh, make sure it boots, make a full backup, then try restoring only data. Remember that /data may contain some of your old magisk stuff that may have added to the problem. So do that at your own risk. What data could be worth all that hassle?
Try to think of it like, if that phone got smashed, and you got a free replacement tomorrow. You'd survive right? Even without that data?
And definitely don't try to flash a magisk version that old over one that new one again.
vladone97 said:
Is there any other partition I should back up? That is, aside from the internal storage, which I've already taken care of.
Click to expand...
Click to collapse
Good advice by @madbat99.
Personally I only ever keep TWRP backups of the devices I test stuff on. But then I do a full backup of the device to have an easy way to get back to the setup I want.
On my everyday device I only keep a backup of the internal storage and messages (Signal). It's so easy to restore apps and other stuff anyway, so I don't really bother...
Didgeridoohan said:
Good advice by @madbat99.
Personally I only ever keep TWRP backups of the devices I test stuff on. But then I do a full backup of the device to have an easy way to get back to the setup I want.
On my everyday device I only keep a backup of the internal storage and messages (Signal). It's so easy to restore apps and other stuff anyway, so I don't really bother...
Click to expand...
Click to collapse
I did all that, but Magisk 19.1 still doesn't work. Some older versions work though. I tried Magisk 18.0, 18.0, 19.0 and 19.1. Only 18.0 and 18.1 worked. So I'm assuming there's a problem with the newer versions of Magisk?