Related
I am using RA-Supersonic-v2.3 and im not use to the stuff i need to delete on the supersonic recovery mode. to the HTC hero to the HTC evo the list is alot bigger.
if this safe to wipe or am i missing something. Just asking so I don't screw anything up. I always nand back up.
[x] ALL userdata/factory reset
[x] CACHE:
[x] DALVIK-CACHE:
[x] DATA:
[ ] SDCARD: .android_secure
[ ] BOOT:
[ ] SYSTEM:
[ ] SDCARD
[ ] SDEXT
[ ] DATA:battery stats
[ ] DATA:rotate settings
also is Cache safe to wipe at anytime without having to reflash the rom, mod, and theme? i did see some people have issues and wiping the cache also helped fixxed some issues.
If your flashing a new ROM, wipe data, cache, dalvik, and SD:ext.
If your flashing a mod or kernel, wipe cache, dalvik, and SD:ext.
If your switching between Sense and ASOP ROMs and find out you have unexplained issues, wipe system as well. (I haven't needed to do this yet)
Don't forget to do multiple nandriod backups, just in case 1 of them is corrupted.
Enjoy.
Edit: Yes, flashing cache can be done anytime.
thank you very much. im currently having issues flashing roms. 3 diffrent roms keep coming up with this cant find country location and now im having issues with the google setup it keeps crashing and the home launcher doesnt load. keeps crashing as well.
Hmmm, I guess I've been lucky. I haven't had any problems yet with flashing ROMs. I make a point to religiously wipe (multiple times even) before flashing.
I've heard of possible issues with AMON_RA 2.3. I don't use it, but that's the general feeling I get from reading that thread.
Here is a bootloader image of AMON_RA 2.2.1 (its labeled as PC36IMG), load it on your SD card in the root folder. When bootloader comes on, it will scan and find this image automatically. Allow it to run and it'll give you 2.2.1.
I'd try that. Then wipe and flash using 2.2.1; see if that gets you to a working system.
@coiledwire
thank you for the tip there. but it failed also. it fails to load any rom the second i flash slayer69 dragon. sucks too. maybe its cause i used unrevoked3
You also want to be wiping system and boot between new roms, that is most likely what's causing it.
Here is a nice little zip that wipes in one swoop, flash it like a rom when going to a new rom:
http://db.tt/RtRcDLr
Its just a little script that makes wiping easier.
And I use amon 2.3 no problem so that's not the issue.
so with this i dont need to wipe anything else??? just flash that and it formats for me?
Correct, it simply wipes system, data, cache, dalvik, and boot through the zip.
awesome i will test that out and i will let u kno the outcome. and thank you!
EDIT: ok well the format.zip ROCKS..... but... the theme still didnt work. i can see the status bar but. the launcher just doesnt exist. its a solid black screen with the status bar. ive tried rebooting and still doesnt work.
idk if its cause the way im doing it or what.
kyhassen said:
awesome i will test that out and i will let u kno the outcome. and thank you!
EDIT: ok well the format.zip ROCKS..... but... the theme still didnt work. i can see the status bar but. the launcher just doesnt exist. its a solid black screen with the status bar. ive tried rebooting and still doesnt work.
idk if its cause the way im doing it or what.
Click to expand...
Click to collapse
I used unrEVOked3 also and I haven't experienced any of the problems you are.
Your theme zip file may be corrupted from downloading. I don't know if where you downloaded lists the correct md5 checksum or not. If they do, compare the one you have to the one they give. If they don't give you the correct checksum, download the theme twice and compare the checksum against each other.
If you're using a windows system, search for a checksum program. I don't remember the name of it, but I installed a free one that added that data to the properties window.
ok so if i do that, how do i deal with it after. cause ive downloaded the file 7 times and tried them all. even unrooted my phone and rerooted. tried 3 different recoveries. idk if using EVO_Radio_2.15.00.11.19_WiMAX_27167_R01_PRI_NV_1.90_003.zip
would cause it.
Is it possible the theme is incompatible with the rom?
Usually a theme replaces the rom's framework-res.apk, and if they are not compatible, you basically overwrite necessary files in that apk which will result in errors/problems.
kyhassen said:
ok so if i do that, how do i deal with it after. cause ive downloaded the file 7 times and tried them all. even unrooted my phone and rerooted. tried 3 different recoveries. idk if using EVO_Radio_2.15.00.11.19_WiMAX_27167_R01_PRI_NV_1.90_003.zip
would cause it.
Click to expand...
Click to collapse
I don't think that radio flash would cause your themed launcher from appearing. Just be careful with flashing radios, as its one of the few things that have a high chance to brick your phone if something goes wrong.
Generally you want to make sure any files downloaded aren't corrupt and you wipe before flashing. Some ROMs like to be flashed and booted into before applying any themes, while other ROMs need to have the theme installed before the 1st boot into the OS.
Seems like you're having a specific issue with the theme. I would check that theme's thread and see if anyone there has any insight for you. Sorry I can't be more help than that. Good luck.
ok well thank you for the replies. but as for the issue. the odd part is i rooted and flashed myn's warm rls5 and then the slayer69 cyan dragon theme and it loaded perfect. well i unrooted cause i had to bring the phone back to to issue. the sprint guy forgot to take the LED chip out of the white back when he put the red back on.
after that i re rooted and flashed the stuff the same way and ever since its been this way.
I use Amon RA recovery 2.3 with no issues.
Sent from my PC36100 using XDA App
i been using that one and still have issues. ive gone through a handful of different recoveries and still got the same issue. idk if i am doing i am doing something wrong or not.
Hey since we are on the topic of wiping stuff.
Anyone willing to send me the Format All zip? I have searched this forum like mad trying to find it, and I found a link for it (or so I thought) and it was broken. Figured I would ask here instead of making a new thread asking.
http://db.tt/RtRcDLr
this is the link another member posted for me. if the link doesnt work. let me kno.
kyhassen said:
http://db.tt/RtRcDLr
this is the link another member posted for me. if the link doesnt work. let me kno.
Click to expand...
Click to collapse
Works great, much appreciated
np, glad it works for u
-I have true s-off, permaroot and superCID
-ENG hboot and CWM work fine
-can successfully load and run ROMs
Device no longer sees a SIM card, yet been testing various ROMs for over 6 months with this handset.
I've taken it apart , and SIM slot looks ok.
I've tried eft wipe, superwipe, all my working nandroids, updated radio (currently running cm9/aokp40) to no avail.
Can anyone point me to how I can determine whether this is a S/W or H/W issue?
I'm leaning towards downgrading to stock/s-on then repeating the unlock to re-set my unlocked status for lack of any other options.
While googling not finding much if anything on radio data, so thanks in advance.
IF this is S/W based and you can help to fix I've a working TP2 in box as a reward/incentive.
If I am not mistaken the newer Roms need a newer SIM card, i.e.: the older ones (I think like 3-5 years old) won't be recognized with say the new radio (*.19)
I'm not sure what the new # is, but mine has 39.01a on the side, and works with the latest radio and CM9, EliteMod ICS, etc.
EDIT: But that might only refer to T-Mobile, not sure how it is with Fido/Rogers.
kbeezie said:
If I am not mistaken the newer Roms need a newer SIM card, i.e.: the older ones (I think like 3-5 years old) won't be recognized with say the new radio (*.19)
I'm not sure what the new # is, but mine has 39.01a on the side, and works with the latest radio and CM9, EliteMod ICS, etc.
EDIT: But that might only refer to T-Mobile, not sure how it is with Fido/Rogers.
Click to expand...
Click to collapse
Food for thought thanks, the SIM stopped being recognized after having flashed the "no service fix" update to this ROM http://forum.xda-developers.com/showthread.php?t=1749445 and have asked in that thread whether anything in the fix file could've set something off on my device.
IT IS an older SIM that I'm using but up to now have used every ROM with it without a hitch. I'll downgrade the radio now as an option.
igor45 said:
Food for thought thanks, the SIM stopped being recognized after having flashed the "no service fix" update to this ROM http://forum.xda-developers.com/showthread.php?t=1749445 and have asked in that thread whether anything in the fix file could've set something off on my device.
IT IS an older SIM that I'm using but up to now have used every ROM with it without a hitch. I'll downgrade the radio now as an option.
Click to expand...
Click to collapse
I noticed that it said "only for 2.7.13", though that seems to be specifically for a version of MUIU.
though when I unpack the fix :
Code:
assert(getprop("ro.product.device") == "vision" || getprop("ro.build.product") == "vision");
mount("ext4", "EMMC", "/dev/block/mmcblk0p25", "/system");
package_extract_dir("system", "/system");
unmount("/system");
Which basically only verifies that the phone is a HTC Vision (as per existing build.prop), mounts the /system partition, then extracts the package's content of /system to your rom
in this case a single file:
/system/framework/framework-res.apk
So from just that, I can't really see the fix having a prolong effect on all your other roms, unless you failed to do a full wipe (factory reset and wipe cache/dalvik cache in recovery before flashing a brand new rom).
This is the only thing I've changed in framework-res.apk:
Code:
<bool name="skip_restoring_network_selection">false</bool>
v1r0x said:
This is the only thing I've changed in framework-res.apk:
Code:
<bool name="skip_restoring_network_selection">false</bool>
Click to expand...
Click to collapse
right but even that change would be completely wiped out if he wiped/changed roms, so would have to be another factor that caused it.
kbeezie said:
right but even that change would be completely wiped out if he wiped/changed roms, so would have to be another factor that caused it.
Click to expand...
Click to collapse
Yes. Maybe it's just coincidence..
But I hope there is a fix for that problem.
Sounding like my SIM slot at this point then. But I didn't just flash the fix on its own. I first flashed the updated zip from later in the thread that included the fix w/the complete ROM. Wonder if anyone else has tried that file?
Sent from my HTC Vision using xda app-developers app
igor45 said:
Sounding like my SIM slot at this point then. But I didn't just flash the fix on its own. I first flashed the updated zip from later in the thread that included the fix w/the complete ROM. Wonder if anyone else has tried that file?
Sent from my HTC Vision using xda app-developers app
Click to expand...
Click to collapse
Maybe nothing to do with this but was using Elitemod/CM9/AOKP before flashing and "su" reported that it needed to close. I'D been experiencing few FCs with that ROM installed.
Didnt thing this would affect it once rebooted to CWM.
igor45 said:
I first flashed the updated zip from later in the thread that included the fix w/the complete ROM. Wonder if anyone else has tried that file?
Click to expand...
Click to collapse
which file do you mean with that?
igor45 said:
Maybe nothing to do with this but was using Elitemod/CM9/AOKP before flashing and "su" reported that it needed to close. I'D been experiencing few FCs with that ROM installed.
Didnt thing this would affect it once rebooted to CWM.
Click to expand...
Click to collapse
Can you be more specific on the EliteMod part, are you simply talking bout the EliteMod ICS rom, or putting EliteKernel on top of a CM9 or AOKP port? (if just the rom, I'm not aware of a 'fix' that was meant for EliteMod).
v1r0x said:
which file do you mean with that?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=28906048&postcount=74
... maybe something in yozgats file?
igor45 said:
http://forum.xda-developers.com/showpost.php?p=28906048&postcount=74
though I see it doesn't include the fix... maybe something in yozgats file?
Click to expand...
Click to collapse
Are you saying you used a fix from one rom (light) with another rom (elitemod)? I'm not getting very clear information from you just bits and pieces.
to clarify
kbeezie said:
Are you saying you used a fix from one rom (light) with another rom (elitemod)? I'm not getting very clear information from you just bits and pieces.
Click to expand...
Click to collapse
LOL - bit of a noob here though not that bad, so no I didn't mix fixes/ROMs :highfive:
I was on latest Elitemod/CM9/AOKP
To be clear,
1 - I first flashed the file from post 74 in the thread that included the bugfixes and few enhancements to the original.
(So wondering whether there's something in that file, and yes it does include the fix)
----this is where "no sim inserted" occurs---
2 - when ROM came up good but no SIM, i reverted to my nandroids, trying each one of them.
3 - then tried full wipes with fresh ROM flashes
4 - then tried superwipe/efs wipe AND updated radio and tried each nandroid/fresh installs again
5 - now downgraded radio to what I had (minus the rils) and living with WIFI only connection til I can fix the SIM issue
btw "Elitemod/CM9/AOKP" are three different roms If you just mean EliteMod ICS just say that , helps reduce the confusion. (since some people do separately install AOKP or CM9 by itself, and then flash EliteKernel on top of those).
k, as for #1 when I originally read about the 'fix', that was for a completely different rom than EliteMod and course probably wouldn't work anyways.
Secondly with EliteMod ICS, I've found that I had to be on the .19 radio (note my signature) in order to boot up with it and manage both data and wifi connection, there was no need to 'patch' anything because nik3r already included the proper ril/data for the newest radio in the rom/kernel itself. And it doesn't matter if you're on either the G2 hboot (0.76.0000 I think) or the DZ hboot like I have, since it's not a sense rom or a rom of that size.
If you are on a functional phone right now (outside of the non-Wifi data connection of course), I would recommend upgrading your recovery to 4EXT recovery first (something like the 4EXT Touch Recovery 1.0.0.5 RC5 that can be installed from the app, the app itself is found in google play and can install the recovery for you, there is a free version of the app that I have if you simply want the installer but I Recommend the paid version since you can control most of it's preferences from the app before rebooting into recovery).
From there (assuming you have everything you need backed up to the computer including say any titanium backup files):
Just to knock out a number of possibilities will just act like we're going to do a 'full' setup, assuming that 1) You are already using an ENG S-OFF hboot and 2) have already upgraded the radio to the latest .19 version
1) re-partition the SD card via 4EXT (I recommend a 2GB sd-ext, skipping the sd-ext2 and skipping swap), so that's freshly setup [that and if you chose to use the dataswap mod for EliteMod the 2GB sd-ext is needed to compliment it, never make a sd-ext less than ~1.5GB in size]
2) once you got that re-partitioned toggle the USB storage so you can copy back all the files you need including the rom files etc etc.
3) "Wipe/Format" menu to do
a) Factory Reset/Wipe
b) wipe cache+dalvik
c) Battery stats (cuz why the hell not, it *could* help lol)
4) No need to do an EFS wipe since the EliteMod rom zip does this for you upon installation, so Flashing the EliteMod Rom, then any optionals (Gtalk, google gallery, T-mobile wifi calling, DataSwap mod) on top of that.
PS: if you like to multitask active apps quite a bit (i.e.: background notifications etc), I would recommend the 64MB Dataswap mod at the very least, especially with all that free space you'll have on /data partition from the use of an sd-ext partition.
5) Reboot, once fully booted, reboot again
6) check connectivity for both SIM/Wifi/Etc.
If you're *still* having problems, even after physically pulling the sim out, blowing some dust out, or whatever you can and putting it back in, I'd start to wonder if 1) the sim is too old for whatever reason [ie: with whatever update], 2) the sim got damaged [maybe via some kind of sim update?], or 3) the sim slot is maybe damaged? 4) or the universe just hates you right now.
---------- Post added at 06:27 PM ---------- Previous post was at 06:26 PM ----------
PS: I highly recommend Titanium Backup, it's been very useful in flashing a fresh clean rom, but then being able to restore most of my applications with their settings/data intact.
kbeezie said:
btw "Elitemod/CM9/AOKP" are three different roms If you just mean EliteMod ICS just say that , helps reduce the confusion. (since some people do separately install AOKP or CM9 by itself, and then flash EliteKernel on top of those).
k, as for #1 when I originally read about the 'fix', that was for a completely different rom than EliteMod and course probably wouldn't work anyways.
Secondly with EliteMod ICS, I've found that I had to be on the .19 radio (note my signature) in order to boot up with it and manage both data and wifi connection, there was no need to 'patch' anything because nik3r already included the proper ril/data for the newest radio in the rom/kernel itself. And it doesn't matter if you're on either the G2 hboot (0.76.0000 I think) or the DZ hboot like I have, since it's not a sense rom or a rom of that size.
If you are on a functional phone right now (outside of the non-Wifi data connection of course), I would recommend upgrading your recovery to 4EXT recovery first (something like the 4EXT Touch Recovery 1.0.0.5 RC5 that can be installed from the app, the app itself is found in google play and can install the recovery for you, there is a free version of the app that I have if you simply want the installer but I Recommend the paid version since you can control most of it's preferences from the app before rebooting into recovery).
From there (assuming you have everything you need backed up to the computer including say any titanium backup files):
Just to knock out a number of possibilities will just act like we're going to do a 'full' setup, assuming that 1) You are already using an ENG S-OFF hboot and 2) have already upgraded the radio to the latest .19 version
1) re-partition the SD card via 4EXT (I recommend a 2GB sd-ext, skipping the sd-ext2 and skipping swap), so that's freshly setup [that and if you chose to use the dataswap mod for EliteMod the 2GB sd-ext is needed to compliment it, never make a sd-ext less than ~1.5GB in size]
2) once you got that re-partitioned toggle the USB storage so you can copy back all the files you need including the rom files etc etc.
3) "Wipe/Format" menu to do
a) Factory Reset/Wipe
b) wipe cache+dalvik
c) Battery stats (cuz why the hell not, it *could* help lol)
4) No need to do an EFS wipe since the EliteMod rom zip does this for you upon installation, so Flashing the EliteMod Rom, then any optionals (Gtalk, google gallery, T-mobile wifi calling, DataSwap mod) on top of that.
PS: if you like to multitask active apps quite a bit (i.e.: background notifications etc), I would recommend the 64MB Dataswap mod at the very least, especially with all that free space you'll have on /data partition from the use of an sd-ext partition.
5) Reboot, once fully booted, reboot again
6) check connectivity for both SIM/Wifi/Etc.
If you're *still* having problems, even after physically pulling the sim out, blowing some dust out, or whatever you can and putting it back in, I'd start to wonder if 1) the sim is too old for whatever reason [ie: with whatever update], 2) the sim got damaged [maybe via some kind of sim update?], or 3) the sim slot is maybe damaged? 4) or the universe just hates you right now.
---------- Post added at 06:27 PM ---------- Previous post was at 06:26 PM ----------
PS: I highly recommend Titanium Backup, it's been very useful in flashing a fresh clean rom, but then being able to restore most of my applications with their settings/data intact.
Click to expand...
Click to collapse
Yes understood that the "fix" was a trivial patch and that it pplies only to the MIUI multilang version in question - trust me I would not have mixed those two up. I opted to first flash the version from the later post since it included app/framework enhancements WITH the "no service fix"
Yes I was on Elitemod ICS (AOKP base) with modified CM9 kernel. Sorry for that confusion.
I'd previously used Elitemod AND AOKPs with my old radio with no issues whatsoever. never had to tweak a thing.
FWIW I'm on hboot .84.2000 ENG s-off and yes using clockworkmod recovery
I'd like to try 4ext - looking into it now.
Appreciate the help.
Maybe I'll put this on hold til I get a new sim from FIDO...
igor45 said:
Maybe I'll put this on hold til I get a new sim from FIDO...
Click to expand...
Click to collapse
Yea the issue in general sounds just weird overall, hopefully it'll get resolved one way or another.
kbeezie said:
Yea the issue in general sounds just weird overall, hopefully it'll get resolved one way or another.
Click to expand...
Click to collapse
Indeed - still hoping that there's someone that can offer a method of testing to see whether its a H/W issue. Must be somethng in adb and/or bootlogs? Perhaps in the bootloader for Radio.
well reading over this thread have you tried another sim? your sim in another phone? you can run some very simple tests in the diagnostics menu. go to dialer and type *#*#4636#*#*
go into phone info and play around with turning radio on and off and gsm only etc to see if anything appears ok. the best ways to test software/firmware or hardware faliure you seem to have tried, wipe fully, flash new rom, new radio...
I guess you can always try to unroot? if it still won't work then my guess is hardware
Sent from my HTC Vision using xda premium
demkantor said:
well reading over this thread have you tried another sim? your sim in another phone? you can run some very simple tests in the diagnostics menu. go to dialer and type *#*#4636#*#*
go into phone info and play around with turning radio on and off and gsm only etc to see if anything appears ok. the best ways to test software/firmware or hardware faliure you seem to have tried, wipe fully, flash new rom, new radio...
I guess you can always try to unroot? if it still won't work then my guess is hardware
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
thx for the suggestions
Have my sim working in my backup phone and works in every other phone I've tried. Yes have also tried airplane mode on/off data on/off - etc...
Did try to unroot yesterday but ran out of time, had to run off to work.
Want to do it right so will try again today as I've a bit more time.
playing with diagnostics menu now thanks.
Issue to resolve: Phone not booting into ROM, stuck at 'htc' screen. Second issue is with Google Play, says "No connection".
Any help on this is highly appreciated!
Short story:
Hello everyone.
After I got my Samsung S3 I decided to play around with my old HTC Desire a little bit. My aim was to install a ROM that would be as plain as possible, visually, so I can play around with it (which I hoped would also maximize battery life) and make it n00b friendly. CronMod seemed the way to go, what with his tweaks and the INT2EXT script etc to maximize app space. Plus didnt want to go to ICS cuz of camera issues.
However, I've been struggling with it. My phone rarely boots up after a shutdown, it just stays at the opening HTC screen and nothing happens. When it does load up into the ROM, on the rare occasion, it'll Reboot fine as many times as I ask. Its just after a shutdown that it doesnt work. Since I want to give this phone to my mom, she, not being very tech savvy, wont have the patience for this. So I need a permanent fix.
The second issue I'm having is with Google Play. It works fine for a little bit but for no reason will stop working. This happened the first time I installed the ROM, then I re-installed and it again having the same issue. I tried "Clear Data" and phone reboot but still no respite.
Phone Details:
CM7r2
6.93.1002
GSM HTC Desire
4EXT recovery.
16GB class10 card: sdcard0 ~13GB, 1.5GB EXT4, 256MB Swap. (also, if someone can explain what Swap is would also help)
Apps2SD script used: Cron's INT2EXT - seemed pretty good.
S-OFF'd and all of course - Revolutionary.io used.
I did try MIUI-Au before this, which was pretty decent, and I may just give up and move on to that if no one has a solution.
Did you changed hboot? i had the same problem when i installed miui on oxygen r2, which wasnt compatible. If you didnt change hboot i think it's the rom, i suggest you flash another one. And about swap..well the point is you dont need a swap partition. It's like another part of ram, when the ram is full the system uses the swap to free it(or something similar, i'm not good on explaining so sry if you dont understand but it's similar).
DannySID said:
Did you changed hboot? i had the same problem when i installed miui on oxygen r2, which wasnt compatible. If you didnt change hboot i think it's the rom, i suggest you flash another one. And about swap..well the point is you dont need a swap partition. It's like another part of ram, when the ram is full the system uses the swap to free it(or something similar, i'm not good on explaining so sry if you dont understand but it's similar).
Click to expand...
Click to collapse
I changed the HBOOT before I flashed the ROM on. The CM7r2 HBOOT is meant to be compatible with the ROM.
Thanks for the info on Swap, it does make it a lot clearer.
I'll probably wait a bit longer to get some more replies, and if I cant fix the issues then I suppose there's no option but to move to to a new ROM. [I really hope the Devs get the camera issue sorted with ICS roms then I'll jump ship "in a flash". ]
You have given hboot version as 0.93.XXX. A cm7r2 hboot ver should be 6.93.XXX.
check!
Sent from my HTC Desire
handy5876 said:
You have given hboot version as 0.93.XXX. A cm7r2 hboot ver should be 6.93.XXX.
check!
Sent from my HTC Desire
Click to expand...
Click to collapse
Yes, that's correct. It is 6.93.1002.
If it is just stopping at the HTC screen then I am inclined to think it may not be a ROM issue. At this stage you are still in bootloader. Will it even refuse to go to recovery when it starts acting up or for that matter is even fastboot available? If it neither goes to recovery nor can you access fastboot then that means it is hung in bootloader.
But the bootloader should be OK since a corrupt bootloader means brick. You cant boot sometimes like you seem to.
The other reason for bootloader hanging would be I guess overheating or some other hardware fault. Does the device boot up fine after you let it cool down well?
handy5876 said:
If it is just stopping at the HTC screen then I am inclined to think it may not be a ROM issue. At this stage you are still in bootloader. Will it even refuse to go to recovery when it starts acting up or for that matter is even fastboot available? If it neither goes to recovery nor can you access fastboot then that means it is hung in bootloader.
But the bootloader should be OK since a corrupt bootloader means brick. You cant boot sometimes like you seem to.
The other reason for bootloader hanging would be I guess overheating or some other hardware fault. Does the device boot up fine after you let it cool down well?
Click to expand...
Click to collapse
I can get into Recovery fine every time - VolumeDown + Power -> Fastboot -> Recovery.
I cant seem to get into the ROM anymore. It does warm up pretty quickly if I leave trying to boot up but I figured that was because of the screen drawing more power due to constant white screen. What I did find earlier in the day was that if I held down VolDown+Power+Trackball (is that hard reset..?) at that HTC screen it would sometimes restart the phone and then it would load up to the ROM - but its hit and miss. Like right now it just wont work.
kashman007 said:
I changed the HBOOT before I flashed the ROM on. The CM7r2 HBOOT is meant to be compatible with the ROM.
Thanks for the info on Swap, it does make it a lot clearer.
I'll probably wait a bit longer to get some more replies, and if I cant fix the issues then I suppose there's no option but to move to to a new ROM. [I really hope the Devs get the camera issue sorted with ICS roms then I'll jump ship "in a flash". ]
Click to expand...
Click to collapse
What do you mean camera issue? Sandvold's ics rom camera works very well, so what' problem you mean?
DannySID said:
What do you mean camera issue? Sandvold's ics rom camera works very well, so what' problem you mean?
Click to expand...
Click to collapse
Arent there still stutter issues when making videos?
Anyway, I'd still like to fix the issues with this ROM.
kashman007 said:
Issue to resolve: Phone not booting into ROM, stuck at 'htc' screen. Second issue is with Google Play, says "No connection".
Any help on this is highly appreciated!
Short story:
Hello everyone.
After I got my Samsung S3 I decided to play around with my old HTC Desire a little bit. My aim was to install a ROM that would be as plain as possible, visually, so I can play around with it (which I hoped would also maximize battery life) and make it n00b friendly. CronMod seemed the way to go, what with his tweaks and the INT2EXT script etc to maximize app space. Plus didnt want to go to ICS cuz of camera issues.
However, I've been struggling with it. My phone rarely boots up after a shutdown, it just stays at the opening HTC screen and nothing happens. When it does load up into the ROM, on the rare occasion, it'll Reboot fine as many times as I ask. Its just after a shutdown that it doesnt work. Since I want to give this phone to my mom, she, not being very tech savvy, wont have the patience for this. So I need a permanent fix.
The second issue I'm having is with Google Play. It works fine for a little bit but for no reason will stop working. This happened the first time I installed the ROM, then I re-installed and it again having the same issue. I tried "Clear Data" and phone reboot but still no respite.
Phone Details:
CM7r2
6.93.1002
GSM HTC Desire
4EXT recovery.
16GB class10 card: sdcard0 ~13GB, 1.5GB EXT4, 256MB Swap. (also, if someone can explain what Swap is would also help)
Apps2SD script used: Cron's INT2EXT - seemed pretty good.
S-OFF'd and all of course - Revolutionary.io used.
I did try MIUI-Au before this, which was pretty decent, and I may just give up and move on to that if no one has a solution.
Click to expand...
Click to collapse
Maybe your Desire's partitions are somehow corrupted. Use 4ext to check partition, or do a full wipe, including sdfat32.
I would wipe davlik cache and perform a system wipe/factory reset from recovery then install CM7 as this is pretty plain and can be easily customised. Also you can install S2E from the play store to manage your A2SD with no separate script needed. Hopefully you don't have anything on the phone you need to back up. With any luck this might fix your play store issue too.
Sent from my HTC Desire using xda app-developers app
@panpjp: I did al that but it still didnt work, unfortunately.
@hans: I've given up on CronMod now. I just went with Marange MIUI. Its working fine so far but the data2ext script doesnt seem to be as smart as the INT2EXT I had installed with the CronMod. At least its working ok. The other issue with it is the Video Recorder - it's very jerky, so the videos do have a lot of stutter, as I had suspected/speculated. Oh well, hopefully an update will fix that.
kashman007 said:
@panpjp: I did al that but it still didnt work, unfortunately.
@hans: I've given up on CronMod now. I just went with Marange MIUI. Its working fine so far but the data2ext script doesnt seem to be as smart as the INT2EXT I had installed with the CronMod. At least its working ok. The other issue with it is the Video Recorder - it's very jerky, so the videos do have a lot of stutter, as I had suspected/speculated. Oh well, hopefully an update will fix that.
Click to expand...
Click to collapse
I have come across this issue once with 1 out of the 4 desires I have personally installed my rom on. Change the kernel to cronmodkernel 1.2 or a kernel of your choice and it will boot and shutdown. I am working hard to find the cause of the issue
kashman007 said:
@panpjp: I did al that but it still didnt work, unfortunately.
@hans: I've given up on CronMod now. I just went with Marange MIUI. Its working fine so far but the data2ext script doesnt seem to be as smart as the INT2EXT I had installed with the CronMod. At least its working ok. The other issue with it is the Video Recorder - it's very jerky, so the videos do have a lot of stutter, as I had suspected/speculated. Oh well, hopefully an update will fix that.
Click to expand...
Click to collapse
To make sure flash gb ruu and take to service.
Sent from my HTC Desire using xda app-developers app
croniccorey said:
I have come across this issue once with 1 out of the 4 desires I have personally installed my rom on. Change the kernel to cronmodkernel 1.2 or a kernel of your choice and it will boot and shutdown. I am working hard to find the cause of the issue
Click to expand...
Click to collapse
I hate to ask this question, since I'm sure you're busy fixing bigger issues, but what exactly is a kernel? I know the ROM is like an OS on a PC but then what is the kernel? How would I install it (is it just the same ol' Recovery --> Install from sd but without any wiping?) and why would it fix the issue with my phone?
Thanks.
kashman007 said:
I hate to ask this question, since I'm sure you're busy fixing bigger issues, but what exactly is a kernel? I know the ROM is like an OS on a PC but then what is the kernel? How would I install it (is it just the same ol' Recovery --> Install from sd but without any wiping?) and why would it fix the issue with my phone?
Thanks.
Click to expand...
Click to collapse
The kernel is what runs the OS it is a Linux kernel patched for the arm architecture it contains the drivers as well as it is responsible for booting the phone and also is the layer between the hardware and software.
For a more in depth explaination PM me
Sent from my HTC Desire using xda app-developers app
kashman007 said:
I hate to ask this question, since I'm sure you're busy fixing bigger issues, but what exactly is a kernel? I know the ROM is like an OS on a PC but then what is the kernel? How would I install it (is it just the same ol' Recovery --> Install from sd but without any wiping?) and why would it fix the issue with my phone?
Thanks.
Click to expand...
Click to collapse
To put it simply, it's just a bunch of codes that makes the link between the hardware part and software part.So without it the software part doesnt know how to use the hardware part. And yes you can flash it from recovery and since it's a part of the rom, maybe the rom's kernel it's deffective or something, it's worth to try.
I'm suddenly having storage issues with every ROM that I flash after running a ROM with some script that isn't widely used.
First I'll give you a brief idea of my problem. I"m running out of storage and get notifications from the market saying as much after I download and reasonable amount of apps. The thing is... It show's I have used 738MB of ext4 out of 1.5 so that isn't the issue. The problem is internal memory. My phone won't move dalvik cache for some reason. When I run any ROM with a2sd or m2sd they both say that there is a problem and leave the dalvik cache where it is.
I think my internal folders are jacked up from 40ad2sdx or a zip that was used to clear memory before the ROM. There was a ext4 superwipe cleaner to load before the ROM. I did that without researching first. When I did go looking for the thread about it, it plainly said that it was for one phone only, and it wasn't my phone. I believe it was the Galaxy S3, but I can't be certain. It was a week ago. It was advised not to use it on any other phone because part of what it did was reset the internal folders. Does this mean I can now flash a ROM for the galaxy s3? Lol Just kidding.... Seriously, the second part is all my speculation and I have been wrong many times concerning android. Will somebody help me get my phone back in oem condition please?
Okay, I'm not even sure what you did here, because not knowing the script, anything could have happened.
Try wiping everything and flashing stock rooted here, then go from there with other roms after that.
If that doesn't work. Here's what I would do. It might be a major pain, but it is almost a surefire fix.
Unroot and return to stock, then root again.
[UNROOT]
[ROOT]
For future reference, NEVER flash anything that is meant for another device. (Obviously, if it's a port then you're ok.)
ALSO EXTREMELY IMPORTANT: Backup your SD card, and wipe that puppy clean!! Only partition using Amon-RA recovery, otherwise it will screw you up quite often. I repeat, if you do not have the partition done correctly, then odds are that A2SD or equivalent won't work.
nate234 said:
Okay, I'm not even sure what you did here, because not knowing the script, anything could have happened.
Try wiping everything and flashing stock rooted here, then go from there with other roms after that.
If that doesn't work. Here's what I would do. It might be a major pain, but it is almost a surefire fix.
Unroot and return to stock, then root again.
[UNROOT]
[ROOT]
For future reference, NEVER flash anything that is meant for another device. (Obviously, if it's a port then you're ok.)
ALSO EXTREMELY IMPORTANT: Backup your SD card, and wipe that puppy clean!! Only partition using Amon-RA recovery, otherwise it will screw you up quite often. I repeat, if you do not have the partition done correctly, then odds are that A2SD or equivalent won't work.
Click to expand...
Click to collapse
I did the wipe and flash to stock earlier today, then flashed the Pac man ROM but the issue is still there. I had looked at unrooting my phone earlier today also. I'm glad to read this because it lets me know that I do have some idea of what to do. Thanks for the reply. I'll post here again with the results. Check back soon.
EDIT----> Man, my phone is okay. I loaded up a fairly recent ROM by Tronit, and it worked fine. It was the ROMs. Just to be sure, I went back to the last two ROMs just to see, and they did the same thing again. Now I'm on the AOKP Unnoffical and it's working just fine. The a2sd is working perfectly like it should, and my dalvik cache is moving to ext4. It was just coincidental that the last three ROM's I loaded all have issue with the a2sd. It's funny how nobody else see's problems but me. I looked in the bin file of one of them and it's missing part of the a2sd file. The other two have weird init.d files that I don't know anything about. I'm assuming the a2sd problem is related to that. It's funny how I see lots of problems, and report them, but I get blown off by some people as a noob who is making mistakes. I am a noob, and I do make mistakes, but I know some of my theories about problems are correct...... I gotta get me some respect by compiling my own ROMs.
Status update..... My phone is jacked up for sure. It does work with the AOKP Unofficial by Tronit, but this morning when I cleared my cache with Smelkus Recovery, it had major problems with almost every app. Clearing the cache in recovery is something I've done with every ROM and this has never happened. I uninstalled all the apps and reinstalled them. Got them working again. Everything seemed to be okay. However, when I cleared my cache with Android Tuner, again it ruined every app. I've used android tuner every day for two months to clear the cache and never had problems like this. Something is very wrong.
*****edited and deleted for the sake of peace*****
Long story short, I flashed something made for another phone. I can't explain why I did this without taking up lots of pages, and it doesn't even matter really. Lets just focus on the solution. Here is the link. I flashed both of the zips in the link.
http://forum.xda-developers.com/showthread.php?t=1477955
So I think my permissions for the files on my phone are out of whack. Is that what I"m reading is the possible outcome of flashing these if your phone is not the one listed? Please post your thoughts. I need them.
Try backing up your SD card on a computer and format you SD card and repartion it
Sent from my PC36100 using Tapatalk 2
g2435 said:
Try backing up your SD card on a computer and format you SD card and repartion it
Sent from my PC36100 using Tapatalk 2
Click to expand...
Click to collapse
I did that. Both with Smelkus, and Mini partition wizard. Same problems. I just tried to fix permissions with smelkus 4.3 on the AOKP Unofficial ROM and it took a minute for it to do it's thing. The line of dots was two full rows. So when It loaded back up, I suddenly see the same disk Icon in my notification bar, and now this ROM says it it out of memory. Man, it was working fine. I had twenty more apps on it too and I uninstalled them. It was working fine then, so with twenty less apps, it shouldn't suddenly say "Running out of Storage space."
I have told you this already: Please do not flash things meant for other phones, it could mess up. If it's meant for another device, it might screw yours up. To stay on the safe side: If it's not generic (works for every Android phone) or phone specific (exclusive to the Evo 4G) then don't flash it.
nate234 said:
I have told you this already: Please do not flash things meant for other phones, it could mess up. If it's meant for another device, it might screw yours up. To stay on the safe side: If it's not generic (works for every Android phone) or phone specific (exclusive to the Evo 4G) then don't flash it.
Click to expand...
Click to collapse
I flashed this about a eek ago, when I was looking for the ext4 wipe. I thought it was the same thing as another zip despite what it said. Stupid... I know. I think this may be the cause of my problems, but I can't be sure. I don't know at all really. Just speculations. I reflashed the CWM touch and used to flash a stock ROM. Gonna try that again. I ran the test on CWM touch and it said that the
/sys/class/android_usb/android0 was missing and unable to perform the test. Can this be the cause of my problems?
Don't beat yourself up man, it was an honest mistake, just learn from it and you'll be alright.
Now the optimal recovery for this device would be the Amon-RA recovery, and I recommend redoing what I said in my first post once you have Amon-RA installed. Amon-RA is an awesome recovery, and it's super easy to install. Check out this easy-to-follow video on how to install by clicking here.
Do that, then do what I said in the previous posts. Let me know what happens, because I'm almost certain this should work.
nate234 said:
Don't beat yourself up man, it was an honest mistake, just learn from it and you'll be alright.
Now the optimal recovery for this device would be the Amon-RA recovery, and I recommend redoing what I said in my first post once you have Amon-RA installed. Amon-RA is an awesome recovery, and it's super easy to install. Check out this easy-to-follow video on how to install by clicking here.
Do that, then do what I said in the previous posts. Let me know what happens, because I'm almost certain this should work.
Click to expand...
Click to collapse
I tried loading the Pacman ROM again with CWM and it wouldn't even load. It gets stuck in a bootloop. After that I flashed smelkus and went back to the Stock Rom.
*****edited and deleted for the sake of peace****
RADIO EDIT------
Sent from my PG86100 using xda app-developers app
edited and deleted for the sake of peace
As I stated in my pm give me a day or so till I get back home and I will check into a fix for you. Only don't expect any one on one help. If the fix works cool if not I will dig further. TNN strives to help with any issue no matter who is at fault. I will look at the wipe script you flashed and see if it can be undone. Just be prepared of the possibility that your phone may never work correctly again.
Sent from my PG86100 using xda app-developers app
I was finally able to get my phone straightened out. I loaded up a stock ROM then decided to use my SD Maid to look around. I found a file with completely different dates on it, but it wouldn't let me remove it. I ended up copying everything else in the subfolder and then deleted the parent folder. Then added everything else back. Wah lah.... magic. I don't know what that file was or where it came from but it was killing my internal memory. I'm wondering how it stayed from ROM to ROM. I dunno, but it's gone, and the Pacman ROM is lovely now. BOOM!!!!
jlmancuso said:
As I stated in my pm give me a day or so till I get back home and I will check into a fix for you. Only don't expect any one on one help. If the fix works cool if not I will dig further. TNN strives to help with any issue no matter who is at fault. I will look at the wipe script you flashed and see if it can be undone. Just be prepared of the possibility that your phone may never work correctly again.
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
Whatever I did only fixed part of the issue. I'm left with in a situation where every time I go into recovery my downloaded apps stop working. It is cutting part of them off whether I clear cache or not. All I have to do is power off into recovery, and when I reboot, all of my downloaded apps begin giving messages that "Unfortuately such ans such has stopped." My phone becomes inoperable. The only way I can keep it working is to send a new launcher to my phone from the market, let it install, then open it up and uninstall all the downloaded apps. I'm pretty sure this is an easy fix for someone like you Mancuso. I have a logcat and it show LOTS of errors that I have never seen before on any of my other logcats. What are my options? Tell me what to do to get my phone back to absolute OEM and then I'll reroot. UNLESS you know of some fix.
I've supplied a logcat from Catlog if you or anybody else wants to have a look. I'd really appreciate some help here. I love my Evo and I love learning this stuff. If somebody can help me positively identify the problem, I can most likely figure it out from there. Please give me your suggestions here. I'm nothing without some guidance on this. It's way out of my scope.
I've included a link to the ext4 script wipe that I used. How I got to this page, I do not know. However, I ran it because this page said it COULD POSSIBLY work on other phones despite the fact that it was made for another phone.
http://www.xda-developers.com/android/darkside-super-wipe-easily-wipe-partitions-when-flashing-roms/
And I flashed both zips from the thread that the story links users to. Here is the link for the two zips.
http://forum.xda-developers.com/showthread.php?t=1477955
I'm not sure this is the problem. I'll try to find the Vold.fstat thread that I tried on my own before you came up with the 40ad2sdx solution for the MIUI ROM.
This is the memory fix I tried as mentioned above.
http://forum.xda-developers.com/showthread.php?t=2246909
Please note that you see before and after pics of sd storage. You can see that my pics clearly resemble the after pics shown in this thread. I believe this is my problem. How can I undo this?
This post reflects the only things I did outside of normal flashing. My problem is here somewhere...
The fix you used is for samsung devices. That could have caused your problems.
Ok here it goes. my network service is off so i use my droin inc for games and such. running custom rom wildstang83 IceCream Scencless 1.0. im not sure what happened to my phone but i left for 3 days and come back to my phone being totally jacked up. It wot dl apps the google play reverted back to the old market icon. wont save my passwords for google sighn in. every time i go to youtube it says to re dl the google play services. im sure other stuff is messed up too. i have tried to flash another rom but when it gets loaded back up it keeps saying process. whatever failed and there a bunch of those that loop and i have to pull battery. when i try to factory reset it says everything was formatted but when i reboot phone its the sme as it was before apps and all. So is there anyone out there who can help me with this. Sorry if i posted in the wrong place or what not. i wasnt sure where to post it cuz its kinda an advanced question but not really a question just need help.
not a virus but it does sound like your phone might have exhausted all the space in the /data folder. I had a similar thing happen to me before I rooted and fixed my phone where i exhausted the space, itt went a factory reset and put the phone into an unusable state.
i don;t know anything about the rom you are running but are rooted and have CWM installed? if so, you should be able flash a new ROM to your device, GAPPS and optionally, the low space disk fix.
tekweezle said:
not a virus but it does sound like your phone might have exhausted all the space in the /data folder. I had a similar thing happen to me before I rooted and fixed my phone where i exhausted the space, itt went a factory reset and put the phone into an unusable state.
i don;t know anything about the rom you are running but are rooted and have CWM installed? if so, you should be able flash a new ROM to your device, GAPPS and optionally, the low space disk fix.
Click to expand...
Click to collapse
Yes i do have cwm but i tried to flash a new rom via the recovery section. after i choose the zip to flash everything goes as expected untill after the reboot and it goes into the setup part where u have to put gmail password and stuff in then it basically freezes up with unlimited process failures. but i will try again. cant hurt from where it is now.
if you are not doing so already, i would wipe cache and dalvik cache after flashing the rom. that may fix the FCs.
I would also suggest you run a newer jelly bean ROM like Tiny;s 5-16 with his version of GAPPS(4-05) version plus the low space disk fix so you can maintain parity with what is the latest.
I am currently using evervolve 6-25 and it is working well for me.
the reason I say that is these newer JB roms have the ability to let you skip the activation easily. I don;t know if it was some feature of GB roms but the activation wizard in the JB roms seem to be better my opinion.
When switching to a different ROM, it is crucial to wipe /system. This can be a source of FCs. Also, if switching, it is also a good idea to do factory reset.
tekweezle said:
if you are not doing so already, i would wipe cache and dalvik cache after flashing the rom. that may fix the FCs.
I would also suggest you run a newer jelly bean ROM like Tiny;s 5-16 with his version of GAPPS(4-05) version plus the low space disk fix so you can maintain parity with what is the latest.
I am currently using evervolve 6-25 and it is working well for me.
the reason I say that is these newer JB roms have the ability to let you skip the activation easily. I don;t know if it was some feature of GB roms but the activation wizard in the JB roms seem to be better my opinion.
Click to expand...
Click to collapse
I just flashed another rom i used in the past by the same dev and so this is my step by step. 1. choose zip from sd. 2. factory reset. 3. wipe dalvik cache. 4. wipe cache partition. If this doesnt work i will try jb roms but i would hate to have to dump the dev that im useing. there the most stabe roms i have come across so far
PonsAsinorem said:
When switching to a different ROM, it is crucial to wipe /system. This can be a source of FCs. Also, if switching, it is also a good idea to do factory reset.
Click to expand...
Click to collapse
what do u mean wipe /system. where do i find that. only reason i ask is cuz maybe ive never done that. but i have never had a problem withthe other 15 roms i have flashed before so thats why im so confused about what happened to my phone. all i did was shut it off and leave it home. nothing changed from my daily use before that and it was working top notch before i shut it off
im getting settings fc. youtube fc, my uploads fc, market fc, clock widget fc, internet fc, rss reader fc, htc sence fc, all those off of a fresh flash ad new sd card
Just lost my bckups that were saved on sd card so now i cant even get on it i dont get it. its not bricked but yet it i unstabe to run any rom but the preivious saved backup (now there deleted)
maybe the rom you downloaded is corrupt. worst case scenerio is that your phone is on it;s last legs.....
i would suggest you try downloading the JB rom and Gapps plus the low space fix.
http://forum.xda-developers.com/showthread.php?t=2050930
it;s kind of proven to work in my opinion. the 5-16 build is pretty stable.
what I do is flash the rom zip, gapps zip and low space zip, then wipe cache and dalvik. it probably should not make a difference but I am using TWRP as my recovery instead of CWM.
goodluck!
tekweezle said:
maybe the rom you downloaded is corrupt. worst case scenerio is that your phone is on it;s last legs.....
i would suggest you try downloading the JB rom and Gapps plus the low space fix.
http://forum.xda-developers.com/showthread.php?t=2050930
it;s kind of proven to work in my opinion. the 5-16 build is pretty stable.
what I do is flash the rom zip, gapps zip and low space zip, then wipe cache and dalvik. it probably should not make a difference but I am using TWRP as my recovery instead of CWM.
goodluck!
Click to expand...
Click to collapse
Thank u and its still not working. probably just takeing a dump on me now it is just bootlooping.
when i do a factory reset i get a wipe completed. but it says "no app2sd partition found. Skipping format of /sd-ext" could that be part of the issue?? ive never noticed that before
i don;t know if switching to TWRP might help you but it might be worth a try. maybe a coincidence but the last time I had a screw up on my Dinc installing a ROM, i was using CWM. I switch right after that. I think i did read something about TWRP specifically supporting the EXT4 Low space fix.
maybe someone more knowledgable can chime in.
tekweezle said:
i don;t know if switching to TWRP might help you but it might be worth a try. maybe a coincidence but the last time I had a screw up on my Dinc installing a ROM, i was using CWM. I switch right after that. I think i did read something about TWRP specifically supporting the EXT4 Low space fix.
maybe someone more knowledgable can chime in.
Click to expand...
Click to collapse
i will try it but it is doing the same thing on every rom i have tried to flash. ive tried 6 different roms so far and i have ran them all in the past so im incined to think its jacked. and is there a specific twrp for the different roms or can i just dl the latest version and it will work