Hi guys, so my problem is this. After my tablet went into infinite boot I flashed my galaxy Tab 10.1 GT-P7500 with a restore ROM(ICS 4.0.4)that i had saved, but now when I try to flash CM10 throught CWM 6.0.xx I get a status 7 error.
Any one had the same problem?
Thanx!
I have download CM10 again for my device but I still get a status 7 error, anyone know how to fix this???
Thanx in advance!
drefcom said:
I have download CM10 again for my device but I still get a status 7 error, anyone know how to fix this???
Thanx in advance!
Click to expand...
Click to collapse
Flash the latest recovery from droidbasement, which is in the CM10 folder you've downloaded.
Status 7
Getting status 7 error, I am finding a lot of 'solutions' so far none have worked. Does anyone have a current solution? Using CM 10.1 on Galaxy 10.1 rooted with Clockwork Mod Recovery v4.0.0.4. Not my first ( or second root), but I'm still basically a noob.
!!! Solution for status 7 error in cwm !!!
A final solution for the status 7 problem is described below (this can be a little tricky but won't harm your device ):
1.Extract the ROM in a new folder, but remember the name of the ROM so you can repack it later for flashing...
2.Go to this address: ROM FOLDER ( the folder originally containing META-INF and system folders and boot.img)\META-INF\com\google\android\
3.open the "updater-script" file with notepad++ or another code editor...
4.the model checking assert is perhaps placed in the first line or is spread over the few first lines, and is this:
assert(getprop("ro.product.device") == "p4" || getprop("ro.build.product") == "p4");
this wicked (!) but sometimes useful model checking prevents flashing on some devices, mostly when flashing Cyanogenmod 10.1...
to tell the CWM system to omit that, you can turn it to a comment (!) by placing a "sharp" sign (#) in the beginning of the line, that will make it like this:
#assert(getprop("ro.product.device") == "p4" || getprop("ro.build.product") == "p4");
5. Happy Flashing!
sorry, I forgot: it doesn't matter if you flash a P7510 ROM on P7500, but I haven't tested it reverse (flashing P7500 ROM on P7510)...
Thanks!!!
Many, many thanks, this solution works!!
arashtarafar said:
A final solution for the status 7 problem is described below (this can be a little tricky but won't harm your device ):
1.Extract the ROM in a new folder, but remember the name of the ROM so you can repack it later for flashing...
2.Go to this address: ROM FOLDER ( the folder originally containing META-INF and system folders and boot.img)\META-INF\com\google\android\
3.open the "updater-script" file with notepad++ or another code editor...
4.the model checking assert is perhaps placed in the first line or is spread over the few first lines, and is this:
assert(getprop("ro.product.device") == "p4" || getprop("ro.build.product") == "p4");
this wicked (!) but sometimes useful model checking prevents flashing on some devices, mostly when flashing Cyanogenmod 10.1...
to tell the CWM system to omit that, you can turn it to a comment (!) by placing a "sharp" sign (#) in the beginning of the line, that will make it like this:
#assert(getprop("ro.product.device") == "p4" || getprop("ro.build.product") == "p4");
5. Happy Flashing!
sorry, I forgot: it doesn't matter if you flash a P7510 ROM on P7500, but I haven't tested it reverse (flashing P7500 ROM on P7510)...
Click to expand...
Click to collapse
Related
Twas the night.......nah that's not gonna work...
Anyways, I had just compiled froyo from android source and wanted to flash it
But apparantly I needed a specific spl when I did "fastboot flashall -w" (one of them being 0.95.0000 or whatever, too lazy to remember..but it was one that didn't support fastboot....which is dumb lol since fastboot is saying to use it)...
So I decided to install engineering spl
I had danger spl and the 2.something radio it needs
I decided to flash it from recovery
BRICK!
So really g1s are impossible to brick...if you flash radio and spls from fastboot not recovery
(Most of this knowledge is from a thread about g1s and spls and bricking that I'm too lazy to link to)
What happens is that recovery FORCES the g1 to boot to recovery on next boot...even if you press buttons
And with a mismatched radio/spl recovery will not start
So you have a brick...
Moral: use fastboot not recovery
Anyways so my solution...
I had a really messed up rogers dream that had a cracked screen and bad ribbon cables...
Pretty much everything was broken except for the motherboard...
Well I decided to try and put this rogers motherboard into my tmobile g1
It worked!
Even booted up into the rom I used to have (biffmod) on the rogers dream before it got screwed up beyond usability
I am posting from my g1 with a rogers motherboard in it as I speak...post....
Moral 2: you can mix motherboards between dreams
One problem is that this ROM still has the keymap for the rogers dream and my home and call button don't work
Hopefully flashing a new rom it will detect the tmobile keyboard
Well this was fun...but I don't know if I'm gonna try to flash my aosp froyo or not again...
Comment please on how you manage to flash a compiled aosp froyo...maybe ill try flashing engineering spl again through fastboot this time
Edit: oh and I like this motherboards vibrate more
Its quieter...
The old one rattled like crazy
So this actually a very win situation
I got Frayo back on and everythings beautiful
In a rom's zip there is this file:
META-INF\com\google\android\updater-script
Try to open it and read the first lines, there are the asserts generally (the part that tells to the device that particular SPL/Radio/Files are needed to proceed the install)
Here's an example of an assert:
assert(getprop("ro.product.device") == "trout" || getprop("ro.build.product") == "trout" || getprop("ro.product.board") == "trout" ||
getprop("ro.product.device") == "sapphire" || getprop("ro.build.product") == "sapphire" || getprop("ro.product.board") == "sapphire");
assert(getprop("ro.bootloader") == "1.33.0013" ||
getprop("ro.bootloader") == "1.33.2013" ||
getprop("ro.bootloader") == "1.33.3013" ||
getprop("ro.bootloader") == "1.33.0013d");
This assert checks many things, with logical operators (|| that's or; == that's equal; "" that's a string; () that's an argument; etc). If you've ever programmed, you'll understand very fast how to change the assert to make it less agressive of checking this things and anothers and not let you install.
The previous assert cheched that the device, or product, ot board where "trout" or "sapphire". Also it needs an specific bootloader ("1.33.0013", or "1.33.2013", or"1.33.3013", or "1.33.0013d").
It's an good idea tho check the updater-script that's in your zip installation file, view what installs it, add/remove asserts and unwanted things, and then, proceed to install it safely from recovery and the SPL/Radio combo that you prefer. Also, it's an good idea to flash an alternative kernel (ezterry one's are very good).
Remember that the only thing that's really recommended to install from fastboot is the SPL and the Radio. Other things are installable from wherever you want (fastboot, OS, recovery) without an potential hard brick risk.
So, if you want to install an ROM (AOSP FroYo as you described), it's not needed to install it from fastboot, and it will not represent an brick risk if it really is only a ROM installer what you have.
---------- Post added at 06:16 PM ---------- Previous post was at 06:12 PM ----------
Oh, and if you can paste here the updater-script it would be usefull, more than one buddy will say you how to change it to let you install everithing by a correct and safe way.
Yes yes I know all of that
I'm using fastboot because the compiled output is not an update.zip
Its all the image files and I am supposed to do "fastboot flashall"
Its alright though...I got cm6 source working
That will work
Sent from my HTC Dream using Tapatalk
It should be also fun to convert your images to a zip format.
When you flash those full images, you don't know if it will flash more things than needed. Zip files give you more control, and the updater-script also.
The "fastboot flashall" command is kinda risky with images that touchs radio/spl/partitions layouts/etc. It's really recommended to do a wipe of everithing from fastboot when you're installing this images, and also, of course, know what those images will install and be carefull to have the right pre-requisites to don't harm the device.
Good to know you got it working after all !
Alright maybe putting images into zips will be an adventure for later
As of now, the AOSP froyo source and built images are in the deep dark room of a PC's deleted files
Thanks for the tip about flashall!
frankdrey said:
Alright maybe putting images into zips will be an adventure for later
As of now, the AOSP froyo source and built images are in the deep dark room of a PC's deleted files
Thanks for the tip about flashall!
Click to expand...
Click to collapse
No need for flashall
instead of using
Code:
make
use
Code:
make otapackage
You will find a zip ready for flashing
if you are building cm6 then use
Code:
squisher
to optimise the zip
have a look in the opticharger script to make improvements like replacing pngcrush with something better
Scrip said:
No need for flashall
instead of using
Code:
make
use
Code:
make otapackage
You will find a zip ready for flashing
if you are building cm6 then use
Code:
squisher
to optimise the zip
have a look in the opticharger script to make improvements like replacing pngcrush with something better
Click to expand...
Click to collapse
Thanks
And here I was about to go and start extracting the images and writing an updater-script
And I went back to AOSP
CM6 has too many missing files that I don't want to go through the trouble of finding
frankdrey said:
...And here I was about to go and start extracting the images and writing an updater-script...
Click to expand...
Click to collapse
OTA packaging is easier and more simple, I agree... but something is true... fighting with those extractions and updater-script is kinda funnier
Happy source-compiling
Alright I have the zip and all
It checks for the spls though
Should I just remove that from the script?
And try with DangerSPL?
DangerSPL is a port of the mytouch spl right?
Maybe I shoulda built for mytouch?
Also, it looks like it patches recovery after install.
Is that safe? Should I remove the entire folder and entry in the update script?
You must do a little change.
First, open the updater-script, then find the bootloader assert
It will be like this:
assert(getprop("ro.bootloader") == "1.33.0013" ||
getprop("ro.bootloader") == "1.33.2013" ||
getprop("ro.bootloader") == "1.33.3013" ||
getprop("ro.bootloader") == "1.33.0013d");
Just be shure to add the SPL version that you've installed on your phone already. For example, if I've a 1.33.2222 bootloader, then the change will be this:
assert(getprop("ro.bootloader") == "1.33.0013" ||
getprop("ro.bootloader") == "1.33.2013" ||
getprop("ro.bootloader") == "1.33.3013" ||
getprop("ro.bootloader") == "1.33.2222" ||
getprop("ro.bootloader") == "1.33.0013d");
It doesn't matter if you put the new bootloader assert on the beginning or at last or in the middle, it'll be the same. Also, you can delete some asserts if you want to. Be carefull to keep right the sintax.
And the recovery thing, it's better to delete that part, zip will give less troubles whithout that part. And better to delete it from the script and the zip!
I recommend you to use the 1.33.0013d SPL, it'll give you extra RAM and is fully compatible with AOSP FroYo. Just be shure that after flashing the ROM, you flash the right kernel to let the OS boot up.
And remember, if you use Amon_RA recovery, you'll need to re-sign the zip that you modify, if you don't do it, the verification part of the flashing will fail.
Ok thanks I thought all of that too, just wanted to make sure
Oh, and I forgot it...
DON'T edit the script with notepad on windows, it leaves an "Error 6" in recovery when flashing.
In windows you can use notepad++ (google it, it's free), or if you're using other text editor just be shure that the "Enter" (new line in text) key is on right encoding, it's kinda of Unicode if I've good memory yet
mishamosher said:
Oh, and I forgot it...
DON'T edit the script with notepad on windows, it leaves an "Error 6" in recovery when flashing.
In windows you can use notepad++ (google it, it's free), or if you're using other text editor just be shure that the "Enter" (new line in text) key is on right encoding, it's kinda of Unicode if I've good memory yet
Click to expand...
Click to collapse
Yes I have edited them before
recovery，
assert failed : getprop ("ro.product.device") == "p4" || getprop("rp.build.product") == "p4" E:Error in /sdcard/cm-10-20120814-EXPERIMENTAL-P4.zip (status 7) installetion aborted .
why ？
crazyflower said:
View attachment 1265106 the right one ,can be successed by recovery , but left one failed...why? pls help me , thx!~~~~~:crying:
and the left i downloaded here : droid basement ,
Click to expand...
Click to collapse
You're not likely to get much help when you couldn't be bothered to type a complete sentence let alone an actual explanation of your issue. The people here are enormously helpful but they aren't mind readers.
Either flash CWM 5.5.0.0 (through ODIN) or if you go into meta inf and look for the updater script and open it with some notepad program and delete the first line and move the rest of the text up
Sent from my Nexus S using xda premium
Agreed. Use the recommended recovery. You're trying to flash CM10...the same droidbasement site where you download the build will contain the recovery you should use. Odin that first, take a backup, wipe, then flash the latest build + GApps.
If that doesn't help you should do a little bit more reading before you get too brave Good luck!
Hello people,
I got a big problem with my tablet.... so.... I use Rom Manager to do the upgrade....
In Rom Manager:
- Download ROM
- CyanogenMod Nightlies
- CyanogenMod 10 20121202
That's all ok... but now i have a P7510 without 3G....
So i go to the clockworkmod folder and i see... the flashed image to my tablet is "cm-10-20121202-Nightly-p4wifi.zip" so... i loose my 3G and in the present moment i can't connect the tablet to the computer... It is simply not recognized.
After this... i go to our friend google... and i find the (Correct ROM ( I Hope ) )....cm-10-20121202-Nightly-p4.zip, but.... when i try to flash this rom... i got this error:
assert failed getprop( ro.product.device ) == p4 getprop( ro.build.product ) == p4
status 7 error
Well ..
So my request is ... can someone help me put the correct ROM on my tablet and get back to 3G and USB?
Thank's a lot!!
Ps--> I forgot to say... i don't have my stock rom backup
mrbouli said:
After this... i go to our friend google... and i find the (Correct ROM ( I Hope ) )....cm-10-20121202-Nightly-p4.zip, but.... when i try to flash this rom... i got this error:
assert failed getprop( ro.product.device ) == p4 getprop( ro.build.product ) == p4
status 7 error
Click to expand...
Click to collapse
Unpack the zip file somewhere, keeping the directory tree intact.
In the folder META-INF\com\google\android, there's a file called "updater-script". Open that with a text editor (but NOT MS Word!! - I use notepad++ on Windows.)
You should see a pair of lines reading:
assert(getprop("ro.product.device") == "p4" ||
getprop("ro.build.product") == "p4");
Or maybe just one line:
assert(getprop("ro.product.device") == "p4" || getprop("ro.build.product") == "p4");
Either way, disable that by inserting "#" at the beginning:
#assert(getprop("ro.product.device") == "p4" ||
# getprop("ro.build.product") == "p4");
Save the new file, rebuild the zip, and it should install fine.
Before ... thanks for your help!
I did what you told me ... I put the # in front of the two lines and looked like this:
#assert(getprop("ro.product.device") == "p4" ||
#getprop("ro.build.product") == "p4");
( I use WordPad to edit the file )
Now I try to install the ROM and now I have another error .... :
E:Error in /sdcard/xxcm-10-20121202-NIGHTLY-p4.zip
(Status 6)
Installation aborted.
k1mu said:
Unpack the zip file somewhere, keeping the directory tree intact.
In the folder META-INF\com\google\android, there's a file called "updater-script". Open that with a text editor (but NOT MS Word!! - I use notepad++ on Windows.)
You should see a pair of lines reading:
assert(getprop("ro.product.device") == "p4" ||
getprop("ro.build.product") == "p4");
Or maybe just one line:
assert(getprop("ro.product.device") == "p4" || getprop("ro.build.product") == "p4");
Either way, disable that by inserting "#" at the beginning:
#assert(getprop("ro.product.device") == "p4" ||
# getprop("ro.build.product") == "p4");
Save the new file, rebuild the zip, and it should install fine.
Click to expand...
Click to collapse
Do not use wordpad. Í suggest downloading notepad++, it's available as standalone (no install required) and doesn't break linux compatible line endings.
Sent from my GT-P7510 using xda app-developers app
Thk's my friend!!!
Tablet 100% working with 3g and wi-fi.
Real a show this rom!!!
Obrigado!!!
Only one question more....
Now i connect the tablet to the computer... but don't works...
Have u any ideia???
If i put in developer mode.... the computer makes a sound... but don't recognize in windows nothing....
Can u help me??
Thk's in advance...
use usb connection settings
mrbouli said:
Only one question more....
Now i connect the tablet to the computer... but don't works...
Have u any ideia???
If i put in developer mode.... the computer makes a sound... but don't recognize in windows nothing....
Can u help me??
Thk's in advance...
Click to expand...
Click to collapse
go to settings, storage and on top right corner you will have usb connection.. click that and check the MTP checkbox... then connect to pc and check.... If it didnt work first time, try unplugging and connecting the cable couple of times...
mrbouli said:
Only one question more....
Now i connect the tablet to the computer... but don't works...
Have u any ideia???
If i put in developer mode.... the computer makes a sound... but don't recognize in windows nothing....
Can u help me??
Thk's in advance...
Click to expand...
Click to collapse
Make sure you're using a Samsung USB cable.
I just spent two days messing around trying to find out why I kept getting failures when plugging a tab into my PC. Cheapo cable doesn't work, but the OEM one does.
Yes it's the original cable of samsung... and i can't connect to the computer
ycharan said:
go to settings, storage and on top right corner you will have usb connection.. click that and check the MTP checkbox... then connect to pc and check.... If it didnt work first time, try unplugging and connecting the cable couple of times...
Click to expand...
Click to collapse
this works! flashed CM10 nightly, then went to Storage and selected MTP, and i rebooted the tablet just in case.
tablet was recognised in Win7
It seems to me that you have a recovery that is for the p4wifi instead of p4. I suggest flashing a recovery for the p4 (like the one here), so that you wont have to deal with this again in the future.
Hello i have a xiaomi redmi note 1w device .i had allready root it and instal twpr recovery
last night i try to flash the new beta rom from the 3g but i get error
can u please advice redmi note 1w is diferent from 3g?
demomi said:
Hello i have a xiaomi redmi note 1w device .i had allready root it and instal twpr recovery
last night i try to flash the new beta rom from the 3g but i get error
can u please advice redmi note 1w is diferent from 3g?
Click to expand...
Click to collapse
i receive a msg that this package is is for 'lcsh_wet_jb9" devices.this is a 'minote'
can u please help
check in the following path of the ROM..... META-INF\com\google\android\
in updater-script
and delete lines similar with below example:
assert(getprop("ro.product.device") == "sample" ||
getprop("ro.build.product") == "sample" ||
abort("This package is for device: samplex; this device is " + getprop("ro.product.device") + ".");
Be careful because if the package is not intended for your device you may BRICK YOUR DEVICE!!!
I think your device is "lcsh92_wet_jb9"
resofty said:
check in the following path of the ROM..... META-INF\com\google\android\
in updater-script
and delete lines similar with below example:
assert(getprop("ro.product.device") == "sample" ||
getprop("ro.build.product") == "sample" ||
abort("This package is for device: samplex; this device is " + getprop("ro.product.device") + ".");
Be careful because if the package is not intended for your device you may BRICK YOUR DEVICE!!!
I think your device is "lcsh92_wet_jb9"
Click to expand...
Click to collapse
check in the following path of the ROM..... META-INF\com\google\android\
in updater-script
can u please advice how to find these and where?
You have to be more precise. Copy the EXACT error so we can help you.
The solution resofty posted helps only if you are trying to install a ROM not intended for your device, which is moreover a WRONG and BAD thing to do.
Probably the problem is another. Copy TWRP output here.
Ok guys,, been a long time since ive updated my vs995, an old old version of resurection remix back in the day. I remember there was a fix for it, i think it was the meta tag or something back in the day was wrong and id have to change it or something... It wont let me flash anything vs995..
Any suggestions on how to correct it? Thanks
Try updating your twrp. Here is my latest vs995 build (thread is here). Basically I suspect you're running one of the old "Elsa" twrp builds when what you're trying to flash may have stopped checking for it. This is all is if you're getting an error like "E3004: This package is for device: vs995; this device is elsa". It can be manually bypassed by deleting a line like
Code:
assert(getprop("ro.product.device") == "vs995" || getprop("ro.build.product") == "vs995" || abort("E3004: This package is for device: vs995; this device is " + getprop("ro.product.device") + "."););
in the updater-script file a few folders deep in the meta-inf folder of the zip.
Did you happen to download these roms with chrome on your phone? Chrome won't download them correctly because it thinks it's a harmful file. On the PC version you can choice to download anyway. On the Android version I haven't figured out how to do that yet.