Today I decided to make my first ROM. I decided to make it stock based with some of the apks from the leaked JB update that DoomLord released.
However, I am facing two problems:
-After uninstalling bloatware and doing a factory reset, my bloatware reappears.
-On every boot the "Android is upgrading: Optimizing applications"- As if the dalvik cache was being cleared on every boot.
xL3thalTuRdZz said:
Today I decided to make my first ROM. I decided to make it stock based with some of the apks from the leaked JB update that DoomLord released.
However, I am facing two problems:
-After uninstalling bloatware and doing a factory reset, my bloatware reappears.
-On every boot the "Android is upgrading: Optimizing applications"- As if the dalvik cache was being cleared on every boot.
Click to expand...
Click to collapse
don't know for bloatware but for dalvik cache , have you put some init.d tweak for dalvikcache in your rom?
vinss68 said:
don't know for bloatware but for dalvik cache , have you put some init.d tweak for dalvikcache in your rom?
Click to expand...
Click to collapse
No. It has happened to me several times in the past, sometimes the problem resolves itself. After doing some research, other people are saying it has something to do with Titanium Backup, for me this is not the case; I don't use Titanium Backup.
How are you making your ROM? and what are you using as your base?
gregbradley said:
How are you making your ROM? and what are you using as your base?
Click to expand...
Click to collapse
I'm just replacing things and doing several, small tweaks, then converting the backup to a zip.
I'm using Sony's .195 firmware as my base.
with dsixda's kitchen?
Right. I'm going to reflash the stock firmware, re-install everything required for dsixda's kitchen. Perhaps something just went wrong somewhere. I'll post my findings.
xL3thalTuRdZz said:
I'm just replacing things and doing several, small tweaks, then converting the backup to a zip.
I'm using Sony's .195 firmware as my base.
Click to expand...
Click to collapse
How are you converting the ftf to a zip and how are you extracting the /system fro the ftf.
Furthermore, you wil probably have to deodex the system if you are messing about with it, that will be why you keep getting the dalvik error and app optimisation errors
gregbradley said:
How are you converting the ftf to a zip and how are you extracting the /system fro the ftf.
Furthermore, you wil probably have to deodex the system if you are messing about with it, that will be why you keep getting the dalvik error and app optimisation errors
Click to expand...
Click to collapse
It appears I wasn't clear enough for others to understand me: I was converting a CWM backup to a zip, not the ftf.
I did deodex the system, however I think something may have went wrong in the process.
xL3thalTuRdZz said:
It appears I wasn't clear enough for others to understand me: I was converting a CWM backup to a zip, not the ftf.
I did deodex the system, however I think something may have went wrong in the process.
Click to expand...
Click to collapse
OK, I see. Its probably a lot easier to use the kitchen to make the .zip. Also, remember not to share the .zip you make from the backup unless you remove all your personal data from the backup.
Let us know how you get on.
I have been told that I must sleep at my grandma's house. So I wont be able to try anything until tomorrow. (She doesn't have broadband)
I guess I'll try then and tell you of my findings.
Also for the reappearing bloat ware, I remember from x10 days that there are apps in a 'customization folder somewhere in system, this might help
If you remove them from there as well then they will not reappear on boot.
Sent from my LT30p using xda app-developers app
/System/etc/customization
Also check /vendor for /etc/customization
You'll see the apk there.
Sent from my LT30p using xda app-developers app
Another problem has appeared. When I try to flash my ROM zip the following is shown:
Finding update package...
Opening update package...
Installing update...
mount() expects 4 args, got 5
E: Error in /external_sd/LT30p-TuRdZzROM-7.0.A.3.195.zip
(Status 7)
Installation aborted
Tried searching for info, but none were relevant enough.
xL3thalTuRdZz said:
Another problem has appeared. When I try to flash my ROM zip the following is shown:
Finding update package...
Opening update package...
Installing update...
mount() expects 4 args, got 5
E: Error in /external_sd/LT30p-TuRdZzROM-7.0.A.3.195.zip
(Status 7)
Installation aborted
Tried searching for info, but none were relevant enough.
Click to expand...
Click to collapse
It seems your updater script file in the META-INF folder is wrong.
Can you upload it so I can check it?
gregbradley said:
It seems your updater script file in the META-INF folder is wrong.
Can you upload it so I can check it?
Click to expand...
Click to collapse
Sure.
Here you go!
xL3thalTuRdZz said:
Sure.
Here you go!
Click to expand...
Click to collapse
wow, lots of extra lines in there...
Try downloading my rom (Or any other stock based rom) and use that updater script as base. You may have to change some things (Like in mine i have ui-print"..." commands that you will have to delete) but give one of those ago and let me know if that works.
I would upload mine, but its on my other machine, sorry...
xL3thalTuRdZz said:
Another problem has appeared. When I try to flash my ROM zip the following is shown:
Finding update package...
Opening update package...
Installing update...
mount() expects 4 args, got 5
E: Error in /external_sd/LT30p-TuRdZzROM-7.0.A.3.195.zip
(Status 7)
Installation aborted
Tried searching for info, but none were relevant enough.
Click to expand...
Click to collapse
Lol
format("ext4", "EMMC", "/dev/block/mmcblk0p12", "0");
mount("ext4", "EMMC", "/dev/block/mmcblk0p12", "0", "???");
Take the "????" Away
That's the fifth argument mount is complaining about.
Though if I was you I would download a known working one and "borrow" the mount commands, the rest appears sound
Sent from my LT30p using xda app-developers app
mpiekp said:
Lol
format("ext4", "EMMC", "/dev/block/mmcblk0p12", "0");
mount("ext4", "EMMC", "/dev/block/mmcblk0p12", "0", "???");
Take the "????" Away
That's the fifth argument mount is complaining about.
Though if I was you I would download a known working one and "borrow" the mount commands, the rest appears sound
Sent from my LT30p using xda app-developers app
Click to expand...
Click to collapse
Really? That's it? I thought that the "???" was strange but I didn't think removing that alone would solve my issue.
I'll inform you if it works.
Have yet to make anything for t yet, it's only a week old, so haven't checked the mount points but the error is for the number of arguments passed to mount.
Sent from my LT30p using xda app-developers app
Related
I'm sure this question has been answered before, but I can't find it anywhere, so here goes:
I always thought that whenever a ROM is installed it completly wipes and overwrites the /system partition. But perhaps I figure wrong, maybe the files/folders within /system are overwritten and any other pre-existing files are left behind.
Which is it?
I ask this because I notice that the size of /sytem in an update.zip varies from one ROM to another, this suggests to me that perhaps files can be left behind when a ROM is installed. Also I'm curious why it's sometimes possible to upgrade a rom without a wipe and sometimes it isn't.
It depends on how the ROM is set up to install...
Basically, a flashable zip is just a bunch of files and a script that installs the package. If the script also has instructions to erase files or directories, then it will...
Sent from my Nexus One using XDA App
it depends on what you are doing. if i flash a full ROM to my phone, it will just upgrade everything as if it were a real OTA from google, meaning it keeps every thing in tact. if i wipe the phone first, of course it re-writes everything. so it's a tough question to answer.
Thanks danger-rat, perfect explanation.
It's quite interesting that we rely on the ROM-dev to wipe whatever is necessary (as a manual wipe from Recovery-mode does not wipe /system). So I guess it's possible to install a new ROM and be left with bits of the old one still in /system if the ROM-dev didn't specifiy a format of /system.
danger-rat said:
It depends on how the ROM is set up to install...
Basically, a flashable zip is just a bunch of files and a script that installs the package. If the script also has instructions to erase files or directories, then it will...
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Hello my fellow Android crack flashers! So Volk and I have wrote(him) and tested(me) his g2x nullifier for our phones. Well it works flawlessly! Which his thread is here. So with our learning adventures he has helped me port it to the O2x. So here is the run down. This was originally created as the g2xscrubber was insufficient enough for our flashberry addiction, and on top of that if wouldn't wipe our /cache either.
So the domino effect has begun. This is a simple script that will wipe your internal partitions cleaner then a whistle and get it dam near like new status, perfectly ready for a ROM. Like as if you just purchased it and didnt have any data on it nor a ROM and needed to be flashed. And yes it came all tricked out like that with CWM and all.. haha
So here it is...
The O2x Nullifier
This uses a special command in combination with a special file to overwrite the internal partitions with 0's, hence "Null" for 0 and "-ifier" for the fact that it does something. It also formats the partitions afterward, including /cache too! Enjoy!
Some brief need to knows:
1. This is a little lengthy process so please bear with it. The longest wipe is on /data which will take about 7 minutes. Obviously, make sure you have plenty of battery life before running it. I've ran this Nullifier like 20 times in the last two days of first testing and on average its about 1204 seconds or about 19.8 minutes, on average. The Single pass zip is only half of the time of course. Or you can just watch the progress bar. After 20 times of nullifing and log pulling in 2 days, im pretty dang sure the bar is accurate. So enjoy!
2. ONCE THE NULLIFICATION PROCESS HAS BEEN COMPLETED DO NOT, I REPEAT, DO NOT TURN OFF OR LET YOUR PHONE DIE BEFORE FLASHING A ROM OR RESTORING... or you will brick your phone.
3. I will provide help, support, etc. for this, but as always flash at your own risk and I am not responsible if you turn your phone into your next non-aerodynamic frisby.
Enjoy!
Also I have now decided to copy the log to sdcard at completion (thanks to DARKSIDE for the idea). But from now on the log created in /tmp while in cwm is now copied to sdcard as O2x-Nullified-recovery.log. So it will still be deleted from RAM but never lost any more!!!!! muhahahahahahah... love it!
Thanks go to Волк aka Volk for letting me test and learn from his G2x Nullifier script. And also to owain94 for helping me make sure that this thing will run ok on the O2x, since I dont actually have the O2x..
Also if is doesn't work, please we need logs. You need to use a file explorer or put the external sdcard into your pc and grab and upload or pm me the log from your sdcard the file will be named 'O2x-Nullified-recovery.log'
mini change log:
1.2 -> fixed sleep command, 1.2
1.3 -> updated binary script and added /cache info per vadonka's advice
1.3.1 -> Bad zip... reupped
1.3.2 -> zipped with 7zip should work now.. dumb winzip... reupped
skipped to 1.5 -> updated script and binary. Also removed /cache format command; instead do a manual wipe for now
skipped to 2.0 -> updated script and binary again. Manual format still.
2.1 -> No more manual /cache wipe and working progress bar!
2.2 -> Single/Dual pass zip options. Thanks to Volk for error check and darkside for log creation idea. Added support for su660
nice work mate!
Ok so i'm hijacking this post to use while i'm at work (with crappy lowest bid PC) and using this FOR MY TEST UPLOADS ONLY. THIS WILL CONSIST OF G2X TESTS GETTING READY FOR THE O2X... DO NOT DOWNLOAD ANY ATTACHMENT ON THIS POST OR ATTEMPT TO FLASH IT BECAUSE IT WONT WORK FOR YOU UNLESS YOU HAVE A G2X!
Thanks a lot mate
da-pharoah said:
This was originally created as the g2xscrubber was not sufficent enough for our flashberry addiction.
Click to expand...
Click to collapse
Remember to read first, if your question hasn't already been asked or answered, ask and maybe you'll get it posted in the Q&A post.
Pharoh, what did you fix I see nothing wrong.
>.>
carburano said:
Thanks a lot mate
Click to expand...
Click to collapse
No worries
Волк said:
Remember to read first, if your question hasn't already been asked or answered, ask and maybe you'll get it posted in the Q&A post.
Pharoh, what did you fix I see nothing wrong.
>.>.
Click to expand...
Click to collapse
lol nice catch.. was in a hurry to leave from work. Fixed now.
Hi friend...
just tried but it's not working... E: Can't Open /sdcard/O2x Nullifier beta 1.zip (bad) Installation Aborted...
Interesting, there will be a log in cache/Recovery can you send it to one of us and we can have a look. It may have not been zipped correctly. Or heck, I'll dl it right quick and have a look.
Ah, it's not signed. One sec.
new link.
http://db.tt/YeuzWktM
Error status 6...
Did you made the updater script in Linux, mac or windows?
If Mac or windows what text editor did you use?
Did you ever edited the updater script if yes what text editor did you use?
Sent from my LG-P990 using xda premium
owain94 said:
Error status 6...
Did you made the updater script in Linux, mac or windows?
If Mac or windows what text editor did you use?
Did you ever edited the updater script if yes what text editor did you use?
Sent from my LG-P990 using xda premium
Click to expand...
Click to collapse
used win7 and notepad++
error with op link or updated link by Волк?
carburano said:
Hi friend...
just tried but it's not working... E: Can't Open /sdcard/O2x Nullifier beta 1.zip (bad) Installation Aborted...
Click to expand...
Click to collapse
Волк said:
Interesting, there will be a log in cache/Recovery can you send it to one of us and we can have a look. It may have not been zipped correctly. Or heck, I'll dl it right quick and have a look.
Ah, it's not signed. One sec.
new link.
http://db.tt/YeuzWktM
Click to expand...
Click to collapse
OP updated thanks again Волк!
Why not just use the nvflash based v10b flashing released by Paul on modaco. I use that when I really want to clean everything up. Since it is V10b, easy to install CWM recovery using psneuter (thought it is not required) and can be done with a simple dd command directly.
hackworks said:
Why not just use the nvflash based v10b flashing released by Paul on modaco. I use that when I really want to clean everything up. Since it is V10b, easy to install CWM recovery using psneuter (thought it is not required) and can be done with a simple dd command directly.
Click to expand...
Click to collapse
Well really thats kind of a longer process.. thats a rom, this is just a tool to wipe clean your internal storage. Basically take it back to like new status, but still having full root ability. CWM will flash the rom of your choice after your done with the nullification process and manual /cache wipe. This will not take you back to a predetermined state (in terms of a rom), it will leave your phone a nice paper weight however until you decide to flash a rom.
nice work!
i have a little advice for you. use this method for the cache wipe and no need to manual wipe cache anymore
unmount("/cache");
run_program("/sbin/mke2fs", "/dev/block/mmcblk0p2");
run_program("/sbin/tune2fs", "-O", "extents,uninit_bg,dir_index,has_journal", "/dev/block/mmcblk0p2");
run_program("/sbin/e2fsck", "-fy", "/dev/block/mmcblk0p2");
run_program("/sbin/tune2fs", "-o", "journal_data_writeback", "/dev/block/mmcblk0p2");
run_program("/sbin/e2fsck", "-fy", "/dev/block/mmcblk0p2");
this create an ext4 partition, if you want ext3 just skip the first tune2fs row, and use the -j option in the mke2fs.
mke2fs recreate a new empty partition no need to fill with zeroes before, so the nullifying parts is unneded, just use the mke2fs. its enough, except if you want to wipe the data for reason.
I still receiving get the error message:
E: Can't Open /sdcard/O2x_Nullifier_1.2.zip (bad) Installation Aborted (Status 6)
Click to expand...
Click to collapse
What I'm doing wrong?
ev!denz said:
I still receiving get the error message:
What I'm doing wrong?
Click to expand...
Click to collapse
its because the update-binary is a bit old
use a newer update binary.
vadonka said:
its because the update-binary is a bit old
use a newer update binary.
Click to expand...
Click to collapse
How can I use a newer one?
Darn it! Ok im on my way to work.. I'll see if I can get around the limitations there an update for y'all...
Sent from my LG-P999 using xda premium
ev!denz said:
How can I use a newer one?
Click to expand...
Click to collapse
just replace the update-binary file in the META-INF\com\google\android\ directory
pull it from the cm7 kang for example.
vadonka said:
just replace the update-binary file in the META-INF\com\google\android\ directory
pull it from the cm7 kang for example.
Click to expand...
Click to collapse
OP updated
Trying to install latest OTA upgrade , but I'm getting the following error:
Code:
Verifying current system...
assert failed: apply_patch_check("/system/app/SlackerRadio.apk", "ee1f4b2d6958d622ce87d3f79d041a0abe0f3e21", "2d6b5132806853c96c77ead372644d3183ebd933")
E:Error in /cache/blur_Version.6.13.219.XT894.Verizon.en.US.zip
(Status 7)
Installation Aborted.
I must have been overly zealous in removing bloatware/crapware.
I tried installing the version from the store, but that failed.
Where can I download the original apk files so the OTA upgrade succeeds?
Thank you.
You can download the sbf for the gingerbread build then install a couple programs, osfmount and ext2fsd. Mount the system.img file and pull whatever apks you may need, then push them back to the phone. Don't try installing the updates crapware applications to replace the original system installations, you need the original apks in order for everything to work.
Download the sbf from sbf.droid-developers.org
Sent from my Nexus 7 using Tapatalk 2
danifunker said:
You can download the sbf for the gingerbread build then install a couple programs, osfmount and ext2fsd. Mount the system.img file and pull whatever apks you may need, then push them back to the phone. Don't try installing the updates crapware applications to replace the original system installations, you need the original apks in order for everything to work.
Download the sbf from sbf.droid-developers.org
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I'll give it a try. Thanks for the quick help!
You can also just download the ICS fastboot files and flash those as it doesn't do a check against what is on the phone, it just puts what is supposed to be on the phone...ie....ICS and all the files of a stock system.
tcrews said:
You can also just download the ICS fastboot files and flash those as it doesn't do a check against what is on the phone, it just puts what is supposed to be on the phone...ie....ICS and all the files of a stock system.
Click to expand...
Click to collapse
This.. Just flash the ICS fastboot files directly, much easier.
Files: http://sbf.droid-developers.org/cdma_maserati/list.php
Instructions: http://www.droidforums.net/forum/dr...otorola-droid-4-xt894-stock-windows-only.html
Do not use one of the two ROMs linked in the instructions thread, use the 6.16.217 ROM from my first link.
Common question,
If one applies the fastboot directly from gingerbread, will they lose their data?
danifunker said:
Common question,
If one applies the fastboot directly from gingerbread, will they lose their data?
Click to expand...
Click to collapse
I don't know. I know fastbooting GB .219 over a configured/apps downloaded-installed over GB .219 doesn't wipe data.
However....EVERYONE should Factory Reset after going to ICS. An OS update...done in place....from 2.x.x to 4.x.x......it does work but is more prone to issues than one that is "RESET" and configured from the start.
Backup your data, restore that to the apps after setting the phone up and re-installing the apps from the Market. You'd also be amazed at the number of apps you find that you don't re-install
I had to flash back to stock .219. Didn't do anything after that but went straight to the OTA update and it worked perfectly. didn't do a reset, although I guess I should back up and do it.
I was trying to mount the memory card by using the usb mass storage mode in a rescue disk but the mobile restarted itself a couple of times.. Later on I tried to mount the usb from cwm5 but was unsuccessful. In between all this, I do not know what happened (improper mounting/unmounting?) my device is now not booting into the OS.
Tried reinserting the battery.. no difference. Tried removing the memory card, stuck on "android" logo.
When I restart the mobile, it goes till the end of the bootscreen "Entering system" but then it reverts back to "cm7" boot screen and is stuck there.
My memory card is ok since i tried to mount it using cwm5 in windows and its working fine.
Can anyone let me know any quick solution to this as I need it working urgently?
I am using latest Apocalypse rom with firekernel kernel and amarrullz(???) script.
Did you considered reflashing the ROM?
Sent from my GT-S5830 using xda app-developers app
I know, but i have lots of data in that rom which I still need. I think it's fixable, that's why am posting.
redlag said:
I know, but i have lots of data in that rom which I still need. I think it's fixable, that's why am posting.
Click to expand...
Click to collapse
You Are In a Boot Loop ... Put In Your Particular Case I Would Advice ... Flash Stock! Install CWM To Restore Mounting Points And Then Flash CM7
SnowPluralism said:
You Are In a Boot Loop ... Put In Your Particular Case I Would Advice ... Flash Stock! Install CWM To Restore Mounting Points And Then Flash CM7
Click to expand...
Click to collapse
But boot loop is more of when you are stuck on "android" screen. I am stuck on boot animation.
Update : I made a fresh installation of Apocalypse.
Restored backup of sd-ext : lots of fc but working.
Restored backup of data : stuck at book animation.
I am thinking maybe some broken application is causing this.. any way to find out for sure?
once happened to me with apocalipse. I lost the data.
Sorry for bad english.
redlag said:
But boot loop is more of when you are stuck on "android" screen. I am stuck on boot animation.
Update : I made a fresh installation of Apocalypse.
Restored backup of sd-ext : lots of fc but working.
Restored backup of data : stuck at book animation.
I am thinking maybe some broken application is causing this.. any way to find out for sure?
Click to expand...
Click to collapse
No its not! Boot loop is what i said ! ... And if u followed my advice u would see that i am right !
Sent from my GT-S5830 using xda premium
how long it will take to install new ROM ?
KradeYana SGY said:
how long it will take to install new ROM ?
Click to expand...
Click to collapse
Less then 10 minutes.
Sent from my GT-S5830 using xda premium
SnowPluralism said:
Less then 10 minutes.
Sent from my GT-S5830 using xda premium
Click to expand...
Click to collapse
10? :what: less than a minute to flash and less than 3 minutes for first boot.
Insert witty sentence here
I already did install a new rom last night! But i still need data from previous rom... like sms and whatsapp and other apps.. so I have made a nandroid backup just in case.
Can anyone help me in solving it or recovering the data from the nandriod atleast? Tried appextractor but it wasn't able to restore sms and didn't show whatsapp only! TB didn't help too. I guess its due too d2sd script due to which these apps are not able to locate the data. Any other app which might work?
redlag said:
I already did install a new rom last night! But i still need data from previous rom... like sms and whatsapp and other apps.. so I have made a nandroid backup just in case.
Can anyone help me in solving it or recovering the data from the nandriod atleast? Tried appextractor but it wasn't able to restore sms and didn't show whatsapp only! TB didn't help too. I guess its due too d2sd script due to which these apps are not able to locate the data. Any other app which might work?
Click to expand...
Click to collapse
Maybe opening the nandroid backup manually with 7zip and such. Look up inside your data and system .img files. Use the files inside to create a flashable zip with the data from the apps you most desperatly need. done by using a flashable zip for a rom, deleting everythin inside it except for META-INF, and looking at the updater-script file to make mount /data and flash to /data instead of flashing to /system, place the folder with the data you need inside the zip.
dxppxd said:
Maybe opening the nandroid backup manually with 7zip and such. Look up inside your data and system .img files. Use the files inside to create a flashable zip with the data from the apps you most desperatly need. done by using a flashable zip for a rom, deleting everythin inside it except for META-INF, and looking at the updater-script file to make mount /data and flash to /data instead of flashing to /system, place the folder with the data you need inside the zip.
Click to expand...
Click to collapse
I am getting what you are trying to say but seems like I don't need it. I was able to restore the sd-ext partition which had all the data.. seems like sms file is corrupt? But anyhow, I think most of the data is there now, but no apps! I can see the ".asec" files in ".android_secure" backup but have no idea how to make apk out of these? Any though how nandriod is able to do that or any script for that?
Logcat Attached.
Anyone??
Sent from my GT-S5830 using Tapatalk 2
My Galaxy Tab 7 P1000 was originally running clockwork 3.X... and I just tried to install clockwork 5... and after installation, the device keeps staying at the boot screen. And when I go to recovery mode, the 'HOME' button doesn't work.... :crying::crying:
How can I fixed this brick back to a normal tab?
The usual.
Use overcome method.
Follow my signature.
Sent from my GT-P1000 using xda app-developers app
priyana said:
The usual.
Use overcome method.
Follow my signature.
Sent from my GT-P1000 using xda app-developers app
Click to expand...
Click to collapse
Hey Dude,
Thanks for your reply. I will try it out tomorrow and hope it works on my stupid tab.
By the way, 1 more question. Before reading your reply, I tried to install CWM-based recovery 5.0.2.8 again and tried to install CM9.x on the tab, but not matter which version I used, (P1000, 1000L, 1000N), all of them gave me 'assert failed getprop( ro.product.device ) galaxytab...'. It sounds that the ROM installation file couldn't recognize my P1000 tab.....do you have any idea on how come my device couldn't be recognized.
I'm not sure what exactly has happened in these cases, but it's clear some information, some kind of ID perhaps, somehow has been removed or corrupted. I've seen it myself, but luckily there's fix. When you install a ROM, the first command of updater-script in folder META-INF is an assert statement. This statement tests what Tab you have, and aborts if it's not the right one. Now, if you get an assert error and you're positive you've got the right ROM for the Tab, you can disable the check and it will install the ROM. Even if it's the wrong one! You open the ZIP, edit updater-script and remove the assert statement. It's best to open the ZIP, and not unpack and repack it. And to modify some ZIPs you will have to use Linux, because Windows can't handle those ZIPs.
Thx X 1000000000000000000000000
ableeker said:
I'm not sure what exactly has happened in these cases, but it's clear some information, some kind of ID perhaps, somehow has been removed or corrupted. I've seen it myself, but luckily there's fix. When you install a ROM, the first command of updater-script in folder META-INF is an assert statement. This statement tests what Tab you have, and aborts if it's not the right one. Now, if you get an assert error and you're positive you've got the right ROM for the Tab, you can disable the check and it will install the ROM. Even if it's the wrong one! You open the ZIP, edit updater-script and remove the assert statement. It's best to open the ZIP, and not unpack and repack it. And to modify some ZIPs you will have to use Linux, because Windows can't handle those ZIPs.
Click to expand...
Click to collapse