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
Koodo Mobile: http://downloadmirror.co/android/tq/G900W8VLU1COI4_G900W8OYA1COI4_KDO.zip
SaskTel: http://downloadmirror.co/android/tr/G900W8VLU1COI4_G900W8OYA1COI4_BWA.zip
Virgin Mobile: http://downloadmirror.co/android/ts/G900W8VLU1COI4_G900W8OYA1COI4_VMC.zip
Bell Mobil: http://downloadmirror.co/android/tt/G900W8VLU1COI4_G900W8OYA1COI4_BMC.zip
Rogers: http://downloadmirror.co/android/tu/G900W8VLU1COI4_G900W8OYA1COI4_RWC.zip
Telus: http://downloadmirror.co/android/tv/G900W8VLU1COI4_G900W8OYA1COI4_TLS.zip
Fido Mobile: http://downloadmirror.co/android/tw/G900W8VLU1COI4_G900W8OYA1COI4_FMC.zip
Source: http://www.theandroidsoul.com/downl...1-update-g900w8vlu1coi4-with-root-info-85381/
Nice, which I've would I download for Wind Mobile?
If Flash fire shows protected on some partitions does that mean I have to use Odin on PC?
Spacemonkie4207 said:
Nice, which I've would I download for Wind Mobile?
Click to expand...
Click to collapse
The Wind Mobile firmware is always released under its parent company's name, Globalive, which is not listed here. It's CSC is GLO if you can find it elsewhere. But it really doesn't matter at all. The last few releases that were labelled Globalive were literally just the Bell version renamed. You can use any of the firmware versions above if you want. I used the Telus one a couple of times, just because I have a grudge against Bell and Rogers. But it makes absolutely no difference.
hexavoodoomal said:
The Wind Mobile firmware is always released under its parent company's name, Globalive, which is not listed here. It's CSC is GLO if you can find it elsewhere. But it really doesn't matter at all. The last few releases that were labelled Globalive were literally just the Bell version renamed. You can use any of the firmware versions above if you want. I used the Telus one a couple of times, just because I have a grudge against Bell and Rogers. But it makes absolutely no difference.
Click to expand...
Click to collapse
Where can I find the proper apn settings?
Zehlek said:
If Flash fire shows protected on some partitions does that mean I have to use Odin on PC?
Click to expand...
Click to collapse
use odin in pc
Spacemonkie4207 said:
Where can I find the proper apn settings?
Click to expand...
Click to collapse
Google it.
Whats new ?
Whhats new on 5.1.1 theme store coming out with this ? What can i find
Plz some one upload captures
brayhanrd said:
Whhats new on 5.1.1 theme store coming out with this ? What can i find
Plz some one upload captures
Click to expand...
Click to collapse
I have 900M so i cant install, maybe anyone can post anything, but 99% sure didnt have themes
Enviado de meu SM-G900F usando Tapatalk
brayhanrd said:
Whhats new on 5.1.1 theme store coming out with this ? What can i find
Plz some one upload captures
Click to expand...
Click to collapse
I think it is more under the hood updates
Sent from my SM-G900W8 using Tapatalk
Anyone figure out how to root this version. I tried to install TWRP and flashed Super SU, cleared cache and dalvik but it just boot loops on first boot after flashing firmware. Tried to install after it booted and set up user name and accounts by the same process but I had the same results.
Any suggestions?
Thanks.
daroco said:
Anyone figure out how to root this version. I tried to install TWRP and flashed Super SU, cleared cache and dalvik but it just boot loops on first boot after flashing firmware. Tried to install after it booted and set up user name and accounts by the same process but I had the same results.
Any suggestions?
Thanks.
Click to expand...
Click to collapse
Only with custom kernel
Enviado de meu SM-G900F usando Tapatalk
Thanks bro! I thought about it but I didn't think it mattered. I'll give it a go.
No dice as of yet, custom kernels are not booting either, good thing I had the sense to do a bacup first
☺
daroco said:
Thanks bro! I thought about it but I didn't think it mattered. I'll give it a go.
No dice as of yet, custom kernels are not booting either, good thing I had the sense to do a bacup first
Click to expand...
Click to collapse
The way I usually root is to flash CF-Auto-Root-kltecan-kltevl-smg900w8.tar using odin. Can you try that?
I haven't updated yet until I'm sure root is there as I gave the phone to my wife.
thanks
Still bootloops when I flashed CF-Autoroot. it also installed the original recovery from another BL version. I reflashed TWRP and cleared cache and dalvik (not that I expected it to do much) but still the same. restored a nandroid and I had all kinds of apps FC. End result was to factory reset the phone to be in a stable condition. If this was a car I could get this damn thing running right! I should have learned more about programming while I was in school...... 2 kids and a mortgage I have no time for it now.
[HOWTO] Root your 5.1.1 G900W8VLU1COI4 firmware
daroco said:
Anyone figure out how to root this version. I tried to install TWRP and flashed Super SU, cleared cache and dalvik but it just boot loops on first boot after flashing firmware. Tried to install after it booted and set up user name and accounts by the same process but I had the same results. [...]
Click to expand...
Click to collapse
mauriicio21 said:
Only with custom kernel
Click to expand...
Click to collapse
Not exactly
You need stock kernel but with sepolicy patched in ramdisk, according to @Chainfire's method.
I think I could help all G900W8's users
Rooting procedure (requires TWRP or CWM):
1. Download patched kernel and the latest SuperSU (2.52+):
>> KERNEL_G900W8VLU1COI4_Stock_patched.zip <<
>> SuperSU BETA by @Chainfire <<
2. Copy both zip files to phone or extSdCard
3. Go to TWRP / CWM and flash both files one by one. Order does not matter
4. Reboot the phone.
5. Enjoy your rooted 5.1.1 firmware
-------------------------------------------------------------------------------------------
It is time to say that I also need your help as there is no 5.1.1 firmware for other S5's variants yet. I need updated SELinux contexts and and permissions list from your 5.1.1 firmware (in all Snapdragon S5 variants contexts/permissions are the same). I require it as I would like to be well prepared with my custom ROMs for G900F/FD. I believe that Android 5.1.1 for G900F/FD is just a matter of a few days...
Please do as follow while running G900W8VLU1COI4 firmware:
- Install Terminal Emulator from Play Store (https://play.google.com/store/apps/details?id=jackpal.androidterm)
- Type commands as follow:
Code:
[COLOR="Red"]su[/COLOR]
cd /system
ls -aRZ > /storage/emulated/0/test1.txt
ls -aRn > /storage/emulated/0/test2.txt
- you will find above txt files in the internal sdcard's root directory - please zip these files and post here as attachment
NOTE1: Rooted phone is not a MUST. If you have not rooted 5.1.1 firmware - just bypass "su" command and ignore "Permission denied" messages. In fact it will also do the work as it should.
NOTE2: Don't worry. Your /system partition will remain untouched by these actions. No private data will be read as all private contents are stored on /data
_alexndr said:
Not exactly
You need stock kernel but with sepolicy patched in ramdisk, according to @Chainfire's method.
I think I could help all G900W8's users
Rooting procedure (requires TWRP or CWM):
1. Download patched kernel and the latest SuperSU (2.52+):
>> KERNEL_G900W8VLU1COI4_Stock_patched.zip <<
>> SuperSU BETA by @Chainfire <<
2. Copy both zip files to phone or extSdCard
3. Go to TWRP / CWM and flash both files one by one. Order does not matter
4. Reboot the phone.
5. Enjoy your rooted 5.1.1 firmware
------------------------------------------------------
It is time to say that I also need your help as there is no 5.1.1 firmware for other S5's variants yet. I need updated SELinux contexts and and permissions/symlinks list from your 5.1.1 firmware. I require it to be well prepared with my custom firmware for G900F. I believe that Android 5.1.1 for G900F is just a matter of a few days.
Please do as follow while running G900W8VLU1COI4 firmware:
- Install Terminal Emulator from Play Store (https://play.google.com/store/apps/details?id=jackpal.androidterm)
- Type commands as follow:
Code:
[COLOR="Red"]su[/COLOR]
cd /system
ls -aRZ > /storage/emulated/0/test1.txt
ls -aRn > /storage/emulated/0/test2.txt
- you will find above txt files in the internal sdcard's root directory - please zip these files and post here as attachment
NOTE1: Rotted phone is not a MUST. If you have not rooted 5.1.1 firmware - just bypass "su" command and ignore "Permission denied" messages. In fact it will also do the work as it should.
NOTE2: Don't worry. Your /system partition will remain untouched by these actions. No private data will be read as all private contents are stored on /data
Click to expand...
Click to collapse
Do you Know how can i get spanish on this Vertion plz. ? @_alexndr
_alexndr said:
Not exactly
You need stock kernel but with sepolicy patched in ramdisk, according to @Chainfire's method.
I think I could help all G900W8's users
Rooting procedure (requires TWRP or CWM):
1. Download patched kernel and the latest SuperSU (2.52+):
>> KERNEL_G900W8VLU1COI4_Stock_patched.zip <<
>> SuperSU BETA by @Chainfire <<
2. Copy both zip files to phone or extSdCard
3. Go to TWRP / CWM and flash both files one by one. Order does not matter
4. Reboot the phone.
5. Enjoy your rooted 5.1.1 firmware
------------------------------------------------------
It is time to say that I also need your help as there is no 5.1.1 firmware for other S5's variants yet. I need updated SELinux contexts and and permissions list from your 5.1.1 firmware (in all Snapdragon S5 variants contexts/permissions are the same). I require it as I would like to be well prepared with my custom ROMs for G900F/FD. I believe that Android 5.1.1 for G900F/FD is just a matter of a few days...
Please do as follow while running G900W8VLU1COI4 firmware:
- Install Terminal Emulator from Play Store (https://play.google.com/store/apps/details?id=jackpal.androidterm)
- Type commands as follow:
Code:
[COLOR="Red"]su[/COLOR]
cd /system
ls -aRZ > /storage/emulated/0/test1.txt
ls -aRn > /storage/emulated/0/test2.txt
- you will find above txt files in the internal sdcard's root directory - please zip these files and post here as attachment
NOTE1: Rotted phone is not a MUST. If you have not rooted 5.1.1 firmware - just bypass "su" command and ignore "Permission denied" messages. In fact it will also do the work as it should.
NOTE2: Don't worry. Your /system partition will remain untouched by these actions. No private data will be read as all private contents are stored on /data
Click to expand...
Click to collapse
Hope this helps, thanks for your help.
Here you go!
Just confirmed the camera can shoot in RAW format
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom "ROM" like OmniROM
Click to expand...
Click to collapse
WARNING!!! Be careful what you do here. One mistake and the device is soft-bricked. I take no responsibility for bricked devices, lost warranty or even OTAs not working!! Booting and/or flashing files from this post is on your own risk.
Requirements
Unlocked bootloader
Yoga Tablet 3 Plus with and without LTE (YT-X703L and YT-X703F) are supported
Known Issues
WARNING! Our device uses dm-verity (verified boot). The system partition should remain read-only. Otherwise a bootloop will occur. You can flash my modified kernel or SuperSU to resolve this but OTA's are no longer possible! You have to restore a factory image or clean system backup to receive OTAs
Potentially DRM keys are lost! Pure unlocking and rooting does not cause the issue. However, there have been reports of lost DRM keys by some unknown action. It is advised to act with caution. Losing your DRM keys can lead to issues with some apps which use DRM which could then have limited or no functionality. E.g. Netflix will only stream in SD (480p). You can check with DRM info if you still have L1 security level which means DRM keys are intact.
Download
Official TWRP for YT-X703F (Wifi): twrp.me
Official TWRP for YT-X703L (LTE): twrp.me
Instructions
Install fastboot and adb on your PC, e.g. from here
Enable developer options and in there select to unlock your bootloader by enabling OEM unlock and enable USB debugging
Connect your PC to your tablet and run
Code:
adb reboot bootloader
using adb on command line. The tablet will reboot into bootloader mode where you will only see the Lenovo logo. Now you use
Code:
fastboot oem unlock-go
to unlock. This will factory reset your device
Setup the tablet again and reboot again to the bootloader
Then run
Code:
fastboot boot twrp-3.2.1-0-yt_x703f.img
to temporarily boot into TWRP. You can also flash if you are sure
Select to keep system read only when TWRP starts to avoid modification which will make OTAs impossible
Optionally flash SuperSU or Magisk in TWRP which should install system less. Keep OEM unlock enabled if you flash or modify anything
Additional Downloads
Backup of original boot, recovery and system image for YT-X703F S000936: MEGA
Modified Boot image with forceencrypt disabled and it switches off CABC fully. You need to factory reset after flashing to format data without encryption boot_yt_x703f_s000963_noforceencrypt_cabc.img (YT-X703F S000963) / boot_yt_x703l_s000963_noforceencrypt_cabc.img (YT-X703L S000963) . Use
Code:
fastboot flash boot boot_yt_x703f_s000963_noforceencrypt_cabc.img
to flash the kernel in fastboot. SuperSU or Magisk should be flashed afterwards if root is desired.
Full factory images with flash tool and instructions YT_X703F_S000689, YT_X703L_S000704, YT_X703F_S000725, YT_X703L_S000725, YT_X703F_S000734, YT_X703L_S000734, YT_X703L_S000744, YT-X703F_S000744, YT-X703L_S000963, YT-X703F_S000963 and OTA updates: MEGA (These images contain the individual boot, recovery and system images that you need to restore from any modification mentioned above)
System Updates (OTA)
In order to successfully apply Lenovo system updates after root you have to restore the original boot, recovery (if you flashed TWRP) and system partitions from your current installed version (e.g. S000744) for your variant of the tablet. This will NOT delete your apps and data but will unroot. Note that OTAs are block based and always check the contents of most of the partitions. This means that all of these partitions (except your data) have to be original and have to be on the exact same version (e.g. S000734) for the update to succeed.
See here for instructions how to restore the partitions with fastboot.
Credits
@pogo1975 - for providing the factory images and fixing the AV sync issue
@launcher20 and @deecept - for testing the LTE version
TeamWin
Changelog
v4:
Now official TWRP with version 3.0.3-0
v3:
enable full disk encryption for access to the encrypted data partition
update TWRP kernel to latest S000725 version
v2:
add support for LTE variant (YT-X703L)
add further mount points to be able to backup more data
Thanks buddy! You are an absolute champion! Tell me what you need me to do and I'll do it before rooting and up load what you need.
Doing good work here.
Who wants to bet on a race between matshias and Lenovo support for who can fix the issues with this device first?
That's great and fast, I'm thinking tab 3 plus is getting hot now.
Great to see there is something moving for the yoga now. You think it will support the lte Version anytime? Or maybee even lineageos?
so you know, i've managed to install xposed thanks to this thread https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268 and is working well.
wayney said:
Thanks buddy! You are an absolute champion! Tell me what you need me to do and I'll do it before rooting and up load what you need.
Click to expand...
Click to collapse
Well if you haven't modified anything yet then it'd be great if you can boot into TWRP with system read only and then connect via ADB to the tablet with a big SD card inserted which has enough free space (4 GB).
The run the following command
Code:
dd if=/dev/block/bootdevice/by-name/system of=/sdcard1/system.img
This will take a while. Then copy the file system.img from your SD card to a PC and zip it (or 7z, rar). Then upload it
Gogoho said:
Great to see there is something moving for the yoga now. You think it will support the lte Version anytime? Or maybee even lineageos?
Click to expand...
Click to collapse
The LTE variant is probably very similar and it wouldn't be much work. But I don't own the device, so I would need some help. So someone with the LTE variant who is not afraid to experiment with fastboot and adb and who can provide me with the details needed I am happy to compile a TWRP for it.
LineageOS is much much more work than TWRP. For an experienced cyanogenmod/LineageOS dev it is not much of a thing and would take only a few days, especially since it is a Qualcomm device and there are already ports for devices with SD 652. But for me this is new as well so it'll take much longer. As soon as I have time I'll look into it.
matshias said:
Well if you haven't modified anything yet then it'd be great if you can boot into TWRP with system read only and then connect via ADB to the tablet with a big SD card inserted which has enough free space (4 GB).
The run the following command
Code:
dd if=/dev/block/bootdevice/by-name/system of=/sdcard1/system.img
This will take a while. Then copy the file system.img from your SD card to a PC and zip it (or 7z, rar). Then upload it
Click to expand...
Click to collapse
You forgot to tell me to go to adb shell :silly:
DD is currently doing a dump, non interactive so I hope it is still alive, it has been close to 1 hour so far. I will upload the clean image once it is done and await further instructions from you. :good:
I'm in Perth, Western Australia (UTC +8:00), so we might be playing timezone tag.
wayney said:
You forgot to tell me to go to adb shell :silly:
DD is currently doing a dump, non interactive so I hope it is still alive, it has been close to 1 hour so far. I will upload the clean image once it is done and await further instructions from you. :good:
I'm in Perth, Western Australia (UTC +8:00), so we might be playing timezone tag.
Click to expand...
Click to collapse
I think I forgot one more thing. The external SD card needs to be mounted in the TWRP menu. I believe it's not mounted automatically. So the DD command does nothing. It shouldn't take that long. Sorry about that!
It's UTC +1:00 here in Germany
matshias said:
Well if you haven't modified anything yet then it'd be great if you can boot into TWRP with system read only and then connect via ADB to the tablet with a big SD card inserted which has enough free space (4 GB).
The run the following command
Code:
dd if=/dev/block/bootdevice/by-name/system of=/sdcard1/system.img
This will take a while. Then copy the file system.img from your SD card to a PC and zip it (or 7z, rar). Then upload it
Click to expand...
Click to collapse
matshias said:
I think I forgot one more thing. The external SD card needs to be mounted in the TWRP menu. I believe it's not mounted automatically. So the DD command does nothing. It shouldn't take that long. Sorry about that!
It's UTC +1:00 here in Germany
Click to expand...
Click to collapse
I was wondering why nothing was happening after 3 hours.
I have rared it and it is uploading at the moment, it is going to take 5 hours.
wayney said:
I was wondering why nothing was happening after 3 hours.
I have rared it and it is uploading at the moment, it is going to take 5 hours.
Click to expand...
Click to collapse
Wow ok. Well thanks a lot for your efforts. This will not just help me but anyone with modified system partition to get OTAs.
Unmodified System Image
Here is the vanilla image via DD of the system partition.
Software Version : YT-X703F_160817
Android Version : 6.0.1
Security Patch Level : 1 September 2016
Kernel Version : 3.10.84-perf
Build Number : YT-X703F_S000689_161105_ROW
Tablet purchased retail from Australia.
https://mega.nz/#!bos0GIjI!vcO9dpSJX...Grjb7k3z6mjnqA
wayney said:
Here is the vanilla image via DD of the system partition.
Software Version : YT-X703F_160817
Android Version : 6.0.1
Security Patch Level : 1 September 2016
Kernel Version : 3.10.84-perf
Build Number : YT-X703F_S000689_161105_ROW
Tablet purchased retail from Australia.
https://mega.nz/#!bos0GIjI
Click to expand...
Click to collapse
Perfect!!
Can you send me the key for the download via PM or post it?
matshias said:
Perfect!!
Can you send me the key for the download via PM or post it?
Click to expand...
Click to collapse
Let's try that again.
https://mega.nz/#!bos0GIjI!vcO9dpSJXp6cKtdH07Kt0RSaqpqQ7Grjb7k3z6mjnqA
matshias said:
Wow ok. Well thanks a lot for your efforts. This will not just help me but anyone with modified system partition to get OTAs.
Click to expand...
Click to collapse
Thank you guys for spending times on it, it would be wonderful if Lenovo people do thing like this way, too.
In the depths of the Russian Internet i have found this
YT-X703F_USR_S000689_1611051146_Q00237_ROW.zip
https://drive.google.com/drive/folders/0B_jGuhC9WsNfYUZzZmhRY2NhQlU?usp=sharing
it is supose to be complete image to Wifi-Version.
I HAVE NOT FLASHED THIS YET. Do it on your risk.
pogo1975 said:
In the depths of the Russian Internet i have found this
YT-X703F_USR_S000689_1611051146_Q00237_ROW.zip
https://drive.google.com/drive/folders/0B_jGuhC9WsNfYUZzZmhRY2NhQlU?usp=sharing
it is supose to be complete image to Wifi-Version.
I HAVE NOT FLASHED THIS YET. Do it on your risk.
Click to expand...
Click to collapse
Hahaha got to love the dark corner of the Russian internets :laugh:
pogo1975 said:
In the depths of the Russian Internet i have found this
YT-X703F_USR_S000689_1611051146_Q00237_ROW.zip
https://drive.google.com/drive/folders/0B_jGuhC9WsNfYUZzZmhRY2NhQlU?usp=sharing
it is supose to be complete image to Wifi-Version.
I HAVE NOT FLASHED THIS YET. Do it on your risk.
Click to expand...
Click to collapse
If that's real it would have saved me a lot of time finding the loophole in the system to extract the boot and recovery image. But still a great find which will rescue some soft-bricked devices.
matshias said:
If that's real it would have saved me a lot of time finding the loophole in the system to extract the boot and recovery image. But still a great find which will rescue some soft-bricked devices.
Click to expand...
Click to collapse
so long as it's safe and not loaded with malware...
Disclaimer: Usual disclaimer applies. I've tested this recovery but it might not work due to a different ROM / device / moon phase / etc. Use at your own risk.
Introduction
After working with upstream TWRP developers and fixing some bugs (in TWRP itself and in this port) this device finally has an official port
There were various builds available at different times (some with bugs) but most of them should now be fixed.
Features
Works
backup/restore
installing zips
ADB
MTP
Screen turns off
Basically the rest of this list
format /data
Adoptable storage
Decrypt /data
Doesn't work (please ask if you need this)
Encrypted backup (set password for /data/data)
USB-OTG
Untested
Backup/restore of stock system / data.
Installation instructions
Warning: only use it on the G800F/M/Y, NOT on the G800H! I only tested the G800F, but think G800M/Y will also work. G800H will most likely NOT work, as it is based on a different SoC (Qualcomm).
Download the recovery image from twrp.me. It also includes some installation instructions.
There are more extensive installation instructions over at the LineageOS ROM installation instructions.
I personally prefer using Heimdall, but you can also use Odin. Commands in Download/Odin mode (power off, then press home+Volume-Down+power):
Code:
heimdall flash --RECOVERY recovery.img
If you're using the stock ROM, use:
Code:
heimdall flash --RECOVERY recovery.img --no-reboot
When you come from the stock ROM you have to make sure the stock ROM doesn't overwrite TWRP: Pull the battery, wait 5 seconds, insert it again, and press home + volume up + power to enter TWRP and replace the stock ROM from there.
If you already have TWRP or LineageOS, it's much easier to install from there, see twrp.me.
Another method is using ADB (from your computer). I used it a lot during testing:
Code:
adb root
adb push twrp-3.1.1-1-kminilte.img /dev/block/mmcblk0p10
Changelog
Code:
2017-07-10:
* fix formatting /data while the partition is encrypted
(device is not encrypted by default)
* add support for adoptable storage
* accept kminiltexx etc. for flashing basebands
2017-06-20:
* ADB
* MTP at the same time as ADB
* Screen turns fully off
* fix for restoring backups made using `adb backup --twrp`
Source code
Kernel: https://github.com/TeamWin/android_kernel_samsung_kminilte/tree/cm-14.1
Device: https://github.com/TeamWin/android_device_samsung_kminilte/tree/cm-14.1
This recovery is built using a LineageOS tree. Instructions are similar to the instructions for building LineageOS for the S5 mini. Differences are: you don't need to patch the source (skip that step) and the last step is mka recoveryimage instead of mka bacon - this only builds the recovery resulting in much faster builds. Also see the official build instructions.
Thanks
Other people who have worked on this project:
Team Win, of course, for the recovery itself! In particular bigbiff which has worked with me to make this device official.
hennymcc
RVR
---
Note to moderators: this is my first DevDB thread started on XDA so I may have made mistakes.
XDA:DevDB Information
Team Win Recovery Project, ROM for the Samsung Galaxy S5 Mini
Contributors
ayke, hennymcc, RVR
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Version Information
Status: Stable
Current Stable Version: 3.1.1
Stable Release Date: 2017-06-20
Created 2017-06-24
Last Updated 2017-07-09
Thanks!
OFFICIAL TWRP...I can't believe it
Great work on this one...many thanks.
Thanks a million @ayke ! However, I found some bugs I'd like to submit some bugs I discovered:
- Recovery is not SEANDROID enforcing" message when booting TWRP, didn't cause any trouble for me but still - it was fine in your previous unofficial build
- Some zip files (tested with latest modem flashable zip) report "This package is for kminiltexx devices; this is a kminilte", so it doesn't flash and fails with ERROR:7
I can confirm that decrypting a File-Based encrypted /data partition works, I didn't test the backup tool though.
P.S. Is it possible to add support for adopted storage, that would be awesome!
Nevertheless - thanks for making this device officialy supported!
Friedensfurz said:
Thanks a million @ayke ! However, I found some bugs I'd like to submit some bugs I discovered:
- Recovery is not SEANDROID enforcing" message when booting TWRP, didn't cause any trouble for me but still - it was fine in your previous unofficial build
Click to expand...
Click to collapse
The current kernel used upstream is somewhat older and hasn't enabled SELinux yet. I don't see why you would want enforcing SELinux in TWRP, though.
Friedensfurz said:
- Some zip files (tested with latest modem flashable zip) report "This package is for kminiltexx devices; this is a kminilte", so it doesn't flash and fails with ERROR:7
Click to expand...
Click to collapse
I think I have a fix for that, please test https://aykevl.nl/download/2017-06-25-recovery-fix-ota-asserts.img (not tested by me)
Friedensfurz said:
I can confirm that decrypting a File-Based encrypted /data partition works, I didn't test the backup tool though.
Click to expand...
Click to collapse
Nice!
Friedensfurz said:
P.S. Is it possible to add support for adopted storage, that would be awesome!
Click to expand...
Click to collapse
I might look into it. I don't use it at the moment but am considering it.
EDIT: I have fixed it, it will be included in the next build.
any chance for g800h support?
sasukesama said:
any chance for g800h support?
Click to expand...
Click to collapse
Not from me. The G800H is a completely different device. I have a G800F so I can't test it.
ayke said:
I think I have a fix for that, please test https://aykevl.nl/download/2017-06-25-recovery-fix-ota-asserts.img (not tested by me)
Click to expand...
Click to collapse
Sorry, but the build doesn't fix the wrong device id issue - still throws error " This is for kminiltexx your device is kminilte. Anyway - maybe the next build will fix it[emoji6]
Friedensfurz said:
Sorry, but the build doesn't fix the wrong device id issue - still throws error " This is for kminiltexx your device is kminilte. Anyway - maybe the next build will fix it[emoji6]
Click to expand...
Click to collapse
Can you give a link to where you downloaded this zip? Then I can test it myself.
I also get the device error with latest official and 2017-06-25-recovery-fix-ota-asserts.img.
Tried to flash one of Spookcity's kernels, you can find it here (search for "test9" that is what I used lately).
https://github.com/Spookcity/ROMS-G800F/issues/10#issuecomment-301915315
The latest pre-official TWRP 3.1.1-0 works (says kminiltexx).
ayke said:
Can you give a link to where you downloaded this zip? Then I can test it myself.
Click to expand...
Click to collapse
This file causes problems with the device id: http://pt.tapatalk.com/redirect.php...1_22.05.2017_DRE-flashable.zip&au_id=13587482
It is a TWRP flashable baseband file, hope this helps
@Friedensfurz @Pat750
I couldn't find a (still online) kernel from Spookcity and I'd rather not flash a new modem unless I know why I should do that. So I haven't verified it.
But here's another build you can try. My previous attempt was incomplete.
https://aykevl.nl/download/2017-06-27-recovery-fix-ota-asserts-2.img
On my device I've verified it has a ro.product.device property of kminiltexx.
ayke said:
@Friedensfurz @Pat750
I couldn't find a (still online) kernel from Spookcity and I'd rather not flash a new modem unless I know why I should do that. So I haven't verified it.
But here's another build you can try. My previous attempt was incomplete.
https://aykevl.nl/download/2017-06-27-recovery-fix-ota-asserts-2.img
On my device I've verified it has a ro.product.device property of kminiltexx.
Click to expand...
Click to collapse
Yeah,I removed all of my test build links from my google drive, but have a thread on here. I already sent you this though. I will test your new build and see if it helps.
Edit:
Yep,fixed. Good work Ayke!
Sent from my SM-G800F using Tapatalk
Friedensfurz said:
...
I can confirm that decrypting a File-Based encrypted /data partition works, I didn't test the backup tool though.
...
Click to expand...
Click to collapse
I'm having a few issues with TWRP 3.1.1 where "wipe / format data" (where you have to key "yes") generates the following error msg (I posted a similar msg in Slim Rom 7 thread):
Code:
Error:unable to wipe /data unknown file system 'auto'
unable to format encryption.
I'm now wondering whether decrypting the data partition from within TWRP will address my format data issue reported above.
Can I ask how you did this? I've dug around the TWRP menus but nothing has jumped out at me (maybe it's something you need to run from the terminal?)
Many thanks!
fidoedidoe said:
I'm having a few issues with TWRP 3.1.1 where "wipe / format data" (where you have to key "yes") generates the following error msg (I posted a similar msg in Slim Rom 7 thread):
Code:
Error:unable to wipe /data unknown file system 'auto'
unable to format encryption.
I'm now wondering whether decrypting the data partition from within TWRP will address my format data issue reported above.
Can I ask how you did this? I've dug around the TWRP menus but nothing has jumped out at me (maybe it's something you need to run from the terminal?)
Many thanks!
Click to expand...
Click to collapse
I have the same problem
Here also this message in unofficial builds, don't tried it, but I think its still present in this version.
fidoedidoe said:
I'm having a few issues with TWRP 3.1.1 where "wipe / format data" (where you have to key "yes") generates the following error msg (I posted a similar msg in Slim Rom 7 thread):
I'm now wondering whether decrypting the data partition from within TWRP will address my format data issue reported above.
Can I ask how you did this? I've dug around the TWRP menus but nothing has jumped out at me (maybe it's something you need to run from the terminal?)
Many thanks!
Click to expand...
Click to collapse
I still haven't found a method to decrypt the /data volume from within TWRP (a reference earlier in the thread implied it was possible)..the hope being this would mitigate the "wipe / format data" error:
Code:
Error:unable to wipe /data unknown file system 'auto'
unable to format encryption.
What I did discover was that when reverting to an older version of TWRP (2.8.x) using Odin, " format data" (where you have to type "yes" to proceed) didn't error. I'm not sure whether that cured the issue, but after that I updated TWRP image back to 3.1.1.0 and installed my ROM as normal.
Still looking for a recognised method to wipe encrypted /data volume from within latest stable TWRP if anyone has any experience of that.
EDIT
Another thread suggests (to my untrained eye) that "unknown file system 'auto" may be related to how twrp.fstab is configured.
I'm very much out of my here ( so apologies for the crude suggestion), but could it be that another build of a TWRP image is needed where twrp.fstab is changed to allow "format data" to work, ie substitute "fstype" from "auto" to "ext4" as outlined below :
Code:
...
/data ext4 /dev/block/mmcblk0p21 length=-16384
...
fidoedidoe said:
I still haven't found a method to decrypt the /data volume from within TWRP (a reference earlier in the thread implied it was possible)..the hope being this would mitigate the "wipe / format data" error:
Code:
Error:unable to wipe /data unknown file system 'auto'
unable to format encryption.
What I did discover was that when reverting to an older version of TWRP (2.8.x) using Odin, " format data" (where you have to type "yes" to proceed) didn't error. I'm not sure whether that cured the issue, but after that I updated TWRP image back to 3.1.1.0 and installed my ROM as normal.
Still looking for a recognised method to wipe encrypted /data volume from within latest stable TWRP if anyone has any experience of that.
EDIT
Another thread suggests (to my untrained eye) that "unknown file system 'auto" may be related to how twrp.fstab is configured.
I'm very much out of my here ( so apologies for the crude suggestion), but could it be that another build of a TWRP image is needed where twrp.fstab is changed to allow "format data" to work, ie substitute "fstype" from "auto" to "ext4" as outlined below :
Code:
...
/dataext4/dev/block/mmcblk0p21length=-16384
...
Click to expand...
Click to collapse
I got it to work by formatting/repairing/changing filesystem in TWRP. Just try some combinations, it will work eventually
Yes, I think it's because of the 'auto' in the fstab. I've set it to ext4 in this build (for data and cache):
https://aykevl.nl/download/2017-07-03-recovery.img
This build also contains the previous fixes (adoptable storage, fixing the kminiltexx error).
If it fixes the issue for you, I'll push the change for inclusion in the next official build.
I didn't see any negative consequences of changing the FS type in fstab. Even setting the fstab entry to 'f2fs' mounts /data as usual (as ext4) so I think it's safe.
ayke said:
https://aykevl.nl/download/2017-07-03-recovery.img
Click to expand...
Click to collapse
Can someone test this change? Then I'll integrate it in the official build.
Hi, I have a redmi note 9 that I wanted to mod but I had a lot of problems modding it. I initially installed crDroid 8.7 but the control center animation was lagging and the battery drains fast, so I decided to change the ROM with Project Elixir (Android 12 all ROMs). I saw that crDroid 8.9 came out (September 22, 2022) and there had been some notable changes, as the battery did not run out anymore the animations were fluid, but i was not able to get working google apps.
I tried everything and it wasn't right. (Nik, OpenGapps, MTG nothing) indeed I installed the gapps I had on 8.7 and them didn't work .. So I decided to move to pixel experience android 12 but I had these problems:
On all the roms that I have installed (except I think MIUI) the system is encrypted. I tried flashing a zip, via commands, via recovery but nothing the system is encrypted. I can't access it and in addition I wanted to change the bootanimation but I can't move the zip because it says it's read only and following these commands too I couldn't do it:
adb root
adb disable-verity
adb reboot
adb remount
adb shell
mount -o rw,remount /system
for these commands i also used ADB Sideload (ofc) but also some zips
It says the /dev /<number>/block is read-only and I have not been able to unlock it. (I tried with all these recoveries: TWRP, SHRP (SkyHawk, OrangeFox [UNOFFICIAL but is only for A11]). (If I go from TWRP to sdcard / I have all the files encrypted. I have the phone rooted with magisk.
In addition, I also had problems formatting the phone because the system with both TWRP and SHRP was not deleted or if I restarted the phone after formatting the ROM would open again so to format it I used Pixel Experience which has worked very well so far.
But custom rom already have ability to rw
Anyway you're lucky there thread available google it like
Universal method to get rw
Idk. I have installed Project Elixir, crDroid and this Pixel Experience and are encrypted.
I already googled it....
/dev/* will be always read-only.
And how i can modify the boot animation? Files are encrypted and the zip is in /system/product/media/.zip
/dev/ and /system/ are not same.
Stock MIUI is system read-only.
If you want to mount system as read-write, you need "universal mount system r/w" by @lebigmac
[Closed] Universal SystemRW / SuperRW feat. MakeRW / ro2rw (read-only-2-read/write super partition converter)
Welcome to the one and only, the original, universal, System-RW / Super-RW feat. Make-RW / ro2rw (read-only-2-read/write super partition converter) by lebigmac Also known as: THE-REAL-RW, FULL-RW, EXT4-RW, EROFS-RW, EROFS-2-RW, F2FS-RW...
forum.xda-developers.com
Oh ok, it will work on A12?
I'm not sure.
Ok so tried flashing systemrw_flashable (Universal RW) with sideload bcs i have crypted files.
This is the error that it gave me:
Extracting ...
There was an error extracting the file. Please install unzip and try again.
I tried flashing with SHRP (TWRP based) bcs twrp can't work with adb sideload (for me).
Edit: searched on xda the problem, i installed the BusyBox module in magisk (From Fox Modules Manager) but nothing to do, still same error.
Deltwin said:
Oh ok, it will work on A12?
Click to expand...
Click to collapse
it should start up if you comment out the checkSDK() function in the script itself.
Not sure if you can sideload it probably not. Just execute it like any other script (runnable in both Android and recovery) or flash it like any other flashable zip in recovery.
Keep in mind I'm working on a new version that should fix some issues. Just need to make sure it works perfect on multiple devices b4 I release it...
If you can't get my script to work and you're too impatient to wait for the new version to be released then you could try some of the copycat imitations. There's a couple of those floating around here... Good luck!
lebigmac said:
it should start up if you comment out the checkSDK() function in the script itself.
Not sure if you can sideload it probably not. Just execute it like any other script (runnable in both Android and recovery) or flash it like any other flashable zip in recovery.
Keep in mind I'm working on a new version that should fix some issues. Just need to make sure it works perfect on multiple devices b4 I release it...
If you can't get my script to work and you're too impatient to wait for the new version to be released then you could try some of the copycat imitations. There's a couple of those floating around here... Good luck!
Click to expand...
Click to collapse
But how can be you make sure without some beta testers you neef guys like me and this op who have device in hand to test it and give you feedback
lebigmac said:
it should start up if you comment out the checkSDK() function in the script itself.
Not sure if you can sideload it probably not. Just execute it like any other script (runnable in both Android and recovery) or flash it like any other flashable zip in recovery.
Keep in mind I'm working on a new version that should fix some issues. Just need to make sure it works perfect on multiple devices b4 I release it...
If you can't get my script to work and you're too impatient to wait for the new version to be released then you could try some of the copycat imitations. There's a couple of those floating around here... Good luck!
Click to expand...
Click to collapse
Oh so it cant work in sideload... Good tip if it will work u made a very good script
To be honest I've never used this sideload feature before... What are the advantages of sideloading versus flashing the .zip as usual?
Mr Hassan said:
But how can be you make sure without some beta testers you neef guys like me and this op who have device in hand to test it and give you feedback
Click to expand...
Click to collapse
That's a good idea. I should release an open beta before releasing the final program.
That way we can make sure it works on as many devices as possible
lebigmac said:
To be honest I've never used this sideload feature before... What are the advantages of sideloading versus flashing the .zip as usual?
That's a good idea. I should release an open beta before releasing the final program.
That way we can make sure it works on as many devices as possible
Click to expand...
Click to collapse
Thanks for appreciating the idea
Hope we'll get beta soon but is there any idea date how many days still need to release it
Ok let me show my progress
I make my vendor sys odm to ext4
And ser the logs according to logs
I have rw now
OnePlus8:/ # mount | grep "dm-0"
/dev/block/dm-0 on / type ext4 (rw,seclabel,relatime)
OnePlus8:/ # mount | grep "dm-19"
/dev/block/dm-19 on / type ext4 (rw,seclabel,relatime)
OnePlus8:/ # mount | grep "dm-3"
But the weird thing is still not able to edit
Any file in these parts.
lebigmac said:
it should start up if you comment out the checkSDK() function in the script itself.
Not sure if you can sideload it probably not. Just execute it like any other script (runnable in both Android and recovery) or flash it like any other flashable zip in recovery.
Keep in mind I'm working on a new version that should fix some issues. Just need to make sure it works perfect on multiple devices b4 I release it...
If you can't get my script to work and you're too impatient to wait for the new version to be released then you could try some of the copycat imitations. There's a couple of those floating around here... Good luck!
Click to expand...
Click to collapse
How i can run ur script directly from android?
Like on magisk?
Deltwin said:
How i can run ur script directly from android?
Like on magisk?
Click to expand...
Click to collapse
Hi. Please check the Manual Installation and Examples section of the thread in my signature
And if you're running Android 12+ don't forget to disable the sdkCheck() function in the systemrw.sh script file @ line # 425 like this #sdkCheck
It should work if your only problem is the shared_blocks read-only feature. If your device got the new erofs read-only protection feature then you must wait for next version of my script or try your luck one of the copycat imitations that are floating around.
Good luck!
So after an hard brick at work (so i leaved it for 5 hours with redmi logo on lol) and after many steps i reinstalled MIUI with root... it's running A11 so how i can install it? I need to disable the sdkCheck? I think no if you need it on A12...
Second question i need to flash it before the first boot or i can do it after the first boot?
Deltwin said:
So after an hard brick at work (so i leaved it for 5 hours with redmi logo on lol) and after many steps i reinstalled MIUI with root... it's running A11 so how i can install it? I need to disable the sdkCheck? I think no if you need it on A12...
Second question i need to flash it before the first boot or i can do it after the first boot?
Click to expand...
Click to collapse
I thought hard bricks were unrecoverable?
If your Xiaomi device is running Android 10 or 11 then you don't need to disable the sdkCheck() function in my old script.
Ok here are all the necessary steps in chronological order for you
unlock bootloader
flash stock ROM
install systemrw_1.32
root
debloat
customize
enjoy
No it's possible, i tought not but here i am with my redmi note 9..
jk apart i unbrick with SP Flash tool but i had other problems like NVRAM warning (it fixed automatically with updates idk lol..) and the IMEI was deleted but fortunately i had a flashable backup..
I need to flash the stock rom? I have pixel experience with A12/13
Edit: I tried to flash it (i have the file on the microSD) but it gave me this error:
There was an error extracting the file. Please install unzip and try again.
Well my script was designed for stock A10, A11 ROMs ( or A12 if you're lucky and your device only uses the infamous shared_blocks read-only feature + you must disable sdkCheck() function in script itself ) but I don't see why it shouldn't work on a custom ROM as well
Ok let me try this again but only because it's you
Boot phone into Android OS and make sure it's properly rooted
download the systemrw_1.32_BUNDLE_proper.zip and extract it
extract the systemrw_1.32_flashable.zip
copy the systemrw_1.32 folder into /data/local/tmp/ on your phone
open adb shell or terminal app and type
Bash:
adb shell
su
cd /data/local/tmp/systemrw_1.32
chmod +x ./systemrw.sh
./systemrw.sh in=`realpath /dev/block/by-name/super` size=50
Good luck!