Model Number: SM-G955FD
I Think i bricked the phone when i installed a TWRP update by flashing the twrp file as an .img file after renaming removing the .tar extension from the file. Currently im stuck in a bootloop where i the device shows up as an unrecognized device in windows when im in download mode. When Booting up i get red Text saying " Could not do normal boot. Invalid Kernel Length"
For those who would say: "Install USB drivers" --> The usb drivers have nothing wrong with them, i tried out another similar phone ( SM-G955FD ) and it works, i flashed stock, flashed TWRP, no problem with that other phone. But when i Insert the bricked phone with it on Download mode, all i get is that its an unrecognized device, device descriptor failed. (This is ever since a long time ago, Even OTG doesnt work somehow, but the device charges fine, and when i use my external SSD with a USB C to USB C wire it shows up).
For now What i have done is:-
I Tried to boot into Recovery -> Doesnt work, its stuck in a bootloop (I think its because i flashed the TWRP file as . img into the recovery Partition).
Booted into Download Mode -> It works
I Opened up the Phone and swapped out the Motherboard with another one from an S8+ with a semi functional Screen. Download mode works, phone works fine, nothing wrong with it, board is just old and i would prefer to fix the other one
What works:-
Download Mode
the USB port has nothing wrong with it. i Swapped in another USB board from a similar phone which shows up in odin and it still would show up.
What doesnt work:-
Recovery mode Doesnt work.
I believe its a Kernel/Software issue. Share your thoughts on this.
For now, i am running the phone on an older board from a phone with the same Model Number SM-G955FD with the Original Parts except the Motherboard. Even though i am somehow fine, i do not want the other board go to waste.
[*Reserved*]
_[*Reserved*]_
Related
Hi
As many people here i've encountred a problem with fota while being using a rooted ROM (g.lewarne ROM)
Now my phone is bricked. I can't go into recovery nor Download mode. I only have the LG logo for moments with error: secure booting error!
cause: boot certification verify
When i plug my phone it is not recognized in the hardware manager. I've already installed Drivers.
All i have in the hardware manager is a new hard under name QHSUSB_BULK that needs driver.
I have just one hope to get my phone alive, by reconizing it again by my computer, then maybe i can go under download mode.
I've tried everything but nothing could work without download mode.
PS: I've made a hard reset, which was maybe a silly decision.
By the way, after installing the OTA my phone went into CWM Recovery, it was detectable by adb, i used adb to reinstall TWRP, then i used command
"adb reboot download" instead of "adb reboot recovery", then i had never seen the CWM recovery again, only the mentioned above error.
After few seconds my phone screen goes black but the phone is still on since i can see light at the corners of the phone.
and it is not reachable by adb.
It makes me crazy now.
once i plug it to the computer it gives me plenty drives to format and one drive with only one folder inside called image, only readable, with many files inside.
Could you please help me to get my phone alive?:crying:
I'm on a rooted I337 that has been factory reset and under normal boot originally told me that normal boot has failed and was stuck with downloading.... but now tells me to select recovery mode in Kies also Download mode is still accessible. Before the crash I was working with a towelrooted 4.4.2. The problem is that nothing I do allows my computer to recognize it, It tells me that the device has malfunctioned and can't be identified. I've changed usb ports and cords and uninstalled/reinstalled drivers. Kies and Odin don't recognize it, but when I took it to a phone repair shop they were able to push a file that changed the normal boot error to what it is now, he gave it back to me to mess with and I could fix it if I could connect to it. Any help with this would be amazing
Thanks in advance
My I337 just got soft bricked earlier today, I made changes to my build.prop file to make it appear to be a Nexus 5, and rebooted just fine. I initially made a backup of the stock build.prop, so I decided to revert back to the stock file. when I rebooted, it gets frozen after the samsung screen and vibrates on any button press. I can boot into download and recovery mode, but I am unable to access the device via adb or kies.
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.
Well. First things first. the root of the issue is probably a bad usb port i guess as it's very unstable it even sometimes reboots into download mode on its own when i plug my phone to charge or even gives a Not charging state until i replug it many times then it gives the normal charging (AC) so it's a really messy one.
that's the usual anyway i was rooted and flashed a lollipop rom normally then bugged some apps so i decided to reflash stock kitkat rom however like i said it's a bad usb connection so sometimes the flashing goes slowly and i have to replug the cable for it got smoothly again.
this time i noticed this at 15% and instead of staying in download mode stuck at that the phone rebooted and ofcourse this time only a black screen no download mode no recovery no nothing i guess a typical hard brick? this is my first time dealing with a hard brick so i didn't know what to do at all so i'm still figuring out stuff anyway i installed Qcomm drivers and checked the device manager it's the 9006 one not the 9008 and it shows many drives on my pc (windows 7 64-bit) but no partitions in windows xp 32-bit on another pc and on the laptop it gives no drives i think. i tried with SRK tools it says everything as it should but when it's done i unplug the cable then reboot however still shows many partitions and no download mode.
I don't use my phone alot however i don't own another one so i kinda need help fast please so if anyone has any ideas don't hesitate please.
Thanks in advance.:good:
Update: After following the linux method i now don't have a black screen only stuck on lg logo and still no download mode.
the phone isn't recognized by the pc at all not even 9006 or 9006
the recovery gets stuck at processing and it doesn't say fastboot either on the logo screen.
Croshio said:
Well. First things first. the root of the issue is probably a bad usb port i guess as it's very unstable it even sometimes reboots into download mode on its own when i plug my phone to charge or even gives a Not charging state until i replug it many times then it gives the normal charging (AC) so it's a really messy one.
that's the usual anyway i was rooted and flashed a lollipop rom normally then bugged some apps so i decided to reflash stock kitkat rom however like i said it's a bad usb connection so sometimes the flashing goes slowly and i have to replug the cable for it got smoothly again.
this time i noticed this at 15% and instead of staying in download mode stuck at that the phone rebooted and ofcourse this time only a black screen no download mode no recovery no nothing i guess a typical hard brick? this is my first time dealing with a hard brick so i didn't know what to do at all so i'm still figuring out stuff anyway i installed Qcomm drivers and checked the device manager it's the 9006 one not the 9008 and it shows many drives on my pc (windows 7 64-bit) but no partitions in windows xp 32-bit on another pc and on the laptop it gives no drives i think. i tried with SRK tools it says everything as it should but when it's done i unplug the cable then reboot however still shows many partitions and no download mode.
I don't use my phone alot however i don't own another one so i kinda need help fast please so if anyone has any ideas don't hesitate please.
Thanks in advance.:good:
Update: After following the linux method i now don't have a black screen only stuck on lg logo and still no download mode.
the phone isn't recognized by the pc at all not even 9006 or 9006
the recovery gets stuck at processing and it doesn't say fastboot either on the logo screen.
Click to expand...
Click to collapse
You must have flashed wrong version of the rom .
After trying the linux method, if you cant get into fastboot mode, recovery or not in download mode, then try this : http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
This requires you to open your phone so be cautious .
Thanks I followed that guide. Download mode after. Using the Windows tool instead of Linux then flash tool normally.
Hello,
I have a galaxy note 4 that was working fine. First the phone couldn't be recognized by any laptop as it showed USB DEVICE NOT RECOGNiZED.
When this happened, i tried flashing CWM using my phone only because it didn't show on ODIN, using FLASHIFY. i downloded a CWM.img file and flashed it i clicked continue, the app asked me if i wanted to reboot the phone, i said yes, then this happened. My phone now is showing me the samsung logo when turned on with RECOVERY IS NOT SEANDROID ENFORCING in red on the top corner. i tried factory reseting the phone, but it wont boot into recovery mode to factory reset it, it only shows the logo and (RECOVERY IS NOT SEANDROID ENFORCING). when pushing POWER button + HOME+ volume down to go into downloading mode, the phone does so, but when connected is showing me again USB DEVICE NOT RECOGNIZED, it's is not recognized by ODIN, every other phone that i tried this on is recognized by odin and by the PC . i have tried reinstalling the samsung drivers several times, unistalling USB BUS, changing cables and using original ones, changing laptops and PC, kies, heimdall gremlin remover and nothing, the phone is not recognized by the PC as it shows in device manager as (unknown usb device (device descriptor request failed)). so anything that can be done using connection to PC is out of question because IT IS NOT RECOGNIZED BY ANY PROGRAM.
At first, i thought it was the micro USB adapter not working correctly or maybe having bent pins as it was charging but not transfering DATA, so i took it to a repair shop and changed the port completly, but NOOO THIS WAS NOT THE PROBLEME, the phonse still could not be recognized...
I have already succeded in rooting the phone several weeks ago without having any problems.
My probleme is that my phone is not recognized by odin heimdall or PC, it can't boot into recovery mode to do a factory reset, and is stuck on (RECOVERY IS NOT SEANDROID ENFORCING.)
Please help, i have TRIED EVERY THING !!!!! :crying::crying::crying::crying::crying::crying:
bro, you need to change the connecting cable, got myself at same situation & same error. I changed my usb cable, put note 4 in download mode, reinstall samsung usb drivers and odin detects it, installed stock rom & its working again. i wanted to root my galaxy note 4 sm-910f, i tried several times with different odin versions, used CF-Auto Root but it got stuck at bootloop every time i do with same Seandroid enforcing message.
nop, didn't work..