Develop Bugs

[General Help] After Rooting & Nand removal

I've been through Toastcfh & friends very helpful directions.
My screen at one point when turning the evo on shows the signature HTC Quietly..(Something in green). It also had a lot of option that seemed to be unlocked/nang unprotect stuff. Like i remember one of apps that were on there like: wiconfig. These apps looked like back doors to options and setting that are for superadmin privileges.
Whenever I finish the last two steps in Toastcfh & friends' instructions I'm back to the normal HTC screen when turning it on. In this state I don't see all the extra apps that seem to let me have superadmin privileges.
I've gone back and forth by using ROM management and Toastcfh's method but every time I go back or forward I have to lose all the apps I've downloaded and most of my settings. Is this normal?
Is there something I'm doing wrong? Am I supposed to flash every time I want to be in "hack" mode or something? Very new to this, need some help from the pro's. What I'm trying to achieve is something permanent that gives me access to taking off sprint apps, free tethering like hotspot and normal awesome day to day HTC Evo phone usage.

I sure hope you didn't remove NAND. (just a quick joke)
Anyways, every time you flash to another ROM you should always clear apps and data. Many ROMs will do it for you.
Some ROMs have updates and the maker will allow it to just be updated, but even so it's not always recommended.
If you're doing alot of experimenting, just do a nandroid backup of a ROM you don't mind defaulting to if you end up wanting to revert back. A nandroid backup is an entire backup with data (apps) and all.
ALSO, to get into "hack mode" (referred to as recovery) you just hold the volume down and press power.
If it asks to flash and/or reboot just say no and select recovery. If you want it to stop asking to flash just rename PC36IMG.zip (on your sd card) to something else.
If you followed part 2 (which it sounds like you did) you will have a modded recovery menu to make things easy.

Do you know right off your head what thread talks about how to Nandroid backups? If not ill do my searching.
Thanks
P.s recommend any roms I might like to stick with?

slimm9969 said:
Do you know right off your head what thread talks about how to Nandroid backups? If not ill do my searching.
Thanks
P.s recommend any roms I might like to stick with?
Click to expand...
Click to collapse
Here's a pretty good thread to look at...
http://forum.ppcgeeks.com/showthread.php?t=123714

[Q] Working with a Used Phone

