hi all
i am trying to do a factory reset to my nexus S but i faced some problems, the phone cant be reset to factory settings. my phone is on 2.3.4 and is rooted
i had tried the following steps
1) going to Settings>Privacy>Reset phone
after i confirm to wipe everything, the phone rebooted and it will stuck at the "Google" logo (in words) with the fastboot unlock logo at the bottom. i took off the battery to shutdown the phone (anything i press at this moment does not get any response from the phone) and start it up again. once it is started (it get pass the google word logo if i do it this way) all my application and even my themes are still there
2) shutting down the phone. press volume up + power button. choose recovery
same thing happen as above. it cant get pass the google word logo and once i restart the phone by plugging out the batt, it went back to previous state without wiping anything
i search online guide and also youtube video and all of them shows that the recovery will bring you to a android with a exclamation mark (in the triangle) but i cant get to the screen. i had left my phone there for 30 minutes but it is still stuck at the google logo.
Please help
Reflash latest clockworkmod recovery, boot into recovery and wipe data + cache + dalvik.
polobunny said:
Reflash latest clockworkmod recovery, boot into recovery and wipe data + cache + dalvik.
Click to expand...
Click to collapse
thanks for the feedback. now i am trying to flash it but i faced "adb device not found" error
ok done
managed to flash it back to an older version and everything works now
thanks a lot for your help! cheers
Make sure to update it eventually because you could run into issues when flashing stuff if your recovery isn't up to date.
No problem!
hi
i use mi 425 spice stellar phone.
i tried to root my phone and it was successfully rooted
but when i rebooted, i saw a blue screen after the boot image after 2-3 minutes of wait.
i kinda got scared so i decided to reflash stock rom by going to recovery menu (in which we have to navigate from the volume rockers)
i applied update from sdcard (update.zip) which is also the method of unrooting.
the update was applied successfully.
then i chose reboot system option and pressed power button
the boot image came but looped back to recovery.
please someone help.
the blue screen doesnt come now but my phone boots to recovery every time i reboot.
i am now not able to use my phone i also tried to wipe data/reset factory settings but no use.
did u manage to solve your problem ? i received a phone in same condition
There is no solution in the net for this problem
You must go to service center in your country
I'm new to the Verizon GS3. I rooted with SuperSu_GS3_Debugfs_r2a, then unlocked with EZ-Unlock12.apk. I then installed CWM V6 using VZWGS3_EZ-Recovery2.2.apk. My phone is rooted and unlocked, but when I boot into recovery mode (vol+,home and power) I get a blue text with the header "Android System Recovery (3e)". Below are a few options in blue, but no bakup option. Below that there are red error messages which state :E:Failed to mount/data(invalid argument), and E:Can't mount /data/fota/ipth-muc.prop. These are repeated three times. Finally below that in yellow is a message regarding using manual mode and appling Multi-CSC.
I tried reinstalling the EZ-Recovery and get the same result. I know I'm probably overlooking something simple, but I've searched for another user with this issue and can't find a solution. Can anyone help? Thanks!
dl ez reccovery from market
ddurandSGS3 said:
dl ez reccovery from market
Click to expand...
Click to collapse
That's what I used. I got the results I posted above. Any other suggestions? Thanks!
STraver said:
That's what I used. I got the results I posted above. Any other suggestions? Thanks!
Click to expand...
Click to collapse
the way you descirbed it it sounded like you sideloaded it through an installer.
i always flash recovery through the app. try that instead of holding buttons down.
ddurandSGS3 said:
the way you descirbed it it sounded like you sideloaded it through an installer.
i always flash recovery through the app. try that instead of holding buttons down.
Click to expand...
Click to collapse
Just tried reboot into recovery from the app itself instead of the 3 button method. Unfortunately I got the same recovery error I reported in the original post. Any other ideas? I wondered if my bootloader was really unlocked, and that perhaps that was the issue. But a search found an unlock check-if the Samsung logo is only on the screen for a second when the phone boots, than my bootloader is unlocked. If that's true than my phone is unlocked. It's got to be something simple since I'm not finding others with this issue.
STraver said:
Just tried reboot into recovery from the app itself instead of the 3 button method. Unfortunately I got the same recovery error I reported in the original post. Any other ideas? I wondered if my bootloader was really unlocked, and that perhaps that was the issue. But a search found an unlock check-if the Samsung logo is only on the screen for a second when the phone boots, than my bootloader is unlocked. If that's true than my phone is unlocked. It's got to be something simple since I'm not finding others with this issue.
Click to expand...
Click to collapse
did you select custom - 6.0.1.0 (or something close to it? my phones not next to me)
STraver said:
I'm new to the Verizon GS3. I rooted with SuperSu_GS3_Debugfs_r2a, then unlocked with EZ-Unlock12.apk. I then installed CWM V6 using VZWGS3_EZ-Recovery2.2.apk. My phone is rooted and unlocked, but when I boot into recovery mode (vol+,home and power) I get a blue text with the header "Android System Recovery (3e)". Below are a few options in blue, but no bakup option. Below that there are red error messages which state :E:Failed to mount/data(invalid argument), and E:Can't mount /data/fota/ipth-muc.prop. These are repeated three times. Finally below that in yellow is a message regarding using manual mode and appling Multi-CSC.
I tried reinstalling the EZ-Recovery and get the same result. I know I'm probably overlooking something simple, but I've searched for another user with this issue and can't find a solution. Can anyone help? Thanks!
Click to expand...
Click to collapse
I had the same issue when I first flashed CWM. If I flashed CWM then rebooted into recovery, it would work properly. Then reboot, and the next time I would reboot it would be back to the android recovery. So this was I how I fixed it (I was missing a very simple selection myself)
1 - From ez recovery flash CWM
2 - Reboot into recovery using ez recovery
3 - You should boot into CWM this time, select Reboot
4 - When you select reboot you will get a warning message asking if you want to disable the stock recovery. Select YES.
5 - Phone reboots and prevents the phone the "re-flashing" stock recovery on reboot
6 - Let it boot up
7 - Power off the phone (not reboot)
8 - Boot into recovery from power off. (Vol +, home, Power)
You should boot into CWM. Without selecting that disable stock recovery option, its switching back to stock everytime. This is how I fixed my problem a few weeks ago. Hopefully that helps. Ive also heard of people having to flash a custom ROM before CWM would stick.
travis.bridges10 said:
I had the same issue when I first flashed CWM. If I flashed CWM then rebooted into recovery, it would work properly. Then reboot, and the next time I would reboot it would be back to the android recovery. So this was I how I fixed it (I was missing a very simple selection myself)
1 - From ez recovery flash CWM
2 - Reboot into recovery using ez recovery
3 - You should boot into CWM this time, select Reboot
4 - When you select reboot you will get a warning message asking if you want to disable the stock recovery. Select YES.
5 - Phone reboots and prevents the phone the "re-flashing" stock recovery on reboot
6 - Let it boot up
7 - Power off the phone (not reboot)
8 - Boot into recovery from power off. (Vol +, home, Power)
You should boot into CWM. Without selecting that disable stock recovery option, its switching back to stock everytime. This is how I fixed my problem a few weeks ago. Hopefully that helps. Ive also heard of people having to flash a custom ROM before CWM would stick.
Click to expand...
Click to collapse
That did it! Thanks!
No problem
Sent from my SCH-I535 using xda app-developers app
I did a factory reload of a rooted phone with CWM.
Now for the CWM issue the Moto G loaded OK and then said there was an update for android to fix some bugs. This was 4.4.3. I loaded it and it gets half way and it then says
"Signature verification fail"
at the bottom of the screen and
" Install Untrusted Package"
The options are yes, no or go back
at the top....
whichever one I try it then tries to boot shows the Android / Motorola screen and starts up gets a txt message for 2-3 seconds... it then goes back to Android CWM recovery with the same options as above and repeats the process. again and again and again. No function keys will stop this cycle which just repeats again. This continues until the battery dies.
any ideas ? how can I override this action in CWM v6.0.4.6 and force it to do a factory reload ? any help or advice much appreciated.
The following thread had a similar problem and was fixed... http://forum.xda-developers.com/showthread.php?p=53404637
NerdNoob1210 suggested...
"If you can still power your phone, can you still access the boot loader? If so, I would suggest using adb from a computer to flash Phillz recovery. CWM always gave me a lot of random errors when flashing items. You could use PhillZ to flash the stock ROM for 4.4.2. After that, just follow the same process I did. Download the update zip via the OTA download when it prompts you. Once it's finished, DON'T boot back into Android. Boot into Phillz recovery from the boot loader, move the zip out of the cache and onto sdcard or your computer, and then flash it either straight from the phone or by sideloading it from your computer. Then you'll have a working version of vanilla 4.4.3, and you can flash over a custom ROM in the future if you so choose."
unfortunately I can't get into bootloader. I can connect usb and it makes no difference. therefore adb commands dont work. it just goes straight into screen described with those three options. I'm hoping that there is an override action in CWM which isn't power and volume down which do nothing.
If not how can I force it into bootloader instead please ? any suggestions appreciated.
Guys, I just gained root access to my phone 5 days ago, yesterday I installed custom recovery (TWRP - openrecovery-twrp-2.8.5.0-xt1032). I think my device is XT1033. After that i tried to install xposed framework by installing it through the recovery and then my phone started to boot loop at the bootloader warning. My phone can access the fastboot menu. From there when i try to access recovery it just shows the logo of TeamWin followed by a black screen and then directs me to the bootloader warning message as usual and keeps looping. Also when I hit the factory reset button it tends to boot loop at the boot loader warning message.
The attachment shows the window it loops.
Please help me. Is my phone over?
Hey dont worryy. Just use philz recovery 6.55.0. That is best as twrp donot support xt1033.
Then in that just clear cache and dalvik cache. And try to reboot. If it does its good. If not then just flash any other rom using otg (usb ) if u dont want to lose any data.
Edit- to flash recovery. Press the power key for like 10 sec until the phone reboot. And black screen comes up. Then quickly press power and volume down key for 3-4 sec to go itno fastboot mode. Then flash the philz recovery ( search for it in original android development or google it) and flash it.