Database Info

Device isn't working properly after wiping...

So I have a problem with my Nexus 5. Yesterday I tried all kinds of different Lollipop roms and at the end of the day I sticked to Cataclysm. I liked it and my phone was all set up but I noticed there were a lot of unnecessary folders on my internal storage and a nested 0 folder (0 inside /0). I didn't like that so I thought about making a nandroid backup, storing it on my computer (together with my music etc.), wiping everything and restoring it by using TWRP and then eventually putting my music back.
So after I stored a backup on my computer, I started my device into recovery mode and chose the option 'advanced wipe'. Usually I would do a lot of research for everything I do but in this case I was a bit lazy to do that, I tried digging into the search results of Google concerning wiping but I gave up after some unsatisfying results. So I checked every box in the list, including data and system and went through with the wiping. So because my storage was completely wiped I didn't have a 'WRTP/BACKUPS' folder anymore. I made a backup from the stuff I had (which was only a few mb's) so I would have that folder again (otherwise I wouldn't be possible to locate my nandroid backup). I wanted to transfer my nandroid from my computer to my phone by connecting it through USB but for some reason the Nexus 5 didn't show up on my PC when it was booted in recovery (this sometimes happens for some reason)
I managed to do it by using 'adb push Cataclysm folder' in cmd. I went into recovery and restored my backup. My phone booted and I thought everything was as it should be. The wallpaper was black but that was logical because my internal storage was wiped, including my custom wallpaper. But then I noticed something strange, my status bar disappeared, sames goes for my navigation bar. I really have no idea what happened because I've restored nandroid backups before and everything went fine.
So then I put a clean version of Cataclysm on my phone and for some reason it asks me to insert a SIM-card into my device while it has one. I skipped that step and then it asked for my home Wi-Fi and I chose mine, then it checked the connection way longer than it would normally do. After I was done with all the steps my homepage entered my screen and guess what, my status bar and also my navigation bar were absent. It was like my cell phone was in immersive mode all the time. Then I tried flashing the KitKat factory image by going into recovery with my phone and opening 'flash-all.bat' on my PC but then it said '< waiting for devices >' while I enabled USB debugging... I opened cmd and typed 'adb decives' and mine showed up, so it was connected (although it now says 'unauthorized' when my phone is normally booted).
Then I flashed clean Cataclysm again and it again said I had to insert my SIM-card and it then again checked the connection with the Wi-Fi for a couple of minutes. When I was done with the installation I tried replacing the wallpaper with one from Lollipop but it didn't work although there was a preview available. There was again no status bar and navigation bar. I then opened chrome and went to this website and now I'm typing this on my Nexus 5 which has a permanent immersive mode now.
So I don't have much in my internal storage anymore, only a TWRP folder with backups, nothing more, not even a 0 folder if I'm not wrong. There's something wrong with my mobile connection and definitely something going on with my navigation bar and status bar. I hope anyone could help me with this because this is really frustrating becausr I tried to fix it for the last couple of hours, unfortunately without any result...
EDIT: I forgot to mention that when I was trying to figure out how to send the nandroid without being able to access my internal storage via my computer, I booted in recovery, went to 'advanced' and then to 'adb sideload' and tried that because I saw it somewhere on the internet. I somehow believe this contributed to the problem I have.
EDIT2: Now, when I try to power off my phone by holding the power button, it reboots the device instead, what's going on... And as I said, I have a black screen as wallpaper for some reason and I can't change this, but if I open my weather widget, the widget window shows up with my chosen wallpaper on the background, what kind of sorcery is this?
EDIT3: I wanted to download a terminal emulator from Google Play to do this but I couldn't get to 100% so I thought there was something wrong with the app on my device. I googled the apk and I wanted to download it from Zippyshare and when I clicked on the button 'download now', the phone showed the message 'no SD card', so I guess that's the culprit of all of this?
TL;DR My phone is acting really weird (no status or navigation bar, phone reboots instead of asking whether I want to have it shut down when I hold the power button, the wallpaper being strange, SIM-card isn't being recognised) after I wiped data and system and actually everything...

Reboot to bootmanager , flash a factory image , wipe , start over . Something must have gotten corrupted in your nandroid backup.
Regarding ADB not working , you also need to authorize the pc you are working from . You will get a prompt on your phone when connecting . If you dont , go to developer setting , wipe ADB credentials , reconnect the phone.
Also , adb push works fine for single files but it sometimes borks when you are pushing big/many files.
Edit : I hope you didn't wipe EFS as well ( though AFAIK TWRP doesn't wipe it on a advanced wipe) . If you did it's time to return it to stock and send it to LG/Google

Niflheimer said:
Reboot to bootmanager , flash a factory image , wipe , start over . Something must have gotten corrupted in your nandroid backup.
Regarding ADB not working , you also need to authorize the pc you are working from . You will get a prompt on your phone when connecting . If you dont , go to developer setting , wipe ADB credentials , reconnect the phone.
Also , adb push works fine for single files but it sometimes borks when you are pushing big/many files.
Edit : I hope you didn't wipe EFS as well ( though AFAIK TWRP doesn't wipe it on a advanced wipe) . If you did it's time to return it to stock and send it to LG/Google
Click to expand...
Click to collapse
Thank you for reading my huge explanation. After hours of searching and trying a lot of things with my device I figured out how to fix it. Do you remember I said that when I tried to flash the factory image with 'flash-all.bat' that it responded with '< waiting for devices >' ? Well, after reinstalling the drivers countless times and trying to find the culprit I realised I was trying to flash it with TWRP being open, and not the bootloader... So after I was aware of that I finally managed to put stock Lollipop on my phone, then I wiped everything and flashed Cataclysm. It felt pretty satisfying to have a working phone again, it's a pity I had to start from scratch but on the other side, I now how a phone without any rubbish.
Regarding adb push, if I would like to ever push a rom or a big file onto my phone in case I would ever have a similar annoyance, what do you recommend me to do it with?
And what is EFS exactly and what happens if I would ever wipe that? Thank in advance!

