Hello,
It seems that Motorola is rolling out an Update!
My XT1052 received it this morning.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
but ??
netokee said:
Hello,
It seems that Motorola is rolling out an Update!
My XT1052 received it this morning.
but ??
Click to expand...
Click to collapse
I also received the notification, but I didn't start the update.
Xt1058 BL open ghost.eu firmware
Inviato dal mio XT1052 utilizzando Tapatalk
5.1.1. 222.27.5 retail.eu I've just finished this update. Very small around 9MB if I remember. Can't see difference yet.
osstis said:
5.1.1. 222.27.5 retail.eu I've just finished this update. Very small around 9MB if I remember. Can't see difference yet.
Click to expand...
Click to collapse
5.1.1 ??
i also received it yesterday evening.
This build fixes known stagefright bugs, although a new one (aka CVE-2015-6602) has recently been discovered by zimperium:
libutils in Android through 5.1.1 LMY48M allows remote attackers to execute arbitrary code via crafted metadata in a (1) MP3 or (2) MP4 file, as demonstrated by an attack against use of libutils by libstagefright in Android 5.x.
Click to expand...
Click to collapse
Do keep in mind the instructions given here: http://forum.xda-developers.com/moto-x/general/xt1053-222-27-5-stagefright-ota-update-t3210786
I had TWRP installed, root, custom logo etc. and just took the update (in my defence, it was early morning and I wasn't thinking). Taking the update with TWRP get you into a semi-bootloop, where the system restarts after about 1 minute to try to install the update again. Just restoring to stock recovery made the update install, but it then hangs at the boot logo.
I had to restore from a factory image to fix it. Whilst restoring it didn't allow me to downgrade gpt.bin, so keep that in mind.
505dv said:
Do keep in mind the instructions given here: http://forum.xda-developers.com/moto-x/general/xt1053-222-27-5-stagefright-ota-update-t3210786
I had TWRP installed, root, custom logo etc. and just took the update (in my defence, it was early morning and I wasn't thinking). Taking the update with TWRP get you into a semi-bootloop, where the system restarts after about 1 minute to try to install the update again.
Click to expand...
Click to collapse
Yea, the OTA is looking at the specific fingerprints of the build.prop, so your custom recovery would indeed prevent it from flashing , also there are the MD5 hash checks that prevent the partitions from patching
505dv said:
Just restoring to stock recovery made the update install, but it then hangs at the boot logo. I had to restore from a factory image to fix it. Whilst restoring it didn't allow me to downgrade gpt.bin, so keep that in mind.
Click to expand...
Click to collapse
It sounds like you may have had issues with the boot or the system partitions, you could have tried re-flashing the stock 5.1 partitions from the image hosted, then taken the OTA, but I'm glad you were able to get your device back up and running
The gpt.bin is applied (near) last in the official OTA procedure, this is the bootloader being updated, and once you update your bootloader, you cannot return to anything before that bootloader safely (there are ways to apply other partitions, but it is risky and complicates the OTA process moving forward), if you do flash without updating the gpt.bin, please remember that in order to safely take OTA's, you will have to flash the most up to date stock image otherwise you will hard brick your device
It seems that the Smart-lock NFC Tag recognition bug was corrected
I had TWRP installed and flashed 5.1's recovery.img to be able to install the OTA. The OTA was installing fine until I noticed a reboot, which left me with the "Bootloader unlocked" warning screen and then nothing. I can boot into fastboot and have cleared the cache partition; to no avail: the wanring screen stays on for minutes.
Any pointers to revive my phone without clearing user data?
Fear not, you can still save your phone and all data on it. See me post a few message above here. I had the exact same problem. Follow the link in my post, and flash the Factory image, then take the OTA. You can skip the command to erase userdata, and even all your data and programs are safe. It will fail on the command to flash gpt, but this is no problem.
505dv said:
Fair not, you can still dave your phone and all data on it. See me post a few message above here. I had the exact same problem. Follow the link in my post, and flash the Factory image, then take the OTA. You can skip the command to erase userdata, and even all your data and programs are safe.
Click to expand...
Click to collapse
I tried that already, but gpt.img failed to flash (downgrade prevention) and the system.img is too big for flashboot and I don't have an mflashboot for 64bit Linux (arch) ...
Edit: missed your edit about gpt
Edit2: installed arch32-light, chrooted into 32bit and mfastboot'ed all, except for user data clear Booting/optimizing as wel speak!!!
Edit3: installed the OTA after going back to stock/non-root and it boots too!
Conclusion: always check XDA before flashing anything!
I also tried the ota. Have Stock 5.1 but TWRP and Root. TRWP showed error after flash-try. Reboot System was OK, but self-restart booted up TWRP again and again.
Update File can be found in "CACHE" folder. Just delete it (in TRWP) and self-restart is gone.
So is this actually 5.1.1 or just an update to 5.1?
5.1 only
Related
adb sideload the kitket update zip is fails with following error:
Verifying current system...
"/system/etc/gps.conf" has unexpected contents.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can anyone upload for me the original gps.conf from Nexus 4 JWR66Y?
alexroz said:
adb sideload the kitket update zip is fails with following error:
View attachment 2408712
Can anyone upload for me the original gps.conf from Nexus 4 JWR66Y?
Click to expand...
Click to collapse
look here:
http://forum.xda-developers.com/showthread.php?t=2525947
you MUST reflash a kind of stock/not gps moddified version :/
Getting this same issue on wifes Nexus 4. Its stock with the 4.3 JB OTA no mods or root since that OTA. Can't understand why GPS.conf could be changed.
If I root and TWRP could a factory image update.zip with the -w wipe removed work to get her to KitKat without wiping and redoing her phone? I am used to flashing custom roms this stock ota stuff is giving me a headache.
EvilAaron said:
Getting this same issue on wifes Nexus 4. Its stock with the 4.3 JB OTA no mods or root since that OTA. Can't understand why GPS.conf could be changed.
If I root and TWRP could a factory image update.zip with the -w wipe removed work to get her to KitKat without wiping and redoing her phone? I am used to flashing custom roms this stock ota stuff is giving me a headache.
Click to expand...
Click to collapse
You do not use custom rom or custom recovery to flash factory image. Use the links in my signature for instructions.
eksasol said:
You do not use custom rom or custom recovery to flash factory image. Use the links in my signature for instructions.
Click to expand...
Click to collapse
I understand that, she is stock ROM, with stock recovery and not rooted when she is having this issue. No root TWRP or custom rom involved. Since it wasn't working with stock recovery was looking for options without wiping device during factory image flash to fix GPS.conf file thats buggered.
She got the OTA normal way on her phone this afternoon, but it failed. Will check out your sig links when I get home and see if I can solve this without spending all night setting her phone back up from a factory image wipe :/ Thx for feedback and any pointers
EvilAaron said:
I understand that, she is stock ROM, with stock recovery and not rooted when she is having this issue. No root TWRP or custom rom involved. Since it wasn't working with stock recovery was looking for options without wiping device during factory image flash to fix GPS.conf file thats buggered.
She got the OTA normal way on her phone this afternoon, but it failed. Will check out your sig links when I get home and see if I can solve this without spending all night setting her phone back up from a factory image wipe :/ Thx for feedback and any pointers
Click to expand...
Click to collapse
The flashing will required an unlocked bootloader, so if its not unlocked you will lose all data when unlocking it. (Doing a factory reset in stock recovery also wipe everything.)
I don't really know what else you can do, if there were never any modifications, then the problem is due to Google having too much protections and issues for their OTA packages.
Unlocked so can do the method in your guide. But she says she wants to clean up her phone so a clean start will probably perform better and she gets the clean slate she wants, problem solved Though OTA checks annoy me now lol
thx for the feedback and guides
Hello guys,
New CM11S OTA Released ...
XNPH25R Incremental, -- FIX : NFC & Gyroscope.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi,
I've unlocked the bootloader, instaled TWRP as recovery and rooted it, now, when the OTA message appears and I click on it, it reboot into recovery, but the updated is not performed... any idea how should I apply the update with the custom recovery?
Thanks
ICEM4N99 said:
Hi,
I've unlocked the bootloader, instaled TWRP as recovery and rooted it, now, when the OTA message appears and I click on it, it reboot into recovery, but the updated is not performed... any idea how should I apply the update with the custom recovery?
Thanks
Click to expand...
Click to collapse
Hi,
I've red in the Opo Forum that OTA currently only works with Stock Recovery or Clockworkmod Recovery, but not TWRP.
Greetz
Uludag
Uludag said:
Hi,
I've red in the Opo Forum that OTA currently only works with Stock Recovery or Clockworkmod Recovery, but not TWRP.
Greetz
Uludag
Click to expand...
Click to collapse
Take backup
1) do a full-wipe and try again..
2) do a full-wipe and install CM11S -- 22R freshly from fastboot and try... (install TWRP & root )
3) Try ota zip and flash... from
http://forum.xda-developers.com/oneplus-one/development/ota-stock-xnph25r-ota-t2804155
https://www.4shared.com/download/4UoLVwKIce/cm-bacon-XNPH25R_fix.zip?lgfp=3000
Uludag said:
Hi,
I've red in the Opo Forum that OTA currently only works with Stock Recovery or Clockworkmod Recovery, but not TWRP.
Greetz
Uludag
Click to expand...
Click to collapse
Not really , my opo is rooted and has TWRP , OTA was successfully installed through TWRP and the phone is still rooted
Make sure that "Update CM recovery" in developer options is unchecked and try again
king1990 said:
Not really , my opo is rooted and has TWRP , OTA was successfully installed through TWRP and the phone is still rooted
Make sure that "Update CM recovery" in developer options is unchecked and try again
Click to expand...
Click to collapse
I didn't even received my Opo, will hopefully arrive today :laugh:fingers-crossed: I just wanted to tell what I heard.
Updated it using TWRP but once booted it tells me there's an udpate, over and over... update in TWRP seems to work (no fails, only message is "radio image updated")
I'm rooted unlocked and using TWRP and it worked fine for me...
Mnt-XDA said:
Hello guys,
New CM11S OTA Released ...
XNPH25R Incremental, -- FIX : NFC & Gyroscope.
Click to expand...
Click to collapse
Apparently, that's not all:
People who have received a OnePlus One through one means or another are now receiving an over-the-air software update that addresses a charging issue affecting the device. Sometimes the phone would think it's plugged into USB when it's actually plugged into AC power and, as a result, charge only half as fast, if not slower. The handset would display Charging (USB) instead of Charging (AC).
Click to expand...
Click to collapse
Source: Android Police
Seems to TWRP has been removed after OTA update. First time it run update with TWRP but update notification still stay in tray. And after second try it disappear but together with TWRP
Works for me too. Using TWRP as Recovery. Press the OTA update then reboot into Recovery Mode automatically and process the rest upgrade command
hi guys, i have a problem istalling this ota update... in the previous version i cancelled cclock app and now when i try to update it fails do to system cant find the app. i tried also to manually istall the app without result... so i cant update!!! anyone know hot to solve without flash the firmware?
thank you!
CafeKampuchia said:
Apparently, that's not all:
Source: Android Police
Click to expand...
Click to collapse
You are right .... Charger AC/USB bug is also fixed ... I have mentioned the same on my OnePlusOne Forum Thread.. yesterday
Mnt-XDA said:
You are right .... Charger AC/USB bug is also fixed ... I have mentioned the same on my OnePlusOne Forum Thread.. yesterday
Click to expand...
Click to collapse
I haven't received the update yet
Wish I hadn't taken the "update". My phone came rooted so I thought that was the default setting. This update killed root so I had the hassle of re-rooting my new phone. Also missing a few features now.
Yep it's out.
For those of you in need to manually update read below.
Download: cm-bacon-d22b777afa-to-0428073396-signed.zip (KTU84P, XNPH30O)
Install: To install the update, flash a custom recovery (TWRP recommended), boot into it, then sideload using adb sideload - if you've ever updated a Nexus device before, then you'll feel right at home, as the steps are exactly the same. TWRP will ask if you want to re-root at the end.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Wtf is this thread....anyways has anyone tried a clean flash yet?
just flashed it. thanks man!
Why can you flash the zip, why do you have to sideload it ?
Mine keeps failing some sort of verification check, on both cm recovery and twrp.
I flashed it through TWRP, NO ISSUES
doalittledanse said:
Mine keeps failing some sort of verification check, on both cm recovery and twrp.
Click to expand...
Click to collapse
Are you sure you're installing with "adb sideload" as instructed? You can't install from the "install" button in TWRP.
clipcarl said:
Are you sure you're installing with "adb sideload" as instructed? You can't install from the "install" button in TWRP.
Click to expand...
Click to collapse
yep. on both the stock cm recovery and twrp i get this error:
Code:
assert failed: apply_patch_check("/system/framework/apache-xml.jar","44e4.........","eab54.........")
If you've flashed any mods or made any changes to the system. It will fail.
Exclusive Member of the OnePlus One Club
If you guys flashed my Smooth Scrolling Mod, flash the revert and then try the OTA
http://forum.xda-developers.com/one...scrolling-mod-mahdi-rom-t2840934/post54762296
Basically when you're on stock ROM and if you did any changes to your /system/ then it will not update because its been modified.
does this include removal of apps ? Mine failed to sideload as well.+
Edit 1: I did do some modding of the build.prop as well this morning.
I had a feeling that the system partition was a problem, so i wiped it and then reflashed the previous build from cyngn.com and the update still fails.
doalittledanse said:
I had a feeling that the system partition was a problem, so i wiped it and then reflashed the previous build from cyngn.com and the update still fails.
Click to expand...
Click to collapse
Same problem here, fails at:
assert failed: apply_patch_check("/system/framework/apache-xml.jar","44e4.........","eab54.........")
Everything is stock, except Recovery. Tried with original recovery and it still fails...
Got mine to update even though the system partition was updated with a modified updater-script.
I will upload the entire zip with the updated script. For those that know what they are doing the updater-script is attached.
Edit 1: Note you do loose root. You have to install supersu again if you did have it previously (if you modified system then you did)
I have a louder sound mod. So basically I have to reflash to pure stock to use this? That sucks.
Sent from my One using xda premium
Anyone tried custom kernels with ota?
Sent from my A0001 using XDA Free mobile app
C-4Nati said:
I have a louder sound mod. So basically I have to reflash to pure stock to use this? That sucks.
Sent from my One using xda premium
Click to expand...
Click to collapse
look at my post.
I guess the update.zip factory image from the official site isn't truly stock. so i went with the nuclear option and just reflashed everything via fastboot. update worked perfectly now haha.
Please go to the thread here to continue the conversation....http://forum.xda-developers.com/oneplus-one/general/cm-11s-30o-ota-slowly-rolling-t2844689
I just happened to do a software check, and it is downloading a new version. Any ideas? I was already on Lollipop.
Milkman00 said:
I just happened to do a software check, and it is downloading a new version. Any ideas? I was already on Lollipop.
Click to expand...
Click to collapse
More than likely security update for stagefright vulnerability. S5 got theirs a week or so ago.
pre4speed said:
More than likely security update for stagefright vulnerability. S5 got theirs a week or so ago.
Click to expand...
Click to collapse
400 megs for Stagefright? That seems pretty big.
OC2
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Milkman00 said:
400 megs for Stagefright? That seems pretty big.
Click to expand...
Click to collapse
Yeah it was 380 for the S5 too.
Thanks for the info. This was the only site that had ANY information about the update.
I'm on Lollipop, but Rooted. Will this update take away root by any chance?
My question exactly!
sibenj said:
I'm on Lollipop, but Rooted. Will this update take away root by any chance?
Click to expand...
Click to collapse
Typically these updates do remove root. Best to wait until someone has a root method figured out for the new update.
sibenj said:
I'm on Lollipop, but Rooted. Will this update take away root by any chance?
Click to expand...
Click to collapse
I just updated via the OTA method on AT&T. Rebooted twice. I still have root (verified by Root Checker). Here's my About page:
Here's the root checker pic:
I now have OC2. Update OTA with confidence!
I originally rooted OC1 (Lollipop) by following the Root/OC1 method.
EDIT: I just checked for stagefright vulnerability (via Stagefright detector). It reports that my device is NOT VULNERABLE. Nice.
I took the chance because this site has helped me in sooo many ways. It's the least I could do. Thanks everyone.
I'm rooted and my update failed at 26%
Sent from my SAMSUNG-SM-N900A using Tapatalk
Update failed for me at 25% too. I'm rooted OC1.
Does this update do more than just fix the stagefright exploit?
If not, then kmokhtar already posted a flashable update fix for stagefright which works great.
Could you post a link to that? I have been unable to find it via xda search, google search, browsing in note 3 forums...
Why is this 'update' 5.0? I could have sworn it was just up to 5.1.1
KestrelX said:
Could you post a link to that? I have been unable to find it via xda search, google search, browsing in note 3 forums...
Click to expand...
Click to collapse
http://forum.xda-developers.com/gal...stagefright-vulnerability-fix-note-3-t3175087
Can confirm that the update worked for me on rooted OC1, now shows OC2 and I retained full root on my phone.
ATT Ota file
https://mega.nz/#!TdE02KwJ!m4pkNivN9q2ZB7hGuXFiq872UoB8D-F-QpiPVX4sWI0
mine worked I am still rooted no problems no failure
peterson65 said:
mine worked I am still rooted no problems no failure
Click to expand...
Click to collapse
Those like me who have installed modded apps like S6 and have mixed in deodexed files, the OTA will fail. the OTA installer MD5 checks the system files and if any fail it will abort the Update. Any deodexed system files will also abort the Update
How to updated to OC2 if your OTA failed
1. Download and unzip and copy this Folder to OC1 stock root backup to your TWRP backup folder,
\TWRP\BACKUPS\0b70b440\N900A_OC1_Lollipop_Stock_Rooted_Backup
2. Copy OC1 kernel recovery installer to your sdcard SM-N900A_N900AUCUEOC1_KERNEL_Recovery-Flashable.zip
*** You can also go ahead and copy Safestrap-HLTEATT-NC2-3.75-B03[1].apk and NC2 Flasher to your sdcard ***
3 Download the OC2 OTA 2400258.cfg
rename the 2400258.cfg OC2 to 2400258.zip and copy to your sdcard
4 Install the OC1 backup,
N900A_OC1_Lollipop_Stock_Rooted_Backup.zip
5. Install OC1 Kernel
SM-N900A_N900AUCUEOC1_KERNEL_Recovery-Flashable.zip
6. (I did a factory wipe , but Warning you will loose UserData settings and Apps you installed) You might try without but if you had a custom SystemUI and Touchwiz as I did it might FC because you have setting in Userdata pertaining to the Custom apps that you will over write with the OC1 backup.
7. Select Reboot and then select Recovery to boot to stock recovery and install as a update from external storage. mine installed with no issues.
8. To get safe strap back working Download and copy Safestrap-HLTEATT-NC2-3.75-B03[1].apk to sdcard (if you have not done yet)
9. Download and copy NC2 Flasher by benwaffle
10. Install Safestrap-HLTEATT-NC2-3.75-B03, run app and install recovery ( do not press reboot to recovery, it will only take you to stock recovery)
11. Install NC2 Flasher app and then use it to boot to recovery.
12. Do a backup of your new OC2
Now you can customized and do what you want
hi,
I have a problem with my huawei nova:
i wanted to root my huawei so i flashed the update supersu , and when i restart my phone i have a bootloop....
So, i wanted to do a wipe cache but it gives me :
"Failed to mount 'cust' (Invalid argument)"
But i can no find any cust.img or update.app that want to work because when i want to update my huawei with a update.app (with a recovery stock obviously), the load is only up to 5% and it gives me an error...
1 week that my huawe still does not work...
But before you had flashed twrp?
merlin21 said:
But before you had flashed twrp?
Click to expand...
Click to collapse
yes obviously....
What version phone you have, and wich software you're on?
Reflash TWRP and restore your nandroid backup.
merlin21 said:
What version phone you have, and wich software you're on?
Click to expand...
Click to collapse
I have the Huawei Nova CAN-L01 but i don't no more... And the Software is CAN-L01 C432V100
Michiel0912 said:
Reflash TWRP and restore your nandroid backup.
Click to expand...
Click to collapse
I already flashed TWRP and i not have a backup....
With me the same error in the recovery menu. I hope there is a solution to solve the problem. My mobile is dead: (, I forgot to make a backup and with the CAN-L11 backup I can unfortunately not start anything because against the conclusion at 99% restoration the following message: "Failed to mount 'cust' (Invalid argument)"
Already several attempts made recovery to flash again.
Please help
Try this;
https://mega.nz/#!B5BxmSQC!p-uVxctJxukBtO7oqW9SdTIaQ0x0dIIBeDXIHLI4ML4
Thanks, / cust I now can fix this, but it failed on the wipen the internal memory. It is successful done, but when I look back then into the recovery are the files like / superuser there, I have played the wrong SuperSU and thus my mobile phone can not start after Restore Backup, because this SuperSU does not remove the bootloop remove.
What am I doing wrong? What can I do for my mobile phone to work again and finally start normally?
Please ask for more help
TCoreXxx said:
Thanks, / cust I now can fix this, but it failed on the wipen the internal memory. It is successful done, but when I look back then into the recovery are the files like / superuser there, I have played the wrong SuperSU and thus my mobile phone can not start after Restore Backup, because this SuperSU does not remove the bootloop remove.
What am I doing wrong? What can I do for my mobile phone to work again and finally start normally?
Please ask for more help
Click to expand...
Click to collapse
You only made a backup after you installed the wrong SU?
The problem is I have the backup from here in the forum taken, the CAN-L11 and have this successfully flashing, with your help (/ cust). But the other problem is simple I can not wipe anything and erase in the recovery because I had before all the problems, the superuser had installed, another source and since bootloop.
This binary I can now however no longer delete, so my mobile phone normally starts after successful flashing of the CAN-L11.
Recovery shows that it is deleted successfully, but as soon as I reboot into the recovery are all deleted files again there, thus also superuser.
I'm desperate
How can I delete and reset everything, so that my mobile works again?
You are mounting the partitions w/r when you wipe?
Yes I did, but why does not it work?
I'm still desperate, it simply does not work, mount and superuser remains, after delete.
Please, who has a suitable step by step guide which I can still make?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Supersu must be hiding somewhere else also, allowing it to come back. Try browsing around and see if you can find any other files associated with Supersu. Also, I would check the official Supersu thread, I believe they have an uninstall zip that should work and/or can probably guide you on what you need to do.
See if this works:
https://forum.xda-developers.com/showpost.php?p=69461377&postcount=470
View attachment 4030838
Thanks, but unfortunately still the same problem
The international memory remains immediately after wipen, etc
Superuser simply does not want to disappear, it can not make my cell phone anymore.
What exactly did you flash? I am guessing you flashed system again and it still was the same? Maybe someone can give you a zip of system to flash, that should erase it.
I would also suggest again heading to the official superSU thread and asking about your problem.
TCoreXxx said:
View attachment 4030838
Thanks, but unfortunately still the same problem
The international memory remains immediately after wipen, etc
Superuser simply does not want to disappear, it can not make my cell phone anymore.
Click to expand...
Click to collapse
I recognized the same problem. And i figured out. I can delete only one file at one time and then must go back and reboot recovery again when deleting files from system partition.
@Xelfmade perhaps you can check this?
---------- Post added at 07:29 AM ---------- Previous post was at 07:27 AM ----------
wangdaning said:
What exactly did you flash? I am guessing you flashed system again and it still was the same? Maybe someone can give you a zip of system to flash, that should erase it.
I would also suggest again heading to the official superSU thread and asking about your problem.
Click to expand...
Click to collapse
exactly that was what i did... Flash via fastboot
What should I now flash over fastboot?
Can one of you make an order as I tackle the whole problem?
Mobile still does not work and there are always errors that can not be written at once / Data, though mount.
Please really help, my mobile phone is totally broken with the software.
It's no fun just to go back and forth between Recovery and Fastboot.
Please provide instructions and help.