yashsingh1/xdaforums huggingface dataset:
[Android] meganame:
I'm not sure exactly where or how to ask this but I need to figure out how to take an Android tablet and limit the interface & options.

End result:

Someone picks up the tablet, turns it on, and they see four apps to choose from. No other usable icons or options. I've already pre-configured all four of the apps to do whatever those apps are made to do. (I'll just get the apps from the Play store)

That's it. The guy that picks it up to use it has no other options what-so-ever...he just has whatever I've told it to have.

Would this be called a Custom UI, or is there just an app out there that I need to download? I haven't been able to find anything on Google.
[Android] lithid-cm:
As long as the user doesn't have access to the play store, this should be pretty easy. It will take a custom Rom though. If you are still willing to go about it with a custom Rom let me know, I started something like this for the nexus 7 I bought for my daughter. I should share some insight.
[Android] meganame:
Oh, man, that would be great! Thanks, buddy! I was wanting to do it with the 7, too.
[Nexus 7 Q&A, Help & Troubleshooting] gieja:
I just got ma N7 from US and i live in Poland. When i was buying it i used my google account and checked to connect it with my account to get the 25$ , but my friend's credit card. When i turned on device there was my gmail already so i typed my password.

I didn't get any confirmation about getting 25$ credit, i did all methodes found on forum and it didn't help. Google Movie is not avaliable in my county so it looks like i won't get the movie/book niether?
[Galaxy S I9000 Q&A, Help & Troubleshooting] droidoidoid:
Hi,

I should update my question:

Is it possible to access a Galaxy S i9000's internal sd (e.g. with ADB or an Android manager) without debugging enabled?

My screen is broken (can't see anything, not responding to touch I think, I can hear texts coming through but can't access them) and debugging is disabled but I need to get the data out.

'

Apparently ADB works straight up if the phone is in recovery mode. I've tried a lot of "blind" recovery mode attempts, but no go. ADB still doesn't recognise the device.

Other users have had this problem but they either a) had debugging enabled, or b) their touch works or can see a portion of the screen. Mine is neither.
[Galaxy S I9000 Q&A, Help & Troubleshooting] slaphead20:
adb?
[Galaxy S I9000 Q&A, Help & Troubleshooting] droidoidoid:
Tried adb using Droidzone's tutorial, but I can't enable usb debugging on my phone cause the screen is completely out of action.

It doesn't explicitly state this in the tutorial, but I gather debugging has to be on for adb to work, no?
[Galaxy S I9000 Q&A, Help & Troubleshooting] droidoidoid:
is my handset a paperweight?
[Galaxy S I9000 Q&A, Help & Troubleshooting] frogger5:
Sure not,acces the recovery(everything with blind mode on:) and mount your sd card and internal sd card. It can be done,recovery doesnt need any touch to work. I cant give you direct instructions right now but maybe some others can help you with those clicky things. What recovery you got?
[Galaxy S I9000 Q&A, Help & Troubleshooting] xsenman:
download this tool and give it a go http://xdaforums.com/showthread.php?t=1761556
[Galaxy S I9000 Q&A, Help & Troubleshooting] droidoidoid:
Man, I'm not sure what recovery I got. I flashed Darky ROM into my phone a while ago so I believe I have CWM. When I say blind I just mean trying to get into recovery without looking at the screen. It doesn't help that for my handset, some people say volume up and others say volume down. It's a big pain. I've done it before but I can't remember the key combo.

The only other thing I'm not sure about is the environment variable for ADB. I got it as PATH under User Variables and as Path under System Variables just to make sure. I think that's right.
[Galaxy S I9000 Q&A, Help & Troubleshooting] droidoidoid:
Getting 'error: device not found' on that one buddy.

Added the environment variable > Plugged the phone in (turned on) > started AndroPlatina > 5. Recovery Tools > 4. Reboot to Recovery > device not found

Will keep at it.
[Galaxy S I9000 Q&A, Help & Troubleshooting] frogger5:
Ok if any methods above didnt work the blind recovery may be the last one. I just need the version of your recovery or just a version of darky rom so i can check the CWM. Trust me it can work:) sorry for my bad english im from east europe.

The COMBO for recovery is vol UP+home+power for a few seconds(maybe 3 or 4)
[Galaxy S I9000 Q&A, Help & Troubleshooting] droidoidoid:
I believe it's Darky ROM 10.4.2
[Galaxy S I9000 Q&A, Help & Troubleshooting] Kagadar:
Need more info. Do you have stock recovery? CWM? TWRP?

What version of android? Gingerbread? ICS?
[Galaxy S I9000 Q&A, Help & Troubleshooting] droidoidoid:
CWM

