yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Q&A, Help & Troubleshooting] shaarky:
Guys, do you know about some way how to disable on I9000 (currently Juwe's 5.1 ROM) annoying low battery notification ? Either only sound or popup, or the best - both. I'm looking more for permanent solution, not using silent profiles or something like this.

Thank you.
[Galaxy S I9000 Q&A, Help & Troubleshooting] $omator:
delete the sound ogg from media folder duh - easiest tweak ever =)
[Galaxy S I9000 Q&A, Help & Troubleshooting] shaarky:
A....I was searching for SND ;-)

You mean maybe to delete file TW_Battery_caution.ogg and TW_Low_Battery.ogg in /system/media/audio/ui/ ?
[Galaxy S I9000 Q&A, Help & Troubleshooting] $omator:
TW_Battery_caution.ogg - just move it to internal sdcard and reboot? ;)
[Galaxy S I9000 Q&A, Help & Troubleshooting] shaarky:
It worked, even without restart. There is still popup, but finally I'm not scared anymore by this sound ;-)
[Galaxy S I9000 Q&A, Help & Troubleshooting] amwebby:
I can find this file with ES File Explorer but it won't let me delete it. I'm running stock Gingerbread 2.3.3 JVQ so can't root. Any ideas?
[Galaxy S I9000 Q&A, Help & Troubleshooting] CommanderTux:
@amwebby

You must have root access, to delete the files.
[Galaxy S I9000 Q&A, Help & Troubleshooting] amwebby:
That's what I figured. Without flashing a custom rom there seems no easy way to root these days, sigh.
[Galaxy S I9000 Q&A, Help & Troubleshooting] dachau:
Yes, there is. Just flash a different kernel, e.g. CF-root.
[Galaxy S I9000 Q&A, Help & Troubleshooting] amwebby:
I didn't want to flash a different kernel. I guess I'll just have to wait until oneclickroot or gingerbreak work out how to do it.
[Galaxy S I9000 Q&A, Help & Troubleshooting] $omator:
you do not need to flash kernel to remove/move one file out of system, just use some rooted file explorer to move this god damn sound file
[Galaxy S I9000 Q&A, Help & Troubleshooting] amwebby:
If I cannot root the phone how can I use a rooted file explorer?
[Galaxy S I9000 Q&A, Help & Troubleshooting] $omator:
how do you want to mod the phone without rooting it ?
[Galaxy S I9000 Q&A, Help & Troubleshooting] amwebby:
I don't. I just don't want to flash a kernel to root the phone. As superoneclick and gingerbreak don't work on gingerbreak I'm stuck.
[Galaxy S I9000 Q&A, Help & Troubleshooting] $omator:
so use cfroot, it is root only basicly not forcing file conversion or anything oter
[Galaxy S I9000 Q&A, Help & Troubleshooting] marser:
Anyway you should flash a kernel/custom rom. Its damn better...
[Galaxy S I9000 Q&A, Help & Troubleshooting] amwebby:
Thanks for the feedback guys. I'm trying to keep it stock so I can evaluate Samsung Android vs other flavours and iPhone as they are in the marketplace. I just find that damned battery beep annoying!

