Database Develop

Why would my hero be completely stable on 1.6, but reboot frequently on any 2.1 rom?

I am extremely frustrated at this point so I have decided to make a thread.
My hero has been a good phone and runs 1.5/1.6 roms without any problems, and has for 6+ months. However, as soon as the 2.1 leaks came around, I was eager to try them. NONE of them will work. I have tried 6 or 7 different versions. My phone will shut off very frequently, which essentially makes it unusable.
Has anyone else experienced this and was able to fix it, or otherwise have any advice for me?
Any help would be greatly appreciated.

pixie dust!!!..jk
I have no idea why.. have u wiped everything and flashed?

spiritcrusher33 said:
pixie dust!!!..jk
I have no idea why.. have u wiped everything and flashed?
Click to expand...
Click to collapse
Haha. Yeah man, factory reset + dalvik cache wipe. Would a bad SD card cause something like this?

sounds like you didn't properly wipe... once you wipe EVERYTHING.. (after a nandroid).. you shouldn't have problems installing any ROM whether it be 1.5, 1.6, 2.1, 4.2 (coming to the htc hero6 in 2013)
edit: you mentioned factory reset... are u doing the factory reset thats installed in the settings menu or are you wiping everything from recovery?

Have you tried to go back to 1.5/1.6 to see if the problem occurred? This might help eliminating the hardware issue.
Which ROM did you tried? The latest one that I ran which is stable (no over clocking) is Fresh 2.1.1, look for this thread title "[ROM] 05/14/10 | Fresh Rom 2.1.1 | Official Sprint RUU + The normal fresh rom goodies"
I have always do this when installed the new ROM.
-Back up all your private apps (not system apps) with Android Commander (search the forums) to your PC.
-Use Recovery and wipe the followings:
1. Wipe Factory / Data reset
2. Wipe Dalvik cache
3. Wipe EXT partition
4. Wipe Battery Stat
Trust me this will save you a lot of hassle and time.
- Re-Installed all your Apps from Scratch using Adroid Commander. This always work best for me. I found less problem and less time consuming doing it this way.
Most of my problems occurred when I am too lazy to WIPE and install new ROM on top of the OLD one with out wiping dalvik and ext partition. An this make it more time consuming.
That's my experience. Hope this help.

roadster92 said:
Have you tried to go back to 1.5/1.6 to see if the problem occurred? This might help eliminating the hardware issue.
Which ROM did you tried? The latest one that I ran which is stable (no over clocking) is Fresh 2.1.1, look for this thread title "[ROM] 05/14/10 | Fresh Rom 2.1.1 | Official Sprint RUU + The normal fresh rom goodies"
I have always do this when installed the new ROM.
-Back up all your private apps (not system apps) with Android Commander (search the forums) to your PC.
-Use Recovery and wipe the followings:
1. Wipe Factory / Data reset
2. Wipe Dalvik cache
3. Wipe EXT partition
4. Wipe Battery Stat
Trust me this will save you a lot of hassle and time.
- Re-Installed all your Apps from Scratch using Adroid Commander. This always work best for me. I found less problem and less time consuming doing it this way.
Most of my problems occurred when I am too lazy to WIPE and install new ROM on top of the OLD one with out wiping dalvik and ext partition. An this make it more time consuming.
That's my experience. Hope this help.
Click to expand...
Click to collapse
Couple of questions. Is wiping the ext partition wiping your SD card? Also, how do I wipe the battery stat? I just booted to my recovery mode but I didn't see that as an option. Maybe I need a new flashrec or something?

splayde said:
Couple of questions. Is wiping the ext partition wiping your SD card? Also, how do I wipe the battery stat? I just booted to my recovery mode but I didn't see that as an option. Maybe I need a new flashrec or something?
Click to expand...
Click to collapse
what recovery rom are u running? and no wiping the ext partition is not wiping your SD card... just the partition you created..

dont wipe the battery but wipe the sd ext.
the sd ext only wipes what apps you have installed when you partition your sd card. it doesn't remove music, picutres, etc...

splayde said:
Couple of questions. Is wiping the ext partition wiping your SD card? Also, how do I wipe the battery stat? I just booted to my recovery mode but I didn't see that as an option. Maybe I need a new flashrec or something?
Click to expand...
Click to collapse
The one I am using now is overclock. But the previous one that I used is "recovery-RA-heroc-v1.6.2-blue.img"
You might have the older version. Battery Stat Wipe is just reference for me every time I using a new ROM to see how the battery life is.
As mentioned above, wipe EXT partition will not wipe any pictures or data on the FAT32 of the SD card.

