Develop Bugs

[Q] I need some help please

I'll try and give as much info as possible so that hopefully this is easy to figure out.
My phone is a Samsung Galaxy s3 sch-r530u the US Cellular version. I didn't see a US Cellular forum and read someplace that it's the same as the at&t one so that's why I'm posting in here.
About a month or so ago I rooted and installed cyanogenmod with the installer and it installed I believe 11.1 maybe 11.2. The Android version my phone said it was I'm pretty sure was 4.4.2. Today in about phone in the settings I got a new version available message so I tried to do an update, which I was understanding that it was a cyanogenmod update and not a stock update but maybe I was wrong.
Right after the update my phone would boot to the boot screen with the blue robot guy on it and freeze basically. I was able to get into CWM and also into download mode. I did a little looking around and went into CWM and did the factory reset/wipe and cleared the cache and dalvik and that changed nothing.
Then I tried to flash the cyanogenmod 10.2 from inside CWM because I read someplace that it fixed the problem for someone else and it just failed when I tried. I also tried to fix via Kies and it isn't accepting my serial number for some reason. Then I found the teamuscellular website and grabbed both roms that say are stock roms and tried to flash both of those (not at the same time) via Odin and when I did the first one I got the something happened during firmware upgrade error.
I eventually fixed that by flashing the pit file with Odin and now I'm back to being stuck on the blue robot boot screen. When I try to flash either stock rom from teamuscellular in Odin they fail at some point and then I have to reflash the pit file again.
Somewhere along the line I couldn't get into CWM anymore and had to reflash that and I now have the philz touch 6.09.2 version of that.
I currently can get into both CWM and Download mode but for the life of me nothing I try works. When I go into Download mode what reads in the top left corner is this
odin mode, in red letters
Product name: SCH-R530U, in white letters
Custom binary download: Yes (4 counts), in white letters
Current Binary: Custom, in white letters
System Status: Custom, in white letters
Qualcomm Secureboot: Enable, in grey letters
Waranty bit: 1, in red letters
Bootloader Ap Swrev: 1, in grey letters
When I try and flash a rom and it fails I get some other line of text in red but I forget what it says
Any help is greatly appreciated
Thanks in advance
EDIT - Also a number of places directed me to samsungs updates websites to get the stock mod for my phone but there isn't one there for the SCH-R530U.
Also I'm looking at the how to guide for unbricking and I see something there about the status 7 error, which I do believe I got when I tried to flash the 2 teamuscellular stock mods but I don't remember for certain. I know one thing I didn't try was updating my bootloader.
I've also tried fixing with the simple upgrade tool and it fails also.

OK so I went ahead and tried the simple upgrade tool again to see the errors it gave me and in the bottom left corner of the program it had gone through a few things and failed when it said ABOOT.
And also at that same time on the download mode screen it added this line in red text at the bottom of the list in the top left corner on my phone screen
SW REV CHECKFAIL: FUSED1>Binary0

Based on a quick search, your phone supports CDMA and the AT&T version is GSM so they are not identical.
Your phone has the 4.3 bootloader with knox security. Since you flashed a custom recovery, it tripped the knox counter which voids any existing warranty.
The 4.3 bootloader cannot be downgraded to an older version and attempts to do so, either in download or recovery, may brick the phone.
In order to flash the phone in Odin, you would need to have a full and completely stock 4.3 ROM and not just a OTA update of the 4.3 ROM.
I suggest that you upgrade your recovery to the latest version and flash a custom ROM to try and get your phone functioning.

audit13 said:
Based on a quick search, your phone supports CDMA and the AT&T version is GSM so they are not identical.
Your phone has the 4.3 bootloader with knox security. Since you flashed a custom recovery, it tripped the knox counter which voids any existing warranty.
The 4.3 bootloader cannot be downgraded to an older version and attempts to do so, either in download or recovery, may brick the phone.
In order to flash the phone in Odin, you would need to have a full and completely stock 4.3 ROM and not just a OTA update of the 4.3 ROM.
I suggest that you upgrade your recovery to the latest version and flash a custom ROM to try and get your phone functioning.
Click to expand...
Click to collapse
OK. What exactly should I be looking for when you say I should upgrade my recovery? If I remember right I thought I removed that stupid Knox crap or maybe I just disabled it I forget exactly.

Thequass said:
OK. What exactly should I be looking for when you say I should upgrade my recovery? If I remember right I thought I removed that stupid Knox crap or maybe I just disabled it I forget exactly.
Click to expand...
Click to collapse
You can try and fix your phone by updating your recovery to the latest version of CWM for your phone. Then, download an install a custom ROM for your phone.
If you are not sure of what or how to do upgrade your recovery, don't do it until you have done some research and really understand the process.
As with any software change, there is no guarantee you won't brick your phone in the process.

