Kingroot works on the Sunset like a charm, but I can't seem to find any info for recovery or roms. Tracfone version of the phone L33L it is a confirmed c50. C50-trf-us as said in build prop. Looking for info to get Leon's twrp for c50.
Related
So here is the thing: bought myself second hand 4 month old K3 Note. This device is really awesome and i really, really love it!
Previous owner stated that he ordered it online (GearBest or some other shop, i don't recall exact name).
And here is where it gets tricky with me trying to upgrade it to MM:
- in system settings it says it's Lenovo K50a40
- sticker under battery says it's Lenovo K50-t5
- IMEI numbers in system info do not match those on sticker on the back of phone
- serial number is SN:00000000
- ROM version is K50a40_S205_151118_ROW (5.0 Android)
- TWRP version 2.8.7.0 is working
- phone is not rooted...
- after OTA downloads its patch, phone reboots into TWRP, but i get error message saying: This package is for "Lenovo K50a40" devices: this is a "Lenovo K50-T5".
Now, i have read here on XDA various and confusing forum posts regarding flashing/OTA upgrades/lost IMEI and stuff, and i am really not sure about the way how upgrade is done properly.
Since i can't imagine i am the single living person with this kind of problem, i am looking for kind soul to help me out. :good:
Many thanks in advance!
Reserved.
Hiya mate. Since you already have TWRP on the phone, better to just download one of the newer MM roms listed on the Index Thread and flash it from there. No need to bother with firmware coding technicalities. I just flashed cuoco92's 1619 MM rom last nite. Works better that the S424 MM I had on before. Only thing is, some chinese crap still lingers in the rom. Get it here : https://www.facebook.com/cuoco92/posts/1741176056126330
Also, regarding the hardware, both a40 and T5 are the same thing just branded differently for different markets.
Thanks for replying. I have an older version of TWRP, does this matter when flashing marshmallow?
Sent from my Lenovo K50a40 using XDA-Developers mobile app
Technically it shouldn't but to be on the safe side, best to upgrade to TWRP 3.0.0.2 first since that version works with pretty much every rom available be it zip or backup format.
Yeah, it's working. Thanks for advice. I will be posting here once i'm finished with testing.
Hello people,
i bought a Galaxy S5 with the model number G900T3 and want to install AOKP on it. (https://forum.xda-developers.com/galaxy-s5/unified-development/rom-aokp-mm-t3293839)
This is the first time i want to flash my smartphone and i couldnt find any idiot-proof answers to this. :/
Now my concerns:
I'am in Germany. According to SamMobile is the G900T3 a model for the USA. Will this cause any problems? Will i have problems with a Sim-Card of another provider then T-Mobile?
Can i use the rom for the "normal" klte model?
Will the Custom ROM remove the T-Mobile branding?
Thanks for your answers.
Read thru that thread https://forum.xda-developers.com/tmobile-galaxy-s5/help/difference-sm-g900t3-sm-g900t-rom-t3329337 to get more info on the T and T3 model.
The post #8 https://forum.xda-developers.com/showpost.php?p=66025221&postcount=8 describes the steps to install a recovery and a ROM afterwards.
You should be fine with a klte version because SM-G900T is in the supported devices list here https://wiki.lineageos.org/klte_info.html
For the recovery you can probably also use the current TWRP 3.1.0 . It worked fine for me on a SM-G900F. You can find it on their Homepage. There are many guides around how to flash it with Odin.
At the moment I would recommend you to use lineageos over AOKP because latest nightlies of AOKP get stuck while booting.
If you want to use AOKP anyway use the zip from 2016-03-08. It is the last known working.
About which carrier you can use with a custom ROM I just don't know.
All at your own risk & good luck.
Thanks for your answer.
I think you meant the 2017-03-08-version, right? I would have gone with the latest Marshmallow-version because i thought it would be the most stable.
You're right 2017, not 2016.
I'm not so sure about how actively the MM version is maintained. The first post of the thread https://forum.xda-developers.com/galaxy-s5/unified-development/rom-aokp-mm-t3293839 states the newest release to be 2016-08-03 but on basketbuild there the most recent MM zip is 2017-03-10.
By the way, the Nugat Release is currently without a active maintainer. That's probably also the reason why the newer release don't boot.
Only the fact that there are new nightlies on AOKPs every day is unfortunately no clear indicator that they actually work. That's because AOKP has a automatic build system that runs without human interaction but can't test them on a real device.
So I just bought an LG V20 US996 (not US Cellular version). I have TWRP installed, and then I installed LineageOS nightly 20170825 and found that the battery meter is stuck at 50% regardless of charge, but more importantly, the touch screen no longer works. Same thing with nightly 20170901. However, after downloading all the nightlies and trying them, I found that the July ones work just fine (ie 20170728, 20170714, and 20170707). Someone on reddit suggested it might be an issue of not having the latest firmware. I did find here at lg-firmwares.com/lg-us996-firmwares that lists the US996 kdz files. It looks like the US Cellular version is more updated than the regular USA version. Is it safe to flash a US Cellular version onto a not US Celllular version even though they're both US996 ?
There are several things to take into account.
First, is you boot loader unlocked using the unlock.bin, or are you using the engineering aboot?
Nevermind. Someone already posted a regression ticket for this. It should be fixed eventually. The person who did it flashed a different kernel and it worked. It appears it might be an issue with the stock kernel.
* UPDATE * I just flashed 20170908 and then flashed the 20170728 kernel and it works. So it must be the more recent stock kernels that are the issue.
trouble with sensors
Hi everyone, just wanted some help.
i flashed my lg g6 h870ds with various firmwares because i was in a boot loop. but none of them work with the proximity sensor, acceleroneter etc etc.
am i flashing the wrong version? if so, how do i find the correct version.
i believe its a taiwanese version from eglobal central but im not 100% sure. i've had no success with imei checkers.
heres the firmwares ive tried;
H870DS10b_00_OPEN_HK_DS_OP_0406 - boots but no working sensors
H870DS10c_00_OPEN_TW_DS_OP_0426 - boots but no working sensors
H870DS10e_00_OPEN_TW_DS_OP_0724 - doesnt boot
H870DS10m_00_OPEN_TW_DS_OP_1019 - doesnt boot
am i missing something? thanks in advance
so i've gone onto the csmg imei checker and its given me :
<model>LGABCD</model>
<suffix>XABCXX</suffix>
no other information! im stumped....
can anyone help?
Flash newest open cis. Works for me coming from twn version.
TLDR: Samsung N920F seems to be a N920T, and you can flush ROM from N920T.
Recently my friends asked to help them with their Galaxy Note 5 which was bought somewhere in China. It was stuck at Android 6, with last updates from 2016, and seemed to have some malware (factory reset did not help).
It was really strange to see model N920F - I checked many threads here, and everyone says that there should be no such version as N920F:
https://forum.xda-developers.com/note5/help/note-5-n920f-n920t-t3310411
https://forum.xda-developers.com/note5/help/settings-sm-n920f-boot-loader-sm-n920p-t3776224
https://forum.xda-developers.com/note5/help/note-5-sm-n920f-eu-variant-please-help-t3527449
https://forum.xda-developers.com/note5/help/sm-n920f-stock-roms-t3482405
https://forum.xda-developers.com/note5/help/note-5-european-version-sale-sm-n920f-t3190929
Unfortunately, not even one of those topics found any reason for this or solution for updating. So I tried to find out the true and update phone myself.
At first, I booted to recovery. And there I saw that it model name was nobleltetmo - same as for N920T.
So I tried to install TWRP from N920T via Odin. TWRP successfully installed but phone stopped booting and TWRP only booted but did not work - it told me about bootloader version mismatch. So I found out that phone's bootloader version was N920TUVU4DPK6. So I tried to find a working firmware for this bootloader version and found it on xda: https://forum.xda-developers.com/tm...eral/stock-n920t-stock-n920tuvu4dpk6-t3518252
Fortunately, I could enter download mode and flush it with Odin. After it, phone worked fine, and now it was officially N920T. But even better things awaited - after updating it managed to fetch fresh updates! So I downloaded and installed them. Phone updated... And found new updates... And about 10 times again like this. Finally, I got the latest official Samsung Firmware with Android 7.0 - and it works flawlessly. Even Googe Play, NFC and banking services. I suppose that after this I could flush TWRP again because bootloader version also updated - but official firmware was quite okay so I didn't want to set up Lineage OS.
By the way, I think that I could find latest firmware and flush it with Odin in one go - but I didn't succeed in finding it.
Please beware that this N920F turned to be N920T - but your one can be another (N920V or N920P, for example)!
Now I am pretty sure that F in model version stands for "F***ed up".
So check bootloader version and be accurate.
jehy_rus said:
TLDR: Samsung N920F seems to be a N920T, and you can flush ROM from N920T.
Recently my friends asked to help them with their Galaxy Note 5 which was bought somewhere in China. It was stuck at Android 6, with last updates from 2016, and seemed to have some malware (factory reset did not help).
It was really strange to see model N920F - I checked many threads here, and everyone says that there should be no such version as N920F:
https://forum.xda-developers.com/note5/help/note-5-n920f-n920t-t3310411
https://forum.xda-developers.com/note5/help/settings-sm-n920f-boot-loader-sm-n920p-t3776224
https://forum.xda-developers.com/note5/help/note-5-sm-n920f-eu-variant-please-help-t3527449
https://forum.xda-developers.com/note5/help/sm-n920f-stock-roms-t3482405
https://forum.xda-developers.com/note5/help/note-5-european-version-sale-sm-n920f-t3190929
Unfortunately, not even one of those topics found any reason for this or solution for updating. So I tried to find out the true and update phone myself.
At first, I booted to recovery. And there I saw that it model name was nobleltetmo - same as for N920T.
So I tried to install TWRP from N920T via Odin. TWRP successfully installed but phone stopped booting and TWRP only booted but did not work - it told me about bootloader version mismatch. So I found out that phone's bootloader version was N920TUVU4DPK6. So I tried to find a working firmware for this bootloader version and found it on xda: https://forum.xda-developers.com/tm...eral/stock-n920t-stock-n920tuvu4dpk6-t3518252
Fortunately, I could enter download mode and flush it with Odin. After it, phone worked fine, and now it was officially N920T. But even better things awaited - after updating it managed to fetch fresh updates! So I downloaded and installed them. Phone updated... And found new updates... And about 10 times again like this. Finally, I got the latest official Samsung Firmware with Android 7.0 - and it works flawlessly. Even Googe Play, NFC and banking services. I suppose that after this I could flush TWRP again because bootloader version also updated - but official firmware was quite okay so I didn't want to set up Lineage OS.
By the way, I think that I could find latest firmware and flush it with Odin in one go - but I didn't succeed in finding it.
Please beware that this N920F turned to be N920T - but your one can be another (N920V or N920P, for example)!
Now I am pretty sure that F in model version stands for "F***ed up".
So check bootloader version and be accurate.
Click to expand...
Click to collapse
Same prob here malware and pops up ads in N920F. And device cannot be registered for updating. And odin says its N920K. If you have any link help me.
Mynouddin said:
Same prob here malware and pops up ads in N920F. And device cannot be registered for updating. And odin says its N920K. If you have any link help me.
Click to expand...
Click to collapse
I think you can try this rom: https://forum.xda-developers.com/note5/general/rom-lineageos-15-1-note-5-android-8-1-t3737405
If it is not compatible, you can enter rescue mode and check bootloader version.
jehy_rus said:
I think you can try this rom: https://forum.xda-developers.com/note5/general/rom-lineageos-15-1-note-5-android-8-1-t3737405
If it is not compatible, you can enter rescue mode and check bootloader version.
Click to expand...
Click to collapse
Thread closed
I need your help.
I am very glad to find your article because i ve the n920f and am really ****ed up.
How can i find my recovery code to know which model am on. I will be very glad if you can help me out. Thanks
Nanakwameampong said:
I am very glad to find your article because i ve the n920f and am really ****ed up.
How can i find my recovery code to know which model am on. I will be very glad if you can help me out. Thanks
Click to expand...
Click to collapse
Download this app it will show you your correct software and model.
https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo