factory reset a rooted phone, corrupt files possibly? - Android Q&A, Help & Troubleshooting

i own a zte quest (n817) which is very sluggish. i had it rooted and decided to uninstall a good amount of apps to help it run faster a few months back. it worked fine for the uses i needed it for (calls, text, few apps, wifi etc.) but i wanted to do a factory reset. after doing so from the settings menu, my phone rebooted and went through the setup but the home screen is blank (screenshots below). im thinking the phone didnt reset all the way and it also might still be rooted. i wanted to know what i could do to try and recover the phone in its original state.
things ive tried: im able to put the phone in stock recovery, tried an update.zip from a similar zte phone but wouldnt work. tried a factory reset and cleared cache from the recovery. when the phone is at the home screen, i can plug the phone up to the pc and see the contents of the phone. i can also put the phone in download mode. while in download mode, tried to run some adb commands so i could maybe use dd to flash the .img files but either the operation not permitted or it just did nothing.
im trying to find the update.zip for this phone because i think that would be the simplest option. other than that, any help is much appreciated

Related

HELP -- Galaxy Tab Stuck

This is my first post, and the only reason I am resorting to this is because I have scoured all existing threads and have exhausted just about every course of action. This is my last resort.
The other day I went to work and left my rooted P7510UW Tab charging. I came back and it wouldn't boot up normally. I held the power button down for about 10-15 seconds and it finally booted, but only to the Samsung logo with the lock image. It will not go past this screen. Until this point I have never had any problems with the device. The good news is that I can get into CWM recovery; unfortunately, I cannot wipe the data. Wiping the cache is fine, but when I attempt to wipe the data and get back to factory settings, it freezes at "formatting data." But I guess the good news is that I can get into CWM recovery and Odin download mode.
I have tried the "Overcome" method. The PIT file takes but the tar file does not. I've tried flashing the stock firmware to no avail. I've tried different laptops, different USB ports, etc. I get a downloadpartition_odin error on the device and an RSQ error in Odin.
I am able to flash a recovery image but after that my options are limited and I don't have a nandroid backup.
I have ADB working on my computer and have tried to wipe data in fastboot but I keep getting a "waiting for device" error.
I'm not a complete noob in that I can understand most directions and follow accordingly but I am having trouble solving this on my own and don't know what course of action to take. I do have an external SD card and adapter if that provides any new course of action. Is there some way I can clear the data in CMD? If so, what steps and commands do I need to accomplish this? So far I have been piecing together parts of existing threads to try and solve the puzzle but obviously have not been able to get it all together yet.
Is there anything that can be done to save this?? Any help is GREATLY appreciated.

[Q] Can't access recovery nor reset to factory settings on rooted device

Hello,
I own an Android tablet KO PARA1 FULL and experiencing a strange problem. This is a chinese atm7029 quadcore tablet (16gb, 1gb ram, without bluetooth, only wifi, bu supports 3g dongle), running android 4.1.1 nad 3.4.0+ kernel, which came prerooted. After some time I've decided to install backup programs on in to make a full backup of the device for the case something would go wrong, and after some trying I descovered, that there is something like recovery for that purposes which seemed a good solution for me. I decided to install CWM, which I managed to install without problems and made some backups on my device. Everything was fine, I did some factory resets through the time, some restoring processes from my previously backup states of the device, was always able to activate CWM recovery menu through Reboot to recovery or through combination of Volume down a Power button...
Until last saturday. I was normaly surfing the internet, reading mails and afterwords I powered my tablet off (it is draining battery in sleep mode, but its another story..). After a while wanted again to write a mail, so I powered it on. In that momet seemed the screen too dirty for me and I tried to cleen it little bit throug the bootup process. Unfortunately I obvious confused the system with it and after boot it was not responding properly. I did not wait enough and after a while powered it off with power key pressed for a long time, to make a new boot.
But when I powered it on again, it stayed stuck in boot logo and did not boot at all. I've tried a copple of times to boot it again with no cuccess, stayed stuck in boot logo for more then 10 min...
Afterwards I decided to make it boot up with the help of computer. I downloaded adb and drivers and somehow managed to make it boot up. I thing I was too excited to see it boot up again, that during boot up process I desconected my device from computer...
My worries were reliesed and I thought it would be a good idea to make a restore from backup to prevent some strange behaviour, so wanted to boot into recovery, but nothing had happened. After some repeated clicks on Boot into recovery button, as well as app called rebooter with nothing happening, I decided to try it out through button combination. It has not worked as well Next try was to reset to factory settings. But when I go through the menu, I can click on reset to factory settings button, seeing warning that I will lost ma data, then I can push the button to make it happen, but nothing is happening. I see only the screen with the button, can touch it 100 times and the tablet stays on, fully funcional. making no factory reset as it done before.
I did a lot of reading and searching, but have not find answer for my problem. I flashed recovery images from my backups (using flashify, flash gordon, adb shell, terminal emulator), from all previously functional states of the device. I refleshed the CWM recovery downloaded from the internet for my chipset, which previously did the job just perfect, with no success...
I am still not able to reach recovery menu. For me it seems like the bootloader would be locked, but I did not find the answer how to unlock it without to be able to start in some recovery state to use fastboot command to unlock it.
Otherwise, my device is functional, still rooted, i can use it without any other problems. But not be able to do recovery from my backups, even do a factory reset.
How can I restore my access to recovery mode? Is it somehow possible?
Hopfully it is not too much information (tryied to follow the intructions and wrote everything I thought would be important to know about) and you will not be bothered to read all my story and pull me out of my darkness with helpfull suggestion.
Thanks a lot in advance
Steve

