yashsingh1/xdaforums huggingface dataset:
[7" Kindle Fire HD Q&A, Help & Troubleshooting] JackRoberts1998:
Thanks for replying. No all it does is go to the normal logo for a couple of seconds, turns off and starts again.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] stunts513:
Odd, well u should just need a fastboot cable to fix since u can't get into twrp. Once you do that its just a simple matter of reflashing some images.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] mr_i_know:
My Kindle Fire 2 logo turns blue and bootloops non stop. I've tried everything I can find, but most forum help says I need my computer to recognize the device, which it won't. any ideas?
[7" Kindle Fire HD Q&A, Help & Troubleshooting] stunts513:
Try turning it on and holding volume up before the logo turns blue, it should go into twrp where you can use my tutorial to push a ROM onto the sdcard.
[AT&T, Rogers HTC One X, Telstra One XL] mhadonis:
hello.. FRiends

i have

htc one x(AT & T)

, i tried to install custom firmware but it bricked and it does not switches on.

Steps i followed:

1) rooted the phone

2) unlocked the boot loader

3)then tried to install custom firmware but got an error, so i googled... and found something called superCID

4) so i followed those steps, it included some token generation and image file generation

5) still i got an error with flashing the firmware and googled again and found to remove 1st line from a specific file... and i followed it

6) and again there was an error so i removed 2nd line which almost read like 1st line , and it gave me success dialogue..

7) then i clicked reboot.... AND the problem was here..:(. it did not rebooted and remained switched off (or something else).

Present Condition:

It does not switches on.

It does not charges.

It is detected by the pc.
[AT&T, Rogers HTC One X, Telstra One XL] immortalneo:
Did you know there is a dedicated forum for your device, which has many guides and tutorials as well as a Q & A Thread?

You can also check out these two threads there:

Frequently Asked Questions (AT&T, Rogers HTC One X, Telstra One XL)

{Answers} 2.20 Root Questions & Answers
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
What ROM were you trying to flash? What were the lines you removed? If they were safeguards against flashing something not meant for your device that was a huge mistake.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] mhadonis:
ROM: cm-10.1.2-endeavoru.zip

sry i dont remember well but started from "abstract" , and second line which i removed also started from "abstract"...
[AT&T, Rogers HTC One X, Telstra One XL] xxnatanxx:
That's a ROM for the international HTC one x not for north american one x.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Well you've bricked your phone by removing the safeguards that stop you from flashing a ROM not intended for your device. I have no idea why you did that.
[AT&T, Rogers HTC One X, Telstra One XL] mhadonis:
:good:thanks.... I was wrongly guided by the tutorial...

Is there any solution to the problem...???
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Your only solution now is to pay for a jtag repair (about $60) or pay HTC to replace the motherboard (about $200).

What tutorial told you to remove safeguards from the update script? I'd really like to know.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] redpoint73:
I'm not familiar with any tutorials that instruct what you mentioned (modifying lines of text). Can you link?

Also, improvising on the tutorial steps (modifying the 2nd line) means you weren't really following it anymore, opening all that much more risk. If you aren't extremely confidant in what you are doing, and willing to live with the consequences, making stuff up is not a good idea when modding phones.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
I'm willing to bet the tutorial does not exist, 99.99999% sure.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] 31ken31:
I've actually stumbled on a few you tube vids for other phones telling how to remove the device checks... Just wasn't gonna follow that sort of advice.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Thanks for clearing that up. I'd never follow that advice either, it's bound for tragedy. I'm still not sure why anyone would obtain their information from anywhere but XDA (unless linked by XDA). Places like YouTube just don't have the facility to differentiate between devices properly.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] redpoint73:
Completely agree. Unfortunately it seems increasingly common for folks to look for YouTube guides as a shortcut to proper learning and reading.
[AT&T, Rogers HTC One X, Telstra One XL] 31ken31:
To me learning is half the fun. And I've been doing this since my first Android.. T-Mobile G1
[AT&T, Rogers HTC One X, Telstra One XL] mhadonis:
trying unbrick....

i used below method but got stucked at step 15, but emmc_recover could not see my phone... i tried several times....

Unbrick process

11. Let's see if Linux sees the phone.

Code:

$ sudo dmesg | grep "qcserial"

You should see "Qualcomm USB modem converter detected" as the last line of the output. If not, you can unplug and replug the USB cable or run...

Code:

$ sudo modprobe qcserial

...to reload the driver.

