yashsingh1/xdaforums huggingface dataset:
[HTC One S] 808phone:
Now it's my turn. Pressed factory reset by accident in boot loader. Can get to TWRP but it says E: Unable to mount storage

e:Unable to mount /sdcard/TWRP/twps. when trying to read settings file. etc...

Advanced File manager in TWRP shows /sdcard/TWRP

Any ideas???? If I try to mount data in TWRP my Mac wants to initialize.

Thanks

TWRP shows internal storage 0 mb
[HTC One S] 808phone:
I flashed the stock recovery, then ran it and somehow it booted right into CM11. Everything was lost, but it's working again.
[HTC One S] null0seven:
Factory reset wipe everything! Including SD card.
[HTC One S] 808phone:
Possibly, but how come CM11 was still on there? I think that the Boot Loader in Moonshine's factory reset is not compatible with CM11. Luckily the stock recovery fixed things for me.
[HTC One S] Rapier:
I had the same issue, pressed by mistake factory reset in bootloader some time ago. I was pressing vol down to reach recovery, there was a slight lag and I pressed it a second time the immediately I've pressed power...so cursor has jumped 2 rows then executed. I've solved it only by flashing stock recovery and resetting to factory settings again, then flashed TWRP.

Now why you still had CM11...well not 100% sure but in TWRP when you wipe to factory the system partition is not formatted. I've paid attention once to the messages during a wipe and it was formatting data, cache, dalvik and android secure but not system. A reason can be that while flashing any ROM, the install script formats system at the beginning so theres no need to do that with factory reset.

Now I can only think that the factory reset from bootloader does the same and system is not wiped. Theoretically it is correct...system is read only especially on a stock non rooted device and resetting it to factory practically means that any trace of personal settings/aps and so on should be erased. And those are not stored on the system partition. There is also no hidden place on the phone where a recovery image of the original android OS is kept so this is not like on the laptops where you reset to factory and Windows is reinstalled from the recovery partition. My guess is that the factory reset just wipes all partitions that contain personal data and settings and leave system intact. So after a wipe and reboot is like you first start it.

You still had CM11 cause the wipe didn't format system...If anyone has a better explanation I would be glad to hear it. So From my point of view nothing went wrong and has nothing to do with the Maximus recovery or it's compatibility with CM11. It would have happen the same if you have used any other stock recovery
[HTC One S] null0seven:
Factory reset, resets youre phone to original settings.

Anyway, its good that the phone works.
[HTC One S] Rapier:
Yes. And it is not formatting system when doing this. So any os is installed will be kept

Sent from nowhere over the air...
[HTC One S] 808phone:
I don't want to try it again but I wonder if moonshine's factory reset is incompatible with cm11?
[HTC One S] Rapier:
Dont understand what do you mean by "incompatible". The factory reset from bootloader is not the same thing as the one from a custom recovery. You shouldn't do a factory reset from bootloader regardless of the ROM you're using

Moonshine is an S-Off method, I didn't used it myself so I don't know what factory reset option is in there

Sent from nowhere over the air...
[HTC One S] 808phone:
I never said anything about the custom recovery. If you should never use it, why is it there and why does it make the SD card not available?

Wow, HTC says you can use it here:

http://www.htc.com/us/support/htc-one-x-att/howto/313779.html

I'm sure you know something others like me don't, but I when I mean "incompatible" I mean that I don't believe that it should make the sdcard unavailable and make the phone think it has zero MB. I think what you might have missed is that I used factory reset from the custom boot loader from moonshine. I was wondering if that factory reset was compatible - that's all.

Again, it was a mistake - it's not like I chose it on purpose. Thank you for the help.
[HTC One S] Rapier:
The reset to factory from bootloader exists because on stock ROM there's no custom recovery that has that option....so it's in bootloader. For it to work properly though, you must have the stock recovery also. If you have a custom recovery like twrp/cwm and use the wipe from bootloader it'll mess your sd cause phone is not able to perform the wipe properly with that custom recovery. That's why, in order to get back to normal you should flash back stock recovery and perform the wipe from bootloader again.