Regarding ADB push / twrp MTP mode you jst need to remember not to try and upload the entire content of a sdcard backup or > 3-4 gigs. Big files rarely missbehave , but I screwed up my SD permissions when trying to restore my sdcard ( thousands of files and about 14 gb total).
EFS is a secure partition that stores your GSM/network id and profile - IMEI and so on. AFAIK it's pretty hard to erase but it is possible if you play around with format/repartition commands. Just follow the guides and instructions on this forum and it should be fine.
Corrupted or erased EFS = no network connectivity besides WiFi . And since tampering with it is illegal in some countries the only way to fix it is by RMA/warranty.
I'm glad you've fixed it - I'm not surprised it was a simple mistake , I've been there myself ( tried for an hour to flash a factory image unsuccessfully only to realize I had my phone plugged in a USB3 socket ) .
Don't forget to make a nandroid now that you are set up with your fav. ROM - it will come in handy sometime.

Niflheimer said:
Regarding ADB push / twrp MTP mode you jst need to remember not to try and upload the entire content of a sdcard backup or > 3-4 gigs. Big files rarely missbehave , but I screwed up my SD permissions when trying to restore my sdcard ( thousands of files and about 14 gb total).
EFS is a secure partition that stores your GSM/network id and profile - IMEI and so on. AFAIK it's pretty hard to erase but it is possible if you play around with format/repartition commands. Just follow the guides and instructions on this forum and it should be fine.
Corrupted or erased EFS = no network connectivity besides WiFi . And since tampering with it is illegal in some countries the only way to fix it is by RMA/warranty.
I'm glad you've fixed it - I'm not surprised it was a simple mistake , I've been there myself ( tried for an hour to flash a factory image unsuccessfully only to realize I had my phone plugged in a USB3 socket ) .
Don't forget to make a nandroid now that you are set up with your fav. ROM - it will come in handy sometime.
Click to expand...
Click to collapse
I'll definitely make a nandroid, just in case. Thanks for the help and the clarification!

