Clockwork Recovery buggy? - Barnes & Noble Nook Tablet

8GB Nook Tablet model.
I flashed CWM via the one-click tool provided by Indirect, and I can boot into it fine. The problems arise when actually attempting to use it, however. It reboots occasionally, and I haven't been able to flash any .zip files successfully. Anytime I attempt to flash them, CWM just hangs, or in the case of the CM9 flash, creates rainbow stripes across the screen.
So, unfortunately, my NT seems to be in a soft-brick state. It'll boot to the white reading screen, but no further. CM7 SD version works fine, but I'm wondering if there's any way to recover back to factory, as well as what I did wrong.

Well, I managed to fix the soft brick by booting into the broken CMW, and using ADB to write the recovery_512MB.img from the CM9 thread to the device. That CWM worked fine, no glitches or lockups during flashes, although flashing CM7 just ending up with it continually booting into recovery.
At any rate, I was able to edit the stock 1.4.2 update's update-script, and got it flashed via CWM, so my tablet is back working.
I suppose my only real question now would be if there's an easy, working way to flash either CM7 or CM9 to the 8GB.

songjacked said:
Well, I managed to fix the soft brick by booting into the broken CMW, and using ADB to write the recovery_512MB.img from the CM9 thread to the device. That CWM worked fine, no glitches or lockups during flashes, although flashing CM7 just ending up with it continually booting into recovery.
At any rate, I was able to edit the stock 1.4.2 update's update-script, and got it flashed via CWM, so my tablet is back working.
I suppose my only real question now would be if there's an easy, working way to flash either CM7 or CM9 to the 8GB.
Click to expand...
Click to collapse
I am having the exact same problem you described in your first post. What changes did you make to the update script to get it to work? I keep getting cannot open package errors.

cheddleson said:
I am having the exact same problem you described in your first post. What changes did you make to the update script to get it to work? I keep getting cannot open package errors.
Click to expand...
Click to collapse
Assuming you have a functioning CWM Recovery, you should be able to flash the 1.4.2 update from the B&N website. Download their software zip, then unzip the contents. I don't remember the exact location of the file offhand, but it's called update-script, and should be located a few folders in.
Open the update-script with Notepad, then delete the first two lines as shown in the CM9 thread:
http://forum.xda-developers.com/showthread.php?t=1534192
assert(getprop("ro.product.device") == "blaze" ||
getprop("ro.build.product") == "blaze");
Save the changes, then rezip the contents. I wasn't sure what compression settings to use, so I just chose the "store" level. Made the update grow to about 408MB. Just flash that zip through recovery, and you should be set.

songjacked said:
Assuming you have a functioning CWM Recovery, you should be able to flash the 1.4.2 update from the B&N website. Download their software zip, then unzip the contents. I don't remember the exact location of the file offhand, but it's called update-script, and should be located a few folders in.
Open the update-script with Notepad, then delete the first two lines as shown in the CM9 thread:
http://forum.xda-developers.com/showthread.php?t=1534192
assert(getprop("ro.product.device") == "blaze" ||
getprop("ro.build.product") == "blaze");
Save the changes, then rezip the contents. I wasn't sure what compression settings to use, so I just chose the "store" level. Made the update grow to about 408MB. Just flash that zip through recovery, and you should be set.
Click to expand...
Click to collapse
Thanks, I think that's about the only thing I haven't tried yet. Can't wait for more development in the 8 gig. I'll be sure to thank you if it works for me.
Sent from my SAMSUNG-SGH-I897 using Tapatalk

Related

Trying to flash My own Rom

