I upgraded my device (it is actually a Huawei GT3 NMO-L31C432, but basically identical to the P9 lite) to Nougat couple of days ago. There were some issues regarding automatically upgrading, so I upgraded using fastboot etc. My model number and build number got messed up (NDR test keys) but apart from that all functionality seemed to be there (Wifi, mobile data, camera, sound etc) so I just fixed that in build.prop. However, I noticed a serious issue with push notifications (e.g. WhatsApp) and figured that this is pretty common for EMUI (this is my first Huawei device), so I went through all the settings to see if I could fix the issue (don't close WhatsApp automatically, ignore battery optimizations for WhatsApp, grant unrestricted data access, priority notifications). Yet, the issue couldn't be solved.
So I decided to wipe the phone through TWRP and reflash the firmware (basically following the steps outlined here: xxx/p9-plus/how-to/easy-upgrade-to-unapproved-emui-5-update-t3649532 Replace "xxx" with "https://forum.xda-developers.com/"). IMPORTANT REMARK: Before wiping and reflashing, I could change the ringtone etc - no issues.
Now, after configuration of the fresh system (root, restore most important apps using TitaniumBackup) it seems that the push notifications work fine. However, I can no longer change ringtone/notification sound in the system settings: Settings -> Sound (I apologize if these are not the usual expressions used in the English UI, I am using the German one). From there, I have options to open up other menus, such as ringtones for SIM1 and SIM2, or notification sound. If I press on those, it looks like they get "activated" but nothing happens. Settings in the same menu (Settings -> Sound) that just require to be activated/deactivated such as vibration on/off or a "sound when screen is locked" work fine. It is just that I can not open the list to choose between the preinstalled sounds. As a workaround I downloaded an app from the PlayStore and changed the ringtone via this app - no issue.
What I already tried/checked:
- Wipe Cache/Dalvik/ART through TWRP
- check /system/media/ringtones and /system/media/notifications -> all exist and all default sound .ogg files are there
- reflash just the system.img and wipe cache afterwards
Nothing of this helped. What could be wrong? What else could I try? In case someone suspects I messed up some files/settings using root: shouldn't be the case. All I did was flash the TWRP through fastboot, flash the recent SuperSU.zip and then used root access to setup AfWall+, AdAway and TitaniumBackup. TitaniumBackup was used to restore most important apps (mail, some office apps and such - NO system tweaks whatsoever). It also seems (only sometimes) like the settings in general are a bit laggy - very rarely they "freeze" for a second or so or if I want to get back to the previous page a black screen appears for a fraction of a second (as if settings crashed - but I end up where I want to).
_theluk_ said:
I upgraded my device (it is actually a Huawei GT3 NMO-L31C432, but basically identical to the P9 lite) to Nougat couple of days ago. There were some issues regarding automatically upgrading, so I upgraded using fastboot etc. My model number and build number got messed up (NDR test keys) but apart from that all functionality seemed to be there (Wifi, mobile data, camera, sound etc) so I just fixed that in build.prop. However, I noticed a serious issue with push notifications (e.g. WhatsApp) and figured that this is pretty common for EMUI (this is my first Huawei device), so I went through all the settings to see if I could fix the issue (don't close WhatsApp automatically, ignore battery optimizations for WhatsApp, grant unrestricted data access, priority notifications). Yet, the issue couldn't be solved.
So I decided to wipe the phone through TWRP and reflash the firmware (basically following the steps outlined here: xxx/p9-plus/how-to/easy-upgrade-to-unapproved-emui-5-update-t3649532 Replace "xxx" with "https://forum.xda-developers.com/"). IMPORTANT REMARK: Before wiping and reflashing, I could change the ringtone etc - no issues.
Now, after configuration of the fresh system (root, restore most important apps using TitaniumBackup) it seems that the push notifications work fine. However, I can no longer change ringtone/notification sound in the system settings: Settings -> Sound (I apologize if these are not the usual expressions used in the English UI, I am using the German one). From there, I have options to open up other menus, such as ringtones for SIM1 and SIM2, or notification sound. If I press on those, it looks like they get "activated" but nothing happens. Settings in the same menu (Settings -> Sound) that just require to be activated/deactivated such as vibration on/off or a "sound when screen is locked" work fine. It is just that I can not open the list to choose between the preinstalled sounds. As a workaround I downloaded an app from the PlayStore and changed the ringtone via this app - no issue.
What I already tried/checked:
- Wipe Cache/Dalvik/ART through TWRP
- check /system/media/ringtones and /system/media/notifications -> all exist and all default sound .ogg files are there
- reflash just the system.img and wipe cache afterwards
Nothing of this helped. What could be wrong? What else could I try? In case someone suspects I messed up some files/settings using root: shouldn't be the case. All I did was flash the TWRP through fastboot, flash the recent SuperSU.zip and then used root access to setup AfWall+, AdAway and TitaniumBackup. TitaniumBackup was used to restore most important apps (mail, some office apps and such - NO system tweaks whatsoever). It also seems (only sometimes) like the settings in general are a bit laggy - very rarely they "freeze" for a second or so or if I want to get back to the previous page a black screen appears for a fraction of a second (as if settings crashed - but I end up where I want to).
Click to expand...
Click to collapse
Reflash firmware using dload method.
Thanks for the suggestion. Sorry that I forgot to mention that I tried this already but it always fails after verification if the software package. At 5% when installation should starts it stops "software verification failed. Incompatible software..." although I just want to reflash the one I installed successfully via fastboot.
Would it be dangerous to flash other imgs in the update.app, such as all the modem related ones. Might that even help at all? For many of them I am unsure what they really are, e.g. Trustfirmware.img... I guess xloader is the bootloader?
Try doing a rollback, search for Unified help thread for p9 lite. I've written in detail how to do it.
Thank you very much. Will give it a try later on. Hopefully the dload method for rollback will work
you have to revert back to your original fw and do the upgrade to nougat through hicare.... I had the same problem
This device is driving me insane. The dload method just never tends to work...
What I did:
put the UPDATE.app into dload folder (ROOT of external SD)
Start "dload" method using VOL+ & VOL- & POWER.
Fails after verification: "Software install failed! Incompatibility with current version. Please download the correct update package."
I suspected (after reading the Huawei pdf accompanying the rollback package) that maybe the root access and unlocked bootloader might be an issue. So I reverted the phone back to stock recovery, reflashed system.img to remove root and relocked the bootloader. Yet, dload fails with the same message as before. I think I will go ahead and try the rollback method for the GR5 mini (even though it's for south asia region, but hey... I just want a working phone. Can change CUST later on).
If that also fails I am really tempted to fully wipe the phone using TWRP and flash every single *.img that can be extracted from the UPDATE.app files. If I use a Marshmallow ROM as source for the img files, this should work as well as a rollback, right? Or do I have to expect major issues?
EDIT: The GR5 mini rollback also fails.
Deleting everything won't work... You will just face major issues.
Do you (or anyone else) have any other suggestion what I could try? Currently, as said, I would flash all *.img files that can be extracted from a Nougat UPDATE.app and can be flashed via fastboot (except for xloader.img and fastboot.img, which I believe to be the bootloader and the fastboot stuff, respectively?). Those that can't be flashed via fastboot would be converted to ext4.img files using imgtool and put into the proper partitions using "dd" command via adb. I hope that if I do this for both the ~1.3GB update.zip and the ~0.7GB update_data_full_NMO-L31_hw_eu.zip, the phone (unrooted, locked bootloader) will be in a state that eventually allows the dload method to work... Does this make sense? Are there any partitions that I should never ever flash manually?
So what I now did is probably not the best solution but for now it appears to be an "okay-ish" workaround. Using the C432 oeminfo of a P9-lite I converted my NMO-L31 to a VNS-L31 and then down/upgraded the smartphone to the recent software for the P9-lite. Seems to work now
Related
Is there any way too root this phone?
Sent from my SGH-T999N using xda app-developers app
More info
Sent from my SGH-T999N using xda app-developers app
Root SGH-T999N (metro PCS) to SGHT999NUVUBMK7 after 4.3 update
RawesomeMike said:
More info
Sent from my SGH-T999N using xda app-developers app
Click to expand...
Click to collapse
Yes, there seems to be a root method for the SGH-T999N that I may have discovered. I synced/backed up on Google sync, when I was running on 4.1.2.
I Unintentionally updated to 4.3 not realizing root would be more difficult. I DID NOT use odin, just cause of the bricking hype. I did do some stuff with sideload, I think.
When flashing I used a 16gig micro SD card & also copied some extracted zip rom files via windows, straight to the phone.
Kept getting the error (in red) when checking for signature or something.(Ex. e: whole-file signature failed <se3>).
In the phone OS, I manually cleared cache, data, notifications, turned off & forced stop on several of the "update" & other potentially restricting security apps on the phone.
Booted into recovery via power + home + volume ? keys.
Wiped cache
Wiped all data
"Upgraded ish" from external SD card.
Reset my phone & still got a signature fail.
Did the wipe & factory default again (after another reboot)
Flashed the same file again (I think) was CWM, Cyanogen or something. d2tmo, d2mtr seem to work.
Did a Factory reset & phone went to metro logo. Did a 2nd recovery reset before 1st one could finish & the phone seemed to go to an out-of-box state/first time setup. That's where I was able to enable superuser root, the box thing & backup?
Sorry I don't remember more detail at the moment. The Google Chrome backup seemed to help a lot for reinstalling rooted apps after 4.3 update w/ factory reset.
polkcontracting said:
Yes, there seems to be a root method for the SGH-T999N that I may have discovered. I synced/backed up on Google sync, when I was running on 4.1.2.
I Unintentionally updated to 4.3 not realizing root would be more difficult. I DID NOT use odin, just cause of the bricking hype. I did do some stuff with sideload, I think.
When flashing I used a 16gig micro SD card & also copied some extracted zip rom files via windows, straight to the phone.
Kept getting the error (in red) when checking for signature or something.(Ex. e: whole-file signature failed <se3>).
In the phone OS, I manually cleared cache, data, notifications, turned off & forced stop on several of the "update" & other potentially restricting security apps on the phone.
Booted into recovery via power + home + volume ? keys.
Wiped cache
Wiped all data
"Upgraded ish" from external SD card.
Reset my phone & still got a signature fail.
Did the wipe & factory default again (after another reboot)
Flashed the same file again (I think) was CWM, Cyanogen or something. d2tmo, d2mtr seem to work.
Did a Factory reset & phone went to metro logo. Did a 2nd recovery reset before 1st one could finish & the phone seemed to go to an out-of-box state/first time setup. That's where I was able to enable superuser root, the box thing & backup?
Sorry I don't remember more detail at the moment. The Google Chrome backup seemed to help a lot for reinstalling rooted apps after 4.3 update w/ factory reset.
Click to expand...
Click to collapse
You say you think.....doesn't sound reassuring can you elaborate a bit more? I don't seem to understand what you are getting at if it works or not? I don't know if I should root my phone now or wait for 4.4.......
Have you heard of/tried the Morobo + Shuame method? Worked a treat for my HTC Wildfire, Motorola Defy, and my HP Slate 7.
Seriously worth a shot if you ask me. A link to the XDA thread:
http://forum.xda-developers.com/showthread.php?t=2092349
Know this is old, but if you're still looking for a method, I successfully rooted my T999N yesterday using ChainFire's autoroot for the t-mobile variant (the T999). I'm new so I can't post a link here, but if you google "chainfire autoroot", it'll direct you to his page where you can download the package from the list of supported devices. The package conveniently contains a version of Odin3 that you will use to flash his stuff to your phone.
Remember, the phone must be in samsung's "download mode" to receive the flash. You get this model into the mode by powering it off, then holding the HOME button, the POWER button, and the VOLUME DOWN button all at once. When the warning message comes up, you push VOLUME UP to continue, then the phone will be in download mode. You can then connect the phone to your computer and if you have the drivers installed correctly, Odin will recognize the phone and be able to send the flash. You will then need to go about disabling Samsung's security software, KNOX, before the phone will be fully rooted. There are plenty of guides on how to do that so no worries there.
Hello guys,
I need some help with my Lenovo K4 Note Vibe (3GB RAM version). The thing is it started popping up random "Unfortunately xxxx stopped working" a couple of weeks ago. That specific app would just crash and restart itself. It can be a system app or game or any random thing (GUI, Contacts, Messaging, Angry Bird and other games etc.). It would usually gets solved on by restarting the phone or stopping the app from setting or on it's own.
Now the problem I have is, I gave it a restart and now it just shows "Unfortunately Notification Center Has Stopped". I have two option "Okay" and "Try To Resolve" none of them does anything except the error goes away for a second or two and pops back up. I can not even see the usual "Enter you PIN" screen. Yes I was using Fingerprint so I had to enter the PIN every time I restart the phone. So now basically I'm stuck at startup screen without any options. The phone is alive I can tell, I can feel it vibrate when I call, hear messaging tones (whatsapp/text). If connect it with PC when turned on, I can see a Lenovo Folder option to browse but its empty since it requires the phone to be unlocked first with pin.
The mobile belongs to my sister and she is dentist by profession and have lots of important data including some research she did (photos) for journal she publishes in national magazines.
How do I get past this error ? I do not have root, I tried the recovery but it is a Chinese recovery and does not have an option to wipe catch partition. The phone was on latest version (Marshmallow) and there is nothing I can do to start it up. Tried booting in safe mode but still the same error.
There is an option to see basic details in Chinese recovery, it shows
Model No. A7010a48
Build Time : 2016 12 27 14:35:36 CST
Kernel Ver. 3.18.19+
Android Ver.: 6.0
along with various other details.
How do I save my data ? Can I recover it anyhow ?
1. Try wipe data and factory reset
if not solve
2. Use SP Flash tools to flash stock rom.
If you have unlocked bootloader, then you can try to flash/hotboot into twrp recovery as it shows all files and folders in pc while connected in recovery mode.
Even if the bootloader is locked, there is no harm in trying.
tiks1001 said:
If you have unlocked bootloader, then you can try to flash/hotboot into twrp recovery as it shows all files and folders in pc while connected in recovery mode.
Even if the bootloader is locked, there is no harm in trying.
Click to expand...
Click to collapse
Bootloader is locked. And there was no custom recovery flashed, every recovery flashing method I searched required for data to be wiped and bootloader unlocked so I`m stuck on that front.
macblaze said:
1. Try wipe data and factory reset
if not solve
2. Use SP Flash tools to flash stock rom.
Click to expand...
Click to collapse
Like I mentioned in post, the data is important, I could throw away the hardware I just need data.
I`m looking for a method to wipe catch partition without getting my data erased or to extract data any other way. Please do let me know if anyone have any solution at all, this is really really important.
Enable usb debugging
Use adb pull command to get the data.
Edit: nevermind, saw you can't unlock the phone.
Pretty sure if you flash twrp it will wipe data data partition as soon as you reboot. So I wouldn't do that.
Other option is do a full nandroid backup using adb but the only way you are gonna get that working is if you flash twrp and like I mentioned it's probably not a good idea but I'm not certain.
Another option is mtktools/spflashtool and do a full firmware backup from that, reset the phone and then restore from the backup, but I have no experience in that but it should work in theory.
Do you see the error even when there is incoming call? If not try from InCallUi i.e. when you answer the phone, try to navigate from that such as opening contacts, if there is a chance pull down notification bar and enter into settings. If any of these happen, it will ask to enter your pin and then you can unlock your phone. Now connect your phone to your pc and backup the data you need
If the data you seek are images, google photos should already backup your images to your google photos cloud account. Check this by signing in from your pc.
If they are media from whatsapp, don't worry, it will be backedup daily to your google drive account and all your messages along with your media will be restored after you install whatsapp again.
If they are Docs, then probably they are in gmail account (PROBABLY) you can always search for required ones in gmail.
Any other files from these cannot be restored if they are inaccessiblefrom your phone.
Suggestion: Maintain a cloud account which you feel safe and backup to that account so that you have no need to worry about the important files. **** like these happen every now and then.
Edit : These are gonna work if you checked the online backup or sync in respective app.
Hi, folks. Few days ago, I updated my MXP via ota, from 6.0.1 to 7.1.1. As this is my first experience with Nougat, I turned off a particular notification without caution, i forgot what it's about, by long pressing the notification and selected silence.
When I look at Settings > Notifications, it turns out that "System UI" was silenced. (attached screenshot 1)
I don't know how to un-silent it as there is no longer said notification for me to long press, and no option to select (in screenshot 2).
If I use a new user, there is an overwrite dnd option (screenshot 3), so I think this might just be affecting some user preference setting.
I would like to restore this if there is some way besides restoring a complete twrp backup. Clearing its cache didn't help, nor did restoring "System UI 7.1.1" via Titanium-nandroid of the twrp backup. Is it possible to do it through adb, or another method?
So I rooted my phone following information on this site/a video guide from youtube (I dunno if I'm able to post links but I can PM if you need to see what it had me do etc) so I did a fresh root with TWRP, RMM bypass, no-verify encryption, magisk. All worked great the phone was rooted etc, I then stupidly removed google play services to try get an early date APK which caused issues so I thought a wipe with TWRP would fix the issue but the startup wizard wouldn't work, so I then removed startup wizard via TWRP got back into the phone and put the new version of play services on, yet still had issues so I got the default firmware for my model at samsmobile and put it on via odin - all worked great phone booted fine etc but some apps said a boot was detected, so I made sure to go into developer options and make sure the OEM was locked, did a wipe via the default options when holding power>bixy>up however some apps still say the phone is rooted.. I checked with a rootchecker and I pass the safety and it says no boot detected. So I dunno what the problem is? The only thing I did see was when I did the wipe this came up
"remove failed dir '/system/carrier/ATT/priv-app/AttIqi_ATT' (no such file or diectory)
e:[libfs_mgr] is_dt_compatible(): firmware info was not valid: '/proc/device-tree/firmware/android/compatible: no such file or directory"
Really dunno what to do from here.
bump
mrberta said:
So I rooted my phone following information on this site/a video guide from youtube (I dunno if I'm able to post links but I can PM if you need to see what it had me do etc) so I did a fresh root with TWRP, RMM bypass, no-verify encryption, magisk. All worked great the phone was rooted etc, I then stupidly removed google play services to try get an early date APK which caused issues so I thought a wipe with TWRP would fix the issue but the startup wizard wouldn't work, so I then removed startup wizard via TWRP got back into the phone and put the new version of play services on, yet still had issues so I got the default firmware for my model at samsmobile and put it on via odin - all worked great phone booted fine etc but some apps said a boot was detected, so I made sure to go into developer options and make sure the OEM was locked, did a wipe via the default options when holding power>bixy>up however some apps still say the phone is rooted.. I checked with a rootchecker and I pass the safety and it says no boot detected. So I dunno what the problem is? The only thing I did see was when I did the wipe this came up
"remove failed dir '/system/carrier/ATT/priv-app/AttIqi_ATT' (no such file or diectory)
e:[libfs_mgr] is_dt_compatible(): firmware info was not valid: '/proc/device-tree/firmware/android/compatible: no such file or directory"
Really dunno what to do from here.
Click to expand...
Click to collapse
BUMPITY BUMP BUMP, plz help my fwiend!
Hello XDA community,
I recently purchased the Nothing Phone 1 running on the latest version of Android 13. After rooting my phone using Magisk, I installed several Magisk modules which worked fine initially.
Here's a list of Magisk modules that I installed in chronological order:
Font Manager
NotoCJK
Fullscreen/Immersive Gesture
G-visual (later closed as I didn't see any effect)
Shamiko
DRM disabler
Revanced Youtube
Webview Manager (replaced with ungoogle chromium)
Nexus Media Before installing the 10th module, I took a full backup of my device using Titanium Backup. However, during the backup process, it got stuck while backing up a file named "Media 13-9427200." After several attempts, I had to cancel the backup for this file to complete the backup process.
Pix3lify (failed to unpack boot image and finally used slim mode)
Safetynet fix
After installing the 11th module, I went to bed and installed several applications before sleeping, such as Kiwi, Shizuku, App Ops, Buzzkill, Automate, Vmos, Brevent, and Greenify.
12.Audio Modification Library
13.Ainur Narsil
After installing the 13th module, I noticed that my phone started behaving abnormally, and it would automatically reboot. Every time I start the phone, the interface freezes after two minutes, and it restarts automatically after several seconds. This scared me, so I uninstalled all the Magisk modules and applications installed after the 11th module and disabled the two audio modules, but it didn't seem to work. So, I turned off the phone for a few hours, and it seemed to work fine after that.
When I tried to log in to my Reddit account, I found that I couldn't use "Continue with Google." When I went to the Google section in Settings, I found that I couldn't open it either.
I searched for solutions online and found that the problem might be due to the Webview. I replaced it with Ungoogle chromium and downloaded the latest version of Android Webview from the Play Store and disabled WebView Manager. But nothing worked. I tried updating the Carrier Services and clearing the Google Service's cache, but it didn't work either. (All Google apps can be opened and used normally.)
After updating the WebView, things got worse. I use a third-party launcher called Smart Launcher, and I have many customized app icons. I found that all customized app icons no longer work, only the native icons can open the app.
I am really frustrated and everything seems out of my control. I decided to restore all the data from the backup I made last night using Titanium Backup (in snap mode). Unfortunately, after the restore was complete and I restarted the phone, I found that my phone was bricked. I can see the boot animation and select the launcher, but once I choose the launcher, the screen goes black, and I cannot do anything. I am also unable to enter Safe Mode as it keeps restarting.
At the same time, I used a software control my phone. I can see NOTHING in sdcard.
What can I do? Is there any way to fix my phone and preserve my data? If not, I am willing to wipe all my data. Also, if I restore my phone to factory settings, can I still use the backup data I made with Titanium Backup?
Thank you in advance for your help.
Additionally, please find attached a screenshot of the only interface I can see on my phone after booting up.
Seems you've broken lot of system apks , clearly Nothing Launcher is first . See if you have a intact bootloader and use fastboot commands to flash the launcher but I'm quite sure there many culprits in system .
So maybe short way is to flash entirely system image shown here in one of all threads about phone unbrick
muppetz said:
Seems you've broken lot of system apks , clearly Nothing Launcher is first . See if you have a intact bootloader and use fastboot commands to flash the launcher but I'm quite sure there many culprits in system .
So maybe short way is to flash entirely system image shown here in one of all threads about phone unbrick
Click to expand...
Click to collapse
Thanks for your advice!