Yeah I understand, I just wanted to make sure you meant CWM. So you think I should try reflashing a 4.3 custom rom over a 4.4? It was running 4.4.2 totally fine for a month ish.

If you want to install another ROM, I recommend doing a full wipe, including the system, cache, Davik, and data, before installing the new ROM.
I have switched between older and newer ROMs without a problem on my i747m.

Ok. I'll definitely wipe everything as I did in the past maybe there's one that I'm missing somehow. I wipe everything and somehow the blue robot boot screen is still there.

Thanks for all of your help. Your suggestions definitely led me in the right direction. I ended up finding a modified stock 4.3 with the bootloader file removed and since it seemed like my issues were related to that I figured what the hell I'll try it, I was almost at the point of going and getting a new phone anyhow. Because it wasn't completely bricked I wanted to try everything I could though and this worked!!!
Thanks again!!

No Sensors Working At All (Proximity, Accelerometer, Light Sensor ect)

So i've been using an F400S since it came out with no issues at all. When i found out that the T-Mobile variant had an unlocked bootloader, i decided to snag a broken one and fix it so i could use and AOSP rom (Bump is taking forever). The day i got the T-Mobile one, i carrier unlocked it, flashed TWRP in fastboot, then started flashing some AOSP roms. When i got the phone the screen was cracked ( has since been repaired) so i don't know if thats affecting it at all, or maybe i just did not follow the right process for setting up TWRP, but none of the sensors are working for me. The screen doesn't auto cut off during calls, auto-brightness doesn't work, neither does auto rotate. I tried reflashing an LG rom and resetting the calibration of the motion sensor, but that failed. I have a feeling this is something software related, because im experiencing a but in every AOSP rom that nobody else has had. About 70% of the time when my screen cuts off (deep sleep) it will not turn back on, and if it does it's delayed. I usually have to do a battery pull. I know that has to be a software issue because on the LG rom, it did not do that at all, and the fact that im the only person experiencing it tells me that maybe something got boinked in the TWRP installation process? I will list the steps i followed to install TWRP
I removed LAF using the following command in ADB
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
adb reboot
After that i booted into fastboot and flashed the latest TWRP (downloaded from the twrp website)
I used the following command
fastboot flash recovery boot.img (boot.img being what i named the recovery)
Let me know if i did something wrong. Who knows maybe the phones just broken, but i find it hard to believe ALL the sensors went bad at once.

joelrwise said:
So i've been using an F400S since it came out with no issues at all. When i found out that the T-Mobile variant had an unlocked bootloader, i decided to snag a broken one and fix it so i could use and AOSP rom (Bump is taking forever). The day i got the T-Mobile one, i carrier unlocked it, flashed TWRP in fastboot, then started flashing some AOSP roms. When i got the phone the screen was cracked ( has since been repaired) so i don't know if thats affecting it at all, or maybe i just did not follow the right process for setting up TWRP, but none of the sensors are working for me. The screen doesn't auto cut off during calls, auto-brightness doesn't work, neither does auto rotate. I tried reflashing an LG rom and resetting the calibration of the motion sensor, but that failed. I have a feeling this is something software related, because im experiencing a but in every AOSP rom that nobody else has had. About 70% of the time when my screen cuts off (deep sleep) it will not turn back on, and if it does it's delayed. I usually have to do a battery pull. I know that has to be a software issue because on the LG rom, it did not do that at all, and the fact that im the only person experiencing it tells me that maybe something got boinked in the TWRP installation process? I will list the steps i followed to install TWRP
I removed LAF using the following command in ADB
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
adb reboot
After that i booted into fastboot and flashed the latest TWRP (downloaded from the twrp website)
I used the following command
fastboot flash recovery boot.img (boot.img being what i named the recovery)
Let me know if i did something wrong. Who knows maybe the phones just broken, but i find it hard to believe ALL the sensors went bad at once.
Click to expand...
Click to collapse
Had exactly this when I flashed the wrong ... I don't know, modem? .. on my old LG G2 D805.
Only way to get it back was to flash the original KDZ for my model.