Try wiping your bum more thoroughly

Mistakenly installed M over L, rollbacks keep resulting in bootloops

I am writing a thorough step-by-step of what I did since something I did along the way may be important for someone helping out to know. Sorry for the length, but I prefer to be thorough instead of wasting people's time with a lot of back-and-forth questions from not being clear in the initial post.
Current ROM: Team Octos OCT-L-WEEKLY-20151219-0359-d2vzw (Dec 19th 2015)
Current OpenGApps: open_gapps-arm-5.1-stock-20151219
Current Modem: d2vzw_VRBMF1_firmware
FYI, I keep the builds for any ROMs or packages I install-as well as the one I had previous to the one I am currently running- on my phone's external SD card so I can keep them organized and have them on-hand to revert back in case of problems.
The situation
1. After numerous crashes and freezes recently, I thought to get the newest stable release of my current ROM to hopefully remove these issues. The latest stable build is from 25 March. Using my phone, I went onto their homepage and downloaded the latest build. Or so I thought.
2. I rebooted into TWRP to install the new ZIP, wipe cache and dalvik, fix permissions, and reboot to system. During the reboot, the animation was different. I've seen builds change animations without it being a new Android version, so I didn't think much of it.
3. After it finished booting to the home screen, my phone buzzed every 2-3 seconds because Google Play Services kept crashing continually. It was 1am at this point and I had seen very similar Google Play Services issues many times before so I knew it would be a time-consuming fix that I didn't have time for. So I pulled the battery and left it for the morning before work.
4. The next morning I went to the Team Octos homepage using my laptop and that's when it hit me- their homepage shows the download links for their newest Android Marshmallow ROM, NOT Android L like I had expected (L is now hidden under a new submenu on their site). So I had mistakenly installed M and caused these Google Play issues. That's my own fault, having missed that one letter that was different in the file name because I was browsing using my phone instead of my laptop, like I have always done before.
5. Thankfully, I have the previous L rom in my SD card. So I booted into TWRP and tried installing that ZIP, wiping cache, dalvik and fixing permissions before booting to system. All I got was an infinite bootloop, never even getting to the home screen.
6. Then I got progressively deeper- I reinstalled the L ROM and the OpenGApps package I had originally installed with the build. With every install and reboot, I cleared the cache, dalvik and fixed permissions as well. Still nothing but a boot loop.
7. Next time in TWRP, I went to Wipe > Advanced Wipe > and wiped cache, dalvik AND system (not "Data"). Fixed permissions, reboot. Same bootloop.
8. Next time, I did the above and repaired the file system. Operation was successful, still the same endless boot loop.
9. Next time in TWRP, Restore > restored package from May 31 2015 (farther back than the ROM). This time the phone DID boot to the lock screen, but as soon as the phone is unlocked, I get the following crashes in succession every time I clicked "OK" to dismiss each:
Unfortunately the process android.process.acore has stopped
Unfortunately Themes provider has stopped
Unfortunately the process android.process.acore has stopped
Unfortunately the process android.process.acore has stopped
After the last "OK", the phone restarts and get to lockscreen, unlocks, has the same four crashes, reboots again. By the way, the home screen isn't the home screen- the background is the "welcome to android! Select your language" screen.
And that's where I am now.
---------------
IMPORTANT NOTES:
1. My phone's charging port hasn't been able to securely hold the MicroUSB cable for over a year now, so I CANNOT connect my phone to anything, whether to my computer or a wall charger. All I do is switch out batteries (I have three) whenever my phone is near death. So hardwiring through ODIN, ADB, etc is impossible. I use AirDroid to transfer files over wifi if needed. At this point I can only manipulate files or data using TWRP. Also, the boot process is limited by how long my battery lasts- about an hour or two depending on how hot the phone gets.
2. I CAN take out my MicroSD card and put it into my laptop using a MicroSD to SD adapter. That's ONE way I can put a newer ROM version onto my phone to use through TWRP that way, if needed.
3. I know from copious reading online that this acore process crash can often be fixed by deleting the Contacts cache, or the cache for other apps. Obviously I cannot do that since I can't get past the unlocking of the phone to access any apps since it would require me to set up Android before getting to any phone data outside of TWRP.
4. I want to avoid a factory reset since there is quite a bit of data that is not cloud-synced on my phone that I don't want to lose.
5. Although this is a great excuse to buy a new phone, I'd prefer to at least get this working so I'm not forced to do that and can still recover the data on my S3 first, making that jump on my own timetable instead of being forced to do it in a rush.
-------------------------
Yes, I know, it's my own fault for mistakenly loading M instead of L without the proper prep. I've jumped from different Android versions before but I did it intentionally and correctly all those times so I know how it's supposed to be done. No need to remind me of how much of a facepalm I caused myself.
The only idea I have now is to attempt to put a new/updated/different ROM version onto my microSD card by putting it onto my laptop first, transferring files and then putting it back into my phone so TWRP can access those files for installation. But I'd rather wait and hear if this is even a good idea before proceeding- I don't want to dig myself into a deeper hole and I'd rather ask for advice.
ANY help would be greatly appreciated. Thank you!

