Database Info

HTC, One S (4) Can not delete SD (data are not deleted even after formatting)

I had already opened a post that no one has found a solution, I just have to give your phone to a service center HTC, my problem at this point is:
The data can not be erased, as the title, even with the formatting of the SD through the PC, so they are visible to anyone, and all my mail and all the other private data, photos, etc.. etc. .. This is something that disturbs me a lot, any of you know how to help me? If you need more information, just ask.

What have you tried?
I am going to suggest booting unto recovery and performing a data reset from there vice the settings menu.
If that doesn't work then give me some more details so I could help.
FYI, verify fastboot is not checked in your power settings.

dellenrules said:
What have you tried?
I am going to suggest booting unto recovery and performing a data reset from there vice the settings menu.
If that doesn't work then give me some more details so I could help.
FYI, verify fastboot is not checked in your power settings.
Click to expand...
Click to collapse
Format SD from PC, formatting OK - Switch phone to "Charge only" files and folders, all present.
Deleting files and folders with "Root EXplorer" - Restart Phone: all the files you are all still present.
Installation of utilities, programs or Apk file, even if the installation is successful, restart, everything goes back to the previous configuration without any alteration.
In short, it is as if the reboot, will mount the same image previous .
I tried to reinstall the Fastboot stock_boot.img and stock_recovery.img, the flash file is successful, but when it reboots no goes into recovery mode, we see only a moment, Recovery, and then go reboot.
I also tried to do the Fastboot boot recovery.img, it should be for a few seconds the white screen with HTC green then reboots with the old installation.
The phone often restarts when I try to camibare configuration, if I go "back to factory settings" but when you restart back as it was before, always the same image.
Forgive my bad english, thanks

My Huawei y520-u22 \data partition is read only

It's my sister's phone and I don't know What she did exactly all she said that she tried to install candy crush from google play and then the problem begun each time the mobile reboots after 5-8 seconds I get a ton of stopped working notifications mainly about google apps like "error com.google.process.gapps has stopped" which repeatedly appear each time I press OK and a ton of other stopped working errors like weather,settings and anything I try to open. No matter what I do uninstall any app, change settings, change wallpaper after reboot everything revert back I tried to wipe/factory reset but no dice, I tried to flash the stock rom using SP flash tool and flashed the rom successfully but nothing changed the same apps the same wallpaper I am not talking about the default apps and wallpaper no I am talking about the apps that my sister installed before like Facebook, whats app etc...
I thought about flashing a custom rom and picked one but it required custom recovery which in turn required root access I tried several programs like kingroot, oneclickroot through PC but didn't work then I tried to flash CWM recovery through SP flash tool following the instructions I found here http://forum.xda-developers.com/showpost.php?p=61359133&postcount=4 and again the recovery was flashed successfully but when I tried to go to recovery I found the stock recovery instead I tried to flash the recovery using Fastboot but Fastboot came up with this error:
"FAILED (remote: partition 'recovery' not support flash)" which when I looked around turn out to be an error related to locked bootloaders but as far as I know the bootloader on Huawei y520-u22 is unlocked but wanted to make sure so I tried this command "fastboot oem device-info" but it gave me ... as in processing and nothing for a very long time until I gave up and closed the cmd. I then tried to boot into safe mode after pressing the power button then tabbing the shutdown option and selecting boot into safe mode but the phone rebooted into normal mode as usual.
and now I am out of options what should I do ?
Edit: eventually I found that my problem like this guy http://forum.xda-developers.com/showthread.php?t=895628 was that the \data partition is read only but I can't fix it the way he did since he used advanced partitioning in clockworkmod recovery but I can't flash it or any other custom recoveries.

