yashsingh1/xdaforums huggingface dataset:
[HTC Sensation] yayakuya:
yes, in here indeed that so hard to found that the original battery....

will try it when it's possible to get...

i won't bet with non-original one....
[HTC Sensation] nlooooo:
I have some Hinorx crap that actually performs very well.
[HTC Sensation] yayakuya:
excuse me???

Hinorx what???

you mean this:

http://www.kupindo.com/Baterije/10274305_-LG-P920-Optimus-3D-Pojacane-Baterije-HinorX-2050mAh
[HTC Sensation] nlooooo:
Yes, Hinorx CRAP, and it's 1200mAh.
[HTC Sensation] yayakuya:
borrowed my friend's XE battery...

DIDN'T SOLVED...
[HTC Sensation] Mile_zdr:
maybe it's stupid thing but try your phone without sim and sd card maybe some of them causing this..
[HTC Sensation] yayakuya:
it's not stupid at all...

some of devices solved the SOD by its method...

but trust me, i already try and wrote it in the OP as i mentioned...

flight mode works on stock ics, but no with CM11

so stressful... but having fun with :p
[HTC Sensation] yayakuya:
Finally Solved!!!

Even by an ACCIDENT :p

see the first post....

Thanks for you guys who kinds to help me in any matters... :highfive:
[HTC Sensation] rzr86:
glad for you mate:good:

but you have to know that in viperS ROM only one kernel is working the one that is already included
[HTC Sensation] yayakuya:
yes i knew it...

that's why i do some EXPERIMENTS that i was done in every ROMs i've flashed before this

( only searching for this kind of accident )

and see... it's working!!! :D

this is one of my experience in 2 years on Android World...
[Nexus 5 General] Sir Zeph:
Hello Peeps,

I have a Nexus 5 with Cataclysm Rom and Faux123 Kernel. Previously I was using the CyanogenMod and Franco Kernel.

I looked around the forums for a thread on this but couldn't find one.

So I decided to make this thread so that we can argue out the top few kernels that really improve the Nexus 5 battery life. Some people were saying that the Faux123 kernel did improve the battery life but honestly I don't see much of a difference.

I also undervolted my device by 50 mV. So what is a good kernel for the Nexus 5?
[Nexus 5 General] _MetalHead_:
There's a reason you couldn't find any comparison threads- Rule 4. http://xdaforums.com/showthread.php?t=2500184
[Verizon Samsung Galaxy S III] vax1170:
Hello all,

Short story, wife had the 4.3 OTA nag popup, accidentally hit 'ok' and pulled battery before unit booted.

I thought maybe I could avoid the 4.3 OTA by flashing CWM via heimdall. I followed the CM directions for d2vzw at wiki.cyanogenmod.org/w/Install_CM_for_d2vzw, basically I did the following:

heimdall flash --ABOOT aboot.mbn --no-reboot

heimdall flash --BOOT boot.img --no-reboot

heimdall flash --RECOVERY recovery-clockwork-6.0.4.5-d2vzw.img

However when I try to boot into recovery mode, I get the android character with spinning globe. I only saw the picture long enough to pull the battery.

Any suggestions on this on? It looks like the confirmation for OTA sets something, and it appears that whatever I did above either was wrong, didn't happen properly, or is ignored at this point. If I boot back into download mode I still see custom binary no, and current/system binary official.

I would like to get this to CWM and CM 10.2, but suspect it is too late ... can anyone tell me how to work around this, or should I just bite the bullet and reboot to see if the OTA updates at this point?

Thanks for any help you can advise on ....
[Verizon Samsung Galaxy S III] buhohitr:
Boot into download mode (vol down + Home + power button). Do you see this? If you see the last 2 lines you are on 4.3

product name: sch-i535

custom binary download: no

current binary Samsung: official

QUALCOMM secureboot: enable

warranty bit:0

bootloader rp swrev: 1

secure check fail: recovery
[Verizon Samsung Galaxy S III] vax1170:
No not quite. I don't see the last few lines. My eyes are a bit old but what I see is only:

ODIN MODE

product name: SCH-I535

custom binary download: no

current binary: Samsung official

System status: Official

QUALCOMM secureboot ENABLE

And nothing else after that (just the green antroid graphic and 'downlaoding....')

Thank you for the fast response :)
[Verizon Samsung Galaxy S III] buhohitr:
Seems like the 4.3 didn't make it. You can boot up the phone and re check..Once phone is up just turn off wifi and 4g to prevent the OTA.
[Verizon Samsung Galaxy S III] vax1170:
Sorry I wasn't clear ....