TWRP backups

So I tried my first Nandroid backup today using TWRP and a howtogeek - "How to Back Up and Restore Your Android Phone with TWRP" guide I found off a quick google search.
Basically TWRP, backup(boot,system,data), reboot to android, shut down, twrp-restore then reboot.
When I would reboot after TWRP-restore, it shows the typical bootloader corrupt error msg.
Shuts down again, shows the bootloader msg, then goes into TWRP, asks for my decrypt password, then begins to run an openrecovery script (I think?) of some sort. I then go to reboot my phone again, bang factory reset mode.
I hope I'm not alone here.:cyclops: I'd just really love to be able to backup/image my phone entirely so I can try out a few custom roms, and for general knowledge sake.
thanks!:silly:

mark7807 said:
So I tried my first Nandroid backup today using TWRP and a howtogeek - "How to Back Up and Restore Your Android Phone with TWRP" guide I found off a quick google search.
Basically TWRP, backup(boot,system,data), reboot to android, shut down, twrp-restore then reboot.
When I would reboot after TWRP-restore, it shows the typical bootloader corrupt error msg.
Shuts down again, shows the bootloader msg, then goes into TWRP, asks for my decrypt password, then begins to run an openrecovery script (I think?) of some sort. I then go to reboot my phone again, bang factory reset mode.
I hope I'm not alone here.:cyclops: I'd just really love to be able to backup/image my phone entirely so I can try out a few custom roms, and for general knowledge sake.
thanks!:silly:
Click to expand...
Click to collapse
What version of TWRP have you been using? I understand, RC2 has issues with properly restoring a backup. (RC is release candidate and is not considered fully stable, however, works well enough to flash custom roms and such).
The partitions on the pixel are set up in a more complex way than previously seen on many android phones, which is why there's no perfectly stable version of TWRP yet. You could try using RC1 to see if you get better luck backing up and restoring, however, you should assume that you may run into other issues and be prepared to deal with them should they arise.

exad said:
What version of TWRP have you been using? I understand, RC2 has issues with properly restoring a backup. (RC is release candidate and is not considered fully stable, however, works well enough to flash custom roms and such).
The partitions on the pixel are set up in a more complex way than previously seen on many android phones, which is why there's no perfectly stable version of TWRP yet. You could try using RC1 to see if you get better luck backing up and restoring, however, you should assume that you may run into other issues and be prepared to deal with them should they arise.
Click to expand...
Click to collapse
I'm running 3.1.0-0RC2 so maybe I'll try RC1. Normally I'd just go off and try everything but unfortunately I'm not in a situation I can simply play with my Pixel and potentially brick it leaving me without a phone for who knows how long.
I don't think there would be any harm with playing with RC1 but I'll research a little bit more into it and see what I can find out first. I heard the partitions are split for redundancy(?) for firmware upgrades and dual-booting. That's something all else on it's own as I've REALLY wanted to get my phone ultimately on a Multi-Rom setup but it seems way too complicated for me at the moment to try on my own even though I'm generally good with this stuff..
Thanks exad for the insight. Any other help is greatly appreciated.

