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!
Related
I've searched, read, tried reflashing in recovery, etc... Repeatedly.
I was running TnT 3389 (which I flashed myself in recovery from /SD on the 23rd) with rothnic's enhancement pack V.1 and the 99% market fix. Additionally, I was using the Zeam launcher. This morning I was streaming NPR through the NPR app and also surfing. Things started to get a little studdery, so I figured I had somehow invoked the dreaded Lag on Wake (even though I had tried airplane mode before sleep.) Solution: the usual, REBOOT! Power off (took a little longer than normal). Power button pressed, Viewsonic splash screen, G Tablet screen, Nexus sparkles for ~15 seconds, blank screen, then Nexus sparkles start over, repeatedly.
The thing which I think makes my situation a little different is that I probably (as in I think I did, but am not 100% sure I did) left a folder on the internal SD with the appropriate recovery folder and rothnic's stock enhancement pack labeled update.zip. I know! I probably should have deleted it from the internal SD after I installed it , but I went on to do the market fix (a few times until it worked) and I forgot to remove the recovery/update business.
So I tried reflashing from SD2 first with stock 3389 and then after that didn't work, I tried installing cw_mod.08 following [GUIDE] How To Install ClockworkMod
My guess is that I screwed myself from being able to recover from /SD2 because I still have recovery in /SD, right? I am willing to fully wipe the tablet and go full root, reinstall everything, and hopefully put Titanium backup, CWmod, and TnT lite 3.1.3 on.
My goals are:
1. Not have a brick.
2. Not have stock TnT (with miserable dashboard, etc...)
3. Have updated Nvidia stuff so I can still have ~2400 Quadrant scores
4. At least 99% Android Market access
5. Flash (Hulu would be a bonus!)
6. All Gapps and syncing working like they do on my Evo.
Please help me! At least point me in the right direction
The command file in the recovery folder was deleted the first time you used it so that is not an issue. Read these 2 links carefully. You need to install clockworkmod recovery.
http://forum.xda-developers.com/showthread.php?t=865017
http://forum.xda-developers.com/showthread.php?t=892090
When you have clockworkmod recovery installed then go to the advanced menu in clockworkword and repartition your sdcard to 2048 and 0
If you install either tnt lite 3.1 or vegan beta4 you do not need to install the performance pack. That pack is for people running the stock viewsonic firmware so they can have gapps and root
Thanks thebadfrog! I had been doing the cwMod steps correctly, so by process of elimination I realized that my 8GB microSD wasn't being recognized. I went back to the last one that had worked and voila! On to new ROMs... Thanks again
So I've had a bit of bad luck mixed with poor timing. Here's the run down.
I have an Asus Transformer TF101 which was running the stock rom.
I rooted my Tablet a few weeks back without any problem. Things were great. Then, I tried to upgrade to Jelly Bean from ICS using Team EOS (I followed these 2 threads mainly, http://www.transformerforums.com/fo...ficial-faq-teameos-4-android-4-2-x-tf101.html & http://forum.xda-developers.com/showthread.php?t=2063406)
I put the ROM and all the files needed onto my micro SD card.
I booted into TWRP and followed the instructions. Things seemed to have gone great. When I rebooted, I saw the new splash Logo upon bootup and awaited it to do it's thing. It never did. I let it run for an hour and it never made it into the OS.
I rebooted, went back into TWRP with plans to redo the procedure, only now the microSD card slot is not being picked up. I tried multiple micro SDs of different sizes (1GB-32GB), I've tried inserting before boot up, inserting after bootup, inserting after bootup and then rebooting the device. No luck.
I bought a USB adapter that plugs in where the power plug goes, hoping I could run the files off a USB flash drive. or a micro SD card within a USB flash drive. No luck.
I am running Teamwin's TWRP 2.3.2.3
My backup from nandroid happens to be on my microSD card too. So I can't use it to recover the old OS either.
TL;DR: Micro-SD card stopped working after a failed attempt to flash an OS. OS and backups are on the microSD card. PC recognizes the device but won't let my access the hard drive.
Does anyone have any suggestions on what to try?
Thanks!
Well, the USB is not set up to be mounted in recovery. Keep in mind, the microSD is mounted at /sdc/ in TWRP.
You can always use ADB and push a file to the internal (/sdcard/) so you can flash if your microSD slot is dead.
Let me find a post on how to do this.
EDIT: Here is what to do if you need to use ADB:
Plug tablet to PC via USB
It should install new hardware and show 1 devices, an ADB device.
Update the driver in the Device Manager on the windows machine to the Naked Drivers
Once that is updated, I downloaded ADB from the Android SDK. You really only need three files, available here: http://db.tt/b9dQ6xzp
Unzip these files to a folder called c:\adb
Open a command prompt and type the following:
Code:
c:
cd c:\adb
adb devices
It should show a device connected. It may error out when restarting the daemon, but keep trying and see if it can find your tablet.
If you cannot get the ADB driver installed or updated, my guess is that you have a bad USB cable. Yes, it IS possible to have a bad cable for data transfer that STILL charges your tablet. I have even had that happen to me.
If you got this far, then here is what to do next:
Download your favorite ROM. If applicable, save any other files needed (GAPPs or kernel)
Save this at c:\adb\ROM.zip. Other files save accordingly like Kernel.zip and GAPPs.zip.
Next, run the following commands
Code:
adb push ROM.zip /sdcard/
Once this competes, you will need to repeat for any other files to flash like GAPPs or Kernel.
After these files have been transfered, you can install a file from the internal (/sdcard/) directory.
frederuco said:
Well, the USB is not set up to be mounted in recovery. Keep in mind, the microSD is mounted at /sdc/ in TWRP.
You can always use ADB and push a file to the internal (/sdcard/) so you can flash if your microSD slot is dead.
Let me find a post on how to do this.
EDIT: Here is what to do if you need to use ADB:
Plug tablet to PC via USB
It should install new hardware and show 1 devices, an ADB device.
Update the driver in the Device Manager on the windows machine to the Naked Drivers
Once that is updated, I downloaded ADB from the Android SDK. You really only need three files, available here: http://db.tt/b9dQ6xzp
Unzip these files to a folder called c:\adb
Open a command prompt and type the following:
Code:
c:
cd c:\adb
adb devices
It should show a device connected. It may error out when restarting the daemon, but keep trying and see if it can find your tablet.
If you cannot get the ADB driver installed or updated, my guess is that you have a bad USB cable. Yes, it IS possible to have a bad cable for data transfer that STILL charges your tablet. I have even had that happen to me.
If you got this far, then here is what to do next:
Download your favorite ROM. If applicable, save any other files needed (GAPPs or kernel)
Save this at c:\adb\ROM.zip. Other files save accordingly like Kernel.zip and GAPPs.zip.
Next, run the following commands
Code:
adb push ROM.blob /sdcard/
Once this competes, you will need to repeat for any other files to flash like GAPPs or Kernel.
After these files have been transfered, you can install a file from the internal (/sdcard/) directory.
Click to expand...
Click to collapse
Thanks so much frederuco! I will be trying this later today and will update this post as soon as I do.
I just wanted to say good luck, and we are all counting on you.
Almost there!
frederuco said:
I just wanted to say good luck, and we are all counting on you.
Click to expand...
Click to collapse
The update! I followed your instructions, while on the cmd prompt, I got no confirmation that the files were moved, but they appear to be on the device now. When I go to reinstall through TWRP, the flashing fails. I am going to do some digging around the forum to see what solutions there may be, but if you (or anyone reading) has an idea, do tell.
I will be sure to update this thread if I fix it, including the solution I found.
Try downloading the ROMs again.
Also, note that I edited my reply as I had said ROM.blob and it should be ROM.zip.
frederuco said:
Try downloading the ROMs again.
Also, note that I edited my reply as I had said ROM.blob and it should be ROM.zip.
Click to expand...
Click to collapse
I think I'm in good shape. I tried to edit my post from earlier, but I had to wait a few minutes before it would let me.
I realized the file didn't finish transferring to the tablet. Moments after my last post, I got a confirmation from cmd prompt that the first file finished. The second one just finished, and the third is still transferring I suspect. That would totally explain the failure.
db1984 said:
I think I'm in good shape. I tried to edit my post from earlier, but I had to wait a few minutes before it would let me.
I realized the file didn't finish transferring to the tablet. Moments after my last post, I got a confirmation from cmd prompt that the first file finished. The second one just finished, and the third is still transferring I suspect. That would totally explain the failure.
Click to expand...
Click to collapse
Yes, that would do it!
frederuco said:
Yes, that would do it!
Click to expand...
Click to collapse
Alright, so I got past the logo, Android upgraded all the Apps and is now "Starting apps" .. it's been here for about 10 minutes. I think I can take it from here.
The ADB push was the solution.
Waited another 15 minutes. Nothing happened (stayed at Starting apps)
Restarted device. Booted up as it should and I am now all set. Thanks again!
Now that you're using EOS can you use the microSD slot? I know moving from stock to EOS fixed my card slot issues not to mention that I'm loving the Jellybean goodness
Sent from my Nexus 7 using Xparent Purple Tapatalk 2
bsoplinger said:
Now that you're using EOS can you use the microSD slot? I know moving from stock to EOS fixed my card slot issues not to mention that I'm loving the Jellybean goodness
Sent from my Nexus 7 using Xparent Purple Tapatalk 2
Click to expand...
Click to collapse
I'm fairly certain the slot itself is broken. Haven't been able to get it to read things yet.
I'm still having some minor issues with the setup, but I know I've seen fixes to these problems when browsing this forum. Google Search/Google Now crashes 3-4 seconds after opening it. The system also reboots "randomly" (really, just when it's idle for more than 10 minutes), I also had to go into TWRP last night to get the system to power down. Long pressing power and selecting Power Off simply rebooted it.
But compared to where I was 24 hours ago (and had been stuck there for 1+ week, I really didn't want to burden people with my problem since I'm a lurker here), I really can't complain and have full confidence that I'll be able to get the kinks worked out.
At least I have an adapter for the power port, so I can plug USB sticks (or USB-microSD adapters) into the tablet still.
db1984 said:
I'm fairly certain the slot itself is broken. Haven't been able to get it to read things yet.
I'm still having some minor issues with the setup, but I know I've seen fixes to these problems when browsing this forum. Google Search/Google Now crashes 3-4 seconds after opening it. The system also reboots "randomly" (really, just when it's idle for more than 10 minutes), I also had to go into TWRP last night to get the system to power down. Long pressing power and selecting Power Off simply rebooted it.
But compared to where I was 24 hours ago (and had been stuck there for 1+ week, I really didn't want to burden people with my problem since I'm a lurker here), I really can't complain and have full confidence that I'll be able to get the kinks worked out.
At least I have an adapter for the power port, so I can plug USB sticks (or USB-microSD adapters) into the tablet still.
Click to expand...
Click to collapse
The workaround for Google Now crashing is to disable Hotword Detection in Settings - Language & Input - Voice Search (or something like that). Search the EOS thread for "Hotword" and you will find the location.
Do you have a SD in the dock? This can cause SOD and RR's.
Hmm, I guess I have never tried powering down on EOS, but I am pretty sure it works. I just put my tablet to sleep and never turn it off. I find my tablet (even undocked) will lose more power when it is off than when it is sleeping.
frederuco said:
The workaround for Google Now crashing is to disable Hotword Detection in Settings - Language & Input - Voice Search (or something like that). Search the EOS thread for "Hotword" and you will find the location.
Do you have a SD in the dock? This can cause SOD and RR's.
Hmm, I guess I have never tried powering down on EOS, but I am pretty sure it works. I just put my tablet to sleep and never turn it off. I find my tablet (even undocked) will lose more power when it is off than when it is sleeping.
Click to expand...
Click to collapse
Nope, nothing was in the dock. I actually didn't have the keyboard dock plugged in during the "crisis"- I did try getting TWRP to read a card from it once, that was about it.
I read somewhere else, that once you let the battery die on it's own, and recharge, the "never powers off" issue goes away for many people (haven't seen one specifically relating to EOS on TF101, but the other symptoms were spot on)
I'll be checking out the Google Now tweak in a bit.
I'd been running a custom kernel on my Transformer since about a week or two after I bought it at a Black Friday sale simply because it would keep running on the stock ICS ROM. Changed to KAT kernel when I moved to EOS. You might want to consider a custom kernel if you have a Transformer that suffers from the reboot issue like mine did.
Sent from my Nexus 7 using Xparent Purple Tapatalk 2
db1984 said:
-snip-
Click to expand...
Click to collapse
You may want to try doing a full format in TWRP, and using the superwipe full scripe from the ARHD thread, then formatting again, wipe cache and dalvik, push the latest EOS, KATkernel and Gapps to the device, wipe dalvik cache and cache, flash EOS, wipe dalvik cache and cache, boot into the ROM, boot back into twrp, wipe cache and dalvik, flash Gapps, wipe cache and dalvik, boot into the ROM, boot back into TWRP, wipe cache and dalvik, flash KATkernel, wipe cache and dalvik, cold-boot into the ROM.
That should set you up with the most stable your tf is going to get, it seems erroneous and like a ton of work, but I strongly believe in doing this whenever I flash a new rom setup, I've gotten to doing it in about 10 minutes now.
Just an update.
EOS's random reboots were getting pretty bad. Happened a few times while I was working on a few docs (thankfully Evernote had autosaved)
I also noticed when the screen would go off, it would eventually turn back on and attempt to reboot, getting stuck at the Asus loading splash (pre EOS logo). I ended up re-flashing with my newly gained leet adb skills (thanks frederuco ) and went with Cyanogenmod 10. I've only had 1 random reboot since and Google Now seems to work 90% of the time.
I'm sure there are some more things I can do to fine-tune it, still getting a hang of everything.
Thanks again for everyone who's helped.
I just got a s5 prime from eBay and was in the process of debloating via tibackup but kept getting stuck at boot screen showing warranty kernel bit. Required a restore of system and data each time to get it going again. Through arduous process of elimination I was able to narrow the culprit down to the aforementioned seemingly innocuous apk. When it's removed the phone dies.
What's even stranger is that this page seems to indicate that it's fine to remove:
http://forum.xda-developers.com/gala...oater-t3319854
I'm just curious as to why!
Sorry for digging but people need to know! I wish I saw this post earlier. I spent whole night trying to see what causing my phone to endless boot.
After few hours I see that If you remove DictDiotek it won't boot anymore. And I thought that this is uselles dictionary and everywhere people write that it's safe to remove.
GALAXY S9+ OREO
KamilKiri said:
Sorry for digging but people need to know! I wish I saw this post earlier. I spent whole night trying to see what causing my phone to endless boot.
After few hours I see that If you remove DictDiotek it won't boot anymore. And I thought that this is uselles dictionary and everywhere people write that it's safe to remove.
GALAXY S9+ OREO
Click to expand...
Click to collapse
I remove it from all my ROM builds with NO PROBLEM...
@AFFAFXP - I believe you because I've always removed it from my S7 and It worked fine. But on S9+ it's causing endless boot for me. I think that it's ROM related or something (or maybe language related)
KamilKiri said:
@AFFAFXP - I believe you because I've always removed it from my S7 and It worked fine. But on S9+ it's causing endless boot for me. I think that it's ROM related or something (or maybe language related)
Click to expand...
Click to collapse
endless boot is from some files in the /lib I believe if you look for these from a rom that worked and replace them in the rom your installing this would work in this case as well...
This link originated here >>>> https://www.tech1xpert.com/guide-to-port-roms-android/
Fixing a Bootloop
Your Port should take less than 5-8 minutes to boot. When the screen dims during boot logo, your Rom has successfully boot.But If your waiting for like 15 minutes, and boot logo is still going, YOU HAVE A BOOTLOOP. Luckily, the fix is easy!
STEP1:
Navigate to “PORT” folder. A ROM THAT BOOTS AND WORKS for you device
STEP2:
Go to lib folder inside System folder of Base Rom.= ROM That you want to install
STEP3:
Inside lib folder of PORT search for these libs:
libandroid_runtime.so
libandroid_servers.so
libmedia_jni.so
Once you find each, copy them to the lib folder of Base Rom.= The ROM you want to install -- Right-click lib folder of Base Rom, select paste, and click the box in the lower left corner. Now “Click Move and Replace”
STEP4:
All done! Now add to a zip and flash!
This HAS WORKED in my attempts on PORTS that BOOTLOOP KUDOS
The same problem happened on my device. I took it to the mechanic before I tried to get into the recovery screen. We thought there was a power problem. The mechanic probably damaged my robust device because they didn't open it properly and handed it back to me in a broken state.
By taking a second N910C device and risking it, I repeated the same process step by step and found that the problem was caused by uninstalling the program "DictDiotek.apk". I restored my backup with Recovery. And my device turned on normally. DictDiotek is not a problem if frozen. Only uninstalling the phone does not turn on.
My phone is N910C. Custom ROM 6.0.1: Ditto ROM DN6
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.
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?