Related
Rooted/Flashed my phone a long time. Constant bugs and errors. I really don't remember what all I did but I think I almost have it completely unrooted and back to stock. However, I can't update OTA. I've reflashed using this file, http://forum.xda-developers.com/showthread.php?t=2658486. Fixed just about all my issues and I actually have a lot of space on my phone. When I try to do the OTA Update, it doesn't install the update. Once it boots into recovery mode to install the update it gives an error. Can someone help my to 100% fully get my phone back to stock and be able to install OTA updates? I'm clueless.
First, did the 4.4.2 ota fail after a certain percentage? If so you may actually be partially updated already. If so, flashing MJB firmware/bootloader will hard brick.
Install and open Terminal Emulator and enter this:
getprop ro.bootloader
If it says MJB, you are still on 4.3 and can refresh that. If it says NE4, do not flash MJB!
If you can still flash MJB, there is a thread in General (I think that's where) that has the Odin flashable firmware package. Flash that with Odin and factory reset. Then try the OTA.
Factory resetting with stock recovery installed will wipe internal sd card, so back up first!
There are also a few threads in General that can help you update if the OTA continues to fail.
I'm unrooted. At least im pretty sure of that. I cant run superu anumore and root checker says im not rooted. Can I still access the terminal without being rooted. I know I had clockeork mod recovery. I also had used cyanogen mod at one point. Now I have the stock recovery but when I boot into recovery I get an error. I will post the error and install percentage as soon as the ota update downloads.
Yes, you can still run getprop w/o root. Just install terminal emulator by jackpal from the play store.
Yeah it said I747UCUEMJB. Like I said my recovery gives me an error. When I try flashing at all with odin it fails. Trying to install the ota update now. After it fails ill give the error recovery gives me. OTA update fails at 24%
Ok, booting into Android system recovery gives me a no command error than it shows the list of options. When I go to reboot system now, it gives me a no command error as well. Download mode used to give me an error, might only show up when attempting to flash something. However, these are the details of my ODIN Mode right now.
Product Name: SGH-I747
Custom Binary Download: Yes (1 Counts)
Current Binary Custom
System Status: Custom
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit: 1
BOOTLOADER RP SWREV: 2
When you try to flash the firmware with Odin, what does it say in the message box?
Have you tried flashing TWRP via Odin?
A lot of people seem to be having issues with the OTA failing at 20-something percent. No idea why though. I know some found that their firmware was partially updated afterwards though, which is why they couldn't flash with Odin. Need to know what odin says about the failure to know for sure though.
You might need to factory reset btw.
I've already did a factory reset when I flashed this latest rom from that thread I posted.
Point me in the right direction of the firmware I need. I've got AT&T btw.
Try MJB firmware again. Im assuming that's what you tried to flash with odin earlier right? When/if it fails again, copy the text from the message box and paste it here.
So you want me to try flashing using Odin with that firmware I provided in that link? Like I said, ODIN on the pc gives me an error. I'll provide the error later when I get off work. Before I just put the firmware on my sd card, went into refovery mode and installed it from there.
From what I can see that is for flashing in recovery only. Of in only flashes .tar and .tar.md5 files.
This is the stock MJB firmware you can use in Odin:
http://www.androidfilehost.com/?fid=23329332407590581
Its from enewman17 in his how to update thread here (step 4):
http://forum.xda-developers.com/showthread.php?p=53563776
If you still want to update to 4.4.2, that thread has had a pretty good success rate from what I've seen.
Let me know if you have any ither questions about this.
I'll try ut as soon as I get home from work and posy my results. Thanks for the help so far!
Wow I think one of the reasons I couldn't use ODIN after trying to unroot, is because I never had turned on USB Debugging mode. You wanted me to just go through Step 4 for right now right? Just to get back to stock 4.3 AT&T S3 like right out the box?
Thanks so much Doc. After following step 4 on that thread I was able to Ota update!
DocHoliday77 said:
From what I can see that is for flashing in recovery only. Of in only flashes .tar and .tar.md5 files.
This is the stock MJB firmware you can use in Odin:
http://www.androidfilehost.com/?fid=23329332407590581
Its from enewman17 in his how to update thread here (step 4):
http://forum.xda-developers.com/showthread.php?p=53563776
If you still want to update to 4.4.2, that thread has had a pretty good success rate from what I've seen.
Let me know if you have any ither questions about this.
Click to expand...
Click to collapse
Been using my newly updated S3 and now the Touchwiz Home stops on startup and resets my default app settings repeatedly. Not sure what's the deal, tried suggestions on diff sites and am trying a factory restore, wipe date, and wipe cache partition. Any clue how to fix this?
PS: Seen in Android System Recovery it says KOT49H.I747UFNE4. Should that be I747UCEMJB since that's what mine is and recovery still gives me no command when I start it up?
You said you had updated with the OTA so NE4 would be correct.
As for recovery, if you want to keep stock recovery, enewman17 has it available in one of his threads (in development section I think). Redland that by itself and it ought to be good to go.
Otherwise, use Odin to flash TWRP recovery.
Factory reset should take care of the launcher/home issue you mentioned. You may not be able to though since it sounds like recovery is corrupted. Fix recovery as I said above and then try the reset.
If you factory reset with stock recovery installed, it will wipe your internal sd card. With custom recovery it will not.
You could also try clearing data for Touchwiz Home in application management.
I am having issues updating OTA too. It gets to 100% and then says my phone will reboot in 5 seconds, then it reboots and some at&t logo with a % counter comes up, that gets to 100% then it reboots into Android and it still says 4.3...what am I doing wrong? Anyone have any advice? Many thanks if so.
Thats a new one for me...how exactly are you going about updating? Are you using one of the threads here? Have you recently modified anything?
DocHoliday77 said:
Thats a new one for me...how exactly are you going about updating? Are you using one of the threads here? Have you recently modified anything?
Click to expand...
Click to collapse
I am trying to update by going to settings --> more --> about device --> software update. Not using a thread, no. I was rooted and uninstalled google books and newsstand then unrooted and did a factory reset in stock recovery because I found out that if you are rooted the OTA update won't take. I am 100% bone stock now except for the 2 bloatware apps I uninstalled. I have since reinstalled them via the play store , but I hear they need to be system apps?
They do, but they also need to be the same versions that were originally included. If you get them from the store they'll be updated and will cause the ota to fail.
I was trying to update my firmware in the hope of using one of the custom roms available, and my M8 is now stuck on the boot screen and will not go further. Here is what I did:
Currently have a GPE M8. It is S-Off, SuperCID, Unlocked, and converted to T-Mobile (Sense) stock rom.
Was on 1.54.401.5 firmware attempting to update to a 2.22.xxx firmware.
The exact process I used was:
Boot into fastboot
fastboot oem rebootRUU
fastboot flash zip firmware.zip twice (successful after 2nd time)
fastboot reboot
After this, it will not go past the default boot screen.
I then tried to revert back to 1.54.401.5 firmware using the same process. This time, it will reboot once after the stock boot screen and go into recovery. Still unable to get back to the OS.
What am I doing wrong and how do I get out of it? :crying:
[edit] I tried to install a newer firmware again, as well as a couple of different roms. No luck, still getting stuck at the boot screen or automatically rebooting into recovery. Had to resort to using the T-Mobile RUU to get back a working phone. I still don't know what went wrong with my attempt at trying to install a new firmware or rom. [/edit]
The firmware includes an incompatible kernel, just flash a different kernel or re-install the rom and you should be alright
thom109 said:
The firmware includes an incompatible kernel, just flash a different kernel or re-install the rom and you should be alright
Click to expand...
Click to collapse
I did try to install a couple different roms after installing the firmware, but either the rom fails to install, or even if it appears to install, it still gets stuck at the white boot screen.
I also don't understand how the kernal can be incompatible. In all the threads I've gone through of the custom roms (mainly ARHD), it's always the same story. "Just flash the 2.22.xxxx firmware and you'll be fine". In the threads specifically related to the updated roms, it's the same thing, just flash and go, regardless if you are on stock and some other rom. I, and only a few others, seem to have no luck actually flashing the 2.22.xxxx firmware.
Mpegger said:
I did try to install a could different roms after installing the firmware, but either the rom fails to install, or even if it appears to install, it still gets stuck at the white boot screen.
I also don't understand how the kernal can be incompatible. In all the threads I've gone through of the custom roms (mainly ARHD), it's always the same story. "Just flash the 2.22.xxxx firmware and you'll be fine". In the threads specifically related to the updated roms, it's the same thing, just flash and go, regardless if you are on stock and some other rom. I, and only a few others, seem to have no luck actually flashing the 2.22.xxxx firmware.
Click to expand...
Click to collapse
hmm weird, I have no idea what's going on here ... I had some issues after flashing firmware but new kernel and it worked just fine.
Maybe something in this thread could help you? http://forum.xda-developers.com/htc-one-m8/development/firmware-flashing-panic-attacks-t2824048
thom109 said:
hmm weird, I have no idea what's going on here ... I had some issues after flashing firmware but new kernel and it worked just fine.
Maybe something in this thread could help you? http://forum.xda-developers.com/htc-one-m8/development/firmware-flashing-panic-attacks-t2824048
Click to expand...
Click to collapse
Tried that too, same issue. Tried with the phone locked and unlocked, manually with fastboot and automatically via external SDcard (as in that thread), installed SkyDragon, ARHD, and stock after installing the firmware, and it still fails with the same issue. Even trying to revert back to the current firmware after trying to install 2.22.xxx results in the same problem, and the only way to fix it is with the RUU.
I think what I'll try next is to install the rom first, then try to install the firmware. Maybe in that order it will work. But it still doesn't make much sense that I can't install the newer firmware when so many others have had no problems.
Mpegger said:
Tried that too, same issue. Tried with the phone locked and unlocked, manually with fastboot and automatically via external SDcard (as in that thread), installed SkyDragon, ARHD, and stock after installing the firmware, and it still fails with the same issue. Even trying to revert back to the current firmware after trying to install 2.22.xxx results in the same problem, and the only way to fix it is with the RUU.
I think what I'll try next is to install the rom first, then try to install the firmware. Maybe in that order it will work. But it still doesn't make much sense that I can't install the newer firmware when so many others have had no problems.
Click to expand...
Click to collapse
always install rom first then firmware
Was trying to get the phone back to stock so I can upgrade. I followed the instructions on the How to Return a Device Back to Stock thread, downloaded the stock TAR, rebooted and tried to boot into recovery but it would not let me. I then tried to boot into the device as normal and now I have a screen with the message Firmware upgrade encountered an issue, Please select recovery mode in Kies & try again. Any suggestions? I downloaded and tried but cannot connect via Kies 2.6.. I can still get into the device via ODIN. Suggestions?
What firmware did you use to flash? Flash NH7 if you haven't
A little back-story and a possible solution.
demonr6 said:
Was trying to get the phone back to stock so I can upgrade. I followed the instructions on the How to Return a Device Back to Stock thread, downloaded the stock TAR, rebooted and tried to boot into recovery but it would not let me. I then tried to boot into the device as normal and now I have a screen with the message Firmware upgrade encountered an issue, Please select recovery mode in Kies & try again. Any suggestions? I downloaded and tried but cannot connect via Kies 2.6.. I can still get into the device via ODIN. Suggestions?
Click to expand...
Click to collapse
I've never updated my S4 past the MDL firmware. I encountered this problem a few months back when I wanted to revert back to 100% stock MDL. I had updated my baseband/modem though to NB4, yet still obviously had the MDL bootloader. I was scared to death that I had bricked my phone because nothing I did would let me boot past that screen. I couldn't get to recovery, normal boot, nothing... the phone would just automatically go to that screen: Firmware upgrade encountered an issue.
What I did was simply revert my baseband/modem back to MDL. Once that was done successfully I was able to flash the MDL firmware again and booted right up. If this might be your issue, you will have to know which baseband/modem you were using and which bootloader version you were running before you attempted to flash stock. It should go without saying that the main idea here is to have your baseband and bootloader versions match before flashing the firmware in Odin.
Seems a little odd to me as the stock Odin-flashable firmware includes the modems and all... I'm just passing along what worked for me when I had that problem.
lordcheeto03 said:
I've never updated my S4 past the MDL firmware. I encountered this problem a few months back when I wanted to revert back to 100% stock MDL. I had updated my baseband/modem though to NB4, yet still obviously had the MDL bootloader. I was scared to death that I had bricked my phone because nothing I did would let me boot past that screen. I couldn't get to recovery, normal boot, nothing... the phone would just automatically go to that screen: Firmware upgrade encountered an issue.
What I did was simply revert my baseband/modem back to MDL. Once that was done successfully I was able to flash the MDL firmware again and booted right up. If this might be your issue, you will have to know which baseband/modem you were using and which bootloader version you were running before you attempted to flash stock. It should go without saying that the main idea here is to have your baseband and bootloader versions match before flashing the firmware in Odin.
Seems a little odd to me as the stock Odin-flashable firmware includes the modems and all... I'm just passing along what worked for me when I had that problem.
Click to expand...
Click to collapse
I'll repost from another hoping this explains it as it is the only thing I can think of.. but it worked.
TLDR: installed stock TAR not stock TMO TAR, updated (stupid me) to 4.3, wrong baseband and recovery did not go back to stock using the stock TAR and the Philz Touch recovery would not have flown to return the phone. I figured it out with some help though!
Thank you, that was it. I returned it to stock after following the instructions in the how-to thread but something happened and it boned the recovery where it would reboot into the device every time. Being they need to inspect the phone and in my case they wiped it in front of me when I turned it in it had to be fixed. The device received the updates from TMO and stupid of me I installed them so it was now 4.3 hence the reason I could not install the stock 4.2 anymore. I found the stock firmware you mentioned above and installed it and it fixed it but tripped the counter. I installed the updates from TMO and it was enough to pass inspection. I was able to go into recovery at the store, show the clerk while he was dicking around with the paperwork for the Note I was about to buy. I reached over, showed him "look here it is in recovery and here is wipe data factory reset okay?" and wiped it. He muttered okay thanks or something like that and we were golden. Heck if he could have read the counter anyways it is so flipping tiny.
Thanks for the suggestions!
Okay so have a I747 AT&T Galaxy S3. Had CM13 running fine on NE4 baseband. Decided to upgrade baseband and flashed NJ1 then NJ2, rebooted and everything was fine.
Well then I decided to check out a different ROM, and tried installing these via recovery and then I get stuck on that AT&T splash screen:
d2att_I747UCUFNJ2.zip (didn't work) so then d2att_I747UCUFNJ2_Deodex_Rooted_KnoxFree_Debloated.zip
I thought I was able to install those since I just upgraded my baseband, but my phone did not like it!
I also noticed that in download mode, in red there was a "warranty bit: 1", not sure if that's relevant?
So I can still get into download and recovery, but any restoring CM13 from backups or return to stock results in a bootloop. How can I get CM13 back?
Can I flash back to stock with Odin and start over to fix this? Is this the file I should use?= I747UCDLK3_I747ATTDLK3_ATT.zip or this one?= I747UCUEMJB.zip
Or will those brick my device since I'm quite certain I'm on NJ2 firmware?
OR should i try reinstalling a certain CM version with certain gapps?
What can I do? I'm really freaking out here, everything I have is on 2fa! Please help!
Was the bootloader updated when the baseband was updated?
turns out im just an idiot and installed the wrong gapps.
I updated to Q by flashing via fastboot. I am not happy with it. I tried to downgrade by flashing a stock image via fastboot but I get an error saying the wrong BL is installed. It's asking for an older version.
How can I flash this older version? Or, better yet, how can I flash a stock image or custom ROM of Android Pie without encountering an error?
I've searched and everything I tried from what I found still results in the version error.
If I remember correctly, you'll need to flash using the flash-all script so that it overwrites everything.
supaneko said:
I updated to Q by flashing via fastboot. I am not happy with it. I tried to downgrade by flashing a stock image via fastboot but I get an error saying the wrong BL is installed. It's asking for an older version.
How can I flash this older version? Or, better yet, how can I flash a stock image or custom ROM of Android Pie without encountering an error?
I've searched and everything I tried from what I found still results in the version error.
Click to expand...
Click to collapse
You can only downgrade with an unlocked bootloader. Downgrading without can brick your p3xl. After unlocking you can flash the 9.0 firmware and you won't have any bootloader or partition errors it will just work.