Factory Reset mtk device without any recovery system - General Questions and Answers

so i have a mtk device in which i mistakenly flashed a wrong custom recovery using mobile uncle tools. now i have no working recovery in this device & device wont even factory reset as it tries to reboot into recovery mode then fails to boot into corrupted recovery & again reboots into operating system without doing any reset.
so im here to know if there is any way to recover my built-in recovery system or atleast factory reset my device without using any recovery. i have tried using adb but faced the following error:
PS C:\adb> adb devices
List of devices attached
0123456789ABCDEF device
PS C:\adb> adb root
adbd cannot run as root in production builds
PS C:\adb> adb shell
[email protected]:/ $ wipe data
Wiping /data
Error opendir'ing /data 'Permission denied'
Done wiping /data
[email protected]:/ $

Khaled786 said:
so i have a mtk device in which i mistakenly flashed a wrong custom recovery using mobile uncle tools. now i have no working recovery in this device & device wont even factory reset as it tries to reboot into recovery mode then fails to boot into corrupted recovery & again reboots into operating system without doing any reset.
so im here to know if there is any way to recover my built-in recovery system or atleast factory reset my device without using any recovery. i have tried using adb but faced the following error:
PS C:\adb> adb devices
List of devices attached
0123456789ABCDEF device
PS C:\adb> adb root
adbd cannot run as root in production builds
PS C:\adb> adb shell
[email protected]:/ $ wipe data
Wiping /data
Error opendir'ing /data 'Permission denied'
Done wiping /data
[email protected]:/ $
Click to expand...
Click to collapse
You need to obtain a copy of your stock recovery and then flash that copy of stock recovery onto your device. If you can find a copy of your stock firmware, you can try extracting a copy of stock recovery from the firmware and use that copy to flash the device.
Sent from my SM-S767VL using Tapatalk

I have searched a lot and found one copy of my stock firmware (still not 100% sure about the rom) and it contained recovery.bin file (but I need recovery.img) image file to flash with mobile uncle or flashify.
So I used SP flashtool to flash only the recovery file into my device. But it showed some error (PMT has changed of this rom) and failed the flash. After searching for solution, people were telling me to erase my full device including boot & bios with SP flash tool then flash the new copy of my downloaded stock firmware. But I can't take the risk of erasing my device and bricking it (as I already told I have doubts about the downloaded rom)

Droidriven said:
You need to obtain a copy of your stock recovery and then flash that copy of stock recovery onto your device. If you can find a copy of your stock firmware, you can try extracting a copy of stock recovery from the firmware and use that copy to flash the device.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
what if the downloaded rom is also corrupted like the custom recovery i tried to flash........ im trying to avoid this kind of risky steps. i have heard mobile uncle tools flashes custom recovery temporarily & the stock recovery is still there somewhere which can be found using root explorer. so i was asking is there any way i can extract that stock recovery from system files and use it OR just any other way to factory reset my device using adb/fastboot

Khaled786 said:
what if the downloaded rom is also corrupted like the custom recovery i tried to flash........ im trying to avoid this kind of risky steps. i have heard mobile uncle tools flashes custom recovery temporarily & the stock recovery is still there somewhere which can be found using root explorer. so i was asking is there any way i can extract that stock recovery from system files and use it OR just any other way to factory reset my device using adb/fastboot
Click to expand...
Click to collapse
I told you what you needed to do, now, you just need to accept it and do it.
Sent from my SM-S767VL using Tapatalk

Related

Tiamat 1.1 -> Stock 3.1 = brick?