Rooting a phone stuck on start up

Hi, I've had a quick search and couldn't find anything that matches my question.
My S3 is stuck on the flashing 'Samsung' screen, I've tried connecting it to my pc to restore it with Kies but it won't load up. I've never tried to root it so could I put the phone into download mode and root it then save my data?
I've done a far bit of reading trying to fix it and I've started the phone in boot mode and wiped the cache but I need to get my data off the phone.
I'd be grateful for any help. Thanks:good:
Edit: I rooted it because I got bored of waiting and it still isn't getting past the flashing Samsung screen any ideas?
Try flashing the exact same firmware with Odin, disable kies first.
This might allow your phone to boot but you'll probably have to factory reset anyway. If done in recovery this shouldn't wipe the internal sd card, but you will lose all apps and settings etc.
For the phone to spontaneously stick during boot usually means a corruption issue, most often of the internal storage.

[Q]DigiLand DL1010Q softbricked

Ok, here is the deal and I hope someone can help me. I have a cheap DigiLand DL1010Q tablet to play around with. It is stock, but I rooted it with KingRoot. There was a recent OTA wireless update and after it was installed it said that it needed to go into recovery mode to install and reboot. I selected install now and reboot. This is where my problem started and has remained. It loaded into recovery mode and is in an endless boot loop. I've tried rebooting it, recovery with the recovery file and every manual reset possible to no avail. DigiLand support said that I should power down the tablet, and while holding down the Volume Down (-) hit the power button and it will boot into a Chinese recovery mode. I've tried that and it just stays on the DigiLand screen forever. (I left it there for 8 hours.) I can sideload via ADB and the drivers are installed, but it will not let me load anything. It states that the bootloader is closed. I receive the same message via Fastboot. Now here is the interesting thing. Even after selecting the factory reset within the Recovery Mode, everything is still there. I have wiped the cache and partition and user data, but nothing really happens. It is still all there. I see the recovery file, but it will not load. All I see is NO Command.
I do have a sd card that I could flash things on, but it doesn't seem to register the card. It sees the sdcard, but that is the internal drive. How do I get it to look at the sdcard that I put into the slot? Is there a bootloader unlock? Does anyone have the factory image that I can put on my sdcard? HELP!!!!
I am fairly good with computers and have rooted phones and tablets before, but I seem to be hitting my head on a bricked wall - no pun intended. Let me know what programs, files or whatever. At this point I am willing to try anything. I can send it back to China for $50 for them to redo it, but I only paid $69 for it and I'm not going to put more money into this cheap tablet. I would just like to get it to work.

*URGENT* HELP! File pulling with ADB

To start off, I suffered, what seems to be a common problem, of the fingerprint unlock on Samsung Galaxy S6 Edge randomly being unable to recognise my fingerprint. Followed by my back-up password not being accepted. Unfortunately, I turned off my data and wifi before the phone locked so the problem doesn't seem to be able to resolve itself unless I Factory Reset the phone.
This i am happy to do as long as I can find some way to retrieve the media files from the phone (just pictures and videos). I read up and watched some videos where some people were able to use ADB through Recovery Mode or Field Test mode, and pull the files from the phone. These people however were using older models of Android phones but I decided to read numerous pages etc and go ahead and try.
I set up everything (I believe) i needed on my Mac Book pro in order to use the Adb Terminal. However when I tried to connect my phone Adb couldn't detect my device. I then decided (after reading somewhere to do so) to press "Apply update using ADB" on the Recovery menu. Again, Adb did not detect my device.
i left this screen up on my phone which resulted in "dm-verity verification failed..." appearing at the bottom of the screen. It then switched back to the Recovery menu and continues to show "dm-verity verification failed..." at the base of the screen. Now when I try and power up the phone normally, the start up screen just repeatedly flashes and it goes no further than that.
Im not completely brain dead when it comes to this stuff but I obviously don't fully understand what I am doing, So Im wondering if there is a genius out there who, even after what I've done, can help me pull the files from my phone before I have to Factory Reset!
The problem is, that you don't have the ability to use adb pull through the stock recovery. This kind of thing can only be done via a custom recovery like TWRP, CWM, or Philz. Now that it's not booting, pretty much the only thing to try is to install a custom recovery and boot directly into it before it tries to restart. Make sure you find one for the correct variant of your phone. If yours is a VZW or ATT version, you're in trouble because they don't have custom recoveries like that for them.

Categories

Resources