yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S7 Edge Questions and Answers] bigdxp:
thank you very much for your reply! what I I ended up having to do was finding a STOCK ROM and had to flash it with that using Odin. (mind you it dosent seem to be quite the same??) anyway, it worked thank GOD! but i'm still left wot one question? is it possible to ROOT my S7? Im thinking no! :(
[Samsung Galaxy S7 Edge Questions and Answers] gamesz2:
Flash twrp with odin and in twrp flash supersu

Twrp you can find in google it...... flash it with odin 3.12.3
[Samsung Galaxy S7 Edge Questions and Answers] bigdxp:
well thank you very much sir! as soon as I get the chance I will give this a try! and AGAIN I want to thank EVERYONE on here who help me out! :)
[Samsung Galaxy S7 Edge Questions and Answers] Hydranize:
Folks I tried to root my phone like the OP and have the same issues going on. Only difference with me is I can get into the blue ish download screen and also get to the area where I can perform a factory reset. This being said I only tried to root my phone to try to recovery videos I had mistakenly deleted using App - Undeleter. However this App will only work if the phone has been rooted. I used Odin and the correct CF file.

At this point the phone will go pass the Galaxy S7 Edge screen then vibrates a couple of times before it stops at the Samsung wording screen. When the phone vibrates its almost as if its looping or having an issue with booting up. I would really really appreciate any kind of help, and also if certain files is needed for me to fix my issue if someone could please post the links to download them.

I can't get into my phone at this point but I can access the bootloader, the blue ish download screen, and also still use ODIN, as well as have access to my SD card.

Once again any help would be greatly appreciated in every way.

---------- Post added at 02:48 AM ---------- Previous post was at 02:18 AM ----------

UPDATE: Folks I can no longer access the black bootloader screen as I tried once again to root things with ODIN and now the only thing I have access to is that blue ish download screen when pressing the power button, the vol. down button and the home button.
[Samsung Galaxy S7 Edge Questions and Answers] testdummy1on1:
Bootloop

sound like you might be stuck in a bootloop because you did your ROM upload on ODIN incorrectly. there are three options in which you upload your ROM file that normally comes from a zip file. for various phones and ROM version you might have only one file to upload to ODIN in a specific location from the tree upload options. with some phones and ROMS from the zip file you may need to upload tree files, one to each of the upload options in ODIN but in a specific order. So take a step back and look at how to use ODIN For your Device and its specific ROM.

testdummy1on1@gmail.com

PS...im searching for and Android Developer as well as someone clued up wit Adruino and would like to join in a project to develop an SAMSUNG "3S" "Secure Smartphone System" this new angle wil provide zero security vulnerabilities.

Im from Somerset West, Cape Town, South Africa.

If anyone knows people with that experience please drop me a meal. currently we are 4guys just short those two
[Samsung Galaxy S7 Edge Questions and Answers] Fiyanef:
Thank you so much! i know that this is an old post, but i tried to root my new phone and i thinked that was hard bricked, but you saved my phone

P.S:Sorry if my english is not very good, but i am from argentina, a spanish-talking country.
[HTC 10 Questions & Answers] rurouniphana:
Hello guys,

My HTC 10 have a problem ?
[HTC 10 Questions & Answers] AB__CD:
Was it run while device was hot?

Is battery saver on?

Any heavy apps running in RAM (e.g. 3D games)?

Running non-stock SW?

Is your device the 652-powered 10 Lifestyle?

A large number of factors can cause device to slow down to benchmark apps. Try a cache wipe, if that doesn't fix it and all of your answers to the above questions were no, it is likely either a rogue app OR your HTC 10 is defective?
[HTC 10 Questions & Answers] rurouniphana:
I use the HTC 10 with the snapdragon 820 :)

I try again
[HTC 10 Questions & Answers] afuller42:
the HTC 10 throttles big time, before a test make sure the phone was not in use at all for a good while. honestly if you want the best result put it in the icebox for a few minutes to get it really cool, itll e a huge difference in scores
[HTC 10 Questions & Answers] SacredDeviL666:
either your device could have been in a very warm state or something hogging memory in backend....