mark7807 said:
I'm running 3.1.0-0RC2 so maybe I'll try RC1. Normally I'd just go off and try everything but unfortunately I'm not in a situation I can simply play with my Pixel and potentially brick it leaving me without a phone for who knows how long.
I don't think there would be any harm with playing with RC1 but I'll research a little bit more into it and see what I can find out first. I heard the partitions are split for redundancy(?) for firmware upgrades and dual-booting. That's something all else on it's own as I've REALLY wanted to get my phone ultimately on a Multi-Rom setup but it seems way too complicated for me at the moment to try on my own even though I'm generally good with this stuff..
Thanks exad for the insight. Any other help is greatly appreciated.
Click to expand...
Click to collapse
I would say use RC1 too. I've used it and never had a problem with it other than the occasional failure to decrypt which is no big deal. Just reboot back into recovery. I would add though, instead of backing up system, backup system image. Also vendor image. If you back up system instead of system image you'll more than likely run into battery drain problems. I'm not sure what causes it but it'll cut your battery life down to only several hours. Using system image doesn't cause that problem.
If you should happen to accidentally backup system instead of system image it's not a huge deal to fix it though. If you're on stock just download the factory image that you are currently on, extract the system.img file and flash it using fastboot. If you're on a custom rom, a dirty flash of the rom will fix it.

mark7807 said:
I'm running 3.1.0-0RC2 so maybe I'll try RC1. Normally I'd just go off and try everything but unfortunately I'm not in a situation I can simply play with my Pixel and potentially brick it leaving me without a phone for who knows how long.
I don't think there would be any harm with playing with RC1 but I'll research a little bit more into it and see what I can find out first. I heard the partitions are split for redundancy(?) for firmware upgrades and dual-booting. That's something all else on it's own as I've REALLY wanted to get my phone ultimately on a Multi-Rom setup but it seems way too complicated for me at the moment to try on my own even though I'm generally good with this stuff..
Thanks exad for the insight. Any other help is greatly appreciated.
Click to expand...
Click to collapse
RC1 and backup system image, vendor image, data and boot.

robocuff said:
I would say use RC1 too. I've used it and never had a problem with it other than the occasional failure to decrypt which is no big deal. Just reboot back into recovery. I would add though, instead of backing up system, backup system image. Also vendor image. If you back up system instead of system image you'll more than likely run into battery drain problems. I'm not sure what causes it but it'll cut your battery life down to only several hours. Using system image doesn't cause that problem.
If you should happen to accidentally backup system instead of system image it's not a huge deal to fix it though. If you're on stock just download the factory image that you are currently on, extract the system.img file and flash it using fastboot. If you're on a custom rom, a dirty flash of the rom will fix it.
Click to expand...
Click to collapse
TheBurgh said:
RC1 and backup system image, vendor image, data and boot.
Click to expand...
Click to collapse
Thanks again guys,
I ran a
fastboot boot twrp.zip to boot to what I thought was like a "live cd" version of twrp
with the rc1 .img and .zip in the sdcard directory I installed the .zip
booted my phone and it forces to recovery everytime now.
did I upset something?
I mean at this point, I could factory reset the google pixel all from the very beginning of time. boot/system the whole shabang, but I think this could be a good lesson from me if I could boot back to system out of this..
Okay. I have RC1 on here and have backed up to USB. I'm extremely tired and going to bed. I'll report back on how the restore goes. THANK YOU ALL!!!

