Related
First of all, I may be posting this in the wrong section. But I desperately need your help on this.
I got a Jiayu S3, and couldn't not try to flash a custom rom on it, so I tried with "Pure AOSP V1 TF".
All went well, untill i found this app which was included with the rom, "Kinguser" (should be Superuser, i believe), which game me the option to toggle root.
At first and only time I opened this Kinguser app, option root was active. I did deactivate it, and reactivated immediately after.
As soon as i reactivated root, the privacy pin screen showed up.
I didn't set any PIN on my phone, so at first i thought it could be something like 1111 or 0000. Tried 5 times and it made me wait 30 seconds. Then tried another 3-4 times.
Here began the real mess: "forgot pin" (or psw) didn't show up, but at the time i didn't even know about that recovery option.
I didn't know what to do, so I just thought that a factory reset would certainly solve the problem, how couldn't it? Well, wiped everything, but PIN lock screen didn't go away.
So, wiping everything, I also deleted my gmail account from the phone, and I lost the possibility to lock phone and give it a new password (Android Device Manager). Too bad at the time I didn't know about this recovery option as well...
Now I'm out of ideas. I think I've tried every method I could find with a search of "Smartphone PIN locked". Tried with resets, plugins, deleting files with adb..
How do I unlock my phone?
little update: after a factory reset, for 2-3 seconds, it shows the default initial screen, but it doesn't last more that and i just can't do anything.
Now i managed to bring back the stock rom, but with that i lost the twrp recovery, and i can't find a way to make pc recognize the phone to reflash it.
It seems it's going worse instead of better...
I had just bought this Jiayu S3 and planned to bring it on holidays on wednesday, but i'm starting to think i won't be able to fix it before then
Did you have any resolution to this problem. I am currently sitting in the exact same boat. Did the factory reset, pass code screen still there, I didn't set a pass code. Basically hands tied, can't update firmware, guessing i'll have to get a new phone, but hoping maybe you found a miracle cure! ha! - Thanks for any guidance. - Arden (Seattle, WA)
Just flash another rom (stock/original) and start over.
How have you done that?
Can you help please?
I tried factory reset (volume plus+ power button), hard reset (volume- plus power button), update, and nothing works; I also went to two different specialized stores and they failed to find a way to reinstall the original Android version or a recent one.
Comparing the files with the factory version installed in the phone, the phone report identified three changes:
- a new file: /system/priv-app/7mK0T6e8Z5.apk
- the lost of a file: /system/app/com.android.fallen.apk
- and a modified file: /system/bin/debuggerd
AzulFogo said:
How have you done that?
Can you help please?
Click to expand...
Click to collapse
To flash firmware you can use SP Flash Tool on a windows or linux computer (not sure about macosx). You have to decide which firmware you want (which one do you have now?). The 'official' firmwares can be found on needrom. SP Flash Tool can be found there as well. There are 2 popular LP firmwares built by Jiayu resellers in Europe (Xtreme from Spain and Jiayu.de from Germany). Guides on how to flash are often present at the place where you find the firmware.
Dior DNA said:
To flash firmware you can use SP Flash Tool on a windows or linux computer (not sure about macosx). You have to decide which firmware you want (which one do you have now?). The 'official' firmwares can be found on needrom. SP Flash Tool can be found there as well. There are 2 popular LP firmwares built by Jiayu resellers in Europe (Xtreme from Spain and Jiayu.de from Germany). Guides on how to flash are often present at the place where you find the firmware.
Click to expand...
Click to collapse
Thank you!
I found "Xtreme from Spain":
needrom.com/download/rom-xtreme-rom-tf/
I found the "SP Flash Tool":
needrom.com/download/sp-flash-tool-v5-1424-00/
but it is for Linux... can you send me the link of the windows version?
And I could not found the "Jiayu.de from Germany": can you send the link?
Also, can you recommend some good manual for dummies?
Thanks again for your patient and help!
latest sp flash tools is 5.1532
search needrom with "5.1532" will leed you to the download page
no link allowed here, so ...
for beta 10 from jiyau.de, search google with "jiyau.de Lollipop 5.1.1 - Beta 10 (14.10.2015)".
it will leeds you to the rom.
Good hunting
tuto sp flash tool
https://youtu.be/ztI8sc8MUNo
AzulFogo said:
Thank you!
I found "Xtreme from Spain":
needrom.com/download/rom-xtreme-rom-tf/
I found the "SP Flash Tool":
needrom.com/download/sp-flash-tool-v5-1424-00/
but it is for Linux... can you send me the link of the windows version?
And I could not found the "Jiayu.de from Germany": can you send the link?
Also, can you recommend some good manual for dummies?
Thanks again for your patient and help!
Click to expand...
Click to collapse
see jaunedoeuf's answers
I would like to add: if you come from KK and go to LP, you must use firmware upgrade to update/adjust internal SD partition layout. Good Luck! if you succeed, and are happy with firmware, consider voting @ http://forum.xda-developers.com/android/general/firmware-jiayu-s3-t3212184 (almost 100 votes)
First, thank you for your great help!
With your suggestions, I managed to install Lolipop in my Jiayu S3S (upgraded from Kit Kat) - Xtreme ROM TF (JiayuS3-5.1Extreme1.1SP.zip).
However the problem remain... the phone still is asking for a PIN (that I never had put there, in first place)...
What should I do now?
you could try factory reset and are you sure its the phone asking for pin and not the sim card
This guide is meant for people that have experience in flashing Android phones. I just consolidated the information from various threads around the web, so it's easier to find.
Advice here works on the latest Lollipop MIUI stable ROM, 8.0.5.0 LHOMIDG for Kenzo Snapdragon version. I tested it myself.
Just to be clear, I am not responsible for any possible problems you may encounter white attempting to do anything mentioned in this post.
1. follow this guide to unlock the Bootloader unofficially ( http://en.miui.com/thread-253680-1-1.html )
2. do not use "emmc_appsboot.mbn" from the above thread, or you will have a bug that causes your notification led light to blink red constantly, while the phone is connected with a USB cable to a charger, or a PC.
3. use "emmc_appsboot.mbn" from this thread ( http://en.miui.com/thread-280771-1-1.html ), or if you prefer, this is the direct link ( https://drive.google.com/open?id=0B6qi9i0uOR-BY21NRGxVN1JiRDQ )
4. install recovery from this thread ( http://forum.xda-developers.com/redmi-note-3/how-to/zcx-twrp-install-twrp-flash-supersu-t3462448 )
That is all. Enjoy.
EDIT: Apps that are safe to freeze with Titanium backup are listed in the attached screenshots. Remember, do not uninstall or remove them. Just freeze them. List updated on 10. Nov 2016
Also, my advice is not to bother with official BL unlock. It's just a data mining operation by Xiaomi. They use it to get your e-mail account, phone number, location and who knows what else... Also, avoid any MI related services, like MI accounts, storages, backups and sync.
After rooting the phone, FREEZE but do not REMOVE any bloat apps. Do not forget to firewall MI apps!
ty for this, although I agree with you they use this for data mining, but unlocked it officialy anyway, because they gave me permission in few hours... Also unlocking only takes like 5sec,
I use dropbox & google stuff so they have my data already
Agreed, but there is no need to add Chinese to the mix
I will post a list of apps that are safe to freeze in a few days, as soon as I finish testing.
List of apps ( screenshots ) added in the first post.
Updated the list of frozen apps. This is as good as it gets, without getting force close on anything.
Thank you. Your thread helped me with the red light issue.
mhm,this method work in miui 8 global 6.12.1 beta? ( dev)
tested and success. thanks you
tested and success. thanks you
@Tomo123
Please confirm, that Using this ROM as base would work for unlocking unofficially?
http://bigota.d.miui.com/V8.0.5.0.LHOMIDG/miui_HMNote3ProGlobal_V8.0.5.0.LHOMIDG_a831ea486e_5.1.zip
And, i plan to use AOSP roms,but please tell me how to go back to STOCK MIUI ROM[without brick] in future if i decide to unlock officially, i have already got the permission, but the unlock tool stuck at 50%.. cant wait more...
Thanks for the help.
Confirmed working.
I'm on MIUI Global 8.2 (8.2.9.99 LHOMIDG) will this procedure work? I just got my Redmi Note 3 Snapdragon variant today and i want to Root it, Xposed it and Enjoy it
ex samsung owner my whole life, very good knowledge in flashing/Samsung, totally NOOB with Redmi, please advice thanks
Tomo123 said:
Confirmed working.
Click to expand...
Click to collapse
@Tomo123
Thanks for the reply, i could unlock the bootloader successfully, but i have a problem.
when i rebooted to the MIUI system ROM while in the process to unlock(after unlocking the bootloader),
i could observe that there was no network, my 4G sim couldnt be detected.. And thereafter when i try CM14.1 or RR rom, i get network but cant make calls/sms but 4G data works.
I tried a few Nougat firmwares, but same problem of no calls/sms
I am getting the feeling it all started from the 5.1 MIUI ROM with no network..
So i was thinking to flash the latest global/dev Marshmallow ROM and start over the BL unlock process.. will it help? have any ideas?
And the most important Ques is that the bootloader talked here would even work on With marshmallow ROM for unofficial unlock or not?
Please suggest.
Thanks.
I've tried this guide loads of times now and I'm always stuck with "FAILED (remote: oem unlock is not allowed".
All the info regarding the problem mention to boot into the system and turn on oem unlock in the developer options. But I can't boot with the modified emmc_appsboot.mbn I only get the Mi logo flashing.
Any ideas?
[HELP THREAD] Stuck in a "Your device has been unlocked and can't be trusted" loop
Hello,
I am using a Motorola Moto G4 Plus (12GB, Android Nougat 7.0) and i tried unlocking the bootloader/ flashing a custom rom because I already managed to do the same with my Moto G3.
After unlocking the bootloader I successfully installed TWRP 3.1.0 on my Phone.
I then wiped all of my data including the system and flashed Cyanogenmod 14.0 (2016-09-13 UNOFFICIAL athene) and installed open_gapps-arm-7.0-mini-20170603.
My problem is that when I booted my phone there is a message saying:
Your device has been unlocked and can't be trusted.
To learn more, visit:
motorola.com/unlockbootloader
ID: N/A
Your device will boot in 5 seconds.
And i have absolutely no way of getting rid of it or shutting down my phone. Every 5 seconds my screen turns black for like one second and the message appears again.
I would appreciate it if you guys could help me access my phone.
P.S. It's my first time posting, please tell me when I did do something wrong
lologke said:
Hello,
I am using a Motorola Moto G4 Plus (12GB, Android Nougat 7.0) and i tried unlocking the bootloader/ flashing a custom rom because I already managed to do the same with my Moto G3.
After unlocking the bootloader I successfully installed TWRP 3.1.0 on my Phone.
I then wiped all of my data including the system and flashed Cyanogenmod 14.0 (2016-09-13 UNOFFICIAL athene) and installed open_gapps-arm-7.0-mini-20170603.
My problem is that when I booted my phone there is a message saying:
Your device has been unlocked and can't be trusted.
To learn more, visit:
motorola.com/unlockbootloader
ID: N/A
Your device will boot in 5 seconds.
And i have absolutely no way of getting rid of it or shutting down my phone. Every 5 seconds my screen turns black for like one second and the message appears again.
I would appreciate it if you guys could help me access my phone.
P.S. It's my first time posting, please tell me when I did do something wrong
Click to expand...
Click to collapse
Ask and answered yesterday in help thread for example. Please have a look at here and the posts before and after https://forum.xda-developers.com/mo...-question-noob-friendly-t3526598/post72528225 for the message at boot.
Because of your bootloop after displaying of the message your device can't be trusted": why you install the abandoned cm14.0? Use newer LineageOS or other supported roms instead of that discontinued one.
I think it's because of the newer twrp maybe. Did you tried an older version like twrp 3.0.2? Did you tried installing the rom without gapps? Maybe the gapps doesn't play well with the old rom?
I got same problem but i solved it.. if u need to solved this problem Flash your device. It works 100%.^_^
Mariashaik said:
I got same problem but i solved it.. if u need to solved this problem Flash your device. It works 100%.^_^???
Click to expand...
Click to collapse
If you have nothing useful to say, say nothing. It can irritate new users.
I guess you should try some other ROM as suggested! You can go to Recovery by using Power+vol down Button for 5 sec... that should take u to bootloader and then recovery and other options!
Let me know if that works!
Ummm.. just read the post again... moto g4 plus (12 GB)... I hope that's a typo!
lologke said:
Hello,
I am using a Motorola Moto G4 Plus (12GB, Android Nougat 7.0) and i tried unlocking the bootloader/ flashing a custom rom because I already managed to do the same with my Moto G3.
After unlocking the bootloader I successfully installed TWRP 3.1.0 on my Phone.
I then wiped all of my data including the system and flashed Cyanogenmod 14.0 (2016-09-13 UNOFFICIAL athene) and installed open_gapps-arm-7.0-mini-20170603.
My problem is that when I booted my phone there is a message saying:
Your device has been unlocked and can't be trusted.
To learn more, visit:
motorola.com/unlockbootloader
ID: N/A
Your device will boot in 5 seconds.
And i have absolutely no way of getting rid of it or shutting down my phone. Every 5 seconds my screen turns black for like one second and the message appears again.
I would appreciate it if you guys could help me access my phone.
P.S. It's my first time posting, please tell me when I did do something wrong
Click to expand...
Click to collapse
umm. why do you flash unofficial cyanogenmod instead of lineageos?
Try flashing the latest roms, with latest twrp and see if it works or not. If it still doesn't, flash stock ROM and start again. I hope you have a backup made.
Okay, so I've been trying to get some answers regarding custom ROMs for the past few days but I haven't even got one...and it seems I'm not the only one looking for them. So...lay it in this thread maybe we can start something up.
I am on stock OREO B04, phone's software has never been tampered with anything, TWRP, BL unlock and so on.
This is the premise of the thread, not only for me but for other users who find themselves in the same situation.
Oreo seems to be a bit of a hassle right now for migrating to custom ROMs, and this is not helped by the fact guides in the A7 section are all over the place as well, some may be outdated and there's no clear "Don't use this on x.x version" warning.
I am not even going to attempt to unlock the BL until I clear answer on wether it's possible or not. So let's start with this:
-Is it possible to unlock the BL on OREO?
-If not, what stock official ROM should we install in order to successfuly attempt to unlock the bl?
-Which guide or method is the best for doing so? I've found 2, one from 2016 on MM ROMs and one provided by TurkDevs that seems to work on some Nougat ROMs.
Then comes the recovery section:
-What TWRP should we install on a freshly unlocked device, the official releases, or the Nfound custom ones?
-Also, what are the prerequisites for installing TWRP...I hear that fastboot commands are gone since Nougat and that some flashing methods don't work, then I hear somehow you can do it by bringing back fastboot. How? There's only replies saying "type that command in fastboot" but nobody says if they had it or reinstalled it somehow.
Then comes the ROMs section:
-All custom ROMs seem to require a vendor partition as most if not all of them are Treble based. How do we get that to work?
- I am aware of the fact that the ROM threads have a prerequisites section, but none of them redirect you to a guide on how to get those prerequisites working. I understand that it's not the dev's responsability, I am not bashing anyone here, but a little bit of info cleaning and structuring should be in order in this section.
What I want for me and others in my situation is a clear answer on how to proceed, not a "flash this flash that". There's no secret that the A7 still has life in it especially with the new PIE ROMs.
I've recently seen a reply in one of the threads, encouraging the dev of one of this ROMs to not be disappointed by the seemingly low interest in PIE ROMs. I don't think there's a low interest in them, I think there are users that don't want to risk a bricked phone because of outdated guides and unlcear steps.
There's a lot of confusion going around here so I hope this thread will become a source of updated info on what's possible and what not. Thanks in advance!
Hi, I'm not the best person to help you with this since i've unlocked my Axon 7 a long time ago and I can't remember everything but I will try to help you based on my experience and on what I can remember.
Let's go
Starting with the bootloader, I unlocked mine on stock Nougat B09 using EDL Tool (Oreo wasn't even out when I unlocked my bootloader so I don't know if you can do it while running Oreo but just to be safe you should downgrade to Nougat)
It should be quite easy to unlock the bootloader, here's a simple step by step (please anyone correct me if I'm wrong)
- Download the EDL tool from the link above
- Downgrade your phone to Nougat (Using the updater on the phone itself or an EDL Package with EDL Tool or MiFlash - you can find the stock ROMs on @raystef66 's Download Center
- Once running Stock Nougat, turn on USB Debugging and Allow OEM Unlocking on Developer Settings
- Plug the phone to your computer and open EDL Tool (that should reboot the phone into EDL mode automatically)
- Navigate through the EDL Tool using the number keys on the keyboard, and it should be easy to find the Unlock Bootloader option. Unlock it and you should be done.
Once again that's the way I did it, I don't know if this is the easiest one available. You have more methods available like this one
Now onto the recovery situation, I think each developer recommends a specific TWRP version for their ROM's, like for example
@raystef66 likes NFound's TWRP 3.2.1-8 as you can see on his ROM's posts (check the first line in the installation guide)
@OrdenKrieger likes the official TWRP as you can see on Lineage OS 16.0 post
Generally, official TWRP should work just fine with any ROM.
On a recently unlocked Nougat Stock ROM, I recommend maybe an older version of TWRP, like 3.2.1 for example and you can flash it also using EDL Tool.
But when moving to Pie I recommend you use the latest TWRP version or the version that the ROM developer recommends. You probably know this but you can update your TWRP version by flashing it over the current version you have.
Now about the ROM's, the new ones have a Vendor partition so you have to create it when you're coming from Stock (because our Axon 7 doesn't support Project Treble) and to do that you can use @Oki 's PARTY Tool and after that you can flash the ROM normally, using the proper Bootstack and Modem files.
You could also try GSI's but I can't help you with that because I never tried them.
And this should be all.
I tried to keep it simple for now but i can help you further
I'm not the best person to guide you but at least I tried Feel free to ask me something and good luck!
@joaocandeias Well, dang it worked. Everything you described:
-going back to Nougat
-unlocking the bootloader with the EDL tool
-flashing TWRP-
creating the Vendor partition, and installing the new ROMs.
There were a few hiccups on the road, mostly driver related from my previous attempt, but nothing severe or something that would cause the device to brick.
I just installed @raystef66 's ResRemix ROM and it works fine. I'll start testing more of them in daily use and see which suits my needs best.
Thanks for the assistance!
TorqueSsS said:
@joaocandeias Well, dang it worked. Everything you described:
-going back to Nougat
-unlocking the bootloader with the EDL tool
-flashing TWRP-
creating the Vendor partition, and installing the new ROMs.
There were a few hiccups on the road, mostly driver related from my previous attempt, but nothing severe or something that would cause the device to brick.
I just installed @raystef66 's ResRemix ROM and it works fine. I'll start testing more of them in daily use and see which suits my needs best.
Thanks for the assistance!
Click to expand...
Click to collapse
I'm glad I could help
Since you're not the only person with questions on how to migrate from stock to custom, I'm thinking about writing a full post so more people can see it.
Btw what method did you use to downgrade to nougat?
@joaocandeias Sorry for the delayed response, I've got a really f'd up sleeping schedule these days. I'll write the exact steps I've done.
1. So, I first downloaded the B09 Nougat full stock ROM from the download center and tried to downgrade using the normal software updater in the phone (OTA window, local option).
It didn't work at first, I received a compatibility error, saying that the update is for "ailsa_ii" devices, while the device is not(or to be more exact, my device was " " ), which I found odd.
But, I thought that maybe I need the linked versions(like the last Nougat ROM before Oreo) so I downloaded the B10 Nougat ROM, and used the same procedure.
2. I set up the phone as a dud(skip everything, no Google account), turned USB debugging and OEM unlocking on, installed the original ZTE drivers straight from the phone and rebooted it into EDL to proceed with unlocking the BL.
At this point, I had the QUSB_BULK driver stick from my previous use of Zadig, so one quick "uninstall device software" and relpuging the phone go me the Qualcom 9008 driver in order.
3. I started the EDL tool, navigated through it and started the BL unlock procedure.
Once the phone rebooted I was greeted by the password screen.
One factory reset later and repeating the procedure greeted me with the "Bootloader unlocked" message. Sucess!
4.Now for TWRP, Vendor and ROM, got all the files onto the SD card, I flashedTWRP 3.2.1-8 NFound, then, from TWRP, I used the party tool, then flashed the UBv2(at which point it reverted TWRP to 3.2.3, flashed the 3.2.1-8 again with EDL ), modem, ROM, GApps, rebooted, set it up, then flashed Magisk...and everything seems fine.
The only issue I have now seems to be the camera, both stock app and GCam.
Open camera works , has the correct photo and video res, 60FPS doesn't work and the flash seems a bit laggy, but for me it's ok.
The DAC however is there, alive and kicking, Neutron detected the Hi-Res codec at launch and switched to it. It sounds the same as stock OREO to me so it is great, as this was my greatest fear when migrating to PIE. The DAC-AMP combo is like 60% of the reason I bought this phone in the first place.
TorqueSsS said:
@joaocandeias Sorry for the delayed response, I've got a really f'd up sleeping schedule these days. I'll write the exact steps I've done.
1. So, I first downloaded the B09 Nougat full stock ROM from the download center and tried to downgrade using the normal software updater in the phone (OTA window, local option).
It didn't work at first, I received a compatibility error, saying that the update is for "ailsa_ii" devices, while the device is not(or to be more exact, my device was " " ), which I found odd.
But, I thought that maybe I need the linked versions(like the last Nougat ROM before Oreo) so I downloaded the B10 Nougat ROM, and used the same procedure.
2. I set up the phone as a dud(skip everything, no Google account), turned USB debugging and OEM unlocking on, installed the original ZTE drivers straight from the phone and rebooted it into EDL to proceed with unlocking the BL.
At this point, I had the QUSB_BULK driver stick from my previous use of Zadig, so one quick "uninstall device software" and relpuging the phone go me the Qualcom 9008 driver in order.
3. I started the EDL tool, navigated through it and started the BL unlock procedure.
Once the phone rebooted I was greeted by the password screen.
One factory reset later and repeating the procedure greeted me with the "Bootloader unlocked" message. Sucess!
4.Now for TWRP, Vendor and ROM, got all the files onto the SD card, I flashedTWRP 3.2.1-8 NFound, then, from TWRP, I used the party tool, then flashed the UBv2(at which point it reverted TWRP to 3.2.3, flashed the 3.2.1-8 again with EDL ), modem, ROM, GApps, rebooted, set it up, then flashed Magisk...and everything seems fine.
The only issue I have now seems to be the camera, both stock app and GCam.
Open camera works , has the correct photo and video res, 60FPS doesn't work and the flash seems a bit laggy, but for me it's ok.
The DAC however is there, alive and kicking, Neutron detected the Hi-Res codec at launch and switched to it. It sounds the same as stock OREO to me so it is great, as this was my greatest fear when migrating to PIE. The DAC-AMP combo is like 60% of the reason I bought this phone in the first place.
Click to expand...
Click to collapse
Thanks! That will help me a lot to write a full guide. You'll be credited, don't worry
And yeah, when you migrate to custom roms you'll have to sacrifice camera quality and functionality and also a bit of speakers sound quality (all dolby atmos ports I tried are quite buggy and don't work well ; i only use atmos with the speakers). Headphones sound quality is great though.
If you don't use camera that much (not my case) and you're okay with the speakers sound quality then custom roms are probably the best option out there.
@joaocandeias
I was fully aware of the camera issues I might encounter, this has been the case with my old Mediatek devices when going to custom as well, same camera issues, but at least...it works here. Yeah, I lost some functionality, but to me it's a good trade-off. It can still take snaps and film properly so it's enough for me.
I am kind of going to miss Dolby on speakers (never liked it on headphones though), as it did a really good job for podcast style videos on YT, but it still sounds way better than a lot of phones without it so it's fine. I just need to crank the volume up a little more than usual.
I've heard that treble Pie Roms require a oreo bootloader, is this true? I am still confused how to install on my A2017G. In which order would I install bootloader and vendor partition?
Hi, I've been researching and I wasn't able to successfully flash a custom ROM for this model.
Following the procedures in other threads tutorials, I was able to flash the following ROMS:
DOT-N-v1.2-20180717-y5-UNOFFICIAL.zip
lineage-14.1-20180715-UNOFFICIAL-y5.zip
To be able to flash them, I had to change the ´updater-script´ to be able to bypass the only Y5 model condition, as I was getting an error regarding my current model is: hwmya_L6737.
I wasn't able to run Lineage and DotOS I was able to boot but WiFi was unresponsive and it didn't detect any SIM card, making this ROM unusable...
I was able to restore my phone back to the state it was (Stock ROM and rooted) thanks to a TWRP backup.
I used this devices comparison to attempt to find equivalent ROMs according to the devices similar to MYA-L13 (which is the one I own) to no avail...
SO... I tried my best with these attempts but I'm back where I began!
I've been researching but I haven't found any other suitable Custom ROM for this device.
Can someone point me in the right direction, please?
OR:
Alternatively, I was able to flash and boot into the above DotOS version, but I wasn't able to detect the SIM card, and also the WiFi even if it seems to work, is disconected almost instantly... I guess it has something to do with the chipset or something beyond my knowledge.
Can someone please help me out regarding this?
Thanks in advance!
next time try to get more comercial, vastly sold, phone. choosing Qualcomm helps a lot
metafaniel said:
Hi, I've been researching and I wasn't able to successfully flash a custom ROM for this model.
Following the procedures in other threads tutorials, I was able to flash the following ROMS:
DOT-N-v1.2-20180717-y5-UNOFFICIAL.zip
lineage-14.1-20180715-UNOFFICIAL-y5.zip
To be able to flash them, I had to change the ´updater-script´ to be able to bypass the only Y5 model condition, as I was getting an error regarding my current model is: hwmya_L6737.
I wasn't able to run Lineage and DotOS I was able to boot but WiFi was unresponsive and it didn't detect any SIM card, making this ROM unusable...
I was able to restore my phone back to the state it was (Stock ROM and rooted) thanks to a TWRP backup.
I used this devices comparison to attempt to find equivalent ROMs according to the devices similar to MYA-L13 (which is the one I own) to no avail...
SO... I tried my best with these attempts but I'm back where I began!
I've been researching but I haven't found any other suitable Custom ROM for this device.
Can someone point me in the right direction, please?
OR:
Alternatively, I was able to flash and boot into the above DotOS version, but I wasn't able to detect the SIM card, and also the WiFi even if it seems to work, is disconected almost instantly... I guess it has something to do with the chipset or something beyond my knowledge.
Can someone please help me out regarding this?
Thanks in advance!
Click to expand...
Click to collapse
Hi, how did you change the updater script file? I have an Y6 MYA-L11 phone but i'm not able to skip model error message (I tried to change all "SCL-L02" with "hwmya_L6737" in the updater script file but it didn't work).
Another question, did you finally find a working rom?