Reading up on cfroot does not reassure me that this fits with my aim or indeed that it is a trouble-free method of rooting. Too many tales of FC and apps gone missing. :(
[Galaxy S I9000 Q&A, Help & Troubleshooting] dachau:
You can flash another kernel then install busybox and Superuser and then revert to stock kernel. The phone should be rootet then and you still have the original kernel. You just have to find it or make a backup with SGS Kernel Flasher (oh, that requires root i forgot...)
[Galaxy S I9000 Q&A, Help & Troubleshooting] $omator:
none of this sort
[HTC Inspire 4G] luvmygadgets:
I have recently encountered an issue where my backlight is dim (backlight levels are at it's maximum) to the point where I can't even see my screen if I'm standing outside during the day (didn't have that issue before), and at times it flickers. It's really irritating, because I have to wait until I am indoors/in my car for me to be able to see what's on my screen. :(

Is there a way to get this fixed without losing the data on my phone? :confused: I really don't want to lose my text messages, if at ALL possible, and I'm hoping it's not just something I have to live with for the life of my phone.

Any suggestions are appreciated! :)
[HTC Inspire 4G] biglittlegato:
There are apps you can use to backup your data. I use SMS backup for my texts and sync all my data to my Google account.

Sent from my Inspire 4G using the power of the dark side.
[HTC Inspire 4G] luvmygadgets:
Oooooh, thanks! I'll try that first.
[HTC Inspire 4G] Scott_S:
Yup. That puppy's goin' back. Start backing up.

No way it should be doing that, or that you should have to deal with it for the life of the phone.
[HTC Inspire 4G] Twistitup:
Have you used your warranty already, or have you rooted?
[HTC Inspire 4G] Scott_S:
The thing is, even if he's out of his 30 days with ATT, he still has a year with HTC.

This is undoubtedly a manufacturer defect. If he is rooted, he'll need to get it back to stock and s-On, or risk having the warranty voided due to the whole rooting thing.
[HTC Inspire 4G] footbal9584:
Titanium Backup might be able to backup texts, but is it under warranty or did you buy it used?

Also this might be a stupid suggestion, but did you try with the auto brightness off? Maybe there is something flaky about the luminous sensor. Good luck dude keep us updated
[HTC Inspire 4G] luvmygadgets:
LOL 'He' is a she, but thanks for the advice. Not rooted, and I haven't used the warranty, yet. My texts were the only thing I was worried about, but I did sync those to my gmail, so I'm good! :) Gonna see about taking it to the warehouse for replacement. :)
[HTC Inspire 4G] luvmygadgets:
I did disable the auto brightness. Unfortunately, it made no difference.
[HTC Inspire 4G] Scott_S:
Sorry. Impossible to tell by your username, and sadly, the ratio of girls to boys here is heavily weighted towards...wait for it...

Waaaay too many dudes. :p
[HTC Inspire 4G] luvmygadgets:
:) It's all good. No harm done. LOL
[Xperia Play Android Development] xperiaplay:
ok so ive just tryed to flash the uk generic .184;

flashing failed because stupidy i forgot to enable usb debugging tryed to boot phone to enable sony ericsson screen loads then a screen with an explanation mark and a phone appears and it turns off again

someone please help!! :(
[Xperia Play Android Development] thatsupnow:
Try using PC companion or seus to repair it
[Xperia Play Android Development] xperiaplay:
yea im gonna try that now cheers i hope it works!!!
[Xperia Play Android Development] xperiaplay:
ok so pc compainion repair didnt work said to go to support online?! trying again now but doesnt look good!

my phone is still under warrenty right because i havent unlocked bootloader or anything?

EDIT

OKSO I DOWNLOADED THE UDATE SERVICE FROM SONY REINSTALLS AND SEEMS TO BE WORKING AS SHOULD AGAIN THANK ****!

NOW DEBATING TRYING IT AGAIN HAHA
[Xperia Play Android Development] ncaissie:
Give it a shot. Just enable the Dev mode.
[Xperia Play Android Development] Mozza2k11:
As long as your bootloader is locked SEUS can reapir the phone all day and night from being bricked.

Follow the guide here, i did with no problems. I didnt have usb debugging on before flashing .184 and it worked fine.

Maybe it didnt properly install the first time. When done it should say something like flash successful turn on phone.
[Xperia Play Android Development] ncaissie:
Or maybe your USB cable came out of the phone. I know mine doesn't feel secure when plugged in.
[Xperia Play Android Development] xperiaplay:
yea not sure what is was but flashed again an now im rooted with 2.3.3 :)

cheers for the help people!
[Xperia Play Android Development] ncaissie:
Cool, have fun.
[Galaxy S I9000 General] Tehpriest:
Android 2.3.3 update for Vodafone Samsung Galaxy S now rolling out via Kies

