yashsingh1/xdaforums huggingface dataset:
[Android General] 7awliet:
Porting From RR 5.6.8

What do you mean by "base" specifically, that you ported

from

RR 5.6.8? If so, what do you

port from

to make RR 5.6.8 in the first place? Or did you download the RR 5.6.8 from the first page?

Also, any idea where the boot.img (or even the kernel inside it) came from that is used in your RR 5.7.0?

I'm trying to pin point the problems of the combinations of these porting methods that are about. Thanks.
[Android General] MithunSanthikumar:
Hi, Can you help me find a rom for MT8382.

My device is Lenovo A3300-GV
[Android General] babigabi:
Nope, I ported RR 5.6.8 for myself and as a base for it I used RR 5.5.9 v2 from here. Sorry the reply was for [MENTION=7523876]7awliet[/MENTION]
[Android General] 7awliet:
Source Of Port Files

Thanks for that, I appreciate it. I spent all day looking at every ported file and cross referenced them with different sources to find the optimal porting method.

So, now, the question remains was it the RR 5.5.9 v2 by opiz zipo or the one by DRT that you used?
[Android General] 7awliet:
So Close

I still can't figure out where you got the following files from:

libaudio.primary.default.so

libcamdrv.so

libcameracustom.so

boot.img

I've inspected just about every option, S030, S124, 5.5.9 v2 (opiz zipo & DRT), 5.6.8, 5.6.8 (mtkroms), 5.7.0, 5.7.0 (mtkroms), 5.6.7 Cam & OTG patch, 5.6.8 Cam & OTG patch...

If you got them from S023 - S029 or S117 - S123 then I give up - I've spent 2 days studying it and I'm just gonna pack it up hahaha.
[Android General] babigabi:
By opiz. Is more stable than that by DRT. This ROM is primary as a base when I I try to port something.
[Android General] 7awliet:
Anything Further?

You have anything on those particular files? I've been through Opiz Zipo thoroughly, but no cigar.

EDIT:

I've found where libcameracustom.so came from so that just leaves:

libaudio.primary.default.so

libcamdrv.so

boot.img

boot.img would happen to be a LuckAs kernel, would it? Whole or just the inner file?
[Android General] jhon roofi:
hopefull with vibe 2.1 ui

Actually i'm interested in this rom. But, is there another download link? Such as google drive or mega?thanks before
[Android General] aidz927:
can anyone link me to a complete tutorial to flash a rom

assume that I have 0 knowledge on anything

I used KingoRoot to one click Root,

I want to know how to unlock bootloader, install twrp or cwm(they are not supported on A5000 right), flash the CM12.1 Bugless V3 Rom, thanks
[Android General] northwindtrades:
1)We break up luckas and take the kernel/zimage from it and replace it to unpacked boot.IMG (of the ROM we want To port)

2)libcamdrv is in sytem->lib

3)I forgot about audioprimary it will be on the same directory as camdrv or system->lib->hw .
[Android General] Hazem Mostafa:
Porting issues

Today I was porting a Cyanogenmod 13 rom from MTKroms as Qwerty@ said in a tutorial in page 73 , downloaded the rom , replaced the files and set the mounting points in updater script , but found that there was 4 mmcblk0p to edit , so I made them like the resurrection remix 5.6.8 posted here (first mmcblk0p is set to 6 , second set to 7 , third and fourth set to 6) , and replaced the boot.img in the downloaded rom from the cam and OTG fix for RR 5.6.8 . so I repacked the rom and flashed it and flashed updated Gapps directly then cleared cache and rebooted . The rom started but at welcome screen , whenever I choose the language and select next it will restart the phone. what's the problem ? tried to flash the cam fix for RR 5.6.8 then starting the rom but it just loads at cyanogen booting screen then keep restarting. also tried with Slim rom but it is stuck at the starting screen for about an hour.

I am new here and don't have much experience in these things . Any help would be appreciated.
[Android General] 7awliet:
MT8382/MT6582 And Vibe UI 2.1?

First, you gotta determine which it is MT8382 or MT6582, you have to be certain first. MTK Droid Tools says one thing and another thing says another.

See post #915 - the .apk in the top right corner of that site - that's one way to find out. Try something else other than Droid Tools and try to provide a screenshot or pic that shows it's either MT6582 or MT8382.

You might as well go to the original post #807 and read from where it says "Also, in the very top-right corner..." (use Ctrl+F in your browser to located that sentence) and read those to paragraphs.

Remember to get back with the link to your test upload or a screenshot or pic of something, anything. Hope that's of any use.

---------- Post added at 11:42 AM ---------- Previous post was at 11:28 AM ----------