mostafa_0017 said:
It's my sister's phone and I don't know What she did exactly all she said that she tried to install candy crush from google play and then the problem begun each time the mobile reboots after 5-8 seconds I get a ton of stopped working notifications mainly about google apps like "error com.google.process.gapps has stopped" which repeatedly appear each time I press OK and a ton of other stopped working errors like weather,settings and anything I try to open. No matter what I do uninstall any app, change settings, change wallpaper after reboot everything revert back I tried to wipe/factory reset but no dice, I tried to flash the stock rom using SP flash tool and flashed the rom successfully but nothing changed the same apps the same wallpaper I am not talking about the default apps and wallpaper no I am talking about the apps that my sister installed before like Facebook, whats app etc...
I thought about flashing a custom rom and picked one but it required custom recovery which in turn required root access I tried several programs like kingroot, oneclickroot through PC but didn't work then I tried to flash CWM recovery through SP flash tool following the instructions I found here http://forum.xda-developers.com/showpost.php?p=61359133&postcount=4 and again the recovery was flashed successfully but when I tried to go to recovery I found the stock recovery instead I tried to flash the recovery using Fastboot but Fastboot came up with this error:
"FAILED (remote: partition 'recovery' not support flash)" which when I looked around turn out to be an error related to locked bootloaders but as far as I know the bootloader on Huawei y520-u22 is unlocked but wanted to make sure so I tried this command "fastboot oem device-info" but it gave me ... as in processing and nothing for a very long time until I gave up and closed the cmd. I then tried to boot into safe mode after pressing the power button then tabbing the shutdown option and selecting boot into safe mode but the phone rebooted into normal mode as usual.
and now I am out of options what should I do ?
Click to expand...
Click to collapse
Hmm...
First, tell her to quit using Facebook app, Facebook Messenger, WhatsApp and other social media and texting apps. I know she just HAS to keep up with all her friends and the latest gossip but her device can't handle all those system demanding apps, they are literal HELL on mid-low end devices. They all constantly run scanning for updates and notifications, CONSTANTLY. They are notorious for making devices act crazy, especially when you have more than one of them.
For Facebook, its best to bookmark the Facebook page in mobile browser then create a shortcut for that bookmark on her homescreen, then it has to be set so that it loads the desktop site for Facebook, then she can view her Facebook messages, if it isn't set to load desktop site it will request she install messenger but she won't need to if she uses the desktop site to view messages. Then she can set her Facebook notifications to go to her gmail account, then in gmail app she needs to make sure it is set to receive notifications for gmail, then when she gets messages or activity on Facebook she will get a gmail notification in her status bar letting her know to check Facebook, then she can open the bookmark to view it. That is just as convenient as having the two apps but without all the strain on the device, also takes less space on internal and has less junk running in the background eating mobile data and draining battery.
As for her texting apps such as WhatsApp, Kik, Snapchat, etc., she needs to pick 1 or at the most 2 of them and leave the others alone, her device will run much faster and smoother.
You can try booting to recovery and wipe cache partition(not factory reset).
As for fastboot and SP flashtool not working, do you have USB debugging enabled in developer options on the device?

well thanks for your reply your advice about phone usage is great but wouldn't matter If I can't revive this phone anyway yes I tried both to wipe cache partition and wipe data and yes I enabled USB debugging but in case of SP flash tool all i need to do is have the proper drivers shutdown the phone click download in SP then connect the phone using USB cable then the red bar would fill up then another yellow one then a big green OK tick and nothing would change in the phone and for Fastboot all I need to do is shutdown then power + volume up then select fastboot then connect the phone then open cmd and type fastboot devices it would show the device Id then use the command fastboot flash recovery recovery-cwm-y520.img then I get the error "FAILED (remote: partition 'recovery' not support flash)" interestingly I got my hands on a normally working similar set which I tried several things on it like *#*#7378423#*#* It accepted the code but didn't do/show me anything just like my broken set then having the set in Fasboot mode I tried "fastboot oem device-info" which yielded nothing but ... just like my broken set other things I tried on my broken set I tried following this guide http://forum.xda-developers.com/showpost.php?p=38337401&postcount=5 using "Mtk_Droid_Tool_v2.5.3" to create CWM recovery for my phone and got the error
error :no find kernelgz
error: no split boot image
then I tried to use easy magic Philz touch installer which eventually asked for root access on the phone
but I can't since I tried every root method and didn't work.
I even made a logcat if it would help I could attach it

mostafa_0017 said:
well thanks for your reply your advice about phone usage is great but wouldn't matter If I can't revive this phone anyway yes I enabled USB debugging but in case of SP flash tool all i need to do is have the proper drivers shutdown the phone click download in SP then connect the phone using USB cable then the red bar would fill up then another yellow one then a big green OK tick and nothing would change in the phone and for Fastboot all I need to do is shutdown then power + volume up then select fastboot then connect the phone then open cmd and type fastboot devices it would show the device Id then use the command fastboot flash recovery recovery-cwm-y520.img then I get the error "FAILED (remote: partition 'recovery' not support flash)" interestingly I got my hands on a normally working similar set which I tried several things on it like *#*#7378423#*#* It accepted the code but didn't do/show me anything just like my broken set then having the set in Fasboot mode I tried "fastboot oem device-info" which yielded nothing but ... just like my broken set other things I tried on my broken set I tried following this guide http://forum.xda-developers.com/showpost.php?p=38337401&postcount=5 using "Mtk_Droid_Tool_v2.5.3" to create CWM recovery for my phone and got the error
error :no find kernelgz
error: no split boot image
then I tried to use easy magic Philz touch installer which eventually asked for root access on the phone
but I can't since I tried every root method and didn't work.
I even made a logcat if it would help I could attach it
Click to expand...
Click to collapse
The advice does more than help, its actually the REAL solution to the problem. If you get it fixed and she's still using all that crap it'll just cause issues again, I'm sure you don't want to have to go through all of this a second time, right?

Droidriven said:
The advice does more than help, its actually the REAL solution to the problem. If you get it fixed and she's still using all that crap it'll just cause issues again, I'm sure you don't want to have to go through all of this a second time, right?
Click to expand...
Click to collapse
God no of course not I will till her to keep her apps in check and use as minimum social apps as possible but right now that won't help me revive this phone :crying:

