Develop Bugs

What to do with my new useless phone

Hi All,
I just bought a phone for my dad in China, since thats where I live and they are cheap here. I ended up choosing a HTC Desire VC (t328d) which are little known outside China and India.
The point is that I can't do anything with it now. I'm taking it back for him in 2 months and using it in the meantime but it does not have any google stuff on it which makes it a bit like a shoe without a sole. I'm not new to this and have messed around with phones before. I have rooted it and unlocked the bootloader. I've tried putting Google Apps on it loads of different ways and nothing works. I've tried putting it on by flashing it with CWM; installing the apk files individually; and copying the files over to system/apps folder (and changing permissions). I've tried several different downloads and they all fail with a parsing error. Anyway the point is it has failed and I've almost given up. There are no custom roms for it outside China so I could put a Chinese one on and try it all again, but Chinese people don't use google much so google stuff is not included in the roms.
Please can anyone offer advice on what to do with an android phone without google on it? are there any apps that offer similar stuff? where can i get apps from without google play store etc? Sorry for all the questions, I'm just annoyed that the new phone is suddenly pretty useless!
Thanks

Throw it(just kidding).
Exchange....:thumbup:

sanjaykumar.sanjay69 said:
Throw it(just kidding).
Exchange....:thumbup:
Click to expand...
Click to collapse
Not easy since its been rooted.

Gapps
rbnfrance said:
Not easy since its been rooted.
Click to expand...
Click to collapse
find gapps on rom manger,flash them,
if does not work, then pm me, i will tell you another store names.

Pritesh.mohan said:
find gapps on rom manger,flash them,
if does not work, then pm me, i will tell you another store names.
Click to expand...
Click to collapse
Hello all togehter here.
Same here. i got it as a present. i really wanted a dual sim phone.
but it aint work with any google stuff.
now they have told me to put this gapps on it. like the google framework and google accounts. but it doesnt work.
those are just chrashing.
http://pan.baidu.com/share/link?shareid=135061&uk=1493554205
anyhow i have a TCL P600 Phone. its nice as such, but without any apps its pretty simple
any idea what to do?

sixpenny said:
Hello all togehter here.
Same here. i got it as a present. i really wanted a dual sim phone.
but it aint work with any google stuff.
now they have told me to put this gapps on it. like the google framework and google accounts. but it doesnt work.
those are just chrashing.
anyhow i have a TCL P600 Phone. its nice as such, but without any apps its pretty simple
any idea what to do?
Click to expand...
Click to collapse
Yes, its so annoying. This phone is just sitting at the bottom of my drawer now. I have not tried using rom manager, but I'll give it another go when I can bare it.

sixpenny said:
Hello all togehter here.
Same here. i got it as a present. i really wanted a dual sim phone.
but it aint work with any google stuff.
now they have told me to put this gapps on it. like the google framework and google accounts. but it doesnt work.
those are just chrashing.
http://pan.baidu.com/share/link?shareid=135061&uk=1493554205
anyhow i have a TCL P600 Phone. its nice as such, but without any apps its pretty simple
any idea what to do?
Click to expand...
Click to collapse
I also have the TCL P600. I rooted it already and now have it including full gapps. I wait for a multilanguage version now but anyhow it's quite nice now. You can root it like every other MTK6589 phone. Reset button is simply made by holding down power button for more than 5 seconds.
I like the phone since it is rooted and has GAPPS. After rooting just use JB GAPP zip and flash it in CWM. Works great from then on.
Here is the JB gapps zip for flashing with CWM: https://www.dropbox.com/s/zlf4rlbd2rav1nm/gapps-jb-20130301-signed.zip

weimerd said:
I also have the TCL P600. I rooted it already and now have it including full gapps. I wait for a multilanguage version now but anyhow it's quite nice now. You can root it like every other MTK6589 phone. Reset button is simply made by holding down power button for more than 5 seconds.
I like the phone since it is rooted and has GAPPS. After rooting just use JB GAPP zip and flash it in CWM. Works great from then on.
Here is the JB gapps zip for flashing with CWM: https://www.dropbox.com/s/zlf4rlbd2rav1nm/gapps-jb-20130301-signed.zip
Click to expand...
Click to collapse
that mtk6589 was the signalword for me now.
i have already rooted the device and now i am downloading the gapps file of yours. THX for the upload weimerd.
to install with cwm (which is a new word to me) and also i have never rooted a device really (except with odin)
how to install this gapps on the tcl600 ? dual sim will work after as well right?

put the downloaded zip on SD-card.
Power-off the phone.
Power on again while holding power and volume"+" button.
You will boot up into the cwm if you got root on the phone on right way.
- optional: I suggest to make a factory reset now from the menu before installing gapps. But it's not necessary.
Choose "Install zip from sdcard" (choose with power-button, up and down with volume buttons in menu) and install the gapps zip you downloaded.
Reboot the phone and see the gapps
DualSim works perfectly. This is not connected to gapps etc. So it's just that you added all google applications to the phone so you can use your google account, use wheather and news etc.
To really root the phone see here:
TCL P600 root package: http://www.4shared.com/zip/3HRtqraE/TCL_P600_Root.html
HowTo Root TCL P600:
- Extract the file
- Start the flash tool in extracted folder
- Make sure under options it is choosen “with battery”
- In FlashTool load scatter file contained in folder
- Click checkboxes of BOOTIMG and RECOVERY
- Doubleclick on BOOTIMG and refer to TCL-P600_130417__boot_patched_130508-162244.img
- Doubleclick on RECOVERY and refer to TCL-P600_130417__recovery_130508-162244.img
- Switch off mobile and unplug it from usb
- Click “download” in flash tool
- Plug in usb in phone
- If you get a green circle from flash tool saying OK you’re ready with root shell
- Unplug phone and reboot into CWM
- Start Droidtools and plugin usb to phone again
- Install superuser of your choice into phone.
- Ready – you have full root to phone.
If you experience any problems please check if you used the right drivers. Please check drivers attached in folders. Only use them.
I'm not responsible for your phone. If you brick it you have a bricked phone Nevertheless: This worked fine for me and a lot of others.