give a reboot to your device wait for few minutes and then try again...

mine taken straight after a reboot....

my device was at 38*C....
[HTC 10 Questions & Answers] rurouniphana:
Yes... is better after reboot but... the snapdragon 820 is very instable finaly...
[HTC 10 Questions & Answers] SacredDeviL666:
well there is always room for improvement else the development of more powerful chips would be stuck at one model forever :D
[HTC 10 Questions & Answers] Mince69Meat:
it's not unstable, it's designed to throttle bk when under heavy load and running a benchmark is going to cause just that sort of load, it's a phone not a supper computer and as such it's ment to do short boosts to complete every day tasks that a typical user of a phone would do, if you want raw power (shorter phone life) then you will have to start disabling all the protection that's built in to keep the phone cool, I won't recommend it in the slightest, also remove everything you can like system apps, user ones too, logging functions and so on then you'll get the true proformance of the hardware.

understanding this is essential if your wanting to compare benchmarks or if your wanting out the box comparison then your going to need to know what's running and whats not going to be running after time while your phone settles down.

havd fun
[Galaxy Tab S2 Android Development] T_I:
I can't state this enough, this build is highly experimental. Don't start with these images unless you know exactly how to recover a device.

I've taken the sources of the T815, added the proprietary-files.txt I use (used the blobs from T715 stock image... these differ from T815), took the dtb.img from the image I have (test, don't know what the difference is with the one in git, diff reports they differ) and copied kernel config for T710. (enough I hope)

I'm very curious if this image boots, as I've copied the method used to transform T810 to T710. As there were loads of questions about a T715 being able to install T815 images, I've went ahead and tried this. Don't start using this image until you're absolutely user about what you're doing. (and how to recover, I expect the first build to fail)
[Galaxy Tab S2 Android Development] Edgrr000:
It seems to work fine except the orientation is wrong. does't seem to pick up the SIM either

I tried to extract the log but it came our blank :(

https://drive.google.com/open?id=0B1GqV5PqFKEXcmZvdjFEYWctUUU
[Galaxy Tab S2 Android Development] T_I:
Drat, forgot the rotation of the T815 system.prop. T715 doesn't need it. Will fix that one. (Unexpected)

For the sim, I expect we'll need to be either very lucky or find a developer that has the device to solve this one.

I'm not seeing the 'no network' error. This could explain a bit. Will try a build from scratch.
[Galaxy Tab S2 Android Development] Edgrr000:
Great,

Let me know if you need anything on my side, all I can do is test
[Galaxy Tab S2 Android Development] T_I:
Recompiled, killed of the system.prop setting which rotates the screen (T810/5 only, don't know why it was there, was sure I had deleted it) and foudn a ril related binary I was using from the T815 build. Replaced that with the T715 one. Upload is running.

Edit: Upload finished, updated OP. Curious if rotation is ok now (should be) and if gsm now works.
[Galaxy Tab S2 Android Development] Philippovitsch:
Hey... did a quick testing session on it... Orientation and modem is working on the latest version! Cameras are working as well. Wow I'm very impressed! Thank you so much!
[Galaxy Tab S2 Android Development] T_I:
Ehm, the cameras are working? I'm curious about the mic. If that works as well, then I can't think of issues the device still has. This would mean the device is ready for nightlies...
[Galaxy Tab S2 Android Development] Philippovitsch:
Yeah... Front- and Backcam are working... xD Used Soundrec. to test the mic, it's working ;) Will use my other SIM-Card tomorrow to do some Test-Calls and SMS to try that as well.

Some things i noticed so far is that the device seems to be very slow sometimes... Installed just a couple of apps, which took me about half an hour and the Wifi is very slow sometimes. Vibration ist also not working.

And the device is still shown as SM-T815 in the device settings. ;)

But except that it seems to be very stable until now! Once again I'm very impressed :D

LG Phil
[Galaxy Tab S2 Android Development] saleappeal:
nach flash incomparable

Hallo, ist das Rom nun für T715 oder T710. Besitze SM-T715 und lässt sich nich flashen drauf ist Android 6.0.1 by Jafangie

Danke

Hello, the Rome now for T715 or T710. Possession SM-T715 and is nich flash it is Android 6.0.1 by Jafangie

thank you
[Galaxy Tab S2 Android Development] Edgrr000:
Everything works?

SMS

Calls

Wifi

Rotation

Mic

Speakers

I couldn't test for LTE, didn't check bluetooth either. It feels pretty solid except 2 things.

1. settings is missing the mobile network option to select APN, Mode, etc.

2. it is somewhat sluggish, lags quite often.

I would consider it a daily driver if it weren't for the annoying lag.

Fantastic job!! i've attached some logs, hopefully they can be useful
[Galaxy Tab S2 Android Development] Philippovitsch:
Ist für T715 - probiere es mal Schritt für Schritt genau wie im 1.Post beschrieben, so sollte es funktionieren ;)

