Related
Hello there. Since saturday evening I'm working on oPhone port. I'm porting from oPhone SDK which is free to download from there
Code:
http://www.oms-sdn.com/
you only need to register.
EDIT (7/7/09 - 17:25):Hey, sorry for "inactivity" but I was working on it but I've updated only my twitter (@detoxcz). I've skipped radio initialization so now you can play with it a lil more. Graphics issue still persists
Get it here: http://www.mediafire.com/?nwdxbmixjm0
EDIT (18/6/09 - 17:18):l Okay, another news. I'm releasing the latest update.zip. Now you can swipe down notification bar and play with it. Graphics issue still persists. I'm workin on it.
Latest build, take it or leave it.
EDIT (17/6/09 - 18:09): We have an update. I won't upload it but now the screen can go black and when you hit Menu you will get to lockscreen (but there is still that crazy graphics issue) and you can see the blue ring (actually, due to graphics issue it's only moving rectangle). Screen is now reacting, when it's dim (not fully black, only dim) and you will tap on it, it will get brightness as before.
EDIT: Some news. I've tried flashing my latest version into G1 and then nandroid. These files I've copied to dir where oPhone emulator images was. I have used mine ramdisk.img, system.img, userdata.img but not the kernel. It works, phone works but can't get trough "Searching SIM Card" dialog (that should be the touch screen block at G1) and when I have done screenshot in DDMS it's same as DDMS from G1. So I'm not sure what the reason for this graphics issue. My personal tip is, that it's kernel with the drivers. I have also tried to copy this (nandroid-ed images from G1) into images forder of regular SDK (not the oPhone one) and phone didn't even start. I'm attaching screenshot with DDMS and emulator.
I already have first test version. It's only for testing because it won't boot properly (in logcat you can see the system is running but no display feedback).
You can get it here
Code:
http://www.edisk.cz/stahni/69148/update.zip_77.28MB.html
(I will upload it on odther sites too)
You WILL need haykuro's new SPL (same as for Hero)
Reason why I'm releasing this is, that I want anyone who can to help. Please try to find out bugs and solutions and write to me and I will do new update.zip. I'm working on it right now but getting even worse than before.
So thanks for your help and advices
PS: You can write me mail: [email protected] or ICQ/AIM: 278-783-808
EDIT: New version is out. It's still only testing version but now it boots and you can see it booted in Home application. From now you can't do anything, you can yust switch out your keyboard and it will animate to landscape and back when you will switch it back. I'm trying my best to get you fully workin' oPhone ROM.
Get it here:
Code:
http://www.mediafire.com/?uimitlz3pr4
and screen from ddms (it's nicer than in device)
{
"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"
}
If you like my work, feel free to buy me some cupcake-s
can't wait for this. think u can post some screenshots.
dont think he can yet
DeToX-cz said:
I already have first test version. It's only for testing because it won't boot properly (in logcat you can see the system is running but no display feedback).
Click to expand...
Click to collapse
I will do some from emulator and i will upload photos what it's doing when it's booting. It have ****ed up graphics and audio drivers or flinkers.
detox hit me up on gtalk [email protected]
A video in HD of the Ophone emulator Here via L3wish
Is anyone else having an issue downloading this...?
Mines constantly stuck on 6%.
Is it safe to say that its a alpha release or pre beta release.
Senorkabob said:
Is anyone else having an issue downloading this...?
Mines constantly stuck on 6%.
Click to expand...
Click to collapse
No mine downloaded...im not sure if i would flash my phone with it but i want to look at the files...
not to go off topic but does any one know how to sign an update.zip on a mac...i want to help DeToX with this.
N3xt2N0N3 said:
No mine downloaded...im not sure if i would flash my phone with it but i want to look at the files...
not to go off topic but does any one know how to sign an update.zip on a mac...i want to help DeToX with this.
Click to expand...
Click to collapse
it will not boot at this time dont flash lol
Yep, if expecting booting to Home screen i have to dissapoint you. What this do is, that it's booting and booting and booting and there is issue with Video drivers or somethink like that. But when it's booting, you can connect it by ADB.
I think one of the biggest hurdles we are going to come across is driver support on the G1. Rumor that Haykuro had it running on his G1 could have meant recovery console...etc. The Hardware is pretty different on the Lenovo oPhone. I don't think just pushing over some libraries and some .so's are going to do it. I can only assume it will take possibly a recompile of the kernel in order to run on the G1's Hardware.
acidnine said:
I think one of the biggest hurdles we are going to come across is driver support on the G1. Rumor that Haykuro had it running on his G1 could have meant recovery console...etc. The Hardware is pretty different on the Lenovo oPhone. I don't think just pushing over some libraries and some .so's are going to do it. I can only assume it will take possibly a recompile of the kernel in order to run on the G1's Hardware.
Click to expand...
Click to collapse
Yeah I was thinking it wasn't going to work but i still wanted to try...juat to confirm this.
Thats why i asked if any one knew how to sign update.zip on a mac
I don't think just pushing over some libraries and some .so's are going to do it. I can only assume it will take possibly a recompile of the kernel in order to run on the G1's Hardware.
Click to expand...
Click to collapse
Yeah, for the meantime I think I'll just stick with playing on the emulator.
The home screen is really the only thing I found so far that makes this an OS I'd like to flash. Personally I think the Rosie UI is a bit nicer.
I do like the ability to have up to 9 screens though.
no this ophone runs on the htc magic which is close to our phone there is a pic of it some where and htc is releasing it this month
acidnine said:
I think one of the biggest hurdles we are going to come across is driver support on the G1. Rumor that Haykuro had it running on his G1 could have meant recovery console...etc. The Hardware is pretty different on the Lenovo oPhone. I don't think just pushing over some libraries and some .so's are going to do it. I can only assume it will take possibly a recompile of the kernel in order to run on the G1's Hardware.
Click to expand...
Click to collapse
Well I agree with you that it seems unlikely that we'll be able to use the full ROM as is, but it seems like we should be able to cannibalize some of the libraries/apks.
Haykuro already ported this, someone might wanna contact him!
Quote from his Twitter page:"no i don't have an oPhone. just got hold of the SDK (openly available http://www.oms-sdn.com/ here) but i DID port the image to the g1
7:06 PM Jun 12th from web"
http://www.twitter.com/haykuro
here is the pic in case any one was curious but its been posted for a while so most of you have probably seen it
i just sent haykuro a tweet asking if he would ever release his port or to atleast tell us what he did to get it working. Is there a way to set the os to english instead of chinese in the emulator.
i just sent haykuro a tweet asking if he would ever release his port or to atleast tell us what he did to get it working. Is there a way to set the os to english instead of chinese in the emulator.
Click to expand...
Click to collapse
It doesnt do it automatically?
I didnt change any settings, and mine is english by default.
I figured this should be in its own thread so those working on a solution can now focus on the software side of things.
{
"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"
}
These are the JTAG connection points I traced from the CPU to their test points. i'm almost 90% sure the Primary is still usable. Auxilary JTAG port is Very very hard to get too and i'd imagine even for the technicians that reprogram them at the repair center. I didnt have much luck getting a connection made due to mu lack of JTAG knowledge and incorrect type of JTAG circuit(working on another though). i'm posting up the complete testpoints I spent MANY MANY countless hours and sleepless nights tracing so someone who has done this before can get a recovery procedure made to fix all bricked HTC-dreams. The reason I am doing all of this is not specifically for the Dream but because in the field of work im in, and the type of work I do I could benefit from it both for my personal phones and at work. I did research over the years but could never quite understand how JTAG is used until now. I took my spare fully working beater G1 and unsoldered the CPU with an IR Rework Station(T-870A) at home with the intentions of placing the CPU back on when done. took ALOT longer than I hoped and because of the fact that i had to hold test probes on the contact pads tight so I could flip the board and trace their also, it killed a couple of the pads so thats when I decided to say screw it, still have all the spares for my main Dream, now I can REALLY find the rest of the pins....and a few extras that might be used in the future to add features.
********Technical Notes*******
Their are 4 Mode control pins listed in the pictures.
Mode 3 is under the SIM slot, accessing requires de-soldering 4 points holding the SIM carrier to the board.
Mode 0 is NOT a testpoint, but a solder point were a resistor could go to ground. it is VERY hard to solder too directly.
Watchdog pin can simply be grounded with a resistor in place or with a needle through the shielding which would be ground. its a single solder point.
Primary JTAG is next to the LCD connector.
When you see were the pins for AUX are located you will see why I think thats not were the focus should be...their scattered in odd places, also have to remove the sim slot to access the last one which took forever to find.
Trackball has a hidden test point for the return clock as well, otherwise you need to solder directly to the connector on the main board.
Note: Return Clock is missing in the Picture for the AUX_JTAG connector...it is located at the top right testpoint just above the trackball pad, otherwise you will need to solder directly to the connector on main board.
if you need any more just let me know, if anyone wants to add to this please feel free.
Images are NOT MINE, they are the property of whomever took them, I only traced and added the labels, if their is a problem with using them let me know!
IF anyone wants to donate a bricked G1 board for experimenting or donate in general please feel welcome! [email protected] [email protected]
Great job, I hope someone with the knowledge can jump on this because even if my phone isn't bricked (which its not) there's always a chance it could get bricked. This is a pretty good find in my opinion.
A clearer picture might be needed though if its possible.
nice find!
I'll be watching this as it "develops".
Hey BinaryDroid,
that's great stuff!!
Excellent finding, now we need some software
Maybe someone should check out accessing the phone with QMAT!
BTW, here's a picture stolen from the Phonewreck team.
I just inserted the testpoints you found. Hope it's O.K.!
If not tell me and i will delete the picture immediately
EDIT: Deleted attachment, because of copyright issues
Very nice work!
Cheers,
scholbert
BinaryDroid said:
...their scattered in odd places, also have to remove the sim slot to access the last one which took forever to find.
Trackball has a hidden test point for the return clock as well, otherwise you need to solder directly to the connector on the main board.
Click to expand...
Click to collapse
If necessary, removing the sim slot and trackball is a small price to pay to bring one of these back from the dead.
But wow, I gotta say.... I wasnt expecting those primary points to be *SO EASY* to get at.
Yea they were easy to trace, also over this past weekend I did manage to find the mode control pins and Watchdog pin, NAND write protection enable pin..basicallly searching for anything that might be helpful. I got the wires all soldered to the board also and the phone does recognize theirs something connected to the port but the data its returning dont seem like its correct. with nothing plugged in I get "no cable connected", after plugging the cable in i'm getting "Phone did not enter debug mode, reset?" This was before I found the mode pins using only what is posted so far and on a perfectly working phone in blue light mode which I dont think matter because it does the same thing with the phone off so long as a battery is in, does not work at all with no battery. I just went out and purchased a new camera for clearer pictures so pointing out the remaining pins is easier. I believe we may see a solution!
BTW i'm using OCD commander, plan on purchasing QMAT with JTAG this week since it tailors to HTC phones, once everything is figured out i'm sure we can use whats available free with a little modding.
@Scholbert, I thought about using those picures myself but didnt want to cause any copyright issues, I am going to put up a better picture anyhow. once thats up can you please remove the image so no one complains?
OpenOCD, OpenOCD, OpenOCD.
Did I mention OpenOCD?
http://openocd.berlios.de/web/
Would be great...
lbcoder said:
OpenOCD, OpenOCD, OpenOCD.
Did I mention OpenOCD?
http://openocd.berlios.de/web/
Would be great...
Click to expand...
Click to collapse
Hehe yea I didnt try that one yet since my Ubuntu install was killed by the latest update so I had to install windows first, gonna install Ubuntu sometime this week and try the tools available their.
BinaryDroid said:
my Ubuntu install was killed by the latest update
Click to expand...
Click to collapse
You're not the only one 9.10 is a car crash.
off topic: 9.10 wrecked my mouse on my laptop, my wifi, my screen doesn't function properly, and sound is messed up.
On-topic: great job on this, i'm glad we might have a way to fix the bricked phones soon, my phone works fine but there is always that chance, and i have been meaning to get off the stock SPL
And this is why I use Fedora....
I don't even remember the last time an update broke something.
Hi!
BinaryDroid said:
@Scholbert, I thought about using those picures myself but didnt want to cause any copyright issues, I am going to put up a better picture anyhow. once thats up can you please remove the image so no one complains?
Click to expand...
Click to collapse
Maybe you're right. That's why i asked.
I just removed the pic!
I'm getting a Dream in the next days, if you're not able to take these pics, i may help out!
Just tell me
Best regards,
scholbert
Ooops double post....
EDIT: You said you got already all the necessary pins.
Anyway, maybe this may help to verify:
http://forum.xda-developers.com/showpost.php?p=4150161&postcount=300
Some time ago r3nrut put a very interesting package for download at his webpage. You may ask him for a link to download DreamJTAGcode.rar.
Included are professional scripts to set up the Dream with a PCI JTAG controller card named JT3710 from JTAG Technologies.
Though no one would afford such a hardware, you may find many useful files
Cheers,
scholbert
scholbert said:
Ooops double post....
EDIT: You said you got already all the necessary pins.
Anyway, maybe this may help to verify:
http://forum.xda-developers.com/showpost.php?p=4150161&postcount=300
Some time ago r3nrut put a very interesting package for download at his webpage. You may ask him for a link to download DreamJTAGcode.rar.
Included are professional scripts to set up the Dream with a PCI JTAG controller card named JT3710 from JTAG Technologies.
Though no one would afford such a hardware, you may find many useful files
Cheers,
scholbert
Click to expand...
Click to collapse
Yes he gave me the access to the files already, thats one of the reasons I need to installed windows first lol. I never used windows on the development machine but honestly the only thing that seems to hold the important data is the scripts which are human readable so I'm almost sure they could be adopted to OpenOCD or similar. I mean it even has the label on which pins need to be set high, low or what have you, ways to flash, erase, you name it its their. after seeing those files I figured we didnt need the JTAG document that were seeking. if everyone can figure it out on other devices with no documents..surely cant be too hard. i have soooo much more software to test on linux though. i have no plan after work so probably going to install Ubuntu 9.04 , turn off updates and then test OpenOCD. that seems really positive! i've got 3 different parallel Jtag adapters made for testing, Old cheapo, Buffered, and the third is a really complicated one that has all the possible connections needed(but more to go wrong hehe)
I could really use some help on how you normally get a phone into debug mode, or how can I do a simple test to read the Chip ID?
Also does anyone have a bricked board their willing to donate? i'm doing all of this on my primary functional board and would hate to kill i, also not sure if i'm actually in debug mode.
Hi BinaryDroid!
I could really use some help on how you normally get a phone into debug mode, or how can I do a simple test to read the Chip ID?
Click to expand...
Click to collapse
May help out if i got my device....
Anyway it would be very nice idea to contact ViperBJK (author of QMAT).
He prooved JTAG access to Diamond already and good very deep knowledge of the device.
Debug mode should be also activated by hardware.
If nothing works out it would be a possibility is to ask one of the Hard-SPL creators. Disassembly of the SPL may give a hint of activating debug mode.
It's obvious, that the mode pins are important to be setup correctly.
The watchdog needs to be disabled (can't remember the pin), PS_HOLD would be required too.
The MSM chipset is bit more complex to access for debugging.
We need patience to gather the necessary informations.
MPU on Hermes was much easier i guess
EDIT:
From what i know so far, there would be mainly two methods on MSM to give access to the NAND chip:
1. Using TAP controller
This is a basic access and it is possible to toggle the pins in hardware, simple LPT adaptor should do the job.
2. Using ETM unit
This should be the mode used in QMAT.
Some binary is loaded into RAM (RAM needs to be initialised) and is used as a programming tool.
ETM gives control to the memory, but it's bit more complex to handle.
Anyway, the ARM units inside MSM chip have different ID's. Both should be accessible through primary port.
As far as in know MMU needs to be disabled while accessing the chip.
Regards,
scholbert
scholbert said:
Hi BinaryDroid!
May help out if i got my device....
Anyway it would be very nice idea to contact ViperBJK (author of QMAT).
He prooved JTAG access to Diamond already and good very deep knowledge of the device.
Debug mode should be also activated by hardware.
If nothing works out it would be a possibility is to ask one of the Hard-SPL creators. Disassembly of the SPL may give a hint of activating debug mode.
It's obvious, that the mode pins are important to be setup correctly.
The watchdog needs to be disabled (can't remember the pin), PS_HOLD would be required too.
The MSM chipset is bit more complex to access for debugging.
We need patience to gather the necessary informations.
MPU on Hermes was much easier i guess
EDIT:
From what i know so far, there would be mainly two methods on MSM to give access to the NAND chip:
1. Using TAP controller
This is a basic access and it is possible to toggle the pins in hardware, simple LPT adaptor should do the job.
2. Using ETM unit
This should be the mode used in QMAT.
Some binary is loaded into RAM (RAM needs to be initialised) and is used as a programming tool.
ETM gives control to the memory, but it's bit more complex to handle.
Anyway, the ARM units inside MSM chip have different ID's. Both should be accessible through primary port.
As far as in know MMU needs to be disabled while accessing the chip.
Regards,
scholbert
Click to expand...
Click to collapse
Ok well purchaed QMAt with JTAG last night since that tool has been written specifically for the job and will help with getting everything figured out, plus i need it for other projects. the QMAT setup does not mention the mode control pins being used at all for some reason. only the pins I already found which did not seem to work with my 5 wire unbuffered Wiggler. I have to do another test tonight with the complete complicated version that is suggested just until I get it working. once I know the connection works i'll adapt the simpler wiggler to do the same job so anyone trying to unbrick can build the simple $10 dollar adapter and build themselves. I aleady have a plan to make the soldering job to the jtag pins painless via modding the EM shield. at least now with QMAT purchased I can feel better asking him questions and getting correct answers. Primary JTAG is definitely the way to go. your correct also about the ps_hold pin attached to 10K resistor to the watchdog pin.
Small step for Man, a giant leap for Android
BinaryDroid said:
Ok well purchaed QMAt with JTAG last night since that tool has been written specifically for the job and will help with getting everything figured out, plus i need it for other projects.
...
Primary JTAG is definitely the way to go. your correct also about the ps_hold pin attached to 10K resistor to the watchdog pin.
Click to expand...
Click to collapse
@BinaryDroid @r3nrut Keep going, good stuff. Thanks for your hard work!
I have my G1 taken apart (no, it's not bricked - I am changing the housing). Do you want me to label the Primary JTAG pinout on one of the high-resolution pictures I am taking?
How close are you to the secondary pinout?
Did you ever find the elusive pdf document with JTAG connection details?
Wonderful
once I know the connection works i'll adapt the simpler wiggler to do the same job so anyone trying to unbrick can build the simple $10 dollar adapter and build themselves.
Click to expand...
Click to collapse
Yeah that would be awesome...
To support the MSM7xxx familie in OpenOCD would also be very nice.
I saw lbcoder already posted a link
Anyway, if we use boundary scan mode the software implementation would not be very complicated.
First step would be to build up a header file from the BSD-file of MSM7xxx.
Also simple buffered LPT-adaptor could be used.
Have a look at this package...
Keep on hacking!
scholbert
Excellent work Binary Droid!!!
I'm working on gathering a few bricked boards for testing on. If I get two I'll send one your way.
Have they been verified?
Ok, we know the pinout, but has anyone successfully connected up to these pins and checked them? I.e. can you get a response to the IDCODE command working?
I gave it a quick test (with Segger), but it was not able to see anything on the chain.
For what it's worth, the Segger wants VTref (target reference voltage), and nSRST (target CPU reset signal) which we don't have labelled. I left nSRST disconnected and tied VTref to an external 3.3 source.
Someone made a thread here looking for a way to fully disable the annoying search button that is SO sensitive that it basically makes you hate wanting to use the phone. I'm in that same boat...I never 'purposely' use that Bing search button and would muchly prefer to kill it....for lack of a better word LOL Someone replied to that post saying "you can remove the button completely by copying a 0kb websearch.exe to /windows/". I have registry editor but I want to make sure I'm completely understanding what they're saying so I don't end up screwing up my phone and needing to re-flash the ROM. The poster of that comment hasn't been online in a few days so I figured I'd ask here instead of waiting for he/she to answer a PM. Can anyone expound on this? Thx!
you dont use a reg edit, use something like touchxplorer to copy a blank file that you create named websearch.exe
you run touchxplorer and copy the file into the /windows/ directory
it should be on the main directory
ill post some pics in a bit
alexrodri0 said:
you dont use a reg edit, use something like touchxplorer to copy a blank file that you create named websearch.exe
you run touchxplorer and copy the file into the /windows/ directory
it should be on the main directory
ill post some pics in a bit
Click to expand...
Click to collapse
Awesome thanks! I'll keep an eye out
first put a blank file on your phone by copying it to an xap file then deploy it to your phone
deploy touchxplorer.xap to your phone
1.http://i44.tinypic.com/10z4juq.jpg
2.http://i40.tinypic.com/xg6xc.jpg
3.http://i43.tinypic.com/9t1eu8.jpg
4.http://i39.tinypic.com/sbh5hz.jpg
5.http://i40.tinypic.com/2jbsjlc.jpg
6.http://i41.tinypic.com/of518g.jpg
alexrodri0 said:
first put a blank file on your phone by copying it to an xap file then deploy it to your phone
deploy touchxplorer.xap to your phone
1.http://i44.tinypic.com/10z4juq.jpg
2.http://i40.tinypic.com/xg6xc.jpg
3.http://i43.tinypic.com/9t1eu8.jpg
4.http://i39.tinypic.com/sbh5hz.jpg
5.http://i40.tinypic.com/2jbsjlc.jpg
6.http://i41.tinypic.com/of518g.jpg
Click to expand...
Click to collapse
You're spectacular for doing this! A million thanks to you
I do have a couple questions tho...
I've never used Touchxplorer however I go have a file explorer combo tool thing from here. Still have yet to use it though...(I'm sync'ing with Zune at the moment so I'm not if that's why nothing is displaying on the screen of the file explorer when I open it or what- 30% more to sync, nearly done)...moving on...
...so, when you say "copy the blank file to an xap"...
#1) ...how/where do I create this blank file and...
#2) ...what do I use to copy it to an xap? I've sideloaded xap's tons of times before just never needed to do what you're instructing.
Also if you'd recommend using Touchxplorer instead of what I currently have I can do that. Let me know...thanks again
@Momomuffins: Advanced Explorer is a great app, but it was never updated for Mango so it will only work if you're on an old WP7 version or possibly a custom ROM. TouchXplorer is only the filesystem component, not the registry component (there's a separate app from the same guy for registry), but it (mostly) works on Mango. http://touchxperience.com/ and look under Forums for TouchXplorer.
However, be aware that neither Advanced Explorer nor TouchXplorer will work correctly if your phone has the HTC updates for Mango. They block the file operations that are needed for those tools to work. These updates are typically installed at the same time you install Mango.
On the other hand, if you have an interop-unlocked HTC phone, that means you don't (or at one point didn't) have those updates, so this *might* work right now. If you're on pre-Mango then it doesn't matter at all. If you're on Samsung, then neither of the apps discussed above will work; you need WP7 Root Tools (sticky on this forum). If you're not on HTC or Samsung, we don't currently have any filesystem write access in \Windows at all.
I'd be interested to hear if this works in any case. It's not supposed to be possible to overwrite ROM files, such as the EXEs in \Windows\.
GoodDayToDie said:
@Momomuffins: Advanced Explorer is a great app, but it was never updated for Mango so it will only work if you're on an old WP7 version or possibly a custom ROM. TouchXplorer is only the filesystem component, not the registry component (there's a separate app from the same guy for registry), but it (mostly) works on Mango. http://touchxperience.com/ and look under Forums for TouchXplorer.
However, be aware that neither Advanced Explorer nor TouchXplorer will work correctly if your phone has the HTC updates for Mango. They block the file operations that are needed for those tools to work. These updates are typically installed at the same time you install Mango.
On the other hand, if you have an interop-unlocked HTC phone, that means you don't (or at one point didn't) have those updates, so this *might* work right now. If you're on pre-Mango then it doesn't matter at all. If you're on Samsung, then neither of the apps discussed above will work; you need WP7 Root Tools (sticky on this forum). If you're not on HTC or Samsung, we don't currently have any filesystem write access in \Windows at all.
I'd be interested to hear if this works in any case. It's not supposed to be possible to overwrite ROM files, such as the EXEs in \Windows\.
Click to expand...
Click to collapse
Ahh cool, good to know...I am running a custom ROM (Touch-IT v4) on an HTC HD7s, however before I ever ripped into my phone and unlocked it I did the load the Mango update thru Zune. That's overwritten anyway by the new ROM I'm assuming so it's a non-issue. I just added TouchXplorer and went to the TouchXperience site for some instruction and saw a file path I thought I'd try...the screen capture below is what I get. I type it and click OK but it goes nowhere and all the options are greyed out. That friggin' site TouchXperience is a maze...what am I not doing right or is this how it acts after the Mango 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"
}
After the samsung firmware update a while back, I haven't had a problem with accidentely hitting any of the hardware buttons. I did at first and I couldn't stand it but I gues I've gotten used to it now. Plus with Mango, mostly everything can be fast app switched back on.
Still I hope you get your problem solved.
Momomuffins said:
Ahh cool, good to know...I am running a custom ROM (Touch-IT v4) on an HTC HD7s, however before I ever ripped into my phone and unlocked it I did the load the Mango update thru Zune. That's overwritten anyway by the new ROM I'm assuming so it's a non-issue. I just added TouchXplorer and went to the TouchXperience site for some instruction and saw a file path I thought I'd try...the screen capture below is what I get. I type it and click OK but it goes nowhere and all the options are greyed out. That friggin' site TouchXperience is a maze...what am I not doing right or is this how it acts after the Mango update?
Click to expand...
Click to collapse
That's how it acts after the HTC updates that are usually shipped along with Mango. It used to be possible to avoid those updates (my phone doesn't have them, but is therefore out of date since I'm on a stock ROM) but it required upgrading to Mango through pre-release versions and then getting the stock retail update, but canceling the HTC update. Now, the HTC update is bundled into the stock update.
There are ROMs which use the older versions of the HTCFileUtility and HTCRegUtility drivers (drivers in this sense being the things that allow low-privilege apps to do high-privilege operations). On those ROMs, TouchXplorer still works (in fact, this is usually how it's advertised). You can probably find one, if you don't mind re-flashing your phone again.
GoodDayToDie said:
I'd be interested to hear if this works in any case. It's not supposed to be possible to overwrite ROM files, such as the EXEs in \Windows\.
Click to expand...
Click to collapse
I have create a blank file websearch.exe and put it over WindowsPhone PowerTools in a exist xap folder.
Then copy it with WP7 Root Tools to \Windows folder. I confirm the overwrite the existing websearch.exe ROM File- But It's not supported to to overwrite ROM files .......
WindowsPhone PowerTools it´s a poweful and cool tool
GoodDayToDie said:
That's how it acts after the HTC updates that are usually shipped along with Mango. It used to be possible to avoid those updates (my phone doesn't have them, but is therefore out of date since I'm on a stock ROM) but it required upgrading to Mango through pre-release versions and then getting the stock retail update, but canceling the HTC update. Now, the HTC update is bundled into the stock update.
There are ROMs which use the older versions of the HTCFileUtility and HTCRegUtility drivers (drivers in this sense being the things that allow low-privilege apps to do high-privilege operations). On those ROMs, TouchXplorer still works (in fact, this is usually how it's advertised). You can probably find one, if you don't mind re-flashing your phone again.
Click to expand...
Click to collapse
WOW...ok...I'm glad you know about this to that extent. I thought loading a new ROM over what was there already negated that whole problem with the updates...I'm still a n00b Much to learn obviously...
Alright then...can you recommend a ROM in particular that will get me out of this so I don't have to go thread hunting again for the billionth time? I don't mind re-flashing...done it plenty of times trying out different things and the last time I did it I didn't download all my apps back or anything that would create too much of an asspain in the future had I needed to re-do it all again
Well, since I use the stock ROM's I can't really recommend one over another. The problem with the update is that people took HTC's Mango ROM as a base, and it already had the (anti-TouchXplorer) patch included. Some people didn't revert that patch, and it sounds like you're using one of their ROMs.
Generally speaking, the DFT ROMs seem to be pretty solid, if perhaps not so "fancy" as some others. I really don't know which ones are actually good, though - never done the research.
Moved to WP7 Q&A
No questions in the development section please. Please refer to the read before posting sticky before posting in this section.
Take it easy
O_G
GoodDayToDie said:
Well, since I use the stock ROM's I can't really recommend one over another. The problem with the update is that people took HTC's Mango ROM as a base, and it already had the (anti-TouchXplorer) patch included. Some people didn't revert that patch, and it sounds like you're using one of their ROMs.
Generally speaking, the DFT ROMs seem to be pretty solid, if perhaps not so "fancy" as some others. I really don't know which ones are actually good, though - never done the research.
Click to expand...
Click to collapse
Thanks for all of your help. I'm just now getting a chance to sit back down and do this. If run into a snag I'll surely be back here
Hey, this seach button problem is super anoying... Dont know why but since the most recent firmware update, i seem to be hitting it all the time. Its there a way to disable it? Nobody in this thread is saying if it worked for them... I would appreciate if someone will share his experience...
Im interop unlocked btw...
ronclone said:
Hey, this seach button problem is super anoying... Dont know why but since the most recent firmware update, i seem to be hitting it all the time. Its there a way to disable it? Nobody in this thread is saying if it worked for them... I would appreciate if someone will share his experience...
Im interop unlocked btw...
Click to expand...
Click to collapse
I definitely know what u mean. That effing button has been the most annoying thing I could possibly imagine. I don't even have to touch the friggin button to make it launch. Because of the impending holiday tomorrow and kid's birthday I haven't had the time I thought I would this week to get this done but we can keep in touch and I'll let you know what happens. What device do you have?
I tried but unsuccessfully, please!
tienthanh080 said:
I tried but unsuccessfully, please!
Click to expand...
Click to collapse
Can you briefly list what you tried? Have you unlocked your phone (what kind of phone), are you using a certain ROM, etc?
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 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