(For reference, I have a MAG2GA FW v6 dated 10/2012) -- yes, I have access to CWM and ADB
Had verygreen's CM11 (1-18, eMMC install) on my HD+ and it was working without any major issues -- came back home one day and the screen was frozen. Did a power + N button reboot, and now the CM logo on boot spins incredibly slowly (completely hanging at several points). After a few minutes it will either bootloop or get into CM11 -- if it does make it into CM11, the system will be very unresponsive and eventually reboot on its own [no matter what I select].
Booted into eMMC CWM 6.0.4.6, formatted /system, /data and /cache and reinstalled CM11 1-18 + PA GAPPS. On reboot, I see the exact same behavior (slow/freezing CM logo, eventual bootloop). When it does sometimes make it back into CM, I see my widgets / wallpaper for a brief moment before it bootloops again, implying that my format/wipe in CWM did nothing...?
I then booted into bokbokan's CM10.1 I had on a MicroSD lying around -- I installed the eMMC brick check app from there (which checked out fine, including a test on the full 16gb). I'm trying to do an ADB push now of leapinlar's NookHDplus-factory-2.2.0-plain-stock.zip so I can install it and try to get it replaced under warranty but it either [tried both SD-based CWM and eMMC-based CWM] :
1 - hangs forever (implying some issue with my internal storage)
2 - says transfer complete, but when I navigate to /sdcard/0/ I don't see it
3 - the one occasion I did manage to transfer stock back over and the system could actually see it, I got a '"Failed to retouch '/system/lib/libemoji.so'" error when installing (and yes, I'm formatting /system every time)
In additional, the eMMC CWM behaves very erratically, sometimes taking over a minute to navigate through folders or respond to a volume button click. Pretty sure my internal storage is damaged somehow.
It seems like no matter what I do in CWM, my HD+ continues to try to reboot back into my old CM11 installation. Any thoughts or ideas on what I can do next?
Edit: Okay, so using a 4GB SD card image, I tried to erase /system, /data and /cache and flash cm 10.1 and twrp just to see if anything would stick. Removed the SD after flash, reboot, and the system goes right back into CM11 boot loop. Trying to reboot into TWRP brings 6.0.4.6 back up -- looks like nothing I'm doing will stick. Brought up ADB shell and ran "mke2fs -T ext4 /dev/block/mmcblk0p8" to wipe system, still reboots back into CM11 no matter what I flash in SD CWM.
226 68565523
I have the same issue, but on my HTC One S. My eMMC chip: MAG2GA.
Looks like its TRIM brick.
I can't wipe or install other rom, and recovery allways say "E:/can't mount /data"
My system works well, but after reboot the system returns to its previous state and all new data (SMS, calls, files) delete.
All it happens after 27 January after installing nightly update for CM11
Leapinlar has the knowledge and info on fixing the partitions. Might be just refreshing them up might fix it. Trim bug can also cause physical damage... don't know which that could be here if its it.
I've played a few minutes with the 29th(?) nightly and had not received this problem though that build had quite a few issues for me. So Korshun could be on to something.
Just swapped it instead -- seems like physical TRIM damage, given that nothing I changed [even writing 0s to disk] would stick.
Related
I had a Nook setup with Dual Boot (not using an SD Image) and now I am trying to restore the device back to factory settings.
I've been trying to do a full factory restore (removing my root) to my Nook Color.
I've used this ROM http://forum.xda-developers.com/showthread.php?t=959461 to remove the dual boot and reparition.
I've formated EVERY partition (except SDCard, which seemed like a bad idea if I booted from it).
I've created a bootable Clockwork Recovery MicroSD Image (3.0.2.8). I can boot from this fine.
I've tried 3 different factory ROMS (1.0.1, 1.2, 1.3, etc) and I can get them all to install and boot up.
However I can't get past the "B&N registration screen". I always get an error registering the device.
When I select "Shutdown" the device, from this screen, I believe I can STILL see the "soft keys" on the bottom of the screen, which makes me feel like the Android system is still "hacked".
Have I restored this correctly? Is there some reason I can't register the device with B&N?
Are you sure /data is getting formatted? Watch it carefully at that step. If you're using an older Clockworkmod, it will fail with newer Nooks due to filesystem changes. IIRC cwm3.2.01 is the latest. I had the same symptom, realized /data was not formatting and tried with a newer version and had no problems restoring to 1.3.
Use version 3.2.0.1 of CWR found here: http://www.multiupload.com/N5C1846GH3
Wipe everything and then install this stock 1.3 .zip: http://www.multiupload.com/3Y5MWE773D
It was mostly working fine.
Would reboot occasionally, twice a week?
Never in a call and was quick to boot so didn't think much of it.
Then one day all apps suddenly went Force Close.
Powered off.
Turn off, stuck on logo.
Booting into recovery the problem becomes apparent.
Trying to mount data/backup I get, Error mounting /data
hardware
HUAWEI U9000-81
Baseband
2.6.32
Firmware
Cherry MagnumHD (Android 2.3.4)FB0-318D-0-5019-A03
Recovery
CWM-based Recovery v4.0.1.4
Booting into download mode (vol up & pwr)
The flash memory mounts ok.
Running a surface scan with a disk utility (HDDScan-3.3)returns no errors.
Browsing with a EXT browser (ext2explore) I can see files and copy them to the PC.
attached pc screenshot
Found some instruction for a full wipe and reload but I wanted to attempt to save my data first.
At least my messaging history.
edit:
Found the sms db and copied off.
data/data/com.android.providers.telephony/databases/mmssms.db
Will now try a full wipe and reflash.
Does not look good.
SUTL3_v1.7.9
fails with a error
QPD_ERROR_DMSS_SET_NV_RESTORE_FLAG_FAIL (0XF6A0)
Bad nand?
I installed TWRP and CM10.1. All was going well, except the CM logo just spun forever.
I figured I may have to wipe again since it's worked on many past devices.
The only problem is, TWRP cannot access the E: location. I tried booting both WITH the sdcard and WITHOUT the sdcard. I get the same result every time.
EDIT: When booting cyanoboot (emmc-cwm-early2), it still tells me I do not have root access. I suspect this could be the cause of the first problem, but why will it not root properly?
EDIT 2: I continued messing with formatting /data, and making sure the root reminder stopped popping up. I flashed CM10.1 one more time and took out the SD card(after unmounting it of course) and it worked! Time to go hunt down gapps.
Moderators, archive or do what you need. I suspect this was just a fluke on my own part. Please note, I never had to flash TWRP or anything after the error occurred. It was all involving the CM10.1 zip.
I wanted to update my sister's Nook HD+ to CM11. I don't have an SD card big enough to do a nandroid backup, so I tried to back up to the internal SD card. It was working fine, then it said "backup of /data failed". I thought this was because the internal SD card ran out of space. When I tried to reboot, it found that it's stuck in a bootloop. It goes to the nook screen, then the Cyanoboot screen, then starts loading Cyanogenmod like normal. The boot animation plays then freezes, and the device reboots. I've tried clearing the cache and dalvik cache and it gets a little farther, but it's still in a bootloop. Please help! I would like to avoid doing a factory reset if at all possible.
If internal space was maxed out, would a factory reset even work any better?
If only booting is corrupted, you should just be able to simply dirty flash the same rom build or newer to fix without losing anything.
I don't know where nandroid backups are made internally but if they are accessible via usb on a pc, then you could just delete those files. If it is indeed full storage. And then dirty flash the build again if needed.
There's probably some other ways to go as well.
After my succesfull CM 13 install attempt and 1 day of use, when I turned it off and turned it on again, it would boot normaly, the CM 13 logo keeped pulsating, but after some seconds, it suddenly stopped pulsating and crashed. Is there a way to solve this, or do I just flash my backup (before CM 13 install)? Preferrably, I wanted to keep my apps.
Did you change anything on system partition? If you haven't done anything then it's hard to say that it can be fixed without a data wipe, but you can try to wipe system, cache and dalvik-cache partitions then flash CM and Gapps.
I wiped the system, cache and dalvik-cache, flashed CM and Gapps. It then booted into CM 13, the logo appeared for a few seconds, it showed the "aindroid is starting - optimizing app (2 of 19)" screen, it went all the way through the 19 apps and then it turned off, I rebooted it and it did the same logo crash thing.
UPDATE: it seems that on the logo crash, technically the device is still turned on, cuz' i leaved on that state for a while without pulling off the battery (the only way to get off that "state"), pulled off the battery, rebooted into TWRP and the battery had decreased
So the problem is probably in data partition. Unless you have a clue to what to erase using recovery"s file manager, adb (if it's enabled) or a previous backup then I think you will have to wipe data. With adb you can try to use logs to search for the cause.
PS: do you have a microSD inserted in your phone? Did you try booting without it?
After I runned some tests, apparently the cause of all this was the microSD that I formatted to be an Adopted Storage. It crashed whenever I put it on the device. Now just gotta find a way to format the microSD for me to get it back (Already on my way, any help would be appreciated).
Here's the correct tool to format a SD card:
https://www.sdcard.org/downloads/formatter_4/
Don't use fast format, use the configuration that tests the whole card memory.