Actually my OPO was running on OXYGEN OS for last 1-2 months. I bored with it so I thought for some time I should install CM12s. I installed CM12s. It installed correctly and running well. Wifi and internal storage was also accessible. After few hours I thought OXYGEN OS is good. While installing the CM12s I backed up current OXYGEN OS by using the TWRP. so I restored the OXYGEN SO. It recovered successfully. From here all problems started.
I turned on my WIFI. But it was not connecting to my OPO. I tried with my iball tablet its connect immediately. After that I opened File Manager but it was also not accessible. so I reinstalled the OXYGEN OS with a fresh start. WIFI worked very well. But STORAGE problem remains same. its showing 32GB free out of 54GB but I do not have access to it. I even tried with connecting to my LAPTOP. Result was same.
PLEASE NEED HELP.
I guess u try with different file manager, while acessing internal memory it gives some messages?
KDPalekar said:
Actually my OPO was running on OXYGEN OS for last 1-2 months. I bored with it so I thought for some time I should install CM12s. I installed CM12s. It installed correctly and running well. Wifi and internal storage was also accessible. After few hours I thought OXYGEN OS is good. While installing the CM12s I backed up current OXYGEN OS by using the TWRP. so I restored the OXYGEN SO. It recovered successfully. From here all problems started.
I turned on my WIFI. But it was not connecting to my OPO. I tried with my iball tablet its connect immediately. After that I opened File Manager but it was also not accessible. so I reinstalled the OXYGEN OS with a fresh start. WIFI worked very well. But STORAGE problem remains same. its showing 32GB free out of 54GB but I do not have access to it. I even tried with connecting to my LAPTOP. Result was same.
PLEASE NEED HELP.
Click to expand...
Click to collapse
You can try the following
1. Flash fastboot images of CMOS12
2. Flash TWRP
3. Flash OxygenOS zip
4. Restore the apps and data whichever you need
Related
Hi friends,
So I was running CyanogenMod 10.1.3 on my S3 and decided to update to the CM 10.2 snapshot that was available for download through the settings page. After messing around with it a bit, I decided I didn't like it and re-installed 10.1.3 through the same page. When it came back up, the CyanogenMod logo just kept turning and turning. I tried to re-install the CM 10.1 .zip file I had on the phone, but Clockworkmod couldn't find it. I also tried to restore to a backup, but again, CWM couldn't find any.
As I see it, all I need to do is get a new CM .zip onto the phone that I can flash from recovery. I downloaded adb for this purpose, but can't get it to open on my computer (Windows 7 x64). So, can anyone tell me another way to get the .zip onto the phone?
I greatly appreciate any help.
berichardson13 said:
Hi friends,
So I was running CyanogenMod 10.1.3 on my S3 and decided to update to the CM 10.2 snapshot that was available for download through the settings page. After messing around with it a bit, I decided I didn't like it and re-installed 10.1.3 through the same page. When it came back up, the CyanogenMod logo just kept turning and turning. I tried to re-install the CM 10.1 .zip file I had on the phone, but Clockworkmod couldn't find it. I also tried to restore to a backup, but again, CWM couldn't find any.
As I see it, all I need to do is get a new CM .zip onto the phone that I can flash from recovery. I downloaded adb for this purpose, but can't get it to open on my computer (Windows 7 x64). So, can anyone tell me another way to get the .zip onto the phone?
I greatly appreciate any help.
Click to expand...
Click to collapse
Hey it sounds like you have a couple issues there, not sure where to start. One thing I can help with is getting adb on the Win7 PC. What you need to do is download the Android SDK at http://developer.android.com/sdk/index.html. Once the Android SDK is on your machine then use that to get the Android Platform-tools. ADB.exe is part of the platform tools. I hope that helps.
did you save the CM .zip file to your phone's internal storage or an SD card? if internal, it may have been erased when you flashed back to CM 10.1. if you put it on your SD card, try reinstalling the SD card and reboot. i've had issues with my S3 where the SD card would come unseated when i put the back cover back on.
also, did you do a wipe when you reinstalled CM? sometimes that helps get you out of bootloop (but it erases all of your data, so hopefully you did a backup).
berichardson13 said:
Hi friends,
So I was running CyanogenMod 10.1.3 on my S3 and decided to update to the CM 10.2 snapshot that was available for download through the settings page. After messing around with it a bit, I decided I didn't like it and re-installed 10.1.3 through the same page. When it came back up, the CyanogenMod logo just kept turning and turning. I tried to re-install the CM 10.1 .zip file I had on the phone, but Clockworkmod couldn't find it. I also tried to restore to a backup, but again, CWM couldn't find any.
As I see it, all I need to do is get a new CM .zip onto the phone that I can flash from recovery. I downloaded adb for this purpose, but can't get it to open on my computer (Windows 7 x64). So, can anyone tell me another way to get the .zip onto the phone?
I greatly appreciate any help.
Click to expand...
Click to collapse
I've had bootloop problems with cm after trying to downgrade from cm10.2. Wiping data, cache, etc didnt help, it still boot looped for me. A TWRP backup was the only thing that saved me. I have used this to get out of a soft brick before, maybe try that as a last resort? Good luck, and i recommend using twrp recovery instead of cwm, it has given me problems before. Good luck!
dkh7m said:
did you save the CM .zip file to your phone's internal storage or an SD card? if internal, it may have been erased when you flashed back to CM 10.1. if you put it on your SD card, try reinstalling the SD card and reboot. i've had issues with my S3 where the SD card would come unseated when i put the back cover back on.
also, did you do a wipe when you reinstalled CM? sometimes that helps get you out of bootloop (but it erases all of your data, so hopefully you did a backup).
Click to expand...
Click to collapse
Hello. I had an older build of CM11 on my One S which started having some issues.
Programs kept closing etc, so I decided to get the latest build update.
I noticed that I couldn't turn on the wifi, it was dark grey.
I read some topics about it, and resetting your phone to factory and clearing the cache and dalvik would fix it apparently.
I tried all of that, still no wifi. Then I tried deleting everything on my SD card, still no wifi + my old rom on the SD card is gone. So I can't go back.
I tried downloading another rom, and my intention was to put it on my phone with USB mass storage, but my computer doesn't recognize my phone at all anymore. I tried using adb sideload, and even the command prompt says it can't recognize any device.
Summary: Stuck on a bad rom with no wifi, don't have a backup rom and I can't put a new rom on my phone.
What should I do?
Thanks in advance, really need my phone to work!
Hi!
I have been facing freezes(then reboots) and my computer not able to detect my internal storage(Windows was unable to install drivers)
This occurred randomly, everything was working just fine. The freezes started after my internal storage vanished. (I'm still able to transfer files through AirDroid) Have switched 3 ROMs, just flashed AICP and it crashed in titanium backup, so this is not a ROM problem.
Could my storage/partitions be corrupted? I am able to flash ROMs just fine though
Will flashing 6.6.10 through fastboot fix this?
(On a side note, formatting the cache partition used to take a few seconds, but it takes about 5 minutes these days, this has been happening for a few months now )
Thanks in advance
EDIT: Flashing the stock ROM did nothing. The problem persists. Internal battery short circuit...?
When I got my replacement tablet for the recall, I followed the instructions to kill the kill switch on my old tablet (a 16gb Wifi only version). I deleted the TegraOTA folder, and used the zip file as well. I then installed BlissPop and have left it that way since.
A few days ago, I decided to switch from the now-defunct BlissPop over to LineageOS. For some reason, I couldn't get the tablet to boot into recovery (I installed the TWRP app, wouldn't boot into TWRP; I flashed TWRP using fastboot, wouldn't boot into TWRP; I flashed Nvidia's stock recovery, still wouldn't boot into recovery).
So I decided to flash stock, but new everything (I think the 5.2 or 5.3 version). Booted into OS setup (without connecting to network) so I could enable debugging/connect with ADB. This worked, so I rebooted into bootloader and finally got into TWRP. But, because of shared storage, I couldn't get into system folder to see if TegraOTA was back. So I decided to go back to original stock so I could access internal storage. Performed a factory reset, flashed the very original stock system/recovery/boot from these forums.
Restarted tablet and... nothing. Black screen. When its plugged in, the light shows it has charging, but no amount of time or effort pressing the power button will get it to do anything.
Did I brick it somehow? I've flashed various upgrades, OTAs, custom ROMs on both Shield Tablets I've had and am 99.99% sure that I didn't do anything wrong this time. Did I unknowingly flash something that would allow the kill switch to be thrown even if the tablet was never connected to my network? Is there any way to test? Basically I want to be certain its 100% done for before I toss it and buy a new tablet (I sold my replacement earlier this week, which is why I decided to upgrade the old one in the first place). Thanks in advance for any help!
If you installed latest stock and system detected tablet with bad battery it probably killed itself even if you did not connected it to internet
So to give a backstory, yesterday night, I ****ed my phone. It got corrupted, but I made a backup before. So today I tried to restore the backup. That did not go very well. So I searched up solutions and found out that it might be the os that is corupted after restoring the backup. So I side-loaded the official oxygen os 9.0.2. That worked and right now I got all my data back+my device is working kinda. After it started I saw that it's not conected to wifi. So I tryed to turn on the wifi but after like 3-4 seconds of trying to start the wifi, it automaticly turns itself off. Anyone got an idea on how to fix this?
Edit 1: My MAC adress is 02:00:00:00:00:00? Uh this does not seem right.
Mighty_Pig said:
So to give a backstory, yesterday night, I ****ed my phone. It got corrupted, but I made a backup before. So today I tried to restore the backup. That did not go very well. So I searched up solutions and found out that it might be the os that is corupted after restoring the backup. So I side-loaded the official oxygen os 9.0.2. That worked and right now I got all my data back+my device is working kinda. After it started I saw that it's not conected to wifi. So I tryed to turn on the wifi but after like 3-4 seconds of trying to start the wifi, it automaticly turns itself off. Anyone got an idea on how to fix this?
Edit 1: My MAC adress is 02:00:00:00:00:00? Uh this does not seem right.
Click to expand...
Click to collapse
I got the exact same problem. Today too. I tried booting from slot a in recovery then that is when it started.
Any solution?
I did go into twrp tried wiping system, then reflashing oos9.0.2 and it was a no go.
I then went into twrp and wiped data and it worked. Of course all data was gone and had to clean install. Hope you have a data back up in twrp.