mark7807 said:
Thanks again guys,
I ran a
fastboot boot twrp.zip to boot to what I thought was like a "live cd" version of twrp
with the rc1 .img and .zip in the sdcard directory I installed the .zip
booted my phone and it forces to recovery everytime now.
did I upset something?
I mean at this point, I could factory reset the google pixel all from the very beginning of time. boot/system the whole shabang, but I think this could be a good lesson from me if I could boot back to system out of this..
Okay. I have RC1 on here and have backed up to USB. I'm extremely tired and going to bed. I'll report back on how the restore goes. THANK YOU ALL!!!
Click to expand...
Click to collapse
Okay so, I stayed up a little late and tried a restore. I got this error near the end of the restore "extractTarFork() process ended with error: 255" in which resulted in corruption of files and a failed restore. Was I supposed to unmount data? Is there any reason I can't backup all partitions?

mark7807 said:
Okay so, I stayed up a little late and tried a restore. I got this error near the end of the restore "extractTarFork() process ended with error: 255" in which resulted in corruption of files and a failed restore. Was I supposed to unmount data? Is there any reason I can't backup all partitions?
Click to expand...
Click to collapse
Not sure where to direct you at this point. I have always used RC1 and backed up system image, vendor image, data and boot and never had a problem restoring. Someone with better knowledge will come around.

TheBurgh said:
Not sure where to direct you at this point. I have always used RC1 and backed up system image, vendor image, data and boot and never had a problem restoring. Someone with better knowledge will come around.
Click to expand...
Click to collapse
Yeah very strange I did exactly what you told me to do as well. Any changes to partitions I backup if my phone is rooted by chance??

mark7807 said:
Yeah very strange I did exactly what you told me to do as well. Any changes to partitions I backup if my phone is rooted by chance??
Click to expand...
Click to collapse
Not that I am aware of. Mine is rooted and backups have been smooth sailing.

I recently attempted creating a nandroid backup via TWRP on my rooted Pixel and I'm consistently getting an error: 'cannot create [path]\backup file" message from TWRP. Is there a permission issue that I've overlooked here or does anyone have any thoughts as to why my rooted Pixel would be denying TWRP authority to create the backup?
Thanks

What version of twrp ?
I only use rc1, never seen this.

Yep- RC1. I'm thinking it's in 'read only' mode or something because as soon as it attempts to create the folder/file- no-go.

pstgh said:
Yep- RC1. I'm thinking it's in 'read only' mode or something because as soon as it attempts to create the folder/file- no-go.
Click to expand...
Click to collapse
When you boot into TWRP did it ask for your unlock PIN? If it doesn't/didn't, either keep rebooting into recovery or turn the phone off and go back into recovery until TWRP does ask for your encryption PIN. Sometimes TWRP doesn't ask, and without the PIN being entered, it can't write to the internal storage.
If you click "Install" in TWRP and see a bunch of gobbledygook it's because the internal storage is still encrypted so TWRP can't do anything with it.
You could probably use USB OTG through the USB-C connector, though, to do a backup to it, if you need to.

Tried it again and it worked flawlessly.... it seems sort of buggy in that sometimes it presents the 'pattern' security lock that I use and sometimes it doesn't. After booting up in the bootloader and fastbooting the TWRP boot image slowly and methodically, the security pattern came up and all is perfect- thanks.
---------- Post added at 08:37 PM ---------- Previous post was at 08:36 PM ----------
Now I'm wondering how to best move that backup folder (or a copy of it) over to Google Drive? I have root explorer, but not sure if it is capable of mounting to Google Drive.. any thoughts on best practices here would be appreciated.
Thanks

pstgh said:
Tried it again and it worked flawlessly.... it seems sort of buggy in that sometimes it presents the 'pattern' security lock that I use and sometimes it doesn't. After booting up in the bootloader and fastbooting the TWRP boot image slowly and methodically, the security pattern came up and all is perfect- thanks.
---------- Post added at 08:37 PM ---------- Previous post was at 08:36 PM ----------
Now I'm wondering how to best move that backup folder (or a copy of it) over to Google Drive? I have root explorer, but not sure if it is capable of mounting to Google Drive.. any thoughts on best practices here would be appreciated.
Thanks
Click to expand...
Click to collapse
I can't confirm since I've yet to do a successful backup but... Flashify Pro version looks like an option???
also
Anyone know when TWRP 3.1.0-0 will be out for Pixel? Looks like it addresses boot slots which off first glance seems like quite a fundamental feature no?

