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
Related
I've been running a ROM I built from the consolidated kitchen this weekend without any problems. Today I updated the radio to 2.69.11 from the cingular 2.25.11. After the flash the phone froze on the windows mobile screen. After some time I tried to reset the phone and it froze again, a few more tries and it finally boots up. I didn't pull the memory card when I flashed and thought that might have been the problem so I flashed again even though the phone was showing 2.69.11. I don't remember everything after that but it wouldn't boot up and I have tried flashing the original Cingluar ROM & T-mobil 2.26 without any luck.
The phone is stuck in bootloader now and is getting a error code 302 I think it's because the phone doesn't stay on when the USB cable is attached. It gets to about 15% and the phone resets and the error 302 pops up. When connected and not trying to update the phone turns on and off in the bootloader screen. I have pulled the battery, rebooted the laptop, tried using mtty,and pulled the sim. I thought the original problem might have been because I flashed at 52% battery. I put a older battery in after that appeared to have a good charge. Right now I put the phone on charge with the newer battery to see if this helps. I am not sure if it is charging because the orange light is not on, I can't get the phone to stay turned off when plugged into the charger and the bootloader screen is on.
And yes I have been searching for hours for a solution to this problem.
Also looking for a post I read about doing a master reset, I have tried holding the 2 soft keys when turning on, didn't help.
I think this says it all I have tried everything, does anyone anything else to try?
Thanks
UPDATE: went out for a few beers and some food. Not sure it the battery charged (bootloader screen on the whole time it was plugged into the charger)
Tried flashing again with cingular ROM, got about 20% and phone shut off and turned on again in bootloader. Flash gave 302 error again. Tried again and phone reset (on and off) every 5 seconds when connected to laptop with USB.
I'm hopping someone out there has a answer for this problem.
Back from the dead HALLAULA!!!!
This morning I spent more hours searching still didn't out find anything.
I tried mtty again and noticed that I never got to the screen that shows USB>
to enter the command "set 14 0"
I came up with a thought and this is what I did. Created a new ROM, OS only. Thinking it will load faster than any other ROM. It reached 100% in 3 minuets the whole I'm coaching come on baby don't restart and than going (don't know how to explain the feeling) waiting the next 2 minuets to get to finished. But it got there booted fine. I don't know why it stayed on this time and didn't restart, maybe having the battery out all night had something to do with it. After I flashed the Cingular ROM than the original I created and lastly Radio 2.69.11
I hope this helps someone in the future,
i need your help
hi man I had a prophet s200 and give me the same error 302 but, with the diference in my case got 98% adn then stuck in boot screem, please help me if you can...and sorry for my english
Guys,
It may help checking out this thread!
http://forum.xda-developers.com/showthread.php?t=294107
Can you help me out?
How did you create a new ROM - OS only? I'm having the same problem..can you walk me through this?
Thanks
How did you create another ROM (Operating System only)? I'm having the same problem and I have tried for the past 2 weeks - but no luck. Can you walk me through it?
Thanks
I used the consolidated kitchen (sticky at the top of this forum)
Uncheck everything on Build OS.
My problems started from a version of battery status that caused the original problem and not having enough of a charge on my battery.
Make sure you are CID unlocked (if you have a G3) and your battery is charged.
Umm, you can't uncheck everything in build OS or you will have problems, especially if you don't check a tuchflo or non touch flo dll or choose a commanager and probably a few others things. I don't have build OS up in front of me to check. The whole point to this msg is that you can check everything in build OS (besides the ones that say choose only 1) and it will build an OS only rom for you. That's the whole point behind build OS.
You are correct, I was kind of going from memory since I had built the striped down ROM awhile ago.
I just got my Captivate last Friday. Hadn't done anything complicated with it, basically I just used "Unleash the Beast" to root and sideload the thing. Ended up with some sort of weird permissions issue going on with the SuperUser app that had been installed with it, I was getting permission request loops. So I used Odin to reset it. At this point there wasn't anything really wrong, USB worked and the device appeared to the computer. So I just rebooted the Captivate into download mode using adb reboot download and went on.
So later on I grabbed SuperUser 2.3.4(?) or whatever the latest one I found online was, loaded that to do adb pull /system/apps since I realized that Unleash the Beast just deleted everything and I honestly hadn't even seen what it removed yet on the phone itself besides the list on the web site. So after the backup I odin'd again and then grabbed the files from SuperUser 2.3.4 replaced the existing files in Unleash the Beast with it. Actually ended up working perfectly for a while.
I'd used the phone for a few days, no issues, finally got my 16GB SD card from my Raphael and inserted it, had been downloading apps left and right. Well all of a sudden the phone seemed to have it's USB stop working for anything but charging. I recall plugging it into a charger or computer when I first got it and it would ask if I wanted to mount the SD cards for use, then I would just see the battery indicator charging. and I'd toggled developer usb a half billion times trying to get access and fix it.
The computer didn't see it, device manager didn't even flinch(Win7 x64) like it normally does when you plug in and unplug a USB device. Tried it with another computer and same issue. So I rebooted into recovery mode and tried that, the first several times around nothing was detected. Well my finger slipped and ended up hitting the Clear user data and cache option in the recovery mode.
At this point when it boots up, i still dont have usb access, I'm stuck in a force close loop, I can't install apps, can't seem to get it to reboot into download mode via the key commands, and installing apps is impossible since browser and market crash on start.
I've spent the night rebooting and trying to get into download mode for odin, I used to be able to get into recovery mode everytime I tried, eventually I started to see an "uknown device" show up in device manager, which I googled some info from it and all I could tell was it was Microsoft's dummy driver for devices that couldn't be found. Another weird response, it seems to be beginning to hang on the charging battery thing from time to time now.
At this point, its been under a week and I'd trade it in. Except the thing is with enough struggling you can see the apps installed. Most of them were removed but Market Access and Superuser are still in the apps list, and I'm worried about AT&T spotting that, figuring out what I've done and rejecting the claim.
just under half the time now, it boots, the other over-half of the time I get the spinning "battery loading" icon that shows up before the battery thing gets loaded, but not spinning. It pops up, and disappears, from time to time goes to show me my battery status instead of booting, even when not plugged in.
I'd like to think I haven't tried everything? quite obviously i can't run update.zip files from my 16gb sd card since it gets mounted at /sdcard/sd, and I've lost the file browser to move anything around. I've tried rewiping but that doesn't do a thing.
I hadn't gotten to the rom manager stuff yet since I wasn't planning on playing with roms if at all. and at this point that doesn't appear to be an option anymore.
Any suggestions? I was getting to continuing to reboot it till the battery thing comes up 100% of the time then goto ATT and see what they say.
So long that you can get to download mode you SHOULD be good. When you plug in the usb..you need to pull the home dropdown..select usb and tell it to mount. I may be telling you what you already know but download mode is hold both volume buttons from the battery screen...one black screen...att screen...black screen and release pwer but hold buttons. I had problems with this so what I did was unplug the usb...volume buttons...hold power and see att boot screen...(plug in usb)...black screen...att boot...black screen and release power til u see download mode. You can use Odin and set back to stock from there normally.
If the PC is showing unknown device..you are kind of stuck til you fix the driver issue. Maybe remove and reinstall or something not sure on that but that's the first order of business. Go to the dev forum and try reinstalling from there. (One click Odin downloader has teh drivers)
If your phone boots or can get into recovery or download mode you are ok. I ran into the problem where I couldnt even power it on.
Well by now I know that download mode is the holy grail to get things fixed. Recovery mode, I used to be able to get to, but didn't show up. I'm wandering if somehow my USB port got shorted or something.
The drop down option to make it mount is why this all began, it disappeared and never came back.
Trying your steps specifically, first couple times would just end up back at the battery screen. I eventually ended up at recovery mode. Did I end up at recovery mode for releaseing early or late?
I've reinstalled the Captivate drivers a couple times now and tried clearing all past installs of it. Still unknown device. At the moment I have it in recovery mode, so I've rebooted my tower into Ubuntu(Which has the sdk, but never tested with it). Since I've kept reading that Linux doesn't need drivers. Well ./adb start-server and ./adb devices still show nothing...
I can grab a fresh computer that never connected to this thing to try, but I'm kinda doubting it will do this trick at this point. I'll download the odin w/ drivers on it and try that.
hmm.... just ran over to one of the computers here that had absolutely nothing to do with android on it, no drivers, no sdk, no software, nothing.
Went to
[STOCK ROM] Odin3 One-Click Downloader and Drivers(new user=no links)
Downloaded the Windows X64 drivers, installed and rebooted
Plugged the phone in after it rebooted and I'm getting
Unkown Device, I'd pull some info from the Device Manager, but all it is reporting is scewed due to it being a usb device and Windows installed dummy drivers.
All I've got left for testing is my brother's Win7 x32 laptop, granted all I've been able to try with here has been x64 so far. Also on the first computer I was doing all this with. The drivers DID work, they WERE installed and functioning. Previously I could ADB to my hearts desire and I've used odin before. I used the same USB port, used different USB ports, tried different cables.
I had some strange issues on mine. When I would try to go to download mode. All of my USB stuff (KB and mouse) froze up and I had to plug in via PS2. I had the unknown device issue and Not sure how I fixed it. I downloaded and installed the Samsung Kies program and I also downloaded the driver. Ultimatly after banging on it for a bit it worked..not a Unknown device but it was some king of...Gadget Driver or some stuff was messing with me. Try installing Kies and see if that does anything...also make sure you remove the drivers before installing. It acted really squirrly to me too tho. From what you say..it sounds like a borked driver. Im on 32bit XP and took it home to my 64 Vista and got it working whne the 32 was jacking me around.
Just had a chance to try with Kies real quick, I'm not so much thinking i killed my drivers but that somehow the cell phone changed it's id calls. I'm going to give it a shot with kies on a fresh Vista x32 system at work. I still can't seem to get it into downloader mode, but I'm getting more consistent with Recovery and getting the thing to boot back up. If I consider the Battery screens to be your blank screens then I can get it to go recovery or "normal" boot. But still can't seem to get download mode at all.
Up until recently, I didn't get Unkown device showing up even when the system was in "normal" boot. Before, originally it would only show up in device manager in recovery mode, and then it would be the unkown device.
Just out of curiosity could you spare the driver specs for your setup so I can compare? Like Date, Version, and any Hardware IDs? I'm wandering what hardware IDs this thing is giving off since windows wont show me.
Well not sure what suddenly happened. But after enough reboot--attempts, recovery mode is finalyl appearing on my office computer as SAMSUNG Android USB Composite Device. Win Vista x32, only installed Kies and download SDK(speaking of, adb still doesn't see devices). Just finished redownloading odin(wish i'd had a thumbdrive on me when i was at home) and am about to see if I'm going to be lucky by vista somehow.
If you still keep having issues find a way to short the phone out and tell at&t that the phone just got really hot and then turned off. They should replace as a bad unit and get you hooked up with a new one.
Sent from my FroyoEris using XDA App
jonscapri said:
If you still keep having issues find a way to short the phone out and tell at&t that the phone just got really hot and then turned off. They should replace as a bad unit and get you hooked up with a new one.
Sent from my FroyoEris using XDA App
Click to expand...
Click to collapse
Well that thought has occured, that and magnets lol
I think i might have found a clue to the cause. I think it was tied to the whole usb thing. When it appeared to show up at all first time around, i had tapped the menu button while in recovery. And the natural way I'd been holding it applied just a little pressure on the usb cable. Well I got the phone to finally show all the notifaction tab options for debug and storage when i held down the usb plug in the phone down a little bit. I'm guessing that the pins for power are fine but maybe the data pins, or maybe one of the data pins is loose and thus it's an unkown device since it's not responding correctly.
I didn't have time to finish trying to fix it at work, and i'm stuck in class now. I'm'a see if i can get admin access on my terminal here and download everything while the teacher does his orientation. Otherwise i think i can fix it once i'm home now.
=====EDIT=====
Well getting the phone into Download Mode was a bit easier with Ubuntu via ADB since I don't have to wait for Windows to load the driver. Then just rebooted the box into windows for Odin. Long painful story short, I didn't setup Rom manager to be able to undo my changes when the USB port went bad/inconsistent and didn't expect those changes to complicate the recovery without USB. So I'm making sure it's a rather provable issue and going down to ATT with it. 7 Days from receiving the phone, and I'm goin in for an exchange due to bad USB. Funny.
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
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.