Database Users

erm. How do I wipe before I flash ?

I rooted my Hero a long time ago and installed Cyanogen's Recovery Image 1.4 on at the same time.
Over the last couple of days I've finally got hacked off waiting for an official 2.1 ROM to be released and decided to have a play with some of the Custom ROMs. The problem I've run into is that all of the guides talk about erasing data from different directories and partitions but none of them discuss how to do it !?
All I really need to know is if this is something that must be done via adb and what/where the directories are that need to cleared out.
I have searched and trawled but I get the feeling that this step is something that is done antomagically by the newer Recovery Images. If that's the case, would you suggest I upgrade mine ? And to what ?
Thanks for the help
(Really looking forward to playing with VillainROM 6 )

Yep,... Id 1st updrage your recovery to AmonRa 1.6.2.
Use BTDAG's guide in my signature to find out how to install it or I think there are ADB instructions for the installation in the Amon Ra thread.
Once that is done, before you flash a new ROM, turn of your phone, you go into your recovery by holding "HOME" and "POWER" buttons, then go into wipe, then select all of them one by one,....
[Recovery ROM] [07-Mar-2010] RA-hero-v1.6.2

Thanks ddotpatel, I guessed it might be due to the age of the Recovery Image I've got
I'll upgrade this evening

ddotpatel said:
Yep,... Id 1st updrage your recovery to AmonRa 1.6.2.
Use BTDAG's guide in my signature to find out how to install it or I think there are ADB instructions for the installation in the Amon Ra thread.
Once that is done, before you flash a new ROM, turn of your phone, you go into your recovery by holding "HOME" and "POWER" buttons, then go into wipe, then select all of them one by one,....
Click to expand...
Click to collapse
Any idea exactly what stats are erased by the battery stats & rotation settings options?

No idea pal,... but if Im flashing a new ROM without having 100% battery I leave the battery settings wipe.
I assumed that wiping battery stuff makes your phone think your battery is full after the wipe,...
So say its actually at 50%, then you wipe stats and flash a new ROM, then your phone thinks that battery is at 100% so will only charge upto that level.
The only thing I'm basing this on is I have read people say that when flashing a ROM when battery is not 100% they seem to lose battery capacity. But who knows, it could be psychological?

AFAIK battery stats deletes stuff like which programs have been using your battery as well as the currently stored battery figure. I assume that on next boot it checks the battery capacity afresh and goes with that figure.
Rotate one - i assume is to do with application rotation and the g-sensor.
I always wipe this data because it can't hurt - worst case it has to work it out again and it takes an extra 10 secs or so on startup.
Lithium Ion batteries don't have the "memory" problem of older batteries where they forget any charge that is left in the battery when it is put on charge and assume when its removed from charge that it is 100%. They should always stay the same capacity for their entire life duration. Again this is all AFAIK

Aahaaa,...
I always take what you say as gospel BTDAG.
Might have a read up on batteries later,... If I remember,... If I can be arsed!
Do you ever flash ROMs without having 100%?... No problems?

btdag said:
I always wipe this data because it can't hurt - worst case it has to work it out again and it takes an extra 10 secs or so on startup.
[snip]
Again this is all AFAIK
Click to expand...
Click to collapse
I took the same cautious view as ddotpatel. I figured if it's important enough to store in it's own private flash, it's probably holding data related in some way to the physical state of the phone, or an estimate thereof. I'm wary to touch them without ever having seen any solid info on what's there.
I've noticed one or two new ROM threads where the user is told to wipe these stats. I hope no one gets burned as a result.
BTW Also all afaik. It's just that in my case that isn't very far.

BATTERY

