yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] lirong:
I recently upgraded to GoldenEye 53.

Ever since installing this ROM I seem to be having issues with LTE reception. It's not as consistent as it used to be. Sometimes I won't be able to get data, and then if I turn mobile data off and on again using the control panel, it will start working again.

My baseband version is i337ucug0c3 in case that matters.

Any ideas?
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] SVTGuy02:
I have the exact same issue...... thinknig of updating Baseband to NJ4 as that seems to be one that alot of people are using!
[Galaxy S 4 Q&A, Help & Troubleshooting] techspark:
Hey guys, I am really fed up with the bugs and issues in stock 5.0.1 of s4 i9500 edition. Snapchat force closes every now and then, chrome crashes , wallpaper gets auto changed and so on.

I would like to know which would be the best rom that I can install which can be used a daily driver, I want to install it once and use it tension-free. Can you guys suggest which ones do you use as your daily driver, which gives the best performance and maximum battery life and should be based on lollipop 5.1

I am not really into changing roms so I would like this one to bug free and stable, I do not need any additional features.

Thanks!!
[Galaxy S 4 Q&A, Help & Troubleshooting] Strephon Alkhalikoi:
The best ROM is subjective, in that everyone's opinions are going to differ. The only way you're going to know which ROM is best for you is trying them out.
[Galaxy S 4 Q&A, Help & Troubleshooting] techspark:
Thanks for your reply. I actually wanted everyone's opinion so that I can know which ones are very stable and working great for them and then I can go ahead and try them and select the one out of them that works best for me :)
[Galaxy S 4 Q&A, Help & Troubleshooting] 0_RoXoR_0:
Euphoria rom is best as if i think so....

But if u want to use samsung apps, airview, air gestures halcyon rom would be nice

For better battery backup go for stock rom which is somewhat stable now.
[Galaxy S 4 Q&A, Help & Troubleshooting] m3a1xx:
Aurora is the best

All air functions work fine and some of the note features are there and in adition very stable

after many roms tests
[Galaxy S 4 Q&A, Help & Troubleshooting] thundastruck:
Been using Aurora V2 - crashed yesterday while in a call. A big NO for me, but otherwise the rom was more than satisfactory overall. I have automatic call record enabled, so could've been that... not sure.

Wanna try Halcyon next...
[Galaxy S 4 Q&A, Help & Troubleshooting] krasCGQ:
For me,

AOSP-based ROM: GearCM and everything based on that ROM

TW-based ROM: Doctor's S6 port/Halcyon/MBP with VoLTaqe Kernel

Sent from my ASUS_Z00AD
[Galaxy S 4 Q&A, Help & Troubleshooting] Ankit0141:
My vote is for darklord...
[Galaxy S 4 Q&A, Help & Troubleshooting] jordann_f1:
AOSP : Gear CM, Resurrection Remix and Euphoria

T.W. : Aurora S6/S6E V3.0, Dark Lord and Halycon.

Kernal : VoLTaqe Kernel and Light-Weight-Kernel.

Doctor's Rom is also good but somehow didn't work good for me.

**Happy to Help**
[Galaxy S 4 Q&A, Help & Troubleshooting] eyedontslaydraguns:
Cyanogenmod. Very stable and fast.
[Galaxy S 4 Q&A, Help & Troubleshooting] Irumar:
Uptill now, am on stock rom, which has been stable . However, waiting for CM 13, as Android 6 is not going to come for s4. Problem for i9500 which has exynos chip and as yet unreleased source code, CM 13 will be delayed. Just released cm 13 for snapdragon i9505. Running CM 12.1s in i9300, s3 for the past year. Very stable.
[Honor 7 Q&A, Help & Troubleshooting] rmonkey100:
Having same problem with notifications not coming through if the app is closed (Snapchat, Whatsapp etc.) they only come through if the app is left open in the background!

Any solutions yet?
[Honor 7 Q&A, Help & Troubleshooting] N!KE26:
Best one i have done is to root your phone and move the apps to system/app folder.
[Honor 7 Q&A, Help & Troubleshooting] Fenderson_Khor:
any idea of how to move the apps to system/app folder? sorry, i'm new user for huawei device
[Honor 7 Q&A, Help & Troubleshooting] N!KE26:
Is your phone rooted?
[General Questions and Answers] roopal:
I am trying to develop an android chat application which and through this I want to stream video from one device to android device over wifi.....

Resources are available for all other methods except android to android video streaming over wifi.........