Sent from nowhere over the air...
[HTC One S] 808phone:
Thank you for the clarification. It makes sense. Too bad that reset is so close to the recovery command. It's pretty weird that I didn't have to run the wipe from the stock boot loader again. It ran and rebooted the phone into CM11. Anyway, I am glad I am back to running. Thanks.
[Xperia Z2 Tablet General] Pondy:
Hi, please make the Cross-Device Development Projects for Sony Devices thread visible in the Z2 tablet area, as it is for other Xperia devices. Apparently there is an exploit available (http://xdaforums.com/showthread.php?t=2784900) for root without touching the boot loader!!!

Can anyone tell me how I can request this? I've tried PMing a moderator with no response.
[Xperia Z2 Tablet General] Pondy:
Bump [MENTION=3887557]Moscow Desire[/MENTION]
[Xperia Z2 Tablet General] Moscow Desire:
Bumped and forwarded to the correct department Mate!

Cheers

MD
[Xperia Z2 Tablet General] Pondy:
Apologies, I didnt know where to raise this.
[Xperia Z2 Tablet General] bbarou:
bumped.

this is a good idea. Why hasn't it been done yet?
[Moto G Q&A, Help & Troubleshooting] carpon:
I was running a custom rom ( SlimKat ) and i went back to stock

i followed these instructions :

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

but my phone has a very bad battery drain

some how it never goes into a deep sleep and google service Consume a lot of battery

i re-flased it many times and i also wiped cache and data but nothing works !

any help please ?
[Sony Xperia Z Ultra] hunterninja:
guys I need help regarding my device.

Everytime my phone sleeps, it plays the Z ultra video (demo video i guess) and my phone sets to its default settings.

I already resets my phone to its factory default settings but I still got the same problem.
[Sony Xperia Z Ultra] blueether:
odd...

Maybe try and flash a full FTF of a generic version?
[Sony Xperia Z Ultra] adm_83:
not removed after flashing
[Sony Xperia Z Ultra] macrostr:
demo mode > *#*#73556673#*#* to disable it
[Xposed General] tonyzzp:
I want to develop a permission manage program.

but how can i hook the method startActivity?

it has

startActivity(Intent)

startActivity(Intent,Bundle)

startActivityForResult(Intent,int)

startActivityFromChild(Activity,Intent)

.....

and other overload method.

which one should i hook?

if I hook all the methods,when startAcitivyt(Intent) is called, and all the methods are called too.

but if I only hook startActivity(Intent), when the startAcivity(Intent,Bundle) is called,i will not catch it.

please help me.thanks.
[Xposed General] GermainZ:
Look at the source code, startActivity(Intent) will call startActivity(Intent, Bundle) so you only need to hook the latter. This may vary between different Android versions so you'll also want to check that.

In general you can also define a hook then use that for multiple methods. For example:

ZC_MethodHook hook = new XC_MethodHook(...);
findAndHookMethod (someClass, "someMethod", Argument.class, AnotherArgument.class, hook);
"someMethod", Argument.class, hook);
[Xposed General] tonyzzp:
but there is a problem.

if the two methods are:

void methodA(){

//some code ..

methodA(0);

}

void methodA(int a){

//...

}

if i hook methodA(int) and prevent it from running. when methodA() is called, the "some code" will execute,but then stop.
[Xposed General] GermainZ:
This isn't the case for startActivity - again, look at the source code.

I'm not sure what you're asking here, to be honest. Of course, you *can* hook both methods (or even all of them using hookAllMethods, but be careful about argument when you do that), but in startActivity's case that seems unnecessary.
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] sequence2469:
Im running http://xdaforums.com/showthread.php?t=2725121 with the note PRO onscreen keyboard. Are there any themes I can flash with TWRP? I like the keyboard, but I wish I could change the colors.
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] mikep2323:
There is a theme that is done and I asked the guy to theme the keyboard and he did.I haven't tried it yet cause he said it doesn't work good.Im about to redo my tablet and flash the themed keyboard. I'll let you know what it looks like and if it we works. I'll attach some screen shots. I'm gonna do tomorrow.
[JASJAR, XDA Exec, MDA Pro Software Upgrading] asci:
Does exist a plug that allows to see more lines of the default WM05 Calendar app without having to install thirds party SW like agenda fusion or pocket breeze?
[Galaxy Tab 3 General] faria:
http://www.android.gs/galaxy-tab-3-8-0-wi-fi-android-4-4-2-ota-update-available-for-installation/

Warning!!!

Locked boot-loader, once you flash this update you cant downgrade (at Present)

Rom has no knox counter ( warranty Bit) or binary counter.

Rom used to downgrades was T310XXUAMF1_T310OXXAMF1_HOME.tar

Another safe way of trying this rom without fear, is flashing it with mobile odin,mobile odin does not flash boot-loaders so you are safe to downgrade etc.

you may find that you WiFi does not work when rom flashed with mobile odin, that means that the older boot loader is not compatible with the new rom.

Update 1

Once You flash the rom the device will reboot several times, because my previous rom was customized i had to perform a hard reset.

