Hello professionals!
I wonder if someone please can instruct me in how to complete the 10.1 Nightly update from ICS 4.0.4.
I'm half there in the process but it always ends with this error :
Installing update...
assert failed: assert failed: getprop("ro.product.device") == "p990" || getprop("ro.build.product") == "p990"
E: Error in /sdcard/cm-10.1-20131006-NIGHTLY-p990.zip
(Status 7)
Installation aborted
I'm using latest ROM Manager and the phone is rooted ok.
How do I solve this, I'm stuck and have read for 10 hours online and on Youtube without finding a resolution!??
What am I doing wrong here and how do I solve it?
Every little help on the way will be very much appreciated!
Anna.A. said:
Hello professionals!
I wonder if someone please can instruct me in how to complete the 10.1 Nightly update from ICS 4.0.4.
I'm half there in the process but it always ends with this error :
Installing update...
assert failed: assert failed: getprop("ro.product.device") == "p990" || getprop("ro.build.product") == "p990"
E: Error in /sdcard/cm-10.1-20131006-NIGHTLY-p990.zip
(Status 7)
Installation aborted
I'm using latest ROM Manager and the phone is rooted ok.
How do I solve this, I'm stuck and have read for 10 hours online and on Youtube without finding a resolution!??
What am I doing wrong here and how do I solve it?
Every little help on the way will be very much appreciated!
Click to expand...
Click to collapse
Last time that happened to me I had to update to a newer version of clockworkmod recovery.
you might ask in the thread for your ROM to see if anyone else is having the same issue.
firefly6240 said:
Last time that happened to me I had to update to a newer version of clockworkmod recovery.
you might ask in the thread for your ROM to see if anyone else is having the same issue.
Click to expand...
Click to collapse
Thank you for your reply!
I have "some" knowledge in this (not totally stupid, that is) and I am sure I will fix this, but please tell me - how do I update Clockworkmod Recovery and where do I find information about it on the phone to know what version I have?
The directions I've read about it just does not give me a clear answer in how to do it!
Anna.A. said:
Thank you for your reply!
I have "some" knowledge in this (not totally stupid, that is) and I am sure I will fix this, but please tell me - how do I update Clockworkmod Recovery and where do I find information about it on the phone to know what version I have?
The directions I've read about it just does not give me a clear answer in how to do it!
Click to expand...
Click to collapse
the version is usually shown at the top or the bottom of the screen while in recovery mode,
it will say "clockwork Mod Recovery vx.x.x.x if its the official CM revovery.
or if its an alternate recovery it will usually say CWM based recovery vx.x.x.x
to be safe I would ask in the forum of your rom what version other people are running that have successfully updated and compare it with yours.
if you have a lower version ask where they got theirs as some roms work better with custom recoverys
as a last resort you should be able to install it from the rom manager app or from the clockworkmod website though I would think some alternate recoveries will be based on higher versions so definitely check with other users before flashing anything.
for reference I am running a MIUI port called GearUI as my Rom (android 4.1.2)
my recovery version is: CWM base version v6.0.3.7 (Gear kernel recovery)
but this will vary from rom to rom.
Thank you for reply!
This is how I do the update to CM 10.1 ;
When I connect the phone to PC it shows as 2 separate external SD-cards. E: and F:
- which am i suppose to use for the .zip? The one with DCIM / LOST DIR?
So I have tried to place cm-10.1-20131006-NIGHTLY-p990.zip0 and gapps-jb-20121212-signed.zip on both (just to be sure, but in no maps), and after that I have tried to open them separately from both E: and F: but none works.
Installing update...
assert failed: assert failed: getprop("ro.product.device") == "p990" || getprop("ro.build.product") == "p990"
E: Error in /sdcard/cm-10.1-20131006-NIGHTLY-p990.zip
(Status 7)
Installation aborted
ROM Manager is version 5.5.3.0 and is suppose to be the latest from GooglePlay, no newer versions can be found.
It's flashed and I have root access.
ClockworkMode Recovery is version 6.0.1.5
I don't get this ; In CWM I don't see the external SD card as an option, only "install zip from sdcard" but I have the zip-files on the external SD-card?
I will keep looking for answer for why updating to 10.1 is so tricky, when both rooting and updating to 4.0.4 was a piece of cake, but is also very glad for help on the way!
Anna.A. said:
(Status 7)
Installation aborted !
Click to expand...
Click to collapse
From MY Android Solutions
[27] Problem:- ClockworkMod Recovery giving Status 7 error "Installation aborted".
Quote:
Solution:- One or some of the prerequisite requirement for the needed upgrade is missing or corrupted . So you may need to identify and replace that requirement for the installation to continue. Most likely could be due to wrong bootloader, wrong CWM, Wrong IMEI, Wrong Radio etc
Check this out! You , YES! you are an " Android ". Not your phone but U.
You Must watch this documentary concerning your privacy Terms & Conditions we had agreed to, by using a PC or Smartphone
How to say Thank you? If you find any post helpful on XDA, click on their Thanks button
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you are using XDA App or Tapatalk, long press on the post and select :good: Thanks
Its easier to give "Feedback" in this manner than make an additional post.
Ok that makes sence.
However, I cannot find any other downloading sites for those files besides from here and here.
A very strange thing though! The phone now sais that I do not have a external SDcard after removing the SIM-card (to use in another while doing this update fix)!!!!
Is the SIM being used as a SDcard, that cannot be right?
So when I placed the zip-files on the SDcard root (E, the phone now sais this ;
E:Can't open /sdcard/cm-10.1-20131006-NIGHTLY-p990.zip
(No such file or directory)
Installation aborted.
But the zip-files ARE there but when being in CWM it sais that the zip-files are placed in /emmc/
What am I doing wrong???!
Anna.A. said:
What am I doing wrong???!
Click to expand...
Click to collapse
First problem is, you have not informed what is your Phone Model? which means no one in XDA can help, unless they are a magician second being, external SD card will be considered emmc, as such you should install from Ext SD card, if files were placed in External SD card or place the files in your internal Sd card and install . Most of all it must be for your phone model, not just for any brand and model.
Check this out! You , YES! you are an " Android ". Not your phone but U.
You Must watch this documentary concerning your privacy Terms & Conditions we had agreed to, by using a PC or Smartphone
How to say Thank you? If you find any post helpful on XDA, click on their Thanks button
If you are using XDA App or Tapatalk, long press on the post and select :good: Thanks
Its easier to give "Feedback" in this manner than make an additional post.
Oh I'm so sorry! But I simply just thought that it was clear on what phone model it's about by the CM-file name.
I have a LG P990 2x.
cm-10.1-20131006-NIGHTLY-p990.zip
you can try deleting the getprop line out of the updater-script file inside the zip. if you search the forums there are instructions on how to do this. but if it fails on that step it could be an indicator it is not for your phone. this line checks to make sure you are using the right build for your phone
smos08 said:
you can try deleting the getprop line out of the updater-script file inside the zip. if you search the forums there are instructions on how to do this. but if it fails on that step it could be an indicator it is not for your phone. this line checks to make sure you are using the right build for your phone
Click to expand...
Click to collapse
Very good advice, thank you! However, that didn't do the trick either.
I found excellent instructions in how to fix the updater-script but the file could not be saved as original again after removing .txt.
I renamed it to .txt and fixed the script in EditPad, but the .txt was not written out TO be removed afterwards, (as on the instruction video) and there was no way to rename it in any other way.
I use Windows 7.
I'm now stuck with 4.0.4 and a wiped out phone on all data. ;-(
I can get internet access though SIM but WiFi doesn't work no more.
When trying to re-create my Google account (to get access to all my accounts and apps) it fails too ; "com.android.vending has stopped working".
I need my Link2SD to get acccess to what needs to be fixed, but that app is also gone. Root is also gone.
Also, when logged in to Google+ account I can see all my apps being installed and everything looks fine - BUT they are not installed on the phone no more and I need to re-install them, but I havent found any information in how to do that either!
I'm very stubborn so I will get this fixed and I will upgrade to JB, and with your help I will succeed!
Anna.A. said:
Very good advice, thank you! However, that didn't do the trick either.
I found excellent instructions in how to fix the updater-script but the file could not be saved as original again after removing .txt.
I renamed it to .txt and fixed the script in EditPad, but the .txt was not written out TO be removed afterwards, (as on the instruction video) and there was no way to rename it in any other way.
I use Windows 7.
I'm now stuck with 4.0.4 and a wiped out phone on all data. ;-(
I can get internet access though SIM but WiFi doesn't work no more.
When trying to re-create my Google account (to get access to all my accounts and apps) it fails too ; "com.android.vending has stopped working".
I need my Link2SD to get acccess to what needs to be fixed, but that app is also gone. Root is also gone.
Also, when logged in to Google+ account I can see all my apps being installed and everything looks fine - BUT they are not installed on the phone no more and I need to re-install them, but I havent found any information in how to do that either!
I'm very stubborn so I will get this fixed and I will upgrade to JB, and with your help I will succeed!
Click to expand...
Click to collapse
i have been successful doing it like this. (you will need 7zip and notepad++)
right click on zip, open archive with 7zip
navigate to the updater-script file
copy to local HD (should come over as just a "file" with no extension)
right click and open with notepas++
use notepad++ to delete the entire line so there are no blank spaces at the top
save the file (ctrl+s) will not prompt for file type
go to open archive and delete updater-script from the rom ZIP (using delete button in 7zip)
drag your local copy (the one we edited with notepad++) onto the zip and it will copy it in
close DO NOT SAVE just close the window
copy rom to phone/sd then flash
Ah, so that's how to save it! "save the file (ctrl+s) will not prompt for file type" - very good to know, THANK YOU!
However, I have managed to fix iCM 10.1 t with help of AIO Tookit and have now 4.2.2 installed, but the only thing not working (and I do not find the answer to anywhere) is that the SD card is not recognized.
I have formatted it with SDFormatter but still it's not found by the camera and spent hours and hours google for answers.
Maybe you know the answer to how to fix that too?
Through bad flashes I've corrupted an SD beyond readability on any device; win/mac/and android. Just had to buy a new one.
Sent from carbon note 2 on XDA premium app
Related
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
I was trying to root NT 1.4.2 8gb, rooted with the Market. And then I tried to root it to CM7, my NT was dead.
With Nook Recovery Flasher.apk., I rebooted, insert SD(...zip), when I tried to backup, it was dead. Then I tried again whithout backup, at first, it worked, but stopped during installing(updating... then stopped). And never boot again.
If i turn on, i can see 'N' logo with black screen, but no process. How can I reboot my NT? I want it to be the very factory setting. -.-;; Or can I find factory-base recovery file anywhere?
edit: Wait you have an 8gb tablet? Have you tried to flash 1.4.2 with cwm?
yes...
I have an 8g NT that was 1.4.2.
any backup file or booting file? please...
Good! Use cwm to flash 1.4.2 update. see if that works
thanks !!
for the quick and helpful response!!
but where can i find it? (sorry, I am not expert.)
any link? i've tried, but i can't.
and is it *.img? if so it will be OK.
but it cannot be booted, so i cannot use Nook Recovery Flasher.apk.
http://forum.xda-developers.com/showpost.php?p=24164043&postcount=1
.. read the ATTENTION 8GB USERS and apply it, and also read the READ ME (link)
~ Veronica
lavero.burgos said:
http://forum.xda-developers.com/showpost.php?p=24164043&postcount=1
.. read the ATTENTION 8GB USERS and apply it, and also read the READ ME (link)
~ Veronica
Click to expand...
Click to collapse
Wait wait wait, not to get off topic or anything. But is the 1.4.2 update, the same thing for both 8gb and 16gb nooks?/
---------- Post added at 02:26 PM ---------- Previous post was at 02:25 PM ----------
firstgleam said:
for the quick and helpful response!!
but where can i find it? (sorry, I am not expert.)
any link? i've tried, but i can't.
and is it *.img? if so it will be OK.
but it cannot be booted, so i cannot use Nook Recovery Flasher.apk.
Click to expand...
Click to collapse
Have you made a bootable sdcard?? Make you sure have at least a 2gb microsd.
soshite said:
Wait wait wait, not to get off topic or anything. But is the 1.4.2 update, the same thing for both 8gb and 16gb nooks?
Click to expand...
Click to collapse
Yes stock 1.4.2 works for both, remember 8GB NT came with 1.4.2 it is why devs base on 1.4.2 mlo, uboot, etc files to make their hacks that work for both models.
~ Veronica
Huh~
I cannot do it.
I tried several times, but failed.
My situatuion;
1. Cannot boot
2. If i try to boot, i can see only 'n' logo with black screen
3. I can boot with SD to CM7(Team-B-CM7SD-Alpha_final). In this case, I can do nothing with NT. but I can enjoy CM7 in SD.
4. I tried several times,especially, i can see sometimes <booti: bad boot img>.
How and where can i start?
firstgleam said:
I cannot do it.
I tried several times, but failed.
My situatuion;
1. Cannot boot
2. If i try to boot, i can see only 'n' logo with black screen
3. I can boot with SD to CM7(Team-B-CM7SD-Alpha_final). In this case, I can do nothing with NT. but I can enjoy CM7 in SD.
4. I tried several times,especially, i can see sometimes <booti: bad boot img>.
How and where can i start?
Click to expand...
Click to collapse
It's the stupid script in Barnes & Noble's file. Go ahead and unpack the 1.4.2 update into a folder, name it like "update" or something. Onto your computer by the way! Make a new zip, just call it update.zip
Now, on your "update" folder, navigate over to /META-INF/com/google/android/
And edit "updater-script" with notepad or something, and delete these two lines:
assert(getprop("ro.product.device") == "blaze" ||
getprop("ro.build.product") == "blaze");
Click to expand...
Click to collapse
Sweet amirite? Save it, and then move everything inside "update" onto the update.zip folder we just made. Don't move the folder, move the contents.
Then put that in the sdcard, boot into clockworkmod again and try to flash update.zip
The reason I have you do all that is because it's signed. At least that's what I think is going on, because I can't edit the files from within the zip itself.
I can't get into clockworkmod.
I can't make booting.
Always I failed.
I can just see 'N' logo....
But you said you tried to flash the update in cwm? ??
firstgleam said:
I cannot do it.
I tried several times, but failed.
My situatuion;
1. Cannot boot
2. If i try to boot, i can see only 'n' logo with black screen
3. I can boot with SD to CM7(Team-B-CM7SD-Alpha_final). In this case, I can do nothing with NT. but I can enjoy CM7 in SD.
4. I tried several times,especially, i can see sometimes <booti: bad boot img>.
How and where can i start?
Click to expand...
Click to collapse
Did you follow my instructions to the T? What errors do you get if any when flashing stock recovery or the B&N stock 1.4.2 update. zip?
If you can boot into cm7 or @meghd00t cwm recovery from sdcard all you have to do is use dd to flash stock recovery and then run the update from another sdcard.
Don't try random unbrick methods, you can make it worst, your problem is not to go and mess with advanced methods. At list yet. But if you have messed around even more since then your boot block can get damaged. Go safe first.
~ Veronica
Sent from my BNTV250A using xda premium
---------- Post added at 10:43 AM ---------- Previous post was at 10:25 AM ----------
soshite said:
It's the stupid script in Barnes & Noble's file. Go ahead and unpack the 1.4.2 update into a folder, name it like "update" or something. Onto your computer by the way! Make a new zip, just call it update.zip
Now, on your "update" folder, navigate over to /META-INF/com/google/android/
And edit "updater-script" with notepad or something, and delete these two lines:
Sweet amirite? Save it, and then move everything inside "update" onto the update.zip folder we just made. Don't move the folder, move the contents.
Then put that in the sdcard, boot into clockworkmod again and try to flash update.zip
The reason I have you do all that is because it's signed. At least that's what I think is going on, because I can't edit the files from within the zip itself.
Click to expand...
Click to collapse
CWM update.zip and B&N update.zip structure is different, so by naming B&N software update "update.zip" (meant to only be booted and flashed from sdcard) wouldn't be right and i doubt it could be flashed in CWM...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
However if you want to convert a B&N update.zip to CWM update.zip you just need:
* META-INF folder
* system folder
* boot.img
* romrestore.zip
But most likely when you attempt to reboot to stock unrooted 1.4.2 you will get bootloop, so it why is better to flash rooted roms in CWM so there is no conflict between unrooted ROM and CWM custom recovery. B&N Stock unrooted 1.4.x ROMS need stock recovery
~ Veronica
lavero.burgos said:
Did you follow my instructions to the T? What errors do you get if any when flashing stock recovery or the B&N stock 1.4.2 update. zip?
If you can boot into cm7 or @meghd00t cwm recovery from sdcard all you have to do is use dd to flash stock recovery and then run the update from another sdcard.
Don't try random unbrick methods, you can make it worst, your problem is not to go and mess with advanced methods. At list yet. But if you have messed around even more since then your boot block can get damaged. Go safe first.
~ Veronica
Sent from my BNTV250A using xda premium
---------- Post added at 10:43 AM ---------- Previous post was at 10:25 AM ----------
CWM update.zip and B&N update.zip structure is different, so by naming B&N software update "update.zip" (meant to only be booted and flashed from sdcard) wouldn't be right and i doubt it could be flashed in CWM...
However if you want to convert a B&N update.zip to CWM update.zip you just need:
* META-INF folder
* system folder
* boot.img
* romrestore.zip
But most likely when you attempt to reboot to stock unrooted 1.4.2 you will get bootloop, so it why is better to flash rooted roms in CWM so there is no conflict with the custom recovery. Stock unrooted 1.4.x ROMS need stock recovery
~ Veronica
Click to expand...
Click to collapse
All it will do is replace the recovery.img and all the other files. B&N updates not only flash /system but /recovery and /bootloader too if I remember correctly.
soshite said:
All it will do is replace the recovery.img and all the other files. B&N updates not only flash /system but /recovery and /bootloader too if I remember correctly.
Click to expand...
Click to collapse
Is why nooktablet_1_4_2_update.zip needs to be flashed from sdcard as it was meant to.
~ Veronica
lavero.burgos said:
Is why nooktablet_1_4_2_update.zip needs to be flashed from sdcard as it was meant to.
~ Veronica
Click to expand...
Click to collapse
That's what I`ve been saying :3
Sent from my NookTablet using XDA
thanks, lots of helps.
I'm not alone.
(but... mm... my knowledge is poor and so Engilsh.)
I can boot with Team-B-CM7SD-Alpha_final only with SDcard.
So I can see CM7 and use CM7.
BUT I can't access PC, PC and NT do not recognise each other so I cannot modify anything.
If I try to reboot with any other method, it will be fialed.
I tried meghd00t-r4, but just can see <booti: bad boot img...>.
I will try again today.
Then I will report.
Thanks anyway.
I Really appriciate.
soshite said:
That's what I`ve been saying :3
Sent from my NookTablet using XDA
Click to expand...
Click to collapse
i dont think so 'cause you were giving other instructions: " Go ahead and unpack the 1.4.2 update into a folder, name it like "update" or something. Onto your computer by the way! Make a new zip, just call it update.zip"
---------- Post added at 12:16 PM ---------- Previous post was at 12:09 PM ----------
firstgleam said:
thanks, lots of helps.
I'm not alone.
(but... mm... my knowledge is poor and so Engilsh.)
I can boot with Team-B-CM7SD-Alpha_final only with SDcard.
So I can see CM7 and use CM7.
BUT I can't access PC, PC and NT do not recognise each other so I cannot modify anything.
If I try to reboot with any other method, it will be fialed.
I tried meghd00t-r4, but just can see <booti: bad boot img...>.
I will try again today.
Then I will report.
Thanks anyway.
I Really appriciate.
Click to expand...
Click to collapse
Alright this "BUT I can't access PC, PC and NT do not recognise each other so I cannot modify anything." needs to be fixed, you need to get adb working if you want to unbrick your device is a must now these days until @meghd00t release a new powerful tool meant to be ran from sdcard so better let's troubleshoot that first.
Boot into CM7 or CWM from sdcard and let us know where are you stuck in setting adb up. what errors or notifications do you get if any.
Oh BTW which model do you have 8GB or 16GB? that's very important
[HOW-TO] Install & Use ADB tool | Android Debug Bridge | Drivers - Videos - Tutorial
~ Veronica
lavero.burgos said:
i dont think so 'cause you were giving other instructions: " Go ahead and unpack the 1.4.2 update into a folder, name it like "update" or something. Onto your computer by the way! Make a new zip, just call it update.zip"
Click to expand...
Click to collapse
The reason I had him unzip it is because the file is signed, but he needs to opt out two lines so that it can be flashed in cwm. This is what I said:
It's the stupid script in Barnes & Noble's file. Go ahead and unpack the 1.4.2 update into a folder, name it like "update" or something. Onto your computer by the way! Make a new zip, just call it update.zip
Now, on your "update" folder, navigate over to /META-INF/com/google/android/
And edit "updater-script" with notepad or something, and delete these two lines:
assert(getprop("ro.product.device") == "blaze" ||
getprop("ro.build.product") == "blaze");
Click to expand...
Click to collapse
Sweet amirite? Save it, and then move everything inside "update" onto the update.zip folder we just made. Don't move the folder, move the contents.
Then put that in the sdcard, boot into clockworkmod again and try to flash update.zip
The reason I have you do all that is because it's signed. At least that's what I think is going on, because I can't edit the files from within the zip itself.
Click to expand...
Click to collapse
acclaim_update.zip itself can be flashed in cwm as well. You just have to edit the updater-script in its folder. For whatever reason, B&N's updater script has device set to blaze. ????
-.-
thank you, Veronica and other guys^^
I will try again.
I have to go business trip with my boss.
-.-
It will be a sort of nightmare this weekend.
See you on the next week days.
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.
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.
HI
Sorry if i am in the wrong section to post. If I am, please move to a more convenient group.
I made a custom Rom in the android kitchen. Everything went through well, no problems at all. then when I try to install to my phone, it wont install and I get these errors:
One error I got while installing was: Installation Abored: Status 6.
Now I get this error white installing: E:Cant open /sdcard/primou_signed_031613_094637.zip (bad) Installation aborted.
Whats going on because I havent changed/converted any update scripts just added an apk then zip aligned it. The original roms install ok, but my own dont install when everything is set the same.
please help me. THANKS
I can upload my two custom roms for you to have a look to see if you can make sense of it. it is for HTC ONE V gsm.
antwonpjmj said:
HI
Sorry if i am in the wrong section to post. If I am, please move to a more convenient group.
I made a custom Rom in the android kitchen. Everything went through well, no problems at all. then when I try to install to my phone, it wont install and I get these errors:
One error I got while installing was: Installation Abored: Status 6.
Now I get this error white installing: E:Cant open /sdcard/primou_signed_031613_094637.zip (bad) Installation aborted.
Whats going on because I havent changed/converted any update scripts just added an apk then zip aligned it. The original roms install ok, but my own dont install when everything is set the same.
please help me. THANKS
I can upload my two custom roms for you to have a look to see if you can make sense of it. it is for HTC ONE V gsm.
Click to expand...
Click to collapse
These are the errors cause by updater script nd update binary.!
Status 6 error in cwm is because u didn't edit ur updated script correctly
Sent from my A2 using xda app-developers app
qmobilea2 said:
These are the errors cause by updater script nd update binary.!
Status 6 error in cwm is because u didn't edit ur updated script correctly
Sent from my A2 using xda app-developers app
Click to expand...
Click to collapse
To add apk's to a rom, you can add them but do not unzip the rom, just add them to the archive, let me know how it goes
I think status 6 is when you corrupt the updater-script. What did you use to update the script? I use EditPad lite.