Alright, after spending hours upon hours researching multiple forums I can firmly say I'm stumped. As an FYI, I change ROM's frequently and have preformed these actions multiple times. So this isnt about me being a noob and doing something incorrect due to lack of knowledge (at least i hope not).
After multiple methods I can not find a single way to get into download mode.
Methods attempted:
1. cards and Battery out
waited up to 30 min with battery out,
battery in
hold volume buttons (tried to do this before the battery goes in as well)
usb plugged in (odin on in background of course)
I have gotten into download mode multiple times using this method, however, doing it now (and multiple variations, including holding only volume up or volume down, tapping power once and a bunch of random things people from various forums 'claim' to work) will result in only one thing; having the battery charging screen pop up and freeze on me. I know it is frozen as the progress timer is stuck at the 12:00 position and doesnt change, even if left there for an hour or two.
If the phone is allowed to power up normally (or i press the power button when trying to go into download mode) the phone will go to the standard ATT screen flash once then show up again and finally go into recovery mode. My research hasnt shown that i can do anything from recovery mode without having access to the internal SD.
upon further research, I came across only one other thread of e=people who had a similar problem, however the OP said he performed the download mode method mentioned above over and over and then it eventually worked. Which doesnt make a whole lot of sense to me, but nonetheless he said he got it within 40 times, I must have done this over 100 times now with the same frozen battery screen result.
I even tried ADB, which is something that was new to me. But after getting ADB to successfully work on the command line, it does not recognize that the phone is connected (my assumption is because in recovery mode, which is the only place i can be with the phone on besides the frozen screen, the internal SD isnt mounted for mass storage). So ADB didnt work either.
I am within my 30 day period, but of course, I would prefer to just fix this thing as opposed to going down to have 'the talk' about bricking my phone with ATT. Has anyone seen this issue? Anyone else have any ideas? Anything I can do from the recovery screen?
Thanks for your help
Adb should work in recovery mode.
Let me know 2 things: your batch #
What ROM you were using when it went out
Sent from my SAMSUNG-SGH-I897 using XDA App
PS don't tell att you modded your phone
Sent from my SAMSUNG-SGH-I897 using XDA App
Yea I had the same problem when i bricked my brothers captivate. I did all the 3 button method and i couldnt still go to download mode but i figured another way on how to get there =) thanks to me. But this method only works if your computer recognize your phone like if your stuck on atnt screen or galaxy s screen or even more if its all dark screen, but most importantly is that your computer recognize your phone and you have clockwork recovery. Here is the link of my post.
http://forum.xda-developers.com/showthread.php?t=842484
@fattire
1. Where do i locate the Batch #
2. It had just finished flashing into Cog 2.3b4. I had flashed to stock (like I normally do) before flashing to Cog. Looking at the screen, everything looked like it went fine and Cog was installed properly. After it finished it started restarting the phone, and this is where I am now.
P.S. Yeah, that goes without saying just so much of a hassle with the ATT people....
P.P.S. I didnt know if this was normal or not, but in recovery mode the computer can see the phone's drive but it (the phones drive) is not mounted so I can not access any of the files on it. From all that I have read ADB is working correctly and have confirmed it in the command line. I have the correct drivers ( and i know they are the right ones bc Ive done this before on the same computer with the same USB port). Odin also recognizes the phone and says it is connected but upon trying to flash to stock or anything else it just hangs, again my assumption is bc the internal SD is not mounted correctly...
@G1
Thank you for your suggestion, unfortunately it appears the phone is not being mounted correctly on my comp to recognize it properly. So your method will not work.
But keep the ideas coming!! Anyone else?
There's a solderless procedure to go in download mode.
http://forum.xda-developers.com/showthread.php?t=841512
@Silver
I attempted the procedure and it only resulted in the phone booting up to the att screen then going into recovery mode.
After this procedure, performing method 1 to get into download mode does not result in a stalled battery screen, it now goes into recovery mode. Maybe I fried something....
Oh well off to att tomorrow.....
madpuma13 said:
@fattire
1. Where do i locate the Batch #
Click to expand...
Click to collapse
Under your battery 100? number
madpuma13 said:
@Silver
I attempted the procedure and it only resulted in the phone booting up to the att screen then going into recovery mode.
After this procedure, performing method 1 to get into download mode does not result in a stalled battery screen, it now goes into recovery mode. Maybe I fried something....
Oh well off to att tomorrow.....
Click to expand...
Click to collapse
If you can get to recovery mode then your fine well it depends if you have clockwork recovery. Clockwork have an option that will take you to download mode.
Sent from my T-Mobile G2 using XDA App
Related
Yesterday my phone started acting up. All running process crashed and not many was able to start. I had to constantly click "force close". I think this started after I installed the Google+ app, but not sure.
I have tried uninstalling all unnecessary apps, without luck. I then tried wiping to factory settings by using the Android menu, but without any changing. I then tried by holding vol+ and power, going in to recovery and wiping both to factory and app cache. This doesn't change anything either. By googling I can see some suggests to hold vol- and power, to get to a another wiping-functionality but this just boots my Nexus S to normal state - no menu appears.
Has anybody an idea of what I can do?
Edit: more info; if I click "Report" and investigate the message sent to Google, I see that error has something to do with SQLite-relatet classes. Which makes some sense, alot of my changes are reset each time the phone is rebooted. For instance did I miss a call a couple of hours before the phone went crazy - this is shown at each boot in the notification area eventhough I clear the area and/or goes to missed call section
Factory reset via menu does delete all your "custom" apps, so I'd say it's not one of the existing apps causing problems.
The way you describe function after your factory reset sounds like factory reset didn't work properly.
If you feel safe I'd recommend rather flashing 2.3.4 again using either Odin or the OTA zip from Google (requires open bootloader).
I think you're right that factory reset doesn't do what is expected. Once I click it, the phone reboots and shows the Android guy next to an unwrapping package. This lasts only 2 seconds, then it reboots itself again and goes into normal phone mode (where all the app-crashing starts again).
I have not flashed or rooted my phone before, but I will consider this now since my NS is pretty much a brick. Thank you for your swiftly response.
Edit: Shouldn't I get a menu, when I push and hold vol- button, while turning on the device? Right now it just boot as normal.
Before you use odin....try going into rom manager a reflashing clockwork! Ive had that android dude on my screeen but reflashibg via rom manager always fixed it. Try that
Sent from my Nexus S using XDA Premium App
Wow my Nexus has totally shut me out.
I cannot use ClockworkMod unfortunately since I am not able to root my phone. It is not detectable via USA (when I use vol+/pwr and connect USB). I am unable to check the USB Debugging option on the phone. Each time I check it, go to home-screen and back to the menu, it has de-selected it again. Also I noticed when I read the info that is sent to Google for all those app-crashes I get, I see SQLiteException and error in an SQLite.java file. So it seems like some database layer is broken.
I read one could copy the ClockWork.img to my phone and use the standard recovery option to flash the img (I think). But when I go into the recovery menu, the file is gone. When I boot the phone again, it has deleted the .img file - eventhough if I copy it to several different folders, they are all gone :-(.
I feel pretty screwed at the moment. How can I else wipe all data?
I'd recommend to check if your device is correctly identified in windows. Missing USB drivers might cause problems. Get the latest drivers and a guide from here.
If you succeed booting into fastboot properly (vol up and power) you can follow this guide. Get the latest cwm recovery.img here.
Last option would be to boot into download mode (vol up + vol down + power + plugging in usb cable) and use Odin from samfirmware.com
--
All options require correctly working USB drivers.
I managed to unlock the bootloader, by quickly turning on USB-debugging (before any processes started to crash) and install the drivers from this post:
http://forum.xda-developers.com/showpost.php?p=6819751&postcount=4
A reboot later, I got this message:
"System UIDs Inconsistent
UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable."
Right below was a button saying "Im feeling lucky" (??)
I installed ClockworkMod using fastboot and tried "Fixing permissions" with no luck. I will try some ROM later on, and hope it will bring my phone back
Normally this error happens when you have a faulty app ruining your system, formating/deleting whole sdcard does usually fix this.
rentaric said:
Normally this error happens when you have a faulty app ruining your system, formating/deleting whole sdcard does usually fix this.
Click to expand...
Click to collapse
I can safely mount USB-storage and format the whole bunch?
I been sweating over this stupid issue all day now, all I want is a fac-reset :´(
Edit: "format /sdcard" using CWM didn't do anything
DennisRP said:
I can safely mount USB-storage and format the whole bunch?
I been sweating over this stupid issue all day now, all I want is a fac-reset :´(
Edit: "format /sdcard" using CWM didn't do anything
Click to expand...
Click to collapse
See I'm no expert on this whole thing. At this point I'd just flash a whole new system via Odin. Prolly not the smartest or safest option, but that's what I'd do because I don't know better. If that wouldn't fix it either, I'd return the phone on warranty
I was looking at Odin from the start, since nothing else seemed to be working.
So right now I got started on Odin. Followed the .pdf steps and flashed the bootloader at first succesfully. I was asked to remove the battery and re-connect my NS. Began downloading "pda" and "phone", but at around 10% a big fat red "fail" message appeared and now I just see the Google-logo on startup. I still cant flash any roms via fastboot.
Im too tired too right now, been working with this for 14 hours straight. I will look at it tomorrow evening. Thanks for your help rentaric
Weird, you're not the first one who had trouble running Odin using their guide.
Overall it's pretty simple.
Enter download mode. Vol up vol down and power at the same time while plugging in the USB cable. Start Odin, should show a yellow colored box with a port number. Uncheck everything but reset timer and auto reboot. Unzip the correct zip file from samfirmware.com (check if you got i9020 or i9023 and get the universal Odin exe), apply file from the folder accordingly. Bootloader and bootloader. Phone and modem. Pda and pda. Csc can remain empty (will change carrier info in fastboot).
Double check md5 hash to avoid broken files.
Sent from my Nexus S using XDA App
rentaric said:
Weird, you're not the first one who had trouble running Odin using their guide.
Click to expand...
Click to collapse
Of course I did not go to bed, how should I be able to sleep with a broken phone .
The firmware suggested on samfirmware.com for my phone, was 2.3.3 and some other version (my phone was 2.3.4.2/GRJ22 or something similar, I suspect that might be the cause. Also I unchecked everything, that might also have been of importance). The flash will always fail when everything was downloaded - it then said something about "remote" and "Loke" and then fail. But as I mentioned, I had succesfully flashed boot.img (2.3.3) thus no boot occured now. I googled the correct bootloader, used fastboot and was booting succesfully again.
I began looking more into the sdcard, as error-messages was leading me this way. To compress 4 hours of investigations into a few lines, it seems as my PBA is malfunctioning as other xda-members have experinced. Only solution is sending the phone to Samsung for a PBA replacement. I purchased the phone in Bestbuy USA and the danish Samsung partners are not too joyfull about this - I will contact Samsung and hope they can help me.
I experinced the exact same thing as this poor guy - http://forum.xda-developers.com/showthread.php?t=993403
Every thing you try to do to /sdcard is worthless.
Formatting (USB/using CWM/using adb shell linux commands) says "Succes" but nothing happens.
Copying files says "Succes" but nothing happens. If I boot phone into CWM, mount usb and upload new rom/apk/whatever and try to do a "install update.zip" it fails with some mounting errors.
Im ready to go cry in a corner - I really want this to be fixable via software, but I probably have to realize that this is a hardware issue.
Apparently Samsung doesn't offer worldwide warranty for cellularphones :´(. God it sucks to pay repair-expenses on a 1 month old mobile.
Getting Rainbow screen on every boot and when trying to get to recovery mode
For some reason I cannot get my computer to detect my device thus I can not even get into download mode. when I launch Odin and and not able to access my SD. I am at a lost here since now I cannot flash nor can I odin to get back to stock can anyone help here? I think I have tried everything I can find.
I just recently flashed octane 2.x per the instructions under development
rozzko said:
Getting Rainbow screen on every boot and when trying to get to recovery mode
For some reason I cannot get my computer to detect my device thus I can not even get into download mode. when I launch Odin and and not able to access my SD. I am at a lost here since now I cannot flash nor can I odin to get back to stock can anyone help here? I think I have tried everything I can find.
I just recently flashed octane 2.x per the instructions under development
Click to expand...
Click to collapse
If you came from Froyo, follow this guide: http://forum.xda-developers.com/showthread.php?p=16762954
Hope this helps.
sent from my CommandCenter using xda premium
sounds like the bootloader.
flash a froyo rom, then try to odin. AFTER you have tried installing the drivers linked in the previous post. That guide should work.
Did you get this fixed?
Sent from my SGH-T959V using xda premium
I bought a Jig an can get into download mode but still cant get into recover (because of the rainbow screen) and i cannot get my computer to recognize my my phone either via sd or via odin or i think i could solve this.
thanks in advance
I bought a Jig an can get into download mode but still cant get into recover (because of the rainbow screen) and i cannot get my computer to recognize my my phone either via sd or via odin or i think i could solve this.
thanks in advance
Click to expand...
Click to collapse
Go into the control panel & uninstall the USB drivers & kies mini if installed. Then reinstall Kies Mini & use the menu option to reinstall the drivers. See if that helps.
Sent from my SGH-T959V using XDA App
I re installed drivers several times and used a different machine. I feel like I am stuck and there might now be a solution to this except toss the phone in the ocean!
rozzko said:
I re installed drivers several times and used a different machine. I feel like I am stuck and there might now be a solution to this except toss the phone in the ocean!
Click to expand...
Click to collapse
Could it be the cable you're using? I've seen quite a few posts here about people using cables that were bad and/or too long and it prevented the phone from being recognized via USB. People could charge the phone but not use ODIN or anything.
Do you have a different cable to try?
ive tried two different cables, i could try another one thats a good idea. somehow i think maybe i messed up the mounting, i thought i followed the instructions to a t. UMMU .. i will try a few different cables when i get home tonight... actually just tried at work no dice, my system storage is also only showing 126 MB
rozzko said:
ive tried two different cables, i could try another one thats a good idea. somehow i think maybe i messed up the mounting, i thought i followed the instructions to a t. UMMU .. i will try a few different cables when i get home tonight... actually just tried at work no dice, my system storage is also only showing 126 MB
Click to expand...
Click to collapse
I thought the phone did not boot up. How are you seeing how much storage you have left?
I'm curious to know what state it really is in. There has to be a way to get it going for you.
the phone boots fine during the boot after the initial boot screen where it says galaxy s 4g it goes into rainbow patterns. so every time i try to get into recovery when I am in the recovery menu (or into where the recovery menu should be) i cannot see anything because of the rainbow screen. I was told maybe i have the wrong boot loaders installed.
because i cant see recovery and I cannot get my computer to see my phone I have no idea what to do get my phone back to stock to start over.
This is why I am stuck.
If i could get my computer to see the phone I think i could odin back to stock, using the dongle is half the battle as i can get in recovery
rozzko said:
the phone boots fine during the boot after the initial boot screen where it says galaxy s 4g it goes into rainbow patterns. so every time i try to get into recovery when I am in the recovery menu (or into where the recovery menu should be) i cannot see anything because of the rainbow screen. I was told maybe i have the wrong boot loaders installed.
because i cant see recovery and I cannot get my computer to see my phone I have no idea what to do get my phone back to stock to start over.
This is why I am stuck.
If i could get my computer to see the phone I think i could odin back to stock, using the dongle is half the battle as i can get in recovery
Click to expand...
Click to collapse
Pardon me if I'm not getting it....but yo said it boots fine but then you get the rainbow screen when the Galaxy S 4G logo should appear? The rainbow screen is definitely a boot loader issue. I'm just trying to figure out a way to either get you into a download mode where the phone is recognized or into recovery so you can get it going again.
How are you getting it into recovery mode?
I'm wondering if Heimdall would be your best bet? You could try to download it from here, extract it somewhere, then go into the Drivers folder and double-click zadig.exe. Select Options from the menu bar, select List All Devics then select Samsung Android Composite (something along those lines), then click Install Driver. This is a different driver than the one that comes from Samsung.
After that, maybe try Bhundven's [Heimdall][One-Click][UVKJ6] The KJ6 Heimdall One-Click Collection [12/11/2011]. Select whichever one-click file you want to go for and follow his instructions. They all have the GB bootloaders in them, so you should be set.
Usually both volume buttons power button for a few secs or through rom mgr
rozzko said:
Usually both volume buttons power button for a few secs or through rom mgr
Click to expand...
Click to collapse
From what I've read ROM Manager is a no-no on this model phone. I dunno why, but I've read that on a few threads.
Let me know if you're able to install Heimdall and the open source drivers that come with it. If you can, you can get into download mode, and it sees the phone, then you can try the One Clicks or even just flash the boot loaders from a ROM that contains them.
I will try when i go home tonight.
just an fyi every time i plug in my phone, it does not show up on my computer. i have tried using debugging mode and mass storage and neither work.
rozzko said:
I will try when i go home tonight.
just an fyi every time i plug in my phone, it does not show up on my computer. i have tried using debugging mode and mass storage and neither work.
Click to expand...
Click to collapse
Ugh...well let's hope for the best. I would uninstall any drivers and programs like Kies you have installed first, then install the Heimdall drivers. Let me know how it goes.
so i uninstalled drivers executed Heimdall and put phone in download mode with dongle. the computer still did not detect phone, however i got my replacement SGS4 today put it in download mode and it was detected immediately.
I dont know what else I can do do get the phone detected or fix the boot loader to get into recovery
rozzko said:
I will try when i go home tonight.
just an fyi every time i plug in my phone, it does not show up on my computer. i have tried using debugging mode and mass storage and neither work.
Click to expand...
Click to collapse
Maybe I'm missing something. How are you switching between debugging mode and mass media if you can't boot the phone?
The way I understood the problem, you would get to the SgS logo screen during boot, then the whole screen would be covered by the rainbow effect, which renders the screen unreadable, nd thus the phone unusable. Is that correct, or is the problem different?
the rainbow screen happens right after the SGS Logo then fades out once the lock screen comes on.
it also shows up once I try to get into recovery but from that point I cannot see anything and have to reboot.
Phone works after fully booted
both debugging and mass storage have been tried
You need to flash the "GINGERBREAD" bootloaders. This issue is 100% caused by froyo bootloaders. Once you obtain the GINGERBREAD bootloader, there is a 100% chance that the issue will go away. Flash THISTHIS/download. in heimdall. Get into recovery, then flash a rom of your choice.
Hello all, any help would be greatly appreciated.
My wife's phone has been rather buggy so I decided to root and rom it. Rooted the phone with the oneclick method. Moved on to getting CWM up and running (it is what I'm familiar with from my G2x). I liked what I was seeing with the Valhalla Final rom OP and decided to give it a try. Read the instructions to install but things have steadily gone down hill.
I am comming from stock. I did a NANDROID backup. Wiped, wiped, wiped and then flashed the ROM. I do believe that I just didn't read carefully enough where it says I "must have pre-installed kernel" . When I rebooted I got a pixelated screen unreadable screen. There was a voice in the background describing what was going on but I plugged along and waited the 5-7 minutes. Figured if it didn't work correctly I would just go back into CWM and restore my nandroid backup. However I can no longer get back into CWM or the recovery prompt that comes before CWM. I just get the Galaxy S 4g screen which then goes to the weird pixelated screen and then it continues in a boot loop.
I tried to follow this debricking thread but got stuck a couple of times. First, that I can't find the boot.bin and sbl.bin files. I google around and found this but the download link no longer works. Does anyone have the boot.bin and sbl.bin files handy?
Also, the Zadig program to install the Heimdall driver doesn't show me any driver options. I suspect that this is because Heimdall or Zadig had not run on the computer before I had the phone properly connected. I saw that it was the Samsung Composite driver that was being asked for. Not sure if I found the correct one but either way it didn't work. I was unable to get the computer to recognize the phone (also phone would continue on its boot loop, also it doesn't change anything whether I am holding down the volume buttons when I turn the phone on or not).
I have stayed up half the night looking for something but am wondering if I just straight up bricked the phone and need to send it to someone with JTAG experience. Let me know if there is something I am missing or some suggestions you have.
Go here:
http://forum.xda-developers.com/showpost.php?p=21953878&postcount=2
The problem is that you tried flashing a gingerbread rom even though your phone still had Froyo bootloaders. If you flash a gingerbread rom using one of the one click files mentioned in the guide, you'll be able to flash more GB custom roms.
Don't worry your phone is fine, you just need to read a little more and you'll be good to go.
Thank you very much for the link, the post is very through. I am getting stuck because my phone appears to not want to go into "Download Mode." Every time I press the up + down vol buttons and plug in the usb I just get the attached images and they go in an infinite boot loop.
I have tried every usb port on the computer and followed the instructions near the first of the post and uninstalled all ports which had Android or Samsung associated with them. I also tried all the different ways I could to get into download mode based on this link.
I am currently in the process of uploading a clip of the infinite boot loop I am in on Youtube and will post it if it helps.
Again thank you all for your help. The XDA community is the best!
That is the rainbow screen indicating you need GB bootloaders. Just pull your battery. You need to flash twice - second time checking the 'flash bootloaders'.
For the driver issue/phone not recognized by the computer - There is a tool in the guide called USBDeview (in the notes). Use it to make sure you have uninstalled all android related/unknown drivers. Go into uninstall programs and make sure you uninstall Samsung drivers. Restart your computer. I also run the CCleanner reg cleaner. Then restart computer again.
For Download Mode - Pull battery. Plug your USB into your computer only. Make sure you are pushing both the volume up and down buttons simultaneously. Without putting battery back in, plug your USB cable into your phone while continuing to hold volume up and volume down buttons. Keep holding volume buttons with USB plugged into phone and computer and put the battery back in.
Start guide over and read thoroughly.
Fb that's the screen I got coming back from nand back up!!! I had to flash a diff kernel with Odin to fix it
Thanks for all your help. Ironically I was doing everything correctly, but my usb cable had gone bad on me the night that it all happened. So thanks all, espicially lumin30 for the excellent guide and for FBis251 pointing me to it. After switching to a working cable and completing lumin30's guide all is now working great!
As a random side note the driver section showed up slightly differently for me (the device I had to pick was [usb composite] but once I figured that out everything went well).
Glad you figured it out
I've spent weeks surfing the forums trying to get past the common recovery file rename and replacement with a system manager that is in super user mode etc. I don't know if it's the particular version of the recovery file that I've replaced being bad, but the first time I was soft bricked I was able to physically reset with a guitar wire in that whole ( was weird cuz it seemed like the button wasn't going to work cuz after minutes of turning the phone on and off it just randomly worked) Let me explain better because after chosing a different recovery file it soft bricked again however the reset isnt working. Ok so if I have USB cable in it brings up charging battery logo (showing the battery as dead which isnt true because the time it did reset... when it worked, the icon illuminated green suddenly. If the USB isnt connected upon turn on the samsung comes on indefinitely (forever)... tried with sim in & out etc. If I reset into download mode it just says downloading (let it go for three hours before stopping it once). Ive installed odin and tried to fix it that way... I made a Jig with 3X100k resistors and 1 1ohm 1watt ..( attempting to get the 301k resistance between the 4th and 5th pin in the micro usb connection... Didn't work ( used a voltmeter to test the jig but I didn't know what the reading should be but I saw a difference ( thougt the 1 watt addition was messing it up so I omitted that resistor. Still didnt work.... guess I could splurge and buy a jig online as a back up if I cant beat it differently. Lastly and more promising was downloading ADB and getting it running correctly... at first because of the inability to adjust bugging or not the device wasnt recognized... miraculously I left it alone andcame back and tried it... device is recognized... tried to adb pull recovery.orig file to C: to rename and push back but I didn't see it on the PC to rename after Adb says the pull file command was done. Thanks for your patience with all this info on first message. Im new to this. Im sad that I have to get into this just to take control bake but there is a user and or group that is runing in my background and changing my permissions and running so many processes its like slow motion. doing this so I can run the roms to control my traffic and get some Ram back... I wish I could just ask him to please stop. Thank you for any help.
If I reset into download mode it just says downloading (let it go for three hours before stopping it once)
Click to expand...
Click to collapse
What exactly are you doing with it when you have it in download mode? If you can get into DL mode already, what's the point of the jig?
What was the exact procedure you used with Odin, and at what point did the flash fail? Maybe I'm missing something in that wall of text, but it seems like, if Odin isn't working for you, you could always try to Heimdall back to stock and then flash a kernel & CWM one-click installer.
http://forum.xda-developers.com/showthread.php?t=1629079&highlight=uclb3
BTW, please separate your paragraphs. One big block of text is kind of a pain in the ass to read through.
Odin
ApexPredatorBoids said:
What exactly are you doing with it when you have it in download mode? If you can get into DL mode already, what's the point of the jig?
What was the exact procedure you used with Odin, and at what point did the flash fail? Maybe I'm missing something in that wall of text, but it seems like, if Odin isn't working for you, you could always try to Heimdall back to stock and then flash a kernel & CWM one-click installer.
http://forum.xda-developers.com/showthread.php?t=1629079&highlight=uclb3
BTW, please separate your paragraphs. One big block of text is kind of a pain in the ass to read through.
Click to expand...
Click to collapse
Odin wasn't recognizing the device before at all, but since I set up ADB and ran the adb sync comand, now when I run Odin it recognizes the device as com5 not com++ (not sure if that matters). I'll try and start a pit and see what happens.
If I went back to stock what kernel do you recomend I flash and do you know a good recovery file to replace the original one to get past the signature verification when reinstalling packets.
Flash entropy's dd kernel. There is no need to replace any recovery file in GB (that's only on froyo).
Sent from my sweet & buttery Infuse
hi im pretty new here a friend of mine gave me her lg c800 mytouch to try and fix it for her.. not sure what she did she said she rooted the phone and the root was successful but i have a good idea that she doesnt know what she was doing..i will post a pic of the error screen im getting. but it says
E:Cant find misc
E:cant find misc
Finding update package...
E:unknown volume for path [sd:/download/adb_fastboot_and_other_tools.Zip]
E:Cant mount SDCARD:/download/adb_fastboot_and_other_tools.zip
Installation aborted
facory reset failed
restart factory reset..
now im far from a pro at this i know a lil more about computers and Ios devices..but ive rooted a few phones and to me it looks like she unzipped adb fastboot on her phone from her sd card??
ive tried holding F..A..vol down..and power..Nothing..
ive tried volume up .volume down and power still nothing..
BUT if i hold E..vol UP and power it brings me to a white screen that says S/W update
the big problem is the phone wont stay on long enough to do anything on the computer it stays on 3 sec. then reboots to same screen (computer says phone is unplugged) then phone just keeps restarting.
but the phone WILL stay on when i put it on the S/W update screen..but computer wont recognize the phone at all on that screen
ive tried the adb and fastboot commands but the phone wont stay recognized..it will recognize the phone and say thats its in recovery mode but when phone restarts it dont see phone no more..
well thanks ahead of time if anyone has any input or solution
and hopefully all this will make sense to someone lol
i think this pic will work.. if not ill try again
any ideas please?? or am i completely out of luck?
When you say:
delilah25 said:
it will recognize the phone and say thats its in recovery mode but when phone restarts it dont see phone no more..
Click to expand...
Click to collapse
...do you mean that you can successfully communicate with the phone over USB, but you only have 3 seconds? What way is the phone recognized? Is it visible to adb/fastboot?
post-mortem said:
When you say:
...do you mean that you can successfully communicate with the phone over USB, but you only have 3 seconds? What way is the phone recognized? Is it visible to adb/fastboot?
Click to expand...
Click to collapse
Yes In Adb device list it shows the phone and then says recovery..but after that I don't have enough time to type any other commands ..the phone is also recognized in "my computer" as removable device then when the phone restarts seconds later it says device unplugged ..and just keeps restarting on its own till I remove the battery...I just read on the forum in a post that Adb will recognize the phone if it's off but I remove the battery and put it back in and plug in USB and phone turns on and keeps restarting won't even let me turn it off!! I'm losing patience with this thing lol
But I don't get why the error mentions fastboot? Not my phone so if it's not fixable I don't really care but I'm just the stuborn type when it comes to fixing electronics ..again thanks ahead of time to anyone that helps cuz I'm completely lost on this one
Have you tried timing it to send a quick "adb reboot recovery"? If you can use fastboot, you can tell it to boot off a new, custom recovery img, without actually flashing it.
i have the same problem
post-mortem said:
Have you tried timing it to send a quick "adb reboot recovery"? If you can use fastboot, you can tell it to boot off a new, custom recovery img, without actually flashing it.
Click to expand...
Click to collapse
i used an app on the market to remove bloatware. i removed slacker and the app stated that after two reboots that everything would be fine and the app would be gone. after one reboot the phone has the same screen this gentlemans lady friend has. it looks like the app its looking for is no longer zip aligned properly. someone told me to rename a recovery image the error message to trick the bootloader into thinking the missing app is there. hes an app dev so i figured he knows whats what. ive tried everything the gentleman in this post said and more. hell i have two of these phones and rooted the other and made a backup of that phone and dragged the backup to an sd card and rebooted to see if any of the backed up system apks would trigger a successful reboot but to no avail. i have all the drivers i need and adb commands but nothing works because the phone doesnt stay connected to my pc long enough for anything. please reply with some knowledge. ive been scouring the web for at least a month. i was so happy when i came across this. i actually became a member just to post about this erroer (look up diabolus ae in the forum search field. my post is about 3 days old with a better pic of the screen message. i bought a galaxy s II but i want to give the lg to my son. please help or respond:cyclops:
diabolus ae said:
i used an app on the market to remove bloatware. i removed slacker and the app stated that after two reboots that everything would be fine and the app would be gone. after one reboot the phone has the same screen this gentlemans lady friend has. it looks like the app its looking for is no longer zip aligned properly. someone told me to rename a recovery image the error message to trick the bootloader into thinking the missing app is there. hes an app dev so i figured he knows whats what. ive tried everything the gentleman in this post said and more. hell i have two of these phones and rooted the other and made a backup of that phone and dragged the backup to an sd card and rebooted to see if any of the backed up system apks would trigger a successful reboot but to no avail. i have all the drivers i need and adb commands but nothing works because the phone doesnt stay connected to my pc long enough for anything. please reply with some knowledge. ive been scouring the web for at least a month. i was so happy when i came across this. i actually became a member just to post about this erroer (look up diabolus ae in the forum search field. my post is about 3 days old with a better pic of the screen message. i bought a galaxy s II but i want to give the lg to my son. please help or respond:cyclops:
Click to expand...
Click to collapse
Normally, if you want to flash a custom recovery through fastboot, people will tell you to run 2 commands:
fastboot flash recovery nameofimagefile.img
fastboot reboot recovery
Since you don't have time to execute those 2 commands, you can tell it to just boot from the .img file, without flashing over your current recovery. (This is actually proper form, as you can test if the .img file works properly without damaging your existing recovery.) The way you do that is to 1st copy a recovery .img file to the root of your SD card, then execute the following 1 command:
fastboot boot nameofimagefile.img
Since you only have ~3 seconds, type the command in, and wait for the right instant to hit enter on the keyboard. If the command is successfully sent to the phone, it will reboot into that .img.
See if that works for you. Good luck.