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
Related
Ever since I flashed LeeDroid 1.8b, I've been having this odd problem. I've wiped the phone since and have flashed Open Desire 3.1.0 and I love it but I'm terrified to reboot my phone.
The phone will boot and freeze at the HTC white screen. This happens even if I try to boot into Recovery, (I can hold down vol+down and power button) but as soon as I select Recovery, it will freeze there at the HTC screen.
The only solution I have is to pull the battery and try again. It will do it around 2 - 3 times before it finally boots into Clockwork Recovery Mod SLCD or boot into Open Desire if I don't boot into recovery. This is the same if I decide to REBOOT the phone or power down and boot up.
This problem never happened when I originally flashed Cyanogen. I'm thinking there's still some files or something left that causes this freezing.. I also did a wipe and delete cache before flashing a new rom.
Does anyone else have this problem or help me sort it out?
Edit: Ah shoot.. wrong forum My bad..
no one?
Although Lee newer acknowledged it, I think it has to do with his ROM. I experienced the same issue while running 1.8b, with 1.8c I haven't rebooted by now, but still I have experienced this only after switching to his ROM and I noticed I am not alone on the ROM thread (other people are complaining too about getting stuck at the bootscreen).
I have changed many ROMs (generic 2.1, generic 2.2, pays, adamg ROM...) and never had such an issue, that is why I think it has to do something with lee's ROM.
If you have OpenDesire I would suggest to reboot it just to see how it will go.
Thanks for your response man! The problem is that I've wiped and everything and flashed Open Desire and I'm still experiencing the issue. Is there another way I can completely delete/format any traces of any previous ROM? I believe there's still some sort of remnants of his files left that are causing this!
THanks,
JD
A full wipe can never hurt.
As for freezing at the HTC screen when trying to boot into recovery, I experience this too. What I have found is that if I press no buttons after booting into HBOOT, until HBOOT has tried to load from the SDCard, and THEN selecting Recovery, Recovery boots every time.
However, if I push a button before HBOOT has loaded from the SDCard, I will freeze on the HTC screen regularly.
TheLastOne said:
A full wipe can never hurt.
As for freezing at the HTC screen when trying to boot into recovery, I experience this too. What I have found is that if I press no buttons after booting into HBOOT, until HBOOT has tried to load from the SDCard, and THEN selecting Recovery, Recovery boots every time.
However, if I push a button before HBOOT has loaded from the SDCard, I will freeze on the HTC screen regularly.
Click to expand...
Click to collapse
I will definitely try that.. do you ever have problems booting though? I freeze on the HTC screen during boot up as well and have to do 2 - 3 battery pulls before it finally decides to boot!
I do not, but hopefully a full wipe (data, cache, dalvik, etc) will solve that. Have you tried wiping everything?
I have, but the only wipe I perform is the one in the Clockwork Recovery. Also deleted the cache, but never have deleted or wiped dalvik cache?
I will try this later today and see what happens.. thanks!
TheLastOne said:
I do not, but hopefully a full wipe (data, cache, dalvik, etc) will solve that. Have you tried wiping everything?
Click to expand...
Click to collapse
Just sayin' I've not ever had a boot problem like this with LeeDrOiD. Running 1.8c at the moment.
Ditto.. No issues, its not a rom issue, you may have bad blocks on your nand.
Sent from my HTC Desire using XDA App
Tawm said:
Just sayin' I've not ever had a boot problem like this with LeeDrOiD. Running 1.8c at the moment.
Click to expand...
Click to collapse
I believe it was an issue with 1.8b..
LeeDroid said:
Ditto.. No issues, its not a rom issue, you may have bad blocks on your nand.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Hmm.. anyway to confirm this? It's a brand new device, barely two weeks old and never had this issue until I flashed 1.8b.. I'm going to try to wipe it completely and go from there, hopefully that solves the issue.
What's a nand?
Hi Quazis,
I have had a very similar problem with my Telstra desire after rooting and installing a Lee based rom called NexTSense. After that I installed Open Desire and experienced the same problems.
I am just now re-rooting my phone and going to install Pinky.
Just out of interest are you running on the 850mhz Rogers network? If so have you updated to the latest radios (5.09.20 I think?)? Telstra runs off this frequency also and I think it may have something to do with incompatible radios. -- Can anyone confirm this?
If this is the case maybe try Open Desire without updating the radios?
Hey,
We got the A8182 version of the Desire which has 850/1900 (I believe), so both bands that run on 3G.
Before I flashed LeeDroid, I had updated the radio (.20) and was on Cyanogen nightly build. I had no booting problems with that ROM, but I wanted something a little more stable. I modded it as well and the phone booted up no problem, also into recovery.
Once I flashed LeeDroid, that's when my problems arose. I only wiped/formated data and the cache.. I never formated that dalvik cache. I will wait until Open Desire 3.2.0 releases today and try that a full wipe/format.
Another member said he doesn't touch anything on the phone when he boots into recovery until the phone does the SD card check.. I tried it once and it went into recovery with no issues so maybe pressing buttons before the SD check does something??
I don't, but I did a full flash, and used my separate test sd card.
plasmafire said:
I don't, but I did a full flash, and used my separate test sd card.
Click to expand...
Click to collapse
I'm going to do this.. thankfully I have't customized my phone a lot so I'm going to format both the FAT32 and EXT3 partitions and full wipe.. to do a full wipe.. there's only data/factory, cache, davlik cache and battery stats correct? If I wipe those 4 items in Clockwork, that's considered a full wipe?
JD
Full flash wont help. I know because I did it.
I am to lazy from installing different ROMs, resetting my device, etc... so I will leave it as it is for now (LeeDroid 1.8c), and will try to reboot it as rare as possible (bootscreen takes a while, bootloop is possible too). But when I'll have some more time I will re-root and install another ROM and I am sure the issue will be gone.
Lee, nothing personal (in the end, I am using your ROM right now) but I think you should read more carefully the thread about LeeDroid. You will see many people get stuck at the booscreen and/or their devices keep rebooting with this ROM.
I don't have this issue with the same ROM as you.
-----------------------------------
- Sent via my HTC Desire -
Yes, not everyone has that problem (in that case we wouldn't need to talk about it - we would KNOW it). Just some people have this issue with that ROM. I would say 5% of the people have the bootloop problem, and 10% of the people have longer-than-average the bootscreen.
Still, it worths taking a look since 3-4 people from 10 participants on this thread say they have this problem with -this- ROM.
My 2 cents.
ljesh said:
Full flash wont help. I know because I did it.
I am to lazy from installing different ROMs, resetting my device, etc... so I will leave it as it is for now (LeeDroid 1.8c), and will try to reboot it as rare as possible (bootscreen takes a while, bootloop is possible too). But when I'll have some more time I will re-root and install another ROM and I am sure the issue will be gone.
Lee, nothing personal (in the end, I am using your ROM right now) but I think you should read more carefully the thread about LeeDroid. You will see many people get stuck at the booscreen and/or their devices keep rebooting with this ROM.
Click to expand...
Click to collapse
Why won't a full flash help? I don't have LeeDroid anymore, I had it for about 10 minutes because I didn't like it. I've since gone to Open Desire and the issue still persisted.. but it never happened when I had Cyanogen installed.
I'm scared to re-root because it requires a reboot and sometimes the HTC screen never goes away.. lol
hey there, its intresting to see that you have the same problem as me,
http://forum.xda-developers.com/showthread.php?t=755835&highlight=Recovery+Issue
the people who are saying they dont have a problem, i'd like to know what recovery you are using?
and what hboot you orignally came from, i.e. do you have a SLCD screen? and how did you root?
because it is now becoming obvious that leedroid rom is causing this issue as a lot of people are having problems.
during the weekend i will try flash the RUU for WWE with the hboot 0.83 included (using gold card)
and start from scratch and flash another.
no disprespect to the developer of leedroid, his work is good. just a lot of people on hboot 0.83 with the SLCD screen have issues.
Hello, i was just wondering if anyone has had any luck with the boot manager app?
I know this app is not specifically supporting the wildfire atm but i asked the devs if it would work and they told me that there is some code built in which should theoretically support the wildfire and they are answering my emails quickly(i'm sending them a log later to see if they can help me out) i had a few problems at first with installing a new rom but eventually managed to get a cm7 zip to unpack and created a system,data,cache and a boot.img.
When i try to reboot into the new rom i seem to be getting stuck at the splash screen, has anyone else tried this app before?
Its a paid app (with a licence check on startup, so pirated versions won't work) so im guessing there isn't many that have tried it before with it not being officially supported. I'm pretty sure it will work and i've only played with it for half a day but just wondered if anyone else had any success and new of any shortcuts?
Woohoo success, tried for days with cm7 to get this working but it just wouldn't write the images to my SD card, switched roms to senseonfire (even though the dev told me cm was my best bet) and it worked first time, haven't had a good play with it working as yet so can't really say how stable cm7 is running from my sdcard but its definitely working now, and its as simple as rebooting to switch roms instead of rebooting into recovery restoring a backup then waiting 10 mins for it to boot. I can also restore a nandroid backup to one of the 4 slots.
Sent from my HTC Wildfire using xda premium
Booting from SD, that's cool. Having you tried using USB disk drive mode?
Haven't tried yet, I'm away for a few days, pretty sure the boot manger app has dual mount built in though, so anyway I've been using cm7 for the last day running from the SD overclocked to 768 and its good, only getting occasional lag spikes but nothing to worry about.
Sent from my HTC Wildfire using xda premium
All right this problem has now been solved! Thank goes to khamsakamal48 for posting the solution for the problem. The problem is solved by replacing the updater-script with the one that is used in the GSM version the of Rom. Then Using the latest 4ext recovery, wipe everything and install. Thank you to everyone that have participated in trying to get this solved. This might also work with other recoveries, but has not yet been confirmed.
Updater-Script: http://db.tt/sUfk5p8E
Latest 4ext recovery: http://db.tt/sP5o7HhJ
only thing i could think of is try a different recovery .I haven't had any trouble at all booting miui an i use cwm touch version.
Alright I'll have to give it a try. Was trying to avoid that but oh well. Thanks!
Sent from my Incredible 2
so I tried 4ext and clockwork recovery. Both have caused my phone to just boot right back into recovery. Wiped data and all.
kylesag21 said:
so I tried 4ext and clockwork recovery. Both have caused my phone to just boot right back into recovery. Wiped data and all.
Click to expand...
Click to collapse
Can you give us a little more background on your phone setup? Have you flashed roms successfully before or is this a first time? Are you s-off?
Sorry bout that. I am S-off and I am able to flash all of the other roms available. But when it comes to this one it just won't flash.
Sent from my Incredible 2 using Tapatalk 2
I have been having this same problem. I am going to try to go through everything I have done to see if I can get more info.
I had MIUI V4 (2.9.29 CDMA) running shortly after rooting this phone (maybe 1 week ago). I installed it from the latest TWRP, so that isn't our problem. I loved it and everything was great. I am unsure what radio I was on at the time, and I think that may be where my problems came in.
I successfully installed ViperINC 1.0.0 after doing a factory reset, wiping cache, dalvik from my WORKING MIUI V4. It booted and I played with it for a few hours, but wanted to go back to MIUI. At this point I was on the firmware from nitsuj17's thread. When I tried to factory reset and install MIUI clean again I started having the same trouble as OP. Since then I have tried every radio I could get my hands on, and may have even been a bit sloppy about what firmware I flashed (the only one I'm unsure of is CondemnedSoul's Return to stock as I am unsure what all it included other than radio and stock rom). After a lot of different attempts, I used CondemnedSoul's PG32IMG and went back to stock where I had everything working fine (for stock). I got an OTA update, but wasn't satisfied so I kept trying different radios from the pinned post on the Development thread (really only .0312 and .0320 as well as the first leaked firmware I linked from nitsuj17). So far nothing has worked to get me any further than the OP unless I just use a different rom. Had this rom never worked I would just talk to the developer, but as I had it working before and no idea what changed I'm at a loss.
I don't have enough posts to get something on the Development forum, but if anyone here can help, I'd really appreciate it.
I've been scouring these forums looking for someone who has made progress on this issue. I'm going to make a list here of posts by people having similar problems, if not the exact same. I have yet to see anyone successfully address them.
One of a few people on the MIUI V4 thread who have had the same issue. I had this rom running at one point, though, so I'm not sure what change caused it to stop. I definitely get further with the TWRP recovery (freezes on "android" splash screen) than the 4ext recovery (reboots to recovery).
I don't believe the JB issues are directly related, but similar problems.
Similar to the Jellybean issue above. More similar to my own situation since I also only started having trouble after flashing ViperINC, but I have formatted, wiped and reverted (even to S-ON and unroot Froyo) so much that I can't see how it would have changed anything that I have not removed. This thread has 3+ people with the same sort of issues. Last report one of them installed ViperINC with all defaults and let it run for a few minutes then wiped and re-installed CM10 with success. I may try this, only with MIUI. I have no idea what settings would be slipping through.
And the cdma miui is one of the only roms that boots for me. Running it now. I think Zelmo is right, there's something sticking around with that Aroma script. I've flashed aosp roms over sense roms and vice versa without even wiping and never had issues like these. I've basically wiped this thing with steel wool and always the same thing. It's gone atleast 15 mins with it's bootloop/freezing max cpu process. It ain't gonna boot! I was up until 2am last night ****ing with it. I'm done.
I'm nearly there. Had I never been able to run MIUI, I would probably have dumped it by now, but it's like an itch I can't reach at this point. There is just something there that I can't see or imagine that is hanging in through every wipe I can find. I just formatted my SD card and did a bunch of wipes (I know that has been tried) and I'm going to try VenomINC with all defaults like Zelmo88 had some success with. If I don't have any luck getting to MIUI from there I'll probably go back to my dinc or buy a new phone soon. This one was really an experiment anyway.
Will follow up if I can figure out anything else.
khamsakamal48 posted pretty detailed instructions here. I have confirmed that my install is going pretty fast, so I am betting that could be our issue. I am not sure what causes this or how to prevent it. I'm going to try and flash it a bunch of times here to see if I can get it to complete.
Edit: I tried 3-4 times with CDMA file and had no success making it take longer than 1-2 minutes. I then flashed the GSM file which I had been having the same trouble with and it succeeded! I am going to check my MD5s again on the CDMA file and give it another go.
Edit: I have tried now around 10 times with the file found here linked from khamsakamal48's thread on the development forum. MD5 matches, but I cannot find any method of flashing>wiping>reflashing>rewiping>crying>flashing>snoring which will make it take more than about a minute with the "install". I'm going to type out my log from 4ext so that I have something to do.
>format all partitions (except sdcard)
>wipe dalvik cache ;multiply the repetetive redundancy
>install from sdcard
>MIUI.us_vivow_v4_2.9.29.zip ;MD5 9f36b433635e50e0daf23768280c050f
;begin log
Finding update package...
Opening update package...
Installing update...
Formatting system...
do not formate system ;???
Installing system files... ;this bit may take 1minute
Creating system links...
Set permission...
Update Boot image...
Install from sdcard complete. ;and done in less than 2 minutes every time.
If someone could post a link to this on the Dev forum or something I would appreciate it. I don't feel like spamming 4 more posts just so I have that privilege.
stoicwood said:
khamsakamal48 posted pretty detailed instructions here. I have confirmed that my install is going pretty fast, so I am betting that could be our issue. I am not sure what causes this or how to prevent it. I'm going to try and flash it a bunch of times here to see if I can get it to complete.
Edit: I tried 3-4 times with CDMA file and had no success making it take longer than 1-2 minutes. I then flashed the GSM file which I had been having the same trouble with and it succeeded! I am going to check my MD5s again on the CDMA file and give it another go.
Edit: I have tried now around 10 times with the file found here linked from khamsakamal48's thread on the development forum. MD5 matches, but I cannot find any method of flashing>wiping>reflashing>rewiping>crying>flashing>snoring which will make it take more than about a minute with the "install". I'm going to type out my log from 4ext so that I have something to do.
>format all partitions (except sdcard)
>wipe dalvik cache ;multiply the repetetive redundancy
>install from sdcard
>MIUI.us_vivow_v4_2.9.29.zip ;MD5 9f36b433635e50e0daf23768280c050f
;begin log
Finding update package...
Opening update package...
Installing update...
Formatting system...
do not formate system ;???
Installing system files... ;this bit may take 1minute
Creating system links...
Set permission...
Update Boot image...
Install from sdcard complete. ;and done in less than 2 minutes every time.
If someone could post a link to this on the Dev forum or something I would appreciate it. I don't feel like spamming 4 more posts just so I have that privilege.
Click to expand...
Click to collapse
Your post is an exact match to what I've done. Even tried reverting to ext3 ( no luck, obviously). Well I've got the bug so now I'm not stopping until I figure this out. I'm running viper 1.0.1 so there might be a common element.
grunt9800 said:
Your post is an exact match to what I've done. Even tried reverting to ext3 ( no luck, obviously). Well I've got the bug so now I'm not stopping until I figure this out. I'm running viper 1.0.1 so there might be a common element.
Click to expand...
Click to collapse
I think most of us first noticed these problems around the time we flashed Viper, but I have nuked this thing so hard from so many different directions since the last time I ran Viper that I can't imagine anything surviving. Still, a little too coincidental.
Running the GSM version didn't last long, either. I played around with trying to get it to use my sim, but as soon as I changed some of my network settings it went into a bootloop tailspin and somewhere along the way corrupted my /system. That took a little work to get around, so now I'm back to aeroevan's CM10 which runs OK... other than what doesn't.
Try replacing the updater-script under meta-inf with one from my GSM version!!
Hope that helps!!
Edit: Replace the updater-script with this one- http://db.tt/sUfk5p8E & use this recovery which I downloaded just now- http://db.tt/sP5o7HhJ
All the best!!
Sent from my HTC Incredible 2 using xda app-developers app
[SOLVED]
khamsakamal48 said:
Try replacing the updater-script under meta-inf with one from my GSM version!!
Hope that helps!!
Edit: Replace the updater-script with this one- http://db.tt/sUfk5p8E & use this recovery which I downloaded just now- http://db.tt/sP5o7HhJ
All the best!!
Sent from my HTC Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
Worked perfectly first try! Now running CDMA version without problem. I don't know why it works, but it works. Everyone thank khamsakamal48!
I'm not seeing a meta-inf folder. Is there another place it could be?
Sent from my vivow using xda premium
I believe it is in meta-inf>com>google>android
Updater-script should be located there.
Sent from my HTC Incredible 2 using Tapatalk 2
Nope, no meta-inf. Back to Google
Sent from my vivow using xda premium
Are you using 7zip to open up the zip file?
Sent from my HTC Incredible 2 using Tapatalk 2
I'm too embarrassed to tell you what I was trying got it now, thanks again
Sent from my vivow using xda premium
I recently have spent a decent amount of time trying to get my inc2 to boot JB without extreme lag(maxed out CPU). I've ran JB quite a few times until one day I overclocked to 1.5GHz and my phone boot looped and could never get JB or ICS to run properly. Its been reported that over clocking over 1.3GHz can break the partition on your phone and even lose root. If u have similar problems this is what I did -
Put the stock ruu GB 2.3.4 on the root SD card as pg32img.zip
Boot into boot loader and click vol up to accept update.
you are now on the latest stock gb without root but s-off will b preserved
download super one click and htc drivers to gain root.
reboot
I flashed twrp thru goo manager cuz that it's what I prefer. Wipe and flashed dkstunna's build 3 with 4.2 gapps and boom BACK TO FAST JB in under 30 min.
hope this helps someone! hit thanks if it did
next I hope to help on the main thread one day, Ive flashed almost every ics jb Rom and would luv to help
Sent from an incredibly running JB inc2
Can anyone verify this works? Not that I doubt you OP, just wondering if this has worked for anyone else?
Quick question.
I have been rooted for so long I've almost forgotten how it is done but I don't remember Super One Click supporting the DInc2. Does this mean it does root 2.3.4?
yes super one click works for inc2, and yes it will root 2.3.4. s off is the hard part on 2.3.4 if ur not already, so be s-off. I'm sure this will work differently for everyone cuz god knows why ics jb stopped working right in the first place. I bet kernel source would fix this too...
Well,
Tried it, and it didn't do the trick.
Still no JB for me.
Frustrating!
I'm running PA for months now and it hasn't locked up or lagged. I came from Venom before. I wiped everything except SD card, installed CM10 10/3, booted, flash PA, booted, flashed gapps and kernel. It booted up just fine for me.
I also flashed the firmware in the Venom thread. I don't use v6supercharger, 1024MHz smartassv2, and I undervolt -50.
TheAtheistReverend said:
Well,
Tried it, and it didn't do the trick.
Still no JB for me.
Frustrating!
Click to expand...
Click to collapse
I was in a bit of a panic cause i was using viper, went to aeroevans 11/13 jb, it worked for about 6 hours and then the massive lag and boot loops started. I couldn't flash any ics/jb aosp rom, I tried mimicry, dkstunna, and aeroevean's cm9/10. all non usable, crazy lag and boot loops. viper seemed to flash fine though.
I did try the solution in this thread and it didn't seem to work so I reflashed viper formatting using aroma. I let it boot and settle. then i formated all partitions in 4ext and reinstalled viper without formatting in aroma and i let it boot and settle, finally i reformatted all partitions in 4ext, installed aeroevan's 11/13 with latest jb gapps and all has been great for the past few days. fingers crossed.
I have tried just about everything. I can't think of anything else to try. I wish we knew why some phones were doing this.
The first thing I remember not going as usual on my phone was MIUI was not installing properly. It would hang on "updating boot" during install. I couldn't for the life of me get it any farther than that. The next thing was a JB NAND wouldn't boot properly, and then it was all down hill.
Back on the same bull**** of bootlooping on cm10. There should be a warning on the viper thread to not install it if you ever want to use another rom.
I don't know why but I'm not having any problems after viper...
I'm so fresh you can suck my nits...
None of us know the answer and that's the only common denominator. I'm just lucky that Miui works or i'd be sol
Uhh so yeah, tried this and it didn't work. Never had any problems with the phone before I got rid of ViperInc. I was on the latest firmware, every ROM flash was a totally clean one, followed the instructions in the OP and CM10 Global is just sitting here bootlooping. I know the dev isn't responsible for what happens to our phones, but multiple cases of the same seemingly unsolvable problem says there's something wrong with that ROM, imho. ****ing bogus.
Does anyone know if.the devs will try n make a fix or maybe implement one in the next build?
Sent from my HTC Droid Incredible 2 using xda app-developers app
chillybean said:
Does anyone know if.the devs will try n make a fix or maybe implement one in the next build?
Sent from my HTC Droid Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
It's not the cm10 devs' problem
Didn't say it was cm10s dev problem its the viper dev problem ..its an awesome.Rom but when some problem as bad as this with many ppl affected ..in my opinion I think the team should at least help ..when ppl start seeing this they aren't gonna want to flash this Rom...then there would be no point in developing it unless for the ppl that WANT to stay on sense...all I asked was if the team was aware n if they plan on a fix or a disclaimer that this Rom may poison your phone so it does happen to anyone else ..no need to be a smartassv2 lol I'm just asking and I'm sure a lot of ppl are too
Sent from my HTC Droid Incredible 2 using xda app-developers app
after getting JB to work for awhile I decided to flash the .312 radio, booted and 5 min later I get jelly beans to the face... now I'm stuck on viper again. I tried multiple times to recreate whatever fixed it the first time and I get nothing. I remember reading somewhere awhile back that going stock s-on then going s-off root might solve the problem
chillybean said:
Didn't say it was cm10s dev problem its the viper dev problem ..its an awesome.Rom but when some problem as bad as this with many ppl affected ..in my opinion I think the team should at least help ..when ppl start seeing this they aren't gonna want to flash this Rom...then there would be no point in developing it unless for the ppl that WANT to stay on sense...all I asked was if the team was aware n if they plan on a fix or a disclaimer that this Rom may poison your phone so it does happen to anyone else ..no need to be a smartassv2 lol I'm just asking and I'm sure a lot of ppl are too
Sent from my HTC Droid Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
I don't think it is ViperROM dev's problem, nor is their responsibility to help. They make it very clear they hold no responsibility for what happens to your device when you flash their ROM. They are also not making any money from the free rom they put out for us to enjoy, so their is no driving force really behind their desire for "fans" if you will.
That being said, it would be nice if they could help and did. Has anyone directly, and nicely asked Nitsuj or any of the Viper team for help?
fen0m said:
after getting JB to work for awhile I decided to flash the .312 radio, booted and 5 min later I get jelly beans to the face... now I'm stuck on viper again. I tried multiple times to recreate whatever fixed it the first time and I get nothing. I remember reading somewhere awhile back that going stock s-on then going s-off root might solve the problem
Click to expand...
Click to collapse
Doubt it. I went all the way except for S-off and re-rooted but it still will not load any JB rom I try. But by all means, it might be worth trying if you're so motivated. Seems like some things work for some, but not for others at this point.
Just got back onto CM10. Was on Viper, did full wipe x2, formatted partitions to ext3 in 4ext Recovery, fix permissions, then formatted cache.
Then...here's the weird part....since Mimicry was the only non GB Rom I could get to at least boot, I tried a clean flash of it. Used only the baseline items in the Aroma installer (only things I installed were the jb animations, trebuchet, v6, and daemon). Booted into Mimicry and let it settle without signing in to Google. Profit!
Next phase was a full wipe x2, flash newest CM10, flash GApps, then format cache.....double profit! Hopefully this will hold up. Will report back once its had time to fully settle.
Sent from my Incredible 2 using xda premium
Sry didn't mean to say it like that but I know its not their responsibility..I just asked if they try to figure this out..I'm gonna try this mimicry method...I hope I profit like twice
Sent from my HTC Droid Incredible 2 using xda app-developers app
I wouldn't call it a method really....I think I may have just gotten lucky
Sent from my Incredible 2 using xda premium
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!