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
Related
hi there.
maybe I am using wrong words but I cannot find any post similar to my subject.
I am on stock ICS but it is not working well - I wanted to downgrade, but it looks like it is not possible to downgrade on stock recovery. I know I have to change the recovery to sth else like ClockWork.
I know about fastboot way - and here my problems starts.
I have all the drivers, phone is visible in Device Manager while it is booten into Android. I can go into Fastboot mode BUT
when phone is in fastboot mode it is not visible in Windows Device Manager at all.
It is not a driver problem. There is no new device I can use the driver for.
I tried different computers. Win7 64bit and 32bit and WinXP 32bit
My phone does not show up on any of them.
I think it ia a problem with the bootloader - my current version is XXKL1 - as when I am in the fastboot mode my volume keys are not working, while they work perfectly well in recovery or in the OS.
Any ideas appreciated.
Cheers
My phone wasn't showing in w7 i had turn on usb debugging in settings -> developer options. I m not sure if this helps but might be worth a try
Sent from my Nexus S using Tapatalk
Thx gm'
It is not an issue for me to connect to Windows when I am booten into android.
Only when I am in fastboot mode the phone is not discovered by windows - and in fastboot mode thre is no USB debbuging - but thx anyway
..
vstar said:
Thx gm'
It is not an issue for me to connect to Windows when I am booten into android.
Only when I am in fastboot mode the phone is not discovered by windows - and in fastboot mode thre is no USB debbuging - but thx anyway
Click to expand...
Click to collapse
Know what u mean.
Windows finds u phone but not in recovery mode.
Download pdanet for android and this will solve ur problem buddy.
http://junefabrics.com
I just realize that what I done a while ago.
You don't need install pdanet app on ur phone as long u have drivers u might get some errors if u press not install but will work anyway.
Hope this will help.
Sent from my Nexus S using Tapatalk
XXK1 sounds like the baseband/radio to me. Granted I never actually looked in the bootloader for a model number. You sure that's not the radio?
What rom is on the phone now? Does it work? Are you rooted? If you got working phone with root you can flash custom recovery from inside the os. Boot directly into it via terminal or adb or any app that does it.
The volume buttons not working sounds odd and does worry me though
did you try to boot into bootloader/fastboot without being connected to any machine (holding vol up + power) to check if your volume keys work or not?
your issue might not be driver related, but you can always try if the test above was ok.
http://forum.xda-developers.com/showthread.php?t=1138755
best of luck
OK guys. I am on 4.0.3 stock. Works almost fine. This phone is unlocked but not rooted. So no chance for any other recovery but the stock one as far as I know. So I am not able to downgrade easily. Yes I can boot into fast boot without being attached to USB. Volume keys still not working here. But working in recovery mode no problem. GM no drivers will help if phone does not show in windows device menadzer at all. I have tried Linux approach but it looks phone is not being discovered there in fast boot mode as well. I have tried unbrick software - does not discover the phone.
And yes it says on fast boot screen boot loader : I9020XXK1
I have run out of ideas.
Downgrade would be best but how to put any recovery manager without root privileges
Sent from my Nexus S using XDA App
you can use ROM manager to jump back to 2.3.x
..
I am not rooted so I cannot use from manager and I do have stock recovery not clockwork so I cannot install superuser.zip
Sent from my Nexus S using XDA App
And for SuperOneClick phone needs to be visible in fastboot mode.
Sent from my Nexus S using XDA App
vstar said:
And for SuperOneClick phone needs to be visible in fastboot mode.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
for SuperOneClick phone needs to be visible in usb debugging mode.
Sorry mate but it only starts in USB Debug/Android mode - then it reboots the phone to fastboot shell and then same issue - phone is not discovered by windows hence nothing else happens.
Is there no other way of gaining root access instead of fastboot option - this would solve all my pains
Thx everyone for input
..
i suggest just follow zedomax tutorial on how to root your ics phone. He also have the download links for all the files that you will need. once your phone is rooted then you can download the old stock version of your phone.
http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/
Looks like a driver issue, when phone isn't discovered by windows in fast boot mode. (You are booting with vol up+power, right?)
Forget about any one-click-stuff etc - unlocking and cwm is the way to go. Everything else just makes troubles.
What I don't get is how you unlocked your phone without fastboot working?! That's not possible... for the moment forget about rooting - superuser isn't needed to flash stuff via fastboot/cwm.
Concentrate on getting fastboot to work. After that it's a piece of cake. Check you have drivers and fastboot set up properly on your PC.
Edit:
By this I mean following the sticky-guides, using the sdk from Google (not any downloads pretending to make it quick'n'easy. Go the official way!)
You should also give the 4.0.4-stockrom (ported from ns4g-leak) a try - it's way better than 4.0.3!
Edit: talking about this one: http://forum.xda-developers.com/showthread.php?t=1474878
OK guys - I have no idea how should I say it in different way - this is not a matter of a driver - the phone is physically not visible to the computer. There is no unknown device of anykind so I have nothing to use a driver for. It is not that fastboot command does not recognize the phone - the phone does not exists in Windows Device Manager. Looks like when phone is in fastboot mode the usb port is dead. So no chance of rooting in standard way.
And I have unlocked it as it was working before. I did realize it is not working when I tried to downgrade recently.
Election Day: I have tried 3 different cables, couple of computers and 3 different operating systems - ubuntu included. How this trick with hairdrier works? If it is a flash why does it work for everything else but not fastboot mode? Should I heat it up without cover and battery? Any specific area? Should I plug in while hot?
Thx guys.
usb working with sys booted up, but broken on bootloader?! makes no sense at all, i hope you can see that for yourself. can't be a hw-failure (then it would be broken everywhere).
have you reinstalled the driver from the sdk? the problem is on your pc, not the phone...
and forget about rooting for the moment, you don't need that to flash a rom. or are you mixing things up?!
that nonsense about heating up the phone with a hair drier was a joke, right?
..
Hi,
I have an issue with a Nexus S i9023 of a friend
I installed the latest stock ICS CF_YAKJU_IMM76D some months ago and everything was fine.
I broke the glass of the screen and it was substitued: after a couple of months, the phone entered in a bootloop.
I tried to access recovery but was impossible, I could get to Fastboot and Download mode but choosing recovery from the first started bootlop again.
I flashed a latest CWM in fastboot via adb but no joy.
On top of that, handset behaviour is strange because only 1 on 20 times it is recognized by the PC as a Samsung device, in all other cases it is a "unknown device".
I remove all drivers from Windows and reinstalled the naked version, but again only sometimes I get it... I found out I need to have connected another handset (my HTC currently...) to have it recognized!
Now I can enter in download mode using the USB jig and I can see it from Odin, but if I use the
CF_YAKJU_IMM76D_full.tar
I get "verify image ipbl (fail)" on the handset.
If I use
CF_YAKJU_IMM76D_nowipe_nobootloaders_norecovery.tar
I get an "invalid volume size"
Do I have an hardware issue here? Some partition/internal memory with failure?
What else can I try to flash via Odin?
Obviously now after the fail I can't even get fastboot...
I also tried Unbrickable resurrector under Linux but it doesn't recognize the handset when I connect it.
Any suggestion? :crying:
SergioBigred said:
Any suggestion? :crying:
Click to expand...
Click to collapse
Ok, update. Using this thread I was able to flash via Odin 1.82 the 2.3.4
However I am still in a bootloop and I can't get fastboot but not recovery... and in fastboot I can't via USB the handset because it says "usb device not recognized"
I have a rooted Sm-g610f and I flashed twrp using the app, and I'm kinda stuck now. when I start up the device the logo screen appears and it just stays like that until the battery runs out, I cant access recovery, I cant flash a new rom because usb debugging is off and which means the device wont get detected on odin i can ONLY access download mode. I would really appreciate any kind of help
Celverboy said:
I have a rooted Sm-g610f and I flashed twrp using the app, and I'm kinda stuck now. when I start up the device the logo screen appears and it just stays like that until the battery runs out, I cant access recovery, I cant flash a new rom because usb debugging is off and which means the device wont get detected on odin i can ONLY access download mode. I would really appreciate any kind of help
Click to expand...
Click to collapse
Just because USB debugging is off doesn't mean Odin won't detect your phone. One of the biggest reasons Odin may not detect your phone is that you don't have Samsung's developer drivers, so make sure you look and install those.
ShaDisNX255 said:
Just because USB debugging is off doesn't mean Odin won't detect your phone. One of the biggest reasons Odin may not detect your phone is that you don't have Samsung's developer drivers, so make sure you look and install those.
Click to expand...
Click to collapse
I actually do have the drivers installed
Celverboy said:
I actually do have the drivers installed
Click to expand...
Click to collapse
Try a different port or cable too. Also, make sure you opened odin as admin and you opened it before plugging in the device. Worth a try...
Hi All
I have ROG 5s tencent edition. it was modified by seller to global. I have been using it for more than 1 year now. Last night something happened and it went off. I tried turn it on but it kept bootlooping at logo. It is not detetedable by computer because bootloader was locked by seller before selling. I had no idea about that at that time.
MY device is now in bootloop. I can open bootloader but it won't take me to recovery mode. Fastboot commands are also not working . Phone not found by computer in any state. Can any one provide me with some pointers on how an i flash firware,
Recoery is not opening. When I select it from bootloader it keeps bootlooping
Fastboot is not seen by computer. Tried many cables, both ports.
If anyone can guide me that be a huge favor as this is my daily driver
Your device should be dected in bootloader mode even if it has been locked. Connect via the side port with a good data cable and check drivers on Windows.
Once you have verified you have access to send Fatboot commands to the device in Bootloader mode, you can simply do a RAW flash to any working version and then upgrade normally to the firmware version you want. You don't need unlocked bootloader to flash this way.
Andrologic said:
Your device should be dected in bootloader mode even if it has been locked. Connect via the side port with a good data cable and check drivers on Windows.
Once you have verified you have access to send Fatboot commands to the device in Bootloader mode, you can simply do a RAW flash to any working version and then upgrade normally to the firmware version you want. You don't need unlocked bootloader to flash this way.
Click to expand...
Click to collapse
I have tried but it is not detected as anything. Not even unknown device. I have installed qualcomm drivers. What other drivers are there? Could u tell?
dksoni411 said:
I have tried but it is not detected as anything. Not even unknown device. I have installed qualcomm drivers. What other drivers are there? Could u tell?
Click to expand...
Click to collapse
If there isn't a hardware issue with the device, you should be able to.
Try to delete the driver and re-install it. Use the official Android USB driver from the SDK as opposed to Qualcomm drivers from random places on the net. Plug it in from the side port and try to turn it on while connected. Have Device Manager in Windows open and notice changes. Read out what it is recognized as. If absolutely nothing, then it's the cable, Windows or the device may really have a motherboard defect.
I believe it's more likely motherboard. Is there any fix for it?
Hi!
I'm using a custom rom (Cherish OS) and it's working pretty fine.
However, i want to turn back to the stock Oxygen OS, so I've tried to use the MSM Tool, but i have a problem.
Whenever i do "adb reboot edl", the phone actually boots in EDL, my PC in device Manager recognize the port (I've also installed the Driver), but when i press "Enum" nothing happen, the EDL MODE is not recognized only by the software. (No Device ID, and N/A on connection)
I've tried so many times but nothing seems to change, does anyone know how I should proceed?
SiiPArch said:
Hi!
I'm using a custom rom (Cherish OS) and it's working pretty fine.
However, i want to turn back to the stock Oxygen OS, so I've tried to use the MSM Tool, but i have a problem.
Whenever i do "adb reboot edl", the phone actually boots in EDL, my PC in device Manager recognize the port (I've also installed the Driver), but when i press "Enum" nothing happen, the EDL MODE is not recognized only by the software. (No Device ID, and N/A on connection)
I've tried so many times but nothing seems to change, does anyone know how I should proceed?
Click to expand...
Click to collapse
try to reinstall the correct driver for the firmware from the thread Unbrick tool for Nord