Ok, so I am running the newest ENERGY ROM, VBN RELOADED, and CORE CELL v4.1 and Im for android Im using hd 3.7, and when I first install the android I can get it to run 5-10mA or when I flash a new ROM, but once I restart android I can only get 50-60mA, i have pushed the back button when haret is running, it is so frustrating becuase I want to switch between android and winmo, and Im already using hastarin custom kernels and cant seem to get it to go less than 50-60mA unless I reflash or reformat and install over. Someone please tell me why the f8Ck this is happening, SO irritating. Ive tried to do some searching but all I have heard is that its from not lighting up my buttons. is there a certain time im supposed to light them up? Also, does having my charger plugged in help? Someone please help! Dont make a grown man cry.
Thanks in advance.
Matt

Just use Excellors' Multi boot app and set it to auto boot/3 secs when you want to boot Android and you should be good. If you run WM for a while reset your phone before going to Android and let it auto boot into Android. The battery drain in Android seems to be related to WM/Sense. By using the auto boot feature, WM/Sense is not allowed to fully boot. You should see significant improvement in battery performance in Android if you follow these simple steps. Cheers.

thanks mate
reocej said:
Just use Excellors' Multi boot app and set it to auto boot/3 secs when you want to boot Android and you should be good. If you run WM for a while reset your phone before going to Android and let it auto boot into Android. The battery drain in Android seems to be related to WM/Sense. By using the auto boot feature, WM/Sense is not allowed to fully boot. You should see significant improvement in battery performance in Android if you follow these simple steps. Cheers.
Click to expand...
Click to collapse
Thanks brodie, Imma give it a shot! let you know shortly

I solved this problem by renaming lights.htcleo.so included in the kernel

?
sykodelyk said:
I solved this problem by renaming lights.htcleo.so included in the kernel
Click to expand...
Click to collapse
Whaqt did you rename it to?

TheGeorgiaSwagger said:
Whaqt did you rename it to?
Click to expand...
Click to collapse
Im assuming hes talking about renaming it to lights.qsd8k.so?

[Q] bricked tmous hd2 from freezing android?

hi all, long time viewer first time poster, i have been reading many post on the net trying to find a definite answer on my tmous hd2 but with no luck. My problem started when i was running android (sandisk mirco sd, yes i know the incompatibility issues, it came with the phone). I was playing music through headphones while charging and suddenly the phone froze with a buzzing sound until i battery flipped, first thing it did when i started it back up again is vibrate approximately 5 times at boot flash screen (indicating excessive heat?), so i battery flipped again and waited 10 mins then i tried to start again and it just froze at boot screen, it would keep doing this and every now and then it will boot to wm, but sooner or later it will freeze in wm and then have booting problems, its still doing this today after doing all the following: 1.flash another custom rom. 2.flashed another radio. 3.task 29. 4. flashed stock rom & radio. 5. flashed nandroid 6.tried different capacity and brand sd cards & none at all.
I now have a hd7 because I couldnt fix it and didnt want to shed the cash they are still asking for a hd2, but i do want to fix the phone to play around more with it, i did look at the possible solution unbrick with jtag thread but im thinking the phone is perma bricked, when it was working it has had alot of custom rom flashes so i dont know if that makes much a difference but i would greatly appreciate some advice, THANKYOU XDA FOR ALL YOUR HELP!

lewy255 said:
hi all, long time viewer first time poster, i have been reading many post on the net trying to find a definite answer on my tmous hd2 but with no luck. My problem started when i was running android (sandisk mirco sd, yes i know the incompatibility issues, it came with the phone). I was playing music through headphones while charging and suddenly the phone froze with a buzzing sound until i battery flipped, first thing it did when i started it back up again is vibrate approximately 5 times at boot flash screen (indicating excessive heat?), so i battery flipped again and waited 10 mins then i tried to start again and it just froze at boot screen, it would keep doing this and every now and then it will boot to wm, but sooner or later it will freeze in wm and then have booting problems, its still doing this today after doing all the following: 1.flash another custom rom. 2.flashed another radio. 3.task 29. 4. flashed stock rom & radio. 5. flashed nandroid 6.tried different capacity and brand sd cards & none at all.
I now have a hd7 because I couldnt fix it and didnt want to shed the cash they are still asking for a hd2, but i do want to fix the phone to play around more with it, i did look at the possible solution unbrick with jtag thread but im thinking the phone is perma bricked, when it was working it has had alot of custom rom flashes so i dont know if that makes much a difference but i would greatly appreciate some advice, THANKYOU XDA FOR ALL YOUR HELP!
Click to expand...
Click to collapse
Please mention your RADIO, HSPL and the last Android Rom in which this happened!