weimerd said:
by weimerd
Click to expand...
Click to collapse
Hi Weimerd,
i have followed your steps, but some things seem not to be so clear to me. I really want this to work and i see i am close to the final solution, THANKS to your help here.
here is what i have done so far.
1. the device was rooted, i had SU installed (with the usual mt6589_rooter) and booted in CWM, the installation of the zip file from sd started, but was aborted. tried it a couple of times, but result was the same
2. so i decided the facotry reset
to follow your rooting instruction in order to make the rest of the steps happening.
1. downloaded and extraced your file.
2. my phone is connected, i start the flash tool and to as per your instructions
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(see picture 1.jpg)
3. when i say download i get the message that there might be some issues with the booting (see picture 2)
4. so i am thinking maybe all is ok, but the drivers are the problem, i checked the device manager and tried to update the driver (which windows seven said all drivers are up to date) see picture 3 and 4
-
tried the same thing again, switched off my phone before i press download, unplugged it, and then pressed download and re-attached the phone in the switched off mode, drivers are trying to install, this time it is unseccessful, but also here i cant install any driver.
any idea what i am possibly doing wrong here ??

sixpenny said:
Hi Weimerd,
i have followed your steps, but some things seem not to be so clear to me. I really want this to work and i see i am close to the final solution, THANKS to your help here.
here is what i have done so far.
1. the device was rooted, i had SU installed (with the usual mt6589_rooter) and booted in CWM, the installation of the zip file from sd started, but was aborted. tried it a couple of times, but result was the same
2. so i decided the facotry reset
to follow your rooting instruction in order to make the rest of the steps happening.
1. downloaded and extraced your file.
2. my phone is connected, i start the flash tool and to as per your instructions View attachment 1985002(see picture 1.jpg)
3. when i say download i get the message that there might be some issues with the booting View attachment 1985005(see picture 2)
4. so i am thinking maybe all is ok, but the drivers are the problem, i checked the device manager and tried to update the driver (which windows seven said all drivers are up to date) see picture 3 and 4 View attachment 1985006View attachment 1985007
-
tried the same thing again, switched off my phone before i press download, unplugged it, and then pressed download and re-attached the phone in the switched off mode, drivers are trying to install, this time it is unseccessful, but also here i cant install any driver.
any idea what i am possibly doing wrong here ??
Click to expand...
Click to collapse
First of all make sure you switched on USB debugging (in phone settings). Then uninstall any existing driver which may be there. Install only the ones in package.
With the mentioned drivers all should work.
Then make sure you follow the points make sure your phone is not connected to usb and is switched off. Then press "download"-Button and plugin the phone.
At that point normally the phone is beeing recognized by windows the first time asking for a driver. Look into device manager if it is so. Uninstall any existing other driver there for your phone and clean install only the driver in the package.
I see in device manager screenshot one unknown device. Please also check this.
I only have Windows8 here. Don't know if it's same with Win7 but should be. What error is showing when trying to install the driver?
By the way: No problem with the booting issue message of flashtool, you can ignore this.
here is gapps for JB uploaded by me to make sure nothing goes wrong: http://www.4shared.com/zip/apWjF47r/gapps_JellyBean.html

weimerd said:
First of all make sure you switched on USB debugging (in phone settings). Then uninstall any existing driver which may be there. Install only the ones in package.
With the mentioned drivers all should work.
Then make sure you follow the points make sure your phone is not connected to usb and is switched off. Then press "download"-Button and plugin the phone.
At that point normally the phone is beeing recognized by windows the first time asking for a driver. Look into device manager if it is so. Uninstall any existing other driver there for your phone and clean install only the driver in the package.
I see in device manager screenshot one unknown device. Please also check this.
I only have Windows8 here. Don't know if it's same with Win7 but should be. What error is showing when trying to install the driver?
By the way: No problem with the booting issue message of flashtool, you can ignore this.
here is gapps for JB uploaded by me to make sure nothing goes wrong: http://www.4shared.com/zip/apWjF47r/gapps_JellyBean.html
Click to expand...
Click to collapse
hi,
first of all: THANK YOU for your great help and support, i really appreciate your time you have been trying to help me. and actually helped me.
finally managed all drivers and everything as you have described. installed superuser as well and rebooted the device.
i see all google apps. google search is stopping, but i dont care about that.
but what troubles me is a bigger isse : I CANT TYPE...
unfortunately android keyboard has stopped...
now that is an interessting one. any experience with this?
i saw on droid tools i can remove china ? maybe ?

sixpenny said:
hi,
first of all: THANK YOU for your great help and support, i really appreciate your time you have been trying to help me. and actually helped me.
finally managed all drivers and everything as you have described. installed superuser as well and rebooted the device.
i see all google apps. google search is stopping, but i dont care about that.
but what troubles me is a bigger isse : I CANT TYPE...
unfortunately android keyboard has stopped...
now that is an interessting one. any experience with this?
i saw on droid tools i can remove china ? maybe ?
Click to expand...
Click to collapse
Never had that issue. Maybe it is because I upgraded the firmware already with tcl updater before. I suggest to do so, you can re-root it and put gapps on it now
I suggest installing another keyboard. Download one with computer, put apk on sd-card and install it through file manager. Should work

Yeah Weimerd.
done that now, thanks again. but google play is stopping after signing in.
maybe i will do the tcl update after a factory reset and give it once more a try.
if i do facotry reset all will go back as it used to be?

factory reset will most probably not delete root. So just do factory reset and delete dalvik cache (under advanced). Then install gapps zip again. Then reboot. Should work then

I checked this once more.
1. First of all I updated the phone with TCL updater to the latest firmware.
2. I rooted it as I described before.
3. I deleted lots of China Apps and also under system/media bootup sounds and some - for me - other stuff not needed in order to get more space on system partition.
4. I installed GAPPS through CWM. I did it with this one: http://goo.im/gapps/gapps-jb-20121011-signed.zip
After rebooting I also got the crash of google search. I ignored it and added my google account. After opening playstore then I got update for google search. After updating there is no crashing anymore.
All other gapps are working quite well. I tested GPS for the TCL P600 and was really suprised it works quite fast and accurate.
The only thing: There is no A-GPS setting. Let's say: There is no GPS setting at all. You can only switch GPS on and off. Settings are not included. Maybe this will be unlocked with a modded rom.
I'm now testing all functions in detail but up to now it works really great.
Hope you got it also up to this point. After all steps this phone is really perfect.

