yashsingh1/xdaforums huggingface dataset:
[Android General] Jitheshwar:
Bro I suggest you not to flash ROM since case of bootloop (which is common while porting) you have no chance to restore system from recovery since you're not able to boot into recovery manually. Try recoveries in this thread and also report to the Developer of the recovery that you're not able to boot into custom recovery but you're able to boot into stock recovery.
[Android General] AddyRoxxzZ:
I'll to port recovery from this post now, i had picked one them and ported but touch was not working so i picked another one from different source SUDroid page and it worked for me. What's your opinion, Porting from kitchen will make any different or should i try some other recovery for porting coz apart from getting into it from boot rest everything is working perfectly
[Android General] Jitheshwar:
will you give the link of the recovery that you're using from SUDroid . Have you ported that SUDroid's recovery or flashed directly?
[Android General] AddyRoxxzZ:
I just checked it's not sudroid, i got it on rom claims LINK then i ported it using this post's method, ported recovery LINK .

From sudroid i got cyanogenmod 12.1 but i can't figured out how to port it plus it's a lengthy process to revive my device again after bootloop coz i don't have a working recovery from boot.
[Android General] Jitheshwar:
I'll tell you easiest way.

First port Boot.img of CM12.1

-unpack both stock and CM12 boot images delete CM split_img and replace the ramdisk/lib/modules with stock boot modules grab mali.ko from /system/lib/modules of stock ROM.

That's it replace the boot.img of CM ROM with the ported boot.img and then flash the ROM from recovery.

This method should work it worked for me may also work for you.
[Android General] AddyRoxxzZ:
I'll try and post you results
[Android General] AddyRoxxzZ:
I've ported another recovery from this source and its working great even from hardware keys. backed up my current system and now flashing ROMS.

Thanks for your support. now working on cyanogenmod
[Android General] Mihirgaurav394:
help please

Please create custom recovery for lava x28:confused:
[Android General] AddyRoxxzZ:
SC 9832A????
[Android General] @redwolf:
Thanks for this tutorial

But i need help

Try porting twrp..some of them work but can't read extsdcard

Porting nova hero..but i got no simcard issues...no audio at all...can't detect extsdcard..

Porting lewa...no simcard issues and no audio at all

Can anyone help me please?

I'm new in porting ;)

---------- Post added at 04:20 AM ---------- Previous post was at 04:15 AM ----------

My device sc7731

Lollipop 5.1

And i replace boot.img port from stock

When i don't replace it...my phone only show white screen

---------- Post added at 04:29 AM ---------- Previous post was at 04:20 AM ----------

And some recovery..."the system cannot find the batch label specified - ~1"...that message show when i unpack recovery.img
[Android General] AddyRoxxzZ:
There is no split_img in it. Provide your built so I'll port that one.

Thanks in advance
[Android General] Jitheshwar:
Port the boot.img, this will fix most of the issues.

Regarding recovery:

Which tool are you using to port recovery? Are you using phone/PC? If you're using some other tool try to use AIK (latest version) available for PC as well as mobile, search on XDA.

---------- Post added at 06:13 AM ---------- Previous post was at 05:15 AM ----------

grab the boot.img from the ROM which you want to port and then unpack it you'll see both ramdisk and split_img folders​(every boot.img will have split_img but​ if you are using some other image kitchen other than AIK you'll see the contents of split_img but they will be out side the folder. After unpacking images you may seen that one folder named ramdisk and some files like boot.img-kernel,boot.img-dtb etc if you use AIK these files will be organized in split_img folder
[Android General] @redwolf:
[MENTION=8028840]Jithe[/MENTION]swar

I use carliv pc

Just nova hero can't detect extsdcard..

No sim issues is fix...its something wrong with my simcard..i replace with new simcard..

Try porting fazfap..."proses.com.android.phone has stop"..i got that eror

No audio with all rom...but there is audio on headset....

Thanks for reply

---------- Post added at 08:35 AM ---------- Previous post was at 08:28 AM ----------

I'll try porting recovery using aik

Give the report soon

---------- Post added at 08:45 AM ---------- Previous post was at 08:35 AM ----------

Try twrp 3.0.2 using carliv

Version mokhtar abid

Extsdcard 0mb...i can't thick/choose it

Twrp on my other phone can read that sdcard...means nothing wrong with the sdcard