12. Reset the driver, which removes any old block devices associated.

Code:

$ sudo modprobe -r qcserial

13. Now create the block device that emmc_recovery needs.

Code:

$ sudo mknod /dev/ttyUSB0 c 188 0

14. Emmc_recovery needs to know what disk to write to. An easy way to find this out is to run

Code:

$ ./getbrickdrive.sh

Which will tell you if it sees your bricked phone, and also give the proper disk. Mine was /dev/sdc and so I use that in the following instructions. Replace /dev/sdc* with /dev/sdb* or /dev/sdd* or whatever yours is.

15. Now we load the 1.12 HBoot (how exciting!)

Code:

$ sudo ./emmc_recover -f ./hboot_1.12.0000_signedbyaa.nb0 -d /dev/sdc12 -c 24576

You can hit enter at all of the prompts here. If it stalls at "Waiting for /dev/sdc12, hold the power button down on your phone for more than 30 seconds, then release it. 10 seconds or less after you do this, emmc_recovery will see your phone and proceed. Flashing Hboot will take several minutes, as it has to load data in ~23K chunks followed by a reset after each.

16. Once that is finished. We have to reset the qcserial driver again.

Code:

$ sudo modprobe -r qcserial

17. And then recreate the block device.

Code:

$ sudo mknod /dev/ttyUSB0 c 188 0

18. Now we restore our original block 4.

Code:

$ sudo ./emmc_recover -f ./bakp4 -d /dev/sdc4 -c 24576

Again, if it hangs, hold your phone's power button for more than 30 seconds then release. This file will flash very quickly (it's only 1K) and once it completes, you'll immediately notice that your chargin light turns back on.

19. Unplug your USB cable and hold the power button to hard reset the phone. In a few seconds you'll be greeted by the familiar HTC screen. Enter bootloader and check out your HBoot version. 1.12!

20. Look for some pandas to feed.

I['m sure someone will boil this process down even further or script it. Hopefully this lets folks willing to brave a Linux shell accomplish this now though.

ATTACHED FILES

File Type: zip	EVO4GLTE112DG.zip - [Click for QR Code] (895.8 KB, 554 views)

File Type: zip	bakp4.zip - [Click for QR Code] (263 Bytes, 511 views)

File Type: zip	getbrickdrive.zip - [Click for QR Code] (668 Bytes, 658 views)

link for this method

http://xdaforums.com/showpost.php?p=32761598&postcount=107
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Where did you find that unbrick method?

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] 31ken31:
On the evo forum I read through it before. Our device is actually really close to the evo
[AT&T, Rogers HTC One X, Telstra One XL] mhadonis:
same forum

i found the method on this forum....

link

http://xdaforums.com/showpost.php?p=32761598&postcount=107
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Yeah it is very closely related, but that method calls to load a hboot that isn't for our phone.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] 31ken31:
True but I would assume if you substituted the evita hboot it may work. .. I'm not gonna brick and try personally
[AT&T, Rogers HTC One X, Telstra One XL] aguitarfreak:
+1 on JTAG repair. I recently did mine, and then onward I was extra, extra, extra careful. Any doubts I had, I posted on the forums here and was promptly guided. You should follow the same.
[AT&T, Rogers HTC One X, Telstra One XL] mhadonis:
Hboot for htc one x att

can i get hboot for our phone....????????
[Xperia Z Q&A, Help & Troubleshooting] webgrafx:
Hello, I want my xperia z rooter unlocks but I find no support for my build numbers is as follows: 10.3.1.A.1.1.0

Thank you in advance
[Xperia Z Q&A, Help & Troubleshooting] Bairei:
Did you try method for .244?

