Related
Ok, I know lots of people brick their phones, and like in my case hard-bricked as well. But everycase is unique but I'd really appreciate if you guys could look over what I did and see if my plan of action is the right thing to do.
So, basically I came across ICS on youtube by chance and it looked to be really cool for my S2. I have no experience with romming and such and I'd only ever heard of it. Then after about only 3 hours of research I set to work to romming it. The instructions said I had to get a clockwork mod to flash the drive to get ICS. I think I messed this up as I'm not entirely sure I unzipped the folder properly to get the .tar. on pda.
So, my phone would turn on but only get to the samsung logo with the warning sign. By this time I was fed up and worried and such and decided it was too much effort and just wanted my phone back. So I set out to put the original firmware back on. I downloaded the stuff and put the in their respective slots, pit,pda and mobile I think. I pushed start and it was if odin had frozen (no progress bar either), I couldn't click anything and the log script in the corner showed nothing.
I was quite annoyed and closed odin and unplugged my phone,put it back in download and such to try again. This time the same thing happened and I unplugged the phone first, Big mistake! My phone went completely black and effectively hard bricked.
Okay that's what happened. I just want advice to see if what I'm going to do is right.
1- Imma try to go through the simple workarounds to try to get my phone back into download mode.
2- This will probably fail, so I will purchase a USB jig from amazon, this will give me 3 potential results
one. My phone will get back into download mode and there will be no warning sign under the samsung logo and custom counter at 0.
two. My phone will get back into download mode but there is still the warning sign and the custom counter is at 0
three. Nothing will happen or my counter will be at one
3- okay so if scenario one happens I will send my phone to samsung and they should repair as they have already told me through e-mail they believe it to be a motherboard problem
scenario two, I will send my phone to vodafone,as I've learnt from the forums their techies should not care as much about that kind of thing.
scenario three, I will send my phone to mobile tech videos in Texas from the UK as everyone seems to trust them and they look pretty legit.
Okay, so that's basically my plan of action. All I want is for you guys is to just go "yeah, good idea thats probably right" or show me what I've misjudged or if you are aware of another option for me.
Thanks,
Adam
Bump, please I know some of you guys can help me out
Hi,
I wanted to update my Nexus S from SlimBean 4.2.1 1.0 to 1.1 this morning.
I didn't do a full wipe which basically ruined my OS so I wanted to back it all up, full wipe and start all over again.
I had big problems with backing up as Titanium Backup either crashed or was stuck at it's initializing SQLite stage.
The phone process and System UI were crashing all the time if that matters.
So I tried to back it up through CWM which first failed while backing up the data partition, but it worked the second time.
I turned the phone off and since then it's not doing anything anymore.
Won't turn on, doesn't show the charging animation when plugging it in.
I tried to recover it several times.
It doesn't show up in Windows' Device Manager and UnBrickableRessurrectorR40 doesn't see it.
Is there anything I can do?
Thanks a lot.
land.apfel
why don't you try to get it to download mode and flash via odin ?
I would do it that way if it was possible. The Nexus won't do anything. Neither fastboot, nor Download nor recovery nor anything else.
The only thing it does is getting hot when being connected to AC.
But I'll try to do the UnbrickableMod and see if it helps.
land.apfel
Did you make the hardware modification? I have to do it with mine to be recognized.
samcortez said:
Did you make the hardware modification? I have to do it with mine to be recognized.
Click to expand...
Click to collapse
hardware modification is so difficult so as to be impossible for most people. it seems to be the only solution though. i only just bought my nexus s (for $150) second hand .. flashed cwm 10 on it and it bricked a few days later when i swapped a battery. i have disassembled the phone but the modification required needs minute tools and expertise beyond my ability. any suggestions? sending it in to experts in the USA will cost me nearly $100 and I'm afraid the diagnosis might mean I will lose that as well.
Without the hardware modification you can trash your Nexus S right now, as the chance that you recover it for some reason is probably 0.01%.
For doing the hardware modification you really need to know what you're doing. If you don't, look out for someone you know and who would do it for you.
After you did the UnbrickableMod, the chance that you can recover your phone is about 60% (maybe).
If you can't recover the phone, you need to exchange the eMMC chip as well.
I found eMMC chips in China for $19, but you still need to assemble it.
This is where I'm stuck at the moment.
my phone is in same condition please someone solve this and share with us
If you haven't already applied the UnBrickableMod you should try that first.
If you have, I have no idea what to do.
land.apfel
I'm new to this forum and this is my 2nd attempt to get help to solve my problem. I have read ALL the rules posted in the XDA New User Guide - Getting Started On XDA, as well as all of the linked pages that are suggested to read before posting. It was very informative but I'm more confused then ever about the right place to seek help. This is all very overwhelming and I'm afraid I'm going to say something to offend someone or post in the wrong place and get in trouble, or worse, ignored. I suspect I did just that in my last post because I never got a response. I apologize in advance if I have done something wrong.
Ok, I'll do my best to explain my problem. I have an LG K20 Plus (I'll refer to this as my original phone) that I bought, brand new, from T-Mobile in May. In August I cracked the screen but continued to use it because besides the crack, it worked fine. By September the crack had worsened significantly and I decided to replace the outer glass as I had successfully done that with my older LG G3.
In that process, while trying to get that dreadful glue off, I scraped off some of the black stuff under the glue on the LCD which caused a white spot, about the size of a 1/2 dollar, on my screen. Although it was bothersome, the phone itself still worked fine. I continued to use it while I searched for the easiest way to fix it within my budget. After reading posts here and realizing it would work, I bought a used LG K20 Plus (I'll refer to this as my used phone) with a bad esn. The plan was to put my original logic board into the used phone and be on my way. That didn't happen.
When the used phone arrived, I turned it on to verify everything worked. I then put my original logic board into the used phone and turned it on. I saw my orignal wallpaper and was so happy I had my phone back. Then I tried to swipe to unlock and nothing happened. I booted it up a couple more times and still nothing. I connected a mouse via an OTG cable and verified that there were no more obvious issues with the phone except the digitizer. To confirm the dispaly wasn't faulty on the used phone, I put the used logic board back into the used phone it came with and booted it up. The digitizer was back to working again. I ran through as much as I could on a locked phone and the digitizer worked like new.
I, carefully, put my original logic board back into the used phone and, again, no touch capability. Again, I researched this problem to no avail. I realized I was way over my head and I decided to ask for help instead of making things worse by trying to fix it without knowing what I was doing. So, I put the phone in a drawer and asked for help here. That was a month ago. I know you are all very busy and, like I said earlier, I'm sure it's my fault and I messed up somewhere because my post didn't receive any replies.
I can't use my original phone because I have no touch ability and I can't use the used phone because it has an esn lock. At this point I decided to try and (I'm sure I'm using the wrong terminology here) flash the used phone and root it to bypass the bad esn lock. After researching that and seeing the word "illegal" A LOT, I decided I just didn't know if it was legal or not, so I decided to not take the risk of doing something that may get me into trouble.
At this point I decided I didn't have much to lose so I backed up my original phone and, with only the display of the used phone attached, I started the process of flashing it with TWRP and rooting it via this guide https://forum.xda-developers.com/android/development/recovery-twrp-v3-lg-k20-plus-t3616248 So, it is now successfully rooted but it still has no touch ability. The really weird thing is, while I was in TWRP Recovery mode, the touch ability worked again. But as soon as I rebooted the phone into regular mode, the digitizer stopped working again. I'm so confused and I don't even no where to start looking because I can't define the problem or the exact thing that is failing. I don't even know if it's hardware or software related.
So, I guess my question is, does anybody have any experience with this kind of problem you could share with me. I'd settle for someone being patient enough to explain to me exactly what is going on so I could research it better myself. Asking for help was not my first step. I have been looking and looking for 6 weeks now. I'm way out of my league with this stuff. It's really difficult to find a solution to a problem you don't quite understand. It's a little bit like being told to look up a word in the dictionary to find the spelling.
*LG K20 Plus
*LG-TP260
*T-Mobile
*Rooted
Baseband: MPSS.JO.
2.0c1.2-00012-8937_GENNS_PACK-1.85468.1
I think it's my original ROM
Kernel Version 3.18.31
I flashed TWRP
USB debugging enabled
OEM Lock Off
Here is what you do. Hook it up to a pc. Take a logcat and that will tell you what is failing. It sounds like a kernel compatibility issue.
zelendel said:
Here is what you do. Hook it up to a pc. Take a logcat and that will tell you what is failing. It sounds like a kernel compatibility issue.
Click to expand...
Click to collapse
I'm so sorry but I have run into a few problems .. firstly, on my phone I have to use a mouse connected via OTG cable because I have no touch ability and my usb connection is set to "charge only". Apparently you can't change that until the phone is plugged in and obviously I need the mouse so I can't connect to computer. I downloaded an app called LogCatX and made a log file but I don't know how to attach a file and when I copy/paste it into the reply it says it is too long and reduce by 30000 characters. Any advice?
HelpNeededPlz said:
I'm so sorry but I have run into a few problems .. firstly, on my phone I have to use a mouse connected via OTG cable because I have no touch ability and my usb connection is set to "charge only". Apparently you can't change that until the phone is plugged in and obviously I need the mouse so I can't connect to computer. I downloaded an app called LogCatX and made a log file but I don't know how to attach a file and when I copy/paste it into the reply it says it is too long and reduce by 30000 characters. Any advice?
Click to expand...
Click to collapse
I think the new touch screen will need a calibration.
PS: i liked how you explained your problem
Sorry for my confusion but I'm not sure if you were telling me what I should do to figure out where the incompatibility issue may be or if you were asking me to upload the catlog so you could look at it and help me. I don't know what a catlog is, nor how to interpret it. At any rate, 6 hours later, I have, finally, figured out how to upload a file. :victory: I've been looking at how to fix a kernel incompatibility issue and I've read you can flash a custom kernel. If I did something like that, would that resolve my problem. Are they specific to the version of operating system your phone has (ie nougat, marshmallow etc) or do you need to use one for your specific phone model? Would flashing a custom ROM do the same thing? And is that model specific or OS specific? Where would I go to find something like that?
NOTE... In looking for differences in my phone to try and figure out where this kernel compatibility issue might be, I noticed that there are two different numbers on the midframe of my phones. I don't know if this means anything. I'm just trying to help someone help me.
zelendel said:
Here is what you do. Hook it up to a pc. Take a logcat and that will tell you what is failing. It sounds like a kernel compatibility issue.
Click to expand...
Click to collapse
Hello? Was this the extent of your help? I'm not sure if you were asking me to run a catlog to upload so you could help me figure out what was wrong or if you were just telling me what to do and then moving on. Because if it was the later, all you've done is piled more stuff on my steadily growing mound of confusion. To make matters worse, my posts is showing as getting a response, so, I fear, nobody else will look at it and I will be left in the same place as before. If someone happens upon this post, could you give me advice that will actually help me solve my problem, along with instructions on how to do whatever I need to do. Thank you in advance. Until then, I'll be anxiously awaiting your reply....
His folks. Here's what happened...
Bought new T95Z Plus. The 3GB/32GB version. Looks funky.
Tried it, very nice, but wanted to install custom firmware.
Tried AMLogic Burning Tool. Not happening - disconnects device at 2% every time. Found about 50 different variations of how to connect, none work. Always stop at 2%.
Reads tutorial on other site about using Flashify to flash TWRP. Of course! Revelation! Installed Flashify from Google Play on stock ROM. It works!
Reboots to TWRP, standard wipe as directed, and installs Poison ROM from SD Card on device.
Success! Reboots into Poison ROM!
Very nice. But what's this? Wi-Fi doesn't work. Posts problem. No replies about Wi-Fi.
Searches around net for answer. Nothing, just a few people in same boat. Really needs Wi-Fi...
Decides to flash back to stock for Wi-Fi. OF COURSE NOT TAKEN ANY BACKUPS BECAUSE DAMN FOOL!
Gets file from post here in the Poison ROM thread. Gets both stock and the modified one just in case.
Tries Burning Tool again. Nope, still crap.
Watches tutorial on SD Card Maker. Decides hey why not?
Sticks SD card in, watches as box bricks. Poison logo flashes on screen, quickly followed by extremely brief Droid logo "updating". Then blackness...
Panics. Curses self for not being more careful I KNOW YOU DON'T HAVE TO TELL ME!
Cannot connect box to either PC or TV now. Computer says no device, and black screen on TV.
Holds paper down with it while crying.
That's my story. Hope it at least gave you a lol for the money! Yes it's my fault, you don't have to tell me. I didn't back anything up (what can possibly go wrong right?), but is there anything left for me to do here? I did also see a tutorial about shorting the NAND chip to get it started, and I have opened the box and attempted this with a little screwdriver but nothing happened beyond a slight buzzing noise on one of the strips and the LED briefly going out.
Any help, advice, well-wishing and general tomfoolery welcomed at this difficult time! Ta folks!
if the pc is not finding the device last chance is to short the pins from nand chip https://www.youtube.com/watch?v=fsyS3p5asZs
you can use the pc or sd card, search for it
K-Project said:
His folks. Here's what happened...
Bought new T95Z Plus. The 3GB/32GB version. Looks funky.
Tried it, very nice, but wanted to install custom firmware.
Tried AMLogic Burning Tool. Not happening - disconnects device at 2% every time. Found about 50 different variations of how to connect, none work. Always stop at 2%.
Reads tutorial on other site about using Flashify to flash TWRP. Of course! Revelation! Installed Flashify from Google Play on stock ROM. It works!
Reboots to TWRP, standard wipe as directed, and installs Poison ROM from SD Card on device.
Success! Reboots into Poison ROM!
Very nice. But what's this? Wi-Fi doesn't work. Posts problem. No replies about Wi-Fi.
Searches around net for answer. Nothing, just a few people in same boat. Really needs Wi-Fi...
Decides to flash back to stock for Wi-Fi. OF COURSE NOT TAKEN ANY BACKUPS BECAUSE DAMN FOOL!
Gets file from post here in the Poison ROM thread. Gets both stock and the modified one just in case.
Tries Burning Tool again. Nope, still crap.
Watches tutorial on SD Card Maker. Decides hey why not?
Sticks SD card in, watches as box bricks. Poison logo flashes on screen, quickly followed by extremely brief Droid logo "updating". Then blackness...
Panics. Curses self for not being more careful I KNOW YOU DON'T HAVE TO TELL ME!
Cannot connect box to either PC or TV now. Computer says no device, and black screen on TV.
Holds paper down with it while crying.
That's my story. Hope it at least gave you a lol for the money! Yes it's my fault, you don't have to tell me. I didn't back anything up (what can possibly go wrong right?), but is there anything left for me to do here? I did also see a tutorial about shorting the NAND chip to get it started, and I have opened the box and attempted this with a little screwdriver but nothing happened beyond a slight buzzing noise on one of the strips and the LED briefly going out.
Any help, advice, well-wishing and general tomfoolery welcomed at this difficult time! Ta folks!
Click to expand...
Click to collapse
I bricked my device as well a few weeks ago. Here's how to fix it -
Open the device and locate the NAND chip. On either side of it, there will be either pins or pads.
Grab a paperclip and bend it into a U shape.
Plug the device in to the PC as well as power and then slide the ends of the paperclip along the pins/pads (touching different ones) until the PC recognizes it.
The nice thing about the the T95z, is that it's very easy to short out the NAND and reset it.
Good luck!
Thanks for your replies and support people. Very much appreciated.
I have somehow magically managed to short the pins and reset the device. The laptop has now installed the device drivers and it sees the box no problem now, whereas before it was completely invisible to the computer. However, there doesn't appear to be any working firmware out there for this device. When I use the AMLogic Flash Tool it fails at 2% with one or two I downloaded, or at 4% with another one. I'm guessing this means there's no working firmware, nothing I can find anyway. I've taken a shot of the box inside while I had it open. Hopefully someone can point me in the right direction. It's attached below. I notice it's a recent board - 31st March 2018. On the Wi-Fi Strip it says IT6335.
Does anyone know which firmware I should try next? Thanks all.
Highly doubt its a complete brick, sounds more like a USB or USB port error, change ports or USB cords
If its detected by the PC its far from a brick, just for reference ive flashed completely incompatible firmware on a H96 Pro H3 and still couldnt brick it..
S912/S905w firmware on an S905x device and still could recovery it
Yes I agree now. I think before shorting the pins it was a goner, but now what with the PC at least recognising it I might have a chance of saving it!
Tried two different laptops with no success though. Maybe it is the cable but it is a new one. Hmmm. Think I'll buy another to be sure. Thanks for replying everyone!
I had the same problem with my T95z and I think it's the same as yours. I contacted the seller and he gave me the following link and I was able to retrieve it.
http://en.mail.qq.com/cgi-bin/ftnEx...514a315e1563&t=exs_ftn_download&code=a4d4081c
THANKS YOU SO MUCH! This flashed first time, same cable and everything. I suspect the AMLogic Flash Tool knows when the ROM is incorrect for the device...? Perhaps. Anyway, this flashed, and didn't show any errors.
However, I'm now stuck on the boot up "T95Z" logo. I figured on first boot up it may take some time to get itself ready, but I left it half an hour and it was still sitting there on the logo. I unplugged it and tried the toothpick solution to get to recovery but that doesn't seem to want to respond either. It just goes straight to the logo and sits there.
Anyone have any ideas at this stage? I'm amazed I got it this far tbh. Thanks to everyone, and particularly Narcoticx for the firmware.
K-Project said:
THANKS YOU SO MUCH! This flashed first time, same cable and everything. I suspect the AMLogic Flash Tool knows when the ROM is incorrect for the device...? Perhaps. Anyway, this flashed, and didn't show any errors.
However, I'm now stuck on the boot up "T95Z" logo. I figured on first boot up it may take some time to get itself ready, but I left it half an hour and it was still sitting there on the logo. I unplugged it and tried the toothpick solution to get to recovery but that doesn't seem to want to respond either. It just goes straight to the logo and sits there.
Anyone have any ideas at this stage? I'm amazed I got it this far tbh. Thanks to everyone, and particularly Narcoticx for the firmware.
Click to expand...
Click to collapse
flash a new stock firmwar, should boot after that
Thanks for replying. So, I can now flash this with a different stock firmware, yes? I'll give it a go. You have one linked in your Poison ROM thread so I'll try that.
Thanks again to all for your help.
K-Project said:
THANKS YOU SO MUCH! This flashed first time, same cable and everything. I suspect the AMLogic Flash Tool knows when the ROM is incorrect for the device...? Perhaps. Anyway, this flashed, and didn't show any errors.
However, I'm now stuck on the boot up "T95Z" logo. I figured on first boot up it may take some time to get itself ready, but I left it half an hour and it was still sitting there on the logo. I unplugged it and tried the toothpick solution to get to recovery but that doesn't seem to want to respond either. It just goes straight to the logo and sits there.
Anyone have any ideas at this stage? I'm amazed I got it this far tbh. Thanks to everyone, and particularly Narcoticx for the firmware.
Click to expand...
Click to collapse
Great, glad I could help Our T95Z looks like a new version. Try reflash again.
The developers can make an adaptation Poison rom with the firmware our original?
K-Project said:
Thanks for replying. So, I can now flash this with a different stock firmware, yes? I'll give it a go. You have one linked in your Poison ROM thread so I'll try that.
Thanks again to all for your help.
Click to expand...
Click to collapse
Yep or your can flash infected rom as its the most recent build specifically for the T95Z plus, but its based on ATV UI so either way whatever you feel is best
Infected rom does not work in our box, it gives an error when trying to flash amlogic usb.
Hi to you all this Sunday morning! Back again in desperation...
Unfortunately since flashing the ROM in this thread (which completed successfully with no errors), I have had no joy at all getting this box working. It boots up, you get the "T95Z PLUS" logo onscreen, and it just sits there. I have tried:
Reflashing with the same ROM and also other ROMS but it makes no difference. The PC now only recognises the box intermittently and the godawful AMLogic Burn Tool always spits errors (erase bootloader/identify/error). Can't even get it to the 2% I enjoyed before. It doesn't matter how you connect the box to it. Toothpick, no toothpick. Load image first, don't load image first. None of the various permutations of connecting this box seem to make a blind bit of difference.
SD Card Tool - but the box won't boot to it. Tried shorting the pins, nada.
I've shorted out those pins so many times I've probably fried the chip by now.
Ricky I looked at your own tools and would have liked to try them. Surely they MUST be better than the AMLogic crap! But it needs an IP address to continue (unless I'm reading it wrong). I don't have this as the box is bricked. Is there anything else I can do here?
Many thanks again for all your help.
K-Project said:
Hi to you all this Sunday morning! Back again in desperation...
Unfortunately since flashing the ROM in this thread (which completed successfully with no errors), I have had no joy at all getting this box working. It boots up, you get the "T95Z PLUS" logo onscreen, and it just sits there. I have tried:
Reflashing with the same ROM and also other ROMS but it makes no difference. The PC now only recognises the box intermittently and the godawful AMLogic Burn Tool always spits errors (erase bootloader/identify/error). Can't even get it to the 2% I enjoyed before. It doesn't matter how you connect the box to it. Toothpick, no toothpick. Load image first, don't load image first. None of the various permutations of connecting this box seem to make a blind bit of difference.
Click to expand...
Click to collapse
did you try another good power supply? maybe this is the problem?
drakulaboy said:
did you try another good power supply? maybe this is the problem?
Click to expand...
Click to collapse
Yes I bought a new one from MyVolts which has been the main PSU since receiving the item. I haven't used the one in the box hardly at all. I also bought two different USB cables - one is 1m and the other is 30cm. Tried three different Windows computers - same result. Also tried different versions of the Burning tool. The one that did the job initially is version 2.16, but like I say even now that isn't working either.
I'm now assuming the box is dead.
looking for this firmware.
any chance this file could be rehosted. i have the same device with same issue.
Narcoticx said:
I had the same problem with my T95z and I think it's the same as yours. I contacted the seller and he gave me the following link and I was able to retrieve it.
Click to expand...
Click to collapse
demiser said:
any chance this file could be rehosted. i have the same device with same issue.
Click to expand...
Click to collapse
https://drive.google.com/open?id=1IE1wW8ny9EBlAGf-aB1i7sOSyGNA_lnQ
thankz
has anyone else had any luck with finding a working firmware for these devices. mine has the same issue were it gets stuck at the boot logo with this firmware and wont burn any other firmware. errors out at ddr
I have had extremely bad luck and all sorts of dramas including frying the mainboard of my T-865 while attempting to flash TWRP on my way to get it rooted. I will get my tablet back a few days later after paying 550 bucks for the repair on top of the purchase price of the tablet itself 10 days ago (of course of out warranty since I unlocked the bootloader and tried to install "unauthorized software" according to their warranty terms)
My simple question now is, is there is a way to get the T-865 rooted without having to install a custom recovery (which under no circumstances I will attempt again)? All I need is root, nothing else.
Thanks for the advice
@VeEuzUKY may I ask how your motherboard got fried?
Did you follow the steps mentioned in this thread https://forum.xda-developers.com/galaxy-tab-s6/development/recovery-twrp-3-3-1-t3975587?
Usually if something goes wrong while attempting root, Odin flashing stock rom will bring back the device to working condition..
jaidev.s said:
@VeEuzUKY may I ask how your motherboard got fried?
Did you follow the steps mentioned in this thread https://forum.xda-developers.com/galaxy-tab-s6/development/recovery-twrp-3-3-1-t3975587?
Usually if something goes wrong while attempting root, Odin flashing stock rom will bring back the device to working condition..
Click to expand...
Click to collapse
Dearest jaidev.s.. it's quite of a long story (and a surprising one at that) as I have been flashing, testing and even helping build several custom ROMs for Samsung deviced in the past 12 years without ever getting stuck in a truly unforeseen situation.
To make a very long story short, after doing all my homework through all the available threads and feedback I could find on the matter, I ventured to unlock the bootloader, install TWRP custom recovery, required custom kernel and magisc root files for my T865. And yes, I followed precisely the available guides on it from our community. Things all went pretty much as planned and I eventually booted into a successful fully rooted session on my tablet. I tested all of the tablet's native apps and functionality, installed Root Explorer and a few other apps that I had backed-up APKs for. My session was about 30 minutes long, I never connect to any data in stayed always offline, after which I decided to reboot the tablet. And then, meltdown.
The tablet immediately refused to restart again, completely bypassing the initial standard Samsung splash screen, and going directly into a warning screen that it had been locked due to the "installation of unauthorised software". From that point on any attempt to get the tablet from that state or to simply flash the stock firmware, failed completely. With the help of some other developers we all ventured together if my firmware was actually from another region, all of which I tried without any success. Eventually the tablet got stuck in a state that would not even turn off anymore even if I forced it via the volume down and power button commands. I eventually just waited out until the battery exhausted itself and then that was that.
Upon taking it to Samsung for repair where within seconds they realised that I had unlocked the bootloader and had tried to install a custom recovery, they came back about half an hour later explaining me that the hardware itself would not read or write any data any more despite their efforts, for which they would have to replace the mainboard.
I am yet to try and understand how the the tablet stopped functioning upon a reboot when up to that point everything had been flashed correctly and I had managed to do a session with everything properly configured. This said, I'm facing a $550 repair to what was an $800 tablet purchased just 10 days ago. I will obviously now not venture to try to install custom recovery again. I believe my tablet might have been a one-off with some sort of a preexisting hardware glitch that got ignited by the custom flashing that I did.. I really don't know and it really doesn't matter. At this point as I am about to collect the repaired tablet in a couple of days, the only thing I am interested in doing (a must for me on any device) is to achieve root and let it be. I don't want custom recoveries, kernel overrides or anything else other than having root. Thus my search on what will be be the best venue I have how to get the tablet safely rooted without messing with TWRP again or trying to mod the bootloader. And that's pretty much it..
And let me state, I have received nothing other than truly overwhelming support and help from lots of members of the community on my particular case for which I am extremely thankful and appreciative.
PS - I also have a Note 10 plus, recently purchased to finally replace my daily driver Note 8 that I've had for almost 3 years. Needless to say that I am absolutely dreading about the thought of installing a custom recovery on it as well and achieving root, and having again any kind of bad luck to get myself stuck in another nightmare again. I will first deal with the tablet, and if that eventually goes well, I will try to gain the necessary courage to get myself to flash TWRP and root on it without destroying it next. More than 12 years doing these things with nothing but success on dozens of devices, and suddenly here I am.
Part of me is wondering if Knox's eFuse tripping could have been the reason the board got fired? Perhaps a fault in that. Can't see any other reason reason why modifying software would cause a catastrophic hardware failure.
Anyway, as far as I'm aware the only other way to achieve root is to patch your stock OS in Magisk, then flash the modified file as detailed in this thread...
https://forum.xda-developers.com/galaxy-note-10+/how-to/guide-how-to-root-note-10-t3960031
Which is originally linked from This Thread
I've not tried it myself and it's a process from before TWRP was developed for the Tab S6 - So, you should do further research on it before jumping in to ensure nothing has changed.
Precisely why I am not installing twrp. The threads pages are having so many varied info and people getting bricks following steps, i feel discouraged to try root.
Tab s6 gonna be my first phone in 10 years that m gonna not root. I am using android since éclair and rooting.
"Samsung splash screen, and going directly into a warning screen that it had been locked due to the "installation of unauthorised software". From that point on any attempt to get the tablet from that state or to simply flash the stock firmware, failed completely. "
I had the same experience. I installed everything and rebooted to see this. Was only annoyed that oem unlock won't be an available instantly but it was. I went to download mode flashed stock, installed twrp again and it was fine. If you couldn't go to download mode (with cable inserted into pc! I assume you must know it because you flahed it, thie was another new idiotic introductement by gnus, i thought i have broken tablet because i couldn't get into download mode, when i found out cable must be in not mentioned anywhere in the instructions, just like we must know it, when it never in the universe been the case) then it's weird bug. Because what you are describing sound like standard behavior for these tablets, but why you couldn't get out of it right away i don't kno, because i could. Moreover i had the same on s9 snap. On s9 i also has issues when oem unlock will never appear, until i run some command checking it status and it got instantly unlocked. I shared it tp developer but he only laughed. When i knio there is nothing to laugh, sung's firmware has millions of such unexplainelable behaviors, a lot of people are faced with it. If you had another tablet and got the same result then just pick up non tgy one and it will be good, i promise. Also who knows why you want note 10 and t s6
Extreemator said:
"Samsung splash screen, and going directly into a warning screen that it had been locked due to the "installation of unauthorised software". From that point on any attempt to get the tablet from that state or to simply flash the stock firmware, failed completely. "
I had the same experience. I installed everything and rebooted to see this. Was only annoyed that oem unlock won't be an available instantly but it was. I went to download mode flashed stock, installed twrp again and it was fine. If you couldn't go to download mode (with cable inserted into pc! I assume you must know it because you flahed it, thie was another new idiotic introductement by gnus, i thought i have broken tablet because i couldn't get into download mode, when i found out cable must be in not mentioned anywhere in the instructions, just like we must know it, when it never in the universe been the case) then it's weird bug. Because what you are describing sound like standard behavior for these tablets, but why you couldn't get out of it right away i don't kno, because i could. Moreover i had the same on s9 snap. On s9 i also has issues when oem unlock will never appear, until i run some command checking it status and it got instantly unlocked. I shared it tp developer but he only laughed. When i knio there is nothing to laugh, sung's firmware has millions of such unexplainelable behaviors, a lot of people are faced with it. If you had another tablet and got the same result then just pick up non tgy one and it will be good, i promise. Also who knows why you want note 10 and t s6
Click to expand...
Click to collapse
Thanks for all the info. The Note 10+ is my girlfriend's phone. I use sometimes as well when I don't feel like holding the tablet. The Galaxy A 8" with S-Pen is the perfect device.. not too small, not too big and has the pen. Unfortunately stupid Samsung decided to make it ridiculously low-end with atrocious specs, can't use it for any productivity.
VeEuzUKY said:
Thanks for all the info. The Note 10+ is my girlfriend's phone. I use sometimes as well when I don't feel like holding the tablet. The Galaxy A 8" with S-Pen is the perfect device.. not too small, not too big and has the pen. Unfortunately stupid Samsung decided to make it ridiculously low-end with atrocious specs, can't use it for any productivity.
Click to expand...
Click to collapse
and now Samsung has 11 and 12 inch tablet versions for the s7...lol (next thing will be maybe a 14 inch or 17 inch 'tablet') 8 to 8.9 is the right size for a tablet. Anything bigger is basically looking at an old-school tv screen from the '70s or '80s just 6 inches or so away from your eyes with your entire face lit up by the screen lol
mac231us said:
and now Samsung has 11 and 12 inch tablet versions for the s7...lol (next thing will be maybe a 14 inch or 17 inch 'tablet') 8 to 8.9 is the right size for a tablet. Anything bigger is basically looking at an old-school tv screen from the '70s or '80s just 6 inches or so away from your eyes with your entire face lit up by the screen lol
Click to expand...
Click to collapse
Haha, I absolutely agree with you
I'd love a 17" Tablet. Lol. Personally, I don't like any Tablet less than 10" - If I want something small, I'll use my phone.
@VeEuzUKY did you get your Tab rooted?