It's for T715 - try it step-by-step like in the 1st post mentioned, that should be working.

----------

Did a little bit more testing today:

- Bluetooth seems to be working - could receive and send files from/ to another android phone. As I don't have a bluetooth headset, I can't test it yet.

- SMS sending and receiving is working - just one little bug: When I send a SMS, I get a a notification, that the Message could not be sent, but it's arriving on the other device.

- Calls are partially working - I can make calls and receive calls, but the mic and loudspeaker are only working, when I receive a call. If I call someone, the other side can't hear me and I can't hear him. I also can't use the "earphone", just the loudspeaker is working. Headset not testet yet.

- GPS is partially working - I get a GPS signal, but it seems to be a little bit weak, because I can't get an exact location.

- Mobile Data (LTE) is working for me

- More testing on the camera - Video recording is working (with sound), couldn't find antything, that wasn't working here

So I couldn't find any big things 'till now.

LG Phil

---------- Post added at 18:18 ---------- Previous post was at 18:08 ----------

I found that settings in the data usage section. Click the 3 dots in the upper right corner, there you'll find an option "Cellular networks", where you can select APN etc.
[Galaxy Tab S2 Android Development] T_I:
Ok, started with the steps to get this build in nightlies. Build is uploaded, OP is updated. Would be nice if major functions work, then it can be moved to nightlies, so others can benefit from the images.
[Galaxy Tab S2 Android Development] Philippovitsch:
Got stuck on samsung bootscreen on the latest build after clean flash.

LG Phil
[Galaxy Tab S2 Android Development] T_I:
Ok, rebuild with the blobs from TheMuppets (used by cm) and clean build again. Should work, but results with T710 indicate it's again non-boot. Could someone test and confirm (pref not confirm, but we'll have to test)
[Galaxy Tab S2 Android Development] Philippovitsch:
After Samsung bootlogo I ended up into a black screen.

LG Phil
[Galaxy Tab S2 Android Development] Edgrr000:
Yup, can confirm. It just goes into a black screen
[Galaxy Tab S2 Android Development] saleappeal:
cm-13.0-20160715-UNOFFICIAL-gts28lte.zip

cm-13.0-20160715-UNOFFICIAL-gts28lte.zip Läst not flash itself, whether from Rome or Stock of [ROM] [6.0.1] [T715] [UNOFFICIAL] CyanogenMod 13.0 for Tab S2 8.0 [EXPERIMENTAL]
[Galaxy Tab S2 Android Development] saleappeal:
Hello, the Rome now for T715 or T710. Possession SM-T715 and is nich flash it is Android 6.0.1 by Jafangie

thank you
[Galaxy Tab S2 Android Development] Pegaside:
Unfortunately I must also confirm it.

Thank you for the effort nonetheless! :good:
[Galaxy Tab S2 Android Development] saleappeal:
Sorry, gibt es keine Antwort, warum sich Cm 15 sich nicht auf das SM - T 715 flashen lässt.[emoji23] (Black Screen) bzw. von Cm 12 auf Cm 15 [emoji35]

Danke für eventuelle Antwort

Sorry, there is no answer why CM15 not on the SM - can flash T 715th (Black Screen) or Cm 12 Cm 15