GTMoraes said:
Had exactly this when I flashed the wrong ... I don't know, modem? .. on my old LG G2 D805.
Only way to get it back was to flash the original KDZ for my model.
Click to expand...
Click to collapse
Just attempted that using flashtool. Tried the TOT method (which didn't go through all the way for some reason), then just went with the regular KDZ, which completed, however, it did not fix the issue. None of the sensor still work. Im starting to think its a hardware issue but i find it hard to beleive that ALL the sensors went out at once.

joelrwise said:
Just attempted that using flashtool. Tried the TOT method (which didn't go through all the way for some reason), then just went with the regular KDZ, which completed, however, it did not fix the issue. None of the sensor still work. Im starting to think its a hardware issue but i find it hard to beleive that ALL the sensors went out at once.
Click to expand...
Click to collapse
Hi
I think I have the same problem with sensors as did the same process in TWRP.
I tested the proximity and motion sensors through hidden menu and noticed that the are working actually and I'm sure it is a software issue making the problem.
but I have not found any solutions yet

Did you fix it?

I have the same problem... Someone found anything?

The solution is to flash the V10B KDZ first and then rooting, flash twrp, flash ROM

FaySmash said:
The solution is to flash the V10B KDZ first and then rooting, flash twrp, flash ROM
Click to expand...
Click to collapse
Hi,
I can't find the v10b kdz for d855, do you have a link?

Andréas.COINCE said:
Hi,
I can't find the v10b kdz for d855, do you have a link?
Click to expand...
Click to collapse
download the .kdz fitting for your model! for my unlocked D855 it was the "Germany D85510A_00.kdz" from here
EDIT: just noticed that's the A-Update, not the B one. I've got both on my PC, either should work. If you want, I could upload the Update B KDZ "D85530B_00_1217_32G.kdz" if the A-Update KDZ doesn't work.

FaySmash said:
download the .kdz fitting for your model! for my unlocked D855 it was the "Germany D85510A_00.kdz" from
EDIT: just noticed that's the A-Update, not the B one. I've got both on my PC, either should work. If you want, I could upload the Update B KDZ "D85530B_00_1217_32G.kdz" if the A-Update KDZ doesn't work.
Click to expand...
Click to collapse
Thank you, it just work perfectly

[Q] Back to stock from Lollipop

Hi everyone
Long time xda follower, newly registered, since I needed to ask a Q.
I rooted and switched to Lollipop on my ATT S3 (i747) a few months ago, Lately, I've started noticing battery issues as well as network issues with this ROM. I figure it is time for me to go back to stock.
However, if I remember correctly, when I tried previously the phone refused to downgrade back to stock. Kies was helpless because the trip counter had been reset (or something similar).
Please, is there a good how-to on downgrading this phone from Lollipop back to stock? If yes, would someone please point me to it?
Much thanks in advance.
lsiravi

Hmm.. I am going to give this a try:
http://forum.xda-developers.com/galaxy-s3/general/fix-s3-to-factory-unroot-stock-recovery-t2323847
lsiravi said:
Hi everyone
Long time xda follower, newly registered, since I needed to ask a Q.
I rooted and switched to Lollipop on my ATT S3 (i747) a few months ago, Lately, I've started noticing battery issues as well as network issues with this ROM. I figure it is time for me to go back to stock.
However, if I remember correctly, when I tried previously the phone refused to downgrade back to stock. Kies was helpless because the trip counter had been reset (or something similar).
Please, is there a good how-to on downgrading this phone from Lollipop back to stock? If yes, would someone please point me to it?
Much thanks in advance.
lsiravi
Click to expand...
Click to collapse

lsiravi said:
Hmm.. I am going to give this a try:
http://forum.xda-developers.com/galaxy-s3/general/fix-s3-to-factory-unroot-stock-recovery-t2323847
Click to expand...
Click to collapse
Nope! No go!!
Triangle away reset the counter.
The stock recovery works well. I was able to boot to recovery and wipe the data and all that.
Odin says "SW Revcheck Fail" when trying to download the stock rom.
I rebooted into Lollipop, downloaded Triangle away again and reset the counter. Still Odin fails with the same message.
I tried flashing ROM first then the recovery as it was suggested in that link. Nope. Again "SW Revcheck fail". For the record, my SWREV appears to be 3. It is supposed to be 0. Triangle Away does NOT reset this. It did reset another counter (as reported by Triangle away itself - was 5, got reset to 0).
I remember *this* was the problem previously as well, hence the original Q:
How *do* you get back to stock from Lollipop on the Galaxy S3/ATT?
Meanwhile, although Keis failed to recognize the device, I tried to run a firmware recovery manually. It took a long time and in the end failed. It also messed up the recovery, so I had to flash CW again to make it bootable. I'm still back up with Lollipop at this point, but I don't want Lollipop.
Anyone anything else I can do? Any other guide out there to downgrade?
Thanks again
L

The thread you linked is for the international version of the s3.
Before flashing anything else, you need to confirm the bootloader on your phone to ensure that you don't flash anything that attempts to change the bootloader if your bootloader is mjb or newer.

audit13 said:
The thread you linked is for the international version of the s3.
Before flashing anything else, you need to confirm the bootloader on your phone to ensure that you don't flash anything that attempts to change the bootloader if your bootloader is mjb or newer.
Click to expand...
Click to collapse
Right. I finally figured it out.
First the 4.1.1 FWs weren't flashing (in other words SW REV CHK FAIL) was basically indicating that my Bootloader was far ahead of the 4.1.1. I dropped 4.1 after I figured that part out.
Next, I tried to flash a 4.4 (UCUFNE-rooted-odex is available as a zip-flash) through CWR, which didn't work (no boot, stuck at splash).
Next I got hold of a 4.3 (UCUEMJB-2024954-REV04-user-low-ship), which successfully flashed through Odin (repartition checked), but there was no sound, IMEI indicated null. Service Mode yielded a blank screen.
I flashed TWRP through Odin (was working on CWR since the beginning) and then flashed the UCUFNE-rooted-odex above on top of 4.3 through TWRP, which was successful, still no sound/IMEI/service mode.
Finally I got hold of the UCUFNE-Modembaseband zip (a small one - 20MB) and flashed that through TWRP. Both sound and IMEI came back.
I'm at 4.4.2 now, but an OTA update from ATT failed (probably because it went through TWRP)
Now I'm back to stock, albeit rooted ROM (because of the Rooted-Odex 4.4 flash), but I am a happy camper.
Thanks to XDA for various bits of info here and there. But essentially *this* is how you go back to stock from Lollipop.
L

various problems with rooted z1 compact

hello everyone,
I am having some big trouble with my phone. since the update to lollipop its getting worse.
and now the problems:
1.) I can't reboot to recovery anymore.. it's unbelievable but it doesn't work no more. neither with an app nor manually. (phone off. phone on. press power and volume down simultaneously and let go when Sony logo appears.) tried NTR Utilities which was pre-installed..nope. tried quickboot.. nope.
2.) sometimes when I used my phone a lot I cannot turn off my 3g or my GPS from the status bar. you know you can customize your bar with 3g or hotspot or GPS etc. and my shortcuts in the downer part of the status bar don't work no more. I can press them shortcuts but it won't work. than I have to restart my phone. and it works again..
3.) when my phone is locked and I press the power button to enter my pattern the display gets bright as the sun (seriously!) all the background gets almost white and afterwards it's getting normal brightness again.. still don't know why this is happening..
4.) and sometimes when I want to take a picture the standard camera app says that I don't have a SD card in my phone (I have one ) . so it changes the save directory of the photos. but when I release the SD card and put it back in the phone everything is normal..
anyone has the same issues?
hope one of you guys can help me.
phone:
Lollipop Stock Z1C root