I believe the phone already had the OTA software downloaded and staged for install. It was popping up that nag screen that asks to run the update. My wife pressed 'OK' on that and as the phone shutdown and brought up the 'samsung' splash screen, the battery was pulled.

It was after this that I attempted to follow the CM directions to flash the older bootloader and CWM. However I don't think it was successful.

After running the procedure, I attempt to boot into recovery. I am expecting to see the usual CWM menu, however I don't. I get the android with the spinning globe in the belly. I am thinking, the flash with CWM didn't take, and the OTA is now attempting to install.

If possible I would like to flash CWM and then load up CM 10.2 from an internal SD card I've prepared.

Let me know what you think .... thanks!
[Verizon Samsung Galaxy S III] buhohitr:
It's possible that the 4.3 bootloader already flashed and it's in the process of flashing the rom when you pulled the battery. In any case, if the software is half done you phone won't boot, and if you attempt to flash the old rom, you will brick your phone if the bootloader already locked. So you need to turn it on to see where you at or you can take a chance and try to Odin old stock rom, again if the bootloader already locked you will brick your phone and if not then you will be back to the older version. I would turn it on and see.
[Verizon Samsung Galaxy S III] vax1170:
Thanks.

Is there anyway to tell for sure if the bootloader is the new one?

Fortunately I have 2 other S3's I can compare against. One is a 32g S3 with OTA 4.3. The other is a 32g S3 I picked up preinstalled with CWM/CM10. The hosed up phone is a 16g S3.

Can I pull something down from these phones with heimdall to check/compare if the 4.3 bootloader is there? I already did a print-pit on all 3 phones, but from what little I know it seems like the only differences are likely due to the memory sizes. 32 vs 16.

If there is no way to tell, then perhaps I'll reboot it and see..... thanks for the help,
[Verizon Samsung Galaxy S III] buhohitr:
If you don't see the last 2 lines like I mentioned above, it should be the old bootloader...since the timing you pull the battery, no one really know what state it's in unless you boot it up.
[Verizon Samsung Galaxy S III] vax1170:
Am I correct in assuming that the 3 heimdall statements I executed above should have resulted in CWM coming up when I do the up-home-power?

The CM instructions for d2vzw are not clear if you really need to let heimdall reboot the phone between each step. I was trying to avoid a full reboot as I expected the OTA to take over if I did.

Perhaps I should reboot it; if it boots up into anything, at least I can sell it ....
[Verizon Samsung Galaxy S III] buhohitr:
Yes, you can boot up now and see what's going on...
[Verizon Samsung Galaxy S III] vax1170:
So it looks like it is bricked to some degree. What might you advise to undo this?

When I power the phone up I see the usual Samsung galaxy logo, then the screen goes black with pulsing blue LED.

If I boot into recovery, I see the android with spinning globe for about 60sec, then the dead android with red triangle, and phone resets.

If I boot into download mode, it still comes up with the same messages I indicated above. It looks like the boot loader is not new. I can connect with heimdall and print-pit, so something is still alive here.

What is your best advice here? At this point, I don't think I care if it is put back to stock 4.1.2 or upgraded; booting and working with anything is fine.

Thanks
[Verizon Samsung Galaxy S III] buhohitr:
I would try to use Odin and flash MF1 full firmware here http://www.androidfilehost.com/?fid=23134718111254196
[Verizon Samsung Galaxy S III] vax1170:
Thanks for confirming ... I was poking around the forums and figured I should probably try the procedure to completely reflash my device back to stock. I'll try that later tonight. Thanks again ... crossing my fingers ;)
[Verizon Samsung Galaxy S III] vax1170:
[RESOLVED]

Looks like flashing the 4.1.2 stock image worked, device boots now!

There was somewhat unexpected behavior however, I don’t know if this is interesting or not. I followed the usual directions to use Odin to flash the full MF1 stock rom; this took about 8-10 min to complete.

