Related
I don't want to repeat a post. But I am not getting enough traffic in the DESIRE subforum to get this answered.
HERE IS MY THREAD THERE:
[Q] How to get Froyo 2.2 OTA in USA for Unlocked UK Desire (w/ T-Mobile USA service) http://forum.xda-developers.com/forumdisplay.php?f=595#
But I want to expand my search here: WHAT IS UP with HTC? HTC SUPPORT WEBSITE IN UK: Search results for: HTC Desire > Android 2.2
{
"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"
}
How can they be so clueless throughout their entire international corporation regarding simple information -- where do I get my update for my HTC DESIRE unlocked UK-purchased phone?
• I have the HTC Desire, UK version, unlocked.
• But I am in the USA with T-Mobile USA carrier service; I bought the phone to use here because T-Mobile USA carries phones i don't care about, and never carries the ones I DO want, so I forego with 3g-- and just get the phones I want since I use wifi 80% of time anyway.
• The Android 2.2 has been available for the HTC Desire in the UK
• HTC Customer Support cannot tel me how I can get it. They first tell me -- seriously -- "Sorry, the OTA is pushed out from UK cell towers and you can't reach that signal in USA, so you are out of luck. All you can do is go to developer.Android.com and download the 2.2 update"
• "You mean to tell me this has been available to me all this time?"
• "yep, for over 2 weeks now."
• "What do I do?"
• "You go there and find the generic 2.2 version, since your phone is not tied to a carrier, it does not have al the carrier-specific update software with it"
• "But I thought these updates are PHONE-specific. I thought that was the whole big thing HTC has been saying. That first they have to wait for Gooogle to release the Android Code, then they have to test the code on various devices, and it takes certain tweeks per phone...?"
• "Nope... Didn't require much testing at all"
• "Well.... Okay then.... So I just go to deveoper.android.com ands I will find the file to download?"
• "Yep. SHould be there. It's been there for 2 weeks."
• Is it like an apk file?
• "No, you need to use HTC Sync..."
ANYWAY, I could go on -- and I do -- in the other thread. Suffice to say: He didn';t know his *** from hole in ground... And after 40 minutes on phone, and two times being put on hold, he comes back this time to say, sorry, i was mistaken, you WILL get your update OTA, but you missed your cluster and will have to wait til it comes around again.
I said "How is that possible? My phone is set for auto-update -- AND i check it manually and have been checking for past two weeks and every time it tells me it is UP TO DATE, no new software... yet it it version 2.1 ....
And more endless crap-talk.
Does anyone know: How can I get my update?
And #2: WHY IS THIS SUCH A MYSTERY?
And #3: MUST IT BE SO RIDICULOUS?
Thanks very much!
Ota does not check for country specificity when the phone is unbranded
Sent from my GT-I5700 using XDA App
tejajuloori said:
Ota does not check for country specificity when the phone is unbranded
Sent from my GT-I5700 using XDA App
Click to expand...
Click to collapse
Okay, that answers part 1 of about 5 parts to the question.
So, if I am in USA, have unbranded HTC Desire GSM model purchased from UK. T-Mobile USA is my carrier.. Who/ what server is pushing my update? IS it on HTC servers? Do they control it? How is it routed? Why have I not seen it? Why have I not gotten it?
How DO it get it?
thank you.
Ok this is what I know,correct me if I am wrong,
-updates are hosted on htc servers.
-it works like this-ota are rolled out to a group based on their IMEI nos,in some order may be the order of production.(not sure)
-when u click 'check for software update' it communicates directly to the software server wherever it is unless restricted by country policy(which I don't think is your case)
-when unlocked and unbranded the phone should get the updates ,if it is available on the server..
- so either your phone will get the update soon,or as someone said update was temporarly removed for bug fixes
Edit: jus read you got the phone on release date,are u on official firmware?
Sent from my GT-I5700 using XDA App
tejajuloori said:
Ok this is what I know,correct me if I am wrong,
-updates are hosted on htc servers.
-it works like this-ota are rolled out to a group based on their IMEI nos,in some order may be the order of production.(not sure)
-when u click 'check for software update' it communicates directly to the software server wherever it is unless restricted by country policy(which I don't think is your case)
-when unlocked and unbranded the phone should get the updates ,if it is available on the server..
- so either your phone will get the update soon,or as someone said update was temporarly removed for bug fixes
Edit: jus read you got the phone on release date,are u on official firmware?
Sent from my GT-I5700 using XDA App
Click to expand...
Click to collapse
Makes sense.
Also confirms just how CLUELESS and idiotic HTC Support is in various nations across the world. The HTC NORTH AMERICA support tech said "HTC DOES NOT HOST UPDATES ON ITS SERVERS"
But as for IMEI #s, the Clown did ask for mine, and after wasting half hour of my time, finally came back in the end and said "Your cluster was already served... You will need to waut several weeks til your cluster comes around again"
Okay, I have one of the very first unlocked HTC Desires SHIPPED anywhere in the world. It was bought from a large UK vendor and shipped to me in same batch as most people on XDA who had pre-ordered as early as Feb, March 2010.
Here is the odd thing: About 2 weeks ago, I was at home where I have wifi all the time and my phone is always on wifi.... I woke up my phone from sleep and I recall for a flash of a second there being a notification message that filled the whole screen as an overlay. It went away in half-a-second -- but I could have sworn it was saying Froyo update, and listed a list of feature changes etc... But I can't be certain because it just went away, i didn't touch the screen.
But immediately, after it went away, because I *thought* i was seeing what might be *the update* I'd been waiting for, I went to menu > settings > etc to go to see what version of software was on my phone -- wondering -- could it have already updated?? -- But no, my firmware version showed 2.1-update1 ... Just to make sure, I checked to see on my camera, did I have 720p? or, did I have apps2sd? NO, neither. So, then I ran a manual CHECK FOR UPDATE:
It said: There are no updates available. Your software is up to date.
-------------------------
Let's just say, for the sake of example, that this WAS the Froyo update that was momentarily in queue for OTA update on my phone. I know you're not an expert on this, but why do you think it would not show up as "UPDATE AVAILABLE" ? There is no way it was in queue for days -- and I missed my window... because i was reading the tech sites daily... and that day matched the day it was being first made avaialble.
So, for whatever reason, let's say it was somehow properly queued for OTA via wifi, recognizing my IMEI as early in the sequence. Why oh why would it not show up as a manual UPDATE AVAILABLE?
-----
Okay, then never mind that.
Let's say that was my CLUSTER of IMEI #s, and that was window of opportunity for OTA... WHAT NOW?
Since the HTC SUPPORT CLOWN first said it was coming via cell from europe and couldn't reach me, and the clown was wrong, and then the clown said I could get it as a download from Android.com, and the clown was wrong, and then the clown said I could downlaod it from a third party site, but he wasn't allowed to tell me which -- and btw, he couldn't find any .... and then the CLown said OH BUT WAIT, you WILL get it OTA, just wait a few weeks....
W. T. F. ?
IS there a rationale you can think of that would place open source OS software behind such ridiculous firewalls that even of you wanted to BUY it, you could not go out and BUY it, it's so cumbersome and stupid the way it is distributed. Is there a rationale that explains this stupidity?
IS IT HTC? Or does this stupidity get shared by others, such as the carriers?
--------
And finally, IF IT'S PURELY HTC STUPIDITY, then i have to ask again,
W. T. F. ? What has happened to their company? Are they falling apart at the seams? Can they not do anything right anymore? They completely botched the delivery of the DESIRE phones themselves. Is this what we can now all expect from the YOU company? F. YOU ?
tejajuloori said:
Edit: jus read you got the phone on release date,are u on official firmware?
Click to expand...
Click to collapse
Yes. Official. 2.1-update 1.
The phone has never been rooted. It is STOCK HTC.
Let the experts guide you but my suggestion is u can try -
- a restart of phone and then check for update,
-try a manual install of froyo(saw a post someone requesting steps for manual update)
- a factory reset and retry update(sometimes it helps,dont know the significance,make sure to backup all vital data first)
The htc have a better customer support than many mobile companies ,but the customer care reps whom we speak to have limited knowledge and can be stupid at times..try this mail them about your problem..I get quick email responses from htc..
And chill out bro u ll find a fix soon
Sent from my GT-I5700 using XDA App
So I'm sure we've all heard about the ExynosAbuse exploit. If not, the original thread is here. The only proper solution is a kernel fix. This thread is only about app-based fixes.
There are various fixes available at the time of this writing, including my own. I don't mind some competition, that is not the problem. What is a problem is that some of these other app-based solutions out there have been mentioned and pushed a lot in the media (tech as well as non-tech) while they are seriously flawed (the only true solution is a kernel fix that simply removes the exploitable memory device, but that requires a non-universal device update, so we focus only on app-based fixes here that users may run immediately).
What I mean by flawed is that while they offer protection most of the time, they may leave a big gaping hole during boot that can be exploitable (as I will demonstrate) - and serious malware authors will of course include this attack vector in any serious malware - as will they include an attack vector to exploit temporary enabling of the exploit so you can use your camera (on devices where the fix breaks camera use).
Serious malware needs only a tiny hole to squeeze through once, and will attempt to leave it's own backdoor in case the hole they squeezed through is closed. Disabling the fix to use your camera only for a second with a malicious app running in the background running the exploit in a loop, and game over. I'm not even going to demo that, that flaw should be clear.
Due to unreliable fixes being mentioned by the media, a lot of people who have read online (or even print) news about this exploit may be using a fix they believe will work, but actual malware will easily bypass. Maybe some noise needs to be made about this ?
We're going to talk about three solutions here:
RyanZA's ExynosMemFix
Supercurio's Voodoo Anti ExynosMemAbuse v0.6
Chainfire's ExynosAbuse APK
The demo
What I am going to demo is running the exploit at boot, even though a fix that runs at boot is installed, on an exploitable device. After reading the rest of this article, find attached the ExynosExploitDemo APK. After installation, open the app, reboot your device, unlock your device (enter PIN, pattern, etc) and watch the screen like a hawk. Within a minute, a toast (bottom of the screen) notification will popup telling you whether the exploit worked. If it didn't work the first time, please try it at least 3 times. Once you are satisfied with the results, you should uninstall it again as it slows down the boot process.
Test setup
For each test I have completely factory reset the devices, and installed the "protection" APK before installing the exploit demo. Tests have been run on both Galaxy S3 as well as Galaxy Note 2, with and without SIMs installed. Tests were performed on December 18, 2012 with the most recent versions at that time.
BOOT_COMPLETED
Both RyanZA's as well as Supercurio's solution depend on Android launching the apps at boot (using the BOOT_COMPLETED mechanism), so they can plug the hole. This is a standard Android practise, The problem is, there is no guaranteed order in which apps are started at startup. A malicious app could also register to be started at boot (as the demo app does), and it would be a race whether the malicious exploit is run first, or the protection code. Luckily, you are more likely to have installed one of the patches before the malware, and the app that is installed first also has a better change of being run first - but is something that you cannot and should not rely on, nor does it guarantee the protection app will win the race, as explained below. The number of apps installed (and their package names, and what exactly they do at launch) may further influence which package "wins". What I'm trying to demonstrate here is that depending on this method of patching is unreliable at best.
The demo vs RyanZA's ExynosMemFix
RyanZA's is probably the least advertised/mentioned solution, which I expect is least used as well. The solution relies on BOOT_COMPLETED and "su" availability (like being rooted with SuperSU or Superuser), but does not rely on the exploit itself.
The reliance on "su" availability makes it vulnerable, it runs "su" to get the required access level to plug the hole. Even if installed before the malware and the system launches its startup code before the malware, the "su" call is an expensive one that can take an arbitrary amount of time to complete, regardless of the app having been granted permission before or not.
In my tests, even with ExynosMemFix installed before the demo, and having verified it's code launched first, it would always lose against the demo (and thus the exploit succeeds) if the root management app installed is Superuser. Due to the way the Superuser app is designed, it takes a longer time acknowledging the "su" request, giving the demo time to run the exploit. I have also seen ExynosMemFix generate an ANR error during testing a number of times, indicating that it may be calling "su" from the actual broadcast receiver (instead of a background thread), with all the problems that may cause.
When SuperSU is used, ExynosMemFix would always win against the demo in my tests (and thus the exploit fails), due to SuperSU responding much faster as it does not rely on the Android framework as Superuser does.
This solution can be somewhat secure, but even if used in combination with SuperSU, it cannot be guaranteed the malware does not launch first (I've seen it happen, but have not found the key to reproducing it yet). In combination with Superuser instead of SuperSU, the patch leaves a major hole.
The demo vs Supercurio's Voodoo Anti ExynosMemAbuse v0.6
Supercurio's is probably the most advertised/mentioned solution in general by media outlets. The solution relies on BOOT_COMPLETED and the exploit itself (but no "su" required).
The reliance on the exploit makes it vulnerable. The exploit may need to run a couple of times before it succeeds during boot, and it takes quite a few milliseconds to run. It runs the exploit to get the required access level to plug the hole. The exploit does however take some time to run, and both exploit as well as the hole-plugging-command must be completed before the malware starts, to effective block it.
In my tests, even with Voodoo Anti ExynosMemAbuse installed before the demo, and having verified it's code launched first, it would always lose against the demo (and thus the exploit succeeds). The protection code would launch before the demo code, but it would not complete (and fix the hole) before the malware was started, thus failing to block it.
Note that this specific case is probably especially sensitive to the number of apps you have installed - it may be the case that the more apps you have installed after this solution and before actual malware, the better the chance the protection will succeed before the malware is triggered. You can't possibly rely on this, though.
This solution is the least secure solution of all available options - it will leave a big hole open, you might as well not run any patch at all.
The demo vs Chainfire's ExynosAbuse APK
Mine is probably the second most advertised/mentioned solution. The solution relies on modifying /system and the exploit itself, with parts relying on "su".
This solution can root the device and install SuperSU as management app itself, though it also works with a pre-installed Superuser. It requires this to install the on-boot fix. After that patch is applied, you can unroot again (inside SuperSU: Settings --> Full unroot) - the patch will keep working. The patch itself does however modify /system, to make sure the fix is applied before any normal Android app is started with BOOT_COMPLETED, completely preventing the hole the demo app (and malware) would use to run the exploit. As such, the exploit always fails.
This solution is the most secure solution of the available options in this regard, topped only by actually fixing the exploit in the kernel.
Virus/malware/etc scanners
I have also noticed that various virus and malware scanners have updated their definitions in the past few days, and they will now detect the original ExynosAbuse exploit. Be warned however, that this specific hole can be exploited in many different ways and the example code provided by alephzain is just that: an example. I am not at all convinced that all different exploits based on this hole can even theoretically be reliably detected by these scanners - including Google's - unless every app is actually tested against in a sandbox environment (and even then ...). They may protect against those using the exploit as-is, though.
The big joke
The funny thing is, all the fixes that can actually work void warranty: mine requires modifying /system, RyanZA's requires root as well, and a proper fix requires a custom kernel.
In other words, right now you can't really protect yourself against this abuse without voiding your warranty. If there ever was a case for having laws against limitations of warranty, this is it. On a related note, any warranty denied because your system status is "modified" is also completely bogus, as a successful exploit might (outside of your knowledge) probably try to install their own backdoor in /system ... which might trigger "modified" status.
Also, if you're thinking this is complicated code, malware authors are not smart enough, etc - think again. Serious malware authors live and breathe this stuff, and the relevant code for this attack is rather trivial and only about 30 lines, including whitespace and actually showing you the exploit result.
Another joke is that I seriously doubt any major news outlet will post a correction, but hey at least I tried
Different test results
Let us please not make this thread about your test results being different. If you have read and understood all the text above, you would know that there are various factors that may throw the test outcome one way or the other. Unless your sure your different result is significant in being different, please do not clutter the thread with it.
Download
If you have a decent and updated virus scanner, it will likely scream at you for trying to download this. It is after all an exploit. You may need to turn it off if you want to test this for yourself.
2012.12.19 Update
I have a new (private, yeah) version of the demo that now beats both Supercurio's (v0.9) as well RyanZA's solution 100% of the time
--- also reserved ---
Thanks for this thread. It's so fun !
But, I have solve the problem (I think) after flashing my phone with my kernel (exynos_mem files modified).
lelinuxien52 said:
Thanks for this thread. It's so fun !
But, I have solve the problem (I think) after flashing my phone with my kernel (exynos_mem files modified).
Click to expand...
Click to collapse
Yes, as stated, the best solution is a fixed kernel
My app clearly states the limitations of the approach (inside the app itself, leaves no doubt)
But it should not loose every time against the demo exploit at boot, so I'll change for a more aggressive way to start.
Thanks Chainfire for taking the time to test.
Chains, it's not much but have an Export 33 on me mate: 8BH470706S240353D :good:
Well said.
Chainfire said:
Yes, as stated, the best solution is a fixed kernel
Click to expand...
Click to collapse
So when do you think Samsung+carriers will plausibly get around to officially fixing it?
Sounds more precarious to not try your workaround & there is reasonable deniability even if there is a warranty issue..?
Tomorrow I'd like to install the official T-Mobile SGH-T889 multi-window update followed by ExynosAbuse-v1.30.apk , anyone expect issues as this recently discovered exynos exploit is not listed as addressed in this likely tested for weeks update?:
{
"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"
}
So is ExynosAbuse-v1.30.apk now regarded as the best-easiest-fastest-safest reversible root method for stock ROM compatible devices (as it also offers a reversible exynos exploit work-around with full unroot)?
-Thanks
Tried demo app this way:
- 2 times under WiFi and I get "Exploit FAIL" and the toast shows the directory that is something like "[!] ... /exynos-...."
- 1 time under 3G regular data connection and I still get "Exploit FAIL" but in the toast I don't see any more the directory but only the message
I use Chainfire's exploit app.
Am I secure???
Sent from my GT-i9300 using TapaTalk2
Chainfire, guys, please give a try to the v0.7 version of my app, same place.
Chainfire, it would have been nice to be informed while you were preparing the article (on your early conclusions)
Just wondering, when Samsung DOES release a fix, I think it'd kinda be a catch 22 because those rooted or modified won't be able to update - or those infected won't be able to update. So Samsung will have to be lax with that rule. Or is that even possible? But regardless, I'm sure you guys will be able to get us the Samsung fix when and if they come out for us modified folks.
ThaiM said:
Just wondering, when Samsung DOES release a fix, I think it'd kinda be a catch 22 because those rooted or modified won't be able to update - or those infected won't be able to update. So Samsung will have to be lax with that rule. Or is that even possible? But regardless, I'm sure you guys will be able to get us the Samsung fix when and if they come out for us modified folks.
Click to expand...
Click to collapse
Yes, that's good thinking.
And also why I tried to provide something (even an imperfect workaround) that doesn't alter system.
I have 2 questions tho and I'll verify to get an answer to the first one.
- Is my app really not triggering the "modified" status
- If Chainfire un-do all the modifications applied by his tools, will the device return to its "un-modified" status
Or maybe the "un-modified" status can be faked, restoring the proper function of OTA updates.
maybe note worthy thing to here, in EU you dont lose your warrantly for applying fixes like this in fact you can install kernels/roms as many times as you want and you still got your warrantly. what comes to my own experience from this, my phone have been repaired 2 times because micro-usb didnt want to co-operate with me first time i had miui installed, second time had cm10 when i sent my phone to get fixed, both times got it fixed free of charge.
source: https://fsfe.org/freesoftware/legal/flashingdevices.en.html
tl;dr
if flashing original firmware dont fix issues you had on your phone, then you must have the damage covered free of charge(ie. micro-usb port goes crazy)
Chainfire, thanks for your elaborate demo.
I tested the exploit demo thrice with mobile security apps disabled; once with your app, and twice with the two "disable exploit" boxes from your app unticked. The first time, the exploit failed.
The kernel I have installed (link in my sig) seems to have fixed the problem. It uses the fix by AndreiLux that was successfully implemented by Entropy512 from the original thread.
Both times I rebooted, the exploit failed (see screenshot). I guess this is expected, but both times after boot, the checkbox "disable exploit" was enabled again without touching it.
Seems like a success story to me.
Thanks again!
SGS2 // RootBox 3.2 // Dorimanx 7.33
The 0.9 update of my app is strong now on boot (or less weak), but this is not very satisfying.
Frustrating as there's no "perfect" fix for regular users I'm thinking about right now.
I'm not really a fan of waiting, are you ?
@supercurio I was wondering the exact same thing on how may the "un-modified" status can be faked. Then again, as another user pointed out, though warranty rules and regulations maybe the same across all regions - it is their comprehension and application which is ambiguous.
I for one can attest that at my place they will simply replace the internals of your phone as long as the purchase bill you produce confirms that your device is still covered by the manufacturer warranty.
Props on the great research Chainfire, I agree with it all 100%
Personally though, malware authors target the easy and low hanging fruit - in this case, 99% of phone users who have not used any kind of fix. (99% is a very low estimate). They have no real reason to try and 'out race' mine or supercurios fix in practice, as (mine in particular) has very few users. Why bother creating a special exploit that only runs on boot, when you can just target 99%+ of all unfixed devices by just running the exploit when the app is started?
I've seen 4 malicious uses of the exploit in the wild so far, and all of them run on app start, which is blocked by all 3 'unsecure'/non-kernel fixes. Users are still VERY heavily encouraged to use any of the fixes as they currently stop all uses of the exploit in the wild. Supercurios is still the best one as it does not require root, and should definitely be advertised by the media as much as possible as it stops a real world and current threat to user security as best as it can.
Gotta say great research chainfire need of the hour indeed :thumbup:
Chainfire said:
The big joke
The funny thing is, all the fixes that can actually work void warranty: mine requires modifying /system, RyanZA's requires root as well, and a proper fix requires a custom kernel.
Click to expand...
Click to collapse
so if i understood correctly. custom kernel solves issue. :good:
i don't care about warranty
The first custom ROM for the Epic is now live! See this thread for details.
So a friend of mine got his hands on one of these, and since he asked me about flashing Gapps into the device, I was wondering if any one of you guys have been doing something just as "epic" for this children's tablet. And yes, I started this thread as a sort-of sequel/follow-up to the VTech Innotab Max thread I posted a year ago.
{
"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"
}
TECH SPECS:
Display: 7-inch capacitive touchscreen with TN LCD display
Resolution: 1024x600
Operating System: Based on Android 4.4 (modified, of course)
Processor: Quad-core, 1.3 GHz (reported by CPU-Z as MediaTek MT8127)
Memory: 1GB RAM
Storage: 16GB; 9GB available for /sdcard partition
Micro SD Card Slot: Yes, expandable up to 32GB
Camera - Rear: 2MP
Camera - Front: 2MP
Audio: 3.5mm stereo jack with microphone
Wireless: Wi-Fi 802.11 b/g/n
Bluetooth: Bluetooth 4.0
Battery Type: Rechargeable lithium-ion
Battery Life: 6+ hours; results will vary based on usage and settings
Port: Micro USB
Sensor(s): Accelerometer
Much to my disappointment, LeapFrog didn't equip the tablet with a GPS module, and despite the potential privacy issues that may arise with including one, it could be legitimately used for certain applications like tracking the device or your son or daughter in case he/she gets lost. The usual backdoor leading to Developer Options is also disabled for some reason, though it can still be accessed through third-party utilities such as this. And maybe it's just my modded Epic, but beaming stuff from another device to an Epic using ShareIT appears to suffer from connection issues, i.e. the device is detected but the sender is unable to connect to it; a workaround for this would be sending a file or two from the Epic and then having the sender do the same from his/her device.
APKs from outside sources can be installed either through ADB or by downloading it on your device and installing as usual, not to mention that there's a semi-hidden feature (tucked away under the Parental Controls panel) that allows for the Amazon AppStore to be loaded. As for rooting, Kingoroot should do the trick from what I've read here, but you can manually install SuperSU on it if you prefer the more established root access app. ADB-wise, the latest debug and fastboot binaries should work on the device from what I can attest.
Oh, and here's a link to the Antutu test results:
http://our.antutu.net/api/?action=v5&act=benchmark&id=54239552
CPU-Z report:
Kernel sources:
Code:
https://www.dropbox.com/s/vo6u4s6b3shjrhb/epic.iso?dl=0
https://github.com/huckleberrypie/android_kernel_quanta_narnia
Mad props to RAMChYLD for volunteering to have the sources mailed to him, as I'm reluctant to have them mail the goods to me no thanks to the rather abysmal postal service here in my place.
Pre-rooted ROM dump courtesy of @epic__fail; This can only be flashed with an unlocked bootloader.
Code:
http://www.needrom.com/download/leapfrog-epic-v1-stock-rom/
Note that while the unsigned ROMs cannot be flashed directly using SP Flash Tool, you can get around this by using the hidden Write Memory option. A quick guide on how to do that can be found on page 12.
Signed ROM dumps. Can be flashed directly using SP Flash Tool v5.1744. Make sure to perform a full backup of the tablet before flashing!
Code:
Epic Academy Edition:
v1.1.95: https://androidfilehost.com/?fid=6006931924117902657
v1.8.160: https://androidfilehost.com/?fid=6006931924117908682
v1.8.804: https://androidfilehost.com/?fid=4349826312261819358
LeapPad Academy:
v1.1.171: https://androidfilehost.com/?fid=4349826312261738402
P.S.: If you're getting a signature error upon flashing, try unticking SEC_RO and then try again.
Official flashable ZIP files:
Code:
Regular:
http://lfcdownload.leapfrog.com/epic/en/KOT49H.user.1.0.124.20150709.140831-to-KOT49H.user.1.5.45.20160310.231145.zip
http://lfcdownload.leapfrog.com/epic/en/KOT49H.user.1.1.146.20150825.120621-to-KOT49H.user.1.5.45.20160310.231145.zip
http://lfcdownload.leapfrog.com/epic/en/KOT49H.user.1.2.90.20150924.150837-to-KOT49H.user.1.5.45.20160310.231145.zip
http://lfcdownload.leapfrog.com/epic/en/KOT49H.user.1.3.27.20151026.144847-to-KOT49H.user.1.5.45.20160310.231145.zip
Academy Edition:
Latest Version: "KOT49H.user.1.1.95.20171215.140555"
KOT49H.user.1.1.52.20170522.123745
URL: http://lfcdownload.leapfrog.com/epic/en/v2/KOT49H.user.1.1.52.20170522.123745_to_KOT49H.user.1.1.95.20171215.140555.zip
Patch notes: This is an incremental update from KOT49H.user.1.1.52.20170522.123745 to KOT49H.user.1.1.95.20171215.140555
KOT49H.user.1.1.62.20170627.010228
URL: http://lfcdownload.leapfrog.com/epic/en/v2/KOT49H.user.1.1.62.20170627.010228_to_KOT49H.user.1.1.95.20171215.140555.zip
Patch notes: This is an incremental update from KOT49H.user.1.1.62.20170627.010228 to KOT49H.user.1.1.95.20171215.140555
KOT49H.user.1.1.64.20170704.010259
URL: http://lfcdownload.leapfrog.com/epic/en/v2/KOT49H.user.1.1.64.20170704.010259_to_KOT49H.user.1.1.95.20171215.140555.zip
Patch notes: This is an incremental update from KOT49H.user.1.1.64.20170704.010259 to KOT49H.user.1.1.95.20171215.140555
KOT49H.user.1.1.66.20170712.151925
URL: http://lfcdownload.leapfrog.com/epic/en/v2/KOT49H.user.1.1.66.20170712.151925_to_KOT49H.user.1.1.95.20171215.140555.zip
Patch notes: This is an incremental update from KOT49H.user.1.1.66.20170712.151925 to KOT49H.user.1.1.95.20171215.140555
JSON files for the updater:
Regular:
http://lfcdownload.leapfrog.com/epic/en/NarniaSystemUpdateVersions1.json
Academy:
http://lfcdownload.leapfrog.com/epic/en/NarniaSystemUpdateVersions_epic2.json
LeapPad Academy:
http://lfcdownload.leapfrog.com/epic/en/NarniaSystemUpdateVersions_epic3.json
The above ZIPs are incremental patches used to update an existing system to a newer build; I couldn't seem to dig up a full system image, let alone a scatter file, for a bricked or bootlooping Epic to be restored back to factory condition though, but still I'm keeping this as a reference in case any one of you guys is interested in downloading them manually. Apparently "KOT49H.user.1.1.99.20150807.173011" is unique to demo units, hence why there weren't any updates available for my device when I ran the OTA utility.
Demo-to-retail conversion tutorial
A tutorial on how to convert a store demo unit into a fully-functional Epic can be found here:
https://huckleberrypie57.blogspot.com/2018/12/and-i-came-in-for-another-leapfrog-epic.html
Custom ROMs
Unofficial LineageOS 14.1 by mac2612, blakegriplingph and kai2000: https://forum.xda-developers.com/android/development/rom-lineageos-14-1-leapfrog-epic-t4161311
The modifications to the way locale is set means that Bluetooth HID like keyboards can pair but cannot work since it cannot be set to be used for input (the options to change or add keyboard layouts is disabled in the Android settings screen and instead is selected from LeapFrog's own screen which divides the world into 7 regions- US, UK, Canada, Australia, New Zealand, Ireland and Other. When you pick Other it forces the UK keyboard and locale on you, which is ridiculous since some countries uses varying combinations of either (for example, Philippines uses US English 100%, while Malaysia uses UK English but US Keyboard). However bluetooth does work with A2DP devices.
Yeah, the CPU-Z and AnTuTu benchmark are my doing. I am the friend Blake mentioned. I should add that the device ran the Project Anarchy demo in AnTuTu somewhat well, averaging at 15fps.
MTK's spec sheet mentions that the SoC also has GPS and FM Radio, but I suspect that both are disconnected on the device since Android doesn't detect them.
The option to enable installation of packages from untrusted sources is still in the android security screen in settings tho, and you will be instructed to turn it on as part of the steps to install the Amazon AppStore.
I actually emailed LeapFrog as to whether they can release a tarball to the MTK kernel sources they used, and I'm keeping my fingers crossed but since they had a history of doing so in compliance with the GPL (c.f. the links to Didj/Leapster sources on eLinux provided by none other than LF themselves), I have high hopes for custom ROM development or at least some mods for the device.
Well, my only problem with the device is that the input method and locale selection is locked down and selected by the "Device Locale" screen, instead of allowing the much more granular selection allowed from the Android settings screen itself. I have determined that the same lockdown prevents bluetooth keyboards from pairing properly with the device. Also, several apps defaulted to downloading videos from UK servers instead (ie BabyFirst TV, Fisher-Price Puppy Player and Little People Player) and thus have what I perceive as "wrong voices".
I'm still waiting for LeapFrog's reply concerning the kernel sources, and if all goes well we'll be golden.
Good luck.
Well, drat. Leapfrog's asking me for a mailing address so they can send me the source CDs. Problem is I am wary of the postal servce here at my place, so is there anyone who's willing to get the sources?
So I bought one of these leap pad epics. Got it at toys r us. It was a return so open box. They gave it to me for $70 (they retail for $169.99+tax) because the last person who owned it left their passcode on it. I can't figure out how to get it off. Any ideas??
Hang in there. I've contacted Leapfrog via Facebook and am awaiting a reply.
RAMChYLD said:
Hang in there. I've contacted Leapfrog via Facebook and am awaiting a reply.
Click to expand...
Click to collapse
Wouldn't doing the standard factory reset procedure be enough for that (as with those who ended up flinging way too many patterns on their device), or is there anything special that's needed to be done?
Okay, got a reply. Go into the parent screen to bring up the pin entry, then enter 4 1 9. Now, when your cursor is in the last textbox, hit the backspace and enter 2 7. Apparently this is a hidden backdoor that Leapfrog puts into the system for cases like these (ie improper returns).
I've tested it, entering 4 1 2 7 upfront doesn't work. It has to be 4 1 9 <backspace> 2 7.
As for doing a factory reset, well, It's a catch 22 situation- to get into the settings screen, you need to enter the password first - they actually modified the settings app. If you don't have the password, well, you're SOL unless you call Leapfrog support, who will probably give you this code anyway. If the ADB interface is up, you could probably do it from there, but I'm not sure if it is.
Hmm, now I'm wondering if there's someone who's up to doing an SP Flash Tool dump of the device.
Good news: RAMChYLD just got his hands on the source tarball, and as such he gave me a link to the ISO containing the kernel sources, ripped off the disc LeapFrog mailed to him recently:
Said link to the sources can be found on the first post, in case you guys are interested.
Actually, Blake did the bulk of the work, talking to Leapfrog and arranging the CD to be sent to me. But yeah.
RAMChYLD said:
Actually, Blake did the bulk of the work, talking to Leapfrog and arranging the CD to be sent to me. But yeah.
Click to expand...
Click to collapse
Yup, pretty much. Though to tell you one thing, I was a bit worried that the sources either wouldn't arrive in time or not at all.
RAMChYLD said:
As for doing a factory reset, well, It's a catch 22 situation- to get into the settings screen, you need to enter the password first - they actually modified the settings app. If you don't have the password, well, you're SOL unless you call Leapfrog support, who will probably give you this code anyway. If the ADB interface is up, you could probably do it from there, but I'm not sure if it is.
Click to expand...
Click to collapse
You can factory reset by holding down Power + Volume Up at boot.
Is any one of you guys here interested?
I will be. I'll be buying my son one this weekend.
alienundies said:
I will be. I'll be buying my son one this weekend.
Click to expand...
Click to collapse
If you could provide an SP Flash Tool dump of the stock ROM it'll be golden., along with a TWRP/Clockwork recovery image. I really wish that I could get my hands on one, but the local Toys R Us here sells it for like twice the price even though it's just some glorified MediaTek device made with children in mind.
XbooX08 said:
You can factory reset by holding down Power + Volume Up at boot.
Click to expand...
Click to collapse
Does that work? They even went as far as to disable the ability to screenshot with power + volume down until I installed an app to re-enable it.
blakegriplingph said:
If you could provide an SP Flash Tool dump of the stock ROM it'll be golden., along with a TWRP/Clockwork recovery image. I really wish that I could get my hands on one, but the local Toys R Us here sells it for like twice the price even though it's just some glorified MediaTek device made with children in mind.
Click to expand...
Click to collapse
+1. The Asian importers for the device are charging way more for it over here than the device sell for in the US. It's going for an insane RM1000 at Toys R Us and Hamleys here. Which imo is ridiculous given that there are vendors selling (malware-laden) Chinese tablets for less than a fifth of that.
I wish to know if there are any custom roms or os'es that wouldn't touch my data using background processes that doesn't ask for permission to do so. Because these apps are either pre-installed or installed by me (which ask for permissions up front)? Or at least that I would be able grant app permissions when it needs them? It's like a real time permission request service.
Thanks.
I don't understand your question very well but I think you'll need an AOSP 6.0 ROM like the one made by Flashhhh beacuse AOSP is the most secure beacuse just Google modifies it and the developer (Flashhhh in our case). You can't make it 100 % secure beacuse you need to encrypt the partition and lock the bootloader. Encryption slows the device like hell and locking the bootloader with costum software cannot by made except if some of the great develoeprs of the falcon can reprogram the bootloader and the other low level bootloaders. Hardware encryption isn't supported on falcon I don't know why beacuse my Lumia 435 has encryption enabled via settings as you can see here:
{
"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"
}
And yes the device is as fast as with the option disabled ! So hardware encryption is supported on Snapdragon 200 and our device has Snapdragon 400. I don't know why but that's the life...I am also interested in a secure OS with encryption that can run on our Moto G without performance loss.
I was really looking forward to cyanogen-mod, because it was looked as safe. But after I've read their DISCLAIMER stating "Modifying or replacing your device's software may void your device's warranty, lead to data loss, hair loss, financial loss, privacy loss, security breaches, or other damage, and therefore must be done entirely at your own risk. No one affiliated with the CyanogenMod project is responsible for your actions. Good luck." I changed my mind. I am paranoid about my privacy and security therefore this disclaimer put all my excitement and hopes to find privacy and security in their custom rom down. On the other had they're stating the things that could happen to my phone through the use of their custom rom, which I am thankful for their honesty and precautions. I was looking for official carbon rom, because of it's flexibility in customization and some other useful features, but sadly they don't support our device so yet again I was let down. Even if there is ports of it. Yet again my paranoia for privacy and security appears to be in action and I just can't help it when It come to it. It's my need and I believe it is everyone's need that sadly seems to be not met... even my keyboard sends data through background services... The more I see what android does the more I want to switch back to windows phone... it was easy to use, simple, and at least secure. I loved the thing that you could use one app for text messaging and social network messaging and I found it really handy feature. Android is highly customizable, but not as secure as WP. Also did everyone else noticed that Android version names are alphabetically ordered which could mean that they have plans up front for Z? Ohhh and google is in alphabet now...
Was WP really more secure or did you simply don't know what it did in the background?
Concerning your question: to find a "perfect" system might by impossible. However, you should not completely give up on Cyanogenmod (or on custom roms in general). You do get the possibility to manage permissions and you get root. The latter you can use to uninstall system-apps you dont like or to set up a firewall for apps and services you dont trust (for instance your keyboard). As a further step you could try if a Google-free device would work for you (i.e. not flash gapps after rom). That might be less convenient in some aspects but you would get rid of the no. 1 risk for privacy. And dont worry too much about the disclaimer! Sure, flashing a custom rom can turn your device into electronic scrap and things like root are risky anyway, the crucial point is that stuff needs to be handled the correct way. With enough information acquired in the first place the risks arent too big
Hwyl.Fawr said:
Was WP really more secure or did you simply don't know what it did in the background?
Concerning your question: to find a "perfect" system might by impossible. However, you should not completely give up on Cyanogenmod (or on custom roms in general). You do get the possibility to manage permissions and you get root. The latter you can use to uninstall system-apps you dont like or to set up a firewall for apps and services you dont trust (for instance your keyboard). As a further step you could try if a Google-free device would work for you (i.e. not flash gapps after rom). That might be less convenient in some aspects but you would get rid of the no. 1 risk for privacy. And dont worry too much about the disclaimer! Sure, flashing a custom rom can turn your device into electronic scrap and things like root are risky anyway, the crucial point is that stuff needs to be handled the correct way. With enough information acquired in the first place the risks arent too big
Click to expand...
Click to collapse
Well yes WP doesn't have such feature as seeing what backgroung processes are active, what they're doing which should be a concern, but I think there are some devices that doesn't support multi-tasking which probably deals with the issue. Well the cyanogen mod does offer that security and frees you from app permission chains, but I don't want to rush on flashing it.
What about ubuntu os? They provide tutorial to port it for your own device which I am really interested in. But is there any advantages over cyanogen mod in terms of user privacy and security? Should I consider porting it myself or flashing a port made by community?
This ROM was created with privacy in mind: (Read the first post carefully and follow the instructions)
http://forum.xda-developers.com/moto-g/4g-development/rom-identity-crisis-6-lte-extreme-t3328861
It will boot on Falcon; if after flashing the ROM, you immediately flash the Stock 6.0 Kernel available here:
http://forum.xda-developers.com/showthread.php?t=2649763
lost101 said:
This ROM was created with privacy in mind: (Read the first post carefully and follow the instructions)
http://forum.xda-developers.com/moto-g/4g-development/rom-identity-crisis-6-lte-extreme-t3328861
It will boot on Falcon; if after flashing the ROM, you immediately flash the Stock 6.0 Kernel available here:
http://forum.xda-developers.com/showthread.php?t=2649763
Click to expand...
Click to collapse
Is it only for LTE version?
Thank you for your time spent on developing this rom for the community. I will flash it straight away.
zgodig said:
Is it only for LTE version?
Thank you for your time spent on developing this rom for the community. I will flash it straight away.
Click to expand...
Click to collapse
As I said, the ROM will boot and work fine on your phone if you flash the Falcon kernel. @minimale_ldz created this ROM based on my previous work.
lost101 said:
As I said, the ROM will boot and work fine on your phone if you flash the Falcon kernel. @minimale_ldz created this ROM based on my previous work.
Click to expand...
Click to collapse
This is madness.
Also
lost101 said:
This ROM was created with privacy in mind: (Read the first post carefully and follow the instructions)
http://forum.xda-developers.com/moto-g/4g-development/rom-identity-crisis-6-lte-extreme-t3328861
It will boot on Falcon; if after flashing the ROM, you immediately flash the Stock 6.0 Kernel available here:
http://forum.xda-developers.com/showthread.php?t=2649763
Click to expand...
Click to collapse
Okay. The rom looks good and seems to offer what I need, but that bug when you dim your brightness and flickering occurs can be annoying, since I like to dim it as much as possible, to save my battery from draining. I guess I will have to keep on using the stock rom till port of your rom will be fixed.
zgodig said:
Okay. The rom looks good and seems to offer what I need, but that bug when you dim your brightness and flickering occurs can be annoying, since I like to dim it as much as possible, to save my battery from draining. I guess I will have to keep on using the stock rom till port of your rom will be fixed.
Click to expand...
Click to collapse
There's also Lollipop version of this rom available, and it doesn't flicker. Installing the rom itself, however, won't be enough - even removing GApps doesn't prevent Google and from collecting "anonymous" data as there are still some leaks through kernel and modem debug settings. They can be blocked by firewall (like AFWall+). You may also want to install Network Log to see all the traffic. XPosed Xprivacy module is also very helpful in restricting internet, network, location, sensors, etc. access to the apps. You can also disable location services and bluetooth (and other things) with Servicely for extra protection and battery life.
All of it will give you SOME protection as obviously your carrier will have a lot of data about your device and this can't be avoided as long as you use its phone services.
minimale_ldz said:
There's also Lollipop version of this rom available, and it doesn't flicker. Installing the rom itself, however, won't be enough - even removing GApps doesn't prevent Google and from collecting "anonymous" data as there are still some leaks through kernel and modem debug settings. They can be blocked by firewall (like AFWall+). You may also want to install Network Log to see all the traffic. XPosed Xprivacy module is also very helpful in restricting internet, network, location, sensors, etc. access to the apps. You can also disable location services and bluetooth (and other things) with Servicely for extra protection and battery life.
All of it will give you SOME protection as obviously your carrier will have a lot of data about your device and this can't be avoided as long as you use its phone services.
Click to expand...
Click to collapse
I think that I should wait for the marshmallow patch. Because I wouldn't have to use the apps you have mentioned in order to protect myself. I've read that you recommend these apps to use on marshmallow too. Which one would you recommend? Lollipop ir marshmallow? From the things you have mentioned it made me an impression that there has to be done more on lollipop to protect yourself as much as possible, than on marshmallow. Besides I suspect that marshmallow is more advanced than lollipop. Anyways an expert opinion is allways worth to concider. A big thank you xda developers for your hard work and time put in developing all of the software available for us. You're the best!
zgodig said:
I think that I should wait for the marshmallow patch. Because I wouldn't have to use the apps you have mentioned in order to protect myself. I've read that you recommend these apps to use on marshmallow too. Which one would you recommend? Lollipop ir marshmallow? From the things you have mentioned it made me an impression that there has to be done more on lollipop to protect yourself as much as possible, than on marshmallow. Besides I suspect that marshmallow is more advanced than lollipop. Anyways an expert opinion is allways worth to concider. A big thank you xda developers for your hard work and time put in developing all of the software available for us. You're the best!
Click to expand...
Click to collapse
Well, I don't consider myself an expert - just spent some time reading security and privacy related stuff in the web and used some of the information to help myself. Please also mind all the things I mentioned (firewall, XPrivacy, etc.) don't come with Marshmallow and need to be installed and set up anyway so it doesn't make much difference if you use Lollipop or MM version. The biggest privacy-related changes that come with MM are built-in permissions manager (which is good but insufficient) and more up to date security patch. And I think that is it, so it's up to you if you want to wait. The thing with Android updates is that they bring new stuff that OEM and carriers need to implement and optimize, so I wouldn't say that Marshmallow is better in every aspect than Lollipo. I was using 5.1.1 for a few months on Moto G and was very happy - I'm using 6.0.1 on Moto X Play now, and see some annoying bugs that came with it. Interesting thing is they only appeared after removing GApps from the rom. So again - it's up to you.
The other fact is that the more you protect yourself from intrusive Google services the more new privacy and security issues appear. For example - if you use stock rom there's no need to unlock bootloader nor using custom recovery which are actually negatively affecting your privacy. You can access all the system and data in TWRP, so your privacy is pretty much none in case someone steals your phone. Good practice is not to keep too much private stuff on it, because there's always a risk someone can get it - one way or another.
minimale_ldz said:
There's also Lollipop version of this rom available, and it doesn't flicker. Installing the rom itself, however, won't be enough - even removing GApps doesn't prevent Google and from collecting "anonymous" data as there are still some leaks through kernel and modem debug settings. They can be blocked by firewall (like AFWall+). You may also want to install Network Log to see all the traffic. XPosed Xprivacy module is also very helpful in restricting internet, network, location, sensors, etc. access to the apps. You can also disable location services and bluetooth (and other things) with Servicely for extra protection and battery life.
All of it will give you SOME protection as obviously your carrier will have a lot of data about your device and this can't be avoided as long as you use its phone services.
Click to expand...
Click to collapse
minimale_ldz said:
Well, I don't consider myself an expert - just spent some time reading security and privacy related stuff in the web and used some of the information to help myself. Please also mind all the things I mentioned (firewall, XPrivacy, etc.) don't come with Marshmallow and need to be installed and set up anyway so it doesn't make much difference if you use Lollipop or MM version. The biggest privacy-related changes that come with MM are built-in permissions manager (which is good but insufficient) and more up to date security patch. And I think that is it, so it's up to you if you want to wait. The thing with Android updates is that they bring new stuff that OEM and carriers need to implement and optimize, so I wouldn't say that Marshmallow is better in every aspect than Lollipo. I was using 5.1.1 for a few months on Moto G and was very happy - I'm using 6.0.1 on Moto X Play now, and see some annoying bugs that came with it. Interesting thing is they only appeared after removing GApps from the rom. So again - it's up to you.
The other fact is that the more you protect yourself from intrusive Google services the more new privacy and security issues appear. For example - if you use stock rom there's no need to unlock bootloader nor using custom recovery which are actually negatively affecting your privacy. You can access all the system and data in TWRP, so your privacy is pretty much none in case someone steals your phone. Good practice is not to keep too much private stuff on it, because there's always a risk someone can get it - one way or another.
Click to expand...
Click to collapse
If you're not an expert then you're not far from it, because I don't think it's easy to do the things you did.
Is it possible to re-flash stoch recovery and re-lock bootloader after flashing one your roms to improve security, or are they essential to make rom work?
zgodig said:
If you're not an expert then you're not far from it, because I don't think it's easy to do the things you did.
Is it possible to re-flash stoch recovery and re-lock bootloader after flashing one your roms to improve security, or are they essential to make rom work?
Click to expand...
Click to collapse
As far as I know relocking bootloader will fail if installed system is not original, but I'd ask @lost101 as he's got much more expertise in Motorola issues.
minimale_ldz said:
You can access all the system and data in TWRP, so your privacy is pretty much none in case someone steals your phone.
Click to expand...
Click to collapse
Using encryption helps in this case. Just remember that when you get your phone back, don't trust it anymore.
zgodig said:
Is it possible to re-flash stoch recovery and re-lock bootloader after flashing one your roms to improve security, or are they essential to make rom work?
Click to expand...
Click to collapse
Originally Falcon (and Peregrine I suspect) did not support Factory Reset Protection (FRP) - this may have changed for those with locked Bootloaders who updated to Lollipop via official OTA Update. Even with FRP, all you are doing is stopping someone who stole / found your phone from accessing your data. Obviously you must unlock Bootloader to gain real control over your data by flashing a ROM just as those created by @minimale_ldz. Once Bootloader is unlocked, it's permanent. So-called 'relocking' is purely superficial and can be simply undone by anyone with fastboot access.
So the answer is no, flashing Stock Recovery and 'relocking' Bootloader does absolutely nothing for you in terms of security.
Newer phones such as Moto G (3rd Gen) support FRP out of the box. But again, you are at the mercy of Google and Motorola when it comes to privacy as long as the Bootloader remains locked. You cannot root, nor install a custom ROM.
I fear ultimately you must examine your own psychological / egoic need for control and privacy, as the world outside your mind is unlikely to deliver what you seek.
lost101 said:
Originally Falcon (and Peregrine I suspect) did not support Factory Reset Protection (FRP) - this may have changed for those with locked Bootloaders who updated to Lollipop via official OTA Update. Even with FRP, all you are doing is stopping someone who stole / found your phone from accessing your data. Obviously you must unlock Bootloader to gain real control over your data by flashing a ROM just as those created by @minimale_ldz. Once Bootloader is unlocked, it's permanent. So-called 'relocking' is purely superficial and can be simply undone by anyone with fastboot access.
So the answer is no, flashing Stock Recovery and 'relocking' Bootloader does absolutely nothing for you in terms of security.
Newer phones such as Moto G (3rd Gen) support FRP out of the box. But again, you are at the mercy of Google and Motorola when it comes to privacy as long as the Bootloader remains locked. You cannot root, nor install a custom ROM.
I fear ultimately you must examine your own psychological / egoic need for control and privacy, as the world outside your mind is unlikely to deliver what you seek.
Click to expand...
Click to collapse
Is it possible to make or do something that no one would be able to enter recovery mode without password or at least pin code?
_that said:
Using encryption helps in this case. Just remember that when you get your phone back, don't trust it anymore.
Click to expand...
Click to collapse
So encrypting the phone would help to protect data. In case of loost or stolen phone, the person would only be able to delete my data through recovery mode?
And what do you mean that after I'd get my phone back I shouldn't trust it?
I know this device is currently only available in China and not planned for a global release. I had one imported and I have been getting my feet wet with development. How hard is it to extract the kernel and driver blobs from the Chinese Rom and create a Global Rom or Custom Rom? I know I'm asking a bit of a "how long is a piece of string" question here. It's because I don't know what I don't know. I figured I just get the conversation started here in-case anyone else has more input / experience on this subject. As this device isn't too much different than the Mi 10 / 10 Pro models, I've been trying to retrace the footsteps of the development on these devices.
The latest Chinese MIUI 12 Rom for Mi 10 Ultra:
http://bigota.d.miui.com/V12.0.7.0....JCNXM_20200813.0000.00_10.0_cn_2513f349af.tgz
I can see the boot.img and recover.img files within. I know you can extract the kernel from the boot.img file but I'm not great with a hex editor / binary splitter.
There is a thread over on xiaomi.eu discussing the possibility of a Mi 10 Ultra Global Rom from them:
https://xiaomi.eu/community/threads/xiaomi-mi-10-ultra-xiaomi-eu-rom-support.56988/
Xiaomi Mi 10 / 10 Pro unlock bootloader / root:
https://forum.xda-developers.com/xiaomi-mi-10/how-to/guide-mi-10-10-pro-root-guide-t4071553
Unofficial TWRP for Mi 10 / 10 Pro:
https://www.xda-developers.com/unofficial-twrp-is-now-available-for-the-xiaomi-mi-10-and-mi-10-pro/
https://forum.xda-developers.com/xi...xperimental-unofficial-twrp-mi-10-10-t4106385
https://github.com/simonsmh/android_device_xiaomi_umi
https://mega.nz/folder/hk0giYJZ#jj3pKafnkhxph5DdWjce1g
I'm with you on this, looking for alternative English rom and the possibility of being able to enable band 20 in the radio chip. I'm sure this has been software disabled, you just wouldn't make a separate chip with no Band 20, it's much cheaper to use a stock chip.
Going to apply for bootloader unlock today, as it looks like there is a waiting period. Done my back ups yesterday, so hopefully bootloader unlocked soon, then wait for twrp and root. I'm no coder but happy to help if I can be of any help.
Developer Options has OEM unlock and the method to use the Mi Unlock Tool to start the waiting period. So the process seems the same as for any other Mi phone I guess I will be starting that off too this weekend!
Sathelp said:
I'm with you on this, looking for alternative English rom and the possibility of being able to enable band 20 in the radio chip. I'm sure this has been software disabled, you just wouldn't make a separate chip with no Band 20, it's much cheaper to use a stock chip.
Click to expand...
Click to collapse
This makes sense... I don't "know" if it's true but I've definitely seen before this attempted in custom ROMS: stuff like changing the modem config, software solutions. And it is the sister phone to the main Mi 10 line, which does come in Global. So... Here's hoping!
This is pretty interesting. Here in Spain the Band 20 is the only one we're missing, and it would be wonderful if it can be activated.
It would be the perfect phone if it wasn't for this and for the red tint on some 4K videos.
There's a thread on xda about unlocking the band frequencies on qualcomm devices. If anyone could try it would appreciate a lot. :fingers-crossed:
The waiting game begins!
{
"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"
}
I ran into a little trouble with the unlock process. Nothing too big, but my sincere advice is log in with your MIUI number, and make sure you can "find your device" on https://i.mi.com/ to get this far
Sathelp said:
I'm with you on this, looking for alternative English rom and the possibility of being able to enable band 20 in the radio chip. I'm sure this has been software disabled, you just wouldn't make a separate chip with no Band 20, it's much cheaper to use a stock chip.
Going to apply for bootloader unlock today, as it looks like there is a waiting period. Done my back ups yesterday, so hopefully bootloader unlocked soon, then wait for twrp and root. I'm no coder but happy to help if I can be of any help.
Click to expand...
Click to collapse
I too am very interested in seeing if it's possible to get band 20 enabled, that would be awesome. I've looked for threads on this subject, there is one in particular that has a lot of information on it, right here. It seems that a lot of people active different bands in the LTE config file, check with an app that looks at the config file but don't actually check to see if the modem installed in the phone supports those bands and lets the phone connect to them. So I'm cautious, looks to me some people here report false-positives.
Please keep us posted, a combined effort here might shed more light on the possibilities and ways to get there.
EDIT: The phone has the Qualcomm X55 5G modem (source), which does just about every band on 2G, 3G and 4G according to several sites (example). So hardware-wise we might be good.
Defo. I'm keeping a cross several forums but as it's so new, there's not too much happening yet. Shame it's only China that it's released in or there would much quicker work. edit, after having a good read of the articles and posts, flashing or changing modem settings looks promising to open up the closed bands. As others have done this, at least there is some hope. First thing is to get this rooted. Another few days to get this done but I am looking for root, twrp and magisk info for this one.
There's a Telegram Group for Mi 10 that will be used also for Ultra
Maybe there will be more infos there, maybe a unified build
Appelsap said:
I too am very interested in seeing if it's possible to get band 20 enabled, that would be awesome. I've looked for threads on this subject, there is one in particular that has a lot of information on it, right here. It seems that a lot of people active different bands in the LTE config file, check with an app that looks at the config file but don't actually check to see if the modem installed in the phone supports those bands and lets the phone connect to them. So I'm cautious, looks to me some people here report false-positives.
Please keep us posted, a combined effort here might shed more light on the possibilities and ways to get there.
EDIT: The phone has the Qualcomm X55 5G modem (source), which does just about every band on 2G, 3G and 4G according to several sites (example). So hardware-wise we might be good.
Click to expand...
Click to collapse
It looks to me like the Mi 10 / Pro / Ultra all share most of the same chips:
https://www.techinsights.com/blog/xiaomi-mi-10-teardown-analysis
Makes me wonder if it isn't as easy as adapting one of the existing roms for those devices to run on the Ultra....
sirTAVARES said:
There's a Telegram Group for Mi 10 that will be used also for Ultra
Maybe there will be more infos there, maybe a unified build
Click to expand...
Click to collapse
Do you have a link to the Telegram Group?
Just saw this:
https://xiaomi.eu/community/threads/guide-how-to-install-xiaomi-eu-rom-for-xiaomi-mi10-ultra.57259/
https://forum.xda-developers.com/xiaomi-mi-10-ultra/how-to/tried-xiaomi-eu-rom-ultra-t4158149
ToneLa said:
The waiting game begins!
I ran into a little trouble with the unlock process. Nothing too big, but my sincere advice is log in with your MIUI number, and make sure you can "find your device" on https://i.mi.com/ to get this far
Click to expand...
Click to collapse
Whats this about? Is this the only option to unlock the phone? I am new to Xiaomi having been a Samsung Note user from day 1, and don't understand this process ....
Is there another option for those who are willing to wait? or is this the only way to unlock the phone? I have tried to stay clear of signing up for anything on this device. I get pop-ups often on this phone. An example is in Settings -> VPN. I have my own paid VPN service, yet there is no way to set anything. Press VPN in Settings and I get "Set Lock Screen Password - Set a lock screen password to save your VPN settings" why? I've never had to do this for any device in the past. I don't do passwords, thumb scan, face reco or any of those things. Yet this is the only option? Its terribly intrusive that MY password MUST be stored on the device for MY VPN service, with no other option.
Is this the case with unlocking? No other option?
Thx.
Burginthorn said:
Whats this about? Is this the only option to unlock the phone? I am new to Xiaomi having been a Samsung Note user from day 1, and don't understand this process ....
Is there another option for those who are willing to wait? or is this the only way to unlock the phone? I have tried to stay clear of signing up for anything on this device. I get pop-ups often on this phone. An example is in Settings -> VPN. I have my own paid VPN service, yet there is no way to set anything. Press VPN in Settings and I get "Set Lock Screen Password - Set a lock screen password to save your VPN settings" why? I've never had to do this for any device in the past. I don't do passwords, thumb scan, face reco or any of those things. Yet this is the only option? Its terribly intrusive that MY password MUST be stored on the device for MY VPN service, with no other option.
Is this the case with unlocking? No other option?
Thx.
Click to expand...
Click to collapse
You REALLY should have worked out some of your scenarios before you got the phone. For me and a lot of other people here I guess, the obvious thing to do is see the phone itself now as a temporary project which you will eventually customise to your liking.
Example now, this morning, I've flashed Xiaomi.eu's ROM instead of the stock Chinese image. And you've not even started the unlock countdown yet and had it as long as me? Trust me, nobody posts things "the hard way", if there was another method I'd have mentioned it.
Please take this as friendly advice: you really don't seem like you like your phone. That's OK, anything positive I've said about the Mi 10 Ultra has been with one eye on the future. MIUI is... I can work with it, but I'm looking to wave it goodbye, yknow?
IMO What you WANT to be doing with this is yes, doing the Mi Unlock service TODAY - and next week, several of us will already have had a week in a xiaomi.eu rom. Plenty of us want as close to stock android as possible!
So, with respect, I see you're having issues now, but get on the boat already - start that unlock countdown, and start dreaming of what can be changed about your phone. Much of what you're unhappy about here is strictly software.
ToneLa said:
You REALLY should have worked out some of your scenarios before you got the phone. For me and a lot of other people here I guess, the obvious thing to do is see the phone itself now as a temporary project which you will eventually customise to your liking.
Example now, this morning, I've flashed Xiaomi.eu's ROM instead of the stock Chinese image. And you've not even started the unlock countdown yet and had it as long as me? Trust me, nobody posts things "the hard way", if there was another method I'd have mentioned it.
Please take this as friendly advice: you really don't seem like you like your phone. That's OK, anything positive I've said about the Mi 10 Ultra has been with one eye on the future. MIUI is... I can work with it, but I'm looking to wave it goodbye, yknow?
IMO What you WANT to be doing with this is yes, doing the Mi Unlock service TODAY - and next week, several of us will already have had a week in a xiaomi.eu rom. Plenty of us want as close to stock android as possible!
So, with respect, I see you're having issues now, but get on the boat already - start that unlock countdown, and start dreaming of what can be changed about your phone. Much of what you're unhappy about here is strictly software.
Click to expand...
Click to collapse
Or you could choose not to reply to my posts if that's not too difficult.
Burginthorn said:
Or you could choose not to reply to my posts if that's not too difficult.
Click to expand...
Click to collapse
You mean like you quoted mine with everything but custom ROM development?
A custom ROM would solve all your problems. But yeah, if I'm the bad guy for saying "the best thing you can do for your phone today is start the unlock process" then I can live with who I am.
But if you have a ton of complaints, list them in a reply to me I get a notification about, then you can't wonder why I respond. I thought you relied on notification features yourself?
Similarly, I am also looking forward to custom ROMs (for example, rehabilitation Remix / PE / havoc). I am a Chinese user, and I hope that God can make native ROMs as soon as possible