yashsingh1/xdaforums huggingface dataset:
[K3 Note General] FrenzyR:
any help please
[K3 Note General] adikri:
Can I fix sensor by it..?
[K3 Note General] sandeep.sethi:
try removing tfa folder and see
[K3 Note General] sandeep.sethi:
for sensor

bin/

akmd**** files

lib/hw/sensor

lib64/hw/sensor
[K3 Note General] Flounderist:
Porting P9000 Eragon V3.0 on UMI Super

Hello and thank you for the wonderful guide. I just bought a MTK device and I am discovering the porting jungle...:silly:

Do you think it is possible to port Eragon ROM for Elephone P9000 on UMI Super?

Same Chipset (MTK6755), same RAM, but different Camera (Sony vs. Panasonic, 13mp both).

I tried a porting but I have a doubt. In the porting ROM the build.prop is the P9000 one....it is right?

Do I have to chance manufacturer and device?

I assume I could use build.prop file of UMI Super.

Am I wrong in some step?

I have not so clear if I heve to use META-INF folder of my stock ROM, or the one of the port ROM (I extracted system.img and I didn't found it).

If I would like to use the Ulephone Vienna camera (same of UMI, a little better), which files I should take?

Sorry for the silly questions, I am 99% noob :laugh: Thank you again for your time!

p.s. any change to see CM13 on this chipset? Do you know if some 64bit MTK devices already have it?
[K3 Note General] sandeep.sethi:
this much long question haha

yes mt6752 has cm13 use build.prop of port

use stock meta inf

for camera i cant be sure that u can use ur stock camera app
[K3 Note General] Flounderist:
OK, how to get stock META-INF?
[K3 Note General] Flounderist:
Bro, I ported CM13 from Elephone P9000 to super using your guide.

do I need to edit build.prop file changing manufacturer, model name etc?

Plz can you help me? I don't want to brick my phone, will wait your answer before flashing. :D

here is the copy of CM build.prop file

https://drive.google.com/open?id=0BzvAF-6zwoYwVjliVU5ESTFYRXM

and here is the UMI build.prop file

https://drive.google.com/open?id=0BzvAF-6zwoYwTjVrbUhJdE1VNTg

here is CM13 updater script, mounting points are the same for both devices (check on build.prop).

https://drive.google.com/open?id=0BzvAF-6zwoYwNUgyOFg1NGNMOG8

Big up for [MENTION=6236982]Deepflex[/MENTION] for all the hard work :highfive:

thx again for your support!
[K3 Note General] CyanonyMous:
such I am trying to carry a rom cyanogenmod for zte a410 I perform all the steps of the guide but do not start me stays in the logo animation've tried everything and nothing works for me that could be the problem
[K3 Note General] sandeep.sethi:
check if the kernel is same
[K3 Note General] sandeep.sethi:
use cm13 build.prop
[K3 Note General] CyanonyMous:
if it is the same kernel x64 mt6735m however carries it and stay in bootlop
[K3 Note General] sandeep.sethi:
if u r porting same chipset try replacing whole hw folder of lib and lib64 onlty and firmware

and boot.img only kernel
[K3 Note General] CyanonyMous:
by replacing the kernel installation is in bootlop me unbootable
[K3 Note General] Flounderist:
Hello, I tried to flash the ported ROM, but i get error 7 on TWRP 3.0.2 while installing.

no damages to the device, restored with backup.

Feel free to download and try some improvement. 99% is due to error in META-INF file.

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

Cheers!

Edit: I tried a second build changing only the kernel file in boot and removing assert line in updater , as per [MENTION=6236982]Deepflex[/MENTION] info. This flashed but device stuck in boot logo.

Restored again, now on stock.

I will try another boot.IMG later on
[K3 Note General] Flounderist:
Replace uneventd.rc file from ramdisk. :highfive:

Also edit default. prop using stock settings.

Replace init.rc
[K3 Note General] CyanonyMous:
not work just gave me bootlop:confused::(
[K3 Note General] Flounderist:
Dont know on mtk6755 works. Try replacing also files specified in OP.
[K3 Note General] mburukamau:
ALWAYS REMOVE RECOVERY-FROM-BOOT.P before you do anything else.

What's boot.p and where is it located to enable me remove recovery?
[K3 Note General] sandeep.sethi:
its present in the system directory of your rom if not present skip
[K3 Note General] el7is:
Awesome thanks. redmi note 2. from Mokee & RR is porting to k3 note. but bluetooth is FC.

help me plz.
[K3 Note General] sandeep.sethi:
replace the files as in the image here
[K3 Note General] el7is:
[MENTION=5450421]sandeep.sethi[/MENTION]

Ok. Many thx. I'll try.

---------------

no. it didn't work. :(
[K3 Note General] baboufret:
I port MTK6735m on other phone rom to my phone Leaogoo Elite 4 Mtk6735M too. All work fine excepte i have bad pixel on screen, and app launch slowly. Plz how can i fix that.
[K3 Note General] sandeep.sethi:
check the selinux

and for pixel try replacing libinput
[K3 Note General] sandeep.sethi:
ou

i think u skipped some replacement libs then
[K3 Note General] Abhisek2002:
Are MT6752M and MT6752 are same?

Please reply
[K3 Note General] baboufret:
I port MTK6735m on other phone rom to my phone Leaogoo Elite 4 Mtk6735M too. All work fine excepte i have bad pixel on screen, and app launch slowly. Plz how can i fix that.[emoji20]

I try both not working for me
[K3 Note General] baboufret:
I try to port cm12.1 from Lava A1 Mt6735 to My devices Leagoo elite 4. All work except sim card don't mount, and i have baseband unknow, no imei
[K3 Note General] ibasha66:
Thank you for this wonderful guidelines...

I have ported your K3 Note miui ROM to my Lenovo K4 Note!!

But After the Lenovo Symbol Phone fully went black.

I did exactly as you said.

My TWRP recovery mode is still working...

Help me to solve this problem..

Thank You in Advance

Sorry for my poor English
[K3 Note General] sandeep.sethi:
according to my study k4 note doesnot have 5.0 kernel so u cant port miui (uses 5.0)
[K3 Note General] gsser:
tried to port once and messed up partitions twice. thankfuly service changed mothetboard in guarantee.

c5 ultra e5553 uses mt6752 and there is no rom support. it will be getting marshmallow soon. it only has twrp recovery but there are no roms.. device is very good but no one cares.... :(

can someone port roms like miui or cm13 ? we would like to donate too.

sorry if i bump or post wrong section.. i wasted so many time opening threads bumping them etc..

if you need files like boot or system it can be found in xperifirm app
[K3 Note General] sandeep.sethi:
pm me
[K3 Note General] gsser:
okay ^_^
[K3 Note General] Parthib:
i need cm 13 (64 bit mtk) rom for porting ..

MT6735
[K3 Note General] sandeep.sethi:
search needrom or use google my thread is for porting not for providing liks :)
[K3 Note General] Teblakuda4o4:
Does this guide work for porting between android versions aswell? Eg. Stock 5.1 to cm13

Same processor.
[K3 Note General] akinis09:
camera bug

i successfully ported infinix x600lte xos to my lenovo k3 note using your guide, so far every thing is running smooth. antutu rating is 49132, the major bug am facing with this rom is the camera. whenever i switch on the camera it respond with cant connect to camera and have tried replacing all lib files relating to camera from system/lib & lib64 without any success, i also tried replacing all the line containing camera on boot project.rc from stock to port but still yield nothing. thanks for this guide
[K3 Note General] Simon Jun:
Hi! I'm porting from redmi note 2 to lenovo k3 note. In RMN2 rom have some file .img. Should delete it?
[K3 Note General] sandeep.sethi:
except boot.img u can delete other img no problem
[K3 Note General] Jansxel:
How to Fix Sensors ?
[K3 Note General] sandeep.sethi:
akmdxxx files from bin and yamaha file if present
[K3 Note General] yui90:
Hii sir, i follow your guide, but always stuck in boot logo..

Any solutions.?
[K3 Note General] Flounderist:
Try porting uevent.d in boot file. Also edit default.prop in boot using stock parameters.
[K3 Note General] sandeep.sethi:
can u explain more like from what chipset u are porting and to which chipset and android version.
[K3 Note General] yui90:
I try porting rom euphoria os 5.1.1 from redmi note 2 to my device mt6735 with base CM12.

Can you help me.?

---------- Post added at 02:52 AM ---------- Previous post was at 02:49 AM ----------

Thanks sir.

Btw, ireplace uevent.d with my stock uevent.d.? Or compare.?
[K3 Note General] Flounderist:
Just replace.
[K3 Note General] yui90:
Thanks sir, btw how to fix stuck on "Android Starting".??
[K3 Note General] Flounderist:
It seems to be in bootloop. Check if you ported proper libs
[Galaxy S 4 Themes and Apps] qareembizzle:
S5 Had arrived update for marshmallow by mistake so i make a theme for old touchwiz launcher but with container (folder that 3rd apps be in with new mm firmware)

Like stock s4/s5/note3 etc.​

(QContainer) is the name of this Theme.

This Theme is for Old Touchwiz launchers and stock launcher too by follow this guide

This Theme contain:

For Some Screenshots

Instructions:

-Just install theme like normal apk

-Then choose it from themes in launcher

-Apply theme and enjoy it.

- Will be an updates and another themes soon with new marshmallow icons :o

Download Link
[Galaxy S 4 Themes and Apps] Usama707:
S5 MM Doesnt have those ugly boxes in icons of 3rd party apps like FB etc so kindly remove those
[Galaxy S 4 Themes and Apps] dragson:
Work good

tahnks

How do I add more themes
[Galaxy S 4 Themes and Apps] andrei1412:
Please make full icons for Galaxy Apps, SideSync, S6 S-Memo and Smart Manager, thanks.
[Galaxy S 4 Themes and Apps] androider hypero:
Is there going to be an update! Because could you remove the boxes on other apps and add memo & smart manager icon if the update launches please give me an apk you won't have to give me an apk if you don't want to but *PLEASE REPLY TO ME* thanks
[Galaxy S 4 Themes and Apps] mafiachat007:
S4 i9505 Does not support themes in launcher
[Galaxy S 4 Themes and Apps] RazOne:
It does. You can enable them. Google it and you ll find how!
[Galaxy S 4 Themes and Apps] brokendreams23:
im thinking going back to stock i9500 lollipop will i able to use this theme ? i cant remember stock i9500 supports touchwiz themes or not
[Galaxy S 4 Themes and Apps] RazOne:
Nope. But you can enavble them by editing some csc files
[Galaxy S 4 Themes and Apps] brokendreams23:
umm how can i do that ? can you give me a simple instruction or link ? also its odd despite stock i9500 support themes and samsung doesnt let us :/
[Galaxy S 4 Themes and Apps] Deathvirus:
Here

You can find my work with S6 Marshmallow icons and not the 3rd Party squares.
[Galaxy S 4 Themes and Apps] androider hypero:
Updates please?
[Galaxy S 4 Themes and Apps] androider hypero:
Pretty Please!

I wish there was an update to QContainer 2.0 I will rate a million if you do!:) Just can't wait any longer
[Fire TV Q&A, Help & Troubleshooting] 85gallon:
I want to unblock the updates so I can get Alexa. I am currently using Kodi and I am on software version 51.1.63_user_blahblah. I am not sure how that version number translates to the versions listed in the general forum (ie. 5.0.X format)

Will it wipe out Kodi and will I have to reload? Or will it leave it intact or will it ruin using Kodi.

Why would I want not want to upgrade? EDIT: It is a fire TV, not a stick.
[Fire TV Q&A, Help & Troubleshooting] deanr1977:
Questions for you-

1.Is your Fire Tv rooted?

2. Fire Tv gen 1?

3.You want to update with root?

4.Or without root?

5.I take it you want your Fire Tv on OS5 software?

What ever firmware your on at the time being Kodi is not blocked or un-usable, on the AFTV2 you can root upto the latest firmware, there is gonna be a OS5 rooted rom (software) available soon from the Developer called rbox, he's just finished the AFTV2 version & he said he will make the OS5 version for the AFTV gen 1 user's soon. You don't have to have a rooted device to run Kodi.

Hope this helps If so press that thanks button
[Fire TV Q&A, Help & Troubleshooting] 85gallon:
This is terrible, but I did it a long time ago. I don't think I am rooted. I think I just pushed kodi on it and then I ran something or ran some shell commands to stop updating. I know I should know!! LOL

I have gone through 3 computers and 6 hard drives to find out if I downloaded a utility to root. But I can't find anything but the download of the kodi .apk. So I am pretty sure I am not rooted.

I am not rooted. Didn't an update take out rooted units a while back? I remember reading that and installing kodi without root.

But I did something to block the updates.

1.Is your Fire Tv rooted? NO

2. Fire Tv gen 1? YES

3.You want to update with root? If I can avoid root I would like to. I play with enough devices. LOL

4.Or without root? YES

5.I take it you want your Fire Tv on OS5 software? Where are you getting the OS version? Mine shows as in my original post.

Now I just have to figure out what the hell I did to block updates. Off to the search window.......
[Fire TV Q&A, Help & Troubleshooting] deanr1977:
Start here mate -

http://www.aftvnews.com/start/

Check the compatible root serial or update number on your Gen1, if you blocked updates You "should" have root still? If you have root I'd wait then update when rbox brings out the rom for the OS5 software which will update you to the latest firmware. Or you could get a free app on your phone that needs root (es explorer or file manager & try to use r/w in the file manager Or turn on root settings) sidelong it to your fire tv, if it fails you don't have root.

Hope this helps If so press that thanks button
[Nexus 7 (2013) Q&A] OrBy:
SD insight says mine is using a Toshiba chip:

Model 016g92, size 16gb, manufacture Apr 2013.
[Nexus 7 (2013) Q&A] k23m:
The third brand - I updated our stats. Thanks a lot for your post!
[Nexus 7 (2013) Q&A] mydian:
Mine also says Toshiba chip that was manufactured June 2013. I purchased it in November of 2014.
[Nexus 7 (2013) Q&A] k23m:
Would you be able to check if dmesg log of Toshiba's chip matches model number in the app? My N7 has HBG4e in dmesg and the app.
[Nexus 7 (2013) Q&A] quickdraw86:
Mine also has HBG4e in dsmesg and the app... Also may 2013.
[Nexus 7 (2013) Q&A] Tmzdroid:
I don't think this flash memory problem is mainly on Kingston equipped Nexus 7's. I previously had a device with hynix flash and it would bootloop/restart/hang at Google logo endlessly so I exchanged it for my current device (with Kingston memory ) which runs superb. Is there any way of measuring degrading flash memory over time if there is I'll do it or anything else to solve this issue.

I still have nearly 2 years warranty so am willing to be a Guinea pig.

So after nearly 2 years of daily usage my device is still running like a champ I haven't noticed any performance slowdown over time ?. The touchscreen response improved after I replaced the battery a while back I'm guessing it had something to do with the ribbon cable or the small circuit board attached to the battery ?.
[Nexus 7 (2013) Q&A] k23m:
I have Hynix N7 which had a bootloop but this was my fault, I think, because I disabled a service. Now it runs CM12.1 and no more OTAs.

Yes there is a way of measuring flash memory just like SMART in HDD - it was introduced in eMMC v5.0 as "Device Health Report" but our Nexus 7 is probably too old for it. I received a very detailed description of fuser-invent's bricked Nexus 7 with Kingston KE4CN5B6A chip which is eMMC v4.5, without the health report function.

Can you please check the production date of your Kingston? It is possible that only early units were affected and you have nothing to worry about. Kingston does not actually manufacture NAND flash and can use any component available for a product or just change it later.
[Nexus 7 (2013) Q&A] Tmzdroid:
It's July 2013 my previous device was pure stock 6.0.1 factory reset etc it wouldn't even turn on 50% of the time I messed about inside with the ribbon connectors and insulating tape and it improved a little. I had to wait 3 weeks for a replacement which I'm very happy with. Have a look at my previous xda posts you'll get the gist of what I'm saying.
[Nexus 7 (2013) Q&A] Erick Pontes:
i flashed on my nexus 7 2013 one 2012 rom, now he changed to grouper and i cannot use any rom from my 2013, how i go back to the 2013 rom ? since i have signature missmatch
[Nexus 7 (2013) Q&A] Tmzdroid:
Try the Nexus Root Toolkit (NRT) by wugfresh
[Nexus 7 (2013) Q&A] k23m:
I read your thread. It was a hardware fault but not of Hynix or other eMMC which, in Nexus 7 2013, fails either catastrophically or becomes unwriteable. It looks like a battery fault. The Nexus is almost 3 years old and statistically it is time for all batteries to go now.

Have a look at my second Nexus 7 2013, it was dead, unrechargeable and would not start on external power. I replaced the original 4Ah battery with 1Ah from an ancient phone. A much smaller battery was not an issue because I always use it with power supply. I have since changed it to 2x 1Ah batteries because the old 1Ah gradually started to do exactly as you describe: rebooting (a lot) also struggling to boot up while being fully recharged and constantly connected to a charger.
[Nexus 7 (2013) Q&A] mydian:
Here is my screenshot from SD Insight. How do I check with dmesg? When I type it in the terminal emulator I get pages and pages of stuff and am not familiar with what I'm looking at.
[Nexus 7 (2013) Q&A] k23m:
Please type the following in the terminal:

dmesg | grep mmc0

it will be probably - mmcblk0: mmc0:0001 016G92

Or use this open source app.

Either way do it asap after reboot because dmesg is buffered and soon overwritten.

Thank you for checking it.
[Nexus 7 (2013) Q&A] mydian:
Thanks that was much easier, and you are correct with what it says.
[Nexus 7 (2013) Q&A] k23m:
Thank you again. I updated the front page with Toshiba info.

:good:
[Nexus 7 (2013) Q&A] aungmyoswe:
i have too with Kingstone 32G EMMC

so so dead Asus Nexus 7 (2013) wifi :D

only, connect to computer it will " Qualcomm HS-USB DQloader 9008 "....and nothing , may be dead boot or damage emmc .If anyone have a good N7 2013 device, there is a way to backup the necessary files. Here....

so please,i need that files....:confused::confused:

thanks for reading and sorry for my english:D:D
[Nexus 7 (2013) Q&A] k23m:
Before you can use backup files, the first step is to switch from 9008 to 9006 mode. Does it work for you?

Would you be able to post the Kingstone's production date, the four digits...

:fingers-crossed:
[Nexus 7 (2013) Q&A] aungmyoswe:
Photo Here.....Kingstone emmc
[Nexus 7 (2013) Q&A] k23m:
Great shots, thank you, but the date code is under the sticker. If you intend to claim warranty, do not remove it.

Another user reported code 1244 meaning the end of 2012 while still working Kingstones are (so far) from the middle of 2013. It would be interesting to know if there is a pattern here - maybe a bad batch from 2012 only?

:D
[Nexus 7 (2013) Q&A] k23m:
"partition[30].size 27852783 KB" is Kingston, I updated our "bricked" logs.

THGBMBG8D4KBAIR (EMMC 5.0)

THGBMFG8C4LBAIR (EMMC 5.1)

These are confirmed 32GB replacements, and unconfirmed:

Samsung KLMBG4WEMC, KLMBG4GEAC

Hynix H26M64103EMR
[Nexus 7 (2013) Q&A] Dazmatic:
Yeah, it's a kingston chip.

I've just bought the USB adapter. What I'm going to do, simply because I'm intrigued as my N7 is now working with the replacement 16gb motherboard, is pull the 32gb kingston chip off the broken board, reball it and put it on the usb adapter loosely, as in hold it in place with tape or croc clip or something, JUST to see if I can get anything off it?

I did eventually via 9006 mode get my windows PC to see the 32gb kingston chip, but it wouldn't initialise it but that could be a hardware limitation of 9006 mode.

I've found the original chip on aliexpress for ~£11, so if I get round to it, I might try replacing it. a FBGA 169 socket is difficult, VERY difficult to come by now because I think the FBGA design has seen it's end of life and use, just not used anymore.

https://www.aliexpress.com/item/KE4...-3bbb-4e87-be85-a58fcc6beb7d&rmStoreLevelAB=3
[Nexus 7 (2013) Q&A] k23m:
Wait, we do not want the original chip ever again! Kingston has ruined this Nexus and the forum is full of horror stories because of it. Secondly, it must be from the old stock/bad batch and may fail like most of them. Finally, note the following:

Kingston eMMC partition[30].size 27852783 KB

Hynix eMMC partition[30].size 28180463 KB

My backup image is form a slightly bigger Hynix chip and it will have to be later re-adjusted to smaller Kingston in TWRP.

The 9006 mode is useless with broken Kingston chips but works just fine in case of software corruption...

https://xdaforums.com/showpost.php?p=71171478&postcount=141

I am skeptical about the "dry" chip-to-pcb connection attempt but I/we can't wait for the results of your experiments.

Cheers!
[Nexus 7 (2013) Q&A] Dazmatic:
The trouble is, the FBGA 169 or even 153 chips are hard to come by and the kingston chips are the ones that appear to be about still.

From my own research, it would appear to be the 5.1 update that's corrupting the chips which is what I believe was on this faulty one judging by the bootloader version 4.04.

That would mean, so long as I don't load 5.1 onto the chip, the kingston one should be fine? nonetheless, I'm going to attempt a dry fit to the USB adapter first, failing that i'll solder it but only because I know that you can only really solder to a PCB a few times before it starts getting flaky.
[Nexus 7 (2013) Q&A] k23m:
Here is FBGA 169 32GB Hynix https://www.aliexpress.com/item/H26M64003DQR/32753213381.html

and alternative chipset USB controller https://www.aliexpress.com/store/pr...e-phone-handset-eMMC/1049678_32831762964.html

The 5.1 update had not corrupted Nexus' Hynix nor Toshiba eMMC chips. The update(s) have nothing to do with it, except they initiate massive flash cells re-write and expose bad chips, like the Kingstones - "Kingston is revealed as simply a vendor that re-marks other people's chips in its own packaging... Effectively, Kingston is just a channel trader and is probably seen by SanDisk/Toshiba as a demand buffer for their production output. I also wouldn't be surprised if SanDisk/Toshiba was selling Kingston 'A-' grade parts, i.e., parts with slightly more defective sectors, but otherwise perfectly serviceable."

https://hardware.slashdot.org/story/10/02/16/1454246/
[Nexus 7 (2013) Q&A] Dazmatic:
AH, I see, well thanks for clearing that one up. I did think it was a bit bizarre how the update trashed the flash because flash itself is inherently reliable because it's basically an SD card or USB stick or something like that? It's just NAND memory with a built in controller and the controller conducts all of the error checking and bad block blocking.

Thanks for the link for the Hynix one too, does look interesting and it too was also on my list of chips to try.

I can't honestly say I'm willing to spent a ton of money on it? I've bought the USB adapter, I've got a 16gb board I can pull copies of flash off if need be, I know you've got a 32gb image for a hynix flash also but that's just the bootloader if memory serves me right so I'd still need an image to put on.

For now, I'll see if I can get any life out of the existing 32gb chip, I'm doubtful but I'll try nonetheless as its dead regardless. If I get no joy, I may try the hynix chip. The main trouble of it all is actually getting an image on to the chip, even through USB. I have got an FT2232H board on order for another project (reading bare nand) which has JTAG functionality (not that I know anything about it) which may also be able to help that just needs MORE research and more time.

Certainly appreciate your help however!
[Nexus 7 (2013) Q&A] CzasowAnton:
Hello!

After probe of re-partitioning the partition table, I bricked my Nexus 7 2013 4G tablet. :(

Only black screen, no reaction for buttons, and "qualcomm hs-usb qdloader 9008" on device manager.

Its a possible to repair via QPST? I'm trying, but it shapes not so good...

Sorry for my bad English. :)

Thanks for help. :)