I bought a T-Mobile Samsung S6 from craigslist and it was working fine until recently that the Rent-A-Center lock screen popped up and rendered the phone useless as it was asking for the security PIN. I googled for methods to remove the annoying lock screen but could not find any guides for the S6.
(Sure, I could turn the phone back into RAC as it was "eligible for the buy back program" and take a loss....but why?)
Out of frustration of not finding a usable guide, I decided to use the existing guides for the S5 and hopefully adapt them for the S6. (The available guides suggest the use of custom ROMs, specifically one from cyanogenmod. However, there isn't any available S6 ROM from cyanogenmod yet.)
In any case, I followed the the basic steps:
Install customer recovery. In my case, I chose the latest version of TWRP (https://dl.twrp.me/zeroflte/twrp-3.0.2-0-zeroflte.img.tar.html)
Install a custom ROM to circumvent the code execution of the annoying custom lock screen.
This is where I made a mistake, but it turns out to be a good one! I had downloaded several custom ROMs but they did not stop the custom RAC lock screen. I am still not sure why I thought Alex-V Personal ROM for the Samsung Galaxy S6 Edge (http://forum.xda-developers.com/galaxy-s6-edge/development/rom-alex-personal-5-1-1-rom-t3156665) would work for the regular S6 but I downloaded it and flashed it.
After the successful flash, I realized that the ROM was intended for the S6 Edge and that the touch screen geometry was off--meaning, the response to the touch was backward. For example, touching the right edge of the screen would cause the left edge of the screen to respond and vice versa.
In any event, I managed to set the phone up and the RAC lock screen was gone! However, the phone is not 100% usable as the touch screen was barely functional due to off coordinate responses.
I searched for another ROM that might work; I found SOW NICE ROM OJC and downloaded it. I tried to flash the new ROM in TWRP but was not able to do it because I could not swipe the screen correctly to start the flashing process!
At this point, I wanted to start over so I used ODIN to flash the stock ROM (G920TUVS3DOJC). I didn't expect the phone to work normally as the stock ROM and other custom ROMs that were based on the stock ROM did not stop the RAC lock screen; but for some reason, the RAC lock screen was gone! And my phone was back to the way it was.
By the way, I had turned on the OEM unlocking and Reactivation Lock off on my phone. Thus I was able to install TWRP.
I hope this post would also work for your RAC-locked S6.
Related
OK, I have searched for this, but have not found it in this context. I did a flawless OTA and install of 4.3 on my S4 Active. After install I had an image of an open padlock and the word "custom" show up on a boot screen, Used to get this in the early root days, but not for several month after following some tips elsewhere in these forums.
I also had trouble connecting WiFi unless I rebooted. Whether I needed or not, I did a complete factory restore, which seems to have cleaned up the WiFI thus far, but not the lock/custom situation.
Any ideas or suggestions?
Hey all,
Looking for some assistance here. I apologize in advance for not having specifics on everything, but it's been a couple years since I've needed to do anything with this phone (SM-G900A). I picked it up used a couple years ago and shortly after, I did a NOX unlock and rooted the phone for two reasons - using Titanium Backup and to unlock the WiFi hot spot. I recently noticed that something had happened and my root access wasn't working correctly- guessing from one of the OTA updates that was attempting to occur on my phone. I say attempt, because I don't believe they ever successfully installed since they always seemed to error out. I'm currently on StraightTalk, not an AT&T customer. Something weird was up with it though, because I could never uninstall the Xposed Framework or app, yet Pokémon Go was recognizing it was rooted and blocking my access. I should also mention that I had towelroot running on the phone and it's showing the custom unlocked padlock on startup.
Fast forward to last night- I wanted to return it back to the stock ROM so I did my research, found a couple different tutorials that included the correct ROMs and applied one - G900AUCU1ANCE_G900AATT1ANCE_ATT.zip. After flashing, the phone will not boot and freezes halfway through the swirls around the Samsung logo, then goes blank. The blue notification light also stays lit on the phone.
Thinking it was most likely bootloader related, I found another ROM that included separate AP, BL, CSC files. I attempted to flash the bootloader, which failed and I got the following error on the phone - SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1
At any rate, it seems like my boot loader somehow got corrupted or isn't compatible with this ROM, but I was hoping some of you experts out there could provide some answers. At this point my phone is dead, so I'm hoping I can get it restored very soon.
Thanks in advance guys!
The issue identified in this thread (http://forum.xda-developers.com/galaxy-s5/help/g900a-stuck-samsung-logo-black-screen-d-t3050369) seems very similar to mine as well as what's described on this website- http://www.galaxys5update.com/fix-black-screen-with-pulsating-blue-led-on-galaxy-s5-g900a/
I'm seeing the pulsing blue light as well. How do I find the 4.4.4 OA1 Kernel identified in the first link?
Hello XDA, I'm having a problem with my grandmother's phone, and I'm in a hurry to get this fixed because she needs it for business. Her phone is an AT&T Galaxy Note 3 SM-N900A unlocked to T-Mobile. It was running Android 4.4.2 KitKat, and I tried to update the phone as I did with my grandpa's, who has the same exact phone before we switched to T-Mobile. Because it was unlocked, the phone couldn't receive the OTA Lollipop update due to the SIM card not being AT&T.
After spending 4 hours searching and trying solutions, I came down to one thread on XDA Forums here. I saw it and I ended up using Odin 3.09 to flash the All-In-one/Non-Wipe Tar file onto it, now my phone is stuck in a boot-loop. Strangely, the Lollipop update seems to be installed as when I plug her phone into my PC/charge it, the battery screen is different than the old one which looked shiny and not flat and material like the Lollipop one. Knox has not been tripped, system status is OFFICIAL, and every time I turn on the phone, it proceeds to boot until the AT&T logo screen, where it freezes mid-way vibrates 2 times and boots the same way over and over again.
Is there anything I can do aside from doing a wipe or factory reset, as I mentioned before she has to use the phone for a business she works for and she had somewhat important work on the phone. The worst part of it all is I was stupid and ignored the warning to back my data up first in the firmware thread. Please help, I'm in a very big hurry to solve this and finish the updating/problem.
P.S If it's not a boot loop and it's called something else, whatever. xD
Did you try using Smartswitch to see if it can see and repair and/or reflash? A factory reset may be the only way to fix it because I believe the file layout for KK and LP and different.
Hello,
I received a at&t galaxy s6 edge, it was rooted and kept popping up knox warnings, so I looked at the baseband version and it was G925AUCU6EQCF, I googled that + stock rom which lead me to this thread.. which I downloaded and flashed using Odin, afterwards my touchkeys/softkeys just no longer work. They were working before flashing.
I've tried, wipe cache, factory reset, safe mode booting, *#2663# -> sensorhub fw update is grayed out, I also tried multiple new charging ports.
Little background, I don't know much about rooting and android roms, but I run a repair shop and do bunch of hardware repairs. I recently received a dozen or so assorted s6, s5, s6 edge, note3, note5 which all appeared to have been throwing KNOX warnings (among other issues, broken screens, charge ports, etc..). Now I'm not completely oblivious to this stuff, but I've flashed stock roms and installed twrp +root before on samsungs. For 10 of the phones I googled the baseband +stock rom and was able to flash it back to stock and KNOX warnings went away and all were fully functional, not sure If I'm doing it right but it works, perhaps unrooting would have been easier/quicker?
I opened up the phone and tried a working charging port from another s6 edge which I know the softkeys work, but I still got no touch on them, they only light up but no function or vibrate, so I did some googling and noticed I may not be the only one. I've seen some threads here but for other samsung phones, some mention something about "flash some idlekernel that will update the touchkey's FW", another mention build.prop and other "qemu.hw.mainkeys=".
Now, I am not all too technical with this so I was hoping some handsome generous person could help me out or point me somewhere, anywhere
Thanks!
Good morning, I hope you can help me. I have a note 9 sm-n960f and with the last update of the stock rom the mobile does not turn on. The update went well and everything was set up fine. The problem I have is that when I turn off the mobile and turn it on, it stays on the Samsung logo and I have to force it off and turn it on again until it starts well, it can stay on the logo several times and other times it starts normally. I have flashed the last stock rom again by odin and the same thing happens, the first boot does it well and lets you configure all the mobile correctly but if you already turn it off and turn it on again, it loops into the Samsung logo and starts when you want. I have also flashed a last stock rom from Germany and I have downloaded several stock roms and the same thing happens to all of them. I have installed custom rom and if they are from android 10 the same thing happens they stay in the logo, on the other hand with android 11 in custom rom it starts perfectly. Could someone give me some advice, I would like to stay on the stock rom for various reasons. To finish saying that when flashing by odin I have tried it with the 4 files and also with the pit file but everything remains the same. I hope your help. Thanks
Try unlock bootloader, so that you can proceed and flash other custom rom.
How to unlock bootloader on Samsung Galaxy Phones
The Linux platform based Android OS is really customizable and easy to use for any user or developer. Just like other devices, the Samsung Galaxy device
www.getdroidtips.com
LR7875 said:
Try unlock bootloader, so that you can proceed and flash other custom rom.
How to unlock bootloader on Samsung Galaxy Phones
The Linux platform based Android OS is really customizable and easy to use for any user or developer. Just like other devices, the Samsung Galaxy device
www.getdroidtips.com
Click to expand...
Click to collapse
I have the bootloader unlocked, but the problem is that all the stock roms remain in the samsun logo and what I want is to have the stock rom. any solution?