Gingerbread
[Galaxy S I9000 Q&A, Help & Troubleshooting] droidoidoid:
If recovery mode auto-enables debugging then theoretically I should be able to view everything on my phone (texts, contacts, data etc) with an Android manager cause all an Android manager requires is that the phone be in debugging mode.
[Galaxy S I9000 Q&A, Help & Troubleshooting] Kagadar:
CWM has adb enabled. Try using Nexus S drivers straight from Google. Have you got a plan for how to extract the data once you adb in? Data isn't mounted in recovery by default. You can use the mount command, if you need details I'll add them in another post.
[Galaxy S I9000 Q&A, Help & Troubleshooting] droidoidoid:
adb pull

What will the Nexus S drivers do?

So as long as adb isn't finding my device, I can rightly assume that I'm simply not in recovery mode. Maybe I am in recovery mode and something else is at fault, like with the adb installation. Could the environment variables be causing anything?
[Galaxy S I9000 Q&A, Help & Troubleshooting] droidoidoid:
The ideal outcome would be to turn debugging on with adb so I can view the phone's contents using an Android manager. That way, I can get out the data, as well as read the texts that have been coming through. Don't know if this is possible though.
[Galaxy S I9000 Q&A, Help & Troubleshooting] droidoidoid:
This is still the best I can get. I'm sick of seeing it.

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

C:\>adb devices

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

List of devices attached

C:\>

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

:(
[Galaxy S I9000 Q&A, Help & Troubleshooting] droidoidoid:
Update: adb works fine on my GS3 in recovery mode (with debugging turned off in settings) but not on my GS for some reason.
[Galaxy S I9000 Q&A, Help & Troubleshooting] Kagadar:
Check device manager on the computer. Is your phone showing up there at all? What about if you reboot into download mode?
[Galaxy S I9000 Q&A, Help & Troubleshooting] droidoidoid:
^ Not showing up in device manager (GS3 shows up fine). Download mode same thing - I can attempt it blind but since I can't see the screen I don't know if I'm download mode - regardless, still nothing in device manager or adb.

I can manage to boot it up (I hear the intro). I can also hear the usb sound on my pc when I plug it in. But then I have to do 2 things with no screen a) do my security pattern, and b) tap 'mass storage mode'. Sounds easy but I've tried it many times and can't nail it.
[Galaxy S I9000 Q&A, Help & Troubleshooting] AlwaysDroid:
Alright I'll take a shot at helping then. Also if you really want I'll flash darky ROM and record the blind steps to Mount from recovery.

Also FYI I am looking for an work around through things like fastboot to get into debug, or directly pull the contents.

Edit: idea for a workaround.

1. Find out if your phone is connected to your wireless network.

2. If it is, find out its IP address using a computer program that tells you what's connected to your WiFi. Find the android. If you don't know which one, disconnect all other devices.

3. Using an ssh client such as winscp try logging in as "user" with no password.

4. Hopefully, be able to navigate to sdcard.
[Galaxy S I9000 Q&A, Help & Troubleshooting] Kagadar:
If it's booting you should be able to get to recovery, unless the phone was one that was shipped with bad bootloaders (like mine). If so the only way to get into recovery to flash good bootloaders is via adb. If the touchscreen is still responsive you could try using a TV out cable.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] ryomakun:
My Rom right now is FusionRom V2.5 with NoteCore Kernel 6.1EX, and i am newbie android developer, my question when i build android app that containt imageview, i got problem with gc_for_alloc freed ,that free % is very low , just 3 or 4% but when i compare with SGS2 stock rom 2.3.6 get 49-50%, so can anyone help?
[Galaxy S II General] bundi22:
I have CM9 installed on my old Galaxy S for my younger bro with the latest devil kernel and CPU at 100-1200mhz. On my S2 I have CM9 with siyah 3.4.1 at 200-1200mhz.

When comparing the two, there is a massive difference in touch sensitivity and scrolling. The Galaxy S is so so much better and responsive and makes the S2 feel crap when you go back to using it. I hate the elastic scrolling on ICS!! It is perfect on the galaxy s, comparable to the S2 with Gingerbread, but S2 with ICS scrolling has never been the same. Fluxi kernel with xxkernel gingerbread touch settings seemed to improve the scrolling a bit, but I still prefer to stay on siyah. My CM9 galaxy s2 advanced settings touch sensitivity is set on 20

The second thing is the screen colours.

The galaxy s has much better whites and the S2 seems to have an ugly green tint to the screen. A difference is also noticed in the background of settings.

