Related
Hello guys,
I have a little problem which seems to be coming when I move the dalvik cache to the EXT partition of my device.
I am using the latest version of MIUI. It has A2SD built in, but it doesn't seem to be working. It was working before though...
What happened:
I restored the NANDROID backup of the stock ROM I had made before flashing MIUI. Once I booted into it, it warned me about the 2.3.4 OTA update. I did it, but forgot that it overwrites the bootloader, removes root and I will not be able to revert to MIUI.
I pushed the Clockwork recovery and immediately started restoring the NAND backup of my MIUI ROM. Without gaining root on the Stock 2.3.4 ROM.
The Dalvik was moved to the EXT on the MIUI I was trying to restore and functioning properly.
The restore went fine, until it got to restoring the sd-ext. It stood there at some *.tmp file for an hour or so. I removed the battery, booted into recovery, wiped and started the restore again. This time it finished, but when I went to start the phone, it got stuck at the Nexus logo, not even showing the MIUI boot screen.
Wiped again. Tried booting into a previous backup, which didn't have the Dalvik moved to the EXT partition. Restored and booted just fine.
I tried several more times restoring the latest backup I had (the one with dalvik to ext) and got the same result.
Then I tried installing the MIUI backup that didn't have Dalvik moved to EXT and tried moving the Dalvik to EXT. The phone rebooted and same thing happened. Didn't want to get past the Nexus logo.
I then wiped everything except batt stats, formatted ext, and flashed the MIUI ROM. It booted perfectly, but A2SD was not working, just like before (solution was to move dalvik to sd). I downloaded the A2SD GUI only and moved the dalvik to EXT AGAIN. And AGAIN - not booting past Nexus logo.
The only thing I still haven't done is formatting the SD and re-creating the EXT partition.
Any other suggestions on what may be causing this and how to fix it?
I want to have a2sd on this ROM and moving the dalvik to EXT seems to be the only way of achieving this.
Repartition SD card, you've most probably corrupted the EXT partition by pulling the battery.
Do you think that restoring the last MIUI backup I had after this will do the job?
After repartitioning? As long as you back up the files from the main FAT32 partition on the computer, and restore them back - the EXT will be overwritten when restoring nandroid anyway.
Well.... I just formatted the card with Panasonic SD formatter. Transfered only the nandroid backup (without creating an ext partition beforehand) and restored it successfully, but when the phone starts booting it is stuck at the Nexus logo.
I also checked the MD5 of the backup and everything is fine.
Godzi said:
Well.... I just formatted the card with Panasonic SD formatter. Transfered only the nandroid backup (without creating an ext partition beforehand) and restored it successfully, but when the phone starts booting it is stuck at the Nexus logo.
I also checked the MD5 of the backup and everything is fine.
Click to expand...
Click to collapse
Wipe Cache and dalvic. Than try again. Your System Need a ext wenn you push dalvic to sd before.
I ran out of options.
Formatted the card, tried restoring - Nexus logo
Wiped Everything + Dalvik and Cache, restored - Nexus logo
Wiped Everything + Dalvik and Cache, didn't restore old MIUI backup - successful boot. When I tried to move Dalvik to EXT after the successful boot - Nexus logo after restart.
If anyone can suggest anything... Because this way I have no access to the A2SD on the device with this ROM. And everything was working fine before I restored the Stock Ginger.
Did you try installing DT on any other ROM and try and move dalvik to the sd to see if it does the same thing?
Dude Random21 said:
Did you try installing DT on any other ROM and try and move dalvik to the sd to see if it does the same thing?
Click to expand...
Click to collapse
No. I haven't tried with another ROM. I guess I will try CM7 and see what happens when I move the Dalvik to the EXT.
I repartitioned once again, this time using the same EXT size as before the breakdown (512MB). When the backup I am trying to restore was made.
Was using 1024 when I partitioned previously and got the Nexus logo again.
Edit: Same thing. Successful restore and then the Nexus Logo.
I suspect it's the ext partition. Why don't you try formatting through recovery, and do a clean install?
Which recovery do you use? I would avoid Clockwork 3.x...
Well. I formated using Panasonic SD Formatted and then partitioned using the recovery. I did a clean install after that and as soon as I move the Dalvik to the EXT, I can't boot past the Nexus logo.
Yes, Clockwork 3.x. I guess I will try Amon_RA as well. Nothing left to lose.
If you partition with Amon Ra, make sure you up the partition from ext2 to ext3 (available through the Ra menu options)...
Ok. Partitioned with RA.
Tried to transfer the nandroid backup made by Clockwork to a sd/nandroid folder so I can restore it from within RA but it kept giving out some error telling me to look at the recovery log when I selected *.img files from the list.
Good news. I booted into MIUI and installed a2sd GUI. Moved Dalvik to EXT without a problem. I guess Clockwork's partitioning is flawed. Everything is working fine now.
Thank you.
Can anyone suggest a method I can use to restore the Clockwork made NAND backup + the EXT backup now when my partitions are finally alright.
Any method would be fine. Even manual through adb. I don't care. As long as I restore my phone to yesterday.
Thank you guys once again.
You should be fine if you load a clockwork prior to v3.x. I think 2.5.1.4 was the latest version prior to the v3.x series. The issues only arise with v3.x.
But only clockwork is able to restore clockwork backups, and the same goes for Amon_RA.
As an alternative, you can just extract the img files and manually load your data back on. It is definitely more time consuming, but it wouldn't matter what recovery you use. It has been a while since I extracted anything from the img files, and when I did, I just got the data from apps stored on the internal (apps and dalvik were stored on the sdcard), and I think the only program I used was unyaffs2 to extract the data.
Thank you guys!
Partitioning the card with Amon_RA and restoring the old Clockwork-made backup with Clockwork 2.* worked perfectly.
I will not use Clockwork ever agian. Putting Amon_RA and that's it.
You will only have this problem with clockwork 3.x - there doesn't appear to be the same issue with clockwork 2.x
I have been using v2.x without any issues (never upgraded to v3.x). I prefer it because it gives me the option to wipe the /system partition, whereas Amon_RA is missing this feature and you can only do it with a flashable zip.
I use 2.x for a number of reasons. I tried 3.x a few times, but always had ext issues on my N1. Having said that, I've used 3.x on my nook, MT4G and G2, and never had issues with them - just on the N1...
I've used RA 2.2.1 on CM7, MIUI ,Sense rom. I never seen sd-ext issues on my Nexus One.
This is related to http://forum.xda-developers.com/showpost.php?p=44237167&postcount=39259
Problem:
Stuck at bootscreen after installing Roboto 4.3 via Rom Toolbox Pro. I'm on ARHD 12.0.
Fastboot erase cache, full wipe, dalvik wipe etc. pp didn't help.
ADB-Sideload also didn't work due to a mysteriously & out of the blue non-mountable internal SD. Something was borked when I installed the new typo, dunno how and why.
So, re-flashing ARHD from my laptop wouldn't work, furthermore I deleted ARHD.zip from my internal SD; but anyway, the SD was to no avail -> no chance to grab a Nandroid.
Solution:
I firstly changed the recovery on my black lady by flashing TWRP in order to substitute CMW. TWRP allowed me to access and mount an USB-OTG, which hasn't shown up on CMW (v6.0.3.4) at all.
So, finally I placed the ARHD.zip on the external drive, mounted the drive and flashed the ROM 2 times, as the first flash freezed on 20%. But then it went throu, the ROM settled down and the bootscreen stuck was gone.
(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.
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.
Hello and greetings from germany,
I have a problem with my Moto G 2014 XT1068. I'm coming from rooted stock KitKat (Xposed) with open bootloader and TWRP 2.8.6.0. Everything seemed fine until yesterday, when the phone just went off (0% battery) and stayed at boot animation.
I've tried a lot of things, but the phone seems to be hardbricked:
- I can access recovery, but restoring does "FAIL" (restoring boot partition works, though). Restoring "system" aborts at about 18%, "data" immediately.
- I can access the phone through fastboot, but cannot flash anything. Whatever I do, the phone isn't changed. Tried reverting to stock (getting error when flashing gpt.bin, everything else seemed to work without errors, but no changes), tested flashing other recoveries (partition size mismatch, but that seems to be normal, whatever I flash, it keeps being TWRP 2.8.6.0), or even upgrade the bootloader (no errors reported at all, but no changes made to the phone).
- I can access the phone by MTP from TWRP, but cannot write to or delete anything from the internal SD.
Do you have any further ideas or is it an hardbrick?
Thanks in advance
René
Seems like the internal SD card is damaged, or there's a faulty partition table. Have you tried repairing and formatting /system and /data partitions with TWRP? Does it read external sd cards? If yes you could try flashing CM11 (because lollipop roms need an updated bootloader) from an external sdcard and see what happens. Also your backup could be corrupted, that's why it doesn't let you restore it at all.
As for the recovery, try updating your twrp to the latest version available (3.0). You can update twrp from twrp itself, just to see if it's fastboot's fault.
Wiped /system and /data. Didn't help. Wiping /data/media led to an error.
Is there anything beyond "wipe" to repair and format those partitions?
Thanks for the hints, will try updating TWRP and installing 11 this weekend, as external SDs can be accessed.
Greetings from Germany
René