I bought a MECOOL KM9 android box from the flea market. The Android on it was something custom from some IPTV service provider. On the bottom it says KM9 so I downloaded firmware from here. Using Aml_Burn_Tool the flashing got stuck at 30%, left it for about two hours didn't budge. After this the computer does not recognize the device (no plug-in sound, tested on two computers) and there is no output on HDMI.
So, I got to method two, which is the SD card burned with Burn Card Maker (multiple versions). Tested several firmware, several SD cards, no luck.
Opened up the device to get the serial output, you can find the output attached. Taking a closer look at the board I saw that is marked as: KM1 X2 DDR3 v1.4. The pcb doesn't look like the KM1's pcb and the SoC is different too. My board has Amlogic S905X2, the KM1 has Amlogic S905X3. Also, the pcb doesn't look like the KM9 board either.
The output log is the same regardless having an SD card or pressing de recovery button. It stops with "sdio read data fail". I don't think the EMMC is broken, earlier in the log it says "Load FIP HDR from eMMC" and there is no error. Also, if I have a bootable SD, shouldn't the EMMC be skipped?
As a last resort I tried shorting pins on the NAND chip, the computer still wouldn't detect it however if i short pins the serial output changes, again file attached.
Any ideas? Can I bring it back to life? At least does anyone have this board and firmware for it?
Thank you,
Alex
fyrewurx said:
I bought a MECOOL KM9 android box from the flea market. The Android on it was something custom from some IPTV service provider.
Click to expand...
Click to collapse
In which country? Do you have the provider information? That information might help identify or locate the original build of the firmware.
fyrewurx said:
Opened up the device to get the serial output, you can find the output attached. Taking a closer look at the board I saw that is marked as: KM1 X2 DDR3 v1.4.
Click to expand...
Click to collapse
It's too late now, but it would have been best to connect the uart and dump the original firmware before flashing anything. I understand that the label on the cover is wrong and that it does not match the board, but if you had a backup you could start over. Now, the drm keys (if any) are probably gone and the wrong dtb seems to have been flashed. Maybe it still can be fixed since the bootloader does still boot somewhat, but that may not be the original bootloader but rather the one that was flashed before the flashing failed.
fyrewurx said:
Also, if I have a bootable SD, shouldn't the EMMC be skipped?
Click to expand...
Click to collapse
There are different types of SD booting. For the lowest level booting, the emmc is skipped only if no bootable bootloader is found on the emmc.
It also will be skipped if the emmc clk resistor is removed. 4R1 may be the emmc clk resistor. Check if it is zero ohms. If it is not zero ohms, check the other side of the board.
Once the device is always booting from the SD card, try various videostrong (not skyworth!) firmware for S905X2 devices, like the KM3 and others (such as the KM9 Pro, which uses the X2). I don't see any information for this KM1 X2 device. It may be a custom variant for OTT providers.
Thank you very much for taking the time to answer.
All I can remember is that it was something Polish. You are right, having the original firmware would have been great. I usually check how much info there is on the internet (mainly xda) about the device I want to flash. If there is a lot, I don't bother with backup. Miiiistake. I didn't knew about the clk resistor and I assume others either because people don't mention on the internet. They recommend shorting the pins which is not a great idea in my mind. I did it with a random 330 ohm resistor to be on the safer side. I will definitely try to get the box to boot from SD and then try firmware from KM1 to KM whatever they got up to with the X2.
From your experience are these devices picky about the SD card? It would be easier if I test only with one card.
The DRM keys you mentioned, would stop the device from booting or the box just wont play Netflix and other streaming services? Even without Netflix I would like to get the box going.
I will have to lookup what a DTB file is, I have no idea. The board looks to be custom as there is one other picture I found about the device here.
Just for my knowledge, the bootloader for these devices is also in the main EMMC? I am used to x86 where you have an external memory to keep first stages of bootloader.
I attached closeups on the EMMC and the back, maybe we need them further on.
Thanks again for the reply,
Alex
fyrewurx said:
The board looks to be custom as there is one other picture I found about the device here.
Click to expand...
Click to collapse
Based on those photos, there is a chance that your board is (or is compatible with the firmware from) the KM9 PRO or the KM9 PRO DELUXE.
If this is the case, the state that your device is in now is probably a result of trying to flash an android 9 firmware image to a device that had an existing installation of android 10. If so, there is a decent chance that you can fix it.
You may be able to get a uart shell prompt by experimenting with shorting the emmc clk at various times, so that the attempt to load the invalid dtb (from the flashed firmware) fails. If you can get a uart shell prompt, you can start burn mode (uart shell command "update"), and then use command line tools to flash the km9 pro or km9 pro deluxe firmware.
Otherwise, remove the emmc clk resistor (once it is located), and raw copy the bootloader (from km9 pro or km9 pro deluxed) to the sd card. It isn't necessary to put the resistor back when you are done, a jumper wire can be used since it is zero ohms.
Functioner said:
Based on those photos, there is a chance that your board is (or is compatible with the firmware from) the KM9 PRO or the KM9 PRO DELUXE.
Click to expand...
Click to collapse
The KM9 devices use DDR4 memory, my board has DDR3. Can the firmware still be compatible?
I don't know. Maybe if the dtb has support for both types of ram. You'd have to check the dtb.
If you flash the dtb while watching the uart output, you'll know if it will work. But first you'd need to be able to start fastboot or have access to the uart shell, in order to flash it.
Support for both types of ram is not uncommon. For example, the sdmc dv8555 (S905x2) has multiple hardware versions, some with ddr3 and some with lpdd4, and both boards use the same firmware.
The original dtb and bootloader on your device are probably gone. They probably were overwritten before the flashing failed at 30%. You don't have much to lose by trying the other firmware, except perhaps a lot of your time.
I will try for sure. As you sad, there's nothing to loose. I probably shouldn't even bother (it was less then 10 dollars), but I hate contributing to e-waste, specially when the hardware is fine, the issue is software. And it's kinda my fault .
Related
Hello, I have several questions about rooting and backing up my Android tablet but I'm not really sure where to begin.
My (current) goal is to back up the firmware that's currently on the tablet so that I can later restore to it in the event that something goes wrong. The only problem is I seem to have a newer version than the latest-offered version that was posted on the manufacturer's website, but the latest-offered version doesn't work. To make matters worse, the manufacturer's website is no longer online so there's no chance that the firmware I have will ever be uploaded. In other words, I need to root my tablet so that I can make a backup of the stock firmware to revert to if necessary.
The tablet in question is a Panimage Media Tablet R79RT2W5 that I picked up for $20. Before you tell me not to bother or that it's a piece of crap, don't worry; I'm VERY aware. The entire reason I bought this to begin with was BECAUSE it was a piece of crap. I was hoping that at the very least I could screw around with it and use it as a testbench to learn Android programming on with hardware I don't care about possibly bricking. (In other words, I wanted a cheap tablet to play around with so I wouldn't risk bricking my phone.)
I'll try to give you all the possible information I have on it. If you need any more information, pictures, screenshots, uploaded files, etc. I'll try to get what I can for you.
Panimage Media Tablet
Model Number R79RT2W5 (according to the physical sticker on back)
Model Number R79RTW5 (according to the 'About Device' page; note the lack of the 2 in the model number there.)
256MB of RAM
Firmware Version 1.6 (Donut, apparently?)
Kernel Version 2.6.29
Build Number WMT2.1.7_PD
2GB Internal Flash Memory (according to the box)
- Apparently it's a Gome Flytouch clone?
- It has a whole bunch of software made by WonderMedia Technlogies. (Which makes sense considering that it has a WMT-based processor.)
- It has "App Market" com.wonderappstore instead of Google Market. In other words, I basically have to sideload apks to get anything worth using.
Click to expand...
Click to collapse
Things to take note of:
- It has no USB port so I can't hook it directly to a computer (meaning regular ADB won't work), but it does take microSD cards.
- I can sideload applications, but they need to be able to work on 1.6, obviously.
- I have FTPServer installed so I can send files to/from my computer, but I can't access protected directories.
- I have run BOTH Universal Androot and z4root. Neither program rooted the tablet. z4root DID install SuperUser (which I'm assuming only worked because USB debugging was turned on), but SuperUser doesn't work.
- I'm willing to work with terminals or command prompts so long as I have someone able to walk me through the process.
Is rooting this thing a possibility?
Alternatively, the way that the firmware update process works is that you put a folder named "script.zip" on the root of the microSD card and then boot the tablet with the card inserted. The tablet will then proceed to automatically install the firmware on it.
Would it be possible to take advantage of this function to allow me to run a script that will back up the firmware to the microSD card before it boots that I would then later be able to restore onto the tablet as necessary?
I can upload a copy of the latest script.zip I have so that you can take a look at it if you'd like.
What do you mean by their isn't a USB port what do you use to charge.
Sent from my HTC Velocity 4G using Tapatalk 4 beta
WildfireDEV said:
What do you mean by their isn't a USB port what do you use to charge.
Click to expand...
Click to collapse
It has a generic electrical plug; one of the round ones with a single prong in the middle.
It doesn't charge through USB like most other phones/tablets, because there's no USB port on it.
you can possibly back up your phone's firmware even without a usb port...
using the stock recovery, you can flash a custom recovery like clockworkmod which gives you a back-up option... and you can also root it with that...
WisdomSky said:
you can possibly back up your phone's firmware even without a usb port...
using the stock recovery, you can flash a custom recovery like clockworkmod which gives you a back-up option... and you can also root it with that...
Click to expand...
Click to collapse
That's a bit of a problem... the tablet doesn't appear to have a stock recovery available.
I've tried as many button combinations upon boot as I can think of (Power + Vol. Down among many other things) and none of them boot into any sort of recovery mode.
I've even gone as far as trying to force my way in using the SysRq trick that someone got to work for the Ouya:
http://forum.xda-developers.com/showpost.php?p=42516267&postcount=6
...but unfortunately that doesn't work either. No mater what Alt + SysRq combination I use (out of the ones that actually work, that is), the tablet automatically restarts. Every time.
However, as I said in my OP, I think that there may be a small bit of hope.
Alternatively, the way that the firmware update process works is that you put a folder named "script.zip" on the root of the microSD card and then boot the tablet with the card inserted. The tablet will then proceed to automatically install the firmware on it.
Would it be possible to take advantage of this function to allow me to run a script that will back up the firmware to the microSD card before it boots that I would then later be able to restore onto the tablet as necessary?
I can upload a copy of the latest script.zip I have so that you can take a look at it if you'd like.
Click to expand...
Click to collapse
After a bit of messing around, I've found that the firmware update process looks for a file named "prepare.bin" and then loads it, which starts the automatic firmware update process.
While I'd rather try doing some sort of manual root on the tablet if possible, I'd be willing to try to make my own version of "prepare.bin" that will allow me to essentially hijack the firmware update process before it begins, which should essentially give me system-level control over the tablet.
...In theory, that is.
Do you think this would be a possibility?
I'd post pictures and screenshots and links and other information I've found, but I don't seem to have enough posts to do that yet...
edit- To be more direct, I'm willing to try to hijack the boot process to run my own code if possible, but I'd much rather do some sort of manual root or something if possible so I don't risk screwing up my tablet. As I said before, neither z4root nor Universal Androot work for my tablet, so I was wondering if there's some sort of manual exploit I can use to get in from within Android. If that's possible, I'd much rather take that approach as opposed to basically brute forcing my way into system-level access and risk bricking something.
My M9S-Pro finally arrived. It's a modest AmLogic S905 chip with a Mali-450, notably only because it has Ethernet, three USB ports, 3 GB of RAM and a 32 GB ROM.
My kids use the Nexus Player as a gaming device, but I am constantly running out of space even with Marshmallow's USB space reallocation (which does not work perfectly by any means). I bought this hoping to replace the Nexus Player which only has 8GB (+ whatever Marshmallow offers, and whatever some apps will allow transfer to external storage).
Right off the bat, it boots quickly and is stable. It included Kodi, some generic TV streamer with pay TV streams in foreign languages, a file manager, Antutu, various video players, and Netflix. The USB port puts out enough current to power an external 2.5" HDD.
Antutu score is 31,300 if that matters to you.
I found a version of TWRP that worked great and I rooted this by flashing the same beta-SuperSU as I used on my Nexus Player.
It uses an IR remote with shortcuts to different apps and a mouse function. It's slow but usable. I use it with an airmouse with a better experience.
I am running HAL Launcher which is just about the best experience you can hope for with a Chinese box. I also added the keylist for the Bluetooth controllers from the OUYA that I had years ago, and my kids use it for a gaming box.
It's a good value for me, but if you use Android TV boxes for streaming only you don't need the space and should probably get a cheaper box - maybe one running 6.0+ so it supports the latest version of Kodi.
Now that I have TWRP and root, I am looking for an AOSP experience.
Are these available for AmLogic systems? I've seen RemixOS for certain AmLogic boxes, but they're all a bit different and haven't tried experimenting with that yet.
How did you get this device rooted and how did you boot it into TWRP?
If rooted the Docooler, could I run a Long Term Release of Ubuntu or Mint on it. I've used Linux with our Brother MFC-J835DW and its simple to print from any Application. Android not good at all. 2nd is with Ubuntu I can set up multiple guest users in various Languages "English" " "Spanish" etc. so a guest can log on , browse, print, done.
On Android it seems to remember Users, not sure how to delete,
Very hard to print "share",
Doesn't appear to allow set up to multiple users so can only run as 1 language.
I really like that these boxes have separate monitors, keyboards, and appear not to require a fan as we are at the beach with a lot of salt air. All my connections require DiElectric Grease from Autozone so as not to corrode. Even better would be a sealed heat sink case.
Ken PlayaLindaHotel.com
root m9s-pro docooler amlogic s905 how
how root and install twrp in that model please tell me
Send me the links of software that must to download
hello, i have the m9s pro 32gb and i have slow speed in WiFi connection. Does anyone have the same problem and how can i solved? thanks in advance
Hello everyone, where can I get the original stock firmware? tnx
shdware said:
My M9S-Pro finally arrived. It's a modest AmLogic S905 chip with a Mali-450, notably only because it has Ethernet, three USB ports, 3 GB of RAM and a 32 GB ROM.
My kids use the Nexus Player as a gaming device, but I am constantly running out of space even with Marshmallow's USB space reallocation (which does not work perfectly by any means). I bought this hoping to replace the Nexus Player which only has 8GB (+ whatever Marshmallow offers, and whatever some apps will allow transfer to external storage).
Right off the bat, it boots quickly and is stable. It included Kodi, some generic TV streamer with pay TV streams in foreign languages, a file manager, Antutu, various video players, and Netflix. The USB port puts out enough current to power an external 2.5" HDD.
Antutu score is 31,300 if that matters to you.
I found a version of TWRP that worked great and I rooted this by flashing the same beta-SuperSU as I used on my Nexus Player.
It uses an IR remote with shortcuts to different apps and a mouse function. It's slow but usable. I use it with an airmouse with a better experience.
I am running HAL Launcher which is just about the best experience you can hope for with a Chinese box. I also added the keylist for the Bluetooth controllers from the OUYA that I had years ago, and my kids use it for a gaming box.
It's a good value for me, but if you use Android TV boxes for streaming only you don't need the space and should probably get a cheaper box - maybe one running 6.0+ so it supports the latest version of Kodi.
Click to expand...
Click to collapse
dow did you root the device?
@alexxdj,
You'll need to do two things.
First, download TWRP for AmLogic devices. The link is below for a whole bunch of them.
http://freaktab.com/forum/tv-player-support/amlogic-based-tv-players/16228-twrp-for-amlogic-devices
I don't remember which one I used, but I believe it was for a Minix S905 device. As long as it's S905, they are similar enough that you should be okay. Make sure it is scaled properly when you use it.
Then you'll need to download ChainFire's SuperSU.
https://download.chainfire.eu/743/supersu
Copy both files to a SD card. TWRP will be bootable, but you will need to press/hold the button that's hidden in the audio out jack. I simply used a pin. So, unplug the unit, insert the SD card, insert the pin, then plug it back in and wait for it to boot to TWRP.
If all looks well, great. You will need a mouse for this part.
Flash SuperSU as normal. Reboot.
After I booted, I actually had to run the supersu APK to make it work properly. I used Root Explorer (since it opens files in zip files with ease) to do this.
I hope this helps.
thanks for your information but where is this hidden button? I cant find it!!!
It's in one of the audio jacks in the back of the unit. Open it up if you need to see it: it comes apart easy and goes back together easy.
Otherwise get a long pin or needle and poke in the jacks until you feel it click.
shdware said:
It's in one of the audio jacks in the back of the unit. Open it up if you need to see it: it comes apart easy and goes back together easy.
Otherwise get a long pin or needle and poke in the jacks until you feel it click.
Click to expand...
Click to collapse
i found it is the spdif jack thanks. do you remember if needs to rename the recovery? Because i downloaded the recovery for minix s905 but i cant boot it to twrp
Try naming it 'recovery.img'
The recovery should not be zipped. Extract the IMG file if it is.
yes i know that. maybe i tried wrong recovery. after 2 times failed to boot to recovery. when i release the button? when i show the android and starts to erase?
alexxdj said:
i found it is the spdif jack thanks. do you remember if needs to rename the recovery? Because i downloaded the recovery for minix s905 but i cant boot it to twrp
Click to expand...
Click to collapse
I press and hold it until the TWRP logo appears.
I think you have the wrong recovery. Try the MINIX MX one. AmLogic makes a lot of devices, and the S805, S812, S905, and S912 all require different recoveries.
You need to make sure it's for the S905. Google is your friend here.
After I successfully rooted, I ultimately decided to flash TWRP itself on my box.
i tried 50 recovery for s905 form yesterday but nothing. Cant boot to twrp!!
alexxdj said:
i tried 50 recovery for s905 form yesterday but nothing. Cant boot to twrp!!
Click to expand...
Click to collapse
Apologies, I didn't realize the URL to Freaktab was truncated. I've corrected it now.
TWRP for AmLogic Devices
Try a few of these. There are only 31, and over half of them can be discounted because they are not for the S905.
If I remember right, I used this one:
/TWRP_MiniMX.img
shdware said:
Apologies, I didn't realize the URL to Freaktab was truncated. I've corrected it now.
TWRP for AmLogic Devices
Try a few of these. There are only 31, and over half of them can be discounted because they are not for the S905.
If I remember right, I used this one:
/TWRP_MiniMX.img
Click to expand...
Click to collapse
You remember right!!!! this recovery was. thanks for your help friend.
@Gi3drius, @k_graham, @stilonas -
I've provided a tutorial. Read the comments and let me know if they help.
is there any update for this tx box?? and why do you want to install TWRP? I use it only fr install roms but I can´t find any for this model
I managed to create a fully unbranded firmware for the X96 that also allows to use custom bootanimations.
Since the hardware of a lot of S905X boxes is literally identical this should work on other boxes as well !?
Mine has 2/16GB but it should be possible to remove some things for 1/8GB models.
I tried a lot of firmwares from other boxes on mine with various success rates (did not modifiy anything in the firmwares).
AFAIK all it takes is a custom recovery for the box in question and that problem should be quite easy to fix anyway.
Has anyone done firmwares that work on multiple boxes?
Would anyone be willing to de-brand their box?
Could not let it rest, so I started playing with TWRP 3.1 in the meantime.
Although I manage to get all partition included, so a few more than with TWRP 3.0, it seems to be impossible to mount the external SD for any good use.
Backups and restores work from internal or USB only
TWRP 3.0 does not backup the logo, bootloader and /tee or the original recovery for that matter.
IMHO that means without the means to flash a genuine firmware in case something goes wrong I am stuck now.
Not 100% certain how important a backup of the other stuff would be these days but I would prefer to offer the option of a full nand backup instead of just system, data, cache and boot.
Still, the mods to the firmware are basically completed and it should work on most if not all S905X boxes with the same hardware.
Working on including more WiFI drivers though.
Very interesting I got a T95X that I wanted to use a "netflix machine" and the android version is atrocious.
The only thing about is that it uses a wifi chipset (9082xs) that it seems there is no sources yet.
Are you progressing?
Progress is relative here...
Several S905 boxes are conform to the same standard in terms of partition layout and hidden partitions, while other manufacturers brew their own.
One thing that would need fixing is a routine to check what WiFi chipset is used and activate the corresponding drivers, or one would need to flash this after the actual firmware.
The other thing, as said, is the partitions.
Could make sense to actually collect and list the data of the various boxes out there to join what can be joined.
This way we should be able to do with just 3 or 4 firmwares to suit all.
Downunder35m said:
Progress is relative here...
Several S905 boxes are conform to the same standard in terms of partition layout and hidden partitions, while other manufacturers brew their own.
One thing that would need fixing is a routine to check what WiFi chipset is used and activate the corresponding drivers, or one would need to flash this after the actual firmware.
The other thing, as said, is the partitions.
Could make sense to actually collect and list the data of the various boxes out there to join what can be joined.
This way we should be able to do with just 3 or 4 firmwares to suit all.
Click to expand...
Click to collapse
OK, so let me know if I can help you.
You can take the WiFi folder from your firmware and replace the one in a suitable firmware to get it working on your box.
If rooted and the bootloader is unlocked you might even be able to just install the Open GAPPS TV package.
Just because it always fails on my box might not mean it fails on all boxes.
I am starting to think a "universal" firmware is only possible by creating a system partition that is happy with whatever kernel and startup routines are present on a device.
But even then there are still problems depending on how the security and additional security features are implemented in the kernel.
Not to mention managing partitions that are not available on all devices.
s905x
sorry for the presumptiousness but i dont know where else to turn. my m9c pro 4k 1/8gb box which has the marshmallow OS has stopped working. i had formatted my sdcard as internal memory forgot took the card out and gave it away now when it boots it continuosly shows the mbox boot screen runs my iptv in the back ground i can change channels up/down but cant see any thing because the mbox boot screen is still there.can you help me to recover using an sd card, please. i had a stroke so my memory is bad. thanks. also need link to the files. this box has a reset button underneath but it apparently only works when it has a bootable sdcard in it.
Downunder35m said:
I managed to create a fully unbranded firmware for the X96 that also allows to use custom bootanimations.
Since the hardware of a lot of S905X boxes is literally identical this should work on other boxes as well !?
Mine has 2/16GB but it should be possible to remove some things for 1/8GB models.
I tried a lot of firmwares from other boxes on mine with various success rates (did not modifiy anything in the firmwares).
AFAIK all it takes is a custom recovery for the box in question and that problem should be quite easy to fix anyway.
Has anyone done firmwares that work on multiple boxes?
Would anyone be willing to de-brand their box?
Click to expand...
Click to collapse
will your fully unbranded firmware work with T3X Mini............if yes will you like to share please
I had this TV Box I'd bought from Wish. I thought I would share a (nearly) stock image. I pulled it after having to play around with the Google Play Store for a while because it ceased functioning.
I had noticed several other people having issues with obtaining a stock ROM, possibly on other forums.
https://1drv.ms/f/s!AtYTbQWzzbfRiBZEsUFK73q2H-pX
Thought it thru some more today and I'm adding a raw image of boot, bootloader and system. There may be more on this device that someone will find useful, if it's the case, let me know so I can dumped and post it.
File availability
Hi engineerchad
I am seeking the files you previously linked to, however they no longer appear available.
I'd be very grateful if you could make them available again please, if you do not mind?
Thank you
Andy
Link dead
engineerchad said:
Thought it thru some more today and I'm adding a raw image of boot, bootloader and system. There may be more on this device that someone will find useful, if it's the case, let me know so I can dumped and post it.
Click to expand...
Click to collapse
I am searching for this ROM but the link seems to be dead. Can you re-upload it?
abpdora said:
I am searching for this ROM but the link seems to be dead. Can you re-upload it?
Click to expand...
Click to collapse
I will go ahead and put it back up, give me a little bit seems like I lost the files on my online drive so I'll have to go ahead and either pull from a backup or take it off the device again. Check back later today or tomorrow and I should have a new link posted for you.
Onedrive:
https://1drv.ms/f/s!Am__eYU6nzsDgYMcl4D4gdMkAnLIuw
Mega:
https://mega.nz/#F!u8t3ECYS!HH8I-DPraAsc1CwMeTt-1Q
I hope it helps! I would post the link for the TWRP recovery that I used, but it was specifically stated to -please- not link up to it, reproduce, copy, re-upload, etc by the author. I located it with a Google search for "TWRP Amlogic S905W" or something of the like. It doesn't function perfectly (on my high-def TV, it displays on the top half of the screen, with the bottom half just kind of filled with garbage and you NEED a mouse hooked to the box to use it, but it's workable).
engineerchad said:
Onedrive:
https://1drv.ms/f/s!Am__eYU6nzsDgYMcl4D4gdMkAnLIuw
Mega:
https://mega.nz/#F!u8t3ECYS!HH8I-DPraAsc1CwMeTt-1Q
I hope it helps! I would post the link for the TWRP recovery that I used, but it was specifically stated to -please- not link up to it, reproduce, copy, re-upload, etc by the author. I located it with a Google search for "TWRP Amlogic S905W" or something of the like. It doesn't function perfectly (on my high-def TV, it displays on the top half of the screen, with the bottom half just kind of filled with garbage and you NEED a mouse hooked to the box to use it, but it's workable).
Click to expand...
Click to collapse
Pull original recovery and send me a link ill try porting a fully functional version
Ricky Divjakovski said:
Pull original recovery and send me a link ill try porting a fully functional version
Click to expand...
Click to collapse
It should show in both links "recovery.stock.img" is the filename.
The conventions of naming partitions on the box are quite simple /dev/block/system /dev/block/recovery /dev/block/boot etc (I believe. I actually haven't plugged this one in for a minute after I got a slight upgrade for it that I'm using now.) I had originally intended to do this myself, but have been trying for a long time to recover from the mental/physical effects of a quarter million dollar set of injuries last year and it's been pretty brutal.
I see where someone has done an unofficial TWRP in https://forum.xda-developers.com/android-stick--console-computers/amlogic/recovery-twrp-3-0-2-0-touch-recovery-t3454549 for this device with 8GB ROM, so I'm not sure if this would work just as well, or if it needs to be remade (this box is labelled as A95X and it's the amlogic s905x chipset with 2GB/16GB so I'm not sure if it would somehow be different from the link above or not.)
I figured I'd update, it seems like I may have misread the post originally on freaktab the author requested people share this link as opposed to mirroring. Here it is (had to search it up again, by coincidence it's also working for my a95x max + box which is also OTT TV brand I'll try to get an image up from that but my computer shows it has a root trojan in the stock image?)
http://konstakang.com/devices/nexbox_a95x/TWRP/
twrp complete backup
Hi Can you post a full backup with all partitions?
I have a a95x pro s905w too, and lost L1 widevine
Thanks for your support.
Best Regards from Spain
Here you have the last update.zip from the vendor:
A95X(905w2_16)_PRO-7.1.2-201806201412 2018062016101756843 zip
https://drive.google.com/file/d/1aSNU51sA3hm2bI-S1w7fz2l_jrmjD6Ks
try and see if it solve your problem
afaik, the OTT TV BOX stock firmware has a su included. There's just no SuperSU or other app to control access to it from what I've seen (and it's been pretty touchy while trying to install one, IME)
hi
i have A95X R1 Android 7.1 CPU Amlogic S905W 2.0GHz GPU Mali-450MP5 RAM 2G ROM 16G, anyone have a firmware or ROM for it pls??
is-serb said:
hi
i have A95X R1 Android 7.1 CPU Amlogic S905W 2.0GHz GPU Mali-450MP5 RAM 2G ROM 16G, anyone have a firmware or ROM for it pls??
Click to expand...
Click to collapse
seeking that same firmware ..
firmware
deetucks said:
seeking that same firmware ..
Click to expand...
Click to collapse
I have a95x 1g 8g and was at android 6 (this has 2 g 16g as well posted below)
Link posted is for ALL firmwares for the ott nexbox devices. Pretty sure some of you will need this. The listing does not say 7.1.2 but it is. It says 7 or 7.1 no worries. I got it, used it.
It is nexbox... so if you have the nexbox logo on your screen this is your stock 7.1.2 as I have just upgraded my box today.
You can use twrp, but do it from SD and never install it as you don't need to. Put twrp .img file NOT the zip with the blank update zip below. Never need to lose stock recovery.... I think. Not sure about custom roms yet but will lknow in an hour I'd say. Also included a zip of a program that will format your sd card fat32. I had a 64 gig card and windows won't make it fat32. Stupid.
As far as making the bootable sd card, I kept only getting 2 files when I ran the burn card maker you may have seen. That uboot one never was put in. Then by mistake I loaded the main img file after one completion. So not sure if you have to hit make twice or maybe because I used a 64 gig card. But with all 3 files there, I stuck in the sd card, nothing except hdmi plugged in.... held the reset button in and powered on..... got the android guy and a long update bar.......updated!
If you can put stock by SD card... do it! That other method via USB with USB burning tool app? If it works, yay. But I never got it working. That fat32 maker was very handy!
Link if you have nexbox:
https://mega.nz/#F!F9xjTSSa!R0vJfTC2U6Qc2skNMrr1iQ!4wpwzJyS
Has twrp but all crappy like mentioned earlier... pretty sure. But all firmware from 5 to 7 and I got 7 from there.
its not a nexbox..and its 2g 16g.. i cant find its stock rom anywhere,, the ds card thing does not work either ..i tried with numerous custom rom jus dont boot with the ds card,,
deetucks said:
its not a nexbox..and its 2g 16g.. i cant find its stock rom anywhere,, the ds card thing does not work either ..i tried with numerous custom rom jus dont boot with the ds card,,
Click to expand...
Click to collapse
That sucks. The link posted has 2 gig 16 gig. All firmwares... think my board is the same.
hmm.. think it is the same box. I will re-read your specs if you listed them
How did you get firmware to sd card, is it fat32 and only stock will work... so not sure but I think if you try from the link I posted, it won't screw you up? I think?
Ott tv box
model: R1
cpu: Amlogic s905w
ram: 2gb rom :16gb
[email protected]
---------- Post added at 11:45 AM ---------- Previous post was at 11:43 AM ----------
i can always try ,, i definately will look into it and give a try,,
deetucks said:
Ott tv box
model: R1
cpu: Amlogic s905w
ram: 2gb rom :16gb
[email protected]
Click to expand...
Click to collapse
oh you got the w.....have you looked on freaktab? Some site I just discovered. There is a good chance you'll find it there or someone can help.
I just tried looking and there is almost nothing. Weird because I could have sworn I saw a lot of s905w when I first started this.. Now you got me looking.
trust me i,m on freaktab cant find nothing.. request help nothing so far..
---------- Post added at 12:08 PM ---------- Previous post was at 11:55 AM ----------
trust me i,m on freaktab cant find nothing.. request help nothing so far..
Hi all, I am new to the forums and I think that I need some help with a custom android project.
[Background]
I have bought a Meraki MC74, This phone is a VOIP office desk phone that has a nice 7 inch LCD screen that make for a ballin' custom intercom phone/general android device.
Cisco Meraki has dropped support for this phone, so even if I wanted to pay for a subscription, I couldn't. So custom android it is
[So what I know]
I know that the OEM OS is android 4.X.X with a custom Cisco Meraki dialer to do Meraki's cloud mumbojumbo. I was able to use ADB and Fastboot to flash ClockworkMod, and a custom version of Android 4.1.2 to get the device somewhat working. (it had lots of bugs and problems; but it was running android free of the Cisco Dialer!)
I was able to do this with the help of fellow xdadevelopers forum user "andrewmospak" (If you're reading this; I'm the dude from Ebay. And of course, thanks bro for the help so far!)
The storage is on a 4 GB Kingston EMMC.
[What I wanted for an end goal]
I wanted to have an interesting discontinued Meraki Desk phone that runs android and get all the functions of the phone working within android.
I also wanted to expand the storage from 4GB to 32GB. ( involving de-soldering existing EMMC and solder in the bigger EMMC.)
[What caused me to write this]
I would be fine if I wanted to stop there, but I wanted to try to install a GSI of android 9 in place of 4.1.2.
Again, this wouldn't be a big deal but I had to go and screw this up. I tried to resize some of the partitions (namely system to accommodate the bigger image of the android 9 GSI)but I accidentally completely killed the system,cache, and recovery partitions.
So, as one of the first steps of trouble shooting, I went to the hardest solution. The de-soldering of the EMMC.
I reached out to Andrewmospak again and asked for a full system emmc dump to try to flash his working file system to a spare 4GB EMMC to see an example of the file system of a working android EMMC. I received the image and flashed it to a spare Toshiba chip and soldered that to the phone, but I was unable to get the phone to boot into android right away, only able to load up fastboot.
Interestingly, I know that the EMMC is working because fastboot reports the S/N as the S/N of Andrewmospak's device and not the one written on my device.
[What I don't know]
Should some of the partitions on the EMMC not be recognized by Gparted in Debian? Like the User/System and others are partitioned ext4 while others are just not recognized.
Why when trying to flash partitions using Fastboot, wont fastboot recognise a recovery partition. It would just say that the partition just doesn't exist. same story with boot.
[What needs help]
I would like to know why fastboot wont see flashable volumes when using the EMMC dump flashed to another spare Toshiba EMMC, it is clearly there.
I would like to know how to reconstruct a volume to fix missing ones, and the number of partitions android needs to run.
Would I be able to flash an image of my working device to a 32gb emmc and just expand the system and user partitions into that extra space?
I will appreciate all help given to assist me and others that want a working device instead of a paperweight. ogChamp: :fingers-crossed:
That is an awesome project, and a great idea for an office line. I'll look into this!
Use MC74 for dashboard
I'm really interest to know, if you can have run a web browser on the MC74.
My needs are not fancy, I want to run a web browser on the touch screen, and have network connection with the ethernet jack in the back. I want to use it to interact with a touch dashboard for my home automation trough the webbrowser.
Thank you
Is it possible you didnt get the hidden boot partition in the emmc device? I know it isn't accessible through a sd card reader but can be seen through a SDIO controller interface.
page 15 of this document discusses this:
Google this: "us-17-Etemadieh-Hacking-Hardware-With-A-$10-SD-Card-Reader-wp.pdf" first link on blackhat.com
This project interests me as these devices are dirt cheap and i could use a few multipurpose desk phones
Thank you for starting this work. I have been waiting for this day since past couple of years now.
When you get a chance, could you please post the steps up to the point where you decided to swap the emmc?
sasha0413 said:
Hi all, I am new to the forums and I think that I need some help with a custom android project.
[Background]
I have bought a Meraki MC74, This phone is a VOIP office desk phone that has a nice 7 inch LCD screen that make for a ballin' custom intercom phone/general android device.
Cisco Meraki has dropped support for this phone, so even if I wanted to pay for a subscription, I couldn't. So custom android it is
[So what I know]
I know that the OEM OS is android 4.X.X with a custom Cisco Meraki dialer to do Meraki's cloud mumbojumbo. I was able to use ADB and Fastboot to flash ClockworkMod, and a custom version of Android 4.1.2 to get the device somewhat working. (it had lots of bugs and problems; but it was running android free of the Cisco Dialer!)
I was able to do this with the help of fellow xdadevelopers forum user "andrewmospak" (If you're reading this; I'm the dude from Ebay. And of course, thanks bro for the help so far!)
The storage is on a 4 GB Kingston EMMC.
[What I wanted for an end goal]
I wanted to have an interesting discontinued Meraki Desk phone that runs android and get all the functions of the phone working within android.
I also wanted to expand the storage from 4GB to 32GB. ( involving de-soldering existing EMMC and solder in the bigger EMMC.)
[What caused me to write this]
I would be fine if I wanted to stop there, but I wanted to try to install a GSI of android 9 in place of 4.1.2.
Again, this wouldn't be a big deal but I had to go and screw this up. I tried to resize some of the partitions (namely system to accommodate the bigger image of the android 9 GSI)but I accidentally completely killed the system,cache, and recovery partitions.
So, as one of the first steps of trouble shooting, I went to the hardest solution. The de-soldering of the EMMC.
I reached out to Andrewmospak again and asked for a full system emmc dump to try to flash his working file system to a spare 4GB EMMC to see an example of the file system of a working android EMMC. I received the image and flashed it to a spare Toshiba chip and soldered that to the phone, but I was unable to get the phone to boot into android right away, only able to load up fastboot.
Interestingly, I know that the EMMC is working because fastboot reports the S/N as the S/N of Andrewmospak's device and not the one written on my device.
[What I don't know]
Should some of the partitions on the EMMC not be recognized by Gparted in Debian? Like the User/System and others are partitioned ext4 while others are just not recognized.
Why when trying to flash partitions using Fastboot, wont fastboot recognise a recovery partition. It would just say that the partition just doesn't exist. same story with boot.
[What needs help]
I would like to know why fastboot wont see flashable volumes when using the EMMC dump flashed to another spare Toshiba EMMC, it is clearly there.
I would like to know how to reconstruct a volume to fix missing ones, and the number of partitions android needs to run.
Would I be able to flash an image of my working device to a 32gb emmc and just expand the system and user partitions into that extra space?
I will appreciate all help given to assist me and others that want a working device instead of a paperweight. ogChamp: :fingers-crossed:
Click to expand...
Click to collapse
Can't get to recovery mode -- wanna help
I'd like to help and write and app that is a (open) SIP client for the MC74. I bought an apparently new MC74 but I can't get it into recovery mode. Any help in doing this (so I can install a rooted Android)?
Holding down VolUp while connecting the POE ethernet to the WAN port doesn't work. The display remains blank then every several seconds the dislpay backlight flashes for a moment. Holding down Mute and connecting power has no effect, just boot normally to the Meraki logo screens then a minute later the normal keypad and menu display. (VolDn and powerup boots normally). I've tried this with USB flash drive (with some random recovery.img file on it) in the side USB port -- then I get an icon of a broken Android robot (presumably meaning it tried something with booting off the USB.
Has my MC74 been locked down somehow? What can I do to get a rooted Android on it?
ribo said:
I'd like to help and write and app that is a (open) SIP client for the MC74. I bought an apparently new MC74 but I can't get it into recovery mode. Any help in doing this (so I can install a rooted Android)?
Holding down VolUp while connecting the POE ethernet to the WAN port doesn't work. The display remains blank then every several seconds the dislpay backlight flashes for a moment. Holding down Mute and connecting power has no effect, just boot normally to the Meraki logo screens then a minute later the normal keypad and menu display. (VolDn and powerup boots normally). I've tried this with USB flash drive (with some random recovery.img file on it) in the side USB port -- then I get an icon of a broken Android robot (presumably meaning it tried something with booting off the USB.
Has my MC74 been locked down somehow? What can I do to get a rooted Android on it?
Click to expand...
Click to collapse
The way That I was able to boot into recovery was to hold mute and volume down NOT IMMEDIATELY hold the two only after the LCD backlight turns on. Only then you will be in recovery.
realc3blues said:
Is it possible you didnt get the hidden boot partition in the emmc device? I know it isn't accessible through a sd card reader but can be seen through a SDIO controller interface.
page 15 of this document discusses this:
Google this: "us-17-Etemadieh-Hacking-Hardware-With-A-$10-SD-Card-Reader-wp.pdf" first link on blackhat.com
This project interests me as these devices are dirt cheap and i could use a few multipurpose desk phones
Click to expand...
Click to collapse
My linux machine recognizes the mystery partitions but not their contents or partition scheme with some cheap USB to SD adapters. I think it works well. Thanks for the recommendation though!
ribo said:
I'd like to help and write and app that is a (open) SIP client for the MC74. I bought an apparently new MC74 but I can't get it into recovery mode. Any help in doing this (so I can install a rooted Android)?
Holding down VolUp while connecting the POE ethernet to the WAN port doesn't work. The display remains blank then every several seconds the dislpay backlight flashes for a moment. Holding down Mute and connecting power has no effect, just boot normally to the Meraki logo screens then a minute later the normal keypad and menu display. (VolDn and powerup boots normally). I've tried this with USB flash drive (with some random recovery.img file on it) in the side USB port -- then I get an icon of a broken Android robot (presumably meaning it tried something with booting off the USB.
Has my MC74 been locked down somehow? What can I do to get a rooted Android on it?
Click to expand...
Click to collapse
You need to hold down the VOLUME DOWN button before powering on the unit, and then continue to hold it. The phone will go into Fastboot mode. The screen will be blank, but backlit, and usually the LED lights up red. Here, you can flash a custom recovery firmware image (such as the ClockworkMod one that's floating around) that allows you to make changes to the system and user partitions. The thing you're seeing with the Android robot is expected. That's the default recovery firmware. Once you flash custom recovery firmware in Fastboot mode, you then unplug the unit, hold down the MUTE button, plug the device in, and continue to hold the MUTE button. It may take some time for it to get into the recovery firmware, but be patient. FYI, VOLUME UP is used for that feature where you can switch between two "slots" for firmware. I don't really know what that is, but I know that it's a thing with Android. It's pretty much unused on the MC as far as I can tell.
Has anyone considered working backwards with the version of Android running on the MC, rather than installing an entirely new version? So, instead of trying to get new firmware to work on the unit, why not work with whatever's on the device by default and pull out what you don't need? I know that some people have gotten different versions of Android to work on the unit, but this leads to bugs or hiccups. I'd imagine that this is because the kernel for that firmware isn't specifically made for the MC, but don't take my word for it. That's just a guess.
Due to the current pandemic situation that's going on here, I've decided to occupy my time by examining the MC in depth. I've managed to get ADB shell working when the device has booted normally, allowing me to examine the filesystem and pull out whatever Meraki included with the firmware. Even got the rainbow LED to stop obnoxiously glowing! I'm currently working on getting the system UI to work (there's no status bar or app switcher).
Got adbd running on MC74, Sort of got Linphone going
@sasha0413 and @jazzcandle, I got the boot.img updated so I could set 'ro.secure=0' in /default.prop in the boot up ramdisk. So now I can 'adb' into it by TCP or USB. Thanks for the help. (My MC74 calls itself a 'test-phone' so it may be a little different software. The problem was that the 'recovery' mode installed on it was pretty subtle, nothing showed on the screen.
My MC74 runs '4.2.5-meraki' version of JellyBean api 17, because I'm not good at porting newer versions of Android -- and because there may be modifications / drivers that Meraki put in to support the hardware, I'm working on a phone app with the original JellyBean.
I managed to get an old version of 'linphone' working to the extent that I can make a call -- and can be heard -- but I haven't mastered the speakers (Android AudioManager/MediaPlayer, etc) so I can't hear the phone call. I can play audio speakerphone speaker, but can't play it on the handset speaker. Figuring out the Android Audio system for JellyBean is hard, the implementation has change a lot since then.
---------- Post added at 14:11 ---------- Previous post was at 14:04 ----------
[/COLOR @jazzcandle I installed com.teslacoilsw.launcher-4.1.0-41000-minAPI16.apk as a launcher and told use it as the launcher rather than /data/app/com.meraki.dialer2-1.apk
How did you stop the RGB LED from cycling through the colors? Does something like: /system/app/DroidNode.apk or /system/app/DroidNodeSystemSvcs.apk start the led cycling, then perahps com.meraki.dialer2 stop it -- when it initializes?
ribo said:
My MC74 calls itself a 'test-phone' so it may be a little different software. The problem was that the 'recovery' mode installed on it was pretty subtle, nothing showed on the screen.
Click to expand...
Click to collapse
This is something that stumped me early on as well. But have no fear, all MCs run the same firmware, and you're not running different "test" firmware. The "test phone" value you're referring to is only seen in the recovery partition in the "default.prop" file, where "ro.product.model" is set to "BCM28155_TEST_PHONE". When booting normally, this value is set to "Meraki MC74" instead.
ribo said:
I managed to get an old version of 'linphone' working to the extent that I can make a call -- and can be heard -- but I haven't mastered the speakers (Android AudioManager/MediaPlayer, etc) so I can't hear the phone call. I can play audio speakerphone speaker, but can't play it on the handset speaker. Figuring out the Android Audio system for JellyBean is hard, the implementation has change a lot since then.
Click to expand...
Click to collapse
The way audio output works on the MC is a bit strange. In fact, it's not really Android's fault from what I can tell. However, I found that you have to "poke" the audio HAL to get it functioning somewhat normally (ie. getting audio to actually play through the speakers). You can do this by running the following command in the shell:
$ tinymix 1 1
At this point, you should be able to hear audio output through the speakers. Additionally, you should be able to switch between handset and speakerphone mode (so long as the app you're using allows you to do this).
ribo said:
I installed com.teslacoilsw.launcher-4.1.0-41000-minAPI16.apk as a launcher and told use it as the launcher rather than /data/app/com.meraki.dialer2-1.apk
Click to expand...
Click to collapse
You should delete the Dialer apk, you don't need it. In fact, you should delete the DroidNode.apk and DroidNodeSystemSvcs.apk files as well.
ribo said:
How did you stop the RGB LED from cycling through the colors? Does something like: /system/app/DroidNode.apk or /system/app/DroidNodeSystemSvcs.apk start the led cycling, then perahps com.meraki.dialer2 stop it -- when it initializes?
Click to expand...
Click to collapse
You need to modify "init.bcm911130_me1.rc" within "boot.img" and either remove or comment out the following:
Code:
service lightsd /system/bin/lightsd
class main
socket lightsd stream 600 system system
user root
Controlling RGB LED on MC74
Thanks jazzcandle, I'll look into /system/bin/lightsd to see what it does.
lightsd seems to open ANDROID_SOCKET_lightsd and listen to /dev/socket/lightsd
It seems to directly write to these /sys files to change the LEDs through which must be controlled through the SOC's GPIO pins..
/sys/class/leds/red/brightness
/sys/class/leds/green/brightness
/sys/class/leds/blue/brightness
/sys/class/leds/white/delay_off
/sys/class/leds/white/brightness
/sys/class/gpio/export
/sys/class/gpio/gpio11/directionout
/sys/class/gpio/gpio11/value
am broadcast -a com.meraki.LIGHTSD_START
I would be great to know what all the GPIO devices did and their a addresses.
I've left the Dialer2, DroidNode and DroidNodeSystemSvcs apps running at this point to see what they do and how they are used. I agree that eventually they need to be removed because they connect to cisco/meraki web services when they start up.
I noticed that the com.meraki.dialer2.LEDController class is how the dialer controls the LEDs:
public void notifyLeds(LedMode mode, int red, int green, int blue) {
this.r = red;
this.g = green;
this.b = blue;
this.m = mode;
sendLightCommand();
}
class LightCmd implements Consumer {
public void accept(Object o) {
Intent i = (Intent)o;
i.putExtra("red", r);
i.putExtra("green", g);
i.putExtra("blue", b);
Log.i(TAG, String.format("Broadcasting color change to rgb(%d, %d, %d)",
new Object[]{r, Integer.valueOf(g), Integer.valueOf(b)}));
ctx.sendBroadcast(i);
}
}
private void sendLightCommand() {
Consumer cons = new LightCmd();
getIntent().ifPresent(cons);
}
Click to expand...
Click to collapse
Methods ilke 'notifyLeds' takes a mode (Solid, Pulse, or Rainbow) and the R, G, B values and uses the sendLightCommand() method which broadcasts an intent that will probably be handled by something like the /system/bin/lightsd daemon. (I'm trying to document all these things for customizing/developing a SIP app.
I notice that the MC74 app is built on the PJSIP ( org.pjsip.pjua2 package) I was thinking of use the org.linphone SIP package. Anyone have experience with these SIP packages?
ribo said:
(I'm trying to document all these things for customizing/developing a SIP app.
I notice that the MC74 app is built on the PJSIP ( org.pjsip.pjua2 package) I was thinking of use the org.linphone SIP package. Anyone have experience with these SIP packages?
Click to expand...
Click to collapse
Thanks for documenting this, this is awesome info. A while back I built a rudimentary SIP client for MC74 based on the AJVoIP SIP package. I gave up on it once my trial period for that package expired. It was quirky, with flaky audio and no LED control (which both now could be solved by the info in this thread), but I did have hookswitch (hangup/answer by picking up the handset) working.
In the spirit of documentation, the hookswitch is an ambient light sensor that gets covered or uncovered by the handset's earpiece. The original Dialer2 app reads the raw value and compares it to a calibrated set point to determine on/off hook state. Reading the path
Code:
/sys/devices/virtual/input/input0/event0/device/raw_adc
with a FileReader will get you the current value. For my device, off hook (answered) is a value below 110. On hook (hung up) is a value above 110. For my testing I just polled this file every 250ms but you could attach a FileObserver to it or something.
jazzcandle said:
Has anyone considered working backwards with the version of Android running on the MC, rather than installing an entirely new version? So, instead of trying to get new firmware to work on the unit, why not work with whatever's on the device by default and pull out what you don't need?
Click to expand...
Click to collapse
This is actually what I am working on with a unit that I got.
The phone I have (from the build.prop file):
Code:
ro.build.version.release=4.2.3-phone-5068355-southern-userdebug
ro.product.model=Meraki MC 74
ro.product.brand=Meraki
ro.product.name=capri_me1
ro.product.device=capri_me1
ro.product.board=capri
Currently trying to work on getting ADB working from within the phone and not just within the Clockwork recovery that I got loaded on it.
Getting a pretty close stock experience on the MC74 is totally possible with some dedication and work. For reasons I cant get into, I am unable to provide the steps / files that it took to get where I am, but I have a functional MC74 with working handset & speakerphone. The only next thing I need to work on is getting the "IR" sensor to hangup in specific Dialer applications.
https://imgur.com/a/FFVq1sL
I am using Grandstream Softphone dialer.
drraccoon said:
Getting a pretty close stock experience on the MC74 is totally possible with some dedication and work. For reasons I cant get into, I am unable to provide the steps / files that it took to get where I am, but I have a functional MC74 with working handset & speakerphone. The only next thing I need to work on is getting the "IR" sensor to hangup in specific Dialer applications.
Click to expand...
Click to collapse
I was able to achieve the same, except GS dialer is not scaled correctly.
Not able to post link to image, as I don't have 10 messages.
So it is a/6aQYsz6 on imgur
Did not bother to fix it, as my intent is custom PJSIP dialer (someday
Headset sensor, led, mixer - figured out.
The only mystery is "mute" button and the red LED behind it.
sasha0413 said:
Hi all, I am new to the forums and I think that I need some help with a custom android project.
[Background]
I have bought a Meraki MC74, This phone is a VOIP office desk phone that has a nice 7 inch LCD screen that make for a ballin' custom intercom phone/general android device.
Cisco Meraki has dropped support for this phone, so even if I wanted to pay for a subscription, I couldn't. So custom android it is
[So what I know]
I know that the OEM OS is android 4.X.X with a custom Cisco Meraki dialer to do Meraki's cloud mumbojumbo. I was able to use ADB and Fastboot to flash ClockworkMod, and a custom version of Android 4.1.2 to get the device somewhat working. (it had lots of bugs and problems; but it was running android free of the Cisco Dialer!)
I was able to do this with the help of fellow xdadevelopers forum user "andrewmospak" (If you're reading this; I'm the dude from Ebay. And of course, thanks bro for the help so far!)
The storage is on a 4 GB Kingston EMMC.
[What I wanted for an end goal]
I wanted to have an interesting discontinued Meraki Desk phone that runs android and get all the functions of the phone working within android.
I also wanted to expand the storage from 4GB to 32GB. ( involving de-soldering existing EMMC and solder in the bigger EMMC.)
[What caused me to write this]
I would be fine if I wanted to stop there, but I wanted to try to install a GSI of android 9 in place of 4.1.2.
Again, this wouldn't be a big deal but I had to go and screw this up. I tried to resize some of the partitions (namely system to accommodate the bigger image of the android 9 GSI)but I accidentally completely killed the system,cache, and recovery partitions.
So, as one of the first steps of trouble shooting, I went to the hardest solution. The de-soldering of the EMMC.
I reached out to Andrewmospak again and asked for a full system emmc dump to try to flash his working file system to a spare 4GB EMMC to see an example of the file system of a working android EMMC. I received the image and flashed it to a spare Toshiba chip and soldered that to the phone, but I was unable to get the phone to boot into android right away, only able to load up fastboot.
Interestingly, I know that the EMMC is working because fastboot reports the S/N as the S/N of Andrewmospak's device and not the one written on my device.
[What I don't know]
Should some of the partitions on the EMMC not be recognized by Gparted in Debian? Like the User/System and others are partitioned ext4 while others are just not recognized.
Why when trying to flash partitions using Fastboot, wont fastboot recognise a recovery partition. It would just say that the partition just doesn't exist. same story with boot.
[What needs help]
I would like to know why fastboot wont see flashable volumes when using the EMMC dump flashed to another spare Toshiba EMMC, it is clearly there.
I would like to know how to reconstruct a volume to fix missing ones, and the number of partitions android needs to run.
Would I be able to flash an image of my working device to a 32gb emmc and just expand the system and user partitions into that extra space?
I will appreciate all help given to assist me and others that want a working device instead of a paperweight. ogChamp: :fingers-crossed:
Click to expand...
Click to collapse
Hey, I am interested but I don't have the device.
First of all:
I would be fine if I wanted to stop there, but I wanted to try to install a GSI of android 9 in place of 4.1.2.
Click to expand...
Click to collapse
You can install a GSI on a 4.1.2 based device, but you can't without creating a vendor partition, GSI is a part of the Project Treble released with Oreo. It requires a vendor partition to work. On 4.1.2, there's simply no device with a partition called vendor, so you can't flash a GSI.
But, if you have a fully working Android Pie tree, you can make a vendor partition yourself.
alex39wkd said:
I was able to achieve the same, except GS dialer is not scaled correctly.
Not able to post link to image, as I don't have 10 messages.
So it is a/6aQYsz6 on imgur
Did not bother to fix it, as my intent is custom PJSIP dialer (someday
Headset sensor, led, mixer - figured out.
The only mystery is "mute" button and the red LED behind it.
Click to expand...
Click to collapse
As you didn't mention that you couldn't share any information like the reply previous to yours, would it be possible for you to share what you used to get there?
As someone with only linux, networking and voip knowledge and that never played around with Android ROMs/ADB before, that would get me started as I can ATM only get to ADB.
Also, did you use the version of android already on the Phone or Flashed it with a new ROM?
Thank you!
jtthecanadian said:
As you didn't mention that you couldn't share any information like the reply previous to yours, would it be possible for you to share what you used to get there?
As someone with only linux, networking and voip knowledge and that never played around with Android ROMs/ADB before, that would get me started as I can ATM only get to ADB.
Also, did you use the version of android already on the Phone or Flashed it with a new ROM?
Thank you!
Click to expand...
Click to collapse
I have used "adb pull" (in recovery mode) to dump boot partition, just used path to it in /dev/...
Used android tools to decompress and unpack boot.
Changed ro.secure to 0 and something like "meraki usb debug" to 1
Repacked boot partition
Used adb to switch to fastboot
Flashed boot and boot2 with this image
Now it is accessable as normal Android phone, for whatever you might want to do with it.
Is anyone able to provide a working ROM for this device? I'm extremely confused about how to get this working. I would greatly appreciate any advice.