I've heard of Vibe UI 1.5 and 2.0 but not 2.1. Is it new? Do you have a link for it anywhere?
[Android General] 7awliet:
Found The Culprit

http://4pda.ru/forum/index.php?showtopic=663798&st=3480#entry49660840

So it was Scout who ported that RR 5.6.8 on the first page all along?! I thought it was HarlequinUA when I saw it on 4pda.ru...

Well at least I know now, I'll wait for him to be free from exams to ask him about those porting base files.

Wishing Scout the best!
[Android General] Hazem Mostafa:
[MENTION=7523876]7awliet[/MENTION] well that may be the problem , but I also tried to set it like you say , system is 6 , data is 8 which was like in the Cm13 ported here by kemo , still no luck and restarts after touching next in the welcome screen . I said it maybe the boot.img fault so i used the one in Cm13 here as both of them are cm13 , but no luck.
[Android General] MithunSanthikumar:
This " http://specdevice.com/showspec.php?id=178c-7a33-362d-310e0033c587 " is the link to my tab's specs.

Even Though it says MT8382 in CPU info tabs there's MT6582 written along the wifi information

Really confused, If it is MT8382 roms i should be looking for . I couldn't find any.

So what should i do now ?
[Android General] Pher-:
Guys exams are done! Sorry to let you wait too long, I used S030 as a base. But I used libs and vendors (excluding hw inside libs) from the Cam + OTG fix. Before I used the Cam + OTG Libs and vendors I copied libs from s030 first then just replaced them with the cam + otg fix. I'll be uploading SlimROM later on Google Drive

---------- Post added at 08:04 AM ---------- Previous post was at 07:10 AM ----------

https://drive.google.com/file/d/0BwJcBxTArUKDeVo3SDY5VExDdms/view

SlimROM, you can get A-Gapps on mtkroms.com page
[Android General] Mr.Đ:
[HELP] I can't flash rom

Format data --> flash zip = Bootloop

Factoryreset --> flash zip = Bootloop

Format data + system + cache + dalvik = Bootloop
[Android General] northwindtrades:
unpacking and repacking boot.img

The simply boot.img copy pasting method was only for RR ROM. You have to do the above method(its easier than setting up android kitchen).

Note : if your getting bootloop then you have to replace uventrc from stock boot.IMG to port boot.img

---------- Post added at 12:05 PM ---------- Previous post was at 11:27 AM ----------

I'm sorry but which ROM are you flashing again ?

Also what ROM where you on while flashing ?

---------- Post added at 12:23 PM ---------- Previous post was at 12:05 PM ----------

[MENTION=7523876]7awliet[/MENTION] can you tell me how to fix GPS/VPN in 6.01 pls? I couldn't make much of the 4pda thread sadly
[Android General] Mr.Đ:
I've try to install cm12.1 dev and cm 13

---------- Post added at 04:41 PM ---------- Previous post was at 04:34 PM ----------

I'm using android KitKat roll back from lollipop

---------- Post added at 04:42 PM ---------- Previous post was at 04:41 PM ----------

Should i upload pictures?
[Android General] 9jabasewap:
Scout, Go and Accept my Request to Download this SlimROM from Google Drive. And Pls Post d A-Gapps Link here
[Android General] Pher-:
Oh wait let me make it public

---------- Post added at 06:38 AM ---------- Previous post was at 06:37 AM ----------

Its already set at viewers can download

---------- Post added at 06:39 AM ---------- Previous post was at 06:38 AM ----------

You need to login to Google to download files on Google Drive.
[Android General] Pher-:
http://go.mtkroms.com/2o
[Android General] northwindtrades:
Doesn't look like your doing anything wrong.you sure you're giving it enough time?first boot takes a long time .

The only other thing I can think of is use twrp2.8.7 or v3 .the other versions like 2.8.1 and 2.8.5 did cause bootloop for me.

---------- Post added at 08:54 AM ---------- Previous post was at 08:43 AM ----------

sometimes you have to enable link sharing for the uploaded item so that others can download.

BTW do you know the files /apk/jar files that needed to be edited to fix GPS/VPN
[Android General] jkjones:
is there any update R-Remix v5.6.8

or much better Rom than this?
[Android General] northwindtrades:
Slimrom is good and there is RR 5.7.0 by gabi ,GPS and VPN fixed RR ROM is on the way
[Android General] jkjones:
Maybe I'll just wait for 5.7.0. Is it also MM?