Used dsixdas Rom kitchen.
Built my own Rom using rogers stock RUU
starts to flash, then I get, error in sd card installation aborted
(status 0)
the last thing it was doing
minzip: extracted file "system/cuE:Error in /sdcard/marksrom
any takers??!!
Thanks guys
markdexter said:
Used dsixdas Rom kitchen.
Built my own Rom using rogers stock RUU
starts to flash, then I get, error in sd card installation aborted
(status 0)
the last thing it was doing
minzip: extracted file "system/cuE:Error in /sdcard/marksrom
any takers??!!
Thanks guys
Click to expand...
Click to collapse
What type of zip file is it?
its just the one that dsxidas tool spits out, although I did notice some differences.
If i click on the Rom.zip file, go to properties, then security. The only 2 that where check-marked was "modify" and "read & execute" So i compared that to a Rom that works on my device and noticed that in that same box they where all checked. - full control
modify
Read & execute
Read
Write
Special permissions
I changed those in my Rom so there all checked,however cant flash till tonight.
Just wondering if that could possibly be an, or the, issue
Not sure how to check what type of .zip file it is??
markdexter said:
Used dsixdas Rom kitchen.
Built my own Rom using rogers stock RUU
starts to flash, then I get, error in sd card installation aborted
(status 0)
the last thing it was doing
minzip: extracted file "system/cuE:Error in /sdcard/marksrom
any takers??!!
Thanks guys
Click to expand...
Click to collapse
markdexter said:
its just the one that dsxidas tool spits out, although I did notice some differences.
If i click on the Rom.zip file, go to properties, then security. The only 2 that where check-marked was "modify" and "read & execute" So i compared that to a Rom that works on my device and noticed that in that same box they where all checked. - full control
modify
Read & execute
Read
Write
Special permissions
I changed those in my Rom so there all checked,however cant flash till tonight.
Just wondering if that could possibly be an, or the, issue
Not sure how to check what type of .zip file it is??
Click to expand...
Click to collapse
Lol .. the "check boxes" you're referring to only indicate the access permissions for the specific .zip file. When in recovery mode, everything runs as root. If there is any read permission on the file, recovery should be able to acces it without any issues. Further, you mentioned above the recovery was in the process of flashing the file indicating the recovery has no issues accessing the file.
If the recovery has no issues accessing the file, there shouldn't be any issues with the specific permissions of the ROM .zip file on that specific file system in recovery mode.
As a ROM developer, the next step to troubleshooting and understanding errors when flashing a ROM is by becoming familiar with the custom recovery error log.
The custom recovery shows very limited information on the display, but in the log shows much more detail. The logs are generally kept at /tmp/recovery.log and /cache/recovery.log.
The best process is to process the .zip file and when the recovery errors, open up the recovery log. If you can paste back here the few lines before the error occurred including the error we can start working on the issue.
We might need a copy of the .zip file to match up with the recovery log to understand how much progress was made in order before the error occured.
The only other common place for ROM flashing errors when developing a ROM will be in the updater-script file. Might need a copy of this posted also.
In summary, the two most common places for issues occur either in the file name/structure of the .zip or in the updater-script.
Hope that helps! Good luck!
joeykrim said:
Lol .. the "check boxes" you're referring to only indicate the access permissions for the specific .zip file. When in recovery mode, everything runs as root. If there is any read permission on the file, recovery should be able to acces it without any issues. Further, you mentioned above the recovery was in the process of flashing the file indicating the recovery has no issues accessing the file.
If the recovery has no issues accessing the file, there shouldn't be any issues with the specific permissions of the ROM .zip file on that specific file system in recovery mode.
As a ROM developer, the next step to troubleshooting and understanding errors when flashing a ROM is by becoming familiar with the custom recovery error log.
The custom recovery shows very limited information on the display, but in the log shows much more detail. The logs are generally kept at /tmp/recovery.log and /cache/recovery.log.
The best process is to process the .zip file and when the recovery errors, open up the recovery log. If you can paste back here the few lines before the error occurred including the error we can start working on the issue.
We might need a copy of the .zip file to match up with the recovery log to understand how much progress was made in order before the error occured.
The only common place for ROM flashing errors when developing a ROM will be in the updater-script file. Might need a copy of this posted also.
In summary, the two most common places for issues occur either in the file name/structure of the .zip or in the updater-script.
Hope that helps! Good luck!
Click to expand...
Click to collapse
Amazing answer, thank you so much for taking your time with me, appreciate it, I'll try the recovery log, see what I get, as you can tell I'm pretty new to this, everyone has to start somewhere!
Thanks again buddy
Sent from my HTC EVO 3D X515a using xda premium

Anyone got a CWM backup handy?

