Database Info

[HOW TO] Keep all your stuff after flashing hero.

Ok, so this is my first Informative thread..so bear with me.
Im a VERY regular hero flasher, and to me, it always seems frustrating to do the whole routine of
Backup>Wipe>Format>Flash>Setup Process>Restore Backup.
especially after you get used to a Rom and you have some stuff that cant be backed up.
Well, i came up with a solution-type thing.
Some people might have tried it out..not sure.
You need:
Nandroid
Android SDK ---> Get it Here
First, do a nandroid backup..(you need it for this to work)
type this into adb
adb shell
echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file ---->to mount SD in recovery..(or you could just reboot and mount or use an SD reader..whatever)
go to the nandroid folder, and recover the data.img file from your most recent backup. copy it somewhere on your computer.
Start up adb and type
adb shell
rm -r /system/sd/app_s
rm -r /system/sd/app-private -->to prevent bootloops
then wipe, and flash new Rom.
reboot and let the device go into setup process, then power off.
boot device into fastboot mode by holding the camera button + Power button.
open cmd, and cd to your android sdk directory. (or however you do it in linux)
now, type in
fastboot flash userdata <chosen path>/data.img
fastboot reboot
Thats it..all done. Now you have all your stuff from previous hero..and dont have to re-enter loadz of information...and also the benefit of having new stuff like "secret optimized apk's" and what-not.
if you have problem with touch-flo force-closing, go to
settings>applications>manage applications.
choose touch flo
choose clear data.
you should have ahome or some other type of home rplacement program because it seems touchflo DEFINATELy force-closes. and you'll need other home replacement to go into settings.
Or you could just assign a shortcut to settings by going to settings>applications>quick launch selecting what u like.

Hey, I really like the idea behind this approach, but being not as savvy as I'd like, lemme ask this:
Could I achieve the same thing by:
1. performing a nandroid backup.
2. Go thru all the steps to flash a new Hero rom.
3. perform another nandroid backup.
4. copy the data file from the first backup to the appropriate location in the new backup, replacing the newer data file with the old.
5. Perform a nandroid restore with the the newly modified backup file. Et voila!
Or not? If not, would someone mind explaining to me the difference in as layman's terms as possible. A clear explanation could likely go a long way towards teaching me alot about many things that I'm not quite clear on.
Thanks!