http://ausdroid.net/2011/07/12/andr...Feed:+ausdroid+(Ausdroid)&utm_content=Twitter
[Galaxy S I9000 General] camomopa:
Hi,

What the improvements with this update?

Thanks for your experiences feedback.
[Galaxy S I9000 General] onetik:
But has any end-user actually been able to update? I'm now so annoyed at Optus/Virgin.
[Galaxy S I9000 General] dizzle118:
It was offically rolled out months ago in the UK
[Galaxy S I9000 General] Northern.dj:
There is none its is horrid major battery drain but i'm on 2.3.4 and that rocks but i don't no when Vodafone are rolling this out
[Galaxy S I9000 General] petermunster:
Try to use 2.3.4 it is much better
[Galaxy S II General] borchgrevink:
Have tried cache clean and everything. This is also listed as a problem to others, but I have found no solution. Any suggestions?
[Galaxy S II General] qwerty warrior:
try a hard reset
[Galaxy S II General] Sp1tfire:
Well, i got a different problem. Today when accessing the market, when i go to my apps it only shows YouTube app as installed, no other app, even though i got a dozen of apps installed from the market. But if i scroll through apps in the market they appear as installed. Strange, as i didn't delete data or cache from market app :o
[Galaxy S II General] borchgrevink:
Well, getting a new phone is as hard reset as it gets? Isn't it?
[Galaxy S II Q&A, Help & Troubleshooting] njord74:
Hi.

I would like to flash some of the newest firmwares out there but they dont have Norwegian letters in the Samsung keyboard T9.Some have in landscape mode,but i prefer type with one hand in T9.

So i would like to copy the files i have now and use Root explorer to paste them back after a flash.

The problem is that i dont know what files to copy.

I find 2 files of AxT9IME under System-app but is it only those 2?

Nothing in bin?

And i dont even know if its those files i need to copy...

Please help!
[Atrix 4G Android Development] Ronaldo_9:
Good thread for our bricked friends. Nice one!
[Atrix 4G Android Development] eval-:
This is exactly the kind of spam I do not want on this thread.

If this starts to happen I will close this thread.

Please respect the big red underlined request in the first post and

do not post

in this thread unless you have experienced 0x1000 yourself, and have something useful to contribute.

Thanks in advance for valuing our time.
[Atrix 4G Android Development] kennethpenn:
Six step plan is a no go for me. I tried it quite a few times with two different batteries.

One battery is low-ish on charge and it reads the following under the traditional error:

Entering NVFlash recovery mode
Battery is too low to flash

The other battery is full. It reads the error for about three seconds and then quickly flashes the "NVFlash recovery mode" line before it turns blank. The screen just goes dark. Still, the device must be on, because it won't let me reboot without battery pull.
[Atrix 4G Android Development] Gandalf:
@kenneth that's exactly what happened with me.

I have already gotten a new atrix and dumped the busted one back to AT&T (on the pretense of a battery dying while doing an OTA update.) So unfortunately I cannot help figure this out.

But for my two cents, im still a firm believer that using a factory cable to connect the phone w/o a battery to a PC holds the solution we seek.

I attempted to make my own, but at 7am after going all day at work (im in the US Marine Corps Infantry ) I was falling asleep while soldering. Im going to work on it again this weekend though.
[Atrix 4G Android Development] Sthony:
I had the 0x1000 error yesterday morning by flashing pudding. I don't think was a hard brick due too the fact that I was able to recover.
[Atrix 4G Android Development] robonoob:
Same issue as jakew02, how ever I still have my bricked atrix. I will get a fully charged battery and try to get some results but I have the same symptoms as Kenneth as well as in phone starts for about 3 seconds and immediatley needs a battery pull. I'm off work in a few hours and will post results then.
[Atrix 4G Android Development] eval-:
Please guys...

the more descriptive the better

.

