I have tried to root my Note 8 and it did not work, (I went with the all in one option). Everything was okay, until I got to the actual root process in Toolkit 1.1.8. There were lots of failed messages (i think I had similar messages with my Nexus 7 root, and that was fine).
Anyway the Note rebooted okay, but there was not SU app, I tried to enable a AV firewall that requires root, and obviously that did not work.
I then tried to boot into recovery, and the tablet is now in
ODIN MODE
PRODUCT NAME: GT-5110
CUSTOM BINARY DOWNLOAD: Yes (2 COUNTS)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
There is that big android image and a mesage that states
Downloading...
Do not turn off target!!
What can I do please?
Is it safe to turn off and try again? (guessing so, becuase nothing is being downloaded)
One other thing that happened was towards the end of the 'root' process the PC tried to install drivers again, and that failed. I installed them via the Toolkit.
UPDATE
Thanks for reading this. It worked second time round, I just moved the tablet usb cable to a different usb port
Related
I'm new and I hope I'm not posting this in the wrong place or re-posting an old question, but I have been searching on this and other sites for days and haven't been able to find anything pertaining to my question, so sorry in advance If I'm not posting this correctly.
I have a rooted epic touch with rogue boot loader installed and UnNamed rom installed. I really liked the way it was running until I had some kind of malfunction happened and now the battery charge light won't shut off and the battery drains within a couple hours of standby time. the phone is only a couple months old and would like to take it to the sprint store as I'm assuming this is an obvious hardware issue. My problem is that my pc doesn't recognize my phone anymore so I can't flash back to stock and get rid of root, voiding my warranty. I have tried uninstalling and reinstalling kies and stand alone drivers multiple times with no avail. I've tried with the battery and sd card removed and have also tried on multiple pc's (2 win7 and and xp machine). every time it says the drivers weren't installed successfully and to replace the device being connected.
My question: Is there a way to revert to stock off of the internal memory of the phone? I know there are zip roms you can flash from the boot loader but I was wondering if there was a way to flash a rom from zip and install the original boot loader as well as get rid of root? Any help I can get would be extremely appreciated and again I apologize if I am wasting anyone's time by asking in the wrong place or re-asking a question.
Ok so I downloaded the Calkin's_Stock_Rooted_EK02_ROM_v1.0 and got it on my sd card via dropbox. Flashed and now have a stock rom on it which I think is a step in the right direction.
The only thing is now I have clockwork boot loader and still rooted. and still not recognizing on pc. anyone know of an unrooted zip with original boot loader?
I couldn't get my PC to recognize either of my 2 E4GT's, each due to a different reason, both issues were resolved by going through each step in sfhub's debugging checklist:
sfhub said:
This post is for the FAQ section:
Why is the install stuck waiting for device to be connected?
Your phone isn't being recognized by your PC as an Android device.
When the drivers are installed and the phone is properly recognized, you should see the following in start->run->devmgmt.msc
Code:
Android Phone
SAMSUNG Android ADB Interface
Modem
SAMSUNG Mobile USB Modem
Until you get the SAMSUNG Android ADB Interface to show up, neither ADB nor this script will work.
Here is a debugging checklist:
1) dial ##UPST# (##8778#) in the dialer and verify AP (or ALL) is checked (if CP is checked, phone won't be recognized as an Android device)
2) restart the ADB server (choose Option G to stop the server, it'll get started automatically by the script)
3) verify USB Debugging is ENABLED
4) verify USB drivers are installed (Win7-64bit see below)
5) try a different usb cable
If you are in Win7-64bit try changing the default install location for the drivers:
If you see an error like this:
Try running the CMD prompt (or e4gtauto-sfx.exe) as Administrator. Right-click on the CMD icon (or e4gtauto-sfx.exe) and select "Run As", then select Administrator.
If that doesn't work, try disabling windows firewall.
Click to expand...
Click to collapse
I went down that list and everything seemed to be in order but still no recognition by pc. I kept uninstalling and reinstalling the drivers and switching usb ports and it finally installed the drivers successfully long enough for odin to recognize it and to flash back to stock. As soon as it was done the machine stopped recognizing it again. Lucky break I guess. So I can now return it to sprint and deal with the hardware issue.
I would still like to find a zip file like the tar that I flashed that installs stock recovery and non rooted ek02 rom and kernel from cwm, if that's even possible.
Thanks Godswrath, for helping me out.
You could use wifi explorer to get files on to sd card and mobile Odin to flash the tar file back to stock....
Sent from my SPH-D710 using xda premium
Lol....I am a noob.
They make a mobile Odin? That would have saved my like 4 hours....
So here's the story:
1) Phone worked flawlessly before root. Did an OTA to stock 4.1.1
2) Flashed CWM with Odin v1.85 --> removed battery --> worked without issues
3) Applied SuperSU v0.87 and this didn't go without issue. While in CWM before the reboot, there was some extra prompt (I have rooted a S3 before and did not receive the prompt) however I cycled too fast and I don't think I hit the right option. The phone rebooted anyway and I had root so I didn't think anything of it.
4) Wanted to add files to my SDcard a couple of days later and the phone didn't show up in My Computer (yes USB debugging is enabled, tried all USB ports, changed cables, uninstalled and reinstalled Samsung drivers, I've never used Kies to do anything with my phone - disabled it from the start)
I thought I should revert to stock and start over so I booted into recovery and CWM wasn't there anymore but I still had SU access. I installed Mobile Odin and placed CWM (the .tar file) on my internal (Placed on SDcard --> moved with My files to internal) and flashed CWM and while I didn't see any errors, now I'm data wiped/factory reset but I still can't boot into CWM, I still have SU, and my phone is still not recognized by my computer.
Anyway for me to fix this issue?
Android version: 4.1.1
Baseband: T999UVDLJA
Kernel: 3.031-370274...SMP PREEMPT Fri Oct 19
Build number: JRO03L.T999UVDLJA
tmayne said:
So here's the story:
1) Phone worked flawlessly before root. Did an OTA to stock 4.1.1
2) Flashed CWM with Odin v1.85 --> removed battery --> worked without issues
3) Applied SuperSU v0.87 and this didn't go without issue. While in CWM before the reboot, there was some extra prompt (I have rooted a S3 before and did not receive the prompt) however I cycled too fast and I don't think I hit the right option. The phone rebooted anyway and I had root so I didn't think anything of it.
4) Wanted to add files to my SDcard a couple of days later and the phone didn't show up in My Computer (yes USB debugging is enabled, tried all USB ports, changed cables, uninstalled and reinstalled Samsung drivers, I've never used Kies to do anything with my phone - disabled it from the start)
I thought I should revert to stock and start over so I booted into recovery and CWM wasn't there anymore but I still had SU access. I installed Mobile Odin and placed CWM (the .tar file) on my internal (Placed on SDcard --> moved with My files to internal) and flashed CWM and while I didn't see any errors, now I'm data wiped/factory reset but I still can't boot into CWM, I still have SU, and my phone is still not recognized by my computer.
Anyway for me to fix this issue?
Android version: 4.1.1
Baseband: T999UVDLJA
Kernel: 3.031-370274...SMP PREEMPT Fri Oct 19
Build number: JRO03L.T999UVDLJA
Click to expand...
Click to collapse
Sigh...
Go here and follow the instructions. My 10 year old was able to do it without an issue.
http://forum.xda-developers.com/showthread.php?t=1949687
Reload the samsung drivers on the computer and boot into download mode. After loading the root66 version via odin download Rom manager from the store and load cwm.
Sorry OP but I does anyone know a way to connect to a PC without install the samsung drivers? I'm asking because I don't have permission to install anything to my computer at work. I've tried this http://forum.xda-developers.com/showthread.php?t=1711009
and this https://play.google.com/store/apps/...9pZC5tdWx0aW1vdW50c2RjYXJkLndpZGdldC5mcmVlIl0.
but still no go. They all treated my SD Card as CD drive which can read only. Any input is greatly appreciated.
jcbofkc said:
Sigh...
Go here and follow the instructions. My 10 year old was able to do it without an issue.
http://forum.xda-developers.com/showthread.php?t=1949687
Reload the samsung drivers on the computer and boot into download mode. After loading the root66 version via odin download Rom manager from the store and load cwm.
Click to expand...
Click to collapse
Thanks for the quick reply and I apologize if I wasn't clear but I was attempting to use Mobile Odin (my first time) because my phone was not being recognized by my PC and thus desktop Odin wasn't working either (even after reinstalling drivers and booting in download mode which I tried before posting).
However, I did find the answer eventually. If people have problems losing CWM after root, the error I made was not extracting the image file from the .tar before flashing with Mobile Odin. I eventually returned to stock but that didn't solve my PC not recognizing my device until I found this:
1. Uninstall any previous instance of Kies/USB driver
2. Download the latest Kies, specific to your S3.
3. Download Samsung USB drivers 1.4.6.0 (I've tried newer versions but they all failed)
4. REBOOT
5. Disconnect from internet (VERY IMPORTANT!!! - forcing Windows to install local drivers ONLY)
6. With the phone disconnected, install Kies + USB drivers downloaded in steps 2,3
7. Connect the phone and let Windows install the drivers.
8. Reestablish the internet connection.
Credit was given to Nacos on XDA
I didn't bother with Kies and obviously used the latest Samsung USB drivers. Problem solved!
Perfect.
Sorry if I sounded a little short. I am glad you found the solution.
after rooting my phone (samsung galaxy s duos 2) it is not getting detected by pc when connected using usb. Everything else works fine. Please help me to resolve this issue
[email protected] said:
after rooting my phone (samsung galaxy s duos 2) it is not getting detected by pc when connected using usb. Everything else works fine. Please help me to resolve this issue
Click to expand...
Click to collapse
Probably best if you ask in your devices forum if you think it had to do with how you rooted. They'll be more familiar with it and any problems that can occur.
http://forum.xda-developers.com/s7582
The only thing I can say is to uninstall kies, install standalone USB drivers (try both the latest and the older version released for your device on Samsung's site), reboot pc and phone and try to connect again.
Good luck!
Sent from my SGH-T999 using Tapatalk
tmayne said:
Thanks for the quick reply and I apologize if I wasn't clear but I was attempting to use Mobile Odin (my first time) because my phone was not being recognized by my PC and thus desktop Odin wasn't working either (even after reinstalling drivers and booting in download mode which I tried before posting).
However, I did find the answer eventually. If people have problems losing CWM after root, the error I made was not extracting the image file from the .tar before flashing with Mobile Odin. I eventually returned to stock but that didn't solve my PC not recognizing my device until I found this:
1. Uninstall any previous instance of Kies/USB driver
2. Download the latest Kies, specific to your S3.
3. Download Samsung USB drivers 1.4.6.0 (I've tried newer versions but they all failed)
4. REBOOT
5. Disconnect from internet (VERY IMPORTANT!!! - forcing Windows to install local drivers ONLY)
6. With the phone disconnected, install Kies + USB drivers downloaded in steps 2,3
7. Connect the phone and let Windows install the drivers.
8. Reestablish the internet connection.
Credit was given to Nacos on XDA
I didn't bother with Kies and obviously used the latest Samsung USB drivers. Problem solved!
Click to expand...
Click to collapse
well nobody wants to help me fix my issue so i will trthis and hope it works.. malfun after trap kernel root no wifi and phone malfunction not recognized by pc.. worked fine nevver any issues till i used g360t1 trap kernal root, didnt relise twrp had a official for his model or i eould have done that so now i need to go on pc to revert back then root using twrp but pc wont connect to phone ahj bullsht
now glad i have root but cant get on pc and all fixs do nothing, not usb cord or pc or mtp settings ect ect not drivers nothing like that.. can i flash stock using twrp, yes but no not me not my phone keeps saying fail so stuck with no wifi and cant connect to pc to tether and its pissing me off.. can someone please help like how has this never happened to anyone at all.. its not a common sense fix here
Don't work , tried all still not working after root
---------- Post added at 07:39 PM ---------- Previous post was at 07:38 PM ----------
Is there no fix ?
Hi guys,
Last night, as I was using some app on my phone, it froze and wouldn't respond to anything. So I held the power button and let it reboot... except it wouldn't. The screen when off, and came back to the Samsung logo screen, but it wouldn't go past that.
I've rooted this phone in the past, but I am currently unrooted and on the stock 4.4.3 ROM from sammobile. No crazy tricks or anything. The phone will go into download mode, but I ODIN flashing fails (I've tried 2 or 3 versions of ODIN), and it will go into Android system recovery <3e> (I get a red triangle over a dead Android) then it says things like
Failed to mount /efs
Failed to mount /system
Manual mode
Applying multi-CSC
Failed to mount /system (no such file or directory)
Failed to mount /cache.....
...there is a lot of this kind of stuff, and then it gives me the options to reboot, apply update from ADB, external storage, etc...none of which work. I've tried wiping partitions, factory resets, flashing with ADB...
In Download mode, when I try to flash the stock ROM using ODIN, it fails. Differently worded errors in different versions, but in short, it's failing to write.
It's been 24 painful hours of reading threads on XDA and loads of other sites, and trying to fix this. Finally, I think my problem (or combination of problems) might just be unique to me. My gut feeling is that the internal SD card is corrupted, and I need to re-partition it, but I'm not sure, and I don't know how...
Please help...
Try reinstall drivers, another port usb or another usb cable. First you can try reinstall drivers and change usb port.
dannchelu said:
Try reinstall drivers, another port usb or another usb cable. First you can try reinstall drivers and change usb port.
Click to expand...
Click to collapse
Hi Dannchelu. I tried that already. I installed Kies and uninstalled to get the latest drivers, but I've also tried to remove the drivers and install them separately. Drivers seem to be fine.
Also tried 2 separate cables, although I think I'm getting a successful connection with ODIN...just not able to write to the internal partition...
For repartition search xda for pit file . You need a pit file for your phone model which you can flash with odin. You need to read very good steps to follow because you can hardbrick your phone.
Sorry for bad english.
Hi all,
I got given this Tab3 because the smd power socket connection guts were physically broken inside socket.
Fitted new power socket (I'm an electronics repair engineer by trade) and checked all pcb (printed circuit board) tracks leading from new fitted socket to ensure there were no hidden breaks ...... new socket refit was 100% successful .....with no solder shorts / bridges and no broken tracks leading to mainboard.
I left Tab3 on charge overnight and next day switched Tab3 on only to be greeted with dreaded .PBL and .PIT failed issue.
After extensive (days!) research I gathered together all necessary firmware and tools and decided that its an easy firmware fix if flashed to an original Samsung SM-T210 UK firmware.
(Please note I dont know past history of this Tab3 .... I dont know if it was rooted / upgraded firmware etc ..... I doubt it though as it belonged to a 7 year old)
Big issue ..... Odin flash tool won't show coms port connection on PC via USB (have tried 3 different laptops one with XP, one with Win7 32bit and another with Win7 64 bit. I've installed / uninstalled / reinstalled multiple Samsung usb drivers that were verified to work with my Tab3 SM-T210 model on each PC .... no joy. Even installed / uninstalled / reinstalled Kies from Samsung .... still wont connect when Tab3 is in download mode. Have kept PC device manager open and nothing appears in device manager. Also have tried 6 different makes of Usb A to micro Usb cables. Have disabled all antivirus, UAC, firewall and Win defender etc ... still no go!
When I go into download mode (power + Vol- +Home buttons) a warning screen does appear BUT it only shows right hand side of graphic warning ..... left hand side is totally grey from top to bottom. (LCD screen is not faulty as it displays full screen info on failed .pbl / .pit flash memory checks) When I then select Vol+ this vertical half graphic info and half grey screen disappears just leaving the backlight on .... which I assume means Tab3 is in proper download mode?
I can go to all recovery modes which allows me to factory reset and delete user cache etc .... it seems to go through the proper routines of reset but upon restart .pbl and .pit failed error in red memory check list is still there.
I can also try and flash firmware file from external sd micro card .... Tab 3 recognises firmware OK and shows Install ..../SD, but then after approx 5 minutes it restarts to failed .pbl /.pit error list again.
Apologies for long post, but from reading above issues can anyone please confirm ....
1) Is half graphic normal when going into download mode? .... or does this point to a previous incorrect or unfinished flash issue?
2) I have downloaded proper .pit flash (LT02) file and original firmware flash for my Tab3 ..... can I flash this any other way other than using Odin ....eg is there any bdm flash method (direct hard wired) flash method to motherboard from external programmer ....like they use for car ecu flash recovery?
3) As I dont know exactly whether Tab3 was rooted / flashed with wrong firmware / incomplete flash upgrade, is there a software tool that can attempt to list what firmware is on my Tab3 at present?
4) I can get into ADB recovery within recovery mode but havent a clue how to use this method .... is this a possible recovery method to use, as I can see SMT210 ADB device in PC device manager when going into recovery mode?
many thanks in advance for help, :good:
Tab3SMD
OK all, here's more info .......AND another additional issue!
I got stuck back in again tonight because not knowing anything about Tab3 ADB recovery mode was bugging me, so here's what extra I've done so far
While "poking my nose" into tonnes more Xda forum troubleshooting guides I discovered I might need PitMagic tool to try and sort my .Pit partition error via ADB recovery mode.
I tried to find Pitmagic but discovered this is now part of EFS Professional, so downloaded EFS Pro and found this got me nowhere as I needed to also install Android SDK .... which also requires Java Development kit, so I downloaded the full Android Studio and Java JDK 8u91 and installed all (about 1.2Gb and requires ~ 4.2Gb hard drive space!)
Anyway, I now ran Android Studio and then ran EFS Professional, opened my Tab3 into ADB recovery mode and connected Tab3 and PC via usb .....
All looking good EFS reported
Initialising ADB server ..... Okay.
ADB server is running!
Searching for device..... OK
Connecting to device .....OK
Checking device status .....
THEN BAMMMM ....popup from EFS
Connected device is currently UNKNOWN
Please ensure ADB server has been authorised by the connected device by confirming your PC's RSA fingerprint, then press OK to continue
like, wtf! .... one step forward and 6 back!
Can anyone please tell me what this means or better still how to proceed from here?
Anyone?
Anyone??? .....Tab3 is still soft-bricked
I did figure out how to use ADB flash recovery mode using PC.
Unfortunately this also did not allow me to flash any firmware (original or custom) due to admin permissions
(I think this is due to USB debugging not activated within Developer options).
I'm sorta banging my head off the wall with this one .... a bit like what came first? egg or chicken?, because since Odin isn't being recognised by the PC, I cannot flash rom and even though the PC fully communicates with Tab 3 in ADB mode, it won't allow me permission to sideload any flash files because I reckon I need root based permissions, and since the darn thing isn't booting fully, I cannot manually change anything!
I then started thinking about trying to sneak around this permissions issue by flashing CWM or TWRP, but again flash fails due to no permission.
All in all, for me this has been a great learning experience tackling the multiple Android recovery modes, and since I feel so close to cracking this non boot issue, I hate to give up and bin it.
Perhaps someone with much more experience can please help me here?
Is there any way of forcing superuser status on this Tab 3 SM-T210, so as to allow me to flash stock rom via ADB recovery mode?
many thanks in advance for your help,
Tab3SMD
I have a P607T currently running Android 5.1.1. I have reset the tablet and installed root checker, and it says that "Root access is not properly operating or granted on this device" and says that KingUser is installed. I had previously used Kingroot to root a previous version of Android, but not sure why it is still installed. I am trying to figure out how to remove KingUser, but there is no icon and it does not show up in the app manager. I tried installing kingroot again and it shows in the app manager as a system app. Kingroot can no longer root my device on Android 5.1.1. I downloaded the 5.1.1 android rom for my device, but when I try to install it tells me that the footer is wrong and that signature verification failed and stops the install and reboots. One additional note, I have never been able to connect the tablet via USB to a pc, it has never shown up as a device or usb drive, so anything that requires me to connect to a pc won't work for me. (It charges fine, via usb and I have changed out the USB connector, but still no pc connection).
If you can follow my ramblings... I am just trying to get my tablet to be able to play movies and video from paid services, but it won't let me since it thinks the device is rooted. So does anybody have any ideas on how I can un-root my non rooted tablet or hide the root from VUDU, Fandango, Amazon, Netflix, etc.?
Have you tried a factory reset?
Yep, first thing I tried. I think kingroot or something wrote it's executable to the part of the system that doesn't get reset/overwritten on a factory reset.
Sorry to hear, try flashing all stock firmware from samsung from samsungs websight, flashing w samsungs flashing software.