Database Develop

[Q] VZW update and CWM

I'm running decrap 1.1...My phone automatically attempts to install the vzw update every day, usually around 5 AM. With CWM installed, it seems that when the phone reboots after the install, it prevents the upgrade from actually being put in place. In theory this is a good thing and prevents unwanted downloads. The problem is that it is preventing my alarm from working and I wake up every day with my phone in CWM recovery mode. Plus I was late to work today. So, I would actually like to try the vzw update and replace it with the revolt rom if I don't like it. Does anyone know where the VZW update gets stored so that I can flash it out of cwm? Any thoughts on this would be appreciated.

You will need to flash back to stock and remove root to have the update install, and then if you change your mind, you will need to downgrade to the old software before being able to root again.

Nooben said:
I'm running decrap 1.1...My phone automatically attempts to install the vzw update every day, usually around 5 AM. With CWM installed, it seems that when the phone reboots after the install, it prevents the upgrade from actually being put in place. In theory this is a good thing and prevents unwanted downloads. The problem is that it is preventing my alarm from working and I wake up every day with my phone in CWM recovery mode. Plus I was late to work today. So, I would actually like to try the vzw update and replace it with the revolt rom if I don't like it. Does anyone know where the VZW update gets stored so that I can flash it out of cwm? Any thoughts on this would be appreciated.
Click to expand...
Click to collapse
Do NOT install the update if you want root and Revolt. Just flash Revolt or Home-Less as instructed in their threads, and you will be good to go!!!

[Q] Root/Flashing problems

I just rooted my Bionic after finally getting tired of any OTA updates from Moto/Verizon. When I went to root it I noticed my build number was 5.5.886, and when I clicked on System Updates, it said it wasn't available and to retry again later. So I found a root method and the files for builds as old as mine and went ahead and rooted.
I used Safestrap and installed a ROM, the CM10 for ICS Leak by DH from here. Well it didn't work. I cleared cache/data, put it into safeboot and flashed it. It said it installed correctly and everything but after I rebooted the phone it did the droid bootloader then a blank screen with the keys and backlight on. I left it there for around 20 min to see if it was just taking awhile to boot.
I then rebooted back into recovery and turned safeboot off. I didn't restore my pre-root rom, rather went back to factory. This time when i clicked on System Updates, it found one and updated. So I figured maybe that was the problem. I repeated the procedure and still got the blank screen. I figured it may be the ROM not working with my phone so I tried another one, and 4 more after that, all with the same result.
Is there something I did wrong? I can still get my phone working by turning safeboot off, but no ROMs have worked yet. Could it be that I updated with an OTA after rooting?

Got it figured out. Just used RSDlite to flash .902 then OTA to .905.

SM-G870A stuck at logo

I'm currently stuck at the s5 active logo screen and then it boots into recovery. I've tried flashing the full odin.rar (yes I extracted it) and it fails everytime. I get the message "Sw REV CHeck Fail: [aboot]Fused 2> Binary 1. I've already tried wiping the data from the recovery menu. Nothing is working.

We need more info. What were you attempting to do and from what ROM. Are you sure you are using the proper ROM 900 or 870?

I was attempting to downgrade back to stock from 5.0 and hit the stock kernel instead of the firmware accidently when in odin. And yes I am absolutely sure i'm using the 870 rom.
Edit: What if I use a stock img and a PIT file for the phone? OR is it because I need a 5.0 lollipop firmware to flash through odin?
Edit number 2: okay I'm stupid, im on G870AUCU2BOF3. I'm going to have to reflash the of3 zip aren't I?

Okay so I found the OF3 cfg on another thread and was able to load it and flash it and get my phone working! Now, the next question is can I root in my situation or downgrade or am I just stuck?
Edit: Going to wait for a possible root! Mod can close this thread.

if you loaded the 2400258.cfg you probably loaded the OF3 bootloader as well and now you can't go back. No root at this time and it doesn't look good for the future.

Cloudsdabomb said:
Okay so I found the OF3 cfg on another thread and was able to load it and flash it and get my phone working! Now, the next question is can I root in my situation or downgrade or am I just stuck?
Edit: Going to wait for a possible root! Mod can close this thread.
Click to expand...
Click to collapse
At command prompt type without the qoutes.
"getprop ro.bootloader"
Then paste output.
Sent from my SAMSUNG-SM-G870A using Tapatalk

