[Q] HTC Desire (HD2) Market / MAGLDR issues - Desire Q&A, Help & Troubleshooting

**Disclaimer: I realize that I am a *noob*. I flashed my original G1 to Cyanogen, upgraded my Vibrant to Team Whiskey, and my HD2 to Cyanogen 7. However, compared to many of you, this is insignificant. This is why I seek your help**
I installed Typhoon CM7 to my HD2 today using the directions given. The phone responded well at first, and I was able to install most of my apps back immediately. Due to commitments, I was unable to finish installing all apps I use regularly. Later tonight, I tried to install Google Maps - no dice. When I select it from the Market, I see a down arrow for a second, then nothing - it does not install. I have found that I am able to install other apps (ie Google Books) but not Maps. As an added note, it appears that I cannot install random apps - Angry Birds, for example - but some are fine - Gun Bros. There does not seem to be any logic to it.
I tried to use ROM Manager to boot to the Clockwork Recovery to reflash the ROM, but when I try, MAGLDR autoboots the OS (GO GO GO!). If I try to reboot holding volume down, I get to HSPL. I cannot seem to get to MAGLDR or Clockwork Recovery.
Because of this, I don't know how to proceed. I would be inclined to reflash the the ROM, but I can't seem to find a way to do so. I don't have a use for a ROM that randomly won't let me download (commonly used) apps, so I am open to switching to another ROM. However, as I can't find too much information on this problem, I suspect that it's a random glitch and not a ROM issue.
Does anyone have advice on booting to MAGLDR? Or on how to resolve the market issue? I have tried to use the 'Bad Behavior' reporting to report a 'WTF condition' but the button doesn't do anything. I really appreciate your help, and understand the urge to immediately direct me elsewhere, but I hope that somebody takes the time to provide details. As such, I am willing to help / provide as many details as possible to help solve this!

Update: I did some reading, and found that holding the power button through the MAGLDR screen gives me options - Hurray! I am now trying to reflash the ROM and will soon update whether I am successful. I would say 'stay tuned', but hey, it's my problem, so hopefully I can close this soon without needing any expert advice.

Screw it! I installed another ROM - this seems to have solved my problem. Hurray for fixed problems! Case: closed.

Related

CM7 problems?

