yashsingh1/xdaforums huggingface dataset:
[HTC EVO 3D] zozeus:
Hello and thanks for reading. I have been working on my girlfriend's phone for the past 3 days or so. We both have evo 3d, mine is rooted, I've had to do the radio fix so I have some experience with the open development/fix world. However hers was stock before the problem. I'm not sure how her phone got the way it did, if it was auto updated or she did or she let someone else look at it. When we got them, they both had hboot 1.4 on them, she just didn't want hers messed with so I left it stock.

Anyways here was the state when I started working on it:

Would boot to HTC splash screen and restart and repeat. I was able to go into fastboot it showed hboot 1.58 s-on. Ruu 2.89.

What I've tried done.

I tried reflashing the stock 2.89 and it would say successfully updated - no change in boot loop

I've tried unlocking and putting on recoveries 4xt, cwm, stock - same problem, could not go into recovery

Tried installing earlier ruu's but it wouldn't allow since they're older.

Tried downgrading hboot using bricking during update method. - successfully went to 1.4.

Tried flashing ruu 1.13, but it was still saying main version was 2.89 and couldn't since it was older.

Tried flashing other ruu's - same problem

Still has boot loop problem.

I read that hboot 1.58 might take 2 consecutive brickings to be able to set mainver lower, but doing that it still has 2.89 and says version error while flashing.

I've tried doing the ruu flashing using both the .exe in windows and from sd in fastboot, same problem.

I've bricked it 6 times in a row and twice when bricking, the ultimate recovery tool 3.0 from live cd won't recognize it so i've used emmc recovery in linux to fix part 13.

Current status:

boot loop problem with fastboot access.

ruu 2.89

hboot 1.40 s-on

fails to load recovery

Does anyone have any suggestions on where to go from here? Need any more info just let me know. Thanks again. I love these forums and have been coming here a long time. Just never really needed anything I couldn't find or knew how to help so just signed up today.
[HTC EVO 3D] gentrithumolli:
I've had that problem with recovery mode too , try to flash via adb another custom recovery i think it will fix that problem

send from EVO 3D Sense 4.1
[HTC EVO 3D] zozeus:
Oh yeah I forgot to mention I haven't been able to unlock since I downgraded to hboot 1.4. I get this message now:

c:\adb>fastboot oem get_identifier_token

...

(bootloader) [ERR] Command error !!!

OKAY [ 0.009s]

finished. total time: 0.009s

I noticed the ultimate recovery tool was updating misc.img in part 33, so I manually did it for 34, which worked and I was able to flash ruu 1.13. However, still boot loops.
[HTC EVO 3D] jaredl45600:
how did you go from 1.58 to 1.40 with s-on?

sounds like you need to ruu again, htcdev unlock and s-off using the wire trick. after that you can install the jbear 1.50. that was my method and i have no issues.
[HTC EVO 3D] zozeus:
I used the bricking method to go into emmc mode and downgraded hboot. I'll try running ruu again after work today. I was under the impression the wire trick requires phone to be in usb debugging mode which since I'm stuck in boot loop I can't enable.
[HTC EVO 3D] zozeus:
Ok I've ran ruu 1.13 again and it says installed successfully. However, still boot loops, fails to load recovery, and I can't unlock.

Ran ruu 2.08 successfully, which upgrades to hboot 1.5. Still boot loops, I CAN unlock/relock and have tried to load into stock, CWM, TWRP, and 4EXT recoveries and all fail to load.

Ran ruu 2.17 successfully, still hboot 1.5. Boot loops. CAN unlock/relock. recoveries fail to load.

Ran ruu 2.89 successfully, upgrades to hboot 1.58. Boot loops. CAN unlock/relock. Recoveries fail to load.

Does anyone know what the 34/35 partitions are? What would happen if I backed up all the ones from my working phone and flashed them on my girlfriend's this would be using the method in the htc unbricking guide by dexter? I'm wondering if there is a bad partition on her phone which is causing the trouble. I believe this is a possibility because the URT 3.0 which is supposed to automatically detect mainver partition was thinking it was 33 and I had to manually flash part 34. Sound reasonable?
[HTC EVO 3D] jcfunk:
Atless for me 2.89 had part 35 as misc, 34 was WiMAX. 2.17 part 33 was Wimax, and 34 misc. If you look back in thread for URT you can see post about issues I've had.

Also how are you booting into recovery, I would unlock and use fastboot command.

Fastboot boot "name of recovery.img file"

That's what we had to do before s-off

Sent from my DOWNGRADED EVO 3D
[HTC EVO 3D] Unknownforce:
You're missing a partition somewhere. Brick it and use URT to backup every partition and tell me the size of each partition. I can use that to tell you which one you're missing.