would this work with a non-Hero ROM? Or going from a Hero back to a cupcake (or whatever it's called?!)
Thanks!

kjdiehl said:
Hey, I really like the idea behind this approach, but being not as savvy as I'd like, lemme ask this:
Could I achieve the same thing by:
1. performing a nandroid backup.
2. Go thru all the steps to flash a new Hero rom.
3. perform another nandroid backup.
4. copy the data file from the first backup to the appropriate location in the new backup, replacing the newer data file with the old.
5. Perform a nandroid restore with the the newly modified backup file. Et voila!
Or not? If not, would someone mind explaining to me the difference in as layman's terms as possible. A clear explanation could likely go a long way towards teaching me alot about many things that I'm not quite clear on.
Thanks!
Click to expand...
Click to collapse
Yeah, that would work, because it's the same thing but rather than just flashing data.img with fastboot, you're reflashing data + everything from your current setup. If that makes sense. You could just use fastboot...

sorry double post..

jomtones said:
would this work with a non-Hero ROM? Or going from a Hero back to a cupcake (or whatever it's called?!)
Thanks!
Click to expand...
Click to collapse
Dont think so, dont think there is a data partition in google based ROMs, all your apps are in the system partition. I'm not entirely sure about that, but I expect you'll get a bootloop.

kjdiehl said:
Hey, I really like the idea behind this approach, but being not as savvy as I'd like, lemme ask this:
Could I achieve the same thing by:
1. performing a nandroid backup.
2. Go thru all the steps to flash a new Hero rom.
3. perform another nandroid backup.
4. copy the data file from the first backup to the appropriate location in the new backup, replacing the newer data file with the old.
5. Perform a nandroid restore with the the newly modified backup file. Et voila!
Or not? If not, would someone mind explaining to me the difference in as layman's terms as possible. A clear explanation could likely go a long way towards teaching me alot about many things that I'm not quite clear on.
Thanks!
Click to expand...
Click to collapse
yes, that should work. sems abit more straight forward...especially for those who dont use adb

kjdiehl said:
Hey, I really like the idea behind this approach, but being not as savvy as I'd like, lemme ask this:
Could I achieve the same thing by:
1. performing a nandroid backup.
2. Go thru all the steps to flash a new Hero rom.
3. perform another nandroid backup.
4. copy the data file from the first backup to the appropriate location in the new backup, replacing the newer data file with the old.
5. Perform a nandroid restore with the the newly modified backup file. Et voila!
Or not? If not, would someone mind explaining to me the difference in as layman's terms as possible. A clear explanation could likely go a long way towards teaching me alot about many things that I'm not quite clear on.
Thanks!
Click to expand...
Click to collapse
Dude that's perfect! I like your style of thinkin!

kjdiehl said:
Hey, I really like the idea behind this approach, but being not as savvy as I'd like, lemme ask this:
Could I achieve the same thing by:
1. performing a nandroid backup.
2. Go thru all the steps to flash a new Hero rom.
3. perform another nandroid backup.
4. copy the data file from the first backup to the appropriate location in the new backup, replacing the newer data file with the old.
5. Perform a nandroid restore with the the newly modified backup file. Et voila!
Or not? If not, would someone mind explaining to me the difference in as layman's terms as possible. A clear explanation could likely go a long way towards teaching me alot about many things that I'm not quite clear on.
Thanks!
Click to expand...
Click to collapse
Sounds kinda round-about to me... You'd have to make a nandroid... flash... then nandroid again... those nandroid backup/restores take much longer than flashing a simple userdata from fastboot. Using fastboot, you could flash it in what... a minute vs another 7-8minutes, but I guess its alright for those terrified of a command prompt...
EDIT: Forgot. Instead of doing the long echo command to mount your sdcard in recovery, you can just type:
Code:
adb shell ums_enable
to start the service and
Code:
adb shell ums_disable
to unmount it from your computer

Thanks for the responses, folks. It's much appreciated.
Yeah, I'm still getting the hang of adb. I don't typically mess around in Terminal, (I'm on a Mac,) so I'm not used to it or the lingo. That doesn't stop me from trying very clear directions, and I do learn a little bit, but the drag-n-drop world makes more sense to me, at least for now.
For instance, when given instructions like this:
"open cmd, and cd to your android sdk directory. (or however you do it in linux)
now, type in
fastboot flash userdata <chosen path>/data.img
fastboot reboot"
I THINK I understand most of it, but I don't know what "cmd" or "cd" means or if it's a typo or what. Also, I think most instructions don't make it clear after what lines I should hit enter and what not. I know that stuff is old hat to most of you guys, but I'm still trying to get the hang of it.
Anyway, thanks for the help!

Drizzy NewVision
Does this work for Drizzy's NewVision? Does it back up the ext3 partition so you dont have to wipe it and get rid of all your apps??

[Q] A question before my first flash

I've been doing a lot of reading lately and I am finally about to flash my first ROM. Below is a list of what I've done as far as backup and prep. What I want to know is if there is anything important that I missed?
Made a nandroid backup with CWM
Backed up apps with Titanium Backup
Backed up efs directory from the phone
I have a copy of settings.db on my compuer
I have Odin 1-click on my computer
I have a jig made up just in case
Also, since I am on stock 2.1(JH7), I assume I don't need to go through the odin 1-click step, right?
Thanks in advance for your help

looks like you have everything covered except one thing (maybe): if you have an unlocked phone, check the forums to learn how to get your unlock back *before* flashing
i also put a copy of my sd card onto my computer in case something goes bad, but that's just my paranoia/ocd
and you should flash at 100% battery and reset the battery stats while flashing. you can even flash while the phone is plugged into the computer or ac outlet, so the flashing process doesn't drain from the phone battery. some ppl say this is voodoo, but i always flash at 100% and reset the battery stats while changing roms because its a convenient time to reset stats

sublimaze said:
looks like you have everything covered except one thing (maybe): if you have an unlocked phone, check the forums to learn how to get your unlock back *before* flashing
Click to expand...
Click to collapse
OK, thanks. I'm glad you mentioned that. I do have it unlocked and I didn't even think about it. I have to go to Thailand in a few weeks for work so I need it unlocked.
I think I remember reading that the unlock code is located in the nv_data.bin file and can be found by searching the file with a hex editor. I'll have to read a little more and play around with that before I flash.

I have been reading a lot lately, but could not find an answer to my noob question. I was just wondering if I flash an I9000 based ROM and lose my unlock or my product code gets messed up, can I just copy the original nv_data.bin file to the new ROM or will that cause me other problems. I know there are post as to how to fix this, but they are geared toward people who didn't make a backup and copying original would be much easier and quicker. Thanks.

^^^ Any help with above question?
I also have one other question. I've been poking around with Root Explorer and I see that all the sytem apps are naturally stored in /system/app folder, but I don't see the downloaded apps in there. I see what apperar to be my downloaded apps in /data/app folder. Is this where they are stored and if so, can I just copy them out and then copy them back after I flash a new ROM? If so, is there anything else I have to do with them to make them work again (like chown through adb)? I was wondering this because I have some paid apps and I don't know if they will automatically be available for download again once I sign on to the market and I don't want to lose them. Thanks for any help.

[Q] CWM recovery and adb

Apologies if this is already answered somewhere or should have been common knowledge - I'm new to Android. I feel like I've read through all the appropriate threads but haven't found the answer.
I wanted to simply remove some of the stock apps from my G2X. I can't get adb connected while in CWM recovery. I've done the following:
- Installed android sdk
- Installed LG adb driver
- Rooted with SuperOneClick
- Installed Rom Manager from the market and "fake" flashed ClockworkMod Recovery
- Booted into CWM and made a nandroid backup
- Factory reset using stock recovery
- Restored nandroid backup using CWM - works fine
Now, I believe all I need to do is get adb connected in recovery mode, mount /system and delete any .apks I don't want; however, the adb device is not present when I boot to CWM recovery. adb works fine when booted normally. As a result, I obviously can't start adb shell. Oh, and I've tried this from XP 32bit and Win7 x64. What am I missing?
Did I need to flash CWM to the actual recovery area using NVflash for this to work? I'd rather not do this for warranty purposes (especially this soon) unless absolutely necessary. Incidentally, the other USB devices (virtual serial port, modem, and storage devices) do show up while in recovery - just not the adb device.
I'm open to other methods of stripping .apks. I don't yet know anything about modifying and repackaging a nandroid backup, if that's possible, or I would try that route.
Any guidance would be greatly appreciated.
Thanks!
EDIT: I've resolved my particular issue by just remounting /system as rw while the phone is booted normally. This still doesn't answer the CWM adb question, but at least for now, I guess I don't need that.

I believe you can just use Root Explorer (or another type of file manager) to delete or freeze the apps that you do not want. Not sure if this belongs in development.

This will be moved soon enough, and you didn't search enough since i know there is threads talking about this. Do a search again. mod plz move this to the right area.

Maybe a freeze is one way to go, but obviously a cleaner way is remove the apps, which should be possible with this method and others.
I did search - a lot - in this forum and others. I found no one directly addressing adb not working in CWM on the G2X. I saw one poster here mention they had a similar issue, but only on XP and no one responded to that either. If you know of a thread with this information in it, please enlighten me.
Maybe this isn't the right forum to post in, but the question is directly about CWM flashed to a rooted G2X and access using adb...

I just use titanium backup's Chuck Norris Mode.

I've resolved my particular issue by just remounting /system as rw while the phone is booted normally. This still doesn't answer the CWM adb question, but at least for now, I guess I don't need that.

Root Explorer is your best friend, a simple delete is all you need, make sure you mount before entering system

davemayo2000 said:
I've resolved my particular issue by just remounting /system as rw while the phone is booted normally. This still doesn't answer the CWM adb question, but at least for now, I guess I don't need that.
Click to expand...
Click to collapse
Haha, plenty of answers, none of which answer your main concern. I too have been mystified by the lack of adb functionality while in recovery. I have come to the conclusion that it's simply not functional with this very early version of clockwork recovery for our phones and probably not a high priority for the devs at the moment as theres probably plenty of other issues deemed more urgent. Especially considering there are many work-arounds to solve this particular missing function. Hopefully I'm wrong though.
Sent from my LG-P999 using XDA Premium App

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.