yes, but i am still struggeling to remove the root, i cleared the dalvik chache, reinstalled everything.
i cant access my google account nor the playstore.
the tcl updater isnt available. or can you show me the icon ?
i think best would be to remove the root and factory reset then and then go ahead and do it all once more.

rbnfrance said:
Hi All,
I just bought a phone for my dad in China, since thats where I live and they are cheap here. I ended up choosing a HTC Desire VC (t328d) which are little known outside China and India.
The point is that I can't do anything with it now. I'm taking it back for him in 2 months and using it in the meantime but it does not have any google stuff on it which makes it a bit like a shoe without a sole. I'm not new to this and have messed around with phones before. I have rooted it and unlocked the bootloader. I've tried putting Google Apps on it loads of different ways and nothing works. I've tried putting it on by flashing it with CWM; installing the apk files individually; and copying the files over to system/apps folder (and changing permissions). I've tried several different downloads and they all fail with a parsing error. Anyway the point is it has failed and I've almost given up. There are no custom roms for it outside China so I could put a Chinese one on and try it all again, but Chinese people don't use google much so google stuff is not included in the roms.
Please can anyone offer advice on what to do with an android phone without google on it? are there any apps that offer similar stuff? where can i get apps from without google play store etc? Sorry for all the questions, I'm just annoyed that the new phone is suddenly pretty useless!
Thanks
Click to expand...
Click to collapse
just try to make your own rom with those existing china roms and roms with google apps.. it is simple, follow this thread. http://forum.xda-developers.com/showthread.php?t=2113479

You may download the TCL updater from here: http://www.tclmobile.com.cn/productsview.php?catid=36&id=462
This is a windows tool for updating your tcl P600. It makes no difference if you decide for P600 or P606, the same firmware will be loaded. The tool will to all flashing, so it's very simple. Just download, install and run the tool, follow the steps and you get a flahed phone. Don't forget to save your data as all will be lost after flashing.
Also root will be gone after flashing with that tool.
---------- Post added at 07:05 AM ---------- Previous post was at 07:04 AM ----------
Aingaran said:
just try to make your own rom with those existing china roms and roms with google apps.. it is simple, follow this thread. http://forum.xda-developers.com/showthread.php?t=2113479
Click to expand...
Click to collapse
It's not as simple as you say. The main problem is that there is no stock rom available as basis. But nevertheless I'll take a shorter look to that

weimerd said:
You may download the TCL updater from here: http://www.tclmobile.com.cn/productsview.php?catid=36&id=462
Click to expand...
Click to collapse
Hi weimerd and all others who are reading this.
1. I have downloaded and installed the tcl updater, it updated the software, the root was gone.
2. then i updated all software with the tcl updater on the phone. software available was still 4.1.2
3. rooted the phone
4. installed the gapps
(there i noticed that its installing 4.2.2 apps)
keyboard is crashing, google play store crashing. same problem as before as i can see it
i will reset it once more and then hope for a final try when i am in the mood again. i sort loosing it over this tclp600, but its such a nice phone.
i like everything about it so far.
just this inability to use it with google standard apps

Towel Root [NE6] - Knox 0x0

So geohot announced last night that he has rooted 4.4.2, its specifically tailored to the S5's with locked bootloaders, but he states it should work on all devices with a kernel older than June 5th (Our latest update, NE6, is dated May 19th).
He also states it shouldnt trigger knox, but he makes no guarantees.
Its also just an apk which is awesome.
Im feeling bold today, so if nobody else gets around to testing it on the tmobile note 3, ill be testing it in a few hours on my lunch.
http://towelroot.com/
http://forum.xda-developers.com/showthread.php?t=2783157
RESTATING OBVIOUS: this isn't my work, all credit goes to geohot, I'm merely linking to it as our phone meets the criteria and should theoretically work works.
UPDATE
Worked without a hitch... Just make sure to install the latest SuperSU (download the zip from chainfires website, and extract SuperSU.apk from common)... It's newer than the play store version.
SuperSU zip:
http://download.chainfire.eu/447/SuperSU/UPDATE-SuperSU-v1.99r4.zip
The play store version of SuperSU has been updated and should work fine now.
1) run towel root ("make it rain"), it will reboot automatically
2) immediatly after reboot, install latest SuperSU (before you run it)
3) run SuperSU, let it update binaries, it will freeze on disabling knox
4) reboot again, run again, disable knox will be successful.
IT DID NOT TRIP KNOX
Just to clarify, this device is a virgin (never been rooted before) running the latest NE6 update...
Restoring to stock (/w nothing tripped) should be as easy as flashing the stock NE6 tar via odin.
UPDATE 2
I can confirm by reply's here, as well as actually trying it on a friends phone that is is not working for NB4, but works perfectly fine on NE6
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SM-N900T using Tapatalk

starnostar said:
So geohot announced last night that he has rooted 4.4.2, its specifically tailored to the S5's with locked bootloaders, but he states it should work on all devices with a kernel older than June 5th (Our latest update, NE6, is dated May 19th).
He also states it shouldnt trigger knox, but he makes no guarantees.
Its also just an apk which is awesome.
Im feeling bold today, so if nobody else gets around to testing it on the tmobile note 3, ill be testing it in a few hours on my lunch.
http://towelroot.com/
http://forum.xda-developers.com/showthread.php?t=2783157
RESTATING OBVIOUS: this isn't my work, all credit goes to geohot, I'm merely linking to it as our phone meets the criteria and should theoretically work.
Click to expand...
Click to collapse
Let me know if it works for you I've got the galaxy s5 for T-Mobile but I'm not sure I want to try it until I've got proof on T-Mobile devices

Worst case scenario if I were to try and right now what would happen
Sent from my SM-N900T using xda premium

Pajar0913 said:
Worst case scenario if I were to try and right now what would happen
Click to expand...
Click to collapse
you would trip knox and/or have to flash a stock tar... ill be testing it in about 30 min.

Keep us updated

There might be bugs since it was intended for the S5. It's not tailored for our devices. Geohot says the same thing. And he didn't say it shouldn't trip knox. Just threw it out there that it didn't trip it for him.
Sent from my SM-N900T using XDA Premium 4 mobile app

Moved to OP

I can confirm that it works following starnostar's instructions.
Sent from my SM-P600 using Tapatalk