On reboot, I saw the tiny blue message at top, and the phone appeared to start in recovery mode, at which point the android graphic with spinning belly globe came up. The progress bar went the full length (no error) and phone rebooted. Phone seemed to reboot fine with typical Samsung and LTE logos. When the phone came up, I was surprised. After unlocking the screen, I got a pop-up indicating that the phone update failed. I then found that all my old data was still available; wi-fi passwords, apps, account syncing, etc. everything. I was expecting the device to be wiped clean with the flash - but maybe I misunderstood. Download mode still seems to report the same messages as before (so it looks like it hasn’t been locked). Needless to say, I hit airplane mode and disabled WiFi, and the phone is not activated, so there is no ability for it to pull the OTA again. If it makes any difference, when I flashed this phone it had no SIM card, and it also had a new 1gb SD card I left in there which was populated with CWM and CM images.

Some summary details to anyone who is interested:

- Phone was running stock 4.1.2 MF1, it received the 4.3 OTA package and was popping up the request to update. Accidentally hit ‘ok’ and phone started reboot sequence to apply update. On phone startup, battery was pulled to prevent update.

- Attempted to run the CM 10.2 d2vzw procedure to flash older bootloader and CWM using heimdall. Transferred just fine, but this didn’t appear to work. Upon entering recovery mode, the android graphic comes up and attempts to do something, but fails.

- On reboot, the phone has pulsing blue LED; bricked

- ODIN’ed the stock 4.1.2 image back, and phone is un-bricked, pops up message on failed update, and all previous data is retained.

If there is any other information from this that could be useful to developers let me know. The phone will not be put back into service for some time, and I can transfer off or adb anything someone might find interesting. Just let me know and I'll try to retried and post here.

Thanks for the help!
[Verizon Samsung Galaxy S III] buhohitr:
You're a lucky son of .....lol.
[Moto X Q&A] sparks83:
Has anyone had any issues with music stuttering while listening over bluetooth? It also happens immediately after I push the power button to lock the screen. I'm running an unlocked bootloader with TWRP recovery and xposed framework. I uninstalled xposed and it still happens. This also happens on other bluetooth headphones for me too. Any advice?
[Moto X Q&A] sethes302:
Try turning off WiFi and see if that fixes it. fixed it for me.
[Moto X Q&A] Ctrl-Freak:
I also have this problem with my [nearly] stock, rooted, XT-1058. It seems to happens every time I lock the screen. I have tried more than one music app, and it happens whether using either headphones or the car.

I do not, however, have any random stuttering.
[HTC One Max] mizzouse:
Hey guys, I bought the htc one max from sprint and having a problem trying to root. For some damn reason I cannot find where to enable usb debugging, in settings I dont have development at all. I have wireless & network buttons and icons, personal stuff then phone stuff. None of them have any development or debugging buttons that I can see. Is there a way to turn this on?

HTC One Max - Android 4.3

Cancel this question.. found my answer through multiple sites till it showed tapping the build number till you see "You are now a developer" which enables the options I need.
[HTC One Max] DVS_Sokar:
Follow info here:

http://www.androidheat.com/enable-developer-options-android/
[Verizon Samsung Galaxy S 4] SeeJayPee:
So I've been messing around with various sms applications. I have not found one that works with the original touch wiz lock screen notification. Is this possible? Is there anyway possible that this can be done? Is there any app or mod that it is possible to do?
[Verizon Samsung Galaxy S 4] decaturbob:
are you a stock S4 or have you rooted/running custom roms? whats your base?
[Verizon Samsung Galaxy S 4] SeeJayPee:
Rooted on mk2.
[Sprint Samsung Galaxy S III] AlanYepez123:
I accidentally formatted my storage and did a factory reset. But my ROM Manager backup got deleted.

Is there someway i can get my backup back or restore it back to how it was?

P.s. I am not using my phone so i'm sure nothing got overwritten.:crying:
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] sniper8752:
I was looking at this article, and saw that the method works for the s4 at&t version: http://www.androidpolice.com/2013/0...-wont-get-to-see-how-for-a-while-here-is-why/. When released, will this work with our phone then?
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] hovax615@hotmail.com:
It was already released this post has been almost a year ago. They already fixed this exploit.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] sniper8752:
What about this: http://www.androidauthority.com/uno...date-breaks-supersu-app-fix-available-333586/. Although it doesn't look like it would be for our AT&T model.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] hovax615@hotmail.com:
Its not for our model its for international. There's a thread about this already.

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

---------- Post added at 01:34 PM ---------- Previous post was at 01:34 PM ----------
[Galaxy Note 3 Android Development] Hashcode:
Reserved

KNOWN ISSUES:

PLEASE USE STOCK TOUCHWIZ FROM SAMSUNG FOR YOUR STOCK ROM -- FLASH TO ROM-SLOTS

