Related
CWM has been updated officialy to 3.2.0.1! See the Changelog and FAQ below for more information!
Changelog:
3.0.0.5 - Initial official release for the nook. Only supported ext3. Had bootloop errors with the 1.1.0 update. (Note: Unofficial builds supported ext4 but not both at the same time)
3.0.0.6 - No significant changes to 3.0.0.5 officially. (Note: Unofficial builds supported ext3 or ext4 but not both at the same time)
3.0.0.8 - Broken build. Blame the samsung phones for messed up additions.
3.0.0.9 - Adds official support for ext4 as well as compatability for ext3. (i.e. No need to swap recovery for different ROMs). Fixes "Always boots into recovery" with 1.1.0 updated u-boot.bin
3.0.1.0 - Adds support to for /sd-ext to recovery.
3.0.2.8 - Sets /system to ext2. You can now backup and restore your stock roms! Delete/Update all 3.0.0.5 threads to point to 3.0.2.8 for all rom types. Rom Manager now pushes a recovery kernel as well as the ramdisk!! No need to manually install recovery kernel. Just flash the lastest from RomManager and you are done!
3.2.0.0 - Support for newer nooks with the 5G /data parition! New .32 kernel is included which fixes the freezing after formatting /data! (/data format issues. Don't Use)
3.2.0.1 - Fixes a bug with 3.2.0.0 (actually a build issue) where ext3 (/data and /cache) wouldn't be formatted properly (they were but CWM was bombing out)
*Recommended *
RomManager can now push the recovery kernel. No need to manually install via CWM or ADB! Flash from RomManager and rock and roll.
Q: Why should I upgrade?
As of the official version 3.0.0.9 there CWM supports both ext3 and ext4 ROMs with a single recovery image. This means no more of this swapping back and forth between different versions of CWM! 3.0.2.8 sets /system to ext2 to allow for proper backing up and restoring of stock roms!
This version also fixes issues with the 1.1.0 version of u-boot.bin. Some with this version may experience that your NookColor will always boot back into RomManager. This is now fixed (as of 3.0.0.9)
Click to expand...
Click to collapse
Q: But I have CWM <insert older version> I am good right?
Always use the latest found on this post or on RomManager. Older version are not supported
Click to expand...
Click to collapse
Q: I used RomManager to install CWM but now i can't use backup or restore
This should be fixed. Report any issues to me either on this thread or via PM
Click to expand...
Click to collapse
Q: I upgraded CWM and now my market doesn't work.
Installing CWM doesn't alter any rom or data files which shouldn't have any affect on recovery. There is something else that may have affected your market.
No worries though you can try the following to try and fix it:
If you are using CM7. Upgrade to the latest nightly (which will be after tonight: 3/3)
Try clearing the following: For "My Apps," go to manage apps, market, uninstall updates, clear market cache. Then delete data for Google Framework Services.
Click to expand...
Click to collapse
Q: I have upgraded but now I am having issues?
So some of you are still having issues with this new CWM version. PLEASE PLEASE PLEASE give me the following information:
What you are trying to do/accomplish. Be as detailed as possible
What rom you are running and what rom you are upgrading to (if applicable)
IMPORTANT! Grab a recovery.log from your nookcolor. You can do this either through adb or through the advanced menu. If I don't have this then there is little I can help with.
Click to expand...
Click to collapse
Q: How do i grab the recovery.log?
Method 1: ADB
After setting up adb type:
Code:
adb pull /tmp/recovery.log
You are done. (This is why everyone should learn and setup ADB. It really is stupid simple)
Method 2: Save from the menu
From the ClockworkMod Recovery main screen do the following
Select 'Advanced'
Select 'Report Error'
There is now a copy of recovery.log on your sdcard. Transfer the sdcard to a computer or boot into your rom and mount your sdcard on your computer.
Click to expand...
Click to collapse
Thank you Nemith
i flashed this earlier today, at first it kept bootlooping so i used the remove CW zip and got rid of it. The 2nd install went fine (both times i rebooted before booting into CW)
however CW says it cannot mount system so i'm unable to make a full backup
davidukfl said:
i flashed this earlier today, at first it kept bootlooping so i used the remove CW zip and got rid of it. The 2nd install went fine (both times i rebooted before booting into CW)
however CW says it cannot mount system so i'm unable to make a full backup
Click to expand...
Click to collapse
What rom are you running?
Nice! Thanks!
Sent from my DROIDX using Tapatalk
nemith said:
TL;DR: If you use RomManager go upgrade it in RomManager NOW!
Click to expand...
Click to collapse
My RomManager still sees 3.0.0.5 as the latest version.
Chahk said:
My RomManager still sees 3.0.0.5 as the latest version.
Click to expand...
Click to collapse
I provided a link/instructions to manual flash cwm. This may help.
Stock 2.1 rom
Sent from my DROIDX using Tapatalk
davidukfl said:
Stock 2.1 rom
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
Grab /tmp/recovery.log from your device after you try to do a nandroid backup.
Thanks!
Excellent! I 'll have a new installclockwork.zip and universal bootable sd out here as soon as I get back from skiing
Thanks!
Thanks for the info. I have been waiting for this.
So I'm stuck in the CM boot loop. Can I install from the boot-looping CM or do I flash it from the SD loaded CM?
No problem either way, just curious what the best approach is?
Moar gees with gginggerbread and tapatalk!
John Kotches said:
So I'm stuck in the CM boot loop. Can I install from the boot-looping CM or do I flash it from the SD loaded CM?
Click to expand...
Click to collapse
Either should work since both are ran from RAM.
Can the img file be written to an SDcard? Also, can Nandroids made with 3.0.0.5 be restored using the update?
Homer
nemith said:
Grab /tmp/recovery.log from your device after you try to do a nandroid backup.
Thanks!
Click to expand...
Click to collapse
the tmp folder is empty. In the clockwork folder on the SD card the boot.img file is in there though.
When i create a backup it says cannot mount system, and when i got to advanced and hit mount system it says the same thing
Homer_S_xda said:
Can the img file be written to an SDcard? Also, can Nandroids made with 3.0.0.5 be restored using the update?
Homer
Click to expand...
Click to collapse
Yes. There is nothing special about the images written to an sdcard. You can even rename the files to uImage and uRamdisk to have it boot without the two-finger salute on the sdcard.
davidukfl said:
the tmp folder is empty. In the clockwork folder on the SD card the boot.img file is in there though.
When i create a backup it says cannot mount system, and when i got to advanced and hit mount system it says the same thing
Click to expand...
Click to collapse
There should always be a /tmp/recovery.log. You need to grab this while in recovery via adb
Code:
adb pull /tmp/recovery.log
nemith said:
Either should work since both are ran from RAM.
Click to expand...
Click to collapse
I'll probably shove remove cw onto the bootable sd card and then push cw again from rom manager.
Moar gees with gginggerbread and tapatalk!
I can't mount /system either. Using CM7. I also have a dual-boot partition, but I doubt that matters.
from log:
mounting /system!
W:failed to mount /dev/block/mmcblk0p5 (No such device)
Error mounting /system!
Also:
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
W:failed to mount /dev/block/mmcblk0p7 (No such device)
edit: Here's the full pastebin
Updated rom manager with cm7 nightly 7. Worked flawlessly.
Hey everyone,
A few days ago, I decided to downgrade from AICP 11 back to 10 (Android 6.0.1 to 5.1.1), wiped everything but internal storage. When flashing, I got an error, saying that the /vendor partition was missing, and indeed, while it existed, I could only mount it forcefully, because the device was busy.
This lead to a complete wipe, as after a reboot, TWRP asked for an encryption password, which I didn't set. Here, I did a factory reset & wiped everything. After that, I tried flashing again (5.1.1), but after it was completed, I got a line, which said "Couldn't unmount /system", which is true, as it's already unmounted. But when I mount it, all the files that are supposed to be installed seem to be there.
When I reboot the device, it gets stuck on the Google logo.
Frankly, I'm afraid to even flash back to stock, so I was hoping that someone more experienced could help me out.
It should be noted, that I still have access to fastboot, and TWRP.
Thanks in advance,
DecentM
How did you force mount /vendor?
Can you clarify where you are seeing these problems? (TWRP or within Android)
Do you have any nandroid backups to test and see if they work?
dmantilal said:
How did you force mount /vendor?
Can you clarify where you are seeing these problems? (TWRP or within Android)
Do you have any nandroid backups to test and see if they work?
Click to expand...
Click to collapse
I used mount -f and umount -f in the TWRP terminal
I see all these problems in TWRP, since I can't boot/get past the initial Google logo.
I do have a nandroid backuip on my laptop (as I had to wipe the tablet clean), but that's currently unavailable for me to use, I'll reply back when I tried it.
I doubt it will work, because it just extracts data to a predefined path, which seems like the same thing an installer zip does.
DecentM said:
I used mount -f and umount -f in the TWRP terminal
I see all these problems in TWRP, since I can't boot/get past the initial Google logo.
I do have a nandroid backuip on my laptop (as I had to wipe the tablet clean), but that's currently unavailable for me to use, I'll reply back when I tried it.
I doubt it will work, because it just extracts data to a predefined path, which seems like the same thing an installer zip does.
Click to expand...
Click to collapse
Why did you need /vendor mounted in TWRP?
I thought flashing used dd (command) or similar to copy the *.img file to the partition (or, more accurately, the block device). If /vendor is mounted during *.img copy, that would most likely cause errors.
dmantilal said:
Why did you need /vendor mounted in TWRP?
I thought flashing used dd (command) or similar to copy the *.img file to the partition (or, more accurately, the block device). If /vendor is mounted during *.img copy, that would most likely cause errors.
Click to expand...
Click to collapse
I mounted it, because when I initially restored the 5.1.1 rom, I got an error, saying that the /vendor partition wasn't mounted.
DecentM said:
I mounted it, because when I initially restored the 5.1.1 rom, I got an error, saying that the /vendor partition wasn't mounted.
Click to expand...
Click to collapse
You are sure it was complaining about "unmounted", rather than "mounted"?
Do these roms include a vendor.img? You may need to flash the stock 5.1.1 vendor.img.
Either way, unless you mkfs'ed or resize2fs'ed the partitions, they should be fine. Full wipe & go.
dmantilal said:
You are sure it was complaining about "unmounted", rather than "mounted"?
Do these roms include a vendor.img? You may need to flash the stock 5.1.1 vendor.img.
Either way, unless you mkfs'ed or resize2fs'ed the partitions, they should be fine. Full wipe & go.
Click to expand...
Click to collapse
I'm not sure.
I already did a full wipe, but it still had issues. I'll try again tomorrow, and report back on how it went.
DecentM said:
I'm not sure.
I already did a full wipe, but it still had issues. I'll try again tomorrow, and report back how it went.
Click to expand...
Click to collapse
Having a mismatched vendor.img could be your problem.
No ROM I know of includes a vendor.img. I think it is a legal issue, like including GApps with a ROM.
dmantilal said:
Having a mismatched vendor.img could be your problem.
No ROM I know of includes a vendor.img. I think it is a legal issue, like including GApps with a ROM.
Click to expand...
Click to collapse
I don't think that the issue is with the vendor image anymore, but with the partitions in general. I always had a mismatched vendor image, as it only results in a modal box after boot.
My problem is again, with the /system partition not being visible to flashable zip files.
Mismatched vendor.img can also cause bootloops and other quirks like battery-charge percentage inaccuracies.
Hi all. I keep getting this error after rooting, installing SuperSu and TWRP. When I try to flash a ROM (any ROM), I get stuck. I've tried the latest Resurrection and CM ROMS. Will someone please help me past this last hurdle? Thank you!
I can't upload or link the screenshot but here's the info:
Can't install this package on top of incompatible data. Please try another package or run a factory reset.
Which I have done several times.
Backup ==> select all ==> Swipe to Backup
Wipe ==> Advenced Wipe ==> /System + /Data + /Cache Confirm "Swipe to Wipe" . Try installing again ROM
maxprzemo said:
Backup ==> select all ==> Swipe to Backup
Wipe ==> Advenced Wipe ==> /System + /Data + /Cache Confirm "Swipe to Wipe" . Try installing again ROM
Click to expand...
Click to collapse
That did the trick! I put Resurrection OS on there and all is well except for finding a stable GAPPS build.
Not working for me, my device is KII-L21 on stock rom and I'm trying to install official CM13, my device is rooted and have twrp
If your device is wiped It isnt rooted.. Wipe it dont forget Cache partitions try again.
maxprzemo said:
Backup ==> select all ==> Swipe to Backup
Wipe ==> Advenced Wipe ==> /System + /Data + /Cache Confirm "Swipe to Wipe" . Try installing again ROM
Click to expand...
Click to collapse
Bro, me sirvió. Muchas gracias
It really works, thanks dude
I think it all boils down to doing a format /system.
Next time I will try that!
Edit: I was wrong, the format /data is needed.
If I don't to the reset I am one of those that always gets error 7.
unmount ->system, data, cache :good:
As I already posted at https://forum.xda-developers.com/showpost.php?p=70851854&postcount=534,
I am able to avoid the Error 7 (inconsistend data) by switching to gapps mini before installing the update.
Since the experiental build, I do the following within one TWRP session: install latest gapps mini, install the upgrade to latest lineage-nightly and reinstall latest gapps stock.
So far it works for me.
Do a clean install wiping system, data, cache and dalvik cache before flashing a new ROM is adviced, it will avoid most of problems. For the GApps, I recommend OpenGapps Pico version to install the minimal needed, then you can install the other Google apps you need from the Play Store.
Guys I need some help here. I'm running into the same TWRP error 7 situation. The phone is unlocked, and I've installed kiwi_twrp_3-21_recovery. The model of the device is Honor X5 (KIW-CL00)
I've tried flashing both ResurrectionRemix-M-v5.7.4-20161220-kiwi & lineage-14.1-20170419-nightly-kiwi-signed ROM, whether it's flashing from the phone's storage or from the SD card, both ROM are giving me the same error code.
I tried formatting the system, advance wipe function (Dalvik & Cache & Data & System), now I don't even have the default factory ROM on my phone, but I'm still getting the error 7 code.
Please help. Thanks in advance.
U need to edit updater script to remove assert for device check
Error7 and then "could not find meta inf..."
Huawei KIWI Honor 5x
KIW-L21 EMUI 3.1
I installed
TWRP3.0.2-0 lineage-14.1-20170607-nightly-kiwi-signed.zip ->Error 7
then
cm-13.0-20160904-NIGHTLY-kiwi.zip and cyanogen recovery the same -> Error 7
Error 7 and if I try to delete assert, the next message is "could not find meta inf/com/google/android/update-binary"
My last problem
If I unzip and zip without change anything the Install message is "could not find..." I try it whit Linux 16.4 Win10 Win7 and 7Zip. all the same.
I can not change the updater-script without unpacking the File
Can anybody Help
robert_web said:
Huawei KIWI Honor 5x
KIW-L21 EMUI 3.1
I installed
TWRP3.0.2-0 lineage-14.1-20170607-nightly-kiwi-signed.zip ->Error 7
then
cm-13.0-20160904-NIGHTLY-kiwi.zip and cyanogen recovery the same -> Error 7
Error 7 and if I try to delete assert, the next message is "could not find meta inf/com/google/android/update-binary"
My last problem
If I unzip and zip without change anything the Install message is "could not find..." I try it whit Linux 16.4 Win10 Win7 and 7Zip. all the same.
I can not change the updater-script without unpacking the File
Can anybody Help
Click to expand...
Click to collapse
Did you try this?
Backup ==> select all ==> Swipe to Backup
Wipe ==> Advenced Wipe ==> /System + /Data + /Cache Confirm "Swipe to Wipe" . Try installing again ROM
robert_web said:
Huawei KIWI Honor 5x
KIW-L21 EMUI 3.1
I installed
TWRP3.0.2-0 lineage-14.1-20170607-nightly-kiwi-signed.zip ->Error 7
then
cm-13.0-20160904-NIGHTLY-kiwi.zip and cyanogen recovery the same -> Error 7
Error 7 and if I try to delete assert, the next message is "could not find meta inf/com/google/android/update-binary"
My last problem
If I unzip and zip without change anything the Install message is "could not find..." I try it whit Linux 16.4 Win10 Win7 and 7Zip. all the same.
I can not change the updater-script without unpacking the File
Can anybody Help
Click to expand...
Click to collapse
Pleasw upgrade to TWRP 3.1.1
Sent from my Honor 8 using XDA Labs
robert_web said:
Huawei KIWI Honor 5x
KIW-L21 EMUI 3.1
I installed
TWRP3.0.2-0 lineage-14.1-20170607-nightly-kiwi-signed.zip ->Error 7
then
cm-13.0-20160904-NIGHTLY-kiwi.zip and cyanogen recovery the same -> Error 7
Error 7 and if I try to delete assert, the next message is "could not find meta inf/com/google/android/update-binary"
My last problem
If I unzip and zip without change anything the Install message is "could not find..." I try it whit Linux 16.4 Win10 Win7 and 7Zip. all the same.
I can not change the updater-script without unpacking the File
Can anybody Help
Click to expand...
Click to collapse
U need to edit and repack everything . And do remember that if u mess a single letter it will give an error
Thanks
Sure I wipe advanced by every attempt.
Twrp 3.1.1 the same problem.
But you have right, the Solution for me is not to unzip and zip the file for delete the "assert". Only the way to edit without unpack the File in the Ubuntu "ARCHIVMANAGER" works.
Now it is installed but now I am in a bootloop But this is an other Problem. One step after another.
robert_web said:
Thanks
Sure I wipe advanced by every attempt.
Twrp 3.1.1 the same problem.
But you have right, the Solution for me is not to unzip and zip the file for delete the "assert". Only the way to edit without unpack the File in the Ubuntu "ARCHIVMANAGER" works.
Now it is installed but now I am in a bootloop But this is an other Problem. One step after another.
Click to expand...
Click to collapse
try again by making a clean flash
robert_web said:
Thanks
Sure I wipe advanced by every attempt.
Twrp 3.1.1 the same problem.
But you have right, the Solution for me is not to unzip and zip the file for delete the "assert". Only the way to edit without unpack the File in the Ubuntu "ARCHIVMANAGER" works.
Now it is installed but now I am in a bootloop But this is an other Problem. One step after another.
Click to expand...
Click to collapse
So , plz upload the updater-script here . I will edit and forward u . Later repack everything as is, lets see if that works . If not , i will build a rom for u especially
Thanks its work fine now. It was my fault, I updated from Lollipop not from Nougat. So I used Huawei Firmbootextraktor extract system.img cust.img recovery.img and boot.img and on my SD I copy ../dload/update.app version B140 Android 5.1.1. Then the Handy started I updated EMUI 4.0 and Android 6.1. Now works my Handy with all zip files where I delete the asserts.
Maybe was the problem, in the assert is wrote "kiwi" and my Handy is a "KIW-L21"
I try update via recovery ( put this file to external strorage only )
1. boot to recovery mode hold Power + Volume Down button
2. Using the Volume buttons to scroll and the Power button to select, choose "Enter
recovery mode
3. Choose apply update from external storage
4. select "reboot system now after finished update
http://fota.asus.com/delta_package/.../WW_PF500KL-12.2.2.43-13.6.5.30-fota-user.zip
This screenshoot from my phone +Station
Error Status 7
I have error:
System partition has unexpected contents
E:Error in /sdcard/UL-ASUS_TOON-WW-13.6.5.30-user.zip
(Status 7)
anyone can help me?!
Same issue as well
Getting the same "System partition has unexpected contents (Status 7 )" any idea whats wrong?
It's most likely because of root, and any changes like installing busybox, or having edited the build.prop . I had to wipe system on my padfone x reinstall lollipop 43 then install the marshmallow ota, then root 2.68 then dd the Xmodem.img I found for USA radio bands and the twrp 3.0.0.0 img to get everything working.
Also I'm not sure if flashing without wiping data partition works the same as well as starting from scratch, but I did do it all in one shot and first without data being wiped and worked fine. But I then wiped everything to see how much space I could recover in app storage. I saved myself about a gigabyte and a half to have a total of 4gb remaining after apps were installed (i have a lot of apps)
Gizoid1337 said:
It's most likely because of root, and any changes like installing busybox, or having edited the build.prop . I had to wipe system on my padfone x reinstall lollipop 43 then install the marshmallow ota, then root 2.68 then dd the Xmodem.img I found for USA radio bands and the twrp 3.0.0.0 img to get everything working.
Also I'm not sure if flashing without wiping data partition works the same as well as starting from scratch, but I did do it all in one shot and first without data being wiped and worked fine. But I then wiped everything to see how much space I could recover in app storage. I saved myself about a gigabyte and a half to have a total of 4gb remaining after apps were installed (i have a lot of apps)
Click to expand...
Click to collapse
Thanks ! It worked for me
I reinstalled ver 12.2.2.43 which really is my current version, and then proceed to install MM 13.6.5.30 with success
Gizoid1337 said:
It's most likely because of root, and any changes like installing busybox, or having edited the build.prop . I had to wipe system on my padfone x reinstall lollipop 43 then install the marshmallow ota, then root 2.68 then dd the Xmodem.img I found for USA radio bands and the twrp 3.0.0.0 img to get everything working.
Also I'm not sure if flashing without wiping data partition works the same as well as starting from scratch, but I did do it all in one shot and first without data being wiped and worked fine. But I then wiped everything to see how much space I could recover in app storage. I saved myself about a gigabyte and a half to have a total of 4gb remaining after apps were installed (i have a lot of apps)
Click to expand...
Click to collapse
Thanks to you I have updated my phone to marshmallow using twrp 3.0.0, which allowed me to re-unlock bootloader, and root my phone.
It can be done, you just need to remove a few lines in the updater-script file.
something with ro.fingerprint (that identifies the recovery, it was originally expecting stock).
Replace it inside the zip. Then transfer update to sd card or internal.
After that wipe system, then reflash .43, right after that flash the mm update.
Will take some time but it should work once everything is verified.
reflash bl unlock and twrp (just a precaution) , then you can leave.
It would say no os but ignore it.
First boot takes around 10-15 mins then presto you finally have it.
Haven't encountered any bugs yet and it freed up a lot of storage space. Makes me wonder why I had to wait for the update to come to me, so glad I'm done with that.
So that concludes the last major update for the padfone s.....
Can u help me pls? I've tried unroot ,wipe system data and reflash .43 which is my current rom but still got signature verification error. any suggestion to fix this? Thx
Justatechie said:
Thanks to you I have updated my phone to marshmallow using twrp 3.0.0, which allowed me to re-unlock bootloader, and root my phone.
It can be done, you just need to remove a few lines in the updater-script file.
something with ro.fingerprint (that identifies the recovery, it was originally expecting stock).
Replace it inside the zip. Then transfer update to sd card or internal.
.
Click to expand...
Click to collapse
which lines exactly ? cause i tried removing mine and im now getting an error in the zip
error 6 or something
dtgo said:
which lines exactly ? cause i tried removing mine and im now getting an error in the zip
error 6 or something
Click to expand...
Click to collapse
On Notepad++: (not sure about notepad, but you must get rid of ro.build.fingerprint lines and the abort command after)
Delete/Remove lines 7 through 9. If left alone or not deleted fully it will not accept the update because its looking at the recovery image.
It expects 5.0 stock recovery but it sees 6.0 twrp. (since it was built off the source of twrp 3.0.0 which is mainly compatable with 6.0+)
Thats about it.
NightbladeSinX said:
Can u help me pls? I've tried unroot ,wipe system data and reflash .43 which is my current rom but still got signature verification error. any suggestion to fix this? Thx
Click to expand...
Click to collapse
Thats odd.
You should probably Re-download or transfer the ww file again. Could just be a bad transfer of data.
Make sure you have twrp 3.0.0 and that system protection off. (it pops up on the first screen, but you can find it under twrp settings)
Justatechie said:
On Notepad++: (not sure about notepad, but you must get rid of ro.build.fingerprint lines and the abort command after)
Delete/Remove lines 7 through 9. If left alone or not deleted fully it will not accept the update because its looking at the recovery image.
It expects 5.0 stock recovery but it sees 6.0 twrp. (since it was built off the source of twrp 3.0.0 which is mainly compatable with 6.0+)
Thats about it.
Click to expand...
Click to collapse
thanks for the reply , i did that and got Error 6 but it just fails right there , no message or anything
dtgo said:
thanks for the reply , i did that and got Error 6 but it just fails right there , no message or anything
Click to expand...
Click to collapse
If it doesn't say anything about identifying the device model or checking system, then something is wrong.
Might be a bad edit or it might have gotten corrupted while transferring back into the zip.
I stick with N++ for the edits, sometimes windows file transfer can be a pain by itself while trying to replace the update script, 7zip might help.
dtgo said:
thanks for the reply , i did that and got Error 6 but it just fails right there , no message or anything
Click to expand...
Click to collapse
got it working thanks again man you've been a big help
Justatechie said:
On Notepad++: (not sure about notepad, but you must get rid of ro.build.fingerprint lines and the abort command after)
Delete/Remove lines 7 through 9. If left alone or not deleted fully it will not accept the update because its looking at the recovery image.
It expects 5.0 stock recovery but it sees 6.0 twrp. (since it was built off the source of twrp 3.0.0 which is mainly compatable with 6.0+)
Thats about it.
Thats odd.
You should probably Re-download or transfer the ww file again. Could just be a bad transfer of data.
Make sure you have twrp 3.0.0 and that system protection off. (it pops up on the first screen, but you can find it under twrp settings)
Click to expand...
Click to collapse
Thx for reply. i manage to get updated to 6.0.1 but now i lost root. i did mistake not flashing twrp before 1st boot n it replace twrp to stock rec. Is there any root method available yet? I've tried latest kingroot but it was unsuccessful. Any way is there any difference between WW and TW firmware version?
NightbladeSinX said:
Thx for reply. i manage to get updated to 6.0.1 but now i lost root. i did mistake not flashing twrp before 1st boot n it replace twrp to stock rec. Is there any root method available yet? I've tried latest kingroot but it was unsuccessful. Any way is there any difference between WW and TW firmware version?
Click to expand...
Click to collapse
You could probably flash recovery through fastboot, only if your bootloader is unlocked. If not it wont allow the flash. it would say FAILED cant flash unsigned image, but theres a chance that it might have been flashed, just check to see if changes have applied.
Assuming that you have went to the fastboot portion of your phone you can check its status.
if its not unlocked, then you have to find another way to root to flash your twrp recovery back on your phone.
Did this, but kept getting errors due to (probably) my use of xposed. Managed to soft brick my phone, and recovered it using http://forum.xda-developers.com/padfone-x/help/guide-restoring-stock-rom-recovery-t3179818
After that, had to edit updater-script to remove all checks.
What tripped me up was just how long the update reboot took. Almost half an hour. I was going to give up but decided to leave it while taking a short nap.
heres the updater script for anyone having issues
Please can someone help me?
I'm trying so hard to get this to work but I'm barely getting anywhere. What I've done (thanks to ninekaw9's guide):
- unlock bootloader
- wiped everything (yet there is still stuff in the file explorer, like the su install folder)
- using fastboot boot recovery:
-- use TWRP 2.8.7.0 to transfer files from sdcard to emmc
-- with TWRP 2.7.1.1:
--- installed WW 99.99.99.0 for KK (works)
--- installed WW 12.2.2.27 for LP & stock recovery (works)
--- installed WW 12.2.2.43 for latest LP (works)
- removed every abort line from updater script to get it to stop complaining about fingerprint/unexpected system contents
- installed modified FOTA WW 13.6.5.30 for MM (no OS change)
So after all that, I'm where I started but with no apps.
Before I found out 2.8.7.0 couldn't flash stock ROMs I flashed 12.2.2.43 after a full wipe and ended up with no System UI...
Outcomes from using different recovery to flash MM update:
2.7.1.1 with unmodified: apparently my phone is TW not WW (incorrect)
2.8.7.0 with unmodified: some weird fingerprint with omni-T00N and 5.1.1, even after wipe and stock 12.2.2.43 flash. Couldn't edit or replace the default.prop file, it would just get overwritten each time
stock with unmodified: couldn't even mount my SD card, so tried ADB sideload, got the unexpected system contents message
stock with modified (no sha1): would no longer allow me to ADB sideload (0.00x message)
TWRP (either) with modified (no prop): unexpected system contents
TWRP (either) with modified (no prop/sha1): seems to work, but upon boot to system, nothing appears to have changed.
I desperately want MM so I have a smaller system partition, then I can stop pushing updates to system to save space, and therefore won't need root so I can play Pokemon GO and use Sky Q.
That or I'm going to try Magisk... Has anyone used this on a Padfone?
If anyone can guide me through which files/folders I can delete from my phone to save space, that would be great. I know most folders are mounting points, but there's a lot of .sh files and other folders that I'm not familiar with.
I've asked in another thread where I can get TWRP 3.x for Padfone S, but nobody has replied!
Please can someone help me?
Nintynuts said:
I'm trying so hard to get this to work but I'm barely getting anywhere. What I've done (thanks to ninekaw9's guide):
- unlock bootloader
- wiped everything (yet there is still stuff in the file explorer, like the su install folder)
- using fastboot boot recovery:
- use TWRP 2.8.7.0 to transfer files from sdcard to emmc
- with TWRP 2.7.1.1:
- installed WW 99.99.99.0 for KK (works)
- installed WW 12.2.2.27 for LP & stock recovery (works)
- installed WW 12.2.2.43 for latest LP (works)
- removed every abort line from updater script to get it to stop complaining about fingerprint/unexpected system contents
- installed modified FOTA WW 13.6.5.30 for MM (no OS change)
So after all that, I'm where I started but with no apps.
Before I found out 2.8.7.0 couldn't flash stock ROMs I flashed 12.2.2.43 after a full wipe and ended up with no SystemUI...
Outcomes from using different recovery to flash MM update:
2.7.1.1 with unmodified: apparently my phone is TW not WW (incorrect)
2.8.7.0 with unmodified: some weird fingerprint with omni-T00N and 5.1.1, even after wipe and stock 12.2.2.43 flash. Couldn't edit or replace the default.prop file, it would just get overwritten each time
stock with unmodified: couldn't even mount my SD card, so tried ADB sideload, got the unexpected system contents messagestock with modified (no sha1): would no longer allow me to ADB sideload (0.00x message)
TWRP (either) with modified (no prop): unexpected system contents
TWRP (either) with modified (no prop/sha1): seems to work, but upon boot to system, nothing appears to have changed.
I desperately want MM so I have a smaller system partition, then I can stop pushing updates to system to save space, and therefore won't need root so I can play Pokemon GO and use Sky Q.
That or I'm going to try hiding root Magisk...
If anyone can guide me through which files/folders I can delete from my phone to save space, that would be great. I know most folders are mounting points, but there's a lot of .sh files and other folders that I'm not familiar with.
I've asked in another thread where I can get TWRP 3.x for Padfone S, but nobody has replied!
Please can someone help me?
Click to expand...
Click to collapse
I used twrp 3.0. Worked like a charm what I ended up doing was reflashing the .43 and then the update after replacing the updater script file here is a link to the thread with the 3.0 twrp http://forum.xda-developers.com/padfone-x/general/padfone-xs-to-stock-lollipop-root-t3263664
xantanion said:
I used twrp 3.0. Worked like a charm what I ended up doing was reflashing the .43 and then the update after replacing the updater script file here is a link to the thread with the 3.0 twrp http://forum.xda-developers.com/padfone-x/general/padfone-xs-to-stock-lollipop-root-t3263664
Click to expand...
Click to collapse
Thanks. No wonder I couldn't find it as it doesn't mention 3.0.0.0 or 3.x or any version number at all.
I have answered my own Q&A thread with a link so hopefully others can find it. Will try it now.
xantanion said:
I used twrp 3.0. Worked like a charm what I ended up doing was reflashing the .43 and then the update after replacing the updater script file here is a link to the thread with the 3.0 twrp http://forum.xda-developers.com/padfone-x/general/padfone-xs-to-stock-lollipop-root-t3263664
Click to expand...
Click to collapse
Thankfully it has worked many thanks. Unfortunately while Sky Q no longer complains about root, it does complain about my Padfone station being an external display, so still won't play videos
Hi all,
Just unlocked bootloader of my S7+ and had Magisk / TWRP installed (https://forum.xda-developers.com/t/twrp-for-the-samsung-galaxy-tab-s7-5g-t976b.4163853/)
I was trying to install the Debloater module for Magisk. I tried to install first using Magisk Manager but it always gave me an error.
I felt curious and decided to install from TWRP instead. But under TWRP it just gave me an error 1 when it was trying to mount /system , so that installation always failed.
I went to Advanced Wipe trying to repair the partition. Interestingly, /system wasn't among the listed options.
I seem to be able to browse the files under /system using TWRP's file manager just fine. So what's with the inability to mount it?
Any help is appreciated. Thanks! I've flashed multi disabler and VBmeta (that didn't seem to matter)