So I can go install a custom recovery thereafter
Hello and this is kind of newbee-ish I am an ATT customer looking (actually getting delivery tomorrow) for an N900T - i.e. Tmo Note - which needs to be sim ulocked after it is rooted and then a custom recovery - and then to my fav - an CM ROM.
I think if I do flash a custom recovery - it will trip knox - Just asking here to see if that's true or get some more insights into my plans for the device.
Thanks for reading so far.

Not working 4.4.2 / first time root
I tried rooting following starnostar instructions and it didn't work. The binaries that SuperSU need wouldn't download after the towelroot initial reboot. Tried installing SuperSU (entire directory in file provided) from the phone/SD card with the same result. Did an uninstall of everything a few times. Reboot -> install tr -> reboot -> install SuperSU provided from phone/SD card (either) -> run SuperSU or reboot and run SuperSU. Tried with other super user apps (ChainsDD and ClockworkMod). Same result.
The only things I can think to do are disable Lookout, factory restart the phone or start then stop KNOX (I disabled it a little while back). Any ideas?

Awesome news!!! Being new to rooting in general I'll wait until I see a bit more feedback, but very excited there is a new Knox friendly root available. Thanks for posting!
Sent from my SM-N900T using xda app-developers app

gitofgits said:
I tried rooting following starnostar instructions and it didn't work. The binaries that SuperSU need wouldn't download after the towelroot initial reboot. Tried installing SuperSU (entire directory in file provided) from the phone/SD card with the same result. Did an uninstall of everything a few times. Reboot -> install tr -> reboot -> install SuperSU provided from phone/SD card (either) -> run SuperSU or reboot and run SuperSU. Tried with other super user apps (ChainsDD and ClockworkMod). Same result.
The only things I can think to do are disable Lookout, factory restart the phone or start then stop KNOX (I disabled it a little while back). Any ideas?
Click to expand...
Click to collapse
How did you disable knox without root? if you rooted in the past, maybe residual files left over are causing issues. If this is the case (that you had rooted in the past), maybe a fresh "never-rooted" odin flash is in order.
Another possibility is I used root checker to verify root before installing supersu (i never opened the app, just accepted the prompt), maybe a root prompt must be triggered and granted to complete the process.

starnostar said:
How did you disable knox without root? if you rooted in the past, maybe residual files left over are causing issues. If this is the case (that you had rooted in the past), maybe a fresh "never-rooted" odin flash is in order.
Another possibility is I used root checker to verify root before installing supersu (i never opened the app, just accepted the prompt), maybe a root prompt must be triggered and granted to complete the process.
Click to expand...
Click to collapse
Yeah, I was thinking that I needed a prompt too. I've never attempted root with this phone.
As to KNOX, I just turned it off/disabled it after I did a reset as I did with a handful of things. I was one of the unfortunate few who had to reset after the 4.4.2 upgrade. I did reinstall KNOX, but there was no change. reboot -> install tr - make it ra1n -> reboot -> check - no root access -> install SU - no SU binary to install. Or little variations on that. I'll just wait around a few weeks to see if anyone figures out a solution or factory reset and try again.
Bummer too, I was really looking forward to getting Call Master back. :/

On ne6. Rooted fine and knox 0x0.

Worked for me, Almost forgot the step to (download the zip from chainfires website, and extract SuperSU.apk from common) got errors updating the SuperSU files but its working now!

Help!! Getting error on SuperSU
On Note 3 Tmobile NB4, never rooted, installed Towelroot, rebooted, and installed superSU, when tried to load Super User I get this message,
"There is no SU binary installed, and SuperSU cannot install it. This is a problem!"
Please help!!
zemaj800 said:
Worked for me, Almost forgot the step to (download the zip from chainfires website, and extract SuperSU.apk from common) got errors updating the SuperSU files but its working now!
Click to expand...
Click to collapse

shijocj said:
On Note 3 Tmobile NB4, never rooted, installed Towelroot, rebooted, and installed superSU, when tried to load Super User I get this message,
"There is no SU binary installed, and SuperSU cannot install it. This is a problem!"
Please help!!
Click to expand...
Click to collapse
I initially tried on NB4 but had the same issue, updated to NE6 with Samsung's Kies app and then tried again and it worked fine.

stpinc said:
I initially tried on NB4 but had the same issue, updated to NE6 with Samsung's Kies app and then tried again and it worked fine.
Click to expand...
Click to collapse
I was on NB4 and getting Kies and updating the firmware fixed it for me. Thanks!

Wow, finally a working root solution for our Note 3!
Kies is installed and as soon as I charge my phone, I will update to NE6 and give this a shot!

So u got it working did it trip Knox for u
Sent from my SM-N900T using XDA Free mobile app

[Q&A] Prerooted Stock Images

Q&A for Prerooted Stock Images
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Prerooted Stock Images. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Ever since I installed the recovery menu and the latest pre-rooted FW I've had a few issues I can't seem to pin to anything. For one thing, now every time I reboot I get the Amazon boot splash screen followed by the updating software screen, as though it's installing a new update, which it isn't. Is this normal?
If so I can live with that, but installing the custom FW has now broken the google play store and Aptoide, leaving me sideloading everything. I've tried uninstalling and reinstalling all of the associated APKs but it doesn't make a difference at all. Starting either market just momentarily starts the app just to immediately close it and kick me back to the launcher. Any ideas here?

Trying to get late October 2014 Netflix working on FireTV
I updated my fireTV to bueller-51.1.4.0_514006420-rooted and the new Netflix didn't play videos- some DRM issue. I downgraded to bueller-51.1.3.0_513011820-rooted and had to install Netflix. It was the old version and played fine. I took the Netflix app from 51.1.4.0 before I downgraded:
com.netflix.ninja-1.apk MD5: ae2a3cfa57a599e6bd13069d9928b725
It doesn't install on 51.1.3.0:
>adb install com.netflix.ninja-1.apk
1506 KB/s (8039804 bytes in 5.211s)
pkg: /data/local/tmp/com.netflix.ninja-1.apk
Failure [INSTALL_FAILED_OLDER_SDK]