Please revert back if anyone can help me.........
[Galaxy Note 10.1 (2014 Edition) Android Developmen] karthikrr:
UPDATE 2: Tutorial and Patched Boot.imgs available here.

UPDATE: Chainfire's suggestion to patch sepolicy in the ramdisk for Samsung LL ROMS works perfectly. For unknown reasons, ODIN flash would not work, but flashing the patched boot.img with TWRP allowed me to successfully achieve root with a fully stock kernel and SEAndroid Enforcing. All the information you need is in the sources I quote below. Once I am confident that everything is working fine, I will create another thread with a concise guide and my patched boot.img for those who don't want to get their hands dirty. In the meantime, anybody who sees this should know that the same process can be done with the P605 as well, with your native ROM instead of a ROM from a different region. Also, stock kernel means no wifi dropping problems either!

[MENTION=336863]garyd9[/MENTION]

This thread is to discuss the possibility of rooting the Samsung Note 10.1 (2014 Edition) without resorting to a permissive kernel. The background information for this thread can be found from the following posts:

http://xdaforums.com/apps/supersu/wip-android-6-0-marshmellow-t3219344

Chainfire's method of patching the device's sepolicy with a reference device to give sudaemon the required permissions that open the doors for rooting and more.

http://xdaforums.com/showpost.php?p=63250893&postcount=26

garyd9's application of Chainfire's idea to the Note 5, which appears to have worked successfully.

http://xdaforums.com/showpost.php?p=63552454&postcount=2375

My attempt to replicate garyd9's method on the P607T, which failed.

http://xdaforums.com/showpost.php?p=63555137&postcount=2376

garyd9's recommendation on how to troubleshoot.

And finally the results from following Gary's advice:

This thread is started to continue exploring this option specifically for the Note 10.1 (2014 Edition). The idea is to achieve root by modifying only the ramdisk and not touching the kernel, and definitely NOT going to the extreme step of using a permissive kernel.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] garyd9:
Can you post a boot.img that's known good? I don't use kitchens, dining rooms, or even bathrooms. I use my own compiled tools... (Are you doing all this work in linux or using win-blows?)
[Galaxy Note 10.1 (2014 Edition) Android Developmen] garyd9:
I've attached "imgtools.zip." Within are the linux binaries I use for unpacking and repacking boot images. They should work under ubuntu 64-bit 14.04.

Here's some idea of how you might use them (again, linux..)

# assumes "boot.img" in the cwd is the original boot image.
mkdir stockboot
# unpack the boot image into a new directory called "stockboot"
unpackbootimg -i boot.img -o stockboot

That will dump a bunch of files into that new directory...

Now, to remake it:

cd stockboot
mkbootimg --kernel boot.img-zImage --ramdisk boot.img-ramdisk.gz --base `cat boot.img-base` --pagesize `cat boot.img-pagesize` --kernel_offset `cat boot.img-kerneloff` --ramdisk_offset `cat boot.img-ramdiskoff` --tags_offset `cat boot.img-tagsoff` --dt boot.img-dtb -o ../newboot.img

What that does is goes into the directory we unpacked the original image to, and then just puts it back together in the original directory under a new name (newboot.img.) For all the parameters, we just re-use the values and items extracted from the stock boot image. The new image won't be identical to the old one, but the sizes should be close.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] karthikrr:
tar of stock boot.img attached. Until Carliv's kitchen, all attempts were on Slackware 14.1. Only Carliv's was done on Win 10.

Will take a shot at it tomorrow with your binaries and post results.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] garyd9:
I'm not going to talk about that. I have a semi-religious belief that anyone using windows to manipulate linux kernel images is BEGGING for trouble. (It's not that I'm anti-windows. I'm just against mixing the platforms.)

Anyway, followed my own directions to unpack and repack your boot.img. I took the resulting newboot.img and zip'd it up (and attached it here.) This is NOT a TWRP/CWM flashable zip. It's just archived to save space (and make XDA's file manager happy.)

I didn't see any strange messages about non-standard images or anything like that. In fact, the process was outright boring.

(FYI, I might not be capable of responding to messages again until late tomorrow night or Sunday...)

~/temp$ unpackbootimg -i boot.img -o stockboot
BOARD_KERNEL_CMDLINE console=null androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 ehci-hcd.park=3
BOARD_KERNEL_BASE 00000000
BOARD_PAGE_SIZE 2048
BOARD_KERNEL_OFFSET 00008000
BOARD_RAMDISK_OFFSET 02000000
BOARD_TAGS_OFFSET 01e00000
BOARD_DT_SIZE 1574912
[Galaxy Note 10.1 (2014 Edition) Android Developmen] garyd9:
oh, that might not boot for you. my repack cmdline doesn't pull in the cmdline from the kernel unpack. Add something like this to the mkbootimg cmdline:

--cmdline "`cat boot.img-cmdline`"

(You might have to actually type out the cmdline inside the quotes instead)
[Galaxy Note 10.1 (2014 Edition) Android Developmen] SHM:
Not surprised :). Most tools available won't give this information. Its typically only available as a cosmetic feature. My work is derived from Xialou's as seen here but modified to work for Linux and ARM alike.

