Database Users

Frankdrey's Brick Adventure

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

ICS Upgrade Errors

I'm having some trouble doing the ICS update, but my issues seem to be different then others are listing.
If I download ThinkPadTablet_A400_03_0069_0130_US.zip and isntall from the sd card, I get the following:
assert failed: file_getprop("/system/build.prop", "ro.build.fingerprint") == "Lenovo/ThinkPadTablet/Indigo:4.0.3/ThinkPadTablet_A400_03/0065_0128_US:user/release-keys" || file_getprop("/system/build.prop", "ro.build.fingerprint") == "Lenovo/ThinkPadTablet/Indigo:4.0.3/ThinkPadTablet_A400_03/0065_0128_US:user/release-keys"
E:Error in /tmp/sideload/package.zip
(Status 7)
Click to expand...
Click to collapse
If I simply use the OTA update I get the following error:
assert failed: apply_patch_check("/system/usr/keylayout/Generic.k1", "9b32bfe46c1a856cd23659c65321ca0daee319", "bc62670ffade18f522a28489c09d75488872a992")
E:Error in /cache/update.zip
(Status 7)
Click to expand...
Click to collapse
Ok, so where do I go from here?
Thanks so much!
-JRW

you have 2 choices:
1) restore your original Generic.k1 and flash with the OTA update
2) modify the update script to skip the build.prop check and the generic.k1 check and flash with CWR

i9001
I have a very similar problem relating to paranoidandroid rom (ICS) that i tried to install. I get the same error. Can you tell what to do as i don't quite get the solution posted here as the device is different.
and thanks as i will use the quote from the guys earlier problem error report in other threads as at the time i was too frustrated and scared at the same time to type it down from my phone

Thanks for the quick reply...
1) How do I do that?
2) Where do I find the upgrade script? I think I know how to comment out the offending item.
Thanks,
-JRW

JRW-910 said:
Thanks for the quick reply...
1) How do I do that?
2) Where do I find the upgrade script? I think I know how to comment out the offending item.
Thanks,
-JRW
Click to expand...
Click to collapse
2) You already have it.
Additional info here, just in case
http://forum.xda-developers.com/showthread.php?t=1740114

toenail_flicker said:
2) You already have it.
Additional info here, just in case
http://forum.xda-developers.com/showthread.php?t=1740114
Click to expand...
Click to collapse
That's a link to this thread...
-JRW

JRW-910 said:
I'm having some trouble doing the ICS update, but my issues seem to be different then others are listing.
If I download ThinkPadTablet_A400_03_0069_0130_US.zip and isntall from the sd card, I get the following:
If I simply use the OTA update I get the following error:
Ok, so where do I go from here?
Thanks so much!
-JRW
Click to expand...
Click to collapse
Ditto here - except I am getting a FlexT9ChineseIME.apk error with the OTA. (Even though I've installed the FlexT9Chinese FROM the Lenovo App Store.)

JRW-910 said:
Thanks for the quick reply...
1) How do I do that?
2) Where do I find the upgrade script? I think I know how to comment out the offending item.
Thanks,
-JRW
Click to expand...
Click to collapse
uncompress the zip and search for "update"

CM10 ROM flash error (status 7) galaxy tab 10.1!!!!!

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

[Q] Lenovo Stock Firmware won't setup with fail on assertion

Sorry for the links, but I'm new user, so I can't post outside links.
I'm trying to install firmware (download(.)lenovo(.)com/slates/think/tablet1/ThinkPadTablet_A310_03_0069_0121_ROW.zip) from lenovo firmware list (download(.)lenovo(.)com/slates/think/tablet1/) on my Thinkpad Tablet 16Gb 3G.
Firstly, when I just tried to use it as backup (CWM) it fails just saying "md5 mismatch". I think it was fully wrong way.
Then, I tried to install it from "install zip from sdcard" CWM command. It fails with this output:
-- Installing: /sdcard/update.zip
Finding update package...
Opening update package...
Installing update...
assert failed: file_getprop("/system/build.prop", "ro.build.fingerprint") == "Lenovo/ThinkPadTablet/Indigo:3.1/ThinkPadTablet_A310_02/0039_0089_ROW:user/release-keys" || file_getprop("/system/build.prop", "ro.build.fingerprint") == "Lenovo/ThinkPadTablet/Indigo:4.0.3/ThinkPadTablet_A400_03/0069_0121_ROW:user/release-keys"
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted
Click to expand...
Click to collapse
Then, I understand that in zip I downloaded there was no /system/build.prop. I found some version of this file, but for US and changed all occurences of US to ROW. That's what I've got: paste(.)ubuntu(.)com/1676846/. It concains this string:
ro.build.fingerprint=Lenovo/ThinkPadTablet/Indigo:3.1/ThinkPadTablet_A310_02/0039_0089_ROW:user/release-keys
Click to expand...
Click to collapse
But now I get the same error as when there was no build.prop at all.
What have I to do?
Thank you, Dmitry.

