Hi
Can anyone please help me. I have Nexus One. The screen was broken and I managed replacing it myself. It works fine except the "middle" rollon button.
The situation here is, I installed Zdbox long ago and protected few apps (including settings) with password. I am not using my Nexus One for sometime and eventually I forgotten the PIN i setup in Zdbox. This Nexus One is running with "MIUI" custom ROM.
I reboot to "CWM recovery" and wants to format data by which I can factory reset the device. But in the recovery mode the selection can only be done (as I know) with the middle button (which is not working in my case). I could scroll through CWM recovery options but could not select any option because of non-working middle button.
I could use ADB and also "adb devices" command show up my device. Is there way to factory reset through ADB or Fastboot command.
Many thanks in advance.
You could do a factory reset from Settings> Privacy> Factory data reset.
You could also try the new 4EXT Touch recovery that use the touch screen and does not requires the track ball.
fastboot erase system
fastboot -w
the -w takes care of everything else
Quick SUMMARY (see details below if you've got some minutes to read!)
-> I need HELP!!!
-> Phone is rooted stock GB with jb hboot unlocked bootloader and TWRP v2.2.0, also superCID.
-> Problem is phone apps keep force closing and won't retain any change I make after reboot
-> Last installed program was ROM Toolbox
-> Steps already taken include: Reboots, Fix permission, Wipe (ALL), ROM Update using Windows, RUU using SD card.
Details
I have a Vivid with Stock Gingerbread (Rooted, Bootloader Unlocked, Juopunutbear hboot, SuperCID S-OFF, TWRP Recovery v2.2.0)
I recently removed the SD card on my vivid to use on another phone (SGS III) and when I returned the SD card and started my vivid, I tried using the file manager (ES Explorer) and it force closed, following series of other apps force closing.
I restarted the phone and the force closing didn't stop. I tried uninstalling the most recently installed app (ROM Toolbox) thinking it might be the culprit and nothing changed. I rebooted the phone and noticed every time I rebooted, the phone goes back to the state (installed apps, settings and every other thing) it was before I removed the SD card.
I installed Titanium Backup to make a Backup and flash the phone, but it kept force closing and after several reboots and attempts, it installed but couldn't acquire root.
I restarted to recovery to fix permissions and cleared cache and dalvik cache then rebooted the phone. No luck!!!
I eventually decided to wipe the ROM and do a fresh RUU install. I wiped system and data using recovery but when I restarted the phone, it booted to the (pre-SD card removal) state and was still force closing.
I tried installing ICS using the RUU from att and I got an "Error 155" on the way. I also tried installing the RUU using PH39IMG method with the SD card, it goes through the normal install process and when the phone booted, it's still the same state it was that it takes me to changing nothing.
I've tried all I know and it seems the phone is "write-locked" as it won't retain any change after reboot, suggestions to what I can do to fix this weird problem please.
I am not so sure...
Did the sgs3 reformat your sdcard to a different file system?
Sent from my HTC Holiday using Tapatalk 2
rignfool said:
I am not so sure...
Did the sgs3 reformat your sdcard to a different file system?
Sent from my HTC Holiday using Tapatalk 2
Click to expand...
Click to collapse
No it didn't. I only used the sdcard to copy some files to the sgs3 and I still could access the sdcard on my vivid through Root Browser in ROM Toolbox.
hardware maybe
Interesting... One thing you could do is enable USB debugging, and save a logcat showing your phone hitting some of these FCs so we can see what is causing them.
Once USB debugging is enabled, simply boot your phone, plug into your computer via USB, open a command prompt to where you have ADB tools installed, and type "adb logcat > log.txt
That will stream the log from your phone into a text file. After you get one or two FCs, on the command window hit CTRL + C to close the console, and save the log. Then post it as an attachment here.
ess.boyer said:
Interesting... One thing you could do is enable USB debugging, and save a logcat showing your phone hitting some of these FCs so we can see what is causing them.
Once USB debugging is enabled, simply boot your phone, plug into your computer via USB, open a command prompt to where you have ADB tools installed, and type "adb logcat > log.txt
That will stream the log from your phone into a text file. After you get one or two FCs, on the command window hit CTRL + C to close the console, and save the log. Then post it as an attachment here.
Click to expand...
Click to collapse
Thanks ess.boyer. I've been busy over the past few weeks so just saw your reply now.
The phone is in a pretty bad shape right now, I managed to drop it and the screen is shattered so I can't touch the screen to use it.
But I put it on and did the log. Please find attached.
Thanks for wanting to help!!!
So I think the install is probably botched. I'd recommend wiping EVERYTHING and reinstalling from RUU (maybe try a different RUU even).
However, first, please try wiping your cache and dalvik cache. Most of the errors are from not being able to find symbols in dalvik.
Also, are you restoring apps using Titanium backup or some other such program? If so, that could also be an issue. If you have, and wiping cache & dalvik cache don't work, you may want to try wiping /data entirely, and NOT restoring apps before you can confirm that the FC issues you were seeing are still there.
Give the cache & delvik clean a try, and if that doesn't work, please attach a similar log so I can confirm you're seeing the same issues, then we can go from there.
ess.boyer said:
So I think the install is probably botched. I'd recommend wiping EVERYTHING and reinstalling from RUU (maybe try a different RUU even).
However, first, please try wiping your cache and dalvik cache. Most of the errors are from not being able to find symbols in dalvik.
Also, are you restoring apps using Titanium backup or some other such program? If so, that could also be an issue. If you have, and wiping cache & dalvik cache don't work, you may want to try wiping /data entirely, and NOT restoring apps before you can confirm that the FC issues you were seeing are still there.
Give the cache & delvik clean a try, and if that doesn't work, please attach a similar log so I can confirm you're seeing the same issues, then we can go from there.
Click to expand...
Click to collapse
Please see my steps already taken.
I've wiped cache and dalvik, I've installed RUU thru windows, I've installed RUU from SD card. But whenever the Phone boots up, the phone state does not change at all (all apps are as they are, all settings are as they are).
I even tried to lock bootloader, remove superCID. Just a reboot and it all goes back to what it was.
Thanks
What happens if you reboot the phone without the SD card in it?
ess.boyer said:
What happens if you reboot the phone without the SD card in it?
Click to expand...
Click to collapse
The phone boots up to homescreen normally and the apps installed on SD don't work, with reduced FC
For Phone specs see signature.
I've damaged my display i.e. my LCD is broken so nothing is displayed but I can turn the phone on as my morning alarm does go off and the 'menu' and 'back' controls light up so board is functioning.
I have decided to sell it as is, so someone else can faff around with it if they want to repair it. What I need to do now is try and wipe my data off of the phone before selling.
BUT...I'm not sure what the steps are for the N7000. I have downloaded the Android SDK and ODIN. Have also seen these instructions elsewhere...
1. Download factory_reset.tar.md5
2. Open ODIN
3. put factory_reset.tar.md5 in PDA section and do not check/uncheck anything else...
4. Put your phone in download mode and connect it to PC..........................Not sure how to put the N7000 into download mode, tbh I had only ever heard of recovery mode. Instructions were as follows....
Volume down + home +power
That will lead to warning Page
Here you have to press volume up to enter download mode.
5. Hit start and it will flash and reboot.................................What exactly am I flashing here? I thought we were just wiping data why do I need to flash anything?
Is there another or better way of wiping the data or will the above work?
Thanks
What is the recovery you have? (before you say gain to check your signature, it states philz and running 4.2.2. So confused.).
Vol up + home + power for about 10 seconds should take you to recovery mode. Connect phone to pc and run adb devices. Check if the device is listed. Then using some Linux commands you can wipe data and your internal sd card.
About adb please Google.
Using odin, if you have the file you mentioned, (idk much about the file) but what it seems to do is when flashed using odin it will run flash a blank data & cache partiton thus performing factory reset. This will not wipe your internal storage.
nokiamodeln91 said:
What is the recovery you have? (before you say gain to check your signature, it states philz and running 4.2.2. So confused.).
Vol up + home + power for about 10 seconds should take you to recovery mode. Connect phone to pc and run adb devices. Check if the device is listed. Then using some Linux commands you can wipe data and your internal sd card.
About adb please Google.
Using odin, if you have the file you mentioned, (idk much about the file) but what it seems to do is when flashed using odin it will run flash a blank data & cache partiton thus performing factory reset. This will not wipe your internal storage.
Click to expand...
Click to collapse
Thanks for getting back to me. Never got 'adb devices' to work, don't know why. For the first time I've managed to get access to see my internal storage. As I had pattern security enabled on the phone I assume I must have managed to get into recovery mode and do what I believe was a factory reset.
Am I right in assuming my personal data i.e. contacts data has been deleted?
Don't know. What exactly did you do?
So my Kindle Fire HD 7(2012) is bricked after trying to factory reset CM12.1. I took some advice and tried to run some ADB commands and then ADB says device unauthorized. Since my Kindle is stuck at the TWRP boot screen I cannot accept the RSA key. What should I do?
wizahh101 said:
So my Kindle Fire HD 7(2012) is bricked after trying to factory reset CM12.1. I took some advice and tried to run some ADB commands and then ADB says device unauthorized. Since my Kindle is stuck at the TWRP boot screen I cannot accept the RSA key. What should I do?
Click to expand...
Click to collapse
Reboot into TWRP, select Wipe -> Advanced Wipe, and then check all the boxes and swipe to wipe. At this point, all your system, data, and cache partitions will be completely empty, so you will need to reboot into TWRP again (ignore the warnings about not having an OS installed or root), copy a ROM zip from your PC to the kindle's internal storage, and flash it. Once you have it flashed, you'll be starting with a clean state (much like a factory reset), so you should have the ability to set up the device again once the ROM fully boots and get ADB to work.
monster1612 said:
Reboot into TWRP, select Wipe -> Advanced Wipe, and then check all the boxes and swipe to wipe. At this point, all your system, data, and cache partitions will be completely empty, so you will need to reboot into TWRP again (ignore the warnings about not having an OS installed or root), copy a ROM zip from your PC to the kindle's internal storage, and flash it. Once you have it flashed, you'll be starting with a clean state (much like a factory reset), so you should have the ability to set up the device again once the ROM fully boots and get ADB to work.
Click to expand...
Click to collapse
Device is stuck at the TWRP boot screen so I can't do any of that.
Stock Android 6.0 with stock recovery, no root, locked bootloader. Ran the device out of internal storage by writing too many files to the application's data directory. The device crashed and now it goes black after the boot animation. Able to get to the bootloader and recover menus. Lots of data stuck on the device. Any advice on pulling the files or getting Android to start again?
Try wiping the cache in the recovery menu.
Red_81 said:
Try wiping the cache in the recovery menu.
Click to expand...
Click to collapse
Tried this already. Thanks for the suggestion!
Sorry, I didn't see that I your original post so I had to start at the beginning with the most simple suggestion.
Go to recovery and try to use the adb shell to copy off the data you want to keep. Maybe also try a backup from adb (I forget the command).
If you know of a program that is taking up alot of data in the data partition that you don't care about losing then you could try using the shell to delete that data file.
Otherwise, you may just have to factory reset and start over.