If your phone is booting, it's not bricked. Did you try another SD card? Have you tried doing a low level format on your SD card? If it were me I'd Format the SD card with an adapter on my PC, low level. Then I would put it back in the phone then run Task29. Then flash MAGLDR 1.1. Then Flash the CMY 1.4n Desire HD Nand build in the HD2 Nand Android Development forum. It's the most stable Nand build up there right now.
I would use the 2.15 radio that comes with the newest Tmobile ROM. You might have to download the 3.14 ROM from Tmobile and flash it first to get the Radio in there. Then Task29 after that. MAGLDR, Then the NAND build. Make sure you find the Task29.exe that doesn't have a radio paired with it. it's on this site somewhere.
lewy255 said:
hi all, long time viewer first time poster, i have been reading many post on the net trying to find a definite answer on my tmous hd2 but with no luck. My problem started when i was running android (sandisk mirco sd, yes i know the incompatibility issues, it came with the phone). I was playing music through headphones while charging and suddenly the phone froze with a buzzing sound until i battery flipped, first thing it did when i started it back up again is vibrate approximately 5 times at boot flash screen (indicating excessive heat?), so i battery flipped again and waited 10 mins then i tried to start again and it just froze at boot screen, it would keep doing this and every now and then it will boot to wm, but sooner or later it will freeze in wm and then have booting problems, its still doing this today after doing all the following: 1.flash another custom rom. 2.flashed another radio. 3.task 29. 4. flashed stock rom & radio. 5. flashed nandroid 6.tried different capacity and brand sd cards & none at all.
I now have a hd7 because I couldnt fix it and didnt want to shed the cash they are still asking for a hd2, but i do want to fix the phone to play around more with it, i did look at the possible solution unbrick with jtag thread but im thinking the phone is perma bricked, when it was working it has had alot of custom rom flashes so i dont know if that makes much a difference but i would greatly appreciate some advice, THANKYOU XDA FOR ALL YOUR HELP!
Click to expand...
Click to collapse

hd2 running MIUI freezing up too
I'm a complete noob here so bare with me. I'm currently experiencing the same probs as lewy255 with the hd2 freezing up. It happens every now and then when I'm accessing certain apps. When the hd2 does freeze up, i have to take the battery out, wait, then boot up again. Once it tries to boot up it freezes on magldr, then i got to take out the battery again, wait, then power it on again. It seemed to happen when i first rooted my hd2. The first ROM i flashed after rooting was typhoon CM7. Currently have:
HSPL 2.08
radio 2.15.50.14
MIUI version: 1.5.27
I hope this isnt a hardware issue cause i bought this phone from one of my friends and he didn't have the receipt. Please advise on what i can do to fix this freezing issue.
Thanks

Sounds like cpu overheat freeze. When you were playing music and charging it the first time it froze, was the phone and/or battery hot?
It's very possible that it got too hot once, and now the cpu its self gets too hot much easier now that it has already happened once.
Sent from my HTC HD2 using XDA App

Cpu overheat freeze? So its a hardware issue? What if I ran task29, and reinstalled magldr, clockworkMod, and then MIUI, do u think that would fix the freezing issue?
Sent from my HTC HD2 using XDA App

germotlp said:
Cpu overheat freeze? So its a hardware issue? What if I ran task29, and reinstalled magldr, clockworkMod, and then MIUI, do u think that would fix the freezing issue?
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
No I do not think that will help your situation. I think your HD2 is starting to show signs of hardware break down. More specifically a breakdown in the connection of the processor and the main board. The only permanent if this is the case is to replace the main board.