If you install Safestrap on a rom-slot it will show "not installed". *DO NOT INSTALL SAFESTRAP ON A ROM-SLOT*

Rebooting from a rom-slot will end up at a blank screen. Battery pull and re-power on.

Sometimes the installation doesn't work correctly. If you don't see the splashscreen after a rebooting. Install Safestrap again. (DEBUGGING THIS AS I GET TIME)

If you don't see files on "Micro SDcard" for some reason try tapping that area and swapping to "Internal Storage" and then back again.

No Aroma installer support. This is due to the stock S5 kernel framebuffer. To build a recovery which worked, it needed QCOM patches. So will Aroma.

If you try a .zip file with an Aroma installer, it will most likely just hang.

If you use the "4way reboot" mod, then "Reboot Recovery" button in the Safestrap APK won't work correctly.
[Galaxy Note 3 Android Development] Hashcode:
Reserved
[Galaxy Note 3 Android Development] micky387:
wonderfull work.

My knox is 0x1 but i think lot of people like your work.

Thanks
[Galaxy Note 3 Android Development] A.N.Droid:
never thought it would be released for hltexx.

i read about it some time ago and was really surprised about the rom slots feature.

i like the idea of having an alternative rom on my device.

downloading it now, will give some feedback later.
[Galaxy Note 3 Android Development] TylerDurben:
Thank you Hashcode!!!

Atm i can say that backuping works fine....looking for an second rom to test with X-Note as Stock, Aroma installer is not supported for now.....

Sent from my Safestraped SM-N9005 BlackBox
[Galaxy Note 3 Android Development] A.N.Droid:
i successfully installed echoe rom 5 into rom slot 1 !

i like safestrap very much, easy to use and self explaining.

if you already have twrp installed, you do not loose it but you don´t need it anymore.

booting to recovery brings up your original twrp, a normal reboot shows the splash screen from where you can launch safestrap.

trying to install a rom with aroma installer of course doesn´t work but i tried just to see what happens :

the screen just freezes and you need to reboot by holding down the powerbutton, thats all.

you can restore a twrp backup of an aroma based rom, that you made from the stock rom slot, to another rom slot (i did it with a backup of bobcatrom).

but it looks like it uses the internal storage directory of the stock rom slot.

edit: seems like the original storage/emulated/0 is always used. i can see all the files from stock rom after installing a complete new rom.

so this isn´t really good for having 2 totally seperate operating systems installed, is it ?

have to read some more about it...

thanks a lot hashcode !

edit:

from the safestrap blog:

DON’T RESTORE A CUSTOM ROM-SLOT BACKUP TO THE STOCK ROM. THIS WILL MOST LIKELY BRICK YOUR PHONE.
[Galaxy Note 3 Android Development] fmotta:
Great Job

Thanks Hashcode, great tool!

Using it on a SM N-9005 without problems except I have a couple of ROMs that do not activate Wi-Fi.

Any clues?
[Galaxy Note 3 Android Development] ktetreault14:
I would love to be able to use this on the N900T
[Galaxy Note 3 Android Development] effortless:
I've been using the AT&T Safestrap Recovery on my Tmobile N900T and it works perfect. I flashed the AT&T X-Note ROM port (in slot 1) that they have and it works fine on the N900T. It does install the AT&T CSC, but installing the TMO one causes crashing in the dialer (which also happens in the international rom currently out in the TMO forum). So, just keep the ATT CSC like it is. For Wi-Fi calling, I just boot back into the Stock slot and use the stock ROM.

The AT&T Safestrap: http://xdaforums.com/showthread.php?t=2572978

The AT&T X-Note Port ROM: http://xdaforums.com/showthread.php?t=2579773
[Galaxy Note 3 Android Development] My1xT:
sounds intresting...
[Galaxy Note 3 Android Development] xclub_101:
If I understand correctly right now all ROM slots boot using (all of them) the same kernel (which of course must be stock Samsung kernel in order to keep knox 0x0).

This means that with kernel 4.3 (and corresponding bootloader) all slots must also be 4.3, while with kernel 4.4.2 (and corresponding bootloader) all slots must also be 4.4.2 - is that correct?

Will existing version work with 4.4.2 or a new version will be needed?
[Galaxy Note 3 Android Development] trader418:
Will this ever be able to backup efs like the official twrp? Also will this ever support aroma? I know you said the kernal doesn't support it, but I was wondering how mobile Odin can do it without tripping knox

Love your work, it is working like a charm :D
[Galaxy Note 3 Android Development] sound2005:
Hi Hashcode