malacoid said:
I updated my fireTV to bueller-51.1.4.0_514006420-rooted and the new Netflix didn't play videos- some DRM issue. I downgraded to bueller-51.1.3.0_513011820-rooted and had to install Netflix. It was the old version and played fine. I took the Netflix app from 51.1.4.0 before I downgraded:
com.netflix.ninja-1.apk MD5: ae2a3cfa57a599e6bd13069d9928b725
It doesn't install on 51.1.3.0:
>adb install com.netflix.ninja-1.apk
1506 KB/s (8039804 bytes in 5.211s)
pkg: /data/local/tmp/com.netflix.ninja-1.apk
Failure [INSTALL_FAILED_OLDER_SDK]
Click to expand...
Click to collapse
Interesting. Amazon must have bumped their SDK version. I'm going to see if I can easily disable the forced upgrade so the old Netflix might still work on the new version. In the end, I need to figure out what's wrong though.

The "Amazon Kernel Not Patched" error is normal. It's telling you that the image contained a stock Amazon kernel therefore it was not patched. Did you install the alternate Amazon AppStore by chance? I do not have the alternate Amazon AppStore installed and I just upgraded three firetv's in the last 30 minutes. One was on the previous "broken" version so the new Netflix was already installed. It connected immediately and I played a video. I proceeded to upgrade my other two. They both prompted me through the download and installation of the new Netflix. I had to re-enter my credentials in each but they worked.
edit
Doh I tried to reply to the pre-rooted dev thread but it got put here. An admin can delete this.

I am on the 51.1.4.0 prerooted fw and want to update to 51.1.4.1, but I have some hiccups in my current verison. (free time not working, su won't launch) Should I try to fix those issues before attempting to update or will updating hopefully fix those issues??

I have version 51.1.1.0_user_511070220 and have installed Boot Menu with custom recovery 6.0.5.1.4. Can I update custom rom 51.1.4.1_514013920 without installing Pre-Rooted ROM version 51.1.4.0 first? Thanks.

vinhdt1 said:
I have version 51.1.1.0_user_511070220 and have installed Boot Menu with custom recovery 6.0.5.1.4. Can I update custom rom 51.1.4.1_514013920 without installing Pre-Rooted ROM version 51.1.4.0 first? Thanks.
Click to expand...
Click to collapse
NO...
Nov 21, 2014 - Added 51.1.4.1_514013920+fixed (md5sum: 4429327daeed0df852731d81fa9b1f54)
Starting with this update, this requires FireTV Boot Menu.
You also must ensure you have already flashed 51.1.4.0.
Click to expand...
Click to collapse

Y314K said:
NO...
Click to expand...
Click to collapse
Thanks. Also, do I need to remove the Boot Menu and lock the bootloader? Or can I leave it and just install Pre-Rooted ROM version 51.1.4.0 first, reinstall the Boot Menu and then install Pre-rooted 51.1.4.1_514013920? Thanks again.

vinhdt1 said:
Thanks. Also, do I need to remove the Boot Menu and lock the bootloader? Or can I leave it and just install Pre-Rooted ROM version 51.1.4.0 first, reinstall the Boot Menu and then install Pre-rooted 51.1.4.1_514013920? Thanks again.
Click to expand...
Click to collapse
I think once you partially unlock the bootloader you leave it like that.

Y314K said:
I think once you partially unlock the bootloader you leave it like that.
Click to expand...
Click to collapse
Thanks Y314K, I have successfully installed 51.1.4.0. How do I know if my partially unlock bootloader is still there and can I proceed to install the Boot Menu or do I need to check to make sure the bootloader is still unlock first? Thanks.

vinhdt1 said:
Thanks Y314K, I have successfully installed 51.1.4.0. How do I know if my partially unlock bootloader is still there and can I proceed to install the Boot Menu or do I need to check to make sure the bootloader is still unlock first? Thanks.
Click to expand...
Click to collapse
I don't think PreRooted FW flashing will get rid of any of that. If you can still go into the CWM custom recovery 6.0.5.1.4 which requires the unlock bootloader then your good.. I thought you mentioned you already had the boot menu installed ??
Hopefully you have CWM 6.0.5.1.4a installed insead of 6.0.5.1.4...

Firmware upgrade.
I have couple questions...
When upgrading to newer pre-rooted firmware, should I clear cache in recovery?
Another one... I'm on 51.1.4.0, rooted, boot menu, recovery... If I want to start over what is the best way? What needs to be cleared (data in recovery?), reset option in FTV launcher? Will recovery and boot menu stay?

how can you delete the prerooted images that are on the SD card? I cant find them in Es File explorer.
I can see them here in CWM though...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Dolphin Browser crashes on Prerooted 51.1.4.0_514006420
I have prerooted 51.1.4.0_514006420 version on my FireTV and I want to report that Dolphin Browser will crash if Jetpack is turned on. Is this also happening on the latest prerooted version ?
Dolphin Browser with Jetpack was working fine on prerooted version 51.1.3.0_513011820

lowbee said:
I have prerooted 51.1.4.0_514006420 version on my FireTV and I want to report that Dolphin Browser will crash if Jetpack is turned on. Is this also happening on the latest prerooted version ?
Dolphin Browser with Jetpack was working fine on prerooted version 51.1.3.0_513011820
Click to expand...
Click to collapse
You should probably complain to the Dolphin developers...

mroneeyedboh said:
how can you delete the prerooted images that are on the SD card? I cant find them in Es File explorer.
I can see them here in CWM though...
Click to expand...
Click to collapse
You would need to do it from ADB or the way I do it is I use ES File Explorer or a similar app. If it's a Google Store app you might need a mouse to control it right. Since they are touch based. Holding the button press for a while over a file will give you the option to move/copy/delete it.

Just wondering if prime videos stopped working for anyone else?
I am on the latest pre rooted and tried to watch a video last night and it errored out.
At work now and can't give the exact error message but it was a dialog that I believe said unknown error has occured.
Worked fine a few days ago.

snorkel01 said:
Just wondering if prime videos stopped working for anyone else?
I am on the latest pre rooted and tried to watch a video last night and it errored out.
At work now and can't give the exact error message but it was a dialog that I believe said unknown error has occured.
Worked fine a few days ago.
Click to expand...
Click to collapse
I was watching prime last night just fine.

rbox said:
I was watching prime last night just fine.
Click to expand...
Click to collapse
OK, found out what the issue was. I was unaware but if XBMC/KODI is left suspended in the background, i.e. you hit the home button on the remote without exiting XBMC/KODI the
prime video does not work. I can do it everytime.
Not a big deal I guess.

Magisk & V4a installation issues

So, I went to change a few settings in V4A yesterday and the icon was missing. I could open the app by searching for it, sometimes it would show the icon, sometimes it would show the system app name "com.xxx.xxx" or whatever it is called. For the record, I have had no issues in the past with installing or running Magisk or V4a.
I decided I'd uninstall it, and reinstall to see if it would fix it.
I went into Titanium Backup and backed up the app and data.
Went to Magisk, uninstalled
Rebooted
Attempted to reinstall in Magisk, and it the install hangs
What resulted was a vicious loop of me trying to install uninstall, with the result being every time the install hangs in Magisk.
I'm wondering if this is a Magisk problem or a V4A problem, or an issue with Google protect being goofy with this app?
Just want to get my beloved V4A back =]
Thanks for your help.
I'm on latest Stock Pie with Latest Kirisakura Kernel.