T-Macgnolia said:
No I do not think that will help your situation. I think your HD2 is starting to show signs of hardware break down. More specifically a breakdown in the connection of the processor and the main board. The only permanent if this is the case is to replace the main board.
Click to expand...
Click to collapse
t-mac
I tried installing setCPU and adjusted the temperature setting so if got too hot then the speed of the phone would be reduced, but still no luck.
What if i unrooted the phone and put everything back to stock? I think that way i will know for sure that its a hardware issue. I dont know much about phones but your probably right. I'll try running task29 and reinstall everything and see if that works, if not then i will un-root and put everything back to stock and test.

Is it an undervolted kernel? Might cause problems, but I'm with mac here on it being a hardware problem, since you flashed back to winmo stock and you still had problems.

Kailkti said:
Is it an undervolted kernel? Might cause problems, but I'm with mac here on it being a hardware problem, since you flashed back to winmo stock and you still had problems.
Click to expand...
Click to collapse
I'm a newbie here. Not sure what u mean by undervolted kernel. Could u explain to me? Btw I have not flashed back to winMo yet.
Sent from my HTC HD2 using XDA App

i have same problem with miui roms. I think this problem is about Miui Roms. Miui developers must solve this issue, there is no way..
When i try other Roms, there is no problem like this issue..

germotlp said:
I'm a newbie here. Not sure what u mean by undervolted kernel. Could u explain to me? Btw I have not flashed back to winMo yet.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
in my opinion and its just my opinion, but you should flash a winmo 6.5 build than boot android from sd its safer because theres no need to worry about battery dying in magldr. and if theres a nand rom you want to try out i suggest using port a droid. im using now with the new nexus 2.8 with a 1gb data.img and it runs great plus i have 3 other builds on there also.

many issues after dead battery on nand droid

the phone is freezing often
slow touch responce
programs force closing
yahoo mail doesnt work anymore
its shutting down on its own randomly
and some other problems i cant remember.
its a nand CMYLXGO stock desire HD v1.1.3
is this a common problem, if so where can i find info aout it i searched for dead battery and didnt show much.

Maybe some data got corrupted. So you should reflash or flash another build. Maybe even your radio to be sure.

why does it happen? i thought we wouldnt have this problem with nand builds.

fuzzysig said:
why does it happen? i thought we wouldnt have this problem with nand builds.
Click to expand...
Click to collapse
well, lot of roms use the data2sd method for storing data on SD, for me its pure nonsense (app2sd is fine). With data2sd the risk is very high that you get data corruption and then all the weird force close madness begins. Now if you run out of battery your device doesnt shut down properly/cleanly, its the same as you would just pull a cable to shut down a pc. So running out of battery is the same as pulling the battery.

wow
I'm using CMYLXGO's BlueTopia (NAND) and the battery widget got to 0% i think... i was worried since charging MADGLR 1.3 requires me to activate the screen / turn on the phone....luckily it did the GO GO GO thing and started to boot .... i plugged in the charger and now all is well.... lucky me I guess...
PS .. I guess the battery widget is a showing a percentage or two off

kiki_tt said:
I'm using CMYLXGO's BlueTopia (NAND) and the battery widget got to 0% i think... i was worried since charging MADGLR 1.3 requires me to activate the screen / turn on the phone....luckily it did the GO GO GO thing and started to boot .... i plugged in the charger and now all is well.... lucky me I guess...
PS .. I guess the battery widget is a showing a percentage or two off
Click to expand...
Click to collapse
That's what it does for everybody.

the phone also started to have SOD.
i plug it in at night to charge, in the morning it would not wake up.
the alarm would go off but the screen is blank.