this rom has some kind of KNOX according to superuser

The rom also adds a new entry to download mode AP SWREV: A1

How to root?

download Cf-auto-root from here and flash it via odin then go to google play and install superuser from chainfire, launch it and update normally.

UPDATE 2...

Rom has a watered down version of knox but no common KNOX entrie in download mode.

Q:Can i install a custom recovery is this rom?

A: YES.
[Galaxy Tab 3 General] DigitalMD:
what we really want to know is does this update have the locked bootloader? If so, then you may possibly forever be stuck with touchwiz and stock based ROMs..
[Galaxy Tab 3 General] HavokbyName:
how could we find out? try to downgrade to 4.2 via odin or simply flash custom rom see?
[Galaxy Tab 3 General] DigitalMD:
Yes you could but be cautioned, that could lead to a bricked device. I'm not sure what a safe test would be.
[Galaxy Tab 3 General] HavokbyName:
try flashing custom rom maybe through custom recovery, or does that have same risks?
[Galaxy Tab 3 General] faria:
I will try to downgrade and see what happens.
[Galaxy Tab 3 General] faria:
Warning!!!

Locked boot-loader, once you flash this update you cant downgrade (at Present)

Rom has no knox counter ( warranty Bit) or binary counter.

Rom used to downgrades was T310XXUAMF1_T310OXXAMF1_HOME.tar

Another safe way of trying this rom without fear, is flashing it with mobile odin,mobile odin does not flash boot-loaders so you are safe to downgrade etc.

you may find that you WiFi does not work when rom flashed with mobile odin, that means that the older boot loader is not compatible with the new rom.

Q:Can i install a custom recovery is this rom?

A: YES.
[Galaxy Tab 3 General] thebestiam:
If I'm rooted, can I just install regular? No custom recovery. Just stock everything except rooted.
[Galaxy Tab 3 General] abramq:
Any views to get this ROM for 3G version of Galaxy Tab 3 8.0 ?
[Galaxy Tab 3 General] HavokbyName:
did you brick your device in the process or did it just fail flashing & error out, or did it work but only flash 4.2 system leaving new bootloader intact?

so with this finding, just to be clear on this, no custom roms can be used for those who upgraded with new bootloader?

would it be possible to restore 4.2 rom backup of only system.img in custom recovery or will it not boot?

sorry for lots of q's
[Galaxy Tab 3 General] faria:
Yes.
[Galaxy Tab 3 General] faria:
Yes I got what is called a semi brick when trying to downgrade the rom when flashing the bootloader partition. This is easily remedied by going into download mode and flashing kit kat.

The good news is once you got the new bootloader installed, it will be virtually impossible to brick your device by conventional means.

Yes, locked bootloader means you can't have custom kernels, but you can have customs recoveries and roms.

In theory yes, but as far as I know only bootloader above 4.3 are compatible with kit kat rom, it may work but you may find that certain drivers will nor work, like loss of wi-Fi may occur. I Know this from my experiences with the note 2 and s4.
[Galaxy Tab 3 General] faria:
As far as I know, the 3g version of this rom has been out for several weeks acording the the interwebs.
[Galaxy Tab 3 General] abramq:
Unfortunately no Sir :(

We have only 4.2.2

Hope Samsung will no forget about us...
[Galaxy Tab 3 General] faria:
http://www.android.gs/flash-officia...xuana1-firmware-for-samsung-galaxy-tab-3-8-0/
[Galaxy Tab 3 General] errol19:
Yes I have just downloaded KITKAT 4.4.2 for my GALAXY Tab3 8.0 LTE SM-T315

Country: Baltic

PDA: T315XWUANA1

From sammobile

Link here

Sorry this link is still 4.2.2 jellybean link removed
[Galaxy Tab 3 General] HavokbyName:
UPDATE

[MENTION=283695]faria[/MENTION]

ok, just restoring 4.2 system.img from twrp backup doesn't work, doesn't boot, blank screen after initial samsung logo, didn't try restoring 4.2 boot.img with it though, thought that had something to do with bootloader but reading up it doesn't appear to, so if i restored that as well maybe it would boot?

flashing custom roms like cm11.0 is still possible as you say & seems to work just fine using this new bootloader, even shows blackhawk kernel in settings/about, should this be possible as its custom kernel?

i didn't have to do anything at all different than when i was on 4.2, just flash custom rom through recovery as normal

no new entries in odin/download mode info screen, all lines still the same

now i don't feel so bad upgrading
[Galaxy Tab 3 General] faria:
[MENTION=5909763]HavokbyName[/MENTION]

Please download Device info from the playstore byjphilli85, run it and post your kernel version an boot-loader version.

I would not be suprised if we can also flash custom kernels to the tab as the Knox version the device have seems to be a watered down version.

Thanks for the feedback.
[Galaxy Tab 3 General] abramq:
No, this is for T315 model (LTE). This is not the same as T311 (3G).

Anyway thanks for your reply! :)
[Galaxy Tab 3 General] HavokbyName:
here, running latest cm build to date:
[Galaxy Tab 3 General] faria:
HA, my mistake, Samsung and their numbering system makes me dizzy :D
[Galaxy Tab 3 General] faria:
Well its official, custom kernels are supported!:laugh:

the only thing we cant change is the bootloader, but at this stage who cares!

Many thanks.
[Galaxy Tab 3 General] faria:
Here is an unexpected suprise...

If you happen to flash cf-auto-root after flashing a custom recovery the device reverts back to official status:good:

Clearly samsung did not want their developers to waste much time in the firmware:D:D:D:D
[Galaxy Tab 3 General] HavokbyName:
just wanted to clarify an earlier post i made, going back to 4.2 is possible if you have a backup of it in twrp or other recovery, i just restored a 4.2 system & boot image and everything works as normal, even goes back to 4.2 kernel, at least there is minimal issue with this release, full knox would have been a real headache
[Galaxy Tab 3 General] smanq:
I'll try to recap for clarifying:

1. We can flash the stock 4.4.2 ROM through Odin

2. Now we can flash a custom recovery (TWRP_T31x_r3.tar)

3. We can finally flash cf-auto-root.

With this 3 steps we will have a TAB3 8.0 with stock 4.4.2, rooted, with custom recovery and official knox status, right?

:)
[Galaxy Tab 3 General] ketut.kumajaya:
Please give me KitKat "cat /proc/cmdline" output. Though I have experience making WiFi only ROM working on 3G device, for now I will patiently wait for Samsung release.
[Galaxy Tab 3 General] ketut.kumajaya:
One possible minimal issue is offline charging will always reboot to normal mode.
[Galaxy Tab 3 General] HavokbyName:
yeah...

attempting to charge whilst device is powered down using old 4.2 with new bootloader results in a grey battery icon center screen with a static circle, static icon & screen never goes off, not so good, guess that's one issue just found using older release with new bootloader, so offline charging isn't so friendly

same goes for custom rom, just checked with cm11

with stock 4.4, it has no such issue, not surprising, offline charging acts normally with green battery filling up & loading animation, 5 dots

---

[MENTION=4021423]ketut.kumajaya[/MENTION]

here's kitkat "cat /proc/cmdline" output

console=ram loglevel=4 sec_debug.level=0 sec_watchdog.sec_pet=5 androidboot.debug_level=0x4f4c sec_log=0x200000@0x46000000 sec_tima_log=0x200000@0x46202000 sec_avc_log=0x40000@0x46404000 s3cfb.bootloaderfb=0x5ec00000 lcdtype=2049 consoleblank=0 lpj=3981312 vmalloc=176m oops=panic pmic_info=67 cordon=540b54ba3baeca9400db9ee8ca8a55ca connie=SM-T310_OPEN_EUR_7de22521b2ab8773703e844dacabe390 androidboot.emmc_checksum=3 androidboot.odin_download=1 androidboot.bootloader=T310XXUBNE9 androidboot.selinux=enforcing androidboot.warranty_bit=0 androidboot.sec_atd.tty=/dev/ttySAC2 androidboot.serialno=000000000000000 snd_soc_core.pmdown_time=1000
[Galaxy Tab 3 General] faria:
Yes, but the custom recovery gets replaced by the one from cf-root that seems to be a officiant one.
[Galaxy Tab 3 General] faria:
In that case then should be possible to downgrade to official 4.2 by simply removing the bootloader partition from the .tar file.

This is a 5 minute job in Linux with the right commands.
[Galaxy Tab 3 General] thebestiam:
Can I manual update with this to kitkat??
[Galaxy Tab 3 General] faria:
New fetures

Anyone interested on this in their tablet?:laugh::laugh::laugh:

Ported Quick connect and s finder on tab 3 8.

Samsung actually did not include the feature in the kitkat update , in a device that actually has the hardware for it! Up yours SAMSUNG!
[Galaxy Tab 3 General] Smokey Mc Pot:
Nice one!

Can you share the download links ?
[Galaxy Tab 3 General] faria:
I'm still working on it, s finder is crashing, will upload a soon as I can.
[Galaxy Tab 3 General] ketut.kumajaya:
[MENTION=5909763]HavokbyName[/MENTION] I found:

New entry:

sec_tima_log=0x200000@0x46202000

sec_avc_log=0x40000@0x46404000

androidboot.selinux=enforcing

androidboot.warranty_bit=0

androidboot.sec_atd.tty=/dev/ttySAC2

Missing entry:

lpcharge=0

lpcharge mean low power charging. Why no androidboot.mode there? CM kernel still compatible to the old bootloader https://github.com/kumajaya/android...mmit/97e454051b3364deafcc47a0e76a3a4fae29c356 but for the new bootloader, maybe init process need to be changed.
[Galaxy Tab 3 General] HavokbyName:
not sure, don't know much about this stuff, that was the full output from that file, are these related to the new bootloader or kernel?
[Galaxy Tab 3 General] thebestiam:
Thanks for replying, By updating from Stock 4.2.2 to 4.4.2, Will i be able to keep ALL my data or it will reset the tablet?
[Galaxy Tab 3 General] smanq:
Flashed stock 4.4.2 ROM (Odin) and I haven't lost my data and settings.
[Galaxy Tab 3 General] thebestiam:
Thanks :), Was it rooted or anything?
[Galaxy Tab 3 General] smanq:
Done, but now the knox status is custom, not official. The recovery is that from cf-root... I'll think for a solution if I'll need it, now I like more to have root and custom recovery :cool:

---------- Post added at 12:29 AM ---------- Previous post was at 12:26 AM ----------

You need to root it, it's a real stock ROM.
[Galaxy Tab 3 General] DigitalMD:
I'd be cautious about installing the OEM 4.4.2 . With a locked bootloader, you may find that you cannot revert and trying to run any non-stock such as AOSP ROM may not work well, especially when they got to 4.4.3 or 4.5 android.

I haven't tried this so, I am just cautioning you based on experience with S3 and S4 locked bootloader. Just remember that once you have a locked bootloader on a Samsung, its forever in most cases. There will be no unlock coming later.

For those of you that have already loaded this update, if you have tried reverting or running AOSP, please check all the hardware functions, especially cameras, wifi, bluetooth etc. and lets us know if they work correctly.
[Galaxy Tab 3 General] ketut.kumajaya:
Kernel command line came from the bootloader.
[Galaxy Tab 3 General] HavokbyName:
From what I can tell all or main functions seem to be working as before on custom roms; wifi, bluetooth, camera (same small video issues as before) & sound

with this new bootloader, installing custom roms, recoveries & kernels is still possible as before, only you can't downgrade to 4.2 with odin unless you remove older bootloader files from tar beforehand, restoring 4.2 system & boot images from twrp/cwm backup is fine although issue below persists unless on stock 4.4

downside is offline charging now doesn't work correctly on anything except stock 4.4 screen stays powered on with battery icon sitting static forever
[Galaxy Tab 3 General] smanq:
Just for information, after variuos flashes (root, custom recovery, stock based ROM), I've flashed stock 4.4.2 (Odin): the current binary and status returned Official!

:)
[Galaxy Tab 3 General] :
Yeah there doesn't seem to be a KNOX aware bootloader in this firmware version. If you have flashed it, your pretty much safe warranty wise just as before as the binary can be reset.

NOTE: I'd still be very wary of flashing any future 4.4.2 firmwares though, it might come later in other regions or updates & bring a more locked down bootloader & with a warranty voiding KNOX flag, not saying that will happen but it's a possibility.

As it stands the only thing you can't do is downgrade the new bootloader, but installing custom ROMs, Recoveries & Kernels all still seem possible for now, there's the offline charging bug as reported if you use the older 4.2.2 or custom ROMs such as CM11.0 that use non stock Kernels, many others have experienced this issue with newer bootloaders in combination with older ROMs, same on Note 8.0 for some users.

Not sure if it can ever be fixed.
[Galaxy Tab 3 General] DarkSide®:
anyone tried to root with "kingo" or Towelroot 2?
[Galaxy Tab 3 General] :
Towelroot v1 & v2 doesn't work on Tab 3 8.0, there seems to be an issue with it not working on Exynos based devices, not sure on Kingo.
[Galaxy Tab 3 General] dparrothead1:
I believe it's more of an issue with 4.4. Towelroot nor Kingo works on the Mega 6.3 anymore once it has been upgraded to 4.4.
[Galaxy Tab 3 General] trazfer:
Try the india build
[Galaxy Tab 3 General] DarkSide®:
ITV kitkat FW roll out

problem i have download the fw but the update fail....tab not rooted