Hi All,
two days back i flashed the 4.3 factory image (because the OTA was downloaded but installation resulted twice in Robot with the red triangle and the error message "error"), rooted, restored the apps/settings with Titanium Backup.
Yesterday the device behaved normal.
This morning the device got no GPS fix and i restarted the device.
Since then i experience these strange things:
- No Notifications
- No QuickSetings
- Not able to receive incoming calls (SIM card is working in other phone)
- Home button triggers vibration and shows optical feedback, but doesn't switch back to the home screen
- "Shutdown dialog" only shows option for Shutdown. No option to change sound profile, flight mode etc
- No Screen-Lock
Wiped the cache partition and the dalvik cache - Without success.
Can anybody help me to heal my GNex ?
Yes, do this:
Fastboot erase boot
Fastboot erase recovery
Fastboot format cache
Fastboot format system
Fastboot format userdata
Then flash a factory image and don't use your titanium backup.
Sent from my Galaxy Nexus using xda premium
Judge584 said:
Yes, do this:
Fastboot erase boot
Fastboot erase recovery
Fastboot format cache
Fastboot format system
Fastboot format userdata
Then flash a factory image and don't use your titanium backup.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
you can restore apps, but do not restore system data using TitaniumBackup. if you restore from a google account then most of your settings will be restored anyway. when you do restore however quickly go to the play store and cancel all the downloads, then restore the apps from Titanium
Related
Hey guys,
I have a Gnex with android 4.2 stock bigxie. Yesterday I installed Purity 1.1 and find out that my storage had now the 0/ problem. So installed the latest cwm and tried everything again. Still had the 0/ problem. I also got messages like the phone's storage is full. And restoring NOVA launcher and TB backups was a pain in the a$$. So now I'm considering al complete wipe. Yes complete. I found this on a android forum. Is this the correct way or will this be harmful for my precious Nexus? I simply can't stand how my storage looks right now haha.
-> Instructions for a bad day: Completely wipe SD, reboot recovery, factory reset, format system, reboot system.
Is this correct or do I need something else? I'm not looking for the bootloader re-unlock way. That's too dangerous for my precious.
Thanks in advance!
Format /data too. So make a backup first
Sent from my Galaxy Nexus using xda premium
So I can do this without any problems? I can go on flashing new roms and kernels?
If everything goes well yes, then your device will be completely blank, you will need to flash a ROM via fastboot
Sent from my Galaxy Nexus using xda premium
When I completely wiped everything, should I do this?
"ROM Flashing
Obtain a ROM of your choice, and note the location on your computer.
reboot your device into fastboot mode via one of the following options.
adb reboot bootloader (requires USB debugging to be turned on).
power off the device then back on with 'vol up' + power button.
Wipe your device.
fastboot -w
Update your ROM.
fastboot update </path/to/your/RomFile.zip>
Your phone will update and automatically reboot into the new ROM."
Sent from my Nexus 7
LarsAussems said:
When I completely wiped everything, should I do this?
"ROM Flashing
Obtain a ROM of your choice, and note the location on your computer.
reboot your device into fastboot mode via one of the following options.
adb reboot bootloader (requires USB debugging to be turned on).
power off the device then back on with 'vol up' + power button.
Wipe your device.
fastboot -w
Update your ROM.
fastboot update </path/to/your/RomFile.zip>
Your phone will update and automatically reboot into the new ROM."
Sent from my Nexus 7
Click to expand...
Click to collapse
https://developers.google.com/android/nexus/images
http://forum.xda-developers.com/showthread.php?t=1626895
LarsAussems said:
Hey guys,
I have a Gnex with android 4.2 stock bigxie. Yesterday I installed Purity 1.1 and find out that my storage had now the 0/ problem. So installed the latest cwm and tried everything again. Still had the 0/ problem. I also got messages like the phone's storage is full. And restoring NOVA launcher and TB backups was a pain in the a$$. So now I'm considering al complete wipe. Yes complete. I found this on a android forum. Is this the correct way or will this be harmful for my precious Nexus? I simply can't stand how my storage looks right now haha.
-> Instructions for a bad day: Completely wipe SD, reboot recovery, factory reset, format system, reboot system.
Is this correct or do I need something else? I'm not looking for the bootloader re-unlock way. That's too dangerous for my precious.
Thanks in advance!
Click to expand...
Click to collapse
use the guide linked in my sig to fix the sdcard "problem"
Thanks a lot everybody, will try k786's method.
Hello,
After last one 4.2.2 update my phone was stuck at the HTC One Beats audio logo.
Then I tried restoring nandroid backup(with CID HTC__038)(http://forum.xda-developers.com/showthread.php?t=1975140) and then flashing boot.img. But this left me with no touch support.
So I tried a rom from here(http://forum.xda-developers.com/showthread.php?t=2107669) but then my phone stuck at HTC Quietly brilliant logo even after flashing boot.img.
Now when I tried to restore the nandroid back from the first link, the phone worked and the touch was working again. But this time, the phone doesn't show any carrier networks. flashing with the boot.mg from this nandroid stopped the phone's touch from working, but then the carrier network came back.
So what do I do next?
My HBOOT version is 1.73.0000
The second should work, did you perform a real full wipe before installing the rom.zip ?
sent from my .......
Yes I cleared any caches and formatted by partitions using the recovery.
Also I did clear the cache using fastboot command, but still no luck. I heard something like AROMA installer's boot.img won't work or something like that. Could that be the problem?
And thanks for replying.
What recovery are you using so i can describe all steps in detail
sent from my .......
TWRP recovery.
BTW I think you should know this. My phone was stuck at boot screen(the htc one beats audio logo) after I did the latest update. I was doing this for recovering from that.
Try this :
Flash this recovery
https://db.tt/MNtVjpOJ
Rename the file to recovery.img and flash it
Fastboot flash recovery recovery.img
Then flash the boot.img from the sd rom.zip
Fastboot flash boot boot.img
Fastboot erase cache
Then enter the recovery and do :
Factory reset
Wipe cache partition
Advanced - wipe dalvik cache
Mounts & storage - format cache, data, system
Then install the sd rom.zip and reboot
sent from my .......
I think you had suggested this same steps to someone else in here right?
I am not sure, but if you had I have already tried it.
Anyway I will try to do it again. Thanks so much for this!
Yep but its a method that should work flawlessly ! If not report back and see for other solutions
sent from my .......
I don't know what I'm doing wrong, I've tried just about every method I've been able to find in order to decrypt this phone but nothing seems to work for me. After every attempt I boot into recovery and can see in the log that the phone decrypted with default password. I also check in security settings and it says the phones encrypted. I've tried flashing twrp 2.8 and 3.0, in both cases I perform a factory reset as the guides instruct and wipe dalvic & cache with no success. I've also rooted the phone with chainfire systemless root and flashed the modified boot img but phone stays encrypted. Also tried flashing a custom kernel that supposed to disable force encryption. I know there must be something I'm missing. Right now I've started from square one and returned phone to stock. Any help would be appreciated, thanks.
Sent from my Nexus 5X using Tapatalk
Format data, not factory reset.
Sent from my Nexus 5X using Tapatalk
Boot into TWRP
Format userdata
Flash SuperSu-systemless
Reboot
So, format user data from adb? Because I chose advanced wipe in twrp and ticked off everything but system.
Sent from my Nexus 5X using Tapatalk
issacbourne12 said:
So, format user data from adb? Because I chose advanced wipe in twrp and ticked off everything but system.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Wiping and formating are two different things. You may format userdata in twrp or with fastboot.
TWRP: Wipe > Format Data (next to the Advanced Wipe button)
fastboot: reboot to the bootloader/power off then hold both the power button and volume down > connect to computer > open terminal > type "fastboot format userdata" without quotes and press enter
This will wipe your device clean. If you want to flash a ROM push it to the phone after formatting data.
Damn, yeah that's the one thing I hadn't done. Got it, thanks pious.
Sent from my Nexus 5X using Tapatalk
PiousInquisitor said:
Wiping and formating are two different things. You may format userdata in twrp or with fastboot.
TWRP: Wipe > Format Data (next to the Advanced Wipe button)
fastboot: reboot to the bootloader/power off then hold both the power button and volume down > connect to computer > open terminal > type "fastboot format userdata" without quotes and press enter
This will wipe your device clean. If you want to flash a ROM push it to the phone after formatting data.
Click to expand...
Click to collapse
nice.
Is "flashing factory img" will get the same effect as format userdata?
While updating the watch to Marshmallow, somehow I managed corrupted my cache partition. The watch is now stuck in a bootloop (always entering recovery). The stock recovery doesn't work anymore (black screen and some occasional text). I flashed TWRP and when checking the partition details, the cache partition is marked as 0mb. Trying to wipe or repair the partition fails.
Is it possible for someone to pull the cache image so that I can flash it in fastboot? I'm not sure if it will work, but I'm running out of ideas. Any suggestions would be greatly appreciated.
Thanks.
We should call "boot loop" "lymbo" instead. I mean you are suck in an infinite loop,
Sent from my SM-N920T using Tapatalk
Hi Storm,
That happens also with me...
Check this....
http://forum.xda-developers.com/huawei-watch/general/guide-return-to-stock-huawei-watch-t3219596
In the TWRP advance settings rebbot like Scott taught me
http://forum.xda-developers.com/huawei-watch/general/huawei-watch-bricked-t3330024
Use only this commads
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
then reboot
Voilá.
If you need any help please tell me
modstorm said:
While updating the watch to Marshmallow, somehow I managed corrupted my cache partition. The watch is now stuck in a bootloop (always entering recovery). The stock recovery doesn't work anymore (black screen and some occasional text). I flashed TWRP and when checking the partition details, the cache partition is marked as 0mb. Trying to wipe or repair the partition fails.
Is it possible for someone to pull the cache image so that I can flash it in fastboot? I'm not sure if it will work, but I'm running out of ideas. Any suggestions would be greatly appreciated.
Thanks.
Click to expand...
Click to collapse
Sounds like you might have to factory reset and let it rebuild the cache partition. But generally its a bad idea to share cache partitions from one device to another as it carries sensitive info about the user and device.
Scott said:
Sounds like you might have to factory reset and let it rebuild the cache partition. But generally its a bad idea to share cache partitions from one device to another as it carries sensitive info about the user and device.
Click to expand...
Click to collapse
Favtory resetting from TWRP seemed to solve the problem! I had kept on wiping the partitions (data and cache) separately in advanced wipe instead of performing factory reset as I assumed that it was exactly the same, however as you mentiond, performing a factory reset rebuilds the cache partition.
Thanks!
... title - a guide would be nice aswell :/
sure! https://forum.xda-developers.com/mi-a2-lite/how-to/guide-how-to-unlock-bootloader-erasing-t3878453
Just be sure that you reenter fastboot after rebooting - by pressing vol-. Then it won´t erase your data.
To be fully sure boot twrp, install it, flash aboot from 9.6.11.0 - else you will get "your system got destroyed" while booting twrp and then you can save your data partition to external sd card - now even if it would try to erase your data, you will have a backup.
And after reboot you will see, if it still tries to erase data - then it will go again and again to twrp... To solve that, reflash stock kernel - just in case.