#3 happens to me all the time, stock not rooted 5.0.2, I hope someone replies a solution, I thought I was the only one

none of you ever experienced one of these problems?
Lollipop Stock Z1C root

really.???
no one can help??
Lollipop Stock Z1C root

rakdumafo said:
really.???
no one can help??
Lollipop Stock Z1C root
Click to expand...
Click to collapse
I don't know much, but it may help to know if you're using locked or unlocked boot loader, which kernel, which ROM, which recovery, did you flash any other mods, (xposed etc.)... These things help people help you. I don't know technical stuff, but I know that some ROMs have recovery built in, and some don't, so you have to flash yourself. Some ROMs work with some recoveries and not others. If you're rooted and unlocked BL, it may be as simple as installing Rashr, and flashing a new rec. image. In general, I've found that CM type ROMs do better with TWRP, whereas stock-based work well with CWM. If your BL is locked, it seems like Nut's dual recovery might be best. Use the PC installer for best results if you can't get any recovery at all.
The other problems you described also sound to me like ROM or kernel issues, and not necessarily lollipop related. Did you do a full wipe before updating, (system,data, and cache)? Did you flash a kernel first, etc., etc...
Like I said, I'm no expert, but I've been helped enough that I'm glad to help if I can. You just might need to add some more info.

The issue with a very bright display is true for my phone as well. I guess that it's rom or kernel related...

Heres what I suggest you do since It worked on mine:
1) Unlock your bootloader here.
2) Re-flash Lollipop FW using Flashtool
3) Boot the phone
4) Reboot Into fastboot mode and in Flashtool flash a custom kernel that has a dual recovery and is for lollipop.
5) Once the phone boots, vol - to enter recovery and flash the latest Supersu zip file to get your fw rooted
6) Download SELinuxMode Changer and set it to permissive
7) This should pretty much fix all problems

[Q] After flashing stock firmware issue still persists

I'm running on a t-mo g4 h811 10H. I recently flashed a 6.0 marshmallow rom which caused me to have several issues. Mainly the device became unstable and the screen would become consistently unresponsive to touch or power button controls. After several recovery wipes and flash attempts with different roms to try and resolve the issue I continued with my last ditch effort and flashed the stock firmware via KDZ method. Even after the phone has been reset to stock the issues I was having still continue. How is this possible? Is there anything else I can do to resolve this issue?