mostafa_0017 said:
God no of course not I will till here to keep here apps in check and use as minimum social apps as possible but right now that won't help me revive this phone :crying:
Click to expand...
Click to collapse
I don't get how installing a game caused this, I believe there has to be more to the story somewhere, somehow.
Besides, with some of the steps you've taken, you've probably created other issues than it started with. Whatever you do, don't format the device in SP flashtool, you'll probably lose IMEI if you do that.

Droidriven said:
I don't get how installing a game caused this, I believe there has to be more to the story somewhere, somehow.
Click to expand...
Click to collapse
me too man me too I didn't believe it at all installing an app won't do all of this but at one point when I was rebooting I got this suspicious message which I took a couple of bad quality pictures for it here http://imgur.com/a/RIGqD

actually I have grown very confident dealing with the phone that no matter what I do It wouldn't matter since it will come back just as always and now I didn't create any other issues since no matter what I hit a dead end the device revert back no matter what I do, Do you feel me I am starting to go insane I am pretty sure even If I tried to brick this device on purpose I won't be able to.

mostafa_0017 said:
me too man me too I didn't believe it at all installing an app won't do all of this but at one point when I was rebooting I got this suspicious message which I took a couple of bad quality pictures for it here http://imgur.com/a/RIGqD
Click to expand...
Click to collapse
Your pic keeps directing me to the imgur app to view it, I'm not installing the app just to view it, why not just upload the pic as an attachment to your post and it will display in your post instead.

Sorry old habits die hard I used to talk in this one forum before and their rules forbid to upload images or anything actually as attachments except in extreme cases here they are
hmmmm strange can't find the attachment button guess I will just post direct links hope they work
http://i.imgur.com/OrSWbzE.jpg
http://i.imgur.com/EcmrDlI.jpg

mostafa_0017 said:
Sorry old habits die hard I used to talk in this one forum before and their rules forbid to upload images or anything actually as attachments except in extreme cases here they are
hmmmm strange can't find the attachment button guess I will just post direct links hope they work
http://i.imgur.com/OrSWbzE.jpg
http://i.imgur.com/EcmrDlI.jpg
Click to expand...
Click to collapse
When did you say it displayed that? That looks fishy, the grammar is a little off as if whoever made that didn't quite know the language, kinda like the way grammar isn't quite right like some of the questionable Chinese apps known to be malware.
If you're using a browser you have to select "go advanced" under the box you reply in, then you'll see "manage attachments"
If you're using an app you should see a paperclip symbol or a pic thumbnail.

Droidriven said:
When did you say it displayed that? That looks fishy, the grammar is a little off as if whoever made that didn't quite know the language, kinda like the way grammar isn't quite right like some of the questionable Chinese apps known to be malware.
If you're using a browser you have to select "go advanced" under the box you reply in, then you'll see "manage attachments"
If you're using an app you should see a paperclip symbol or a pic thumbnail.
Click to expand...
Click to collapse
Yeah thanks found it and it displayed this only one time when I was rebooting after doing various things and I never saw it again and yeah the grammar felt really strange when I googled its content I only found a couple of Spanish forums talking about this but couldn't get any information about the source of this message and that's why I thought about the logcat in the first place.

the same problem
hi i have the same probleme with my huawei y520 u22 i can do nothing just start up the phone i got the message and i can do nothing when i try to unistall any app the phone restart and go back to the same situation wipe cache and wipe data nothing change flashing 1000000000000000000 roms nothing change any one can tell me there the problem is
as i think the flash memory is the problem its blocked in write and read.
any solution plz