Tapatalk'd by Xperia Z
[Xperia Z Q&A, Help & Troubleshooting] ckyy:
"Downgrade" (it's arguable if .10 is an actual update) to .244

.10 is a bull**** carrier update that does more bad than good.

Gesendet von meinem C6603 mit Tapatalk 4
[Xperia Z Q&A, Help & Troubleshooting] worf_1977:
Try to Flash .423 kernel, root it as usual, then reflash .10 kernel again...
[General Questions and Answers] mosh11:
hi

i have a zopo zp900 , it didn't get wet , i didn't drop it, touch screen just stopped working like that (no response at all) , i disassembled the phone , disconnected the digitizer cable and reconnected it but same problem. solution anyone ?

thanks
[General Questions and Answers] obscuresword:
Pretty sure it is defective. You may have to replace the digitizer itself. Does the screen work at all? Maybe it needs to be calibrated?
[General Questions and Answers] mosh11:
yes the screen is absolutely fine , but the touch screen doesn't respond at all , it is like you are never putting your finger on it
[HTC Sensation] ayaznoor:
ok so im using Sensation XE since three weeks, its updated to ICS from day one. but the updates keep coming. every second day, i turn on wifi and it notifies me that an new update is ready to be downloaded. but nothing changes inside the About Phone info, as attached here. is anybody else getting so many updates? is it normal?
[HTC Sensation] cutejerk420:
What rom u using? Maybe u shud ignore the updates if u feel its useless.
[HTC Sensation] ayaznoor:
im using the official HTC ICS rom
[HTC Sensation] ayaznoor:
and just now i got another notification for available system update. each of these updates is 60.53 MB large, so im guessing its either the same update again and again :/
[HTC Sensation] rzr86:
do you have custom recovery installed?

are you rooted?

check also in your sdcard/downloads i think if the update.zip exists there

if it is exists then delete it
[HTC Sensation] ayaznoor:
my phone is not rooted, it doesnt have CWM recovery or anything like that. plus there's no update.zip in downloads folder either
[HTC Sensation] rzr86:
so you are saying that you are completely stock

if yes then that's weird notifying all the time for update

also there should be somewhere located the update.zip because when i was in stock condition too i had OTA updates in my sdcard

try this

connect to the internet and search again for update

if it shows you that there is an update available just download it but not install it

disconnect from internet and then perform the update

see how it goes after that
[Android Q&A, Help & Troubleshooting] mosh11:
hi

i have a zopo zp900 , it didn't get wet , i didn't drop it, touch screen just stopped working like that (no response at all) , i disassembled the phone , disconnected the digitizer cable and reconnected it but same problem. solution anyone ?

thanks
[Android Q&A, Help & Troubleshooting] Unaided:
Have you tried to do a factory reset?
[Android Q&A, Help & Troubleshooting] mosh11:
yes i did but same problem
[Nexus 7 (2013) Q&A] appelflap:
Guess a single falsification of this expectation will do.

I have horrible spontaneous reboots on my N7 2013. Really hope the update will fix this. I monitored a lot of update threads but didn't find a confirmation (or falsification) yet that this issue is solved.
[Nexus 7 (2013) Q&A] MattDN93:
Reading this thread http://xdaforums.com/showthread.php?t=2380866&page=32 it might not fix the issue but the update isn't widespread enough yet for people to check. More reports will probably be here.
[Nexus 7 (2013) Q&A] appelflap:
Ah! Someone reported in that thread today that he got a reboot on the new update. So, no fix. Terrible
[Nexus 7 (2013) Q&A] wintermute000:
try a factory restore, rogue apps etc. others on forum have reported fixing it by uninstalling chome beta, some IP TV monitoring app, etc.
[Nexus 7 (2013) Q&A] daraldf:
I haven't experienced this issue on mine as of yet.
[Nexus 7 (2013) Q&A] appelflap:
Tried all suggested fixes and then some more. Hope Google will find the culprit sooner than me

Also am in the unfortunate circumstances that I can't return the tablet. I've imported it.

Oh well...
[Nexus 7 (2013) Q&A] wweeii:
Not for me, installed JSS15Q, multi touch issue is fixed, but reboot problem still remains.

The first 2 hours was OK after flashing, then reboot returned to every half an hour or so.
[Nexus 7 (2013) Q&A] cyberprodigy:
I have never had a random reboot on my device. Maybe I'm just lucky.
[Nexus 7 (2013) Q&A] danvee:
Bad news is that there have only been 123 people posting about this freezing, rebooting, etc issue.

Need everyone effected to make it known by posting there.... Or they won't take it seriously....

https://productforums.google.com/forum/#!topic/mobile/mG4JXaT-SHs[351-375-false]
[Nexus 7 (2013) Q&A] sfhub:
Should you be asking more people to post? Aren't you worried with 124 people Google may not get you the hand-picked replacement? :)

Just kidding.

I think they have two types of random reboots. One is software related which will eventually get fixed. Another is hardware related, which may never get fixed and will be left to the RMA process to resolve.
[Nexus 7 (2013) Q&A] danvee:
Doubting that would ever have been a possibility... :beer:

Fact is that a poster or 2 said basically, statistically, 123 out of the however many thousands were sold is little more than statistical noise.

I agree. I also see many more people posting here with varying degrees of issues, but all boiling down to the 3 issues : freezing, rebooting, GPS.

Maybe increasing the numbers will bring the statistics to a more accurate number.

It's almost 3 days, and I still haven't had the update pushed to mine yet.

Shine enough light on something and it gets attention... :thumbup:
[Nexus 7 (2013) Q&A] fosser2:
I had a reboot today and I am running the latest software...
[Nexus 7 (2013) Q&A] sfhub:
It is silly to take 123 as an absolute # and say it is noise. You need to compare relative to other issues for the same user base to get a weighted #

Obviously many more than 123 are having the issue and obviously many people aren't.

If you sell 1m units and 10‰ have issues you still have 900k users with no issues wondering what you are complaining about. However 10% is actually a pretty high defect rate and can easily erase margins and erode your brand.

The question is not who is screaming the loudest, but whether your problem is a 1%, 10%, 20%, etc problem. I suggest you judge your problem relative to how many people complained about the GPS and multi-touch issues.

erratic touchscreen

216 authors

GPS searching

222 authors

Random freeze and restart

127 authors

So if you take GPS as the biggest issue by number of unique users

erratic touchscreen is being reported by about 97% of GPS levels

and random reboots is being reported by about 57% of GPS levels

We know Google addressed multi-touch and GPS issues and have asked for bugreports for random reboots so I'm sure it is on their radar. It probably is just a more complex problem to solve than updating drivers.

Any other issue being reported is just noise compared to these big 3. Other issues are probably at 1-10% of GPS levels.
[Nexus 7 (2013) Q&A] vcallas:
I am running the 15Q update for past 30 hours and have had 2 random reboots about 16 hours apart. The first I was trying to. Test the GPS issues as I lost lock and GPS TEST was not seeing any satellites. The second I was reading an article in Feedly.
[Nexus 7 (2013) Q&A] appelflap:
It must be on their radar. A random reboot is the most horrible thing that can happen to a user. Especially when it happens when you are writing that long, well thought mail to your boss asking for a salary raise. :o

I'm sure they received a lot of complaints about this from frustrated users.

Because of the severity of the problem and the number of people affected by this (not only xda members) it really makes me wonder why the don't respond to it with a statement. Then again, I agree, the problem can be very complex. A pain in the ass for Google also.
[Nexus 7 (2013) Q&A] b22ri22an:
before i returned my nexus 7, the random reboot was always while pandora was trying to change songs. at the worst it was rebooting as many as 4 times in a 10 minute drive, making it a terrible device for a car stereo replacement combined with the gps issues.... glad the gps is resolved but i'm waiting for the reboots to be addressed before i give the tablet another try.
[Nexus 7 (2013) Q&A] danvee:
ATP their radar must be on fire, but, no, no response addressing the rebooting other than having the effected send logs.

In my case it only happened while it was asleep, and I'd only know it as the expected background apps weren't there, prompting me to check the up time.

I'm suspecting a lot of finger pointing between Google and ASUS going on in the background.

Either way, no help for those of us past our return window.

Only advice I can give is to return/exchange any device with the freezing, rebooting, touch or GPS issues while you can.

There are 'good' units out there if you want to take the time to find them.

Otherwise, keep an eye here: https://productforums.google.com/forum/#!msg/mobile/mG4JXaT-SHs/doD54oeEJrUJ to see how Google/ASUS is handling it.

Consumer Reports also had issues with their test unit:

http://www.thestreet.mobi/story/12017053/1/wait-before-buying-a-nexus-7-tablet-consumer-reports.html
[General Questions and Answers] gmurph59:
I'm new to XDA and I'm looking for a file to root a Samsung Galaxy note 2 i605 vramc3. I have oden but I can't seem to find a file to just root the phone so that I have SU privileges. I won't be changing ROMs. Does anyone know where I can find the CF file or this phone?

Thanks,
[General Questions and Answers] immortalneo:
That's the Verizon variant right?

Here you go:

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

Your device has a dedicated forum for it. Use it to look for guides, ROMs, and to get help and support. :)
[Android Q&A, Help & Troubleshooting] H0wdy:
Hello,

