Related
Hi all, this is my first post here, but I've been reading walkthroughs for a while now. I really apologize for being such a noob, but any help/pity to help a girl figure out if she's just bricked her phone would be greatly appreciated.
I tried to flash a Gingerbread beta I got through one of these forums. I used Odin to root and it seemed like the install went OK, but when the phone started back up the screen went through a crazy colors standby (red, green, blue lines all over it), right after Samsung and before AT&T. This continued to happen at that point of startup every time, in case that's helpful. I also would randomly not send texts even though it looked on my end like they sent. I must not have rooted it properly because I tried to install an app (ROM Manager, I believe) that needed root permissions it said it couldn't get. I decided I was not ready for the phone ROM world and read up on returning it to stock.
To do that, I found this thread:
http://forum.xda-developers.com/showthread.php?t=1116251
I used GTG's Ultimate Unbrick, but again, I must have done something wrong. I downloaded Odin3 v1.70, ran as Administrator, and connected my phone in download mode. I clicked "PIT" and selected infuse.pit, I clicked "PDA" and selected PDA_UCKD5.tar.md5, then "PHONE" and PHONE_UCKD5.tar.md5. The "Re-partition" box was checked. The first time it said it failed. Two subsequent times it said nothing happened. For some reason my phone said it was "Downloading" even though nothing was happening on my computer and it said it had failed. It had been at that same screen for probably ten minutes or so with no progress I could see, and the thread mentioned it might boot loop or something, so I unplugged it. After that, it never started up again.
So far I've tried:
- Holding down power and volume buttons
- Removing the battery for about an hour
- Leaving it on its charger for about two hours
- Plugging it into the computer without SIM, SD or battery
I'm at a loss and at this point I'm pretty sure I've bricked it. I bought it from someone else (it was fully functional up to the point I tried flashing the ROM, although it said it was missing something it needed for a factory reset), so no warranty here. I'm hoping some brilliant dev will have some insight to save me from going back to a dumb phone!
Thanks for any ideas.
try putting it back in download mode and see if odin recognizes it if it does do the return to stock agian
fawn87 said:
Hi all, this is my first post here, but I've been reading walkthroughs for a while now. I really apologize for being such a noob, but any help/pity to help a girl figure out if she's just bricked her phone would be greatly appreciated.
I tried to flash a Gingerbread beta I got through one of these forums. I used Odin to root and it seemed like the install went OK, but when the phone started back up the screen went through a crazy colors standby (red, green, blue lines all over it), right after Samsung and before AT&T. This continued to happen at that point of startup every time, in case that's helpful. I also would randomly not send texts even though it looked on my end like they sent. I must not have rooted it properly because I tried to install an app (ROM Manager, I believe) that needed root permissions it said it couldn't get. I decided I was not ready for the phone ROM world and read up on returning it to stock.
To do that, I found this thread:
http://forum.xda-developers.com/showthread.php?t=1116251
I used GTG's Ultimate Unbrick, but again, I must have done something wrong. I downloaded Odin3 v1.70, ran as Administrator, and connected my phone in download mode. I clicked "PIT" and selected infuse.pit, I clicked "PDA" and selected PDA_UCKD5.tar.md5, then "PHONE" and PHONE_UCKD5.tar.md5. The "Re-partition" box was checked. The first time it said it failed. Two subsequent times it said nothing happened. For some reason my phone said it was "Downloading" even though nothing was happening on my computer and it said it had failed. It had been at that same screen for probably ten minutes or so with no progress I could see, and the thread mentioned it might boot loop or something, so I unplugged it. After that, it never started up again.
So far I've tried:
- Holding down power and volume buttons
- Removing the battery for about an hour
- Leaving it on its charger for about two hours
- Plugging it into the computer without SIM, SD or battery
I'm at a loss and at this point I'm pretty sure I've bricked it. I bought it from someone else (it was fully functional up to the point I tried flashing the ROM, although it said it was missing something it needed for a factory reset), so no warranty here. I'm hoping some brilliant dev will have some insight to save me from going back to a dumb phone!
Thanks for any ideas.
Click to expand...
Click to collapse
Check out my thread on the HOW TO. The link is on the signature line. Read it a few times.
re: the first paragraph with the colors -rainbow - it's due to lack of GB bootloaders.
The part where the phone is not responsive:
http://forum.xda-developers.com/showthread.php?p=19445643.
This link give you various method of getting into DL mode.
If it doesn't work,
try a different usb port on the pc, diff usb DATA cable, try a diff computer.
IF the phone is still not responsive, you a need a usb jig to put the phone back in DL mode.
search youtube for "usb jig". There's a vid that shows you how to make one.
gl
Hello, I know, this question rather belongs to this thread:
http://forum.xda-developers.com/showthread.php?t=935578
but since I had no intention to flash my phone and I also have not enough posts to reply to the other thread, I hope this forum might be the right one
(edit: sorry, somehow I managed to get even this wrong. I wanted to post in the LG Optimus 7 subforum )
I installed the most recent update, when my LG lost connection. I then removed the battery (duh!) and eventually it transformed to a pocket warmer (well, it got no other function than heating up ).
I tried all the things Microsoft recommended me (Phone recovery tool on different computers & different usb slots ).
But always the same message : Can't repair, contact service.
So I stumbled upon the flash thread. I managed to get my old winxp sp3 rolling and installed everything. After countless tries my phone was recognized and it was even successfully flashed - wait!
It shows 100% and then the emergency download screen disappears, it reboots and shows up the LG logo.
The same state as before. (I am also not able to shut it down, it keeps firing up itself)
I tried the format all keys (vol + - & pwr) but it doesn't accept this combination.
I tried the vol - key in emergency download, but it does nothing
So i downloaded the European firmware besides the German one (allthough the download I could find, only had ~170 MB)
Anyways, it had no effect. Still only the LG logo, nothing more, nothing less.
Zune only shows, I should contact service (like the support tool) and the phone itself only accepts the key combinations for connection mode, cold boot, emergency download + power off (although this is rather a reset function, 'cause it always restarts)
Is there anything I could try which might get Windows back on my LG (besides sending it back to manufacturer ) ?
Thank you in advance and sorry for any spelling / grammar mistakes I made
Hi friend,
you can take out the SUB board (the board which insert SIM card), then Power ON. If you can get in to Wellcome Screen. You can fix this problem.
==> The eMMC Toshiba IC got problem, try to re-solid it. i was do this way and my fone working again.
sorry about my English.
I have an extreme problem with my Nexus. I've been through thick and thin with this phone, and I'm hoping you guys will help with a solution to this problem.
The power button to my Nexus is broken completely. I stabbed it so much that the clicking black part is completely removed from the slot (on the motherboard).
One time, my Nexus S died, and I realized I had no way to turn it back on. I tried every single method (battery pulling, button pressing, USB connecting, etc) with no answer. I finally was able to find a solution. I used Odin to restore the bootloader tar md5 file, and thus auto rebooting the nexus (when the box is checked). This worked like a charm, until I realize I made a fatal mistake.
I chose an md5 file for the ORIGINAL Nexus S (not 4g).
I was able to easily go into recovery with Quick Boot from the Play Store. I installed Raspbean Jellybean (02-05-13 build), but the installation was very faulty. The home button is nonfunctional (it vibrates when pressed, but nothing happens) and Browser is not working as it just closes itself instantly. Like an idiot, I didn't install Gapps before rebooting into the ROM.
Stuck in that dilemma, I used the built in email app to sync my Gmail account to the phone. I sent a Quick Boot APK to myself to try and open so I could reach recovery, but it said there's no type of program that can open that file (maybe because Gapps isn't installed).
The last thing I tried was Odin again. I tried to restore the ICS release keys, but Odin will not recognize my phone anymore for nothing. I tried 3 different USBs (2 with shorts, and 1 normal one. I don't know if the type of USB has anything to do with it). Nothing.
So here I am with a faulty, Gappless ROM on my Nexus S 4G with a completely broken power.
I'm wondering if you guys have any solution/suggestion to get Odin to recognize my phone again so I can restore it and work from there.
Apart from that, ANY solution to this problem is highly acceptable and greatly appreciated (ways to get into recovery, etc). I don't want this to be the last of me and my sweet ole Nexus =(,
Thanks x1000 XDA!
Hey Guys. I was actually able to reach recovery, because the ROM I'm using has a Power Menu widget in it's quick settings (Go Figure). But my phone is still unable to be recognized by Odin in Download mode. The phone is also not recognized by my pc at all. It only charges, no matter what USB I try. I even tried mounting in recovery, no go.
Please help. Thanks!
Hey gang - I've been traveling for work and just have some crappy slow satellite wifi for access. The phone has been great because I can use wifi calling and all is good.
A few weeks ago my phone crashed. When I rebooted I was at the "touch android to begin" screen. Well... fix permissions and clear caches didn't work.
So next I restored a backup from CWM.
Unfortunately, after that the phone hangs at the initial Samsung splash screen.
Now, stupid me didn't go an a six-month trip with the Android software on my laptop - so I had to wait for my wife to mail me a thumbdrive that has SOC, HOC, drivers, & etc. on it in order to do anything.
In a previous thread from when this first happened, you all recommended I use HOC to flash the phone back to stock. Which now that (yesterday) I got the thumbdrive in the mail, I am happy to do.
My problem comes from the fact that the phone hangs at the Samsung splash screen seemingly no matter what I do... zadig.exe doesn't recognize the phone on the USB port (just "unknown device") and therefore HOC can't do anything (I think?) Furthermore, I can't even get back into recovery or download mode; at least not with the several techniques I've tried so far.
Recommendations? Or am I hosed?
Thanks in advance,
JaimeZX said:
Hey gang - I've been traveling for work and just have some crappy slow satellite wifi for access. The phone has been great because I can use wifi calling and all is good.
A few weeks ago my phone crashed. When I rebooted I was at the "touch android to begin" screen. Well... fix permissions and clear caches didn't work.
So next I restored a backup from CWM.
Unfortunately, after that the phone hangs at the initial Samsung splash screen.
Now, stupid me didn't go an a six-month trip with the Android software on my laptop - so I had to wait for my wife to mail me a thumbdrive that has SOC, HOC, drivers, & etc. on it in order to do anything.
In a previous thread from when this first happened, you all recommended I use HOC to flash the phone back to stock. Which now that (yesterday) I got the thumbdrive in the mail, I am happy to do.
My problem comes from the fact that the phone hangs at the Samsung splash screen seemingly no matter what I do... zadig.exe doesn't recognize the phone on the USB port (just "unknown device") and therefore HOC can't do anything (I think?) Furthermore, I can't even get back into recovery or download mode; at least not with the several techniques I've tried so far.
Recommendations? Or am I hosed?
Thanks in advance,
Click to expand...
Click to collapse
Interesting problem. I have bricked my phone a bunch of times and have always been able to get back to at least "download Mode". The method I use to go to "Download Mode" is With the usb cable plugged into the computer only, power off the phone. If phone wont power off, or stay powered off, pull battery, then put battery back in. Now hold vol down and vol up buttons only, keep holding these buttons as you plug the usb cable into the phone. In 3 seconds the download screen should appear. I hope this helps you get your phone back.
JaimeZX said:
Hey gang - I've been traveling for work and just have some crappy slow satellite wifi for access. The phone has been great because I can use wifi calling and all is good.
A few weeks ago my phone crashed. When I rebooted I was at the "touch android to begin" screen. Well... fix permissions and clear caches didn't work.
So next I restored a backup from CWM.
Unfortunately, after that the phone hangs at the initial Samsung splash screen.
Now, stupid me didn't go an a six-month trip with the Android software on my laptop - so I had to wait for my wife to mail me a thumbdrive that has SOC, HOC, drivers, & etc. on it in order to do anything.
In a previous thread from when this first happened, you all recommended I use HOC to flash the phone back to stock. Which now that (yesterday) I got the thumbdrive in the mail, I am happy to do.
My problem comes from the fact that the phone hangs at the Samsung splash screen seemingly no matter what I do... zadig.exe doesn't recognize the phone on the USB port (just "unknown device") and therefore HOC can't do anything (I think?) Furthermore, I can't even get back into recovery or download mode; at least not with the several techniques I've tried so far.
Recommendations? Or am I hosed?
Thanks in advance,
Click to expand...
Click to collapse
This sounds like a time where a jig would be helpful. Any chance you can have your wife order one, and send to you? http://www.youtube.com/watch?v=D7I4dFX_iJ4
This should put you straight into download mode, and you can then flash.
Thanks, guys. I continued fiddling and got the phone into DL mode.
I also noted that when plugging and unplugging the phone, it would show up in zadig as "unknown device."
I tried to load the drivers on that, but (a) it still shows up as "unknown device" and (b) when I run HOC it doesn't see the phone under the list of compatible devices.
So.... still kind of stuck.
Any more ideas?
Oop. duplicate post
It's been awhile since I've played with the one clicks, but, "serial gadget" is what I remember seeing when I used them.
Right. MORE messing around later and "Serial Gadget" is it.
That said, I still think I have a driver issue. I have tried uninstalling and reinstalling the zadig-recommended drivers for Serial Gadget several times. I also tried manually installing the drivers from Super One Click.
Anyway, now when I load up HOC I get the green <<connected>> at bottom; but then sometimes it wants me to install the drivers (again) and sometimes it gets past that part, but then goes to
Flashing Kernel: 0%
...hangs there for about 10 seconds and then
Failed!
So... driver thing you think?
Thanks again,
If you reboot the phone after the 0% hanging for 10 seconds, does it go to the yellow exclamation mark screen? If so, just reflash again and you should be back to working... both my and my wife's phone always did that when I had to flash a kernel.
That's just another download screen that theraze is describing.
Exacatly. But the alternate download screen always came up after restarting the phone after a 'failed' flash where it stayed at 0% where it was successfully communicating through the cable. That just meant to not break the drivers or unplug anything... just reboot fast and finish up quickly.
Okay - I can definitely try that! It had not occurred to me to try and reboot the phone right then.
Question, though - when I get the "Failed!" Then HOC essentially hangs, when it says something along the lines of "ending session..." and never progresses from there. So how do you "restart quickly?" Because I have to like, close and reopen HOC. I guess I will see if it succeeds at ending the session when I reboot.
I will try it again. Strange though, sometimes HOC accepts the existing driver (I managed to DL the Samsung driver installer) and sometimes it wants to reinstall "WinUSB." does that make sense? Is the WinUSB an acceptable one?
The winusb is the right driver for heimdall, it doesn't like the Samsung driver.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Samsung drivers and the one click drivers clash. Yes, uninstall Samsung completely if you want to use the one click.
Hm. Thanks for that - might be part of the problem.
Dunno what I did differently, if anything, but last night I tried flashing again and this time it went through! I was very glad to see the whole HOC process completed successfully!
So anyway - thanks so much for the help, guys.
I think I killed my phone. I lil' story -- i decided to flash my Redmi 9A, flashed PBRP onto it and.. Black screen. I already faced it, so I just try to flash original firmware with SP Flash and... Error. Can't quite remember what it was. I try to use bypass, and although bypass does give the "Success" output, SP Flash still gives the same error. I google this error and it seems like it is an issue with drivers. OK, I remove all the drivers and try again. It got zero battery at this point. Now it's not recognized by PC at all, Windows gives no error, FIlter Wizard doesn't even recognize it, Bypass gives a driver error. I'm sure I installed all the drivers correctly. I also tried:
To use my installation of Arch Linux using this guide, no success, bypass doesn't recognize the phone
This LIveCD, where all the drivers should be properly installed, but no success, same as every other try
I'm very stuck. Any suggestions?
ignaycyhry said:
I think I killed my phone. I lil' story -- i decided to flash my Redmi 9A, flashed PBRP onto it and.. Black screen. I already faced it, so I just try to flash original firmware with SP Flash and... Error. Can't quite remember what it was. I try to use bypass, and although bypass does give the "Success" output, SP Flash still gives the same error. I google this error and it seems like it is an issue with drivers. OK, I remove all the drivers and try again. It got zero battery at this point. Now it's not recognized by PC at all, Windows gives no error, FIlter Wizard doesn't even recognize it, Bypass gives a driver error. I'm sure I installed all the drivers correctly. I also tried:
To use my installation of Arch Linux using this guide, no success, bypass doesn't recognize the phone
This LIveCD, where all the drivers should be properly installed, but no success, same as every other try
I'm very stuck. Any suggestions?
Click to expand...
Click to collapse
If u install a recovery rom and you did it wrong you can boot to fastboot, no?
Hey I faced similar or even worse (twice), I had a similar story to yours,
FIrst itme:
I first bricked my phone, but it was cool, the phone just flashed MIUI for a fraction of a second when trying to go to recovery, other than that, nothing, I tried flashing, wich made it much much worse, black screen, no key combo did nothing, windows not just did not recognize it,it told me there was no way of recognizing it, (error 43 in devices admin, its not posible to reinstall the driver, nor do crap at this point) filter wizard showed nothing, bypassing imposible, etc.
It got pretty similar to what you had:
I just left the phone do some charging discharging cycles (at least 4 days with me checking if the phone did anything at all almost once every day, just so you know the phone was really bricked) and it eventually responded after all that (Im not quite sure what fixed this, I dont kno if it was complete discharge or what, but something happened and it vibrated when holding the pwr button.
Once that worked, I managed to install the filter by pressing volup voldown and conecting the phone to the USB port (dont use 3.0, it works worse for some reason) at the same time, you need to connect and press the buttons and connect at the same time (
at 1:30 he does it, video on spanish) and then you can install the filter.
Then you can Bypass and attempt to flash with SPflash tool, I recomend autoconcect, UART never made it for me, Im thinking thats for when you can put it in EDL mode by presing the test points, but I dont know enough to say for sure, point is, UART never worked for me, even tho I eve know what comms I was using.
second time:
I was running Custom ROM ArrowOS 12, ArrowOS13 came out some weeks ago, so I decided to lash it, it was better in some areas and worse in others, the contacts app did not work, but now Volte fingerprint(irrelevant to us redmi 9a users) and face unlock did so I decide to test some stuff, I wasnted to flsh boot.img from original MIUI ROM on top of ArrowOS13, to check if that fixed some stuff (that worked wonders on ArrowOS12) that bootloped thephone but it was fixable from recovery, I did that and decided to flash MIUI ROM to check if flashing ArrowOS13 from MIUI ROM worked, and flashing MIUI bricked my phone.
unrecgnized with error 43, not posible to fix from software, black screen no response whatsoever from any key combo (all 7 combos) no charging, no filter, no nothing, I know I had around 50% battery (days ago I remembered the exact number, now I forgot it, but just so you know, its not a hunch, I knew it had battery) I tried doing the same stuppid crap, charging and leaving it alone for couple hours, but after one night nothing worked, so I assumed I would have to repeat the procees I did before (I wrote it complete on an unbricking thread so I knew I could go back there and redo that or variate it until it worked), but I decided to do one final thing.
I knew it had battery, so I decided to try and forcedrain the battery, I took a piece of TP and gave it a turn around the phone over the buttons (this is just to not dirty the phone) then with electrical tape, I left the power button and the vol down button pressed) this for around 7 hours my plan was leaving it like that for a full day, but around 6 hours I thought I heard a vibration from the phone, so I kept it with me, then after a while I thought it happened again, but I also had my own phone with me so I thought it was that and some other things distracted me so Im guessing I missed a few, but after that I started to take time from every vibration and yeah, around every 8 - 10 minutes the phone vibrated
I decided to connect the phone (I hadnt before because it would just slowdown the battery draining process) and the phone conected to the pc, still bricked, but it was a lot better, I quickly installed the filter, wich I dont quite remeber, but it wasnt easy, I had some hickups, cmd bluescreened my PC when using Bypass like 6 times, so I switched to powershell and that worked (to do that you need to press shift+right click and open powershell here, then run "python main.py") that worked, but I did not flash using SP flash tool.
I was trying to avoid turning on the phone for fear it would go back to the previus state, but after a while pluged on the PC it showed the no battery logo so I tried to tun it on and it was bootlooped, I was able to go to recovery and fastboot (not normally, I pressed the keys, the phone try to go into those menus, it showed no battery, and in the next cycle after splash logo no matter what you did it sent you to the previus key combo menu) I tried leaving it charging on fastboot, but that did not work, I tried flahing a rom from recovery (wich said I had 47% battery) and it successfully did but when trying to reboot to system it again showed no battery logo. so I put it on fastboot and tried flashing MIUI with Miflsh, did not work but it told me the ROM was bad (same one I had use before) I made sure to extract it again and again nothing, I assume it was the antirollback, so I downloaded the next one on line 12.5.6.0 (I was on 12.5.4.0) and that finally worked (Miflash actually gave me lots of errors but you can google them and most of them have easy fixes, like creating a log folder, etc)
that was yesterday, after it worked it showed me the phone had around 60% batterywich lasted around 30 minutes to 40%, then it took 10 minutes to spend the next 20% (it told me that) and then it drained 1% every second (Im not exagerating I thought I had fried my battery with all that power button pressing) but I had hopes of it just being a configuration issue of the phone not knowing how much battery it had so I just left it power of and pluged it then so the phone knew what was his zero, now the phone as been on 100% for like 2 hours (sharing internet), so yeah, I think the battery has some issues but its better than nothing so Im happy with that.
that is my whole experience, I hope it helps you, see if you manage to get any response from the phone and if you do you can try contact me for help in any point along the way.
Update, it just got to 99% after 2 hours 10 minutes aprox IDK, I would need to test more to be sure