I read this and just think, what the hell... i can not understand why "/data" is write protected. Just some thoughts running through my head:
- phone is not rooted and completely stock, but factory reset not working!? in this case ask for warranty and send it back to seller!
- if no warranty, ask Huawei for support. don't tell much, just claim factory reset is not working.
- ask any mobile repair shop, they have special hardware like Octoplus Box and can do factory reset.
- if possible - make a "backup user data" with Android system recovery, you may restore it on working phone, later.
- if you have read-access to "/cache/recovery" look for file "last_log" and copy to sdcard. "/proc/emmc" and "/proc/partitions" are another useful files. keep this in case you have to manually create the scatter file.
- you can use MediaTek SP Flash Tool Readback function in download mode to make a ROM backup dump. for readback you need to install VCOM Drivers, then first click Read back, then connect the phone to PC while switched off and insert battery. MTK Droid Tools will then help to segment the partitions from it. or readback every partition separately with scatter file. the most important files are "nvram.bin", "preloader.bin", "boot.img", "recovery.img".
- if phone is locked, ask Huawei for unlock code (not sure if this works on broken phone). there are different kinds of S-ON some will lock only bootloader, some lock all partitions, too.
http://www.modaco.com/forums/topic/362724-official-code-request-to-unlock-the-bootloader-final-post
- try fastboot mode factory reset (not sure if working, just googled this stuff i found).
http://www.hardresetandroid.com/hard-reset/huawei-hr/huawei-ascend-y520-hard-reset-code-format-solution
- once you have unlocked the phone, do factory reset. phone should boot now. its hardly imaginable that "/system" is damaged because of never rooted the phone.
- if still not working, you should now be able to flash custom recovery, too. be careful, select tested binary for your special phone model only! flash in fastboot mode. avoid flashing with SP Flash Tool as long as you not absolute sure that scatter file is 100% correct (MTK Droid Tools may give you wrong scatter files for devices > 4 GB!)
- from custom recovery, you should able to root the phone via adb root method or install the "supersu.zip"
- once you have root, you can mount data partition read-write from adb shell (in recovery mode) and format or delete it. of course the custom recovery has a wipe data option, too.
- installing aroma file manager zip is another way to browse and modify everything in recovery mode. you can copy files from similar phone into "/system" folder, if phone still not working properly.
- don't restore a full backup from similar phone (especially NVRAM folder), this may clone IMEIs and WiFi MAC address.
- you can install a stock rom zip from custom recovery instead, and use my script bckp2cwm.zip to convert the user data backup into cwm format and restore "/data" folder only (converting script requires linux pc).
- delete suspicious apps from "/data/app" + "/data/dalvik-cache" + "/data/data" (every app has three entries with similar name). do it in recovery mode with aroma file manager, or on linux pc from backup file during converting (at this point where script is waiting for user input).
- search and read for "unbrick guides" on forum.xda-developers.com, as long as it is not a physical damage (Vol keys not working, emmc wearing out, etc) there must be a solution to get this phone working

- if no warranty, ask Huawei for support. don't tell much, just claim factory reset is not working.
yeaah I don't think they would respond with any helpful answer and would probably tell me to send my phone to the nearest service center.
- ask any mobile repair shop, they have special hardware like Octoplus Box and can do factory reset.
That's what I settled for eventually and I already sent it to my sister and told her to visit any mobile repair shop that has boxes like miracle box and such.
- you can use MediaTek SP Flash Tool Readback function in download mode to make a ROM backup dump. for readback you need to install VCOM Drivers, then first click Read back, then connect the phone to PC while switched off and insert battery. MTK Droid Tools will then help to segment the partitions from it. or readback every partition separately with scatter file. the most important files are "nvram.bin", "preloader.bin", "boot.img", "recovery.img".
done that already but what I got in the end didn't help me to fix the phone note that I don't care about the phone's content sure I care about the IMEI but the phone is not affected by any write attempts so I am not so worried.
- if phone is locked, ask Huawei for unlock code (not sure if this works on broken phone). there are different kinds of S-ON some will lock only bootloader, some lock all partitions, too.
I searched online and in threads talking about custom roms and recoveries for this phone and not a single one of them mentioned anything about the bootloader being locked.
- try fastboot mode factory reset (not sure if working, just googled this stuff i found).
haven't tried that but will try it ASAP since I don't have the phone right now.
One last note the phone boots normally but as I described in my later posts I can't edit anything without it reverting back after restart like changing the wallpaper or uninstalling an app.
And anyway thank you for your respond.

did you try to get (temporary) root access?

aIecxs said:
did you try to get (temporary) root access?
Click to expand...
Click to collapse
Not sure of What you mean but I think I tried and failed you can tell me What you mean exactly and I will tell you If I tried .
Edit: Alright I googled it and turn out to be temporary root for locked bootloader devices no special procedure just the same procedure as in permanent root but will lose root as soon I reboot again I tried a lot of rooting methods including kingoroot and 360root.

