i spent like 10 hours on the internet searching for a way to root my gnex maguro without using the usb cable, yet there's absolutely nothing.
my phone is unlocked but needs rooting and needs a custom recovery. is there absolutely no way i can either get to boot a custom recovery or to root it without the usb?
I mean, it doesn't make sense. why does the phone need to connect to a pc to download and run a file that can be run from its internal storage anyway? and even if google doesn't want this to happen, is it so hard to do an exploit in order to flash a file from the internal storage? and i'm even more surprised by the absense of manual installation of supersu, there is no way to put the damn files in the right place without running the recovery. why?
and for transporting data to the phone, there's airdroid which works pretty well.
please help me my usb port is broken and only charges, no data throughput capabilities :crying: :crying: :crying: :crying:
So apparently there exist 2 apps on the play store which enable add connection over WiFi - WiFi adb. All this time for nought, this is the first thread on the Internet that has the solution for rooting without USB. The end.
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
Can anyone please assist to get data off an S3 which sticks at the blue-backed throbbing SAMSUNG splash screen just after the android rocket take-off.
The history is that the phone started constant-rebooting and I left it off for a few weeks. Then I took it into a shop to get the power switch replaced and the repairer noticed that it no longer reboots, it just sticks at that SAMSUNG screen. When neither of us could get it into safe mode, he diagnosed that it was "definitely" a software problem. Resetting caches from recovery mode doesn't do anything and as I am trying to get data off it, I am a bit reluctant to follow other solutions I have found here and do a master reset!
I THINK this device is rooted (with towelroot)? See below
I can get to an Odin screen and can get the device recognised on the computer and wondered if I could do resets from there with one of the 4 files included with 3.07. Curiously enough one of them did succeed (though the success was too quick to convince me it had actually flashed very much) and the device did reboot but still got stuck at the same splash screen! Taking the battery out and restarting/cleaning caches again etc didn't help and now, none of the Odin files will 'flash' successfully, which is why I am not sure if I am still rooted or if something is returned to stock. I am just not sure which file or what exactly flashed successfully and what it did to the ROM, bootloader, CID, etc etc etc. SO I am assuming that if I can still load Odin and get the S3 recognised, it is still rooted.
Is there anything else I can try either through odin or independently to get me into the os please? I have loaded skipsoft and run it and it has connected to the S3 (and changed things) just by connecting to the computer in download mode: But I can't see where in skipsoft I can diagnose or correct whatever is wrong
Flash TWRP via Odin, boot into TWRP, mount data partition, connect the phone to a computer, and try to copy the phone's data to the computer.
What that guy said ^^^ Install a new OS for your system which should replace your old one. You don't need to boot TWRP if you are going to boot a new OS. My method involves you losing all your data so you have been warned. You can get the stable version for that here http://techbeasts.com/update-t-mobi...o-android-4-3-jelly-bean-t999uvuemjc-guide/2/. Good luck
Thanks for that guys but I have apparently already loaded Philz and it SAYS it has backed up the data and/or storage to sc card and I am wondering if Ican restore it to a new Galaxy J7. I especially need to figure out if I can restore telephone text messages from the S3 onto the J7 but i could make do for the moment with knowing whether such messages have made their way onto the SD card.
Yes, I am a bit reluctant to do a full wipe and restore until I can figure this out.
Or if I can access the files through my computer as you suggest, what file / format would they be in?
If you used Philz to create a backup, I don't think you'll be able to restore the data to the J7, but I could be wrong because Philz hasnt been updated for a long time which means there may be no Philz for the J7.
Philz can only be restored with Philz and possibly cwm.
I got Philz installed through Skipsoft but am wondering whether there is any newer utility I can install over whatever Skipsoft has put there? Or is that what TWRP is?
I am a bit reluctant to install anything through TWRP if it is going to not only overwrite the OS but also delete all the data I am trying to access! But is there any utility which might conceivably get my phone working again without deleting all my data please?
If I load T999UVUEMJC_T999TMBEMJC_TMB,md5 through Odin, will it delete all my data??
Flashing twrp should not over write the rom, only the recovery.
Was the phone recognized as a removable when it was booted into philz?
audit13 said:
Flashing twrp should not over write the rom, only the recovery.
Was the phone recognized as a removable when it was booted into philz?
Click to expand...
Click to collapse
Why did you ask me that? 'cos I was pretty sure it was recognised but checked again and it isn't recognised by the computer at all when I plug it in (and obviously isn't recognised by Odin)
Philz shows as Touch 6.26.6 and ClockworkMod v 6.0.4.8
Why would I ask? Because twrp can mount the phone as a removable drive to copy off the data as you wanted to do in your original post.
audit13 said:
Why would I ask? Because twrp can mount the phone as a removable drive to copy off the data as you wanted to do in your original post.
Click to expand...
Click to collapse
Sorry to harp but are we agreed generally that there is no way of getting this phone working again, - whether with some utility or by re-flashing the stock or some new ROM?
Once the phone starts hanging at that third throbbing SAMSUNG screen, is it effectively dead save only for the purposes of getting data off it as a media device please? I really need to access my text messages and couldn't even identify them on a file directory and wouldn't know what format they were in if I could access the file browser. That was sorta a last resort but I am now downloading T999UVUEMJC_T999TMBEMJC_TMB for installation through Odin? Or for installation through Philz if I can get the file onto the SD card.
Did you try twrp and use a otg usb?
It really depends on how much your time is worth.
audit13 said:
Did you try twrp and use a otg usb?
It really depends on how much your time is worth.
Click to expand...
Click to collapse
I will keep retrying to see if it is something I am doing wrong but whereas Skipsoft installed easily, i dont seem to be able to install twrp on this nonbooting pda?
If the phone is not recognised by the computer, either the drivers are not working properly, the USB port is damaged, or the USB cable is not compatible with Odin.
Until the phone is recognised in Odin, you can't flash a stock rom from sammobile.com.
audit13 said:
If the phone is not recognised by the computer, either the drivers are not working properly, the USB port is damaged, or the USB cable is not compatible with Odin.
Click to expand...
Click to collapse
I am not exactly a newbie at this but I am beginning to wonder if I havent just got a developing massive hardware failure. I have tried a number of computers, including ones which formerly recognised the computer/cable/S3 setup and none can now recognise the phone, eg in Odin.
The phone is detected on plugin to Windows 10 (with the recognition beep) and is then not seen in windows explorer. Changing cables doesn't do anything. I am assuming it should automatically appear on the drop-down menu in TWRP's app in the playstore. That menu only shows a phone I plugged into the system about 6 months ago (without it being rooted) and asks for root permissions on this now-nonexistent phone.
The phone is not now recognised as it was up till only a few days ago in XP. Nothing is now recognised on a Mac, though on all three units the phone charges.
Restarting in download mode a few times changes nothing.
audit13 said:
.Until the phone is recognised in Odin, you can't flash a stock rom from sammobile.com.
Click to expand...
Click to collapse
The only other thing I can think of is putting some TWRP file (?) on an SD card, booting into recover/Philz and can i not install TWRP or reflash some ROM from there?
I'm not sure if twrp can be flashed from Philz as I have always flashed TWRP via Odin.
You have done everything I would have done to get the phone recognized short of a installing a fresh installation of a Windows OS.
You could also try Heimdall (http://glassechidna.com.au/heimdall/).
Hello everybody.... I write because I'm facing a problem that's causing lot of headhache:
I have this Samsung A3 (SM-A320FL) with broken screen, no USB debug, no root and stock recovery and I need to retrieve data from it.
I tried almost everything:
- programs like Dr.Fone, but the model wasn't supported
- connect the smartphone to the pc, but I can't confirm the mtp connection from the first
- used a USB otg splitter, one port filled with a mouse and another connected directly to the pc, but the smartphone wasn't even seen
I was thinking to flash a custom recovery to use adb, but:
I don't even know what version of Android is installed, nor firmware and I think that encryption was automatically turned on, so unless someone of you has a solution, the best for now is to repair the screen.
The situation is interesting but honestly I didn't see as many solutions...
Sent from my Pixel 2 using Tapatalk
Is there any way to backup my data from a S4 mini with a completely broken display? full disk encryption off, locked, USB debugging off, running kitkat. Thx.
Of course! If you have a custom recovery like TWRP it often allows adb access, using which you can 'pull' the internal storage off the device. In many recoveries MTP access is even enabled by default using which you can simply access the files through USB. If you do not have a custom recovery you can use fastboot or Odin to install one.
That said, it might be easiest to just replace the screen. A new one is not that expensive. Or buy a second hand S4 Mini and put your current motherboard in that one.