If scout wants to share it he will... meh
[Android General] northwindtrades:
Yes its marshmallow .scout already shared his ROM ,he just forgot to enable link sharing in Google drive .(I forget that too most of the time)
[Android General] Pher-:
Link Sharing already enabled! Download all you can!
[Android General] Pher-:
I'm on S123 stock for a while now. And damn it we dont have compass sensor on this phone so this wont work on VR Box. But atleast I have my trusty ol' Xperia P to enjoy VR with
[Android General] Hazem Mostafa:
[MENTION=7387201]Qwerty@[/MENTION] Tried your method , set the mounting point to 6 8 6 6(as 6 is for system , 8 is for data) , followed every step in the porting guide in the rom site but no luck , the phone restarts after touching next . what is wrong ?

btw the ported rom is CM 13 that has bluetooth fixed (can't post the link as I am a new user) and the base rom is CM 12.1 bugless v3 by opiz that is posted in first page

also is there a way to flash a rom over an existing rom without removing data and apps without problems ?
[Android General] northwindtrades:
Then you're doing nothing wrong ,its a fault with the ROM (some ROM in mtkroms have bugs other than mentioned their site for our phone like write issues in temasek ,camera crash in all mm ROMs(now fixed) ) you'll have to go to the trouble of decompiling some system files using apktool (let's just say doing this isn't worth the time;)) try another ROM

As for overwriting without wiping the likely result will be bootloop (some versions of twrp also auto wipes before installing a ROM) better you make a backup and then restore the data after wiping.

BTW no one here has even tried the ROM you are working on ,you also tried slimroms right? Work on that ,if you're getting bootloop then replace uventrc in init folder of decompiled boot.IMG from stock to port
[Android General] 7awliet:
May have corrupted downloads, also, be careful when porting to choose right folders and files. Which port method did you use again?

Also, make sure you have enough space on your storage, on SD card too.

If the first page instructions for flashing are too muddled then I re-did them: #1029

