I've had my N1 rooted pretty much since day one. Installing Froyo (at the time) wasn't as smooth as I have come to except of Google products, since the OTA updates wouldn't install and I needed to use repackaged versions. Recently my phone started nagging me to install 2.2.1. I got fed up and finally re-flashed the stock recovery image (I didn't restore anything else).
Ever since, I haven't been promoted to install the the update. Additionally, trying to update manually (using the original file) resulted in an android guy and an exclamation mark - but nothing further.
From my understanding, as long as you have the stock recovery, you should be able to flash original packages. Am I mistaking?
UPDATE: So the update was pushed to my phone again. After clicking install, the phone rebooted and the update started installing. At some point however, it froze with the android guy and an exclamation point development. I had to remove the battery to reboot.
Was re-flashing the recover image not enough?
I believe you have to be on stock recovery and stock rom.
I believe I'm on both. I cant get a checkin to indicate that there is an update. Is that normal?
I'm in the same boat but can't even reflash the original rom through vol- power.
In on this!
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!!!
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.
I need some help. I woke up this morning and my phone will not stay powered on. It will boot but after about 3 minutes it will notify me that it's shutting down and then start up again and repeat the process. I'm rooted on 4.4. I'm thinking maybe my phone tried to automatically update me with the 4.4.2 update, but it doesn't seem like it. I can't seem to find the thread where it goes through deleting the update file. But other than that, I don't know what else it could be.
kashtrey said:
I need some help. I woke up this morning and my phone will not stay powered on. It will boot but after about 3 minutes it will notify me that it's shutting down and then start up again and repeat the process. I'm rooted on 4.4. I'm thinking maybe my phone tried to automatically update me with the 4.4.2 update, but it doesn't seem like it. I can't seem to find the thread where it goes through deleting the update file. But other than that, I don't know what else it could be.
Click to expand...
Click to collapse
When I tried to update to 4.4 rooted I had this issue. I went from stock 4.2.2(shipped) to 4.4. I had to downgrade to 4.2.2(camera update). Then when I rooted up to 4.4 I had the problem you had. I had to use RSD lite to reflash(i guess is the correct term) 4.2.2 then update to 4.4 as it didn't download 4.4 correctly the first time.
So it may have tried to update, but if it didn't download the update fully could be the problem.
Boot into recovery and clear cache, that should clear any pending ota until it downloads again.
you can freeze the moto-ota apk to prevent it from downloading.
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