Today i bought Sony Ericson Xperia Mini ST15i, i upgraded the default firmware to the latest v.62 then i used flashboot to unlock the bootloader which appeared to work according to flashboot in command prompt. I then booted into the CWM-based Recovery 5.0.2.6 and i did "wipe data/factory reset" then installed cynogenmod latest stable version then restarted and it just hangs on the cynagenmod logo, sometime it shows the unlock screen for a few seconds then shows cynagenmod logo. I can get into CWM Recovery, i've tried re-flashing my official backed up image that i made with CWM-based recovery and i've tried flashing cynagenmod. I've also tried formatting cache, data and system and then flashing cynagenmod or the backup image but still doesn't work.
The links on this site for the v.58 firmware are dead.
I need to bring my phone back to life and prefereably put the latest cynagenmod on it. The phone was factory unlocked to all networks btw, i'd like to keep that.
I have "flasher" which is able to communicate with the phone but i've got no original images to try and re-flash my phone with.
PLEASE HELP!
hajj_3 said:
Today i bought Sony Ericson Xperia Mini ST15i, i upgraded the default firmware to the latest v.62 then i used flashboot to unlock the bootloader which appeared to work according to flashboot in command prompt. I then booted into the CWM-based Recovery 5.0.2.6 and i did "wipe data/factory reset" then installed cynogenmod latest stable version then restarted and it just hangs on the cynagenmod logo, sometime it shows the unlock screen for a few seconds then shows cynagenmod logo. I can get into CWM Recovery, i've tried re-flashing my official backed up image that i made with CWM-based recovery and i've tried flashing cynagenmod. I've also tried formatting cache, data and system and then flashing cynagenmod or the backup image but still doesn't work.
The links on this site for the v.58 firmware are dead.
I need to bring my phone back to life and prefereably put the latest cynagenmod on it. The phone was factory unlocked to all networks btw, i'd like to keep that.
I have "flasher" which is able to communicate with the phone but i've got no original images to try and re-flash my phone with.
PLEASE HELP!
Click to expand...
Click to collapse
Try downloading the stable version 7.1.0.1 or something like that....doent download the one which says .2 at the end... 0.1 will definately work..
oh wow, it actually fixed it, i can't believe it !
Do you know which file i need for the google apps by any chance?
there are gapps file on xda forums. try searching it for gapps for cyanogenmod 7.1.0.1 gapps....u will definately get it....
i've already looked, the only thing i get is this: http://wiki.cyanogenmod.com/index.php?title=Latest_Version#Google_Apps
the xperia mini isn't listed so i don't know which to choose.
http://api.viglink.com/api/click?fo...txt=Download&jsonp=vglnk_jsonp_13297674014261
try this one....it should work
Related
Hi guys,
I'm quite the newbie to advanced techniques of rooting/unlocking/flashing as this is my first Android!
Nevertheless, I successfully rooted my Live With Walkman WT19i (4.0.A.0.58) using the Zerg rush method.
Then I installed ClockWorkMod Recovery 5.0.2.7-nAa-r2(ported by nobodyAtall) and made a Nandroid backup.
Later I followed Sony's official guide on unlockbootloader.sonymobile.com/instructions to unlock my bootloader. To check if the unlock was successful, I went to the Service Menu where it said Bootloader Unlocked: Yes.
Then placed CM 7.2 coconut on the SD card, booted into Recovery, wiped data and cache partition, install ZIP from SD card. It then gave me an assert error (something along the lines of Status 7 error, Installation Aborted). So I read somewhere to remove the first line from META-INF\com\google\android\updater-script in my CM 7.2.0 ZIP package. So I once again tried installing ZIP from SD card. This time no error showed up. I got a message like ZIP updated or something. Then I restarted the phone and now its stuck for around 10 minutes on the 'Sony Ericsson' initial screen. No sign of CyanogenMod bootscreen either.
Consequently I can't enter recovery mode too. (because the Vol down button needs to be tapped just BEFORE the Sony Ericsson screen vanishes (which doesn't vanish at all now!))
Any help would be greatly appreciated! Is the phone 'bricked'? Thanks!
Have u try to flash ftf using flashtool?
Sent from my WT19i ExMIUI-ed
blackstallion1234 said:
Hi guys,
I'm quite the newbie to advanced techniques of rooting/unlocking/flashing as this is my first Android!
Nevertheless, I successfully rooted my Live With Walkman WT19i (4.0.A.0.58) using the Zerg rush method.
Then I installed ClockWorkMod Recovery 5.0.2.7-nAa-r2(ported by nobodyAtall) and made a Nandroid backup.
Later I followed Sony's official guide on unlockbootloader.sonymobile.com/instructions to unlock my bootloader. To check if the unlock was successful, I went to the Service Menu where it said Bootloader Unlocked: Yes.
Then placed CM 7.2 coconut on the SD card, booted into Recovery, wiped data and cache partition, install ZIP from SD card. It then gave me an assert error (something along the lines of Status 7 error, Installation Aborted). So I read somewhere to remove the first line from META-INF\com\google\android\updater-script in my CM 7.2.0 ZIP package. So I once again tried installing ZIP from SD card. This time no error showed up. I got a message like ZIP updated or something. Then I restarted the phone and now its stuck for around 10 minutes on the 'Sony Ericsson' initial screen. No sign of CyanogenMod bootscreen either.
Consequently I can't enter recovery mode too. (because the Vol down button needs to be tapped just BEFORE the Sony Ericsson screen vanishes (which doesn't vanish at all now!))
Any help would be greatly appreciated! Is the phone 'bricked'? Thanks!
Click to expand...
Click to collapse
You have to flash a compatible cm 7.2 kernel. You can use the one that comes with the downloaded zip. Or you can use the ported rage kernel for cm 7.2.
Sent from my ics wt19i using tapatalk 2
Works great!
motorazrv3 said:
You have to flash a compatible cm 7.2 kernel. You can use the one that comes with the downloaded zip. Or you can use the ported rage kernel for cm 7.2.
Sent from my ics wt19i using tapatalk 2
Click to expand...
Click to collapse
Thanks a bunch there mate! I was still on stock kernel! I flashed boot.img from the CM 7.2 ZIP. Initially it got stuck in a (boot?)loop and I saw that the same stuff kept happening through
Code:
adb logcat
but after a restart, it works fine. Except that gApps, specially Market sometimes works and sometimes doesn't on wifi!
Thanks again! Its a huge world out there about flashing/unlocking/kernels/ROMs and stuff so I guess it's somewhat easy to get lost!
Hi, few month ago, I have unlocked the bootloader, rooted my phone, and installed CWM and CM 11.
It was quite buggy, and OTA updates didn't work, and I needed something more stable.
Yesterday, I wanted to reboot into recovery, and try flashing SlimKat or a newer CM if I don't like the Slimkat.
The combination of keys for Recovery didn't work and there wasn't any reasonable way to get around it.
On adb, the phone got detected, but offline, so I wasn't able to reboot into recovery this way.
Fast forward couple of hours, I have tried flashing about everything, but didn't manage anything besides being able to pass adb commands.
Now,
- when I turn on the phone the phone hangs on the Sony logo and I have to force turn it off
- I get the phone on ADB even when it keeps hanging on the Sony logo
- I can get into Fastboot by holding the up button on conneting to computer
- I have flashed the boot.img from CM11 for XPeria P to bring CWM back, but didn't happen, or did happen, but I can't get into recovery
- "adb reboot recovery" brings me to the same old hanging SONY logo.
- pushing whatever on boot doesn't help > SONY logo
Please help!
Why not just flash stock with flashtool?
[SOLVED] Partially...
I have downloaded FTF file for the device, and manage to flash it using Flashtool (worked only if I flashed incl. Kernel) and got the device up and running. I tried reflashing CM and Slim again, but none worked as I still wasn't able to get into recovery, so I reflashed once more. Finally, the device is working - with the stock firmware, at least...
davidszedely said:
worked only if I flashed incl. Kernel
Click to expand...
Click to collapse
This is a solution. When you flashing CM you need to flash CM kernel too. In some cases kernel needs to be flashed several times(for example before flashing CM and after flashing it).
Sorry for my bad English.
Thanks a lot for explanation. I'm happy to have the stock now, and will probably stick with it for the time being.
This is what i did
OK i ve been trying to flash a new custom rom on my Xperia P, i looked at a number of guidelines and doing things step by step.
Since im very new to this i downloaded a few Roms. I was following the guide "http://droidors.com/2014/07/08/update-xperia-p-lt22i-to-android-4-4-4-kitkat-with-slimkat-custom-rom/2/" and everything was going fine. I reached the step to "fastboot flash boot boot.img", i did that and then went on the next step to boot in CWM Recovery and install the zip rom and the Gapps. During the Zip Rom install i got status 7 error.
Now, i noticed that i might have flashed the wrong Rom so rechecked the guide and installed the correct Rom which is mentioned in "http://forum.xda-developers.com/xperia-u/p-development/rom-slimkat-4-4-2-release-candidate-t2657795" . But now THE PROBLEM IS, AFTER I FLASHED THE INCORRECT IMG, MY PC IS NOT RECOGNISING THE XPERIA P SAYING IT DOESNOT RECOGNISE THE DRIVERS, therefore im not able to copy the ROM Zip on the SDcard, to then run it from CWM.
After I flashed the SlimKat Rom, and things went out of hand ( till this point i could see Slimkat logo at boot and could also go in CWM Recovery ), I tried to restore through Nandroid Backup i had done. As soon i selected the restore option and then the backup file, within 2-3 seconds the phone went off, and then on boot all i can do is see "SONY" on screen. Nothing else happens. i cannot even go in CWM now, its just stuck on "SONY"
I then tried to flash the stock Rom through this link "http://forum.xda-developers.com/xperia-u/p-development/ftf-firmware-xperia-p-generic-world-t2322163", through flashtool to bring my phone back to life. I installed the drivers as per instructions from drivers folder, but for some reason the pc is just not accepting. I did install the drivers through this exact method yesterday night and it worked perfectly.
I have tried all this on a different machine, different cables and ports, but still the issue persists
Please suggest. I hope im asking at the right place.
Kindly advise, im stuck with no spare phone.
hello everyone
I would like to permanently hard brick my phone wt19i...... I tried everything from flashing other phone's rom, kernel and recovery. Tried using rom manager too, but nothing worked. As soon as I flash stock gb or stock ics, the phone comes back to life again.
Please if someone could suggest a working method so that even the service centre guys won't be able to fix.
Why would you want to do that
Easiest way would be to physically mess up the chip, shorting something or so.
Sent from my SM-N9005 using Tapatalk
How to short something in hardware.....all I found by searching was flashing improper things.....but each method failed....as soon as to confirm hard brick I tried to flash stock rom it flashed normally and booted too
anikanu said:
How to short something in hardware.....all I found by searching was flashing improper things.....but each method failed....as soon as to confirm hard brick I tried to flash stock rom it flashed normally and booted too
Click to expand...
Click to collapse
have Xperia Mini St15i rooted unlocked bootloader. Running on CM 11.0 very well
but I recent update to latest build 24072015 and I can't boot my phone; after I tried to restore my old backup,tried to install old Rom which is( I installed in past successful)l and tried flash Xperia mini stock rom ftf (various version) but phone doesn't start can say hard brick.
I can install all of them successfully but phone does not start. always displays error of "unfortunately the process com.android.phone has stopped and phone restart on boot logo again and again.
update......
I recently flash BeanStalk-4.4006-20131128-smultron and after many tries I success to start phone but I noticed that in apps only 50 MB memory is free. I didn't have installed any app. in past I have there is about 370 MB free.(xperia mini has 420 mb data partition)
I have try to erase system,data with fastboot but nothing happens
I attached text file of fastboot commands.
I tried to flash sony origional firmware too but it only restarts again and again .
I have tried to erase system and userdata with fastboot but i see that it encountered bad block in erase data, I can't understand why data partition can't be formated ? text document attached
I think my data partition is full. after reboot in recovery there is an error of " no space left in device " phone does not start normally. I can boot in recovery but still can not use phone .
running on CM 11 and this problem is start on flashing cm-11-20150723-UNOFFICIAL-LegacyXperia-smultron. after that my phone doesn't start.
hello,
I downloaded Flashify and I install with it TWRP (image), but I think, I downloaded a bad version, because when I restart my phone, It can't load boot screen..
- in 4.4 android I get error message: "error: can not load invalid boot image"
- in 5.0 android I dont get any info, it stops in boot screen..
I tried to change ROM (with full wipe), but it doesn't works (5.0 --> 5.0 --> 4.4 --> 5.0, etc.)
So I cant use my phone... Have you any idea? How I solve this problem? :/
thanks!
(sorry for my bad english..)
When you get into recovery does it look stock with the android there or does it show twrp.
If its not twrp you could use fastboot to try flashing a new recovery and then boot recovery after.
Then you could just reflash the fw you have before.
That could mean that you might have flashed the recovery img under boot.
Because you only restarted your phone and it just came up like black screen.
But what confuses me is you have went to 5.0 to 4.4 somehow and the problem still exists. Im wondering how you did that exactly, is it from backups or fw files from Asus.
If its the asus fw and the problem persists It might be the recovery and you might want to flash a different one.
The 4.4fw to 5.0fw should have flashed stock recovery again and the problem would have been solved. Only if you have used the downgrade fw and bootloader gets relocked
Overall its a weird problem
You could also try to flash cm 12.1 or 13.0 using custom recovery too if the bootloader is unlocked. And it should work just fine then you could go back to stock. You just might want to back up the data partition on stock then restore it after you get back to stock