---------- Post added at 08:52 AM ---------- Previous post was at 08:45 AM ----------

Is this how to port boot.img?is it work for all device or just CM?

Delete split_img?just delete it or replace with stock?
[Android General] Jitheshwar:
As I said first port the boot.img unpack boot.img of port rom replace split_img of port rom with stock rom and files in ramdisk/lib/modules of port rom boot.img with stock at last repack it flash the boot.img using fastboot/TWRP/Flashify in most cases this will fix the crashes like com.android.phone and storage int/ext sdcards.

For audio make sure you have replaced files under system/lib/hw and libaudioservice.so,libtinyxml.so,libtinyalsa.so and in etc tiny.xml audiohw,audiopolicy,codecpga. If this doesn't help replace every file named libaudio***so under system/lib.

For fixing 0mb disk space issue change the mount points of twrp after unpacking the recovery the mount points will be in ramdisk/etc/twrp.fstab change them according to your stock recovery in stock recovery file name will be as recovery.fstab.

Porting boot.img will be same for almost all ROMs but some times we have to edit some files to fix bugs and bootloops but in case of CM12 the boot.img is already ported to be compatible with all most all spreadtrum phones with sc8830/7731 by Hadi here we have less work just replacing modules and split_img and repacking it and it's done. You can also port many manufacturer ROMs also using this method.
[Android General] @redwolf:
Got it...i'll try that..

Thanks alot
[Android General] nikhilpal2705:
Is there Marshmallow based rom(like cm13)?

My device is Android 6.0 having sc9830.
[Android General] Jitheshwar:
try to port the ROMs of Samsung devices this requires lot of patience, little bit knowledge about porting ROMs and kernel (boot.img),debugging when you won't able to boot after (use adb ). For finding the compatible ROMs search like Samsung CM 13/14 followed by chipset.
[Android General] AddyRoxxzZ:
I don't have mali.ko in my stock boot.img, what should i do now ?
[Android General] Jitheshwar:
Grab it from system/lib/modules
[Android General] AddyRoxxzZ:
Could not find 'Meta-INF/com/google/android/update binary' in the zip file

Got the file mail.ko too and replaced that as well
[Android General] Jitheshwar:
:confused: Every flashable zip does have updater-binary but in few cases developers adds flashing related scripts in updater-binary as shell script in those cases also you'll see updater-script but inside you'll see lines like "this is dummy file updater-binary is a shell script" or something for ex:SuperSU.zip. make sure you have downloaded the proper zip file without errors while downloading or try to download other ROM.
[Android General] AddyRoxxzZ:
I've download it from SU-droid, will you please suggest one for our chipset coz i got this only for our chipset, the exact same rom is also available on needrom
[Android General] Jitheshwar:
look in Advan S4p official Group you'll find CM12.1 ROM,as per my knowledge,the Admin (Hadi) of that group had made these Samsung ROMs compatible to work on almost all Non-Samsung SC8830/7731. you'll find​ many ROMs in that group you can also try CM13.1 and some other CM based marshmallow ROMs.
[Android General] @redwolf:
Can i port kitkat cusrom to lollipop phone?

I want xperia z lollipop

Can anyone help me?

Guide me porting kitkat to lollipop phone

Or give me link to xperia lollipop

Spreadtrum chipset

Thanks

---------- Post added at 04:10 PM ---------- Previous post was at 03:45 PM ----------

Report

No luck on recovery still 0mb

Audio fix...work like charm

Auto rotate still not working on lewa after i flash fix file

Sony rom can't read sdcard...both internal and external

Can you give me link to cusrom xperia z lolipop

Or guide to port that kitkat xperia rom to lollipop if possible

Thanks
[Android General] Jitheshwar:
You'll not be able to port KitKat ROM to lollipop device since the bootloader doesn't support and the kernel's sepolicy and most basic things has changed that that leads to no chance in booting KitKat ROM to a lollipop device.

Don't bother about the Xperia ROM try CyanogenMod 12.1 and even CM 13 will support for lollipop devices (just need to modify little bit in stock lollipop boot.img) that's it you can use the great CM ROM(one of the best custom ROM out there) with negligible bugs, you can get it at Advan S4p official group on FB. If you still want the Xperia ROM do a search on Google followed by our chipset you may get one.

Regarding 0mb storage on recovery:

Is your device shipped with lollipop or you have updated it to lollipop using any ports or something or you got update from manufacturer later.