Hi,
firmware updates should come OverTheAir, not by downloading something.
There is an option in Settings->About where you can check for updates.
Maybe this ROM doesn't match your tablet or current ROM (if it's just a partial update).
If you're absolutely sure that this ROM matches your current configuration (and ONLY then):
I think the problem isn't in the zip, but on your tablet.
The assertions are in the zip and check for the target system.
This should prevent you from accidentally installing the wrong ROM.
So check your tablet's /system/build.prop
If you force the update by editing your build.prop, you may brick it!!!
Micky

[Q] Help Root Galaxy Y GT-S5369

Hi Guys
My head is wrecked trying to root my S5369. i've downloaded so many Update.zip's but they all aborted installation.
i tried the multi root installer. I changed the script in updater and the installer runs and says that the phone is rooted but when I rebbot i dont have super user and if I run root checker it says I'm not rooted.
Maybe I'm not changing the script correctly
Post #77
Valid for GT-S5369 with modifications:
getprop("ro.product.device") == "GT-S6102"
change for this:
getprop("ro.product.device") == "GT-S5369" ||
getprop("ro.product.device") == "GT-S6102"
Click to expand...
Click to collapse
This is what the original script looks like
assert(getprop("ro.product.device") == "GT-S6102" ||
getprop("ro.build.product") == "GT-S5360"
Click to expand...
Click to collapse
is it just one line I change or two lines ?
please some one help I've spent hours rebooting and updating
Thanks

this is what I changed it to
assert(getprop("ro.product.device") == "GT-S5369" ||
getprop("ro.build.product") == "GT-S6102"
Click to expand...
Click to collapse
to change it I do the following
open the zip file
extract the updater-script file
open updater-script in wordpad and then make and save changes as above
then i open the zip file in winrar and navigate to the folder containing the updater script file - i right click and select "add file to archive " - then add the modified script file.....this overwrites the original script file
Is this correct way of doing things ?

multi root .. not working also in S5360B

You're supposed to Flash the update.zip of gt-s5369
Not any other update.zip
Or you could just flash a custom rom which is pre rooted
sent from my katana

Thanks for your reply DS
the only update.zip I could find are for GT-S5360
anychance you could point me in the direction of the correct zip file or custom ROM ?
Oh... I thought if I flashed it with another ROm without rooting it would return to the stock rom on next reboot ?

and ifampe
I cant believe it... I finally got it roted
I used this htt p search.4shared.com/postDownload/7i2UwaPp/universal_gingerbread.html[/url]
I had to extract the universal_gb_root_v25.zip from the universal gingerbread.rar before i could see it on the sd card when applying the update
now that I've root acces what should I do first ???
link2sd card to give more space .... then what????

typhoonsteve said:
I cant believe it... I finally got it roted
I used this htt p search.4shared.com/postDownload/7i2UwaPp/universal_gingerbread.html[/url]
I had to extract the universal_gb_root_v25.zip from the universal gingerbread.rar before i could see it on the sd card when applying the update
now that I've root acces what should I do first ???
link2sd card to give more space .... then what????
Click to expand...
Click to collapse
You can get adaway and remove ads
And if you like gaming, chainfire3d, which will help you play some hd games
sent from my katana
---------- Post added at 05:51 PM ---------- Previous post was at 05:50 PM ----------
Adaway isn't in the market
You have to google it
Chainfire3d is in the market
sent from my katana

Godddddddamn it !!
i tried putting the Hyperion ROM on it an bricked it.... it just boots to Galaxy Y logo
currently in the middle of D/Ling stock rom... gonna try use odin to reflash it. I always make a balls of these things
fingers crossed

typhoonsteve said:
Godddddddamn it !!
i tried putting the Hyperion ROM on it an bricked it.... it just boots to Galaxy Y logo
currently in the middle of D/Ling stock rom... gonna try use odin to reflash it. I always make a balls of these things
fingers crossed
Click to expand...
Click to collapse
You remembered to wipe data and cache right
sent from my Katana

darkshadow246 said:
You remembered to wipe data and cache right
sent from my Katana
Click to expand...
Click to collapse
yeah I did that... may have forgot about mounting sdcard
I manage to get it going again...slowest part was waiting for/and downloading files from hotfile
anyway.... managed to flash it with Jellyblast
now to start building my apps . before I bricked it i managed to get Fifa 10 to work ...using chainfire3d
When browsing websites i cant watch gifs.... do i need to do anythig to get these to work ?

root file
typhoonsteve said:
I cant believe it... I finally got it roted
I used this htt p search.4shared.com/postDownload/7i2UwaPp/universal_gingerbread.html[/url]
I had to extract the universal_gb_root_v25.zip from the universal gingerbread.rar before i could see it on the sd card when applying the update
now that I've root acces what should I do first ???
link2sd card to give more space .... then what????
Click to expand...
Click to collapse
could u send me a copy of that root file please