The galaxy s is still a damn good phone! But I love my S2!
[Galaxy S II General] zemariaabreusantos:
I wish I could see for myself, but my Galaxy s has a broken screen. I agree on the scrolling issues but the rest I can't say. Can you upload some pics of both devices side by side?

On what cm9 release are you on? RC2 improved scrolling a lot!
[Galaxy S II General] bundi22:
I'm on 21/06 CM9, might update tomorrow and try the new changes
[Galaxy S II General] BLiTZTN:
Yes I can confirm that
[Galaxy S II General] marcellocord:
You will find no scrolling/color difference.
[Galaxy S II General] bundi22:
I've been checking the changelogs and that's what I thought. Maybe the updated newer kernel has been the difference.

Cant wait for supercurio to release his display expert app, hopefully it can improve things.
[AT&T, Rogers HTC One X, Telstra One XL] RobertX1:
I think my ATT htc one x may be hard bricked... :( :( :(

I was playing around with ROMs and lost track of time. The last recovery I had on there was clockworkmod (was going back and forth between it and twrp).

I was trying to install the new jellybean rom and it kept on giving me an "assert failed" error. At this point, I deleted the assert lines from the recovery script as advised by one of the posters, and ran the install again. Went through... rebooted and...

The phone is completely dead now. I think it may have discharged? I plugged it in to the wall socket and nothing... absolutely no lights, no screen..... :( :( :( Power+ vol down does not work either....

Please help me, is there any way to recover from this situation?
[AT&T, Rogers HTC One X, Telstra One XL] BenPope:
Wrong subforum.
[AT&T, Rogers HTC One X, Telstra One XL] Rusty!:
You don't flash a Tegra One X ROM to your Qcom S4 One X did you? I assume the partition layouts are quite different, so this is bad.
[AT&T, Rogers HTC One X, Telstra One XL] shadehh:
Doesn't seem like a rare thing occurring. Either people are overseeing this or they are not really aware that for you can't flash a rom made for a tegra quad core device onto a dual krait.
[AT&T, Rogers HTC One X, Telstra One XL] RobertX1:
I used this....

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

Sheesh..... Is this meant for the tegra? I never thought I would do such a thing.... I was aware of the issue/hardware differences....

Is there any hope? Actually, in device manager it shows up as QHSUSB_DLOAD and I heard thats a bad sign?

If it cannot be fixed, does anyone have an estimate about how much HTC would charge to reflash/fix it?

My signficant other is as po'ed at me as can be... especially since I had really pushed for the upgrade.... man...
[AT&T, Rogers HTC One X, Telstra One XL] Rusty!:
Yes it's meant for the Tegra One X, that's why it wouldn't install (that, and it's not in the AT&T One X section). You bypassed the check the install script does to make sure you're installing it on the right phone.

In short, yes you have buggered it, QHUSUSB_DLOAD is a state where you can write things to the phone, but whether anyone as done any research into it on the S4 One X I don't know.

As for getting it fixed, I have no idea on cost, however... if you convince HTC that you didn't do it yourself, it might be possible to get it done under warranty.

Edit: Did a bit of research and /system on the Tegra One X is is HBOOT on the S4 One X, that's why it's ruined your phone.
[AT&T, Rogers HTC One X, Telstra One XL] lawrence750:
htc would just replace the motherboard and charge for that - loads of people have reported the cost its something like £169 to replace motherboard, which would of course un brick it.
[AT&T, Rogers HTC One X, Telstra One XL] Pudex:
Have you tried to keep it plugged in to a charger for an hour or so? My HOX was dead too but started to flash red light after an hour, moment after solid light and it booted
[AT&T, Rogers HTC One X, Telstra One XL] Rusty!:
He doesn't have an HBOOT any more, there is nothing he can do.
[AT&T, Rogers HTC One X, Telstra One XL] supendal:
This is why people should stop being stubborn and call that phone HTC One XL. These kinds of situations would happen sooner or later.
[AT&T, Rogers HTC One X, Telstra One XL] RobertX1:
I guess I did... I actually had come to that page via google and since, perhaps I was a bit sleepy, did not verify the source... should have....

Is there any fix at all? Like loading the drivers and reformatting it or something?

Im a bit confused about the motherboard replacement: since its a software issue, cant HTC fix it with a software update? Ill call them today and post the answer on this group as well, but knowing what I am dealing with may help in talking with them.

Thanks to everyone again
[AT&T, Rogers HTC One X, Telstra One XL] Rusty!:
No fix that I'm aware of. You really need to be asking this in the XL section though. The phones really are quite different, we don't have the mode you're stuck in (not being Qualcomm based).
[AT&T, Rogers HTC One X, Telstra One XL] RobertX1:
Thanks... Someone in that section has kindly agreed to see if he/she can help me... Keeping fingers crossed... :) doent feel right to tell att that my phone stopped working for a replacemenf...
[AT&T, Rogers HTC One X, Telstra One XL] Hunt3r.j2:
Hate to say it but your phone is dead. It's not revivable ar this time and so your only option is jtag or warranty replacement because you overwrote the Hboot.
[AT&T, Rogers HTC One X, Telstra One XL] shadehh:
Don't let morals get you on that one. Lie to them, if not for yourself than for me.
[AT&T, Rogers HTC One X, Telstra One XL] Castellano2:
I am sorry, QHSUSB_DLOAD is dead end at every HTC phone. There is nothing you can do. I know what I am speaking, I hardbrick my last HTC in the same way.

But quarrantee will work, HTC cannot find out that you root it. They will replace you mainboard..as someone already mentioned
[AT&T, Rogers HTC One X, Telstra One XL] Rusty!:
Not quite, there is a debricking method for the Sensation that can recover from it.

In most cases though, you're right.
[AT&T, Rogers HTC One X, Telstra One XL] miniterror:
i already revived 2 sensation xe's from the qhusb_dload.

need linux though but it definetly is possible:-o
[AT&T, Rogers HTC One X, Telstra One XL] RobertX1:
Please move this thread to the XL subforum

Thanks... any hope for this being possible for the one XL? Also, could the mods please move this thread to the ATT section (sorry for posting it in the wrong section... but I really didnt know the importance of the difference.... wanna look at my phone? :) )

Thanks everyone. I think I might send the phone to HTC to get it repaired.... although the s***ty thing with that is that Ive heard they take that opportunity to replace the motherboard instead of just replacing the software, and hit me with a big bill rather than a reasonable/fair price....

So.... trying to be honest (by not returning the phone as defective to HTC) ensures that I get scammed by them... :victory:
[AT&T, Rogers HTC One X, Telstra One XL] Rusty!:
Possible? Yes of course, that's the point of that mode as I understand it, with some other HTC phones you can hook it up to a RIFF Box and load it up.

Likely? Probably not, as it'll take people looking into it in depth to figure it out and as far as I can see, no-one has/is looked/is looking into it on the OXL.

It really does look like you'll need to send it to HTC, which (as you sound quite honest) will probably be expensive.
[AT&T, Rogers HTC One X, Telstra One XL] niceppl:
its possible

i unbricked mine from brick mode

however you have to know what was the cause

for my hox while i was researching for soff i tricked my hox to think its an evo 4g lte then flashed an evo rom and after applied panda...the hboot got replaced with a moded one which fail the signaturr check....so it bricked...

long story short....with linux you can flash the hboot back....and if thats cause of the brick then u may unbrick.

if you previous dump all ur partitions u may likely.unbrick as well....

havent looked at the rom i flashed... but i dont think i has a hboot in a custom rom..but probably stuff flashed into the wrong partitions again u can try flashing other peoples partition dumps on urs

steps：

1 take a look at the rom see which mmcblks it flashed to

2 get all dumps on a linux machine

3 try to flash those partition the rom touch in emmc mode.....hope it will unbrick

the emmc mode for hox only last about 5 sec then its cut off by the protection....

anyway i know the method...but this is not my findings....which i dont wanna post a how to....

if you r under warrenty...take.it.to.att to them ur phone is.just dead... not physical or water they replace it....

good luck
[AT&T, Rogers HTC One X, Telstra One XL] Hadcook:
I stuffed up my phone flashing sent it directly to htc they replaced the motherboard for free, took a week but its good as new. I didnt tell them it was from flashing though or that i had unlocked it.
[AT&T, Rogers HTC One X, Telstra One XL] RobertX1:
Thanks niceppl and hardcook

@niceppl - need to do a bit of reading to undestand your message completely! Before starting though, I do have both cwm and twrp backups, is that what you mean by dump files?
[AT&T, Rogers HTC One X, Telstra One XL] RobertX1:
Thanks

Thanks for your replies everyone.

@niceppl - need to do a bit of reading to undestand your message completely! Before starting though, I do have both cwm and twrp backups, is that what you mean by dump files?
[AT&T, Rogers HTC One X, Telstra One XL] Rusty!:
In theory you'd only need an HBOOT to resurrect the phone, but it's getting it installed that's your problem.
[AT&T, Rogers HTC One X, Telstra One XL] RobertX1:
emmc mode

@niceppl : How do I get into emmc mode on the one X? I know I use linux, but could you point me in the right direction?

I know it will be difficult to describe everything, but if you point me in the right direction, or tell me the tools, Ill learn :)
[AT&T, Rogers HTC One X, Telstra One XL] beaups:
What exactly is your question? P12 is system on T3 hox and hboot on S4 hox. That's why these rom's not only don't work...but they brick the S4 HOX. (which can be recovered, btw).

Even if you updated the script to install proper, it ain't gonna work. Period.
[AT&T, Rogers HTC One X, Telstra One XL] sassafras_:
As mentioned, if you can get the phone into eMMC mode, you can quickly flash the HBOOT partition again which should allow to get it working.

To do this, you have to hold the power button for 10 seconds until the lights start flashing (make sure the phone is already plugged into a linux computer). Right as the lights start flashing, the phone realizes there is no HBOOT and falls back into eMMC mode for a few seconds which is more than enough time to dd over the hboot again. So, you need to get a working hboot (from a RUU I would imagine), then 'dd if=/your/working/hboot of=/dev/sdX12' (where X and 12 are the One X and the correct partition, respectively). This will push the hboot back into place, and then should be able to boot from it again, allowing you to fastboot a recovery back onto the phone. From recovery, you are golden.

Edit: Also, good on you for not lying and returning the phone. Rare these days.

sassafras
[AT&T, Rogers HTC One X, Telstra One XL] TheNightHawk223:
From what i heard, In linux you can DD the hboot in to recover the phone...maybe. Im not sure on the details, ill try to find out where i read that . Best of luck to you! :good:

EDIT: Seems like sassafras beat me to it
[AT&T, Rogers HTC One X, Telstra One XL] Hunt3r.j2:
Good luck, if you can get the hboot back onto the phone then you will be one of the few people who have managed to get into QHUSB_DLOAD mode and still managed to resurrect the phone.
[AT&T, Rogers HTC One X, Telstra One XL] Blackcircle:
This is very interesting. I have an EVO LTE and I'm also at this state. Is there any kind of guide on this mode? my hboot is also gone and I need to somehow try to restore it.
[AT&T, Rogers HTC One X, Telstra One XL] Hunt3r.j2:
There is a QHUSB_DLOAD unbrick tool in your device's development section released by the same people who made Lazypanda.
[AT&T, Rogers HTC One X, Telstra One XL] JSLEnterprises:
You've bricked it. This isnt the same thing as the Evo 4G s-off tool. You cant recover from this unless you jtag the device or use qualcomm engineering tools, and have access to a qualcomm image (this is not an ruu)

This is more similar to the QLOAD brick in older devices like the sensation xl and desire hd.
[AT&T, Rogers HTC One X, Telstra One XL] beaups:
Not true. Most of these bricks are caused from flashing international roms, which overwrite our hboot (p12). This can be recovered with linux using eMMC mode.
[AT&T, Rogers HTC One X, Telstra One XL] MugiTenks:
not sure if my phone is bricked, or just crippled, but it's pretty unusable.
[AT&T, Rogers HTC One X, Telstra One XL] beaups:
How did you do it?
[AT&T, Rogers HTC One X, Telstra One XL] wonghiukong:
i have the same problem

hey guys, how's going with your attempt to rescue your bricked hox?? I have the same problem now , I tried to flash a htc one x international rom to an at&t htc one x , and it turned into QHSLOAD mode too:crying:! If you succeed, tell us the method~~~
[AT&T, Rogers HTC One X, Telstra One XL] Kindatired:
How are people still doing this? Everyone should double, hell even triple check what model phone a rom is for.
[AT&T, Rogers HTC One X, Telstra One XL] TheNightHawk223:
The type of things that make me hang my head in shame of the human race's ignorance... :banghead: Didn't you notice the couple..... HUNDRED warnings out there...

Well anyways there supposedly is a method because when you boot or fail to boot (Or somthing along those lines) you go into emmc mode for 5 seconds in which you can possibly dd the hboot back in. This is about all I know and heard about this method and I think it works although I'm not sure. Let this serve as the 500th warning for everyone not to FLASH INTERNATIONAL ONE X ROMS ON THE EVITA!

....hell who am I kidding...
[AT&T, Rogers HTC One X, Telstra One XL] NJGSII:
I really don't think that anyone who would flash a Tegra 3 One X rom onto their phone would be able to resurrect it by typing commands into a command prompt.
[AT&T, Rogers HTC One X, Telstra One XL] wonghiukong:
hey, why so mean? I just made a mistake here. Actually, I'm familiar with command line and Linux, if there's such method that works, I would like to try!
[AT&T, Rogers HTC One X, Telstra One XL] lambergino:
i know have the same problem .. .is there no solution ???