Thanks... I'm thinking I'll just adb pull the file over to my desktop... not sure.

pstgh said:
Thanks... I'm thinking I'll just adb pull the file over to my desktop... not sure.
Click to expand...
Click to collapse
Root Explorer does have support for Google Drive. In Root Explorer touch the plus sign in the lower right corner and in the menu that opens choose Google Drive tab.

Can get Root Explorer to connect to Google Drive, but when I select all of the backup files from my Pixel's TWRP backup folder, my only choices are to cut or copy them- so I tried both and then RE creates this little clipboard icon that you presumably click on to paste them once you've opened the proper GD folder.... so I tried that and in both cases (cut and copy) it says 'fail'.... ? Thoughts? I've given RE permission to manage folders and files in GD.

pstgh said:
Can get Root Explorer to connect to Google Drive, but when I select all of the backup files from my Pixel's TWRP backup folder, my only choices are to cut or copy them- so I tried both and then RE creates this little clipboard icon that you presumably click on to paste them once you've opened the proper GD folder.... so I tried that and in both cases (cut and copy) it says 'fail'.... ? Thoughts? I've given RE permission to manage folders and files in GD.
Click to expand...
Click to collapse
It sounds like you've got the right idea. Cut will move the files, copy will do just that. You choose one of the two and browse to the Google Drive tab, find the folder you want to use and then use the little clipboard thing to transfer the files to that folder. If that's what you're doing, the only thing I can think of right off the top of my head would be that you don't have enough space left on Google Drive for the size of the files you're trying to transfer. Try a picture or something and see if it takes that. If so, I'd suspect lack of Drive space is the reason it fails.

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.

Experience & questions on Flashing unofficial lineageos17 & magisk on Doogee S68Pro

TL;DR, I'm having 'SIM not detected' issues and my laptop will crash if I open another tab, please help I've attached output of `locat -b radio`
SOURCES
https://sourceforge.net/projects/an...8-UNOFFICIAL-treble_arm64_bvS.img.xz/download
https://github.com/topjohnwu/Magisk/releases/tag/v23.0
open_gapps-arm64-10.0-nano-20211021.zip from https://opengapps.org/
https://unofficialtwrp.com/twrp-3-3-1-root-doogee-s68-pro/
PREVIOUS EXPERIENCE:
I believe about two years back I had already installed an earlier build of LineageOs v17 Magisk v19 using fastboot. This was a trial and error kind of thing as I'm only a fanatic when I have to be. After a long time I finally had a working combination; sort of. Soon about every month or so, or after a couple of restarts, my SIM card would not get detected. Though different behaviors would occur, like 'Emergency calls only', 'No Service' or SMS suddenly not coming through. Since then one time or two a restart fixed the issue until the next month or so. I tried inserting the SIM in every order of events, wiping cache/ dalvik, switching airplain mode, resetting network settings, uninstalling magisk and so on. Then I read somewhere I can't remember about draining the battery capacitors(?) by turning the device on and off on an empty battery until there's no power left and the screen doesn't light up. So I did that and that worked! After a couple of times running into this issue on a fully charged 6300mah battery I downloaded 'generic battery drainer' from the GPlayStore and that app is still on my main screen. Apparently when the device shuts down as the app is draining it, the SIM is detected again when I power up after that, so no need too drain completely... I couldn't find answers anywhere and I like Lineage so much that I just accepted it :')
RECENT EXPERIENCE:
This weekend I decided to give it another try and went for LineageOs v18 but TWRP wouldn't go any further than 'Failed to mount /system/<something>' and I finally went for the above mentioned sources. I patched TWRP recovery using the Magisk app (though I get the impression that this was designed out of necessity, I kinda like being able to switch between Magisk like this). It took me a while to understand that using wipe and decrypting data in TWRP before flashing system (fastboot) has the result of adjusting the system partition to the size of system image when flashing, leaving no space for gapps. Then I flashed stock rom, started device and let it encrypt, then flash the new system image. This kept the original system size with enough space. System started up nicely after, except for: In magisk I got "abnormal state, other su detected". After much reading I could link it to the /system/xbin/su binary. Renaming this (scared to remove) fixed that and $PATH was even appended with ":/sbin:/sbin/.magisk/busybox:". And then, the SIM card issues started after my first couple of reboots :') When it works, so far it's only when I boot without magisk.
QUESTIONS:
Whenever I use the wipe option in TWRP that will also decrypt the device, I can wipe whatever I want. But as soon as system starts it's encrypting data again and I have to use adb for example. Isn't this a generic thing? I get confused about reading so much to use TWRP for this.
Can anyone shed light on the effects of what I'm describing with "draining the battery"? And how running the drainer app might have similar effects?
What is a better approach to configure the size of the system partition? Cause now it's basically twice as big as it has to be
Is the /system/xbin/su in the Lineage build? Is that the built-in root that was/ is/ will be deprecated?
And the GOLDEN question, how can I fix these SIM issues? My head is exploding with information trying to figure out what apps and processes are involved in this. As a logcat first-timer I managed to get the output of `logcat -b radio`, see attached file. This line caught extra attention "Failed getting samsung hardware radio", but I'm out of my territory.
THANKS in advance for any input,
greetings, from a little experienced flasher

