I've MeLE A200 HTPC (single core A10S SoC, FW Android 4.0.4 v1.2b rooted, Board HMC-G41A03WL). Recently after installing a small app, something went wrong, the box Internal Storage changed from 10% full to 0.0B, meaning its not mounted anymore on device reboot. I've no access to previously installed packages, and can't install any new package that requires access to Internal Storage ( Data partition) or root access. I tried soft recovery from Settings and Hard recovery by pressing the device button, but they didn't fix the issue.
I earlier installed CWM ROM Manager, but was unable to find Recovery image for this device. Wanted to re-install original firmware, but official links are dead. Mele Support never answers any emails, and they block registration emails on the company forum, so no way to ask a question on the forum. They posted an updated firmware v1.3 for "A200 upgraded version" device on the forum, but that device hardware has 1GB RAM, and mine only 512MB, and there may be other differences. So I'm not sure, it will boot, and if it doesn't I'll get a brick.
I installed Terminal package, and can access the box partitions from PC using ADB via Wi-Fi, since USB Recovery option is not showing in the device Settings, and Mele provides no USB Windows driver. I can see that Data, Cache, and probably some other partitions are not mounted. I mounted them OK manually, but lost Wi-Fi access after that, probably because the device lost access to Data folder on root it was using instead of Data partition on NAND.
This picture has proper links, since I can't post them here so far:
{
"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"
}
My questions are:
1. Can anyone point to a link to A200/A210 original firmware? I need:
A200_Mele_HTPC_20130117_V1.3.1
A200 Mele_HTPC_ Home _20121220_V1.2
2. What are my chances to get a brick, if I flash the above mentioned v1.3 for "A200 upgraded version" device? Can I unpack & modify that firmware to fit my device - how?
A200升级版_A10_SDK1.6_V1.3_20140715.img
3. If I flash that FW to the device, will it erase original Recovery partition? If Yes, and the device can't boot after flash, could I recover it by pressing Hard Recovery button? Does it mean, Hard Recovery partition is stored separately in NAND, and never erased when a new FW is flashed from SD Card?
4. May be I can change some automount rules via ADB? So far, I found that /etc/vold.fstab has no automount rules for any system partitions, only for SD Card and USB partitions. So what file contains automount rules for Data and Cache?
5. What else can lead to Data not being mounted, what else can I check or do to fix the device? I can post some debug and dmesg logs saved by the system if needed. How I can fully backup or recover the device from full backup in this situation?
Update: the only resolution I found was reinstalling factory firmware procured from Mele upon request.
Does your device have a custom recover? Flash a new rom
Related
Hello,
So im not a complete novice with rooting and such, have done it on several phones with and without issues and still fixed them.
But when it comes to unbranded stuff like this stereo im a bit lost and confused.
Heres some info on the stereo in question
{
"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"
}
Pretty much a generic chinese stereo found on ebay.
Apparent specs were advertised as -
Operating System: Android 4.4:
ARM Cortex A7 Dual Core,
1.0GHZ CPU ,1
GB DDR3 RAM,
8GB NAND Flash
This is not entirely true though and this is where my problems come in.
Booting into recovery doesn't actually allow any selections and it boots into recovery for about 3 seconds and then reboots.
The only info it shows in these 3 seconds are -
wing_k70-eng 4.4 KRT16S 20141208 (i assume this is a custom android version)
volume up/down to move highlight; enter button to select.
Reboot system now
apply update from ADB
wipe data factory reset.
(now i cant even try this because it reboots itself before you can try and select anything, also whats the up/down volume buttons and enter button on a stereo)
Boots with an allwinner logo.
Now thats the info on the stereo itself. The problem i have is with the storage. Again i dont know a ton about NAND. But the advertised specs stated 8gb.
When you look in storage in the settings it shows -
Internal storage 0.98gb (this is where apps are installed, or would be is there was space)
Internal storage 4.50gb
This shows in the settings but is not accessible, you can format it but still cant access it.
Tried opening in file browsers but it says its not mounted. No option to mount or unmount it in the storage settings.
SD card port works fine. I have a 16gb card in it but i cant install any apps onto it.
Some apps such as Torque ODB require profiles to be saved into storage and also need access to storage.
This is not possible as the internal storage is not accessible, i get a message of -
Waiting for memory cars / storage to become accessible.
This times out after a while because the storage is not accessible.
So im not here for some help.
What are my options?
Would rooting the device maybe fix the issue? if so how woudl i go about rooting this?
Is there a way without root to change the settings of apps to install into SD card, i tried the regular options in settings and it wont let me move or save apps to SD.
Any other way i can gain access to the 4.5gb?
Hopefully somone can give me some advice.
Hello all,
I've been flashing rooms on the phone for quite a while now, but last weekend i flashed a new CM14.1 ROM onto the phone with the new GAPPS with it. Before doing this i ofcourse wiped the needed partitions in order for them to work right. However, since i've done this and flashed the new software, the phone doenst have access to the internal storage while being booted into the system (OS)..
When i boot into TWRP, i have full access to the internal storage and i'm able to create new folders and copy/cut/paste files onto it. Down here, you see i've created a new folder using the PC while its booted in TWRP.
{
"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"
}
When i try to do this while its booted in CM14.1 (android 7.1.1, but i think any ROM i'd flash) this happens:
To translate this from Dutch to English: "The new folder couldn't be created on this location. The device isn't responding anymore or the connection has been lost".
When i browse to the internal storage through the OS itself, it does show up. However, i dont have any access to create new folders or files or to change them:
Also when i try to take a picutre using the camera, it says this:
Even when i enable developer options and giving root to both apps and adb, it still doesnt have the required access to perform these actions:
Also going to the gallery, it says that there is no storage available:
I also looked up some info about the partition, which might be useful for those who have some knowledge about this.. This is what i found using the app "Diskinfo":
And i also used the commands ls -l to show the permissions of the /data/media/(and)0/ to see what rights are giving out:
As you see here, the app itself didnt have access to go to the storage location untill i gave it "su" rights. Does this mean the entire OS doesnt have access to this location because it simply doesnt have the right permissions for it?
If anyone has any suggestions or wants to help me figure out what is wrong, please feel free to reply here or through a PM. It would be highly appreciated.
///Edit
After searching around on the web i came across a post where someone said that running the TWRP advanced option "Fix Context" would reset all permissions that you normally dont do yourself. So i've ran that, it ran for like 0.5 second before being finished. After rebooting the phone into the system (OS/Android) all problems were solved and permissions were set right.
Therefore my problem is resolved now, and this topic could be closed ^^
Dear XDA Developers Users,
I have two STK Hero X mobiles. One of them is rooted and working (1), the second one is soft-bricked (2). I´m looking for a way how to unbrick the second one, maybe using the first one.
Both mobiles: No official or custom ROM available, no custom recovery available, rooted using KingRoot, Android 5.1, MTK6735P chipset.
The working one (1): Can use ADB, Fastboot, Dev options, stock recovery
The bricked one (2): Can only get to recovery, fastboot. Bootloader locked. Freezes at the STK logo during booting. I had removed a few system apps using System App Remover: AVG antivirus or Chrome. In recovery, there is a root integrity check. A few files are modified (2; because of root, I suppose, including /system/bin/app_process64), missing (7; antivirus), and new (13 of them). It´s the Android System Recovery <3e> which looks like that (not a my photo):
{
"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"
}
What I´ve tried (2)
- Factory reset using recovery (/data, /cache). Still feezes at the logo during booting (two hours).
- Create a ZIPme recovery from the working one (1) with system apps. In the recovery (2), the ZIP is loaded via SD card and suddenly interrupted with no reason. (Battery charged.) Tried with two different ZIPme recoveries.
- Create a FlashFire ROM brackup (1). Can´t because of the KingRoot. Supersume Pro didn´t help. Source: https://www.xda-developers.com/chainfires-flashfire-can-now-create-fastboot-flashable-backups/
- Create a complete ADB backup (1), and restore it (2). Well, wasn´t possible because the ADB in recovery (2) doesn´t support adb restore. Source: https://forum.xda-developers.com/galaxy-nexus/general/guide-phone-backup-unlock-root-t1420351¨
- Unlock the bootloader (1). I can´t boot the OS and allow OEM via Dev tools. Unlocking with Fastboot fails. Source: http://www.theandroidsoul.com/unlock-bootloader-via-fastboot-android/
- Port a TWRP recovery and then simply use a recovery from (1). Well, I can´t unlock the bootloader. Source: http://forum.xda-developers.com/showthread.php?t=2798257
- Create a complete nandroid backup (1). I can´t restore it using the stock recovery. Source: https://www.informationlord.com/create-nandroid-backup-without-cwmcustom-recovery/
I will be grateful for any idea how to make my mobile (2) boot into Android. Maybe using the files from the working one (1), restoring the partitions? In the recovery (2), there is a backup user data option. The mobile has a 16GB storage, and after a factory reset, the backup user data needs around 12GB of free space on SD card. Since there is no user data, is it possible it includes the system files somehow?
{
"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"
}
OrangeFox Recovery UNOFFICIAL
By @iamshubh69
Fw: Realme UI 2.0
Download: Click here
Changelog:
- build for Realme ui 2.0
Bugs:
- For working of OTG, plug it before booting to recovery
- Decryption in a12
Notes:
Only for Realme UI 2.0 Firmware
Guide to flash:
1. Unlock bootloader using the Realme UI 2.0 Deeptest tool
2. Enable usb debugging
3. adb reboot bootloader
4.fastboot --disable-verification flash vbmeta vbmeta.img (vbmeta 4KB)
5. fastboot flash recovery recovery.img
Credits:
Thanks to @sarthakroy2002 for trees and help
What do you mean by "Decryption in a12"? Like the OS fails to read an encrypted partition, resulting in a brick if we encrypt our drive? Or rather it refuse to decrypt the drive in case you don't want to be encrypted anymore? Or something else? Wasn't it already denied widely to unencrypt an Android installation from when it has been done?
The phone would not the able to perform any OTG anymore if we don't plug it to the computer before the booting preceding the installation of this recovery? Or an OTG function into this recovery will not work for the session if not plugged before booting? Or something else?
Can you add a part who warn about potential data loss? And redirect to tutorials about how to backup the most possible of the phone (app data and settings, android data and settings, kernel, RAM/ROM, phone personal identification files, anything that could help in case of brick and that could help restoring as most as possible thing like before any manipulation)?
dd
pingopower said:
What do you mean by "Decryption in a12"? Like the OS fails to read an encrypted partition, resulting in a brick if we encrypt our drive? Or rather it refuse to decrypt the drive in case you don't want to be encrypted anymore? Or something else? Wasn't it already denied widely to unencrypt an Android installation from when it has been done?
The phone would not the able to perform any OTG anymore if we don't plug it to the computer before the booting preceding the installation of this recovery? Or an OTG function into this recovery will not work for the session if not plugged before booting? Or something else?
Can you add a part who warn about potential data loss? And redirect to tutorials about how to backup the most possible of the phone (app data and settings, android data and settings, kernel, RAM/ROM, phone personal identification files, anything that could help in case of brick and that could help restoring as most as possible thing like before any manipulation)?
Click to expand...
Click to collapse
dude can you just email me on [email protected] I am tired of reading this long threads
iamshubh69 said:
dd
dude can you just email me on [email protected] I am tired of reading this long threads
Click to expand...
Click to collapse
Sure thing, but I think people maybe have those questions too. I don't ask them just for me
Bro link not working
Hi!
I tried to install this rom to this device. I put it into fastboot mode, booted twrp from there, copied the rom zip to the root, and installed without problems. Then I wiped Dalvik and tried to restart the phone, only to boot into twrp again (twrp was already installed I think, this version: 3.7.0_12-RedmiK40Pro+_v6.7_A13). The original system I think was the factory 13.03 Android.
Now the folders on the phone seem different in the twrp browser, and I cannot seem to locate the zip file of the rom to reinstall. Internal storage shows size to be 0M. Maybe this was the mistake, but in an attempt to fix things, I changed the Slot to slot B, which was successful, but only booted into fastboot. Then, when I tried switching back to Slot A again, it gave errors for not being able to mount certain partitions, as seen in this image:
{
"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 then tried to copy the rom to a pendrive and install it from there, but it showed a similar error. When connecting the device to the computer, it shows up, but I cannot open it in a file explorer. Unfortunately I did not make any backups beforehand. Do you think there is a chance of bringing this device back to life again? It was given to me with instructions, because I'm a "computer person" and I thought it would be an easy process as I have done this my phones many times without problem. What could be the issue? If you need me to include any logs, or photos of the errors, let me know. I'm really worried that I might have bricked this device. Thank you for your help!
gaspargergo said:
Hi!
I tried to install this rom to this device. I put it into fastboot mode, booted twrp from there, copied the rom zip to the root, and installed without problems. Then I wiped Dalvik and tried to restart the phone, only to boot into twrp again (twrp was already installed I think, this version: 3.7.0_12-RedmiK40Pro+_v6.7_A13). The original system I think was the factory 13.03 Android.
Now the folders on the phone seem different in the twrp browser, and I cannot seem to locate the zip file of the rom to reinstall. Internal storage shows size to be 0M. Maybe this was the mistake, but in an attempt to fix things, I changed the Slot to slot B, which was successful, but only booted into fastboot. Then, when I tried switching back to Slot A again, it gave errors for not being able to mount certain partitions, as seen in this image:
View attachment 5810281
I then tried to copy the rom to a pendrive and install it from there, but it showed a similar error. When connecting the device to the computer, it shows up, but I cannot open it in a file explorer. Unfortunately I did not make any backups beforehand. Do you think there is a chance of bringing this device back to life again? It was given to me with instructions, because I'm a "computer person" and I thought it would be an easy process as I have done this my phones many times without problem. What could be the issue? If you need me to include any logs, or photos of the errors, let me know. I'm really worried that I might have bricked this device. Thank you for your help!
Click to expand...
Click to collapse
how about flash over mi flash, stock rom