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?
Related
hi i managed to update my tab to the latest firmware 4.0.4 . Previously it was already rooted and TWRP installed. I was thinking of rooting and backing up this build so from romtoolbox i boot into recovery mode (thinking that i will be seeing TWRP) But when boot i was shown the folllowing picture
{
"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"
}
since all of my buttons are not working (hence the reason installing TWRP ) i was ok fine lets reboot it via adb. therefore i run adb reboot and yet it still boots back to the same screen . Thinking i need to reverting all of the changes via odin i tried reboot download also does not work. reboot-bootloader also does not work. apprently i am stuck at this screen.
Right now i only have access to adb and is there any way i can recover from this?
many thanks again
I'm assuming you were running some kind of custom rom with TWRP as your recovery before going to stock ICS. Essentially, flashing stock ICS overwrote the old TWRP.
To fix it, flash in TWRP again (its somewhere in the development section) via Odin.
EDIT: If you can't access download mode... Try push the TWRP .tar file via ADB
Sent from my GT-P7510
Soryuu said:
I'm assuming you were running some kind of custom rom with TWRP as your recovery before going to stock ICS. Essentially, flashing stock ICS overwrote the old TWRP.
To fix it, flash in TWRP again (its somewhere in the development section) via Odin.
EDIT: If you can't access download mode... Try push the TWRP .tar file via ADB
Sent from my GT-P7510
Click to expand...
Click to collapse
the thing is i only root and installed twrp for the sake of backing up since my daughter loves to install application. I've read about pushing / Installing application but that would requires root right? this is my command console like
Right now is there a way to force it to boot into download because thats the only way i see i can fix it (without using physical buttons)
Again many thanks for replying.
{
"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"
}
ClockworkMod recovery is a special boot mode by Koushik Dutta that gives access to administrative functions, such as installing the base firmware (ROM), making backups, and performing a 'factory reset'. .
This Recovery have this
Features:
install zip from sdcard or sideload into system1 or system2
backup system1 and system2 individual or together into one package
much choices of where you want to restore backups to
mount and format system1 or system2
fix permissions on system1 or system2
set bootmode to system1 or system2
automatically checks for install-recovery.sh on both systems and asks you if you want to delete them
TrueDualBoot
TrueDualBoot notes:
Enabling or disabling TDB will completely wipe your data-partition. Once enabled your data partition will be VIRTUALLY split which means that both systems together can use the full space of the data-partition.
There are some things which will break TDB:
everything which removes CWM(like Xiaomi Updater App's live install)
ROM's which don't support mount_ext4.sh (I did not see any ROM without support yet)
Recovery CWM --->http://d-h.st/zAe
Recovery Stock ---> http://d-h.st/czl
Download recovery-signed-***.zip
Copy the file in the root directory of your sdcard
Use updater installation from settings/info
This work will be impossible without previous work and actual help of @m1cha
Github: https://github.com/M1cha/android_bootable_recovery/tree/cm-10.1
Hello, is this recovery for Tegra or for Snapdragon MI3?
Pepe.II said:
Hello, is this recovery for Tegra or for Snapdragon MI3?
Click to expand...
Click to collapse
Snapdragon
Well, a Tegra version would be nice
Thank you for the Snap one
I have problems when wiping cache and installing ROMs... It takes a very long time to do it.
magarto said:
I have problems when wiping cache and installing ROMs... It takes a very long time to do it.
Click to expand...
Click to collapse
Download any rayglobe rom on miui.it. I use a different rom script to flash to avoid this problem
acer73 said:
Download any rayglobe rom on miui.it. I use a different rom script to flash to avoid this problem
Click to expand...
Click to collapse
I don't understand. If I download a rom what could it help me? I need a CWM recovery for the Mi 3W without that flashing delay.
Thanks mate
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
This phone is my brother's. He said he just downloaded a system update, I think it is OTA. And when update starts (from the stock recovery? not sure) It stucks at 50% progress bar, and it reboots. And update starts again, and reboots again. It won't boot even after removing battery, putting battery back on and turning the phone on, it persistently go back to loop update system. Should I flash it with a stock ROM? which one? The build no. I think is 1.0020? Can I flash the 1.050 one? Here is a pic of what's happening in a loop.
{
"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"
}
Follow this guide to reboot into recovery
http://www.hardreset.info/devices/acer/acer-liquid-z630/recovery-mode/
After entering recovery , try factory resetting your device.
This will reset all data.
If the above method didnt work , only option is to flash a Rom manually using SP Flash Tool
Stock Rom
http://vache-android.com/hubicAcer/Z630/OS Images/Acer_AV0L0_T03_1.020.00_EMEA_GEN1.zip
Hello there. Please take a look at this guide by Shreps.
Download a compatible custom recovery (CWM or TWRP) for your device. Also download the firmware (ROM) for your device (list by Shreps). Please refer to the guide (there should be one). You would need to (a) Install necessary drivers, and (b) ADB and Fastboot interface (try this)
Copy the custom recovery image into the root folder of your ADB and Fastboot program. Copy the firmware to your device (via external sdcard since you cant copy directly into the internal sdcard).
Go to recovery via (a) volume up + power buttons, or if device accessible via ADB, (b) adb reboot recovery
In the recovery options, choose 'fastboot' (or simply, via adb: adb reboot bootloader)
Go to your terminal/cmd: fastboot devices - and see if your device is recognized
Then: fastboot boot "recovery.img" (replace "recovery" with the name of the recovery image)
In the recovery, navigate and select "Install" and select the firmware on the external sdcard. (wiki)
If you cant install via fastboot (bootloader must be unlocked first before using fastboot), then flash the rom via SP Flash tool (refer to the guide)
{
"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"
}
This is how I rooted my KM8P, using help and tools made by people far more awesome than me. Probably works for other RAM/ROM size variants too and possibly for Android 6 if you can get the TWRP for it.
1. Copy TWRP.zip and Magisk.zip file to SD Card or USB key. The Android recovery can read extFAT but TWRP cannot. FAT32 works for both.
2. Boot to Android recovery - hold reset and power on until logo appears Reset hole is at the front on the top face where the "KM8 P" writing is.
3. Apply update, from external.
4. "Install" TWRP (attached, for Android 7) - It will just load, not actually install. Optionally backup your ROM now or have a recovery zip on hand.
5. Install magisk from TWRP - I used 15.3 (attached) but feel free to try a newer one.
5a. I could not update Magisk via the manager so I flashed 17.1 via TWRP. (attached)
6. Reboot
7. Install BusyBox (Stericson)
8. Open Magisk Manager - Check for update
9. Donate a couple of bucks to topjohnwu for Magisk: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
This worked for my T95Z Plus with a few hiccups. I had to wire up the UART.
Since updating to 7.1 it won't boot to recovery from the reset button anymore. I had to use UART to get into the bootloader console (hold space while plugging in power) and execute "run recovery_from_flash". It refuses to boot recovery images directly from external media anymore, but by going into recovery this way I was able to execute TWRP (which starts up in Russian, but can be changed) and make a backup.
Next, installing Magisk ended up being a chore. I had to use the "create patched image" method. For whatever reason it refused to let me copy files to my USB stick, so I ended up having to split the patched image into chunks and email them to myself... anyway, TWRP was able to flash the image.
The final complication is that Magisk could only install to the recovery partition (no ramdisk) which means it's only active when booting in recovery mode. I was able to make this the default mode from the bootloader console by executing "env set bootcmd run recovery_from_flash" and "saveenv". After that, it boots up normally with Magisk enabled. I guess I don't have an actual recovery mode now, but I can use UART or USB Burn Tool to recover from bricking, so no big deal.
(Also Android itself was in Vietnamese but again this can be changed)
Thanks for the files and guide!