Upload the recovery.fstab from stock recovery ramdisk/etc and twrp.fstab from TWRP's ramdisk/etc this will reduce my work to help you, if you don't know what these things are then just upload both stock recovery and custom recovery and provide me with links ( mega/drive will be preferable)

For fixing auto rotation don't flash that fix as it is replace the files in the rotation for l fix zip files with stock ROM files after that flash it.

For fixing storage bug replace storagelist.xml in framework-res.apk of port ROM with stock Rom storagelist.xml you'll find this file in xml folder of apk after extracting it, not sure that this will fix the storage bug but give a try if this isn't worked then unpack the stock boot.img then replace replace init.storage.rc file in stockboot/ramdisk with the port ROM's init.storage.rc if you don't see this file in Port ROM (this will surely exist in stock) then you have to port the boot.img also for this just unpack port boot replace split-img of port with stock split-img after that replace ramdisk/lib/modules that's it flash that ported boot.img wipe dalvik-chache Reboot this should fix storage and many bugs in Port ROM.
[Android General] @redwolf:
My device is shipped lollipop

I'll upload my stock recovery later

I have cm13...it's marshmallow base..i dont know how to port

I've port boot.img

Don't know how to extract system.ext4.win

I extract with winrar...make some change...but i can't repack it..

Still looking info with no succes

Can you guide me?

---------- Post added at 07:33 AM ---------- Previous post was at 07:21 AM ----------

And my device had a very very very bad data signal

Its working good with wifi