If you took the of3 ota or are otherwise on the of3 bootloader your stuck there....no downgrade or root as of this time.

Me too
I am in a similar situation. Saturday I was on a rooted 4.4.2, flashed a stock unrooted 4.4.2 with Odin (G870AUCU1ANE4_G870AATT1ANE4_G870AUCU1ANE4_HOME.tar.md5), let AT&T update me to 4.4.4, installed the old kernel with Odin (G870A_NE4_Stock_Kernel.tar.md5), rooted with towelroot, installed the new kernel with Odin (G870A_OA1_Stock_Kernel.tar.md5), updated to 5.0 with Odin and it retained root. However, certain things such as XPosed didn't work and I really really hated the white notification drawer so I just want to go back. I tried flashing the stock 4.4.2 in Odin again and it said success. It restarts and seems to be working but gets stuck on the AT&T logo. Now if I restart it always sticks on the AT&T logo even when I flash again. I don't know what else to try. A different file? Is there a way to go back to KitKat?
Update: I got into recovery mode (I kept trying vol up, vol down, power but it's actually vol up, home, power). I wiped the cache and did a data reset and restarted the phone. It worked! I'm excited to have a black notification screen again

pgross41 said:
I am in a similar situation. Saturday I was on a rooted 4.4.2, flashed a stock unrooted 4.4.2 with Odin (G870AUCU1ANE4_G870AATT1ANE4_G870AUCU1ANE4_HOME.tar.md5), let AT&T update me to 4.4.4, installed the old kernel with Odin (G870A_NE4_Stock_Kernel.tar.md5), rooted with towelroot, installed the new kernel with Odin (G870A_OA1_Stock_Kernel.tar.md5), updated to 5.0 with Odin and it retained root. However, certain things such as XPosed didn't work and I really really hated the white notification drawer so I just want to go back. I tried flashing the stock 4.4.2 in Odin again and it said success. It restarts and seems to be working but gets stuck on the AT&T logo. Now if I restart it always sticks on the AT&T logo even when I flash again. I don't know what else to try. A different file? Is there a way to go back to KitKat?
Update: I got into recovery mode (I kept trying vol up, vol down, power but it's actually vol up, home, power). I wiped the cache and did a data reset and restarted the phone. It worked! I'm excited to have a black notification screen again
Click to expand...
Click to collapse
How long did you have to wait for your phone to boot all the way up from the ATT logo? Mine is doing exactly the same thing and I've flashed all kinds of kernels via odin and heimdall with no affect. None of the various fixes I've found have helped, including trying to re-apply the OTA file (system just won't do it). All I wanted was to unroot. Awesome.

The first boot can take a while but if it lasts more than 10 minutes it's probably not going to happen. I've gotten it stuck there twice since my last post and I'm always able to salvage it by going into recovery mode (vol up, home, power while powered off). Wipe the cache and data reset and it should be a fresh start like out of the box new.

Hm. So the only real two options are take it in to AT&T and hope they have the full stock G870AUCU2BOF3 image to flash over (since Samsung locked down their bootloader so hard, so downgrading is impossible :good: ) or hope they release G870AUCU2BOF3 on SamMobile/Kies/Smart Switch. This is like the new hard brick... potentially it's salvageable but the company (I'm guessing AT&T here since this is an AT&T exclusive phone) is just screwing us. Guess I'll try the walk of shame to AT&T. Or maybe putting in a claim like that one person did, get a whole new phone because of a mysterious cut on the rear panel seal...

Alright, took it in to AT&T and sure enough they had the full 5.0 image available so after signing a no-return data waiver (didn't even confirm my AT&T account or ask for any ID) the tech took my phone in the back and flashed it back to stock. First boot still showed the "custom" with unlocked padlock on the boot screen but after I rebooted it, I guess it updated the bootloader because it was back to normal.
No more root and he confirmed there's no way to go back to 4.4 once you go up to 5.0, so if you want root, I'd suggest staying away from 5.0. At least now I can use my phone again. Just thought I'd post this up in case anyone wasn't sure if AT&T would actually be able to reflash stock 5.0 and at the very least get your phone working again... enough to put on ebay and get a Moto or some other brand that doesn't lock down the bootloader so hard.
Edit: note the first boot will take a few minutes but I knew it worked when there was a quick vibe and the notification light went from pulsing blue to off. Maybe 4-5 minutes.

retro486 said:
Alright, took it in to AT&T and sure enough they had the full 5.0 image available so after signing a no-return data waiver (didn't even confirm my AT&T account or ask for any ID) the tech took my phone in the back and flashed it back to stock. First boot still showed the "custom" with unlocked padlock on the boot screen but after I rebooted it, I guess it updated the bootloader because it was back to normal.
No more root and he confirmed there's no way to go back to 4.4 once you go up to 5.0, so if you want root, I'd suggest staying away from 5.0. At least now I can use my phone again. Just thought I'd post this up in case anyone wasn't sure if AT&T would actually be able to reflash stock 5.0 and at the very least get your phone working again... enough to put on ebay and get a Moto or some other brand that doesn't lock down the bootloader so hard.
Edit: note the first boot will take a few minutes but I knew it worked when there was a quick vibe and the notification light went from pulsing blue to off. Maybe 4-5 minutes.
Click to expand...
Click to collapse
It's not Samsung that locks down the bootloader, it's AT&T. the T-Mobile Version doesn't have a locked bootloader and is easily rooted . Just have to SIM unlock it and you can use T-Mobile phone on AT&T network.

Delete

Random reboots after flashing Root Debloated

My wife and I both have H811 G4s. I've gone through and rooted both of our phones with Low Effort, flashed twrp, debloated, updated to 10n debloated. Everything has been great until last week. My wifes phone started randomly rebooting. It's actually random. I can't find anything consistent. I removed apps with updates, factory reset and it would reboot during the setup wizard. Yesterday I did a full return to stock 10n, and it behaved all day.
Today I try to root with the 10n debloat , and now it's rebooting again. I have a hard time thinking it's bad hardware as the full stock works fine, and with it not rebooting on stock how would I prove it for the replacement?
What else can I check or do to fix this, and why is it only happening to one of the phones?

Bad download.
Sent from my LG-H811 using Tapatalk

MicroMod777 said:
Bad download.
Click to expand...
Click to collapse
Good idea, but I've used the same file on multiple phones without issue. It's only the one device having problems. Also the md5 matches, just double checked.
As I work my way backwards I'm pretty sure this it turning into failed hardware. I've had it reboot a few times on stock during the setup wizard. But it's nowhere as frequent as the rooted roms.

No WiFi When Going From pre-rooted 5.1 to pre-rooted 4.4.4

To those of whom have downgraded back to a rooted 4.4.4 IMG from a rooted 5.1 IMG
I started out on a 4.4.4 img from ComputerFreak and then I did all the steps in his readme to upgrade to the pre-rooted 5.1 IMG. Everything went smoothly and everything worked correctly. The reason I want to go back to KK is that the XPosed Mods I use most do not work on 5.1 just yet. So I decided to revert back to KK until those mods become available on LP.
I flashed back to stock KK. That was also successful. The only mishap that comes up when on stock KK is the "Uninstall Motorola Sensor Serivces firmware". I researched this and everyone said they did not know what it was and/or to just reboot the phone and it does not come up again. I did not choose to uninstall it or take any action besides rebooting the phone and it usually "goes away".
THE REAL ISSUE:
Whenever I flash any rooted KK IMG to the phone via mofo the wifi does not turn on, no matter which rooted KK IMG I flash to the Turbo. I go to turn on the WiFi and the little switch image simply goes back to off as soon as i release my finger.
The WiFi works on stock KK and any pre-rooted LP IMG. I have done multiple data and cache wipes. I did it every time after flashing a new IMG.
ComputerFreak and I have been trying to figure this out and no solution. He said he's had the issue before but doesn't remember how to solve it and that others have had it too.
Thanks in advance for any help!! :good::good:

zacw4328 said:
To those of whom have downgraded back to a rooted 4.4.4 IMG from a rooted 5.1 IMG
I started out on a 4.4.4 img from ComputerFreak and then I did all the steps in his readme to upgrade to the pre-rooted 5.1 IMG. Everything went smoothly and everything worked correctly. The reason I want to go back to KK is that the XPosed Mods I use most do not work on 5.1 just yet. So I decided to revert back to KK until those mods become available on LP.
I flashed back to stock KK. That was also successful. The only mishap that comes up when on stock KK is the "Uninstall Motorola Sensor Serivces firmware". I researched this and everyone said they did not know what it was and/or to just reboot the phone and it does not come up again. I did not choose to uninstall it or take any action besides rebooting the phone and it usually "goes away".
THE REAL ISSUE:
Whenever I flash any rooted KK IMG to the phone via mofo the wifi does not turn on, no matter which rooted KK IMG I flash to the Turbo. I go to turn on the WiFi and the little switch image simply goes back to off as soon as i release my finger.
The WiFi works on stock KK and any pre-rooted LP IMG. I have done multiple data and cache wipes. I did it every time after flashing a new IMG.
ComputerFreak and I have been trying to figure this out and no solution. He said he's had the issue before but doesn't remember how to solve it and that others have had it too.
Thanks in advance for any help!! :good::good:
Click to expand...
Click to collapse
Did you reflash the 4.4.4 modems and radios, or did you just flash the 4.4.4 system image? I'm assuming that when you upgraded to 5.1, you flashed the 5.1 radios and modems.

TheSt33v said:
Did you reflash the 4.4.4 modems and radios, or did you just flash the 4.4.4 system image? I'm assuming that when you upgraded to 5.1, you flashed the 5.1 radios and modems.
Click to expand...
Click to collapse
Yeah, I flashed the 4.4.4 modems and radios. Which I'm assuming that's why it works on a stock 4.4.4 IMG. But idk why when the phone has rot access it won't work.

zacw4328 said:
Yeah, I flashed the 4.4.4 modems and radios. Which I'm assuming that's why it works on a stock 4.4.4 IMG. But idk why when the phone has rot access it won't work.
Click to expand...
Click to collapse
I'd be willing to bet that it has to do with the sensor firmware message that you got before. That message is no joke. Something involving the sensor firmware or whatever that is destroyed my last Turbo, which was luckily still somehow under warranty after everything I did to it. If I were you, I'd try flashing back to stock 4.4.4 and if you see that message, pick uninstall this time.

TheSt33v said:
I'd be willing to bet that it has to do with the sensor firmware message that you got before. That message is no joke. Something involving the sensor firmware or whatever that is destroyed my last Turbo, which was luckily still somehow under warranty after everything I did to it. If I were you, I'd try flashing back to stock 4.4.4 and if you see that message, pick uninstall this time.
Click to expand...
Click to collapse
I get it when I am on stock 4.4.4. Do you know what it does though? I need my phone.. Everything is working on stock 4.4.4 and a 5.1 IMG. Just not rooted 4.4.4.

zacw4328 said:
I get it when I am on stock 4.4.4. Do you know what it does though? I need my phone.. Everything is working on stock 4.4.4 and a 5.1 IMG. Just not rooted 4.4.4.
Click to expand...
Click to collapse
I believe it's the firmware for the various sensors on the phone (IR, gyroscope, etc.). When mine got corrupted, it affected all kinds of things on the phone. It took literally 20 minutes to boot and android OS would force close, among other things. Flashing back to stock (all images) did not solve the problem, which seems to imply that the firmware is stored on a partition that isn't flashed even during a full restore. The only thing that solved the problem was allowing the firmware to uninstall. However, when I went back to 5.1, they got corrupted again, this time beyond repair.
It doesn't sound like yours are corrupted since your problems are limited to Wi-Fi, and aren't catastrophic like mine were. You probably just have the 5.1 version still installed, which doesn't play well with the 4.4.4 images for some reason. Why the problem only appears when you have root, I have no idea. Are you using a rooted image that sets SELinux to permissive? If not, that might have something to do with it.

TheSt33v said:
I believe it's the firmware for the various sensors on the phone (IR, gyroscope, etc.). When mine got corrupted, it affected all kinds of things on the phone. It took literally 20 minutes to boot and android OS would force close, among other things. Flashing back to stock (all images) did not solve the problem, which seems to imply that the firmware is stored on a partition that isn't flashed even during a full restore. The only thing that solved the problem was allowing the firmware to uninstall. However, when I went back to 5.1, they got corrupted again, this time beyond repair.
It doesn't sound like yours are corrupted since your problems are limited to Wi-Fi, and aren't catastrophic like mine were. You probably just have the 5.1 version still installed, which doesn't play well with the 4.4.4 images for some reason. Why the problem only appears when you have root, I have no idea. Are you using a rooted image that sets SELinux to permissive? If not, that might have something to do with it.
Click to expand...
Click to collapse
If it is the literal sensors for things like IR and gyro, that would make sense as my IR sensors are not on right now on stock, non-rooted KK IMG. But I am afraid that if I do the uninstall, the phone will not be usable.
I'm not sure if the IMG sets SELinux to permissive or not. @computerfreek274 any input on that?

zacw4328 said:
If it is the literal sensors for things like IR and gyro, that would make sense as my IR sensors are not on right now on stock, non-rooted KK IMG. But I am afraid that if I do the uninstall, the phone will not be usable.
I'm not sure if the IMG sets SELinux to permissive or not. @computerfreek274 any input on that?
Click to expand...
Click to collapse
If it's CF's image, it does. I would do that uninstall if I were you. It will replace it with the factory default firmware. Up to you. If you decide to do it, flash a stock, unrooted image first, and clear cache. Maybe even factory reset if it's not too much of a pain.

TheSt33v said:
If it's CF's image, it does. I would do that uninstall if I were you. It will replace it with the factory default firmware. Up to you. If you decide to do it, flash a stock, unrooted image first, and clear cache. Maybe even factory reset if it's not too much of a pain.
Click to expand...
Click to collapse
I'm already back on a factory KK IMG and did aa few factory resets and cleared cahce multiple times. So just go ahead and do the uninstall then?

zacw4328 said:
I'm already back on a factory KK IMG and did aa few factory resets and cleared cahce multiple times. So just go ahead and do the uninstall then?
Click to expand...
Click to collapse
That's my recommendation. Just to be extra safe, leave your phone on for a while after you do it. Don't reset unless it tells you to for some reason.

TheSt33v said:
That's my recommendation. Just to be extra safe, leave your phone on for a while after you do it. Don't reset unless it tells you to for some reason.
Click to expand...
Click to collapse
Alright. I might try it out tomorrow.

Look, man. I have fxzd from LP images (cf, thest33v) over and over again. eveey single time, I did the uninstall. seems the only way you will have an issue is if you do not uninstall (revert) that piece of software. you can mod the xml file in the FXZ by removing the line "erase user data" and all will be golden. personally, I tend to back up my internal and just wipe anyway, though. run the stock fxz, do that option, and you will be good. Good luck man.

kitcostantino said:
Look, man. I have fxzd from LP images (cf, thest33v) over and over again. eveey single time, I did the uninstall. seems the only way you will have an issue is if you do not uninstall (revert) that piece of software. you can mod the xml file in the FXZ by removing the line "erase user data" and all will be golden. personally, I tend to back up my internal and just wipe anyway, though. run the stock fxz, do that option, and you will be good. Good luck man.
Click to expand...
Click to collapse
TheSt33v said:
That's my recommendation. Just to be extra safe, leave your phone on for a while after you do it. Don't reset unless it tells you to for some reason.
Click to expand...
Click to collapse
I just did the uninstall. It tried to download the 5.1 OTA(I keep force stopping MotoOTA) so I force stopped that again. After a second my phone rebooted. My IR sensors now work on stock 4.4.4. I haven't flashed a rooted 4.4.4 IMG yet to see if the WiFi will then work. I will do that sometime soon. This no root is killing me haha. Luckily I at least have a modded Pandora APK for no ads and unltd skips.
[EDIT]:
Well I still cannot use WiFi when flashing a rooted KK IMG to my phone.

zacw4328 said:
I just did the uninstall. It tried to download the 5.1 OTA(I keep force stopping MotoOTA) so I force stopped that again. After a second my phone rebooted. My IR sensors now work on stock 4.4.4. I haven't flashed a rooted 4.4.4 IMG yet to see if the WiFi will then work. I will do that sometime soon. This no root is killing me haha. Luckily I at least have a modded Pandora APK for no ads and unltd skips.
[EDIT]:
Well I still cannot use WiFi when flashing a rooted KK IMG to my phone.
Click to expand...
Click to collapse
That's bizarre. Have you been using the same rooted image every time? There might be something that's just corrupt in that image.

TheSt33v said:
That's bizarre. Have you been using the same rooted image every time? There might be something that's just corrupt in that image.
Click to expand...
Click to collapse
I've tried two different ones. They worked fine before I went to the rooted 5.1 img.