sorry if i posted this the wrong place but nevertheless here is what i need help with.
i was looking for a stable 4.4.2 rom to flash on my at&t note 2 and i found this http://forum.xda-developers.com/gal.../rom-att-i317-ucucne5-mj4-stock-odex-t2802189
so i followed the instructions and flashed with odin and flashed the new bootloader since i was running lower than mj5
after flashing everything went well the rom was great until i wanted to take some photos from my laptop and send them to the phone.
the laptop recognizes a usb device but no prompt for folders or anything is being given, ive tried multiple usb cables and even multiple pcs to no avail.
so i tried reverting back to my old firmware 4.1.2 and the problem is still there
after digging around the computer in the device manager, the phone is being listed as SAMSUNG_ANDROID and is unknown followed by an error when i click properties which says:
This device is not configured correctly. (Code 1)
To find a driver for this device, click Update Driver.
so i tried updating the driver which failed and said an error occured data invalid
i really need some help on this because my phone isnt being picked up by odin or download mode
please help asap
Hi,
Please note the following sticky from the top of this section,
> General discussion > XDA Assist > The Purpose of XDA Assist [Please Read]
XDA Assist is here to help navigate the site, not for support. You've been shown your device section by Assist before, and have posted in it. That is where to post questions or issues about your device.
Thank you for understanding, thread closed.
Related
Hello I am new here, and also a noob in rooting, I recently rooted my Note 3 N900T on 5.0 it was all working good but I didnt had a recovery so I decided to install Rom manager and installed a recovery and clicked boot into recovery after that I got a bootloop so I flashed a stock firmware from Odin and then it failed after that My device is showing "Firmware Upgrade encounter connect to Kies", but now when I connect to the PC is says Usb device not recognized, I tried uninstalling both Kies and usb drivers and reinstalling still no good,
Please Help!!
Thank You
osamashakeel1999 said:
Hello I am new here, and also a noob in rooting, I recently rooted my Note 3 N900T on 5.0 it was all working good but I didnt had a recovery so I decided to install Rom manager and installed a recovery and clicked boot into recovery after that I got a bootloop so I flashed a stock firmware from Odin and then it failed after that My device is showing "Firmware Upgrade encounter connect to Kies", but now when I connect to the PC is says Usb device not recognized, I tried uninstalling both Kies and usb drivers and reinstalling still no good,
Please Help!!
Thank You
Click to expand...
Click to collapse
Hello and thank you for using XDA Assist.
Sorry to hear about your trouble but fortunately there is an XDA area dedicated to the T-Mobile Samsung Galaxy Note 3 N900T at http://forum.xda-developers.com/note-3-tmobile which would be a good starting place. I suggest you post your question with all relevant details in the friendly Q&A forum there at http://forum.xda-developers.com/note-3-tmobile/help where the experts familiar with your device will be best able to guide you.
Good luck!
EDIT: Member has now posted in the suggested area. Thread closed.
Hello,
I'm new to the forum. I decided to register, because here is the biggest base of android knowledge.
I need your help about my phone Landvo L500s. I tried to install custom rom-cyanogenmod 12 on it and eventually I bricked the phone. I have tried all the ways shown in internet tutorials to unbrick phone with factory rom, but I always get this error-BROM ERROR: S_FT_ENABLE_DRAM_FAIL (4032); [EMI] Enable DRAM Failed!
I have already installed USB VCOM drivers and my phone is recognised by device manager(Windows 8.1 x64) so that's not the cause.
Also I can't access recovery mode, as phone doesn't start any more.
If you know any solution, Please help me solve the problem.
Hi,
Thanks for using XDA assist.
I couldn't find a thread that could help you unbrick your device.
Please create a XDA account and post in the following forum:
Android Q&A, Help & Troubleshooting
Good Luck! - gsstudios
Already solved it!
I already solved the problem. I found more stable Stock ROM and flashed it...
Hello,
I was using Samsung Galaxy S3 SCH-I535 and tried to install a custom recovery named "LOCKWORKMOD" and unfortunately I failed.
Recovery mode was not working and displaying error that found on device is from another source and system can not start. (DAMAGED RECOVERY!)
Secondly, I used EZ-UNLOKER to my boot-loader but things went from worse to worst for me. After choosing , the never turned on after turning it off. I CAME TO KNOW IT IS HARD BRICKED.
Samsung GalaXy S3 SCH-I535 VERIZON.
: 4.4.2 KitKat
No charging.
Not turning on.
When is connected to PC via USB it shows new device detected named, RELINK HS-USB QDLoader 9008 (COM1).
I want to re-flash my with correct files to get it back to life but for doing this I need help.
1. Flash tool and procedure.
2. Required files for flash.
Please help me regarding this issue.
Hi HassanMujtaba000
Thank you for using XDA Assist
We were able to determine that you have already posted your issue here. It would be convenient that you give some time for our experts to analyse and answer you. Therefore, I will be closing this request here.
If you feel that it's taking too much, you may create a new thread at the below forum addressing our experts there.
Verizon Galaxy S III Q&A, Help & Troubleshooting
Thankful for your understanding.
Nice regards and good luck.
THREAD CLOSED
.
HassanMujtaba000 said:
Hello,
I was using Samsung Galaxy S3 SCH-I535 and tried to install a custom recovery named "LOCKWORKMOD" and unfortunately I failed.
Recovery mode was not working and displaying error that found on device is from another source and system can not start. (DAMAGED RECOVERY!)
Secondly, I used EZ-UNLOKER to my boot-loader but things went from worse to worst for me. After choosing , the never turned on after turning it off. I CAME TO KNOW IT IS HARD BRICKED.
Samsung GalaXy S3 SCH-I535 VERIZON.
: 4.4.2 KitKat
No charging.
Not turning on.
When is connected to PC via USB it shows new device detected named, RELINK HS-USB QDLoader 9008 (COM1).
I want to re-flash my with correct files to get it back to life but for doing this I need help.
1. Flash tool and procedure.
2. Required files for flash.
Please help me regarding this issue.
Click to expand...
Click to collapse
Hello,
I got a dreadful malware on my phone that takes it over almost completely, a hand cursor appears on the top right of the screen and it downloads apps left and right even if I disable download from unknown sources.
I have done a factory reset and that thing is still there, I can't seem to flash a ROM with all the tools I found online, flashify does not see the zip file, ROM manager does not work either. I have tried to follow various tutorials but always arrive at a standstill, the recovery apps just don't seem to see anything but folders.
My phone is a Jiayu F2, on the official site they recommend to flash with SP flashtools but I can't use that since my USB port is broken.
Are there any other options? I have superuser enabled, can do very little with my phone except in safe mode. Airplane mode tames the malware a little but not completely.
Malwarebytes does not see anything wrong with my phone anymore ( there used to be a riskware), yet it's still completely unusable.
Can someone help me please? I'm getting desperate and can't buy a new phone before 2 weeks
Thanks
Hello and thank you for using XDA Assist,
please ask in our Android Q&A section:
Android Q&A, Help & Troubleshooting
The experts there should be able to help you.
Kind regards & good luck
Trafalgar Square
XDA Assist
Hi everyone,
I own a Motorola Moto G2 (XT1068, dual sim) that came used with Android 6.0 on it.
I installed TWRP (twrp-3.0.2-3-titan.img) on it but failed to root Android 6.0 as well as 5.0 for whatever not yet understood reason. I don't do Android development for a living but I'm an IT professional, so handling adb and fastboot as well as reading and understanding instructions isn't a problem.
I flashed stock Android 4.4.4 (RETDEALL_XT1068_4.4.4_KXB21.85-14) which I successfully rooted by installing SuperSU via TWRP.
Next I updated SuperSU, verified that root access is indeed working and installed FlashFire, which I hoped to use to install OS upgrades, possibly without losing root. FlashFire is new to me (as of yesterday), everything else mentioned up to here is not.
I used the "Flash ZIP or OTA" action from within FlashFire and the previously downloaded update file in the /cache directory. I can't reproduce the file name since the phone is currently unusable and I didn't write the file name down prior to using FlashFire.
The state of the phone after this unsuccessful attempt was that of a broken USB device, i.e. unable to even register as whatever type of USB device. I learned that this can be fixed by holding the power button down for more than one minute, after which I managed to
get the phone to be shown as working "RELINK HS-USB QDLoader 9008" USB serial device in Windows 7 device manager.
I used the information in these two threads:
http://forum.xda-developers.com/moto-g/help/how-to-unbrick-moto-g-falcon-t3394788
http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
Since I started with Android 4.4.4 trying to upgrade to 5.0, I had hoped that the blank flash package for one of these Android versions would help fix my problem, but as of now, this doesn't seem to be the case. At the end of the blank flashing process, I get the message
FAILED <blank-flash:sdl-transfer-image:sdl-hello: error sending packet>
After that, the phone still has a black screen and cannot boot into anything. Repeating blank flash works after resetting whatever part of it is still working by holding the power button down for about 30+ seconds.
Is there anything obvious (or maybe even not so obvious) that I missed?
Thanks for reading and any help and/or pointers in the right direction.
Hello and thank you for using XDA Assist,
please create an account and post your question in our Android Q&A section:
G 2014 Q&A, HELP & TROUBLESHOOTING
The experts there should be able to help you.
Kind regards & good luck
Trafalgar Square
XDA Assist