hi everybody, i got a problem with my tablet, it's a samsung galaxy SM-t113Nu, i modified stupidly the file build.prop(cause my menu button doesn't work)and get stuck on the logo.
My pc can't recognize as a mobile, multimedia or usb device (appears as "SAMSUNG-Android" ) but recognize it as a device not specified
when i tried to enter into recovery mode i select "apply update from adb", why this is the only way that my pc can install a driver as mencioned above, else , just is an "unknown device", even in download mode is an "unknown device"
in adb mode appears as :
List of devices attached:
300492ee86641200 sideload.
so, i think i need a update.zip that contains a factory file build.prop, sideload maybe is the only way to send a package to mi tablet via pc.
please help
Related
Hi all
Just got me PoV Mobii Tablet und want to flash ModdedStock ROM.
My problem is, I cant get the Tablet into recovery mode.
I connected USB and Power and tried all keycombinations.
Home+Power on leads to "Prepare enter mmc update mode" and stuck there.
Left+Power on bringt up the same screen.
Right+Power on shows a selection screen where I can choose from "Android mass storage", ADB and "Other OS". I tried all three options and it booted to android, but my PC (win7) does not recognize it. Tried it on an other PC as well.
Can someone help?
OK, found the cause.
This Thread can be closed!
Hi all,
My phone is bricked with following syptoms:
1) Not being recognised in download mode
2) Adb without root acess (unable to push files)
3) No recovery
Detailed problems
I have a (Korean) Lg G2 (F320s) and its stuck on bootloop. It goes into download mode with Vol + with plugging into computer but the computer doesnt recognise it as attached...no sound, nothing in device manager and no found by Lg Flashtools or Kdz updater.
When simply turning on i connect it to the PC it shows as an ADB interface device and i have ADB but no root authorization (my phone was rooted before).
Lastly when i try to enter recovery it just flashes a couple of times and goes black...back light still on. In this mode when i connect it to PC it shows up several drives and phone comes up as Qhsusb_bulk device. I read a thread using UBUNTU to repair this but it wont work for me....the PC just hangs up and Ubuntu is unable to mount the drives (Even after the settings from Dconf Editor).
Please help i have been stuck for days
Please help
Please help ppl... is there a possible solution to the problem..?? JTAG maybe??
I am new to posting, but I have followed XDA for a long time and used it to install custom ROM's on other phones. However, I now have a problem with my wife's Samsung Galaxy GT-S5360L. I have searched for hours, but can not find a solution.
The phone is stuck in a boot loop. I can enter stock recovery mode. When I try to perform a factory reset, I get the following message:
E:format folume: rfs format failed on /dev/stl11
formatting /cache
Data wipe complete
After wiping the cache partition, the phone continues to be stuck in the same boot loop after reboot (Samsung logo appears on screen, followed by animation, back to Samsung logo).
The phone will not enter into download mode. When I press power+volume down+home, I see a white screen, followed by a black sreen, followed by another white screen. the suggested method of removing the battery, SIM, and SD card, and plugging into the computer while holding both volume buttons does not work. Odin will not recognize that the phone is connected.
I tried to connect the phone to two different computers. One runs Linux mint with Windows XP on a VM. This computer has always worked for flashing ROM's to other phones. Odin would not recognize the phone, and I received messages that the device was not properly installed.
I then tried to connect the phone to another computer with Windows Vista. This PC has Kies installed and Samsung drivers. Kies would not connect to the phone, and I also received messages that the device was not properly installed. Odin would not recognize the phone. I should note that the phone has interfaced with this computer sucessfully before.
This phone has never had a custom recovery or ROMs installed. It only has the original stock ROM. Is the phone's hardware defective, or can it somehow be fixed? Please post any links to threads that I may have missed. Thanks.
Download mode is only effected by a change in bootloader normally by Flashing incompatible firmware or a hardware fault
For flashing via odin kies is not required - its useless as it's not compaitable with the galaxy y for this purpose
You just need the Samsung USB drivers available from my firmware thread (links in signature)
It maybe possible to still flash the device
Once USB drivers installed
Enter download mode
Connect USB to pc
When the white screen appears push Vol up
Wait a few seconds
Open odin
Put the 3 firmware files in their places & flash
If it doesn't flash you will either need to flash a new bootloader via a jtag (repair shop) Or replace the motherboard - either way unless you can get it done very cheap it's more economical to buy a new phone
Thank you marcussmith2626 for your sound advice. The phone is working again. I will share the problems I solved in order to flash the stock ROM. Hopefully this will help anyone else that may have a similar problem.
The Samsung USB drivers had been previously installed on my PC running windows vista. I installed the drivers so that I did not have to use the bloated Kies software. However, when I tried to connect the corrupted phone to the PC via USB, it was not recognized, even though the correct drivers were installed. Below is the procedure I had to follow in order to connect the phone:
1. I connected the phone to the computer via USB. The phone had the battery installed and was powered off. After connecting to the computer, the phone started charging (battery icon on screen). Connecting in download mode at this point did not work. The phone must be powered off.
2. When the "found new hardware" notification box appeared, I had to make a note of each device that had been discovered.
3. I then had to open Device Manager from the control panel and find each device (the name in Device Manager matched the name in the new hardware notification).
4. I right clicked on each unknown device and selected "update driver software"
5. In the next menu, I selected "Browse my computer for driver software"
6. In the following menu, I selected "Let me pick from a list of drivers on my computer"
7. This brought up a list currently installed drivers. I selected the Samsung phone driver.
8. The driver then installed for the selected device..
9. Steps 2 through 9 were repeated for each new device discovered by Windows (each device listed in the "found new hardware" dialog).
10. I started the phone in boot mode (power+home+volume down, phone still connected to PC). I saw only a white screen. However, when I pressed the volume up button, the phone connected to the PC. Odin recoginized the phone and the stock ROM was flashed.
So, even if you only see a white screen, download mode can still be active. In my case, the drivers on the PC were not working correctly, probably due to the corruption of the original stock ROM. The drivers can only be added on my PC using the above method. The option to choose from a list of currently installed drivers was not available from the found new hardware wizzard.
Also, I will also say for reference that in the USA, the stock ROM from Brazil is the one that should be used so that the phone broadcasts on the proper GSM frequencies.
The drivers have been tricky with the Amazon Fire to say the least, and this seems to be because windows recognizes the driver as unsigned. To get around this issue, you will need to temporarily enable installation of drivers that are unsigned.
First go to Settings>Update and recovery.
from there click on advanced startup.
Your PC should say "please wait" then pull up a menu.
In this menu click on "troubleshoot" then click "start up settings"
Your PC will now restart
The PC will now boot into Startup Settings. Click 7 on your keyboard to disable driver enforcement then hit enter.
Your PC will restart once more.
Now your fire drivers should install as they are intended. Allowing installation of unsigned drivers can be a security risk, so once you have completed this process and installed the drivers reboot your PC and windows will automatically turn Driver Signature Verification on once again.
its smart to uninstall the fire drivers and reinstall them using the driver signature mode to make sure theyre installed correctly.
its also worth noting that in my case, the device needed a different driver from the downloaded for each mode (normal/on, fastboot, sideload), there is another thread on here for this but Ill add it here just in case someone else stumbles upon this first.
when installing the drivers in device signature mode, youll want to put the device in all 3 states while in signature mode to make sure you dont run into any problems trying to return the device to stock or moving on from fastboot etc. ( i did this, it was scary..)
1. when installing the drivers in signature mode youll come across 3 different drivers to choose from, the first driver "android ABD interface" is for when the device is in normal/on mode.
2. youll need to next boot the device into fastboot mode, i used the rootjunky amazon fire supertool and booted the device to fastboot, then disconnect and reconnected it to my pc and chose the second adb usb driver "android bootloader interface"
2. after installing that driver disconnect the device from the computer and power it down. power the device into the recovery mode by shutting it down then holding volume down and power (when holding the device in portrait orientation the volume down button is the one to the left) and navigate to the option that requires you to connect your device to a PC to load software (sorry i cant remember what option it is) it will say something like its waiting for a connection, connect the device to the PC and install the final driver "android composite ADB interface" now every facet of operation should have a driver, reboot your PC out of driver signature mode and if you were in the same boat as me, you should be able to sideload back to the android os, and flash roms or whatever else.
I have a Sprint Samsung Galaxy Tab A 10.1 (SM-T587P) from Sprint. The device is currently stuck in a boot loop. First, when it powers on, the black screen with the white text "Galaxy Tab A" text have "Recovery Booting" in the upper left corner. Then, proceeds to try to install an system update and it finally reboots to the startup screen ad infum when connect to a power micro usb cable. I have downloaded Odin to flash firmware; however, my PC fails to detect the device. In Device Managers in Windows 10, it states Unknown USB device (Device Descriptor Request Failed). However, when using a functional Galaxy Tab A 10.1 (SM-T587P) device manager can see that and I can transfer files over to the functional Tab A 10.1 via USB. ( I have install the latest Samsung drivers on my PC). Odin can't detect the tablet to install/flash firmware to possible fix tablet. Is there anything that I can do to repair the tablet?