[Q] Failed Flashing CM9, Tried Several Things, Please Help - Galaxy Tab Q&A, Help & Troubleshooting

Hello All!
I am having an issue trying to flash Cyanogen Mod 9 on my rooted Verizon Galaxy Tab 7 (SCH-I800, the older model).
I downloaded Cyanogen Mod 9 (cm-9.1.0-p1c.zip) and placed it on my SD card. Using GooManager I rebooted into recovery to flash the rom. When I tried to flash it I got an assertion error on the following statement:
assert(getprop("ro.product.device") == "galaxytab7c" || getprop("ro.build.product") == "galaxytab7c" ||
getprop("ro.product.device") == "p1c" || getprop("ro.build.product") == "p1c" ||
getprop("ro.product.device") == "SCH-I800" || getprop("ro.build.product") == "SCH-I800" ||
getprop("ro.product.device") == "SPH-P100" || getprop("ro.build.product") == "SPH-P100" ||
getprop("ro.product.device") == "vzwtab" || getprop("ro.build.product") == "vzwtab");
...
...
To try and outsmart the updater script I disabled asserts using the recovery menu but strangely enough (and probably a good topic for another thread) the assert statement STILL failed. (So much for disabling asserts. )
I figured something must be wrong with disabling the asserts so I decided to try a different approach. I unzipped cm-9.1.0-p1c.zip in a temp folder on my PC and proceeded to edit updater_script using notepad. I removed the entire assert statement and saved the file then re-zipped it up and called it cm-9.1.0-p1c_NOASSERT.zip.
I then copied this new zip file back over to my flash card and rebooted into recovery. The updater script no longer failed on the assert however it just halted without giving me any useful information. Here is the log of the script:
-- Installing: /sdcard/cm-9.1.0-p1c_NOASSERT.zip
Finding update package...
Opening update package...
Installing update...
Installation aborted.
So here I am. Stuck at this point and I don't know what to do. I tried installing with the original rom. I tried turning off asserts and installing again. I modified the updater script to remove the assert statement but that just pushed the error further down the line (and made it less verbose).
I am 99.9% sure I downloaded the correct rom and that my device is indeed a Verizon (CDMA) Samsung Galaxy Tab 7 model number SCH-I800.
I even checked the /system/build.prop file on my tablet and there was a property called ro.product.device and it was set to SCH-I800.
...
ro.build.tags=test-keys
ro.product.model=SCH-I800
ro.product.brand=samsung
ro.product.name=SCH-I800
ro.product.device=SCH-I800
ro.product.board=s5pc110
...
I am at a loss for what to do next. Can anyone give me advice to point me in the right direction or even better tell me exactly what to do!
Thank you!!
Jan

When editing the zip and updater-script do not re-zip the file. The way I do this on my S2 (will be same for any device) using 7zip is:
- Open zip and drag and drop the updater-script from 7zip onto my PC
- Edit in Notepad++ and save
- Drag updater-script back into 7zip window where it was
- Close 7zip
I've never had to re-zip the file and I edit the ROM zip I'm compiling and using every time to remove and add apps, edit build.prop etc Same principle should apply to any device using CWM zips so hope it helps

AvRS said:
When editing the zip and updater-script do not re-zip the file. The way I do this on my S2 (will be same for any device) using 7zip is:
- Open zip and drag and drop the updater-script from 7zip onto my PC
- Edit in Notepad++ and save
- Drag updater-script back into 7zip window where it was
- Close 7zip
I've never had to re-zip the file and I edit the ROM zip I'm compiling and using every time to remove and add apps, edit build.prop etc Same principle should apply to any device using CWM zips so hope it helps
Click to expand...
Click to collapse
Why do you think it's better to use 7zip and pull the file out, edit it, then put it back in. I don't understand why that would be different that unzipping the whole thing then re-zipping it up. The only thing I can think of as to why your method might work is if there is some kind of checksum or special "tag" in the original zip that gets lost doing it my way.

I just thought of something else.... Could it be that I am having the problem because I am going from the stock setup straight to Cyanogen Mod 9? Do I have to put CM7 on my device first then update to CM9?

