Related
Hi there,
I noticed I can't get in download mode anymore. Whatever I try it won't show the yellow triangular download sign. It just boots into cyanogen.
I have tried the 3 button trick but recovery nor download works. That's when I had the idea to apply the 3-button fix. adb reboot recovery brings me in the cwm recovery mode. adb reboot download just reboots the phone. I even tried the 300k ohm jig which always seemed to work as a failsafe. That also just boots the phone into cm.
I have checked with my brother who also runs CM nightly 101 and for him the download mode works fine so it is my phone, not CM.
The phone works fine now, is rooted too so I wondered if there's any way to fix this by rewriting the bootloaders. I want to have this fixed as a failsafe is flashing ever fails or if one of the nightlies gets corrupted.
Is there anyone who can confirm the download mode is in the primary bootloader (boot.bin from a stock rom) and is it safe to just flash_image that to the boot partition or will that be a guarantee to brick. The idea is that I still have root console access so I have to fix it from there.
Any help is appreciated.
Christiaan
Galaxy S
CyanogenMod 7 Nightly #101
Their is a chance that whenever u tried to go into download mode your phone was connected into charging and phone doesn't go into download mode when charging , please reply and tell Me that did I helped!
Sent from my GT-I9000 using XDA Premium App
BHuvan goyal said:
Their is a chance that whenever u tried to go into download mode your phone was connected into charging and phone doesn't go into download mode when charging , please reply and tell Me that did I helped!
Click to expand...
Click to collapse
Thanks for the quick reply.
Tried the tricks with and without pc-usb/charger and it made no difference. The 300k ohm jig trick can't be done with power or computer connected since you have to use the usb connection on the phone for it. It usually was my ever working failsafe.
I also tried the quickboot app without any luck. It seems it is responding to the download command but the code isn't there anymore.
Hey try going into download mode by touch controls although I haven't ever used cyanogen but i assume as every custom rom has this feature cyanogen must also have this! The download mode option in quick network options when u press the power button for 2 seconds ! Although it isn't safe but you cab try this and then if it goes into download mode then their must a way to go into download mode manually!
Sent from my GT-I9000 using XDA Premium App
BHuvan goyal said:
Hey try going into download mode by touch controls although I haven't ever used cyanogen but i assume as every custom rom has this feature cyanogen must also have this! The download mode option in quick network options when u press the power button for 2 seconds ! Although it isn't safe but you cab try this and then if it goes into download mode then their must a way to go into download mode manually!
Click to expand...
Click to collapse
Holding the power button for two seconds indeed brings up the profile/reboot/shutdown options. Selecting reboot only gives two additional options, reboot and recovery which do as they say. I can boot cwm recovery but from there I can't go into download mode either.
Try downloading terminal emulator and then reboot download or ADB reboot download
Nitro_123 said:
Try downloading terminal emulator and then reboot download or ADB reboot download
Click to expand...
Click to collapse
Tried it from the terminal with reboot download. Also tried adb reboot download long before that. It just reboots and starts. I have the feeling the piece of bootblock that's holding the download mode isn't there anymore.
There is an option in recovery to boot into download mode, Have you tried that ?
It sounds to me like that part of the bootloader is corrupt / missing.
Does the phone still work normally ? can you still continue to use it daily without the download mode option ?
azzledazzle said:
There is an option in recovery to boot into download mode, Have you tried that ?
It sounds to me like that part of the bootloader is corrupt / missing.
Does the phone still work normally ? can you still continue to use it daily without the download mode option ?
Click to expand...
Click to collapse
The phone works fine otherwise. I just want to fix this before it stops working fine and I need the download mode.
Recovery boots into CWM-based Recovery v4.0.1.5 which I got with CM7 with no option to return to the stock recovery or download mode as far as I can see. Also zipped updates from sd-card install fine from CWM recovery mode. If I just knew where to find a cwm ready zipped bootloader that will fix this.
cvdveer said:
The phone works fine otherwise. I just want to fix this before it stops working fine and I need the download mode.
Recovery boots into CWM-based Recovery v4.0.1.5 which I got with CM7 with no option to return to the stock recovery or download mode as far as I can see. Also zipped updates from sd-card install fine from CWM recovery mode. If I just knew where to find a cwm ready zipped bootloader that will fix this.
Click to expand...
Click to collapse
Thats a good idea, I think that should be made, Would save a lot of hassle...
In my recovery under 'advanced features' the option is there to reboot into android or reboot into download..
In order to go from CM7 - Stock, do you need re-partition with all 3 files ? or can you flash it through recovery ?
If so, flash it to stock and sell it to someone who has no idea about Custom ROMs / Hacking. (like me 12 months ago )
EDIT: is this issue not kernel related by any chance ?
azzledazzle said:
Thats a good idea, I think that should be made, Would save a lot of hassle...
In my recovery under 'advanced features' the option is there to reboot into android or reboot into download..
In order to go from CM7 - Stock, do you need re-partition with all 3 files ? or can you flash it through recovery ?
If so, flash it to stock and sell it to someone who has no idea about Custom ROMs / Hacking. (like me 12 months ago )
EDIT: is this issue not kernel related by any chance ?
Click to expand...
Click to collapse
Well I have no clue to make any package and I don't dare to flash_image some random boot.bin.
My recovery -> advanced only has reboot recovery which brings it back into recovery.
I'm afraid bringing it back to stock also needs odin/heimdall, that brings me back to the initial problem.
Selling it gives me the money for half a new phone. As long as its working fine I'd like to stick with it. My worst case scenario so far is that I'm stuck with CM7 nightly #101 for the coming 1.5 year which is annoying but far better than the slow stock samsung hands out.
The issue can't be directly kernel or CM7 related. My brother has CM7 #101 running and download mode works fine with him. (And no I can't secretly swap phones ) He doesn't know how to work with odin so I arranged everything for him. Exactly the same steps as I did my own phone. Perhaps a glitch in flashing or something.
cvdveer said:
Well I have no clue to make any package and I don't dare to flash_image some random boot.bin.
My recovery -> advanced only has reboot recovery which brings it back into recovery.
I'm afraid bringing it back to stock also needs odin/heimdall, that brings me back to the initial problem.
Selling it gives me the money for half a new phone. As long as its working fine I'd like to stick with it. My worst case scenario so far is that I'm stuck with CM7 nightly #101 for the coming 1.5 year which is annoying but far better than the slow stock samsung hands out.
The issue can't be directly kernel or CM7 related. My brother has CM7 #101 running and download mode works fine with him. (And no I can't secretly swap phones ) He doesn't know how to work with odin so I arranged everything for him. Exactly the same steps as I did my own phone. Perhaps a glitch in flashing or something.
Click to expand...
Click to collapse
Hmmm... tricky one to fix..
I have no more ideas i think flashing bootloaders through recovery would work like you said, But unless its a tried and tested method i wouldnt recommend it at all.
Have you posted this issue in the CM thread ? perhaps you could PM one of the Devs for assistance, or whether the whole 'flashing bootloader in recovery' idea would work at all.
You have nothing to lose by asking them.
Hope you get a solution... But until them im out of ideas.
Keep us updated if you get a fix.
Good luck man !!
EDIT: one more idea, Sounds risky but.... What if you made a nandroid backup on your brothers phone and restore it on yours ?? Thats if nandroid does back up bootloaders im not sure
azzledazzle said:
Hmmm... tricky one to fix..
I have no more ideas i think flashing bootloaders through recovery would work like you said, But unless its a tried and tested method i wouldnt recommend it at all.
Have you posted this issue in the CM thread ? perhaps you could PM one of the Devs for assistance, or whether the whole 'flashing bootloader in recovery' idea would work at all.
You have nothing to lose by asking them.
Hope you get a solution... But until them im out of ideas.
Keep us updated if you get a fix.
Good luck man !!
EDIT: one more idea, Sounds risky but.... What if you made a nandroid backup on your brothers phone and restore it on yours ?? Thats if nandroid does back up bootloaders im not sure
Click to expand...
Click to collapse
Thanks for thinking with me. I'll give the nandroid solution a go if there are no other replies within a reasonable time.
I'll post the same question in the CM forum but contacting the CM devs could be hard. They don't give any official support to nightlies and I can't say I'm convinced it has anything to do with CM at all. Though they do have the knowledge to answer the question or build a package to repair it. But you're right there's nothing to lose in asking.
Ofcourse I searched the forum before posting and found out I seem to be the only one ever with this problem. The solution could be as rare so I'll keep you posted if I make any progress beside here. That's what the whole idea behind this forum is for right?
True man !!
And if you get a solution or a dev to make a flashable bootloader. It could help other people in future
Good luck. Keep us posted
http://forum.xda-developers.com/showthread.php?t=1236273
Nitro_123 said:
http://forum.xda-developers.com/showthread.php?t=1236273
Click to expand...
Click to collapse
Interesting but that project still needs a bricked i9000 to tear apart. I don't have a captivate. Well if it ever becomes really bricked I'll consider donating mine.
And I'm okay with handling computers (yes I consider the phone a small computer about 400 times faster than my first pc) but when actual soldering is involved I give up.
fixable?
i have a samsung here the S GT I 9000 and i tryed to use odin on it and now this pops up every time i try to up load an os
--installing package...
finding package...
opening package...
verifying update package...
installing update...
successfully install update...
--copy media files...
successfully copied media files..
formatting /data...
E:format_volume: rfs format failed on / dev/block/mmcblk0p2
formatting /dbdata...
formatting /cache..
deleting meta data
data wipe fail.
-- appling multi-csc...
installing multi-csc..
cant access to '/system/csc/bmc/system/' . sucessfully applied multi-CSC
Help!
Hi! If it still doesn't work, try downloading ROM Manager from the market and install the latest CWM. It sounds like your bootloader got modified/locked.
Erahgon said:
Hi! If it still doesn't work, try downloading ROM Manager from the market and install the latest CWM. It sounds like your bootloader got modified/locked.
Click to expand...
Click to collapse
Errr talking to me or adonai? Sounds like two seperate problems for two seperate topics.
cvdveer said:
Interesting but that project still needs a bricked i9000 to tear apart. I don't have a captivate. Well if it ever becomes really bricked I'll consider donating mine.
And I'm okay with handling computers (yes I consider the phone a small computer about 400 times faster than my first pc) but when actual soldering is involved I give up.
Click to expand...
Click to collapse
I REALLY liked your answer
BTW , same here
Hello there,
i've rooted my GC with newest 4.1.2 Android and all went fine. Then i wanted to use the cool init.d Script, which makes it possible to set the extSdCard storeage as 'internal' and the internal as external Storeage, to get more space for a lot of Apps.
But for this init.d script i needed to use a compatible kernel. So thinking, the GalaxyCamera HW is almost the same like from the Galaxy S II Phone. i decied to use this tut: http://forum.xda-developers.com/showthread.php?t=1772234 to download the init.d script and siyah- kernel. getting this things into the Camera i should use ClockWorkMod.
And there the Problem starts: In ClockworkMod install-tool i sayed "yes" to install it for a Galaxy S III.. humm, device restarting into recovery and Screen flashes with disorientated GalaxyCamera Logo und went blank afterall... i rebootet and all went fine, but recovery was "corrupted" (with my luck i didnt make a backup in ClockWorkMod ROM Utility on Android... ( )
So i decided to start over and started to flashing (idont now why) the root- Restore file from Chainfire for the GalaxyCamera again. Recover Mode works fine again, but NOW on normal boot my Touchscreen doenst react anymore.
After trying with several Stock recoveries, even with 4.1.1 and so on an re- Routing.... issue still persists.. ( Can anyone help me, or did i just killed the Touchscreen Controller with this Action??
Do you try a hard reset, you probably can do it from recovery mode, but not sure.
Maybe he solve your issue ?
I've already tried. But thank you for your tip!
The Problem is (i guess) that ClockWorkMod or Chainfires Root, locked up some file- permissions and the Touchscreen- driver cant load into Memory. If it where possible for me to repartition the device, all locked Data gets wiped and a fresh Andoid flashed back to NAND . I tried this with Adam's Pit- File in Odin or Heimdall several Times with differen OS'es. No success.
Yesterday i Sent the camera in for repair to a Samsung Service Provider. I Hope they will fix it. Small problem: i couldnt reset the Flashcounter with an 'defective' Touchscreen! ... I hope they would not recognize my 20 custom OS restores!
I will inform you if my lovely GalaxyCamera gets fixed!
WEissbr0t said:
I've already tried. But thank you for your tip!
The Problem is (i guess) that ClockWorkMod or Chainfires Root, locked up some file- permissions and the Touchscreen- driver cant load into Memory. If it where possible for me to repartition the device, all locked Data gets wiped and a fresh Andoid flashed back to NAND . I tried this with Adam's Pit- File in Odin or Heimdall several Times with differen OS'es. No success.
Yesterday i Sent the camera in for repair to a Samsung Service Provider. I Hope they will fix it. Small problem: i couldnt reset the Flashcounter with an 'defective' Touchscreen! ... I hope they would not recognize my 20 custom OS restores!
I will inform you if my lovely GalaxyCamera gets fixed!
Click to expand...
Click to collapse
Dude, did you get your camera back?? I made he same mistake just a couple of hours ago.. I am feeling so depressed, I dont know what to do.
Did they say anything about the flash counter?
me too
I have had this problem as well. My camera has no touch on the screen after rebooting. I saw it flick and lock and then I tried to re-flash the rom etc, but it didn't help.
Sent to Samsung and they are saying that the motherboard and screen have to be replaced at a cost of $350. They are seeing if they can repair under warranty, but it doesn't sound too hopeful.... Perhaps, I will give up on my Galaxy Camera. I am not going to pay $350 to have the item repaired. I didn't know if it was a software fault or a hardware failure. I think it really should be a warranty issue....
Anyhow, I guess clockwork mod can really wreck things up..... Anyone, found a way to fix this issue? Why didn't the default Samsung ROM flash and factory reset fix the issue if it is supposedly software?
WEissbr0t said:
Hello there,
i've rooted my GC with newest 4.1.2 Android and all went fine. Then i wanted to use the cool init.d Script, which makes it possible to set the extSdCard storeage as 'internal' and the internal as external Storeage, to get more space for a lot of Apps.
But for this init.d script i needed to use a compatible kernel. So thinking, the GalaxyCamera HW is almost the same like from the Galaxy S II Phone. i decied to use this tut: http://forum.xda-developers.com/showthread.php?t=1772234 to download the init.d script and siyah- kernel. getting this things into the Camera i should use ClockWorkMod.
And there the Problem starts: In ClockworkMod install-tool i sayed "yes" to install it for a Galaxy S III.. humm, device restarting into recovery and Screen flashes with disorientated GalaxyCamera Logo und went blank afterall... i rebootet and all went fine, but recovery was "corrupted" (with my luck i didnt make a backup in ClockWorkMod ROM Utility on Android... ( )
So i decided to start over and started to flashing (idont now why) the root- Restore file from Chainfire for the GalaxyCamera again. Recover Mode works fine again, but NOW on normal boot my Touchscreen doenst react anymore.
After trying with several Stock recoveries, even with 4.1.1 and so on an re- Routing.... issue still persists.. ( Can anyone help me, or did i just killed the Touchscreen Controller with this Action??
Click to expand...
Click to collapse
I had the same problem dude, got the touchscreen replaced at the service center.
New touchscreen works totally fine.
Hi;
I'm using samsung galaxy camera. I wanted to root with odin. But I selected bootloader instead of PDA wrongly, Then I selected start. My Camera rebooted and not opened. Just showing "samsung galaxy camera" logo.
If somebody help me, I will happy.
Flash stock rom
7dervish said:
Hi;
I'm using samsung galaxy camera. I wanted to root with odin. But I selected bootloader instead of PDA wrongly, Then I selected start. My Camera rebooted and not opened. Just showing "samsung galaxy camera" logo.
If somebody help me, I will happy.
Click to expand...
Click to collapse
You should be able to flash the stock samsung standard rom. It will update everything including the bootloader. Haven't had this problem, but this solution seems logical. Download the full rom and flash with PDA option.
Good luck.
ant75 said:
You should be able to flash the stock samsung standard rom. It will update everything including the bootloader. Haven't had this problem, but this solution seems logical. Download the full rom and flash with PDA option.
Good luck.
Click to expand...
Click to collapse
Thank you,
I flashed stock rom. SGC opening but touchscreen did not work. Just otg cable with mouse.
I will send to samsung service on monday
7dervish said:
Thank you,
I flashed stock rom. SGC opening but touchscreen did not work. Just otg cable with mouse.
I will send to samsung service on monday
Click to expand...
Click to collapse
There is no solution for touchscreen problem. You just give service your camera and they change touchsreen. Cause it's a hardware problem
Jeah it definitively was an HW Problem. Got a New Touchscreen and all works fine
Gesendet von meinem GT-I9100 mit Tapatalk 2
A pity, read the solution, because I'm at the same point
Hi guys,
recently i had a problem with my phone whenever i change my battery the date show as 1 jan 2000 and i had to rectify it manually..I thought cause i was on a custom rom ..so i flashed philz safe kernel (latest 2.99) and JB GT-N7000XXLSC_N7000OXALSC_N7000XXLSC rom...
everything was ok until...i replaced my battery again as i use two batteries on the go and then my fone was stuck again on the first boot samsung image...when i tried the up+home+power keys it went to the original safe recovery android rather than philz ... it looks like everytime i replace battery this is going to happen again...any one had same issue ...i was reading the posts on this forum and someone had similiar issue with battery and was suggested it is a fault on the fone itself....
any suggestions are welcomed ..and thx in advance
How did you flash the xxlsc rom?
nokiamodeln91 said:
How did you flash the xxlsc rom?
Click to expand...
Click to collapse
Hi thx for reply...i used oden ...pressed the down+power +home then it went to download mode then oden pc connected thru cable...
When you installed the new rom, philz recovery was replaced by the stock recovery. And JB leak has issues of getting bootloops if not shut down properly. So when you power off the phone wait till the last haptic feedback and then change the battery. Still not 100 % but will save some bootloops
yeah although after i installed jb i reflashed again philz...but i will keep an eye on this ..as i suspect could be hardware issue ...usually it should not lose the time and date once you replace battery ...
its normal on that rom I think
Ok, so a few months ago I had messed up my O2x while trying to NVflash a recovery, as I had described in this thread->
http://forum.xda-developers.com/showthread.php?t=1952614
The LG service centre told me it's a hardware problem and it'd cost me around 60% of the phone's price to get it fixed. I didn't get it done and put the phone away.
Now after all these months I took it out yesterday and Googled to see if I could fix it. I found this "full brick repair" tool that was really easy to use and now the phone has cm10 and cwm installed and is booting fine.
But the problem is that the touchscreen is not at all working. The display is working fine, but touches aren't getting registered. This may very well be a hardware issue. But the phone not booting up earlier was also said to be a hardware issue, which turned out to be a software problem. So, I just wanted to make sure that the touchscreen not working isn't a software problem before I hand it over to LG service executives.
I've flashed the 725 v10 baseband to see if that solves it, but it didn't. Also flashed v20l to no avail. Flashed another rom after wiping cm10 (Dovahkiin 1.2), no improvements. Any other suggestions?
Did you try flashing cwm 6 (touch)?
My first thaught was a incompatible (wrong) Kernel (I had this on my tablet).
MrKra said:
Did you try flashing cwm 6 (touch)?
My first thaught was a incompatible (wrong) Kernel (I had this on my tablet).
Click to expand...
Click to collapse
The brick repair tool installed CWM 6.0.1.5. Does that support touch? Idk cause the touchscreen isn't working in recovery either. I can navigate and select with the vol and power buttons, which work fine.
If I install a touch recovery and the touchscreen still doesn't function, I'll lose my ability to use the recovery too, so i'm a wee bit apprehensive. (or can CWM touch also be used with the volumed and power keys?)
sean8000 said:
The brick repair tool installed CWM 6.0.1.5. Does that support touch? Idk cause the touchscreen isn't working in recovery either. I can navigate and select with the vol and power buttons, which work fine.
If I install a touch recovery and the touchscreen still doesn't function, I'll lose my ability to use the recovery too, so i'm a wee bit apprehensive. (or can CWM touch also be used with the volumed and power keys?)
Click to expand...
Click to collapse
Recovery always can be controlled by volume keys.
If I were you I would Install the latest CWM via AO Tools. Than I would try to install something with aroma installer, like optithrust rom or so
MrKra said:
Recovery always can be controlled by volume keys.
If I were you I would Install the latest CWM via AO Tools. Than I would try to install something with aroma installer, like optithrust rom or so
Click to expand...
Click to collapse
Ok, I'll install the latest CWM touch. Are you sure I should install optithrust? I was using cm10, so I think i'm on old bootloader. Optithrust seems to be for the new bootloader.
Downloaded CWM 6.0.1.5 touch from this thread ->
http://forum.xda-developers.com/showthread.php?p=34286893
It flashed fine, but touch still isn't working, not even in the recovery menu.
Should I flash a different rom or something?
You dont need to flash the rom, this is only a test if the touch is working in aroma installer.
if no => this is a + for hardware problem
if yes => Ill think about new ideas
Ok then, can you tell me in a little more detail what this aroma installer is and what I have to do with it? I tried to find out myself, but i'm not sure i fully understand it and I rather not take any chances.
The Aroma Installer provides an installation via Touchscreen.
e.g. you touch "Cancel" or "Next" instead of pressing the power button during installation.
This implementation of touch is very low level and "kernel independent".
Optithrust, Django Manouche and the CIV ROM and the Dual Boot Tool areshipped with the Aroma Installler
I am not sure, but I think CWM >=6 is needed for this
Hi guys,
Did you find any solution to the screen not working. Mine stopped working yesterday.
If its a software problem, how do i verify ?
If its a hardware problem, what needs to be changed ?
Thanks for any replies ...
I don't have a solution.. but I have the same problem. No touchscreen when I install any ics roms (including lg stock). Touchscreen works fine with gingerbread e.g. CM7 so it's software not hardware... any ideas?
Sent from my LG-P990 using xda app-developers app
i'll make it short
One night,i've used my phone,and before going to sleep(phone still working),i left it to charge.(That's at about 11pm).The morning i wake up,phone cannot boot in recovery nor in download.It was like dead.But i have left it to charge for some hours then charging animation came back,then phone could boot again,including download mode but not recovery(linegeos 14.1).Until today,i have tried to flash custom recovery,stock recovery,wipe file to wipe data and cache,tried to install cm12.1,but none of them worked,still stuck on bootloop.If i recall,the night i used my phone last,i tried to use lucky patcher to get unlimited coins on dream league,but with play protect,they warned me that google would give warning,but i did not do anything.After all the flashes including recovery and the rom that failed,i ticked the nand erase in odin but seems like nothing changed.And now i'm out of options,if someone could really help me please,this is the only phone i've got.Phone can boot fine,but not in recovery and it will not install idk why,please help me...
something i've seen in download is that after flashing recovery or wiping data,in the place of current binary,it writes something like sdcard write status:2(7) or something like that.
does any of you know the problem?
no answer?
pls help me
i have the same problem is so sad
so there's no fix?
I have the exact same problem in my i8190, despite of being totally stock. I'm trying to flash stock rom, stock recovery, custom recovery, custom rom, something... and nothing happens, Odin says PASS but it seems to be like there is no memory to write on. I'm thinking it could be some hardware issue :'(
then there's nothing to do...
so sad
If its software you could use this: https://androidfilehost.com/?fid=24269982087010584
Flash it through odin
IkerST said:
If its software you could use this: https://androidfilehost.com/?fid=24269982087010584
Flash it through odin
Click to expand...
Click to collapse
this for i8190L not I8190
do you have any files for I8190?
Ioty1705 said:
this for i8190L not I8190
do you have any files for I8190?
Click to expand...
Click to collapse
My bad, search in this folder for your device http://androidfilehost.com/?w=files&flid=38726
tried to install any software but does not work.I think it's a hardware issue,i'm not sure though!!
does any of you know what the problem means?
Hi everyone, I am having a similar problem. Last month I have tried to install novafusion RR distribution to s3 minI because it was rebooting all the time, but since I didn't liked it I went back to the original firmware. A few days ago my cell died, it wasn't turning on. The guy in the repair shop told me it wasn't the battery... the nextday it was turning on, buy keep rebooting. I bought a new original battery, charged it but still the same problem.
I tried to install twrp and central recovery via Odin but nothing works, it freezes on the "Samsung Galaxy s3 mini" or it reboot..
I would like to know if there is something that I can do, because I want to backup some contacts that were saved in the phone memory, sms and the last whatsapp chat, for some reason the last automatic one is from january...
Any ideas?