Hello all,
Introduction:
My name is Dev, and I have purchased a phone from Craigslist about a year ago. I used to use Windows Mobile phones. I had no problems with them. I have used the T-mobile MDA, Wing, and Touch Pro 2. They have been good phones for me, until recently. I have always wanted a faster phone and the Touch Pro 2 seemed to be quick enough for me. Nope. It slowed down just like the others. My brother is younger than me, and he has been attracted to the Android market since the T-mobile G1. I never got an opportunity to enter this operating system market. I am very tech savvy however, and it has merely been a case of me not wanting to "change." However, I am past that and I want to contribute to the Android community. My first Android phone is the T-mobile myTouch 3G Slide. (I like sliding phones in case you haven't noticed. I must have the physical keyboard. I text a lot.) I bought it used from Craigslist, and it seemed to work fine then. The previous owner was nice enough to clear all the data off of it, and give it to me fresh. I have been using it since.
Leading into my problem/question:
Lately, however, it has been slowing down too. I want to reset it to a clean slate. I know how to do it. It is in the menus. However, I do not like how this phone has been modified. Why would you modify a phone? I have never had to do this with my Windows phones. There has never been a need to flash any roms or anything. They had updates which were simple to use. Plug the USB into the computer and follow the simple steps. Make sure it doesn't shut off during flash. Simple. I've done this plenty of times with printers, motherboards, CD-ROMs, and all other flashable devices. I understand how big of a risk this is. If the flash doesn't complete (or is the wrong rom), then the device will not work again. Unless, you J-TAG the device and flash it again correctly. But, that requires a lot of work, and a wiring schematic to figure out where the J-TAG ports are. I have learned this information from back in the day when I used to do dish testing. You would flash roms to satellite TV boxes and experiment with new encryption technologies for satellite TV. That being said, I am terrified of flashing phones, because I would have no idea where to look for J-TAG ports for phones, if I mess something up. So, in conclusion, my experience in flashing has been for testing purposes only.
Problem/Question:
How do I figure out what the status of my phone is? It says Cyanogen Mod on start up. My brother tells me this is a very good rom. Who decided that though? Is it a bad idea to go back to stock T-mobile rom? I've always had this thought nagging me to try it and see why people go through all this headache of S-OFF and rooting phones. However, if I go back to the stock rom, will I be able to gain access to the phone's internal memory again? I don't like the idea of losing the S-OFF and rooting privileges the previous owner worked so hard to do. I would like to flash the latest T-mobile rom to the device, but how do I know if it will mess up everything and clash with some code leftover from the modified rom of Cyanogen Mod? Also, how do I backup all my stuff? I want to keep all my setting for the programs I have downloaded from the Google Market. I want to keep my contacts and notes. I want to keep my text messages and MMS messages. I am one of those idiots who keeps all his text messages and MMS messages archived. I go back through the messages from time to time for retrieval of important information I may have spoken about with someone in the past. I know this is a loaded post. I am sorry. If anyone is willing or able to help me, then please pick any point in this post and we'll go from there. This was just an outline of everything so you guys can help me find a starting point.
What I Know About the Phone:
T-Mobile myTouch 3G Slide
Android 2.3.3
Baseband 47.63.35.21U_7.15.35.16
Kernel 2.6.32.17-cyanogenmod-g501281a [email protected] #1
CPU ARMv6-compatible process rev 5 (c6l)
Mod CyanogenMod-7.0.0-Slide
Build GRI40
I believe it is S-OFF and it is rooted. I would like a procedure to verify though. Please.
Memory Card:
Memory card has a lot of folders and stuff on it from which I have no idea. Some of it says nervous stuff like ".android_secure" "clockworkmod" "2111.zip" "signed_Froyo_Slide_Radio.zip" "gapps-gb-20110120-signed.zip" "update.zip" "update-cm-7.0.0-Slide-signed" and "Android" I like it when my memory card is clean with nothing but a few folders like "Pictures" "Videos" "Movies" "Data" "Programs" "Software" "Music" and other general stuff like that. I like this so I can use the memory card elsewhere and know where everything is. Basically, I want to know if I can delete everything without shooting myself in the foot. How do I find out what each .apk is for? Will a stock T-mobile rom come with all the stock backgrounds, contact pictures, and all the other stock goodies? I feel like some of those were on the SD card too.
Things I like:
Speed. I like things to be fast. Utilitarian. I don't want any fancy effects, typically. I like everything simple. For example, my desktops are all using the Classic Windows Theme, and all fade in / fade out have been disabled. I want my phone to be the same way. Nothing I don't need. Minimalistic. I don't like to keep many programs running at once. This was something I liked about the Windows phones. I could click in the upper right hand corner and it would present a list of running programs. I could close specific ones that I did not want to run in the background. Android doesn't seem to have a feature like this, but it does seem like they close if they are not being displayed on the screen.
WIFI
How do I fix the WIFI in this phone? It seems like the radio drivers are wrong are outdated. It keeps dropping the connection immediately after the phone connects to a wireless network. I noticed a thread, but I cannot post to it. I wanted to ask how I would apply this patch to my phone without having a rom or anything. I thought maybe I could boot the phone into the recovery mode, and install the radio drivers maybe? I don't know what I am doing though, and want some guidance.
http://forum.xda-developers.com/showthread.php?t=1177650
And, why does the GPS take so long to get a fix?
Moderators/Thanks
I am very sorry to anyone and everyone whom I may offend in this post. If all my questions are answered somewhere else, please direct me to the correct area. I have been searching and researching for so long and I don't seem to be getting anywhere. I gave up about two months ago, and now I am back again trying to fix this phone. Please do not be mad at me for pestering you guys with annoying questions from new users like me. I know you guys are tired of answering these questions over and over again. Please. Just give me a little guidance. Thank you so much for any and all help. I really truly appreciate this. Android seems to be a very good operating system, and I am looking forward to all your posts.
P.S.
Sorry about the length of this post. It is my first time.

Test
Testing to see if I get notification of replies.

Well, for starters, welcome to the myTouch 3G Slide fora, second, yes, your brother is right, you are running the best ROM available at the moment, but your running an older version of itif you like, i can link you to an updated version of the ROM or i can point you to the "Android Development" section of the forum for the myTouch Slide and you can pick one your self, if you need any help with your device, feel free to PM me or reply to this thread at any time, seeing as how iI am one of the last people who actually still support this device for ROMs, i would reccomend my "TeamFreedom LeWaOS" ROM, but im still working out some kinks in it, for now, i will give you the opportunity to update to the latest version of "CyanogenMOD 7.2":
Download the ROM (has fix for WiFi i believe): http://download.cyanogenmod.com/get/RC/update-cm-7.2.0-RC2-espresso-signed.zip
Download for the latest 2.3.3 GAPPS: http://goo.im/gapps/gapps-gb-20110828-signed.zip
Also, here is how to FLASH these ROMs:
Pre-requsite: PLACE "update-cm-7.2.0-RC2-espresso-signed.zip" and "gapps-gb-20110828-signed.zip" on the root of your sdcard
1: Hold the power button on your phone
2: Tap "Reboot"
3: Tap "Recovery"
4: when in "Recovery" use the Volume +/- keys to move and the trackpad to select "Wipe data/factory reset" then select "yes" if necessary
4a: select "Install zip from sdcard"
5: then select "choose zip from sdcard"
6: select "update-cm-7.2.0-RC2-espresso-signed.zip"
7: When finished select "reboot system now"
8: again, reboot into recovery
9: flash "gapps-gb-20110828-signed.zip"
10: reboot system, and enjoy your updated phone, this process overall is the same for all android phones, and for all ROMs

Thank You
Thanks. I will try the new CyanogenMod rom.

Dealing with the performance of your phone, how many SMS/MMS msgs do you have currently? I noticed you said you dont like deleting them. Thing is, if you have a lot of msgs it can significantly impact your phones performance. Obviously it impacts the messaging app but in my experience it can affect the whole system. This may not be the case on CM ROMS but i have noticed it on stock. (i dont use CM much, prefer Sense).
Also u can try overclocking. I like NoFrills app from market. Its free and allows u to select your i/o scheduler and governor.
For backups, hands down Titanium Backup is the best if u ask me (and many others).
Hope this helps a little.
Sent from my T-Mobile myTouch 3G Slide using XDA App

Update on CM7
Hey, guys.
So, I've updated to CM 7.2.0. Since then, I've been having problems with the touch screen and the phone app. If I use the directional pad, I can highlight the phone app, but when I click on it, it crashes. Also, the touch screen is unresponsive all the time. Sometimes, I will get lucky and when I reboot it, I will get access to the touch screen again. I am wondering if maybe I didn't update the drivers for the touch screen or the phone radio or something. I have a hunch that the phone app is crashing and lagging the whole system, so the touch screen isn't working because of that. When the touch screen does work, the phone app is also working. I am thinking of just flashing the phone with HTC's stock rom and then rooting and s-off it all over again, because I think the previous owner didn't do something right. I want to know if I can just flash the stock rom without any consequences. And, also will I be able to get it rooted and s-offed again? I'm hoping that by flashing the stock rom, I can test my touch screen and phone app with confidence. Maybe the phone app is sending commands for a newer firmware revision, and mine isn't updated to that version yet. Not sure how this works really. Anyways, any help would be greatly appreciated. Thanks in advance.

Suggestion. Re-flash the rom, but in recovery go into advanced, wipe dalvik cache. Hit back, now in mounts and storage. Wipe the following, boot, system, hit back wipe/factory reset, wipe cache. Flash rom, then gapps. Reboot. You should be good to go. Hope this helps.
Sent from my T-Mobile myTouch 3G Slide using xda app-developers app
---------- Post added at 05:07 PM ---------- Previous post was at 05:05 PM ----------
Oh and to check for S-off reboot to bootloader when holding power, or while phone is off power on while holding vol down. Should say alfarev s-off or unlocked.
Sent from my T-Mobile myTouch 3G Slide using xda app-developers app

Ran into a wall
Alright, guys.
So, I ran into a wall. It is now completely unresponsive to the touch screen. I had recently flashed it, and I am trying to do what you had suggested, Dvarl. The problem is that I cannot touch the android logo so I can continue onto the Rom Manager where I can flash and reboot into recovery. If I try to go into the recovery by holding the down arrow and power button, then clicking on "Recovery," I get the red triangle logo. It has always been this way. Lastly, my phone is not s-offed. Thanks for helping me out with that. lol Any ideas on how to flash without the Rom Manager recovery flash?
Edit: I think I have found the problem. I think my digitizer is going out. I am going to maybe purchase a new one and see if it fixes the touching problem. I'll keep you guys posted. Thanks for all your help thus far!

[Q] Unusual problem installing Jellytime R16

I have just flashed Jellytime R16 to my DHD but have a slightly damaged touch screen. Unfortunately the part of the touch screen that doesn't work is the bit where you have to press the start button to move off the screen where you select the language on first boot up.
Does anyone have any ideas how I could skip the first configuration screen of the Jellytime R16 ROM?

I don't think it's permanent maybe a bad zip? Did you check MD5 checksum before you flash? And did you full wipe?

Sorry, I don't think I made myself clear. I do have a damaged touch screen nothing to do with the rom. There is a section of the touch screen that just doesn't work. It is this part that sits exactly where the start button is. It is a shame these start screens don't rotate or the start button was slightly bigger.
So if I could skip this fisr language selection screen I would probably be ok for using the rest of the rom.

I had quite a bit of trouble earlier today installing R16 due to the screen not working at all after the bootup. Had to pull the battery 2 times in a row and make sure the charger was unplugged before the screen would react to touch. Maybe you're also experiencing this thing (several others are reporting it in the JT thread).

foxx1337 said:
I had quite a bit of trouble earlier today installing R16 due to the screen not working at all after the bootup. Had to pull the battery 2 times in a row and make sure the charger was unplugged before the screen would react to touch. Maybe you're also experiencing this thing (several others are reporting it in the JT thread).
Click to expand...
Click to collapse
As I said in my last post this is not a Rom problem I do have a damaged touch screen. I Just need a way of getting past the first setup screen or rotating th screen.

Skunkworx said:
As I said in my last post this is not a Rom problem I do have a damaged touch screen. I Just need a way of getting past the first setup screen or rotating th screen.
Click to expand...
Click to collapse
This is a horrible suggestion for any other use and goes against everything we know about proper flashing, but if all else fails maybe try dirty flashing it over another ROM in which you CAN go through the first boot settings (for example, an ICS ROM that doesn't require the START button in that location). If the unexpected problems that sometimes arise from dirty flashes don't come up, you might be able to get into Jelly Time without the first boot menus.
Obviously, all the problems with dirty-flashing different ROMs come with this "solution."

bananagranola said:
This is a horrible suggestion for any other use and goes against everything we know about proper flashing, but if all else fails maybe try dirty flashing it over another ROM in which you CAN go through the first boot settings (for example, an ICS ROM that doesn't require the START button in that location). If the unexpected problems that sometimes arise from dirty flashes don't come up, you might be able to get into Jelly Time without the first boot menus.
Obviously, all the problems with dirty-flashing different ROMs come with this "solution."
Click to expand...
Click to collapse
Thats an interesting suggestion but the question there is which ICS ROM would give the best results?
I think I would prefer to have a full wipe on installation. So having a way of skipping that first configuration screen, or remotly pressing the start button or even been able to force it to rotate the screen would do the trick. However untill you have got past those first configuration screen you are locked into not been able to run any applications.
I was wondering if there was any way via ADB command line to achive this?

Skunkworx said:
Thats an interesting suggestion but the question there is which ICS ROM would give the best results?
I think I would prefer to have a full wipe on installation. So having a way of skipping that first configuration screen, or remotly pressing the start button or even been able to force it to rotate the screen would do the trick. However untill you have got past those first configuration screen you are locked into not been able to run any applications.
I was wondering if there was any way via ADB command line to achive this?
Click to expand...
Click to collapse
Yes there is. You can use the "adb shell input keyevent <event_code>" command.
You'll probably want to send the DPAD_CENTER command to click that button. I think its event code is 23. Try typing "adb shell input keyevent 23".
Try the code for KEYCODE_ENTER as well.. its 66.
There is a whole list of keyevents at this link:
http://developer.android.com/reference/android/view/KeyEvent.html
Just lookup the "Constant Value" in the description of whatever KEYCODE_xxx you're trying to simulate and use that constant value as the event_code for the command.
I've tried simulating the DPAD_LEFT and DPAD_RIGHT keypress and they're working like a charm
---------- Post added at 04:34 PM ---------- Previous post was at 04:14 PM ----------
Yup. I've tried working with these Keycodes and they work fine.
Use event_codes 19 for UP, 20 for DOWN, 21 for LEFT, 22 for RIGHT to navigate to whatever button you need to press and then use 23 for pressing that button.
Should solve your problem.

Skunkworx said:
I have just flashed Jellytime R16 to my DHD but have a slightly damaged touch screen. Unfortunately the part of the touch screen that doesn't work is the bit where you have to press the start button to move off the screen where you select the language on first boot up.
Does anyone have any ideas how I could skip the first configuration screen of the Jellytime R16 ROM?
Click to expand...
Click to collapse
Hi, did you flash Gapps as well? I've moved from ARHD (which has the configuration start screen) to JellyTime and never got the language or any other configuration start screen (which I'm glad to get rid of). I always full wiped, clean flashed just the ROM, then booted into the OS for the first time to check it out. No Gapps and no language/configuration screen - it would always go straight to the lock screen where I would just swipe to the right and it would ask me to choose either the Nova or Trebuchet launcher. I'd then rebooted into recovery again and flashed Gapps. Hope this helps.

if4ctOr, Thanks for your suggestion this is what I was originally looking for however I didn't get around to trying it as the idea that divche put forward was a much easier approach.
Divche: Thanks, that did the trick perfectly. I am also comming from ARHD so I thought I give your idea a try. I was flashing the Gapps at the same time but booting into the OS first then flashing the Gapps after that prevented the configuration popup.
I am currently swapping between ARHD and Jellytime using the recovery backups as I still haven't got everything installed and setup in the new ROM yet. I didn't realise but I had quite a few of my contacts as phone contacts and not google contacts so they didn't sync into the new rom. So I am looking for a soloution to that and also a way to move my sms messages over.
Eventually I am planning on using the Jelly time as my full time ROM but there are alot of updates to it at the moment, which is a good thing in making it stable. However it takes quite a while to apply all the applications and settings I use after doing a full wipe. Do you need to do this when flashing a new version of JT over a previous one or is there an easy way of doing that? As I read in a lot of places that you should always do a full wipe and that titainum backup is not recomended?

Skunkworx said:
if4ctOr, Thanks for your suggestion this is what I was originally looking for however I didn't get around to trying it as the idea that divche put forward was a much easier approach.
Divche: Thanks, that did the trick perfectly. I am also comming from ARHD so I thought I give your idea a try. I was flashing the Gapps at the same time but booting into the OS first then flashing the Gapps after that prevented the configuration popup.
I am currently swapping between ARHD and Jellytime using the recovery backups as I still haven't got everything installed and setup in the new ROM yet. I didn't realise but I had quite a few of my contacts as phone contacts and not google contacts so they didn't sync into the new rom. So I am looking for a soloution to that and also a way to move my sms messages over.
Eventually I am planning on using the Jelly time as my full time ROM but there are alot of updates to it at the moment, which is a good thing in making it stable. However it takes quite a while to apply all the applications and settings I use after doing a full wipe. Do you need to do this when flashing a new version of JT over a previous one or is there an easy way of doing that? As I read in a lot of places that you should always do a full wipe and that titainum backup is not recomended?
Click to expand...
Click to collapse
For moving SMS, I'd suggest this app : https://play.google.com/store/apps/...mNvbS5yaXRlc2hzYWh1LlNNU0JhY2t1cFJlc3RvcmUiXQ..
And as far as flashing the updates of JellyTime are concerned... It is recommended to always full wipe but you might get away with flashing the update over the previous version without a wipe. In some updates the author of the ROM explicitly says that full wipe is needed... in those cases you must. In other cases you can flash the ROM without the wipe which will keep your apps and data intact. However, it would still be better to wipe your cache and dalvik cache atleast.
Using Titanium Backup is not recommended at all when you're switching between different Android versions.. however I personally think it works ok when used between updates of the same ROM.

Skunkworx said:
Divche: Thanks, that did the trick perfectly.
Click to expand...
Click to collapse
I never encountered the config screen, so it was more of a guess based on what I did, so I'm glad it helped!
I am currently swapping between ARHD and Jellytime using the recovery backups as I still haven't got everything installed and setup in the new ROM yet. I didn't realise but I had quite a few of my contacts as phone contacts and not google contacts so they didn't sync into the new rom.
Click to expand...
Click to collapse
I also had all my contacts as phone contacts too. I chose to convert my contacts (and my calendar as well) to google for ease of syncing later on, so I have no tried and tested suggestions on how to maintain them as phone contacts. What I did was let HTC Sync synchronise with Outlook (I created a new PST file for this, then specified it in HTC Sync), then used GO Contact Sync Mod (sorry I can't post links yet) to sync it with my gmail account.
If you really wanted to leave as phone contacts, you could try Titanium Backup - but since your phone contacts are saved as system data it's a bad idea - so I'd recommend against it. If you're backing up your nandroid for ARHD, you could always try TiBu and let us know how it went - I think it was labeled Dialer Storage - filter to system data and just look through all the green-colored items for something that says "CONTACTS" or "PEOPLE".
However it takes quite a while to apply all the applications and settings I use after doing a full wipe. Do you need to do this when flashing a new version of JT over a previous one or is there an easy way of doing that? As I read in a lot of places that you should always do a full wipe and that titainum backup is not recomended?
Click to expand...
Click to collapse
+1 to what if4!ct0r said regarding wiping before flashing.
There will always be some system settings that you will have to re-enter manually if you customize them a lot even when updating builds of the same ROM (probably because these are the system items that you shouldn't be restoring). These will depend on the ROM, but for me and JellyTime, the ones I had to redo were developer, lock screen, system/status bar, sound, display, language, as well as ringtone/sound notifications for alarms, messaging and calendar. Also you'll have to manually set up your widgets again - typically ones that require you to configure it as you place it.
As for TiBu not being recommended - personally I didn't have a problem with it when moving over to JellyTime. I actually purchased the Pro version just for this and for flashing new JellyTime builds. There are two things to consider when restoring via TiBu: 1) system data; and 2) app and app data.
System data: The main concern here is, when changing to a completely different ROM, do NOT restore any system data (unless you're aware whether it was updated in the new build or just experimenting). Even when you're updating to a new build of the same ROM, you should at least avoid restoring the red-coloured items and just stick to green and yellow items that may contain useful data such as contacts, sms, call logs, saved wifi access points, bookmarks, etc.
App and app data: I personally think it's ok to restore your apps themselves, but you could always record a list of what you had and download them manually again just to be safe - not a big deal unless you have over a hundred apps. When switching ROMs, try to avoid restoring the app's data unless you really wanted/needed it for certain apps - in that case, be conservative with what you choose. I'm not a programmer or developer, so I don't know how this would affect your system/app if switching to a ROM with a different Android version. Restoring app data between builds of the same ROM should be fine, as I've done it between all my JellyTime flashes with no issue even when it updated to Android 4.1.2.
Tip: after flashing the ROM, and doing your typical post-ROM-flash stuff (like fixing permissions, rebooting, wiping cache+dalvik, flashing Gapps, etc), and you've tested it and are happy with its stability, download TiBu again (or if you had the apk stored somewhere after you purchased it, just install it manually), boot to recovery and make a nandroid of the new ROM as it stands: nice and clean before any apps are installed. This way you've got a recovery option without having to go through the hassle of re-flashing the ROM build again, setting it up, etc if all you did was stuff up while experimenting with restoring data on TiBu.
As always, make a nandroid backup before flashing. As I mentioned, if you're initially happy with the ROM, I recommended also doing one after you flash while the system is fresh and clean. Sorry if this post is a bit wordy, but I thought more info would help, as it helped me in the past.
Skunkworx said:
So I am looking for a soloution ... to move my sms messages over.
Click to expand...
Click to collapse
if4ct0r said:
For moving SMS, I'd suggest this app...
Click to expand...
Click to collapse
+1 for SMS Backup & Restore; I also used it, but keep in mind AFAIK it doesn't save MMS. I also used Call Logs Backup & Restore, in case you're interested in backing this up too. But since I started using TiBu, I don't need either of these apps any more.

Maybe changing the digitizer could help asd
Sent from my Galaxy Nexus using xda app-developers app

Stuck in Bootloop & Unable to Access HBoot screen

Hi guys,
I've got a bit of a problem. My phone is stuck in a boot loop, which is a problem I've dealt with before, with help from these threads.
But this time I'm really stuck. I can't access the HBoot screen like I normally can, by holding down the volume up and power off buttons simultaneously.
I am using (racks memory) I think it's the War something mod of Cyanogen 7 I believe. I installed it 5 months ago and it's been working fine. This is not a new or recent install!
The phone does suffer from low memory issues a lot, as do all Wildfire S's. I have managed to get around that previously by moving apps to the SD card or linking to it or making user apps into system apps. I was in the middle of chatting on whatsapp when suddenly the phoned just blipped and died on me.. then it went into the boot loop. It's never happened before and my suspicion is that it ran out of memory or something.
I've tried removing the battery and leaving it out for some time, no luck. I've tried restarting without the SD card and Sim card. No luck. I've tried connecting it to my laptop... no luck. All the usual tricks just aren't working.
I have TiBu installed and my most recent back up was less than 4 weeks ago. I also did a Nandroid system backup a few months ago, so I should be able to restore ok, I just can't access the HBoot screen.
The other weird thing is, when I left the loading screen going round long enough, like in the time it would normally have booted.. suddenly the sound of my new emails popping up plays... and today, even tho it was on the load screen, it made clicking sounds like when I activate apps when my finger touched the screen. It's almost like the phone has started up as normal, but the load screen just won't go away and underneath it all is normal.
I've never had anything quite like this happen before and I've been without my phone for 3 days now, so came here in desperation for some inspiration! hehe.
I am probably going to buy a new HTC phone with a large system memory cos altho I dearly love my Wildfire S, the low memory has caused me nothing but problems since I first bought it, and I have wasted hours and hours on it, trying to get around the problems caused by it. But until then, I need to get my contacts and messages back and continue to use it for now. I would also ideally like to keep it going and give it to my sister perhaps who doesn't have a smart phone. She won't need as many apps as I do, so it would likely suit her, or maybe my Mum.
Any help anyone can give would be massively appreciated. Thanks guys!

Can't access HBoot!
Hey is anyone out there? I know lots of people get stuck in boot loops and there's a million threads of support for that, but this is different. I can't access the recovery system either. I have clockwork mod on it and normally you can get into that fine. Trying to find help on this problem is really tough cos I have to wade through all the noob threads for standard easy fix boot loops. If anyone could help me on this I'd be extremely grateful.

This might be all I can offer but two things come to mind. The first is you said volume up its volume down to get into the bootloader. The other is to search in the wildfire forum regarding whatsapp. Recently I read a post about a guy who's phone crashed from whatsapp. I don't remember how he recovered you have to search on it; unfortunately the second time he couldn't recover.
Good luck
Sent from my HTC_Amaze_4G using xda app-developers app

Thank you!
MiCeltic said:
This might be all I can offer but two things come to mind. The first is you said volume up its volume down to get into the bootloader. The other is to search in the wildfire forum regarding whatsapp. Recently I read a post about a guy who's phone crashed from whatsapp. I don't remember how he recovered you have to search on it; unfortunately the second time he couldn't recover.
Good luck
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
Thank you for this... I'm willing to grasp at any thread at the moment. I did try the volume down option too but no dice there... but the whatsapp thread sounds promising, so I'm going to follow that up right now. It's after 4am and I've been sitting here working on this for hours and hours and at my wits end, so thank you! Fingers crossed!

Accessed HBoot!
Update:
Ok, I couldn't find the thread about whatsapp that was referred to above, but I have just tried accessing the recovery menu, using the volume down and power key, after first removing the sim card, but leaving the sd card in place. Suddenly that seemed to work! The menu came up!
I tried accessing it again with the sim card back in, and it refuses to come up again as before. So that at least is one issue resolved.
Now I'm having trouble mounting my SD card, which it says can't be mounted. I know the backups and recovery files are on the the SD card, but it just doesn't seem to see them there.
I wiped the dalvik cache in case that was causing any problems and it doesn't seem to have resolved this current issue so far. I'm going to keep trying other options as see how I get on, but I least wanted to share the solution to one of the problems my thread raised.

Further Update
I couldn't remember the name of my mod in the first post.. it was the WildChild mod.
After getting my phone into HBoot by removing the sim but keeping the SD card in, I found I was unable to mount the SD card. I researched this problem and some suggest the card may be corrupted.
I have checked the card on an external reader plugged into my PC and it read perfectly fine, and I managed to copy every bit of data on it across to the computer with ease. Others however found that after a reformat it eliminated any problems with mounting.. so that is what I am going to do and then try and restore the copy of the data I saved to the PC back onto the SD card.
Attempting now to reboot normally with the sim back in and the SD card removed this time produced a very desirable result. My phone started back up, albeit without the normal operating system. I was able to connect to wi-fi and my network and see a missed call voice mail message symbol. There are however no apps at all as yet and no background screen. I should mention that the phone did ask me to allow SuperUser permissions again.. I should also mention that I foolishly tried to Fix Permissions in CWM which then sat for a long time, eventually I removed the battery cos I thought it wasn't gonna do anything.. this is a big no no I now find out from the threads and I may have buggered it up a bit. I don't know.
My saga continues anyhow, and although I've not had much support on this, it might still be helpful for others to read and follow should whatsapp crashed their phone too and mess with their SD card somehow.

Another Update - Making Progress!
Next update on this...
I removed the SD card and put it in an external reader again on my PC.
Then I installed the free program Mini Tool Partition Wizard Home Edition and selected MiniTool Partion Wizard rather than the Power Data Recovery.
The Wizard allowed me to see the hidden partition on my drive. I understand now why it has always had trouble reading and writing to the SD card in the Ext section that was hidden. This should have been an EXT-2 or EXT-4 format partition I think, and mine is an EXT-3.
Maybe I'm wrong, I don't know much about these things and just learn as I go and by experiementing.
I had hoped to back up the hidden data in the partition but I was unsuccessful. Instead I found the Rebuild MBR (Master Boot Record) option and applied that to the entire SD card.
I then put it back in my phone, again without the Sim, and went into HBoot and recovery. I then went to my advanced back up and restore section and now the SD card is mountable and readable! I didn't have to wipe it or reformat!
I found my most recent up date which was the end of August... I wish I'd done them monthly, but oh well not too bad... and selected it and chose to Restore Boot.
Once it had completed I tried to reboot, but no dice. I put the sim card back in.. still didn't work... BUT I was now able to get into recovery again, this time without removing the Sim!
So inching along slowly here with this but making progress.
Next I plan to restore boot again, this time with the Sim card in.. and try and restart.. if that fails, I will go back into advanced recovery and try to also Restore System, and lastly restore SD-ext and see if each of those options repairs whatever damage that stupid Whatsapp did to my phone! I hope the little solution to various problems I've had are of some use to someone else here. Now wish me luck!

Wow, you were busy last night while most of the western world slept . I'm guessing if I posted at 11:10 PM and you said it was 4:00 AM, that your in the London timeline. I thought a little bit more, later, and I think that person's post I read fixed his phone by eventually getting into recovery and restoring, which as I remember worked that one time, until he reinstalled and used Whatsapp again some time later (it was at the insistence of a girl that used it). Whatsapp has, like 300 million users, but it does seem to give some people serious problems, and that's why I think most people are hesitant to try and help. They don't want to make things worse, since there are those instances of totally bricking a phone...but as long as a person can get into recovery, it's not bricked!
Interesting...I have done the, "fix mbr" in PCs many times, but I think you've taken it to new levels using it in phones! At least I don't remember reading anything much about someone doing it (in phones) before and it's brilliant, IMHO. You really did a great job sharing what you've done and I hope you get it fixed. I clicked a, "Thanks" for a good post follow up.
Insert standard disclaimer here: I'm not telling you to do anything, or what will or won't work, but sooner or later you're gonna have to restore that backup, but it's your choice on what to do; and, it sure seems like you know what you're doing, especially having made a backup to work from. I can appreciate the way you've gone piece by piece in your restore efforts to try and find where the problem occurred. The nice thing about the Wild Child ROM is it all works, and incidentally I think the developer uses ext2 for his extended SD card partition! It sounds like you reformatted to ext2 or ext4 from ext3, so the only thing there now is what came from restoring that backup piece in Clockwork; therefore, there's nothing that would be lost that isn't already; and, you backed up everything else on the SD card. So I don't want you to brick your phone either, but I'm wondering about wiping the cache and then the dalvik-cache, and then restoring your whole Nandroid backup?! I think your Whatsapp contacts are saved and so if the phone boots to a working condition you could just uninstall Whatsapp right away, boot into recovery and wipe cache and dalvik-cache again just to be safe, and then decide what to do about using Whatsapp again. As long as you can get into recovery, ultimately you could wipe, wipe, wipe and reinstall Wild Child to start all over if nothing else works.
On the other hand maybe you've already got this whole mess straightened out, if not, I'll again wish you - Good luck!

Solved!
So I next wiped the cache partition 3 times, as someone on another thread said sometimes it takes more than one go to clear it all properly for some reason.
I also wiped the dalvik cache again a couple more times. Then I went back to my back up and restored system. Then I tried to boot my baby back up.
I was falling asleep at this time but I remember the phone partially recovered. But most of the apps were broken. I had low memory issues too, so I uninstalled a few apps, managed to restore some individual apps or update them, and log in long enough to send messages to contacts with my email so I wouldn't lose them.
Then I fell asleep with the phone in my hand haha.. when I woke up I immediately continued with it and finally worked my way back to whatsapp being the last app I wanted to deal with. I managed to get into it and send some messages.
Then I did a full nandroid restore on everything.
The phone returned to it's state as of 2 months ago when I last did a nandroid back up. But some of my TiBu apps were backed up more recently. So I manually restored those and things were mostly back to how they were before and I am fairly happy with the low loss of data.
Whatsapp was working fine for a while.. but then it started having problems. It first had all my contacts there... then it lost their names but kept their numbers, then it lost all the old messages and right now I'm in the middle of trying to restore everything again and it's stuck on a restoration. I did a full uninstall of the app, restored the back-up, then it tried to update, but it always fails and now it's just hanging. So it definitely appears that whatsapp is one of the major causes of problems on my phone.
It was also one of the largest apps I had on there. Wildchild is an awesome rom, it only lacked video really and I installed a codec and player for that and got it working again, despite the guys on the Wildchild thread saying they didn't think it was possible. Yes I had trouble with it sometimes, but most of my trouble stems back to the low memory issues and the fact I broke all my apps up by spreading parts of them over the SD card, internal storage as user apps and system memory. That's a Wildfire S problem, not the fault of the Rom.
Anyway, I've made note of all the important numbers and will be buying a larger capacity HTC phone this week. Not sure which yet, but possibly a Sensation or Sensation XE, depending on my budget.
Thanks for your support MiCeltic. Yes I'm in London hehe. And I hadn't read anything about using MBR on a phone, but it was the SD card which had the problem and that certainly fixed it without having to wipe all my data.
I think what I have here is multiple layers of problems.. and I'm really pleased that after 3 days effort I managed to get past most of them. Once I get my new phone and transfer the contacts, I will have to think twice about using whatsapp.. it's my favourite app of all tho, so it will be hard to part with. This phone has many bugs.. I will completely erase it and reflash it when I get time and either keep it as a back up and maybe gift it to my sister or mum as I said before.
:good:

Last update
OK this is my past update on this... Whatsapp had one last surprise in store for me.
After it started messing up my phone again. I gave it one last chance. I completely removed it from the phone and installed it as new from the GooglePlay store. Then when I loaded it, it found the backed up Titanium BackUp messages and restored those.. then when I opened the app, it also had restored all my most recent messages, up to the day before it crashed the whole phone. I was amazed. They must have been stored on the server or something.. I think they sit there for 3 weeks. So I'm likely only missing one weeks worth of messages at most, about 4 weeks ago! Ha! Brilliant. I'm not doing a Nandroid backup cos everything is stable again and I hope to have no more troubles until it comes time to transfer all the date to the new handset... that's gonna take a while cos I will have to learn how to gain the boot mod rights all over again and maybe even flash a custom rom as the stock is sure to be loaded with bloatware. Still.. if it has a 1GB internal memory it shouldn't slow the phone down too much.. not compared to the tiny 150MB this little baby has!
If someone wants to close this thread now, feel free.
Cheers. :good:

You inspired me to read a little more last night and I did see where some people found a fix by uninstalling and then installing new (not from backup), then restoring their contacts. Seems like you've proved that point! Interestingly I read that ALL of your contacts are stored on the Whatsapp server, not just your contacts that have Whatsapp (Remember those permissions you accept when you install an app!). As I said, there are 300 million users, obviously not everyone has the problems, so hopefully it will work for you now and on your new phone, which after reading your posts I know you will make a back up of immediately and again after rooting...AND definitely before installing Whatsapp ! ! ! You might even find your next phone easier to root as a lot of them don't need an update of the bootloader on htcdev for the first step when unlocking and/or many can gain Soff!
Glad you got it working and now all's right with the world...well for now

N5 sorta stuck in bootloop. Looking for help on backup and remedy!

Hey there guys!
So I'm having a bit of a situation with my Nexus 5. It is a first production run as I ordered it the hour it came out.
Today it started having HUGE issues. This is a few days after I downloaded Marshmallow 6.0. The device would shut down and then go into a boot loop for HOURS. Sometimes it'd start back up fine and be usable for a few minutes, but then shutting down and becoming unusable. Sometimes it'd start up and the "Optimizing Apps" screen would come up as if I had just made an Android upgrade, and it would complete after some minutes and become usable until it restarted again.
The phone "seems to be working" now OK. This thread is gonna be a bit multi-faceted, so sorry for asking so much :/ Just having a situation with my phone I want to remedy.
First, I'm looking for a good unrooted backup program I can use to backup the stuff on my phone to my computer or somewhere else. I want it in case I get the phone working again or I get a new android and want to transfer stuff over. Is it possible to move data from one backup to a new phone? Not sure. Either way, just looking for a good backup program I can use, if anyone can recommend me one.
Second, besides the obvious possibility of Marshmallow messing my phone up, a lot of people say it could have to do with a "stuck internal power button" and that "smacking the phone against a hard surface near the camera" could help. This seems mega sketchy, but at this point Im willing to do it after a backup. Does this solution have any merit or is it, as we say, "bulls***"?
Third, is there any possible way to remedy a bootloop software-side?
Thank you!

Since you are talking about downloading 6.0, and don't mention the N5X, I'm assuming you are in the wrong forum
That said:
You can run backups with adb (search for "adb backup"), without root. Just need adb debugging turned on in Android. This will also let you restore apps.
I've always used Titanium or a custom recovery myself, so I'm not familiar with the whole process.
I think you can clear the cache in the stock recovery too - might help? Fastboot & TWRP would offer more options, of course.
No idea on the stuck button theory - hopefully mods move this over so N5 veterans can you help out.

Thanks for the help!
To be perfectly honest, I didn't even know a Nexus 5X existed until now :$ Sorry for posting in the wrong forum, thought the X just stood for some production run number. My bad!