Thanks for any reply
[Galaxy Tab S2 Android Development] T_I:
Sorry, but you lost me, there is no cm 15, only 13. (At least for the T715, for the T710 we also had a cm-12). The image last image 20160712 boots. (well, both boot, but the incorrect working one has the screen rotated relative to the touchscreen)
[Galaxy Tab S2 Android Development] saleappeal:
SORRY, The Rome runs very poorly, sometimes called experimental.

Long load times, telephony very bad this is my personal opinion.

Question: why do not we continue working on the development, CM is for many the ne plus ultra.Es puts a lot of work behind it is known to me, sorry but not wenns runs.

Next improve would be good.
[Galaxy Tab S2 Android Development] DarthGenius:
Installed it today, but latest build doesn't work at all, just black screen, so had to install the previous one. A bit slow but it is OK for experimental. Camera and LTE works fine, but Vibration doesn't work at all.

Will wait for updates :)
[Galaxy Tab S2 Android Development] T_I:
Sorry, but the development was blind and is stuck. Unless there is someone with the device and some development skills willing to work on this, I'm afraid there won't be much improvement.
[Galaxy Tab S2 Android Development] samsung_xoom:
if we had more help with the t710 would be great ,t_i not sure what you did with the last compile but wow the differences, thats the only one i couldnt get to boot at all no matter what i did, which previous build did you go back to, and ill try to work with that one to optimize.

---------- Post added at 12:25 AM ---------- Previous post was at 12:24 AM ----------

hmmm guess im not allowed to quote people now (again)
[Galaxy Tab S2 Android Development] Katzenstreu:
Hi,

thanks for your work. I'll test this ROM!

But the upper sentence is wrong, isn't it? "SM-T710"?!

Best regards

Tim
[Galaxy Tab S2 Android Development] Philippovitsch:
[MENTION=4557146]T_I[/MENTION]

I had a little bit spare time today and did some compiling. I used your latest gts28lte device sources and blobs (TheMuppets) on git, the gts2-common and kernel sources from CM.

I came to the same result as for the T710. Got stuck into a black screen. What worked for me is flashing the boot.img via TWRP from the latest working version (cm-13.0-20160612-UNOFFICIAL-gts28lte.zip) to get to the CM bootscreen.

Is there anything I can do to help you?
[Galaxy Tab S2 Android Development] T_I:
The biggest problem I have is I can't figure out what is the difference in sources between the last booting image and the first non-booting. It looks like there is a kernel issue. Did you get a last_kmsg file in /proc after the failed boot?

Reboot to twrp after the device hangs and via advanced -> shell and

cp /proc/last_kmsg to /ext_sdcard/.

copy it to the external sdcard before you restore.

I'd almost think I'm having issues with the device tree.
[Galaxy Tab S2 Android Development] Philippovitsch:
I have 3 last_kmsg logs for you now.

The 1st is my latest build untouched, the 2nd is my latest build with the boot.img from your last bootable build (20160612) and the 3rd is your last bootable build untouched.

I hope it will help you.
[Galaxy Tab S2 Android Development] T_I:
It should be SM-T715. (corrected it in OP)

I'm recompiling the T710 tree for cm-14.1 . I'll dive into these last_kmsg's to see if they state anything else then 'starting kernel'. (had the same issue on T810, completely new tree helped there)
[Galaxy Tab S2 Android Development] naty106135:
well first of all wanted to thank you! - great job mate!! :) .

so i have tried installing cm-13.0-20160715-UNOFFICIAL-gts28lte.zip on my SM-T715Y (which is exactly the same as WITHOUT Y) and it failed (Blackscreen in boot)

also i tried to install cm-13.0-20160712-UNOFFICIAL-gts28lte.zip - the device booted and seems to functioning correctly.

