yashsingh1/xdaforums huggingface dataset:
[HTC 7 Pro] mapaz04:
I was thinking thesame thing... to an extent... You know how Microsoft was resetting devices as they were being unlocked? That is, once you synched with their server, your unlock would be gone...

When I first tried this it did not work... I gave up that day and came back to it yesterday... I have to say that the tweak was in my system for at least 24hrs... maybe there is something that has now bypassed this on MY particular account? I dont know...

Also: I just flashed a stock (Well not unlocked/tweaked/or anything) ROM and did a full factory reset, then I updated my PROFILE and PRL just to make sure that no settings were left on the phone from the previous flash. I then proceeded to flash the DFT ROM and all I had to do was the registry edit, when I went to the messaging... I sent the 161+ sms...

I dont know... Id have to say something flicked the switch... on one side or the other... Would you mind checking tomorrow throughout the day :confused: to see if this may be the issue...

If this is the issue, it makes sense why nobody had found it yet, they did the edit and did not let it get "registered" in their phone??? jejeje... Too many questions... jejeje
[HTC 7 Pro] dandrayan:
Interesting theory. I'll keep the setting on and try again tomorrow to see if there is any change. Thanks for the help!
[HTC 7 Pro] atm153:
Worked on my Ansar 8773 V1 install! Thanks! Only complaint I had with this phone up to now.
[HTC 7 Pro] mapaz04:
AWESOME!!! Glad it worked for you... :D
[HTC 7 Pro] atm153:
Yeah, I just wish I knew why it wasn't working for dandrayan. Not enough to flash DFT Freedom to my Arrive though :P
[HTC 7 Pro] houdini13:
Thanks Man. It worked for me without rebooting on dft. I made the change, and tried to send a 161 test to myself. It sent fine with no error and I received both texts within a minute. Thanks!
[HTC 7 Pro] leadpoizon:
Awesome work! Now to release a ROM. :D
[HTC 7 Pro] mapaz04:
Cant wait to see what you bring to the table man! Thanks again.
[HTC 7 Pro] spydc:
I'm using the Ansar v1 rom and this reg edit doesn't work for me. Does it depend on area? I'm in the north jersey. When I try to send a message to myself longer than 160+ characters, I either get no reply whatsoever or I get the following error "can't send message Try again".

Any suggestions? I tried rebooting.. updating prl.. updating network profile.. doesn't work for me.
[HTC 7 Pro] mapaz04:
when u get this msg...

1.) REBOOT the phone.

2.) Go back to sms and click retry... it should go but no response for a while...

3.) type new 161+ sms and send to yourself again.

Let me know.

EDIT: And I know you probably have tried this but just give it a shot again... Also, go back to the registry and re-edit the string, save again and click MENU then EXIT to leave the application. REBOOT and try to re-send
[HTC 7 Pro] leadpoizon:
I was able to reproduce this only once and with a few tries and only when texting myself. Do you have this working completely after this edit and are able to send others texts?
[HTC 7 Pro] mapaz04:
Been texting like crazy man...

Yep, ive been texting more now that the limit is gone... I dont have to worry about my limit being reached... So ive been sending multiple part messages to everyone... jejeje

Anyway, to be safe and to hold some proof (not that I need it... jejeje) here is a picture of my HTC Arrive (left) and my wife's Evo 3D (right). I sent a 3 part message and she received every one of the pieces... I made sure my phone had nothing on it (yes, reset it AGAIN... jejeje) as you can still see the RED accent color... jejeje...
[HTC 7 Pro] leadpoizon:
Cool, thanks. There must be some reason why I can't get it to work.

Time to find out why... Did you have to do that procedure after you reset the device to factory settings, or did you just do the registry change and that was it?
[HTC 7 Pro] mapaz04:
Just went to the REGISTRY and changed it... That was it. Didnt have to do the procedure after the first couple of times that I tried it... I do have to say that whe I try it I do it with a CLEAN INSTALL... I dont know if that is the difference in my success since I flash the ROM squeaky clean and do the edit from the beginning (since I have been testing didnt want something else to mess with this...)

Dont know what is the issue... Some people have reported to be working fine, others are having issues... hmmm... dunno what to say at this time...
[HTC 7 Pro] leadpoizon:
I wonder if this has to do with what plan people have... Like, I don't pay the $10 data charge. I wonder if that has anything to do with it.
[HTC 7 Pro] mapaz04:
Now, I did have issues at the beginning while trying to make this work... However, once it worked, it seems that it has not stopped working...

