Kitkat 4.4.2 is now available on Galaxy S III mini (ATT) G730A.
Just came through ATT OTA update today, but was officially released on 8/27/14
From ATT:
"Update summary
On August 27, 2014, AT&T and Samsung released a software update for the Samsung Galaxy S III mini (SM-G730A). This software package updates the OS to Android 4.4.2 (Kit Kat). The update file is 700 MB, and is available for download via Wi-Fi only."
Official new versions:
Android version: 4.4.2
Baseband version: G730AUCUBNG3
Build number: KOT49H.G730AUCUBNG3
Official Link (replace "[dot]" with "."). Sorry for being a newb....
www[dot]att[dot]com/esupport/softwareUpdateArticle.jsp?sid=KB424695
Hopefully saferoot or some other method will work with this update. :fingers-crossed:
I saw a software update being download through my phone which was killing my battery. I called Samsung to see what was going on.
I'm pretty sure I weirded out the Samsung rep on the phone because I was ECSTATIC when she said "well, it looks like you should actually be running 4.4.2"
jakitgt said:
Kitkat 4.4.2 is now available on Galaxy S III mini (ATT) G730A.
Just came through ATT OTA update today, but was officially released on 8/27/14
From ATT:
"Update summary
On August 27, 2014, AT&T and Samsung released a software update for the Samsung Galaxy S III mini (SM-G730A). This software package updates the OS to Android 4.4.2 (Kit Kat). The update file is 700 MB, and is available for download via Wi-Fi only."
Official new versions:
Android version: 4.4.2
Baseband version: G730AUCUBNG3
Build number: KOT49H.G730AUCUBNG3
Official Link (replace "[dot]" with "."). Sorry for being a newb....
www[dot]att[dot]com/esupport/softwareUpdateArticle.jsp?sid=KB424695
Click to expand...
Click to collapse
In S3 Mini I8190 want!
None of the root procedures that worked for 4.2.2 will work for 4.4.2 :crying:
rdk2k said:
None of the root procedures that worked for 4.2.2 will work for 4.4.2 :crying:
Click to expand...
Click to collapse
Root needs to be figured out asap then haha! Just glad they kept their word and finally updated it though! :good::laugh::highfive:
My heart broken Maybe GT-I8190 ? porting etc.
MehmetAliCan said:
My heart broken Maybe GT-I8190 ? porting etc.
Click to expand...
Click to collapse
If I would have known - I would have tried to capture the OTA update...
Don't Apply Update to an Encrypted Phone!!!!
I made what I think is a fatal error in applying this update...two errors, actually...
1. Didn't have contacts, texts, various docs, etc stored on internal memory backed up to the could, external computer, etc
2. Applied update before decrypting the phone (I keep it encrypted for security reasons obviously but this may have just bitten me in the butt)
So here's happened when I applied the update. First, there was no warning not to apply it to an encrypted phone (found this out from an AT&T Device Support Center technician, who also told me the update was pushed direct by Samsung and not AT&T and really did try to help me out of this jam). I selected yes to apply the update, then it prompted me for my password 2 or 3 times at it went thru the update/reboot process. No problem, right? Well when it appeared to have completed, it went back to the lock screen on bootup, I typed in my password, the green "android crypto unlock" image came on, then...nothing. screen went black and phone locked up. Restarted several times and same thing happened. Restarted in safe mode and same thing happened. Tried hooking up to my computer and accessing thru Windows and Samsung Kies...nothing. Phone connects to computer, but it isn't recognized and no access (neither before nor after typing password into phone). Went into the phone's system recovery mode and rebooted from there and same thing happened - get to unlock screen, type password, and locks. In the phone's system recovery screen, I get the following at the bottom of the screen:
#MANUAL MODE#
-- Appling Multi-CSC...
Applied the CSC-code : ATT
Successfully applied multi-CSC.
E:failed to mount /data (Invalid argument)
can't mount '/data'(Invalid argument)
E:failed to mount /data (Invalid argument)
E:Can't mount /data/log/recovery_log.txt
I have not yet done a "wipe data/factory reset" nor had AT&T wipe and reset the phone at their Device Service Center as I really really really need to recover some data that is now locked on the phone and I can't seem to get past the encryption even with password as it appears the encryption corrupted the OS update installation. Neither 3 hrs with a very helpful AT&T tech nor an hour on the phone with Samsung tech was able to get me into the phone to at least recover data. If i can just recover the data, at that point I have no problem doing a factory reset (and taking a harsh lesson learned) and rebuilding the phone. But I want to exhaust all possible options at data recovery before I go that route, and any help any of you out there can provide would be greatly appreciated. Maybe a way to extract an image of the phone's internal storage to a computer and then decrypt that image to extract the data? Maybe a way to remotely decrypt the phone's internal storage over USB connected to a computer and then extract data that way?
I asked both Samsung and AT&T if they had an FTP site or something where I could download the update to a microSD card and try re-applying the update from external storage (which at least in theory would preserve user data during the update) in the system recovery boot module but both said they couldn't do it. Which I think is BS, since that 700MB file has to come from somewhere. I'm guessing they only want the update distributed via OTA or Kies not as a separate installer package that could be easily shared.
That's about it. I'm really hoping someone can help me out of this jam, but am prepared for the worst - data loss and associated harsh lessons learned. Thanks for listening and I hope no one else out there makes the same mistake I did.
Rob
Trying to Odin back to 4.2.2 results in an error and soft bricks the phone. At least my phone is still under warranty and there are no signs of me moding the phone, so i'll be shipping it to Samsung tomorrow.
2317
Can someone please put the firmware on mega or firedrive or something im not getting the update. and SamMobile has old firmware www[dot]sammobile[dot]com/firmwares/3/?download=22911
hkjr said:
If I would have known - I would have tried to capture the OTA update...
Click to expand...
Click to collapse
If you want to go through the trouble, can you Odin back to 4.2 and grab the 4.4.2 OTA update again?
KaneVanguard said:
Can someone please put the firmware on mega or firedrive or something im not getting the update. and SamMobile has old firmware www[dot]sammobile[dot]com/firmwares/3/?download=22911
Click to expand...
Click to collapse
OTA update is downloading a zip file called /data/fota/2400258.cfg, I'll try to capture it. Hoping it doesn't delete it before I can get to it
It's the same filename as the OTA updates for other S 4.4.2 devices but I would guess not the same contents.
I have the 4.4.2 update in place but need to root my device to get rid of all the bloatware again. Anyone finding any success with root apps?
maybe towelroot?
djdevin said:
maybe towelroot?
Click to expand...
Click to collapse
Tried that one. It says my model is not currently supported.
Boo. I know towelroot is configurable, maybe another modstring will work.
Anyways here's the OTA update
https://mega.co.nz/#!r1lxzISZ!5KD71NdDu8Lj96G2mXFlbk75tQgzAZg7FEyHMEkajgA
Warning, none of the below worked for me and I had to restore
I assume this is the install process
Download OTA file
Change 2400258.cfg name to update.zip
Connect your phone to your PC and then move the update.zip file to the phone's /cache
Disconnect the phone from PC, power off the phone and then boot it in Recovery Mode.
Select the ‘Apply Update.zip’ from cache
OR
Apply update from adb
Then adb sideload 2400258.cfg from your computer
Wait until the install process is complete and then reboot your phone in normal mode.
Same as http://www.android.gs/flash-official-android-4-4-2-kk-update-for-att-galaxy-s4/ except with a different file.
rob.rossi97 said:
I made what I think is a fatal error in applying this update...two errors, actually...
1. Didn't have contacts, texts, various docs, etc stored on internal memory backed up to the could, external computer, etc
2. Applied update before decrypting the phone (I keep it encrypted for security reasons obviously but this may have just bitten me in the butt)
So here's happened when I applied the update. First, there was no warning not to apply it to an encrypted phone (found this out from an AT&T Device Support Center technician, who also told me the update was pushed direct by Samsung and not AT&T and really did try to help me out of this jam). I selected yes to apply the update, then it prompted me for my password 2 or 3 times at it went thru the update/reboot process. No problem, right? Well when it appeared to have completed, it went back to the lock screen on bootup, I typed in my password, the green "android crypto unlock" image came on, then...nothing. screen went black and phone locked up. Restarted several times and same thing happened. Restarted in safe mode and same thing happened. Tried hooking up to my computer and accessing thru Windows and Samsung Kies...nothing. Phone connects to computer, but it isn't recognized and no access (neither before nor after typing password into phone). Went into the phone's system recovery mode and rebooted from there and same thing happened - get to unlock screen, type password, and locks. In the phone's system recovery screen, I get the following at the bottom of the screen:
#MANUAL MODE#
-- Appling Multi-CSC...
Applied the CSC-code : ATT
Successfully applied multi-CSC.
E:failed to mount /data (Invalid argument)
can't mount '/data'(Invalid argument)
E:failed to mount /data (Invalid argument)
E:Can't mount /data/log/recovery_log.txt
I have not yet done a "wipe data/factory reset" nor had AT&T wipe and reset the phone at their Device Service Center as I really really really need to recover some data that is now locked on the phone and I can't seem to get past the encryption even with password as it appears the encryption corrupted the OS update installation. Neither 3 hrs with a very helpful AT&T tech nor an hour on the phone with Samsung tech was able to get me into the phone to at least recover data. If i can just recover the data, at that point I have no problem doing a factory reset (and taking a harsh lesson learned) and rebuilding the phone. But I want to exhaust all possible options at data recovery before I go that route, and any help any of you out there can provide would be greatly appreciated. Maybe a way to extract an image of the phone's internal storage to a computer and then decrypt that image to extract the data? Maybe a way to remotely decrypt the phone's internal storage over USB connected to a computer and then extract data that way?
I asked both Samsung and AT&T if they had an FTP site or something where I could download the update to a microSD card and try re-applying the update from external storage (which at least in theory would preserve user data during the update) in the system recovery boot module but both said they couldn't do it. Which I think is BS, since that 700MB file has to come from somewhere. I'm guessing they only want the update distributed via OTA or Kies not as a separate installer package that could be easily shared.
That's about it. I'm really hoping someone can help me out of this jam, but am prepared for the worst - data loss and associated harsh lessons learned. Thanks for listening and I hope no one else out there makes the same mistake I did.
Rob
Click to expand...
Click to collapse
Too late. Think I just bricked it too, OTA update failed so it probably wasn't just you.
Correction: I was able to get back to 4.2.2, I used PDA instead of Phone in ODIN. My guess is that the bootloader has to be flashed first before reverting to 4.2.2. However I did a clean wipe many times before so I'm not sure if it did that, in your case it would not be preferred.
I'm seriously sick over this bootloader BS, enough to never buy a Samsung electronic device ever again. Or deal with AT&T in any capacity ever again.
@SamsungSupport gave me a pretty good "we don't care" conversation: https://twitter.com/SamsungSupport/status/507252356657184768
djdevin said:
Too late. Think I just bricked it too, OTA update failed so it probably wasn't just you.
Correction: I was able to get back to 4.2.2, I used PDA instead of Phone in ODIN. My guess is that the bootloader has to be flashed first before reverting to 4.2.2. However I did a clean wipe many times before so I'm not sure if it did that, in your case it would not be preferred.
I'm seriously sick over this bootloader BS, enough to never buy a Samsung electronic device ever again. Or deal with AT&T in any capacity ever again.
@SamsungSupport gave me a pretty good "we don't care" conversation: https://twitter.com/SamsungSupport/status/507252356657184768
Click to expand...
Click to collapse
How did you manage that? I stupidly tried to downgrade with Odin and have a soft-brick on my hands. I've tried everything I can think of. I wish SamMobile had the 4.4.2 firmware.
Update made the phone slower and laggy. Someone needs to find a working root method
Related
For the past week I've been trying to install the NE9 update. When trying it reboots the phone and starts installing. Half way through installation the android falls on its back and fails. Then when it boots back up again it tells me that the update wasn't applied due to failure.
Prior to the update before trying I've been rooted with towelroot if thats worth mentioning.
I also tired Verizon Software Upgrade Assistant on the PC and the software tells me its up to date, not acknowledging that there is a newer firmware available.
Is there another way to "update" without flashing. I'm not really up to reinstalling and reconfiguring everything. Although I have Titanium Backup Pro.
Also if no solutions how do I get rid of this screen which pops up everyday?
You already know the answer and are trying to avoid it. Odin is the most reliable way to apply an update. OTA updates fail for numerous reasons and we couldn't begin to guess why in your case because you provided almost zero information about your phone e.g.what was the exact, verbatim error or failure message you received, have you frozen any apps, syslog, current firmware version or anything else.
We don't have your phone in front of us, so when you don't describe those crucial details, the best we could possibly do is make stabs in the dark as to what is going on.
If you do a proper backup, restoring your programs afterward shouldn't be that hard. You could probably just restore your backed up /data partition over the updated system and have most of your apps and settings restored in one swoop. Alternately, you might be able to apply the new firmware image with mobile odin pro, while leaving your existing /data partition intact.
Or disable the OTA update manager to avoid the update. Verizon likes to rename or at least append vzw to system apps, so search the Verizon forum for the name of the Verizon OTA update manager app.
.
fffft said:
You already know the answer and are trying to avoid it. Odin is the most reliable way to apply an update. OTA updates fail for numerous reasons and we couldn't begin to guess why in your case because you provided almost zero information about your phone e.g.what was the exact, verbatim error or failure message you received, have you frozen any apps, syslog, current firmware version or anything else.
We don't have your phone in front of us, so when you don't describe those crucial details, the best we could possibly do is make stabs in the dark as to what is going on.
If you do a proper backup, restoring your programs afterward shouldn't be that hard. You could probably just restore your backed up /data partition over the updated system and have most of your apps and settings restored in one swoop. Alternately, you might be able to apply the new firmware image with mobile odin pro, while leaving your existing /data partition intact.
Or disable the OTA update manager to avoid the update. Verizon likes to rename or at least append vzw to system apps, so search the Verizon forum for the name of the Verizon OTA update manager app.
.
Click to expand...
Click to collapse
I got through it. Thanks for replying. The Verizon Software Upgrade Assistant started working. I was getting ready to go into odin after I plugged in my USB cable then I noticed to the bottom right something said downloading update. The software did everything. After I swapped kernels rooted and swapped the kernal back with odin. Sorry my mind is a bit foggy I've recently came back to Android. Last time I was around was way back with the Motorola Cliq and the HTC Sensation. I really wasn't up for flashing because I had the phone for about 2 weeks and if I hit a snag then it will require a bunch of research /rant.
All is well solved.
Tuesday
306sh activated with MVNO, SA300 firmware, rooted, with TWRP recovery,
working fine for past 2 months.
For unknown reasons, it decided last friday (at home, none to low signal) to do a system update
(from SA300 to S7232). Phone - on the desk- just "dinged" and msg came up "updating
system software". I attempted to cancel, but it didn't respond. Less than a minute later, "Update Successful" msg. Didn't reboot, anything, settings showed S7232 firmware. (SA300 before,
i had done my weekly backup earlier that morning).
Since then, phone constantly reboots at the "Aquos" screen; after an average 8 hours of rebooting, it will boot to setup, the talking setup screen. Works perfect for about an hour then rebooting starts again. Let battery die last nite, tried again this am - same thing rebooting.
TWRP backups don't fix problem- weekly backup, i have 6 i've tried, factory reset doesn't fix, if i try to Software Update, it checks, tells me, "up to date".
I turn on wi-fi to use the phone from home, , guessing it did a ? hit & miss ? ota update since the
wi-fi was off when it attempted the update. Home is a very minimal signal area.
Any way to force it to take the S7232 update again?
(I could update over wi-fi if i had wanted, only i didn't want the update anyhow).
thanks, rik
I can give you a link for a backup with latest firmware, you will have to wipe data tho
https://mega.nz/#!fkommKgJ!fkiaT_p8ZFOBzyJpUdNAqOZlTWpt-5hNuQ-2vvA5tSQ
This is a full backup from newest firmware but you need to wipe data before boot
sent from rooted 306sh
Stick firmware updates are not compatible with custom recoveries
sent from rooted 306sh
Just home, thanks
Hi,
Thanks for the help, just home from work (rough), so i will plug the
Aquos in tonite and hopefully be able to try the file tomorrow,
(that 8 hour boot thing), just downloaded your file, i'm ready.
This is my take-to-work personal phone, sprint zone, and i missed it today.
Your help is really appreciated.
rik
Final note
thought i'd just post to let you know the phone obviously had big problems
-- it failed to start today -- just buzz on buzz off -- even after 4 hours charging,
all i could get was the battery dead screen, wouldn't come on at all.
Guess the real problem was with hardware, i laid it away in the junk phone box
in the attic, end of Aquos Crystal.
rik
I downloaded this backup and yesterday to restore the firmware, works great, huge thank you , you saved me. :хорошо:
can you help me?
badbadri said:
I downloaded this backup and yesterday to restore the firmware, works great, huge thank you , you saved me. :хорошо:
Click to expand...
Click to collapse
can you help me dude? :crying:
im already download this firmware and confuse how to restore it
im looking for how to root my phone but always confuse
and finally i installed supersu on playstore and reboot
im waiting for 5 minutes and not booting, and im plug my phone to pc and the computer request for formating all my storage
and my phone can enter the recovery mode and i go to wipe data & factory reset, and still not work
can you send to my email?
my email is [email protected]
thx ..
Question: My 306SH would not update (still at S8216). Could use your back up to update my firmaware?
After 306SH ph was acting weird, did a hard reset & saw system Software updtd to S7232, & unk file in Misc (.eCtcQjbu1dgnvtFnvnr6yepTp1M=) I then installed Malwarebytes & scan detects this S7232 software update as malicious malware Android/PUP.RiskyTool.Agent.ay (dm.redbend) "/system/priv-app/fotaClient.apk". When going to System to do an manual update, Malwarebytes popups w/same msg every scan "Software App", even aft reboot 2days ago 7/12/2017. And phone wont let me create new google acct. An error that "google account mgr not working" popup & I see that same unk file reappears. Ph not rooted -XDA says "there's no root for 306SH that works">see XDA blog 'Root for Aquos Crystal 306SH ONLY'.
Go to the Sharp USA website for the 306SH firmware, and see what firmware you are on.
Download the firmware from the versions higher than yours, and if there is a repeat, notably "kernel.img", download the most latest version of it.
Then, plug your device into your computer, make sure you have the proper drivers installed for the Sharp Aquos Crystal installed on your computer. Boot your device into bootloader. Go to a terminal, cd to the directory where you downloaded your .img's from the website, and do
fastboot flash kernel kernel.img
Ex.
fastboot flash foo foo.img
And you can flash all the latest updates. When done, exit the terminal, make sure the device is unmounted, unplug from computer, and reboot your Crystal.
Hooray, it should be updated!
turkbot said:
I can give you a link for a backup with latest firmware, you will have to wipe data tho
(Mega-nz link expired)
This is a full backup from newest firmware but you need to wipe data before boot
sent from rooted 306sh
Click to expand...
Click to collapse
Turkbot, I hate to beg on my first XDA post, but is there any chance that you still have that ROM and is there any chhance that it's not TextNow loaded? I've got TWRP, Busybox, SuperSU, Xposed, and I've tried every which way to edit the prop, tweak it with modules, unlock etc (it even works with my Sprint MSL, but crashes when I try to manually set my MDN and MSID) It just says no SIM/no service and refused to give me any signal except for GPS and WIFI without one. Countless 'techs' over the phone and 3 different Sprint repair stores claim they don't have the stock firmware and Sharp actually claims that the reason they can't help me with the firmware is their contract with Sprint forbids it.. If you still have the file or a TWRP / Titanium etc backup you would be my savior.
I recently purchased a Galaxy Note 4 on EBAY running stock firmware and activated it on my cellular network with no issues. The phone works fine i.e calls, texts, other functions. I am however faced with a Wi-Fi issue. If I ever power off my phone and turn it back on, the Wi-Fi fails to automatically connect. I have to manually reconnect and every time I do so I get a message that says" the phone in in factory mode and wifi is now turning off, change to user mode, "This message does not stay for too long on the screen. I used ODIN to redo the stock firmware. It was during this process that i noticed the messages (mention below) in recovery mode.
E: failed to mount /efs (invalid argument)
dm-verity verification failed...
I still went ahead and re flashed the stock firmware assuming it would fix all issues, but it did not. Not sure if this phone was rooted at sometime or not. Any help would be much appreciated.
I have used ODIN to flash stick US Cellualr ROM, but problem still exists.
4dloveofgod said:
I recently purchased a Galaxy Note 4 on EBAY running stock firmware and activated it on my cellular network with no issues. The phone works fine i.e calls, texts, other functions. I am however faced with a Wi-Fi issue. If I ever power off my phone and turn it back on, the Wi-Fi fails to automatically connect. I have to manually reconnect and every time I do so I get a message that says" the phone in in factory mode and wifi is now turning off, change to user mode, "This message does not stay for too long on the screen. I used ODIN to redo the stock firmware. It was during this process that i noticed the messages (mention below) in recovery mode.
E: failed to mount /efs (invalid argument)
dm-verity verification failed...
I still went ahead and re flashed the stock firmware assuming it would fix all issues, but it did not. Not sure if this phone was rooted at sometime or not. Any help would be much appreciated.
I have used ODIN to flash stick US Cellualr ROM, but problem still exists.
Click to expand...
Click to collapse
Whats your model number shows in download odin mode ?
4dloveofgod said:
I recently purchased a Galaxy Note 4 on EBAY running stock firmware and activated it on my cellular network with no issues. The phone works fine i.e calls, texts, other functions. I am however faced with a Wi-Fi issue. If I ever power off my phone and turn it back on, the Wi-Fi fails to automatically connect. I have to manually reconnect and every time I do so I get a message that says" the phone in in factory mode and wifi is now turning off, change to user mode, "This message does not stay for too long on the screen. I used ODIN to redo the stock firmware. It was during this process that i noticed the messages (mention below) in recovery mode.
E: failed to mount /efs (invalid argument)
dm-verity verification failed...
I still went ahead and re flashed the stock firmware assuming it would fix all issues, but it did not. Not sure if this phone was rooted at sometime or not. Any help would be much appreciated.
I have used ODIN to flash stick US Cellualr ROM, but problem still exists.
Click to expand...
Click to collapse
Did you have a back uo of your efs files? That contains your imei which if its corrupted is very hard to revive.... and by the sounds of it yours could be corrupted.
Can you get into the phone now will it boot?
Note 4 (US Cellular) model N910R4
callumbr1 said:
Did you have a back uo of your efs files? That contains your imei which if its corrupted is very hard to revive.... and by the sounds of it yours could be corrupted.
Can you get into the phone now will it boot?
Click to expand...
Click to collapse
I am able to use the phone and have also used it on the cellular network, was wondering how I could resolve the mentioned issue. The phone must have been rooted at some point and it wasn't done by me, so I do not have a back up of the efs folder.
4dloveofgod said:
I am able to use the phone and have also used it on the cellular network, was wondering how I could resolve the mentioned issue. The phone must have been rooted at some point and it wasn't done by me, so I do not have a back up of the efs folder.
Click to expand...
Click to collapse
As long as the phone works thats good. Just boot to twrp and back up efs folder just incase. As for your issue i would of thought flashing stock would of fixed it. Have you wiped dalvik and cache?
Try to Make a full backup then flash a stock firmware with pit file of your exactly device
Someone gave me a note 4, but it's a Sprint device and I'm an at&t subscriber; I'd prefer to not have the Sprint garbage on here, but I have a business need to not run a rooted device.
Is there anything preventing me from running the at&t firmware on this? I get that LTE won't work since this doesn't have the necessary band support, but the hardware appears to be otherwise identical.
Im guessing it may not be that easy given the fact that the latest bootloader on the sm-n910p is a fused 5. There may be a way to flash a modified att firmware if you replace it with the 5DQ15 bootloader. I say "may be" as I can not tell you for certain. Also even if you are successful, you will not get LTE as the hardware is different. If you do not have the latest N910PVPU5DQI5 firmware, Im pretty sure you could sell it and buy an ATT Note 4. A lower version of the sm-n910p is very hard to find and most likely fetch a little higher price.
Yeah, I wasn't expecting LTE, I was just hoping for something that didn't have all the Sprint crap that doesn't work.
I think I'll just wait until I'm working again and get a S10 or Note 10 and retire this to the phone drawer.
mikeytsi said:
Yeah, I wasn't expecting LTE, I was just hoping for something that didn't have all the Sprint crap that doesn't work.
I think I'll just wait until I'm working again and get a S10 or Note 10 and retire this to the phone drawer.
Click to expand...
Click to collapse
Hello, If you decided or if anyone else has the same question, perhaps this is what your looking for.
https://www.xda-developers.com/uninstall-carrier-oem-bloatware-without-root-access/
Well, this is likely moot now as the device has pretty well crashed and I haven't been able to recover it yet.
I'm using a note 3 at the moment, which isn't great as it's just a bit too old. I'm also borrowing a OnePlus 1, but I don't think that's going to work for me as it doesn't have an SD slot. I may just pick up an S6 since those are relatively cheap until I can upgrade to a 10.
I just noticrd your reply and I will post a reply later today, I hope I can help you bring back a working Note 4 .
Yeah, something's wrong with it on a pretty basic level now. I did briefly get it functioning again two days ago (after doing a bunch of factory resets and firmware reloads), but it started crashing again during build-out and it's been unusable ever since.
I did tease out a kernel panic at one point, here's what it threw:
Kernel Panic
Krait info
panic caller : mdm_subsys_powerup+0xf0/0x12c
panic msg : CP BOOT UP FAIL - NEED cP DUMP
Thread : mdm_helper_prox:759
pm8841_rev : 0x0
I'm using "N910PVPU5DQI5" which I pulled down from this very site.
That was the first thing that I thought when you posted. Ondin fail and that is due to the latest firmware update on n910p Sprint Note 4. The last update was a fused 5, version 4 and to my knowledge ATT firmware is a fused 4. Also called aboot. (aboot) . Aboot is always upward compatible but is not downwards compatible. Meaning, if you upgrade to a higher aboot as in your case fused 5 then you will not be able to dowmngrade back to a fused 4 aboot. When you gashed the ATT official firmware that had an lower aboot is the reason you bricked you device. The good new is I think I may have a solution to unbrick your device. I need to confirm a few details before I reply.
No, I'm still using the Sprint firmware, haven't tried the at&t one yet.
ok
---------- Post added at 03:41 AM ---------- Previous post was at 03:35 AM ----------
Was it a flash that caused a soft brick? How did this happen?
I was getting random perf issues, then it started randomly crashing and restarting, eventually getting to the point where it would no longer boot. That's when I started trying to reload the firmware to hopefully get it stable again. No such luck.
On a more entertaining note, I've managed to soft-brick the OnePlus 1 a friend loaned me trying to update it from cyanogenmod to Lineage 16 since there's apparently a build for it. I got TWRP , the image, and the google stuff installed but it just won't boot and ultimately restarts back to TWRP. I'll poke around the dedicated forum for that though.
https://forum.xda-developers.com/note-4-sprint/general/firmware-qi5-released-10-11-2017-t3686982
---------- Post added at 03:58 AM ---------- Previous post was at 03:55 AM ----------
mikeytsi said:
I was getting random perf issues, then it started randomly crashing and restarting, eventually getting to the point where it would no longer boot. That's when I started trying to reload the firmware to hopefully get it stable again. No such luck.
On a more entertaining note, I've managed to soft-brick the OnePlus 1 a friend loaned me trying to update it from cyanogenmod to Lineage 16 since there's apparently a build for it. I got TWRP , the image, and the google stuff installed but it just won't boot and ultimately restarts back to TWRP. I'll poke around the dedicated forum for that though.
Click to expand...
Click to collapse
Dam!!! From the frying pan to the fire. I feel fot yoy bro. .... Sorry to hear that... Entertaining maybe, frustrating is a definite. Ouch!!! &^//^#
Did you make a back up in TWRP before flashing lineage 16?
---------- Post added at 04:51 AM ---------- Previous post was at 03:58 AM ----------
Just to confirm, I understand that you did in fact wipe user data and did a full factory reset. Is this correct?
Sprint Note 4
1 . Try booting into safe mode and see if that helps. if not
2. Boot into stock recovery and wipe dalvik chache and perform a factory reset and I recommend to do this 3 or 4 times a row before you reboot. Then reboot your device. I sould also mention. while in stock recovery in start page read the notification at the bottom.
3. If the above dose not fix your device then flash 5DQ15 official factory firmware with Odin. Remind you to open develop option and enable adb beforehand.
I had an old Note 4 with similar issues as your describing. It was an emmc hardware failer. The only fix was a new motherboard.
Of course not.
Should be easy to recover though, I just need to find a utility so I can flash it.
For you Note 4. Use pc or laptop , proper drivers anf Odin software.
link for Odin download only. None of the official Tar firmwares in this link are compatible . I just want to be very clear that flashing any Tar in the link provided will end in Odin fail and a soft bricked device. Odin is the only thing you need to download. Hope this is of some help.
https://forum.xda-developers.com/note-4-sprint/general/stock-tar-odin-flashable-t3250864.
Yeah, I wiped it three times in fact, I read something about that in another thread.
It won't even boot to the point where you could try to get in to safe mode.
I've done several factory wipes before and it didn't seem to help, I'll that again and try reloading firmware again though and see what happens.
..... Recovery mode appears to be hanging on "Installing System Update" we'll see if it finishes.
Hmmm, I'm not seeing an ADB option. I'm using Odin v3.12 if that matters.
Finally got in to recovery.
dm-verify verification failed...
e:failed to mount /cache (invalid argument) - see several of these
e:Can't mount /cache/recovery/log
e:Can't open /cache/recovery/log
e:failed to mount /cache (invalid argument)
:can't mount /cache/recovery/last_log
can't open /cache/recovery/last_log
... /cache/recovery/last_install
..../cache
.../system
...last_locale
So, several errors.
DM-verify is one of the worst and it is also likely to include a DRK error . I have over 5 year experience with Sansung rooting and flashing, porting and........ Im a flash-a aholic and soft brick my devices many times. In all that time I only had one that I could not recover from. Yep DM-Verity fail(device mapper) and DRk (device root key) and Note 4. There are you tub videos and a good amont of information on the net. 4 files flashed via Odin. I had a rooted device and DM-verty involves security prodection as I had root the issue may have been woth su' binaries. However. as youare not rooted maybe flash factoy firmware in Odin will work for you.
You may have wondered why I suggested looking at the bottom screen in stock recovery. I answer is DM-verity.
In recovery at te top of first page is a knox counter. If its un-tripped reads 0x0 similar . If it has been tripped then a number will be visible as an indication 1x0 or 2x0 or similar.
I had to root the device to unlock platform so I could use it with the at&t sim. That was months ago and had no impact on running the stock firmware.
Hey guys, I done goofed. Big time. And I'm aware of that.
I was an a 9.0 rom (can't remember which one unfortunately) and my stupid ass tried to flash a 8.0 official firmware via odin to get back to stock.
Yes, exactly.
Obviously odin didn't even try to flash anything but got immediately stuck with error messages. One was "can't open the specified file (line 1892) and other times it just got stuck at "setupconnection".
I tried 2 different roms (one from samfirmware and another one from that one little download tool you can use), tried extracting the PIT file and flash everything with that, but it never flashed anything completely.
Also tried 2 different PC's and different cables, since that's always the first answer people get. And I was using ODIN 3.12 as well as 3.13.
Even though odin didn't do anything my phone wouldn't boot anymore.
Interestingly enough I can still boot into TWRP just fine.
The only issue is that TWRP can't access internal memory anymore. For instance, when I try to factory reset an wipe, I get a ton of error messages about how none of the paths could be mounted (failed to mount '/data' (invalid argument). Size is shown as 0mb.
I tried flashing a 9.0 rom from here, and aroma didn't show any error mesasges whatsoever. But upon reboot it got stuck and after 2 hours I just unplugged the cable and let it die.
When plugging it into my PC while running TWRP, the external SD card pops up as a USB drive, but the phone doesn't show up as phone.
When I tried doing that last week it didn't show any drives, no internal and no external.
Sooo... completely bricked even though I can access TWRP?
Help would be much appreciated because I'm at a loss here.
TIA
I had a similar issue. However, after a comprehensive check done by an authorized dealer, they found a hardware issue.
robotov said:
I had a similar issue. However, after a comprehensive check done by an authorized dealer, they found a hardware issue.
Click to expand...
Click to collapse
You think it's plausible that software caused a hardware failure?
hoeni said:
Hey guys, I done goofed. Big time. And I'm aware of that.
I was an a 9.0 rom (can't remember which one unfortunately) and my stupid ass tried to flash a 8.0 official firmware via odin to get back to stock.
Yes, exactly.
Obviously odin didn't even try to flash anything but got immediately stuck with error messages. One was "can't open the specified file (line 1892) and other times it just got stuck at "setupconnection".
I tried 2 different roms (one from samfirmware and another one from that one little download tool you can use), tried extracting the PIT file and flash everything with that, but it never flashed anything completely.
Also tried 2 different PC's and different cables, since that's always the first answer people get. And I was using ODIN 3.12 as well as 3.13.
Even though odin didn't do anything my phone wouldn't boot anymore.
Interestingly enough I can still boot into TWRP just fine.
The only issue is that TWRP can't access internal memory anymore. For instance, when I try to factory reset an wipe, I get a ton of error messages about how none of the paths could be mounted (failed to mount '/data' (invalid argument). Size is shown as 0mb.
I tried flashing a 9.0 rom from here, and aroma didn't show any error mesasges whatsoever. But upon reboot it got stuck and after 2 hours I just unplugged the cable and let it die.
When plugging it into my PC while running TWRP, the external SD card pops up as a USB drive, but the phone doesn't show up as phone.
When I tried doing that last week it didn't show any drives, no internal and no external.
Sooo... completely bricked even though I can access TWRP?
Help would be much appreciated because I'm at a loss here.
TIA
Click to expand...
Click to collapse
Go into Twrp and Wipe > Format Data and type Yes. This should remove encryption from your internal storage and you should be able to flash any custom rom.
For any reason if this doesn't work, you'll need a stock firmware with latest bootloader and modem version than which is currently on your device otherwise odin will just show error. The best way is to download latest firmware (october patch) for your model regardless of country and flash that via odin. Tick nand erase in odin.
Going back to android 8 from android 9 is not stupid .
I have even gone back to android 8 from android 10 since android 10 destroyed my partitions.
If your PC doesn't show Internal Storage. Go to Mount and tick system and try again.
Which firmware for S7 edge already has October patches?
Thanks.
musmax said:
Which firmware for S7 edge already has October patches?
Thanks.
Click to expand...
Click to collapse
If you have a G935F
https://www.sammobile.com/samsung/g...e/SM-G935F/VIR/download/G935FXXS6ESI4/296136/