Are you comfortable with linux? You will want to back them up to a flash drive for use later...

You can probably skip partitions 1-18 because the hboot and radio seem to be in tact otherwise It would be a perma brick and not work anyways.

After we know which one you're missing we can take the backups you have and increment them by one from where the missing one is and I can probably provide you the one you're missing and then flash the missing one where it belongs. URT will work for all of this.

Sent from the spots between 4G coverage where I typically am
[HTC EVO 3D] zozeus:
Right now with 2.89 here are the partitions, it hangs up on 23-25 and I have to break out of program

(SIze in KB)

19 - 8191

20 - 16384

21 - 16384

22 - 16383

23 - Failed to backup

24 - failed

25 - failed

26 - 32

27 - 4096

28 - 4096

29 - 20480

30 - 4

31 - 256

32 - 16

33 - 1281

34 - 8191

35 - 1023
[HTC EVO 3D] Unknownforce:
It doesn't hang, it just won't get the whole thing cause it's so big and emmc mode shuts off after 5 seconds so it doesn't get enough time to get it all. (These are data, system and cache, we don't need these for our purpose here)

However, I don't see a problem with these.... None are missing. How it's detecting at 34 makes no sense, because you have a 35, which is the exact size of misc and all the others line up with what they should be... can you zip up and pm me the 34 image as you have pulled it above? I want to see how it's possible that it's seeing that as a misc partition... because it most definitely should not.
[HTC EVO 3D] zozeus:
I wasn't sure how to send attachment so I sent you link to file on dev-host. Not sure if you got it since I didn't check verify read or save in sent messages. Looking with HEX editor 34 looks the same as 35 except different version number. After downgrade with the two just go down a partition. Here is a screen shot with the two (34+35) before 1st downgrade on left and the two (33 + 34) after downgrade on right.View attachment 1818384
[HTC EVO 3D] zozeus:
I'm not able to boot into recovery. :( It boot loops for everything except going to fastboot.I'll double check the URT thread for what you had and see if it helps.
[HTC EVO 3D] Unknownforce:
Well I see why it thinks that's a misc partition now. It looks like someone used the old downgrade tool on this device. Which was hard coded to write to partition 34, but on the ICS update 34 is used for WiMax udata, which stores the WiMax MAC and all that, and 35 was the misc partition... So incidentally it now has "two" misc partitions.

Send me a picture of the inside of the back of the phone please, I need to rebuild this partition. This might fix it, it might not, I'm not sure how much the phone relies on this udata to be intact. But it will at least stop the tool from detecting it as a misc partition and fix at least this partition.

I'm going to have to look at the others to make sure none of the other ones are corrupt, but I'm at work right now, so it will not be easy to get anything done on it until later tonight.
[HTC EVO 3D] jcfunk:
You know that's funny, I didn't have an issue when I wrote misc part to my wimax part. it seem to fix it self cause my wimax works.
[HTC EVO 3D] Unknownforce:
Well, it most likely rebuilds itself when it boots to system or at some other point, and it might store the MAC somewhere else on top of this (I haven't looked into that specifically, but the device MEID is like this where it exists in more than just one partition) but since he can't boot, it isn't allowing it to do that rebuild.

But I just ran through all the files and did compares with some from my 3 devices and I did find another partition that is "different" than expected. So hopefully between the two here, we can get it booted.
[HTC EVO 3D] Joshcwiththee:
I've been trying the past few days to sucessfully run RUU 1.13. I'm trying to use the HBOOT downgrade Toolkit and I have bricked it up to 4 times and sucessfully recovered it into HBOOT 1.40. Whenever I try to run RUU 1.13 I get ERROR 140.

I originally got ERROR 131 and fixed that by 'fastboot oem writecid 11111111'. I ran RUU 1.13 after that and that's when I started getting ERROR 140. Bricked again and still got error message.

How did you sucessfully run the RUU? Did you use the wire trick to brick and then use toolkit to recover?

My Phone is also Bootloader 1.58 S-ON and I want to downgrade and S-OFF. Thanks for any help in advance.
[HTC EVO 3D] zozeus:
Before you run 1.13 make sure that the phone's version is that or lower.

fastboot getvar mainver

Also what partition is URT saying it found misc on?

You might need to look at it to make sure it's good.

To get mine working I got a copy of misc.img and put it on part 34(which may or may not be the one you need)

I think my case is kinda specialized in that some partitions got messed with somehow.
[HTC EVO 3D] Unknownforce:
I'm going to add another level of verification for the misc partition detection. This shouldn't affect a downgrade from scratch, but it looks like some that have used the old tool on 1.58 HBOOT and ICS ROM's are running into problems running the new tool after already running the old tool once before...

Another level of verification will only make the misc partition that much better. The file is small enough that another level of checking won't affect the speed of the tool enough to matter.

3.1 will be out later tonight to at least add this new check. I'm also going to try and get the LiveCD to work properly on a read-only media like a CD. (currently the radio fix does not work properly when booted via CD, but it does work from a USB Flash drive.)
[HTC EVO 3D] zozeus:
Update for everyone following, I found out the screen had been cracked and got replaced. Worked before minus obvious touch response issues and dead areas on screen. Boot loop after. So I'm going with the conclusion they missed something replacing the screen or whatever cracked the screen might have loosened something inside and it was just a matter of time before it quit working.
[Sony Xperia T, TL, TX, V] griffin_1:
Hello

A friend is looking to get a new phone and he doesn't want a big screen like you see now a days on phones like the galaxy s3/4 or other like that. His previous phone was a s2 and the screen size was ideal for him. So,since i can't find much phones with smaller screens and with at least a dual core processor on my carrier, i suggested the Xperia T because it seems to have a good camera and not a huge screen and he likes the phone.

However, i have been reading some complaints about battery life and i was wondering if it really is that bad and if there is anything else he should have in mind when buying it? Any bugs or negative aspects of the phone (but positive ones are welcomed also!) so just he knows what to expect from the phone or if he should look for other one instead.

Thanks
[Sony Xperia T, TL, TX, V] gregbradley:
Sounds a bit like asking a girl a out for friend in the playground.

Why can't your friend ask the question himself?

Sent from my star trek communicator

Sony Flagship device circa 2145
[Sony Xperia T, TL, TX, V] griffin_1:
Because he asked me to help me pick out a phone and he isn't familiar with xda and he doesn't use message boards to much, but since i do i thought i would ask here. I picked the xperia T because it seemed like it would fit all the requirements but wanted second opinions and to be sure before really recommend it and before he buys it.

Hope this answers your question and now hopefully someone will answer mine:D
[Sony Xperia T, TL, TX, V] emuX:
Well Xperia T has 4.6 inch screen so if your friend doesn't like the big screens of the S3 (4.8 inch) then he probably won't want the T either!

I only suffer bad battery life when I've been using the Walkman app (and then media server seems to use loads of battery) and I fix that by killing all apps after using it with ES Task Manager.

Camera is epic and has got lots better with the Jelly Bean ROM.

I could go on but there are already plenty of threads about this - use the search facility!
[Sony Xperia T, TL, TX, V] griffin_1:
Thanks for the reply.

The 4.55" screen was the smallest i found with still decent specs in my carrier and then the camera does seems great. My main concern was anything else besides the battery that could be an issue that i have missed while searching.

He liked the phone from what he saw from the specs and pictures, but we will go to a store to see the floor models because its always different than just look at the pictures.
[Sony Xperia T, TL, TX, V] Arcano:
Size was also a concern for me, coming from the 3'7 screen of an HTC Desire, and it was also one of the main reasons I picked the Xperia T: smaller screen compared to similar phones.

The only issues I've seen reported are a few who suffered the back peeling off, and a few with a dead phone after a few days. Those problems seem to have affected only a certain batch or batches that are no longer on sale, since those reports have faded away.

All in all, it is a nice phone, and I'm very satisfied with it.

EDIT: Oh, make sure your friend doesn't NEED a notification led, because that is a weak point.
[Sony Xperia T, TL, TX, V] gregbradley:
Ok, well setting as your friend had already said he liked the Xperia t I would also recommend it to him

Sent from my star trek communicator

Sony Flagship device circa 2145
[Xperia Play Q&A, Help & Troubleshooting] UndisputedGuy:
Now this might sound like a stupid question, but I'm none the wiser at the moment.

I followed the steps for this tutorial:

http://xdaforums.com/showthread.php?t=2161135

but now i want to revert back to Doomkernel V14 for GB. However, upon flashing the kernel, my ROM doesn't seem to boot. What do I need to do?

I'm guessing i need to flash the previous ftf files but I'm not sure.

In essence, i want to revert back to they way i was before i followed the tutorial :)

I was running NXT on DoomKernel with fully working touchpads etc.

Thanks

It's nice to be important, but it's more important to be nice.
[Xperia Play Q&A, Help & Troubleshooting] abdel12345:
Flash the ftf necessary for that rom. Then flash the kernel. After flashing doomkernel wipe data cache and dalvik. Then either restore a backup if you have one or reinstall it.
[Xperia Play Q&A, Help & Troubleshooting] UndisputedGuy:
Thanks for the help

It's nice to be important, but it's more important to be nice.
[Xperia Play Q&A, Help & Troubleshooting] fritzbored:
yes you need to flash the previous ftf for this as the ftf used for running doomlords version for ICS/JB is different from the one that is made specifically for gingerbread which doomlord has worked on the v14:)
[Xperia Play Q&A, Help & Troubleshooting] UndisputedGuy:
Doing that will erase my data and lose root, right? I can't seem to make a proper CWM backup with turbokernel. There was an error, then when I rebooted, things just went wrong to put it simply