And I DO pay the $10 for data so... that MAY be something to look into... :eek:
[HTC 7 Pro] houdini13:
^It shouldn't have anything to do with the plan. FYI I'm on SEROP $40/month for unlimited text,pics,data, and any mobile to any mobile.
[HTC 7 Pro] mapaz04:
Well then THAT blows THAT theory out of the water... jejeje

I honestly can't say what the difference is between ur device and mine that would make that change work... Hate to ask but have U tried a factory reset or fresh flash and then applying the fix?.. Just a thought...

Sent from my HTC Arrive 8773 using Board Express
[HTC 7 Pro] leadpoizon:
Haha, darn. I have not gone to a factory ROM (of course), but I have reflashed Ansars and the DFT ROMs and tried this on both. I'll keep trying.
[HTC 7 Pro] mapaz04:
Do you just not get anything back? Or still getting the cannot send Message? when U send itself a message... Make sure to put the area code first... At least that's how I tried... Don't know... Just thinking... jejeje

Sent from my HTC Arrive 8773 using Board Express
[HTC 7 Pro] vaporE:
I think mapaz04 is not asking you to flash the factory ROM. He's asking you to hard reset. Remove the battery, hold vol down/up and then hold power button. Then follow the prompts to hard reset. I believe it's vol down, vol down.

Anxiously waiting cuz I don't actually want to hard reset my device and the steps aren't working for me. I'm in Seattle if it makes a diff.
[HTC 7 Pro] leadpoizon:
From a completely fresh ROM, I sent a 162 character text. The text sent with no error... and didn't come back to me. I should get the error within a couple of minutes according to you, but from past tries, I get a error after almost a half hour. During this time, none of my texts go through, whether they are within the 160 limit or not. Odd, eh?
[HTC 7 Pro] mapaz04:
Ok... Last thought... Sorta...

Ok, here is what I can say for certain:

I was on the ANSAR 8773 18L V1 release (April 16) when this finally worked for me and I was able to replicate it... Here is what I suggest:

Go to the GOLD_C thread and download the 18Language ROM. (I hate "RAPIDshare", should be called "SLOshare"... jejeje) If you need quicker downloads, go to the end of the thread, find my post with my SKYDRIVE link to download.

Flash the ROM and when it comes up do the edit and reboot your phone.

Test to see if it works...

Go to Settings - About - Reset Your Phone. Let the ROM do the factory reset for you and try it one last time.

If this does not work... I will try to dump my files off from my ROM and we can compare and see where the difference is... jejeje
[HTC 7 Pro] leadpoizon:
Thanks, just tried your instruction to the dot and it still doesn't seem to work. I'm really curious what on earth the difference is between your phone and my phone, lol.
[HTC 7 Pro] adihere:
WOW :eek::eek::eek: I just did the 1 step simple reg edit, sent the 160+ to myself and waited for the error message except i never got one BUT i recieved my message in 2 parts....weird but it WORKED :eek: instantly right off the bat W/O a reset required nor an error message...wahoo now im goin to test to other providers like friends iphone and see if it come thru as 1 message or what have you. Thanks again man!!!!

Oh and BTW im still on DFT rom

EDIT* Ok i tested to another provider (at&t) and it did split the message however i noticed it splitting just before the 160 mark, like it backs it up a character or 2 and breaks up the message but they did go come thru instantly like literally seconds after i hit send...my friends iphone bleeped twice, one right after another. So im good to go...can't believe it was just 1 freakin reg tweak from 0 to 1 that makes a world of difference...makes no sense why this is turned off or limited in the 1st place. Good job peeps...mad kudos to you all!!!
[HTC 7 Pro] turdsamich:
ok I have a bit of a problem I tried this on my DFT Gold C arrive and it didnt work. When I change the registry value and try to send the message it appears to go through but I never get a text back and I never get an error message and restarting otherwise just breaks text messsaging (and email too appaently).

Texting over 160 characters isnt at all essential to me but it would be nice to have, maybe ill give this another try after some more feedback.
[HTC 7 Pro] mapaz04:
Have you tried...

Have you tried just leaving the tweak on? Earlier I had a thought that possibly... POSSIBLY... there is a network setting that gets updated over time, so keep the edit turned on for at least a day or so and see if anything changes... Sorry I cant be of much help... I was able to do it with the steps I posted... But as you can attest, results may vary... jejeje
[HTC 7 Pro] turdsamich:
maybe Ill try leaving the tweak on overnight, I guess if by the time I wake up I dont either get an error message or my actual message sent back to my phone I will know that it isnt working.