I have attached images showing me unpacking and repacking his stock boot.img from my device.

With that said, I have been researching this error, "unsupported dev_type", and most of what I have came across points to it being a specific issue with Odin itself. However, I can't really rule this out because his device does not have root so I presume he can't write the boot image to his boot partition using the dd command in a terminal to verify if it will boot up using this method. If it were to boot up then it would clearly point the problem towards the Odin program being used.

---------- Post added at 02:21 PM ---------- Previous post was at 01:59 PM ----------

[MENTION=5420874]karthikrr[/MENTION], when making an Odin compatible package you are using the command:

tar -cf

I don't own a Samsung device but I have helped build TWRP for some so given my experience shouldn't the command actually be:

tar -H ustar -c boot.img > Odin_boot.tar

Where Odin_boot.tar is the package used to install via Odin.

Please use that command i just shared with you and try again.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] karthikrr:
Short version: No luck!

Long version:

In all cases, just unpack stock boot.img and make new stock boot.img, no changes.

Gary, everything except for the ODIN flash was done on Linux for the following.

SHM, all tars created using your command.

1) Used Gary's tools following all instructions including cmdline to create garyboot.img and then .tar

2) Used SHM's tools to try again, this time with his tar cmd to create shmboot.tar

3) Found a mkbootimg binary in the P607T KK Source from Samsung's opensource portal. Used that to create P607Tboot.tar from the img unpacked by Gary's tools.

4) This might have been completely off-base, but ... Used xialou's mkboot-master source code; edited mkbootimg.c with the Non-Standard addresses from SHM's image above. Ran make to compile a new binary, used it to create recboot1.tar

5) umkbootimg from another toolset gave me a different set of addresses to change in the mkbootimg.c file, this time to change kernel offset, ramdisk offset and second offset. New binary again, after make clean and make, used it to create recboot2.tar

ODIN 3.10.6 failed with the same unsupport dev_type error with ALL of these images.

Tried the first two with ODIN 3.09, no difference, same error again.

Questions:

SHM, your image above, as well as the warning on umkbootimg both say Modify mkbootimg.c and try again ... Should I look into this more?

Is there ANY chance that the problem is not with mkbootimg, but with unpackbootimg?

SHM, you mentioned unsupport dev_type in context with ODIN problems. Where can I find more info on this? FWIW, I have never had ODIN problems before, flashing firmware updates and twrp on this tablet, as well as on my Note 2 phone. Can't think why only in this case, it should fail like this.

What are my alternatives to ODIN? Can I flash using twrp? I have never created a twrp flashable zip, so will go read up on that some now, but do you think it makes sense to try that? If not, are there any other methods of flashing to try before being absolutely sure the problem is with mkbootimg?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] SHM:
[MENTION=5420874]karthikrr[/MENTION], if you have the latest twrp for your device than there is something you need to try to see if in fact this is a problem with Odin specifically. I want you to take your boot.img that has been unpacked and repacked but don't make it into a tar. Leave it as an image. Boot up TWRP then select Install. At the bottom right of your screen will be a button that says, zip. If you click on it you will see it change to, image. This allows you to install either a flashable zip or flash a boot/recovery.img. Select to install the boot.img. The next screen will ask you to select either the boot or recovery partition based upon the image you chosen. In this case, choose the boot partition. Swipe to proceed. When done, reboot your system. If your device boots up successfully then your problem lays with Odin. Let me know if these instructions are a bit confusing.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] karthikrr:
No confusion, I even have all the imgs loaded on the device to try this. Two reasons I did not try it yet, perhaps you can clarify whether these are legitimate concerns:

1) TWRP is formally not out for LL on my device yet. I, like everybody else out there, is using the latest KK img on this device and it SEEMS to be working properly. The only noticeable difference I have seen is that it seems to take a lot longer to get into twrp than usual. But I made some 5 backups of the device yesterday and all of them seemed to be fine. Given this is not official for LL, I wasn't sure if it was wise to try to flash an image from twrp.

2) I was also concerned that PERHAPS Odin is doing me a favour and aborting the flash because there was something wrong, and that if I went with twrp and it flashed it without any problems, I might find that it killed my device. I was discussing this with a friend (no experience with Android flashing, but a developer who knows these things) and he said it was highly unlikely that this would happen, as long as the img I was flashing was within the size limit for my device, which I believe is 11mb. All the images are 10.5mb. Thoughts?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] SHM:
If the partition table between KK and LP does not vary on your device then it will be fine.

As for flashing a boot image to your boot partition via twrp, this will not brick your device. Worse case, device doesn't get past the bootloader or the boot animation. In this case, use twrp to install your stock boot.img to your boot partition.. If you have a backup of your boot image then restore that. Either way you will be OK.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] karthikrr:
IT WORKS!!!

Flashed a stock boot.img using TWRP to be safe, was fine. Patched the ramdisk again, created a new patchedboot.img using the binary I pulled from the P607T sources, crossed my fingers and flashed it with TWRP, the device booted successfully. There was a SEAndroid Not Enforcing; Set Warranty Bit Kernel message while it booted, but I don't care about Knox. Once I confirmed that it booted and worked alright, back to recovery, flashed SuperSU Beta 2.52, rebooted, and I HAVE ROOT!!!

No idea why Odin would fail to flash, but confirmed working with TWRP. Do you know what the policy is on me creating a thread and uploading my patchedboot.img for others to use? I am no developer, and I have no idea if the rules prohibit me from putting this up. I do know though that not everybody is going to go through this whole manual process to get root, and too many are resorting to permissive kernels to get root. Ideally, I will also repeat this process is someone sent me a P605 boot.img, so they too can have root with stock kernel. Just not sure where this thread should go, and if I can even make one.

In anycase, THANK YOU SO MUCH BOTH OF YOU FOR TAKING THE TIME TO WALK ME THROUGH THIS! Much appreciated :)
[Galaxy Note 10.1 (2014 Edition) Android Developmen] garyd9:
Glad you got it working. If you want to post the image, I'd suggest posting in the dev section for the device. (If it's just a repack of the stock kernel, don't use the original dev...) Yes, it is allowed to do that. Being that you aren't recompiling anything, there's no need for you to post any source code (but it might be nice to link to the source from samsung's site. We all know that Samsung doesn't update that anyway.)

Take care

Gary
[Galaxy Note 10.1 (2014 Edition) Android Developmen] karthikrr:
Thanks for the suggestions on how and where to post. I think I will take the time to write out a decent tutorial and then post it with this image in the dev forum. Im sure the P605 users will also want to do this with theirs, so they are not stuck with an unsecure kernel!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] SHM:
Good luck with your future endeavors. I'm currently fighting with sepolicy right now with my CM13 builds lol. Whole other battle right there haha.
[Android Apps and Games] MZ4Mobile:
Hi,

A new Zip code app to find any postcode in australia,

i'm sure you will find it helpfull and easy to use.

The app is free and can work offline so you can use it even when no internet connetion is available.

Yours comment are welcome.

https://play.google.com/store/apps/details?id=com.mz4mobile.australiapostcode&hl=en
[One (M8) Q&A, Help & Troubleshooting] janiber:
Hello Everyone!

I have problem with my HTC m8 and started to read in the forums, but could not figure out how to solve it.

Because:

Im using an old custom rom viperOne 1.8, on android 4.4.2 have S-ON and have an old TWRP 2.7.0.0 - (newer versions where just stuck on "Entering recovery...")

If i understood it right i have to upgrade the firmware, but i cant because of S-ON, tried Sunshine but it says "sunshine cannot function on devices which are set to debuggable".

So, if no S-OFF, cant do firmware update and cant get the latest rom etc. right?

Wanted to install the SkyDragon+M8+v+10.2+Sense+7 ROM and a firmware.

Could someone please tell me how to proceed or at least point me to the right direction?

(I would be really thankful for some exact versions or links to a file i have to use, not just like "you need to flash a stock firmware")

Some details:

(bootloader) version: 0.5

(bootloader) version-bootloader: 3.16.0.0000

(bootloader) version-baseband: 1.16.2133156.UA10G

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main:

(bootloader) version-misc: PVT SHIP S-ON

(bootloader) serialno: XXXXXXXXXXXXXXXX

(bootloader) imei: XXXXXXXXXXXXXXXXX

(bootloader) imei2: Not Support

(bootloader) meid: 00000000000000

(bootloader) product: m8_ul

(bootloader) platform: hTCBmsm8974

(bootloader) modelid: 0P6B10000

(bootloader) cidnum: T-MOB101

(bootloader) battery-status: good

(bootloader) battery-voltage: 0mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: c3d94491

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

Thanks !
[One (M8) Q&A, Help & Troubleshooting] ckpv5:
You have two options :

Option 1

1. Install a better version TWRP 2.8.1.0

2. Restore the 1.57.111.2 nandroid backup - download : https://www.androidfilehost.com/?fid=95747613655045642

3. Install the 1.57.111.2 stock recovery - download : https://www.androidfilehost.com/?fid=23622183712459364

4. Do multiple OTA installation up to the latest 4.19.111.3

5. install latest TWRP 2.8.7.0

6. install any ROM that you like or skip 5 & 6 if you want to keep it stock

Option 2

1. Download the 4.19.111.3 RUU zip - Download : https://www.androidfilehost.com/?fid=24052804347812799

then rename it to RUU.zip

2. Download htc_fastboot.exe - https://drive.google.com/file/d/0B8L4pkbzdlR3eTlJSjdKVEdHX1U/view

3. boot to bootloader and relock bootloader with command fastboot oem lock

4. put the RUU.zip and htc_fastboot.exe in your fastboot/adb folder

5. Run these command

fastboot oem rebootRUU

htc_fastboot.exe flash zip RUU.zip

6. re unlock bootloader with unlock_code.bin that you got from HTCDev

7. install latest TWRP 2.8.70

8. install any custom ROM that you like or skip 6 & 7 & 8 if you want to keep it stock

Note - flashing RUU zip and reunlocking bootloader will wipe your internal storage data, backup your important files like photos, musics & etc to PC before you proceed
[One (M8) Q&A, Help & Troubleshooting] janiber:
Thank you very much for your detailed and fast answer!

Option 2 sounds good.

So if i'm done with Stock install - as you described, and i want to upgrade to the new ROM , i still need to be s-off and flash a new firmware right ?
[One (M8) Q&A, Help & Troubleshooting] ckpv5:
No .. no need S-Off and no need new firmware because once you completed the process your device already on the latest firmware. You can install any lollipop based ROM.

To flash RUU.zip .. you need USB2.0 and latest HTC USB driver installed.

If not sure, download HTC Sync Manager - http://www.htc.com/us/support/software/htc-sync-manager.aspx

install it as it will install the latest HTC USB driver then uninstall the HTC Sync Manager but leave the driver.

Good luck and good night ..
[One (M8) Q&A, Help & Troubleshooting] janiber:
I think i've just bricked it. :eek:

Does nothing anymore :(

c:\adb>htc_fastboot.exe flash zip RUU.zip

sending 'zip'... (54311 KB) OKAY

sending time = 2.604 secs

writing 'zip'... (bootloader) adopting the signature contained in this image...

(bootloader) signature checking...

(bootloader) zip header checking...

(bootloader) zip info parsing...

(bootloader) checking model ID...

(bootloader) checking custom ID...

(bootloader) checking main version...

(bootloader) checking hboot version...

(bootloader) start image[hboot] unzipping for pre-update check...

(bootloader) start image[hboot] flushing...

(bootloader) signature checking...

(bootloader) [RUU]WP,hboot,0

(bootloader) [RUU]WP,hboot,99

(bootloader) [RUU]WP,hboot,100

(bootloader) ...... Successful

FAIL90 hboot pre-update! please flush image again immediately

FAILED (remote: 90 hboot pre-update! please flush image again immediately)

For "hboot-preupdate" response, restart the same procedure for device HT43HWM052

47...

< waiting for device >

sending 'zip'... (54311 KB)
[One (M8) Q&A, Help & Troubleshooting] janiber:
Ok, sorry working again.

The console hung, had to disconnect the phone and restart in a new console again.

:good:
[One (M8) Q&A, Help & Troubleshooting] ckpv5:
What is your downloaded size ? It seems too small. It should be 1.7gb

You have a S-On device, it won't brick. I'm too tired now .. I'll check tomorrow your progress.

You also can try to unlock bootloader again and go for option 1