Related
Unfortunately, app has stopped in Marshmallow
Good morning in South Africa time to everybody !
I decided to post my situation in here since I can see that all of you are quite helpful and would be able to help me with my Lenovo K3 Note T3s, purchased recently
The strange thing is that I have older apps which I use but every, I mean every, ROM,for the T5, which I have installed to my Lenovo K3,and almost every app that I have installed, and when I run these apps,it returns an error stating...UNFORTUNATELY, xxx HAS STOPPED. Most of the apps do start, and when the error is displayed, i can still see the app in the background underneath the error text that is displayed, which seems that the app does start, but something is preventing it with displaying the error above, and shutting it down when I press on the OK text in the error
I have tried around five roms already, various ones, most from Needrom.com, made for the T5, and they all return the same error when running the newly installed app, its as if this phone has a built in security function that doesnt allow any apps to be installed and used! The original ROM was ok but too much of bloatware and chinese writing which required me to find a better rom
Currently as I type this, I am downloading a rom for the T3S from needrom.com, hoping that I dont receive this error anymore
I have installed an updated app on one of the roms and it worked and did not display the error, however, I use some apps that do not have a later updated version available which causes the error to be displayed.
Are there any ideas on what could be causing this ? I have tried a few things from what I have read via a google search but none has worked
Any ideas or help would be much appreciated!
PS: I will keep you guys informed of what happens from this time of writing as well, just in case I find the cause/solution and somebody out there is also going through the same problem.
Heres the latest update so far...
Installed Lenovo K3_Note_MTK6752_Android_5.0_20150513 ROM from http://www.teamandroiders.com/lenovo-k3-note-stock-rom-firmware/
Its Android version 5.0, and still the same problem, almost every app still gives me the same error.
Going to try a rom built for Lenovo K3 Note T3s and reply afterwards.
quetiano said:
Unfortunately, app has stopped in Marshmallow
Good morning in South Africa time to everybody !
I decided to post my situation in here since I can see that all of you are quite helpful and would be able to help me with my Lenovo K3 Note T3s, purchased recently
The strange thing is that I have older apps which I use but every, I mean every, ROM,for the T5, which I have installed to my Lenovo K3,and almost every app that I have installed, and when I run these apps,it returns an error stating...UNFORTUNATELY, xxx HAS STOPPED. Most of the apps do start, and when the error is displayed, i can still see the app in the background underneath the error text that is displayed, which seems that the app does start, but something is preventing it with displaying the error above, and shutting it down when I press on the OK text in the error
I have tried around five roms already, various ones, most from Needrom.com, made for the T5, and they all return the same error when running the newly installed app, its as if this phone has a built in security function that doesnt allow any apps to be installed and used! The original ROM was ok but too much of bloatware and chinese writing which required me to find a better rom
Currently as I type this, I am downloading a rom for the T3S from needrom.com, hoping that I dont receive this error anymore
I have installed an updated app on one of the roms and it worked and did not display the error, however, I use some apps that do not have a later updated version available which causes the error to be displayed.
Are there any ideas on what could be causing this ? I have tried a few things from what I have read via a google search but none has worked
Any ideas or help would be much appreciated!
PS: I will keep you guys informed of what happens from this time of writing as well, just in case I find the cause/solution and somebody out there is also going through the same problem.
Click to expand...
Click to collapse
Ok when you flash it the flash tools, you use the preloader.bin and lk.bin frome the original rom?
When you instal the new rom make recovery reboots betwen wipes? This last is for you make a clean instal and avoid problems like that you have it now, or meaby you can lost the imei number, or the keyboard miss it, i dont know many problem came if you dont make reboots betwen wipes
I hope be helpfull to you.
Enviado desde mi Lenovo K50-t5 mediante Tapatalk
Thank you for your reply.
I came across a website that had a guide to try, two options were available, the first option I have tried and it worked, havent tried the second option though. The first option was the Android System Webview app, where, by opening it under apps in settings, and choosing to uninstall the update, it should help fix my error, and it did. There were one or two apps that still gave me the same error but most of the apps began to work after doing this.
Got a new Moto X4 1900-7 two days ago (reteu channel). Unlocked and rooted with MAGISK 17. Yesterday installed LineageOS 15.1 (Android 8.1 was shown) as described here. AddonSU and MindTheGApps did not work as install from the LineageOS Recovery. So installed them via TWRP.
Today it showed there is a new update for LineageOS. It seemed a good idea to test the update channel. LineageOS downloaded, installed and I pressed the reboot button. Since then the device does not switch on anymore. Just nothing. No lights, no booting screen. Looks fairly hard bricked now.
It is a bit frightening since I made good experiences with LineageOS on Moto X Play for years. But this time it did not work as seamless. As a side note, the second sim slot was disabled. I did not find out, where and how to enable it. This would be issues to be sorted out, before I support the project again.
I appreciate all your efforts about these devices and free software! :good:
Is there a reason you are not posting (and reading) in the proper thread?
https://forum.xda-developers.com/moto-x4/development/rom-lineage-os-15-1-t3802265
You will find all your answers there.
The developer specifically advised not to use the OTA updater.
Same issue here. Got a brand new Moto X4 delivered today. Verified nothing was obviously broken (tried WLAN, Cell, Dual SIM from stock). All fine.
Then I installed last night's nightly "lineage-15.1-20181017-nightly-payton-signed.zip" from within TWRP. After installing the nightly, I went with reboot recovery.
Since then, the phone appears hard-bricked as described by halori above.
No lights, no activity. Had it on charger most of the afternoon and all evening (it is 22:13 in Germany now). No signs of life. No matter how long I pressed VOLUMEDOWN+POWER. Same thing if I only press POWER. Same thing if I try charging it for 10-20 minutes, then try switching it one. Neither of the methods works.
Update:
- Similar symptoms, but different way of getting there
- Installed nightly 2018-10-17 via TWRP, *NOT* via OTA
Please post in proper thread.
jhedfors said:
Please post in proper thread.
Click to expand...
Click to collapse
That's a 64-page monster thread. Loads of different topics are "cross-talked". On the last two pages alone there are people
asking whether particular variants can be unlocked,
asking about issues with SIM2,
asking about storage requirements,
responding to those questions and
responding to questions from the pages before.
That thread is pure chaos. Web forums got threads, subjects and all that stuff for a reason: to keep things tidy and on-topic.
No offense meant. It is just very hard to grasp how merging all sorts of topics into one massive thread helps anybody keeping an overview.
Anyways, I posted in the thread, as you asked.
This Lineage is obviously crime with this device - it is just too sensitive to anything than 100% unmodified stock.
Exactly the same here. Today's 10/23 OTA update bricked it. :-/ No lights or anything. Not even from charging. Trying to figure out what to do at this point.
If you've already bricked your device you'll need to restore to stock ( https://forum.xda-developers.com/moto-x4/how-to/guide-how-to-flash-official-factory-t3808348 ) and then reinstall LOS.
From there you can apply updates without bricking your device by following this procedure: https://forum.xda-developers.com/showpost.php?p=77861941&postcount=616
As for finding specific things in the threads, there is a search function within each thread that is your friend.
DISCLAIMER:
Code:
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
INTRODUCTION
This thread is mainly intended for devs (pro devs don't really belong here because they're pro and this thread is useless), for someone who need help to continue the work for Nova and fix the bugs on Pie (not many left). I'll help as long as you can speak English xD (no google translate because it can cause misunderstandings). However, don't expect me to spend the same time into this as i''ve did when i've had the phone. Yes, i no longer have the phone (it's still dead) and if you're not up to date with that, then you can read the announcement here and i've mentioned that i've got a new phone here. On top of this, i can't build anymore because i can't sign up on Google Cloud Platform anymore. I've wrote about this here at the hidden content (below as a side note).
Users can also help with doing researches, testing things and logs.
I don't know if i'll consider to continue working on it myself alone without the phone. I'd need at least to be able to build and then i'd need people to test new builds / flashable zips. At some point i might consider that because i'm missing this phone and the community xD.
SOURCES
Device: https://github.com/skinzor/android_device_huawei_hwcan/tree/lineage-16.0-last
Vendor: https://github.com/skinzor/proprietary_vendor_huawei/tree/lineage-16.0-last
Kernel: https://github.com/skinzor/android_kernel_huawei_msm8953-1/tree/lineage-16.0-last
Click to expand...
Click to collapse
There's two branches:
1) lineage-16.0: those ones were used when i've booted Pie the first time. Remember that i've wrote about it here? Those ones were updated from mido's ones.
2) lineage-16.0-last. those ones are the last ones and updated, which i've used in my last build. Those ones were continued from previous branch and updated from tissot ones which were / are updated by another dev (not the same dev as on mido). I recommend to continue with this branch, but it's up to you. You might not be able to get a successful or bootable build anymore with lineage-16.0 branch anyway because lineage's sources were updated since then.
I've used mido's trees as reference for lineage 14 and 15 trees too. You can figure that yourself if you check mido's trees and then Nova's ones, as i've cherry-picked the commits. Why did i use mido's trees? Because:
1) It has the same qcom chipset as Nova.
2) It is a popular phone.
3) A good dev was working on it.
4) It has official lineage support.
Now you might ask why i haven't did myself everything from scratch. Well, as a newbie dev, it would've been much harder and would've took much more time. Also, i'd say that there's no point at all to do something from scratch when it was already done unless you want to go the "hard" way, assuming you have time and want to learn more. I've still learnt a lot since i've started.
There are "universal" commits which are about fixes / improvements that can be related to e.g. the android version or the qcom chipset and those commits are usually found in many device trees, so you just cherry-pick them. A good example would be this commit: hwcan: Use mke2fs to create ext4 images.
FIXING THE BUGS OF LINEAGE 16 / PIE
I assume that you've used lineage-16.0-last branch as i've recommended. I no longer remember what bugs had my last build, but i think that the bluetooth was working, while it wasn't working in the build made from old lineage-16.0 branch. However, i remember that it had a new bug and as far as i remember, it was the RIL, but the baseband was showing up. I think i've tried to fix it and i've got it working (i remember that it was about the blobs), but i don't remember how. As of typing now, i've looked into the logcat which i still have and i've seen this:
Code:
F linker : CANNOT LINK EXECUTABLE "/vendor/bin/tftp_server": library "liboemaids_vendor.so" not found
That kind of error is self explanatory: the blob / lib is missing. After i've seen this, i've remembered that it's a new blob which got added in the original commit and which i've cherry-picked here. I didn't include that blob for a reason, but i don't remember that reason lol (it's not that i've forgot it, but i've skipped it for a reason). I remember that back then i've added the blob manually after i've seen the error, but i don't remember if that's what fixed the RIL, so you can try that and let me know.
As i've said already, i don't remember what bugs had that build besides the RIL, so you can try it and let me know.
At the introduction i've mentioned that i can help. I'll help only here on XDA in this thread because it may help other people too if they're having the same error / problem and after all, it's nice to have a thread like this in my opinion.
You can attach the log or paste it to gist github, pastebin, del.dog or any pasting website, but don't paste it in the XDA post because it just sucks.
Click to expand...
Click to collapse
DOWNLOADS
MEDIAFIRE | ANDROIDFILEHOST
As i've recommended to use lineage-16.0-last branch to build / continue the development, i also recommend to flash that build.
The build from lineage-16.0 branch folder doesn't boot. Back then, when i've seen that it doesn't boot and took a look at the logcat, i've tried the graphic blobs from the tree of zenfone 3 and that one was using them from nokia 7 plus (based on the commit). I had two zips in my PC and i've uploaded both. The first one created is graphic_pie_blobs_zenfone3_nokia_7_plus.zip and the second one sdm_blobs_zenfone3_nokia7_plus.zip, so you flash them in that order. As i've mentioned in that post in which i've said that i've booted Pie, there is some lag / glitches while scrolling, due the display / graphic blobs.
ENDING
As i've promised, i've pushed the tree sources and uploaded my first and last build. The reason i'm willing to help in fixing the bugs is because i'm missing this phone and this community here on XDA (as i've expected xD). It was fun and thanks to this phone and y`all for your support and kind words, i've learnt so many things in this journey. That's simply unforgettable for me.
Hopefully someone will jump on and continue the development further. I'll be here to help.
XDA:DevDB Information
[DEV][9.0] LineageOS 16, ROM for the Huawei Nova/Nova Plus
Contributors
#Henkate
Source Code: https://github.com/skinzor/android_kernel_huawei_msm8953-1/tree/lineage-16.0-last
ROM OS Version: 9.x Pie
ROM Firmware Required: Unlocked bootloader, TWRP
Version Information
Status: Testing
Created 2019-01-02
Last Updated 2019-01-05
Reserved
Reserved
Thank you for all the hard work you put into this. I would try to follow the leads, but for me this phone is dead now. I had hoped it would be something, but naw, just a hunk of something. Maybe someone can pick it up and go with it, encouraged everyone to try. If you are thinking about it Robert @#Henkate will help you. Great person, and this phone got me to know him so boom, good phone.
Maybe this should be in off topic thread, but I will post here.
Thank you for the great work that you have done. You gave us nougat, oreo, almost a pie. LineageOS 15.1 is the best firmware I have ever used. EmUi far behind. Thanks again a lot. Pie is full of bugs (I have already tried), counted a huge list of 10 items, but I think it's time to relax. You gave nova a second life and for that I am grateful to you. I found out that you are switching to another phone. Good luck in developing it, you are a good developer, the main thing is to believe in yourself!
Hi enkate... does wifi calling work on 16 ?
thanks
virusdunil said:
Hi enkate... does wifi calling work on 16 ?
thanks
Click to expand...
Click to collapse
He has no way to check. Maybe someone who has flashed it could test.
wow！thx a lot，I will try it now！
Hey Henkate !, Yesterday I installed LOS16, the last build that you compiled, botched and everything, but at the moment of continuing with the initial configuration, the screen does not give an image, the touch works, but it runs out of image: /
Alee.se said:
Hey Henkate !, Yesterday I installed LOS16, the last build that you compiled, botched and everything, but at the moment of continuing with the initial configuration, the screen does not give an image, the touch works, but it runs out of image: /
Click to expand...
Click to collapse
With the first build go two files, except for the firmware, responsible for the display. Flash them after flash lineage 16 last build and everything will work
Logcats
Hey there!
Finally tried it. I flashed just the latest build and there is what I got:
After flashing only ROM, it booted, but nothing was drawn at the display. Ok, that was expect
Then I wiped system and data again, flashed the build and both of the other zips (from the first build folder)
It booted fine, RIL was working at start, wifi ok. Many other things couldn't be tested, because randomly (one time taking photos, other when scrolling settings, other when trying to test bluetooth) screen went black the blue led got lit up.
I took a logcat only with errors and it seems there is a lot to fix. Still today (just a lot later today, I have to work) I'm gonna fetch los 16 trees, but I still have no idea how to solve any of the bugs. I'll do a lot of search though.
Here is the gist I made with the logcat I took. Any help would be appreciated.
EDIT
just forgot to mention that besides RIL working, I couldn't make a call (display went black and blue led). When rebooted it, I had no signal reception at all
Vinnom said:
Hey there!
Finally tried it. I flashed just the latest build and there is what I got:
After flashing only ROM, it booted, but nothing was drawn at the display. Ok, that was expect
Then I wiped system and data again, flashed the build and both of the other zips (from the first build folder)
It booted fine, RIL was working at start, wifi ok. Many other things couldn't be tested, because randomly (one time taking photos, other when scrolling settings, other when trying to test bluetooth) screen went black the blue led got lit up.
I took a logcat only with errors and it seems there is a lot to fix. Still today (just a lot later today, I have to work) I'm gonna fetch los 16 trees, but I still have no idea how to solve any of the bugs. I'll do a lot of search though.
Here is the gist I made with the logcat I took. Any help would be appreciated.
EDIT
just forgot to mention that besides RIL working, I couldn't make a call (display went black and blue led). When rebooted it, I had no signal reception at all
Click to expand...
Click to collapse
Also to the list of bugs: personally, my phone did not work with a SIM card, constant crash of applications. The YouTube crash, the camera does not take a photo (camera stock), after restarting, the fingerprint disappears (it is not deleted from memory, but it can only be unlocked if you make a new fingerprint) Any heavy application will crash after a while
Thx for u work, I have a reboots after few mins the system starts
nova canL11, cant reply link to adb bugreport logs x_x
penk3 said:
Thx for u work, I have a reboots after few mins the system starts
nova canL11, cant reply link to adb bugreport logs x_x
Click to expand...
Click to collapse
Disable out sim card
AssasinAkindinov said:
Disable out sim card
Click to expand...
Click to collapse
ye, phone in airmode workrd normally,
AssasinAkindinov said:
Also to the list of bugs: personally, my phone did not work with a SIM card, constant crash of applications. The YouTube crash, the camera does not take a photo (camera stock), after restarting, the fingerprint disappears (it is not deleted from memory, but it can only be unlocked if you make a new fingerprint) Any heavy application will crash after a while
Click to expand...
Click to collapse
penk3 said:
Thx for u work, I have a reboots after few mins the system starts
nova canL11, cant reply link to adb bugreport logs x_x
Click to expand...
Click to collapse
Sorry guys, no mean to be rude here, but this thread is for development purposes. My point in posting was to give a logcat and receive help to try and fix the bugs I found. I know that when possible, #Henkate gonna take a look and give some directions, so work can be done. So, if you wanna test and see if the rom works for you, that's fine, but provide logs, please. It's good to have other logs and be able to compare if the bugs are the same and I think it can help development a lot (no need to flood with logs either, be reasonable).
Unbrick no screen.
To repair the phone (when there is more image) it must start in fastboot mode and then flash boot image) wait for the phone to go off or remove the battery. When it is off plug the usb cable c on your huawei nova and the phone will show that the phone is charging. Now you can reflash another rom but not lineage os 16. Sorry i use google translation
Android 9 with jdi screen
Android 9 with jdi screen
Amazing near.
As it is known, custom firmware was not friends with the jdi screens.
And here came LOS16 on Android 9. Read reviews that it is now not usable even on smartphones with "normal" screens, what can we say about JDI
But from the realization that he had bought a new phone and having a lot of time, the thought crept in to try to put a fresh custom for total disappointment in his smartphone and quiet use of the new.
However, not everything is so simple. After the first launch, the screen began to flicker well, I thought everything had arrived, now it will get dark and the sensor will fail. Cured with just one reboot. more of this did not happen.
Sim cards did not pull out (I have 2 of them), some wrote that because of them there were some problems crashing and rebooting the system (I don’t have that)
After a night out, the interface began to respond with a delay of 0.5 seconds. (It was cured by a complete reboot) ..
Quickstep launcher is often closed with an error
The camera does not remove the drain, installed from the playlist of the market works without comments.
The navigation bar disappeared after a telephone conversation, when the interlocutor first completed the call (It was decided to reboot)
Vkontakte application crashes, but I use Kate Mobile, it flies with a bang.
YouTube crashes
The sound from the conversational dynamics is quiet, I think you can fix it in the mixer_paths but this is not exactly
Waiting for the moment until the screen fails.
All right, testing 9 android is over!
Discharged the battery to 0, the phone turned off, when turned on, the painfully familiar symptom with the diagnosis "JDI", no image, the screen backlight is on.
Hope no more. I return the phone to the stock and sell it, turn to Meizu pro 7. Thank you all!
R0mi4 said:
All right, testing 9 android is over!
Discharged the battery to 0, the phone turned off, when turned on, the painfully familiar symptom with the diagnosis "JDI", no image, the screen backlight is on.
Hope no more. I return the phone to the stock and sell it, turn to Meizu pro 7. Thank you all!
Click to expand...
Click to collapse
Ты все посты будешь переводить и сюда кидать?) (It is joke)
I have a strange error with the latest Canary-Version.
First of all, I made the app "invisible" via Menue....so I gave it a new name.
Anyway, after the update, when I start the app, the splash screen appears briefly with the familiar icon, then disappears again and reappears.....so every second the app wants to start, but can't.
What is going on there ?
Is there somewhere old versions to which I can wake back ?
// via OnePlus 8T 11.0.7.10
https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-84488771
First thanks to the creator of the script, original post here! I just systematized the steps:
What you need to have - PC(windows or linux), USB cable, and battery above 60%.
1. Download the starberryperl.
2. Download the deeptesting-junk.pl script.
3. Start the "perl command prompt" (it should be the first result when you type "perl" in window's search box) or just standard CMD.
4. Inside the command prompt change to the directory where you had downloaded the script, example:
Code:
cd C:\Users\Admin\Downloads\RMX3311_Unlock
5. Then change to UTF-8 with:
Code:
chcp 65001
6. Run the commands and follow the instructions from the github page. Take care to replace the dummy SERIALNM/HHH... and IMEI1NUMBERHERE/DDD... with your actual serial number and IMEI1!
Quote of the steps:
- Go to Settings/About Device/Status and copy Serial number and IMEI 1
- Then run in the command prompt:
Code:
perl deeptesting-junk.pl pcb 0xSERIALNM imei IMEI1NUMBERHERE cmd applyLkUnlock
- If the answer is
Code:
{"resultCode":0,"msg":"SUCCESS"}
, continue with
Code:
perl deeptesting-junk.pl pcb 0xSERIALNM imei IMEI1NUMBERHERE cmd checkApproveResult
- If the answer is somethink like
Code:
{"resultCode":0,"msg":"SUCCESS","data":{"unlockCode":"0345af...lots of hexdigits"}}
then go to next step.
7. Now follow the official guide how to unlock.
I did it on RMX3311_11.C.10_EU_202303171905 and work fine, the orange warning at boot is there(about unlocked BL).
The attachment contain the script and the apk from links above.
Backing everything up and going to try it right now, so pissed at Realme for locking us out of the Device.
I don't even care if it bricks anymore, gonna report if it works.
//It's 04:14 am, and it worked. I've followed the Instructions, but had the problem, that the device wasn't getting recognized in fastboot mode.
Problem: Phone does not get recognized in fastboot mode on Windows System
That is because the OnePlus Fastboot USB Drivers are NOT SIGNED!
Solution:
You have to restart Windows with advanced startup settings, and deactivate driver signing. So that Windows trusts unsigned drivers.
Then you can restart Windows in that mode, Settings -> windows update -> advanced options -> reset options -> advanced restart.
Go to advanced boot -> deactivate usb driver signing (option 7), start the pc with that option.
AND THEN you can boot your device into fastboot mode, go into your drivers and if it's still coming up as unrecognized, right click it and update it's drivers manually with the oneplus drivers.
Then it should work for you, too. Gave me lots of Headaches.
Thanks for the Guide @b0nb0n3v
/edit: linking here, i've uploaded the boot.img and Oneplus drivers that i used for fastboot mode.
"This phone model does not support deep testing." Is it possible to bypass that screen in the Realme's deep testing app?
Update: after a break for a couple of days, this appears to work again. But probably not for long -- so better try it if and while it's still up ;-) I was able to do just that (and unlock the bootloader on my phone) some two months ago (in...
forum.xda-developers.com
Tried and worked perfectly here! Huge thanks to the creator of the script and the guide!
Oh wow, can we get some development for this device now xd
This is great news! Thank you for posting this!
Worked for me too ! What now ? There arent many ROM available. I need to flash a rom with Call recording. What should I do ? Also is there a way to root ?
Fixed my call recorder issue with BCR module for magisk. Working perfect.
Last thing is battery life. Hope it will be fixed with custom roms.
This is really the worst phone i ever had, with bad battery life an Locked bootloader.
Hi,
I am having trouble with google pay not working because of root i guess. I already cleared cash and had it working twice, but after a while it somehow notices the root and stops working. What am i doing wrong here.
I had similar issues, I've tested if the device passes safetynet and it failed. I've solved it by loading a magisk module, universal safetynet fix 2.4 from here: https://github.com/kdrag0n/safetynet-fix/releases
Now my banking apps and NFC payment work fine. Make sure to put all banking apps in magisk denylist.
wizard8400 said:
I had similar issues, I've tested if the device passes safetynet and it failed. I've solved it by loading a magisk module, universal safetynet fix 2.4 from here: https://github.com/kdrag0n/safetynet-fix/releases
Now my banking apps and NFC payment work fine. Make sure to put all banking apps in magisk denylist.
Click to expand...
Click to collapse
Did the same and it worked a while. I made it work twice, but both times it stopped working after using it a few times.
karayemis said:
Did the same and it worked a while. I made it work twice, but both times it stopped working after using it a few times.
Click to expand...
Click to collapse
I noticed that Play-services is being removed uit denylist by magisk by its self. That mught be the issue
Mine is also unchecked, no issues with banking apps, NFC payments or safetynet. Make sure you select every option under every app so that the blue bar is full and also rename/hide magisk app. Does it pass safetynet?
Yes it passing the test,but somehow play services is being removed from the denylist by its self. I have to select it each time. Also I see that you selected a lot is there any reason for that. I only selected Google Play, play services, Google Pay and wallet
Besed in latest news from realme they stop temporary unlocking for all, to upgrade the server and may be will fix this "exploit"/method. So who unlock it till now is lucky.
Doesn't work anymore for me. Script is working, deep testing app is successfully approved, but the "Start deep testing" button doesn't work as intended, it reboot the phone, show a fastboot message for a split second, and boot to the OS. Fastboot reboot bootloader/fastboot does the same. After reboot, OEM Unlock is automatically activated tho, so it's still doing something.
I've successfully unlocked another GT2 (EU) two days before they did their server "upgrade", so there is definitly something wrong/patched, or maybe the upgrade isn't done yet.
Lightning- said:
Doesn't work anymore for me. Script is working, deep testing app is successfully approved, but the "Start deep testing" button doesn't work as intended, it reboot the phone, show a fastboot message for a split second, and boot to the OS. Fastboot reboot bootloader/fastboot does the same. After reboot, OEM Unlock is automatically activated tho, so it's still doing something.
I've successfully unlocked another GT2 (EU) two days before they did their server "upgrade", so there is definitly something wrong/patched, or maybe the upgrade isn't done yet.
Click to expand...
Click to collapse
They said they'll try to bring back the applications by next week, wait till then
Lightning- said:
Doesn't work anymore for me. Script is working, deep testing app is successfully approved, but the "Start deep testing" button doesn't work as intended, it reboot the phone, show a fastboot message for a split second, and boot to the OS. Fastboot reboot bootloader/fastboot does the same. After reboot, OEM Unlock is automatically activated tho, so it's still doing something.
I've successfully unlocked another GT2 (EU) two days before they did their server "upgrade", so there is definitly something wrong/patched, or maybe the upgrade isn't done yet.
Click to expand...
Click to collapse
Not working for me too, all working but when you click on the "Start deep testing" it reboot and appear the fastboot for a second a reboot instantly on the os.
Waiting next week maybe someone find something
BR4UTAL said:
They said they'll try to bring back the applications by next week, wait till then
Click to expand...
Click to collapse
Any update?
Luigi2201 said:
Any update?
Click to expand...
Click to collapse
Based on this chat, may be this is the end of global BL unlock.