So I just tried out some pie roms earlier and when I finally settled on a specific rom, i migrated my files, fixed some settings etc. And when I decided that I was done, I just wanted to transfer some backup files to and from my phone in case I'd need to revert to my prior setup. Weirdly enough, when I pressed the file transfer option on my phone, it would stop or even restart to the bootloader or recovery then I'd have to boot my phone again. I tried it a couple more times and I even lost some data. I then decided to restore a nandroid backup of my oreo rom thinking it was a rom problem but the data partition couldn't be read in bluspark twrp. So, I just did another clean flash of the pie rom (format data, decrypted and all that) and same thing except for the data loss part. Im pretty sure nothing went wrong with flashing as everything works fine on the actual rom but as soon as I select the MTP option, the phone just restarts. Now Im on the said pie rom and everything's working fine but I can't attempt to transfer any files as I'll just run into the same problem. Any help would be appreciated. Thanks!
Related
Team Vanir Jellybean v2-7, Galaxy Nexus Verizon
Last week i was having issues with the phone not booting, or just locking up not responding etc. A wipe seemed to help, and wit work for a while. I'd get my phone setup to where I wanted it again, and then the issues would come back.
I found a post that said it was possible EXT4 formatting issues because of a bad poweroff. So I downloaded all the stock 4.04 images, fastboot erased system boot recovery. Flashed the latest radios, stock system boot userdata and clockwork recovery 5.5.0.4. Booted seemed to be fine.
Rebooted into Clockwork and installed Vanir v7, ran fine for a few days. I thought the issue was gone. Until this morning when I got a text message and went to unlock the phone and it was locked up. I pulled the battery and that is when everything got extremely bad
Would not boot past the boot animation. I tried the following
I reinstalled the ROM,
i treid to wipe data,
wiped data and reinstalled the ROM.
although I was able to make a nandroid backup before I tried all of this
Then as a last resort I went into the mounts and storage and FORMATTED /system /data and /cache in CWM. Reinstalled the ROM and it actually booted.
What greeted me there is the last thing I'd EVER expect to see. I don't know how, what or why but all my data was there... every app text missed call... all of it.. even tho I had wiped AND formatted several times and did NOT restore my backup. EDIT: Even more oddness... My user apps didn't get wiped, they are all still there, but they are all acting like I had cleared their data through the applications menu....
I still don't know if this is because of a NAND issue that formatting fixed both times (flashing stock and using format in CWM) or if it will ever come back. Has any1 else had any issues of this sort? I really don't think this is a ROM issue.
you're probably causing more damage by flashing this, wiping this and that. best option is to leave it stock for now by flashing the factory image again. if it is a NAND issue then it would have stopped booting when the issue occured. but if it is still causing problems then send it back for a replacement.
Hi everyone, this is somewhat complicated and il try my best to describe what happened.
My device is a i747m (rogers).
I was running CM10.1 (running gapps-jb-20130812 and CWM recovery 6.0.4.3) for a long time, tried to update to 10.2.
(i messed up on 2 things.I don't think i cleared neither of the cache or data and also didn't have proper gapps which would be 20130813).
After installing 10.2 through recovery, it would just stay in the boot Cynogen booting logo.
i restarted into recovery, since my old CM10.1 zip was still there, i installed that instead, but same thing happened, it would just stay at booting logo.
I had made a nandroid back up from before all of this, and so i wiped data, dalvik cache, cache, formatted system, and i recovered into that, which was a stock 4.1.2 rooted (rogers).
However, nothing worked, only WiFi. I couldn't make any phone calls, send/receive messages, or get data.
I then used ODIN 3.07 to flash the new stock 4.3 rooted (rogers). WiFi worked as before, but i still couldn't make any phone calls, send/receive messages, or get data.
i then re-installed the latest recover 6.0.4.5, and installed paranoid android 4.4.2 and gapps for this version. But still nothing, so i went back to the stock 4.3 rooted.
4 months ago, when i made the nandroid back up, i also made an IMEI back up as well (i did not do a full imei/NV/EFS/IMSI/data backup) , i only had my IMEI backup, so i wrote using "NV items reader writer" the IMEI back onto my phone, and now i can recieve/send messages, and get phone calls and make phone calls. wifi also works.
But my data is stuck in Edge, its extremely slow, takes 10min to download a 15mb file.
so far:
-The APN settings are correct
-my IMEI number in settings menu, matches the one on the back of my phone.
-network mode is GSM/HSPA/LTE
-i have installed the latest modem for i747m through CWM recovery and also tried slightly older versions.
i am pretty much lost and i dont know what i should do.
-rogers has told me to use kies and perform backup and then recovery, apparently that will factory reset my phone.
-should i simply use kies to install the latest 4.3?
-does anyone have the imei/NV/EFS/IMSI/data files? or the full NV file?
-should i install CWM recovery and wipe everything that i can? and re-install stock rooted 4.3?
-should i use QPST to fix my IMEI? <-- dont know anything about this, noticed a few threads.
i have used these threads in all my rooting and so forth.
http://forum.xda-developers.com/showthread.php?t=2179330
http://forum.xda-developers.com/showthread.php?t=1831898
http://forum.xda-developers.com/showthread.php?t=2129993
please someone help me out, I dont know how to fix this.
thank you for reading this long and complicated problem.
same problem, ive spent every minute working on it for a week
So, yesterday I unlocked my OnePlus 3, rooted it and flashed a custom recovery. So I managed to install MIUI 8, and fingerprint scanner didn't work, so I flashed 3.2.4 firmware. Then I realised that I couldn't get my native language and I installed CM14, but before I flashed 3.2.6 firmware. As far as Nougat is still not ready for my daily usage, I restored OOS 3.2.6 from my entire backup.
I couldn't unlock the device. The pattern was not recognised as correct, even if it was. So I flashed cleaned data, cache and dalvik, and from here my problems started. I had no IMEI, no baseband, no wifi, my phone constantly randomly rebooted, so I tried to flash EFS twrp restore. Nothing. I tried with 3.2.6 firmware. Nothing. I decided to return "original". I copied JUST the EFS and Boot backup from TWRP folder to my pc, locked bootloader, flashed original recovery and OOS 3.2.7. Still the same problems, plus at the beginning I couldn't even complete my first setup. My actual condition is:
OnePlus 3 A3003, locked bootloader, unrooted, stock recovery, oem unlocked, debug enabled, efs partion (at this point I think so) messed up, efs backup doesn't work. Any help would be appreciated. Thanks in advance
EDIT: As the user @_ekis_ suggested me via private message, I flashed OOS, performed a "Fastboot erase modemst1;
Fastboot erase modemst2", and I got back IMEI, baseband (most important thing for me) and SIM. And no more random reboots. But there is still a problem: the wifi. It seems it disabled. Whenever I activate it, I cannot see any wifi, I cannot refresh the WIFI list etc. I already backed up my EFS, and I will perform a new OOS installation via fastboot. I hope for the best
EDIT 2: And yes, it worked! Now everything is back. A real thank you to @_ekis_ for his support and all the OnePlus 3 Telegram group.
Try flashing a modem package and it might help the imei. Theres a thread on the modems around here somewhere.
NZnewbie said:
Try flashing a modem package and it might help the imei. Theres a thread on the modems around here somewhere.
Click to expand...
Click to collapse
I don't mind about IMEI. The only thing I want back is just the baseband. I'm trying to flash OOS 3.2.6 now.
If it will not work, I will perform a modemmst erase
LuckyNuke1310 said:
EDIT 2: And yes, it worked! Now everything is back. A real thank you to @_ekis_ for his support and all the OnePlus 3 Telegram group.
Click to expand...
Click to collapse
Heya! Got the same problem couple days ago, would you be so kind and share how you managed to get your WIFI working again? It will save a tonn of my nerves.
Hi there,
Yesterday I rooted my oneplus 5T and installed TWRP 3.2.1 & masgisk. Then, I´ve installed Pixel experience AOSP which seemed like fairly stable from the description. Everything went fine, the OS started I started configuring it then after setting the password I got the OS having always the setting app to crash. So, I thought well, I can just go to recovery and try once again factory reset. Otherwise, I can mount the recovery and install another ROM. I went to recovery and to my surprise it was asking for a password and mine didn´t work. I tried the factory reset and still the encryption stayed. I found that this version has a decryption problem and all my files were encrypted and not accessible, that was fine, since I had everything backed up. So, I have installed the new version of TWRP which seems to fix this issue after loosing all encrypted file. I have formated the data, system, dalvic and cache and installed once again pixel exerience but the OS keeps on bootloop. Have anybody seen something like this? How should I fix it? My best guess was to reinstall stock OS via adb, but in the past I've rooted a couple of devices and I've never seen something like this.
Thanks in advance
Ever since updating to A10 on my OnePlus 5t, I can no longer access the "SIM & network" menu within "Wi-Fi & internet". Each time I do, it loads a white page briefly with com.android.phone.oneplusOPMSimActivity as text across the top before kicking back to the previous page. If I try more than once, then the popup for "com.android.phone keeps stopping" comes up with the options for "App info" or "Close app". Each time I try to open this menu, the cell network drops and then reconnects. All of the other options in the "Wi-Fi & internet" menu work as expected.
Yesterday is when I started this whole process. I initially had my phone on the OOS version from late December 2019 (I don't recall the exact version number) with TWRP 3.3.1-0 for recovery and Magisk 20.4. I went into recovery, flashed the A10 OTA full zip, flashed the TWRP 3.3.1-x blu_spark v9.110 recovery, flashed Magisk 20.4, then booted like normal but had no cell connectivity at all (no baseband, IMEI was unknown, etc). After a lot of troubleshooting and reflashing several times, it turns out the one Magisk module that I had installed was not compatible as once I removed it and rebooted, the cell connectivity worked fine.
Fast forward to today and I noticed that I could not access the "SIM & network" menu. I have tried reflashing everything again; removing Magisk and leaving TWRP; going back to full stock without root; booting into safe mode; flashing back to TWRP, wiping Dalvik / ART cache, Cache, and System, then flashing OTA, Magisk, and blu_spark kernel 199; booting into TWRP and wiping Dalvik / ART Cache, Cache, and System, then flashing the OTA without TRWP or Magisk; etc. I could not access the "SIM & network" menu without the app crash at any point, even in safe mode on the factory ROM without root or custom recovery. I also tried clearing the cache and data for com.android.phone, SIM Toolkit, and Phone without any change.
I have not yet tried to take my device completely back to factory state yet (wipe all partitions and start from scratch) as that will take an eternity to restore from. If I have to I will, but I will try every option available to me before I do.
I did a logcat through adb and reproduced the problem. I'm not an Android dev so the logs are of questionable use to me but may point me to something to look at.
Any thoughts on what I should do? Is this something having to do with the previous recovery or root? Is this something caused by existing files on my phone? Is this something broken in the factory OTA and I need to contact OnePlus? The phone is functional otherwise, but man it is annoying not being able to access this menu.
Have you tried wiping data while on "full stock" state? (you will not lose /sdcard)
If that doesn't work, I would suggest that you use Unbrick tool 9.0.11 (which wipes everything including /sdcard) and OTA to OOS 10 (and reunlock).
---------- Post added at 07:32 AM ---------- Previous post was at 07:31 AM ----------
Have you tried wiping data while on "full stock" state? (you will not lose /sdcard)
If that doesn't work, I would suggest that you use Unbrick tool 9.0.11 (which wipes everything including /sdcard) and OTA to OOS 10 (and reunlock).
I had the same problem, dirty flashing the ETA from this xda post has fixed the issue for me for now: https://www.xda-developers.com/oneplus-5-5t-stable-android-10-oxygenos-10-update/
So, I hadn't messed with this for a while and just put it on the back burner. That was until I realized that I could not make calls as I would just get a bunch of chirping, garbled, chipmunk like sound which made the call useless. It worked fine if I answered a call, but not if I made one. I figured it was related to this issue so I went through the process of trying to get things working again. I tried just flashing the A10 OTA again with the blu_spark TWRP and Magisk 20.4, but that didn't fix it. I then proceeded to try and do a full backup of my phone as I was going to try the full wipe and start over fresh, but trying to backup everything is a joke through the USB2.0 connection on this phone let alone trying to get everything just in case I wanted to roll back to how the phone was working prior to the wipe.
At some point I gave up on the backup stuff and just got my user data. Then I got the idea to try going back to the previous working version of Android Pie. I don't recall what my thought process was, but it didn't end up working. For whatever reason, the 53 update was doing the same thing the 54 update did where it would boot up and immediately power off once the lock screen came up. It worked fine before with update 53, but now it wasn't so I flashed back to A10. Now, suddenly, I've noticed that I can access the "Network & SIM" section of the menu without that error from before. I don't know when or what fixed that issue, but it works every time now. Mind you, I did wipe the Dalvik/ART cache, cache, system, and vendor partitions at various points in my attempt to get things working, some of them more than once. I also played around with what partitions were mounted within TWRP though I really did not know what I was doing.
The chipmunk, chirping, garbled thing is still there, but it sounds like many people have had that issue with A10 on other phones. So luckily enough, just turning on and off speaker phone fixes the issue immediately (but I believe for just that call). That is an easy enough work around for me. As much as I want to leave my phone alone, I still have an issue where the phone always boots into recovery first and I have to select reboot > system through TWRP for the phone to boot up normally. I tried reflashing things multiple times, wiping the various partitions, and even some commands from a Nokia forum, but nothing worked. I imagine this is because I messed with the mounted partitions within TWRP and did a flash, but I am not sure on that. I think it could be that the system is booting into recovery because it thinks that is the "normal" partition with the whole A/B partition system, but again, I am not sure on that. I may post again if I end up figuring that all out.