I tried run Boot Manager on the Desire Z for a multiboot environment so I could easily test ROMs before flashing them.
No matter which ROM I try to run from SD, the phone stays at the HTC bootlogo.
Last time I've let it run for 5 hours until I removed the battery and reflash Andromadus to bring it back to life.
Any ideas what I'm missing? The app should officially support the G2/DesireZ.
Anyone managed to make it work or having the same issues?
I never bothered with something like that to 'easily test a rom', I simply make a full backup in recovery, wipe, flash new rom, try it out, and if I don't like it, wipe and restore backup.
I imagine the utility might run you into problems if you have an sd-ext partition used by two different roms (or a rom not designed to work with something like that).
DaFunkShun said:
I tried run Boot Manager on the Desire Z for a multiboot environment so I could easily test ROMs before flashing them.
No matter which ROM I try to run from SD, the phone stays at the HTC bootlogo.
Last time I've let it run for 5 hours until I removed the battery and reflash Andromadus to bring it back to life.
Any ideas what I'm missing? The app should officially support the G2/DesireZ.
Anyone managed to make it work or having the same issues?
Click to expand...
Click to collapse
Try setting the large boot option and recreating the slot.
You will have to follow their instructions from the top, not just use the application to setup a secondary slot. Setup both your main rom and the slot1 from scratch while following the instructions. Also make sure your sdcard has enough space.
Sent from my HTC Vision using xda app-developers app
Related
I made a thread on this before and didnt get much help so this im doing it right.
Size of sdcard used: 8gb Kingston class 4
Size of each partition created and type of partitions made : Primary fat 32 (4.7gb) and Primary EXT4 (2gb)
Software used for partitioning (Gparted, Amon Ra recovery etc): Gparted
Recovery Software installed, with version and subversion number (Eg: Clockworkmod 3.0.0 R3): Clockwork Mod Recovery 2.5.0.7
Whether you are S-OFF or S-ON (If you dont know what this is, or you dont have the picture of a Joker holding a card, on the bootup screen, you are S-ON): S-OFF
Detailed account of steps you did for the procedure, with output/errors at each step as received from the Recovery/Partitioning software: This part im not too clear about
Did you do a full wipe from Recovery before installation?: Yes
If you didnt, what ROM were you running previously?:
Version of the ROM you installed, and the names of the Data2SD installer/reinstaller flashable zips you used (if any.): Starburst (1.3.3.5) – Standard Edition Data2Sd installer (Stable) VersionCode :1.3tiny
If you’re using a custom kernel, full name of the kernel with author name, the kernel voltage if known, whether you have an overclocked/undervolted configuration: None
Did you get any of the following messages in recovery? …………………………………….
sd-ext could not be formatted, file already exists?
Failure mounting ‘sd-ext’
Or a message similiar to the above?: No
My battery is draining in 9 hours of moderate use opposed to full days or more before rooting and using this custom rom. It also lags now, it will be all zippy then it will freeze for a few seconds or just lag insanely. Maybe the battery issues are stemming from the cpu working too hard trying to deal with the lag. Thats just me brainstorming but ya, if anyone could help me out here I would greatly appreciate it.
(As of now I am using a default homescreen free of all custom apps to see if the problem is stemming from one of them) EDIT: it made no difference so I am assuming it is not a running app.
(Also, it lagged as soon as starburst was installed so maybe the apps have nothing to do with it. Another issue is that when I press the power button to turn the screen on the screen dosent always turn on. This is another issue associated with the lag that is bothering me)
A note. The battery melts away when I start to use apps, the internet or anything that takes the phone out of standby mode. If I'm correct the kernel in the starburst rom overclocks the CPU to one thousand and something. Maybe this could be my problem. And if you think this may be the case could you recommend a better kernel to me? Thanks
Sent from my HTC Desire using XDA App
I think I may have figured out the issue. You see, when I first installed the rom I restored my default settings effectively replacing my new fancy rom with the old one.
When I wiped the internal memory (2 gb or so off of ext 4 primary I think) the external still had a few files on it from the last install of the rom. I left those there thinking they would be no issue. Could those remnants from my first starburst install be the cause of my issues?
Sent from my HTC Desire using XDA App
Joshua3109 said:
I think I may have figured out the issue. You see, when I first installed the rom I restored my default settings effectively replacing my new fancy rom with the old one.
When I wiped the internal memory (2 gb or so off of ext 4 primary I think) the external still had a few files on it from the last install of the rom. I left those there thinking they would be no issue. Could those remnants from my first starburst install be the cause of my issues?
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Wipe and repartition with Gparted, this time only leave 1 Gb for ext4. Dont install Setcpu and dont manually set vdd levels for kernel. See if it lags before any apps are installed. If it doesnt try restoring apps with Titanium and see again. Since you do have 10 posts, why dont you continue this qn in StarBurst thread? Please dont PM me. I rarely if ever check these!
Btw..you can also flash the Leedroid 2.2f from Kernels section of my site. It's known for its better battery life.
Should we erase all previous files when updating roms? Do they cause trouble?
hurin8 said:
Should we erase all previous files when updating roms? Do they cause trouble?
Click to expand...
Click to collapse
If your previous installation worked fine, no need to wipe. If you are coming from another Rom, you definitely need to wipe
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
As the title suggests my phone refuses to boot properly after a reboot. I flash a new rom and everything works fine but when it comes to powering it off/rebooting it will either hang on the boot animation (the animation will play but nothing else- In the case of Sandvolds ROM) or it will boot, screen will go blank, vibrate and boot again only to go straight into recovery (when using this ROM)
I'm stuck on Sandvold's 0.12 rom (since I did a Nandroid backup of it, that's the only ROM which works. Anything new and it refuses to reboot).
Using 4EXT recovery, format all partitions (except SD card), using SuperWipe script, CM7 hBoot, S-Off.
Any fixes? I've tried a lot of potential fixes (reflashing the rom etc) but every time the same thing happens- the reboot never works. I can leave it for an hour (which I have twice) and it will always just stay on the animation making me have to restore the backup.
i have the similar problem.look: http://forum.xda-developers.com/showthread.php?t=2012808
siavash2death said:
i have the similar problem.look: http://forum.xda-developers.com/showthread.php?t=2012808
Click to expand...
Click to collapse
I was reading that earlier. It seems to be something with ICS and JB. Also reading the latter pages of Sandvold's thread, seems the latest version of the Playstore is creating bootloops and there's means to temporarily fix it using adb but that's all I got.
Don't know if this will help however but I suppose it's worth a shot- http://forum.xda-developers.com/showpost.php?p=34429350&postcount=16767
i don't want to use playstore.because i can't access to that for sanction! can removing the playstore with something like titanium backup solves the problem?
siavash2death said:
i don't want to use playstore.because i can't access to that for sanction! can removing the playstore with something like titanium backup solves the problem?
Click to expand...
Click to collapse
I don't know myself but it may work. Apps may not work however since they call back on the store to see if you've purchased it (or for your phone to re-download the apps after you login with your google account).
I recently recieved my One V and finally decided on rooting/installing a custom rom. I came from an Optimus V and had no problems installing a custom rom in that.
However it seems that no matter what kernel/rom I use they eventually lock up within the first 5 minutes of booting and restart. I've tried practically everything and can't get them to work. I wanted to ideally run the CDMA Pacman Rom w/ the Supersick kernel. Any help would be greatly appreciated so I have can have this working before work tomorrow.
Did you do a full wipe ???
ryansinibaldi said:
I recently recieved my One V and finally decided on rooting/installing a custom rom. I came from an Optimus V and had no problems installing a custom rom in that.
However it seems that no matter what kernel/rom I use they eventually lock up within the first 5 minutes of booting and restart. I've tried practically everything and can't get them to work. I wanted to ideally run the CDMA Pacman Rom w/ the Supersick kernel. Any help would be greatly appreciated so I have can have this working before work tomorrow.
Click to expand...
Click to collapse
"It ain't workin" isn't enough information for anyone to troubleshoot from.
Be more specific on what you did, which instructions you followed, what ROM and what kernel, what sort of computer you're running, where you're downloading from, and the steps you are taking. If none of the ROMs are working, the problem is probably not the ROM, if you know what I mean...
donhashem.dh said:
Did you do a full wipe ???
Click to expand...
Click to collapse
Full wipe as in? (sorry, still a bit new). I did do a factory reset in CWM before installing whichever ROM I was trying at the time. I wiped all caches too.
slack04 said:
"It ain't workin" isn't enough information for anyone to troubleshoot from.
Be more specific on what you did, which instructions you followed, what ROM and what kernel, what sort of computer you're running, where you're downloading from, and the steps you are taking. If none of the ROMs are working, the problem is probably not the ROM, if you know what I mean...
Click to expand...
Click to collapse
I used the HTC One V AIO Toolkit to unlock the bootloader, get root, install CWM 6.0, create a backup and then install a kernel (I used the Super Sick JB one). From there I used CWM to gain access to my SD card and transferred over the CDMA Pacman ROM (after wiping everything clean) and then installed the ROM. It booted up successfully however as stated in a minute or so it would freeze up and restart itself. Even if I don't do anything after a reboot it'll still reboot itself anyways.
I did a bit of research and I'm thinking it could be due to the OTA Radio update from 2-3 weeks ago? I'm at my bootloader now and it says I have radio version 1.00.00.0928.
Any further help to resolve this issue would be greatly appreciated. It's worth noting that I've tried many different Kernels (repeating all the steps above with full wipes every time) and different ROMs that were supported by the kernels. I've even tried to restore my phone back to stock and it just starts skipping at the VM Boot screen.
Oh, and I'm running Windows 7.
You mean the Rom booted normally right ?? If yes then the problem is with the Rom
donhashem.dh said:
You mean the Rom booted normally right ?? If yes then the problem is with the Rom
Click to expand...
Click to collapse
Pardon my ignorance but that just doesn't make sense. I've tried several different ROMs with the correct kernel's (Pacman, CM9/10, AOKP JB) and it's all the same scenario. They all boot (or occasionally don't boot and restart themselves at the boot animation) and then reboot themselves once they're pass the lock screen.
Like I said even currently if I restore my stock rom file it just loops at the VM Boot animation (which doesn't play fluidly).
Figured out the issue . It was radio version 1.00.00.0928 messing up my kernel.
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!