im having a similar issues i cant get my phone to stop restarting. ive wiped everything you can even repartitioned and it sill does it.
are we doing somehting wrong?
i have a thread i started not seeing this one.
http://forum.xda-developers.com/showthread.php?t=684727

check the hardware
As someone suggested, please be sure to rollback to 1.6 to rule out a hardware problem.
I have a battery -- one of four in rotation -- that consistently reboots the phone after it draws down to 80% or so. This is probably the battery that I misplaced and didn't use for a few months. Before I pinned the problem down to this particular battery, I thought 2.1 was haywire, rebooting all the time. Once I pulled the battery out of rotation 2.1 became relatively stable again.

[Q] Why would you Wipe Boot Partition?

Hello,
I am about to install CM7. I currently Have Nookie Froyo 0.6.8 with CWM 3.0.0.5. I believe I need to update to CWM 3.0.1.0 first. Do I need to wipe / format the boot partition first or will the update to CWM / CM7 do that? What data lives in boot curerntly and what would be a situation / reason for wiping the boot partitition? When is it ever done?
Thanks in advance!
~J

you should not wipe boot when installing cm7

mooja said:
you should not wipe boot when installing cm7
Click to expand...
Click to collapse
What would be a situation / reason for wiping boot? When is it ever done?

OK. thank you, but what would be a situation / reason for wiping the boot partitition? When is it ever done? I'm trying to learn about all aspects of rooting / cwm.
Thank you
~J

Not needed,running cwm will handle everything. Also the boot should stay so that SD keeps priority for recovery reasons.
There is a ROM Manager option to wipe data/cache, this should be done if changing rom types (ex nookie to CM7) but isn't usually needed between minor versions of the same rom unless issues arise.

It wipes the boot sequence, doesn't matter what rom you're going too, you need the boot data.
I've wiped it twice. Both times required I restored to stock before moving to a custom rom. Just wipe data and cache, and you'll be fine.

when going from nookie Froyo to CM7, you are changing the file system from EXT-3 to EXT-4. Remember to format /system /data /chache, and wipe Dalvik-cache within CWM 3.0.1.0 before installing the CM7 rom. By formating the three partitions in CWM 3.0.1.0 you upgrade the file system.
There is almost never a reason to format /boot. You will only cause problems that are annoying to fix.
Remember to do a backup in CWM before you format and flash CM7. You never know.

Moving Dalvik cache to EXT - unable to boot

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.

[Q] STUCK A

got my nexus one week back.its rooted .it has rapassion recovery 2.2.1 and HBOOT v0.35.0017.i wated to try my hands on flashing.so i downloaded [ROM][2.1+3.0/2.3.3] Rev0lutioN v2.8 followed the steps wiped data,done partition swap size 0 and ext 1 1024 mb ,selct ext2 ext2,then ext3 ext 4.then flashed the rom from sd card .but on rebooting it is stuck @ NEXUS ONE X IMAGE .pls show me some way to flash sucessfully i can get back to that fastboot,recovery etc page by volume down and power button

i would dl this to sdcard and flash a couple times thru recovery before flashing rom. wipe dalvik and battery/rotation settings too
http://dl.dropbox.com/u/28338566/Extreme-wipe.zip
not wiping system can cause issues
assume you met ALL other rom requirements
also i don't reformat sdcard while in phone--use sdformatter
the first thing i do when i get stuck is pull battery and reboot--not sure if you tried that

thanks..i will try that...does it matter well i was trying to flash nand version may be that caused problem..one more help can u pls guide me to how to do 1gb ext4 partiton..or sugget me some stable sense version for nexus i can flash easily

if you are new as indicated by one week ownership, i would start out with cm7 stable roms from android development section
use the system wipe zip i provided
sounds like your card is already partitioned
best thing to do is read up in wiki and as much of rom thread you are going to flash, the op page has good info and i usually read last few dozen pages
if you flashed nand version, assume you flashed blackrose hboot and repartitioned
hboot to recommended sizes per op page link, if you did you will have to go back to stock hboot to flash cm7 or try sd version of rev rom
i had surgery and not feeling well tonite, let someone else come along to add to my posts
ken