Is that a logical way of thinking about it?

Id leave it for longer but Id rather not be stuck a full day (or longer) without texting (especially considering it seems to have broken email on my phone as well)
[HTC 7 Pro] mapaz04:
If you leave it enabled, it still kills your sms and e-mail? I thought it was only when you turned it back off... Sorry man, I dont know what is causing for some people to get it just with the Reg Edit and others having so much trouble getting to it... Let me know if anything changes on your end...
[HTC 7 Pro] turdsamich:
yeah, if I leave it on I get no email or text messages. I assume if everything was to work the way it is supposed to I would get the error message right away?
[HTC 7 Pro] mapaz04:
Ive never had to wait... if I got the message it was almost instant... I clicked SEND and the error came in within 5 seconds... I said a minute or two because results may vary but... Thats strange... just like Leadpoizon...

Where are you located? Maybe compare with him and we can lock down the issue... sorry you are having issues...
[HTC 7 Pro] leadpoizon:
I have the same issue. I can only imagine that it might be based on the area you are in. Just a wild shot in the dark. It could be that some of the towers have the updated network capability and some don't, which is why Sprint left this setting in. I mean, there MUST be a reason they put the setting in there to begin with. Try testing this in a different location/city. I will do the same.
[HTC 7 Pro] dandrayan:
I have kept the edit active for two days now, but I'm still not able to send texts over 160 characters. I did do a hard reset this weekend after installing a new 32GB memory card (successfully, I might add). My old HTC Touch Pro 2 didn't have this problem, but it might have been handled in software before sending to the towers. I'm at a loss as to why it's not letting my Arrive do this. :(
[HTC 7 Pro] killerkhatiby009:
Working fine on the DFT ROM didn't even have to reboot! Thanks a lot this bug wasn't horrible just really annoying glad its finally fixed!
[HTC 7 Pro] turdsamich:
I guess this is a reasonable explanation, I am planning on being out of town this weekend, so maybe I will try it then. I live in Bishopville, MD a very rural area so it would make sense that there isnt the most up to date technology in the towers. What is odd though, I believe that every phone I have had on Sprint other than this one had the automatic splitting of messages over 160 characters, even when other networks didnt have that feature.
[HTC 7 Pro] tdecision10:
Excellent work. This worked fine for me.

Now, has anyone figured out how to actually increase the volume when using earphones to talk? I've tried the registry chage to increase the numbers in the volume (30-40 & 10-20) but that didn't seem to actually increase the volume....just the numbers.

Just a link to a related thread would be great. I don't want to change the topic here. Thanks

-tdecision10
[HTC 7 Pro] haramzee:
Yes it works fine even without a reboot on my Arrive using Ansar's 8773 V1.

Huge thanks.
[HTC 7 Pro] leadpoizon:
Tower Issue

Ok, so I have now confirmed that the 160 character limit is dependent on the towers near you. I just tested texting while roaming on Verizon with the exact same setup as before. The tweak works. No wonder it wasn't working for me! It now makes sense why Sprint disabled this option!
[HTC 7 Pro] turdsamich:
Now, if you get it working off of one tower does that mean once the fix is in it will work on the tower it previously did not work at or will texting be broken?
[HTC 7 Pro] leadpoizon:
I don't think so, though I have yet to find out for sure. I will try this once I am home. It wouldn't make any sense at all if it now worked at the previously non-working towers, because it doesn't have anything to do with the phone and just with the Sprint network towers. I'll post back just in case.
[HTC 7 Pro] mapaz04:
hmmmm....

This puzzles me a bit because I had issues when I first did it too... Thats how I came up with this procedure... When I would try it would never send and give me a response so I could retry send... When it finally worked, it has not stopped working, even after flashing other roms...

I know that as of now is just speculation but if this is true... then why did I get errors at first and then no errors now? hmmm... This is interesting... I hope that once you have experienced success it maintains that from then on...

Its also weird being that other phones (O/S's) seem to send the multiple "thread" message just fine... Anyways, I'll also be waiting on this so I can update the first post...
[HTC 7 Pro] leadpoizon:
MY FINAL RESULTS:

This method is dependent on the towers near you, because of the following*:

Some Mobile Phone Operating Systems are designed to split up texts whens they are sent over the 160 character limit before they are sent to the network (even dumb phones can do this). Windows Phone does not seem to have this capability, it sends your message in its' entirety to the network and hopes that the network can sort it out into split texts. The problem is, not all Sprint towers seem to support this. For that reason, Sprint completely disabled the option to send a text over 160 characters.

When you know this method will work**:

1. Make the registry Edit (Reboots is not really needed, WP dynamically monitors the registry, it seems.)

2. Send yourself a text over the 160 characters. (It should allow you to after the registry edit.)

3. The text will give you an error either instantly or in a few minutes.

4. Reboot, if you want (just to be sure.). Then, resend the same text.

5. It will send without errors and you should receive the content back in more than one text. Done.

When you know this method will NOT work**:

1. Make the registry Edit (Reboots is not really needed, WP dynamically monitors the registry, it seems.)

2. Send yourself a text over the 160 characters. (It should allow you to after the registry edit.)

3. The text will not give you an error. After a LONG time (an hour or so, you will get the error.)

4. During the time between you sending the text and receiving the error, your MMS and SMS will be broken and you most likely will not receive or be able to send texts.

5. Reboot your phone and things should be back to normal. Change the registry back to default value to avoid making an accidental text over 160 characters. Go yell at MS and Sprint.

* Only speculation after my trials

** YMMV
[HTC 7 Pro] mapaz04:
Hope you dont mind, im adding this to the first post. Thanks man. that sucks though... again, I had issues at first and then they went away... maybe I was hitting an older tower at first??

Thanks for your help on this.
[HTC 7 Pro] houdini13:
seems everywhere I go has capable towers. No issues anywhere so far.
[HTC 7 Pro] leadpoizon:
Cool. Hopefully we can figure out a work-around for that issue as well.

Just to be clear: The issue is with towers near the person sending the text (You), not towers near people you are texting.
[HTC 7 Pro] purian23:
Thank you tons! This worked perfectly for me! One error, then rebooted and resent..went through and so far so good!!!!!
[HTC 7 Pro] starsoccer9:
Ofcourse I would be one of the ppl who is screwed.
[HTC 7 Pro] jaygriggs:
Im not having any luck either. I get an error message about 30-40 minutes later and ya texts seem spotty with the hack on, yahoo email too.

I'm in metro detroit if that matters, and I have the same results across town:confused:
[HTC 7 Pro] mapaz04:
Just a thought, have you guys changed the "CELLULAR" settings :confused: ?

Go to Settings> cellular> then change the Data roaming options to "ROAM" and the Network type to "AUTOMATIC" then do a reboot.

Then try to send your message again, if it doesnt work, then its ok, you have not lost anything... but if it works :eek: ... Worth a shot no???

Just a thought, we have already derrived that some SPRINT towers (near YOU the user) are partially or completely the problem so... maybe we can have it hit other towers if we have ROAMING enabled...

Post back and let us know... that way, we know if this works OR... we can scratch it off the list... jejeje :cool:
[HTC 7 Pro] jaygriggs:
settings

Those were my settings when I tried the hack. Has anyone tried baking that into a rom? I'm not a cooker but I wonder if that would have any positive effect. The thing that I can't let go with the towers, is that I remember reading a yr ago about a guy who got his Verizon trophy on the sprint network and the texts worked fine. It made me think instantly that it was a phone or rom issue not a sprint or wp7 issue.
[HTC 7 Pro] leadpoizon:
It's not a ROM issue. I had these settings settings cooked in while I tested them. I am quite sure that this is a tower issue, unless I am proven wrong. Check my post for details.
[HTC 7 Pro] starsoccer9:
No difference

I had them enabled while I did the hack and it doesnt seem to matter. Maybe trying to do that hack while airplane mode is on might affect it somehow?
[HTC 7 Pro] Central-GsM:
very nice thank you sir
[HTC 7 Pro] aqualls:
No go for me as well. But worth a shot.
[HTC 7 Pro] haramzee:
The good part is at least you tried, hopefully something will be done server/tower side to fix these issues, or WP will receive an update to split up the messages on its own before sending.
[HTC 7 Pro] sadffffff:
works great! Thanks!!
[HTC 7 Pro] mapaz04:
Also works on 7.8 roms

Due to the 7.8 ROMS available now (Leadpoizon and Sianto1997), I am proud to announce that this is also working on them too! I do have to state that it may still be dependent on the towers around you so test on a fresh install! :silly:
[Kindle Fire Q&A, Help & Troubleshooting] showmeaction:
I used KFU to root and install FireFireFire (first) then TWRP, after installing the latter, I noticed that the Android above the "Kindle Fire" logo was gone, is this normal. I apologize in advance if this is a repost.
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
Are you able to use the power button to enter recovery? If not, use fastboot to install FIREFIREFIRE.

fastboot -i 0x1949 flash bootloader u-boot.bin

"u-boot.bin" being the name of the version of FIREFIREFIRE you want installed. You must be in fastboot mode with both "fastboot" and "u-boot.bin" in your present working directory (dir).
[Kindle Fire Q&A, Help & Troubleshooting] mughalgxt:
consider the thread as stated making sure no steps were missed and if Rom boot fine into android OS no issues.

http://xdaforums.com/showthread.php?p=24129239
[Kindle Fire Q&A, Help & Troubleshooting] showmeaction:
I used the Kindle Fire Utility to install both TWRP and FireFireFire, I decided to install the "ReloadedRom", it went well until I took the device out of the charger after leaving it overnight. I noticed that half of the screen had pinstripes and the other half was fine. Another question, is how do I get into fastboot? I am familiar with installing roms and such, so I do have a decent background. Thanks in advance!
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
With FIREFIREFIRE installed you can enter the fastboot command (in your command prompt) with the device powered down. When it says <waiting for device> turn the device on and the command should run when FIREFIREFIRE goes into temporary fastboot mode.

Otherwise:

adb shell idme bootmode 4002

adb reboot

To change it back:

fastboot idme bootmode 4000

Be sure to <shift + right-click> on your KFU/tools folder and select run from command prompt to use fastboot
[Kindle Fire Q&A, Help & Troubleshooting] showmeaction:
I was able to get into fastboot, but what next? Also, what is wrong with the screen?
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
I tried the Reloaded rom today and it seems like the rom itself is the culprit. I was having the same kind of screen problems before I switched back to Hashcode's rom. There have been others here with the same exact problem and they all were using Reloaded.
[Kindle Fire Q&A, Help & Troubleshooting] mtnlion:
Update to hashcode's #7 kernel
[Nexus S Q&A, Help & Troubleshooting] kwudude:
<DELETED>
[Nexus S Q&A, Help & Troubleshooting] stealthychief:
No this has to be a Android Market related issue. Iv'e talked to a few developers and they are seeing the same. I first noticed this at about 8pm est and it still hasn't been changed. No word yet on what is being done or why...
[Nexus S Q&A, Help & Troubleshooting] Garoto1973:
I can report the same now I dont see any paid apps. I am on XWLP7 Galaxy S2 ICS 4.0.3. It was fine last night.
[HTC Rezound] carm01:
I have seen a lot of folks having all kind of strange issues with AR recovery after s-off. Myself included. Most notably:

1) No being able to mount the SD card getting error:

E: can't mount /dev/block/mmcblkp2 ( File exists )

2) unable to preform nandroid back up stating oops an error occurred, please check the log. well there is no log.