Anyone know if/when/where this update can be gotten?:)
[Moto X Q&A] soklean:
I am looking to find the isis mobile wallet apk for att. Not sure why it isnt available in the app store to download but it should be can someone please help by pulling the apk for this app for att.

Thanks in advanced.
[Moto X Q&A] gunnyman:
It's still in a restricted beta isn't it?
[Moto X Q&A] distortedloop:
Nope, it's not in closed beta anymore. On their website it looks like it's not even in limited test markets anymore, although looking at their site's "where can I use it page?" it suggests only Salt Lake and Austin, but a city search pulls up locations here in Los Angeles.

It's in the app store for all (with compatible devices) to download: https://play.google.com/store/search?q=isis%20mobile%20wallet&c=apps

I just installed it on my VZW Droid Maxx, but it's not available for my T-Mo HTC One.
[Moto X Q&A] soklean:
the moto x is an isis approved device but i download it from google. I need the apk so i can side load the app.
[Moto X Q&A] dworsky:
I need the AT&T ISIS apk too (I have an AT&T S4 with a TMO advanced sim but it won't work). It seems like it wants the AT&T ISIS app, not the TMO app (or one simply cannot mixed and match phones, ISIS apps, and simcards).

Thanks,

Edgar
[Moto X Q&A] meccanikal:
I'm having the same problem. I'm using the at&t LG G2 with T-Mobile secure Sim. I'm able to download the T-Mobile Isis app and bypass the root check but when trying to activate it the app says "unable to communicate with Isis." I've tried market unlocked to change the play store market (to at&t) but I can't find Isis is the results. When I try through the website, it tells me I don't have any compatible devices.

I'm hoping the at&t Isis app works for me.
[Moto X Q&A] pivotraze:
This is ripped directly from the Play Store. It doesn't work with my GPe HTC One, though. :(

https://mega.co.nz/#!kdRzBCgC!Q-7KKWdtOYiDbbYNgvhiDGK9Z91Pt5DtuK50kNf_U_k
[Moto X Q&A] mvndaai:
Device problems

I downloaded the app using the 'evozi apk downloader' I would post the link but I am new to commenting on the forum.

The problem I am having on my AT&T Moto X, is it says I do not have a compatitble device. If someone could find a way for it to skip that test, that would be the best.
[Moto X Q&A] mvndaai:
If anyone could get rid of this error, I would be estactic.
[MDA III, XDA III, PDA2k, 9090 General] Uziel:
Extended Roms???? ok i am a total n00b can anyone explain to me what these are or what you do with them?

Or at lease point me to a tutorial or info?

I also would like someone to explain what the kitchen is for?...............(& dont say cooking food :-) ....)