It's nice to be important, but it's more important to be nice.
[Xperia Play Q&A, Help & Troubleshooting] fritzbored:
yes you will loose root and superuser control, mind if i ask what model is your play is it r800i? because if so doomlods easy root kit can easily solve that issue with CWM.
[Xperia Play Q&A, Help & Troubleshooting] UndisputedGuy:
It is indeed an R800i, Thanks :)

It's nice to be important, but it's more important to be nice.
[Xperia Play Q&A, Help & Troubleshooting] UndisputedGuy:
Where can I find Doomlords kit? I don't believe I've seen it before so don't know how it'd solve these issues

It's nice to be important, but it's more important to be nice.
[Xperia Play Q&A, Help & Troubleshooting] fritzbored:
http://xdaforums.com/showthread.php?t=1312859 remember this can be used by ftf lower than .58
[Xperia Play Q&A, Help & Troubleshooting] UndisputedGuy:
Thank you! Hopefully I'm able to make a backup with CWM with my current settings. If not, I do have a previous backup. Thanks again

It's nice to be important, but it's more important to be nice.
[Samsung Galaxy Nexus] 93fuelslut:
i used rom tool box to download the latest twrp...

how do i install it now?
[Samsung Galaxy Nexus] infinit22:
Download goo.manager an it will do it for you.
[Samsung Galaxy Nexus] 93fuelslut:
i suppose il have to reflash my rom and gapps on the new twrp to fix my doubles of gallery pics and music songs??

