My phone is stuck on the vibrant scree and nothing happens........ i am trying to use odin to flash back to stick and it is always stuck on file analysis.....please help!!!!!!!!!!!!!!!
Try this: http://forum.xda-developers.com/showpost.php?p=8445823&postcount=11
Well mine just sits on file analysis for 10 mins and nothing else happens...can someone please help me i have no phone.
Remove the USB from the phone, remove battery.
Place the battery back in your phone and get back into DOWNLOAD MODE
Close Odin
Run Odin as Administrator
Select the 512 PIT FIle
Select the T959UVJFD.tar file for PDA
Plug in your phone (Make sure you see a COM Port come up)
Start Flashing
rolf90 said:
Well mine just sits on file analysis for 10 mins and nothing else happens...can someone please help me i have no phone.
Click to expand...
Click to collapse
as you i had the same problem and finally got it to work by watching this video on you tube:
1.go to you tube
2.search for flash vibrant
3.first video should be "Flashing Firmware with Odin on Samsung Vibrant" by ZDoomentral, its a 3:00 min video
(sorry can't post direct link but i a restricted since i am a new user)
pay close attention as to how he gets his phone into DOWNLOAD MODE, thats where i was going wrong, and just follow the directions of the video.
my phone is up and running with stock kernel and re-rooted it
man i just want to say i just had this same issue happen to be... im a truck driver and having my phone is serious... mainly to play games or what not...but i just got some from Minnesota and tried the odin method and saw that video on you which help give me a visual and its back up ... im very happy... sad to say it was a careless mistake somewhere but i did a back like i always do and it didnt work for some reason...i had a g1 before this vibrant and ive flashed a lots of roms... but anyway i wanna thank everyone one this forum ... i got my phone back
Does this restart the WHOLE THING? because I have information I didn't backup :/
Yes. It deletes EVERYTHING. Just like it's brand out of the box.
I recommend using Titanium Backup and back all your apps. ALWAYS ALWAYS, do a Nandroid backup before flashing ANYTHING.
scootatheschool1990 said:
Does this restart the WHOLE THING? because I have information I didn't backup :/
Click to expand...
Click to collapse
If you have adb up and running & have the ability to get into recovery while you're bricked you can do aN adb pull before flashing
Adb remount
Adb pull /sdcard
After un-bricking you can adb push the folders back
When I did it..it flash back to stock but I have titanium back up so mt phone is back to how I had it ...and I still have every thing else back on, like my movies music etc..
Sent from my SGH-T959 using XDA App
I was trying to help my friend with his Vibrant and now it's stuck at the splash screen in a loop. I can't seem to get it to download mode or recovery or anything. I've pulled the battery, held down both vol keys while pushing power. Any time I connect the usb, it just starts up the boot loop without giving me a chance to do anything else. I can never get to the green charging battery. Any ideas?
I guess I could provide more info... We had rooted the phone multiple times, but Superuser would FC every time. So, we decided to flash eugene's froyo build (http://forum.xda-developers.com/showthread.php?t=740558). That's when I got the boot loop. Odin said it was finished, and it did not go into recovery. It just started boot looping. Maybe I didn't wait long enough before hitting the power? I'm not sure. Anyway. I'm stuck.
EDIT: Unstuck now. I guess I just need to not panic and read more. I held both VOL keys in while connecting to USB and it went into downloading mode. SO, I flash a stock 2.1 ROM and it's back to the way it was. Calling works fine. No data though. Apparently, that was one of the issues before. I'll try rooting again, but it seems like there's another issue. Also... No settings survive reboots. Like turning on USB debugging... Strange.
i was trying to root a phone for someone and after odin completed it said it had failed.
the phone is a telus samsung t959d running froyo.
I followed the instructions from (I would post the url for the link but i am not allowed to.)cyanogenmod's wiki, after it failed I rebooted the phone and it got stuck on the screen in the attached pic. I have tried to boot back into download mode to no avail. From the screen it's stuck on I cannot get any tool to register the device as being present, adb, heimdall, zdiag, etc... I even tried fastboot out of desperation.Before I used odin I tried to get the phone to boot into the bootloader but it only ever went to either recovery or a normal boot and I tried every button press combo I could think of and found and nada.
Even running adb reboot bootloader just made the device boot normally. I think that if I could get it to boot to fastboot usb i could then try fastboot. I am new to rooting devices and have successfully rooted my HTC EVO3D and got s-off and simlock removed for any carrier. So I do know how to follow instructions properly, why flashing the recovery.bin failed I don't know and every fix I seem to find says BOOT TO DOWNLOAD MODE. if I could do that I wouldn't be having this problem lol. Anyway can someone please help me figure this out. Thanks. ANd if you need any further info please let me know. I don't want to have to give my friend my phone due to a software issue.
And YES I did pick PDA not anything else.
machv5 said:
i was trying to root a phone for someone and after odin completed it said it had failed.
the phone is a telus samsung t959d running froyo.
I followed the instructions from (I would post the url for the link but i am not allowed to.)cyanogenmod's wiki, after it failed I rebooted the phone and it got stuck on the screen in the attached pic. I have tried to boot back into download mode to no avail. From the screen it's stuck on I cannot get any tool to register the device as being present, adb, heimdall, zdiag, etc... I even tried fastboot out of desperation.Before I used odin I tried to get the phone to boot into the bootloader but it only ever went to either recovery or a normal boot and I tried every button press combo I could think of and found and nada.
Even running adb reboot bootloader just made the device boot normally. I think that if I could get it to boot to fastboot usb i could then try fastboot. I am new to rooting devices and have successfully rooted my HTC EVO3D and got s-off and simlock removed for any carrier. So I do know how to follow instructions properly, why flashing the recovery.bin failed I don't know and every fix I seem to find says BOOT TO DOWNLOAD MODE. if I could do that I wouldn't be having this problem lol. Anyway can someone please help me figure this out. Thanks. ANd if you need any further info please let me know. I don't want to have to give my friend my phone due to a software issue.
And YES I did pick PDA not anything else.
Click to expand...
Click to collapse
I kept reading other threads and sadly I din't pully the battery first before disconnecting the usb and repartition may have been checked as I see that it does the as default for my version. Also i turned off ODIN as I was hoping a reboot of my computer might help. I will keep trying to find an answer till someone gets back to me. this post may not even show up if I can't do a second post if no one has replied first.
Everyone was a nub at one time wasn't it FUN hahahahahaha sob cry
machv5 said:
I kept reading other threads and sadly I din't pully the battery first before disconnecting the usb and repartition may have been checked as I see that it does the as default for my version. Also i turned off ODIN as I was hoping a reboot of my computer might help. I will keep trying to find an answer till someone gets back to me. this post may not even show up if I can't do a second post if no one has replied first.
Everyone was a nub at one time wasn't it FUN hahahahahaha sob cry
Click to expand...
Click to collapse
I tried a jig and that didn't work. There must be some way of getting the device to give up on completing a task i no longer can give it due to ODIN being shut off.
Why is it that the "how to root/unlocks" never have the "if x fails then do these steps etc..." Had the how to had "pull the battery before disconnecting USB and don't reset or shut off ODIN" I wouldn't be in this mess. I realize that it's user beware but a few important steps like that in case of a fail would go a long way to you guys not shaking your heads. Instead of "silly nub hahahahahaha". No offence but I get that a lot and try to remember that when I teach someone how to use a computer. I am new at phones not at everything.
Further Developments Please can someone help?
I was giving someone a new memory card and they had a Samsung SGH-I896 it has an EB575152VA battery and the one I have the T959D has an EB575152VU battery. I exchanged my battery for hers by accident somehow and when I plugged my phone in it didn't go to the phone triangle computer logo screen it booted to recovery and said it couldn't charge the battery and kept rebooting to recovery. I got my battery back and it booted back to the phone triangle computer logo again. Grrrr....
The other thing I saw while the recovery screen was an error message that said
Code:
E:/data/fota not accessible
(may not be 100% accurate I don't have the battery to check right now but can get it again if need be) anyway I now see that there may be some light at the end of the tunnel. i have the correct stock firmware for the device I tried flashing it while in recovery but the phone kept rebooting before anything got done. My question is how can I get the dang phone to stop asking for Odin and go to recovery so I can flash stock firmware and ROM back to it? As I cannot as far as I know give it what it wants because I reset Odin and nothing seems to see that the phone is connected to the computer. I am going to try the other battery on a full charge to see what that does.
I am new at all this and want to get it fixed. I cannot afford to send it off to a service center and besides that I want to do it myself as I want to become a developer and droid technician. I would gladly donate to anyone but am still trying to get Google to accept my pay-as-you-go credit card and I don't have PayPal either. Which is really frustrating when it comes to giving back. I posted a Q&A on how to without PayPal or CC but as of the last time I checked no one has gotten back to me about it.
The CyanogenMod guide is flat out WRONG. I've tried to change it, but anything I do is reverted in an instant. I also tried to use it to install the ROM only, ended up bricking my phone and it took me hours to unbrick. That's how I became acquainted with XDA.
So, to get this straight:
1. you're using the stock USB cable
2. you remove the battery
3. you hold volume down
4. you plug in the usb cable
5. after a few seconds, you release volume down
6. the screen does not display a yellow triangle with an android
Posted from my Galaxy Tab with CM10
MultipleMonomials said:
The CyanogenMod guide is flat out WRONG. I've tried to change it, but anything I do is reverted in an instant. I also tried to use it to install the ROM only, ended up bricking my phone and it took me hours to unbrick. That's how I became acquainted with XDA.
So, to get this straight:
1. you're using the stock USB cable
2. you remove the battery
3. you hold volume down
4. you plug in the usb cable
5. after a few seconds, you release volume down
6. the screen does not display a yellow triangle with an android
Posted from my Galaxy Tab with CM10
Click to expand...
Click to collapse
That is correct. If you think that my idea below is a bad one or if I downloaded the wrong firmware package please let me know and /or you have a fix that will work? ty
I have though come up with an idea that may work. I am going to charge the "wrong" battery in erm the right phone lol and then use it to trick the device into booting into recovery instead of the cellphone triangle computer (CTC, for want of a better acronym) The I896 battery ends in a V not an ? (sorry can't rem don't have it on me) from the I896 model I think it is, plugging it into USB with the power off sends it to recovery with the "battery cannot be charged " message instead of the CTC screen.
I tried it but the charge in the battery was too low and rebooted. I am hoping that with a full charge (as long as I don't power on the phone first as this will make it go to CTC logo again.
I am hoping that I can install the update.zip that I made by first unzipping the T959UVJFD_firmware.tar I downloaded then unpacked and then repacked into an update.zip as I don't think that it will read the package as a tar file and if it's not called update.zip The recovery is still stock. If I get the phone working I am not going to try unlocking and rooting it again. I will just post two separate adverts one as a carrier locked device and the other one (higher of course to cover buying the unlock from Telus) as carrier unlocked and then I will buy the unlock code if the blah blah you get the drift. sorry for rambling on.
oh and I can't rem if I said this or not, In recovery it "E:/data/fota not accessible" I don't know what that means yet I have been busy with other things and haven't looked it up yet.
Since you can get into at least some version of recovery, your bootloader is intact and you should be able to unbrick it. You ought to be able to get into download mode using a download jig. You can get one on ebay for a few bucks or you can make one yourself. There's a guide floating around here somewhere that lets you make one from a microusb cable.
Posted from my Galaxy Tab with CM10
Hi, I unfortunately don't know a lot about what I am doing here (the root of all my trouble), I'll try to get the info straight:
Motorola Droid Razr (XT910), bought in Dubai, using it in UK, so I didn't receive OTA updates. I decided to try update to ICS using RSD Lite, but the flashing got stuck at system_signed. I gave it a lot of time (hours) before I switched off the phone and tried again, which is when things started going haywire:
During my following attempts, the battery ran low, so I couldn't go on trying (soft brick). I made a patched "factory cable" as per instructions in this forum somewhere, the cable works and powers the phone for flashing.
Now all it does is coming up with the fastboot screen, which reads:
AP Fastboot Flash Mode (S) (Flash Failure)
0A.6C
[...]
Device is LOCKED. Status code: 0
Battery OK
OK to Program
Transfer Mode:
USB Connected
...which suggests to me it would be ok to be flashed, if only I could get it to accept the files. Being a big numpty, I am unfortunately not quite sure what was the exact version that was on there before (big mistake, I know that now), it was 2.3.6 and I suspect it must have been a MEA version, since it was bought there(? - also, when I first switched it on, all was in arabic).
What I have tried so far was:
* using several different fastboot firmware files with RSD Lite 5.7, all of which do not get over the step '1/xx flash cdt.bin "cdt.bin_signed"' - it just hangs supposedly "In process..." forever. I noticed all of these have an "ota" folder (although they vary considerably in size between <1 and 2.5 GB) - maybe all the ones I downloaded are only updates? Is there an actual, base operating system image somewhere?
After many failed attempts, I got desperate and tried files for different regions at random. The ones I tried so far:
SPDREM_U_01.6.5.1-73_SPU-11-M1-2_SIGNEuropeAustraliaEMEA_USASPDRRTGB_HWp2b_Service1FF_fastboot.xml
SPDREM_U_01.6.5.1-73_SPU-11-M1-2-ULB_1C.85P_0A.6B_DATDE_CFC_HWp2b_SIGNED.xml
SPDREM_U_01.6.5.1-167_SPU-15-M2-3_SIGNEuropeAustraliaEMEA_USASPDRRTGB_HWp2b_Service1FF_fastboot
SPDREM_U_01.6.7.2-180_SPU-19-TA-11.6_SIGNEuropeAustraliaEMEA_USASPDRICSRTCEE_HWp2b_Service1FF_fastboot.xml
SPDREM_U_01.6.7.2-180_SPU-19-TA-11.6_SIGNEuropeAustraliaEMEA_USASPDRICSRTGB_HWp2b_Service1FF_fastboot.xml
SPYDERIRD_U.01.26.0_SPD-IRD-21_SIGN_ASIA_RETAIL_HKTW.xml
SPYDERIRD_U.01.26.0_SPD-IRD-21_SIGN_MEA_RETAIL.xml
The only thing I am quite sure about is that it is not LATAM.
* I tried manually flashing the various image files with moto-fastboot, fastboot, and eprj-mfastboot, both the Windows and the Linux versions, with pretty much always the same result: it would flash some files (e.g. ebr, mbr, devtree), but not what I think are the crucial ones: boot, system, also logo.bin. As there are so many possible combinations, I have not tried every file from every firmware I downloaded with every possible program, but as far as I can tell, the results were the same. I did get some error messages about signing (indicating wrong region) sometimes, but most of the time it just hangs forever while supposedly transferring the files.
* I also tried the DroidRAZRUtility, both 1.51 and 1.6, which both invariably fail at the first step of flashing the "allow-mbmloader-flashing-mbm.bin" file on there.
So, I am out of ideas now. Please, someone tell me I have overlooked something obvious. Also, please tell me I haven't bricked the thing for good.
Is there not a way to write something new into it's memory on an even more basic level (I am thinking Linux' dd here), or to read out which region it is currently locked to? I repeat, all I get is the Fastboot screen, I can get into the Fastboot menu, but none of the options gets me anywhere else, (stock) recovery does not work... My last idea is that it might still be a power issue despite the "factory cable", and to try and crack it open and power it at the battery contacts for flashing - but the fact that some flashing works, and the other files don't fail because it goes dead, but because it rejects them, suggests to me it is not a power problem.
Any suggestions appreciated, thanks!
Try flashing SPDREM_U_01.6.7.2-180_SPU-19-TA-11.2_SIGNEuropeAustraliaEMEA_USASPDRICSRTGB_HWp2b_Service1FF_fastboot
with rsd lite.
Those failures are because of two things:
1. You are trying wrong sbf for another region
2 and/or you are trying to flash an older firmware.
Please note that now your only bet is to flash ICS firmware, and try various regions untill you find your right one.
Also if you manually flash use eprj-mfastboot , others fail to flash corectly.
Again for the power issue, when RSD throws an error , look at the phone, if it says "Low battery, cannot program" then the factory cable is bad, if not there is no power problem.
Don't worry your phone is not dead, you only need to find the correct sbf file, try more variants with rsd lite, it must work.
Mine had problems flashing correct sbf's, it was my system. Even with correct drivers and lastest RSD it would not work, nor with my other laptop, but working fine on my old xp install on a macbook. I could however install stuff individually using fastboot flash command. Sorry that I dont have a solution but I just wanted to let you know that sometimes it can be your computer/os install.
still trying
@Killer2k8: Thanks for the encouragement, I will try with the file you suggested with eprj-mfastboot.
As per power: I seem to have tried so many times that the battery is way deeply uncharged (I hope it isn't permanently damaged once I get the phone to charge at all again), so anyway, I crack'd'er open and tried powering directly at the battery contacts (battery disconnected, of course). As you would guess from what you wrote, that did not make any difference to my problems... But also, it proves my factory cable is good, as I can even flash the few files that work if no power is connected at the battery contacts, powering through the cable only. Some files will transfer correctly, and when it says "writing", the phone will just reboot, causing an error - that's why I thought of power issue, e.g. the actual flashing process requiring more power than just the transfer... Anyway, that issue did not go away even with direct power. - Will see what happens once I find the right files for me...
I'm good with flashing ICS, that's what I wanted to do in the first place. And thanks for the encouragement!
@drolgnir: Thanks, I had the same idea, as initially I had tried everything from Win7 running in VirtualBox (at first, I only found all the tools for Win, should've really researched better before starting this), I thought maybe it doesn't have the proper low-level access to the USB ports. Anyway, since trouble hit me, I tried also on three different Linux machines (2 different dirtros), and also again on the virtual Win, and on many, many different USB ports on these (just in case it was a USB power issue), all to no avail. I guess Killer2k8's suggestion sounds most promising at the moment... Cheers anyway.
no luck - situation deteriorating..?
Sorry for the many posts, I hope someone is still reading this...
So, I tried the file you suggested. I flashed manually, not RSD, with "fastboot" from eternity project, which is the Linux equivalent to "eprj-mfastboot.exe", as far as I can tell (download from the same post as the Win version).
I could flash cdt.bin, ebr, mbr. Note that these are all just 16kB.
When trying logo.bin, it sent it ok, but during 'writing logo.bin...', the phone just switched off. After restart, same again. Same also with boot_signed.
Since then, things got worse: whenever I try to switch on now, it flashes ~1/4 of the red "M" logo, then flashes the AP fastboot screen, and repeats that a few times before staying off (sometimes not, just switches off right away). I can still get into the Boot Mode Selection menu by holding all three buttons, but selecting AP fastboot there has the same effect. Starting with power&Vol- button shows the fastboot screen immediately, but again only for a flash...
The only thing that will stay on is the SBF Flash screen, but I don't know what to do with that..?
So, I still smell a power problem, but neither applying external power, nor using the factory cable alone made a difference. The cable is ok, I re-checked. The fact that the SBF Flash screen stays on suggests that it is not a stuck power button (someone had that problem, apparently), am I right?
So, any suggestions from here? Thanks..
Although this doesn't help, I have pretty much the exact same issue. However, I do know what/where my phone is from, it requires the central Europe update. But apart from that the issues are identical; it only boots into the flash failed fastboot menu, and any RSD attempts have failed at cdt.bin, while using the fastboot tool does not work either as I get preinfovalidation flash errors. The utilities don't work either.
Now, as you did, I also tried quite a few different versions of the firmware, and none of them worked. So what I was wondering is, is there a way for us to find out exactly what version the phone 'thinks' it is on, so we can find the same/a newer version of the firmware to update it to? Because I am quite certain I am using the files from the right region, so it must be the version that is too old.
update: still struggling, but giant leap further! Please read my tale...
...just in case anyone might find this useful, I'd like to give an update on my "patient":
I actually managed to flash ICS on there! Kind of.. What I did, was:
With the battery unplugged, I supplied external power to the phone, additional to the factory cable. The issue was that it would often flash small files, but for larger files would successfully "send" them, but in the "writing" phase the phone would just switch off. So, I supplied carefully monitored 3.7V to the contacts, which seemed to make a difference, but in the "writing" phase, Voltage dropped to below 3V where it would again switch off. Ok, you can charge a LiIon battery with max. 4.2V, and you should normally charge the battery before flashing, so I tried again while providing 4.2V. And - Success!! Voltage would drop to ~4V during "writing", but it stayed on, and allowed me to further test which Firmware the device would actually accept.
I do not believe that applying 5V from an USB cable directly to the (plugged-in) battery contacts, as mentioned in the forums somewhere, is very healthy for the battery. I reconnected the battery and tried charging it directly from the contacts, but I made sure the Voltage would always stay below 4.2V. Occasionally in my exploits, the charging circuitry would actually spring into action (confirmed by a drop and fluctuations in Voltage, and the faintest of noises from the phone itself), and I used that of course to squeeze some life back in, but most of the time it would not charge at all. I can not say what combination of flashing attempts, rebooting, un- and replugging the cable, switching and changing the charging current,... actually triggered the charging process occasionally, sorry. I could not reliably reproduce it.
In the process, I also tried the DroidRazrUtility 1.8, which interestingly flashed the AP fastboot to v 0A.74, but of course failed further on...
With the new AP fastboot, I thought maybe something more might now work, and at last I found it would now miraculously accept:
SPDREM_U_01.6.7.2-180_SPU-19-TA-11.6_SIGNEuropeAustraliaEMEA_USASPDRICSRTGB_HWp2b_Service1FF_fastboot.xml and
SPDREM_U_01.6.7.2-180_SPU-19-TA-11.6_SIGNEuropeAustraliaEMEA_USASPDRICSRTCEE_HWp2b_Service1FF_fastboot.xml
Fantastic!
First thing, before any actual booting, was to try if I could finally charge my battery again, and at last - yes!
At about 70%, I got adventurous, and unplugged the charger to put it in another power outlet. This made the phone actually boot up, but I thought that's not too bad now... But:
Now I have the following issue: After being freshly flashed (I tried several times now), it will charge as long as I don't actually switch it on, ONCE, but when it boots, after asking the setup questions and a little while on, it will switch off on its own, and then it's stuck in some variation of the bootloop (M dual core logo, pulsing M forever, OR rebooting ever and ever again at the pulsing M, OR just stuck at the M dual core). At least I now have a recovery menu. Erasing cache and data DON'T solve the issue (as proposed many times in the forums). I read a hint that it might be a kernel issue, or that it might be caused by a wrong radio.img (CDMA on a GSM phone). I checked and tested the latter by deactivating the radio in the extended settings, but it would still switch off after a short while (and it had defaulted to GSM, as it should).
So...am I stuck to wait for some new Firmware to come out, that might fix the issue? Or what should I try? Thanks in advance...
Resolved!
Long read, but I finally managed to do it. Basically, I am not 100% sure what happened, but I have a hunch:
After I thought I had solved the power issues by at least being able to charge the battery once after each re-flashing, I tried to fix the issue about the phone randomly switching off (and on - it wouldn't stay off!). I read that it might have to do with flashing failures (no error message??), or incorrect kernel or radio images...
Not long, and I ran into familiar problems again: It would flash the smaller files, but not system and cdrom; it would successfully "send" the files, but never stop "writing" them (I waited for somewhere between 10 min and an hour at each attempt), only way to stop the process was to switch off the phone, which certainly is not healthy during flashing...
...so battery started to go down again and I started to more and more clearly face a power issue again (I had disconnected the external power and didn't want to risk that McGyver approach again). As it happened, I also 'got some new USB 3.0 external hard drives at this time. I found that one would readily power up on all my USB ports, the other one could not get enough power even from some supposed 3.0 ports..
...which made me try flashing the very same firmware I was just trying (with the factory cable, of course), all the smaller files of which worked on the one computer but not the large ones (indicating I had the right firmware, at least):
SPDREM_U_01.6.7.2-180_SPU-19-TA-11.6_SIGNEuropeAustraliaEMEA_USASPDRICSRTGB_HWp2b_ Service1FF_fastboot.xml
, on another computer, on the one USB 3.0 port that had proven to supply the most power - and taa-daa! It wrote it, very quickly, without complaining!
And it booted alright (after charging it first, just in case). And it stayed on (and off, when I eventually rebooted it). I am running that ever since, and it seems ok...
Originally, I had aimed for:
SPDREM_U_01.6.7.2-180_SPU-19-TA-11.6_SIGNEuropeAustraliaEMEA_USASPDRICSRTCEE_HWp2b _Service1FF_fastboot.xml
, but I think the differences are minimal and I don't want to risk anything going wrong again, right now.
In conclusion, to me the main issues were
- finding the right firmware, stupidly not having paid attention to the original version number, and
- all sorts of different power issues!
The factory cable did not solve all of my problems.
Recharging the battery (eventually) did not solve my problems.
ADDITIONALLY, it needs to be flashed from a USB port supplying sufficient power!
This might point into the direction drolgnir suggested, but for me, it was not an OS/driver problem, but definitely power (same, fresh install of Fedora Linux on the two machines that did, and didn't work, one of them alternatively running Win 8; the Linux Mint computer I also tried doesn't have USB 3.0, the USB 2.0 ports - including an externally powered USB hub - did not work). @drolgnir: maybe it was power for you too, but you didn't notice because it was a different OS too?
...I hope this overly detailed report might help someone else too...
I have little hope for this, but thought I'd post it up anyway before buying a new phone. I have been using the JellyBomb ROM for about two weeks now, and until today it was working fine. Then (seemingly) randomly, while I was browsing a webpage in Firefox, the phone locked up.
"Okay, I'll just force a hard reboot." So I held down the power button and it turned off. When I turned it back on, it got stuck at the HTC screen (I let it sit for about 15 minutes). So I did another hard reboot and booted into bootloader (power + vol down), which came up fine. I went into recovery (TWRP 2.3), which took about 5-10 minutes to move past the TEAMWIN splash screen into the menu.
Once in the menu, I went to reflash the ROM, but no files showed up in either the internal or external storage which I found strange. I then went to reboot from the menu, at which point TWRP informed me that I had no OS installed. At that point, TWRP froze up, so I did a hard power off again and tried to boot it back into recovery but nothing happened. The soft buttons didn't even flash like usual.
Once I had access to my computer, I plugged it in, hoping that something would change with it connected to a PC. At that point, the Windows driver manager reported failure at installing a driver. I checked device manager to see that I had a QHUSB-DLOAD device connected. After some Googling, I attempted Unlimited.IO's fix tool (using a Linux live CD, obviously). I had little hope, however, because my device was S-ON. And sure enough, although the tool reported completion there was no change to the phone.
So, now that that long-winded (and hopefully sufficiently detailed) story is complete, does anyone have any suggestions/advice/instructions for me?
Thanks!
elead1 said:
I have little hope for this, but thought I'd post it up anyway before buying a new phone. I have been using the JellyBomb ROM for about two weeks now, and until today it was working fine. Then (seemingly) randomly, while I was browsing a webpage in Firefox, the phone locked up.
"Okay, I'll just force a hard reboot." So I held down the power button and it turned off. When I turned it back on, it got stuck at the HTC screen (I let it sit for about 15 minutes). So I did another hard reboot and booted into bootloader (power + vol down), which came up fine. I went into recovery (TWRP 2.3), which took about 5-10 minutes to move past the TEAMWIN splash screen into the menu.
Once in the menu, I went to reflash the ROM, but no files showed up in either the internal or external storage which I found strange. I then went to reboot from the menu, at which point TWRP informed me that I had no OS installed. At that point, TWRP froze up, so I did a hard power off again and tried to boot it back into recovery but nothing happened. The soft buttons didn't even flash like usual.
Once I had access to my computer, I plugged it in, hoping that something would change with it connected to a PC. At that point, the Windows driver manager reported failure at installing a driver. I checked device manager to see that I had a QHUSB-DLOAD device connected. After some Googling, I attempted Unlimited.IO's fix tool (using a Linux live CD, obviously). I had little hope, however, because my device was S-ON. And sure enough, although the tool reported completion there was no change to the phone.
So, now that that long-winded (and hopefully sufficiently detailed) story is complete, does anyone have any suggestions/advice/instructions for me?
Thanks!
Click to expand...
Click to collapse
Hey elead got your pm and I'm sorry this has occurred to you. I'm not familiar with the unlimited IO. But I will suggest that you allow your phone to charge tonight while its off... The reason for this is I believe the battery has fallen to a level such that will not allow the boot process to work... Having said that allow it to charge the night... Then see if it will boot into bootloader in the morning. If it does this you should be able to flash an ruu. I realize this is a stressful time, I've been in your shoes before and actually bricked. BUT, I believe your phone is salvalgeable and with a proper charge you be able to fix the issue... Please report back in the morning and let me know... Ok??
VeNuM said:
Hey elead got your pm and I'm sorry this has occurred to you. I'm not familiar with the unlimited IO. But I will suggest that you allow your phone to charge tonight while its off... The reason for this is I believe the battery has fallen to a level such that will not allow the boot process to work... Having said that allow it to charge the night... Then see if it will boot into bootloader in the morning. If it does this you should be able to flash an ruu. I realize this is a stressful time, I've been in your shoes before and actually bricked. BUT, I believe your phone is salvalgeable and with a proper charge you be able to fix the issue... Please report back in the morning and let me know... Ok??
Click to expand...
Click to collapse
I will post back with results. Not like I've got much else to do with it right now, eh? :laugh:
No change. I'm thinking maybe I'll take it to the Sprint store and play dumb to see if they'll just give me a new one (it's worked before!).
elead1 said:
No change. I'm thinking maybe I'll take it to the Sprint store and play dumb to see if they'll just give me a new one (it's worked before!).
Click to expand...
Click to collapse
Damn. Well I've been there done that too...
send it to htc.
elead1 said:
No change. I'm thinking maybe I'll take it to the Sprint store and play dumb to see if they'll just give me a new one (it's worked before!).
Click to expand...
Click to collapse
i had the same problem but my situation was that i downgraded the radio while s-on. I was in the same situation that you are right now. i did everything i could but nothing worked so my last hope was sending it to HTC and say that i lefted updating the software while sleeping and when i woke up it was like that. i sended they didnt even ask, i got it back like new . :laugh:
Hey guys, I'm really hoping someone can tell me of a solution Ive not though of.... So Ive got the note 3 from sprint. currently had 4.4.4. I shoulda just left wellenough alone, I realize, But I tried to flash just a modem via mobileOdin and upon reboot, it will say "recoverybooting" and then I get the blue android. Thats all. This was just over 6 hours ago I did this and Im dead in the water, Ive SEARCHED the internet high and low and there are other facing similar problems, but it seems like every mishap Ive read about EVENTUALLY gets fixed. This just will not do anthing with any button combo as far as recovery and/or download mode. I cant access download mode either. recovery never actually boots, just a forever frozen blue android.. Now, with the phone attached via usb to my PC, it DOES see it as COM7, BUT REGARDLESS what ive tried it just remains at the "recovery booting" spot then blue android until I pull the battery again. Please HELP.! IF ANYONE HAS ANY SUGGESTIONS I would be just delighted if you may have some other approaches to this matter. THANKS! Please let me know iTs DESPERATE!
Zscott87 said:
Hey guys, I'm really hoping someone can tell me of a solution Ive not though of.... So Ive got the note 3 from sprint. currently had 4.4.4. I shoulda just left wellenough alone, I realize, But I tried to flash just a modem via mobileOdin and upon reboot, it will say "recoverybooting" and then I get the blue android. Thats all. This was just over 6 hours ago I did this and Im dead in the water, Ive SEARCHED the internet high and low and there are other facing similar problems, but it seems like every mishap Ive read about EVENTUALLY gets fixed. This just will not do anthing with any button combo as far as recovery and/or download mode. I cant access download mode either. recovery never actually boots, just a forever frozen blue android.. Now, with the phone attached via usb to my PC, it DOES see it as COM7, BUT REGARDLESS what ive tried it just remains at the "recovery booting" spot then blue android until I pull the battery again. Please HELP.! IF ANYONE HAS ANY SUGGESTIONS I would be just delighted if you may have some other approaches to this matter. THANKS! Please let me know iTs DESPERATE![/QUOTE
Have you tried removing the battery for a couple of minutes ? If you have read a couple of my threads on NH7 4.4.4, once your there downgrading anything is risky. Here is a link to read http://forum.xda-developers.com/note-3-sprint/help/4-4-4-download-mode-t2877528 . Here is a link for a recovery from a hard brick, by creating a boot image and then copy and paste it on a sdcard http://www.rom-central.com/showthread.php?87-GUIDE-HOWTO-Recover-from-a-HARD-BRICK-N900V-NC2-NC4 there are several sites on this type of fix, I just can't remember where they are. However, I do have something that may help, on one of those sites there was a link for someone who has already created a SM-N900P Unbrick img for Sprint and I downloaded it just in case. Here is the link http://www.mediafire.com/download/l6q1152x5c9d4h6/N900PUnbrick my copy. From what I understand you need to format/erase your sd card then copy and paste the unbrick img to the sd card from a PC. Pull the battery and install the sdcard back in the device, then try and boot the phone into download mode. Here is another link http://forum.xda-developers.com/showthread.php?t=2439367 I have not had to do this so you will have to do a little reading to be sure.
Click to expand...
Click to collapse
The fact that it still shows up as COM is a good sign.
Get a hold of ODIN 3.07+ I had issues with ODIN 3.06.
Here are a few things to try:
1.Take the battery out and hold all the buttons that you normally would to boot into recovery. While holding all the buttons, plug in the usb cable. If it boots into download mode, awesome, just put the battery in before you flash.
2. .Take the battery out and hold all the buttons that you normally would to boot into recovery. While holding all the buttons, plug in the battery. Hopefully it will boot into download mode.
3. try different cables, remember regular micro usb cables work with the note 3.
Make sure you put the modem file in the phone slot, and the rom/system tar in the pda slot.
Best of luck
Thanks for the suggestions guys! Iguess time is just what it needed. I actually fell asleep after trying for so long, and when I woke up I decided to try once more and VOILA... It let me into download mode! Went back to stock and have since been rebuilding . ha! Thanks again