The issues that I always had with v4a was that when I went to update it would install the update and then it would keep trying to load the driver after reboot. I ended up just going into magisk and manually uninstalling it before I went to install the update. And then it works great. I never backed up the settings in titanium before. I just saved my settings in the 'profile' page of the v4a and it always stays when I update. I update it and then load the old profile and move on with life.
So I am not sure if it was the titanium backup that messed it up or the lack of uninstall prior to the install of the updated version, I am, again, not sure. But I hope that this may help?

Yeah, I'm confident it wasn't anything to do with TiBu.
Incidentally, I later tried restoring the TiBu backup, but it just hung, as I anticipated. Perhaps I'll have to just do a clean install. Something got mucked up the first time the install hung I'm guessing.

MeetFace said:
Yeah, I'm confident it wasn't anything to do with TiBu.
Incidentally, I later tried restoring the TiBu backup, but it just hung, as I anticipated. Perhaps I'll have to just do a clean install. Something got mucked up the first time the install hung I'm guessing.
Click to expand...
Click to collapse
The more that I think about my experience with viper4android. I once also had that same issue where the icon would disappear. Ultimately I ended up manually uninstalling and reinstalling from the magisk repository and it seemed to work after that.
I understand the concept of titanium backup, however, I have, personally, never had any luck with any of the backups that I've ever made on reinstalling things. So honestly I don't really use Titanium Backup.

brandonpa said:
The more that I think about my experience with viper4android. I once also had that same issue where the icon would disappear. Ultimately I ended up manually uninstalling and reinstalling from the magisk repository and it seemed to work after that.
I understand the concept of titanium backup, however, I have, personally, never had any luck with any of the backups that I've ever made on reinstalling things. So honestly I don't really use Titanium Backup.
Click to expand...
Click to collapse
Thanks Brandon, did you just uninstall and reinstall Magisk in TWRP?
Any more, I typically just use TiBu to back up data on my apps for when I clean install, which isn't often anymore. The beauty of undefiled android is I can typically dirty flash monthlies without issue.

MeetFace said:
Thanks Brandon, did you just uninstall and reinstall Magisk in TWRP?
Any more, I typically just use TiBu to back up data on my apps for when I clean install, which isn't often anymore. The beauty of undefiled android is I can typically dirty flash monthlies without issue.
Click to expand...
Click to collapse
I just did it all through magisk.