Yipee!!!

I'm so glad you decided to release this on the n9005.

i'm off on the weekend, will test this and let you know the outcome!!!

Again
[Galaxy Note 3 Android Development] nguyenson318:
Do not download. Please give another link.
[Galaxy Note 3 Android Development] sound2005:
[MENTION=465387]nguyenson318[/MENTION]

Mirror 1: Goo.im Download <--- not working

Mirror 2: Crackflashers Download <--- is working

So far this is working perfectly on my note 3 n9005.

Have backup my stock (actual it a custom rom!!) and installed a couple of roms in the free slots and all is working.

Still testing the software out but its very good, esp. if you want to try all the rom being released without messing with your main system.

Still need to test whether restore works and at the moment i have notice that i still have CWM as my recovery but when booting to Safestrap TWRP takes over.

Like i said i'm still testing this great piece of software but Hashcode has done a great job making this work on the n9005

Well Done :)
[Galaxy Note 3 Android Development] nguyenson318:
I download from n9005 note 3 (Next Browser) but only 0.1KB is stopped.
[Galaxy Note 3 Android Development] sound2005:
Here is the file

To mods, please remove this post if it violates the forum rules

To Hashcode, if you prefer people to download from your links provided i shall remove this post, i do not wish to cause you any offense.

Thanks for creating a killer app and i hope you keep on improving this product

If you wish me to test any aspect of your software on my handset, please let me know
[Galaxy Note 3 Android Development] Nirak:
I'm sorry if i sound like an absolute noob...but this requires root.

Afaik rooting the Note3 trips the Knox warranty flag......thus no more warranty.

Am I wrong?
[Galaxy Note 3 Android Development] trader418:
This is for people who have rooted via kingo or URDLV etc that don't trip counter.
[Galaxy Note 3 Android Development] pirate.666:
What does "encryption disabled" mean in the op? Password or other locking method?
[Galaxy Note 3 Android Development] My1xT:
no. The Full device encryption is meant here...
[Galaxy Note 3 Android Development] pirate.666:
Ok. Thx. Could you plz tell me how do I know if my device is encrypted?
[Galaxy Note 3 Android Development] My1xT:
Settings -) Security, the top option, if you haven't used it it's off.

Gesendet von meinem SM-N9005 mit Tapatalk
[Galaxy Note 3 Android Development] sound2005:
Hi guys

Has anyone tried running this app on kitkat (4.4.2)??

App worked great on Jelly bean (4.3) but when rebooting into recovery mode on Kitkat, i just get a blank screen.

App installed on Kitkat without a hitch and i have selected install recovery, when i select boot into recovery the phone doesnt restart.

When i force restart my phone, the Samsung logo appears and hangs on the black screen. I have to remove my battery to get back in to my phone.

I'm wondering if this app is compatible with the 4.4.2 bootloader??
[Galaxy Note 3 Android Development] sanjsrik:
So, what ARE compatible ROMs for SafeStrap to work with?
[Galaxy Note 3 Android Development] A.N.Droid:
all 4.3 touchwiz roms and all current cm 11 builds.

edit:

from my experience, you can only have cm on the stock rom slot.
[Galaxy Note 3 Android Development] sanjsrik:
Aren't CM11 builds 4.4.2? Wouldn't that be incompatible? Don't those require you to have a CWM recovery and Safestrap only works with TWR recovery?
[Galaxy Note 3 Android Development] A.N.Droid:
they are based on 4.4.2 but the current cm builds do not contain the new bootloader.

all the issues are about the new bootloader that you get when you flash 4.4.2 touchwiz roms.

i have the official cm 11 nightly on stock rom slot and bobcatrom, which is android 4.3, on rom-slot 1.

i also had the temasek unofficial cm11 build installed.

you can see it in my sig.

the dual boot thing between touchwiz and cm/aosp is a bit complicated atm but i think that was not what you were looking for.
[Galaxy Note 3 Android Development] sanjsrik:
I've been flashing and working with Android ROMs for a few years and nothing what you wrote here made any sense. Sorry, could you elaborate a little?

For example:

How can you have the temasek unofficial CM11 build in the stock ROM when the original instructions say that if you put anything but the original stock ROM in the stock ROM slot, you can brick the phone?

I get the bobcat ROM thing but is that any better than what we have with TouchWiz now? I just don't like TouchWiz but I don't also want to get rid of my pen capabilities on the N3.