I did something stupid(because frankly i have no idea what some of the things in the cwm mod do)
I'm not sure exactly what triggered this but I read somewhere that i should format my system then i did a data/cache wipe and every single file on my phone disappeared so now i can't even relock the bootloader to flash an ruu file because whatever thing that was on the phone to enable that also got wiped. I've tried flashing other roms to get the files back but obviously that isn't going to work. Can anyone help me out? I'm freaking out and I don't want to have to buy a new phone just because I messed up
I'm still not exactly sure what the problem was but it seems that my phone was messing up because cwm was crashing when attempting to install CleanRom 6.0 from the sd card. And for whatever reason, the third time i attempted to install this rom, it worked and my phone seems to be working fine.
Hi, I have a Xperia Neo V (MT11i) which is not rooted, not BL unlocked, no CWM, no Custom ROM, not even OTA updated. It is like the day my gf bought it, didn't even OTA updated it as i said (so it is still 2.3.4 GB).
For some weird reason the phone is dead now and boot loops while trying to power it on. I don't care if it is a software or hardware issue for now but I would like to know if there is anything to be done in order to recover the DATA (the contacts mainly) from the phone.
I already tried booting into safe mode didn't work, booting into recovery (don't know if there is a stock recovery actually) didn't work either. I don't want to revive the phone I just want to extract or recover the data from the phone.
Is it possible to install CWM in order to make a NANDroid Backup and exctract the data from there and all these without being able to boot the phone and without wiping the data? Maybe I should try fastboot mode and Flashtool?
Thanks
P.S There was not a google account linked with the phone so no cloud buckup was done (sadly) :<
Edit: Never mind solved it.
I also have this problem 3 days ago but I want to revive the phone, can someone please help me? tyvm.
Hi All,
Can I run this past you guys as I don't want to brick my phone...
I want to downgrade from B170 back to 121, I have installed a ZIP with a few Xperia things in it and its messed up a few things on the phones system partition, nothing critical the phone boots etc... its just my launcher isn't saving its settings, it has duplicated my ringtones with Xperia ringtones so I want to go back to 121 and then go back up to 170 with a clean ROM to try customising it again.
My plan was to put the stock recovery.img back in then use the MM downgrade ROM so that it does the getting to 95%, I will then run the 121 full ROM update.app, is this the correct thing to do to perform a downgrade?
Also, if I backup up boot.img, system.img etc... once I am on B170 I presume I can use these to recover my phone back if I mess around with the system and want to go back to factory without doing the above process every time? I want to try and create a custom ROM for the phone because EMUI is doing my head in with certain features
Thanks for your input
The method above worked without issue I have got back to stock 121 then upgraded back to 170 happy days!
tl;dr - Can't seem to find my way out of a software brick. Have sideloaded the stock OS from 1+ but still forever getting the spinning dots or fastboot screen, depending on which mode i boot into.
Hi all. Signed up to make this thread, but i've been lurking for years.
I have a OnePlus X that is about the least modded smartphone i've ever owned. I've never been pleased enough with a retail product that i didn't feel compelled to strip out the bloat and start over, until this phone. Other than stock, i've just got a gallery app, some apps for manipulating text files or compiling code, couple games, and social media apps.
Anyway, a few days ago i got a notification about a software update. Downloaded. Installed. Updated. No problem.
Maybe yesterday or the day before, it showed up again. This morning i downloaded, installed, and suddenly i have apps closing. It's been over 12 hours so i'm hazy on how it all started, but i was getting something like "package installer" errors when attempting to open some apps. Same deal when i went to adjust permissions of those affected apps. Every time i unfocused a box that had pulled up swype, i would get an error message saying swype crashed or closed or something.
So i started uninstalling third party apps (i don't keep many, and most i've had for years so i think they're probably trustworthy). Same deal. Started uninstalling updates to google apps. Same deal. Went to uninstall and reinstall some non stock apps that i'd kept previously. Nothing.
I went to cook breakfast while an app was reinstalling, and i came back to a red dot on my screen with two white dots chasing each other around it. From what i'm reading that's a sign of a bootloop or software brick. I've taken all steps i could find, including wiping cache and sideloading a fresh stock OS, but to no avail.
Is it that i've ruined my google apps somehow and need to restore them? How would i even go about figuring out what the problem is? Any advice or guidance is appreciated
Hi,
As your device is in bootloop state, try flashing the stock rom. Make sure you wipe data and cache. As far as after update problems, i faced it few times. After updating many app crashed and phone hangs. So i prefer clean flash over dirty flashing, to make sure everything is hazel free. For the time being i upgraded from 3.1.2 to 3.1.3 without wiping data or cache and facing no problem( of course since it was an OTA). But sometimes situation comes when after update phone act weird, so tbe option which i prefer then is clean flashing the stock rom. Hope this helps.
"A09" said:
Hi,
As your device is in bootloop state, try flashing the stock rom. Make sure you wipe data and cache. As far as after update problems, i faced it few times. After updating many app crashed and phone hangs. So i prefer clean flash over dirty flashing, to make sure everything is hazel free. For the time being i upgraded from 3.1.2 to 3.1.3 without wiping data or cache and facing no problem( of course since it was an OTA). But sometimes situation comes when after update phone act weird, so tbe option which i prefer then is clean flashing the stock rom. Hope this helps.
Click to expand...
Click to collapse
I have wiped cache, deleted data, tried a factory reset in the stock bootloader, and i have used ADB to sideload a full stock rom (not upgrade package) that i downloaded from OnePlus.
Flash old stock recovery then 2.2.3. From there you can flash any MM stock firmware.
Exodusche said:
Flash old stock recovery then 2.2.3. From there you can flash any MM stock firmware.
Click to expand...
Click to collapse
Pardon me for being nooby, but how do i do this? Do i just sideload in ADB like i did the ROM? Most instructions i'm finding assume access to the OS either normally or through fastboot. I'm just stuck in the default recovery.
Thanks for the tip, though. Looking for a copy of the old stock recovery now. Did OnePlus alter their stock recovery recently? In some threads i've seen people say that a recent update made them unable to load a non-stock ROM. Is that the new recovery blocking access to non-1+ operating systems?
jtg1984 said:
Pardon me for being nooby, but how do i do this? Do i just sideload in ADB like i did the ROM? Most instructions i'm finding assume access to the OS either normally or through fastboot. I'm just stuck in the default recovery.
Thanks for the tip, though. Looking for a copy of the old stock recovery now. Did OnePlus alter their stock recovery recently? In some threads i've seen people say that a recent update made them unable to load a non-stock ROM. Is that the new recovery blocking access to non-1+ operating systems?
Click to expand...
Click to collapse
Fastboot flash easiest way. Make sure it's the old recovery from 2.2.2. Not the new mm stock recovery.
Yes, but how do i install the old stock recovery? I dug around on the forums and found the file, but the phone rejects it when sideloading and doesn't show the .img in the filesystem when inserted on a SD card.
Have to send it off to 1+ maybe? Literally all i can access right now is the (new) stock recovery. I never modded, rooted, etc before the software update sent me into the chasing dots
jtg1984 said:
Yes, but how do i install the old stock recovery? I dug around on the forums and found the file, but the phone rejects it when sideloading and doesn't show the .img in the filesystem when inserted on a SD card.
Have to send it off to 1+ maybe? Literally all i can access right now is the (new) stock recovery. I never modded, rooted, etc before the software update sent me into the chasing dots
Click to expand...
Click to collapse
I m not a dev, i m a newbie like you. i hv done a lot of experiments with my oneplus-x, as for u the first update u got few days back should be oos 3.1.2 and the one u got 2 days before should be 3.1.3. When u upgrade from lollipop to marshmellow, even your stock recovery got upgraded to latest version, which is something different from old lollipop recovery.
You said you have access to recovery mode. thts pretty much gud, what u can do is that wipe data and cache through stock recovery and do a clean install of oos 3.1.3. I ll be providing all the necessary links down below. If you need assistance with fastboot cmds and anything feel free to ask.
Thanks to original link provider @Sachin7843
Useful Links: -
1. Stock Lollipop Recovery - https://s3.amazonaws.com/oxygenos.oneplus.net/OPX_recovery.img
2. Official TWRP Recovery - https://dl.twrp.me/onyx/
3. Blu Spark Recovery - http://forum.xda-developers.com/devdb/project/dl/?id=20236
4. SuperSU for OOS 3.x.x - https://drive.google.com/file/d/0B4K5cvm1zdldcmZpc3RuVnRjUUE/view
5. Unbrick Guide - http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
6. Official Oxygen OS 3.1.3 link - https://s3.amazonaws.com/oxygenos.o...OTA_018_all_201609291837_741146bcf28e4587.zip
7. SD Card Writable fix in MM - http://forum.xda-developers.com/android/software/fix-extsd-fix-v1-0b-2016-01-18-t3296266
8. For Stock MM Recovery - http://forum.xda-developers.com/oneplus-x/general/oxygenos-3-1-0-marshmallow-community-t3445043
Sorry for my bad english
jtg1984 said:
Yes, but how do i install the old stock recovery? I dug around on the forums and found the file, but the phone rejects it when sideloading and doesn't show the .img in the filesystem when inserted on a SD card.
Have to send it off to 1+ maybe? Literally all i can access right now is the (new) stock recovery. I never modded, rooted, etc before the software update sent me into the chasing dots
Click to expand...
Click to collapse
Don't sideload it, use fastboot to flash it. "Fastboot flash recovery name.img" - without he quotes and the image name.
Sorry for vanishing. Had a busy week.
Not sure what happened the first time i tried to put the 2.2.3 image on the SD card, because the file didn't show up in my recovery, but i tried again later (after giving up on flashing the old recovery, since i couldn't figure out how to do that in recovery) and managed to do a clean install of the older OOS version.
That did the trick, and after booting up, my phone proceeded to update again - this time without any crashes or errors with my apps afterward. The phone still does the red dot with the white dots chasing around it when it boots up, which must be the new boot screen. It also seems to stay on that screen for much longer than it stayed on the old morphing shape boot screen, but it still boots up reliably now after 30-60 seconds rather than freezing in boot forever.
I've since enabled dev mode on my phone. Is that going to be enough to enable ADB commands from recovery? I kind of like that i've kept my phone stock, so i'll leave it that way if i can, but it would have been much easier to fix this problem if i'd had access to most of my debug commands. As it was, without dev mode and in the standard recovery, it seemed that sideload was the only command i was able to use, and only when the phone was requesting a sideload over usb
There were some issues installing Android 11 on my phone, and now I'm in a situation where,
- The phone goes into fastboot
- Remains there for 5s
- Resets
Sadly, this time period is not enough to be able to pass vendor.img and system.img from the PC to the phone, so the I can't run flash_all.sh in order to reset the phone.
I was able to flash everything other than vendor and system partitions in 5s chunks, but this doesn't solve the problem.
I've also tried flashing twrp/orange recovery but this doesn't change anything either.
Is there anyway out ? I can't even shutdown the phone.
Fastboot usually reboots automatically if there are no or incorrect drivers installed. Try a different USB port first and if it doesn't fix the issue, then reinstall drivers with these https://developer.android.com/studio/run/win-usb
Also pay attention to which drivers you install, do not confuse ADB and fastboot/bootloader drivers.
spycimasala said:
There were some issues installing Android 11 on my phone, and now I'm in a situation where,
- The phone goes into fastboot
- Remains there for 5s
- Resets
Sadly, this time period is not enough to be able to pass vendor.img and system.img from the PC to the phone, so the I can't run flash_all.sh in order to reset the phone.
I was able to flash everything other than vendor and system partitions in 5s chunks, but this doesn't solve the problem.
I've also tried flashing twrp/orange recovery but this doesn't change anything either.
Is there anyway out ? I can't even shutdown the phone.
Click to expand...
Click to collapse
Hmm weird issue
Which rom did u flash?
ABHINAV-ACHHA said:
Hmm weird issue
Which rom did u flash?
Click to expand...
Click to collapse
I was playing around with Lineage 18; updating to Android Q after installing stock was probably not a good idea.
I fooled around with the flash script and let the phone's battery run down a few times. There was one point where the phone didn't reset in 5s, and I was able to flash the stock rom. I was playing fast and loose before; need to be a bit more careful now.
spycimasala said:
I was playing around with Lineage 18; updating to Android Q after installing stock was probably not a good idea.
I fooled around with the flash script and let the phone's battery run down a few times. There was one point where the phone didn't reset in 5s, and I was able to flash the stock rom. I was playing fast and loose before; need to be a bit more careful now.
Click to expand...
Click to collapse
May be u can try for edl method and flash stock
But "LOOK BEFORE YOU LEEP"