Sthony, you OTAd to 4.5.91 from 1.8.3 by putting the .zip in /sdcard and fastboot menu into Recovery? Then, you flashed Pudding and soft-bricked. How did you recover? Were you unlocked before OTA? Or you only unlocked after flashing pudding?

Can those of you who recovered please

cat /sys/firmware/fuse/ReservedOdm ? (as root)

We would like to determine what prevents you all from downgrading (and maybe, possibly, get the still-bricked out of nvflash mode, but this will probably require cable + SBK). So it will help knowing exactly what versions you went FROM and TO (with OTA inbetween) and the type of 0x1000 you got (bootloop with RSD option using battery during volume-up method, VS. nvflash, VS. fastboot menu) including the SVF (usually 105:1:2) message if possible.
[Atrix 4G Android Development] bl0wf1sh:
Kenneth, same here.

the 6-step thing is a no go for me. It flashes the NV thing very quickly, then goes dark. At least I know what I did wrong, and quite stupidly so

- On 2.3.4 stock

- tried to push a de-odexed services.jar , deleting the services.odex (stupid in hindsight)

- pushed kenneth's boot.img and system.img (without reading that the system needs to be UNLOCKED)

- since the only thing left was RSD, tried to flash 1.2.6, which failed. BOOM. hard brick.

I only hope my stupidity helps people not make the same mistakes.

Will try to give it to a moto service center tomorrow, see if they can fix it.

*EDIT* doing the steps in the first posts without battery but plugged into wall outlet leaves the phone in "starting nvflash... battery too low to flash." If you push in the battery, and then pull out the cable, the screen stays on. Not sure if that helps anything, since I don't know how to do nvflash, and don't have the right tools to begin with.
[Atrix 4G Android Development] knigitz:
Please fill out and use the following template when posting to this thread:

1. Before the 2.3.4 (4.5.91) OTA upgrade, did you flash a fresh install of 1.8.3 .sbf from RSD?

2. If the answer to #1 was no, what mods (if any) did you have installed at the time of your 2.3.4 (4.5.91) OTA flash (cwm, pudding, root, et cetera...), also what version of software were you on if not 1.8.3?

3. After flashing the 2.3.4 (4.5.91) OTA by putting the update.zip in the root of your /sdcard-ext/ and booting into the stock recovery, did you install any mods (cwm, pudding, root, et cetera...)?

NOTE: If you did not flash the 2.3.4 (4.5.91) OTA by putting the update.zip in the root of your /sdcard-ext/ and booting into a stock recovery, please detail what method you used to get to the 2.3.4 (4.5.91) OTA. This thread is only for users who flashed with this method.

4. Did you use RSD to flash anything else while on the 2.3.4 (4.5.91) OTA, such as pudding?

5. Did you use fastboot to flash anything else while on the 2.3.4 (4.5.91) OTA, such as cwm or preinstall root?

6. Did you then try to flash back to the stock 1.8.3 .sbf via RSD? If so, what version of RSD Lite did you use?

7. If the answer to #6 was no, what version of .sbf did you flash via RSD, also what version of RSD Lite did you use?

8. Did you encounter the 0x1000 error after trying to downgrade to a lower version .sbf?

9. Have you been able to recover from the 0x1000 error and resume normal functionality? If so, what software version are you currently on?

10. Please detail below exactly what had occurred during and after the downgrade to a lower version .sbf via from the 2.3.4 (4.5.91) OTA. If you were able to recover, please detail the steps that led up to your recovery. Also what type of 0x1000 you got (bootloop with RSD option using battery during volume-up method, VS. nvflash, VS. fastboot menu) including the SVF (usually 105:1:2) message if possible.

Also include everything required from the first post of this thread. This is very important.

If you can also provide filenames for the files you've flashed, that would be optimal.
[Atrix 4G Android Development] Whipon:
=>

Well, I had this issue some days ago following the Pudding stickied topic.

