Guys my D6653 is rooted and on eXistenZ Marshmallow firmware.
Dont know what went wrong (may be a wrong xposed module ro some app dont know) now whenever i reboot phone it keeps rebooting even after lockscreen appears. The only way to stop is immediately swipe on lockscreen to gain entry on to desktop.
Anyways theres lot of app clutter now in phone so would like to factory reset it.
But will just factory reset solve the issue or do i need to wipe dalvik and cache via twrp for clean rom??
I know I'm late on this but I feel you should factory reset your phone and install the rom all over again.
Related
Ugh! Please help! freaking out. I have a G2. I was messing around on Rom manager and downloaded a pershoot kernel, when it went to reboot.. It never turned back on. I did a factory reset, wiped SD, wiped data, wiped cache.. Is there any way to do a complete reset? I have S-On and everything.
chill out, just get odin and upload/download (whatever you like to call it) a actual stock rom to your phone. then it should work again!
It's a bootloop caused most time by wiping the dalvic cache completely, some of the dalvic cache files have critical system information in them..
Please explain the steps for that.. Or give a link or something.
should i tell you the 1,2,3-method ?
ok
1. download odin and a stock rom from the developers forum of your device
2. start odin, put your device in update/download mode, flash the stock rom
3. done! If not, use search: http://forum.xda-developers.com/search.php or try youtube (flash g2 rom)
Now it's my turn. Pressed factory reset by accident in boot loader. Can get to TWRP but it says E: Unable to mount storage
e:Unable to mount /sdcard/TWRP/twps. when trying to read settings file. etc...
Advanced File manager in TWRP shows /sdcard/TWRP
Any ideas???? If I try to mount data in TWRP my Mac wants to initialize.
Thanks
TWRP shows internal storage 0 mb
I flashed the stock recovery, then ran it and somehow it booted right into CM11. Everything was lost, but it's working again.
Factory reset wipe everything! Including SD card.
null0seven said:
Factory reset wipe everything! Including SD card.
Click to expand...
Click to collapse
Possibly, but how come CM11 was still on there? I think that the Boot Loader in Moonshine's factory reset is not compatible with CM11. Luckily the stock recovery fixed things for me.
808phone said:
Possibly, but how come CM11 was still on there? I think that the Boot Loader in Moonshine's factory reset is not compatible with CM11. Luckily the stock recovery fixed things for me.
Click to expand...
Click to collapse
I had the same issue, pressed by mistake factory reset in bootloader some time ago. I was pressing vol down to reach recovery, there was a slight lag and I pressed it a second time the immediately I've pressed power...so cursor has jumped 2 rows then executed. I've solved it only by flashing stock recovery and resetting to factory settings again, then flashed TWRP.
Now why you still had CM11...well not 100% sure but in TWRP when you wipe to factory the system partition is not formatted. I've paid attention once to the messages during a wipe and it was formatting data, cache, dalvik and android secure but not system. A reason can be that while flashing any ROM, the install script formats system at the beginning so theres no need to do that with factory reset.
Now I can only think that the factory reset from bootloader does the same and system is not wiped. Theoretically it is correct...system is read only especially on a stock non rooted device and resetting it to factory practically means that any trace of personal settings/aps and so on should be erased. And those are not stored on the system partition. There is also no hidden place on the phone where a recovery image of the original android OS is kept so this is not like on the laptops where you reset to factory and Windows is reinstalled from the recovery partition. My guess is that the factory reset just wipes all partitions that contain personal data and settings and leave system intact. So after a wipe and reboot is like you first start it.
You still had CM11 cause the wipe didn't format system...If anyone has a better explanation I would be glad to hear it. So From my point of view nothing went wrong and has nothing to do with the Maximus recovery or it's compatibility with CM11. It would have happen the same if you have used any other stock recovery
Factory reset, resets youre phone to original settings.
Anyway, its good that the phone works.
null0seven said:
Factory reset, resets youre phone to original settings.
Anyway, its good that the phone works.
Click to expand...
Click to collapse
Yes. And it is not formatting system when doing this. So any os is installed will be kept
Sent from nowhere over the air...
Rapier said:
Yes. And it is not formatting system when doing this. So any os is installed will be kept
Sent from nowhere over the air...
Click to expand...
Click to collapse
I don't want to try it again but I wonder if moonshine's factory reset is incompatible with cm11?
Dont understand what do you mean by "incompatible". The factory reset from bootloader is not the same thing as the one from a custom recovery. You shouldn't do a factory reset from bootloader regardless of the ROM you're using
Moonshine is an S-Off method, I didn't used it myself so I don't know what factory reset option is in there
Sent from nowhere over the air...
I never said anything about the custom recovery. If you should never use it, why is it there and why does it make the SD card not available?
Wow, HTC says you can use it here:
http://www.htc.com/us/support/htc-one-x-att/howto/313779.html
I'm sure you know something others like me don't, but I when I mean "incompatible" I mean that I don't believe that it should make the sdcard unavailable and make the phone think it has zero MB. I think what you might have missed is that I used factory reset from the custom boot loader from moonshine. I was wondering if that factory reset was compatible - that's all.
Again, it was a mistake - it's not like I chose it on purpose. Thank you for the help.
808phone said:
I never said anything about the custom recovery. If you should never use it, why is it there and why does it make the SD card not available?
Wow, HTC says you can use it here:
http://www.htc.com/us/support/htc-one-x-att/howto/313779.html
I'm sure you know something others like me don't, but I when I mean "incompatible" I mean that I don't believe that it should make the sdcard unavailable and make the phone think it has zero MB. I think what you might have missed is that I used factory reset from the custom boot loader from moonshine. I was wondering if that factory reset was compatible - that's all.
Again, it was a mistake - it's not like I chose it on purpose. Thank you for the help.
Click to expand...
Click to collapse
The reset to factory from bootloader exists because on stock ROM there's no custom recovery that has that option....so it's in bootloader. For it to work properly though, you must have the stock recovery also. If you have a custom recovery like twrp/cwm and use the wipe from bootloader it'll mess your sd cause phone is not able to perform the wipe properly with that custom recovery. That's why, in order to get back to normal you should flash back stock recovery and perform the wipe from bootloader again.
Sent from nowhere over the air...
Thank you for the clarification. It makes sense. Too bad that reset is so close to the recovery command. It's pretty weird that I didn't have to run the wipe from the stock boot loader again. It ran and rebooted the phone into CM11. Anyway, I am glad I am back to running. Thanks.
No matter what rom i'm running I get random reboots. I even took the update from Verizon to 4.4.3 and still recived random reboots. Is this just me? I have also ran safe mode and get them.
Have you tried a factory reset?. If not try that. Don't do it from security settings though. Do it through fasboot. Just be sire to save anything you don't want to lose.
Yes and have tried multiple roms. IT does it not matter what rom or what settings I have.
Sounds like a complete wipe via fastboot may be your only fix. Just be sure to back up all the stuff youbwanna save cause it gonna wipe it clean. I am stock and was having same issue did the reset and everything fine now. I however forgot to make a back up lol
How do I do that? I tried the factory reset option and it took me back to TWRP
Make sure quick boot is turned off in battery settings. Then power down device. Power back on holding down volume and power. Your phone will boot to a white screen. Then use volume down to cycle to factory reset. Only thing is I'm not entirely sure what it will do to s-off and unlocked bootloader. You may want to Google that and see what it says
I've had my m8 for several weeks and never had a random reboot, that's on both stock and custom Rom. If the factory reset doesn't fix it, you may have a hardware issue
Factory reset doesn't work on a custom recovery
tjamscad said:
Factory reset doesn't work on a custom recovery
Click to expand...
Click to collapse
Better: You should not try a factory reset from settings if you have a custom recovery installed. It can lead to unintended consequences......
And why would you? That's what a recovery is for! TWRP and CWM both have the factory reset option, which basically just wipes /data (without /data/media), cache and Dalvik. And that's what you need 95% of the time. For the rest format data.
A factory reset doesnt clear everything. I have done a few and nothing ever seems to be reset. When I did it from hboot I was required to set up phone again as if it had just been powered on for the first time.
berndblb said:
Better: You should not try a factory reset from settings if you have a custom recovery installed. It can lead to unintended consequences......
And why would you? That's what a recovery is for! TWRP and CWM both have the factory reset option, which basically just wipes /data (without /data/media), cache and Dalvik. And that's what you need 95% of the time. For the rest format data.
Click to expand...
Click to collapse
For the record,twrp wipe was what I was referring to when I said factory reset. I thought about saying wipe, but was afraid of how that might be interpreted.
mdorrett said:
A factory reset doesnt clear everything. I have done a few and nothing ever seems to be reset. When I did it from hboot I was required to set up phone again as if it had just been powered on for the first time.
Click to expand...
Click to collapse
A factory reset in TWRP (at least on every version I've used) wipes /data without wiping /data/media, cache and Dalvik.
Meaning it wipes all your apps and settings without wiping your personal files, but rquiring ou to go through setup again. Just did exactly that before installing CleanROM 2.0. If you had a different result I don't know which option in TWRP you chose.....
So it seems my lollipop custom hyperdrive rom has come down with a odd hangup suddenly where if I install a new app and then reboot it suddenly comes to a freezing halt after awhile, unless I go back and uninstall the most recently installed app's again and reboot. I've tried clearing dalvik and art cache and regular cache.... My question was what is clearing system, I know if I clear data I loose all my user installed app's info, is system the same thing but preinstalled app's when ya first boot up the rom and your defined choices in settings? What else am I able to do before trying a dirty flash or clean install altogether to get rid of this odd bug?
n1nj4Lo said:
So it seems my lollipop custom hyperdrive rom has come down with a odd hangup suddenly where if I install a new app and then reboot it suddenly comes to a freezing halt after awhile, unless I go back and uninstall the most recently installed app's again and reboot. I've tried clearing dalvik and art cache and regular cache.... My question was what is clearing system, I know if I clear data I loose all my user installed app's info, is system the same thing but preinstalled app's when ya first boot up the rom and your defined choices in settings? What else am I able to do before trying a dirty flash or clean install altogether to get rid of this odd bug?
Click to expand...
Click to collapse
Wiping system partiton would mean that you dont have an OS like in computer if you format the C drive(hypothetically), your pc wont boot up but your data(in hard drive D or E) would be there. Only wipe system from TWRP if you will subsequently flash another ROM. You could do a factory reset instead(goto TWRP click Wipe then Swipe To Factory Reset . If that doesnt solve your problem, flash a stock ROM or switch to a diff custom one.
My Android tablet v. 4.2.2 Was recently factory reset now there are no apps on device. Can not access setting. The message Unfortunately system ui has stopped keeps popping up and I am unable to do anything except press ok on messages. Need help fixing this so I can get back to using device. Please help solve why and how this has happened so I can avoid in future
Blk$tewie said:
My Android tablet v. 4.2.2 Was recently factory reset now there are no apps on device. Can not access setting. The message Unfortunately system ui has stopped keeps popping up and I am unable to do anything except press ok on messages. Need help fixing this so I can get back to using device. Please help solve why and how this has happened so I can avoid in future
Click to expand...
Click to collapse
Deleting dalvik cache should work, I assume you don't have TWRP recovery or root access?
As for why, it may be because you reset the device while using a UI module from Xposed or magisk or something similar.
XDHx86 said:
Deleting dalvik cache should work, I assume you don't have TWRP recovery or root access?
As for why, it may be because you reset the device while using a UI module from Xposed or magisk or something similar.
Click to expand...
Click to collapse
Device has been factory reset and everything is erased including settings. So how am I am to solve the system ui stopped
I think your only option is to flash your stock ROM or a custom ROM through fastboot.
Maybe one click root apps like kingoroot can root your device since it's old (4.2.2) but I highly doubt since you don't have USB debugging on.
If you do manage to root or install custom recovery then update here. Preferably custom recovery.