Hey everyone, I'm VERY new to this forum. I have no idea if this post belongs here, so if it doesn't please forgive me. I have spent a lot of time "ghosting" this forum for advice as well as tips and I can't seem to find any threads specifically tethered to my questions.
First off, I'm not even sure I should be posting here because I'm unsure on whether or not questions about the FUZE should be in the Raphael section. I know it's the same phone but I couldn't find one specifically for the FUZE.
Anyway, I'm having a couple problems (mainly with the new rom 5.11 from the htc website.)
The first and formost, I hate the new messaging style they have. I carry my phone in my pocket, and I hate how my phone wakes up every time I get a text message. My screen keeps getting touched after I get a text and ends up pressing things I don't want it to. Also, it used to be that if you kept a convo opened, all the texts you received would count as read. Not the case anymore. I now have to open and close the conversation once for each message I received. 10 messages means opening and closing 10 times. That's ridiculous...I don't want to have to spend a lot of time getting my phone to register I read the texts. My last problem with the messaging, is I used to be able to open the keyboard, and start typing, not worrying about trying o find the last message I received. Unfortunately, now I have to scroll all the way down to read the message, and I have to click the entry box to type. The last one isn't really that big of a problem, it's just more of an inconvience.
The next problem I'm having is my phone likes to use WAY too much battery to do anything. Even when I have no programs running in the task manager, my usage is at 48% (give or take 2%). I know I read somewhere on XDA about a rom that uses 25%, and starts up quickly, but I have no idea where I read that.
I'm not looking for people to just hand me answers or programs or anything like that, but if you guys can just link me to the thread containing where I could possibly find what I'm looking for. Any help would be greatly appreciated.
Thanks in advance guys, Nitro
Hey Nitro i'm going to try and answer your questions (since im still somewhat new im not sure ill be 100% right but ill try =D) ok so for the messaging thing. that is a rom specific thing i think. Becasue i am using a WinMo 6.5 rom and dont have that issue. As for the second thing im not sure if its a WinMo 6.1 problem but i kind of remeber it being a reason i switched to 6.5. Now for battery life you should go into the roms section and look for some kind of rom that says something about energy (usualy there is one in the top list). How ever most of the new rom's are on 6.5 so... you will have to either look far back in the pages or upgrade (and maby if your lucky there might be a 6.1 in the top list.) The energy rom's will also affect your ram usage but be warned it will have an impact on how fast your phone is. So you might have to do a bit of testing to see which ones are for you. Also when looking for the rom make sure it says for the fuze on that page if it is not you can still use it (however you will need to get a thing called keyboard switcher because its really funny when you are trying to send an email and press the @ on your keyboard and get the number 2 =P. Any way here is a link to the roms Link to roms
Thanks for the reply.
I had no idea WM 6.5 was even out...That's awesome. I'm gonna play around a bit with those roms to see if one is better...Thanks for your help
So today I found another big problem I have with the rom I have...I can no longer send a text to more then one person at a time...Why did they take that out?? I used to be able to send a message to a bunch of people, and it worked perfectly, but now it only registered the first person. I noe have to send the same message 15 times just so everyone gets it...Like seriously, As if the rom using 50% power isn't enough, let's make people take 10 minutes to do something that should take 30 seconds. I officially hate the software devs at HTC.
Just as a funny side note, it took me 4-5 min to write this message, and my battery went from 100% down to 92%...AWESOME! God I hate this.
Hello there
You may want to flash a new ROM and Radio to your phone. Its not a difficult task and you will like the results. I personally use NRG's ROM Here and love it.
The radio rom is really what conserves battery life. I matched the latest one on the radio page here to the rom i linked above ( Radio 1.14.25.35) . Its a good combination if you ask me. I see that you are just north of me in PA ( Im in Baltimore ) and also on ATT. To be honest you may have to play with radios until you find the balance between signal strength and battery. What works for me may work for you because we are in the same general area with the same cellular provider. My battery has been off charge for more than 2 hrs and im at 98% ( although ive been on my laptop for the most part).
As far as accidentally hitting buttons, I use a slide lock on my screen ( like the Iphone screen lock) so when it turns on, you have to use the slider to unlock it. This will not only lock your phone from accidental misdials and screen taps, but also it shuts the screen BACK OFF after a set number of seconds therefore conserving your battery !!!!!! This is the application I use . Download the VGA version.
If you need help, feel free to send me a PM here and Ill do my best
P.S.
This is the right place to make a post. A Fuze is a Raphael.
Hey guys, remember those who used Tenfar's custom Recovery to format and partition their internal SD? Remember how it damages the touch screen response on the bottom half inch of the screen? Mine is fixed!!
I don't know what it does, but that particular function damages the PDS file. I've received help from a person who cannot be named and my AT&T Atrix is 100% fixed. Touch screen works flawlessly again, no Wifi issues, no Bluetooth issues and System Updates work fine.
He is working on scrubbing my personal data (serials, etc) from the PDS file and I'll be able to share it with the entire community. But if there's a dev out there who can contact me specifically I can send both the damaged and corrected file right now. I need help figuring out how to apply these serials to a blank PDS file so others in the community can fix this problem as well.
Out of respect, I will not name the person who assisted me as it compromises their work security. They went out on a huge limb and graciously assisted me without any reason other than they're a kick ass person with a huge heart. I'm no programmer by any stretch, but if anyone could assist me I know that there's about a dozen others (maybe more) who really need help fixing this issue. Someone please PM me if they can help!!
i messed up mine too...
any chance to get any help/solution?
One thing you could do is diff the two files to see if they're different. I don't know what the file is either though. Can you ask him how he fixed it? Also can you run the program strings against it? One other thing, is this fixed on changed partitions our did you change them back to the default?
Sent from my MB860 using XDA App
currently i'm in the situation that i can only flash my device, as i cannot complete motosetup, i cannot access debug option so no adb.
i read that the partition with the pds file has been already found
100% mmcblk0p3 PDS.bin 2097152 Persistent Data Storage
(from the atris sbf thread)
would be great to know what is executed in the script of tenfar for the internal sd partitioning, but my knowledge ends here.
so i guess (i'm everything but a developer )
if could be possible to flash/restore that partition with the nvflash selective option
or integrate it in a generic sbf, or the second init will save us all or the gingerbread update...dunno
but i see we are many we touched the wrong button but i don't see any dev interested here or in the thread of tenfar's recovery
i read that psd contains unique infos like the imei so maybe none of the devs wants to release a potential cloning system...
really i don't know even if what im saying is correct
bongd said:
Hey guys, remember those who used Tenfar's custom Recovery to format and partition their internal SD? Remember how it damages the touch screen response on the bottom half inch of the screen? Mine is fixed!!
I don't know what it does, but that particular function damages the PDS file. I've received help from a person who cannot be named and my AT&T Atrix is 100% fixed. Touch screen works flawlessly again, no Wifi issues, no Bluetooth issues and System Updates work fine.
He is working on scrubbing my personal data (serials, etc) from the PDS file and I'll be able to share it with the entire community. But if there's a dev out there who can contact me specifically I can send both the damaged and corrected file right now. I need help figuring out how to apply these serials to a blank PDS file so others in the community can fix this problem as well.
Out of respect, I will not name the person who assisted me as it compromises their work security. They went out on a huge limb and graciously assisted me without any reason other than they're a kick ass person with a huge heart. I'm no programmer by any stretch, but if anyone could assist me I know that there's about a dozen others (maybe more) who really need help fixing this issue. Someone please PM me if they can help!!
Click to expand...
Click to collapse
I am willing to help. This should be relatively easy to do.
in android recovery touch screen works correctly till the bottom, menu/ok button too.
the problem is in the os i guess, but damn i cannot use adb (no debug), seems that neither the early usb+shell root works for me...i can only flash using rsd
and after flashing stock rom i'm stuck at the damned motosetup
maybe are useful infos for you
god knows how i'm desperate
edit i'm reading that for old motorola phones like v3 exist a flashbackup and a psd editor, used to unlock the phones but also to revive damaged ones. maybe...
I've got my original corrupt PDS at home as well as one which has been corrected from a legit developer (can't release any of their information due to work employment security concerns).
I guarantee that it has been 100% fixed though. Bluetooth works, Wifi works, cellular data works and I was even able to upgrade from 1.26 to the latest AT&T OTA update and root everything.
When I announced this no one gave a **** so I didn't make a fuss. I know there are still a few bros with this problem though. I sent my PDS files to another member and they're looking into it. Hopefully you guys can get this working for yourselves as well!
dear friend you are promising salvation with your words, but you're not helping too much...
you gave the phone to that developer, he told what/how he solve the problem?
i understand psd is based on personal imei, so your fixed one is not working on mine etc etc
the point is that possibly your friend as legit developers has access to software to create/flash psd to the atrix.
the question is would be possible to receive the same helping hand?
there is no support in my country for this phone, and i'm not a dev.
so the only chance for me and the rest of the halfbricked people is to get the tools and the tutorial how to from you/your friend.
do you think it is possible?
KeRmiT80 said:
dear friend you are promising salvation with your words, but you're not helping too much...
you gave the phone to that developer, he told what/how he solve the problem?
i understand psd is based on personal imei, so your fixed one is not working on mine etc etc
the point is that possibly your friend as legit developers has access to software to create/flash psd to the atrix.
the question is would be possible to receive the same helping hand?
there is no support in my country for this phone, and i'm not a dev.
so the only chance for me and the rest of the halfbricked people is to get the tools and the tutorial how to from you/your friend.
do you think it is possible?
Click to expand...
Click to collapse
Sorry, I'm not helping much? I'm NOT A DEV!!! I have no obligation to help anyone whatsoever. I lack the technical know-how to help anyone. Please don't ****ing test me.
I've begged every Atrix developer here for help - NO ONE helped other than Tenfar. And unfortunately his advice took me in a completely different direction. No one can point a finger at me for not trying my best. I was so desperate that I got another Atrix because mine was dead for over a month before it was revived.
meneomic has been working feverishly to get his Atrix working as he's encountered the same problem. I've sent him my original and damaged PDS, as well as the one which has been corrected. The strings are not in plain text format and when I viewed it in a Hex editor I found nothing useful. That's all I can do. If someone knows how to put the IMEI and other serial numbers into the fixed PDS they can write it to the appropriate block and this problem will be fixed. That's all that needs to be done... but that alludes me.
I realize there are some people who are upset that their Atrix's aren't working after messing around in the recovery menu, but I've done my best. I have literally stayed up for days working continuously on this. My wife nearly smashed both my Atrix's in frustration because of all the time I've invested in it. I've done what I could and unfortunately got no where.
/rant
bongd said:
Sorry, I'm not helping much? I'm NOT A DEV!!! I have no obligation to help anyone whatsoever. I lack the technical know-how to help anyone. Please don't ****ing test me.
I've begged every Atrix developer here for help - NO ONE helped other than Tenfar. And unfortunately his advice took me in a completely different direction. No one can point a finger at me for not trying my best. I was so desperate that I got another Atrix because mine was dead for over a month before it was revived.
meneomic has been working feverishly to get his Atrix working as he's encountered the same problem. I've sent him my original and damaged PDS, as well as the one which has been corrected. The strings are not in plain text format and when I viewed it in a Hex editor I found nothing useful. That's all I can do. If someone knows how to put the IMEI and other serial numbers into the fixed PDS they can write it to the appropriate block and this problem will be fixed. That's all that needs to be done... but that alludes me.
I realize there are some people who are upset that their Atrix's aren't working after messing around in the recovery menu, but I've done my best. I have literally stayed up for days working continuously on this. My wife nearly smashed both my Atrix's in frustration because of all the time I've invested in it. I've done what I could and unfortunately got no where.
/rant
Click to expand...
Click to collapse
Chill out buddy....
Atrix ~_~
tons of words but nothing useful guys
leaving the good manners debate aside for one moment...
bongd you say you have the 2 file corrupted and corrected, but someone had to flash somehow/somewhere into your phone. who? you or your friend? what did he use to manipulate? can you ask him or not?
second easy group of questions for every dev out there,
-not interested because no reward (for the moment)?
-not interested because impossible?
-not interested because xxxx?
i'm trying to understand please...
msd24200 said:
This forum has young people, even children on it and all tho I hope you guys get this fixed you have to watch the language!
Click to expand...
Click to collapse
KeRmiT80 said:
tons of words but nothing useful guys
leaving the good manners debate aside for one moment...
bongd you say you have the 2 file corrupted and corrected, but someone had to flash somehow/somewhere into your phone. who? you or your friend? what did he use to manipulate? can you ask him or not?
second easy group of questions for every dev out there,
-not interested because no reward (for the moment)?
-not interested because impossible?
-not interested because xxxx?
i'm trying to understand please...
Click to expand...
Click to collapse
I sent my broken file to dev, he fixed it and I flashed it.
There was no exchange of phones, nothing special done, etc. I just used the dd command to write the fixed PDS file. How it was fixed, I an uncertain. I've tried for days and days to no avail. This is what you guys will have to figure out. I've invested too much time and already have a fixed phone which was sold to a friend.
If anything from that phone is needed for whatever reason, it's been sold to a coworker and I can obtain it any time.
ok we are talking now
the question is how did you extract that file?
i don't have adb access because after partitioning my phone failed to boot and i had to flash stock rom. now i cannot pass the motoblursetup (no wifi-no data, i'm stuck there) so cannot enable debugging
KeRmiT80 said:
ok we are talking now
the question is how did you extract that file?
i don't have adb access because after partitioning my phone failed to boot and i had to flash stock rom. now i cannot pass the motoblursetup (no wifi-no data, i'm stuck there) so cannot enable debugging
Click to expand...
Click to collapse
Yes you can. To bypass the motoblur activation type this when you are on the select language screen
Fn,E,Fn,E,B,L,U,R,O,F,F
Hold the Menu button to get the keyboard to pop up. That should work.
This will allow you to get to Settings > Applications and enable USB Debugging. Just make sure not to click on the wrong icon because you can't close a program once it's opened because of the bottom portion of the screen not responding.
I had to battery pull about 500 trillion times doing different things to fix this.
If you write my PDS it will fix the screen, but of course the serials will all be incorrect. And I don't know what this could do so I'd not recommend it.
mmm my phone recognizes the menu button as the bottom of the visible screen so pressing menu results in selecting the emergency call, pressing search button moves me to "next", the home or back button in the middle bottom of the visible screen...
KeRmiT80 said:
mmm my phone recognizes the menu button as the bottom of the visible screen so pressing menu results in selecting the emergency call, pressing search button moves me to "next", the home or back button in the middle bottom of the visible screen...
Click to expand...
Click to collapse
Hold the menu button down until the keyboard pops up and give this a shot.
I'm positive you'll be able to.
Please stop the foul language. Thanks.
according to this thread http://forum.xda-developers.com/showthread.php?p=15026407
you just have to open adb shell and run
Code:
su
dd if=/dev/block/mmcblk0p3 of=/sdcard-ext/pds.img
anyone backed up this partition??
I need it badly
tan G said:
according to this thread http://forum.xda-developers.com/showthread.php?p=15026407
you just have to open adb shell and run
Code:
su
dd if=/dev/block/mmcblk0p3 of=/sdcard-ext/pds.img
anyone backed up this partition??
I need it badly
Click to expand...
Click to collapse
maybe you will find what you are searching about there: http://forum.xda-developers.com/showthread.php?t=1035228&page=4
gitbrew.org is down for now
http://dev.gitbrew.org/~dasmoover/android/atrix/atrix-devkit-fs.tar.gz
do you have this file on your computer?
Hi, hi. I don't recall if this is my first post or not, but my original intent was to post on the developer's forum. I then found out I couldn't. So I'll post here and include a couple of questions/comments I have.
1. Have you noticed that XDA looks like a really happy dude puking the first letter of the alphabet? (That's totally an aside, just getting it out of the way.)
2. Due to some ridiculousness, I now have two Cricket Zios. One of them is working, the other one not. I've had the old one for a few months now and all this time I've been wondering what the heck to do with it. To specify: It went nuts when I tried the update on it (it originally had 1.6) and the corporate store flashed it when I brought it to them. Now when you turn it on, it shows the Android android and tells you to touch it (with the disembodied hand appearing, moving over it, then disappearing, as it's supposed to), but it ignores all input. Have to pull out the battery to shut it off, even. I can then turn it on (so at least I know the End Call button works and I *think* I've tried some combinations that work) and go through the process all over again. The good thing is that I now have a spare battery (go, me). In reading all the threads where developers are unsure of certain things, like whether or not the trackball can light up and whatnot, I'm wondering if it might be worth it for me to take the damn thing apart and take detailed pictures. At the very least, people would be able to see chipsets, individual chips, connections, lights, etc. Does anyone think this would be worth the effort? And, of course, complete loss of the device, though possibly I could use parts in other projects. (The screen, for instance, might be cheap, but it'd be REAL handy used as a miniature second/third monitor like those Liliput monitors.)
3. As a Linux user that doesn't give a damn whether a Windows OS can communicate with my microSD card, is there a reason I should not just format the entire card to something better than fat32?
4. As we all know, the trackball input on the Zio sucks like the Spaceball 1. Could this be improved by replacing the ball itself? It feels cheap anyway and I'm wondering if I could, for instance, take the ball out of a MyTouch 3G and put it in my Zio.
The FCC already has detailed pictures of the zio available, so that would be a waste of a phone.
If your 2nd phone doesnt work, you can always send it to me as a guinea pig phone -- it _really_ would be helpful to have an extra phone to develop with (provided I could get it working -- no guarantees but I'd be willing to try for the following reasons)-- being as any release, mod or anything for that matter I wish to test for you guys has to be done on my main phone, which Im sure any tester could tell you, is a major pain in the ass. lol. So if you really wanna help the cause, that would help me greatly
As for formatting the SDcard -- dont. Your phone saves all data to FAT. The only thing you _may_ wish to do is partition 512Mb off as an ext3 and use link2SD to symlink ur apps to the ext partition.
As for the trackball -- you can try taking it out (if you have the right screwdriver for it), cleaning the contact points, and putting it back together -- that might make it respond better (as I have no problems with my trackball.).
Hope that helps.
~Cheers!
Thank you very much! And I'll totally donate to you the phone (I appreciate a lot of what you've done anyway). Would you mind getting it without the battery?
Don't mind at all -- it'll be plugged in 100% of the time.
Not home atm, but Send me a pm m8.
Sent from my Zio using XDA App
Nice! as an openZio user I thank you
@ SilasMortimer :
Any updates m8? Havent heard from you in a while.
Cheers.
Heya. Sorry I disappeared. I kind of forgot to come back. I think I need to change my settings so I get email notifications.
It'll be sent soon.
Hello,
I see in most of the guides I've read here on XDA that people mention that not all the ROMs are compatible with the devices and it depends in many factors, but most of the time, the information either it's not mentioned or it's confusing (for me at least)
Is there a guide of some type that I can read to learn about all this?
I want to be able to go and test as many of the ROMS around here and see wich one fits best for me, and I want to do it without bricking or semi-bricking my phone.
For example, this phone I have right now I bought it from another person and it was already been tempered with. How can I tell what has been done to the phone (without having to ask the last owner)?
Been going around all the forum but I only get more and more confused from all the comments I've read.
Thanks a lot for the pointers/help/tips or whatever you can help me with!
Well first lets go over what was done to your phone by the previous owner. To make this a little less confusing I want you to power off your phone and when you go to power back on, hold power and the volume down key. there will be info on the screen that comes up. put that info here and I will help you.
You know, I've been looking everywhere for a little while now.
I remember when the first root of the note8 was shown publically, and how they used a su binary left in a combination firmware to facilitate the use of the user mid debug level.
But what has never been explained, even when I ask some dev's, is how it was really implemented in the first place on the n950U.
That root method is now depricated, can some one point me to the specifics of the original Note8 root?
I would really like to continue on where others have left off, but I've found it tremendously hard to get any information to take on the task of continuing where others left off.
Can someone please, give me details. I'm really willing to work on rev 5 bootloaders if some dev's from the older process can give me a crash course or two to catch up please.