I had 4.1.8.3 with old Tenfar's CWM so following the steps in that topic flashed 4.1.8.3 again with RSD Lite. It was a service SBF.

Then I booted in Android recovery mode and flashed the OTA. Everything went fine, I had 4.5.9.1 with all my data and apps.

Then I flashed Pudding.

Instantly after RSD rebooted my phone, I had this 0x1000 error. I didn't know what to do, I followed the guide step by step and I was confused. So I tought "Maybe I need to unlock my bootloader". So I booted the phone in fastboot mode and unlocked my bootloader through fastboot.

Then I did a fastboot reboot and voila, the phone booted again in 4.5.9.1.

I notice I have a "Unlocked" text in the Motorola boot screen.

Well, I hope this info helps someone.

Let me know how it went.
[Atrix 4G Android Development] kamikazy:
Failed to boot 0x1000

I have the same issue that you guys have...

I did the update to Gingerbread 2.3.4 and then I tried to roll back to froyo so I used RDSlite 5.3.1 and this .sbf: OLYFR_U4_1.2.6_SIGNED_OLPSATTSPE_P012_HWolympus_1g_1FF.sbf and the phone got hard bricked...

I left it with the battery inside yesterday and today the phone drain the battery completely... I took it off, charge it for 2 or 3 minutes and put it back, connect it to my pc and it displays:

SVF: 105: 1:2

Failed to boot 0x1000

Entering nvflash recovery mode

Battery is to low to flash

But if i take the battery from my other atrix, fully charged it just turn on, display the error and for a second "Entering in nvflash recovery mode" and then Black Screen.
[Atrix 4G Android Development] bl0wf1sh:
Just going to point this out in a new post for everyone to see on unbricking transformer: http://xdaforums.com/showthread.php?t=1123429

I am wondering if sth like this could work (with the right .cfg and .sbf). I am going to take a look at the nvflash package in any case.
[Atrix 4G Android Development] cranch:
You would need your SBK which is why the NVFlash issue is a 'hard' brick in the first place.
[Atrix 4G Android Development] NYG-SBXLII:
First i would like to apologize if this post is not of much use to you guys as I have not hard bricked my device. However I have flashed the 4.5.91 OTA and I noticed something intersting.

1 I unlocked my bl the night pudding was released.

2 I flashed a fresh 1.83 sbf

4 OTAd form android recovery to 4.5.91

5 on the very first reboot after OTA I entered into RSD protocol and once I connected to RSD lite 5.3.1 I noticed RSD identified my device as SE-Olympus insted of the normal NF-Olympus.

6. I flashed zomgunlock-lite.sbf. After it completed SE-Olympus changed back to NF-Olympus.

I may be wrong but i dont ever recall RSD seeing my device as SE-Olympus.

Anyways I hope this may useful and good luck!
[Atrix 4G Android Development] trvstw:
On my bricked Atrix, it just shows the error, and stays there until a battery pull (no other text shows up)
[Atrix 4G Android Development] kholk:
When you see the LOW battery warning, it's a false warning. On Olympus, NvFlash can only be accessed with external power from the factory cable (without ANY battery inserted). That's why your devices are "flashing" and powering themselves down. It's a "protection" implemented by Moto (as factory cable should be only built by Moto for repairing bricked devices).

Anyway, why are you hardbricking your devices flashing an old bootloader?

...At least, do you know why your device isn't relockable?

The new bootloader writes a bit into a fuse (in the ODM Reserved set) that isn't already blown. When it reads it back, if it's set to 1, it shows the "Unlocked" message and disables security checks.

Still, why can't I relock the device?

As you might know, when a fuse is blown, its programming power ramp is literally blown, so, you can't reprogram a fuse that has been burned.

And still, so, after so many hours of boring reading of your post, can you tell me why the **** my device is bricking with an old bootloader?

...The bootloader reads the entire ODM Reserved fuse set. When it reads it, it won't read fuse 1,2,3,4.... but the ENTIRE set.

