Hello, i'm having a problem about my phone not recognizing my external keyboard. The keyboard is working on my computer and it used to work on my phone then suddenly my phone cant recognize it anymore although it gives power to it. Not sure if it's the OTG cable or my phone in general.
danny.worsnoop2828 said:
Hello, i'm having a problem about my phone not recognizing my external keyboard. The keyboard is working on my computer and it used to work on my phone then suddenly my phone cant recognize it anymore although it gives power to it. Not sure if it's the OTG cable or my phone in general.
Click to expand...
Click to collapse
Have you changed anything about the device between when it worked and now?
Does the kernel the device has now support OTG?
Sent from my SCH-I535 using Tapatalk
Droidriven said:
Have you changed anything about the device between when it worked and now?
Does the kernel the device has now support OTG?
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
No, i didn't change anything, i just use my phone the way i use it before.
danny.worsnoop2828 said:
No, i didn't change anything, i just use my phone the way i use it before.
Click to expand...
Click to collapse
You haven't applied any stock updates or anything? If it worked before then you've changed something in settings or something if you haven't updated the device.
It would help if you posted your device model number and the stock firmware version/build number that your device has. Then I can help you troubleshoot through the required steps for your device.
Droidriven said:
You haven't applied any stock updates or anything? If it worked before then you've changed something in settings or something if you haven't updated the device.
It would help if you posted your device model number and the stock firmware version/build number that your device has. Then I can help you troubleshoot through the required steps for your device.
Click to expand...
Click to collapse
Its a local phone here in the philippines.
Cherry Flare S3 Power Build Number is Lollipop SW04 08252015
I just checked for software update and it says that i have the latest version, i don't remember changing anything on the settings, but i'm quite sure i haven't
danny.worsnoop2828 said:
Its a local phone here in the philippines.
Cherry Flare S3 Power Build Number is Lollipop SW04 08252015
I just checked for software update and it says that i have the latest version, i don't remember changing anything on the settings, but i'm quite sure i haven't
Click to expand...
Click to collapse
You are missing the point about the update.
I'm asking if the device has what it had when you bought it or has it had a stock update applied at any time? If it was on one version when you bought it and the keyboard worked at that time but has had a stock update since then and now the keyboard isn't working then that could be what is giving you problems.
Have you also checked the language and input setting to see if you have the physical keyboard enabled?
Droidriven said:
You are missing the point about the update.
I'm asking if the device has what it had when you bought it or has it had a stock update applied at any time? If it was on one version when you bought it and the keyboard worked at that time but has had a stock update since then and now the keyboard isn't working then that could be what is giving you problems.
Have you also checked the language and input setting to see if you have the physical keyboard enabled?
Click to expand...
Click to collapse
The physical keyboard is enabled. Sorry, I dont have idea what is stock update but it's still the same version when i bought it.
Related
Is anybody familiar with this model?
I want to install ICS on it, but unfortunately am at a loss here.
Some kind of 3.2 beta was installed to it and the "About device" settings menu stated that it was a GT-P6800.
Unfortunately Odin failed write a GT-P6800 firmware on it (PDA only).
It was only then that i noticed that it says product name GT-P7560 in the Download Mode. But I cannot find any firmware of that model.
Which firmware shall I use?
herecy said:
Is anybody familiar with this model?
I want to install ICS on it, but unfortunately am at a loss here.
Some kind of 3.2 beta was installed to it and the "About device" settings menu stated that it was a GT-P6800.
Unfortunately Odin failed write a GT-P6800 firmware on it (PDA only).
It was only then that i noticed that it says product name GT-P7560 in the Download Mode. But I cannot find any firmware of that model.
Which firmware shall I use?
Click to expand...
Click to collapse
Umm.. i think u should post this in tab 7.7 forum ?
Sent from my GT-S5830 using Tapatalk 2
pretty good idea actually
herecy said:
pretty good idea actually
Click to expand...
Click to collapse
And i believe i never heard of GT-P7560 before, sorry..
Sent from my GT-S5830 using Tapatalk 2
kevintangi said:
And i believe i never heard of GT-P7560 before, sorry..
Sent from my GT-S5830 using Tapatalk 2
Click to expand...
Click to collapse
Thanks anyway.
Couldn't find any info except the device specs either.
Actually you are in the right section
kevintangi said:
Umm.. i think u should post this in tab 7.7 forum ?
Sent from my GT-S5830 using Tapatalk 2
Click to expand...
Click to collapse
Actually, you are in the proper section.
The following website has the info on your tablet. It is a GT 7+ variation.
http://pdadb.net/index.php?m=specs&id=3142&view=1&c=samsung_gt-p7560_galaxy_tab_7.0_plus_16gb
Why not do a factory reset and go from there. If that does not get you to where you want to go, give Samsung support a call.
Keep us posted on what ou find out.
Cbill
iUnfortunately I can do neither soft nor hard reset.
Due to the failed attempt to install the wrong firmware the tablet does no longer boot.
And nothing happens when I try to access the recovery menu by pressing volume up and the power button.
But even if I was able to reset the device, this would not bring me closer to my ultimate goal of installing ICS on it.
Is there no firmware of another model similar enough to be flashed safely on this model?
Samsung Support would be my last shot.
herecy said:
iUnfortunately I can do neither soft nor hard reset.
Due to the failed attempt to install the wrong firmware the tablet does no longer boot.
And nothing happens when I try to access the recovery menu by pressing volume up and the power button.
But even if I was able to reset the device, this would not bring me closer to my ultimate goal of installing ICS on it.
Is there no firmware of another model similar enough to be flashed safely on this model?
Samsung Support would be my last shot.
Click to expand...
Click to collapse
You'd probably have to as garyd9 or another dev to give ClockWork Recovery support to your model number, install that, make a backup, then you can ask to have your model number added to the what they support in this thread
http://forum.xda-developers.com/showthread.php?t=1576553
when your post count is high enough ...
WiFi isn't working in the build, and other minor glitches.
Good luck?
While I personally think that CyanogenMod is great, it is no option in this case.
I need a stock rom.
Samsung gave us this device in order to test our apps on it.
Seems that it is some pre-release device or a device that never will be released.
I guess I will have to get in touch with Samsung support.
Update: The first Samsung Service Center rejected the device, stating that they do not handle unofficial devices.
At the second however (halfway across the city) they told me that they would have a look at it. The technician there said that the IMEI number printed on this device did not even exist.
By the way: I would like to thank all of you for your pieces of advice.
herecy said:
Update: The first Samsung Service Center rejected the device, stating that they do not handle unofficial devices.
At the second however (halfway across the city) they told me that they would have a look at it. The technician there said that the IMEI number printed on this device did not even exist.
By the way: I would like to thank all of you for your pieces of advice.
Click to expand...
Click to collapse
Hi,
I am having the same issue, were you able to somehow get your device to boot again?
Thanks
Sorry if this is a trivial question.
Is there a way to know if a device is using the stock firmware or a custom ROM..
In my case the device is an 8.9" galaxy tab GT-7300 wifi + 3G model?
Model:
GT7300
Android Version:
3.0.1
Baseband Version:
P7300XXKE7
Kernel verson:2
.6.36.3
[email protected] #1
Build number
GT-P7300-eng 3.0.1 HRI83XXKE8 test-keys
Apreciate any help
scrambler3 said:
Sorry if this is a trivial question.
Is there a way to know if a device is using the stock firmware or a custom ROM..
In my case the device is an 8.9" galaxy tab GT-7300 wifi + 3G model?
Model:
GT7300
Android Version:
3.0.1
Baseband Version:
P7300XXKE7
Kernel verson:2
.6.36.3
[email protected] #1
Build number
GT-P7300-eng 3.0.1 HRI83XXKE8 test-keys
Apreciate any help
Click to expand...
Click to collapse
Did u buy this used from someone? Do u know if it's rooted? If u aren't sure trying downloading an app that requires root and see if it works. Of it doesn't then you're stock
brandonarev said:
Did u buy this used from someone? Do u know if it's rooted? If u aren't sure trying downloading an app that requires root and see if it works. Of it doesn't then you're stock
Click to expand...
Click to collapse
Yes I bought it used.
I can definitely test to see if it is rooted, hopefully the chances it has a custom Rom but was then unrooted are slim.
Thanks
Download root checker app from play store...
graphiczzz said:
Download root checker app from play store...
Click to expand...
Click to collapse
^this!
scrambler3 said:
Sorry if this is a trivial question.
Is there a way to know if a device is using the stock firmware or a custom ROM..
In my case the device is an 8.9" galaxy tab GT-7300 wifi + 3G model?
Model:
GT7300
Android Version:
3.0.1
Baseband Version:
P7300XXKE7
Kernel verson:2
.6.36.3
[email protected] #1
Build number
GT-P7300-eng 3.0.1 HRI83XXKE8 test-keys
Apreciate any help
Click to expand...
Click to collapse
I have tried to see if I can get the ICS update via Kies, but I get the message
your device's current firmware version is not supported to update firmware vis kies
version: PDA:KE8 / PHONE:KE7 / CSC:KE8 (XXX)
If I type *#1234# in the phone dialer I get
PDA7300XXKE8
PHONE: P7300XXKE7
CSC7300XAKE8
So i am still trying to figure out why I cant update with Keys, if it is because it is on a non Stock Firmware or if it is because I am in the US and it seems to be a UK tab.
Does someone knows if you can run Kies for an Update while in the US on a UK tablet ?
Thanks
scrambler3 said:
I have tried to see if I can get the ICS update via Kies, but I get the message
your device's current firmware version is not supported to update firmware vis kies
version: PDA:KE8 / PHONE:KE7 / CSC:KE8 (XXX)
If I type *#1234# in the phone dialer I get
PDA7300XXKE8
PHONE: P7300XXKE7
CSC7300XAKE8
So i am still trying to figure out why I cant update with Keys, if it is because it is on a non Stock Firmware or if it is because I am in the US and it seems to be a UK tab.
Does someone knows if you can run Kies for an Update while in the US on a UK tablet ?
Thanks
Click to expand...
Click to collapse
If it is on a custom rom then no you cant update that way. Also might have a prob as it will not see an update as your not in the devices default country.
I don't know much about that model of phone, but I think it would be a good idea to wipe and flash a stock image - one that will give you factory recovery (not having it can stop you from getting updates - one possibility). That way you know you are starting clean.
brandonarev said:
^this!
Click to expand...
Click to collapse
Yeah.... forget to read above posts...
Pennycake said:
I don't know much about that model of phone, but I think it would be a good idea to wipe and flash a stock image - one that will give you factory recovery (not having it can stop you from getting updates - one possibility). That way you know you are starting clean.
Click to expand...
Click to collapse
More then that, who knows what glitches piled up while previous owner fooled around with it?
If you reset it, you will at least get stock, well-known glitches .
BalorNG said:
More then that, who knows what glitches piled up while previous owner fooled around with it?
If you reset it, you will at least get stock, well-known glitches .
Click to expand...
Click to collapse
I have already reset the device, but as far as I know (read) resetting the device does not go back to a stock ROM if a custom One was installed, it only goes back to the default of the Custom ROM.
scrambler3 said:
I have already reset the device, but as far as I know (read) resetting the device does not go back to a stock ROM if a custom One was installed, it only goes back to the default of the Custom ROM.
Click to expand...
Click to collapse
Hmm, I guess you are right. I mixed up 'rooting' and 'custom roms'.
By the way, I suppose custom rom does not even have to be rooted. so 'root checker' might a good, but not 100% accurate check.
Just reflash an other ROM, a stock one perhaps? Or some other one, that suits you better?
scrambler3 said:
I have already reset the device, but as far as I know (read) resetting the device does not go back to a stock ROM if a custom One was installed, it only goes back to the default of the Custom ROM.
Click to expand...
Click to collapse
This is why I recommend you re-flash stock with factory recovery using a computer, not just the "factory reset" option in the phone.
Sent from my Transformer TF101 using xda app-developers app
I would recommend simply finding your stock firmware and flashing it. That should do the trick. Or you can just find another ROM, why disable the goodyness of having a rooter phone by unrooting it?
Eddie^^ said:
I would recommend simply finding your stock firmware and flashing it. That should do the trick. Or you can just find another ROM, why disable the goodyness of having a rooter phone by unrooting it?
Click to expand...
Click to collapse
A new twist has surfaced.
First it appears that KE8 is a samsung firmware so i am on stock
But the twist is that this tablet as a fully functional Phone dialer in the Samsung mini app panel and can place and receive phone calls.
Doing some research I found out normally none of these tablets have phone functionality except some of the early demo models.
So either the previous owner had found a way to add phone capabilities to the stock firmware, or it is one of the early models (after all it is running 3.0.1).
In both cases, I would guess it means that if I update to a more recent stock firmware, I will likely loose phone capabilities.
Does someone know if there is a way to find out if a firmware has phone support?
Is there a way to backup the current firmware in the tablet before flashing a new one so I could go back to it ?
Thanks to all for the answers so far!
I removed root via SU, ran root checker to confirm, but I still cannot get OTA updates, get message saying "this device is suspected in rooting"
I can't unroot it any more than I have..
my main reason is the GPS, my phone has the poorest performing GPS of any phone I have had going back to my Google G1, gps will not lock while in a vehicle, cannot use google maps or any other nav.
Im hoping the update will fix it, failing that I will have to send it in for replacement, either way I need it fully unrooted.
Any ideas?
http://forum.xda-developers.com/att-lg-g3/general/unroot-return-to-factory-stock-att-lg-g3-t2820827
jerrycoffman45 said:
http://forum.xda-developers.com/att-lg-g3/general/unroot-return-to-factory-stock-att-lg-g3-t2820827
Click to expand...
Click to collapse
I should have mentioned this.
I don't have access to a PC, OS X only.
Wingnutt said:
I should have mentioned this.
I don't have access to a PC, OS X only.
Click to expand...
Click to collapse
oops well maybe someone with a mac can help
... Apparently not
Wingnutt said:
I should have mentioned this.
I don't have access to a PC, OS X only.
Click to expand...
Click to collapse
As far as I can tell, a PC is the only way. Make sure you find one with a USB 2.0 port.
Not an option, at all.
Hello everyone, I have a tablet that is stuck in recovery and looks to me ADB is going to be the only way out here. Problem is ADB isnt recognizing my device, device manager named it MTP but computer says Android. I have tried changing the USB /VID ID that reads off what is displayed in Device manager not sure if I did it right running myself crazy really, read HRS of Android info Im a noob but a fast learner especially if I get a little bit of guidance. I have tried doing every and all factory hard resets tried different flash tools probably didnt work because my computer doesnt display the correct model. Im trying to learn python at the very moment new to all of this have only hrs of experience of this all. Somebody plz be ever so kind to help me out, thanks!
Device-State:Recovery/Bootloader
Ellipsis 8
QTAQZ3
Vendor:Verizon Wireless
Build:KTO49
4.2KitKat
samson716 said:
Hello everyone, I have a tablet that is stuck in recovery and looks to me ADB is going to be the only way out here. Problem is ADB isnt recognizing my device, device manager named it MTP but computer says Android. I have tried changing the USB /VID ID that reads off what is displayed in Device manager not sure if I did it right running myself crazy really, read HRS of Android info Im a noob but a fast learner especially if I get a little bit of guidance. I have tried doing every and all factory hard resets tried different flash tools probably didnt work because my computer doesnt display the correct model. Im trying to learn python at the very moment new to all of this have only hrs of experience of this all. Somebody plz be ever so kind to help me out, thanks!
?
Click to expand...
Click to collapse
You want help with a device but you don't tell us any kind of information about your device, how smart was that? What you need and how to do it can depend on what device model number you have.
Sent from my SM-S903VL using Tapatalk
SORRY
Droidriven said:
You want help with a device but you don't tell us any kind of information about your device, how smart was that? What you need and how to do it can depend on what device model number you have.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Not very smart at all sorry about that! I didnt disclose that, reason being the research i have done everybod turns there head when this crap device is mentioned. Yes I agree not worth time and energy but already invested so much time its worth it to me and also i have.
Ellipsis8
QTAQZ3/4.2Jellybean/KTO49
samson716 said:
Not very smart at all sorry about that! I didnt disclose that, reason being the research i have done everybod turns there head when this crap device is mentioned. Yes I agree not worth time and energy but already invested so much time its worth it to me and also i have.
Ellipsis8
QTAQZ3
4.2Kitkat
KTO49
Thanks!
Click to expand...
Click to collapse
samson716 said:
samson716 said:
Not very smart at all sorry about that! I didnt disclose that, reason being the research i have done everybod turns there head when this crap device is mentioned. Yes I agree not worth time and energy but already invested so much time its worth it to me and also i have.
Ellipsis8
QTAQZ3
4.2Kitkat
KTO49
Thanks!
Click to expand...
Click to collapse
are you using stock recovery or a custom recovery?
Click to expand...
Click to collapse
ayu321 said:
samson716 said:
are you using stock recovery or a custom recovery?
Click to expand...
Click to collapse
Stock
Click to expand...
Click to collapse
samson716 said:
ayu321 said:
Stock
Click to expand...
Click to collapse
Can you please tell me that what caused this problem ? what were you doing with the device? flashing roms ?
Click to expand...
Click to collapse
ayu321 said:
samson716 said:
Can you please tell me that what caused this problem ? what were you doing with the device? flashing roms ?
Click to expand...
Click to collapse
No I was literally doing nothing I was actually flashing my Samsung Device at that moment. From what I remember it occurred when I noticed at update to marshmallow updated then rebooted it. Ever since its been in this bootloop! Im not trying to root it put a custom rom on it just want it to function nothing special.
Click to expand...
Click to collapse
samson716 said:
ayu321 said:
No I was literally doing nothing I was actually flashing my Samsung Device at that moment. From what I remember it occurred when I noticed at update to marshmallow updated then rebooted it. Ever since its been in this bootloop! Im not trying to root it put a custom rom on it just want it to function nothing special.
Click to expand...
Click to collapse
You have soft bricked your phone . The only way to fix it is it flash its stock rom. If you are new to this stuff I would suggest you to read this article carefully and if you have any doubts , ask me.
https://www.maketecheasier.com/android-root-custom-recovery-and-roms/
Click to expand...
Click to collapse
samson716 said:
Hello everyone, I have a tablet that is stuck in recovery and looks to me ADB is going to be the only way out here. Problem is ADB isnt recognizing my device, device manager named it MTP but computer says Android. I have tried changing the USB /VID ID that reads off what is displayed in Device manager not sure if I did it right running myself crazy really, read HRS of Android info Im a noob but a fast learner especially if I get a little bit of guidance. I have tried doing every and all factory hard resets tried different flash tools probably didnt work because my computer doesnt display the correct model. Im trying to learn python at the very moment new to all of this have only hrs of experience of this all. Somebody plz be ever so kind to help me out, thanks!
Device-State:Recovery/Bootloader
Ellipsis 8
QTAQZ3
Vendor:Verizon Wireless
Build:KTO49
4.2KitKat
Click to expand...
Click to collapse
Where did this problem start? Did you cause this by modifying, attempting to root or flashing the device with something that caused this?
If so, about your only option is to use your device's flashtool to flash the stock firmware. If your device's stock firmware isn't available then you might be out of luck repairing your device. If this is the case then your only other option might be getting someone that has a device exactly like yours that is rooted and getting them to pull copies of the various .img files needed for your device then using adb shell to dd those .img files on your device. But, to be honest, I don't think this is gonna happen for you. You probably will have to take the device to a repair shop. It will probably be cheaper to just buy another tablet because the cost of repair will probably be more than what you paid for the device.
Sent from my SM-S903VL using Tapatalk
ayu321 said:
samson716 said:
You have soft bricked your phone . The only way to fix it is it flash its stock rom. If you are new to this stuff I would suggest you to read this article carefully and if you have any doubts , ask me.
https://www.maketecheasier.com/android-root-custom-recovery-and-roms/
Click to expand...
Click to collapse
Okay not sure which Flash tool to use nor get my stock rom I dread to say but i dont think there is one available. Its a generic tablet its made by Quanta. Not sure how to put it in a download mode either I assume ADB is the only way to transfer any files.
Click to expand...
Click to collapse
Your device probably uses SPFlashtool or fastboot.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
Where did this problem start? Did you cause this by modifying, attempting to root or flashing the device with something that caused this?
If so, about your only option is to use your device's flashtool to flash the stock firmware. If your device's stock firmware isn't available then you might be out of luck repairing your device. If this is the case then your only other option might be getting someone that has a deuce exactly like yours that is rooted and getting them to pull copies of the various .img files needed for your device then using adb shell to dd those .img files on your device. But, to be honest, I don't think this is gonna happen for you. You probably will have to take the device to a repair shop. It will probably be cheaper to just buy another tablet because the cost of repair will probably be more than what you paid for the device.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Its pretty easy to fix a soft bricked device , even if stock rom isnt available , any rom compatible with his device can fix the issue .
ayu321 said:
Its pretty easy to fix a soft bricked device , even if stock rom isnt available , any rom compatible with his device can fix the issue .
Click to expand...
Click to collapse
To be compatible, the ROM typically has to be ported and that usually requires the stock firmware or stock source from the device that the ROM is being ported over to. 99% of the time you can't just flash a ROM from a different model number, even if the CPU is the same, there's quite a bit more to it than that. The android operating system is built for the specific hardware it is installed on, the two devices would have to be exactly the same and have the exact same components, any differences in hardware make he firmwares incompatible.
For this particular device, I doubt the stock firmware or stock source code area available, even if it were, porting another ROM wouldn't be necessary because if it were available it could just be flashed with that instead of porting a ROM.
About the only time a ROM from a different model number can be used without any porting or edits being made is when the devices are exactly the same device just rebranded with a different "name".
But thanks for trying to tell me something that you thought I didn't know, now it seems I've told you something that you didn't know.
Sent from my SM-S903VL using Tapatalk
samson716 said:
ayu321 said:
Okay not sure which Flash tool to use nor get my stock rom I dread to say but i dont think there is one available. Its a generic tablet its made by Quanta. Not sure how to put it in a download mode either I assume ADB is the only way to transfer any files.
Click to expand...
Click to collapse
1.Search for your tablet's root package , download it and move it to your tablet's sd card. Then enter your recovery mode by pressing power button+ Home button+ Volume button at same time for 10sec. Once entered , go to option "apply update from sd card" and select the root package you downloaded. (CONGRATS YOU HAVE ROOTED YOUR PHONE!)
2.Search for your tablet's 'custom recovery' , download it and flash it through odin tool(pc) .
3.Final Step ! BASED ON THE RECOVERY YOU FLASHED THESE STEPS MAY DIFFER , SO REPLY ME IF YOU SUCCEED IN FLASHING CUSTOM RECOVERY
Click to expand...
Click to collapse
ayu321 said:
1.Search for your tablet's root package , download it and move it to your tablet's sd card. Then enter your recovery mode by pressing power button+ Home button+ Volume button at same time for 10sec. Once entered , go to option "apply update from sd card" and select the root package you downloaded. (CONGRATS YOU HAVE ROOTED YOUR PHONE!)
2.Search for your tablet's 'custom recovery' , download it and flash it through odin tool(pc) .
3.Final Step ! BASED ON THE RECOVERY YOU FLASHED THESE STEPS MAY DIFFER , SO REPLY ME IF YOU SUCCEED IN FLASHING CUSTOM RECOVERY
Click to expand...
Click to collapse
Odin is for Samsung devices, not other devices.
The device they are repairing is not a Samsung device. They have this device and a Samsung device. The issue on this device occurred while they were in the process of flashing their Samsung device.
I know you're trying to help but don't post anything unless you are absolutely certain that you know what you're talking about.
In this case, you didn't and that can easily lead to a hard bricked device because they followed your instruction.
Stick to answering questions about devices you personally have dealt with, don't go assuming that you understand someone else's device. They are all different, the methods, tricks and tools for one won't necessarily work on another.
You understand android somewhat but judging by your posts, you don't understand the differences in devices and methods. But you will after you've been here a while.
Sent from my SM-S903VL using Tapatalk
---------- Post added at 10:39 PM ---------- Previous post was at 10:32 PM ----------
DO NOT USE ODIN ON YOUR DEVICE!!!
Odin is only for Samsung devices.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
Where did this problem start? Did you cause this by modifying, attempting to root or flashing the device with something that caused this?
If so, about your only option is to use your device's flashtool to flash the stock firmware. If your device's stock firmware isn't available then you might be out of luck repairing your device. If this is the case then your only other option might be getting someone that has a device exactly like yours that is rooted and getting them to pull copies of the various .img files needed for your device then using adb shell to dd those .img files on your device. But, to be honest, I don't think this is gonna happen for you. You probably will have to take the device to a repair shop. It will probably be cheaper to just buy another tablet because the cost of repair will probably be more than what you paid for the device.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
thankyou so much for the fast responses much appreciated to take your time to explain. Okay i have a question what would be the course of detailed action to preform getting any and all missing .img's it may need. Also i know its a crazy question but would i be able to preform this in store with the displayed tablet that matches mine? How difficult is something like this, and is there any other methods at all I can try to boot past this bootloader. And now that i remember correctly from reading others this happened when I upgraded to 5.1 or 5.0 thank you everybody once again!
samson716 said:
thankyou so much for the fast responses much appreciated to take your time to explain. Okay i have a question what would be the course of detailed action to preform getting any and all missing .img's it may need. Also i know its a crazy question but would i be able to preform this in store with the displayed tablet that matches mine? How difficult is something like this, and is there any other methods at all I can try to boot past this bootloader. And now that i remember correctly from reading others this happened when I upgraded to 5.1 or 5.0 thank you everybody once again!
Click to expand...
Click to collapse
No, you wouldn't be able to get it from a tablet in the store, it's a rather involved process that requires connecting the device to PC, it also requires rooting the device and flashing a custom recovery, and that's all before you actually get to where you can pull the files. It'll take a couple of hours,or more to do it.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
No, you wouldn't be able to get it from a tablet in the store, it's a rather involved process that requires connecting the device to PC, it also requires rooting the device and flashing a custom recovery, and that's all before you actually get to where you can pull the files. It'll take a couple of hours,or more to do it.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Is there absolutely anything i can try, just a long shot in the dark?
samson716 said:
Is there absolutely anything i can try, just a long shot in the dark?
Click to expand...
Click to collapse
The only other option is pretty risky. You can try a firmware from another device that has the same CPU and hardware as your device, you'd have to compare specs. It would have to have the same CPU, same screen resolution, same camera(front and rear), same amount of RAM, same amount of internal storage, same accelerometers, etc.. It has to have all the same components that yours has.
Sent from my SM-S903VL using Tapatalk
Hello,
I have two j7 2016 fn. One is mine one for repair. I recognized that there is a bootlogo difference. The onw which works has a thin powered by android line while the one with touch problems has a bold android. So I guess there I have an outdated bootloader on that phone. How can I update?
spirit_of_the_ocean said:
Hello,
I have two j7 2016 fn. One is mine one for repair. I recognized that there is a bootlogo difference. The onw which works has a thin powered by android line while the one with touch problems has a bold android. So I guess there I have an outdated bootloader on that phone. How can I update?
Click to expand...
Click to collapse
Use samsung smart switch
sandeepkumar0153 said:
Use samsung smart switch
Click to expand...
Click to collapse
Yes I already tried
But smartswitch said that the phone does not allow data transfer via usb.
I can't use touch. Every rom I flashed does not make the touchscreen work.
I saw on youtube that some said to get back to marshmallow. But I heard that could lead to loosing the imei.
What should I do?
spirit_of_the_ocean said:
Yes I already tried
But smartswitch said that the phone does not allow data transfer via usb.
I can't use touch. Every rom I flashed does not make the touchscreen work.
I saw on youtube that some said to get back to marshmallow. But I heard that could lead to loosing the imei.
What should I do?
Click to expand...
Click to collapse
Does the touch work in twrp ?? There is a twrp flashable stock rom in here, maybe it helps
sandeepkumar0153 said:
Does the touch work in twrp ?? There is a twrp flashable stock rom in here, maybe it helps
Click to expand...
Click to collapse
Thanks for your help. Since in download mode frp lock shows as on I did not tried to install twrp. I don't know what will happen because my friend gave it with a Factory reset to me.
spirit_of_the_ocean said:
Thanks for your help. Since in download mode frp lock shows as on I did not tried to install twrp. I don't know what will happen because my friend gave it with a Factory reset to me.
Click to expand...
Click to collapse
Out of ideas now, good luck and i hope you get it solved