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
Related
I tried searching to install custom kernel , i couldnt find one.
1.) should i have to install/flash the custom kernel while i am at V5s and then flash V5c over it ? or how to proceed ?
2.) anyone on ULBL + custom kernel and find any significant or notable performance increase / stability ?
3.)Also can someone tell me how to remove "GET GAMES" , "EXTENSION SEARCH" & "MEDIA SERVER"(If possible) .
4.) Also is there a way to freeze "setup guide"
I am on WB V5s ROM now .
any one ?
/10char
1) You can flash a custom kernel now, you don't need to flash v5.0c first
2) I get pretty good battery life with Freekernel and I suppose overclock would mean faster performance, but I don't personally use high frequencies.
3) Use Titanium Backup
4) I think Titanium Backup Pro would be able to
Thanks a lot first for replying.
1.)select a custom kernel ftf file and flash while in V5s ? and then flash a V5c after ?
do i need to check for signal / radio working after flashing a custom kernel or any other kind of procedure ? I tried searching but there is no proper installation instruction given . thats i posted here.
2.) to ULBL , do i have to be in any specific kernel ? mine is not network locked. also ULBL will prevent me from using SEUS for further updates ? or incase if something goes wrong , SEUS is the final hope to flash to a stock GB and get back to WB or any custom ROM`s now.
3,4.) Will Do with TB . I wanted to know freezing them wont affect the phone working right ? particularly "setup guide"
Again thanks for the reply
Before anything else, is your sim unlocked? If you used anything other than SEtool2 to unlock your sim, I don't think there is a method to unlock your bootloader yet. This link describes the steps and requirements. Follow those steps and you'll only need to downgrade your kernel to unlock bootloader. Then you can upgrade back to GB kernel.
Now if you can unlock bootloader, I assume you're tying to flash DoomKernel 5.0. Flashing custom kernel ftf file requires unlocked bootloader. If you've already unlocked, you can just flash that ftf. You don't need to mess with WB v5.0c at all. The only difference between WB's roms is that 5.0c already has DoomKernel 4.0b. Doom also provides wifi modules that you can flash via Xrecovery for working wifi.
If you have any problems, there's a tool to relock your bootloader.
I don't think freezing setup guide will affect anything, but I am not sure.
Ogbert_theNerd said:
Before anything else, is your sim unlocked? If you used anything other than SEtool2 to unlock your sim, I don't think there is a method to unlock your bootloader yet. This link describes the steps and requirements. Follow those steps and you'll only need to downgrade your kernel to unlock bootloader. Then you can upgrade back to GB kernel.
Now if you can unlock bootloader, I assume you're tying to flash DoomKernel 5.0. Flashing custom kernel ftf file requires unlocked bootloader. If you've already unlocked, you can just flash that ftf. You don't need to mess with WB v5.0c at all. The only difference between WB's roms is that 5.0c already has DoomKernel 4.0b. Doom also provides wifi modules that you can flash via Xrecovery for working wifi.
If you have any problems, there's a tool to relock your bootloader.
I don't think freezing setup guide will affect anything, but I am not sure.
Click to expand...
Click to collapse
really thanks for the reply.
I ran s1 tool and got the following
RUNNING S1_EROM VER "R8A013"
SOFTWARE AID: 0001
LOADER AID: 0001
FLASH ID: "002C/00B3"
LOADER VERSION: "R4A024"
MODEL (from GDFS): X10i
SOFTWARE VERSION: 1227-4612_3.0.1.G.0.75
CUSTOM VERSION: 1241-1846_R1C
FILESYSTEM VERSION: WORLD-1-4-8_3.0.1.G.0.75
SERIAL NO: CXXXXXX8
SEMC SIMLOCK CERTIFICATE
Elapsed:26 secs.
Click to expand...
Click to collapse
i think mine is not simlocked right ?
i will wait for ULBL for sometime .
can you tell me how to proceed to get custom kernel , either Doom`s or zKernel currently from WB V5 s . always WB used to say to boot and get the signal and then proceed to next step in some cases .
what exactly is the procedure to get a custom kernel on a WB V5 s.
Thanks for helping me out.
If you're not going to mess with unlocked bootloader, it makes things a lot easier. You can just install a custom kernel through Xrecovery or just flash WB v5.0c over your v5.0s.
Ogbert_theNerd said:
If you're not going to mess with unlocked bootloader, it makes things a lot easier. You can just install a custom kernel through Xrecovery or just flash WB v5.0c over your v5.0s.
Click to expand...
Click to collapse
actually last time i flashed V5c over 4.04 and ended up with bootscreenlock up.
thats why i wanted to know the exact procedure. when i flashed the wrong ROM over stock kernel last time , volpad told me to clear dalvik cache and reboot so that it will work , he too said V5c has its own Doom`s kernel , but it didnt work for me. I ended up using SEUS to get into Stock GB and get back to WB V5s now.
Then your phone could just be incompatible with Doomkernel. The same thing happened to me actually. I installed v5.0c over v4.0.4c and ended up in a lock up. I took the battery out, put it back in, started up the phone again, spammed back button to get into Xrecovery and installed Goro's kernel. My phone then booted up normally. Since, you're on v5.0s, just install a kernel that's not Doomkernel through Xrecovery.
Ogbert_theNerd said:
Then your phone could just be incompatible with Doomkernel. The same thing happened to me actually. I installed v5.0c over v4.0.4c and ended up in a lock up. I took the battery out, put it back in, started up the phone again, spammed back button to get into Xrecovery and installed Goro's kernel. My phone then booted up normally. Since, you're on v5.0s, just install a kernel that's not Doomkernel through Xrecovery.
Click to expand...
Click to collapse
well i didnt install V5c over V4c . I did a flash of V5c over V4s .
sorry for askingagain n again , since i am not quite clear.
V5s doesnt support custom kernel right ?
so if i flash a custom kernel then V5s wont be compatible right ? then i have to flash V5c over the flashed custom kernel right ?
also do i need to to boot in to see if signal/radio works and get back to flashing other things , procedure like that ? ?
None of that matters. Think of it this way, v5.0c is just v5.0s that already has Doomkernel installed. If you flash Doomkernel onto a v5.0s, then you effectively have v5.0c; however, since Doomkernel causes your phone to lock up, you'll have to choose another kernel. Here's Goro's kernel, which I have had luck with. Doomkernel FS series should also work, but it doesn't have OC/UV.
So try this:
1) flash WB v5.0s (which you already have, correct?)
2) reboot and check for signal, if you are concerned
3) reboot into Xrecovery and make a back-up, if you want
4) now flash whichever kernel you choose
5) reboot, of course if it everything boots up then you're good to go
Ogbert_theNerd said:
None of that matters. Think of it this way, v5.0c is just v5.0s that already has Doomkernel installed. If you flash Doomkernel onto a v5.0s, then you effectively have v5.0c; however, since Doomkernel causes your phone to lock up, you'll have to choose another kernel. Here's Goro's kernel, which I have had luck with. Doomkernel FS series should also work, but it doesn't have OC/UV.
So try this:
1) flash WB v5.0s (which you already have, correct?)
2) reboot and check for signal, if you are concerned
3) reboot into Xrecovery and make a back-up, if you want
4) now flash whichever kernel you choose
5) reboot, of course if it everything boots up then you're good to go
Click to expand...
Click to collapse
Really thanks a lot ...
I think your reply here will serve as "HOW-TO" for many who seek how to install Custom Kernel and ROM.
yes i am on WB V5s now
one last question . After custom kernel (i will go with Goroh`s Kernel itself) installation , and after rebooting , should i have to flash V5c ?
No, do not flash v5.0c. That would overwrite everything and you'll get locked boot screens again.
Ogbert_theNerd said:
No, do not flash v5.0c. That would overwrite everything and you'll get locked boot screens again.
Click to expand...
Click to collapse
thanks for clearing the doubt. so if WB updates his ROM , which version should i choose next time ? s or c ROM ?
S-version should always be safe, but you would have to reflash a custom kernel afterwards. C-version may or may not be okay. Depends on what custom kernel Wolfbreak decides to go with in the future or if Doom adjusts his kernel. During bootup, Doomkernel briefly peaks at 1.228Ghz, which causes some devices to freeze or lock up. If you're unsure, you should go with S-version.
Ogbert_theNerd said:
S-version should always be safe, but you would have to reflash a custom kernel afterwards. C-version may or may not be okay. Depends on what custom kernel Wolfbreak decides to go with in the future or if Doom adjusts his kernel. During bootup, Doomkernel briefly peaks at 1.228Ghz, which causes some devices to freeze or lock up. If you're unsure, you should go with S-version.
Click to expand...
Click to collapse
thanks a lot. this might be normal , but last time Custom kernel in V5c ran few codes art boot-up and after that the lock-up occured , might be the problem you are saying here , peak of frequency.
thanks a lot for taking time and replying for each question.
will flash a custom kernel and report back with PM to you.
again , really thanks for all the help.
I've been having a look at trying a few custom roms on the Neo V and some say to install a different baseband. Some of the links aren't clear what I should be using. Is the baseband for the Neo the same as the Neo V?
I'm guessing that if I flash 4.0.2.A.0.62 then I'll get baseband 64, but I'm looking to see if I can flash just that baseband without the whole stock rom.
Yes you can! i have neo V .42 but having .283 kernel .62 baseband of neo! works perfectl!
I did this tonight and have had quite a few problems. Nothing wrong with the advice, I had other issues. While trying to resolve them I found my own thread, so thought I'd add some more info.
The baseband flash went fine until a point where it rebooted, then said it was connected with debugging off, even though I'd switched it off. It also said to make sure 2011 devices weren't in MTP mode.
At this point, I found another thread that said to flash the rom anyway, so I booted into fastboot mode & flashed a kernel. After that I booted to CWM and tried to flash CM7. I got an error that included getprop and I found the same error in the CM7 for Neo V thread. The solution was a new scripts-update file, but I already had it.
I edited the updater-script to run getprop, so I could see what it was returning and got an error to say getprop wasn't found.
At that point, I decided to flash the complete 4.0.2.A.0.62 rom, which went fine, though Flashtool did tell me I needed to install some included drivers at one point.
From there I followed the instructions on here to root 62 by flashing some of 42, though I did it slightly differently and ticked to exclude the baseband as that was the whole point of this.
After that I was able to install CWM again. I then booted into fastboot again & installed a different kernel. Booted into recovery & flashed CM7 + the Neo V fixes.
All good.
So if you get stuck in boot loops, weird things happen, don't panic. Use the search and you'll get there in the end.
Celtic67 said:
I did this tonight and have had quite a few problems. Nothing wrong with the advice, I had other issues. While trying to resolve them I found my own thread, so thought I'd add some more info.
The baseband flash went fine until a point where it rebooted, then said it was connected with debugging off, even though I'd switched it off. It also said to make sure 2011 devices weren't in MTP mode.
At this point, I found another thread that said to flash the rom anyway, so I booted into fastboot mode & flashed a kernel. After that I booted to CWM and tried to flash CM7. I got an error that included getprop and I found the same error in the CM7 for Neo V thread. The solution was a new scripts-update file, but I already had it.
I edited the updater-script to run getprop, so I could see what it was returning and got an error to say getprop wasn't found.
At that point, I decided to flash the complete 4.0.2.A.0.62 rom, which went fine, though Flashtool did tell me I needed to install some included drivers at one point.
From there I followed the instructions on here to root 62 by flashing some of 42, though I did it slightly differently and ticked to exclude the baseband as that was the whole point of this.
After that I was able to install CWM again. I then booted into fastboot again & installed a different kernel. Booted into recovery & flashed CM7 + the Neo V fixes.
All good.
So if you get stuck in boot loops, weird things happen, don't panic. Use the search and you'll get there in the end.
Click to expand...
Click to collapse
Rightly said my friend!
Well I was wondering the same thing- Can you flash basebands from 62 on 283? This thread has given me some answers.
I have some other questions though. I am a noob running stock neo v .283 firmware with unlocked bootloader(testpoint method) and CWM(the one for stock roms) installed. I want to flash the CM9 by FXP tonight. I have made a backup through CWM so that I can revert back in case something goes wrong.
Now the CM9 installation process involves flashing different kernel+baseband. If at some point I want to restore my previous CWM backup(taken on .283 stock rom), then what should be the procedure I should follow? For example, do I need to flash stock .283 .ftf+kernel again before I restore my backup through CWM?
I had a good search & didn't find a great deal about basebands. It would be useful to have something in the Neo section.
Flashing the stock ftf should include the kernel, I believe. You should be back at the same baseband & kernel and just need to install CWM again and restore your backup. I'd do the usual wipe everything in CWM before restoring, though.
Having said that, You've made me realise that I didn't note which firmware I was on before doing mine. So even though I took a CWM backup, I've no idea which stock to flash. Ah well, I wasn't planning on going back.
I later decided that the .283 firmware is simply too old and not supported by kernel/ROM developers anymore; besides flashing the entire stock .283 every single time just for restoring a backup seems too big a hassle. So I relocked my bootloader, updated to stock .62 firmware through PC companion, unlocked bootloader again, and then flashed a custom .62 kernel with recovery. After that I made my backup through CWM and installed CM9 afterwards. This way, all I will have to do for restoring my original backup is flashing the same custom .62 kernel. no ftf flashing involved.
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!
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
Here's the story in short,
I bought a new LGOG a week ago.
Rooted it.
Running on stock 4.1.2 Jellybean , AT&T(unlocked for use with any operator).
Now , today I installed freegee and updated it. Took a backup of my EFS , and copied it in my external MMC.
Apart from that also attached the freegee with my dropbox account.
Now , I tried to install CWM recovery , but it seems that there was some sort of problem with download of CWM , as it was taking eternity. I waited for few minutes but then I rebooted the phone.
The phone actually didn't booted up fine. It's now stuck at LG logo , followed by a Google logo afterwards at the beginning with padlock symbol.
The logo stays there for a second and then the phone shuts down.
I panicked when I saw this , realizing that this may be a hard brick. Now I tried combination of volume keys , and it seems that it brought up a menu on the screen , with couple of options and information.
The options available are :
Start-
PowerOff-
Recovery Mode-
Restart boot loader-
The info available below are :
Fastboot mode
product_name : mako
variant -mako 16gb
hw version : rev_10 (88)
bootloader version : makoz10f
baseband version : n/a
carrier info : none.
serial number : 05959*******98de7**
signing- production
secure boot- enabled
lock state - unlocked
When I select reboot recovery , it reboots and then same as stated above. Seems as if the recovery is either not installed properly or is not working.
I was wondering that whether this is a complete brick or is there any chances of this being fixed ??
PS There's no warranty , it's an imported set from USA . SO cant avail it here .
A help would be really appreciated , willing to donate few bucks , if things work.
http://forum.xda-developers.com/showthread.php?t=2230994
Read carefully before attempting to use it.
You can also read this thread, I just helped another person: http://forum.xda-developers.com/showthread.php?t=2556006
Let me know if you have questions.
aedren said:
You can also read this thread, I just helped another person: http://forum.xda-developers.com/showthread.php?t=2556006
Let me know if you have questions.
Click to expand...
Click to collapse
Thanks for your immediate reply Guys. That sounds really helpful.
It seems zombiegeek was able to fix the phone , and seems mine phone is in similar state.
I am going to go through the LGPNST and will see if that works. Searching for the tutorial thread on it.
optimusv45 said:
http://forum.xda-developers.com/showthread.php?t=2230994
Read carefully before attempting to use it.
Click to expand...
Click to collapse
I am going to go through it. Thanks for sharing.
EDIT : Successfully booted into Download mode By holding both the volume keys ( when device was completely switched off) and then plugging it into the PC using data cable.
It went straight to download mode.
Started LGNPST. Made sure that it detected my device. Registered LS970.dll file use rgsvr32.
Selected the DLL and BIN , and it went to 67% progress after start .
Rebooted , and went into boot loop.
I tried the same procedure again , but this tie with ATLBin instead of original Bin.
It rebooted and went into TWRP mode.
Finally a sigh of relief , as It booted into recovery.
Followed the steps as mentioned in the thread above. It worked!!
--------------
Haven't installed any ROMS yet.
optimusv45 said:
http://forum.xda-developers.com/showthread.php?t=2230994
Read carefully before attempting to use it.
Click to expand...
Click to collapse
same thing happened to my phone. Use freeGee to unlock and download cwm
but cwm download failed and have the same google logo and options.
just do the lgnst to stock.
Now I root my phone again. and not sure what should I do next.
so should I use the E970 Original TeenyBin to unlock bootloader and install cwm?
thanks
laofan said:
same thing happened to my phone. Use freeGee to unlock and download cwm
but cwm download failed and have the same google logo and options.
just do the lgnst to stock.
Now I root my phone again. and not sure what should I do next.
so should I use the E970 Original TeenyBin to unlock bootloader and install cwm?
thanks
Click to expand...
Click to collapse
Try the original teenybin, I think it includes twrp recovery. Don't worry about cwm. After flashing the bin boot into recovery and flash a rom. Again read the teenybin thread carefully and make sure you understand first.
PS. Original bin didn't work for me I had to use the other one. So if the same happens don't freak out.
optimusv45 said:
Try the original teenybin, I think it includes twrp recovery. Don't worry about cwm. After flashing the bin boot into recovery and flash a rom. Again read the teenybin thread carefully and make sure you understand first.
PS. Original bin didn't work for me I had to use the other one. So if the same happens don't freak out.
Click to expand...
Click to collapse
Yeah , I also want to stay away from CWM as long as TWRP is there.
What I am confused about is that if we flash the original JB bins from AT&T , will it leave the bootloader unlocked with TWRP recovery ??
All I need is Stock JB , with unlocked bootloader and TWRP recovery.
You said that original bins , didn't worked . DId you mean you used the ALTBin or something else ?
Rishi. said:
Yeah , I also want to stay away from CWM as long as TWRP is there.
What I am confused about is that if we flash the original JB bins from AT&T , will it leave the bootloader unlocked with TWRP recovery ??
All I need is Stock JB , with unlocked bootloader and TWRP recovery.
You said that original bins , didn't worked . DId you mean you used the ALTBin or something else ?
Click to expand...
Click to collapse
Yes, your bootloader will be unlocked and you will have twrp. Teenybin will not give you a working rom, it updates your phone to the newest software and give you a recovery. I think there is a bin that will recovery your phone to stock jb, you will have to look for it on the teenybin thread. Btw stock jb battery life is quite bad and there are quite a few stable 4.3 roms to choose from. Yes, I used altbin but that's just my phone. Original bin may work for you.
@Rishi.
here is the bin I use to go back to stock using LGNPST
http://forum.xda-developers.com/showthread.php?t=2219953
optimusv45 said:
Yes, your bootloader will be unlocked and you will have twrp. Teenybin will not give you a working rom, it updates your phone to the newest software and give you a recovery. I think there is a bin that will recovery your phone to stock jb, you will have to look for it on the teenybin thread. Btw stock jb battery life is quite bad and there are quite a few stable 4.3 roms to choose from. Yes, I used altbin but that's just my phone. Original bin may work for you.
Click to expand...
Click to collapse
Actually original TeenyBin , didn't worked in my case either.I had to flash the ALternative bins to make the TWRP work.It went into bootloop with original teeny bin , alt one worked though.
Good that the recovery is working now.
As you mentioned that the battery on stock Jb is bad , so I am going to leave that. But Can you confirm any 4.3/4.1 stable rom that has no issues whatsoever. ??
Rishi. said:
Actually original TeenyBin , didn't worked in my case either.I had to flash the ALternative bins to make the TWRP work.It went into bootloop with original teeny bin , alt one worked though.
Good that the recovery is working now.
As you mentioned that the battery on stock Jb is bad , so I am going to leave that. But Can you confirm any 4.3/4.1 stable rom that has no issues whatsoever. ??
Click to expand...
Click to collapse
The issues I encounter is insignificant comparing to how much benefit I gain. I run houstonns PA 3.99 RC 2 Adreno build . battery a lot better, less heat, deep sleep great, always wake up, fast and smooth, theme enabled too. Link for it http://forum.xda-developers.com/showthread.php?t=2228880 cm10.2 stable is also out. Bear in mind no one is gonna promise you you won't run into some issues and the stock rom isn't trouble-free either. If you are worried then you can just stick with stock for now. I honestly do like the stock rom, I think it looks great. Maybe eventually your curiosity will drive you to try custom roms.
PS: you can get stock running, make a backup, and then try some roms. Also now you know you have teenybins on your side, you should feel quite safe trying roms. Go with big name first , houstonns work is very good.
optimusv45 said:
The issues I encounter is insignificant comparing to how much benefit I gain. I run houstonns PA 3.99 RC 2 Adreno build . battery a lot better, less heat, deep sleep great, always wake up, fast and smooth, theme enabled too. Link for it http://forum.xda-developers.com/showthread.php?t=2228880 cm10.2 stable is also out. Bear in mind no one is gonna promise you you won't run into some issues and the stock rom isn't trouble-free either. If you are worried then you can just stick with stock for now. I honestly do like the stock rom, I think it looks great. Maybe eventually your curiosity will drive you to try custom roms.
PS: you can get stock running, make a backup, and then try some roms. Also now you know you have teenybins on your side, you should feel quite safe trying roms. Go with big name first , houstonns work is very good.
Click to expand...
Click to collapse
I have had experiences with lots of custom roms , MROm , Beanstalk , MIUI , CM7 , CM10 , etc, when I was an Atrix 4g user. The Roms have excellent performance difference . MIUI was best though as it had the appeal in terms of layout.
Anyways , unless I don't try one on LGOG , I am sure I won't be able to tell the difference.
BTW , I am going to try the Official Cyanogen 10.2 first.
If you flash the 11c or 20j bin you will be back to locked bootloader and no recovery. That is why I linked to flashable zip for 20j, it should work with twrp. Sorry for not being able to reply sooner.
Rishi. said:
I have had experiences with lots of custom roms , MROm , Beanstalk , MIUI , CM7 , CM10 , etc, when I was an Atrix 4g user. The Roms have excellent performance difference . MIUI was best though as it had the appeal in terms of layout.
Anyways , unless I don't try one on LGOG , I am sure I won't be able to tell the difference.
BTW , I am going to try the Official Cyanogen 10.2 first.
Click to expand...
Click to collapse
People are reporting issue with turning off NFC. They recommend either rebooting right away after booting into the rom or flash the rom again, So keep these in mind.
optimusv45 said:
People are reporting issue with turning off NFC. They recommend either rebooting right away after booting into the rom or flash the rom again, So keep these in mind.
Click to expand...
Click to collapse
installed cm10.2 , working good . seems stable with no issues , at least none with nfc yet.
will take a backup of this and will flash the stock bin with twrp.
adfurgerson said:
If you flash the 11c or 20j bin you will be back to locked bootloader and no recovery. That is why I linked to flashable zip for 20j, it should work with twrp. Sorry for not being able to reply sooner.
Click to expand...
Click to collapse
Thanks. It seems the Flashable zip you posted is better to use , since I went through the Flashable bins(.tot) thread and realized that rooting it back after LGNPSTing was kinda of doubtful.
Have taken CM10.2 backup. Will flash the TWRP/CWM flashable stock.
hi I am having trouble registering my dll files is there anyone that can help me?
nicklefloss said:
hi I am having trouble registering my dll files is there anyone that can help me?
Click to expand...
Click to collapse
Registering ?