Develop Bugs

Help please:(

Have done several rom flashes on unrooted Desire in past and justwent to put another one on but cannot open the windows.bat file when the red exclamation mark is on the phone. I have always gone through it swimmmingly but this time round, nothing is happening. I can get the bootloader screen but not really much else. I have tried the cable in a different usb port in case it may have been that but still no joy. I notice when it does the very initial boot thing, it says wrong image. I have also tried booting the phone normally but it gets to the loading screen then goes blank and if I press the wake button it still shows the boot screen.
Any ideas?? I think the phone is ok, looks like a software problem and I havent the foggiest how to get round this

Have you updated via ota or .exe to 2.2?
Sent from my HTC Desire using Tapatalk

I tried to install the new 2.2 that was released today but there was a script issue so reverted to Pirate Rum rom 2.2 as I was using it before but this time around it hangs on the screen. I havent done anything different to before. I put the new radio .20 on earlier and it worked fine with the Pirate rom. Normally my pc makes a sound when it is connected and it is not doing it now. Im really stuck.

Resolved - Thank you.

Another "Stuck on the Samsung Boot Screen" Post

Hey Everyone,
I have searched the intererd and here as well and have not found any advice that has helped hence this post.
Recently my wife's epic 4g was on ACS ICS v 5.5 with the samari kernel it comes with. It started acting strange by locking in landscape mode. I rebooted it only to not be able to get into recovery or the ROM itself.
I initially was unable to get odin to recognize the phone in download mode due to usb oxidation corrosion. I took apart the phone since I saw greenish oxidation on the usb port. I used 91% rubbing alcohol to clean the motherboard of corrosion and cleaned the contacts. I opened Odin and put the phone into download mode without a SD Card or battery in.
Odin finally recognized the phone and I clicked all three buttons (Partition, reboot and F Reset). I selected the correct PIT file and selected the SPH-D700-EL30-8Gb-REL.tar.md5 file.
ODIN worked and my phone reboots after flashing. I unplug from the PC and put in the battery and press the on button. The phone the proceeds to show the SAMSUNG screen but does not progress past this screen. It restarts itself to the same screen and repeats this forever. I have tried various batteries ( ihave stock and extended) and cables with no avail. I have even tried Stock EC05 tar files. Nothing works.
Does any one have any other insight that I am missing?
Thanks in advance.

Sounds like A bad download. Download the EL30 tar fresh and try again.
Sent from my SAMSUNG-SGH-I717 using xda premium

Exactly what kenny said. Just this time have reboot and repartition checked "only"
Sent from my SPH-D700 using xda premium

Thanks guys. I tried your suggestions to no avail. I think one of the usb contacts aren't 100% so its enough to fool Odin into thinking its right to the NAND ok when it is in fact not.
The misses is going to sprint today to see what the can do. Oh well. Thanks for the replies.....always appreciated.

Green Andy said:
Thanks guys. I tried your suggestions to no avail. I think one of the usb contacts aren't 100% so its enough to fool Odin into thinking its right to the NAND ok when it is in fact not.
The misses is going to sprint today to see what the can do. Oh well. Thanks for the replies.....always appreciated.
Click to expand...
Click to collapse
whatever you do, don't tell them it's rooted. deny to them any knowledge of root

[Q] Strange things followed by brick galaxy nexus.

Phone is Verizon Galaxy Nexus, running the vicious jellybean build that first came out (yeah I was too lazy to install a new ROM when the first Jellybean build I got my hands on worked fine)
Alright so here's the sequence of events,
Last night - phone working just fine
When I went to look at my phone and set an alarm for when I went to sleep I noticed it was powered off. So I tried to power it on and it hanged at the Google logo. It did this for about 20 minutes, and then I pulled the battery and tried again. This time I left it at the Google logo bootscreen over night (plugged in). Note: I'm not sure if it was bootlooping or hanging at this point, I don't remember it vibrating)
I'm awaken in the morning by the sound of my phone vibrating every 10 seconds. I look at my phone and it's at the unlock screen but the only things I can do are emergency call and, strangely, it asks me to enter a password to decrypt my phone. I never encrypted it. I started freaking out, at this point I probably should of started Googling for a default password or something, but in my morning stupor I rebooted the phone and it just bootlooped on me.
I got into CWM recovery, looked for a NANDROID backup but it kept telling me sdcard wasn't mounted, and attempting to mount it failed. I'm not seriously scared.
Reboot back in to CWM recovery to see if anything changes. Nope.
I Google this problem and land on this page. (I guess I can't post links, but it tells me I just have to reflash CWM) I think, "oh, I just have to reflash CWM. Not too hard!
I downloaded the GN toolkit and update to the latest CWM touch.
Attempted to reboot phone - nothing happens. All buttons unresponsive, no battery shows up when trying to charge. My laptop doesn't find it.
More Googling. I land on this page (link removed - GSM forums for legija's .bat unbrick fix thing), so I try plugging in my phone to my laptop without the battery, sure enough I see the OMAP 4460 device attempting to install. I follow the instructions and install the OMAP drivers, but when I plug in my phone it acts as if its being unplugged and replugged back in constantly. It won't stay connected for more than 3 or 4 seconds without reconnecting, so any attempts to try and use the .bat file fail
And so that's where I am. I have my phone plugged in right now incase for some reason it isn't charged, but I'm stuck. I hope I gave enough information for anyone to help me, thanks!

Sleete said:
[*]More Googling. I land on this page (link removed - GSM forums for legija's .bat unbrick fix thing), so I try plugging in my phone to my laptop without the battery, sure enough I see the OMAP 4460 device attempting to install. I follow the instructions and install the OMAP drivers, but when I plug in my phone it acts as if its being unplugged and replugged back in constantly. It won't stay connected for more than 3 or 4 seconds without reconnecting, so any attempts to try and use the .bat file fail[/list]
And so that's where I am. I have my phone plugged in right now incase for some reason it isn't charged, but I'm stuck. I hope I gave enough information for anyone to help me, thanks!
Click to expand...
Click to collapse
some also have had this issue "It won't stay connected for more than 3 or 4 seconds without reconnecting, so any attempts to try and use the .bat file fail"
but no, they've managed to do it in the end, it's just that you have to be ultra-quick
can you still get in fastboot/bootloader? if yes, flash latest twrp (i'm sure it supports encryption); if after flashing twrp it still doesn't work, flash google stock images by following the procedure here

Thought I should update this in case anyone else manages to hard-brick their phone, but I sent it in to Samsung and they replaced the entire mobo under warranty. I think they either didn't care or it was bricked enough where they couldn't tell I rooted it. Also good side effect of fixing the finicky USB port on my phone. Happy ending!

...

I was on the FK23 rom for a while, and everything was working perfectly. However, last night, I ran a white noise machine app from my phone while it was on the charger all night.
When I went to unlock the phone this morning, it wouldn't unlock, so I pulled the battery, and it started to bootloop. It would do the Galaxy SII screen, then the Sprint bootup, then it would play the Sprint boot down animation. Over and over.
So I tried flashing FL16 with ODIN, and when I do that, it gets stuck on hidden.img and doesn't do anything. Then I tried flashing EL29 with ODIN, and it gets stuck on recovery.bin and doesn't do anything. I have used multiple PCs and multiple cables. WHAT AM I DOING WRONG?! I just want my phone to work T_T

anchor_th said:
I was on the FK23 rom for a while, and everything was working perfectly. However, last night, I ran a white noise machine app from my phone while it was on the charger all night.
When I went to unlock the phone this morning, it wouldn't unlock, so I pulled the battery, and it started to bootloop. It would do the Galaxy SII screen, then the Sprint bootup, then it would play the Sprint boot down animation. Over and over.
So I tried flashing FL16 with ODIN, and when I do that, it gets stuck on hidden.img and doesn't do anything. Then I tried flashing EL29 with ODIN, and it gets stuck on recovery.bin and doesn't do anything. I have used multiple PCs and multiple cables. WHAT AM I DOING WRONG?! I just want my phone to work T_T
Click to expand...
Click to collapse
Do a factory restore and wipe then odin one click stock EL29 and start from scratch.

I can't do a factory restore. When I hold Vol up + power, it says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"

:edited: Didn't see your response to graydiggy
Redownload a complete one click, verify md5 and try putting the phone in download mode and attempting again. It's possible that your download was bad.

so is there nothing I can do?

By technicality, that is not a brick. You should be able to flash from that message. That was the case with the Samsung Captivate.

I downloaded EL29 and verified it again. It is doing the same thing. stuck on recovery.bin
I also tried flashing from that message just now. Same thing. ODIN gets stuck on recovery.bin
thanks for the help but I think it's ****ed. something might have messed up in the filesystem and that's why ODIN gets stuck maybe.

anchor_th said:
I downloaded EL29 and verified it again. It is doing the same thing. stuck on recovery.bin
I also tried flashing from that message just now. Same thing. ODIN gets stuck on recovery.bin
Click to expand...
Click to collapse
Ok, so I found a solution by sfhub that worked for someone from a while ago. Try using pc odin to flash each piece seperately. Modem, kernel, then rom..
Here's my ref:
See post #9 http://forum.xda-developers.com/showthread.php?t=1492771

I'll see if this works. Hopefully it does, I'm ready to toss the thing out of a window, haha
edit: noob question, how do I flash the .md5 files? I downloaded odin multi downloader but the phone doesn't show up in it.
edit 2: okay nevermind I figured it out, it seems to be flashing
edit 3: so modem flashed just fine and the phone rebooted but when I try kernel it loads the green bar all the way on odin then it freezes...
edit 4: so I think my phone's flash memory might be screwed somehow. I've been reading other threads and someone had a similar problem as me and couldn't fix it.

anchor_th said:
I'll see if this works. Hopefully it does, I'm ready to toss the thing out of a window, haha
edit: noob question, how do I flash the .md5 files? I downloaded odin multi downloader but the phone doesn't show up in it.
edit 2: okay nevermind I figured it out, it seems to be flashing
edit 3: so modem flashed just fine and the phone rebooted but when I try kernel it loads the green bar all the way on odin then it freezes...
edit 4: so I think my phone's flash memory might be screwed somehow. I've been reading other threads and someone had a similar problem as me and couldn't fix it.
Click to expand...
Click to collapse
Have you flashed all three pieces before trying to let the phone boot completely? Once you flash the first piece and it restarts, Just hold power+vol down and get back into download. Do that until you have all three segments flashed. Then try letting it boot.

I flashed the modem, it worked, then I rebooted back into download. Then I tried flashing kernel and the bar on ODIN filled up but then it froze and did nothing. I let it sit for about 10 minutes and it still did nothing. so I tried skipping that and flashing the rom and the bar on ODIN moved barely then froze. Like I said, I think my phone's flash memory got messed up somehow. :\

anchor_th said:
I flashed the modem, it worked, then I rebooted back into download. Then I tried flashing kernel and the bar on ODIN filled up but then it froze and did nothing. I let it sit for about 10 minutes and it still did nothing. so I tried skipping that and flashing the rom and the bar on ODIN moved barely then froze. Like I said, I think my phone's flash memory got messed up somehow. :\
Click to expand...
Click to collapse
Then there may be one more thread that might help if that's the case.
Kernel is only the zimage file. Hang on, let me find it.
:edit: Maybe this will help you. If not, maybe graydiggy or someone else has some ideas.
With this, you'll have to see if you can't flash a custom recovery. From the sound of it, it may not be helpful at all.
http://forum.xda-developers.com/showthread.php?t=1865102
Sent from my SPH-D710 using Xparent ICS Tapatalk 2

Yeah, I don't think there's a way to do that since I can't access ADB...

anchor_th said:
Yeah, I don't think there's a way to do that since I can't access ADB...
Click to expand...
Click to collapse
http://mobiletechvideos.mybigcommerce.com/samsung-epic-4g-touch-jtag-brick-repair/

I'll try that as a last resort. I'm going to a Sprint store tomorrow and I'll see what they tell me. I just might use all this as an excuse to finally get a Note II.

anchor_th said:
I'll try that as a last resort. I'm going to a Sprint store tomorrow and I'll see what they tell me. I just might use all this as an excuse to finally get a Note II.
Click to expand...
Click to collapse
They will probably know you borked it by trying to flash. If they can get to a recovery to see if you have flashed anything, you are screwed.
Do you by chance have a USB Download Mode JIG?

No, I don't. My download count in download mode is at 1, too.... so they probably won't fix it... but I might get lucky. Who knows.
edit: the messed up thing is I don't really know what messed it up. it worked fine for about a month on FK23, then boom, this morning it won't unlock and bootloops when I pull battery. before I tried flashing it, it wouldn't even go into recovery. when I held vol up + power, it just went to the Samsung screen and rebooted over and over

anchor_th said:
No, I don't. My download count in download mode is at 1, too.... so they probably won't fix it... but I might get lucky. Who knows.
edit: the messed up thing is I don't really know what messed it up. it worked fine for about a month on FK23, then boom, this morning it won't unlock and bootloops when I pull battery. before I tried flashing it, it wouldn't even go into recovery. when I held vol up + power, it just went to the Samsung screen and rebooted over and over
Click to expand...
Click to collapse
I have a theory... Give it a couple hours of plug in time without turning it on or trying to flash. Just give it like 3 hours and see if you can flash from there. You may have a battery that is low and it could be resulting in your problem of not being able to flash.

the battery was also on the charger all night... but I'll plug it in. is it charging even though it is on the connect to kies screen?

anchor_th said:
the battery was also on the charger all night... but I'll plug it in. is it charging even though it is on the connect to kies screen?
Click to expand...
Click to collapse
Just keep it completely powered off and use the normal wall charger.

Note 4 either won't start, or has random reboots that make it no longer start

Have had this problem for about two weeks now. Every time I get the phone able to boot (either by reflashing a rom or odin) it will work for a few hours then it'll freeze in the middle of use or idle and restart. After restarting a few times the phone will no longer boot and I have to reflash it with odin or TWRP. It's happened so much though that as of today even if I get it to start it'll end up freezing up shortly after booting, get stuck on the black start screen and hang there until I pull the battery. At that point the phone will only boot into download or recovery. I'm at the end of what I can do and out of ideas.
So far I have tried
Odin to:
N910PVPS4COK1_N910PSPT4COK1_N910PVPS4COK1_HOME.tar.md5
N910PVPU4DPH4_N910PSPT4DPH4_N910PVPU4DPH4_HOME.tar.md5
and flashing multiple different roms to try to fix it.
Sometimes it won't even mount data, cache, system, etc within twrp.
I've also tried to format each individual partition when it wouldn't start no matter what and that did make it so it was able to start but the same problems were there after it did start.
I've searched and I cannot find a solution to anything similar to the problem I'm having. If anyone has any ideas they'd be greatly appreciated.

justintworley said:
Have had this problem for about two weeks now. Every time I get the phone able to boot (either by reflashing a rom or odin) it will work for a few hours then it'll freeze in the middle of use or idle and restart. After restarting a few times the phone will no longer boot and I have to reflash it with odin or TWRP. It's happened so much though that as of today even if I get it to start it'll end up freezing up shortly after booting, get stuck on the black start screen and hang there until I pull the battery. At that point the phone will only boot into download or recovery. I'm at the end of what I can do and out of ideas.
So far I have tried
Odin to:
N910PVPS4COK1_N910PSPT4COK1_N910PVPS4COK1_HOME.tar.md5
N910PVPU4DPH4_N910PSPT4DPH4_N910PVPU4DPH4_HOME.tar.md5
and flashing multiple different roms to try to fix it.
Sometimes it won't even mount data, cache, system, etc within twrp.
I've also tried to format each individual partition when it wouldn't start no matter what and that did make it so it was able to start but the same problems were there after it did start.
I've searched and I cannot find a solution to anything similar to the problem I'm having. If anyone has any ideas they'd be greatly appreciated.
Click to expand...
Click to collapse
Try falsh repair firmware with pit file in odin.
Do factory reset immediately from recovery after flash firmware to get clean OS.
You can download repair firmware from here
https://www.androidfilehost.com/?fid=24591020540821805
Extract firmware you will get pit file inside of it.

Trex888 said:
Try falsh repair firmware with pit file in odin.
Do factory reset immediately from recovery after flash firmware to get clean OS.
You can download repair firmware from here
https://www.androidfilehost.com/?fid=24591020540821805
Extract firmware you will get pit file inside of it.
Click to expand...
Click to collapse
I used both of them for a restore and did a factory reset and things looked good for about 30 minutes and now its back to the random freezes that turn into a restart

justintworley said:
I used both of them for a restore and did a factory reset and things looked good for about 30 minutes and now its back to the random freezes that turn into a restart
Click to expand...
Click to collapse
I suppose this is a long shot, but are you running on the original or an old battery? It's possible that a bad battery is causing the reboots. I was back and forth to the Sprint store about 4 times in one week. They first tried flashing the firmware. (Yeah, I could have done it, but I have insurance.) They sent me home and on the way my phone rebooted itself. I got a replacement Note 4, but it started getting hot, then also rebooting. They "let" me upgrade to a Note7, which I loved. I had to give it back even though it was from the new, supposedly safe batch. At this point, I couldn't even get the Note 4 to boot at all. Boot loops, or would boot into download mode. Couldn't do anything with it, except pull the battery. Got a third Note 4, but also ordered a new battery pack from Sprint. They were and still are, only $24.95, with free shipping! You get a new battery, an external charging unit and a carrying case for the battery. (You have to use your own charger.) This finally fixed the problem. I had two batteries when I ordered the new one. I'm pretty sure one of the older batteries was defective, even though it wasn't bulging. I'm still using the other one that's also older, even though it is bulging a bit. It charges and runs fine. No over-heating. So, my problem was a combination of a defective battery and a couple of bad phones. The other thing was some of the previous firmware seemed to make some Note 4s run hot or get hot while charging. Things are much better since PG1. YMMV.

I had this issue and sent my phone back to Samsung THREE TIMES, I thought I bricked my phone from custom rom.
Turns out it was my battery. Sounds dumb, but true. Strangely even with battery out, I was having issue. Once I put in new good battery issue resolved.

I had that issue on my pc and my note. I had a creepy stalker in full control of my device (which basically was a virtual machine). I could tell when I was on the right track to get rid of him because it shut me down. I can't say that's what's going on with you but it is a thing.
Sent from my SM-N910P using Tapatalk

Note 4 batteries are dying for lots of people anywhere from 18 months to just over 2 years, and the symptom is often fail to boot, boot loops, etc. As piggynuts said, it's not logical, but it's true. It happened to me, and when I replaced the battery, everything was fine.