Had Tiamat xoom 1.1 + Tiamat Kernel. Trying to get back to stock
I have tried to flash the .img files several times. Boot, recovery and userdata all flash just fine. However, when ever I flash system I get the following error:
Failed to process command error (0x120000)
anyone have any ideas how to recover from this? I've tried changing usb ports as one thread for a very slightly similar issue stated. Didn't work.
UPDATED: managed to get on stock 3.1.. eventually. huge PITA but it's done.
holtenc said:
Had Tiamat xoom 1.1 + Tiamat Kernel. Trying to get back to stock
I have tried to flash the .img files several times. Boot, recovery and userdata all flash just fine. However, when ever I flash system I get the following error:
Failed to process command error (0x120000)
anyone have any ideas how to recover from this? I've tried changing usb ports as one thread for a very slightly similar issue stated. Didn't work.
UPDATED: managed to get on stock 3.1.. eventually. huge PITA but it's done.
Click to expand...
Click to collapse
I am running into a similar issue. Coming from Tiamet 2.2 + Tiamet kernel I am unable to flash back to system. I can flash boot, recovery, and userdata images, but the system image gives the same error (Failed to process command error (0x120000)).
Could you please share how you made it back to stock (if you can remember, I know it's been a few months
Recover from Failed to process command error (0x120000)
I have tried to flash the .img files several times. Boot, recovery and userdata all flash just fine. However, when ever I flash system I get the following error:
Failed to process command error (0x120000)
Alrighty, it took me 2 days but I finally figured out how to get past this dreaded error.
My Fastboot was unable to flash system.img (but successfully flashed boot, recovery, and userdata) to my rooted, unlocked US Xoom Wi-Fi Only running 3.1, 3.2, and/or 3.21 (yes I tried from all 3 versions using various update.zip methods).
I was attempting to revert to stock using the methods described in multiple threads on XDA, but couldn't get past the 0x120000 error when trying to flash the system.img.
Disclaimer:
This was done on an unlocked, rooted US Wi-Fi Only Xoom running HC 3.1. While this fixed my issue, I take no responsibility if the method does not work on 3G/4G versions, non-US versions, or just plain works differently between different devices. Using dd to flash images is not the safest route, but for me it was the only route.
Prerequisites:
Have adb access (preferably through installing the Android SDK)
Have CWM Recovery installed on Xoom
Steps:
Download the stock HWI69 images from bwcorvus' sticky http://forum.xda-developers.com/showthread.php?t=1049485
Extract the image files into your platform-tools directory in the android-sdk
Reboot into recovery
Code:
adb push boot.img /sdcard/
adb push system.img /sdcard/
adb push recovery.img /sdcard/
adb push userdata.img /sdcard/
adb shell
su (if it doesn't bring you into root # prompt)
busybox dd if=/sdcard/boot.img of=/dev/block/mmcblk1p7
busybox dd if=/sdcard/system.img of=/dev/block/mmcblk1p8
exit
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
Follow lock instructions on device

[Q] Can't boot after CM9[SOLVED]

Hey XDA
I tried to install CM9 today, it fail...
I have unlocked my phone using htcdev.com.
Then I followed this:
If you unlocked your phone via htcdev.com, you must flash the included
boot.img after flashing the ROM in recovery:
- Boot into fastboot, either by:
- Turning phone on whilse holding VOLUME DOWN, or
- adb reboot bootloader, or
- using an option in your recovery (eg. Reboot Bootloader)
- Connect your phone to your PC and copy the boot.img from the ROM .zip
to the same place as fastboot.exe and issue the following command:
- fastboot flash boot boot.img
Failing to follow these instructions on a htcdev.com unlocked device will
cause the ROM to fail to boot.
And now it just stands with a mobile and a ret warning sign. I can get in bootloader, but that's all. I have the CM9.zip on the sdcard but I forgot to run it before I did the above mentioned. I have tried to reset the mobile from bootloader nothing helps
Pleas help me what should I do?
So what is your problem exactly ? Do you have a custom recovery like 4EXT ? It's needed in order to apply the CM9.zip.
None
No i have not installed any recovery app. I cant start my mobile
Naaler said:
Hey XDA
I tried to install CM9 today, it fail...
I have unlocked my phone using htcdev.com.
Then I followed this:
If you unlocked your phone via htcdev.com, you must flash the included
boot.img after flashing the ROM in recovery:
- Boot into fastboot, either by:
- Turning phone on whilse holding VOLUME DOWN, or
- adb reboot bootloader, or
- using an option in your recovery (eg. Reboot Bootloader)
- Connect your phone to your PC and copy the boot.img from the ROM .zip
to the same place as fastboot.exe and issue the following command:
- fastboot flash boot boot.img
Failing to follow these instructions on a htcdev.com unlocked device will
cause the ROM to fail to boot.
And now it just stands with a mobile and a ret warning sign. I can get in bootloader, but that's all. I have the CM9.zip on the sdcard but I forgot to run it before I did the above mentioned. I have tried to reset the mobile from bootloader nothing helps
Pleas help me what should I do?
Click to expand...
Click to collapse
1.install a custom recovery like 4ext or cwm
(2. Backup current system) this time you don't have to do this since you don't have a working system at the moment.
3. Full wipe (data, system, boot, caches... Not sd card) from recovery
4. Flash ROM zip from recovery
5.flash boot.img via adb
6.reboot
7.done
Sent by my fingers to your head.
How?
The recovery app Is it ón the computer or the Mobile?
ón Mobile how do i get it ón?
1.install a custom recovery like 4ext or cwm
(2. Backup current system) this time you don't have to do this since you don't have a working system at the moment.
3. Full wipe (data, system, boot, caches... Not sd card) from recovery
4. Flash ROM zip from recovery
5.flash boot.img via adb
6.reboot
7.done
Click to expand...
Click to collapse
That's it.
here is 4ext 2.2.7: http://dl.dropbox.com/u/45382761/PG88IMG_4EXTrecovery_2.2.7_RC5_Desire_S.zip
Extract the "recovery.img" and flash it using fastboot:
fastboot flash recovery recovery.img
Thanks
Thanks it works now
Naaler said:
The recovery app Is it ón the computer or the Mobile?
ón Mobile how do i get it ón?
Click to expand...
Click to collapse
I'm assuming you know how to boot into fastboot and use fastboot and adb commands. If not, just click on the link in my signature under Helpful links.
Once you're done, just put the attached file in your adb folder, then boot into fastboot and issue the command ;
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
You will now have the custom 4EXT Recovery. From there, just follow the steps you outlined in your first post, and you should be up and running.
Cheers.
EDIT: I see you already got it working while I was composing my post. Congrats!
@op could you please update the thread title to something like [solved]
Sent by my fingers to your head.

Accidentally delete everything using TWRP in "wipe"

Hey,
first of all i KNOW there is a subject with nearly the exact same topic, and i followed the directions but somethng doesn't work.
I still have TWRP on the phone, and when im in bootloader mode and run "fastboot devices" i see the result.
but i can't seem to ADB push or anything else (maybe im missing some commands?)
so i used the NRT root kit and i use the "fastboot flash" function and install the .img file - the software says my device is identified and it installs the system.img file (found on the "image-hammerhead-mra58k" zip), but then the device boots to TWRP and still can't boot to the system itself.
help please!
Sideload a factory rom and u will be fine. U can do it in the advanced portion of TWRP, but u need a pc, or ur hit
Sent from my Nexus 6 using Tapatalk
Sounds to me like you're using adb commands in fastboot.
Boot into bootloader (not recovery)
Type fastboot devices
It should return showing your device
Then you need to make sure you have stock img's downloaded and completely extracted so you have all the img files in the folder you're running fastboot from (rename the radio to simply radio.img)
Then type
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash radio radio.img
Then boot back into recovery and wipe cache and dvalik for just in case fun
Then reboot system and wait
Sent from my Xperia z5 by Tapatalk
Thank you very very much guys!
that worked! WOOHOO!!
Good good!
Sent from my Xperia z5 by Tapatalk

Need help after installing a ROM

Hi,
today I have tried to install a custom rom and after a lot of troubles.
I have done a total wipe (cache, dalvik cache, system, data and internal storage) and I have tried to flash this rom, but always failing.
I typed in cmd:
fastboot flash system Lant.zip
now I'm stuck in bootloop and I can't turn off my phone -.- (pressing power button the device is rebooted, not turned off)
I don't know what you tried to install, but you can't install zip files using fastboot. Reboot to recovery and install it using ADB sideload. Or adb push it to the device and install it using "Install".
_that said:
I don't know what you tried to install, but you can't install zip files using fastboot. Reboot to recovery and install it using ADB sideload. Or adb push it to the device and install it using "Install".
Click to expand...
Click to collapse
Thanks,
Isn't there a way to push a zip through fastboot? My phone isn't seen as ADB device, only as fastboot one.
stefano0798 said:
Thanks,
Isn't there a way to push a zip through fastboot? My phone isn't seen as ADB device, only as fastboot one.
Click to expand...
Click to collapse
ADB works while in TWRP. If not, you may need to install some drivers (or use Linux).
stefano0798 said:
Hi,
today I have tried to install a custom rom and after a lot of troubles.
I have done a total wipe (cache, dalvik cache, system, data and internal storage) and I have tried to flash this rom, but always failing.
I typed in cmd:
fastboot flash system Lant.zip
now I'm stuck in bootloop and I can't turn off my phone -.- (pressing power button the device is rebooted, not turned off)
Click to expand...
Click to collapse
If your bootloader is unlocked then just enter these commands in fastboot:
fastboot erase system
fastboot erase userdata
fastboot erase cache
Then install a custom recovery using:
fastboot flash recovery recovery_name.zip
And then finally install the custom ROM in the recovery.
stefano0798 said:
Hi,
today I have tried to install a custom rom and after a lot of troubles.
I have done a total wipe (cache, dalvik cache, system, data and internal storage) and I have tried to flash this rom, but always failing.
I typed in cmd:
fastboot flash system Lant.zip
now I'm stuck in bootloop and I can't turn off my phone -.- (pressing power button the device is rebooted, not turned off)
Click to expand...
Click to collapse
install motorola drivers on pc and boot in twrp then plug the phone to pc and copy the rom to phone.
Paradox♀ said:
If your bootloader is unlocked then just enter these commands in fastboot:
fastboot erase system
fastboot erase userdata
fastboot erase cache
Then install a custom recovery using:
fastboot flash recovery recovery_name.zip
And then finally install the custom ROM in the recovery.
Click to expand...
Click to collapse
Thanks a lot,
now how should I proceed? I have the rom in a .zip in my PC, but the command:
adb push rom.zip /data
says: "error: device '(null)' not found.
It also says "unable to mount /data" and "unable to mount /system". Any ideas?
Ok, i solved the driver problem, but I didn't found any solution about the 'mount' problem. It says my internal storage is 0 MBs and it don't let me mount any partition (Data-Cache-System).
Any help?
stefano0798 said:
Ok, i solved the driver problem, but I didn't found any solution about the 'mount' problem. It says my internal storage is 0 MBs and it don't let me mount any partition (Data-Cache-System).
Any help?
Click to expand...
Click to collapse
Try formatting these partitions in TWRP (Wipe -> Advanced ....).
stefano0798 said:
Ok, i solved the driver problem, but I didn't found any solution about the 'mount' problem. It says my internal storage is 0 MBs and it don't let me mount any partition (Data-Cache-System).
Any help?
Click to expand...
Click to collapse
While in the recovery just wipe all the partitions and reboot to the recovery that should solve your mount problem and if you have installed TWRP as the custom recovery then it would initiate the MTP protocol from your device so you can transfer the ROM from your PC directly as you transfer your media. :good:
Thank you very much! It works perfectly

I kinda wiped away my phone's OS and I'm not sure how to fix it, help?

Hi, so I was messing with the recovery mode on my phone when trying to install a new rom and somehow ended up wiping the os. I actually managed to install the rom, but I don't know what possessed me to start tapping random buttons and that's how it got messed up. Now my phone is stuck in fastboot mode and I don't know how to get it back to normal. Any advice on how would be a great help, thanks in advance.
sara_ said:
Hi, so I was messing with the recovery mode on my phone when trying to install a new rom and somehow ended up wiping the os. I actually managed to install the rom, but I don't know what possessed me to start tapping random buttons and that's how it got messed up. Now my phone is stuck in fastboot mode and I don't know how to get it back to normal. Any advice on how would be a great help, thanks in advance.
Click to expand...
Click to collapse
Fastboot flash recovery, then try using adb commands to boot into recovery and flash your ROM again. Or, try extracting the system.img from your ROM, place the system.img(rename the file to system.img if it is labeled by another name) in your fastboot folder on PC, open a terminal and flash the system.img via fastboot using the following command:
fastboot flash system system.img
Droidriven said:
Fastboot flash recovery, then try using adb commands to booting recovery and flash your ROM again. Or, try extracting the system.img from your ROM, place the system.img(rename the file to system.img if it is labeled by another name) in your fastboot folder on PC, open a terminal and flash the system.img via fastboot using the following command:
fastboot flash system system.img
Click to expand...
Click to collapse
Thank you so much. I was able to install the ROM via flash recovery, it was pretty easy. THANKS A LOT!!

Categories

Resources