I'm making this thread to try and solve issues and problems with cm7 for problems that you can probably solve instead of posting 10 times and making a repeated question in the official thread of cm7 development thread
If you have any issues we can help each other, to start with I got the blue then green light on my first restart, but after wiping data and cache AGAIN (I already did it before installing from zip) it worked!
I had problems with the notification widgets, but after a few restarts it didn't dissapeared. So that problem solved by itself
I currently have the flash notification widget not working (and it works on camera but not on video recording) I don't know if it is a common problem from the beta 3 version (If someone knows I would be thankfull***) but meanwhile you can get the flash to work with this widget https://market.android.com/details?id=com.advback.ledflashlight&feature=search_result
The Wifi is working OK but it seems like the refreshing time of signal is too low (I get close to the wifi router and maybe there are 1min. until the small widget at the top fills up) and viceversa I get away from signal and it is remained full until 1 min or so.
edit:
For Gps small fix you can find in the page 123 this from AkkiandDefy:
1.Search FasterFix in the market and install!
2.Open it and choose your region the
3.Now theprogramm will install the right Config
4.And then install GpsFix and let him search
Don't be afraid..let him search longer(till he tell the right adress). Once fixed he will find it always faster.
Admin or mods if there is any problem with my thread let me know, I'm just trying to help
good Idea
just trying to help hehe my idea is to get the important information in the first post just done the flashing of the test2 for gps going to try right now
I was installing this, and it was all going fine, used the recovery thing here, it booted up fine. I then rebooted again to put on the googleapps as an update.zip, updated and now it gets stuck at the Motorola boot screen?
EDIT: OK, so I tried another data/cache wipe and installing CM7 again as update.zip, but have to use the default bootloader now and it says "signature verification failed". :S
did you instal the nordic version? 3.4.3 11 (the last one) flash this, then install superuser (with superoneclick) afterwards instal the clockwork (I used the same one as you) then wipe data, cache install beta 3, gapps and gps test 2 and reboot it should work
Viridis said:
I was installing this, and it was all going fine, used the recovery thing here, it booted up fine. I then rebooted again to put on the googleapps as an update.zip, updated and now it gets stuck at the Motorola boot screen?
I had the same error - i reflashed the 3.4.3.11 sbf with rsd lite
after that, rooted , instaled clockworkrecovery and booted into recovery mode to instal CM7
After installing CM7, i allowed to boot itself (2init is set on automatic) then just reboot and enter into custom recovery via pressing vol down right after blue notification light appears - frome here you can acces custom recovery and install addons like gapps and gps fix.
Warning - entering from Clockwork recovery after CM7 installed will get you in bootloop and need to reflash the main sbf again.
Click to expand...
Click to collapse
really? I think I did it and it didn't happen that, but anyway my recomendation for those we don't know so much is to install from clockwork the beta, gapps and any fixes (gps etc) at the same time without rebooting so we don't have to use it anymore (in this logical order, 'cause maybe it doesn't mind but maybe it can prevent us from getting any error)
Thanks for the replies everyone.
Right now I've flashed 3.4.3.11 on with RSD Lite, that went fine. I've rooted with Superoneclick and installed the custom recovery app from before, and I can get into Clockwork recovery with that.
Now though when I try to do a wipe it says "can't mount /dev/block/mmcblk0p2 (File exists)" and "error mounting /sd-ext/!". I took out my SD card and formatted and partitioned it with 500mb ext, 50mb linux swap and around 1.5GB FAT to see if that would help, but it hasn't. I did this with my PC, however I did use the one on the recovery before that, which was probably a bad idea. I didn't think to much of it since it should have only affected the SD card.
I think now I need to use ADB or something to fix this, I've also unrooted and rooted again. I also tried installing cyanogenmod before the mount errors when only an "app2sd" error was coming up on the wipe, but it didn't actually do anything, it just started up with the stock 2.2 froyo again.
EDIT: I tried just wiping and installing cyanogenmod.zip and gapps.zip anyway, but it just comes reboots with stock blur/froyo. I don't have any "update.zip"s or anything.
try wipe from stock. do: vol down + power and then when the ! appears with the android guy press vol down + vol up
afterwards you will get stuck in the moto logo. get out the battery, put it again and flash the nordic version 3.4.3 11 then enable adb and with superoneclick install root
IMPORTANT: NOW GET OUT ADB AND REBOOT
after reboot install clockwork and get the beta 4 and gapps into the sdcard,
then wipe data and wipe cache
install from zip first beta then gapps (if an error of line X appears and says installation aborted just try again it will work, happened to me several times) and reboot!
Hey, thanks for the thread.
I have a problem with FasterFix. Mine asks for root permission but it just won't load. Remains in black screen and does nothing. GPSFix opens, but don't sync.
Any ideas?
@Quarx
Thank you for the CM7 mod, I'm loving it.
Will post it to the original forum post once I'm able to.
And will buy you a beer
you made a really good point, fasterfix worked in beta 2 and 3 (installed it several times with some wipes) now that I've read your post and tried installing it it installed granted permissions but it doesn't run so it seems to be a beta 4 problem that wasn't present before!
mariosanoguera said:
you made a really good point, fasterfix worked in beta 2 and 3 (installed it several times with some wipes) now that I've read your post and tried installing it it installed granted permissions but it doesn't run so it seems to be a beta 4 problem that wasn't present before!
Click to expand...
Click to collapse
I hope someone post this on the main thread.
I just applied the *.zip(s) and the am loading in for setup, it seems to be working so far. The boot screen is AWESOME as always... setup seems a bit twitchy but hopefully I'll get it to work here soon. *crossed fingers*
I think Im starting to have the earphone piece problem
Quarx posted another version to the main thread. Downloading now. Seems like it doesn't need to wipe. Lets see...
It seems a little buggy for those who have green lens. I'm waiting with 4.0.
Can I delete this post?
Problems to edit the contacts
Hello.
I've had problems to edit the contacts, in my phone book.
I syncronized my contacs with the Facebook contacts. Have all of then in my contact list, but when i need to add a phone number to the contact, it says that i can't edit Facebook contacts in that device. I need to create a new contact and put the phone number in that new one, and that pisses me cause i will need to have 2 contact from 1 person, duplicating my entire contact list. And all my contat that are in my SIM card don't show in the MOD. I have downgraded and all the contacts now have reapered.
Please, if someone knows how to help, since i was using the Blur, and had all my contacts from Facebook before, editing and merging then when they are duplicated.
It seems like the camera is not THAT working. When I zoom in too much it crashes and I lose access to the camera.
Is Quarx even knowing about this thread?
Edit: I was listening to a song in PowerAmp, opened an YouTube video and all sounds gone, some process forced close and no sound was played until restarted.
Edit2: it seems like that DSPmanager forced close when YouTube opened. Disabled for now.
I've updated to beta4 and the only issue I have is with GPS. Just tested camera, video and flash and all working.
Edit: also issue with video playback... it jumps.
Sent from my MB525 using XDA App
I can't play any videos at all. Guess I'll be back to froyo till this is fixed.
Sent from my MB525 using XDA App