The best thing you could do right now is try to get a FULL BACKUP (mentioned how to backup: #1029) of your device and extract the files then compare how different they are from the files in one of the ported ROMs on the first page (use WinMerge). That could give you an idea of whether your device may be compatible with MT6582 ROMs. Also, tablets are a lot different to phones, not just by build.prop.

May what to search/start a MT8382 thread for fellow users of your chipset. I've not heard of a fake MediaTek chipset - the real ones are dirt cheap :eek:

Hahaha thanks man. You probably already saw post #1031 but just check it out quick once more if you can 'cause this is I think is the 4th time I'm asking in this thread haha man it's getting muddy again.

#1021

#1023 - basically, the three files listed under the edited section are a question specifically to you (actually boot.img is a question for [MENTION=7326280]babigabi[/MENTION] but they may have used your 5.6.8 kernel, not sure)

#1030 - an important one

#1031 - reiterating

I'm just determined to get to the bottom of this :p

FORMATTING could cause you problems.

WIPING is what you should be doing.

WIPING system could cause you big problems.

READ: http://xdaforums.com/android/genera...overy-roms-t3316677/post67619328#post67619328

NOTE: 10-15 minutes the first boot could take for stock ROM flashing.

Well I was trying to wholly use babi's 5.7.0 boot.img into my 5.7.0 port (RR to RR) yet it wouldn't boot haha but thanks for that info. Once I get the answer from [MENTION=5283894]Scout919[/MENTION] and [MENTION=7326280]babigabi[/MENTION] I can possibly get started on the boot.img origins.

As for GPS/VPN fixes I'll get back to you on that. Everyone's just posting random stuff right now in the thread and it's hard to keep up, especially with partys yesterday and today ahaha :cowboy:

RR 5.7.0 HERE:

SlimROM HERE:

Use S124 - link

Qwerty's right, it's hard to help if we can't see what ROM it is exactly and also like they said - some ROMs have unlisted bugs. Try try what I said above though.

---------- Post added at 11:27 AM ---------- Previous post was at 11:19 AM ----------

PEOPLE try searching for your problem FIRST! Use the thread search box for your problem key word, keep it simple. If you can't use that search box because you don't have 10+ posts then Google something like: a5000 myproblemkeyword xda

That would search this thread for you via Google cache.
[Android General] northwindtrades:
"a5000 myproblemkeyword xda" this would keep same questions from popping up again. Anyone heard anything from kemo? This thread could use some maintanence like deleting the instructions on first page that was Google translated from 4pda and replacing them with 7awliets #1029 instructions.so new members could start customizing with less hassle.
[Android General] 7awliet:
Thread Maintenance

Haha I agree but I meant that that when people find this thread showing the problem through the search results, they'll hopefully read the solution in someone's reply to the problem. Basically, I meant someone would mention the problemkeyword in their solution post when replying. Like for example if someone is searching "lenovo a5000 xda mmcblk0p6 mount" and they click "More results from xdaforums.com", they'll come to http://xdaforums.com/android/general/lenovo-a5000-root-recovery-roms-t3316677/page100 - specifically #994 (I tested it) - which is a pretty good post. They can easily find the word on the page by using [Ctrl]+[F]. It always baffles me how people are skilled enough to be messing with updater-script files in extracted custom Android ROMs but don't know about using the find function of a web search engine, or a thread, or even their browser :laugh:

---------- Post added at 12:00 PM ---------- Previous post was at 12:00 PM ----------

I don't think Kemo is gonna be around any time soon haha, never spoken to them but I should.

---------- Post added at 12:02 PM ---------- Previous post was at 12:00 PM ----------

I'm just currently waiting on answers from [MENTION=5283894]Scout919[/MENTION] and [MENTION=7326280]babigabi[/MENTION] so I can continue my work. If we got paid for the work we did offline... hahaha you wouldn't believe...
[Android General] 7awliet:
No IMEI But Got 4pda

Every time I flash (I'm on TWRP 3.0.0.0) I lose my IMEIs. Right now, I don't even know if the WLAN and BT MAC Addresses are even mine. I really doubt it because those changed too.

I've still got my original IMEIs and S/N from the sticker on the box so I'll fix those right at the end but can someone tell me the first 6 characters on THEIR

original

(not downloaded) stock ROM for WLAN (Wi-Fi) and BT addresses, please?

Like just the X's in XX:XX:XX:__:__:__ and not the last six characters.

The first 6 are the chip's manufacturer, which ALL of us should have as the

same

.

Also, I got a 4pda account muhahahahahaha aaaaaaall the patches!
[Android General] northwindtrades:
WiFi - a0:32;99

Bluetooth-e0:2c:b2

So you can download the pathches from 4pda with an account but those who don't will get a error 404?

Flashing with some versions of sp flash tool (mines 5.1 and it doesn't) could result in a efs partition lost. But flashibg in twrp? That's new to me ,when the twrp starts for the first time did you check the leave system files unmodified mark?

Note: I looked this up on my phone but its not the stock ROM ,the imei is as it should be so I'm thinking the above address are okay as well.
[Android General] northwindtrades:
PS this is not me :silly:
[Android General] Hazem Mostafa:
[MENTION=7387201]Qwerty@[/MENTION] and [MENTION=7523876]7awliet[/MENTION] I don't know but when I tried the method of copying the boot.img to slimrom it gave me the bootlogo of the rom and kept loading , it didn't even start after an hour , so It may mean that I have screwed it from the beginning while the Cm13 started in almost every method and restarted after touching next in the setup wizard, whether it was changing the mount points or changing in the boot.img or both. I'm not experienced but I'm not drunk . :silly:

But I didn't try the method of replacing the files inside the boot.img with slimrom honestly , I have been experiencing all on cm13 , and I have flashed over 20 times in the past couple of days so I want to wait a little to see if there is a new rom to try porting , also then I would experience with slimrom and see what happens. [MENTION=7523876]7awliet[/MENTION] yes you're right the first site needs maintenance also yes I have to search first , but always I get some nonsense answers and nonsense topics , as you know almost of the topic followers are newbies like me and there is at most 3 ~ 5 experienced geeks here , asking a question and getting a specific answer is better for me than reading an unspecific question with not wanted answer then getting a softbrick, be patient body it won't cost you a penny but it would help others ;)

And to solve this , kemo should select the most frequent questions in porting or other and their answers , with the help of any geek here , say Qwerty@ , 7awliet or scout919 and write them on the first page . That would help a lot , save a lot of time and is better than searching.

Also if I may ask , how would gps and vpn bugs would be fixed? Isn't it kernel issues? And would it be for RR roms only?
[Android General] northwindtrades:
GPS and VPN bugs will be applicable to all marshmallow ROMs. Its just that following activities on 4pda is a pain.

And different ROMs may have different ramdisk files so simply pasting the boot.IMG won't work(sometimes it does ) ,you have to copy and paste the kernel instead (and if your getting bootloop then also uventrc)

Simply put GPS and VPN despite being kernel bugs can be fixed if we're to decompile both a mm ROM and also a working(GPS and VPN) ROM and comparing everything.this too is a pain since its a lot of time and you have to compare everything line.this is where 4pda comes in as they know where to look but with Google translate " look at that" "do this" "maybe do this" is really confusing. But since 7awliet already got a copy of patches GPS and VPN can be fixed with less hassle.now since theses patches are generally for 6582/6592 these can be applied to all marshmallow ROMs.

I think we can manually set up a VPN connection using orbot /psiphon already without any further patches in all ROMs released here.

[MENTION=7570298]Hazem Mostafa[/MENTION] truth be told your slimrom is at a better condition than cm13.you just have to replace uventrc too.

If you want upload the boot.IMG of the slimrom(unported ) and I'll make the changes nesseccary;). Or you could download scout's slimrom
[Android General] AndroidTiger25:
Do I have to be on KitKat to install resurrection remix 5.6.8 or can I do it on lollipop ??? :confused:
[Android General] northwindtrades:
Kitkat ,you know these are repetive questions right?
[Android General] Hazem Mostafa:
[MENTION=7387201]Qwerty@[/MENTION] so we have to wait till 7awliet gets it for us , and vpn setting through wifi isn't fully operational , it worked for me on spotify but not completely in other apps , not really helpful.

Well it's very nice of you Qwerty@ but I want to try porting for myself , and I already downloaded the one ported by scout , thanks champ !
[Android General] AndroidTiger25:
sorry about that but i really wanted to get this rom and hasn't been able too for a while now ...sorry again :o
[Android General] northwindtrades:
[MENTION=7523876]7awliet[/MENTION] can you upload those patches somewhere else ? I'd love to take a look at the changes they made:D
[Android General] Mr.Đ:
Flash zip failed, and then i can't start my phone

https://drive.google.com/open?id=0B0s24LAWQhsNckY5eG4yX2dDZ0U

https://drive.google.com/open?id=0B0s24LAWQhsNb1RiTENWRnpLQ3M
[Android General] northwindtrades:
Might be fault on my end but I can't view this .how did the flashing zip fail any error like error code 7 ?
[Android General] Mr.Đ:
I'll install your recovery and try again later, thank for your support
[Android General] 7awliet:
Addresses, 4pda, Porting, And Flashing

Again, I can count on you :) I appreciate that. It currently looks like that when we flash downloaded ROMs, that we end up flash other people's NVRAM, EFS, sec_ro, or sec_co no matter what fixes are available AFTER flashing the ROM. I've had 2 different address for both Wi-Fi and BT so far.

With downloaded S030:

WLAN = 00:08:22

BT = 00:00:46

S/N: NULL (or it was 0000000000000000)

Currently ported RR 5.7.0 from that very S030:

WLAN = 8c:77:16

BT = 44:8e:fb

S/N: 0123456789ABCDEF

So maybe it is my second set, but I need to collect more first to determine this. Also need info of what ROM yours is and ported from what.

Yes, I can download from 4pda ;)

No, I didn't check the leave the system files unmodified box. I was thinking that this would allow me to flash over the system partition (OS). Was I supposed to check it? :confused:

Haha I hear you :laugh: I think it's the timezone differences that make it like that. I sometimes want to take conversations to Telegram instead and then post (with permission and anonymous) the chat messages or any productive findings from that chat to the board to speed things up.

Well you know what to do then... Backup and get to porting that kernel in the way that you were told to. :)