RUNNING WITH MAGISK
Further inspecting the lines of logcat -b radio, it seams that ril-daemon isn't started when I'm booting with Magisk/ root, like in the previously attached file. Also getprop shows way fewer props with 'ril' in the value than starting non-root, though altering in count between boots. Reading this https://wladimir-tm4pda.github.io/porting/telephony.html and under RIL Initialization "RIL daemon reads rild.lib path and rild.libargs system properties to determine the Vendor RIL library to use and any initialization arguments to provide to the Vendor RIL" I'm wondering, can it be something as simple as a missing PATH or env value? Anyone have the same experience?

RUNNING WITHOUT MAGISK
logcat -b radio shows way more output and many more things happening. I get the impression that the issue is in or close to the application framework layer... I'm now, still hopeful, attaching two files of logcat radio output. One after boot, up to the login screen and one after login.
Between my post and now, I did however "Remove Telephony Subsystem" through setting => Phh Treble Settings => Misc features, (just trying things out as I read stuff) and I haven't been able to get SIM working again, also not after draining the battery as previously worked. Can this be related? How do I get it back (without reflashing)?

Finally some time to update again. As I have understood, Lineageos18 seems to have an extra level of complexity with the need for mounting system as rw and gets more complex if it is encrypted, so I'm still with magisk patched twrp and GSI Lineageos17.
My SIM still isn't working while booted as root, and I can at least determine that rild is not started and also not present/ available through the terminal. As to why and how to fix that, please let me know if you do! I read some places that PATH has to be inserted with the value of PATH from the non-root env in the init.environ.rc file. That did not make a noticable difference for me. I have not installed the magisk app. So far my SIM is working better than before in non-root/ normal system boot, even after restarts and switching to and back from root.
Some (trivial) things I found many questions and few answers about so far on my quest, in case it might help someone:
I could get rid of "too many symbolic links encountered" in the twrp terminal by setting PATH to just one bin location like '/sbin'. I also had this ld.config.txt error in the terminal (which indeed did not exist on my phone) and was able to trace it back to the /system/system/bin/dlinker64 binary trying to mount that file. I just renamed that and that resolved the error. Then I was able to use the terminal to edit the init.environ.oc file (I could not get adb to work in twrp mode). Not anything specifically, but I found this (among many posts on this forum) quite helpful https://www.didgeridoohan.com/magisk/MagiskInstallationIssues.