Hey guys, I just got a Hero after switching from Android to winmo for a while, so I've been out of the loop since 1.6. I was able to get the phone rooted no problem, got the custom recovery image on it, got it to tether, even installed busybox. The only thing I can't seem to do is load a custom rom. Whenever I put any rom on it at all it gets stuck looping the boot screen. I tried 4 different roms, none work. The only way I can get it to boot after a custom rom is to do a nandroid restore since I backed up right after I rooted it. I've tried partitioning the sdcard from the recovery image as well, once with a swap and ext partition for apps added, and once with just the ext partition, neither of them had any affect. Anyone have any ideas on what else to try?
Solved
For those with this problem in the future, it was being caused by a2sd on my phone, specifically the dalvik cache. I did the following from the latest a2sd post:
"If you experience boot loops when you move the dalvik-cache to the cache partition, go into adb shell while the phone is boot looping and run the following commands:
a2sd nocache (if you want to put your dalvik-cache on your internal storage) or a2sd cachesd (if you want to put your dalvik-cache on your SD card)
a2sd resetcache (this clears the dalvik-cache and reboots)"
Then I ran logcat as the phone booted up to watch to make sure it didn't loop, and it took it a while but it did start up into the custom ROM.
Related
Howdy friends. I recently rooted and installed cyan 4.0.1/teds hero. Everything was going smooth until about 20 min ago. The messaging app kept force closing everytime I would open a thread, so I rebooted. Upon startup, it said my sd card is now damaged. I clicked format, and nothing happened at all. what's the solution? Any help would be appreciated.
i assume your doing auto apps 2 sd with an ext2/3/4 partition? go to recovery and repair ext filesystems. that should fix you up.
I did nothing beyond rooting / cyan / teds hero.
christpuncher said:
I did nothing beyond rooting / cyan / teds hero.
Click to expand...
Click to collapse
k. if you did not partition the sdcard, then take the sdcard out of the g1 (unmount it first in settings), and put it in your pc. try to get the data off of it as best that you can. repartition and format as fat/fat32. put the data back on it, then stick it back in your g1 and see if you can access it, etc.
good luck.
your sd card corrupted, gonna have to reform it, if you install the recovery image from the mytouch that is floating around in the android devolpment forum under new recovery that has an option of reformating your sd card.into 3 partions that would work for you than reflash your rom and theme
here is the link to it. just use in terminal (after putting on root of sdcard also make sure that cyanogen's 1.4 is on the root of your sdcard as well, also for safe keeping have your cm 4.0.x rom on sdcard too)
Code:
su
flash_image recovery /sdcard/recovery-RAv1.2.1G.img
reboot recovery
then once it boots into recovery use the option to format your sdcard into 3 partitions then once it is finished reflash your rom to activate apps2sd, then once it boots up go to the terminal and type
Code:
su
flash_image recovery /sdcard/cm-recovery-1.4.img
that way you will have easily partitioned your sdcard, got apps2sd workning, then return to a recovery image with a recovery console!
I agree with you on having a recovery console but that mytouch recovery is a great way to point noobs since it will easily partion the card for them
gridlock32404 said:
I agree with you on having a recovery console but that mytouch recovery is a great way to point noobs since it will easily partion the card for them
Click to expand...
Click to collapse
thats why i included the steps to going back to the 1.4 recovery after using maybe cyanogen will look into this for his next recovery image. i also sent nephron a pm to see if he would like to include it into his partitioning guides
I hope he does make it into 1.5 for us because it just his 1.4 with some great additions and just missing the console
I have a 8 GB class 6 SD card with an ext2 partition that I created while running JF 1.51. I also used LucidREM to move everything over, but then moved my dalvik cache back to internal memory.
Following JesusFreke's retirement, I flashed Cyanogen 4.0.2 (stable). After encountering a boot-up loop, I wiped my phone and almost everything seems working fine.
The problem, however, is that my apps now seem to be installing to my internal memory instead of my partition. I'm pretty new at this, so I'm not really sure what's going on or how to fix it. Help please.
Use cyan 4.0.4, the most recent build. Open parted from command line and type print, just to verify you have an ext partition. Most likely you don't have an ext partition because the rom does it automatically.
The parted command implies you have cyan's recovery 1.4.
My G1 is running AmonRA 1.7.0 recovery and I recently switched from OpenEclair to Cyanogen 5.0.8. But when I wiped to factory reset/data wipe and installed the new ROM, all the applications were still there from the earlier ROM. I wiped ext partitions, cache and everything. I even tried partioning the SD card through the recovery, but it still lingered there. Anyone know what the problem is?
RodrigoKim said:
My G1 is running AmonRA 1.7.0 recovery and I recently switched from OpenEclair to Cyanogen 5.0.8. But when I wiped to factory reset/data wipe and installed the new ROM, all the applications were still there from the earlier ROM. I wiped ext partitions, cache and everything. I even tried partioning the SD card through the recovery, but it still lingered there. Anyone know what the problem is?
Click to expand...
Click to collapse
Yep. You didn't wipe one of either the ext partition or the userdata partition.
Use cyanogens recovery that has a console... then you can check type the scripts with the hard keyboard and check your work...
To wipe the ext partition:
mount /system/sd
rm -rf /system/sd/*
To see what is on the ext:
ls system/sd
Does nobody use switchrom.sh anymore?
-------------------------------------
Sent via the XDA Tapatalk App
will try that, thanks.
usually i use the console, but the options in the 1.7.0 recovery looked convenient and thought it would do the same thing as the commands on the console.
if you have found that you have wiped all sections in the recovery and the apps still appear. try going into your privacy settings and unchecking the option to back up system data to servers, then do a wipe.
I've been crawling forums looking for several ways to partition my SD, but to no avail.
Recently upgraded from damagecontrol 2.08 to 2.09. Bought a new 8gb micro SD.
I'd like to partition the SD card so that Apps2SD runs, and I remember the first time I rooted my phone and loaded a rom, there was an option in recovery to partition the SD card. Now, my phone boots into clockworkmod recovery v1.8.1.4, and the list of commands doesn't include a card partition option.
How can I get this option back?
I resorted to using adb and trying to work around this problem through the command line, but all of those attempts failed. "parted not found" etc.
I'm at my wit's end and my school work is suffering! (I'm crazy if my phone is not working perfectly) PLZ help this girl stay in med school!
you could flash back to godspeed or darch's unofficial 1.7 recovery found here both these recovery images have the option. clockwork must not support partitioning.
or, you could take your card out and put it in your pc and use a gparted livecd (or linux) to partition the card.
remember to backup your data first as re-partitioning will erase all data on the card.
I'd love to flash a new image, but my phone doesn't seem to allow me to. I use flashrec and it won't flash a new image.
Here's the chronology of my troubles
What I did with my rooted and fully functioning hero was...
back up apps
changed SD cards
set to factory settings via an option of the clockwork recovery
updated my rom to damagecontrol 2.09
found that apps2sd wouldn't work
tried to partition- clockwork recovery doesn't support it
tried to get back SU capabilities unsuccessfully
tried to mimic my first flash attempt unsuccessfully with flashrec
Now I'm stuck with a slowed down hero which can't allow Su and won't do apps2SD
I'm at the point of insanity with this thing
any suggestions?
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.