Hey guys, long time lurker, 1st time poster. I made a mistake with a miniCM9 ROM install.
I've had no problem rooting, unlocking the BL, Flashtool etc...
And I've done this before with a little Huawei and had no issues.
This time trying with a Sony Ericsson Xperia X10 Mini Pro.
I installed nAa's ICS kernel (u20_nAa-ics-04_2.6.29.6-nAa-ics-04.ftf), which worked fine. Then tried to install a ROM (MiniCM9-3.0.5-mimmi.zip).
And yes, I did read everything on the guides several times. BUT I was pretty sure I had the required firmware, my guess is that I didn't (Latest 2.1.1.A.0.6/2.1.1.C.0.0 SE firmware).
And yes I have searched and searched (and then searched some more) the forum for another noob who has asked the same question.
Anyway, here I am 3 days later with my tail between my legs :silly:
I would be most appreciative if someone can point me to a nice kernal like nAa's and a ROM that I can use previous to 2.1.1.A.0.6/2.1.1.C.0.0 SE firmware (I'm pretty sure that is the problem.)
Thanks in advance.
A z a z e l said:
Hey guys, long time lurker, 1st time poster. I made a mistake with a miniCM9 ROM install.
I've had no problem rooting, unlocking the BL, Flashtool etc...
And I've done this before with a little Huawei and had no issues.
This time trying with a Sony Ericsson Xperia X10 Mini Pro.
I installed nAa's ICS kernel (u20_nAa-ics-04_2.6.29.6-nAa-ics-04.ftf), which worked fine. Then tried to install a ROM (MiniCM9-3.0.5-mimmi.zip).
And yes, I did read everything on the guides several times. BUT I was pretty sure I had the required firmware, my guess is that I didn't (Latest 2.1.1.A.0.6/2.1.1.C.0.0 SE firmware).
And yes I have searched and searched (and then searched some more) the forum for another noob who has asked the same question.
Anyway, here I am 3 days later with my tail between my legs :silly:
I would be most appreciative if someone can point me to a nice kernal like nAa's and a ROM that I can use previous to 2.1.1.A.0.6/2.1.1.C.0.0 SE firmware (I'm pretty sure that is the problem.)
Thanks in advance.
Click to expand...
Click to collapse
Quite impressive, you list everything you've done. Only thing you've forgotten to do is tell us what your problem actually is
I'm guessing you lost your signal?
SmG67 said:
Quite impressive, you list everything you've done. Only thing you've forgotten to do is tell us what your problem actually is
I'm guessing you lost your signal?
Click to expand...
Click to collapse
Well that's a better reply than asking what I have done
"BUT I was pretty sure I had the required firmware, my guess is that I didn't (Latest 2.1.1.A.0.6/2.1.1.C.0.0 SE firmware)."
"I would be most appreciative if someone can point me to a nice kernal like nAa's and a ROM that I can use previous to 2.1.1.A.0.6/2.1.1.C.0.0 SE firmware (I'm pretty sure that is the problem.)"
That's my problem (where I said pretty sure that's the problem ; )
The kernel guide didn't mention the need for that firmware but the ROM guide did. I thought I had that one, but I don't think I did.
Is there another easy to use Kernel that is compatible with the old firmware?
A z a z e l said:
Well that's a better reply than asking what I have done
"BUT I was pretty sure I had the required firmware, my guess is that I didn't (Latest 2.1.1.A.0.6/2.1.1.C.0.0 SE firmware)."
"I would be most appreciative if someone can point me to a nice kernal like nAa's and a ROM that I can use previous to 2.1.1.A.0.6/2.1.1.C.0.0 SE firmware (I'm pretty sure that is the problem.)"
That's my problem (where I said pretty sure that's the problem ; )
The kernel guide didn't mention the need for that firmware but the ROM guide did. I thought I had that one, but I don't think I did.
Is there another easy to use Kernel that is compatible with the old firmware?
Click to expand...
Click to collapse
NO, that is not your problem... you flashed the right kernel and the right ROM, so what is not working for you? The thing that is not working is the problem.
Whether you did or did not have the right firmware may be the cause of your problem, but it is not your problem. So, what is not working???
Can you boot up the phone? If so, go to settings - about phone and check your baseband version, it should end in 4015 if you had the right firmware to start with If so, then that is not the cause of your problem.
SmG67 said:
NO, that is not your problem... you flashed the right kernel and the right ROM, so what is not working for you? The thing that is not working is the problem.
Whether you did or did not have the right firmware may be the cause of your problem, but it is not your problem. So, what is not working???
Can you boot up the phone? If so, go to settings - about phone and check your baseband version, it should end in 4015 if you had the right firmware to start with If so, then that is not the cause of your problem.
Click to expand...
Click to collapse
The phone gets the nAa splash screen repeating, can get into recovery and mount USB easily, load the ROM from SDcard, no workie, still gets nAa splash screen.
A z a z e l said:
The phone gets the nAa splash screen repeating, can get into recovery and mount USB easily, load the ROM from SDcard, no workie, still gets nAa splash screen.
Click to expand...
Click to collapse
Did you do: Wipe data/Factory reset, Wipe Cache and in the Advanced-menu: Wipe Dalvik-cache and Wipe Batterystats?
If the ROM doesn't boot, do those wipes again, it will usually work better if you do those wipes after you install the ROM.
SmG67 said:
Did you do: Wipe data/Factory reset, Wipe Cache and in the Advanced-menu: Wipe Dalvik-cache and Wipe Batterystats?
If the ROM doesn't boot, do those wipes again, it will usually work better if you do those wipes after you install the ROM.
Click to expand...
Click to collapse
I followed all the instructions on the guide, I did a wipe data/factory reset. Haven't tried the Dalvik part, I'll give it a go. Thanks.
SmG67 said:
Did you do: Wipe data/Factory reset, Wipe Cache and in the Advanced-menu: Wipe Dalvik-cache and Wipe Batterystats?
If the ROM doesn't boot, do those wipes again, it will usually work better if you do those wipes after you install the ROM.
Click to expand...
Click to collapse
I tried all that, still just get the nAa splash screen.
Anyone know how to check the firmware version when it's in this state?
A z a z e l said:
I tried all that, still just get the nAa splash screen.
Anyone know how to check the firmware version when it's in this state?
Click to expand...
Click to collapse
Find S1Tool, if you haven't got it already, and click the identify button I'm pretty sure it will tell you what is on your phone, but if you flashed the MiniCM9 ROM it should show Android 4.0 as version.
If all else fails, repair your phone with Sony Update Service or PC Companion, it will give you the latest official firmware, and then try again.
SmG67 said:
Find S1Tool, if you haven't got it already, and click the identify button I'm pretty sure it will tell you what is on your phone, but if you flashed the MiniCM9 ROM it should show Android 4.0 as version.
If all else fails, repair your phone with Sony Update Service or PC Companion, it will give you the latest official firmware, and then try again.
Click to expand...
Click to collapse
Thanks, I'll give that a go. PC Companion didn't work for me before that's why I tried the other method.
SmG67 said:
Find S1Tool, if you haven't got it already, and click the identify button I'm pretty sure it will tell you what is on your phone, but if you flashed the MiniCM9 ROM it should show Android 4.0 as version.
Click to expand...
Click to collapse
Ok, S1Tool says:
SOFTWARE VERSION: 1235-3411_2.1.1.A.0.6 - does that mean that's the firmware?
FILESYSTEM VERSION: WORLD-1-2-5_2.0.A.504 - or this number?
S1Tool not recognize the version of android (i use GB version), i tested it.
MODEL (from GDFS): U20a
SOFTWARE VERSION: 1235-3411_2.1.1.A.0.6
CUSTOM VERSION: 1239-2460_R4B
FILESYSTEM VERSION: WORLD-1-2-5_2.1.1.A.0.6
Azazel dont use PC Companion, dont work, use instead Sony Update Service.
Sorry for my english.
So using the Sony Update Service should make it usable again, even with the new Kernel and ROM on there?
No will update your phone with the last stock rom (unbricked phone).
After that try again.
Thanks guys, managed to get the phone working again. Thought it was SIM locked again, but it's come good.
Will try the update again in a couple of days.
The ROM guide says you need "Latest 2.1.1.A.0.6/2.1.1.C.0.0 SE firmware / Baseband: M76XX-TSNCJOLYM-53404015"
My phone says I have Firmware version 2.1 -update 1 and the above Baseband version.
Any ideas why the Kernel loaded fine but the ROM wouldn't work?
View if your bootloader is already unlocked.
Copy the rom and gaaps to your sdcard
Reboot on recovery mode.
Wipe data/factory reset, wipe cache and wipe dalvik cache
Flash rom, flash gaaps
Reboot your phone
and wait to boot 5 to 10 min.
Sorry 4 my english
Sent from my iPhone 7 using xda enterprise
Related
Hi everyone,
I was able to recover my phone on the weekend after trying my hand for the first time using FlashTool on the weekend. I understand now how putting .ftf files in the firmware folders work (please don't laugh at how non-technical I am with this - I am a Windows system admin by day - I just don't have a lot of under the hood experience with Android). I understand how to flash the .ftf files onto my handset.
I flashed on Saturday, in a means to recover my phone a whole bundled package (I got it from: http://forum.xda-developers.com/showthread.php?t=1192152&highlight=) It's essentially the stock 2.3.3 ROM and it has Baseband 2.1.71 prebundled.
The downside is that I can't install Xrecovery now because my phone isn't rooted now and I don't want to go through the process of using ADB to use gingerbreak.
Is there a 2.3.3+ ROM including BB 2.1.71 and xRecovery ftf bundle out there?
That thread is the pre-rooted 2.3.3 with recovery. Not sure what else you could want.
Try entering recovery when you turn the handset on and pressing the volume down key when you see the white Sony Ericsson text
Okay thanks. I've always entered recovery by going thru by pushing the back button (not volume down). Let me try it. I'll get back to you in a minute.
Ya pressing the volume down didn't get me into recovery. I've also tried installing xrecovery the usual way of downloading busy box, allowing non market apps, using a file mgr to open the xrecovery installer but it fails because the device isn't rooted. I can't su on a terminal emulator either so I don't think this rom i flashed is rooted.
It completely wiped my phone and installed 2.3.3 and 2.1.71 baseband (which is what I want) but now I want it to be rooted so I can play around with more ROMs.
Ok, I remember from when this first came out, you need to flash 2.1 firmware and root it, install xrecovery and then follow the procedure in that thread you posted. That should give you the pre-rooted and pre-installed xrecovery.
It's okay, If I'm going to do that much work I might just use the Android debug bridge (ADB) to install Gingerbreak. No big deal..
2.3.3 stock is a very nice improvement over 2.1 from what I remember. I used FreeX10 2.2 and it was nice as well (but I felt the UI looked a little dated). 2.3.3 stock looks and feels great, but I want even better battery life and better perfomane I know some of the custom ROMs can offer me.
I like the CM7 based 2.3.5 ROM I've seen on this site, and I wanna try 2.3 Free X10 from zdhiu.
Fair enough, I'm using the CM7 FXP rom and its flying. Battery life is pretty much the same as I was getting from SE firmware too.
Awesome!
So just to clarify the usual procedure:
You get your device rooted and xRecovery installed by whatever means. Since my X10 is a clean slate with just 2.3.3 on it with baseband 2.1.71, I will need to use Gingerbreak to root and subsequently install xRecovery.
Then put the .zip for the ROM on the SD card, flash it using xRecovery
Then remove battery, reboot, then using flashtool, flash the baseband and firmware?
I've only been using Android for a few months, and just learned about using custom ROMs in the past 6 weeks or so. I've learned a lot since then lol.
Sounds pretty much right to me if your bootloader is locked.
Okay, great. I really am learning more and more. I'm in IT myself for work, but phone hacking was never really my forte until just recently.
I like the type of flashing that I did in FlashTool with the current ROM I'm running from that previous post.
It was the baseband and firmware and ROM all bundled. I know FlashTool lets you make bundles too.. I find that easier than flashing the ROM in xRecovery and then flashing the firmware and baseband second.
What do you think?
I've found that installing the rom in xrecovery is good as I can make a full backup first and then flash the zip.
I always tend to flash the baseband and/or firmware first, but thats personal choice.
Ya I understand all of that. I am fully aware how to install xRecovery (on ROMs previous to 2.3), how to take backups, wipe caches, flash zips.
I used FlashTool to flash a firmware (it was a .ftf file) for the baseband, however when I turned on my phone, it went to the Sony Ericsson white text, then white LED, then boot loop. So I didn't flash that file correctly or I didn't flash the right file.
Is there any prebuilt ftf packages for 2.3.3+ ROMs you know of that include the 2.1.71 baseband? I found that FreeX10's 2.2 ROM was very quick and made my whole Xperia experience more fluid and fast, so I'm interested to try FreeX10 2.3.. I don't know if zdhiu has a prebundled ftf.
Dresden21 said:
Ya I understand all of that. I am fully aware how to install xRecovery (on ROMs previous to 2.3), how to take backups, wipe caches, flash zips.
I used FlashTool to flash a firmware (it was a .ftf file) for the baseband, however when I turned on my phone, it went to the Sony Ericsson white text, then white LED, then boot loop. So I didn't flash that file correctly or I didn't flash the right file.
Is there any prebuilt ftf packages for 2.3.3+ ROMs you know of that include the 2.1.71 baseband? I found that FreeX10's 2.2 ROM was very quick and made my whole Xperia experience more fluid and fast, so I'm interested to try FreeX10 2.3.. I don't know if zdhiu has a prebundled ftf.
Click to expand...
Click to collapse
Let me clarify...
1. ROMs are in zip packages, and are to be flashed using xRecovery.
2. Firmwares are in ftf bundles, which are flashed through flashtool.
3. If you want root and xRecovery on 2.3 follow aZuZu's post on rooting and xRecovery.
4. If you want to unlock the bootloader follow the_laser's thread
Dresden21 said:
Ya I understand all of that. I am fully aware how to install xRecovery (on ROMs previous to 2.3), how to take backups, wipe caches, flash zips.
I used FlashTool to flash a firmware (it was a .ftf file) for the baseband, however when I turned on my phone, it went to the Sony Ericsson white text, then white LED, then boot loop. So I didn't flash that file correctly or I didn't flash the right file.
Is there any prebuilt ftf packages for 2.3.3+ ROMs you know of that include the 2.1.71 baseband? I found that FreeX10's 2.2 ROM was very quick and made my whole Xperia experience more fluid and fast, so I'm interested to try FreeX10 2.3.. I don't know if zdhiu has a prebundled ftf.
Click to expand...
Click to collapse
You need to downgrade baseband so you can root.
Check here buddy....http://forum.xda-developers.com/showthread.php?t=1196808
then you can install xrec and install your rom. Might want to read this: http://forum.xda-developers.com/showthread.php?t=1254087
then this: http://forum.xda-developers.com/showthread.php?t=1278318
all very simple procedures.. good luck!
Dear XDA developers,
I was tired of sony ericson servers being overloaded and thus being unable to update my phone, so I decided that I wanted to have CyanogenMod on it. I followed this tutorial http://wiki.cyanogenmod.com/wiki/Sony_Ericsson_Xperia_Mini_Pro:_Full_Update_Guide and then I had a phone that kept showing me the startup animation of a droid with a spinning circle.
I had done the CWM backup before flashing as described by the tutorial. I've searched a lot on the internet and tried these tips to try to fix a bootloop:
- wipe cache
- wipe data/factory reset
- wipe dalvik cache
- install update.zip (cyanogenmod) again
- restarted 100 times
In all kind of combinations, nothing helped.
Then next I wanted to just restore the backup I had made, so I pressed Restore and selected the backup. Rebooted the phone and the SE splashscreen showed up. Then the SE logo kept displaying for minutes. I connected the phone to Logcat in Eclipse (I'm an android developer) to see that the phone kept doing the same loop over and over again.
In all the steps I did I never rooted the phone, because the tutorial didnt say so. After reading a lot it felt like I should have rooted it first. Can anyone confirm that this is correct?
I now beg for you help to tell me what to do next? I have downloaded latest flashtool, I also have a working flashboot. I dont know what to flash/do anymore. I'm totally lost and the phone is looping forever. What should I do now?
~Master004
reflash to stock FW using wootanserver.
...or you can just flash via fastboot prerooted kernel like Rage 2.4 for mini pro, and try everything again.
http://forum.xda-developers.com/showthread.php?t=1398910
and try reding this:
http://forum.xda-developers.com/showthread.php?t=1445821
and
http://forum.xda-developers.com/showthread.php?t=1226715
same problem
Guys I have the same problem, but I even rooted my phone, the CyanogenMod does start with the android on a skateboard and once the homescreen even came up but just rebooted straight after.
If I were to start all over with stock firmware how would I go on about doing that? Links?
Any help is much appreciated, thanks.
Did you flash the kernel provided in the zip file?
Also, before restoring your previous backup try doing a full wipe, non just factory, but go into mounts&storage from cwm and hit the fortmat sstem and then tr restoring backup.
All files and knowledge neede to resolve the issue can be found here http://forum.xda-developers.com/showthread.php?t=1568792
DONE!!!
Rudjgaard said:
Did you flash the kernel provided in the zip file?
Also, before restoring your previous backup try doing a full wipe, non just factory, but go into mounts&storage from cwm and hit the fortmat sstem and then tr restoring backup.
All files and knowledge neede to resolve the issue can be found here http://forum.xda-developers.com/showthread.php?t=1568792
Click to expand...
Click to collapse
After a lot of research I found the solution, even though it takes me back to stock rom I'm happy
Basically I repaired it with pc companion, on the home screen --> clicked on start under Support Zone; then Start under Phone Software Update;
then on the pop up box I clicked repair phone (underlined in blue); { click Continue, check box, Next} and just follow on screen instructions and the phone is reset to factory settings :good:
However I still found my bootloader unlocked when I tried to install rom again, don't whether it stayed or because I also unlocked my simlock today too.
Anyway the rom still didn't work for me so had to repeat this process all over again
If anyone has a good tutorial for rooting a sony xperia mini pro and & installing a good rom on it pls let me know, my model's still on Gingerbread and it hogs the battery crazy.
Try thishttp://forum.xda-developers.com/showthread.php?t=1688980
Or thistalk.sonymobile.com/thread/35239
Hit thanks f I helped.
Sent from my SK17i using xda premium
I've looked and not found an identical problem.
I've an x10 mini pro (U20i) which workls fine with the SE firmware, but as soon as I install a new kernel (tried the gingerbread and ICS nAa) I get the system freezing after the kernel boot logo.
I can get into recovery if I hit the back key during startup, but other than that all I can do is remove the battery.
I've tried booting with just the new kernel and with new kernel +minicm7
Ive been using the flashtool (tried on both ubuntu and windows xp) and that shows that the bootloader is unlocked OK, and will allow me to go install the new firmware.
Even though the phone freezes, I can still get in with flashtool to upgrade the kernel again - but that doesnt help.
I'm using PC companion to take the phone back to build 2.1.1.A.0.6 firmware 2.1-update1 with baseband ending 4015 after my attempts fail.
I've tried now with and without a sim (phone is sim locked o2 uk) with 16gb sd and 2gb sd but I'm getting the same result every time.
I must be doing something stupid, but I can't see what. I've exactly followed instructions here and elsewhere to no avail.
So suggestions?
Is there any way that I can monitor what is going on through the boot process?
Is there another kernel that I should try?
I'm going to grab my wifes X8 and try that tomorrow, but for now I'm off to bed.
thanks in advance for any help.
I'm kind of thinking you're trying to use the kernels with the stock rom, and that will never work.
You say you tried the new kernel with minicm7, but which kernel did you flash when you tried that? and did you wipe the data/factory reset, the cache and dalvik-cache after you installed the rom?
All these things can have an impact on what you're trying to achieve
If you use the nAa ICS Kernel, you need the MiniCM9 ROM.
If you use the MiniCM7 ROM, you need the nAa-Gingerbread kernel.
Hope i've helped, and if the answer isn't here, you may need to be a bit more specific in what combinations you've tried and maybe where you got the kernels and roms from.
Sleep well
Hi,
Maybe thats it? I updated the kernel to gingerbread first then used the built in boot manager toinstall miniCM7 from the sd card.
Kernels taken from here, downloaded several times - in case of corruption.
Should I have installed CM7 first? I assumed the kernel needed updating before installing the updated interface.
So I'll need to install CWM onto stock first, then use that to install CM7 then once happy that that is OK upgrade the kernel?
I'll try it that way this evening.
No, installing the kernel and then installing minicm7 is ok, no need to do that the other way around
But did you make sure you got both from them both from the proper forum?
GB kernel from Here
MiniCM7 from Here
Strange by me it also freeze as i flash the kernel first. I install always with CMW on stock kernel and flash the nAa kernel than.
Interestingly:
requirements for that kernel are : miniCM7
requirements for CM7: latest kernel
However - redownloaded from those link and it worked.
Which is good, but also bad because I didn;t do anything differently to get it to work.
Since I did download a couple of times before, all I can think of is that I've inadvertently downloaded from elsewhere.
Hmmm
maybe is the bad memory management but when it happend to me i hard rebooted the phone then pressed the back button to go to recovery and before kernel boots to recovery i realesed it.If this problem keep existing then flash kernel,when it sows the logo pull out the battery quickly and then boot again
Hi Everyone
I have been readind pages on this site for a while, I have a Xperia mini pro sk17i on UK O2 and I would like to remove the O2 and Sony bloatware along with the facebook rubbish. With a you tube guide I have made a back up of my existing rom using flash tool, I have tried it seems in vain to find a standard rom, the type you have on a unlocked phone from the UK, the mny guides are a bit confusing i have the4.0.2.A.0.62 build and understand I need to down grade first, I did try this a few weeks ago but my phones screen locked up completely luckily at the same time as i had used a foreign rom by mistake so I reflashed and pulled the plug part way through so a little triangle apperared and O2 repaired it and had to replace the screen it seems, that crapped me up a tad. So I thought I would get some advice this time. So im looking for the r4ight rom to flash with then root to remove the rubbish. Apologies if this has been brought up before but some of the liks I go to say the roms have been removed.
Thank you for any assistance you can provide.
Mark
P.S if my rom back is helpfull please let me know I can upload it or email it to you.
Check out my signature there's a step by step guide how to root and then Update to .62 again. Then you can uninstall Facebook etc
Sent from my SK17i using xda app-developers app
Hi
Thanks I flashed to the firmware and did the zerg bit but could not upgrade or remove anything also the radio did not work so i assume i need to flash with a baseband 64.
Thanks
Mark2260 said:
Hi
Thanks I flashed to the firmware and did the zerg bit but could not upgrade or remove anything also the radio did not work so i assume i need to flash with a baseband 64.
Thanks
Click to expand...
Click to collapse
Why weren't you able to update? Something wrong or just no notification for the update?
You can flash the update via flashtool, but for that you will have to use local-prop and push-root-files method as far as I know...
Yes flash the baseband you had before or the recommend for your provider/region. I don't even changed my baseband, so I don't know much about the baseband
Hi Again
Ok flashed again and then flashed to baseband 64, radio works interweb ok super user icon shows up still no update but i have no wifi at my home only hard wired. Now how do i get rid of the crap please?.
Thanks for your help so far.
Mark
update now shows but will have go round to my brothers as he uses wifi. just need to know how to getrid of useless rubbish now. o/
update 2 cannot update to 62 with wifi can i use somthing else?
Mark2260 said:
Hi Again
Ok flashed again and then flashed to baseband 64, radio works interweb ok super user icon shows up still no update but i have no wifi at my home only hard wired. Now how do i get rid of the crap please?.
Thanks for your help so far.
Mark
update now shows but will have go round to my brothers as he uses wifi. just need to know how to getrid of useless rubbish now. o/
update 2 cannot update to 62 with wifi can i use somthing else?
Click to expand...
Click to collapse
You have to use wifi, otherwise you could update to .69 firmware version. Download from here the 4.0.2.A.0.69 zip file to install via cwm.
Download x-parts from playstore and install cwm. Then do a backup and flash the zip via cwm. Do a factory reset, wipe cache
and davlik cache and you should have superuser installed and it should work
If you don't know how to use cwm, ask here and I will tell you exactly what to do!
Hi
Ok I went daft got bored and updated by sus, and now I am happy I have ICS everythingworks spot on apart from front camera option missing but thats no big deal, I disabled all the crap and it runs just as sooth as gb and i have more memory and ram left, pictures are just as good as before, I am very happy with this, I made a ftf file in case anyone wants it. This is on a uk phone on the giffgaff network.
Many thanks for your help.
Mark
I got a (sk17i / o2) 4.0.2.A.0.62 today and im also confused on how to get root, put on cwm & upgrade it beyond 2.3.4
DK71 said:
I got a (sk17i / o2) 4.0.2.A.0.62 today and im also confused on how to get root, put on cwm & upgrade it beyond 2.3.4
Click to expand...
Click to collapse
Check out my signature for a link to the rooting guide. There you should find out how to root it. It's an easy tutorial for newbies
Thanks Mihahn I will check out the guides.
Whats the best stable custom ROM for the mini pro ?
Im just waiting for my 7 days cooling off period to pass before I play
DK71 said:
Thanks Mihahn I will check out the guides.
Whats the best stable custom ROM for the mini pro ?
Im just waiting for my 7 days cooling off period to pass before I play
Click to expand...
Click to collapse
Best stable custom rom for locked bootloader? Don't know on gingerbread there aren't many custom roms and on ics there are only a few like real ics lite and MiniCMSandwich...
I'd stay on stock gingerbead rom, best rom for everything
I managed to root the phone but on each custom ROM I tried thats listed as suitable for locked bootloader (3 different ROMS)
I had a stuck black screen after the SE words after powering up.
DK71 said:
I managed to root the phone but on each custom ROM I tried thats listed as suitable for locked bootloader (3 different ROMS)
I had a stuck black screen after the SE words after powering up.
Click to expand...
Click to collapse
Did you wipe data/factory reset wipe cache and dalvik cache (and on some roms required format system) BEFORE you installed the zip file?
Yes I done the wipes & formats. All CWM installs gave me black screen no matter what options & roms I tried so I used flashtool & put on 4.0.4 after 4.0.2.A.0.69 just to get the phone functional & to try it out for speed & problems. Will have a crack another day when my hair loss grows back
DK71 said:
Yes I done the wipes & formats. All CWM installs gave me black screen no matter what options & roms I tried so I used flashtool & put on 4.0.4 after 4.0.2.A.0.69 just to get the phone functional & to try it out for speed & problems. Will have a crack another day when my hair loss grows back
Click to expand...
Click to collapse
When you want to install custom roms like real ics and similar ics roms for locked bootloader, flash them through cwm when you are on ics. If you have been on gingerbead before, it won't work, but if you are on ics, it should work
On 4.1.B.0431 I dont have root or CWM so I will no doubt get a headache when I next have a tinker around.
Im actually shocked I didnt turn it into a paper weight!
I have a Xperia U blocked bootloader rooted and with CWM installed.
I had an ICS .100 ROM installed and working perfectly but I decided I wanted to test Honami Experience ROM. As I had the terminal rooted I just downloaded the Honami Experience V2 ROM for blocked bootloader device, I copied the file to internal storage, I booted to CWM, I did a data/factory reset, wipe cache, wipe dalvik cache, and finally I installed the Honami_Experience_ST25i_v2_LB.zip from SD card.
After the installation finished I rebooted and as described in installation instructions it took some minutes to boot. After that the phone interface is working very smooth but I have lost many functionality: the sim card is not recognized, wifi is not working, cam not working, when I plug USB it is not recognized saying that the drivers can't be installed (in the windows device manager is shown as ST25i but with a warning under other devices), ... So basically the ROM is pretty smooth but useless this way. I'm not sure if I did something wrong though I think it is correct what I did. It is not important anyway just now.
So, my question is, what can I do to restore the mobile. I have already downloaded st25i_6.1.1.b.1.100 generic - user_sony.zip but the problem is that I don't find the way to put it now on the internal memory as the USB connection is not working. I have tried connecting the mass storage from CWM too but with same problem, windows can't install the drivers and in this case in the device manager shows it as Android instead of ST25i but with same warning.
As USB is not working I can't use flashtool to try to restore either.
I'm going to mention too that no matter if I disable the debug mode on the settings, it looks of on the user interface but when I reboot the phone it comes up with debug mode on always.
Any suggestions appreciated. My last solution would be to use bluetooth that seems it is working on the phone. The problem is just in this very moment I have another bluetooth device to send the data and that's why if possible I would like to know of any other way to solve this issue.
Thanks.
You should download file ftf and flash via flashboot mode
flash mode works
After reading another thread I have realized that flash mode works anyway so I have flashed the stock .100 and seems all is working now again.
So I change the question to, What have I did wrong when I installed Honami Experience ROM? I'm not sure what to do when the big Power Off button and Use Phone button appear on screen. I have waited a lot on that screen but maybe I did something wrong. What exactly I have to look at on that screen to be sure all is fine. When I flash the stock .100 I have no problems.
paulsm said:
After reading another thread I have realized that flash mode works anyway so I have flashed the stock .100 and seems all is working now again.
So I change the question to, What have I did wrong when I installed Honami Experience ROM? I'm not sure what to do when the big Power Off button and Use Phone button appear on screen. I have waited a lot on that screen but maybe I did something wrong. What exactly I have to look at on that screen to be sure all is fine. When I flash the stock .100 I have no problems.
Click to expand...
Click to collapse
I'm not sure, I also installed Honami v2 this morning but my phone is UB and it works normally. Have you followed the instructions in the topic, instructions for Lock Bootloader , your phone is ST25a or ST25i. you can do it again and report to the topic's owner
and power off and use phone button, it depends on you. if you are doing something, you can choose use to continue and turn off later
hungminhon said:
I'm not sure, I also installed Honami v2 this morning but my phone is UB and it works normally. Have you followed the instructions in the topic, instructions for Lock Bootloader , your phone is ST25a or ST25i. you can do it again and report to the topic's owner
and power off and use phone button, it depends on you. if you are doing something, you can choose use to continue and turn off later
Click to expand...
Click to collapse
The phone is ST25i locked bootloader. And on the moment I did the test was rooted, it had stock .100 firmware and CWM Touch 5.5.0.4. Taking that into account I just uploaded the Honami v2 zip file (for locked bootloader), I booted into recovery, wiped everything, I installed the zip from SD and rebooted when installation finished.
The only thing I can't be sure if it is wrong to start from .100 firmware (kernel included). Don't know if that is wrong and I must start with .10 kernel.
Now I have it again with .100 firmware, rooted and with CWM Touch 5.5.0.4 so maybe I can just flash .10 kernel and try again the installation of Honami from CWM.
paulsm said:
The phone is ST25i locked bootloader. And on the moment I did the test was rooted, it had stock .100 firmware and CWM Touch 5.5.0.4. Taking that into account I just uploaded the Honami v2 zip file (for locked bootloader), I booted into recovery, wiped everything, I installed the zip from SD and rebooted when installation finished.
The only thing I can't be sure if it is wrong to start from .100 firmware (kernel included). Don't know if that is wrong and I must start with .10 kernel.
Now I have it again with .100 firmware, rooted and with CWM Touch 5.5.0.4 so maybe I can just flash .10 kernel and try again the installation of Honami from CWM.
Click to expand...
Click to collapse
i think you should follow the instructions, flash the .10 kernel first. In UB, I also have to install another kernel to install this rom
hungminhon said:
i think you should follow the instructions, flash the .10 kernel first. In UB, I also have to install another kernel to install this rom
Click to expand...
Click to collapse
I tried and no way even with .10 kernel same exactly problems, no cam, no wifi, no sim recognized, ... Not sure if I'm going to try anymore. Really the stock .100 is smooth enough.
one more test
I tested once more. Just reread the instructions very very carefully.
- The instructions say that you have to start with 6.1.1.B.1.100 so I was doing it correctly from the beggining.
- The instructions say to root with superuser while I was rooting with supersu so in this last test, though I supposed it was not the problem, I decided to use superuser.
Again, same problems, no wifi, no cam, no sim recognized, ..., so I only can imply that Honami Experience doesn't work on locked bootloader.
If someone has tested too and read this and it is working for him in locked bootloader I would be glad to hear how he did it.
I can't ask for help nor notify it in the developer thread because of the limits imposed by xda-developers forums.
Thanks
Glad I saw this post...
I have a locked bootloader as well, and have been wanting to try various ROMS.
Was thinking about trying this one on the weekend, but now I'm not sure.
Currently using JB eXperience V2, it works well and everything works, but I'm always looking for something new to try.
I'm not savvy enough to fix problems, so would rather flash ROMS with few "bugs"
Sorry I know I didn't answer your question, but it certainly answers mine of if I should flash this ROM or not.
I certainly give credit to all the devs on here though, don;t get me wrong! They work hard!
need to re-flash the 6.1.1.B.1.100 firmware or not?
I wanna try it but have some questions.
Now I am currently on zperience 1.0. Can I install this rom on over it or sould re-Flash the 6.1.1.B.1.100 firmware.
smtsth said:
I wanna try it but have some questions.
Now I am currently on zperience 1.0. Can I install this rom on over it or sould re-Flash the 6.1.1.B.1.100 firmware.
Click to expand...
Click to collapse
The instructions say you have to start with 6.1.1.B.1.100 firmware
Always Flash the 6.1.1.B.1.100 firmware before flashing this ROM, then follow instructions
Click to expand...
Click to collapse
Same problems on LB
I have LB and i had the same problems with this rom, the wifi didn't work, the screen didn´t turn off. In fact, the same problems. The owner of the roms told me that they are bugs of the rom, i think he will fix it in the v3. As i see it works perfectly on UB, but i'm not going to unlock the bootloader.
incry2 said:
I have LB and i had the same problems with this rom, the wifi didn't work, the screen didn´t turn off. In fact, the same problems. The owner of the roms told me that they are bugs of the rom, i think he will fix it in the v3. As i see it works perfectly on UB, but i'm not going to unlock the bootloader.
Click to expand...
Click to collapse
Thanks for the info. In my opinion if the owner of the rom knows about all those bugs he should include the info on the rom thread.
The rom thread shows a list of bugs and if those bugs are only the bugs of the unlocked bootloader version he should have explained better.
When I decided to try I thought it was a full operative rom with just the few bugs that we can read on the thread. But wifi not working, sim not detected, screen not turning off, lock screen not working properly, cam not working, ..., are bugs that can't be ignored. With those bugs, even with only one of those, because all of them are imprescindible features, the rom is useless.
same problem
paulsm said:
The phone is ST25i locked bootloader. And on the moment I did the test was rooted, it had stock .100 firmware and CWM Touch 5.5.0.4. Taking that into account I just uploaded the Honami v2 zip file (for locked bootloader), I booted into recovery, wiped everything, I installed the zip from SD and rebooted when installation finished.
The only thing I can't be sure if it is wrong to start from .100 firmware (kernel included). Don't know if that is wrong and I must start with .10 kernel.
Now I have it again with .100 firmware, rooted and with CWM Touch 5.5.0.4 so maybe I can just flash .10 kernel and try again the installation of Honami from CWM.
Click to expand...
Click to collapse
incry2 said:
I have LB and i had the same problems with this rom, the wifi didn't work, the screen didn´t turn off. In fact, the same problems. The owner of the roms told me that they are bugs of the rom, i think he will fix it in the v3. As i see it works perfectly on UB, but i'm not going to unlock the bootloader.
Click to expand...
Click to collapse
same problem here. I Just tried 2 times but the problem is same... so waiting for v3