Hello everybody
i just installed cm 7.2 +gapps everything is good except that phone doesn t boot
I tried to go in the recovery but nothing happen
I can go on download mode and i tried to install syiah and philz touch so i can install a new rom
but nothing good ---- pc restart while odin flash
so i uninstalled kies reinstalled usb driver desactivated antivirus and when i wanted to start it stuck at settup connection then in 3 reconds pc restart tried on another pc -- same result i read that is nand rw corruption tried the guide but same --- pc restart
What can i do now? i dont have warrany for sgs2
only recovery works
C'mon. You spend a lot of time in Q&A and should know you should be searching for similar threads (I.E 'troubleshooting Odin won't work' - there are a bunch of things you haven't tried yet). And you should also know you try those steps until it works (because it invariably does eventually).
I doesn't matter i managet and installed siyah tar file somehow now i have a yellow triange (i can get rib of it) and used rom nuke then restored a backup
Related
lemme start by saying what i did that caused the problem
i installed PFittech 1.0.4 and everything was moving fine untill touchwiz began FCing alot. i dont use touchwiz anyway (as i had set Apex to default) so i thought i could remove it safely without any reprocussions. i used titanium backup to do a force uninstall but the phone rebooted into a black screen. I cannot get into recovery move at all so i tried to reflash the kernel in hopes that my recovery would be fixed.. I got into download mode just fine but neither odin or windows can connect to my phone
i really need help because nothing from the other posts related to this topic is working, i followed a few other posts and nothing is making odin pick up my device in download mode
Stuff to try when Odin doesn't work:-
*Must run Odin as administrator in Windoze.
*Ensure Kies & it's processes aren't running in Windoze task manager. Kill them if they are.
*Try different USB ports; you must be using a 'powered' or mainboard port.
*Try different USB cables (particularly the cable that came with the phone if you're not using it now)
*Try different versions of Odin (search on here/Google)
*Uninstall Kies, reboot, redownload & reinstall it, reboot, try the flash again. Also run Windoze Update.
And if all this fails, try a different PC. If it doesn't work first try on the other PC, go through the above steps on that PC as well.
MistahBungle said:
Stuff to try when Odin doesn't work:-
*Must run Odin as administrator in Windoze.
*Ensure Kies & it's processes aren't running in Windoze task manager. Kill them if they are.
*Try different USB ports; you must be using a 'powered' or mainboard port.
*Try different USB cables (particularly the cable that came with the phone if you're not using it now)
*Try different versions of Odin (search on here/Google)
*Uninstall Kies, reboot, redownload & reinstall it, reboot, try the flash again. Also run Windoze Update.
And if all this fails, try a different PC. If it doesn't work first try on the other PC, go through the above steps on that PC as well.
Click to expand...
Click to collapse
dont have another pc available so im stuck with this one, tried other USB cables, tried running odin as administrator, tried uninstalling n reinstalling kies, tried another version of odin (1.87)
nothing is working -_-
i should mention that when i attempt to boot normally, the PC is able to discover the drivers and connect to the device. even MTP connects and im able to view the contents of my phone's memory (for some reason, its all 0MB in size)
based on my readings, havent heard anyone having my specific symptoms for my phone.. im getting more and more depressed because i use my phone so much and now that its down and i cant fix it.. just feeling sad :crying:
and all this because i tried to uninstall touchwiz.. :crying:
ok this is what i will try doing
since my PC recognizes my phone only when it boots normally, i will try to flash a recovery image by dropping it on my SD card, then flashing it using droid explorer's "flash recovery image" option - REALLY hope this works
EDIT
nope - not working, even after flashing using droid explorer phone reboots into black screen, no recovery, no nothing..
i recently tried odin3 v 3.04 and odin still doesnt detect my phone in download mode.. drivers are still saying "unknown device" when i boot into download mode.. ive uninstalled and reinstalled and restarted both pc and phone so many times i just feel helpless right now.. like i should just give up and buy a new phone
Need this question answered
does odin pic up the ID:COM on a device whether it is in download mode or not? based on what i read here
http://forum.xda-developers.com/archive/index.php/t-1484607.htm
odin is capable of picking up on an ID:COM even if the device isnt in download mode - in my case, odin isnt picking it up at all nd as is, windows is still able to pick up my device if i boot it normally and load MTP and the correct drivers
24 hours now since problem occured and i have made no progress whatsoever.. feeling like giving up.. dont know what to do, and dont think anyone can help me anymore -_-
After 26 hrs of talking to myself and dedication - i finally solved my problem.. i decided to update my windows base and cleared the registry on all installations and all current associated drivers, reinstalled kies, updated new drivers and when connected my phone which was in download mode my phone connected as a "gadget serial" device.. with this - odin was able to pick up on my phone and i flashed a new kernel + recovery.. with that flashed back my rom and bam - back to status
Vylle said:
After 26 hrs of talking to myself and dedication - i finally solved my problem.. i decided to update my windows base and cleared the registry on all installations and all current associated drivers, reinstalled kies, updated new drivers and when connected my phone which was in download mode my phone connected as a "gadget serial" device.. with this - odin was able to pick up on my phone and i flashed a new kernel + recovery.. with that flashed back my rom and bam - back to status
Click to expand...
Click to collapse
Just an observation... isn't this more or less what MistahBungle said to do in his post in his last suggestion? (short of clearing the registry entries, which is a good idea as well.)
ctomgee said:
Just an observation... isn't this more or less what MistahBungle said to do in his post in his last suggestion? (short of clearing the registry entries, which is a good idea as well.)
Click to expand...
Click to collapse
honestly, i tried everything he suggested, but i suppose without the windows update + updating the USB drivers through kies (not download them by themself) - i possibly wouldnt have been successful. i read a tutorial that told me that kies could put my phone into download mode for an update - so what i did was clear registry, uninstall all current drivers and manually made kies reinstall them.. then after that, connected my phone while it was on (with the screen still blank) and selected the option to peform firmware update from kies (which put my phone into download mode) from there, when my phone got into download mode the new drivers loaded up and thats when odin was able to connect
in my situation, the constant plugging out and plugging in and hoping windows by itself could pick up the drivers never helped at all.. few people stated that i didnt need kies and that it interferes with it so what i did was only install the drivers and got rid of kies.. however in my case if not for kies i wouldnt have been able to connect to odin
Hello,
my device (i9300) as mentioned above got stuck in a boot loop.
First I did was I installed the latest pac-man ROM from here. After successful testing I decided to flash the latest OmniRom 4.4 from here.
Now here comes the dilemma with: My Failure was that I had a old Recovery (CWM-based Recovery v5.5.0.4) and I didn't see the point where it says that I have to update it first.
My USB Connection to my PC was already broken before I started to flash any of the ROMs. So I can't connect to the PC to flash via Odin. It fails on the driver installtion. (I copied everything in my cloud and downloaded it to the internal sd)
The Device Manager shows alwas a ! in a yellow triangle near the "Samsung Mobile USB CDC Composite Device" (Download Mode) with a errer code 10: Device cannot start. I did millions of solutions but nothing worked against this issue ...
Currently my device starts where the Samsung galaxy s3 logo pops up, get stuck by that with a red 1 on the upper left corner and boots into the "old" recovery.
This is my Problem. Please help me to fix this (and the USB bug).
Thank you very much
Kind regards,
A.R.Cante
A.R.Cante said:
Hello,
my device (i9300) as mentioned above got stuck in a boot loop.
First I did was I installed the latest pac-man ROM from here. After successful testing I decided to flash the latest OmniRom 4.4 from here.
Now here comes the dilemma with: My Failure was that I had a old Recovery (CWM-based Recovery v5.5.0.4) and I didn't see the point where it says that I have to update it first.
My USB Connection to my PC was already broken before I started to flash any of the ROMs. So I can't connect to the PC to flash via Odin. It fails on the driver installtion. (I copied everything in my cloud and downloaded it to the internal sd)
The Device Manager shows alwas a ! in a yellow triangle near the "Samsung Mobile USB CDC Composite Device" (Download Mode) with a errer code 10: Device cannot start. I did millions of solutions but nothing worked against this issue ...
Currently my device starts where the Samsung galaxy s3 logo pops up, get stuck by that with a red 1 on the upper left corner and boots into the "old" recovery.
This is my Problem. Please help me to fix this (and the USB bug).
Thank you very much
Kind regards,
A.R.Cante
Click to expand...
Click to collapse
To fix the USB bug, you must uninstall that driver and download the driver ( try to install kies for example )
To fix the bootloop try to do a full wipe in recovery mode
abidifethi said:
To fix the USB bug, you must uninstall that driver and download the driver ( try to install kies for example )
To fix the bootloop try to do a full wipe in recovery mode
Click to expand...
Click to collapse
None of your advices worked. I did unistall all drivers and also Kies. Reinstalled and it doesn't worked. So I uninstalled it again and installed only the drivers but this didn't worked too.
Everytime I uninstall the drivers and connect the device to the PC it is trying to Install the Drivers over Windows Update and Kies isn't reacting at all.
Now since I wiped data/factory reset, cache partition, dalvik cache and formated /system and /preload my device won't start automatically in the recovery anymore. It get stuck on the Samsung Galaxy SIII Logo with the red 1 in the upper left corner. To Access to the Recovery I have to take the battery out and and insert it again and press volume up + home + power.
What can I do now?
Thanks in advance
A.R.Cante said:
None of your advices worked. I did unistall all drivers and also Kies. Reinstalled and it doesn't worked. So I uninstalled it again and installed only the drivers but this didn't worked too.
Everytime I uninstall the drivers and connect the device to the PC it is trying to Install the Drivers over Windows Update and Kies isn't reacting at all.
Now since I wiped data/factory reset, cache partition, dalvik cache and formated /system and /preload my device won't start automatically in the recovery anymore. It get stuck on the Samsung Galaxy SIII Logo with the red 1 in the upper left corner. To Access to the Recovery I have to take the battery out and and insert it again and press volume up + home + power.
What can I do now?
Thanks in advance
Click to expand...
Click to collapse
Try to download any custom ROM if you don't done yet and put it in your external sd card ( use an other phone or card reader ) and now try to enter in recovery mode and install it and let us know the result
abidifethi said:
Try to download any custom ROM if you don't done yet and put it in your external sd card ( use an other phone or card reader ) and now try to enter in recovery mode and install it and let us know the result
Click to expand...
Click to collapse
I tried this now on my Desktop Computer and it worked fine. I didn't need to install drivers manually. It installed it by itself and therefore i was able to use odin!
I flashed the new recovery and put the omnirom and pa-gapps on my sd card (I also tried this on my notebook but my card reader is maybe broken)
so i installed teamwin recvovery over pc, put rom and gapps on my sd card and flashed them over recovery.
Now all works fine.
Thank you for your help.
But what I don't understand is my Win 7 OS (32 bit) is recently set up on my VM everything was fresh but it didnt recognized my device... Google says a lot of people are having this issues. I've tried everything whenever I found allegedly a solution for this problem. None of them worked. I simply switched the computer and everything is fine. This is ridiculous. One year ago, when I had running windows as main OS, there were no problems at all. If the problem was caused by a virtual machine I think that not many people would complain about this issue.
Kind regards
Why would old Win 7 recognize your device unless you install drivers .
JJEgan said:
Why would old Win 7 recognize your device unless you install drivers .
Click to expand...
Click to collapse
I don't really understand your comment. The Problem of this USB error has no root. When your Windows System says error code 10: device cannot start then you have a big problem because you don't know why and how to fix this. Try and Google this. You will find thousands of people complaining the same error. Everyone has other solutions for that. Some edit their registry, others simply do a soft-reset and try another USB-Port.
Samsung support can't help you at all because they don't know why this is happening. And the solving of this problem is really random. i tried for hours to solve this with no success (except switching to another computer).
Windows says on my laptop the device cannot start but it is perfectly connecting to my other computer. How can this happen? I don't know. Maybe the error code 10 is not that specific and there is something other wrong than my device.
Hi, XDA! I need your help.
So I'm on this unofficial version of CM 12, link : http://forum.xda-developers.com/galaxy-s3/development/wip-cyanogenmod-12-t2936990
I was on Weekly 8/7/6 of it( I don't remember exactly) (refer to changelog, the top entry date 1/4/15 is weekly 10) and wanted to upgrade to weekly 3(refer to changelog), of cm 12.1 made by the same guy who made the rom i was using, link: http://forum.xda-developers.com/galaxy-s3/development/5-1-x-cyanogenmod-12-1-t3066864. I dirty flashed(if that's what flashing a new rom on top of an old one without factory resetting means) because it was just CM 12.1 ported to S3, and i thought that CM says on it's website that you don't need to factory reset to flash a rom which has a new android version.
When I opened recovery mode, I found out that I had this new recovery, called Cyanogen Recovery. I was like 'Whatevs'. I flashed the new ROM, but about halfway in, it stopped and on the top of the failure report, it said: "cannot load volume /misc" it also said further down "signature verification failed". Now let me tell you that this recovery is pretty limited,no mounting features, no system wiping, no dalvik cache wiping, no signature verification toggle, etc. and on top of that, factory resetting, wiping media or cache didn't show a log of it as it happened, so you didn't know whether it had actually happened. My phone was bricked and it would stay keep going on the starting screen( the head of The CM mascot, the blue android bot, with ripples spreading from it)
I was like 'okay, i can do this'. I connected my phone to my pc, installed samsung usb drivers from the net, installed Odin, downloaded philz touch recovery ( a tar md5 version) (to flash it using ODIN and then flash one of the different cm 12/ cm 11 roms located in my external sd card,using the new recovery) , put the phone in download mode, but Odin wouldnt recognize it. It was admin mode, just so you know. No ID:COM would show up. I tried everything, putting in download mode before connecting it to the PC, reinstalling the drivers, trying different versions of the drivers, trying different versions of Odin, allowing Odin all access and security permissions for all users to my PC, compatibility mode for windows 7(im on win 8), factory resetting, wiping media and cache, using different wires and ports, even the ones on the back of the system unit(system box or CPU), doing all this stuff on my mum's laptop(it's a windows 7 laptop), like doing almost everything. My phone starts charging, so it isn't a problem with the phone. I looked up the issue on Google, and found other people had the volume /misc and signature issue too. My phone starts charging when I connect it, so it isn't an issue with the phone's micro USB port, but if it is, please tell me. I read somewhere that USB debugging might have something to do with it, but I can't change that setting cos' my phone's bricked.
XDA, HELP ME PLEASE!
If you can still go to your cm recovery, you can install philz from there.
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/i9300/philz_touch_6.48.4-i9300.zip
Download the zip file, flash it through cm recovery , turn off your phone and boot it to new recovery.
https://www.dropbox.com/s/qzgn1abhr4qcmls/Ultimate_Kernel_Cleaning_Script_v1.0_en_SGS3.zip?dl=0
https://www.dropbox.com/s/f1zbm0tvsvh5ww5/MegaWipe_-_GS3.zip?dl=0
Also use these two to wipe clean your entire phone even kernel or system leftovers. If odin still doesnt see your phone, try to install a custom rom
So....about aweek ago my phone seemed laggy (i was on neatrom 6.4) so when i plugg the phone to the pc , pc can able to show the phone (GT-i9000) but when i open the phone (GT-i9000) in the pc no files are shown . so i entered the recovery and i wiped the data&cache&dalvik and i flashed cm12.1 so i stucked in bootloop and cm recovery i can't flash anything from recovery on sdcard or external i tried to format the phone many times but nothing i tried to flash stock rom in odin .. my phone is shown in odin but when i flash (stock rom ,kernel) nothing happen in the download mode or odin no flashing progress are shown . i searched alot and i didn't find any solution and i don't even know what is the real problem my phone is bricked or i need to change something in the hardware:crying: i need any solution for my problem please and sorry for my bad english:silly:
okay i found a solution i changed the usb cable and the usb port and it worked :3
Hey
i flashed a custom rom on my samsung ace gt s5830i, it also worked until i tried to reboot. then i get stuck in a boot loop.
recovery and download mode still working but nothing else.
wanted to unbrick with odin, but odin doesnt recognize the device. when i plug it in windows just says there is an unknown device.
drivers are all up-to-date. tried odin 1.85 and odin 3.
also flashing other roms doesnt work. during date/cache wipe i often get errors like can't mount /system or /cache or /cache/recovery.
please help
first forum use
hope i didnt't missed something. if i am somehow wrong, i am sorry. its my first forum use.
teneedshelp said:
Hey
i flashed a custom rom on my samsung ace gt s5830i, it also worked until i tried to reboot. then i get stuck in a boot loop.
recovery and download mode still working but nothing else.
wanted to unbrick with odin, but odin doesnt recognize the device. when i plug it in windows just says there is an unknown device.
drivers are all up-to-date. tried odin 1.85 and odin 3.
also flashing other roms doesnt work. during date/cache wipe i often get errors like can't mount /system or /cache or /cache/recovery.
please help
Click to expand...
Click to collapse
Ok, its in your usb connector, its kinda broken, i saw a fix for galaxy S1 woth this problem
You take a toothpick and look inside you micro usb connector and you will se a "tongue", gently push that "tongue" up with a toothpick or anything non-metalic and see if it works
Cheers!!!