MeetFace said:
Just want to get my beloved V4A back =]
.
Click to expand...
Click to collapse
I've been in this cycle before. What's worked for me is deleting the module in magisk, rebooting, downloading the module with magisk (don't install, just download) and then flashing the zip with EXKM app.
My install options are as follows - New Version of Viper --> Material Theme --> Install as System App. For some reason when I install the original themed version I get the "driver failed to install" message and have to start over again.

That is the exact process I go through when I update. I just use magisk to reinstall versus the exkm program.

This is puzzling. I removed the module, rebooted , downloaded, rebooted to TWRP, installed zip.
App icon doesn't show up, but when I search, I get this and I am able to open and it says it's processing:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Pixel 3 XL using Tapatalk

ffchampmt said:
I've been in this cycle before. What's worked for me is deleting the module in magisk, rebooting, downloading the module with magisk (don't install, just download) and then flashing the zip with EXKM app.
My install options are as follows - New Version of Viper --> Material Theme --> Install as System App. For some reason when I install the original themed version I get the "driver failed to install" message and have to start over again.
Click to expand...
Click to collapse
This method works and on first reboot driver status is normal but on subsequent reboots driver status shows neon enabled=no and driver status=abnormal. If I use Magisk to flash V4a then there's no icon on reboot as mentioned previously. All this didn't begin till I installed Magisk 19.

MeetFace said:
This is puzzling. I removed the module, rebooted , downloaded, rebooted to TWRP, installed zip.
App icon doesn't show up, but when I search, I get this and I am able to open and it says it's processing:
Click to expand...
Click to collapse
Same here

I'm starting to believe this is a Magisk problem since updating?
The YouTube Vanced icon appears and disappears as well.
Sent from my Pixel 3 XL using Tapatalk

[HELP] No sim card icon after upgrade to last version of magisk 25.2

Like the title said after upgrade magisk to v25.2 i receive no sim card icon also seems like i lost my root after this....
someone can help me pls?

roberto_1986 said:
Like the title said after upgrade magisk to v25.2 i receive no sim card icon also seems like i lost my root after this....
someone can help me pls?
Click to expand...
Click to collapse
Magisk shouldn't have affected your SIM card icon in any way.
Open your phone app and type: *#06# and tell us if you get both IMEI numbers. You can also check this in Settings (the location will vary depending on which ROM you're using).
Compass.

Compass Linux said:
Magisk shouldn't have affected your SIM card icon in any way.
Open your phone app and type: *#06# and tell us if you get both IMEI numbers. You can also check this in Settings (the location will vary depending on which ROM you're using).
Compass.
Click to expand...
Click to collapse
Yes i can see both IMEI and ICCID 1 and SERIAL NUMBER!!!
I root my phone with LR TWRP-3.3.1-1104 that come with magisk v20 by default!
then from magisk im update first the app to 25.2 then magisk but when i put my magisk to 25.2
i receive no sim card icon....what i can do>???
its a week im stuck....>.<

roberto_1986 said:
Yes i can see both IMEI and ICCID 1 and SERIAL NUMBER!!!
I root my phone with LR TWRP-3.3.1-1104 that come with magisk v20 by default!
then from magisk im update first the app to 25.2 then magisk but when i put my magisk to 25.2
i receive no sim card icon....what i can do>???
its a week im stuck....>.<
Click to expand...
Click to collapse
Since I don't know what you've done to your phone, I recommend you the following:
Backup all your data;
Flash the latest MIUI fastboot ROM according to what you want (12.0.x for A10; 12.5.x for A11/A12/A13) with data format and don't re(lock) your bootloader;
Install the Custom ROM of your choice.
Some Custom ROMs pass SafetyNet by default, so there's no need to install any SafetyNet module neither Magisk Hide Props Config.
Instead of Magisk you could try Magisk Delta. I've never used it but it exists.
In the TeleGram groups people have been avoiding Magisk 25.2. I'm using 24.3 here.
Compass.

Compass Linux said:
Since I don't know what you've done to your phone, I recommend you the following:
Backup all your data;
Flash the latest MIUI fastboot ROM according to what you want (12.0.x for A10; 12.5.x for A11/A12/A13) with data format and don't re(lock) your bootloader;
Install the Custom ROM of your choice.
Some Custom ROMs pass SafetyNet by default, so there's no need to install any SafetyNet module neither Magisk Hide Props Config.
Instead of Magisk you could try Magisk Delta. I've never used it but it exists.
In the TeleGram groups people have been avoiding Magisk 25.2. I'm using 24.3 here.
Compass.
Click to expand...
Click to collapse
Ty for your answer!!!
Im always used stock ROM with A9 (the last firmware before A10) V11.0.3.0.PGGEUXM with Magisk v25.2
and LR TWRP-3.3.1-1104 without problem...
Only now i get this problem and its weird...also im followed this guide to root my phone:
[GUIDE][BEGONIA]Unlock Bootloader, Flash TWRP and Root[PROPER]
/* * 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 in...
forum.xda-developers.com
Why i dont need to relock when use MI Flash??? tbh im always leaved as default without problem...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also everytime i made a fresh install im used "advanced wipe" in recovery and delete everything system too
withouth problem!!!
Witch custom rom u suggest is the best to be installed? usually im prefer stock rom because the custom rom has some bugs so i prefer stay on stock rom but if there is some custom rom that is better then stock why not!!!

roberto_1986 said:
Ty for your answer!!!
Im always used stock ROM with A9 (the last firmware before A10) V11.0.3.0.PGGEUXM with Magisk v25.2
and LR TWRP-3.3.1-1104 without problem...
Only now i get this problem and its weird...also im followed this guide to root my phone:
[GUIDE][BEGONIA]Unlock Bootloader, Flash TWRP and Root[PROPER]
/* * 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 in...
forum.xda-developers.com
Why i dont need to relock when use MI Flash??? tbh im always leaved as default without problem...
View attachment 5804157
Also everytime i made a fresh install im used "advanced wipe" in recovery and delete everything system too
withouth problem!!!
Witch custom rom u suggest is the best to be installed? usually im prefer stock rom because the custom rom has some bugs so i prefer stay on stock rom but if there is some custom rom that is better then stock why not!!!
Click to expand...
Click to collapse
I recommend using the "clean all" option. If you use "clean all and lock" you'll relock your bootloader, and won't be able to flash fastboot ROMs anymore (for example). You won't be able to root either.
If you prefer stock ROMs use them. The matter of which custom ROM is better is an never ending discussion.
Compass.

Compass Linux said:
I recommend using the "clean all" option. If you use "clean all and lock" you'll relock your bootloader, and won't be able to flash fastboot ROMs anymore (for example). You won't be able to root either.
If you prefer stock ROMs use them. The matter of which custom ROM is better is an never ending discussion.
Compass.
Click to expand...
Click to collapse
Im use clean and lock because then im unlock with MI UNLOCK!!!
Im updated again magisk to v25. 2 because i wanna test when i get no sim card icon if it show my imei and it show it but with the difference that instead of write IMEI its write HEX IMEI...why???
Also i cant understand yet why if i update to last version i get no sim card icon???

roberto_1986 said:
Im use clean and lock because then im unlock with MI UNLOCK!!!
Im updated again magisk to v25. 2 because i wanna test when i get no sim card icon if it show my imei and it show it but with the difference that instead of write IMEI its write HEX IMEI...why???
Also i cant understand yet why if i update to last version i get no sim card icon???
Click to expand...
Click to collapse
If you relock your bootloader you'll have to wait 168 hours to unlock it again. Your choice.
I've never seen the message "HEX IMEI" and I don't know what that means.
If you flashed the MIUI fastboot ROM you wanted and the SIM card icon is there, you're doing something that's removing it. You have to find out what that is and avoid doing it again.
Compass.

Compass Linux said:
If you relock your bootloader you'll have to wait 168 hours to unlock it again. Your choice.
I've never seen the message "HEX IMEI" and I don't know what that means.
If you flashed the MIUI fastboot ROM you wanted and the SIM card icon is there, you're doing something that's removing it. You have to find out what that is and avoid doing it again.
Compass.
Click to expand...
Click to collapse
Hey!!!
Nope only the first time u have to wait 168 hr!!! then u unlock without wait!!!
Yhea im flash the ROM as fastboot with MI flash
OK seems like we didnt find it why i have this problem...well then later im try to update magisk only to v24.3
and how about magisk app? i can upgrade to last version??
Ty anyway for your support >,<

roberto_1986 said:
Hey!!!
Nope only the first time u have to wait 168 hr!!! then u unlock without wait!!!
Yhea im flash the ROM as fastboot with MI flash
View attachment 5804445
OK seems like we didnt find it why i have this problem...well then later im try to update magisk only to v24.3
and how about magisk app? i can upgrade to last version??
Ty anyway for your support >,<
Click to expand...
Click to collapse
I think you are able to unlock immediately because your device is still linked to your Mi account. If you try unlocking a new device the 168 hours should kick in.
I don't see how Magisk is related to your problem, but try Magisk 24.3 instead of 25.2 and see if that works. This is the first time I've heard of Magisk affecting the Sim card icon.
Compass.

Compass Linux said:
I think you are able to unlock immediately because your device is still linked to your Mi account. If you try unlocking a new device the 168 hours should kick in.
I don't see how Magisk is related to your problem, but try Magisk 24.3 instead of 25.2 and see if that works. This is the first time I've heard of Magisk affecting the Sim card icon.
Compass.
Click to expand...
Click to collapse
Ok im just finished to make fresh install + ROOT with magisk v24.3 and magisk app v25.2 + safity net 2.3.1 (passed)
and seems like everything working just fine appart i cant change name at magisk...when i try it tell me failed....
also when i was updating all app my messages app keep crashing but after update no more.
- Why i cant hide magisk by changing name?
- Im hide google play services with deny list but if i reboot my phone he gone from deny list and i need to put again...
appart google play services witch file i need to put in deny list???
ty so much!!!

roberto_1986 said:
Ok im just finished to make fresh install + ROOT with magisk v24.3 and magisk app v25.2 + safity net 2.3.1 (passed)
and seems like everything working just fine appart i cant change name at magisk...when i try it tell me failed....
also when i was updating all app my messages app keep crashing but after update no more.
- Why i cant hide magisk by changing name?
- Im hide google play services with deny list but if i reboot my phone he gone from deny list and i need to put again...
appart google play services witch file i need to put in deny list???
ty so much!!!
Click to expand...
Click to collapse
Why are you mixing Magisk 24.3 and Magisk 25.2? Use only Magisk 24.3! Then verify SafetyNet is passing using YASNAC (Google Play Store).
The fact that you can't spoof Magisk neither permanently add Google Play Services to the Deny List seems to indicate that your bootloader isn't unlocked or SafetyNet isn't passing.
You'll keep having issues by mixing Magisk versions.
Compass.

Compass Linux said:
Why are you mixing Magisk 24.3 and Magisk 25.2? Use only Magisk 24.3! Then verify SafetyNet is passing using YASNAC (Google Play Store).
The fact that you can't spoof Magisk neither permanently add Google Play Services to the Deny List seems to indicate that your bootloader isn't unlocked or SafetyNet isn't passing.
You'll keep having issues by mixing Magisk versions.
Compass.
Click to expand...
Click to collapse
Idk wtf its going on here...im checked now on Settings > Additional Settings > Developer Options and seems like my device isnt unlocked but if i reboot my phone on the bottom tell me is unlocked...i pretty sure my phone was unlocked...
I never had all this issues....i will try again to root or i will buy new phone...>,>

roberto_1986 said:
Idk wtf its going on here...im checked now on Settings > Additional Settings > Developer Options and seems like my device isnt unlocked but if i reboot my phone on the bottom tell me is unlocked...i pretty sure my phone was unlocked...
I never had all this issues....i will try again to root or i will buy new phone...>,>
Click to expand...
Click to collapse
The easiest way to know if any Xiaomi phone has an unlocked bootloader is by turning it on and looking at the top for a opened padlock () during the initial boot process.
Compass.

Compass Linux said:
The easiest way to know if any Xiaomi phone has an unlocked bootloader is by turning it on and looking at the top for a opened padlock () during the initial boot process.
Compass.
Click to expand...
Click to collapse
Yhea on RN8P its on bottom!
The weird thing is on opening tell me its unlocked but on Developer Options no because when its unlocked i cant add MI account account and its on grey so u cant click it!
instead when its locked i can add mi unlock like in this screenshot below...
k
Later i will try again....ty for your effort on help me.

Spoiler: lll
lll
roberto_1986 said:
Yhea on RN8P its on bottom!
The weird thing is on opening tell me its unlocked but on Developer Options no because when its unlocked i cant add MI account account and its on grey so u cant click it!
instead when its locked i can add mi unlock like in this screenshot below...
kView attachment 5804923
Later i will try again....ty for your effort on help me.
Click to expand...
Click to collapse
You're using an older MIUI so the location of the open padlock is different? OK. I haven't used anything based on MIUI 11.x for a while.
Perhaps because you have an unlocked bootloader it doesn't allow you to select the Unlock Status neither add a MIUI account (probably due to security reasons).
Compass.

Compass Linux said:
Spoiler: lll
lll
You're using an older MIUI so the location of the open padlock is different? OK. I haven't used anything based on MIUI 11.x for a while.
Perhaps because you have an unlocked bootloader it doesn't allow you to select the Unlock Status neither add a MIUI account (probably due to security reasons).
Compass.
Click to expand...
Click to collapse
OK this time i will try to upgrade to A10...maybe its just time to upgrade to new version also A10 its a mature version because now there is A11!!! i will test and let u know!

Ok @Compass Linux
Im finished now to install A10 - V12.0.5.0.QGGEUXM on my phone!!!
Also finaly im installed with no problem both magisk / app 25.2 with no problem!!!
But i noticed 2 problem...
- The first its i renamed magisk to hide but now i have 2 app...1 renamed + magisk...im reboot phone but app still there
so i can uninstall normal magisk???
- The second problem its on modules...I have this module (.core) blank...usually i received this on A9 when i tryed to install last version on magisk that cause me a problem so i can delete this module???
whats its that???
Again i wanna tell u ty so much for all your effort to help me^^

EDIT:
- Fixed the magisk app cloned while im tryed to hide.
- Got another problem...im successfully unloked bootloader but after reboot my phone "Unlock OEM" its not anymore
grey like its happened when i was on A9....what did u think its the problem???
Also when i reboot my phone on up side i can see the lock its unlocked.

roberto_1986 said:
Ok @Compass Linux
Im finished now to install A10 - V12.0.5.0.QGGEUXM on my phone!!!
Also finaly im installed with no problem both magisk / app 25.2 with no problem!!!
But i noticed 2 problem...
- The first its i renamed magisk to hide but now i have 2 app...1 renamed + magisk...im reboot phone but app still there
so i can uninstall normal magisk???
View attachment 5805113
- The second problem its on modules...I have this module (.core) blank...usually i received this on A9 when i tryed to install last version on magisk that cause me a problem so i can delete this module???
whats its that???
View attachment 5805117
Again i wanna tell u ty so much for all your effort to help me^^
Click to expand...
Click to collapse
I don't know what this module is.
Compass.