Hello!
I have Note 1 N7000, about 2 and a half years old and I'd like to keep using it.
It has it's original OS 4.1.2, factory reset has been performed about 2-3 times.
None of the USB functions work - data transfer, tethering, OTG, nothing. I can only charge the phone (but not with any cable which indicates a bad [worn out] USB port).
The problem came out of nowhere (as it always does) - one day I wanted to transfer files via cable and the phone simply couldn't be recognized by the PC.
Before that I disabled some google's apps (and some others) that I never used so I performed a factory reset just to make sure I didn't disable somenthing required by usb to operate but with no luck.
I ordered a new USB port (the little board with usb) from ebay and installed it today by following instructions from youtube.
The phone can now be charged with any cable (as expected) but all other USB functions still refuse to work (not as expected).
I'm currently out of ideas, what could be the cause?
Dr Frane said:
Hello!
I have Note 1 N7000, about 2 and a half years old and I'd like to keep using it.
It has it's original OS 4.1.2, factory reset has been performed about 2-3 times.
None of the USB functions work - data transfer, tethering, OTG, nothing. I can only charge the phone (but not with any cable which indicates a bad [worn out] USB port).
The problem came out of nowhere (as it always does) - one day I wanted to transfer files via cable and the phone simply couldn't be recognized by the PC.
Before that I disabled some google's apps (and some others) that I never used so I performed a factory reset just to make sure I didn't disable somenthing required by usb to operate but with no luck.
I ordered a new USB port (the little board with usb) from ebay and installed it today by following instructions from youtube.
The phone can now be charged with any cable (as expected) but all other USB functions still refuse to work (not as expected).
I'm currently out of ideas, what could be the cause?
Click to expand...
Click to collapse
i would re-flash stock. you should be able to find a guide and files in your devices forum.
you could have some corrupt files, and a factory reset wouldnt fix that.
if stock doesnt fix the problem, you likely would have some additional hardware issue, im not sure what it would be though.
short story: I installed custom ROM (this one: http://forum.xda-developers.com/showthread.php?t=2179332 - the v16) and it still doesn't work.
Long story:
Stock recovery didn't let me to create a backup, nor it allowed me to install ROM from SD card. I couldn't flash via Odin or some other similar tool because my phone's USB doesn't work
I figured out I should try a custom recovery.
Is there any other way to flash a stock ROM (or any other) than installing it from a SD card? I haven't done this before so please, be patient
I found PhilZ Kernel (5.0.3) and CWM recovery (6.something), merged into a single .zip that could be put on a SD card and installed from there. It said it was for XXLT5 (which is my version of 4.1.2) if that matters.
Installed it and now I had that CWM recovery that gave me the ability to create backup and flash from SD card.
I downloaded stock ROM from SamMobile.com, identical to my original one (XXLT5, my country, my operator, TWO mark), put it on SD card, did a full wipe and tried to install it but it said "installation aborted".
Then I downloaded another stock from the same site, also XXLT5 and Croatia but no carrier specified, TRA mark. It was the same size (786 MB) as the previous one if it's of any importance.
That one also refused to install.
Then I searched for a custom ROM until something not too wild shown up, the link is in the beginning of this post.
It installed normally from SD card and it behaves normally too, except for the fact that the USB problem persists.
Dr Frane said:
short story: I installed custom ROM (this one: http://forum.xda-developers.com/showthread.php?t=2179332 - the v16) and it still doesn't work.
Long story:
Stock recovery didn't let me to create a backup, nor it allowed me to install ROM from SD card. I couldn't flash via Odin or some other similar tool because my phone's USB doesn't work
I figured out I should try a custom recovery.
Is there any other way to flash a stock ROM (or any other) than installing it from a SD card? I haven't done this before so please, be patient
I found PhilZ Kernel (5.0.3) and CWM recovery (6.something), merged into a single .zip that could be put on a SD card and installed from there. It said it was for XXLT5 (which is my version of 4.1.2) if that matters.
Installed it and now I had that CWM recovery that gave me the ability to create backup and flash from SD card.
I downloaded stock ROM from SamMobile.com, identical to my original one (XXLT5, my country, my operator, TWO mark), put it on SD card, did a full wipe and tried to install it but it said "installation aborted".
Then I downloaded another stock from the same site, also XXLT5 and Croatia but no carrier specified, TRA mark. It was the same size (786 MB) as the previous one if it's of any importance.
That one also refused to install.
Then I searched for a custom ROM until something not too wild shown up, the link is in the beginning of this post.
It installed normally from SD card and it behaves normally too, except for the fact that the USB problem persists.
Click to expand...
Click to collapse
you cant flash stock firmware through recovery.
take a look at this. it flashes stock firmware from on the device.
you will need to verify there is a version for your device, and how to use it. i have never used it myself. seems simple enough though. put firmware on device, flash with app. done.
Thank you for this, excellent app.
I flashed stock ROM successfully, but USB still doesn't show any signs of life (the only thing it does is charge battery).
...not a very bright future, right?
Dr Frane said:
Thank you for this, excellent app.
I flashed stock ROM successfully, but USB still doesn't show any signs of life (the only thing it does is charge battery).
...not a very bright future, right?
Click to expand...
Click to collapse
right, now that you are clean stock, there should be no reason its not working other than hardware.
edit, maybe try some different usb cables, could be you got a bad one.
I have several other cables and other phones (and other PC-s) at home. All combinations work on every PC.
It's only my phone that doesn't work regardless of which cable I use (or which PC I try to connect it to).
One friend suggested me to downgrade it to 2.3.5 (and then try to update it back to 4.1.2 in case it works [or even if it doesn't ]). His idea is that it might work because gingerbread uses USB mass storage protocol instead of MTP.
I downloaded some apps (tried a few of them) which switch from MTP to USB mass storage (in 4.1.2 ), one even required reboot after changing the setting but none of them gave any results.
Somehow I doubt this switching back to 2.3.5 would work, should I even bother?
Hi everyone, I ran into a serious problem today with my S6 G920F. I was running stock android 7 with Magisk and TWRP installed, I flashed the firmware using Flashfire from the Google Play store.
This morning the phone decided it would stop charging, a problem I faced with Android M. Anyway I reflashed the firmware package but this time i chose NOT to select the options to inject supersu and save my custom recovery, thinking that I could get it back to stock and re root it from there.
The phone previously would not boot if either Magisk or SuperSu was not installed (after i rooted it), it would just endlessly loop. Unfortunately this was the case after i flashed the firmware .
I assumed it would be a quick fix as I could just use Odin to flash the stock firmware . Unfortunately I was wrong again: my computer gives me an error message "USB Device Not Recognized" no matter how many times I uninstall and reinstall the Samsung Driver, Odin wont detect the phone either. Even Smart Switch is at a loss. The phone is currently plugged into my PC and is charging normally, I CAN boot into stock recovery and download modes.
SOMEBODY PLEASE HELP!! :crying::crying::crying:
Seems very obvious now but I found the solution I found the original cable that came with the phone; plugged it into the PC and just like that the computer registered that it was a Samsung devices and started installing drivers right away, seems like the P8 Lite cable I was using isnt a data cable?
I was able to flash TWRP using Odin and flashed Magisk using TWRP. All is well
hey everybody!
i was using my galaxy a3 2017 (SM320FL) for half a year with lineage os (15.1) and flashed the latest build (Lineage 15.1-20180821-UNOFFICIAL-a3y17lte) some weeks ago.
i allways noticed little bugs etc. but all in all it worked for me.
since a week now, the phone won't boot into the system anymore if not connected to charge. i can still boot in download mode and recovery without plugging it in but not into the custom rom. as soon as i deconnect it (when using the custom rom) it reboots and gets stuck at the samsung screen.
that wouldn't be that bad if the usb connection was not dead as well. that happened a few month ago allready. i tried to connect it via odin, kies and smartswitch in download mode and recovery. but nothing. i also reinstalled the drivers via kies. i also flashed "ressurection remix oreo" to check wether it works with different roms but it didnt.
does anybody here have an idea what i can do to make the usb connection work? or is there a possibility to flash the firmware without it?
device SM-320FL
Android 8.1.0
TWRP 3.2.3-0
Bootloader: 0x030c (?)
EDIT: i guess this thread is supposed to be in the device-forum but i'm not able to move it myself am i?
EDIT: the problem turned out to be broken cables. i tried with a third one and usb is working fine.
Sorry to start a thread on this old device and guessing there may not be anyone who can help me.
I flashed the Lenovo VibeUI ROM from needrom which seemed to work well, but I wanted to go back to stock and used the Ulefone 'onekey flashing tool' which usually worked to go back to the stock ROM. This time there was an error message, so I used SP Flashtool to flash the stock rom.
However the phone appears bricked - no screen, no charging indicator when plugged into the charger or USB on PC, whether latest official V1 or V2 ROM flashed. Not identified by PC as plugged in, but with battery removed, it appears I can 'flash' stock ROM using SP FT or Onekey official flashing software, but it is still 'dead' when battery reinserted.
Even though flashing the ROM with SP Flash Tool and the official Onekey flashing tool appear to flash the ROM to the EMMC, the phone won't even boot to the boot logo. Plugging in the charger doesn't show the charging indicator. I think the issue is with the 'ERROR: NAND flash was not detected!' message when I do a memory test. Not quite sure how this happened.
I thought it was difficult to brick MTK devices, but I seem to have achieved the almost impossible! Does anyone have any idea how I can recover from this bricking? The phone is recognised by SP FT so I hope there is a possibility.
Is there an easy way of solving this as I would like to donate this phone to someone who needs it? Tried lots of 'fixes' from XDA and other sites, but nothing working so far.
Any help/advice greatly appreciated.
:fingers-crossed:
Hi, I tried to flash LineageOs to a Cubot King Kong Mini using this guide: https://forum.xda-developers.com/general/rooting-roms/installing-custom-rom-cubot-kingkong-t4050815
I had to flash recovery_TWRP.img, lk_patched.img and vbmeta.img in order to avoid orange and red states, but I couldn't be able to run LineageOs.
Then I flashed stock rom, and the phone worked ok for a couple of hours. Then I realized that I didn't lock the bootloader, and after running the command "fastboot flashing lock" the screen went to black and buttons didn't respond.
The threat mentioned at the begining of this post, says that waitting for battery discharge will bring phone back to life again, but my battery didn't discharge for 11 days, so finally I disassembled my phone, I removed battery with the hope of getting same result as running out battery, but the problem still persist.
There is any way to solve this problem?
Finally I could bring it to live flashing stock rom with SP Flash Tool, both files downloaded from here:https://www.cubot.net/index.php/platform/Support/detail/id/311/cid/8.html (I suggest you to download the instructions posted in that site)
At first, I tried it in linux (with SP Flash Tools downloaded from another site), the last version of SP Tools didn't recognize the MT6761_Android_scatter.txt, and v5.18 recognized it, but flash process was stuck at 0%.
Then I tryed at win 10 with downloaded files from cubot website and it worked (no VCOM drivers need to be installed)
My battery was empty, but after flashing I had to wait arround 2 minutes while usb wire was connected to phone, to see the empty battery icon.
After that, I could turn on my phone.
Thanks,
pikas81 said:
Finally I could bring it to live flashing stock rom with SP Flash Tool, both files downloaded from here:https://www.cubot.net/index.php/platform/Support/detail/id/311/cid/8.html (I suggest you to download the instructions posted in that site)
At first, I tried it in linux (with SP Flash Tools downloaded from another site), the last version of SP Tools didn't recognize the MT6761_Android_scatter.txt, and v5.18 recognized it, but flash process was stuck at 0%.
Then I tryed at win 10 with downloaded files from cubot website and it worked (no VCOM drivers need to be installed)
My battery was empty, but after flashing I had to wait arround 2 minutes while usb wire was connected to phone, to see the empty battery icon.
After that, I could turn on my phone.
Click to expand...
Click to collapse
Well, I removed the battery and the kkm2 is up and running again. thanks.