i installed the rom because i thought it my solve my GPU issue .. but it didnt ;( ( https://www.youtube.com/watch?v=mwtFb_pY_NQ )

maybe you can tell me if its Kernel issue or physical issue ? (it's Brand New SM-T715Y)

anyway , good job mate!! .
[Galaxy Tab S2 Android Development] donky kong 017:
thank you guys for the effort. i would love to see more development on this matter. i am not a developer, but i would love to help where i can.
[Galaxy Tab S2 Android Development] nostupidthing:
Pleaaaaaase! :D
[Galaxy Tab S2 Android Development] T_I:
I'm busy with LineageOS, that works now for T810. Also we're rewriting code zo we can compile the dtb for the devices. With a compiled dtb, we'll never have a mismatch between kernel and dtb (as they come from the same sourcetree).

Can someone with a T715 look into /proc/last_kmsg after a 'reboot bootloader' for the following section:

<device info>
chip_id: 0x00001539
platform_id: 0x00003138
subtype_id: 0x36480ee3
hw_rev: 0x00000008

I'm curious to whether this is the same on T710 and T715 or isn't. (the info above is from T710)
[Galaxy Tab S2 Android Development] Philippovitsch:
Got the same result as for T710 (cm-13.0-20160712-UNOFFICIAL-gts28lte.zip)

<device info>
chip_id: 0x00001539
platform_id: 0x00003138
subtype_id: 0x36480ee3
hw_rev: 0x00000008
[Galaxy Tab S2 Android Development] metterschling:
[MENTION=4557146]T_I[/MENTION] here is the information gathered on a T715:

<device info>

chip_id: 0x00001539

platform_id: 0x00003138

subtype_id: 0x36480ee3

hw_rev: 0x00000008
[Galaxy Tab S2 Android Development] Philippovitsch:
Did a repo sync on all sources (gts210lte -> gts28lte and samsung_dtbh.h from gts28wifi), but couldn't get it compiled as an error occoured:

mkdtbhbootimg: model_info-chip of /home/philipp/Android/LineageOS/out/target/product/gts28ltexx/obj/KERNEL_OBJ/arch/arm/boot/dts//exynos5250-smdk5250.dtb is of invalid size, skipping
mkdtbhbootimg: model_info-chip of /home/philipp/Android/LineageOS/out/target/product/gts28ltexx/obj/KERNEL_OBJ/arch/arm/boot/dts//exynos4412-odroidx.dtb is of invalid size, skipping
mkdtbhbootimg: model_info-chip of /home/philipp/Android/LineageOS/out/target/product/gts28ltexx/obj/KERNEL_OBJ/arch/arm/boot/dts//exynos4412-smdk4412.dtb is of invalid size, skipping
mkdtbhbootimg: model_info-chip of /home/philipp/Android/LineageOS/out/target/product/gts28ltexx/obj/KERNEL_OBJ/arch/arm/boot/dts//exynos5440-ssdk5440.dtb is of invalid size, skipping
mkdtbhbootimg: model_info-chip of /home/philipp/Android/LineageOS/out/target/product/gts28ltexx/obj/KERNEL_OBJ/arch/arm/boot/dts//exynos5250-arndale.dtb is of invalid size, skipping
mkdtbhbootimg: model_info-chip of /home/philipp/Android/LineageOS/out/target/product/gts28ltexx/obj/KERNEL_OBJ/arch/arm/boot/dts//exynos4210-universal_c210.dtb is of invalid size, skipping
mkdtbhbootimg: model_info-chip of /home/philipp/Android/LineageOS/out/target/product/gts28ltexx/obj/KERNEL_OBJ/arch/arm/boot/dts//exynos4412-origen.dtb is of invalid size, skipping
mkdtbhbootimg: model_info-chip of /home/philipp/Android/LineageOS/out/target/product/gts28ltexx/obj/KERNEL_OBJ/arch/arm/boot/dts//exynos5440-sd5v1.dtb is of invalid size, skipping
mkdtbhbootimg: model_info-platform of /home/philipp/Android/LineageOS/out/target/product/gts28ltexx/obj/KERNEL_OBJ/arch/arm/boot/dts//exynos5433-gts210_eur_open_06.dtb is invalid, skipping
mkdtbhbootimg: model_info-chip of /home/philipp/Android/LineageOS/out/target/product/gts28ltexx/obj/KERNEL_OBJ/arch/arm/boot/dts//exynos4210-smdkv310.dtb is of invalid size, skipping
mkdtbhbootimg: model_info-chip of /home/philipp/Android/LineageOS/out/target/product/gts28ltexx/obj/KERNEL_OBJ/arch/arm/boot/dts//exynos4210-origen.dtb is of invalid size, skipping
mkdtbhbootimg: model_info-chip of /home/philipp/Android/LineageOS/out/target/product/gts28ltexx/obj/KERNEL_OBJ/arch/arm/boot/dts//exynos5250-snow.dtb is of invalid size, skipping
mkdtbhbootimg: model_info-chip of /home/philipp/Android/LineageOS/out/target/product/gts28ltexx/obj/KERNEL_OBJ/arch/arm/boot/dts//exynos4210-trats.dtb is of invalid size, skipping
mkdtbhbootimg: unable to locate any dtbs in the given path
error: could not load device tree blobs '/home/philipp/Android/LineageOS/out/target/product/gts28ltexx/obj/KERNEL_OBJ/arch/arm/boot/dts/'
device/samsung/gts2-common/mkdtbhbootimg.mk:7: die Regel für Ziel '/home/philipp/Android/LineageOS/out/target/product/gts28ltexx/boot.img' scheiterte
make: *** [/home/philipp/Android/LineageOS/out/target/product/gts28ltexx/boot.img] Fehler 1
make: *** Auf noch nicht beendete Prozesse wird gewartet ...

Edit: got a build compiled, same result as for T710 - stucked on Samsung bootscreen
[Galaxy Tab S2 Android Development] Edgrr000:
Trying to build lineageOS, getting 4 errors

device/samsung/gts28lte/ril/telephony/java/com/android/internal/telephony/SlteRIL.java:271: error: cannot find symbol
+ IccUtils.bytesToHexString(dc.uusInfo.getUserData()));
^
symbol: variable IccUtils
location: class SlteRIL
device/samsung/gts28lte/ril/telephony/java/com/android/internal/telephony/SlteRIL.java:401: error: method does not override or implement a method from a supertype
@Override
^
device/samsung/gts28lte/ril/telephony/java/com/android/internal/telephony/SlteRIL.java:441: error: method processUnsolicited in class RIL cannot be applied to given types;
super.processUnsolicited(p);
^
required: Parcel,int
found: Parcel
reason: actual and formal argument lists differ in length

/home/ed/LineageOS/kernel/samsung/gts2/security/tima_uevent/tima_uevent.c:217:1: fatal error: opening dependency file security/tima_uevent/.tima_uevent.o.d: No such file or directory
module_exit(tima_uevent_exit);
^
compilation terminated.
/home/ed/LineageOS/kernel/samsung/gts2/scripts/Makefile.build:308: recipe for target 'security/tima_uevent/tima_uevent.o' failed

:confused:
[Galaxy Tab S2 Android Development] T_I:
It's the same kernel witn the same issue. As soon as T710 boots, T715 will also boot and the other way around.

Sent from my SM-T810 running lineage-14.1
[Galaxy Tab S2 Android Development] T_I:
I will correct my sources for LineageOS, device name is incorrect for usage wiyh gts2-common. Named it gts28lte, gts2-common expects gts28ltexx. Biggest issue is still tne kernel though. Need to take the working boot.img apart to fets=ch the kermel/dtb config to try a rebuild witn those.

Sent from my SM-T810 running lineage-14.1
[Galaxy Tab S2 Android Development] ish_123:
Hello,

Is it possible to do a build for the SM-T713 model? I tried flashing the version linked here, but TWRP gave me an error saying something like, "this build is for the gts28wifi or gts28wifixx, this device is a gts28vewifi".

I definitely realize the disclaimer at the beginning of this thread saying it's for the T715, not the T713, but I wanted to try anyway.

If not possible, do you know what is different about the T713 that makes it not work? I am new to this whole thing and curious. Thank you!
[Galaxy Tab S2 Android Development] T_I:
The main difference is the board, wifi has exynos, vewifi an msm board. I received nice donation, together with another developer. We're now working on the T813 image. With some luck we can find a dev with the t713 and let him convert to that model.

Sent from my SM-T813 running L1ghtning 6.0