Hello,
Please help me with this.
I have a AMOI N828 MIUI 4.2.1 JB ROM(latest update) which I wanted to port to my device with ''Exact same specs'' . I used the S4UI ROM as my base as it is the only perfect ROM. I then successfully ported using the ROM porter tool...>>(http://forum.xda-developers.com/show....php?t=2276871). Applied about 5-7 tweaks. I was quite skeptical whether it would install via CWM but it installed flawlessly. And when booted up it shows the MI logo and is stuck there.
Help please.
Go back and take a copy of the ported rom before the tweaks and flash, see if it bootloops
it it does bootloop then its not ported properly
if it doesnt bootloop then it is probably the tweaks
Warped420 said:
Go back and take a copy of the ported rom before the tweaks and flash, see if it bootloops
it it does bootloop then its not ported properly
if it doesnt bootloop then it is probably the tweaks
Click to expand...
Click to collapse
If it does bootloop then how to port it properly?
http://forum.xda-developers.com/showthread.php?t=2314836&page=44
go to my thread and post your question to bcrichster or pukeup
Pros at porting
If you aren't on a team
join LEGION MODZ
hit thanks on post # 75
Related
I have started porting MIUI v4 using Proxuser tutorial here.
So first I used CM9 nightly (cm-9-20120629-EXPERIMENTAL-i9300-BLED.zip) rom as base and SII MIUI v4 official from miui.us And no luck...:crying: (Stuck at Boot logo using base or MIUI libandroid_runtime.so).
Then I used the same base but Nexus S (Crespo) MIUI v4from MIUIAndroid and the same :crying: (Stuck at Samsung Screen using MIUI libandroid_runtime.so and stuck at boot logo using base libandroid_runtime.so)
After that I used unofficial SIII AOKP rom here as base and Nexus S (Crespo) MIUI v4 and same no luck.. :crying:
I uploaded my LOGCAT here.
So please I want someone to tell me what wrong I did and help me finishing the port..
Pmed
Sent from my GT-I9300 using xda premium
I guess your thread is still relevant, but I am attempting to port 4.1 MIUI to the S3... unfortunately, I may have similar problems, but minus a 4.1 ROM for the S3 to port from... I figured the GNexus build was a place to start, but I presume that's also the reason I get stuck at the MIUI logo and the rom never boots.....
Followed instructions from 2 separate port threads very closely..... anyone know how to help from here?
kickassdave said:
I guess your thread is still relevant, but I am attempting to port 4.1 MIUI to the S3... unfortunately, I may have similar problems, but minus a 4.1 ROM for the S3 to port from... I figured the GNexus build was a place to start, but I presume that's also the reason I get stuck at the MIUI logo and the rom never boots.....
Followed instructions from 2 separate port threads very closely..... anyone know how to help from here?
Click to expand...
Click to collapse
Hi there just try to pull Logcat and paste it in your post or pastebin or as an attachment and I could help...:good:
Any dev ready to port this ROM
http://forum.xda-developers.com/showthread.php?t=1588145
I already made it boot but the thing is it has many FC's ....and bugs !!!
Any one can deodex the RC2 from that post ?
Dear Team,
I have made a rom for micromax cabvas knight. I fact i have made two roms. 1 miui and one lewa.
I picked g4s lewa rom and miui kitkat rom and made necessary changes acccording to miui porting tutorial.
The problem is , it ports sucessfully but after boot logo screen goes blank.
i am sure its related to boot.img. i followed the boot.img unpack and repack to resolve bootloop problem. There is no boot loop but only blank screen.
Can someone help me.
Regards
Nishikanta
Nishikanta Mohanty said:
Dear Team,
I have made a rom for micromax cabvas knight. I fact i have made two roms. 1 miui and one lewa.
I picked g4s lewa rom and miui kitkat rom and made necessary changes acccording to miui porting tutorial.
The problem is , it ports sucessfully but after boot logo screen goes blank.
i am sure its related to boot.img. i followed the boot.img unpack and repack to resolve bootloop problem. There is no boot loop but only blank screen.
Can someone help me.
Regards
Nishikanta
Click to expand...
Click to collapse
​Bro u should try porting a rom which is based on mt6592.
If u want to port the lewa os try porting THL phone rom bcoz it has mt6592 processor not a gs4 rom coz it does not have Similar processor..and prashant is currently working on a miui v6 kitkat based rom so i think u should try porting a lewa os rom to canvas knight.
Hi
I have tried porting many roms for mtk 6592..
I always get stuck at CM logo or boot animation.And if it goes to the next step it gets stuck at
"Android Is Upgrading:"
"Starting Apps"
I have searched forum after forum thread after thread without any solution
ROMS that I have tried
1.Mystic OS v5.0 For Xiaomi Redmi Note 3G.zip
2.Xperia Mix CM 12.1 For Infinix X551 by Dennnis Murimi Wachira
3.CyanogenMod_11_Ported_to_SKK_Mobile_Lynx_by_Jhommark_Macasaet
4.CM-11_For_MT6592_Ajit_mtkroms-com.zip
5.NAMELESS_Miui_v7_5.10.8_for_CX100_by_Yow_Mike.zip
Most of the ROMS were downloaded from MTKRoms
I have android kitchen setup properly.
I have stock rom Version 4.4.2
I have MTK DroidTools Setup(I know How to use it).
I have SP Flash Tool Setup(I know How to use it).
I have TWRP Recovery Installed.
Please help me port this rom.
The Stock ROM (working Perfectly is available from here )
http://www.needrom.com/download/qmobile-noir-x600/
Thanx in advance
Edit:
I am adding the logcat of the CM rom that got till "Android is Upgrading"
http://ge.tt/7gV4Gja2
Hello guys, i have a Samsung Galaxy A3 2016 (SM-A310F) and my stock rom is Advanced three (Ported from advanced seven for a7 2016 that is ported from note7) and i want to port this rom:
https://forum.xda-developers.com/samsung-a-series/development/rom-a5-2017-grace-ux-t3531719 from A500G 2015.
I ported this and got bootloop.
I tried the fix with replacing the lib files.
But unfortunately this method didn't work too. Can you please help me? I don't have any ideas how to fix this.
how do we know what have you edited.
Moving everything to new Rom is not call as porting. Kernel is an issue obviously
mikasu said:
how do we know what have you edited.
Moving everything to new Rom is not call as porting. Kernel is an issue obviously
Click to expand...
Click to collapse
I used this guide: https://forum.xda-developers.com/showthread.php?t=1908008
And there is an actual fix for the bootloop