feeling a bit better, here is quick answer
backup sdcard
i use sdformatter to format outside phone--full erase and size adj on
http://dl.dropbox.com/u/28338566/SDFormatter 2.0.mht
this ensures card is fully formatted--phone just does quicky
then put card back in phone and use amon ra to repartition card to 1gb ext 4 0 swap
seems you did those steps already
then copy sdcard data back to phone

create ext4 for use with a2sd

hi,
i'm usin ra passion 2.2.1 and wan't to use a2sd from ics 4.0.3 evervolv. how can i create a part ext4?

Google:
"a2sd partition sd card".
Enjoy.

Try 4EXT recovery www.4ext.net
I think its the easiest way to create partition.
Or else you can do it in pc via partition managers(i use minitool partition wizard)
You can google it and also can search in youtube for video tutorials.
Sent from my Nexus One using Tapatalk

thanks for your help, i've done it in recovery.
one question is left:
what happen if i format the partioned sd-card under windows and do a full wipe in preparation for installing a new rom. i've read sd-ext even survive a full wipe? what does that mean? stays the partition untouched when i format the sd-card with windows? and what about the apps in the partition? are they still there even after a full wipe and can i use them after flashing a new rom out of the box?

Glad u succeeded in partitioning
Now if you format the fat32 partition in windows using those partition tools doesnt affect ur ext. Ext stays untouched but all the data on fat32 will be wiped(so backup first to pc)
If u want to merge there is an option called merge for that.
There is an free windows software called sdformatter, that formats the entire sdcard(fat32+ext)
Hope i helped a bit :thumbup:
Sent from my Nexus One using Tapatalk

ok. i wan't to format it with the windows internal function via right click. is it the same and the ext4 stays untouched?

Full wipe in recovery wipes SD-EXT too.

heinz gruber said:
ok. i wan't to format it with the windows internal function via right click. is it the same and the ext4 stays untouched?
Click to expand...
Click to collapse
i do beleive that it should be untouched, cos normally windows cannot see the ext partition and hence only fat32 will be formatted
Sent from my Nexus One using Tapatalk

ok. when ext4 stay untouched and i flash a new rom the apps are still in the launcher after flashing?

Jack_R1 said:
Full wipe in recovery wipes SD-EXT too.
Click to expand...
Click to collapse
when i flash a new rom i use the format.zip form the xda user temasek which wipes system, boot, data and cache. so is sd-ext untouched when i use this file?

You insist on not listening and/or not understanding.
When you select "wipe data/factory reset" in custom recovery, EXT partition IS WIPED COMPLETELY. It doesn't stay.
I believe the same happens when using temasek's script, never bothered using it, so I can't say with 100% certainty.
If you don't wipe your phone and install a new ROM - be prepared for crashes of anything to everything, unless you install a ROM which is 100% compatible with what you have already - the next generation of the same ROM, usually.
If you're using A2SD and don't wipe EXT partition - you'll have crashes as soon as you boot, since system apps' data will be there (and wrong).
To keep your apps and their data, use one of the backup apps available in the Market, like Titanium Backup.

as Jack_R1 explained its always better to wipe everything(system,cache,dalvik n sdext) to be on safer side to avoid crashes n FCs.
Sent from my Nexus One using Tapatalk

Temasek's Extreme Wipe does Data/System/Boot partitions but don't remember seeing ext in the list
However, as alluded too, I would format all outside phone with sdformatter or I think gparted, although never used that one
I thought I read a long time ago Windows formatter not recommended and do a full wipe not partial with whatever you use
Back up sdcard first
also, I believe you can use the Alignment Cool zip to get ext 4 from 3 on Amon and not lose anything--still backup
you do know MeDroid uses Ia2sd and different from a2sd on implementation

You don't need to wipe the regular FAT partition on SD card between flashes, because there's nothing there that loads automatically. And "wipe data/factory reset" option in recovery also wipes /sdcard/.android_secure.

hey guys, thanks for your answers i will keep them in mind.
edit:
one more question:
if i uses temaseks script and the sd-ext is untouched and i flash a newer version of my rom, are the apps then still there after flashing and booting the updated system? or is there another step i've to do?

No, the apps aren't there anymore - or to be correct, the apps are there, their data is gone (because the app data doesn't reside on EXT partition, unless you use specific mounting methods).
When you flash an updated version of your ROM, just don't wipe anything at all unless the instructions specifically mention having to wipe before installing that version. That means - don't execute temasek's script at all.