Related
I compiled ROM and flash it into the mobile phone, The phone screen is black after starting
Connect the computer with USB. I can see the two devices in the Device manager.
SAMSUNG Mobile USB Composite Device
SAMSUNG Mobile USB Modem
It is not same with the fastboot mode in the equipment . Is it right? Kernel has started?
run ADB devices, display 4dXXXXXXXXXXXX offline
What is the problem? Why show black screen? Kernel has launched?
No, the kernel hasn't booted yet.
Seems like not even the primary OS bootloader was hit yet, something went wrong and it probably fallback to download mode.
Try using ODIN, if neither ODIN recognizes this you could be stuck in something like Qualcomm Emergency Download Mode and variations for other brands.
One of my thoughts is that you flashed an unsigned kernel with SecureBoot on.
greenboxal said:
No, the kernel hasn't booted yet.
Seems like not even the primary OS bootloader was hit yet, something went wrong and it probably fallback to download mode.
Try using ODIN, if neither ODIN recognizes this you could be stuck in something like Qualcomm Emergency Download Mode and variations for other brands.
One of my thoughts is that you flashed an unsigned kernel with SecureBoot on.
Click to expand...
Click to collapse
+1
Hi Everyone ^^
I sort of got my Samsung Galaxy GT-S5660 bricked without being able to find a fix for it..
I've followed an installation Guide to the letter, yet i now find my Phone stuck on all sides
Been searching and reading XDA & Google, thus-far without any fix in sight :x
Setup:
- I'm running a Windows 8 PC, updated & running properly, all Drivers Installed
- Before all of this, the Phone worked properly on default ROM, un-tampered with, PC could connect and transfer files to the Phone while it was running. Didn't try the download mode until after brick.
Used this XDA Thread to first root the Phone, using Recovery Mode to install the zip from SD: http://forum.xda-developers.com/showthread.php?t=1111414
Then followed this Guide to the Letter to install the CM10.1, also installing it using Recovery Mode, installing the zip from SD: http://www.android.gs/update-galaxy-gio-android-4-2-2-jb-cm10-1/
Thats where the fun ended ... it rebooted and ... nothing :x
Resulted into this situation:
- Normal Boot (Pwr-Btn): The Phone wont boot, it first loads a static Samsung logo, then after a bit shows the ''GALAXY Gio GT-S5660" logo and just permanently holds on that
- Boot into Recovery Mode (Home-Btn + Pwr-Btn): No longer works, Instead of going into old Recovery Mode or CWM Recovery mode, it just displays the static Samsung logo for a looong time, then reboots into "Normal Boot" described above. So no more installing from SD Card ... No more Recovery Mode
- Boot into Download Mode (Vol-Down + Home-Btn + Pwr-Btn): No problem, displays the yellow "Downloading..." mid-screen. Problem is, PC's keep telling me "USB Device is not Recognized".. Any USB-Cable, any PC, none recognize the device. Tried every driver i could find, trying and retrying, the Samsung Kies Drivers and app as well, every version of it. Still, i can not get a PC to recognize the device in Download Mode, so Odin doesn't find it either.
- Boot into Emergency Download Mode (Vol-Up + Vol-Down + Home-Btn + Pwr-Btn): PC recognizes the device, Odin detects it aswel, i can do the Odin setup i found here: http://forum.xda-developers.com/showpost.php?p=20896513&postcount=2 , and Odin verifies all files correctly, detects the device on the COM Port, all seems well. When pressing the Start button in Odin it starts out fine, displays the log saying "Download Start..., etc", but it stops at "<1> setup connection...", and there it stays ...
Been trying to find an XDA-Thread or Google solution for this scenario but i'm coming up empty, thus i come here to post the problem ...
Nutshell:
- Phone wont Boot into Android OS, simply won't boot ..
- I can't boot into Recovery Mode to load from SD, simply no more Recovery Mode
- Can boot into Download Mode, but all PC's seem to throw up a "USB Device not Recognized" error, no matter the USB-Cable, thus Odin does not detect the Device
- Can boot into Emergency Download Mode, but Odin doesn't seem to want to install in this manner and halts at setting up the connection...
= What am i to Do????
Please Help! ^^
- Is there some magical driver that will result in the Device Being recognized while it's in Download Mode?
- Is there something i can use or do to install a CWM using Emergency Download Mode or SOMETHING? (Maybe get Recovery Mode working again, or have Odin work with Emergency Download Mode)
Thanks for your time,
Kind Regards!
x6XceS6x said:
Hi Everyone ^^
I sort of got my Samsung Galaxy GT-S5660 bricked without being able to find a fix for it..
I've followed an installation Guide to the letter, yet i now find my Phone stuck on all sides
Been searching and reading XDA & Google, thus-far without any fix in sight :x
Setup:
- I'm running a Windows 8 PC, updated & running properly, all Drivers Installed
- Before all of this, the Phone worked properly on default ROM, un-tampered with, PC could connect and transfer files to the Phone while it was running. Didn't try the download mode until after brick.
Used this XDA Thread to first root the Phone, using Recovery Mode to install the zip from SD: http://forum.xda-developers.com/showthread.php?t=1111414
Then followed this Guide to the Letter to install the CM10.1, also installing it using Recovery Mode, installing the zip from SD: http://www.android.gs/update-galaxy-gio-android-4-2-2-jb-cm10-1/
Thats where the fun ended ... it rebooted and ... nothing :x
Resulted into this situation:
- Normal Boot (Pwr-Btn): The Phone wont boot, it first loads a static Samsung logo, then after a bit shows the ''GALAXY Gio GT-S5660" logo and just permanently holds on that
- Boot into Recovery Mode (Home-Btn + Pwr-Btn): No longer works, Instead of going into old Recovery Mode or CWM Recovery mode, it just displays the static Samsung logo for a looong time, then reboots into "Normal Boot" described above. So no more installing from SD Card ... No more Recovery Mode
- Boot into Download Mode (Vol-Down + Home-Btn + Pwr-Btn): No problem, displays the yellow "Downloading..." mid-screen. Problem is, PC's keep telling me "USB Device is not Recognized".. Any USB-Cable, any PC, none recognize the device. Tried every driver i could find, trying and retrying, the Samsung Kies Drivers and app as well, every version of it. Still, i can not get a PC to recognize the device in Download Mode, so Odin doesn't find it either.
- Boot into Emergency Download Mode (Vol-Up + Vol-Down + Home-Btn + Pwr-Btn): PC recognizes the device, Odin detects it aswel, i can do the Odin setup i found here: http://forum.xda-developers.com/showpost.php?p=20896513&postcount=2 , and Odin verifies all files correctly, detects the device on the COM Port, all seems well. When pressing the Start button in Odin it starts out fine, displays the log saying "Download Start..., etc", but it stops at "<1> setup connection...", and there it stays ...
Been trying to find an XDA-Thread or Google solution for this scenario but i'm coming up empty, thus i come here to post the problem ...
Nutshell:
- Phone wont Boot into Android OS, simply won't boot ..
- I can't boot into Recovery Mode to load from SD, simply no more Recovery Mode
- Can boot into Download Mode, but all PC's seem to throw up a "USB Device not Recognized" error, no matter the USB-Cable, thus Odin does not detect the Device
- Can boot into Emergency Download Mode, but Odin doesn't seem to want to install in this manner and halts at setting up the connection...
= What am i to Do????
Please Help! ^^
- Is there some magical driver that will result in the Device Being recognized while it's in Download Mode?
- Is there something i can use or do to install a CWM using Emergency Download Mode or SOMETHING? (Maybe get Recovery Mode working again, or have Odin work with Emergency Download Mode)
Thanks for your time,
Kind Regards!
Click to expand...
Click to collapse
Try with heimdall, an alternative to Odin : http://glassechidna.com.au/heimdall/ . For the emergency download mode, you won't be able to do anything with it. And make sure you have the samsung usb drivers : http://developer.samsung.com/technical-doc/view.do?v=T000000117
Tried, same result
Dear TheIcE65,
Thank you for your quick response.
I've tried the USB Drivers you supplied, clean install
Unfortunately these drivers result in the same problem. While the Phone is in Download Mode, once connected windows still throws up a "USB Device not Recognized" error.
Heimdall also does not recognize the device, as Windows doesn't either.
Please help, I'd like to get this Phone un-bricked!
Kind regards
Anyone found a fix for this ?
Exactly the same issues here
same issue
facing the same issue. cant find any solution anywhere. hoping someone can help
So i somehow managed to brick my H6X ( BLN-AL20 ), and i have many problems :
1. No Recovery ( gets stuck on the screen where it says that it is booting to recovery )
2. Broken OS ( infinity booting on the ''Honor'' logo )
3. Fastboot & Rescue mode doesn't seem to work ( I connect my phone to the PC, i can hear the Windows beeping sound, but ADB doesn't recognize my device )
4. eRecovery seems to work, downloads the original ROM an everything, but then we are back to problem nr. 2 ( infinite booting again )
My only thoughts are that i could save my device using Fastboot & Rescue mode, but i can't seem to get it to work.
If anyone could help, that would mean the world to me!!!!!
Arcticparadox said:
So i somehow managed to brick my H6X ( BLN-AL20 ), and i have many problems :
1. No Recovery ( gets stuck on the screen where it says that it is booting to recovery )
2. Broken OS ( infinity booting on the ''Honor'' logo )
3. Fastboot & Rescue mode doesn't seem to work ( I connect my phone to the PC, i can hear the Windows beeping sound, but ADB doesn't recognize my device )
4. eRecovery seems to work, downloads the original ROM an everything, but then we are back to problem nr. 2 ( infinite booting again )
My only thoughts are that i could save my device using Fastboot & Rescue mode, but i can't seem to get it to work.
If anyone could help, that would mean the world to me!!!!!
Click to expand...
Click to collapse
Are you able to boot in to fastboot?
Yes, but ADB can't seem to recognize my device. ( When i type ''adb devices'' it doesn't show up )
Ok so i have noticed a weird thing. When my phone is in the Fastboot & Rescue mode, it doesn't show up in HiSuite. BUT if the HiSuite app is minimized and i connect my phone to the PC, HiSuite opens up and nothing happens. Basically it gets recognized, but nothing happens.
I somehow got to a weird screen on my H6X where there is an USB icon and 5% below it, and a chinese writing. After that a window on HiSuite popped up asking to allow connection in HDB mode. Anything i can do ?
After trying to restore stock OOS and rebooting fastboot my phone is now stuck in Qualcomm Crashdump mode. I have MSMDownloadTool installed but it won't open, it just opens a windows saying "Program has been started" after executing it.
I also can't reboot to the bootloader, the phone just turns on or off.
What to do?
From my rather long post in https://forum.xda-developers.com/t/...your-device-to-oxygenos.4180837/post-86563159 :
"connect the phone to the PC whilst it's still in CrashDump mode and then press Pwr + Vol Up until the phone buzzes and then hold Vol Up + Vol Dn and MSM will then connect."
Thank you, that worked. I have another question if you don't mind:
I tried to restore OxygenOS with https://forum.xda-developers.com/t/...xygenos-fastboot-roms-for-oneplus-8t.4348023/ but it cant find the create-logical device and delete-logical-device commands, also when I try to flash some of the image files fastboot complains about not being able to flash system critical files. I tried running fastboot flashing unlock_critical but that didn't change anything. Is there any other way to restore Oxygen OS with fastboot or is there any fix to my issues? I've been looking on the web for a few hours now, to no result.
petrolblue said:
Thank you, that worked. I have another question if you don't mind:
I tried to restore OxygenOS with https://forum.xda-developers.com/t/...xygenos-fastboot-roms-for-oneplus-8t.4348023/ but it cant find the create-logical device and delete-logical-device commands, also when I try to flash some of the image files fastboot complains about not being able to flash system critical files. I tried running fastboot flashing unlock_critical but that didn't change anything. Is there any other way to restore Oxygen OS with fastboot or is there any fix to my issues? I've been looking on the web for a few hours now, to no result.
Click to expand...
Click to collapse
The delete/create logical commands are in the thread OP, but you have to tap on "click to show" button.
Note that fastbootd is not the same as fastboot. And you need to be in that mode to avoid the "critical" warning and to be able to do the logical partitions stuff.
So, after massively failing to update my 8T I am stuck in a bootloop with a bit of Crash dump [dm-verity device corrupted force dump].
I am still able to access fastboot but that is it. I can't get adb working, when I attempt to enter recovery mode all I get is a black screen, MSM is not able to find my phone/I can't get my phone to enter EDL (been trying for about 5 hours now).
I feel so defeated by this can anyone help me?
Did you read my post (#2)?
Does your PC make a sound when you connect your phone to it in EDL mode? If so, try reinstalling the Qualcomm driver (though I've never needed to do that).
If you can get into bootloader, then you can try using the method in https://forum.xda-developers.com/t/guide-unbrick-or-restore-to-oos-using-only-fastboot.4289013/
BillGoss said:
Did you read my post (#2)?
Does your PC make a sound when you connect your phone to it in EDL mode? If so, try reinstalling the Qualcomm driver (though I've never needed to do that).
If you can get into bootloader, then you can try using the method in https://forum.xda-developers.com/t/guide-unbrick-or-restore-to-oos-using-only-fastboot.4289013/
Click to expand...
Click to collapse
Whenever I connect my phone to the pc it just auto-boots. In my devices the driver does show up. But I don't think I have been able to access EDL.
I did reinstall the driver as well, no change. I tried installing the drivers and MSM stuff on a 2nd pc, still unable to get it going.
I did come across this method and my phone/fastboot keeps erroring whenever I try to use cmd for anything beyond Reboot fast boot. It's weird.
Angilias37 said:
Whenever I connect my phone to the pc it just auto-boots. In my devices the driver does show up. But I don't think I have been able to access EDL.
I did reinstall the driver as well, no change. I tried installing the drivers and MSM stuff on a 2nd pc, still unable to get it going.
I did come across this method and my phone/fastboot keeps erroring whenever I try to use cmd for anything beyond Reboot fast boot. It's weird.
Click to expand...
Click to collapse
I see that your PC sees the phone (Qualcomm...) but has an ! against it. If you open that you should see the option to update the driver.
PS: you may need to flash boot, DTBO, and recovery in fastboot first before you can use fastbootd to flash the other partitions for the fastboot method.
BillGoss said:
I see that your PC sees the phone (Qualcomm...) but has an ! against it. If you open that you should see l the option to update the driver.
Click to expand...
Click to collapse
Right but where's the update? From everything that I can find it is the most updated version
Angilias37 said:
Right but where's the update? From everything that I can find it is the most updated version
Click to expand...
Click to collapse
I use the driver (Qualcomm HS-USB QDLoader 9008) from https://www.catalog.update.microsoft.com/Search.aspx?q=qualcomm hs usb 9008
OK
BillGoss said:
Did you read my post (#2)?
Does your PC make a sound when you connect your phone to it in EDL mode? If so, try reinstalling the Qualcomm driver (though I've never needed to do that).
If you can get into bootloader, then you can try using the method in https://forum.xda-developers.com/t/guide-unbrick-or-restore-to-oos-using-only-fastboot.4289013/
Click to expand...
Click to collapse
Ok I take back what I said! That link with the CMDs worked!
I really don't know what I did differently, probably skipped a step or something, but I was able to reset my phone!
Still unsure what is going on with the drivers but the crisis has been averted!
Thank you BillGoss! You are incredibly helpful!
Hi, I accidentally bricked my phone flashing the wrong image.
Now i can't turn off the phone, cant access to recovery or fastboot. (device doesn't respond when i click any button).
'Poco' logo is in loop. Anyone knows a way to install a ROM? Any way to access fastboot in this situation?
Try pressing the buttons for a long time. It resulted for me to get to recovery mode, but no to download mode. Sometimes it works.
I bought a poco x4 gt like that too, hoping to get it fixed, I believe the way to get it is via EDL mode and miFlas, but for now miflash still doesn't recognize the image of the poco x4 gt. I hope that in some future update I will recognize it.
i have same problem
Same problem here
did anyone was able to find a fix? or at least locate the test points for EDL?
mtk devices use a different way to access edl mode. in my case I access the edl mode, the computer recognizes it, the software recognizes it, but when running it says that SPflash still does not work with the scartter version of the rom that I downloaded
how did you manage to boot into edl mode? i tried several hw key combinations but it gives me "preloader handshake failed" or several BROM error.
i think my scatterfile seems ok. its just the brom/edl connection.
when you turn it on with the volume button less pressed and it connects quickly to the pc install the MTK driver and then run the python where it will read the brom
Mine already fixed
butaw1 said:
Mine already fixed
Click to expand...
Click to collapse
what did you do?
if any one want to fix his poco x4 gt bootloop only. can't reach fastboot or recovery. at first you need auth to bypass dim 8100 security. i found a person on github name Rafon he fixed my phone and it's working perfectly right now. his username on telegram is @Rafon24
same issue
the only way of fixing is through an authorized xiaomi account sadly
i however found a way to turn it off when nothing works:
press all 3 buttons (volume up, down and power for like 20 seconds)
and then it will turn off