Tag Info

New answers tagged

2

Try doing what it suggests... run e2fsck -b 8193 /dev/block/platform/msm_sdcc.1/by-name/userdata. If that doesn't work, try running mke2fs /dev/block/platform/msm_sdcc.1/by-name/userdata. You can also boot into fastboot mode and run fastboot format userdata. If none of these work, please elaborate on this "long story". How did you mess up your data ...


0

I was running into the same problem yesterday with my Nexus 5, I updated to the latest version of TWRP and nothing... Eventually I followed one of the guides online to flash the Nexus 5 with the Factory Images and that worked at the price of loosing my data..... https://developers.google.com/android/nexus/images


0

You need to flash stock recovery to install stock OTAs without computer-based intervention. Alternatively, you can download the relevant OTA for your version of KitKat, put it somewhere on your Nexus's internal storage and flash it in TWRP like you would any other flashable zip. Although you may want to note that xposed doesn't work with Lollipop yet, and ...


0

just flash stock recovery.img file through mobile uncle tools app avaailable here at-https://play.google.com/store/apps/details?id=com.mobileuncle.toolbox&hl=en But in case you want your stock rom back, this will not be helpful to you. you will have to flash stock firmware through mtk droid tools.


0

As Izzy has said, this entirely depends on the device and the particular image you are flashing. Some might flash a new recovery, some not. Some might flash only the system partition and leave your data alone. There are even packages that will flash a new bootloader. If you want to see what a ROM contains, you should open it up and have a look. Here is ...


0

After doing some more research, I think I've found a partial solution here: http://forum.xda-developers.com/showthread.php?t=2450045 First, you need to get ADB set up on your computer. In Linux it's pretty easy. Something like running # apt-get install android-tools-adb or downloading and extracting a directory. Find your partitions. Run something like: ...


0

I had a similar problem with my Nexus 5. Windows 8.1 and adb recognized the device until I put it in recovery mode, then it disappeared. I finally said "let me pick from a list of device drivers" and chose the "Android Composite ADB interface." Then adb recognized it and I was able to sideload an update.


0

Do you have CWM recovery installed? If yes, then try going in CWM and format your phone from there. It may help.


0

have you ever used Andoid data recovery program? This kind of recovery work for Android device specially. You can have a try, I ever used a program named Tenorshare Android Data Recovery to recover lost photos from my Android phone, you can have a try!


0

I enquired and found some answers to this problem. 1) If you press exit button in recovery menu, phone will reboot and regular app screen should be seen. 2) as answered earlier wipe cache does not delete user data, (only system cache files are deleted) 3) to exit the download mode (when not flashing anything to the device) is to either pull the battery or ...


1

To use fdisk without recovery, i.e. while Android is running, you need to root your phone, install a terminal emulator, and install BusyBox (the fdisk command won't be available without BusyBox, which provides a bundle of common Linux tools that aren't included in Android). Note that to install BusyBox, it's not sufficient just to install the app. You need ...


-2

wipe cache won't delete user data at all. a factory reset will preserve your photos, but not your messages... though they still might be retrievable. formatting the drive nukes everything


1

I recently wiped my phone to factory after I had rooted the phone and got rid of the bloatware I did not want. (Forgot the passcode) I thought I would have to root my phone again and then get rid of factory installed bloatware....again. I was pleasantly surprised to find both that the root was intact AND the bloatware was still gone. Also, my superuser app ...


-1

This worked for me : connect usb OTG cable and a regular pc keyboard, then power on.


0

TWRP recovery project make it like below maybe this can help case rb_recovery: check_and_run_script("/sbin/rebootrecovery.sh", "reboot recovery"); Github ref


0

A 'newer' and free (and in my opinion the best so far) root app is Flashify. It can flash kernels and recoveries from your phone. Additionally it can download the images for you, too. https://play.google.com/store/apps/details?id=com.cgollner.flashify


1

On the Samsung Galaxy S4 (GT-i9505) Volume Up, Power and Home is to enter recovery mode. Volume down, Power and Home is to enter 'Download Mode'. From download mode you can make the device visible to odin. From Odin you can flash a custom recovery, or root the device with CF Auto Root and other methods such as flashing a pre-rooted stock ROM for example. ...


3

I've found that if I run into problems with the custom recovery, I can get rid of it altogether by re-flashing the stock firmware, and then I can install the custom recovery again. You have a different device, but that's what works on a Samsung Galaxy S4, so it might work for you. Of course, there's always the possibility that if you try installing CWM again ...


-1

so hold menu button and volume up and power on once you see the sasmung logo release the power button and hold the home key and volume up button unless you see the rest option worked for me on the SM T530NU


0

Okay, it turned out to be something silly. The problem is that SE status reverts to Enforcing when you reboot. So, you have to set it to Permissive with setenforce 0 again before the first time you use Safestrap after a reboot.


0

Try holding down the home button, the volume up button and the power button for a few seconds. If that doesn't work, try the volume down button. Vol up will try and boot into recovery, vol down into download mode. Source



Top 50 recent answers are included