Related
Hi, hope im posting in the right section.
i have had my desire since it came out , rooted it straight away , flashed loads of diffrent roms (from here) but now all of a sudden my desire has started crashing all the time and when i say all the time i mean about every 15 mins. I take the battrey out, boot use it for a min then when i next go to use it it wont do anything and i have to take the battrey out again and boot.
i have tried lots of diffrent roms it still does the same, i have even tried to run backups from rom manager and still the same. i have run antivirus still the same.
any ideas
thanks
It sounds like a kernel issue (too much undervoling or overclocking maybe, and some ROMs might not contain a kernel image), but first of all it would help us if you told us what ROM you're actually using right now.
Try to flash your sd rom.
If you use a2sd..partition again.
Full wipe again and flash you favorite rom.
If the problem still percist....Flash an official rom better old one 2.1 for no change to newer boot. Test the device if still freeze.
If everything ok, root again your phone ...partition again sd and then flash your favorite rom.
I've been having the same problem mate. Just flashed back to stock 2.1 and all seems fine now. Will reroot later this week and see what happens!
Sent from my HTC Desire using XDA App
Moved to Q&A.
Please do not post question threads in Development.
Post What Where:
General - general technical discussion items, news, anything else that does not fit into the other fora categories.
Q&A (Questions and Answers) - all questions, irrespective of type, get posted in here whether they be theme related, accessory related, technical, etc.
Accessories - any items to do with components and/or accessories relating to your device.
Rom Development - only meant for very advanced technical discussion directly related to ROM development activity and the delivery of actual ROMs and ROM components ONLY. Nothing else goes in here.
Themes & Apps - anything to do directly with the development of themes and/or applications. Nothing else goes in here.
Right sorry for the late reply the misses made me paint the kitchen before the new floor was put in.
well tried everything so then tried flashing back to stock but it carnt find bootloader (using magic mem card)
any more idea's?
ps im using aurxtsense 8.0
i was thinking it was something to do with clocking as well.
mine seams to have calmed down now, it still couldn't find bootloader though when i tried to flash a stock ruu.
i formated my memory card and re-flashed aurxtsense 8.0 and it hasn't crashed since.
haven't tried doing anything since because i aint got time to sit and sort it out at the mo if something goes wrong again
Not sure what the means but you should be able to flash the ruu from HTC or if your phone is branded then one from the network. There's a like to them all in the dev section.
Can tell u though that I flashed back to stock and had no problems. Bit since rooting again its back. Even wiped my SD card and recreate the partitions. Doesn't seem as frequent this time though. I went straight to a hd Rom. It never used to happen on older custom roms and do think its something to do with the volting & clocking.
Sent from my HTC Desire using XDA App
Hey everyone,
I'm really new to android modding, and don't know much about all this. I'm good at modding but never been on android before. I went through the stickies and full desire guide etc threads, but its really getting confusing for me.
I've come to know some things: (correct if wrong)
1) You have some custom ROMs which you can flash after rooting the phone.
2) Most ROMs have pretty much everything working, but some things don't work on some ROMs (like camera for some)
3) Rooting voids warranty.
Seeing the vast amount of ROMs in the development section, I'm confused which one to look for. Can anyone suggest me which would be the best (stable and everything working) ROM for me? I basically need APP2SD or APP2SD+ (NOT the froyo one because its useless, I'm talking about the custom one) and minor tweaks like changing the homescreen etc.
Which would be the best suited ROM for above description? Basically, what criteria decide which ROM to put on the phone?
@Moderators, sorry if its the same old story. I'm really confused and so HAD to make a thread.
Hi and welcome. A couple of points I can help you with:
There are loads of roms to choose from, I am using this rom atm:
http://forum.xda-developers.com/showthread.php?t=768703
Everything on this particular rom works fine and is very fast and stable. I generally find if roms have several revisions then are are generally very good. i.e. are having continuous support and developement.
As for rooting voiding warranty? Well this is no longer an issue as rooting can easily be reversed )
Hope this helps
LEWY
thehrushi said:
Hey everyone,
I'm really new to android modding, and don't know much about all this. I'm good at modding but never been on android before. I went through the stickies and full desire guide etc threads, but its really getting confusing for me.
I've come to know some things: (correct if wrong)
1) You have some custom ROMs which you can flash after rooting the phone.
2) Most ROMs have pretty much everything working, but some things don't work on some ROMs (like camera for some)
3) Rooting voids warranty.
Seeing the vast amount of ROMs in the development section, I'm confused which one to look for. Can anyone suggest me which would be the best (stable and everything working) ROM for me? I basically need APP2SD or APP2SD+ (NOT the froyo one because its useless, I'm talking about the custom one) and minor tweaks like changing the homescreen etc.
Which would be the best suited ROM for above description? Basically, what criteria decide which ROM to put on the phone?
@Moderators, sorry if its the same old story. I'm really confused and so HAD to make a thread.
Click to expand...
Click to collapse
You do indeed need to Root the device before flashing, the only ROM that don't have 'things working' is the Desire HD ROM. I am not sure if that has been fixed or not yet though. All the other AOSP and Sense based Desire ROMs have everything working just fine. Rooting will void your warranty but it's super easy to reverse so there is nothing to worry about.
The most popular ROMs by far seem to be the AOSP (Android Open Source Project) ROMs (Non-Sense ROMs), all of them will have APP2SD built into them, the Sense ROMs also have APP2SD built into them.
LeeDrOiD is by far the most popular Sense based ROM, RCMixHD is the Desire HD based ROM, which I think still doesn't have the camera working.
And by far the most popular Desire ROM overall is the ASOP Cyanogen based DeFrost.
To get the most out of APP2SD you will need to download ROM Manager and create an EXT3 partition on your SD card so the ROM will place all of the Froyo compatable apps into the partion and not your internal memory.
Being brand new to the desire, I've flashed every Rom available in the last 2 weeks.
Leedroid is a very good sense Rom. I prefer having a Rom with sense right now because this is my first HTC.
Right now I'm running the Aurax sense Rom, solely because it has its own setCPU built in.
The hd roms didn't impress me that much, not yet at least, with a little more time they will be awesome though.
The MIUI roms are also amazingly pretty, if you don't mind the iPhone feel. My only problem with it though, and I've been told this hardly happens, my battery life was pathetic.
At the end of the day though, apart from the hardware, it is android and all the available apps that make our phone so great.
All the custom roms do add a lot of speed to the phone though, you have to do a quadrant after you flash so that you can see how awesome the Rom makes your phone run. They also add additional functionality compared to the stock Rom.
Honestly, I can't see why anyone would keep any Android device stock when there are such amazing roms around. At the end of the day its all down to your own preferences and what functions you like. You'll love any Rom you flash.
Sent from my HTC Desire using XDA App
Thanks for such amazing replies. Meanwhile, I've also been through many ROMs and their descriptions. The terminologies are kinda new for me, but I can understand many things now....
The only thing I care about right now is App2SD because I found FroYo's move to SD doesn't help much. Also second thing is that I'm not having MY desire yet, its my friend's device m gonna try out everything on! So I'd be taking some extra care!
One big relief is that rooting is reversible. That'd be cool.
What are the odds of bricking your phone while flashing or applying mods?
thehrushi said:
Thanks for such amazing replies. Meanwhile, I've also been through many ROMs and their descriptions. The terminologies are kinda new for me, but I can understand many things now....
The only thing I care about right now is App2SD because I found FroYo's move to SD doesn't help much. Also second thing is that I'm not having MY desire yet, its my friend's device m gonna try out everything on! So I'd be taking some extra care!
One big relief is that rooting is reversible. That'd be cool.
What are the odds of bricking your phone while flashing or applying mods?
Click to expand...
Click to collapse
It is honestly impossible to brick a desire. I bricked my MOTO backflip, there was no coming back from that. With the desire I flashed something that didn't work, but pressing volume down and power gets you right into the hbooot menu, from there just mount as usb and copy over a new Rom to flash.
The one thing you need to remember, when flashing new roms the first boot takes a while, never pull the battery thinking there's nothing happening, that will destroy your phone and there's no coming back from that.
Before every Rom you flash make sure to do a factory reset in the recovery menu, that ensures that the new Rom will work to its full capability and minimizes the chances of experiencing problems.
Sent from my HTC Desire using XDA App
thehrushi said:
What are the odds of bricking your phone while flashing or applying mods?
Click to expand...
Click to collapse
You can brick your device flashing Radios, but you can always send it back to HTC, pay them an extortionate amount and they will revive it for you. But overall, the chances are slim to none in my experience.
Just make sure, after rooting, you make a Nandroid backup of the OS. Then you can do whatever you like to the phone and it will be reversable.
I keep a Nandroid of my DeFrost ROM, and one of my PaysROM, and I have one of my MoDaCo R8, you can switch between them just using Recovery, as the mood takes you, absolutely everything will be exactly as it was everytime you load the backup back onto the phone, I just wipe the cache, Dalvik Cache, factory reset the ROM then reinstall whichever ROM I want to use (DeFrost, PaysROM etc etc) from the SD card and then backup from the Nandroid.
Depending on the age of your desire, you shouldn't need to flash a radio though. I've never needed to flash a radio, but that's because my desire came with the latest radio, thankfully it still has the amoled screen.
If you do need to replace the radio and somehow brick it, if its still under warranty HTC will replace it for you because there is no way that they can prove you bricked the device.
Sent from my HTC Desire using XDA App
Kalavere said:
Just make sure, after rooting, you make a Nandroid backup of the OS. Then you can do whatever you like to the phone and it will be reversable.
I keep a Nandroid of my DeFrost ROM, and one of my PaysROM, and I have one of my MoDaCo R8, you can switch between them just using Recovery, as the mood takes you, absolutely everything will be exactly as it was everytime you load the backup back onto the phone, I just wipe the cache, Dalvik Cache, factory reset the ROM then reinstall whichever ROM I want to use (DeFrost, PaysROM etc etc) from the SD card and then backup from the Nandroid.
Click to expand...
Click to collapse
Wow that means you install a ROM, make settings you want, put in your data (phonebook etc) and then take a full backup. Switching between them is as easy as restoring a backup!
Is that right?
Initially, I'd be trying out ROMs, and would stick to the one which suits me best. I just can't wait before my desire arrives this monthend!!
thehrushi said:
Wow that means you install a ROM, make settings you want, put in your data (phonebook etc) and then take a full backup. Switching between them is as easy as restoring a backup!
Is that right?
Initially, I'd be trying out ROMs, and would stick to the one which suits me best. I just can't wait before my desire arrives this monthend!!
Click to expand...
Click to collapse
It saves everything, app data, messages, settings, the lot. Although when switching ROMs I still factory reset, wipe the caches and reinstall the ROM I want to use before loading the backup of that specific ROM. I am not sure things will go so smoothly if you just reload the backups without factory resetting and reinstalling the ROM first, but it won't hurt to try.
Kalavere said:
It saves everything, app data, messages, settings, the lot. Although when switching ROMs I still factory reset, wipe the caches and reinstall the ROM I want to use before loading the backup of that specific ROM. I am not sure things will go so smoothly if you just reload the backups without factory resetting and reinstalling the ROM first, but it won't hurt to try.
Click to expand...
Click to collapse
Exactly!
Hello there everybody,
I've been searching for a new Android phone under £200 for the past few days and I stumbled across the HTC One V and it seems like a good upgrade from my OSF2 but I just have a few questions before I decide on ordering it in a few weeks time.
I'll be buying it from ASDA online for only £179 sim-free which seems to be a pretty good deal so I'm just wondering what to expect (in terms of quality of the design etc) from the device when compared to the lower budget phones I've purchased in the past- Samsung Galaxy Europa I5500 and the Orange San Francisco II (OSF2).
I'll be rooting/installing custom recovery and ROMs as soon as I'm comfortable with the device (Which will probably be within a few days) so I understand the toolkit is a pretty easy-to-use tool but I'm wondering which Custom Recovery is the best/most reliable for the HTC One V, on my past devices I've always used Clockworkmod but if the other recoveries are better for the One V then I'll be sure to flash the most compatible/reliable recovery.
Which Custom ROMs are fully working and also is there any ROMs that are fully working and have the stock ICS/JB appearance as I'm not really a fan of the actual appearance of HTC devices although I could learn to love it I guess! So which ROMs would you guys recommend for a fully working/stable daily use device and is there any fully working stable Jelly Bean ROMs?
Finally, I noticed a thread about the HTC One V having a nag for getting bricked easily, some of the things were ridiculous such as holding a certain button combination and when the battery is low it will die and not turn back on. Just wondering if it's a major issue.
Thanks for the taking the time to read this.
Curtis.
EDIT-
I forgot to ask;
Does A2SD scripts + A2SDGUI work on this device? I like to move my Dalvik Cache to my 16gb class10 SD so it'd be nice if it works and how do I know which type of device my phone is as I heard there's something about an International version and a Virgin version (Primou or something like that? I'm completely lost) And finally; what's a stable over-clock for this device? My current phone is 800mhz but is overclocked to 122-902mhz with no issues, just wondering what kinda speed I can boost the One V up to.
Thanks again.
Bump!
Quite eager to get an answer before I purchase!
I can help a little
There are two recoveries for the one v
TWRP 2.3.1 and CWM 6.0.1
If you are Europe you will get the PrimoU (primo means one U probably means international) it is GSM
The PrimoC is the CDMA version now with its own forum so GSM is under android dev and CDMA is under CDMA dev.
I reccomend the TWRP recovery because I love having a touch screen recovery.
OC and UV settings:
OC'ing: 345min - 1200 or 1500 Max
UV'ing: 245min - 768 or 1024max
Always make nand backups before flashing. Read the directions multiple times. And grab the RUU for your carrier / country if you screw your phone over past restoring a nand backup.
On topic for ROMS bro you are covered. The primoU has everything from Cm9, cm10, aokp, miui, sense ROMs, to PAC man. Your never short of stability either.
The one weird thing to HTCs is you have to flash the kernel from the ROM .zip file (boot.IMG) to get the phone to boot after all that junk
So the process from recovery would be:
-wipe system (factory reset)
-wipe dalvik
Then boot into boot loader
Grab a kernel flasher script (somewhere in forums)
Grab the boot.IMG and use the script and flash it
THEN you can boot into the ROM
I love my one v CDMA sometimes it can be weird but I love it
Sent from my One V using xda app-developers app
Thanks for the reply, helped a lot!
For flashing there is no need of any script. You can just use fastvoot flash boot boot.img....
Sent from my One V using xda app-developers app
Can anyone verify if a2sd scripts and A2SDGUI are comparable with this device? I like to move my dalvik cache to SD to save space for plenty of apps. Also does the 1ghz processor struggle with playing games like Temple Run? Finally, can you replace the original stock Sense launcher to something like Apex Launcher from the PlayStore (Probably a stupid question but just want to know if Sense locks things down like that).
Thanks
Hey guys,
For months now, I've constantly been chopping and changing the ROM around on my DHD, without any issues. All ROMs used to install without errors, and they would all boot to a usable level.
Recently, for the past week or 2, I have only been able to successfully install JellyTime 4.2.2 R11.
Every other ROM I have tried (and trust me, I've tried a fair few), all successfully install, but then become frozen at the boot HTC logo.
I have had a look around the forum to find a solution to this, however most issues similar to this seem to be S-ON, or an issue installing all ROMs.
I am yet to find someone with the same issue as I am having, making it super difficult to find the solution.
That's where you guys can come in...
I'd really appreciate the help. I've just this week turned down the offer of the HTC One, on favour of keeping my now 3 year old DHD, and I'd love to be able to keep modding it for years to come.
So please, help me to have some more fun with my DHD before they finally are obsolete..
Sent from my Inspire 4G using xda app-developers app
Go to the Recovery and wipe then install the rom again
Gesendet von meinem HTC One X mit Tapatalk 2
Alkerino said:
Hey guys,
For months now, I've constantly been chopping and changing the ROM around on my DHD, without any issues. All ROMs used to install without errors, and they would all boot to a usable level.
Recently, for the past week or 2, I have only been able to successfully install JellyTime 4.2.2 R11.
Every other ROM I have tried (and trust me, I've tried a fair few), all successfully install, but then become frozen at the boot HTC logo.
I have had a look around the forum to find a solution to this, however most issues similar to this seem to be S-ON, or an issue installing all ROMs.
I am yet to find someone with the same issue as I am having, making it super difficult to find the solution.
That's where you guys can come in...
I'd really appreciate the help. I've just this week turned down the offer of the HTC One, on favour of keeping my now 3 year old DHD, and I'd love to be able to keep modding it for years to come.
So please, help me to have some more fun with my DHD before they finally are obsolete..
Sent from my Inspire 4G using xda app-developers app
Click to expand...
Click to collapse
Some of the sense ROM's come with kernels that can be flashed only with s-off.
otherwise, make sure you use 4ext recovery.Wipe all except sdcard, then go to the tools menu and format>ext4 menu>wipe data, system,cache, all with ext4.I've had an issue again with CWM/TWRP, where it gave me Encryption Unsuccesful error on boot, and it did so on every ROM onwards.Switched back to 4ext, all is working fine.
In the long run, the S-Off is worth it.
I've tried that. A fair few times...
I've wiped and formatted /system, /data and /cache, as well as wiping the dalvik cache before clean installing each ROM.
I have quite the OCD when it comes to residual files and such, so I wouldn't dream of installing a ROM without a full wipe first.
For me, this still wouldn't explain why I can still install JellyTime without any issues. If anything, JellyTime is working better than any of the previous ROMs I've tried, I'd just like to open up the possibility to explore further..
Is it likely to be a problem with the SD card? The one I'm using is as old as the handset (3 years), and I've named this as the cause of some alight lag issues in the past, but I've never come across this problem before...
Nothing against the ROM, but I wouldn't want to be stuck on JellyTime indefinitely..
Sent from my Inspire 4G using xda app-developers app
Steam. said:
Some of the sense ROM's come with kernels that can be flashed only with s-off.
otherwise, make sure you use 4ext recovery.Wipe all except sdcard, then go to the tools menu and format>ext4 menu>wipe data, system,cache, all with ext4.I've had an issue again with CWM/TWRP, where it gave me Encryption Unsuccesful error on boot, and it did so on every ROM onwards.Switched back to 4ext, all is working fine.
In the long run, the S-Off is worth it.
Click to expand...
Click to collapse
Yeah, I'm on S-Off (Altogether, this seemed like the simplest Root form when I first began exploring, and I've kept it that way since).
But I'm having the same issue when I try to install ROMs that I've used without problems before, on the same handset, so I can't understand what's changed?
Sent from my Inspire 4G using xda app-developers app
Alkerino said:
I've tried that. A fair few times...
I've wiped and formatted /system, /data and /cache, as well as wiping the dalvik cache before clean installing each ROM.
I have quite the OCD when it comes to residual files and such, so I wouldn't dream of installing a ROM without a full wipe first.
For me, this still wouldn't explain why I can still install JellyTime without any issues. If anything, JellyTime is working better than any of the previous ROMs I've tried, I'd just like to open up the possibility to explore further..
Is it likely to be a problem with the SD card? The one I'm using is as old as the handset (3 years), and I've named this as the cause of some alight lag issues in the past, but I've never come across this problem before...
Nothing against the ROM, but I wouldn't want to be stuck on JellyTime indefinitely..
Sent from my Inspire 4G using xda app-developers app
Click to expand...
Click to collapse
Hi I got the same problem six months back. I format the SD card then I tried to install other ROMs. It was successful. So try Good Luck.:good:
UPDATE - After trying over 10 different ROMs without success, I resigned to buying a new SD card, eventually deciding that this simply MUST be the source of the problem.
I bought a new 32GB SD, partitioned it, and flashed a ROM at random.
No issues at all.
I've tried a fair few since, including ones I had problems with before, all without any trouble whatsoever
Cheers for your help guys!
Sent from my Desire HD using xda app-developers app
ok guys i have htc one x and my nephew just got a wildfire s and tried to root and rom it.
so heres where im at. ive flashed this rom but im stuck at the htc logo.
he installed the latest CWM for this phone 5.0.2.8. then full wipe and installed a few roms but none worked and then i got here.
with my one x i have to flash boot.img but as far as i can see thats not the issue here??
can anyone help?
It's a gsm wfs with a sim slot. I'm assuming the next step is to install the correct RUU for the phone right?
the phone is stuck at the htc logo
Can someone possibly point me to the correct RUU? Its a UK phone that was on Tesco/o2 mobile and I cant find the right RUU.
Any help is greatly appreciated
Nothing??
Sent from my HTC One X using Tapatalk 4
Seriously no help at all????
Sent from my HTC One X using Tapatalk 4
Oh well
Sent from my HTC One X using Tapatalk 4
So I get told of four posting in a rom thread and get told to post here and I get zero help. Ffs
Sent from my HTC One X using Tapatalk 4
Usually when you're stuck on the HTC logo it's because the ROM you are trying to flash also needs the kernel flashed, which you have to be S-off to do and the developer you got the ROM(s) from should have provided it. You were very general, but I presume a full wipe was cache, dalvik-cache, data/factory reset, and (optional), battery stats? Are you just plain stuck, can't do a factory reset and/or didn't make a backup before trying the ROMs? I was going to flash this ROM at one time and he gives some pretty good instructions to follow...sounds like it might work for you. Better than staring at the HTC logo, eh?!
http://forum.xda-developers.com/sho...ht=what+files+can+i+remove+from+my+wildfire+s
Thanks for the reply. I can get to recovery but I can't install anything as recovery can't seem to find the internal storage.
Sent from my HTC One X using Tapatalk 4
Most recoveries are going to look on the external storage, the actual sd card. Can you move your ROM to that and give it a try? Just to save time, I'll say I'm figurin' the sd card is formatted (FAT 32) and if there's a problem seeing that you might have to go into, "Mounts and Storage" and mount the sd card. I'm in the middle of a movie and will get back after, if you have another question I can help with. Hope it works.
ok so i finally got CWM to see the sdcard and i installed a rom and flashed the boot.img.
now the phone just reboots into recovery. what the hell is wrong with this dam phone????!?!?!
So far we've been successful with the, "One step back and two steps forward" approach so:
You extracted the boot.img file from the ROM zip to your PC for use after and then installed the ROM, rebooted the phone into recovery>>fastboot, hooked up to the PC in a command prompt and changed directory to where you have the boot.img and the adb/fastboot command files and at the command prompt typed: fastboot flash boot boot.img
Typically you would then type: fastboot erase cache, or back in recovery wipe the cache and reboot to find the ROM (slowly) booting for the 1st time.
I'm a one step at a time person (so I know what worked). So if all that's true, and it's still stuck in a recovery loop then I'd try wiping cache again and dalvik-cache and rebooting.
If that doesn't work I'd suggest one of two things:
1. Start over and I don't mean at htcdev, but wiping cache, dalvik, and data...install ROM, flash boot.img, wipe cache reboot...or
2. We can go over all the steps (as briefly as possible for both our sakes) and I'll say why: one time I was writing a macro and it just wouldn't work, after 3 days of spending too much time on it each day I asked someone else to look at it and he found I had missed a slash or used a comma instead of a semi-colon or some one simple thing. So it wouldn't hurt to see if there was one little thing skipped.
Lastly for now - if you post again, whatever you post, just for my curiosity tell me which (compatible with the Wildfire S) ROM your wanting to use.
First of all I just want to thank you for trying to help.
I did those steps perfectly and they've always worked with my HTC one x but no dice with this wildfire.
http://forum.xda-developers.com/showthread.php?t=2206780
That's the ROM I'm trying to get to boot.
I really want to fix this phone for my nephew but its not looking good.
Sent from my Nexus 7 using Tapatalk 2
I know how it is...we all get fixed on wanting one thing and then intent on making it work.
I did a quick look at the page for your intended ROM and first thought, aha...in the instructions to install, the wipe file he provides seems to indicate for a marvelc in the name, so does it wipe all it should on a gsm WFS; but, then he's got that link to the ROM for a marvel c(dma); anyway I did a quick search of the thread (there are 119 pages!) for, "Reboots into recovery" and found this (among others):
http://forum.xda-developers.com/showthread.php?t=2206780&highlight=reboots+into+recovery&page=102
I do see where there was a rebooting into recovery problem with this ROM and a fix was applied in July 2013. I think the link above is to the, "fixed" ROM (hopefully for GSM WFS) but I'm not going to claim that as fact; again, I just took a quick look between my morning news readings and did not read around the problem or, about Lizards patch.
We could go deeper like formatting partitions, but since he has provided a wipe script and there's so much info there...well, I'm not dumping you, but I am thinking researching there might get you more specific results since we've pretty much been going through the generic version of flashing ROMS. What do you think?
ok i read the entire thread and flashed all the fixes etc but no dice. however i did flash a different rom altogether and now everything seems to be working fine!!!!!
dont know why that never occurred to me before!
i must say thank you for all your help. it is very much appreciated
now for some strange reason the original rom now works !!!!!!!!!
For as long as I"ve been fooling around with electronic devices, it often still just seems like, "PFM" sometimes; and, I don't know how many times I've done the right thing over and over and over and then just given up and set it aside only to pick it up again a day or two later and then everything goes like it should...and not doing anything different!
I'm glad you got everything going again, and I'm sure you just want to get back to enjoying it, but I'm curious to know (along with anyone else that might be following) what ROM finally worked, and then you ended up going back to which, "Original" ROM, stock?
I hear you on that. So many times I've had to work on systems for hours then magically I'll do something and it works.
What I did was flash another custom ROM which was unofficial cm10.2 it's on the main page made by owl. That booted up fine but I wasn't happy with that ROM so I flashed the one that I've been trying to flash, marvellous cm10, the one you helped me with.
The only thing I did differently was flash the boot. IMG after I flashed the ROM , I usually flash the boot image first on my one x.
And that's about it.
Sent from my Nexus 7 using Tapatalk 4
I clicked a thanks (and thank you for yours). I enjoyed the exchange and glad you've got it going. The Wildfire S is a great phone, especially for me (although I have my SIM in another phone now) and hopefully your nephew, because it needs to be managed, tuned, tweaked, etc. which is what I love to do and hopefully your nephew will too and keep at it now that you got him off to a good start.
good start yes, but i have to fix the mistakes!! lol
Do you know where u can get int2ext?
Sent from my HTC One X using Tapatalk 4
You caught me right at the end of a movie I was watching!
I've always been happy with Link2SD, but you can't beat moving all of data to SD.
Try this:
http://forum.xda-developers.com/showthread.php?t=1716124
also, this is an easy way to get init.d if you don't have that...I think it's needed for int2ext:
http://forum.xda-developers.com/showthread.php?t=1710980
Have fun!