any help point in the right direction would be a big help...

Thanx PPL
[MDA III, XDA III, PDA2k, 9090 General] Lewisham:
This is in the Wiki, I learnt from there.

Just for you, because you asked nicely, the extended ROM is what is loaded onto the phone that is non-essential to operation (basically, anything that isn't the operating system). When you hard reset, and then it starts installing software after boot; that's your extended ROM being loaded.

A lot of people make their own because they don't like/want/need the software in the extended ROM (see: O2 Active, iMate bundling Skype).

The whole cooking thing I don't really get either, I think it's just another word for rolling your own extended ROM.

Chris
[MDA III, XDA III, PDA2k, 9090 General] Uziel:
Lewisham..

thanx for your help heading on over to wiki now to look a lot harder. :-)
[MDA III, XDA III, PDA2k, 9090 General] findus:
Cooking is all about customising your extended ROM to include the files and registry settings you want straight away after a hard reset. You will need to cook an extended ROM if you want to upgrade to 1.40 and keep your operator settings for GPRS etc.
[MDA III, XDA III, PDA2k, 9090 General] Bret:
Hi guys,

I only found this site a couple of days ago and I have already unlocked my XDA2s, stripped the O2 software, and tried out a few little tweaks.

However, I am really not confident enough yet to do anything more serious, despite being an IT & Communications engineer.

Could you please help me? I am looking for your latest ROM version to use on my XDA to completely remove the O2 stuff, hence stopping it attempting to install software after a reset. I am also missing some useful utilities, such as the battery monitor etc.

Are there any extended ROMs readily available for anyone to use, with some useful programs/utilities included?

I have looked at the wiki but don't really know what I am doing!!

Many thanks,

Bret :D
[MDA III, XDA III, PDA2k, 9090 General] Bret:
Oh, and I forgot to ask... is there anything available to debrand the XDA2s? I would love to stop it displaying the O2 start-up screen.

Maybe there should be an XDA-Developers start-up screen instead. :wink: