Related
Hi all, I'm a normal XDA user with my HTC hero.
My girlfriend recently bought the Rogers Samsung Captivate, and had a few issues with it. First the battery life was only lasting half the day. Then one day, it restarted itself 5 times. Then it seemed like it was laggy. At first when she told me about the battery issue I thought, ok maybe if we put a custom ROM on, it may help. So I rooted, put clockwork recovery, then installed Assonance ROM. We seemed to have gotten rid of the lag but the random restarts seemed to persist, then she was having Sms's coming in weird, so I decided we should put it back to stock and get it back to rogers. So i tried doing a restore from clockwork, but it still has the AT&T logo, and when the phone boots, I have a black screen that says no service on the top right, and swipe screen to unlock, but it won't unlock.
All I want is this thing back to stock, no AT&T screen so I can try to warranty this thing.
Thanks in advance for any help, I've done some searching and can't seem to get this thing back to life.
Thanks,
AZ
AbsoluteZero said:
Hi all, I'm a normal XDA user with my HTC hero.
My girlfriend recently bought the Rogers Samsung Captivate, and had a few issues with it. First the battery life was only lasting half the day. Then one day, it restarted itself 5 times. Then it seemed like it was laggy. At first when she told me about the battery issue I thought, ok maybe if we put a custom ROM on, it may help. So I rooted, put clockwork recovery, then installed Assonance ROM. We seemed to have gotten rid of the lag but the random restarts seemed to persist, then she was having Sms's coming in weird, so I decided we should put it back to stock and get it back to rogers. So i tried doing a restore from clockwork, but it still has the AT&T logo, and when the phone boots, I have a black screen that says no service on the top right, and swipe screen to unlock, but it won't unlock.
All I want is this thing back to stock, no AT&T screen so I can try to warranty this thing.
Thanks in advance for any help, I've done some searching and can't seem to get this thing back to life.
Thanks,
AZ
Click to expand...
Click to collapse
Go here....http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S/SGH-I896
Scroll down and you will see a link to the stock Roger's ROM.
Microwave...15 seconds...you don't want to overcook
I have that, i'm trying to install it, but it's taking a long time to start installing update. I've tried reformatting everything, I've tried renaming the Rogers stock to update.zip.
any thoughts on how long it should take to install, or any better instructions on how to get back to stock?
Still stuck at installing update after 15 minutes.
also, is there go instructions on how to get rid of the AT&T Logo, or will the stock rom/firmware fix that?
Ok So, I unzipped the stock firmware and it seems to have installed, but I still get the AT&T logo, and I'm still frozen at the swipe screen to unlock section. I can't swipe at all or do anything for some reason.
AbsoluteZero said:
Ok So, I unzipped the stock firmware and it seems to have installed, but I still get the AT&T logo, and I'm still frozen at the swipe screen to unlock section. I can't swipe at all or do anything for some reason.
Click to expand...
Click to collapse
I'd just like to post that I had this exact same issue when I tried to restore to my original ROM Manager backup, and a solution would benefit both of us.
Auridran said:
I'd just like to post that I had this exact same issue when I tried to restore to my original ROM Manager backup, and a solution would benefit both of us.
Click to expand...
Click to collapse
Did you end up being able to boot ok somehow?
AbsoluteZero said:
Did you end up being able to boot ok somehow?
Click to expand...
Click to collapse
Nope. I'd always be stuck at that black lock screen unable to unlock. After one erase and restore there was a background image instead of blackness, but it didn't go any further. I just decided to stick with Assonance, but that's not really an option for you unfortunately.
so I was wrong right from the beginning, I didn't flash Assonance, i flashed Cognitionv2.3b8. Sorry for the confusion
I clipped this from the above link to the rogers stock rom.
"Be aware when installing AT&T Firmware 2.2 and trying to recover to Rogers stock, you will have a short AT&T display on boot up. One way to remove this is to flash the phone with firmware from a Samsung I9000 model and then reflash it with the Rogers Firmware. This will remove the AT&T logo. However, there is a chance that this method may, in certain circumstances, leave a seemingly random pixlation on screen upon boot-up for the time the AT&T logo was meant to be displayed. A very minor issue and doesn't affect the phone or boot process"
So try to find a stock I9000 rom I guess. The assonance rom is based off the I9000(Or at least that what it says on boot :/). I'm not sure if that will be good enough. I'm running Assonance right now on my fiance's rogers captivate. It's been working great since she has gotten it. So maybe even just flashing Assonance will fix things for you.
As a side note, I returned my x10 with a custom rom on it for warranty and I never heard from them. My understanding(hearsay) is that it doesn't even go to rogers. I'm in Ontario, and I believe it goes to a refurbishing company that is contracted by rogers where they check for water damage.
So I'm not sure where you are located but it may be the same.
(Disclaimer: I'm not saying you WONT get billed for the phone if you send it back with custom rom on it.. I'm simply saying that I didn't and I have heard of others not being as well. Perhaps we were just lucky)
Good Luck.
If you try this let me know if it works, should I ever need to send hers in for warranty.
check your pm
Hi i have the Galaxy S4 Active from At&t SGH-I537. It is rooted using activeroot by geohot and i have removed some blootware with titanium backup. It has worked fine for months and all of a sudden today the screen went black. The led notification light works and i can hear myself getting text messages but the screen simply will not turn on. Tried booting into recovery with no luck the screen was still off. When i plug my phone into my computer i can browse my files through the computer normally. I requested a new phone under the factory warranty and just realized that i am screwed and will get charged full price for replacement because my phone is rooted. Does anyone have any suggestions??
Udipti said:
Hi i have the Galaxy S4 Active from At&t SGH-I537. It is rooted using activeroot by geohot and i have removed some blootware with titanium backup. It has worked fine for months and all of a sudden today the screen went black. The led notification light works and i can hear myself getting text messages but the screen simply will not turn on. Tried booting into recovery with no luck the screen was still off. When i plug my phone into my computer i can browse my files through the computer normally. I requested a new phone under the factory warranty and just realized that i am screwed and will get charged full price for replacement because my phone is rooted. Does anyone have any suggestions??
Click to expand...
Click to collapse
It sounds like your screen is broken, it could be something on the software side, but my bet is that the screen is broken. One thing you could try before sending it off for warranty replacement is to flash the Odin files for MF1, this will wipe everything but you would be able to see if the screen is truly broken or not.
If you do have to send it off for warranty, I suggest flashing the ML2 Odin package, don't flash the ML2 bootloader as this will provide you a way to get back to MF1. This will revert your phone to stock and they shouldn't be able to tell you rooted it. The flash counter shouldn't be tripped either since it's not possible to flash anything to the i537. Beware that your warranty replacement will probably come with ML2 pre-installed meaning you will no longer have root. Most of the time Samsung will simply replace your phone, but if they just install a new screen and don't update the firmware, make sure you don't flash the ML2 bootloader.
The other thing you could do is search around for a replacement screen and try to install it yourself.
All the Odin packages can be found in the i537 Firmware thread.
So here's my problem. I think I've bricked my device. Don't know if it's softbrick or hardbrick, but either way my phone just does not boot up. The only instance it works is when I remove the battery and try to charge the phone, it shows a picture that it didn't find a battery. All of this occurred while trying to unlock the bootloader. Something similar already happened to me like a month or two ago, but I was able to flash stock KDZ using the online LG Support Tool. Anyway, the part where it all messed up is probably the aboot.bin file, although I'm quite certain I flashed the right file for my device. Also, installed CWM recovery, and after restarting the device it just won't boot at all, not even the software upgrade mode or anything. So my guess is that something is wrong because of either a wrong aboot.bin file for my D405N or the custom recovery. I tried flashing stock KDZ, but I couldn't get my phone into software upgrade mode. Also, tried doing a hard reset, but an LG logo didn't even come up. The battery is at least half full. So is there anything I can actually do in this case? Any help is appreciated.
P.S. Yeah, I did post in another thread (though I didn't create it), but I'm quite desperate with this. Either I fix it myself somehow, or I'll have to take it to the warranty.
EDIT: Took it to a repair. Should be done in around a week. Got an old Samsung Galaxy Mini as a replacement.
linasj said:
So here's my problem. I think I've bricked my device. Don't know if it's softbrick or hardbrick, but either way my phone just does not boot up. The only instance it works is when I remove the battery and try to charge the phone, it shows a picture that it didn't find a battery. All of this occurred while trying to unlock the bootloader. Something similar already happened to me like a month or two ago, but I was able to flash stock KDZ using the online LG Support Tool. Anyway, the part where it all messed up is probably the aboot.bin file, although I'm quite certain I flashed the right file for my device. Also, installed CWM recovery, and after restarting the device it just won't boot at all, not even the software upgrade mode or anything. So my guess is that something is wrong because of either a wrong aboot.bin file for my D405N or the custom recovery. I tried flashing stock KDZ, but I couldn't get my phone into software upgrade mode. Also, tried doing a hard reset, but an LG logo didn't even come up. The battery is at least half full. So is there anything I can actually do in this case? Any help is appreciated.
P.S. Yeah, I did post in another thread (though I didn't create it), but I'm quite desperate with this. Either I fix it myself somehow, or I'll have to take it to the warranty.
EDIT: Took it to a repair. Should be done in around a week. Got an old Samsung Galaxy Mini as a replacement.
Click to expand...
Click to collapse
Remember Next time Unlock Bootloader before Installing CWM.
So I have a Sony Xperia Z1 C6902
And I've been messing around with ROMs, since I didn't know what exactly I wanted I've been installing a lot of different ROMs for about two-three days. I ended up using Slimroms as the ROM and RockZ1 as the kernel. I specifically used that version in particular since I wanted to use KitKat instead of Lolipop.
So after a while of using it, I found out it somehow became not rooted, and I couldn't install SuperSU properly (what with updating binaries and such) and this phone had a previous owner who had the bootloader unlocked and everything unlocked previously with this ROM
So I decided to try to root it using this method then when I went to flash C690X_14.4.A.0.108_KernelOnly.ftf as part of instructions, my phone ended up being stuck on a Blank Screen somehow?
The thing about the Blank Screen is that upon booting, the Sony screen shows up, and then nothing else. However, I can lock the phone, and when I unlock the Sony logo dissapears and I get a completely blank screen. I could touch certain areas and get some kind of feedback on what I assume is the PIN screen. So I just assumed that means the ROM isn't compatible with this kernel, so I flashed C690X_14.4.A.0.157_KernelOnly.ftf ahead of instruction since I couldn't normally access the phone to use Debugging because of the lock PIN.
On boot again, it still didn't show anything, so I just tried a Hard Factory Reset using the red button on the phone. That didn't resolve my problem whatsoever, but when I booted it again and touched the blank screen, I get Phone Dial noises?
Help?? The phone isn't bricked as far as I'm aware, since it can still boot and such, but I can't get into recovery to flash other roms or kernels, and I don't know what to do.
Update, I suppose. I tried the Sony PC Companion method, with repair phone/tablet, and it just gave me an error saying I have modified software and it didn't do anything about it.
Unecessary post, apologies
Unecessary post, apologies
I don't see EQC1 on sammobile, anyone else see the 127 MB update?
I'm on EQB1.
Yup, I see it, 127.53mb on both of mine SM-N910T3 and
SM-N910T
I have it as well. Have you flashed yet?
I have it too. I'm not sure I want to flash, especially if it patches the ability to root my phone.
My phone also suffers from the SD card / reboot issue (the phone constantly boot loops when both an SD card and SIM card are in the phone). I wonder if this update will fix that?
I tried flashing it and it failed, I'm running a stock highly modified rom. I'll try reflashing the original stock unmodified rom when I get a chance tomorrow and apply the update. It looks like it's just security updates
Says "Various system improvements" for the QC1 update.
https://support.t-mobile.com/docs/DOC-28899
I updated to this version the other day, now I'm looking to root. Anyone know if the old root method still works? I may try myself in the next few days myself and find out.
I upgraded to it yesterday. Took about 30 minutes from start of install to finish. It updates the security to March 2017, has the new Google Play Store. Other than that I do not notice any other differences
Can i root after upgrade?
Does anyone know if this fixes the mmc_read failed issue along with its constant lagging/freezing problem?
febzz88 said:
Does anyone know if this fixes the mmc_read failed issue along with its constant lagging/freezing problem?
Click to expand...
Click to collapse
I'm pretty sure the mmc_read failure issue is failing hardware and no firmware release can fix this. My understanding is some Note4's had dodgy flash memory and will eventually fail. I had this happen to my note4 last year and got it changed out under warranty at a tmobile store. My phone had the constant lagging/freezing for about a month before it would just no longer boot, it wouldn't do anything other than a quick vibrate on power up, no boot screen of any type.
If you are getting mmc_read I would suggest you get the phone replaced ASAP, and make backups of everything you have on it that you want to keep. At some point it probably just wont power back on again. Hopefully you are still under a warranty and can get it swapped out.
d0ug said:
I'm pretty sure the mmc_read failure issue is failing hardware and no firmware release can fix this. My understanding is some Note4's had dodgy flash memory and will eventually fail. I had this happen to my note4 last year and got it changed out under warranty at a tmobile store. My phone had the constant lagging/freezing for about a month before it would just no longer boot, it wouldn't do anything other than a quick vibrate on power up, no boot screen of any type.
If you are getting mmc_read I would suggest you get the phone replaced ASAP, and make backups of everything you have on it that you want to keep. At some point it probably just wont power back on again. Hopefully you are still under a warranty and can get it swapped out.
Click to expand...
Click to collapse
Hi,
That's certainly is one possible scenario (hardware failing). But based on my extensive research too, many have said that this could be faulty firmware. I went to a Samsung Experience Center and talked with a guy there and he said that it's a known issue affecting many Galaxy Note 4 Sprint users a few months ago. Samsung in the end replaced/repaired the affected units free of charge.
In the past 2 months or so, more and more Galaxy Note 4 users started experiencing this issue. And so it could be that the firmware triggered the issue, and eventually damaged the hardware.
Since we don't really have a 100% certain answer (of course, Samsung will never tell us), I'm just trying to see if anyone has updated the phone to the latest firmware and could tell us if it fixed the issue.
Soooo..... Is this rootable or not?
sino8r said:
Soooo..... Is this rootable or not?
Click to expand...
Click to collapse
Try this https://forum.xda-developers.com/no...rom-n910t3uvu3eqc1-stock-rooted-odex-t3592242
I can't seem to get TWRP to work on this. I've tried several times with Odin, it appears to be successful, phone reboots, but then when I try to reboot into recovery there's no TWRP, only stock. Anyone else have this issue or any suggestions?
Edit: Tried something I remembered reading in another thread. I pulled the battery immediately after Odin successfully finished and the booted directly into recovery. It worked. I'm flashing pvsgh's rooted EQC1 and will report back if TWRP sticks
Edit 2: Success. Seems like pulling the battery after Odin/TWRP before the phone reboots did the trick
ok, thanks for the suggestion.
Anybody have a link for the firmware?
thecrunked said:
Anybody have a link for the firmware?
Click to expand...
Click to collapse
https://forum.xda-developers.com/no...firmware-galaxy-note-4-n910tuvs2eqb1-t3569911
Can I autoroot with EQC1?
I tried auto root and got
RECORVERY IS NOT SEANDROID ENFORCING,
AM I screwed? I assume there's some way to get back to EQC1 and boot the phone. There has to be. But could I do it and keep the data. I was trying to get deleted photos back.