If another fuse is blown, the old bootloader can't recognize why the damn there's an 1. It doesn't know what it is.... so boot fails, MotoBoot stops its execution and passes it to the Emergency NV3p Server (Emergency NvFlash Mode, from nVidia MicroBoot).

I think those infos should clear some doubts in your mind.

Cheers!
[Atrix 4G Android Development] t0dbld:
very nice of you :-) I offered to possibly fix some bricks but with out knowing actual facts as to what is going on with their devices it would be hard . have you talked to any of them ? you know they dont talk to me , do they actually have access granted to NV3p server or nvflash or are they still locked out?

as per the first post, the OTA DOES CHANGE YOUR BP, THIS IS NOT A ?, as i was graceful enough to enter irc under another handle and post earlier in the week.

on a side note the irony of this entire situation is that i was booted from #moto-atrix after arguing the subject of blindly flashing back to older versions with a sbf, true at the time i was concerned with 1.84 - 1.29 , but now just a short time later ...

Regardless a fix maybe possible but need to know exactly what access you have once powering on device

*edit* for the sake of giving you what you asked here is my output , I am unlocked, rooted, I did use OTA I never bricked , I am now running my own stuff after flashing a CWM and building

DeviceKey FFFFFFFF
JtagDisable 0
KeyProgrammed 1
OdmProduction 1
ReservedOdm 10000000000010001000300004000
SecBootDeviceConfig 0
SecBootDeviceSelect 7
SecBootDeviceSelectRaw 0
SecureBootKey
SkipDevSelStraps 0
SpareBits
SwReserved 0
kfuse_raw ��j�s��Q��'��9@�C��%57�ܠ� ��.�޴�܏��fm���vp��^����D}�G������K�*^V��w�+�����6:��YяmTq���;bH9�٩$M��nT&�7����4.�ŷX{�J������[�;N{�,(Ay���V��K=tTD���!$�{%�f��y;v��~�\�C:L-|��w���)�g#�!mv���+W�T�����(����|�3LNP�HV�J��|q��b�Wfa��/
�.���^df�6�6�e�n��U�Sj��j}�_g��i��c�i�h��0$ bz)�ߋ�Cd|ge-G���oU�GF��w���YLn2E,�rU����5�V��3.�V��NjY�m�v*Bt�����2�V2@�?��ؘ��#w��&6�+rdb;TK_r��� �,�F_���vQ�NJ
�2��}(�8mg�ȯ#nv������M$�Oǹ=E��I�v��E�9tP"�[`�'�a#X�E��S+�4 �u/�ö4�B|y�1bd��*��N��/"U��p���� F���%4>X�0H�xx�����
sku F
[Atrix 4G Android Development] robonoob:
So here is my basic info now that I am home.

I was on stock att 1.83, flashed 2.3.4 via zip through sd card. Tried to install pudding, phone went into bootloop then flashed the red led. upon reboot showed error and message of "no os available cannot boot."

After panicking a bit, I loaded the 1.26 sbf, got to the moto boot screen and the phone shut off, no led, no message, nothing. I pulled the battery and restarted, then all I got was the 0x1000 message for 3 seconds, then the NVflash message and immediately a blank screen.

Now that I am home I have tried the steps provided and haven't been able to see the phone through rsd lite, and it still has the same symptoms. If you need any other info, or if i have forgot anything please let me know I will help where I can since I now have a paperweight and a brand new functioning atrix, thank god my mother-in-law was due for an upgrade.:D
[Atrix 4G Android Development] kholk:
They're still locked out. No SBK no party.

"No OS to boot" implies that you need to repartition/reflash without absolutely touching the MotoBoot. So, someone make a recovery SBF that won't flash the bootloader or you'll see plenty of bricked devices.

They can't recover with NvFlash.
[Atrix 4G Android Development] t0dbld:
ouch ya still locked out is a problem.... and even with dev cable they cant get to any other options correct? it jsut forces into nv3p mode witch is useless because of sbk am i correct so far ?