Related
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:
I have a rooted SM-t817t and have been attempting to flash Lineage 14.1 to it through TWRP 3.1.0-1_ashyx.
I have tried to flash with the gts210ltexx and the gts210wifi and the results are the same, receive the Error 7 message.
After reading up on other threads I attempted to alter the script to either tell it that the ROM is for the gts210ltexx or just remove it entirely and still getting the error.
Also attempted to run it without authentication.
I have read that the t817x tablets can be flashed with the t810 ROMs but have had zero success with doing so at this time.
I am unsure how to proceed from this point.
TheBigby said:
I have a rooted SM-t817t and have been attempting to flash Lineage 14.1 to it through TWRP 3.1.0-1_ashyx.
I have tried to flash with the gts210ltexx and the gts210wifi and the results are the same, receive the Error 7 message.
After reading up on other threads I attempted to alter the script to either tell it that the ROM is for the gts210ltexx or just remove it entirely and still getting the error.
Also attempted to run it without authentication.
I have read that the t817x tablets can be flashed with the t810 ROMs but have had zero success with doing so at this time.
I am unsure how to proceed from this point.
Click to expand...
Click to collapse
Format (not wipe) DATA and if that doesn't work FORMAT the system partition.
If neither works then maybe you should use an updated twrp.
ashyx said:
Format (not wipe) DATA and if that doesn't work FORMAT the system partition.
If neither works then maybe you should use an updated twrp.
Click to expand...
Click to collapse
Thank you for the advice, I will update to the latest TWRP and then format the data and try that. Will report back with results.
After formatting the data and updating to the latest TWRP, 3.2.3-1, I come across the same error 7.
Have updated the script filed to make certain no trace of verification exists for the ROM and still receive the error.
Have now attempted at least five different ROMS all with the same results.
The following is a summarized look at the details it gives.
Installing zip file 'lineage.zip'
Checking for Digest file...
Skipping Digest check: no Digest file found
Warning: No file_contexts
detected filesystem ext4 for /dev/block/platform/15540000.dwmmc0/by-name/SYSTEM
Patching system image unconditionally...
E1001: Failed to update system image.
Updater process ended with ERROR: 7
Error installing zip file '/lineage.zip'
Updating partition details...
Failed to mount '/hidden' (Invalid argument)
...done
Update: I have now wiped data but have not yet formatted it. I believe I will need to install Magisk for that.
However based on other recommendations I have come to find out about the encryption on the Samsung storage and that it might be causing the issue.
I have tried to circumvent this by formatting the data into ext2 then back to ext4 and restarting recovery, but so far this has not worked. The error 7 message persists regardless.
Will come back with further updates.
TheBigby said:
Update: I have now wiped data but have not yet formatted it. I believe I will need to install Magisk for that.
However based on other recommendations I have come to find out about the encryption on the Samsung storage and that it might be causing the issue.
I have tried to circumvent this by formatting the data into ext2 then back to ext4 and restarting recovery, but so far this has not worked. The error 7 message persists regardless.
Will come back with further updates.
Click to expand...
Click to collapse
You didnt read my previous post correctly.
You don't need Magisk to FORMAT DATA.
The FORMAT DATA button is right there under the wipe options.
However what you did would have formatted DATA anyway.
Now do the same for the system partition after formatting DATA.
Do not reboot just check DATA and SYSTEM can be mounted then try and install the zip again.
ashyx said:
You didnt read my previous post correctly.
You don't need Magisk to FORMAT DATA.
The FORMAT DATA button is right there under the wipe options.
However what you did would have formatted DATA anyway.
Now do the same for the system partition after formatting DATA.
Do not reboot just check DATA and SYSTEM can be mounted then try and install the zip again.
Click to expand...
Click to collapse
Formatted the data and the system. Verified they were both mounted. Then attempted to flash the ROM.
Error 7 message still appearing. As does the unable to mount hidden.
TheBigby said:
Formatted the data and the system. Verified they were both mounted. Then attempted to flash the ROM.
Error 7 message still appearing. As does the unable to mount hidden.
Click to expand...
Click to collapse
What device is the ROM intended for?
ashyx said:
What device is the ROM intended for?
Click to expand...
Click to collapse
Have tried multiple ROMs, all intended for either the t810 or the t815. They include Lineage, Resurrection Remix, Paranoid Android, AOSP, and a couple more besides.
TheBigby said:
Have tried multiple ROMs, all intended for either the t810 or the t815. They include Lineage, Resurrection Remix, Paranoid Android, AOSP, and a couple more besides.
Click to expand...
Click to collapse
It may be that the system partition sizes are different?
Unknown. I have tried reflashing the stock firmware and that still failed in Odin.
I have given up at this point and restored from a backup. Thanks for the help however.
Same issue with Lineage 15.1
TheBigby said:
I have a rooted SM-t817t and have been attempting to flash Lineage 14.1 to it through TWRP 3.1.0-1_ashyx.
I have tried to flash with the gts210ltexx and the gts210wifi and the results are the same, receive the Error 7 message.
After reading up on other threads I attempted to alter the script to either tell it that the ROM is for the gts210ltexx or just remove it entirely and still getting the error.
Also attempted to run it without authentication.
I have read that the t817x tablets can be flashed with the t810 ROMs but have had zero success with doing so at this time.
I am unsure how to proceed from this point.
Click to expand...
Click to collapse
Can you share root procedure for the sm-t817t my roommate has one for sale, I'll only buy it if I can root it though.
If you had problems (like myself) with installing custom roms via twrp where the system would stuck in a bootloop and the recovery would return "No OS Installed" error, here's the solution to how to fix it:
1. Enter TWRP
2. Go to Wipe - Format Data
3. Restart recovery
4. Copy the rom to internal storage and install custom rom
Enjoy!
vulgaran said:
If you had problems (like myself) with installing custom roms via twrp where the system would stuck in a bootloop and the recovery would return "No OS Installed" error, here's the solution to how to fix it:
1. Enter TWRP
2. Go to Wipe - Format Data
3. Restart recovery
4. Copy the rom to sd card and install custom rom
Enjoy!
Click to expand...
Click to collapse
Thanks for the useful info. :highfive:
evanB70 said:
Thanks for the useful info. :highfive:
Click to expand...
Click to collapse
Whoops, forgot it doesn't have the sd card slot I've edited the first post.
Apparently, when you change rom type (for example, from official stable to xiaomi.eu weekly), you have to do this complete device wipe. For updating to a new version only wiping dalvik and cache should do.
not work on me
Thanks but didn't work for me either. After following your instructions, the phone booted into TWRP again. It no longer says there's no OS, but it won't boot. Just stalls into boot animation for a while and then goes into twrp recovery... Bummer!
After trying to update to a newer version of a custom rom, crDroid 6.4, I can no longer boot into the system. The phone only boots into recovery. TWRP no longer asks for a password in order to decrypt the phone, as it has done before. I have tried wiping Data, Cache, and Dalvik, and flashed the rom again, with no luck. Is it a way for me to force decrytion or something?
Any help is much appreciated! I am new to this, and still learning.
Ukulelen said:
After trying to update to a newer version of a custom rom, crDroid 6.4, I can no longer boot into the system. The phone only boots into recovery. TWRP no longer asks for a password in order to decrypt the phone, as it has done before. I have tried wiping Data, Cache, and Dalvik, and flashed the rom again, with no luck. Is it a way for me to force decrytion or something?
Any help is much appreciated! I am new to this, and still learning.
Click to expand...
Click to collapse
I assume that the data partition is actually still encrypted and you see random folder names in TWRP. If so, try formatting data in TWRP (not wipe, but format) then reboot to the ROM.
Robbo.5000 said:
I assume that the data partition is actually still encrypted and you see random folder names in TWRP. If so, try formatting data in TWRP (not wipe, but format) then reboot to the ROM.
Click to expand...
Click to collapse
Will this delete all my files?
Also, I'm not sure if I am flashing the ROM correctly. I have the ROM, magisk and other files on my computer. I use "ADB Sideload" under advanced in TWRP and "adb sideload romname.zip" on my computer.
Ukulelen said:
Will this delete all my files?
Also, I'm not sure if I am flashing the ROM correctly. I have the ROM, magisk and other files on my computer. I use "ADB Sideload" under advanced in TWRP and "adb sideload romname.zip" on my computer.
Click to expand...
Click to collapse
Yes it will delete all your files. If you boot to TWRP and it doesn't ask for the PIN, etc., but you see all your folders have random encrypted names, then everything is lost anyway. There is nothing you can do to recover that data.
In future just copy the ROMs onto the phone and flash them directly off the phone in TWRP, using the install menu.
Robbo.5000 said:
Yes it will delete all your files. If you boot to TWRP and it doesn't ask for the PIN, etc., but you see all your folders have random encrypted names, then everything is lost anyway. There is nothing you can do to recover that data.
In future just copy the ROMs onto the phone and flash them directly off the phone in TWRP, using the install menu.
Click to expand...
Click to collapse
Thanks for your help. Luckily I had backed up all my photos. I am up and running with a new rom. I am testing omni rom as it now comes with microg prebuild.