and this means starting all over after i reflash my rom?
[Samsung Galaxy Nexus] pr0xyw0rm:
Yes. You need to install/set up/adjust everything again after you do a full wipe and re-install a ROM. No need to re-flash recovery again, it will survive the wipe :D
[Android Q&A, Help & Troubleshooting] erdal67:
Hey everyone,

Can someone help me please

i made a port from a Samsung GALAXY Mini to my HTC Wildfire a3333 but it won't boot

i used this guide: http://xdaforums.com/showthread.php?t=1908008

logcat in attachments

Thanks in Advance:fingers-crossed:
[Galaxy S III Mini Q&A, Help & Troubleshooting] giociampa:
My old (HTC) phone used the controls on the headphone cable to move between tracks, instead of change volume.

I have to admit I prefer things that way - so would like to know if there's any way to change the behaviour on my Mini.

Any suggestions (apps, mods to flash, etc) appreciated
[Galaxy S III Mini Q&A, Help & Troubleshooting] ppero196:
Tried holding the buttons?

I had those also on my previous phone (Motorola) and it worked by long pressing those buttons.
[Galaxy S III Mini Q&A, Help & Troubleshooting] dariolob:
Take a look at my thread here, there's a "press volume keys to skip tracks mod" and there's a chance it could also work with your headphones control :) http://xdaforums.com/showthread.php?p=39282702#post39282702
[Galaxy S III Mini Q&A, Help & Troubleshooting] giociampa:
Thanks for the suggestion - but no joy I'm sorry to say :(

Will take a look :D
[Galaxy S III Mini Q&A, Help & Troubleshooting] das.dian24:
just got this function..all i did was download N7player on market and in advanced settings there is an option allowing you to skip tracks by pressing the app start button twice on the headset..
[Galaxy S III Mini Q&A, Help & Troubleshooting] giociampa:
No joy again i'm afraid - thanks anyway :)
[Galaxy S III Mini Q&A, Help & Troubleshooting] giociampa:
Looks like that works in Doubletwist too - thanks! :D
[Galaxy Note GT-N7000 General] jakethesnakeuk:
For those of you who are looking for decent security software, avg pro worth 6.65£ is available for free on Samsung apps.
[Galaxy Note GT-N7000 General] kof200440:
Can't find it :(
[Galaxy Note GT-N7000 General] cgjones:
I thought Android was a secure system anyway. What benefit would AVG give?
[Galaxy Note GT-N7000 General] fpjteng:
Checked. Not free.
[Galaxy Note GT-N7000 General] jakethesnakeuk:
Yes it is free, and it is still there
[Galaxy Note GT-N7000 General] Braxos:
UK Only! maybe?
[Galaxy Note GT-N7000 General] jakethesnakeuk:
Probably UK only
[Galaxy Note GT-N7000 General] kyleastley:
Installed fine I'm in uk seems ok just don't I ow if there is any real benefits to it apart from if you lose you phone you can remotely wipe it ect.
[T-Mobile Samsung Galaxy S II SGH-T989] r_david562:
I want to do some public pranks, but I don't know what mic to get. Since my Galaxy S2 is the only audio recorder I have. My limit is about $50.
[T-Mobile Samsung Galaxy S II SGH-T989] rafaelrfq:
Try Jabra

