*** Urgent help needed *** - Sony Xperia M

I wiped data/factory reset, wiped the cache and wiped the media, installed cm12 nightly (tried 2/19 and 2/18/15) along with gapps through sdcard and when both were done i rebooted.
Rebooting displays Sony logo for a while then reboots and boots into CM recovery again...
I noticed while installing both zips cm12 and gapps it was showing e: cannot load volume /misc yet the progress bar continued on both and finished.
what is the problem? why does it take me back to recovery instead of loading cm12?
Please help
device is Xperia M single sim

I think that is a version specific bug. Try an older nightly.
*blink*

tried 4 nightlies the same result.
let me explain what i did:
I had a 4.3 xperia m single sim with locked bootloader.
installed fastboot drivers, phone fastboot drivers and all android sdk java... all
i unlocked the bootloader following the steps on sony's web page.
i went into cmd typed fastboot boot boot.img with the img from cm12 nightly zip.
both on the unlocking bootloader and then booting the img it said success/ok.
i then went to recovery wiped data cache media factory resect and installed cm12 zip and gapps from sdcard.
and now every time i start it shows sony logo for a while then restarts and goes back to cm12 recovery...

Related

adb Sideload cm13, stuck on boot animation

Hi- I've recently gotten ahold of a old SE xperia arc, it was stock ICE, non-bootloader unlocked, not rooted etc.
I've unlocked the bootloader w/ sony's webpage where you fill in imei etc,
I go for installing a custom rom, namely the cm13 from the LX Project page ( http://legacyxperia.github.io )
i extracted the boot.img from the zip, did fastboot flash boot boot.img .
when i enter recovery after doing this, I have no option to flash from sdcard, where i've put the romzip, the only option i see is sideload, I've never used adb sideload functionallity before, i'm used to do it from the sdcard inside the clockwordmod recovery.
Anyway, formated /system, etc., fired up adb, did the sideload of rom & gapps (Mardon's Mini GApps), and then rebooted.
Now the device is stuck in boot animation of marshmellow. What to do?nevermind, the power of trying, trying and trying again 10 times actually made it boot, yet- ive done nothing different.

Cannot load image fastboot

I've recently tried to update my radio and bootloader to the latest versions, i was on a custom rom (7.1.1), I've updated the bootloader and radio via fastboot and wiped the cache then rebooted then my phone was stuck in a never ending boot and all is saw was the boot animation, i decided to reboot the phone so i held the power button until it restarted and to avail, the same thing happened. I rebooted to twrp and tried to wipe the cache and dalvik/ART cache and i got an error that it cannot be mounted and the partition size was at 0mb and twrp could not repair it either, and it could not format any of my partitions, so i tried to return to stock and i tried to flash the images from the stock .zip provided by google and it said that it could not load any images. I can access download mode and twrp, any solutions? (someone said to flash the vendor image after flashing both the radio and bootloader images? could that have cause my problem because it did not flash it?
i was on the latest vendor already)
thanks.
EDIT: after continuously trying to wipe the cache & dalvik/ART cache in twrp it worked and it recognized the partitions and it wiped and my device was able to boot, i'm not sure what caused the problem but it boots properly now, although i'm not sure if i can flash in fastboot again, otherwise it works.

Phone always boots into twrp not able to see one plus boot logo.Pls help

I had formatted all things including internal storage using twrp. After that I flashed oxygen os 4.0 with USB using twrp.Installation is successfull.But when I rebooting the system it still boots into TWRP screen.I am not able to see one plus boot logo as it always boots to twrp screen even after successfully installation.I am wondering why even after succesfull flashing still the phone always boot into twrp screen.Pls help in resolving the issue
Flashing a lower version and then the 28 version back helped me... Had the same problem
jaganmohans said:
I had formatted all things including internal storage using twrp. After that I flashed oxygen os 4.0 with USB using twrp.Installation is successfull.But when I rebooting the system it still boots into TWRP screen.I am not able to see one plus boot logo as it always boots to twrp screen even after successfully installation.I am wondering why even after succesfull flashing still the phone always boot into twrp screen.Pls help in resolving the issue
Click to expand...
Click to collapse
1 ) flash stock recovery and sideload full zip of 3.2.8 oxygen os
2) boot to system
3) reboot to stock recovery
4) sideload full zip of 4.0.1
5) boot to system
6) boot to bootloader and flash twrp -28 recovery (adb fastboot flash)
7) after flashing boot to twrp recovery from bootloader
8) flash SU SR2 v2.79 and boot to system

Stuck at bootloop after installing stock rom

My device was rooted with magisk,and when i tried to update device to android 10 manually it restarted in twrp recovery mode.
When i tried to format data it said "unable to mount vendor ( it was showing some permission issue).
Then i flashed Stock rom and it installed successfully. Then i cleared cache and data and rebooted my device. And now its stuck in boot loop.
Please help me.

Bricked? Solutions?

Hello.
Tried flashing older stock rom via TWRP.
TWRP installed fine, worked fine, flashed vbmeta, still everything worked.
Downloaded ROM, put it into the sd card, went into twrp, formatted data, rebooted into twrp again, wiped Dalvik/ART cache, cache, system, vendor and internal memory, tried flashing, gave error 7, with "mkdir folder file not existing or whatever". In twrp i went into terminal, made a directory /cache/recovery, tried flashing, worked. Wiped dalvik and when i tried to reboot, the backlight turns on for a split moment and then it turns off.
Recovery does the same, and fastboot lights up the screen with the image of fastboot but it turns off. Plugging it with the usb makes it so it repeatedly turn on backlight and off again.
What does this mean? Device dead? Any help?
Thank you.
Maybe try flashing a custom rom
With what tools if I may ask? Any advice you can give me?
Fastboot doesn't stay on like it should, the screen just flashes the fastboot picture and it restarts again. Recovery does the same.
Try following bliss rom guide with installation of twrp
Trying to do anything with ADB tools just gives me a "< waiting for any device >".
I'm sure there's other ways of flashing twrp
VirusWar said:
Hello.
Tried flashing older stock rom via TWRP.
TWRP installed fine, worked fine, flashed vbmeta, still everything worked.
Downloaded ROM, put it into the sd card, went into twrp, formatted data, rebooted into twrp again, wiped Dalvik/ART cache, cache, system, vendor and internal memory, tried flashing, gave error 7, with "mkdir folder file not existing or whatever". In twrp i went into terminal, made a directory /cache/recovery, tried flashing, worked. Wiped dalvik and when i tried to reboot, the backlight turns on for a split moment and then it turns off.
Recovery does the same, and fastboot lights up the screen with the image of fastboot but it turns off. Plugging it with the usb makes it so it repeatedly turn on backlight and off again.
What does this mean? Device dead? Any help?
Thank you.
Click to expand...
Click to collapse
i think it's dead
-when the twrp gave you the error you should log it
-you should format data after flashing a rom ,not before (and only few roms require it)
your only option is flash VBMETA then TWRP again and see if it work
use the unofficial twrp : (3.3.10)
https://forum.xda-developers.com/re...ecovery-unofficial-twrp-xiaomi-redmi-t3997267
You should have formatted data partition after flashing the rom(not manually create those folders). You would be okay.
Any solution?

Categories

Resources