I have failed rather spectacularly trying to reflash my phone using heimdall. (This has worked previously, but now it decided to break my phone)
Long story short, it will no longer flash the factoryfs.img of anything I try and make it flash (it fails at 42%, oddly). clockworkmod recovery mode still works (version 5.0.2.7), however I did not make a backup of the phone while it was in a workable state. When I attempt to install an update.zip file using clockworkmod I get an assertation failed error whinging that my build.prop file does not contain the proper device identifier string (Seems I managed to bork that, too).
I had the idea that I might be able to edit a factoryfs.img of an existing ROM and put in a build.prop file that has the required property, however have been unable to mount it. Those things seem to be structured oddly.
Using Odin is not an option. I do not have access to a windows computer.
Does someone have a clockworkmod backup of a working SGS2I9100, then? It is my hope that if I can procure one of these and stick it on the SD card clockworkmod will be able to load it (And then, provided this fixes the whole build.prop thing, I can install something from a zip).
Does there exist a way of editing build.prop from the computer? All I can seem to find are instructions of the form "Install this app and do it from your phone" - not much use when the thing won't boot.
Does anyone have any thoughts about why heimdall no longer works? It has worked before, but now, as I said, fails consistently at 42% of the way through factoryfs.img for whatever ROM I try to use.
Any other ideas? This thing's been bricked for a while now and I'm fresh out of ideas on how to fix it. Heimdall does seem to still be able to flash other things (just not factoryfs). So other plausible solutions would seem to be some way of flashing a working build.prop with heimdall or some update.zip of a working system that precludes the entirely sensible assertations that check the file.
If your recovery is working why not just install a custom zipped firmware.. after that you can reinstall a stock rom.
If you're positive you're installing something in CWM recovery for the correct device, you can disable script asserts.
get acses of pc an use odin.jus to make sure ur device is good
Sent from my GT-I9100 using xda premium
rocky23 said:
get acses of pc an use odin.jus to make sure ur device is good
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
here u go
Thank you all for your responses, but alas these all seem not to have worked :-
bored_stupid: As mentioned in my first post, I cannot use CWM recovery mode to install a zip from the sd card because of the assertation failure problem.
oinkylicious: Great idea! But rather strangely this had no effect on the problem - the same assertation failure error was always produced.
rocky23: That is certainly worth a try, but I wasn't kidding when I said I have no access to a windows pc. I really, really don't. Only Linux. (And it seems distinctly odd that I'd have to use Windows to fix the Unix based OS on my phone).
Thank you for the apk, however isn't that apk simply the clockworkmod recovery manager app? I am unsure how this is useful when my phone does not boot? Or did I miss something?
When I requested "a CWM backup" I was hoping for an actual system bacup, as generated by CWM recovery by it's "create backup" function. My reason for requesting this is that it is my belief that this would be installed without checking the (apparently broken) build.prop file, or at the very least would correct it so I'd be able to install an update zip in the usual way.
Thank you again - any other ideas?
In case it is helpful, the precise assertation failure error produced when attempting to install an update zip with CWM recover:
Code:
assert failed: getprop("ro.product.device") == "GT-I9100" || getprop("ro.build.product") == "GT-I9100" || getprop("ro.product.device") == "galaxys2" || getprop("ro.build.product") == "galaxys2"
As you can see, it appears the installer is (rather sensibly) checking that my phone really is a galaxy s2 I9100 (Which it is, I promise), and the phone seems to be incorrectly reporting that it is not.
As mentioned, I think this is because I managed to ruin my build.prop file somehow. Any ideas on how to correct that (Or any other alternative solutions)?
If indeed someone gave you a CWM backup it would contain a lot of personal information .
jje
Potentially so, yes, unless work was done to prune that out at the start. I am unfamiliar with the structure of these backups - could one that consisted only of /system be created?
daperson said:
In case it is helpful, the precise assertation failure error produced when attempting to install an update zip with CWM recover:
Code:
assert failed: getprop("ro.product.device") == "GT-I9100" || getprop("ro.build.product") == "GT-I9100" || getprop("ro.product.device") == "galaxys2" || getprop("ro.build.product") == "galaxys2"
As you can see, it appears the installer is (rather sensibly) checking that my phone really is a galaxy s2 I9100 (Which it is, I promise), and the phone seems to be incorrectly reporting that it is not.
As mentioned, I think this is because I managed to ruin my build.prop file somehow. Any ideas on how to correct that (Or any other alternative solutions)?
Click to expand...
Click to collapse
You could just delete the part of the script that checks what deveice you are on.

[Q] assert failed: getprop("ro.product.device") =="p4wifi" ...

Hi all,
assert failed: getprop("ro.product.device") =="p4wifi" ...
I can not seam to delete the first line that i read from some post using Notepad++ if i make a copy to my desktop i can delete the first line of the install script, but can not copy it back to the zip folder. Trying to load an older version of the same rom i get the same error now also.
Any help would be great. and yes i have the right file for the right tablet ver GT p7510 wifi and trying to use cm-10-20121017-exp zip.
Loaded the new recovery and bootloader also.
any help would be great.
did you try to update script directly into zip file ?
I don't know which OS you are using (maybe windows ?), with linux, you can edit a file directly a zip file (file roller for me). After saving your file, zip is automatically updated.
if you are using winzip, i guess you can drag and drop updated file into your zip.
of course, you need to edit the zip file out of your tab.
Thanks Light,
But i tried all different ways with no luck. I am on the 20121017 now i just had to use an older version of the CWM recovery.
;P
Kokapelly said:
Thanks Light,
But i tried all different ways with no luck. I am on the 20121017 now i just had to use an older version of the CWM recovery.
;P
Click to expand...
Click to collapse
Hey could you please just list files you used to make it work? I think I have the same issue as you.
Thanks in advance,
Regards,
Baptiste
BatBat said:
Hey could you please just list files you used to make it work? I think I have the same issue as you.
Thanks in advance,
Regards,
Baptiste
Click to expand...
Click to collapse
this is the path of the file : /META-INF/com/google/android/
the file name is : updater-script
Code:
assert(getprop("ro.product.device") == "p4wifi" || getprop("ro.build.product") == "p4wifi");
mount("ext4", "EMMC", "/dev/block/platform/sdhci-tegra.3/by-num/p4", "/system");
package_extract_file("system/bin/backuptool.sh", "/tmp/backuptool.sh");
package_extract_file("system/bin/backuptool.functions", "/tmp/backuptool.functions");
...
you just need to delete the first line (assert(getprop...).
Kokapelly said:
Hi all,
assert failed: getprop("ro.product.device") =="p4wifi" ...
Click to expand...
Click to collapse
If you're seeing that, then you should update your CWM. It's not recognizing your tablet device. I'm using CWM 5.5.0.4 and it does recognize the P7510 as "p4wifi".
Kokapelly said:
I can not seam to delete the first line that i read from some post using Notepad++ if i make a copy to my desktop i can delete the first line of the install script, but can not copy it back to the zip folder. Trying to load an older version of the same rom i get the same error now also.
Any help would be great. and yes i have the right file for the right tablet ver GT p7510 wifi and trying to use cm-10-20121017-exp zip.
Loaded the new recovery and bootloader also.
any help would be great.
Click to expand...
Click to collapse
If it's easier, edit the file and just insert a "#" before the "assert". That will comment it out. However, I'd recommend updating the recovery instead.
Success Story - you figure out how...
This is a SUCCESS story...
I got by this somehow, not sure what it was but will over communicate so someone else can figure out specifics.
updating my gt-p7510 from android 3.1 to Android 4.1.2 (CM 10 ROM 20121215 nightly)...
My tab was in weird state from a prior rom sequence (I had rooted it long ago.. some programs said it was rooted, but programs trying to get the permission, like titanium backup, would fail)
so I followed the instructions to root again from HERE
up to the point to the point where you load a ROM. ie. I loaded CWM 5.5.0.4 using odin3.
Then I downloaded the latest CM 10 , copied it to root folder on my tab... and tried to use CWM to install it...
got the "assert(getprop("ro.product.device") == "p4wifi" ... Failure...
went wild and tried other programs (ROM Manager, System Updater etc. avail from "Play Store" ... actually I had tried these prior to rooting again...
they failed before (not able to get root permissions) and after (not able to perform the update... assuming they got and hid similar error)
Tried to edit out the assert in the updater-script as in the prior post... but unzipping had a lot of duplicate file overrides (into clean folder) and they were not all exactly the same file (ie some had different sizes)... so gave up that path.
I had been avoiding updating CWM further because of k1mu's success above ... and avoided the "CWM Touch" flash as I thought base CWM would be better.
Went back to try to update CWM (went to www.clockworkmod.com) and was annoyed when I could not download the CWM zips... links returned characters in browser...
Finally went wild again... used ROM Manager Pro to update CWM to the latest "CWM Touch"
Surprisingly this updated CWM easily...
Then used it to Load the latest CM 10 nightly ... again shockingly easy AND successful... (no Assert failure)
ROM Manager did not automatically update the google apps ... so I got my first look at the CWM Touch interface installing gapps...
But it all worked... So LOVE ROM Manager...
(although for grins I also found and tried CM 10 downloader and retried System Updater Pro etc.. .they all work now)
But hats off to ROM Manager's update and to CWM touch for seemingly fixing all my problems.
lightman33 said:
this is the path of the file : /META-INF/com/google/android/
the file name is : updater-script
Code:
assert(getprop("ro.product.device") == "p4wifi" || getprop("ro.build.product") == "p4wifi");
mount("ext4", "EMMC", "/dev/block/platform/sdhci-tegra.3/by-num/p4", "/system");
package_extract_file("system/bin/backuptool.sh", "/tmp/backuptool.sh");
package_extract_file("system/bin/backuptool.functions", "/tmp/backuptool.functions");
...
you just need to delete the first line (assert(getprop...).
Click to expand...
Click to collapse
I open in notepad++ and here is the code from updater-script
Code:
assert(!less_than_int(1383478437, getprop("ro.build.date.utc")));
assert(getprop("ro.product.device") == "p4wifi" || getprop("ro.build.product") == "p4wifi");
mount("ext4", "EMMC", "/dev/block/platform/sdhci-tegra.3/by-num/p4", "/system");
So do I need to delete full 1st line or 2nd line?
If I follow your instruction, I have to delete 2nd line...
EDITED:
Line 2 deleted! And done flashing
The answer to all of this: The problem is the recovery, not the update package, or the updater script.
The assert fails because CWM, TWRP, and some other modified recoveries do not include the getprop command in their small, ramdisk linux OS. So, when the assert tries to run getprop to check ANY property for the installed system, it fails.
Apparently CWM Touch has this binary included.
Custom recoveries generally don't think to include it because pretty much the only thing being flashed through them are custom roms, with their own custom installer scripts, and these rarely (have they ever?) include asserts checking for properties.

Android kitchen is not using the correct mount points.

So I was trying to package a rom and let the kitchen create the meta-inf folder along with the updater-script but the problem is that it's not using the specified mount points.
My phone isn't supported in the kitchen so I had to make a file in the edify_defs folder for my phone. I did all the right steps, I renamed the file to that of the ro.produc.device, used the template and made the necessary edits using notepad ++, and checked the file for any incorrect syntax yet after all that, the kitchen isn't using the mount points I put but instead uses the default value "mount("MTD", "system", "/system")".
Any help?
bump
Don't rely on kitchen's mount. Instead, use the update binary of a working zip for your device and edit the updater-script manually to make it work.
iZLeeP said:
Don't rely on kitchen's mount. Instead, use the update binary of a working zip for your device and edit the updater-script manually to make it work.
Click to expand...
Click to collapse
Yah, the thing is there are no roms for my device not even a stock rom. This is the reason why I'm trying to learn how to build a rom.
Anyways, I got the kitchen to detect the mount points. Turns out i had put the kitchen in the wrong directory. Made the zip flash correctly but now i encountered a new problem. After flashing the zip, the interface on my phone becomes really small. It's like my display went into tablet mode. Any idea on this?
black_fire21 said:
Yah, the thing is there are no roms for my device not even a stock rom. This is the reason why I'm trying to learn how to build a rom.
Anyways, I got the kitchen to detect the mount points. Turns out i had put the kitchen in the wrong directory. Made the zip flash correctly but now i encountered a new problem. After flashing the zip, the interface on my phone becomes really small. It's like my display went into tablet mode. Any idea on this?
Click to expand...
Click to collapse
What's your device and android version? Much better if you could post on your device's specific thread.
It's a local phone called starmobile quest, running jellybean. Sadly, there is absolutely no support for the device not even from the manufacturers. There are no developers either. The only thing we have is root and cwm.

Update Fota Lollipop 43 to MM 13.6.5.30 (WW)

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

Categories

Resources