Related
Since it is using Android 2.1 we cannot seem to install Flash player from the LExi Market there is no Android market on the tablet. Cannot find any information on upgrading the OS to a newer version.
Any one no much about the tablet? updates ,rooting any information would be good news.
Some here could advise me please , if I was able to root this tablet with visonary even temp root could I then copy android Markey to system/app to get access to the market?
Same question to me... I have the LexiTab Neon and can´t find any way to root!
Bringer1 said:
Same question to me... I have the LexiTab Neon and can´t find any way to root!
Click to expand...
Click to collapse
This device is almost 10 years old, it wouldn't be worth it anyway, most of today's apps don't work with android versions older than 4.4-5.0 and your device wouldn't be able to handle android 5.0, it would be way too slow and unstable.
Sent from my SM-S767VL using Tapatalk
Hello all,
I recently rooted my Samsung Galaxy S4, running on Android 5.0.1 lollipop, and am using SuperSU to try and get SB Game Hacker, Game Killer or something to work. I have tried all of Game hacker's versions and none of them work, and Game killer says that it needs root privileges to work, although I have already checked and my phone definitely rooted successfully and I went into SuperSU and gave it root privileges too. Whenever I open Game killer I grant it root access but it never works, and although I would much rather use SB Game Hacker, I know this doesn't yet work in Lollipop. I have again tried various versions of game killer and it seems that 3.11 works best.
If anyone wants any more information to help work this out, I'd be glad to respond. And if anyone knows how to fix this anyway, I am always happy to find out.
With regards,
Atcman77
The official link to download it leads me to a website where I wait 120 seconds, click the download link and it sends me back to where I started. Also, I got this from Aptoide and not onhax
Hi, thank you for using XDA Assist. XDA does not support or condone the use of warez. See rule #6, http://forum.xda-developers.com/announcement.php?a=81
Thread closed.
Deleted. Beaups released a full unlock using this. No need.
npjohnson said:
All,
Due to the recent accidental leak of Samsung eMMC vendor commands allowing write to protected eMMC areas, we are now able to write CID values on production devices.
Beaups has written an awesome tool called 'SamsungCID' (found here: https://github.com/beaups/SamsungCID). This makes the process all teh simpler!
I have built this tool from his source, and used it on a multitude of devices that use a Samsung eMMC. It works without flaw on the Moto G (Second Generation), Galaxy S5 (VZW/ATT, though, ATT doesn't have a Developer Edition that I am aware of), and many, many others.
How does this apply to you?
The S5 uses a Samsung eMMC, and has a Developer Edition. This means that it is vulnerable to this exploit.
How can I help this progress?
I need a few thing to make this work:
- A few testers with Production devices, and root (temp-root should work fine) -- I will contact these people individually, do not ask here to test.
- One person with a Developer Edition that has root (need an aboot dump, and them to run one command).
If any of you know of someone with a Developer Edition, please get them in contact with me. I can be reached on Hangouts, or on Telegram (@npjohnson).
PLEASE do not post your CID publicly.
I will be trying to package this into an app that will extend across multiple vulnerable devices.
Click to expand...
Click to collapse
I know we'll be able to get a bootloader unlock from this, but hopefully we'll be able to get it done ASAP. I've already moved on to the Nexus 6, but I'd still love to have my S5's bootloader unlocked anyway. Good luck with this, I can't wait.
npjohnson said:
All,
Due to the recent accidental leak of Samsung eMMC vendor commands allowing write to protected eMMC areas, we are now able to write CID values on production devices.
Beaups has written an awesome tool called 'SamsungCID' (found here: https://github.com/beaups/SamsungCID). This makes the process all teh simpler!
I have built this tool from his source, and used it on a multitude of devices that use a Samsung eMMC. It works without flaw on the Moto G (Second Generation), Galaxy S5 (VZW/ATT, though, ATT doesn't have a Developer Edition that I am aware of), and many, many others.
How does this apply to you?
The S5 uses a Samsung eMMC, and has a Developer Edition. This means that it is vulnerable to this exploit.
How can I help this progress?
I need a few thing to make this work:
- A few testers with Production devices, and root (temp-root should work fine) -- I will contact these people individually, do not ask here to test.
- One person with a Developer Edition that has root (need an aboot dump, and them to run one command).
If any of you know of someone with a Developer Edition, please get them in contact with me. I can be reached on Hangouts, or on Telegram (@npjohnson).
PLEASE do not post your CID publicly.
I will be trying to package this into an app that will extend across multiple vulnerable devices.
Click to expand...
Click to collapse
cant wait to see this going
So how have you gone about compiling and running this? Try as I may I can't seem to do a proper build. It's probably the lowest of the low, but if you could send me a binary, I'd greatly appreciate it
I'd be more than willing to try it on my rooted verizon s5.
Successfully compiled the tool - currently scouring the internet looking for anyone with a developer edition that might be able to help, we should have this done in no time. Have already sent out messages to a few, will look for more. I'll PM you if I get any details
Kinda cool watching this unfold over a few weeks, I'm really excited for what's to come.
You all need to check something else first, you need your current CID
If it starts with anything other than 15, this will not work for you. Samsung EMMC's start with CID 15, Toshiba 11, and there may be more. If you Don't start with 15, this WILL NOT WORK.
Regarding a compiled verison
http://s000.tinyupload.com/?file_id=64141875024257149501
Yeah...unfortunately mine starts with an 11 :c
Yep, mine starts with a 15. I'm ready to start any testing. All of my possible developer editions have fallen through - many requesting a purchase of the actual phone. I'll keep looking, but I might be outta options atm.
I can't believe all we need to open this phone up is a dev phone for a few minutes. It would add new life. I'm searching out people as well. Hopefully we find something soon
Mine starts with a 15 and it's not my daily driver, count me in for testing!
Question. Didn't someone post in one of the forums (General or Android Development) about them having a Walmart Straight Talk S5 and that it was actually a VZW Dev Ed? Because he was wanting to put a CM ROM on it. If that's true, then we also need to find anyone with that particular device as well. If i can find the thread it was posted in I'll add the link. Found the links. If it's true we need to see if these variants could help out.
http://forum.xda-developers.com/showpost.php?p=65432642&postcount=48
http://forum.xda-developers.com/showpost.php?p=65143644&postcount=1
al50 said:
Question. Didn't someone post in one of the forums (General or Android Development) about them having a Walmart Straight Talk S5 and that it was actually a VZW Dev Ed? Because he was wanting to put a CM ROM on it. If that's true, then we also need to find anyone with that particular device as well. If i can find the thread it was posted in I'll add the link. Found the links. If it's true we need to see if these variants could help out.
http://forum.xda-developers.com/showpost.php?p=65432642&postcount=48
http://forum.xda-developers.com/showpost.php?p=65143644&postcount=1
Click to expand...
Click to collapse
That's actually brilliant. It MIGHT work, but even though they have identical hardware, I don't know if that guarantees that it will have a compatible bootloader - unless it does, in which case that's amazing, and we need to get a hold of someone with one asap. Unless they are the same model, just rebranded, I don't see this working as the bootloaders may not be signed with Verizon's keys.
True. Forgot about the VZW keys... Was thinking too much of finding a Dev Ed....lol
al50 said:
True. Forgot about the VZW keys... Was thinking too much of finding a Dev Ed....lol
Click to expand...
Click to collapse
Don't give up hope so fast. I'm getting in contact with a few people, and I'll certainly try it. This may actually be the same phone, I see a lot of websites suggesting Straight Talk phones are the exact same as Verizon ones. We shall see. My information about the keys might not even be accurate, with my limited knowledge.
It was a good thought though, even if it isn't true
How can you compile it? I'm running Ubuntu 14.04.1 and i can't even get NDK to install correctly.. Any help?
CreeperPVP said:
How can you compile it? I'm running Ubuntu 14.04.1 and i can't even get NDK to install correctly.. Any help?
Click to expand...
Click to collapse
Hmm. I dunno. I'm currently on Windows - there wasn't really any installation for NDK, just running from the extracted folder. I can post a link to a compiled version of the program, I'm pretty sure someone in another thread posted one.
---------- Post added 30th March 2016 at 12:02 AM ---------- Previous post was 29th March 2016 at 11:59 PM ----------
Here's a link to the thread, the OP has a link at the bottom. http://forum.xda-developers.com/showthread.php?t=3337909
Is there a way to check CID from the phone? I can't seem to find out how to check it, build prop and whatnot doesn't have anything about it like some places suggest, and can't use fastboot.
Sent from my SAMSUNG-SM-G900A using Tapatalk
Rakuu said:
Is there a way to check CID from the phone? I can't seem to find out how to check it, build prop and whatnot doesn't have anything about it like some places suggest, and can't use fastboot.
Sent from my SAMSUNG-SM-G900A using Tapatalk
Click to expand...
Click to collapse
Use eMMC brickbug checker on the play store. First 2 numbers of your cid should be 11 or 15. You want 15
Rakuu said:
Is there a way to check CID from the phone? I can't seem to find out how to check it, build prop and whatnot doesn't have anything about it like some places suggest, and can't use fastboot.
Sent from my SAMSUNG-SM-G900A using Tapatalk
Click to expand...
Click to collapse
Search google play for "eMMC Brickbug Check"
Sent from my SM-G900V using Tapatalk
Welcome.
Very short about me: Most of you know me as ieatgravity, I ported TWRP Recovery a little less than a year ago and was able to achieve root on the Life One X2. Since then I have developed guides, auto rooting tools, roms, and I maintain BLOX2.com a dedicated site for all Life One X2 and Mini Development. I apologize for the long absence. However it seems as if this community has really bloomed from where I left off. I want to thank EVERYONE who has supported this development for our phone over the last year, whether it be financially, simple encouragement, thanks, prayers, or you even helping develop something new. I tried my best to credit everyone involved, though many have come and gone we hope YOU will take an interest and try your hand at developing!
As of now we have all been using the first thread we had for our device as a catch all for development, apps, support, general q&a's. Though it has worked for us up until now, a few of us have decided that we should have a dedicated thread to development ideas, topics and questions to keep everything organized.
For now this thread will support both the X2 & Mini. So when you post, please specify the device.
Table of contents:
List of current development to date
Great "How To's" and Guides
With all of that said, here is a consolidated list of all development to this date. If you don't see something on here please let me know and I will update it.
Roms
X2:
Stock - ieatgravity
Blox2core - ieatgravity
Lineage OS 13 - srgrusso
Drax - Draco
X2 Mini:
Stock - papacharlieecho
Minicore - papacharlieecho
Lineage OS 13 - srgrusso
Drax Mini - ieatgravity
Kernels
X2:
Butter Kernel - Draco
X2 Mini:
N/a
Apps:
Both:
Ultra Power Saver - Draco
CRAB-Custom Recovery Automated Backup- Draco
Similar devices
X2:
Redmi 3s
X2 Mini:
Yu Black
Wiko U codeFeel Prime
Source:
X2:
Source
Device Tree
X2 Mini:
TBA
In the next post I will go over methods we have used to create everything. If you have any recommended methods on porting or how to do something feel free to add them. I will be updating and adding to this OP as new things come to light. Feel free to use this thread to post questions about or to show off your new development.
as always, Happy modding
-ieatgravity
Reserved for how tos and guides
Reserved
Another Reserve
Yet another reserved
Hi ieatgravityI have a question for you, I think you can help me. I have one wiko Ufeel prime and I rooted the phone blox2 or with drako auto-root tool wen it hade marshmallow Android. Do you no if this works in nougat 7.1.1? My thanks in advance ?
alex moymoy said:
Hi ieatgravityI have a question for you, I think you can help me. I have one wiko Ufeel prime and I rooted the phone blox2 or with drako auto-root tool wen it hade marshmallow Android. Do you no if this works in nougat 7.1.1? My thanks in advance ?
Click to expand...
Click to collapse
Personally I haven't tried. As I'm still running on marshmallow, but from what I gathered from the wiko thread i started months ago the auto root tools were not successful. So for the time being there is no root for 7.1.1
I confirm we can't flash anything in fastboot mode on ufeel prime 7.1.1.
We are looking for since September. Impossible to root.
foxyone0809 said:
I confirm we can't flash anything in fastboot mode on ufeel prime 7.1.1.
We are looking for since September. Impossible to root.
Click to expand...
Click to collapse
Has anyone attempted using Kingroot.apk (NOT KINGOROOT) to root then use a root flasher like flashify, rashr, official twrp app, to flash the custom recovery. From there root using magisk manager patch the boot.img, reboot into twrp then flash the patched_boot.img to boot partition. While still in TWRP, navigate to the kingroot.apk location within /system/app. Delete the kingroot.apk and reboot. At this point you should have a working systemless root without the sketchiness of using kingroot.
If anyone has the time to test this out let me know the results please.
ieatgravity said:
Has anyone attempted using Kingroot.apk (NOT KINGOROOT) to root then use a root flasher like flashify, rashr, official twrp app, to flash the custom recovery. From there root using magisk manager patch the boot.img, reboot into twrp then flash the patched_boot.img to boot partition. While still in TWRP, navigate to the kingroot.apk location within /system/app. Delete the kingroot.apk and reboot. At this point you should have a working systemless root without the sketchiness of using kingroot.
If anyone has the time to test this out let me know the results please.
Click to expand...
Click to collapse
I have try wit kingroot from pc with USB, but not with apk
Kingroot apk doesn't work
Hi ieatgravity ? about yours drax rom, does it work on wiko U Feel Prime? Maybe it's a dummy question but I have my doubts so it's better to ask you (OP) I think ? thanks in advance
Hi guys. I tried another thing in my Ufeel. One week now I have it with Red Wolf custom recovery and Viper_garlic rom 7.1.2 both for Yureka Black running. Everything works fine only with the recovery not. It's working but not 100%? I'm not a developer and I don't have the knowledge and tools for see what can do to better working. I thing sharing this with you guys it's important. And maybe someone with the knowledge (and time) want to see it. I try to get logs from the problems.
ps. Sorry for the bad English ?
New OTA update in France this morning. Version V39, always android 7.1.1. No bugs anymore with delay for unlock phone at reboot. Now fastboot devices is detected but always impossible to unlock. All commands says "unknown command"
Hi guys ? I found one thread for another wiko and it have the same problem but they found a way. I think maybe works for we to but I have no time ( work and new family member ?) maybe someone want to try
https://forum.xda-developers.com/android/help/root-how-to-root-wiko-view-t3740005
Ps- I tried the "Tinno" code in another wiko in nougat and it worked. Hope this is useful
Hello everybody, I just got the BLOX2 Mini and wanted to start working with it. I can see this thread hasn't been updated and that the blox2.com web is down. Can anyone direct me to the best resource available in order to unlock, install TWRP, root, etc. in the Mini, either in XDA or elsewhere? I noticed there's a long thread on the regular sized BLOX2 but I am not completely sure if what is available there will work in the mini.
Thanks!
Lineage 16 for Blu Life One X2 Mini?
Hi ieatgravity,
Are you still out there?
I'm wondering if Lineage 15 or 16 is also available for the Blu Life One X2 Mini?
Best daraabi
X2 is dead.
Guide to restore to stock and add TWRP/root is here: https://forum.xda-developers.com/showpost.php?p=77932487&postcount=6
I realize that there may already be a thread about this and if there is (and it's not one I started) then please link it here so I can go read it. I've read just about every thread on this topic and I still can't find the answer I'm looking for:
In essence this phone is perfect in every way that matters to me...except for the fact that I can't enable Wifi-Calling. I have tried using the "Wifi-Calling" app in the Google Play Store, I have also tried modifying the setting (wfc_ims_mode=2) in adb, but still nothing. I guess part of my issue is that I can't understand how, if this ROM (Funtouch OS 4.0) is based on Android 8.1 and Android 8.1 supports WiFi-Calling...why this ROM does not?
Anyone with any ideas I welcome your feedback. Also, there are a series of ADB global settings that I can seem to find out what they do. Anyone have any ideas? Could any of these be the key to getting this thing working on this phone?
vivo_wifi_2_mobile_enabled=0
volte_vt_enabled1=0
volte_vt_enabled2147483644=0
volte_vt_enabled=1
wfc_ims_enabled1=0
wfc_ims_enabled=1
wfc_ims_mode=2
wfc_ims_roaming_enabled1=0
wfc_ims_roaming_mode=2
Thanks
M.