Hi. I've never really liked the Android version in my Lenovo but I am now facing an annoying issue with Play Store downloads getting stuck and delayed and going to have to reinstall.
At this point I am ready for a root and changing the ROM but I am rather lost in what android distribution are working and tested at the moment as after reading for a while there are some which are only for the Win version. I also see some references to X90L on threads about rooting and installing twrp but I am assumming these would work the same on my F version.
So the question is, what updated current ROMs are working fine and are worth (better than the official one) after root and TWRP on the Android version?
Also, once unlocked and changed bootloader, where can you get the official ones again?
Thanks for any help.
"Also, once unlocked and changed bootloader, where can you get the official ones again?"
You don't need it if you flash YB via Intel Flash Tool with oryginal rom.
Related
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 have a 32gb Amazon-variant XT1625 on MPJ24.139-48 with an unlocked bootloader and root. I want to update to Nougat, but it's looking like setting up to take the Amazon update is going to be a fair amount of effort; I'm wondering if it's possible to just flash the retail version of Nougat since it's looking like I'm going to have to go to a fair sum of effort anyway.
I've also heard that Moto G4 Plus ROMs will work on the G4, but I don't know the specifics on that.
i dont see why not as long as you already unlocked the bootloader prior to Moto(Lenovo) disallowed unlocking of amazon varients of the g4. heres a link to the stock nougat firmware
https://androidfilehost.com/?fid=673368273298955218
I flashed -64 retus software on mine and it immediately had two nougat updates afterwards. Still waiting for one that fixes the aboot sector vulnerability too but never know when that may come
Travisholt92 said:
I flashed -64 retus software on mine and it immediately had two nougat updates afterwards. Still waiting for one that fixes the aboot sector vulnerability too but never know when that may come
Click to expand...
Click to collapse
then you was able to flash retail version in a amazon prime phone? I have one and it dont boot if i instal a retail version.
di anybody actually get this working? I had the same issue as @iurd2007 I was able to unlock the bootloader just fine. The flash appeared to have taken successfully. But it just gets caught in a boot loop when trying to reboot the system after the flash. I followed the instructions here:
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
okay, so i've tried various roms both official and unofficial, as well as even the stock Nougat and Oreo flashable roms found here:
https://forum.xda-developers.com/moto-g4-plus/development/rom-oreo-8-1-0-soak-test-t3873367
So far, the only ROM i've been able to get installed is omni rom 9, but it keeps crashing several apps over and over on the setup wizard. I've read somewhere that using a different version of TWRP recovery image might help. I've tried the official TWRP recovery from twrp.me, the patched arm64 version found here: https://sourceforge.net/projects/tw...3-r1-athene-arm64_rajatgupta1998.img/download , also the latest version patched for efs backup/restore here: https://forum.xda-developers.com/devdb/project/?id=29106#downloads. So far the the one that seems to work the best is the third version of TWRP. It would be nice if all these custom patches made it back into an official release, but it's probably asking a lot of a phone that is almost 4 years old at this point. and a budget friendly phone at that.
im planning on installing a custom rom at the very least since the stock rom is giving me some software glitches. i wanted to know if theres any problem with the new update that would prevent me from rooting, or is just best to update to the newest version while its still on stock
shatheone said:
im planning on installing a custom rom at the very least since the stock rom is giving me some software glitches. i wanted to know if theres any problem with the new update that would prevent me from rooting, or is just best to update to the newest version while its still on stock
Click to expand...
Click to collapse
if your talking about the AT&T XT2 it can be rooted on any version
problem right now is Huawei's bootloader unlock page is gone and you'll have to try DC unlocker to pay for a bootloader unlock
I was talking about the original XT, I updated since I see most of the road support the latest version
I've just got a new Zuk Edge as a replacment for my broken one.
Unfortunately it runs on Android 6 ZUI 2.3. OTA option is disabled.
Since the site developers.zuk.com seems to be abandoned and does not send the file for unlocking the bootloader anymore I cannot flash via TWRP.
Are there any official downloads (either recovery update packages or QPST-images) for international roms with Android 7 or 8?
I searched everywhere but coudn't find any.
Pls help. Don't want to stick to android 6.
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