Hi guys, today I built a rom with the last Android Kitchen, everything ok, I downloaded the rom from samfirmware, I made the device configuration file for S3 Mini in the edify folder of the kitchen, I set up the rom.. made some changes with the kitchen and I built the rom. The rom flashed ok, all went ok but there's a big problem... if I use the rom the WiFi wouldn't connect anymore and the phone doesn't recognise that I have a sim inserted, and the USB cable doesn't connect mass media.. I didn't include the kernel in the rom, and I didn't wipe data because the data is from the same rom but without any modifications, any ideeas? I belive it's something related to CSC, I included the modem that came with the rom.
In that case.. Extract the sec_csc.zip from cache.img and include the files to your rom.
tys0n said:
In that case.. Extract the sec_csc.zip from cache.img and include the files to your rom.
Click to expand...
Click to collapse
I already did that.. the kitchen extracted the cache.img and copied the files from csc.zip to /system but it still doesn't work.
dei.andrei98 said:
I already did that.. the kitchen extracted the cache.img and copied the files from csc.zip to /system but it still doesn't work.
Click to expand...
Click to collapse
ok
Have you read this thread? [HOWTO] Build your own rom for GT-I8190(golden) with dsixda's Android Kitchen
Modem was not included in my rom.. I'll try to include it.
Sent from my GT-I8190 SIII Mini using Tapatalk
Related
Hello friends,
after trying lots of roms i decided to build my own rom
based on jvo.
I took the cwm version jvo which is allready deodexed
and zipaligned from this thread : http://forum.xda-developers.com/showthread.php?t=948790
Then i extracted the files, inserted some files from xda developers
and deleted a lots of apps i dont use.
After that i packed everything with WinRAR in normal kompression mode.
I put the rom on the internal sd then and tried to install it via cwm.
But the installation only takes 1 sek and nothing changes.
Is there someting i do wrong?
BTW: I flashed jvo with bootloader via odin first, then cfroot for jvo to get
cwm.
Sorry for poor english guys.
After that i packed everything with WinRAR in normal kompression mode.
Win Rar is that the correct format . .rar
jje
What JJEgan said, you want be using a zip format.
I actually find it easier to not decompress the whole rom and just insert/remove things into the original archive with WinRAR, done this with kernels, modems apps etc.
sorrry I'm a newb user, tried to flashing CM10 nightly rom and succes, but then I realized the baseband is unknown and I can't receive signal. tried flashing this modem http://forum.xda-developers.com/showpost.php?p=20162933&postcount=2 and it cant flashed, it says status 7. tried the 2nd ways to copy modem.bin to radio folder and no luck. can anybody help me?
sorry if i post it to wrong section
Don't flash.
Just unpack the modem and copy and paste modem.bin into /system/vendor using root explorer.
Sent from my GT-P1000 using xda app-developers app
priyana said:
Don't flash.
Just unpack the modem and copy and paste modem.bin into /system/vendor using root explorer.
Sent from my GT-P1000 using xda app-developers app
Click to expand...
Click to collapse
thankyou verymuch, that works and really helpful
hotheabilly said:
sorrry I'm a newb user, tried to flashing CM10 nightly rom and succes, but then I realized the baseband is unknown and I can't receive signal. tried flashing this modem http://forum.xda-developers.com/showpost.php?p=20162933&postcount=2 and it cant flashed, it says status 7. tried the 2nd ways to copy modem.bin to radio folder and no luck. can anybody help me?
sorry if i post it to wrong section
Click to expand...
Click to collapse
I have a Samsung Galaxy i987 AT&T GSM US Tablet. I have had CM9 on it working the phone and GPS previously. I now loaded the latest CM10 and have not either found the right modem or have other issues. I loaded the 0923 yesterday and it was said that you could pull the modem from Wiki CM and use CM to load it. I tried both of the modems in the links below one for AT&T and one that says Galaxy i987. Both show that it was successful, but in both attempts the modem.bin file did not show up under the /system/vendor folder. I used Root Explorer to finally move the modem.bin file from both of these download into the /system/vendor folder, and while the modem.bin file did show up, it still has unknown modem baseband and no modem or GPS working.
http://forum.xda-developers.com/show....php?t=1069727
and here
http://wiki.cyanogenmod.com/wiki/Sam...port_Downloads
That is because the latest cm10 move modem.bin back to /radio/modem.bin like cm9 again.
Man, if you want to flash cm10 you have read the whole thread.
Be interested. Don't just jump in.
Sent from my GT-P1000 using xda app-developers app
priyana said:
That is because the latest cm10 move modem.bin back to /radio/modem.bin like cm9 again.
Man, if you want to flash cm10 you have read the whole thread.
Be interested. Don't just jump in.
Sent from my GT-P1000 using xda app-developers app
Click to expand...
Click to collapse
Wow, thanks for the response. I read the thread every night on the CM10 Development, or is that the wrong one. I saw where dev posted you could get your modem.bin from the wiki and use Clockworks Mod to update again. Also, they were going back on the partition to CM9 like to allow 2gb and that there would be a wipe. Nothing said go to that directory /radio/modem.bin, unless by saying that you could go back to wiki like CM9 meant that directory. I thought I could use Clockworks and do a zip file firmware update. I admit that I am a bit new to all of this, but I have been modding something or other back to the Nintendo PS1 and original Xbox days, I guess I still need to get my sea legs here and will take a thrashing once in a while until I do. I do appreciate the help.
BTW, I got my GPS back, but not my phone. I will go back and search some more, but I got the modem.bin file from
http://wiki.cyanogenmod.com/wiki/Samsung_Galaxy_Tab_(GSM):_Support_Downloads
AT&T
UCKJ1
Using Root Explorer I put the modem.bin in the /radio directory. The GPS is working great, but no cell registration. I guess I should say, I get data, but when it goes to dial it beeps and ends the call immediately.
Yes, haha, CM9 was on /radio/modem.bin
then CM10 too, then CM10 move to new MTD partition, and modem.bin goes to /system/vendor/,
then CM10 move back again to another partition (not sure if it is back to same old partition or a new old partition )
but modem is back to /radio/modem.bin
once it is back to /radio, the one in Wiki will work, regardless of the way it is partitioned. You just need to read inside the zip, the updater script put the modem there.
It is a simple matter of modifying the path within the script for any layout.
Having said that, the older modems in modems thread in dev sticky, they are for pre-MTD time. During original Samsung BML partition, the modem is on a partition of its own, so a more complex method is required to put the modem there, including using CWM (zip) and Odin (tar)
But nowadays is just using Root Explorer and you are ok.
That is why I said you should read the whole thread, you will know such changes happening.
There is a CM10 thread and dev and one in General for discussion.
Ask questions in General if necessary, never on Dev one unless you have issue compiling, or have some other dev bug.
If you are interested on CWM updater script, just unpack the rom zip or the modem zip or any of the CWM flashable zip and have a look at the updater-script within the META-INF.
Edit: regarding AT&T tablet no call, I think it is network related. AT&T know you are on tablet and don't allow making calls. That is my theory.
gps and phone fail, baseband unknown
I have the same problem on baseband, where can I get the files and please get me some good link and info.
thanks.
btw is there a way to save the restore data in recovery mode, just in case if I lost it, I have no way to go back to cm9.
priyana said:
Don't flash.
Just unpack the modem and copy and paste modem.bin into /system/vendor using root explorer.
Sent from my GT-P1000 using xda app-developers app
Click to expand...
Click to collapse
It is the first sticky tread in Dev section
http://forum.xda-developers.com/showthread.php?t=1069727
get the JPZ modem.
It says Gingerbread but does not matter.
Unzip it to find a modem.bin
Use it with root explorer or ES File Explorer in root mode, system mounted as read-write.
Put in /radio/modem.bin (there may be one already there but likely broken)
not available
Make sure you use Notepad++ to edit the updaterscript. If you have problems. Take an updater-script from a working rom and see if it flashes successfully.
---------- Post added at 09:34 AM ---------- Previous post was at 09:33 AM ----------
Copy the entire META-INF folder from any rom and paste it in your rom's zip.
EG- If your rom is based on cm7, copy cm7's meta-inf
I copied META-INF from Adrenaline ROM
And it didn't work
assert failed:raw_boot_img
Could it be a kernel problem (boot.img)
Sent from my GT-S5830 using xda premium
Which boot.img are you using?
You need to use a boot.img from a custom kernel, stock boot.img wont work.
Mate Upload Your Rom and PM it to me and i'll look at what is wrong if u like.
Are you sure you never used any of the Dsixda kitchen tools?
Because they are not compatible with the Ace.
Plus, I hope you never converted it into update-script.
Is your rom CM7 based, or stock based?
Im using stock boot.img
I thought it would work... I don't like custom kernels like nims or CF-Root.
As soon as I get home I'll send you ROM.
It was originally update-script and changed with dsixda kitchen to updater-script.
Stock based
Sent from my GT-S5830L using xda premium
Tovagulet said:
Im using stock boot.img
I thought it would work... I don't like custom kernels like nims or CF-Root.
As soon as I get home I'll send you ROM.
It was originally update-script and changed with dsixda kitchen to updater-script.
Stock based
Sent from my GT-S5830L using xda premium
Click to expand...
Click to collapse
So that's the problem.
Dsixda scripts are not compatible with the Ace.
did the stock rom u are basing this rom on have a Meta-Inf. or was it from a system.img
Tovagulet said:
Im using stock boot.img
I thought it would work... I don't like custom kernels like nims or CF-Root.
As soon as I get home I'll send you ROM.
It was originally update-script and changed with dsixda kitchen to updater-script.
Stock based
Sent from my GT-S5830L using xda premium
Click to expand...
Click to collapse
After creating zip usi.g dsixda kitchen. Extract zip and copy meta-inf folder from.other rom and replace. Stock kernel wont work. Extract the zip of any custom kernel, copy system folder and boot.img and paste in the root directory of extracted files of rom. Zip back everything. It will work.
tj_droid said:
After creating zip usi.g dsixda kitchen. Extract zip and copy meta-inf folder from.other rom and replace. Stock kernel wont work. Extract the zip of any custom kernel, copy system folder and boot.img and paste in the root directory of extracted files of rom. Zip back everything. It will work.
Click to expand...
Click to collapse
Yes exactly.
Do right as he said and your rom will boot.
Cheers.
tj_droid said:
After creating zip usi.g dsixda kitchen. Extract zip and copy meta-inf folder from.other rom and replace. Stock kernel wont work. Extract the zip of any custom kernel, copy system folder and boot.img and paste in the root directory of extracted files of rom. Zip back everything. It will work.
Click to expand...
Click to collapse
So I just replace boot.img with a custom kernel and start building from that?
or after creating the .zip I also have to copy the META-INF from another ROM?
Tovagulet said:
So I just replace boot.img with a custom kernel and start building from that?
or after creating the .zip I also have to copy the META-INF from another ROM?
Click to expand...
Click to collapse
Just replace META-INF in your rom with META-INF from Blackhawk(if stock rom) and make necessary edits.Your rom will work perfectly.I personally haven't had any problem by using stock kernel.
POTATO!!!!
Tovagulet said:
So I just replace boot.img with a custom kernel and start building from that?
or after creating the .zip I also have to copy the META-INF from another ROM?
Click to expand...
Click to collapse
Ok. Read carefully.
After creating the zip via dsixda kitchen. Close it and dont touch it at all. The follow the steps from my last comment.
Buddy.
Just upload your meta-inf..
and i'll look into it.
Got this problem before , it's because the assert command in updater-scripts do not support boot.imgs larger than 4MB .
Just remove the assert() and replace the commands in the proper format (replace commas at the end of command with semi-colons) as well as grab a proper update-binary , your boot.img should work .
Sent from Ursa's claws.
CallMeVentus said:
Got this problem before , it's because the assert command in updater-scripts do not support boot.imgs larger than 4MB .
Just remove the assert() and replace the commands in the proper format (replace commas at the end of command with semi-colons) as well as grab a proper update-binary , your boot.img should work .
Sent from Ursa's claws.
Click to expand...
Click to collapse
I'm working on a Samsung Galaxy GT-B5510, having the same problem trying to install custom ROMs and kernels. All failing with the same error you describe here. However, when I edit the script and rerun it, it does not throw an error but it looks like the kernel is not replaced. The only thing I didn't do was change the update-binary. What do you mean by a "proper" one?
Thanks.
MrRimmer said:
I'm working on a Samsung Galaxy GT-B5510, having the same problem trying to install custom ROMs and kernels. All failing with the same error you describe here. However, when I edit the script and rerun it, it does not throw an error but it looks like the kernel is not replaced. The only thing I didn't do was change the update-binary. What do you mean by a "proper" one?
Thanks.
Click to expand...
Click to collapse
The ones inside the custom ROMs where flashing a custom kernel has been a success in
I give up writing anymore signatures.
Hello community,
I'm currently trying to modify the stock rom for my GT-I8200n. I didn't find cwm for the S III mini VE, and the version of twrp I found was very buggy. So I need an odin-compatible flash file for my rom. I tried to modify the stock rom by downloading the .tar.md5 from sammobile, unpacked it with winrar and copied the system.img into an ubuntu-VM. After that I created a sys.img (or sys.raw, same problem) out of system.img using the simg2img-file I found somewhere here on xda, mounted sys.img (or sys.raw) and modified it. Then I unmounted it and used img2simg to create my system_new.img. Copied it to my windows system, into the unpacked stock rom folder, renamed it to system.img, overwriting the old system.img and packed everything into a .tar file using ZArc. Now while flashing my ROM, odin works on the system.img for some minutes and then shows a fail.
Does anyone know what I'm doing wrong?
P.S.: I tried simply using simg2img on my stock system.img and then - without mounting and modifying - used img2simg kn the sys.img file. Same problem with odin and I noticed that my new system.img is approximately 50 mb smaller than the stock img, although I didn't modify it.
I hope I described my problem well (I'm not an english native speaker, but did my best to make this text understandable )
Any ideas or hints that could maybe solve this problem are welcome.
Thank you,
Chris
I have the same problem
any solution ?
Hi there, I am trying to create a flashable zip of stock rom, the newest UBPLP firmware, I extracted everything from original md5 packace, converted to ext and mounted as virtual image and so on, took system and preload things, then csc stuff from cache.img, created a zip, all permissions etc etc, I have some experience.
Everything works except the fact there is no signal and wifi can't connect, can't really understand what's wrong, I know I am missing something, already tryed also flashing modem, kernel and so on, but nothing, baseband is unknown, but everything is fine with efs and imei, flashing another rom solves everything.
I really would be grateful if someone can explain me how to do this or can supply with a flashable zip of that firmware, odexed or deodexed, doesn't matter, I would like to learn how to correctly make stock rom flashable from zip package
Pdevo said:
Hi there, I am trying to create a flashable zip of stock rom, the newest UBPLP firmware, I extracted everything from original md5 packace, converted to ext and mounted as virtual image and so on, took system and preload things, then csc stuff from cache.img, created a zip, all permissions etc etc, I have some experience.
Everything works except the fact there is no signal and wifi can't connect, can't really understand what's wrong, I know I am missing something, already tryed also flashing modem, kernel and so on, but nothing, baseband is unknown, but everything is fine with efs and imei, flashing another rom solves everything.
I really would be grateful if someone can explain me how to do this or can supply with a flashable zip of that firmware, odexed or deodexed, doesn't matter, I would like to learn how to correctly make stock rom flashable from zip package
Click to expand...
Click to collapse
Try SuperR kitchen: http://forum.xda-developers.com/chef-central/android/kitchen-superrs-kitchen-t3202296 .
Thank you @#Henkate, after lots of testing I found out the problem was in some symlinks in /system/bin folder corrupted, so the only way was to use nandroid backup and take everything from there
Have u created the flashable zip[email protected]
sm_adil said:
Have u created the flashable zip[email protected]
Click to expand...
Click to collapse
Sorry for huge delay!
Yes, I did