Related
i have tried the fresh roms, and the TTG CDMA rom, regardless of the rom i get force close errors on settings in the phone and i dont have data or voice service. everything else works perfectly EXCEPT for settings and service.
help?
ae you performing a wipe before you flash? I know a lot of these roms say that they are no wipe but I have found that that it is always better to wipe then flash that way you know you are getting a clean install. also do you have a ton of apps? it is a known problem that the phone will freak if you have more than like 60 apps
yeah, i have wiped also. but one thing i only wipe data/factory reset
should
i wipe
dalvik cache also? alsong with anything else?
when I install a new rom I wipe both the factory/data reset and delvik cache. I also do this when I am going from say TTG 1.6 back to my backup of fresh 1.1. It just assures me that anything that one dev did in their rom will be wiped out and replaced by what the other did with no problems. the only FC I get is google voice ( which FC's on EVERYTHING for no particular reason)
ok wiping data, and dalvik because jusr assuming battery status, rotate settings and partition doesnt matter.
from my personal use I dont use all the options in recovery. the partition SD is going to be usefull once you get the ROMs running if you want to run apps2sd
nope...
ive unrooted used kitchen numerous times to auto root aswell then just apply update and I can get everything to work except FC on settings and no service, im trying to figure out how to use ruu 1.2.3 instead of the 1.5 one idk just gonna try.
samrozzi said:
nope...
ive unrooted used kitchen numerous times to auto root aswell then just apply update and I can get everything to work except FC on settings and no service, im trying to figure out how to use ruu 1.2.3 instead of the 1.5 one idk just gonna try.
Click to expand...
Click to collapse
RUU 1.29 will not work for you if you have used 1.56. Are you sure you're running a Sprint CDMA Hero? Can you step by step explain the process you go through when RUU'ing and when flashing, and when the problems start?
ok if i wanted to start from scratch, i will unroot my phone with htc sync and reload the stock rom.
then i use kitchen and run the tests and everything checks out good.
i auto root and its successful and working.
then say I download fresh 1.1, load it onto the root of the sd card.
Power off the phone then power on while holding home.
apply .zip on sdcard. it applies the fresh 1.1 update says successful
i click reboot, phone goes through startup process everything seems fine, rom loads up i can navigate through menues. except i get force close errors anytime i goto settings, and i have no service, no data or voice signal.
I have tried renaming fresh and other roms to update aswell, i have tried numerous roms, one of the most recent was the TTG cdma hero rom. and i get the same errors.
One interesting thing is the first rom i tried on the cdma hero was eclair 2.1 beta and that worked flawlessly like all the roms i tried on my g1. but i decided to go to fresh and nothing works.
samrozzi said:
ok if i wanted to start from scratch, i will unroot my phone with htc sync and reload the stock rom.
Click to expand...
Click to collapse
I'm not sure what you mean by unrooting it with htc sync and reloading stock rom? You need to be using the RUU to flash back to stock.
Also if you are using apps2sd then I would recommend temporarily formatting your sdcard back to 100% fat32 (you will lose all data) and then try RUU and flash. Or just grab another sd card and put it in there. If you are using apps2sd and there is an app on your sdcard that is breaking things then it will persist even after a wipe.
1. Partition sdcard to 100% fat32 or replace it with another temporarily
2. Run 1.56 RUU to return to bone stock. Confirm everything works.
3. Run auto-rooter in kitchen. Confirm everything works.
4. Flash a rom, confirm everything works.
If you follow those steps exactly then everything will work out for you.
ok gonna try it again when wiping sd card and foratting to fat32.
any way or know how to get htc sync to recognize my phone?
it picks it up on my vista laptop but on my windows 7 64 bit it doesnt, but atm all i have is my windows 7 one.
samrozzi said:
ok gonna try it again when wiping sd card and foratting to fat32.
any way or know how to get htc sync to recognize my phone?
it picks it up on my vista laptop but on my windows 7 64 bit it doesnt, but atm all i have is my windows 7 one.
Click to expand...
Click to collapse
http://www.mydigitallife.info/2009/08/24/workaround-for-htc-hero-sync-problem-in-windows-7/
ok about to return to stock, when i apply the fresh 1.1 rom after i use kitchen auto rooter i jsut stick it on root of sdcard and DO NOT change file name?
just used to most roms from g1 have to be renamed update.zip
samrozzi said:
ok about to return to stock, when i apply the fresh 1.1 rom after i use kitchen auto rooter i jsut stick it on root of sdcard and DO NOT change file name?
just used to most roms from g1 have to be renamed update.zip
Click to expand...
Click to collapse
You can do it either way. But you don't have to rename it.
WOW IT WORKS, their had to be something wrong with my sd card, because it wouldnt let me format it.
I had to delete all the files, then install some 3rd party software that would let me format it. idk what was wrong, but working great !!!
so excited finalllly lol
thanks everyone and especially flipz
i am running fresh 1.1 defreshed atm, love it but curious about what AOSP i think its called. what exactly is that, looking at it and seems interesting,
im hoping we get a rom similar to nexus, love the app drawer etc..
It may have worked because when you wiped your Sd, you deleted your apps, if you install too many, you'll have the same issue. I went round and round with mine before I figured it out, then found a thread on it.
AOSP stand for "Android Open Source Project" they are ROMs that are crated and developed from scratch by various developers.
I have played with AOSP builds and I have found that out of them all I like AOSP 1.6 best. The thing you have to rememeber about AOSP builds right now is that A. we still dont have the Kernel source so not everything is working correctly and they can be kinda buggy and B. all the AOSP builds are vanilla android, meaning they dont use sense UI which in my opinion defetes the purpose of having a hero. If I didnt care about sense then I would have gotten a moment.
that being said I will say that the AOSP builds are REALLY fast.
if you want to try a ROM that is close to an AOSP build but still has sense try TTG1.6 its really fast and has a really small memory footprint due to it being almost completely gutted and optimized.
Hi Peeps,
I have searched in vain for a guide to changing from cm 4.2.15.1 to super d stable, but I cant seem to find one.
can someone advise me what to do so I dont brick my phone, and is it really worth moving to super d I hear its faster.
I am running cyanogen 4.2.15.1 H&E red I have the ra-dream 1.5.2 recovery, I have ext2 partition on sd card and I have a PVT board
Also I am worried about the ext2 partition because I have heard you have to remove it first and there is a certain way to do it??
Thanks in Advance
I was able to flash SuperD over Cyanogen without wiping or repartitioning. This is with an sdcard partitioned the usual way, fat32 and ext2.
The only issue I ran into was the battery meter - had to remove /data/system/batterystats.bin. Not sure of the exact procedure, so I did that from the recovery console and then booted up with a full charge.
Works great and really is a lot faster.
I would always wipe when moving from one rom to another. You never know what's could be hanging around.
I go thru this same process every time and never had problems:
1. Nandroid or Bart backup
2. Copy backup from SDcard to PC just in case SD card gets corrupted somehow
3. Wipe
4. Install new rom
5. Fix apk mismatch
6. Reboot
7. Check to see if Gapps are working, namely market, talk, sync, and of course google voice
nmw407 said:
I would always wipe when moving from one rom to another. You never know what's could be hanging around.
I go thru this same process every time and never had problems:
1. Nandroid or Bart backup
2. Copy backup from SDcard to PC just in case SD card gets corrupted somehow
3. Wipe
4. Install new rom
5. Fix apk mismatch
6. Reboot
7. Check to see if Gapps are working, namely market, talk, sync, and of course google voice
Click to expand...
Click to collapse
5. When you say "fix apk mismatch"....what do you mean?
7. I did the same thing (went from Cyanogen to SuperD) and I can boot into SuperD fine, but it won't connect to T-mobile's network and I am missing the Market. Any help?
shuboy00 said:
5. When you say "fix apk mismatch"....what do you mean?
Click to expand...
Click to collapse
It's an option in Amon_RA's recovery
shuboy00 said:
7. I did the same thing (went from Cyanogen to SuperD) and I can boot into SuperD fine, but it won't connect to T-mobile's network and I am missing the Market. Any help?
Click to expand...
Click to collapse
Wipe, Flash the DRC83_Base_Defrangled, the flash SuperD. Since both are legal, they need to pull the google apps from the base. And you would probably be fine without a wipe from SuperD to CM since they are similar donut builds. Wipes are recommended if you go from eclair to donut (and donut to eclair, elcair to sense, sense to dount.....). Cyanogen fixed it so you don't need to wipe as in the olden days...
mejorguille said:
It's an option in Amon_RA's recovery
Wipe, Flash the DRC83_Base_Defrangled, the flash SuperD. Since both are legal, they need to pull the google apps from the base. And you would probably be fine without a wipe from SuperD to CM since they are similar donut builds. Wipes are recommended if you go from eclair to donut (and donut to eclair, elcair to sense, sense to dount.....). Cyanogen fixed it so you don't need to wipe as in the olden days...
Click to expand...
Click to collapse
I see. So I am already running the DRC83_Base_Defrangled. Here is what I am doing:
I am currently running Cyanogen 4.1.99. My build number is DRC83. But my model number says "Android Dev Phone 1" <-- could that be why I don't have the Market in my roms?
So anyways this is what I do from Cyanogen 4.1.99: I backup, wipe, flash the DRC83, flash SuperD, then flash the 26I radio. Like I mentioned, rom boots up fine, just no market and no network access. Am I doing something wrong?
Absolutely no reason to flash the radio. The only thing that I can think of is that you have a bad download? Download this. Go to recovery, backup, flash the base, flash the rom. That should be all you have to do. Also, try CM 4.2.15.1 if SuperD isn't working for you. You are using a version of cyanogen about 4 months old and there have been 20 something releases since.
mejorguille said:
You are using a version of cyanogen about 4 months old and there have been 20 something releases since.
Click to expand...
Click to collapse
i believe he said that he is running latest cyan rom. try backing up your fat32 partition and reformat, that should do the trick
b0ricuaguerrero said:
i believe he said that he is running latest cyan rom. try backing up your fat32 partition and reformat, that should do the trick
Click to expand...
Click to collapse
I was referring to the poster above my post
mejorguille said:
Absolutely no reason to flash the radio. The only thing that I can think of is that you have a bad download? Download <removed>. Go to recovery, backup, flash the base, flash the rom. That should be all you have to do. Also, try CM 4.2.15.1 if SuperD isn't working for you. You are using a version of cyanogen about 4 months old and there have been 20 something releases since.
Click to expand...
Click to collapse
K. Did what you said. Downloaded the base you provided. Flashed. Then flashed the SuperD rom. Booted up. First I see is "!Sorry - The process com.google.process.gapps has stopped unexpectedly. Please try again." Still no network and still no Market. Urgh. Frustrating!!
Also, I tried CM 4.2.15.1 after the SuperD didn't work and it hung on the G1 screen. IDK why 4.1.99 works but not 4.2.15.1.
i guess it didnt hung, you just have to wait a bit longer.
HELP! having multiple issues with Nexus S. Cannot wipe cache partition, and wont mount in recovery either. Also my built in storage is now gone. let me give you guys a quick overview of what happened:
We have a dev version of the nexus s (gingerbread version is not retail) in our office. We were having difficulty factory wiping the device (it would complete but nothing would erase) so someone decided to flash a different leaked rom for the Nexus S. The phone was basically a brick afterward. I managed to flash Clockwork on to the device. This is where I found that the cache partition wouldn't mount. Either would the SDCard (USB storage, whatever). I couldnt erase either partitions, and it also couldnt mount the USB storage (was going to try a nand restore from another thread). The only way i could get mass storage was by partitioning the "SDCard" through recovery. This managed to give me a 1 GB partition that windows would recognize (and would mount through clockwork) It wasnt formatted, so i did a quick format with windows, copied the nand backup and restored it to the device. it now boots, but with a few issues. First no data, second i cannot hard reset through menu, third we're having multiple FCs. FINALLY the worst, is still no USB storage. Wont mount USB storage at all. Sometimes device memory displays 3.5 TB (WUT!?). Cannot download any apps.
WHEW
Sorry that was really long. Basically, the phone is messed up, and I cannot mount or wipe the Cache partition, the USB Storage is now missing, and the Restored Nand backup is super bugged. Any ideas?
As a note
I've also deleted the cache partition and re-created through parted. still wont mount cache OR USB Storage
Sorry to bump an old thread, but I'm having this problem too. I want to install CM7, but I don't want to risk formatting the /system and /data partitions if the /cache partition refuses to format. You seem like you're having the same problem as I am having and I wonder whether this is done on purpose from Samsung to disable custom ROM flashing. (I got mine straight from Samsung too).
Has anyone solved this?
looks like I have this issue also ... looks like memory is corrupt ... I can't save any files when mounting the usb device ... When I disconnect, all the files disapear ... any ideas ?
have the same problem but i can't boot in android either it just hangs at google logo and if i boot in recovery i get this error (didn't flash any roms yet it happend after i flashed clockworkmode
i was able to boot andriod again with odin but clockwork still gives the cache error so i still can't flash anything else on it
Am still learning....but just a few quick questions....adb is still working?.....and computer makes connection sound when phone plugged in? Have you tried reinstalling drivers the flashing recovery and then nandroid.......for some reason when i had a simiilar problem....my phone would not flash any rom but only do restore for nandroid....
also can you access the usb storage at all? You say it dissappears after ?
well i was able to put my device in download mode and install a rom with odin and i can boot again, but after that i reinstalled clockworkmod and again it's giving me the cache error. i can't install/backup/restore/.... anything in clockworkmod i keep getting cash error.
ps. it's a new i9023 device running 2.3.3 stock
can you tell me what it says on your bootloader screen when you boot into it( assuming that you can)
fastboot mode
product name - hearing
hw version - rev 52
bootloaderversion - i9020xxka3
baseband version - i9020xxkb3
carrier info - eur
serial number - ... (if you need it pm)
lock state - unlocked
...
So whilst in bootloader you can flash recovery.img (I have the file if you need it)
eg...fastboot flash recovery recovery.img......
then can you access newly flashed recovery and maybe then restore.....I still dont know if you can access usb storage on the device
well yes i can access usb storge in clockworkmod (it's one off the only things that works in clockworkmod ) and if the recovery you have also is clockworkmod then it won't do much difference clockworkmod doesn't seem to find my cash or anything
btw i just saw there are 2 threads with almost the same around and looks like i posted in both don't know why but was pretty late last night when i posted seems the problem i have is the one in this topic (still no solution tough): http://forum.xda-developers.com/showthread.php?p=12204800#post12204800
suboxide said:
well yes i can access usb storge in clockworkmod (it's one off the only things that works in clockworkmod ) and if the recovery you have also is clockworkmod then it won't do much difference clockworkmod doesn't seem to find my cash or anything
btw i just saw there are 2 threads with almost the same around and looks like i posted in both don't know why but was pretty late last night when i posted seems the problem i have is the one in this topic (still no solution tough): http://forum.xda-developers.com/showthread.php?p=12204800#post12204800
Click to expand...
Click to collapse
Yeah so have you tried a nandroid restore then....Not a new rom installation!......a nandroid restore which was either a stock restore or a rooted rom in which cache was accessible....sorry if you have just want to check the obvious first.
have you tried flashing an older recovery of clockwork mod?
If you have then probably is just a new nexus S issue which needs a workaround?
oh yes tried nandroid restore first (got cache error during that aswel if i rember corectly, atleast didn't work)
only thing that worked was using odin from: http://www.samfirmware.com/apps/blog/show/6263048-nexus-s-roms-now-online-
after that i was able to boot the phone again and i did another clockworkmod recovery and got the same error that's shown in first post: http://forum.xda-developers.com/showthread.php?p=12204800#post12204800
atleast i can access android now, i think there is maybe something different between the new phones in europe since some other ppl that bought their phone recently are having the same problem and it's only since this week you can buy them (well in belgium atleast, don't know about other country's)
i can try if you know where to find an older clockwork mod, i seem only to find "recovery-clockwork-3.0.0.5-crespo.img"
suboxide said:
i can try if you know where to find an older clockwork mod, i seem only to find "recovery-clockwork-3.0.0.5-crespo.img"
Click to expand...
Click to collapse
try this one I think it s a previous version ....worked for me
...but then i have older nexus s.....
same error:
http://db.tt/r7oe3wz
suboxide said:
same error:
http://db.tt/r7oe3wz
Click to expand...
Click to collapse
Hmm ok ....well im stumped as well.....sorry i couldn't be of any more help...
look at the image it's about ppl that just unlocked the new htc thunderbolt but seems they also have the cache problem looking at the screenshot
http://www.androidpolice.com/2011/0...orkmod-recovery-loaded-rom-floodgates-opened/
Where to begin...
So I based my install off of this YouTube Video: youtube.com/watch?v=88qRbLLEAPQ and after I got done following everything to the T, I was not able to format /data. I feel this may be my problem. After doing all the steps minus that one I tried to install CM7 and it would boot the second time around in CM7 (Something I read was common). IT would get the the skateboard screen and then it would just stay there with the arrow continuously looping around and around. I let if sit for quite some time before I had to power it off.
I called up my buddy who told me I would more then likely have to install it manually with the Android Developer tools (Or whatever he called it). I did not have those tools so I kept poking around online. I found that sometimes the SD card caused problems so I bought a new 4Gb class 4 card. This was not the issue.
I poked around alittle more in CWR and I accidentally formatted /boot. The unit froze up so I restarted it. It booted into CWR just fine and after trying to wipe the /system, /data (Still not working) and /cache and rebooting, it has now just turned to a black screen that I can't even boot from a card.
Now before I just cash in on my protection plan, What can I do to get this running again? I hate having a paper weight sitting on my desk..
Thank you so much!
tl;dr, Tried to install CM7, can't format /data, tried new card and re installing, accidentally formatted /boot and now it won't boot at all.
Honestly, I can't watch Youtube at work so I am clueless what instructions you are following.
1. What version of your NC? 1.2? 1.1? 1.0?
2. What version of CwMR?
3. You tried to install CM7 in the eMMC or uSD?
I don't know which Nc it is... I just got it 2 weeks ago today.
I do believe that the cwr was 3.0.0.3 or something like that... it was supposedly the newest.
and it was the latest stable version of CM7.
My problem now is that my computer has totally crashed and it won't start in safe mode even. I am fairly sure it has something to do with having the files on my computer.. I just have to get that part figured out, then I can get the rest of it working..
Latest CW is 3.2.0.1 if I recall.
I know when I leave my imaged microsd card in my adapter on the laptop that the laptop won't boot. You don't have the card in an adapter on the system do you?
Also, I assume you are trying to install CM7 to internal memory?
You have to use CWR v. 3.2.0.1. Earlier versions will not wipe/clear everything. Do that and you should be ok....
If it has been around 2 weeks ago, then it most likely be v1.2 which you need CwMR v3.2.0.1, which reportedly fixes the format /data issue.
Give it a try again.
Ok, got the Nook to boot back to the Nook software. Won't get past the loading screen, but atleast it is booting..
I got my computer working finally after booting in Safe mode and deleting all the zip files and images from the computer. So now I am back to a clean slate.
Where do I get CWR 3.2.0.1? And then where do I get the CM7 latest release? I feel like I should be listening to you guys rather then listening to the YouTube video.. It was nice to see things happen on there, But it did not work for me.
Thank you guys SOOO much for having this forum and the "How to fix the black screen" tutorial! I would be lost without it!
Can someone please help me? I have a Samsung focus that was recently acting up.. Games wouldn't open etc.. so I decided to reset it.. After I reset it.. Its now stuck at the Samsung logo after resetting.. I am guessing that I need to reflash it.. If so, I need to make sure my battery isn't dead. Does the Phone charge while showing the Samsung boot logo?? Help Please..
I dont have a focus but with a Google search looks bout the same as I wud do on my epic ..found this if it helps http://forums.androidcentral.com/dr...ks/130642-help-stuck-samsung-boot-screen.html
Alright, heres what I did.1. Rebooted in*CWM2. Wiped data/factory reset3. Wiped cache partition4. Wiped dalvik cacheAt this point I couldn't reflash because I forgot I couldn't access my SD card, I kept getting the "e:can't mount /sdcard" message whenver I went to install zip from sd card.5. Took off the back and pooped out the SD card and put it right back in. Seemed to work6. Flashed 2.07. Flashed kejar's sd card fix8. Rebooted through*CWMPhone starts up, do all the set up stuff, but still can't access my sd card or anything. Booted back into*CWM*just to see and was getting the "e:can't mount /sdcard" error again and couldnt reflash anything, so back to step 1.Here's a list of other things I have done since the original crap out a few days ago that might be affecting this.*1. Yesterday I tried reflashing 2.0 and it seemed to be boot looping again. So I just wiped data and cache partition and flashed 1.9.1 that I had on my SD card. Was having the same problems so that was the only time I tried it. Not sure if built in kernels might affect anything or whatever.2. After it seemed like I had a stable 2.0 again last night. I flashed blue*CWM*because I've had yellow this whole time. I also flashed EP1 radios through ODIN because I was planning on going to GG 2.1 (I was following your video dave! its awesome btw*).I'm not sure at what point I lost access to my SD card. Ive read a lot this morning about voodoo lag fix affecting things. Could this be a problem with what I've done?
Sent from my SPH-D710 using Tapatalk 2
jpeclf said:
I dont have a focus but with a Google search looks bout the same as I wud do on my epic ..found this if it helps http://forums.androidcentral.com/dr...ks/130642-help-stuck-samsung-boot-screen.html
Alright, heres what I did.1. Rebooted in*CWM2. Wiped data/factory reset3. Wiped cache partition4. Wiped dalvik cacheAt this point I couldn't reflash because I forgot I couldn't access my SD card, I kept getting the "e:can't mount /sdcard" message whenver I went to install zip from sd card.5. Took off the back and pooped out the SD card and put it right back in. Seemed to work6. Flashed 2.07. Flashed kejar's sd card fix8. Rebooted through*CWMPhone starts up, do all the set up stuff, but still can't access my sd card or anything. Booted back into*CWM*just to see and was getting the "e:can't mount /sdcard" error again and couldnt reflash anything, so back to step 1.Here's a list of other things I have done since the original crap out a few days ago that might be affecting this.*1. Yesterday I tried reflashing 2.0 and it seemed to be boot looping again. So I just wiped data and cache partition and flashed 1.9.1 that I had on my SD card. Was having the same problems so that was the only time I tried it. Not sure if built in kernels might affect anything or whatever.2. After it seemed like I had a stable 2.0 again last night. I flashed blue*CWM*because I've had yellow this whole time. I also flashed EP1 radios through ODIN because I was planning on going to GG 2.1 (I was following your video dave! its awesome btw*).I'm not sure at what point I lost access to my SD card. Ive read a lot this morning about voodoo lag fix affecting things. Could this be a problem with what I've done?
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for your help but seeing as your phone is an Android phone, I don't think the same process applies. But thanks for the effort, I have this baby up and running now.. I just had to reflash the ROM.. Thanks again :good:
FocusHelp said:
Can someone please help me? I have a Samsung focus that was recently acting up.. Games wouldn't open etc.. so I decided to reset it.. After I reset it.. Its now stuck at the Samsung logo after resetting.. I am guessing that I need to reflash it.. If so, I need to make sure my battery isn't dead. Does the Phone charge while showing the Samsung boot logo?? Help Please..
Click to expand...
Click to collapse
If you have decided to reflash then use ROM provided by 'voluptuary' (3.10a). And moreover, to flash, it would not matter if your battery is getting charged. Just plug the device to your PC using the USB cable and flash the device.
Be VERY sure you flash the correct ROM for your phone. If you have a version 1.3, then ONLY flash 1.3 ROMs to it. If you have a version 1.4, then ONLY flash 1.4 ROMs to it. You can find the version number under the battery on the sticker. If you flash the wrong version of ROM to it, you will end up with a brick.
When having problems like this, I would recommend flashing the Stock ROM to it first to set everything back to normal. Then, if that works fine, go to custom ROMs if desired. Stock flashing will replace everything back to new settings, including spl, radio, etc... Some of the custom ROMs are truly worth flashing, FASTER, stable, nice features.
Unokashi01 said:
If you have decided to reflash then use ROM provided by 'voluptuary' (3.10a). And moreover, to flash, it would not matter if your battery is getting charged. Just plug the device to your PC using the USB cable and flash the device.
Click to expand...
Click to collapse
I know I had 3.05a and reflashed 3.10a Clean Rom.. It works great now... I remember I use to have problems with the 3g but not after reflashing it works great