Database Users

trouble entering recovery mode

hi,
one of our members in and-roid.ir is facing a strange problem... his phone is s-off and recovery v.3 was flashed.
he was installing a rom and suddenly there was an error in the installation... he tried to enter recovery and restore a back up but when trying to enter recovery from bootloader instead of entering recovery mode it will enter fastboot mode...
he flashed recovery again but no luck...
suddenly when usb was plugged he entered recovery mode... he tried again with usb unplugged and couldn't enter recovery mode...
so after entering recovery mode with usb plugged memory card won't mount... he tried to manually mount it and still no luck...
any ideas what's the problem?and how to trouble shoot it?

any clues at all?

Reflash the misc partition. (you can see how to do this in the root HBOOT 1.00 thread) Or you can boot into recovery...
Go to fastboot
put the custom-recovery.img in your android-sdk/tools folder
fastboot boot (drag and drop recovery.img into cmd or terminal) press enter

so i have to do following commands? correct?
Code:
adb shell
su
...you should have root privileges now (showing #). Next thing is backing up misc partition and replacing it with one from hack4legend-v5.zip. Extract this zip somewhere and fire another command promt there. Now you should upload flash_image binary and misc1-2.img:
Code:
adb push flash_image /data/local/
adb push misc1-2.img /data/local/
...switch back to 1st command prompt and change permission of flash_image_binary:
Code:
chmod 755 /data/local/flash_image
...and backup your current misc partition:
Code:
cat /dev/mtd/mtd0 > /sdcard/misc_backup.img
Now flash misc1-2.img:
Code:
/data/local/flash_image misc /data/local/misc1-2.img
exit
Click to expand...
Click to collapse

I believe so yes

[SOLVED] Recover from Failed to process command error (0x120000)

Description of the Error:
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)
Solution:
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 and fastboot setup (e.g., 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

Plugging into another USB slot solved mine
I had the same problem. 1200003 error.
Plugging the tablet without an extension cable directly in on of the back slots solved the prob.

Brick/ stuck?

I think I accidentally bricked my kf when I was attempting to root it, wheni turn it on it gets stuck on the flame triangle then freezes after a few minues, I can also boot into recover but I can't seem to mount the usb storage into the computer, it doesn't show anything on my cmputer or anythin so I can't copy the rom over to the storage inside. Is there any way to push a file throug fastboot? Sorry I'm a newb at all this

go into twrp and tap mount - mount sdcard - it will show up on your computer
if not check your drivers

I believe you can adb push files to your device if it booted into recovery (check your device is recognized by adb devices; if not it might be a driver issue), however TWRP also can mount your "sdcard" and have it show up on your PC like any other mounted device; look for the "mount" button.
Good luck!

So its a possibility I can access it through adb while its in recovery? Ill try as soon as I get home
Sent from my SPH-D700 using XDA App

Open adb shell and type
idme bootmode 4000
reboot
I assume that you are able to communicate to your KF.
Regards
Sent from my GT-S5830 using XDA App

i can't seem to access it through adb but i can through fastboot

well i made little progress
i took a random custom rom > took the system file > then packed into a zip file > flash with "fastboot flash system ect."
but now it goes through a boot loop into recovery (boots into the kindo logo for about 1/2 a second and then reboots into recovery automatically)

issue:
adb shell idme bootmode 4000
adb reboot

Or, if you can't get there through adb but can with fastboot
fastboot -i 0x1949 oem idme bootmode 4000
fastboot reboot

connect w/ adb on device w/ broken touch/screen

i have an oppo find5 device w/ broken touch/screen.
is there a way i can connect w/ adb to erase all data before i send it to be repaired?

Connect to adb and run
adb reboot bootloader
If already turned off boot your phone into the bootloader and run
fastboot -w or fasstboot erase userdata
If you wish to format the sdcard
You could use
adb shell "su -c rm -rf /sdcard/."

Lumia 520 RM-914 with lineage os. Constantly restart after showing nogia logo.

Hello,
half a year after installing the os lineage, I decided to turn on the nokia again. Unfortunately, the phone restarts when the Nokia logo appears. All I can do is go to fastboot by holding down the volume down key. When I try to run twrp with command: fastboot boot twrp.img the phone will also restart. Nokia was completely unused for half a year, it had to be deleted by itself. ADB is not working. Anyone have any idea what can be done to run it? Charge the battery probably won't work without the proper boot.img. Could it be the fault of a discharged battery?

OKAY. Somehow I managed to restore the phone to Win 8. After switching to fastboot (volume down + connecting the USB cable to PC) I ran a series of commands: fastboot oem device-info, fastboot oem unlock, fastboot reboot bootloader. After this last command, OS lineage started - maybe something has crashed. I used fastboot from the file which is attached flash.7z ,then follow the instructions on the page:
Restore Windows Phone 8 if you have Android installed (Windows instructions)
Thanks to @feherneoh who posted the content of this thread originally here:Post #1 Post #2 NOTE: DO NOT ask for a backup. If you do not have one, you have to accept to be permanently on Android like me. Create a folder somewhere that we can...
forum.xda-developers.com
I have fallow through all the steps.
I manually copied the fame_wp_unlocked.gpt file from running the lineage OS to the / sdcard directory because adb commands do not work in TWRP. I run the sgdisk --load-backup /sdcard/fame_wp_unlocked.gpt / dev / block / mmcblk0 command manually from TWRP terminal.
When flashing partitions, i used the command not like flash TZ.img but fastboot flash TZ TZ.img etc ... (name of the partition mmust be written before image name). After that i was abe to restore all system thru WIndows Phone Internals application.
Better not to upload this Lineage OS - only problems! The phone may have been blocked by the network !!!