now the phone just freezes randomly.
can anyone suggest any fix or troublehsooting tips.
yes im well aware that i can reinstall it again but id like to try and find the problem first before wiping it all clean AGAIN.
why would a dead battery cause this on a custom build and not on a factory installed rom?

fuzzysig said:
now the phone just freezes randomly.
can anyone suggest any fix or troublehsooting tips.
yes im well aware that i can reinstall it again but id like to try and find the problem first before wiping it all clean AGAIN.
why would a dead battery cause this on a custom build and not on a factory installed rom?
Click to expand...
Click to collapse
Been there. The only solution that worked for was to flash it from scratch once again.
Dunno why the phone is acting this way but now I always charge or turn off my phone when my battery is down on 10 %. Better to be safe than sorry.
I'm using MDJ's CM7 v. 2.6 so I think this is an issue on many builds if not on everyone.

fuzzysig said:
now the phone just freezes randomly.
can anyone suggest any fix or troublehsooting tips.
yes im well aware that i can reinstall it again but id like to try and find the problem first before wiping it all clean AGAIN.
why would a dead battery cause this on a custom build and not on a factory installed rom?
Click to expand...
Click to collapse
Since u are aware u can reinstall it again then simply do so...Yeah its a real pain but just tk time out n do it...I've been using CMY's builds for so long and have never encountered such an issue..but dats just me...
i see u r still using V 1.1.3, CMY has released a much more better build (but then u already know that), so go download dat...perform a Task 29 ,install MAGLDR ( u know d works) etc...
As 4 y a dead battery will cause this on a custom build and not on a factory installed ROM? ...Me thinks u already know d answer (stick 2 stock WinMo if u think its better)..
P.S. Remember charging ur battery to 100% b4 starting..gives u a fairly calibrated battery.

you could also try to wipe the battery information via magldr?
you choose recovery in magldr > clockworkmod recovery > advanced > wipe battery stats.

tried that didnt work
isnt there another way besides reinstalling everything over and over?

wow i mean we went so far as to have it working on the phone but nobody knows why a dead battery causes corrupted system on a custom rom but not on the original?

fuzzysig said:
wow i mean we went so far as to have it working on the phone but nobody knows why a dead battery causes corrupted system on a custom rom but not on the original?
Click to expand...
Click to collapse
?! it has been answered in this thread...

Reformat Device A70H

i was trying to make full format and I made a mess...
i choose full reformat and i install SDE
boot into the AngStrom OS
i trying to Install android firmware 2.4.83
i choose "Update Firmware"
but
update failed
what should i do now?
somebody help please...

please...someone???
Im stuck here...

Hi!
Try another cable or download again the firmware. Verify if it's the good version.
Tell us which tab you have
Sent from my GT-I9000 using XDA

And try to learn how to use the search function of this forum, as we had this question and many answers allready.
for ex: did you make sure that the aos file has the correctg name?
Or maybee you could post the complete errorcode!

