Have a Verizon S9 that is bootlooping then go to the screen in the picture after running the Pie update. Has anyone else had this issue? Is giving an authentication error in Odin when trying to flash.
Had an S9+ last week that did the same, flashing firmware with Odin didn't resolve that one, don't want to wipe it.
Related
After unboxing my new nexus it downloaded an update to Android 4.3 (probably the new patch to the OS). It gets as far as rebooting then when applying the update I get an Error and the Android laying on its back... A reboot brings me back to life however still with the old ROM. Has anyone else experienced this or can tell me how I can fix it? I have tried resetting the device back to how I got it but the problem still persists. Any help is appreciated.
if you are totally stock then you are probably suffering from the corrupt /system issue.
Try flashing factory images using this technique:
http://forum.xda-developers.com/showthread.php?p=44888268#post44888268
Got my Note 4 rooted it right away with no issues been running smoothly for a week or so. This weekend it has just got into a bootloop several times, the only thing I have been able to do is wipe data and start over. I mean I have Titanium Backup of all the apps but it is still a hassle. The only thing I have noticed is in the stock recovery it says "dm-verity failed"
I have read running a non-stock kernel will take car of this but not sure this is the issue. Has anyone else had this issue or have a solution?
It's the root. That root is causing that error to pop. Un-root your device.
I am trying to correct this issue as well for s friend who bought a used note smn910p.
It boots up
Its in the abnormal factory reset, reactivation loop i have to provide samsung account from unknown previous owner
rooted s5 smg900r4
fixed dm verity issue using kies3, updated firmware and initialization option.
rooted s5 smg900r4
I've done a lot of digging through the forum and can't find an answer, so forgive me if this is an already-answered question.
I have a T-mobile S4 with a camera stuck on the classic "updating camera firmware" error message with black screen. If I open Snapchat the front facing camera will work, but with a slight delay in projection.
Here's the thing...this has happened on two separate phones now and on both of them it happened about 48 hours after I signed into the phone with my google account. Is it possible there is some kind of malware attached to my google account?
In the newest phone I have done a clean full wipe using TWRP, then Odin-flashed a full firmware package I found here on xda (recovery, OS, modem, kernel). Cache wipe and factory reset immediately after rebooting from Odin mode. Still have problem.
Have switched out known good cameras from other phones, and the phone I'm working on was functioning perfectly until I signed into it with my account. Totally stumped here, and really need some assistance.
Phone is:
M919 logic board in I337 body
Kitkat 4.4.4
Baseband: M919UVUFNH7
Kernel: 3.4.9-6281449, [email protected] #1
Build: KTU84P.M919UVUFOK3
Security software version: MDF v1.0 release 3, VPN v1.4 release 2
If anybody's got some ideas, please let me know!
Ok, no answers yet but plenty of views, so either this is an extremely rare issue that no one knows a solution for, or it's a ridiculously stupid question that everyone knows the answer to. I'm going to try and keep a log of what I'm doing with this phone in case any other rookies need assistance in the future.
So far I've flashed three different versions of stock Kitkat onto the phone....OH3, OK3 and NH7. When I flash OK3 my build number doesn't match my baseband (baseband reads NH7)...not sure what's going on there. Also, if I flash OK3 I lose my wifi....do not have this problem with other versions of firmware. Each flash is done after a full clean wipe with TWRP.
I found a thread that mentions an almost identical camera issue being caused on an M919 that was flashed with Nottache Xposed framework for AT&T phones. The OP said they could fix the issue by wiping the framework off the phone. Since my M919 motherboard is installed in an I337 body, I'm wondering if this is something related to a compatibility issue between T-Mobile and AT&T components. Best lead I've got so far.
Two posts have mentioned a fix. One says he opened Google Edition Camera Photosphere and his problem went away. He was running a different machine than mine so I haven't tried this yet, but I'm doubtful. The other user said they have only been able to solve the cam issue by installing a stock modded kernel by @jovy23. All the links I've found to this kernel are dead now, so no dice there.
I'm gonna put my M919 motherboard into an M919 body, wipe and flash stock rom again and see if somehow that does anything.
As a side note, I started getting "SIM not inserted" errors just before I began flashing different roms, and since the initial flash I've lost my SIM completely. So now I've got no camera, no SIM card being read, and sometimes losing wifi. I need this phone for work, so this is kind of sh*tty.
You cant downgrade once youve updated to OK3. The order would have to have been NH7, OH3 then OK3. It seems like mabey its not flashing correctly. Try a different odin program 3.04 3.07 3.09 are good ones. Flash it twice, untick auto reboot and manually power off and back into download mode and flash again. Dont use adv reboot menu to boot into download or it may not flash correctly. If that doesnt work I'm not sure what else to try. Good Luck
Ok, latest update for future readers...
It seems that lordodin912 is right when he says that flashing to OK3 means you can't flash backwards to a previous baseband/build. I hadn't seen that info anywhere so I didn't know about it. I'm not sure how to go about finding this kind of info on the forum but it would have been nice to know ahead of time. Anyhow...thank you for that information lordodin.
Here's where I'm at now:
-I was originally on NH7 with the camera error and sim card error. Flashed NH7 full stock after doing a full wipe and still had problems.
-Flashed OK3 full stock after full wipe and still had the problems, and also lost wifi capabilites (as in the phone wouldn't turn on wifi at all). At this point the baseband read as NH7 but the build read as OK3. I don't know why.
-Tried flashing OH3 after that (didn't know any better) and it wouldn't take. At this point wifi capabilites returned but still no cam and not reading sim card.
-Flashed OK3 again and wifi returned but still no cam and no sim. A couple hours later I powered the phone off and then back on, and Samsung then notified me of OTA updates. This update notification hadn't appeared before I manually rebooted the phone. I took the updates and now have wifi, sim card is being read, and my camera appears to be functioning properly as well. About 20 minutes or so after the updates are applied, the sim card error returned and told me to restart the phone. I did so and now the phone is reading the sim card again.
Right now my best guess is that when I was on NH7 I had accidentally made some app and update settings changes that prevented me from receiving some of the important OTA updates connected to camera and sim functioning, and this caused incompatibility between certain parts of the firmware that had been updated and others that had not. Trying to flash OH3 failed to solve the issue because I had already flashed OK3 before that and you can't go backwards from OK3. I don't know why the initial OK3 flash failed to fix anything, but I'm guessing the flash just didn't take as well as I thought it did. Flashing OK3 twice in a row seems to have done the trick, I presume because it reset and updated everything so that all firmware was compatible with itself.
I don't know how this could have happened (I try to be very careful about what I freeze and uninstall), but it's the most likely culprit because after flashing the latest firmware manually (twice) and allowing OTA updates my phone returns to proper function. Why OK3 didn't work correctly at first is beyond me....I don't see why it should have taken a few hours or a second reboot for OK3 to begin offering updates but whatever.
I'm doubtful that the camera will continue to work after the next 48 hours, but we'll see. I'll report back in with what happens after a few days go by.
Leaving an update here as I said I would.
For two months the phone has been functioning properly. Camera, sim and wifi have all been good. About one week ago my camera started acting glitchy again and then stopped working. The problem is the same as before- upon opening camera app the screen is black with a message saying "updating camera firmware", then nothing happens. This occurred around the same time I started using google hangouts frequently...don't know if that is related to the issue or not.
Yesterday the phone began showing the error message about sim card not being read, and then today it stopped reading the card altogether.
I repeated the same procedure that seemed to fix these problems two months ago and it hasn't done the trick. Full clean wipe of phone using TWRP, then installation of Chainfire's Autoroot, then flashed OK3 stock firmware twice with battery pulls between installations. Factory reset immediately after install of stock ROM. When connecting to wifi, no OTA updates appear. Camera not functioning, sim card not being read.
Phone shows baseband and build number are matching. I have no ****ing idea what the problem is with this phone. Beyond frustrated.
Anyhow, I'll keep updates going as long as I am working with this thing, maybe it'll help someone later. Anyone knows anything that could help, feel free to chime in.
Hey, I have a question.
I've encountered something kind of strange with this device. I've been running Android P with the December 2018 security patch, rooted with Magisk. I've never encountered any problems with it so far except for a few bootloops I've got for deleting some modules in Magisk.
One day I decided to restart my phone because it was kind of laggy and so far so good it was booting. It showed me the Xiaomi logo and then it asked for the pattern to start Android. I entered the pattern and it just got into bootloop. (I've gotten bootloops before but it never got to the point where it shows me the logo and asks for pattern). I don't know what caused the bootloop because lately I haven't been messing with Magisk. However I thought it was a good idea to get into recovery and factory reset it (this has gotten me out of bootloops before so I gave it a try). After the reset it started to bootloop again, I just restarted it and it worked out just fine. I set up my phone, obviously root was gone because of the reset but I realized my phone's gotten updated to the March 2019 security patch. This was quite a surprise because I've been trying to update it and nothing seemed to work. (I tried updating it once by reflashing the original firmware with MiFlash, it was version 10.0.2.0, and before rooting it to install the security updates, they were just failing for no reason because there was no root on the phone).
So do you guys have any idea why my phone got into bootloop out of a sudden? And also why did the update successfully got installed after the factory reset?
Merky_21 said:
Hey, I have a question.
I've encountered something kind of strange with this device. I've been running Android P with the December 2018 security patch, rooted with Magisk. I've never encountered any problems with it so far except for a few bootloops I've got for deleting some modules in Magisk.
One day I decided to restart my phone because it was kind of laggy and so far so good it was booting. It showed me the Xiaomi logo and then it asked for the pattern to start Android. I entered the pattern and it just got into bootloop. (I've gotten bootloops before but it never got to the point where it shows me the logo and asks for pattern). I don't know what caused the bootloop because lately I haven't been messing with Magisk. However I thought it was a good idea to get into recovery and factory reset it (this has gotten me out of bootloops before so I gave it a try). After the reset it started to bootloop again, I just restarted it and it worked out just fine. I set up my phone, obviously root was gone because of the reset but I realized my phone's gotten updated to the March 2019 security patch. This was quite a surprise because I've been trying to update it and nothing seemed to work. (I tried updating it once by reflashing the original firmware with MiFlash, it was version 10.0.2.0, and before rooting it to install the security updates, they were just failing for no reason because there was no root on the phone).
So do you guys have any idea why my phone got into bootloop out of a sudden? And also why did the update successfully got installed after the factory reset?
Click to expand...
Click to collapse
You want help without logs? This is a developers site not Magic kingdom!
My mom has had a z2 force for almost 2 years...no issues, now all of a sudden data and wifi are gone and the phone doesn't have an IMEI. Seemingly after an ota update. As it's already old o figured I'd try to flash a rom to fix. I've tried returning to stock with the most recent flash all, the last flash all, tried installing lineage, tried installing 10 potato...nothing is working! Anything else I can try to get this working again???
I also tried to run other flashalls from xda, but didn't see a .bat file in the zip file....only a flash file...is there something else I'm missing? Sorry I'm not really proficient in motos
Mom wasn't dabbling in the dark arts known as pie was she? If not then you should be able to flash the latest TMO firmware then do a factory reset from recovery to restore the baseband.
She was still on Oreo when everything happened .....I attempted to flash the latest firmware, but still no luck...that's when I tried to install a pie rom---no luck there either
Draztik31 said:
She was still on Oreo when everything happened .....I attempted to flash the latest firmware, but still no luck...that's when I tried to install a pie rom---no luck there either
Click to expand...
Click to collapse
The trick to restoring baseband is the factory reset from recovery, not a reset from settings or anything else. As for trying to flash a pie rom, hopefully it was just a rom and not a pie firmware. If anything took from a pie firmware you might be sol.
It was just a rom, no pie firmware at all. I tried restarting from recovery and everything to no avail...is there a specific flashall you would recommend? I tried both the March and August T-Mobile ones...don't know if anyone has had success with a different one?