3) cant move the error log, gives another error.

After hours of trying to do everything under the sun, this is extremely frustrating; nothing works, but....

CWM touch. I can mount the SD card, and do nandroid back ups.

Is anyone else having issues with AR recovery?

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

SOLUTION FOR NANDROID backups and restores ONLY ( suggestion thanks to: a.mcdear & Mikej69 ; give credit where credit is due )

WARNING THIS WILL ERASE YOUR EXTERNAL SD MEMORY CARD

Some steps can be omitted since I have CWM touch installed.

**An important note about CWM: For the Rezound there is a charging bug. This bug prevents the phone from charging if you happen to let the battery die. This happened to me and sux big time.**

OPTION 1

1) boot to hboot usb mode

2) flash AR 3.15

2a) ( option from scotty1223 ) within AR choose wipe sd card

3) Reboot to your ROM

4) Navigate under SETTINGS -> SD and phone storage

5) Choose Unmount SD card

6) Choose Erase card

7) reboot into recovery and run your backups and restores; they should work

OPTION 2 usb mounting

Within AR recovery choose partition SD card with all default settings ( that resolved the error when mounting the SD card within AR recovery, however i cannot view the files on a PC when mounted in AR recovery still ). Others are claiming that it works, so i believe that, just me having issues.

If anyone needs AR 3.14, you can get it here

6/20/2012: below is a flashable via bootloader of the latest AR recovery 3.15