long story short. I tried to flash a newer updated copy of SuperSU or whatever to get root back after updating to 4.0.4 earlier this week.
Once I did that I was able to get back into the operating system and run Root Checker. Everything passed. I then tried WiFi tether and it kind of locked up on me for a bit. then I was able to stop it and exit out of it. I Force closed the programs. Life was good.
For whatever reason I restarted the tablet. once I did that I was stuck on the Samsung screen for at least 15 minutes.
I then tried to re-run root file and then the new updated SuperSU. Then everything went all to hell.
Then I get a message that says
"Firmware upgrade encountered an issue. Please select recovery mode from Kies & try again."
Now I can not boot into anything but recovery...
I am able to with that message on the screen, connect to Odin and proceed to run the "factory" restore. However it has been sitting at what I would assume is about 5% or so for a long time. at least 20-30 minutes. Should this take this long?
And is there anything else I can do to do a restore? I am fairly new to this tablet and I use it for work and of course I have a super full day of work tomorrow and really got to get this thing back up and going.
Related
Here is the story so far. I rooted my phone and got a little carefree with Titanium back up and uninstalled some essential gapps. I was able to get into download mode and am using LGNPST to restore my device to factory settings. The issue is I keep running into is I am getting stuck at 85%, which I know is a common error point in the LGNPST process. I turn the phone off and power it back on while keeping the phone plugged in and the phone reboots. After a few minutes I finally get an error message saying the following
Process:Upgrade_Masterbin
SubProc: Masterbin Download
Cause: Error: Fail opening port
Any kind of help would be much appreciated
Thanks!
Desconect the phone and do a hard reset.
Alright that seemed to get my farther. After a hard reset I was able to catch a glimpse of the phone setup before the phone immediately shut off. I am going to try and re install stock firmware through LGNPST again to see if this will work finally. Thanks!
Instal the 11c update anf root with the universal root.
So I have a S4 i9545 for Verizon. It was on 4.2.2 rooted and I upgraded using Fireflash with I545_OC1_Stock_DeOdexed_ROMwNK4_BL.zip. Everything seemed fine so I was using Titanium back up to remove the bloatware and then my battery died. When I charged it and booted up it got to the Verizon screen and hung there. I reset and tried several more times. I tried to use odin and flash a stock ROM SCH-I545_VZW_1_20140330160240_yni63xq6zh and I also tried one more. Odin gave a an error and failed. I then tried going into the boot loder and flash the I545_OC1_Stock_DeOdexed_ROMwNK4_BL.zip. Not sure if this was foolish or not. When I booted up I got to a black screen and there was a voice talking, maybe some sort of training, but I couldn't do anything.
If anyone can point me in the right direction on how to unbrick my S4 I would appreciate it. I know I screwed up.
Right now when I turn on the phone it says firmware upgrade encountered an issue. Please select recovery mode in kies and try again. I tried connected to my computer and opening kies but it doesn't find it.
Try disconnecting your phone, completely closing Kies, then re-launching it with your phone still disconnected. Then click Tools > Firmware Upgrade and Initialization then follow the prompts
Please please please help!!! Lg G3 model sv985 running lollipop 5.1.1
So one day I wanted to connect my ps3 controller to my ps4. I found out how to do it but it requested my phone to be rooted. So after a couple of days trying to root my phone I finally found a solutions. I used the kind root method. After getting root access you are required to put your phone into recover mode. The problem I am having is when I go into recovery mode all I get is an error message stating "secure boot loading error 1003" then proceeds to go to a black screen with the notifications lights blinking red and blue. Then I have to take my battery out and reboot my phone that way. It starts up normal but twrp does the same process as do other rebooting apps. Today I got the update to install marshmallow 6.0 and it also needs to go into recovery mode. When I try to reboot the same black screen appears. I finally came to agreements with myself to just get rid of root and go back to kitkat then upload 6.0. My problem here is the program you need to download to switch back requires a password and user name. Which according to the steps, you just download a file then switch it to the program and shouldn't need a password or username anymore. Every time it fails. Sorry kinda spaced what it's called. (it's the program needed to downgrade sorry I forgot the name) I've been at this for about a month and now my phone won't even get notifications. The root totally messed it up. I wouldn't mind if I could get super su to work. Basically my question is, how can I get around the secure boot error 1003 to get into recovery mode. Even if I just take my root loses and uprgrade to 6.0. All I need is to reboot, it shouldn't be so hard. All the YouTube videos I have found are all in Spanish that get good reviews but I can't understand most of the conversations. Thank you to the XDA for everything you guys do. Your awesome!
So I was having so many issues with my rooted phone crashing on jasmineRom 7.0 I thought maybe an OTA update had made it through and started downloading. No matter what I was doing the screen would turn blue and then restart. Sometimes it would crash blue again during reboot, and sometimes it would crash and then show the green demigod crash screen. So I researched flashing the .tot files to go back to stock. KDZ I didn't care for because it still showed the phone as modified software, and I wanted full stock so I could use the extended warranty with Verizon if need be. I eventually got the .tot method to work and everything was hunky dory, and showing stock. I upgraded all the way to marshmallow and decided I love every bit of it, but I couldn't figure out how to get my contacts and stuff off titanium backup without root. So I figured, "well roots not the problem if an OTA tried to download it just means I missed a setting or something". So I rooted again. No issues, I reinstalled JasmineRom 9.1 this time. Eventually it started crashing again, although this time I followed absolutely every guide I could find on disabling OTA. So I thought, "Great it's Jasmine" and I really wanted Marshmallow anyway so I followed xdabbeb's guide for getting the 35b bootstack on my phone, worked great no issues, and then I installed xdabbeb's firmware, combined with Edor's debloating zips. Everything was working great! I had no issues, I backed up just my apps, and some data, and reinstalled others and everything was great and working fine, and the phone was still official, no OTA's getting through. That was almost a full week ago. Yesterday I woke up and the phone wouldn't turn on. I took the battery out and put it back in and the phone came on, but then crashed with the blue screen again. So I thought great I guess I'll put it back to stock and use the warranty. By this time though I was having trouble getting it to load past the LG screen. I finally got it into TWRP and was able to wipe everything (except SD card) and then I stuck it in download mode and went to install the .tot files. Weeeeelllll, long story short, it crashed during download mode install with the LG Flash Tool. So now the phone gets stuck in download mode everytime I pull the battery and power it on. And crashes again every time I go to install anything. KDZ doesn't work, the flash tool says it can't communicate with the phone, because it crashes. And LG Flash Tool for the .tot files seems to crash everything it loads the modem, or consistently crashes on LAF:bin_user_mode. So I have no idea. At the moment it just looks like my phone is all funky defective, and Verizon may take it back and give me a new one so I'm going to try that. HOWEVER! If anyone has any ideas on what the issue is or what else can be done, I still want to hear it. Feel free to post
Also I've tried updated drivers for the computer, I've tried rolling back drivers, I've tried different KDZ files, I've tried the LGUP8974.dll fix where you flash that in flash tools and then flash the vs985 dll, which is what I had to do to get it back to stock the first time. I've tried everything I could find online except anything to do with fast boot and shorting the pins. Which I haven't tried because I can still access download mode it just seems to be stuck in download mode. Those methods from what I understand are for hard bricking, and for people who's phones don't turn on at all. Although if Verizon won't help I may try one of the laf recovery methods.
Thanks!
Hello. I have a Sprint M9. It had been acting flaking lately (I would try to install the latest update, and it would reboot without installing and report that the phone had recovered from an error and ask if I wanted to send to HTC). Tonight, I was trying to use DLNA to play video from my phone to my TV, I was in settings and gave DLNA permission to access my storage. As soon as I did that the phone rebooted without warning and continues in a loop of displaying the HTC logo, then restarting over and over.
I can get into bootloader, download, and recovery mode by holding down the volume down key. I have tried Wipe Cache Partition and Wipe Data, but the phone still will not get out of the loop.
Phone is stock. I have never tried to root or disable S-on or load my own recovery.
What, if anything, can I do to get my phone working again?
Just tried doing what I think is called RUU? I downloaded the .exe from this site:
http://www.htc.com/us/support/htc-one-m9-sprint/news/
It found my phone, and rebooted into download mode. It tried to flash my rom, but shortly after trying to send the file (progress bar jumped from 0% to 100% in 1/2 second). The utility gives me a Error [155]: Unknown Error. I've tried a couple times and get the same problem each time.
The utility reports I have version 3.41.651.21 and tries to flash to 3.41.651.31
Great, now it is telling me my software has been modified. (it hasn't) The only things I've done is run the RUU and reboot into recover to clear cache/data. Bad NAND?
Well, found out why RUU wouldn't work. Low battery. Apparently it ate a lot more battery than I realized while it was in the reboot cycle. Tried manually flashing the firmware and fastboot told me the reason it was failing. C'mon HTC, if the CLI can tell me there's not enough battery to proceed, your GUI utility should be able to as well.
Still leads to the question of:
- Why did this happen in the first place
- This is actually the second time I've had a problem with OTA, with the phone thinking the system had been modified. So either the OTA failing somehow modified the system before failing, or there's a bigger issue afoot. (as noted above, this phone is stock, I've never tried to root, install a custom recovery, or anything else)
shawndoc said:
Still leads to the question of:
- Why did this happen in the first place
- This is actually the second time I've had a problem with OTA, with the phone thinking the system had been modified. So either the OTA failing somehow modified the system before failing, or there's a bigger issue afoot. (as noted above, this phone is stock, I've never tried to root, install a custom recovery, or anything else)
Click to expand...
Click to collapse
Same thing happened to me. The update that Sprint pushed last Wednesday completely bricked my HTC One M9. Same failure mode that you experienced. Sprint technical center was unable to do anything with it, so they are replacing it, allegedly ( been waiting a week for said replacement ).
I talked to a few other people who had the same problem, by the way. Someone in Sprint's QA team completely dropped the ball on this update.
Well, even after RUU it says my system has been modified and the phone will no longer boot into recovery. Just errors back to Download with the message that recovery couldn't launch.
I've also now got intermittent problems with the com.android.settings crashing. So I've thrown in the towel and purchased my first non HTC phone since the original Windows Mobile days.
Hello there. The same problem has come to my mind and the phone has been off for almost a month. Did you solve your problem? If you could solve it, how did you do it? I sent you above the original stock rom set. Nothing changed. The phone developer rum works. but the original 0pja200 rom is starting again.
my phone soft bricked, unlocked bootloader and S-off. Whether it is possible without blocking bootloader flashed RUU rom?