AvRS said:
When editing the zip and updater-script do not re-zip the file. The way I do this on my S2 (will be same for any device) using 7zip is:
- Open zip and drag and drop the updater-script from 7zip onto my PC
- Edit in Notepad++ and save
- Drag updater-script back into 7zip window where it was
- Close 7zip
I've never had to re-zip the file and I edit the ROM zip I'm compiling and using every time to remove and add apps, edit build.prop etc Same principle should apply to any device using CWM zips so hope it helps
Click to expand...
Click to collapse
OMG YOUR SUGGESTION WORKED!!! I love you!!! (Don't worry I am a girl. )

Glad to hear it worked
Only reason I think it works is because it's a tried and tested process seriously though I'm not sure but possibly I think re-zipping the file could change the compression or like you say maybe break some checksum or whatever.
Haha like the extra bit
Sent from my GT-I9100 using xda premium

AvRS said:
When editing the zip and updater-script do not re-zip the file. The way I do this on my S2 (will be same for any device) using 7zip is:
- Open zip and drag and drop the updater-script from 7zip onto my PC
- Edit in Notepad++ and save
- Drag updater-script back into 7zip window where it was
- Close 7zip
I've never had to re-zip the file and I edit the ROM zip I'm compiling and using every time to remove and add apps, edit build.prop etc Same principle should apply to any device using CWM zips so hope it helps
Click to expand...
Click to collapse
Opening tru 7zip works on mine too. Thanks much!

Follow up using Mac
MarlX said:
Opening tru 7zip works on mine too. Thanks much!
Click to expand...
Click to collapse
I ran into this same issus. I had to edit using 7-zip (Parrallels VM).
My approach that got me a working CM9 on my SGH-849 T-Mobile (GT-P1000 )was to download/install Heimdall suite for MAC.
Download and extract GB-Stock-Safe-V5. I then downloaded cwm-5-p1.tar. I replaced the zImage in the Subdirectory GB_Stock_Safe_V5 with the cwm zImage and moved the t-mobile modem file and gt-p1000 files to this same GB_Stock_Safe_V5 subdirectory. I then opened terminal and cd'd to this subdirectory.
I ran Heimdall with "heimdall flash --repartition --primary-boot boot.bin --cache cache.rfs --dbdata dbdata.rfs --factoryfs factoryfs.rfs --pit gt-p1000_mr.pit --modem modem.bin --param param.lfs --secondary-boot Sbl.bin --kernel zImage --verbose"
I had previously loaded the modified CM-9 file and Gapps to my micro sd card. So, when the system rebooted, I could do the factory reset, clear cache, and (advanced) clear Dalvik cache. and install from zip.
All seems to be working. Thanks for the zip file hint -- last piece of the puzzle for me.
Jack

AvRS said:
When editing the zip and updater-script do not re-zip the file. The way I do this on my S2 (will be same for any device) using 7zip is:
- Open zip and drag and drop the updater-script from 7zip onto my PC
- Edit in Notepad++ and save
- Drag updater-script back into 7zip window where it was
- Close 7zip
I've never had to re-zip the file and I edit the ROM zip I'm compiling and using every time to remove and add apps, edit build.prop etc Same principle should apply to any device using CWM zips so hope it helps
Click to expand...
Click to collapse
WORKED PERFECTLY on my Sprint Samsung Galaxy Tab SPH-P100!
Was getting the status 7 error after removing the ASSERT portion of the script and then Installation Aborted error with no explanation.
I download the trial version of WinZip for OSX, pulled out the updater-script, edited the file in VIM, and dragged it back into the .zip file.
So awesome! (Not a girl and yes I clicked the thanks button)

Assert lines in updater script code?
AvRS said:
When editing the zip and updater-script do not re-zip the file. The way I do this on my S2 (will be same for any device) using 7zip is:
- Open zip and drag and drop the updater-script from 7zip onto my PC
- Edit in Notepad++ and save
- Drag updater-script back into 7zip window where it was
- Close 7zip
I've never had to re-zip the file and I edit the ROM zip I'm compiling and using every time to remove and add apps, edit build.prop etc Same principle should apply to any device using CWM zips so hope it helps
Click to expand...
Click to collapse
Total n00b question here, but which lines are the assert lines? I tried looking for the obvious "assert lines here", but nothing so helpful. Any help would be appreciated, GB is now so old as to be about unusable these days.
edit: I was in the wrong file, but now I can't get the edited updater back into the folder. I shall persevere, though!

I managed to edit the update script, but now after flashing, the tab just hangs out the Samsung screen. Any suggestions?
edit: poking around some more, I found I had deleted too many lines. Oops!

Related

[Q] Unable to flash UOT zip

Hey guys, I've looked around and haven't found any reason why I SHOULD'NT be able to flash a custom theme from the Ultimate Online Kitchen, so I'm posting for suggestions as to why I am getting this error when trying to flash this... here is the error message I keep getting:
Installing update...
E:Error in /sdcard/Flashing/Themes/UOT-08-25-17-41-1.zip
(Status 0)
Installation aborted.
I also tried flashing it from the root of the SD card with the same results.
At the kitchen I am using the Type MTD (default) update binary...
Looking forward to your suggestions, maybe I have my settings wrong in the kitchen
From the how-to page:
WORKAROUND for recovery error (Status 0):
1. Unzip your ROM and find
META-INF/com/google/android/update-binary file
2. Put this file in the UOT zip (overriding UOT's file)
Click to expand...
Click to collapse
I saw that in the How TO section and tried different ways:
1: Just dragging the file (update-binary)to root of the zip
2: Navigating in the zip to where the update-binary is and dropping it in there
3: Unpacking the zip and placing the file in the root of the zip
4: Unpacking the zip and replacing the file in the zip with the one from my rom
They all yield the same results (I'm pullin' my hair out) because the 2nd technique should've worked
did you ever figure out how to make this work?
My bad fellas, I should've posted back that I got this resolved...
I eventually downloaded a fresh copy of my ROM, unzipped the entire thing instead of just dragging out the file I needed.
I then deleted the file I was replacing with the one I got from my ROM and it went fine (after about 10 tries).
I also flashed my recovery to my phone and the amss and the dsp1...
Anyway, now I'm a cookin' fool changing themes every other day
cdzo72 said:
My bad fellas, I should've posted back that I got this resolved...
I eventually downloaded a fresh copy of my ROM, unzipped the entire thing instead of just dragging out the file I needed.
I then deleted the file I was replacing with the one I got from my ROM and it went fine (after about 10 tries).
I also flashed my recovery to my phone and the amss and the dsp1...
Anyway, now I'm a cookin' fool changing themes every other day
Click to expand...
Click to collapse
Hi, I am from CR too
I am trying to do this but no luck
Galaxy S2 i9100
Ice Cream I9100XXLPQ
I have the file but when I try to install it I get the error (Status 0)
I understand this:
WORKAROUND for recovery error (Status 0):
1. Unzip your ROM and find
META-INF/com/google/android/update-binary file ----->> What do they mean to unzip the ROM?? I installed ICS from a .tar.md5 file and it is without folders (opening with Winrar). I also searched in the phone with root explorer and didn't find META-INF....
2. Put this file in the UOT zip (overriding UOT's file)
PV!
mrfmanuel said:
Hi, I am from CR too
I am trying to do this but no luck
Galaxy S2 i9100
Ice Cream I9100XXLPQ
I have the file but when I try to install it I get the error (Status 0)
I understand this:
WORKAROUND for recovery error (Status 0):
1. Unzip your ROM and find
META-INF/com/google/android/update-binary file ----->> What do they mean to unzip the ROM?? I installed ICS from a .tar.md5 file and it is without folders (opening with Winrar). I also searched in the phone with root explorer and didn't find META-INF....
2. Put this file in the UOT zip (overriding UOT's file)
PV!
Click to expand...
Click to collapse
I have a i9100 also and you really don't need the kitchen because there so many themed ROMs out there. If you like send me a private message and will contact you with pointers on getting the most out of your i9100

[Q] Can we make a signes zip file own are own?

I was thinking if we can make a zip file of our apps like the gapps which we can zip it via recovery.
There are so many roms coming up everyday and you are tempted to test each one of it. But with our basic apps we feel the rom is incomplete
And downloading it from the market or finding and installing via a file manager again and again is very irritating and boring
Can we make our own CUSTOMIZED SIGNED ZIP file file without complex signing??
Thanks in advance
yes you can.
hetunandu said:
I was thinking if we can make a zip file of our apps like the gapps which we can zip it via recovery.
There are so many roms coming up everyday and you are tempted to test each one of it. But with our basic apps we feel the rom is incomplete
And downloading it from the market or finding and installing via a file manager again and again is very irritating and boring
Can we make our own CUSTOMIZED SIGNED ZIP file file without complex signing??
Thanks in advance
Click to expand...
Click to collapse
Well, if you are changing your ROMs like underwear ... head over into the Android Development and Hacking section and grab yourself any tool you're able to find there which can batch-install APKs at the convenience of pushing a button.
You must put all the files you need to system/app folder.
Then use the simpliest script:
Code:
mount("yaffs2", "MTD", "system", "/system");
package_extract_dir("system", "/system");
unmount("/system");
You can try with other commands.
Then save this as updater-script in META-INF/com/google/android
Extract attached binary to the same folder as script. Pack it as zip in normal compression and voila
If you need to sign your package search for tools in XDA. There's a lot of them.
hetunandu said:
I was thinking if we can make a zip file of our apps like the gapps which we can zip it via recovery.
There are so many roms coming up everyday and you are tempted to test each one of it. But with our basic apps we feel the rom is incomplete
And downloading it from the market or finding and installing via a file manager again and again is very irritating and boring
Can we make our own CUSTOMIZED SIGNED ZIP file file without complex signing??
Thanks in advance
Click to expand...
Click to collapse
You can try titanium backup it's one of my favorite apps because I often change roms
eagleeyetom said:
You must put all the files you need to system/app folder.
Then use the simpliest script:
Code:
mount("yaffs2", "MTD", "system", "/system");
package_extract_dir("system", "/system");
unmount("/system");
You can try with other commands.
Then save this as updater-script in META-INF/com/google/android
Extract attached binary to the same folder as script. Pack it as zip in normal compression and voila
If you need to sign your package search for tools in XDA. There's a lot of them.
Click to expand...
Click to collapse
thanks im trying it now...
also can we put the apps in data partition too? cause i also want to back up some games which i guess we can put in the system...
can i use sign+ to sign the zip??
B.Jay said:
Well, if you are changing your ROMs like underwear ... head over into the Android Development and Hacking section and grab yourself any tool you're able to find there which can batch-install APKs at the convenience of pushing a button.
Click to expand...
Click to collapse
could not find any 1 button tool... can u attach a link which u use or u know?
Yeah. You could extract data as well. Don't forget to mount data and /data. Signing zip files is not necessary to use them (of course, you might do this if you want).
Maybe there is one button ADB tool, but using ADB is really simple. Just download Android SKD, put it on C: drive, copy cmd.exe from windows/system32 folder to platform-tool and run it.
If you will place apk's inside platform-tools just type "adb install" with your phone connected in debugging mode.
Good luck
getting a error of installation aborted
Which status?

Help.

Holla amigos...
I need help........again.
See, I'm creating my own rom and my base uses blackhawk. I want to change this to firekernel. I searched xda and Google but I couldn't find anything. All they talk about is how to flash another kernel. I want to know how to include it in rom before flashing. And also, could someone tell me the .XML that is used for Modding the lock screen.
Sent from my GT-S5830 using xda app-developers app
Inside the flashable zip (any flashable zip) you'll find several folders and files. To see where each file gets flashed to, look inside the META-INF folder and search for a file called "updater script".
Its the updater script the one that indicates where each part of the zip will be flashed, so open it with a text editor, take notes where each file ends up, and copy them to their location inside your rom.
dxppxd said:
Inside the flashable zip (any flashable zip) you'll find several folders and files. To see where each file gets flashed to, look inside the META-INF folder and search for a file called "updater script".
Its the updater script the one that indicates where each part of the zip will be flashed, so open it with a text editor, take notes where each file ends up, and copy them to their location inside your rom.
Click to expand...
Click to collapse
And at the start, through dsixda kitchen updater script was converted into update script. Is it the same? Okk. And what about including scripts, I want adrenaline engine. I downloaded the zip. Ignored the Meta -inf and copied the system folders inside the system folder of the working project....Am I right?
Sent from my GT-S5830 using xda app-developers app
If you're using the kitchen its OK, you can add any flashable zip that way, copying the files and folders to their respective location inside your Project. Checking the updater script is only necessary when in doubt of where each thing goes.
Don't use kitchen's updater script and binaries.They won't work,could even brick the device.To change kernel,download firekernel and replace the boot.img in that pack with the one in your rom.Boot.img is the kernel.Scripts go in init.d
Prawesome said:
Don't use kitchen's updater script and binaries.They won't work,could even brick the device.To change kernel,download firekernel and replace the boot.img in that pack with the one in your rom.Boot.img is the kernel.Scripts go in init.d
Click to expand...
Click to collapse
Hey. Thanks for that. Please help me out here: http://forum.xda-developers.com/showthread.php?p=28891130#post28891130

Can't Upgrade CM9

So while I was still learning about flashing, ROMs, Kernels, etc, I managed to get a CM9 build on my Captivate. However, I installed the build for smtd device instead of mtd device. Now when I go to install the latest nightly CM9 build (mtd version), it fails right away with an assert failure. I think it is because it is checking my device type and sees that I have the smtd version currently.
Is there an easy way around this? I've considered editing the install script in the zip file to bypass the assert. Would that work, or there a better way?
cgulka said:
So while I was still learning about flashing, ROMs, Kernels, etc, I managed to get a CM9 build on my Captivate. However, I installed the build for smtd device instead of mtd device. Now when I go to install the latest nightly CM9 build (mtd version), it fails right away with an assert failure. I think it is because it is checking my device type and sees that I have the smtd version currently.
Is there an easy way around this? I've considered editing the install script in the zip file to bypass the assert. Would that work, or there a better way?
Click to expand...
Click to collapse
Open the .zip file with winrar, then go to "\META-INF\com\google\android" and open the file "updater-script" with Notepad ++. Delete all the lines (The very beginning) that says: assert(getprop("ro.product.device") == "captivate" etc... save it, let winrar update the files. Then try flashing it again.
Thanks! That worked. That was what I suspected I needed to do. I can tell you this, it takes a LONG time to re-zip such a large file on a little under-powered netbook.
Nick0703 said:
Open the .zip file with winrar, then go to "\META-INF\com\google\android" and open the file "updater-script" with Notepad ++. Delete all the lines (The very beginning) that says: assert(getprop("ro.product.device") == "captivate" etc... save it, let winrar update the files. Then try flashing it again.
Click to expand...
Click to collapse
I've been having a similar problem, so I did this and was able to install the ROM, but it gets stuck in the boot animation. Any ideas?
UPDATE: Fixed it by formatting the boot and system partitions. I blame semaphore.

[GUIDE][N8000/8010/8013] Adding GN 10.1 to dsixda's kitchen

Hello everybody!
I created this thread, because I had realized that this device isn't supported in dsixda's android kitchen.
Although adding support is not difficult..!!
So here is what you need to do..
dsixda kitchen tools addons:
1. Download [dsixda Kitchen fixes for Note 10.1.rar] from the attachment bellow.
2. Open your dsixda's kitchen_dir/tools/edify_defs folder and copy the content of [dsixda Kitchen fixes for Note 10.1.rar] edify_defs folder (p4noterf) into it (this will install mounting points for the device)
3. Open your dsixda's kitchen_dir/tools/update_files folder, rename emmc-update-binary file to something else. (e.g.: emmc-update-binary.bak) and copy the content of [dsixda Kitchen fixes for Note 10.1.rar] update_files folder (emmc-update-binary) file into it (this will tell the device to use appropriate update-binary during flashing)..
We haven't finished yet; after finishing cooking a ROM, you need to pay attention to the followings in the updater-script:
updater-script fixes and addons:
1. format command needs 4 args instead of 3 args:
This one is wrong (3 args):
Code:
format("ext4", "EMMC", "/dev/block/mmcblk0p9");
This one is OK (4 args):
Code:
format("ext4", "EMMC", "/dev/block/mmcblk0p9", "/system");
2. To flash recovery.img, put it on the root of rom zip and add these commands:
Code:
assert(package_extract_file("recovery.img", "/tmp/recovery.img"),
write_raw_image("/tmp/recovery.img", "/dev/block/mmcblk0p6"),
delete("/tmp/recovery.img"));
3. To flash modem.bin (for GT-N8000), put modem.bin with flash_image (content in [dsixda Kitchen fixes for Note 10.1.rar]) on the root of rom zip and add these commands:
Code:
package_extract_file("flash_image", "/tmp/flash_image");
set_perm(0, 0, 0777, "/tmp/flash_image");
assert(package_extract_file("modem.bin", "/tmp/modem.bin"),
run_program("/tmp/flash_image", "/dev/block/mmcblk0p7", "/tmp/modem.bin"),
delete("/tmp/modem.bin"));
and that's all.. hope you all good cooking folks
You are on fire:laugh: , nice work this will be much helper :good: .
For the noobs like me
What is dsixda Kitchen ? = http://forum.xda-developers.com/showthread.php?t=633246
Great!
Inviato dal mio GT-N7100 con Tapatalk 2
Great great work!
majdinj said:
Hello everybody!
I created this thread, because I had realized that this device isn't supported in dsixda's android kitchen.
Click to expand...
Click to collapse
I continued your work and made little stronger integration with android kitchen. I modified some scripts and did Note 10.1 integration in same way as S3 and S4 integration was done.
What I did?
Automatic adding of proper update binary - no more manual renaming of update binary is needed!
Automatic adding of flash_image to ROM - copping it from samsung_files/flash_image
Automatic converting of format back to delete_recursive - as for other galaxies
Added Note 10.1 to show rom info
edify_defs file and update binary used are yours, just renamed.
I must confess that I haven't test this yet, but I maintain most of Linux shell scripts that we use at work, so I am very confident in what I did.
Would you mind if I post this here?
viking13 said:
I continued your work and made little stronger integration with android kitchen. I modified some scripts and did Note 10.1 integration in same way as S3 and S4 integration was done.
What I did?
Automatic adding of proper update binary - no more manual renaming of update binary is needed!
Automatic adding of flash_image to ROM - copping it from samsung_files/flash_image
Automatic converting of format back to delete_recursive - as for other galaxies
Added Note 10.1 to show rom info
edify_defs file and update binary used are yours, just renamed.
I must confess that I haven't test this yet, but I maintain most of Linux shell scripts that we use at work, so I am very confident in what I did.
Would you mind if I post this here?
Click to expand...
Click to collapse
not at all,,, sharing is caring dude,, we are all here exchanging our experiences
please go ahead :good:
majdinj said:
not at all,,, sharing is caring dude,, we are all here exchanging our experiences
please go ahead :good:
Click to expand...
Click to collapse
Android-Kitchen-Note10.1-support
Some quick instructions:
1. Backup your current AK - if anything goes wrong, you will be able to quickly restore your current AK
2. Download and install AK v0.224 from https://github.com/dsixda/Android-Kitchen/tags - this modification works only with v0.224
3. Download Android-Kitchen-Note10.1-support.zip from http://db.tt/czMk3fQe
4. Do not add majdinj files to AK - his files are already inside Android-Kitchen-Note10.1-support.zip, just renamed
5. Extract archive and copy scripts and tools folders over AK
6. Overwrite files that are already there (almost all files from scripts folder) - this is the reason why AK version must be v0.224
That's all.
All things that automatically work with S3 and S4 should now work with Note 10 (N8000, N8010 and N8013)!
I did quick check and everything looks fine, but unfortunately, this is still not properly tested yet. The problem might happen if I misspelled some of the variable or file names.
Darkman wanted to test it, but he had to finish some things on work before vacation. I have some very close deadlines at work.
Please let me know if you encounter any problem, so I can fix it.
If everything works fine, I will post this to dsixda, and I hope he will find some time to incorporate this into official release.
EDIT: I forgot to mention that I modified scripts from AK v0.224, so this version must be used in order to work properly!
Kitchen v0.224 doesn't work on the newest ROM XXUCMH2 for N8010:
Code:
cp: /tmp/for_kitchen/app/Dropbox.apk: No such file or directory
cp: /tmp/for_kitchen/app/FaceLock.apk: No such file or directory
cp: /tmp/for_kitchen/app/Gmail.apk: No such file or directory
cp: /tmp/for_kitchen/app/GmsCore.apk: No such file or directory
cp: /tmp/for_kitchen/app/GoogleTTS.apk: No such file or directory
cp: /tmp/for_kitchen/app/GroupCast.apk: No such file or directory
cp: /tmp/for_kitchen/app/Phonesky.apk: No such file or directory
cp: /tmp/for_kitchen/app/PlusOne.apk: No such file or directory
cp: /tmp/for_kitchen/app/PolarisOfficeTablet.apk: No such file or directory
cp: /tmp/for_kitchen/app/SNS.apk: No such file or directory
cp: /tmp/for_kitchen/app/SamsungAppsUNA3.apk: No such file or directory
cp: /tmp/for_kitchen/app/SamsungApps_Tablet.apk: No such file or directory
cp: /tmp/for_kitchen/app/SamsungIME.apk: No such file or directory
cp: /tmp/for_kitchen/app/Samsungservice.apk: No such file or directory
cp: /tmp/for_kitchen/app/SecEmail_Tablet.apk: No such file or directory
cp: /tmp/for_kitchen/app/SecSettings.apk: No such file or directory
cp: /tmp/for_kitchen/app/Snote_P4C.apk: No such file or directory
cp: /tmp/for_kitchen/app/Snote_P4C_Provider.apk: No such file or directory
cp: /tmp/for_kitchen/app/Talk.apk: No such file or directory
cp: /tmp/for_kitchen/app/Velvet.apk: No such file or directory
cp: /tmp/for_kitchen/app/YouTube.apk: No such file or directory
any solution?
This looks interesting, I might have to sit down and work out the mods for the n8020 and post em if anyone is interested...
viking13 said:
Android-Kitchen-Note10.1-support
Some quick instructions:
1. Backup your current AK - if anything goes wrong, you will be able to quickly restore your current AK
2. Download and install AK v0.224 from https://github.com/dsixda/Android-Kitchen/tags - this modification works only with v0.224
3. Download Android-Kitchen-Note10.1-support.zip from http://db.tt/czMk3fQe
4. Do not add majdinj files to AK - his files are already inside Android-Kitchen-Note10.1-support.zip, just renamed
5. Extract archive and copy scripts and tools folders over AK
6. Overwrite files that are already there (almost all files from scripts folder) - this is the reason why AK version must be v0.224
That's all.
All things that automatically work with S3 and S4 should now work with Note 10 (N8000, N8010 and N8013)!
I did quick check and everything looks fine, but unfortunately, this is still not properly tested yet. The problem might happen if I misspelled some of the variable or file names.
Darkman wanted to test it, but he had to finish some things on work before vacation. I have some very close deadlines at work.
Please let me know if you encounter any problem, so I can fix it.
If everything works fine, I will post this to dsixda, and I hope he will find some time to incorporate this into official release.
EDIT: I forgot to mention that I modified scripts from AK v0.224, so this version must be used in order to work properly!
Click to expand...
Click to collapse
Hi,
tried the link,
support zip - http://db.tt/czMk3fQe -but seems dead,
please help,
thanks.
Sent from my GT-N8000 using xda app-developers app
jebll said:
Hi,
tried the link,
support zip - http://db.tt/czMk3fQe -but seems dead,
please help,
thanks.
Sent from my GT-N8000 using xda app-developers app
Click to expand...
Click to collapse
Sorry for late reply, but I was in the hospital, having a surgery.
I just check, link works fine here.

Categories

Resources