Not sure, too.. installing kingoroot.apk and root the phone may give root access until reboot (can't remember if rooting requires a reboot)?

Brainstorming. Lets come from other side. When you intend to write a malware - how would you realize this setting?
one thing is remount /data partition read-only, but is this really enough? what happen if /data is not writeable anymore - apps should crash or give errors on write cycle, didnt they?
but you claim phone is changeable until reboot. so we need the possibility to let them write in some other memory without noting that it storage has changed.
another way is copying /data to any hidden storage, and restore it on each reboot, but this should be time consuming, didnt it? and where can this amount of data be stored? sdcard? cache partition?
besides this, guess the malware needs root access to modify /data. or is it imagineable to change it without root access? lets find a conception to understand whats going on

No reboot is fast and not time consuming and I am always working on the phone without the SD card and about apps sometimes uninstallation is complete and the app disappear to show again after reboot and sometimes the phone restart upon uninstallation of an app

[SOLVED] Wi-fi "memory" reset on every disabling!

Hello,
I got a little problem with my phone (so freak... I'm explaining)
I got a router before but now I changed it, because I switched to another operator. But it feels like the Wi-fi of my phone is not agree with that.
I "forget" the now inexisting router I had and connect to the new one...
...But I do this each time I turn off then on Wi-fi, and even after switching off the device with enabled Wi-fi!
For now I just have to remember one Wi-Fi router (and, thank you Kika Keyboard developers who made an extensive clipboard where I can store my password <3) but figure out what it will be when I'll have to save more passwords! So yes it's annoying. And I also already lost at leat 8 router passwords because of this strange cr*p.
Fortunately I got a Wi-fi retriever app but this is not auto connecting and this is no longer working!
That was the last point: even the router password retriever app is acting like I didn't connect to a new router since its last analyze!
So could you help me fix this annoying bug?
For now I got an hypothesis: I got XPosed and a device ID changer app.
And it contains an useless but impossible to disable option that is "changing the SSID"
Default configuration make your phone to display your SSID. But not with the local variable where your actual SSID is displayed! No, with the SSID you got when you installed the app. So you can connect to another Wi-fi and still got the same SSID (perfectly useless)
Rest of my theory is that messing up with SSID display may cause network state not to be saved properly. But this is only a supposition. And this is hard to figure it...
So to corroborate this theory, a subquestion: What is the local Android variable where SSID is stored? Tried %WIFI, %SSID but it doesn't work. And I didn't found it after a quick search.
Thank you in advance!
Sorry for wasting your time with so much text :/

https://android.stackexchange.com/questions/124792/my-phone-stopped-remembering-wifi-passwords
There are also people conplaining this problem.
In the link pasted on the top, there is a possible fixes for some fortunate people... But actually this doesn't work for me.
-First, ro.secure.storage or ro.securestorage. thing does not exist on my device. I don't even know if it existed on my device.
-Second, there is something about /efs/ss_data, a file that also not exists on my device.
So I don't know if it's because Samsung built it differently or it has been removed. Keep checking...

After a check of my backups I saw that I got none of the file and property mentionned before.
So I'm unable to know where is the problem...

Atronid said:
After a check of my backups I saw that I got none of the file and property mentionned before.
So I'm unable to know where is the problem...
Click to expand...
Click to collapse
If you're saying that you looked in build.prop but you don't see any lines that say ro.securestorage, you can add those lines if they don't exist. Just edit build.prop and type the line in at the bottom then save build.prop and reboot the device.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Droidriven said:
If you're saying that you looked in build.prop but you don't see any lines that say ro.securestorage, you can add those lines if they don't exist. Just edit build.prop and type the line in at the bottom then save build.prop and reboot the device.
Click to expand...
Click to collapse
This is what I did. Uneffective.
Why? Because I never got this prop before.
I checked my backups where the Wi-fi worked perfectly in case all of this would be due to the fact that this prop vanished because of a dark and random informatic process. And after checks I finally realized that I never had this prop...
Same thing for the file I mentionned before, located in /efs. I didn't lose it because I basically never got it.
So... This means that my device save Wi-fi informations by another way. And because I don't know this way, I cannot fix it...
(Device: Samsung Galaxy Core Prime SM-G361F AOG1 build.
Pre-rooted firmware, release date 23 February.
Latest Xposed Frameworks, Custom build by Wanam )

Atronid said:
This is what I did. Uneffective.
Why? Because I never got this prop before.
I checked my backups where the Wi-fi worked perfectly in case all of this would be due to the fact that this prop vanished because of a dark and random informatic process. And after checks I finally realized that I never had this prop...
Same thing for the file I mentionned before, located in /efs. I didn't lose it because I basically never got it.
So... This means that my device save Wi-fi informations by another way. And because I don't know this way, I cannot fix it...
(Device: Samsung Galaxy Core Prime SM-G361F AOG1 build.
Pre-rooted firmware, release date 23 February.
Latest Xposed Frameworks, Custom build by Wanam )
Click to expand...
Click to collapse
If you got a different router but kept the same network name and password and didn't change anything on your device, that might be the issue, your device is probably looking for your original router because the information you originally saved was saved while the other router was in use.
Try backing up your apps, app data and settings but don't backup your wifi settings or saved wifi information. Then boot to recovery and factory reset and wipe cache and dalvik/ART. Then reboot the device, when it boots to system, try connecting and signing into your network again and see if it saves it correctly.
If the backups you are talking about are nandroid backups created in TWRP, you can also try doing an advanced restore in TWRP, you can restore just the data from your previously working backup without restoring everything else.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Thank you, I'll try this out

Droidriven said:
Try backing up your apps, app data and settings but don't backup your wifi settings or saved wifi information. Then boot to recovery and factory reset and wipe cache and dalvik/ART. Then reboot the device, when it boots to system, try connecting and signing into your network again and see if it saves it correctly.
If the backups you are talking about are nandroid backups created in TWRP, you can also try doing an advanced restore in TWRP, you can restore just the data from your previously working backup without restoring everything else.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
Well, tried what you told me and this didn't end well...
I used to make a factory reset of my phone. The problem was fixed. When I connected to the wifi first time, now each time I disabled and re-enabled it automatically reconnected (auto-connect is miraculous lol)
Then I flashed data back with TWRP recovery (backup by Nandroid app because I got a classical TarFork error with TWRP 2.7.0.1...)
When rebooting to Android it spammed 1M layers of various program crash message box.
Then using TWRP I reflashed this time everything I got then rebooting to Android the bootloader freezed.
I thought my phone was dead until I realized I could boot to recovery again. So I flashed an older backup and lost some data (fortunately I backed up SMS and apk).
My device is safe now, but this misadventure taught me lots of things:
-When I did a factory reset data has been erased, but system still the same and it reworked. So maybe an app is locking my Wi-fi like this. But which?
-Nandroid backup app is NOT reliable. If your device isn't clearly identified your backups are corrupt. Gotta erase all Nandroid backups I made.

Solved. Bug due to a bad TWRP backup. Made a fresh install and everything is fine now.
Thread closed.

cannot use adb to solve continuous reboot - device offline

I have oneplus one came from chineese retailer already rooted and with adware. always meant to reflash with straight CM or with a version of AOSP, but ended up use adb (which I have for development, though I am NOT experienced in using adb, flashing rom or what ever only programming) to disable a number of apps and it seemed to be stable.
More recently I had a phone crash following the crash of an app that I think is the CM app launcher, something begining with t, trebuchet?, i dont recall. Since then the phone keeps rebooting and I cannot seems to use adb, the device is either not present or offline.
I can boot to cyanogen recovery which offers:
- reboot system now
- apply update
- apply from adb
- choose from internal storage
- wipe data/factory reset
- wipe cache partition
- wipe media
If I select apply from adb then the device is nolonger offline but in sideline mode, but I don't think this is what I want.
I never liked CM and I had always thought that I might try to flash with a version of AOSP if possible and I wondered if now was the time. I thought TWRP might be useful for this and the first step to installing this was:
C:\...\Downloads>adb reboot bootloader
but I get
error: closed
I briefly see the debugging notification before the phone reboots but in adb it is always not present or offline.
How do I get to the point of either solving my repeating reboot at least or preferably installing a version of AOSP that would be compatible with OnePlus One, preferably without destrying data. I think the data is in a different partition or something but I have forgotten the little I learnt about this a few years ago.
I would be so grateful of some help and learning, right now to all intents and purposes I have a nice looking brick.

hardya said:
I have oneplus one came from chineese retailer already rooted and with adware. always meant to reflash with straight CM or with a version of AOSP, but ended up use adb (which I have for development, though I am NOT experienced in using adb, flashing rom or what ever only programming) to disable a number of apps and it seemed to be stable.
More recently I had a phone crash following the crash of an app that I think is the CM app launcher, something begining with t, trebuchet?, i dont recall. Since then the phone keeps rebooting and I cannot seems to use adb, the device is either not present or offline.
I can boot to cyanogen recovery which offers:
- reboot system now
- apply update
- apply from adb
- choose from internal storage
- wipe data/factory reset
- wipe cache partition
- wipe media
If I select apply from adb then the device is nolonger offline but in sideline mode, but I don't think this is what I want.
I never liked CM and I had always thought that I might try to flash with a version of AOSP if possible and I wondered if now was the time. I thought TWRP might be useful for this and the first step to installing this was:
C:\...\Downloads>adb reboot bootloader
but I get
error: closed
I briefly see the debugging notification before the phone reboots but in adb it is always not present or offline.
How do I get to the point of either solving my repeating reboot at least or preferably installing a version of AOSP that would be compatible with OnePlus One, preferably without destrying data. I think the data is in a different partition or something but I have forgotten the little I learnt about this a few years ago.
I would be so grateful of some help and learning, right now to all intents and purposes I have a nice looking brick.
Click to expand...
Click to collapse
Did you try factory reset?

Thank you so much for your the suggestion, I appreciate it.
Not yet I haven't. I'm not familiar with the CM Recovery Software and the option is entitled "wipe data/factory reset". Do you happen to know if this means bother or either and if selecting this explains more and gives options before proceeding. Key is I want to avoid wiping data if possible because while most is sync'd offline some is recent and not or not for particular reasons.
If there's a choice then will "factory reset" leave personal data alone? Do you know, will the factory reset likely be to version/adaptation of CM put on by rooting retailer PLUS anoying/mal/ad/ware apps put on by rooting retailer.
If this is my only option then I will go ahead and do it and take the hit.
If following this, it is possible to install a stable Android 7.n.n AOSP only that will support the hardware and leave data intact (ONLY LEAVE DATA IF POSSIBLE) I would be very grateful for a clear and complete script to achieve this. I was a professional developer for 20 years, now semi-retired, so I know what I know and what I don't know in terms of foundational knowledge, taking care etc etc, but I am very inexperienced in flashing phones and using ADB except the fact the eclipse/android studio uses it.
I used a windows script to install fastboot if that is any help (though the script did show some errors it still said "All Done!" at the end. Tried to C&P the errors but failed). I can also try to install TWRP (or what ever) if that's any help.
Many thanks would really appreciate your help in my getting my OnePlus One working and stable again.
Andrew.

hardya said:
Thank you so much for your the suggestion, I appreciate it.
Not yet I haven't. I'm not familiar with the CM Recovery Software and the option is entitled "wipe data/factory reset". Do you happen to know if this means bother or either and if selecting this explains more and gives options before proceeding. Key is I want to avoid wiping data if possible because while most is sync'd offline some is recent and not or not for particular reasons.
If there's a choice then will "factory reset" leave personal data alone? Do you know, will the factory reset likely be to version/adaptation of CM put on by rooting retailer PLUS anoying/mal/ad/ware apps put on by rooting retailer.
If this is my only option then I will go ahead and do it and take the hit.
If following this, it is possible to install a stable Android 7.n.n AOSP only that will support the hardware and leave data intact (ONLY LEAVE DATA IF POSSIBLE) I would be very grateful for a clear and complete script to achieve this. I was a professional developer for 20 years, now semi-retired, so I know what I know and what I don't know in terms of foundational knowledge, taking care etc etc, but I am very inexperienced in flashing phones and using ADB except the fact the eclipse/android studio uses it.
I used a windows script to install fastboot if that is any help (though the script did show some errors it still said "All Done!" at the end. Tried to C&P the errors but failed). I can also try to install TWRP (or what ever) if that's any help.
Many thanks would really appreciate your help in my getting my OnePlus One working and stable again.
Andrew.
Click to expand...
Click to collapse
Okay,since you want to flash Aosp N,leave that factory reset thing.
https://forum.xda-developers.com/showthread.php?t=2788632
This thread should be enough atm.Everything has been explained,and it's just simple copy paste,so,even if you're unfamiliar with adb,you should be able to do just fine.
Just follow,install adb/fastboot drivers,unlock bootloader,and flash twrp.
Now,unlocking bootloader will format internal storage,which means everything....but,a simple adb command should be able to back everything up into your pc.
Ensure your adb/fastboot drivers are already installed,and using adb devices in cmd shows your connected device id,before below process!
adb backup -apk -shared -all -f C:\Users\NAME\backup.ab
Where "NAME" is the name of your Windows user name.
On the device, a new screen should appear. If you want to encrypt the backup, enter a password -- otherwise, tap Back up my data. The backup will begin, and you'll find the backup file in the folder declared in the backup command.
Depending on how much data your device holds, this process can take quite some time.
The restoration process is simple. Connect the device to be restored and (from the same location you issued the backup command) enter the command:
adb restore C:\Users\NAME\backup.ab
Where NAME is the name of the same Windows user from the backup process.
Again, depending on how much data is on the backup, the restore process can take some time.
Click to expand...
Click to collapse
When you're done doing all of this,just follow any rom's thread instructions to flash that rom.
Btw,you're on Cos13.1.x,yes?

So sorry for not replying to say thank you sooner, I have been busy with family issues.
Thank you so much for your response, I really appreciate it. I shall take a look at this soon and try to get regular android N on the phone soon. Thank you.

I'm just starting to read and work through this. Just to clarify, re my original post, is the fact that my phone is continually rebooting and that adb shows the device as offline a problem? Will I still be able to use adb to backup the phone contents? Do I need any special understanding to do that?

I finally came back to this and flashed a new rom carbon rom. I only noticed afterwards that there is very little support for this rom and I've had some issues.
If you think the issues are in some way generic and you have come accross them before you may have some ideas:
- there is no built in task manager and third party ones do not seem to cover the apps I am interested in. Any ideas why there is no built in task manager anymore like there used to be and how one might be able to turn it back on?
- the camera does not work and the open camera I installed instead has some image faults (or misunderstood feature). Big line down the middle of the image.
Any ideas.

How to debug data related bootloop?

begonia (Xiaomi Redmi Note 8 Pro), MIUI 11.0.6.0
I had an unfortunate series of events that resulted in a booloop. Basically:
- Magisk suddenly stopped working one day, after 1.5 year of no issues. I did nothing related to it recently, except just using root functionalities in e.g. Tasker
- I flashed newer Magik 23 and also updated TWRP fom 3.3.1 to 3.5.2
- everything worked fine up until one restart, which resulted in TWRP encryption problems. Right before restart I'm pretty sure I installed Viper4android. I could still get into system with a workaround of TWRP's "Decrypt user" hanging into button reboot, but Magisk/root wasn't working anymore
- so I thought reflashing Magisk and dm-verity/forceencrypt would help, but here's where the bootloops started. During the flash attempts I saw some partition mounting errors since the device was decrypted, so maybe that caused some data issues?
I tried now:
- downgrading TWRP to 3.3.1 - decryption works fine in it and I can flash problemlessly from it, however, doesn't help with bootloop. Reflashing Magisk/dm-verity zips from it also didn't help
- flashing recovery ROM (the same MIUI I had - 11.0.6.0) changed nothing
- flashing fastboot ROM in MiFlash with "save user data" option changed nothing, except I guess confirming the issue is with data
- last thing I tried was flashing uninstall.zip for Magisk since that removed its data folders, which I thought may have got corruped, also to no avail
I know it would probably get fixed with data wipe, but I need the data - I have hundreds of apps with lots of configuration for permissions, notiications, etc. and my recent backups from few months ago vanished because SD card got lost. I have a TWRP 3.3.1 backup of the data now, too bad I didn't do it before updating Magisk/TWRP - lesson learned... So the question is - what can I still do to further debug and fix this without losing data?
I read that reading these logs may also help with debugging, but not sure what to look for.
Kernel log (/proc/lastkmsg): https://pastebin.com/T2xBBRvi - some error looking lines at the end, but non-comprehensible. Can I use them somehow futher?
dmesg log: https://ghostbin.com/paste/vyBDk - don't really see anything here, but it's quite long and not sure what to look for
logcat: https://ghostbin.com/paste/PSh7f - lots of "avc" errors
Please help

Bump. Any help would be appreciated

Plug in the USB cable with the phone powered off. Then issue the commands
Code:
adb devices
adb wait-for-device
adb logcat
from your Windows CMD or Linux terminal: it will hang waiting for the device to come on-line, now power up the phone. The logcat should start scrolling off then.

While it's turned off:
Code:
$ adb devices
List of devices attached
mfaajbdu5s79pfhy unauthorized
If you `adb wait-for-device`, the cmd just waits and you can't enter next command.
`adb logcat`, if I skip the above, waits for device itself, but nothing happens, it just restarts to TWRP and the commands still hang. I can use logcat while in recovery though, that's what I did above

Ok, so I just went ahead and tried the following, too:
- made sure the TWRP data backup can get restored, just in case
- wiped data through TWRP, still the same (re)bootloop into TWRP. I tried both factory reset and advanced wipe with Dalvik/Data/ntenal Storage/Cache.
- so I tried reflashing 11.0.6.0 using MiFlash with that erasing data. That at least worked and phone boots after doing this, but unfotunately not what I'm looking it
- I then tried to get TWRP 3.3.1 back. I got into that and the usual rooting steps were invalid - recovery_fromboot ile was not present in system_root/system. Maybe that's not just present in downloadable ROMs? No clue, but doing the rest of required rooting steps - Magisk 23 install -> Close AVB (TWRP action) -> Remove dmverity (TWRP action) resulted this time in infinite type of bootloop, not sure why, waited for over 30 minutes
- so I reset into TWRP and tried flashing the dmverity zip that's from xda. And this is definitely what caused previous (re)bootloop as after flashing that its more or less the same time length before boot stops and restarts into TWRP. Now, weirdly, while installing this there was an error this time, saying that nvdata cannot be mounted
So I guess the problem before was with mounting nvdata? I see it's something related to phone's IMEI. How does it work exactly, is it somehow related to /data partition? Why wouldn't it mount? Why does it work with pure standard flashed ROM? Is it supposed to be empty when you look at it with TWRP's file manager? Could be something else but this is my only clue right now...
EDIT: oh, you can mount it in TWRP and that works fine, it's not empty. Not sure why that install scipt suddenly stated claiming it can't be mounted, by the end of log, though.

Completely no insights?

I'm coming back to the topic after almost 1 year on old backup phone because I got depressed by this incident and couldn't continue working on it. The old one is like 6 years old, it has abysmal battery life, it ran out of space and I can't install certain apps on older Android, I'm also missing a lot of the set up that I had and which was pretty convoluted - with Tasker and lots of other heavily configured apps. Which slows me down each day.
I can bring the new phone into usable state anytime, a matter of less than hour and reflashing the soft completely, however, setting it up initially took me one year of almost daily changes, many of which can't be retraced as my Titanium backup is old for some reason and there were a bunch of root related changes.
So any sort of help as to how I could potentially recover it with the data would be really appreciated.

And bump

Let's try a bump again

And one more hopeful bump. I'm even willing to pay/donate for any useful insight that will lead to progress with this as my old backup phone is becoming unusable and I don't want to start setting up this one from scratch again.

One last bump before trying in a new topic.
TLDR: what's the best way to debug a bootloop? Do the logs above help or is there something else?

Destroy666x said:
I'm coming back to the topic after almost 1 year on old backup phone because I got depressed by this incident and couldn't continue working on it. The old one is like 6 years old, it has abysmal battery life, it ran out of space and I can't install certain apps on older Android, I'm also missing a lot of the set up that I had and which was pretty convoluted - with Tasker and lots of other heavily configured apps. Which slows me down each day.
I can bring the new phone into usable state anytime, a matter of less than hour and reflashing the soft completely, however, setting it up initially took me one year of almost daily changes, many of which can't be retraced as my Titanium backup is old for some reason and there were a bunch of root related changes.
So any sort of help as to how I could potentially recover it with the data would be really appreciated.
Click to expand...
Click to collapse
Titanium backup is now broken, at least the recovery is now broken. You also are not allowed to start duplicate threads.

Titanium backup doesn't really help me anyways. And ok, I guess I'll keep bumping it then...

Can you access fastboot?