Data signal is killing me:(

Can i fix it?or its hardware problem?

---------- Post added at 07:46 AM ---------- Previous post was at 07:33 AM ----------

https://mega.nz/#!kqgWnSRD

---------- Post added at 07:47 AM ---------- Previous post was at 07:46 AM ----------

Its my stock recovery

---------- Post added at 07:48 AM ---------- Previous post was at 07:47 AM ----------

Replace the file in rotation?which file?
[Android General] Jitheshwar:
After modifying the system.ext4.win you have to compress it as .tar not in .zip format after there you have to compress the META-INF,syatem,data,boot.img and system.ext4.win as .zip format alternatively​ you can use AromaFM.zip (a recovery file manager):usage is just flash the AromaFM​.zip in recovery then you'll see UI of recovery based file manager with core options that a root explorer will contain like deleting/moving/replacing system files while in recovery itself you can also change the permissions of a file

Is this bad signal problem occurred in stock ROM?

Have you flashed any modes for stock ROM?Are you facing this issue recently? If yes try to flash your device using SPD or research download tools (do backup first). If this is occurring Port ROMs this might be because of the modem which is different to different devices and different to same device of a different carriers technically we can't do anything to fix it, except replacing ril related files from stock to Port, since you're porting the ROM not building​ it from source. Also make sure that the network you're using had good signal strength in your locality try to use another network notice the difference, if any, some Networks will not be fully compatible with some devices and also see whether any firmware updates available for you due some bugs in modem/kernel/system files which search for signals,etc otherwise it would be hardware problem there will be less chance of fixing the hardware issue in your case unless you have any replacement option/warranty.

You provided the link without description key copy link with decryption key in mega without decryption key I can't use the link.

The files with name of files in rotation fix zip.
[Android General] @redwolf:
https://mega.nz/#!kqgWnSRD!jG7mljtzOYyLIq6PiE4ncb7tmNCu_t_8ShcShvBAjAM

---------- Post added at 09:47 AM ---------- Previous post was at 09:43 AM ----------

Is it right?

Its says complete link

---------- Post added at 09:50 AM ---------- Previous post was at 09:47 AM ----------

Extract system.ext4.win with winrar but the data and system folder is empty...is it right?

---------- Post added at 09:50 AM ---------- Previous post was at 09:50 AM ----------

Extract system.ext4.win with winrar but the data and system folder is empty...is it right?

---------- Post added at 10:10 AM ---------- Previous post was at 09:50 AM ----------

This is how i port boot.img cm13...is this right?

Should i format it as .tar or leave it as .img
[Android General] Jitheshwar:
Yes that's what I needed.

I need the custom recovery too that you are using. Compress it before uploading. And some screenshots of external and​ internal storages taken using Diskinfo.apk

those folders are for show no need to worry about them. don't modify the system.ext4.win instead flash the ROM directly in recovery without modifying except replacing ported boot.img after completion of flashing process flash AromaFM.zip and then replace system files with the stock ROM files (you have to copy important files need to boot the ROM in easily accessible folder in SDCard) after that exit from Aroma reboot into system now CM 13 should boot.

don't format the image file as .tar you have to leave as it is.
[Android General] @redwolf:
Copy important file..i did like page 1...is it enough or anything else?
[Android General] Jitheshwar:
what important file? is it the recovery.fstab you talking about?

I need to modify some partition path of custom recovery to make work properly in your device so please give me the link of custom recovery that you are using I'll try to fix the bug. Then I'll upload fixed recovery here.

What's about page1 I didn't get you. Are you talking about listed recoveries out there?
[Android General] @redwolf:
I means replacing system file

Tutorial porting rom on page 1

Is there anything else that i should replace?
[Android General] Jitheshwar:
no that will not work with CM ROMs go and look in Advan S4P group you'll find guide for booting CM 13 don't need to replace any file just port the boot.img that's enough but for fixing bugs you have to replace some libs not all the files like in stock based ROMs. See in Advan group you'll find guides in fixing bugs.
[Android General] @redwolf:
Got it

I'll report soon
[Android General] Jitheshwar:
Bro I need custom recovery also provide me that then only I can help you.
[Android General] @redwolf:
Got it

I save it on my pc

I'll upload soon

I havent use pc for today

On the way home:laugh:

---------- Post added at 01:51 PM ---------- Previous post was at 01:42 PM ----------

https://mega.nz/#!NvQWUaQK!W8Cl9sTOmK8C3T0irF4a4fokY9EIMOveHi0gVLP17G4

---------- Post added at 02:20 PM ---------- Previous post was at 01:51 PM ----------

I dont use facebook:laugh:

What about wiping?data dalvik cache?or i should wipe system to?
[Android General] @redwolf:
No luck....stuck on boot logo
[Android General] Jitheshwar:
Stuck? Make sure you have wiped dalvik-cache,cache and system. Which tool you are using to port boot.img? If you are using any other tool to port Use AIK it is easy to setup (just extracting the contents to desired directory) and easy to use (drag and drop to unpack double click to repack) consider to use AIK-MOBILE which is a time savour which lets us modify ramdisk on-the-go with less efforts (if you already know about this tool it's good). And tell me how you posted boot.img. While porting ROMs other than AOSP based we have to concentrate on booting first rather than fixing bugs so don't replace any file in stock except mali.ko in system/lib/modules I think this file was moved to ramdisk/lib/modules of CM boot.img by the guy who made it compatible to non-Samsung devices if you're not replaced this file while porting then you have to replace it this is one of the core module of system, apart from this you don't have to replace any file. Even after that if it's not worked then there may be more chances that it may be incompatible with your device. And one more thing I have seen that your device is SC7731 but the ROM is made for SC8830, you may have seen files like init.sc8830.rc not files as init.sc7731.rc(which may be your stock boot file), I this may be causing the issue is we are confident by our side the only way to port to your device is cross-porting I don't know about this not sure it will work on CM and CM based ROMs.
[Android General] @redwolf:
I did replace mali.ko from syste/lib/module

But i dont wipe system :o

I'll try wipe it

If its fail..i'll give up :laugh:

Can you edit build prop?maybe can fix my signal data..a little bit better would be very helpfull

Its getting worse when i use paw rom

---------- Post added at 07:16 PM ---------- Previous post was at 07:13 PM ----------
[Android General] Jitheshwar:
I think build.prop has nothing to do with signal strength, build.prop contains only the frequency rate at which WiFi and mobile networks will be updated, these frequency rate will be predetermined by manufacturer tweaking it might have adverse impact on battery/performance and even low strength than now. The files and code responsible for mobile data and it's signal (WiFi as well) will contains in kernel,some libs and most part in modem (the baseband and wmodem) you may have seen the things in firmware .pac for when loaded in upgrade/research download tool.

I'll see what's​wrong in recovery and I'll upload it soon.
[Android General] @redwolf:
Thanks alot

Still no luck on cm...still stuck on bootlogo after complete wipe including system
[Android General] Jitheshwar:
have you modified anything in in system.ext4.win (even extracting and compressing)? From which site you downloaded that CM 13? Download it from Advan Group (I suggest you to create one FB account).
[Android General] Jitheshwar:
[MENTION=8387655]@redwolf[/MENTION]

I took a look at stock as well as custom recovery that you provided to me. Everything thing related to SDCard seems to be normal to me. The problem may be with the SDCard that you are using. Make sure your SD Card is formatted as vfat only and nothing else since recovery may not be capable of detecting every file type (format). So try to format the memory card and check in recovery, if this ain't worked then try to use another SDCard.
[Android General] @redwolf:
My sdcard format is fat32

My other device twrp can read that sdcard

Maybe its just bad luck for me:o

Thanks anyway for helping me
[Android General] Jitheshwar:
Is formatting to vfat worked?
[Android General] @redwolf:
I use windows dont know how to format it as vfat

Only ntfs fat32 and exfat
[Android General] @redwolf:
Where can i find this file in stock?

To fix auto rotate
[Android General] Jitheshwar:
Don't know exactly but try to format the SD Card in phone itself and check whether it worked. And also try to format it from recovery from wipe options.

look at folders where the files of rotation fix contain for ex: if a file in fix.zip located in system/lib then look for the same file in the same path of stock ROM.
[Android General] Jitheshwar:
Hi all.

Please read my post completely.

I manually upgraded my phone(sc8830 chip) from KitKat to lollipop by using some kind of trail and error method. But I got some bugs namely camera can't connect, no audio output (no sound from speaker), some sensors are not working and few other negligible bugs but the major ones are camera and audio but luckily I managed to fix camera by using some other device's camera hardware libs (file under system/lib/hw) but flashlight is not working anyway I don't bother about but I need to fix audio bug for this I audio related libs and files to get these files I had to download ROMs of sc8830 mobiles randomly then use those files which is lot time taking and significant data charges. So I request all the users of this thread to upload the files of their lollipop stock ROMs by compressing them name the zip file containing those files with your device model please help me.

Files that I need:
in system/lib/hw folder
all files
in system/lib folder
files with name libaudio***.so
libhardware.so
libhardware_legacy.so
libtinyalsa.so
libtinyxml.so
in system/etc folder
audio_effects.conf
audio_hw.xml
audio_para
audio_policy.conf
codec_pga.xml
tiny_hw.xml

and if you have downloaded ROMs of other device them upload them also by zipping it with device name. The compressed zip file may be less than 10mb which will same my time and importantly data charges.
[Android General] @redwolf:
What about my rom?

Can it help?
[Android General] Jitheshwar:
Send me I'll try. If I fixed these bugs in lollipop I can update it further to Marshmallow. The speaker of my phone powered with Class-K Amplifier with Beats(I thing it might be Sony's beats technology just like lenovo having Dolby Atmos) I didn't find any sprd device having Class-K Amplifier so far because of that the libs of other devices are not matching with my device even the ones whose kernel(lollipop) is working on my KitKat device.

Apart from this there are two more options one building from source for which we need kernel sources and device which manufacturer is not going to provide and another one is editing the libs using HEX Editor because we can't edit libs directly from a text editor but I don't know what to edit in which file I have to edit. If we open a lib(even a 5kb lib) it look like too messy​.
[Android General] @redwolf:
Let me know if its work
[Android General] Jitheshwar:
I replaced libs the libs you provided but no luck. And one thing is in logcat app the audio related logs are showing less errors​ when replaced with your libs compared to stock libs and I have seen tiny_hw.xml( opened using text editor) there the lines are lot similar to my KitKat file there may be something​ is causing issue but don't know how to figure it if I came to know which is causing the issue I can focus more on it hope I'll fix audio and other bugs sooner just like camera bug

If you downloaded some other device's ROMs for porting then attach it's libs also. Please name the zip with the device brand and model since it will be easy to figure out which device's libs worked (in case it worked) and then I'll download that ROM and see If there is a chance of fixing in other bugs
[Android General] @redwolf:
No

I just download custom rom that provide on page 1
[Android General] Jitheshwar:
ok then send those ROMs file
[Android General] Akidbz:
how to fix wifi bug in lewa os. chipset : SC9830

Help me with the wifi bug in lolipop (Lewa OS)

Chipset : SC9830
[Android General] Jitheshwar:
Make sure you have replaced all files under modules of lib folder and in boot.img /ramdisk/lib/modules/ all files and in etc folder all files related to WiFi.