Sorry if there is another same thread
When I installed UrukDroid 1.6.4 update I got 2 problems..
1.when the device was in standby mode,the hard drive was working and I consumes the battery in a few hours.
2.I tried to install applications from the market but no luck because ''not be installed in space usb or sd card''
So I decided to do Reformat the Device...
I installed SDE
after I installed android firmware(bizcuite you had absolutely right buddy.i download again the firmware and everything is ok now.)
I installed the custom kernel + initramfs and then UrukDroid 1.6.
so far so good...
when I tried to install again UrukDroid 1.6.4 update the Device stuck (The screen and buttons didn't respond)...
now I reinstall again the SDE and android firmware
reinstall the custom kernel + initramfs
and reinstall the custom kernel + initramfs UrukDroid
i am trying to reinstall UrukDroid but the Device stuck in screen ''tranfer now installation file over usb and press power button once''
what should i do now?
i have a Archos A70H
sorry but my english is not very good

As stated here and in the dev part, stay away from uruk as long as you don't know what you are doing.
Uruk is still not ready for the harddrive version.

Thanks for your reply but could you be a little more gentle with me???
still learning here...
so I can not installed yet UrukDroid...???
Simple method will start installation on SDCard or HD (A70H)
http://code.google.com/p/urukdroid/wiki/EasyInstall
Thanks again for your answer...

It wasn't meant to be hard on you.
Uruk is optimised for the sd version.
ATM it is installed on the harddrive and therefore it consumes alot more batterie and is not really as stable as on the A70S.
That's why you really have to know what you are doing.
And $auron has the Problem ATM that his device is broken, so the development is not as fast as before.

I think I got much info here.

fzelle said:
It wasn't meant to be hard on you.
Uruk is optimised for the sd version.
ATM it is installed on the harddrive and therefore it consumes alot more batterie and is not really as stable as on the A70S.
That's why you really have to know what you are doing.
And $auron has the Problem ATM that his device is broken, so the development is not as fast as before.
Click to expand...
Click to collapse
i understand...
have you any advice for my device???

Not ATM.
The problem is that the A70H is different to the A70S as the h only has 2gb of ssd and that is partitioned differently and as neither $auron nor divx118 have one to test it will probably not change in the near feature.
So atm the best thing you can do is chulri's root or live with the restrictions of UrukDroid.

fzelle said:
Not ATM.
The problem is that the A70H is different to the A70S as the h only has 2gb of ssd and that is partitioned differently and as neither $auron nor divx118 have one to test it will probably not change in the near feature.
So atm the best thing you can do is chulri's root or live with the restrictions of UrukDroid.
Click to expand...
Click to collapse
I did chulri's root
(Install SDE , Install my android firmware , Install the custom kernel + initramfs)
but
when am in Developer Edition the device stuck and the screen does not respond
only in android edition the device works normally...but I have not superuser options...

I have same device, im running uruk 1.6.3 boot with .2 init everything runs smoothly but i also upgraded from 1.6.2 so maybe try an upgrade from there, i will try 1.6.4 though and let you know how it goes
Edit: ive upgraded to 1.6.4 and everything is running smooth, i had one bad startup where touchscreen was not at all responsive, a reboot in recovery an fix permission and clearin dalv cache and its now been a few days with no (unknown) force close, just a couple of my own doing lol
Sent from my A70H using XDA

When you are in standby mode the hard drive was work???

When my device is in sleep mode or standby my hdd doesnt spin an cause any abnormal drain.. yesterday i was out for 12 hours in he sun skateboardin and hiking with music on and/or in standby.. i had 67% batt left when i came home
Sent from my A70H using XDA

Dyverse said:
When my device is in sleep mode or standby my hdd doesnt spin an cause any abnormal drain.. yesterday i was out for 12 hours in he sun skateboardin and hiking with music on and/or in standby.. i had 67% batt left when i came home
Sent from my A70H using XDA
Click to expand...
Click to collapse
How is that possible????
with 1.6.4 ???

It shows a lower % at times then actual voltage drain of battery, if you deep sleep it an wake up the % will jump up from say a 50% to about 80%, i also take some power savin precautions like disablein wifi and using nightmode (thanks chainfire3d) it helps with display power and also no glare lol, but i havnt really ever had a power drain issue as far as it goes lol i guess i got lucky somehow or managed to do something righ for a change lol
Sent from my A70H using XDA

so..i have problem..again...
can someone tell me the steps to format like when I bought it???
i choose full reformat.
Install SDE , Install my android firmware , Install the custom kernel + initramfs
ok but...
the device starts normally android but the screen does not respond..
any ideas please???

Only touch screen is not responsive, or nothing is displayed at all?
You can still see the boot progress on the screen?

so...
i Install again the SDE and android firmware normally...(thank God)
no custom kernel + initramfs
reboot
the device is working normally in android mode.
When I go to the option dev edition the screen stuck to developer edition boot in progress...
when i reboot the device in normally mode the screen does not respond
i don't know what to do to solve the problem