Hello. Well my friend... I have tried recording with my Jabra headset and it works pretty well. Bought it from amazon about a year ago and it's still holding up just fine.

Link: http://www.amazon.com/Jabra-EASYGO-...23487&sr=8-3&keywords=jabra+bluetooth+headset

If you want to use the headset as a voice recorder you'll need an app called Bluetooth Recorder Lite.

Link: https://play.google.com/store/apps/details?id=bluetooth.recorder&hl=es

It's not the best app but oh well... There aren't too many free options right now.

If you really are into that I recommend Easy Voice Recorder Pro. It costs around 4 dollars right now and it has bluetooth support.

Link: https://play.google.com/store/apps/details?id=com.digipom.easyvoicerecorder.pro

Hope I helped :good:
[Verizon Samsung Galaxy S III] RogerSC:
I usually take about an hour walk on Sunday, along the ocean, where there isn't great 3G/4G coverage, and listen to internet radio stations. Last time, before flashing my S3 with CleanROM 6 r2 and the modem and rpm.zip, I was pretty annoyed with the radio in my S3, lots of cutting out and dead air. This time, after flashing, the internet radio station stayed on for essentially my whole walk, first time for that. I assume that this was the modem.zip that helped out.

Just thought I'd share, since this made me happy *smile*. Thanks to all that have worked on this software, it is serving me well.
[Verizon Samsung Galaxy S III] jasondhsd:
ERM where is it?
[Verizon Samsung Galaxy S III] corbn89:
It's just the newest mb1 radio from Samsung. You can find it in the modem/radio thread in the dev section.

It's not really Rom specific. Should work on whatever your running as long as it's jelly bean.
[Verizon Samsung Galaxy S III] kendive:
You mean this one

VRBMB1.modem.zip

http://www.androidfilehost.com/?fid=9390345248346996854
[Verizon Samsung Galaxy S III] corbn89:
Would have to compare md5 to verify the actual file you linked to but here's where I get mine. Should be the same though

http://xdaforums.com/showthread.php?t=1788313
[Verizon Samsung Galaxy S III] kendive:
Yea I am flashing now and trying it out... I have been having issues with this SIII and signal and service...

I can have two bars and 3g and try to send a text and it will tell me can't send because of service in certain areas and same area the RAZR MAXX has no issues.

If this don't work. I can see me with a HTC DNA real soon.

My RAZR MAXX blows this SIII away with call quality and Verizon service.
[Verizon Samsung Galaxy S III] kendive:
Well I flashed the new CleanROM 6 R2 and the updated modem and rpm I535VRBMB1

and still same signal issues. No way did this improve service.

Don't get me wrong this is a great ROM I just think the SIII is not a good phone.

I think I will order me a HTC DNA soon and sell this SIII.

I want a droid that works. I never had this issue until the SIII and I still have my Nexus and the RAZR Maxx and they work with no issues.

What gives with the SIII. Read the reviews on Amazon I guess I am not the only one with issues.
[Verizon Samsung Galaxy S III] RogerSC:
Like reviews of most products that sell well, there is a spectrum of user opinions. Amazon shows this phone with 4-stars with a lot of reviews, which is pretty good. The HTC DNA has slightly higher rating (4.4-stars), but many fewer reviewers. I find that as the number of people rating something goes up, the overall rating often tends to go down (unless what's being rated is a real dog). Also, the S3 radios were comparable to the iPhone 4 that I had before it, and now are somewhat better for me than the iPhone with the latest software.

I hope that your DNA is all that you want it to be *smile*. I think I'll be sticking with the S3 at least for the length of my Verizon contract. I like it, and am enjoying the ROM that I flashed as well. I didn't really want to root my phone in the first place, but it was the only way that I could get a decent full backup. Now that I'm using it with a sort of de-bloated stock ROM, I'm enjoying that even more.