[Q] Nonstop rebooting, even after full wipe/reinstall - last_kmsg inside

Hey everyone.
I know there's a couple other threads with this problem, but none of them included their last_kmsg files. It took a bunch of tries before I could stay booted up long enough to grab it, but I have one.
I'm getting a significant number of reboots on my EVO. Like almost unusable at times. It seems fairly random, although there's a slight suspicion is has something to do with the GPS. Maps has been a crash-cause before and the most recent bout last night was brought on by foursquare. (the annoying part is I had just used 4sq fine 30 minutes prior with no issues. Then, booted it up, refreshed locations and my phone was unusable for hours.)
I've done all the standard things. Fix permissions, wipe cache, wipe dalvik, wipe data/system, reinstall the latest CM7 build (update-cm-7.0.2.1-Supersonic-signed.zip), wipe cache, wipe dalvik. I entered my google account info but told it not to sync anything. It is now rebooting less than a minute after it starts up. I haven't installed any apps at all since this most recent wipe/reload of CM7. It reboots with and without the sd card installed.
I'm at a loss here and getting incredibly frustrated. Many replies say it's as easy to fix as wipe everything and re-do it. Obviously something abnormal is screwed up on my phone and I can't figure it out.
Here's the pastebin from this morning: pastebin.com/Ki7H8bH3 (Crap, I don't post here enough to be allowed to post links. Just add the http part to that.)
And then when I got awake enough, I did another complete wipe/reload. The rebooting is even worse now, it's taken me almost an hour to get to a point I can install es explorer to try and pull another file. And when I did, it was blank.
Any ideas?
Thanks!
1. Go to the link below and download the PC36IMG.zip file for amon RA v2.3 and place it on the root of your SD card.
http://forum.xda-developers.com/showthread.php?t=705026
2. Shutdown your device.
3. Simultaneously press the DOWN volume button and the power button until your device starts. There will be a short pause and then a few lines of text will scroll across the screen. Afterwards, the bootloader will automatically detect the PC36IMG.zip file and prompt you to install it. Follow the easy prompts to install. Installation will take less than 10 seconds to complete. Afterwards, reboot into your new recovery. Go to the backup/restore menu and make a nandroid backup of your current setup.
4. Now go to the wipe menu and wipe EVERYTHING in it EXCEPT the SD card.
5. Go to the flash menu and flash the rom you desire to flash.
On many occasions, reflashing the recovery solved rebooting issues and hopefully, it will solve yours.
posting & replying via the XDA Premium app.
Hi dougjamal,
Thanks for the reply.
I've made some progress. Last night I had done a majority of what you suggested, with installing amon RA. I've also just formatted my entire sd card just to be sure.
I haven't tried wiping things other than cache and dalvik, so I'll try that.
My progress I mentioned is that I had CM7 up and running until I flashed a new kernel and gapps in there. So I guess I'll just stick with the stock CM7 kernel, try your extra wiping and see how that works.
Thanks!
grifta67 said:
Hi dougjamal,
Thanks for the reply.
I've made some progress. Last night I had done a majority of what you suggested, with installing amon RA. I've also just formatted my entire sd card just to be sure.
I haven't tried wiping things other than cache and dalvik, so I'll try that.
My progress I mentioned is that I had CM7 up and running until I flashed a new kernel and gapps in there. So I guess I'll just stick with the stock CM7 kernel, try your extra wiping and see how that works.
Thanks!
Click to expand...
Click to collapse
You're very welcome. Sorry for the delayed response. I was having a late lunch and then drove home. Anyway, keep us informed of your progress and enjoy the rest of your day.
posting & replying via the XDA Premium app.
No worried on any delay, just glad to have someone that took a read and time to reply!
Ugh, it's the randomness of this that has me so frustrated. I thought I had a good install again, I left it sit on the "touch the android" screen for a few minutes and it stayed on. Made it through the setup process ok. I allowed the setup to "auto-download" a handful of the google apps it asks if you want. Once they got to about 38%... boom, restart.
So I did another toooootal wipe and I'll manually install those apps one by one. We'll see...
dougjamal said:
1. Go to the link below and download the PC36IMG.zip file for amon RA v2.3 and place it on the root of your SD card.
http://forum.xda-developers.com/showthread.php?t=705026
2. Shutdown your device.
3. Simultaneously press the DOWN volume button and the power button until your device starts. There will be a short pause and then a few lines of text will scroll across the screen. Afterwards, the bootloader will automatically detect the PC36IMG.zip file and prompt you to install it. Follow the easy prompts to install. Installation will take less than 10 seconds to complete. Afterwards, reboot into your new recovery. Go to the backup/restore menu and make a nandroid backup of your current setup.
4. Now go to the wipe menu and wipe EVERYTHING in it EXCEPT the SD card.
5. Go to the flash menu and flash the rom you desire to flash.
On many occasions, reflashing the recovery solved rebooting issues and hopefully, it will solve yours.
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
Seems like this gets posted quite often, huh??? lol
Don't rule out a corrupt download. If you have the time, download both Salvage-Mod 1.2.1 and the gapps zip from http://www.salvage-mod.com/node/4. If you like CM7, you may like Salvage-Mod. It is pure gingerbread. If you decide to flash it, see whether or not you get bootloops with it.
posting & replying via the XDA Premium app.
HipKat said:
Seems like this gets posted quite often, huh??? lol
Click to expand...
Click to collapse
Indeed, my friend...lol...but it works.
posting & replying via the XDA Premium app.
HipKat said:
Seems like this gets posted quite often, huh??? lol
Click to expand...
Click to collapse
It does and it wish it was that easy. It's frustrating to read that others seem to have no issues at all yet when I follow those directions, which are everywhere, nothing seems to work.
dougjamal said:
Don't rule out a corrupt download. If you have the time, download both Salvage-Mod 1.2.1 and the gapps zip from http://www.salvage-mod.com/node/4. If you like CM7, you may like Salvage-Mod. It is pure gingerbread. If you decide to flash it, see whether or not you get bootloops with it.
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
I re-downloaded CM7 this morning thinking that might be the issue, but it hasn't seemed to help. I'll give a different rom a try probably, maybe there's something other than CM7 I'd be content with.
Whelp, I downloaded SalvageMod and their gapps. Wiped everything, installed salvage, installed gapps, rebooted.
I got through set-up, was ok for a couple minutes, then as I was going into my contacts to see if they had sync'd yet... reboot.
This makes me think this can't be a ROM issue.
Any other ideas?
Does the same thing happen when you run a stock (or close-to-stock) rom? Main reason I ask is that this might actually be some sort of hardware problem, but one of the best ways to test for that is to be running on stock software. I wouldn't necessarily suggest flashing an RUU to get to the latest official release, but there are stock rooted roms out there that you could try.
You probably went with CM specifically to get away from Sense and the default HTC stuff (that's most people's reasons anyway), but if you flash a stock rom and it's still rebooting like that then I'd say chances are REALLY good that it's hardware and that you'd have grounds for getting a replacement phone (just remember to unroot first.)
And if it stops randomly rebooting on you then you'll have at least narrowed things down a bit.
jesuspgt said:
Does the same thing happen when you run a stock (or close-to-stock) rom? Main reason I ask is that this might actually be some sort of hardware problem, but one of the best ways to test for that is to be running on stock software. I wouldn't necessarily suggest flashing an RUU to get to the latest official release, but there are stock rooted roms out there that you could try.
You probably went with CM specifically to get away from Sense and the default HTC stuff (that's most people's reasons anyway), but if you flash a stock rom and it's still rebooting like that then I'd say chances are REALLY good that it's hardware and that you'd have grounds for getting a replacement phone (just remember to unroot first.)
And if it stops randomly rebooting on you then you'll have at least narrowed things down a bit.
Click to expand...
Click to collapse
Hey jesuspgt,
I haven't tried that yet. I'll look around for a rooted stock ROM later and give that a shot.
My current status is back to uncertainty. At the moment, my evo has been sitting here fine, not rebooting, for the past hour or two. It's still the Salvage ROM I first installed (i.e. I haven't reinstalled it since it rebooted). Now I haven't really used it any, so it might go to hell as soon as I do that, but for now, it's on and only had that one (maybe two, I can't keep track...) initial reboot.
That's what makes it tricky to diagnose. I know using any custom ROM runs the risk of loosing stability and all ROMs probably produce a reboot here and there. Tough to tell if it's just a "comes with the territory" type of reboot or an actual problem.
Even though I'm sure there's some CM features I'll miss, maybe Salvage is my answer.
Thanks!
*sigh* Well I decided to try using some apps and guess what... reboot.
All I was doing was trying to play a game of Androminion, which is about as basic and not-tasking as possible, so I can't imagine that's what crashed things.
The only thing I can think of that you *may* need to do is reflash your hboot and/or your baseband, PRI & NV from within recovery. You can download it from the link below.
http://forum.xda-developers.com/showthread.php?t=715485
posting & replying via the XDA Premium app.
dougjamal said:
The only thing I can think of that you *may* need to do is reflash your hboot and/or your baseband, PRI & NV from within recovery. You can download it from the link below.
http://forum.xda-developers.com/showthread.php?t=715485
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
Excellent, I'm going to try that. My hboot is still 0.93!
Hey dougjamal,
Just wanted to drop an update. I know how annoying it is to help someone out and never hear how things ended up!
Who knows what combo helped, but I'm fairly stable now. After updating my hboot, I flashed to Sprint Lovers, did the ##GPSCLRX# trick and then flashed to the latest nightly of CM7 (63 I believe). Only one or two crashes and one bootloop since then.
Of course, as luck would have it, a new problem showed up in the form of a dead spot on my touch screen. Right about where the "Clear" button is for notifications, that entire strip across the phone won't respond to touch. I was hoping it was a nightly issue, but I switched to a different rom and the issue was still there. Looks like it's going in for a warranty claim after-all!
Thanks for all your help
-grifta67

Revolutionary on new wildfire problem (or extreme muppetry)

Hello everyone.
I enjoyed the noob video and also look forward to being pasted no doubt.
I have a wildfire running 2.2 android which I understand means I am running the latest firmware, which I also understand is going to make it difficult for me to root easily.
Never the less not being one to be beaten I have tried with EVO3, which no matter what I tried would not work, constantly asking if my firmware was too new. I even wiped it but no luck.
So I struck upon revolutionary, which yes I understand is beta.
This is perhaps where my lack of understanding comes in. Would I be right in thinking that custom roms require a specificly rooted device?
The thing is I have apparently been successfull with revolutionary. I can boot into it and I was able to instaly cryongena rom which worked OK until I installed google apps where by it constantaly showed the spinning blue arrow, round and round, rebooting and rebooting.
Thing is all other roms I have tried, everyone, has failed, with either script being old 'error 6' etc etc.
I found I needed a different kind of rom, which a few were offering however these also failed with error 6 which apparent was something to do with not being pure unix or something.
Sorry I am not up on the language, but I think I have tried all the popular ones, puzzle etc and none will install.
When I start up with the volume button pressed it shows the screen then says something about failing to load image, but goes away to quick to read pc4diag.img or something.
Is it possible I have not loaded revolutionary correctly, and have I gained 'root'
Thanks for reading, and please feel free to tear me a new one.
- Yes, I am sure you have Revolutionary installed correctly. You got a bootloop while installing GApps, in which case I would recommend performing a full wipe in Clockworkmod and try to install again. (Install the CM ROM first, then the GAPps Zip. Also, I hope you are using a filename called gapps-gb-2011xxxx.zip)
- If you want to install other ROMs, Sense and Android 2.2.1 ROMs require Clockworkmod 2.x. Attempting to flash them in Clockworkmod 3.x/4.x will give you the "Scripting not supported" error. The workaround to this is to download this attachment:
http://forum.xda-developers.com/attachment.php?attachmentid=662193&d=1311319218
Flash this in your new Clockworkmod Version, which will give you temporary 2.5, then proceed as normal.
- When you boot into the HBoot Mode, it will automatically perform a search for the files PC49IMG.diag and .nbh. It's normal, and theres nothing to worry about. After the search is over, and, it has not found the files, you can navigate properly again.
Oh, and I think you are being too paranoid about the video and everyone here trying to tear you a new one.
Good Luck
Thanks very much for your answer.
Honestly I spent 2 hours on google last night trying to get my head around it.
To be honest all I want is a quick phone, and I am not getting that with stock software on my wildfire, I get very frustrated when trying to scroll but it reads it as me tapping an app icon, and there are loads of them I don't want in here, footsteps and tweets and the likes, I am simply not interested and neither am I allowed to remove them. The cynogenmod looked amazing, but I can see even more processor intensive than the stock software.
I will have a look at what you have suggested and thanks for your help!
In that case, I think you might want to stick with the Stock ROM, and, get an app like 'Root Uninstaller' or 'Titanium Backup' which allows you to uninstall (Or, to be more correct - 'freeze') any apps you wish - Including System Apps.
Not trying to advertise Cyanogenmod here, since I understand ROM preference is a personal thing, but, I would recommend giving it one more try, after a full wipe. Also, go with the latest nightlies rather than the Stables. I have been using it since it was released back in January, and, honestly, I am never going back to Stock / Sense based ROMs.
Don't get me wrong it looks awesome. But the boot up time was just shy of 4 minutes (although I now understand it may have been because of first boot) and two attempts at install failed.
I shall look at how to fully wipe, but to be honest, being very new to hacking my phone I am quite happy having the back up there to revert too.
Well I tried to install anything but nothing works so I shall revert to my original back up and see about these tools for removing unwanted apps.
Thanks for the help, but something is not right. All roms either get as far as the twinkly noise on the HTC screen then do it again and again, and cynogen gets to the rotating arrow, then eventually an android zips across the screen and back to the arrow
Well I don't think I have root on this device. I tried to install busybox and titanium and both tell me my phone is not rooted.
Sigh.
If you are on the Stock ROM, you will have to flash this additionally:
http://bit.ly/su2361ef
This will install Superuser, which is what will give you "root". If you are on Custom ROMs, flashing this additional file is not required, since, they include the Superuser Binary already,. So, flash that, and then try installing Busybox / Ti Backup. (make sure you get a "superuser" icon in your app drawer after flashing that zip)
EDIT:
- Are you on Clockworkmod 3.0.0.6 incidentally? That version has caused bootloops for many users when installing ROM's.
- First boot time is extremely long (Upto 7-8 mins), and its normal.
Hello thanks for the info.
I am not confident I know what mod I am on, I just went to the revolutionary website and downloaded the latest beta.
When you say it can take 7-8mins to load up would this include the boot loops though? Thats all I get on all of them
I shall install the super user bit see if that helps.
No, not including bootloops. BTW, I am referring to the Clockworkmod Version, not Revolutionary,
When you enter the Recovery to flash something, at the bottom, you will "Clockworkmod Version x.x.x.x". It is that version I was asking.
Sadly I am not getting anywhere here, every single rom just goes round in circles in one way or another.
The version say revolutionary CWM v4.0.1.4
I was unable to get the standard revoked installed as I am runnning the latest android firmware and it just kept failing.
Something I am getting rather used to!
I cannot see a clockwork mod number anywhere, although it must be there as I have clockwork folder on the SD card.
Sorry, I am being a muppet here.

JIUI JB and CWM problem

Hi everyone, hope someone can help...
I’ve been playing around with custom roms for years, on all sorts of phones from my old HTC Hero through to my current Defy, without any problems that I haven’t been able to fix, but this has got me stumped. I've spent ages searching the forums, but haven't found anything relevant - apologies if I've overlooked a thread.
I installed JIUI JB on my trusted Defy, just to see what it was like and fully expecting to be able to re-install my favourite WajkIUI rom. Unfortunately, now I’ve decided to return to a stable rom I’ve run into a bit of a hitch.
I can’t work out how to boot into ClockworkMod recovery to install the zip from my SD card. I’ve tried power button and volume down but only get as far as the Android system recovery, and this obviously won't let me install a normal .zip file. Is there something blindingly obvious I’m missing?
I thought I could install a recovery manager from Play and use that to reboot, but some bug in JIUI JB – or something I’ve inadvertently done! – means that my phone is reporting inadequate internal storage. When I go into Apps in Settings it reports no internal storage at all, so no apps will download.
So now I’m stuck with a smooth but buggy rom, and I can’t replace it. Any ideas or suggestions gratefully received. Thanks in advance for your help.
Reboot and on blue led ress volume down button.....Viola u r in bootmenu....then go to recovery and custom recovery whatever........
And come on dis info is in d open of the guide thread which is a sticky too
Sent from my MB526 using xda app-developers app
Thank you for your help, that seems to have done the trick.
And apologies too - I knew the info would be somewhere, but I did search and didn't find it. If that's down to my inability to search effectively then mea culpa, but don't blast me for not trying! Sometimes the answer you want doesn't appear, however hard you look.

[Tutorial] Installing Wildchild and getting it working on VM WFS CDMA

I'm not entirely sure where this topic would go, but I have figured out how to get wildchild 2.0 and 3.3 up and running on the VM WFS. It might work for other CDMA Wildfires, but I'm not sure. I figured it out after reading a post by 'threefootsmurf' who said he got it working. I'm just making a tutorial on how to install it and get it running fully without problems, since I had a few problems, and to show that we have a great rom for CDMA phones. Oh and these steps are pretty straightforward, but I left out things like backing up everything since you should be in the habit of it already.
1. Download the wildchild file. Either 3.3 or 2.0, I have found that the odex version for 2.0 and the deodex for 3.3 tend to work better than the other..
2. Download the 'Hensemod' VM patch.
3. Put them on the root of you micro sd.
4. Boot to recovery and factory reset and wipe dalvik
5. Flash the wildchild ROM.
6. Boot the phone and go through everything, you will probably get error messages and the phone may shut off and power back on, but your main goal is to get to the home screen after doing the google setup and everything.
7. Reboot back into recovery and do a factory reset and dalvik wipe again.
8. Flash the hensemod VM Patch. (You may need to reflash the rom again and then the VM patch in one go here, it all depends)
9. Boot the phone and go through the google set up and everything again, and the phone should be in working order.
Those were the exact steps I used. I tested multiple ways to do it, some gave me bootloops, some stayed on the HTC splash screen, and some kept rebooting the phone. I like the wildchild ROM and this tut will open up the wonderful rom for VM and possibly all other CDMA users. I hope this helped you guys.
Wildchild 3.3: http://forum.xda-developers.com/showthread.php?t=1842771
Wildchild 2.0: http://forum.xda-developers.com/showthread.php?t=1652973
Hensmod: http://forum.xda-developers.com/showthread.php?t=1434497
thanks for the shout out.
yeah not sure why exactly but i usually need to flash the keyboard add-on to get any keyboard function. and the flashing of the rom on official CWM for marvelc seems to have its issues like deodexed don't like to load right or boot loops. after i switched to the unofficial CWM touch recovery for our phones not an issue at all loading after flash. and i usually flash it all at one time. if anyone has the same CWM as me, to do a data/cache reset select it then press vol up 5 times and you are on yes even though you can not see the option, press power and let it finish its wipe. definitely a great fast rom. found some new tricks i wasn't to test so might go back up to 3.3 soon for the extra speed boosts, only thing holding me back is i don't want to spend a whole night restoring my apps backups again lol.
love experimenting with this little thing though even if i am slightly noob to droid
I advise you to post tutorials like this in the General section
threefootsmurf said:
thanks for the shout out.
yeah not sure why exactly but i usually need to flash the keyboard add-on to get any keyboard function. and the flashing of the rom on official CWM for marvelc seems to have its issues like deodexed don't like to load right or boot loops. after i switched to the unofficial CWM touch recovery for our phones not an issue at all loading after flash. and i usually flash it all at one time. if anyone has the same CWM as me, to do a data/cache reset select it then press vol up 5 times and you are on yes even though you can not see the option, press power and let it finish its wipe. definitely a great fast rom. found some new tricks i wasn't to test so might go back up to 3.3 soon for the extra speed boosts, only thing holding me back is i don't want to spend a whole night restoring my apps backups again lol.
love experimenting with this little thing though even if i am slightly noob to droid
Click to expand...
Click to collapse
I know what you mean I'm a pretty big noob at this stuff too, but it's fun thinking I have some kind of involvement in something. I'm using WC 2.0 right now since I can't get 3.3 to load on the odexed version with wifi and data working. I gotta edit my post. I got the deodexed version running, but it's got bugs, like FB wont work, and a few apps wont work right either, and of course no A2SD support... Lame. And I tried flashing all at the same time. But i'd get bootloops with 2.0. So I had to do it the way I described. Not sure if it's my phone my recovery or what. But yeah....
THANKS
This should be stickied for marvelc.
Thank's wc running great on marvelc.
Sent from my HTC_A510c using xda app-developers app
I just flashed WildChild 3.3 to my VMUSA Wildfire S last night. Here is my experience so far:
Definitely install WC and the VM patch right on top of each other in one shot
Skip the keyboard tutorial in the setup
If you get to the wifi setup and yours isn't listed, you need to wipe/reset/clear dalvik and install both files again or you're gonna have a bad time
I've got video playback problems. Videos I record playback with horizontal matrix green crap, and videos in the YouTube app give me audio only
Opinion: There are a few things I don't like about WildChild which are causing me to abandon it after 24 hours. The video issue is unacceptable, and a bunch of strange app choices make this not much better than the crap apps that come with HTC/VM Sense to begin with. Stock browser is absent in favor of Dolphin, no Google Talk app, no default Calendar, required use of Startup Manager (Free) which I feel is pretty useless to me, and a whole list of other apps (like a dozen) I am too lazy to deal with. I realize what I am looking for is a barebones setup, and I'm going to look for it starting now.
Thanks for this post. I've been running Wildchild 2.0 for a few months now. The video issue mentioned above comes & goes with certain app installations - oddly enough a reinstall of the youtube app usually clears it up on my WFS.

Categories

Resources