Corrupted cache partition - Huawei Watch

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!

Related

[Q] [VERY STRANGE] Wipe data doesn't work anymore!

Hi everybody,
I'm getting into the new AOKP Milestone 4 from the Codename 1.5.0 - so I downloaded the files and get recovery (clockwork 5.5.0.2) to make the wipes and flash the new rom and gapps... the usual routine.
Wipe data - Wipe Cache - Wipe Dalvik - Flash AOKP - FLASH GAPPS - REBOOT
1st strange thing after that: the Old Franco Kernel bootlogo. And in stuck, obv.
Why the Franco bootlogo? Bah, re-wipe everything and go on...
Nothing, stuck on Franco. So I decided to re.wipe everything again and re install the Codename android, 1.5.0 - the same wich i was coming from - to get the phone work for tomorrow. And here we go for the biggest surprise.
EVERYTHING IS HOW I LEFT BEFORE THE WIPES WHEN I WAS ON CODENAME!!!!!
Same routine, flashed Codename and reboot. Franco logo and then no configuration wizard, no backups.. everything was EXACTLY like how i left before the first attempt!!! My apps, my homescreen, even my login account, like i have never attempt any wipe or flash!!!!
IT DOESN'T WIPE ANYTHING, ANYMORE!
I'm getting mad.. tried this ten times. It's like nothing is getting wiped!
P.s: clockwork is correctly installed.. i've tried TONS of roms on my gnexus, everything has ALWAYS worked fine. No errors during wiping, usuals script "wiping /data .... wiping /cache etc.." until "DONE". No error flashing the AOKP.
Help please..
Fab
Hey there,
mike, the dev from Android Revolution HD, has a super wipe script in his thread, on the first page, might want to try that one.
It works like flashing a ROM
-Syn
You are not wiping correctly. You are having problems because the system and boot partitions were not wiped at all....
Sent from my Galaxy Nexus using xda premium
SynFox said:
Hey there,
mike, the dev from Android Revolution HD, has a super wipe script in his thread, on the first page, might want to try that one.
It works like flashing a ROM
-Syn
Click to expand...
Click to collapse
Already tried. Same results, it ends successfully the superwipe string.. and then no wipe at all!
adb reboot bootloader
fastboot -w (might wipe SD card)
or
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot update update.zip (for installing the rom)
Ok new infos.
From the log file the /data wipe seems to be undone due to the "filesystem is read only".
Any ideas?
Stupid question... but maybe check if the device is still rooted and unlocked correctly?
Maybe something messed up there...
these are signs that the internal hdd is getting screwed up... like the partition values... its a known issue for all samsung devices. the i9000 had it, the nexus s had it. they even have a lot of threads out there reporting issues abt it but no fix till now. i even had it with my nexus s (which is now a paperweight)
some fixed it with a simple wipe using oem lock n unlock, others fastboot wipe....
the most common symptom is that you can see a lot of files on your phone, but can neither delete them nor add anyting to the sdcard.
As anton2009 said, you should try wiping all the partitions, then reflash CWM, then flash your ROM/kernel.
Reboot into fastboot and type the following:
fastboot erase boot
fastboot erase system
fastboot erase recovery
fastboot erase userdata Note this will wipe/sdcard
fastboot erase cache
Then flash CWM and then ROM/kernel.
Sent from my Galaxy Nexus using Tapatalk
I am also having the same issue. However I just reflashed a bunch of roms and even though all my data is still there everything seems to be working fine.
Cptsamir said:
I am also having the same issue. However I just reflashed a bunch of roms and even though all my data is still there everything seems to be working fine.
Click to expand...
Click to collapse
Guys, all of your data is stored on the userdata partition. Most ROMs I don't think flash that partition, so all the data still remains. As well, I don't think every ROM includes a kernel, so the boot partition is not erase either. Wiping in CWM does not wipe /sdcard (which is actually located on the userdata partition as /data/media).
Use what I had posted 2 posts up and it will certainly wipe.
efrant said:
Guys, all of your data is stored on the userdata partition. Most ROMs I don't think flash that partition, so all the data still remains. As well, I don't think every ROM includes a kernel, so the boot partition is not erase either. Wiping in CWM does not wipe /sdcard (which is actually located on the userdata partition as /data/media).
Use what I had posted 2 posts up and it will certainly wipe.
Click to expand...
Click to collapse
I also think your solution will work well.
My only question is about new rom flashing: erasing ALL datas even in the /sdcard how will I be able to flash new roms if there will be nothing more on the phone? Where will i get'em?
Will I need to flash again even the CWM?
Sorry for the stupid question..
fab2disco said:
I also think your solution will work well.
My only question is about new rom flashing: erasing ALL datas even in the /sdcard how will I be able to flash new roms if there will be nothing more on the phone? Where will i get'em?
Will I need to flash again even the CWM?
Sorry for the stupid question..
Click to expand...
Click to collapse
You can still wipe userdata, boot into Android (obviously you can't do this if you wipe system), and download a rom from there. Otherwise you can download a rom onto your computer and then:
adb push /where/your/file/is/rom.zip /data/media/download
This will put the file from your computer to your download folder in your SD card. I'd recommend pulling any necessary files before you wipe userdata (such as music, pictures, etc) or you can pull the whole SD card (adb pull /data/media) and then cherry pick what you want to add back later.
SOLVED.
Wiped all with fastboot, pushed new rom with adb push and flash it.
Just to feel relaxed installed a couple of apps, gone back in recovery and tried to wipe data/cache/dalvick then re-flashed AOKP, everything is now working fine, the wipe erase all app and userdata now.
Hope this won't happen anymore.. thank you all..
fab2disco said:
SOLVED.
Wiped all with fastboot, pushed new rom with adb push and flash it.
Just to feel relaxed installed a couple of apps, gone back in recovery and tried to wipe data/cache/dalvick then re-flashed AOKP, everything is now working fine, the wipe erase all app and userdata now.
Hope this won't happen anymore.. thank you all..
Click to expand...
Click to collapse
Good to hear! Glad everything worked out for you. You can put [Solved] in the thread title so other people with the same problem will know what to do.
anton2009 said:
Good to hear! Glad everything worked out for you. You can put [Solved] in the thread title so other people with the same problem will know what to do.
Click to expand...
Click to collapse
I feel sooooo newbie, but.. how can I do that?
Backing up and restoring /sdcard is very time-consuming and usually unnecessary in these situations. It only takes a minute to fix the filesystem errors on /data and then you can wipe data as normal (in CWM, no need to use fastboot which also erases /sdcard). Just boot into CWM and in an adb shell:
Code:
e2fsck /dev/block/mmcblk0p12
Answer 'y' to everything if prompted. Done.
Jimmy Flip said:
Backing up and restoring /sdcard is very time-consuming and usually unnecessary in these situations. It only takes a minute to fix the filesystem errors on /data and then you can wipe data as normal (in CWM, no need to use fastboot which also erases /sdcard). Just boot into CWM and in an adb shell:
Code:
e2fsck /dev/block/mmcblk0p12
Answer 'y' to everything if prompted. Done.
Click to expand...
Click to collapse
Confirmed working.. Thanks a lot for your help. You are a life saver.
Help
I can't delete anything, i can't flash anything..
everything stay where it is, wipe or format doesn't work.. and my phone is stucked on infinite reboot..
please help!
Dobie999 said:
I can't delete anything, i can't flash anything..
everything stay where it is, wipe or format doesn't work.. and my phone is stucked on infinite reboot..
please help!
Click to expand...
Click to collapse
Try to lock the bootloder and if it fails, your phone is bricked...the emmc is broken.. try warranty

(Problem) system uid's inconsistent

Hey guys,just tried Tod flash the New codenameandroid Rom,but i geht a weird message after the reboot. Your system uid's are inconsistent.you need zog wipe your data partition unless your device will be unavailable. and just a button with i'm feeling lucky.tried Tod Format /data but it didnt help.
Also tried other Roms but same Problem.
After that i wanted Tod restore a backup via cwm but it stopped with: error restoring /data.
Could both relate To thr same issue?
I really dont know what to do now.
I googled the Problem but didnt find a real fix for that.
Hope someone has an idea.
Cheers
Gesendet von meinem Galaxy Nexus mit Tapatalk 2
try mount /data in recovery, wipe data/factory reset, reflash rom.
Sent from my i9250
Probably the cleanest solution HERE
Try flashing the factory image over fastboot. Make sure your device is unlocked, adb is installed on your computer, and your device is connected to your computer booted into fastboot mode. On the computer, load fastboot and type: fastboot erase system, then: fastboot erase data,and at last: fastboot erase cache. Then install the factory image by extracting it and running the flash-all script. If you still need help, see the google factory image webpage.

[Q] Hardware navigation buttons do not work on some ROMS after clean install

Hi,
I'm finding with some ROMs (SlimBean, ProBAM, CM Domination) after an install on my HOX that the hardware navigation keys don't work anymore. I have to enable the soft keys in order to be able to use the phone - obviously not desirable as it wastes screen space.
I've done a crapload of googling, searching the forums, etc and can only find info on disabling the buttons. Is there some obscure setting I am missing somewhere?
The process I use is the same as is recommended on most of the other posts:
- fastboot erase cache
- fastboot flash boot boot.img (of the rom I am installing)
- in CWM, delete userdata, format cache/dalvik
- install rom
- reboot
When the phone boots up - straight away the capacitive buttons no longer work.
Reflash with a different ROM (CM10, Blade) and they are fine.
Can anyone help?
Thanks
I've had that happen on probam/slimbean if I don't flash Gapps.
Sent from my HTC One X using Tapatalk 4 Beta
sinkster said:
I've had that happen on probam/slimbean if I don't flash Gapps.
Sent from my HTC One X using Tapatalk 4 Beta
Click to expand...
Click to collapse
Aha - thanks for the suggestion, I'll give it a go. From memory I probably hadn't installed Gapps at that stage since I was just checking the ROM out..
thanks man
Gapps would have no bearing on such a problem, coincidence. And to prove a point, gapps are included in the ProBAM rom and the fault still occurred. I would suggest you change slightly the method of wiping between roms.
From CWM recovery, format data,system and cache. Then mount usb storage and format the sdcard to fat32 from your pc or laptop, but change the allocation unit size from 16 to 32 in the dropdown. Then while usb is mounted copy over the rom, and gapps if required. Just to be sure wipe dalvik cache in recovery then reboot the bootloader and flash boot image in fastboot and fastboot erase cache.
Very important to erase cache in fastboot.
Once that is done, back to recovery and flash rom and gapps if required and your done. This is the method I use every day and never have a problem.
Just re-read OP and I noticed that you fastboot erase cache before flashing boot image, you must also erase cache after flashing boot.
sent from my shorts
nogotaclue said:
Gapps would have no bearing on such a problem, coincidence. And to prove a point, gapps are included in the ProBAM rom and the fault still occurred. I would suggest you change slightly the method of wiping between roms.
From CWM recovery, format data,system and cache. Then mount usb storage and format the sdcard to fat32 from your pc or laptop, but change the allocation unit size from 16 to 32 in the dropdown. Then while usb is mounted copy over the rom, and gapps if required. Just to be sure wipe dalvik cache in recovery then reboot the bootloader and flash boot image in fastboot and fastboot erase cache.
Very important to erase cache in fastboot.
Once that is done, back to recovery and flash rom and gapps if required and your done. This is the method I use every day and never have a problem.
Just re-read OP and I noticed that you fastboot erase cache before flashing boot image, you must also erase cache after flashing boot.
sent from my shorts
Click to expand...
Click to collapse
notgotaclue, thanks for the detailed response - I will most definitely give this a go when I get some time over the next few days. Cheers mate
@nOtgotaclue: I went through your process and it did work for me with CM10 Domination - but not ProBam or Slimbean, they still had the same problem with hardware keys not working.
I've ended up flashing another kernel (TripNDroid v15 AOSP) and it has fixed the issue (for SB at least, yet to try it on ProBam).
Thx again for your help

Bricked?

Im in desperate need of help.
My one X randomly locked up and on a hard reboot (held power button) it now no longer boots to CM, instead it boot loops.
On booting to recovery (CWM) I was presented with a black screen. So using fastboot I was able to flash TWRP 2.4.0.0 and successfully boot to it.
It opens with a password prompt to which I can click cancel and get to the options. This is where it complains things get complicated :/
If I try to wipe anything:
E: error unable to mount '/cache'
It will do the same with /data and /system.
adb sideload so far has failed me,
failed to write data 'protocol fault (no status)'
It seems once one attempt fails the phone seems to go into some locked status until the battery is fully drained and recharged. Which makes everything so long and tedious to troubleshoot.
adb push cm.zip /sdcard returns an error. But this is all in vain as I have cm10.1 on the /sdcard but twrp fails to flash it.
Any help would be greatly appreciated! Ive been without internets at work for days now :crying:
bump.
Update your twrp to latest 2.7 or whatever its near the top in development thread. Then fastboot erase cache, flash boot image for desired ROM fastboot erase cache, boot to recovery flash ROM then gapps, wipe davlic and cache, enjoy..
Sent from my alarm clock.
myheroduane said:
Update your twrp to latest 2.7 or whatever its near the top in development thread. Then fastboot erase cache, flash boot image for desired ROM fastboot erase cache, boot to recovery flash ROM then gapps, wipe davlic and cache, enjoy..
Sent from my alarm clock.
Click to expand...
Click to collapse
Brilliant mate. There was an option in 2.7 to repair the partitions. I had to set /data back to ext4 (even though it said it already was) then repair the partition, and voila. Its all working again

[REQ]Corupted Or A Brick Plz Help!!

Hi All Thank For Reading My Post I Have A Problem With My Nexus 5x I Need Help
My Problem Is The Following:
My Phone Won't Boot To Recovery,System and Download Mod
My Phone Can Only Run 4 Core
Android O Installed
Android O Recovery 4core Installed
Android O Kerenel 4 Core Installed
My PC Sometime Detect It As Qualcomm HS-USB QDLoader 9008
This Happened To My Phone After TWRP 3.1.1 4 core Get Stuck On Installing And He Won't Turn On Again I Have Try A Factory Image But Won't Work Android M,N And O All Haven't Work
I Think TWRP Cause Corruptions Or Something Like That
If Any One Know How To Fix Tell Me Ok
Help Is A Good Action
Thanks
Sofiane omega said:
dose any one here know how to fix corrupted partition I can't boot my phone I can go to fastboot but the phone won't boot to recovery
if any one know how to do help me
Click to expand...
Click to collapse
Try flash the recovery (You can extract the recovery image from the factory system image file) from fastboot. Then sideload the factory image from recovery.
truekasun said:
Try flash the recovery (You can extract the recovery image from the factory system image file) from fastboot. Then sideload the factory image from recovery.
Click to expand...
Click to collapse
I've already try it,
My phone is a bootloop devices I have only 4core an I've already try all the 4 core recovery and kernel,
twrp cause this after getting stuck on an installation my phone turn off and after that I've try to turn it on again he begin to bootloop and get suddenly brick,
I think twrp cause corruption to my partitions .
Sofiane omega said:
I've already try it,
My phone is a bootloop devices I have only 4core an I've already try all the 4 core recovery and kernel,
twrp cause this after getting stuck on an installation my phone turn off and after that I've try to turn it on again he begin to bootloop and get suddenly brick,
I think twrp cause corruption to my partitions .
Click to expand...
Click to collapse
if you can boot into bootloader you can try to fastboot erase boot, recovery, system, vendor, userdata, cache, and try then flash the manualy one by one (not from the ota zip)if the partitions are corrupted this will delete them and when you flash them again the will be recreated note that userdata and cache partition dont exist in the factory images so you need to create them with the command fastboot -w if you need any more help feel free to ask more things
kastik4 said:
if you can boot into bootloader you can try to fastboot erase boot, recovery, system, vendor, userdata, cache, and try then flash the manualy one by one (not from the ota zip)if the partitions are corrupted this will delete them and when you flash them again the will be recreated note that userdata and cache partition dont exist in the factory images so you need to create them with the command fastboot -w if you need any more help feel free to ask more things
Click to expand...
Click to collapse
I try it and it won't work

Categories

Resources