I agree. ^ It may not seem like that but having to fix a problem that we've dealt with often that seems big is better than dealing with a problem that we've not seen before that looks small.

Ahaha I'll collate as many as I can first. Also if you need any specific downloads, drop me a mention or a PM and I'll try to download it for you. Also I could try helping you signup for an account, I should write up the updated specific details on how to do that.

TWRP 2.8.2.0? Where are you getting these from?

From the first pic it seems like your mount points are wrong/conflicting, updater-script or update-binary is corrupted/not readable, or that you zipped the ROM folder not the contents in the root of the ROM, or that your SD card is not compatible or set to some restrictions like and encryption password.

From your second pic it seems something was misedited in updater-script or updater-binary was touched... or that it's simply because you have TWRP 2.8.2.0 and not 2.8.7.0 or 3.0.0.0. Qwerty even told you about this in post #1041.

Make sure the file \META-INF\com\google\android\update-binary is untouched when porting (as in don't replace it) and backup then try TWRP 3.0.0.0 from the first page.

If you can't flash the 3.0.0.0 recovery.img from the first page in TWRP for whatever reason then here's (attached) a flashable zip I made of it that works for me.

Backup before you try it. Backup before you try anything really.

P.S.: Google Drive nor Google Photos links can't be parsed in the IMG tags. Only images that have the extension like .jpg directly accessible and their host sites don't require signin.

P.P.S.: Delete .txt from end of attached md5 file

P.P.P.S.: MD5 for attached A5000_TWRP_3.0.0.0.zip: 2efc1869ebf5d18d821fa8437e9d3c56