When USB plugin my Neo, screen goes on and if I wait 5 seconds then I can start it. But if I press and hold the Back key or the Menu key and plugin USB it doesn't go to flashmode or fastboot mode. I am not sure how it got the 0% battery problem but I can't get it to accept new kernels so I can resolve the issue.
I see they most phones go to flashmode and then is simply to write new kernel's and resolve the problem.
Please help someone if you know how I can write new kernels.
PS. Back and Menu key are working fine when using the phone.
Sent from my MT11i using Tapatalk 2
ciuc007 said:
When USB plugin my Neo, screen goes on and if I wait 5 seconds then I can start it. But if I press and hold the Back key or the Menu key and plugin USB it doesn't go to flashmode or fastboot mode. I am not sure how it got the 0% battery problem but I can't get it to accept new kernels so I can resolve the issue.
I see they most phones go to flashmode and then is simply to write new kernel's and resolve the problem.
Please help someone if you know how I can write new kernels.
PS. Back and Menu key are working fine when using the phone.
Sent from my MT11i using Tapatalk 2
Click to expand...
Click to collapse
1. Kernels are flashed in fastboot mode not flashmode.
2. Have you unlocked your bootloader?
3. Which version of recovery have you installed.
4. Which ROM/kernel are you running now?
gregbradley said:
1. Kernels are flashed in fastboot mode not flashmode.
2. Have you unlocked your bootloader?
3. Which version of recovery have you installed.
4. Which ROM/kernel are you running now?
Click to expand...
Click to collapse
THX for answer:
1-Phone doesn't go on fastboot mode
2-I dont't know but in Service info/Configuration/Rooting status: Bootloader Unlock Allowed: YES (Where can i see if the bootloaders are unlocked?)
3-No recovery installed
4: Kernel: 2.6.32.9-perf [email protected]#1 - 4.1.B.0.431 - StockRom
I have also one Neo V that i unlocked the bootloaders myself and instaled FXP CM9.1
ciuc007 said:
THX for answer:
1-Phone doesn't go on fastboot mode
2-I dont't know but in Service info/Configuration/Rooting status: Bootloader Unlock Allowed: YES (Where can i see if the bootloaders are unlocked?)
3-No recovery installed
4: Kernel: 2.6.32.9-perf [email protected]#1 - 4.1.B.0.431 - StockRom
I have also one Neo V that i unlocked the bootloaders myself and instaled FXP CM9.1
Click to expand...
Click to collapse
2. If your bootloader is unlocked you would know about it becuase you have to do it yourself.
3 and 4. You have not rooted your phone yet. I suggest you read the sticky threads in order to find out how to.
1. root phone.
2. install recovery
3. unlock bootloader (Optional, but necassary if you want to flash kernels)
4 Flash custom roms (And kernels)
First place to look is in the the very first thread in the dev section. Download flashtool and start reading the threads.
I flashed NightElf Kernel mod for ICS Beta - that suport 0% Baterry workaround and now I have a working phone again. (without ned to be pluged in all the time)
Now I can't root my device. I tried from flashtool alt 3 options: force psneuter, force zergrush and force emulator. Also tried DoomLord's solution. Noting worked for me:
09/019/2012 20:19:50 - INFO - Device connected with USB debugging on
09/019/2012 20:19:51 - INFO - Connected device : MT15
09/019/2012 20:19:51 - INFO - Installed version of busybox : N/A
09/019/2012 20:19:51 - INFO - Android version : 4.0.4 / kernel version : 2.6.32.9-v1_587
09/019/2012 20:19:58 - INFO - Pushing C:\Flashtool\.\devices\MT15\busybox\1.19.0\busybox to /data/local/tmp/busybox
09/019/2012 20:19:58 - INFO - Pushing C:\Flashtool\.\custom\root\zergrush.tar.uue to /data/local/tmp
09/019/2012 20:19:59 - INFO - Running part1 of Root Exploit, please wait
09/020/2012 20:20:01 - INFO - Waiting for device
09/020/2012 20:20:25 - ERROR - The part1 exploit did not work
09/020/2012 20:20:35 - INFO - Pushing C:\Flashtool\.\devices\MT15\busybox\1.19.0\busybox to /data/local/tmp/busybox
09/020/2012 20:20:36 - INFO - Pushing C:\Flashtool\.\custom\root\psneuter.tar.uue to /data/local/tmp
09/020/2012 20:20:36 - INFO - Running part1 of Root Exploit, please wait
09/020/2012 20:20:37 - INFO - Running rootit
09/020/2012 20:20:38 - INFO - Waiting for device
09/021/2012 20:21:38 - INFO - Forced stop waiting.
09/021/2012 20:21:39 - ERROR - The part1 exploit did not work
Any sugestions please?
If you flashed that kernel then you are rooted.
The kernel comes pre rooted.
Try entering recovery mode.
Reboot phone and press back key when you see the sony logo
I entered in recovery mode.
From here i think i will manage to install Custom Rom.
Thanks.
ciuc007 said:
I entered in recovery mode.
From here i think i will manage to install Custom Rom.
Thanks.
Click to expand...
Click to collapse
No need to say thanks, there is a button for that if you feel the need to thanks anyone. Also, if you need anymore help you can PM me.
Good luck
gregbradley said:
No need to say thanks, there is a button for that if you feel the need to thanks anyone. Also, if you need anymore help you can PM me.
Good luck
Click to expand...
Click to collapse
I have installed ICS Pureness on my Neo but i am still unable to ROOT. When opening SuperSU it ask me to update SU and than i get Installation failed.
i have Android 4.0.4, BB 72, Night-elf kenel - 2.6.32.9-v1_587, [email protected]_pureness_13.0
I have tried DoomLord V3 - ZergRush and Flashtool.
Flash tool said "You are already rooted" - but applications that require root access give me error.
(in my NeoV the pureness is rooted ok because i can run applications that require root)
Any ideas?
ciuc007 said:
I have installed ICS Pureness on my Neo but i am still unable to ROOT. When opening SuperSU it ask me to update SU and than i get Installation failed.
i have Android 4.0.4, BB 72, Night-elf kenel - 2.6.32.9-v1_587, [email protected]_pureness_13.0
I have tried DoomLord V3 - ZergRush and Flashtool.
Flash tool said "You are already rooted" - but applications that require root access give me error.
(in my NeoV the pureness is rooted ok because i can run applications that require root)
Any ideas?
Click to expand...
Click to collapse
The solution is in the pureness rom thread. Try the search button in that thread next time.
Solution.
Install superuser from play store.
Run it and click home button when you see the splash screen.
Then open supersu again, allow root rights, update su binary.
Then uninstall superuser app that you just downloaded
Related
I bought an x10 from a friend today and now I was trying to unlock the bootloader using this link: http://forum.xda-developers.com/showthread.php?t=1254087 however after the batch file finished it got stuck on the SE logo. After waiting a while I decided to just go back to 2.1.
I downloaded X10a_1.0_2_1_A_0_435 and tried to use flashtool to flash it but here is the log:
30/011/2011 18:11:51 - INFO - Searching Xperia....
30/011/2011 18:11:51 - INFO - Found at USB\VID_0FCE&PID_ADDE\5&10EF021E&0&6
30/011/2011 18:11:51 - INFO - Start Flashing
30/011/2011 18:11:51 - INFO - VER="r8A033";DATE="20100928";TIME="12:04:00";
30/014/2011 18:14:02 - INFO - Flashing loader
30/014/2011 18:14:02 - ERROR - Error flashing. Aborted
Click to expand...
Click to collapse
Any ideas how I can revive my phone? I have the PC companion but when I go to phone update -> repair phone, it keeps giving an installation error.
Edit: I forgot to add that I can still get into xrecovery.
were you at 2.3 when you tried to unlock the bootloader??
Yeah, my friend had some sony ericisson 2.3.3 custom rom on. (Wolf something?)
you were supposed to switch back to 2.1 before attempting to unlock the bootloader.
That thread says that it can be unlocked from any rom.
However I don't know what went wrong.
oh sorry about that you needed to downgrade your kernel. did you check if your phone was eligible with the tool provided in the thread. if it says your phone is able to goback to the flashtool and downgrade your kernel and retry unlocking your bootloader. dont do it though if your phone is not elible for the unlocked bootloader.
Yeah I ran the tool and it said my phone was SEMC simlocked or something similar. So I first downgraded, ran the batch to unlock then I got stuck at the SE logo. Been trying to get my phone to boot (to any rom right now then I'll try to unlock the bootloader again).
Any ideas?
did you flash doomlords kernel?? and from what i remember there were 2 applications that came with the file provided. if one doesnt use the other one.(if i remember correctly)
fcb1 said:
did you flash doomlords kernel??
Click to expand...
Click to collapse
I didn't get that far. All I did was flash the kernel downgrade, then ran the batch file. After it was successful I noticed my phone was stuck on the sony ericsson logo so I didn't continue with the rest of the instructions.
ok then just flash doomlords kernel. if you dont see the white sony ericcson letters after flashing doolords krnel, then you should be in the clear
fcb1 said:
ok then just flash doomlords kernel. if you dont see the white sony ericcson letters after flashing doolords krnel, then you should be in the clear
Click to expand...
Click to collapse
It won't flash the kernel. Here's the log:
30/024/2011 19:24:48 - INFO - Searching Xperia....
30/024/2011 19:24:48 - INFO - Found at USB\VID_0FCE&PID_ADDE\5&10EF021E&0&6
30/024/2011 19:24:48 - INFO - Start Flashing
30/024/2011 19:24:48 - INFO - VER="r8A033";DATE="20100928";TIME="12:04:00";
30/026/2011 19:26:59 - INFO - Flashing loader
30/036/2011 19:36:58 - ERROR - Error flashing. Aborted
30/036/2011 19:36:58 - INFO - Now unplug the device and power it on
30/036/2011 19:36:58 - INFO - Then go to application settings
30/036/2011 19:36:58 - INFO - turn on Unknown Sources and Debugging
Click to expand...
Click to collapse
Notice that there's about a 10 minute difference between "Flashing loader" And the ERROR.
Hi,
Attempt to restore your bootloader via this tool and attempt your unlock again.
NOTE: Make sure you have the stock Sony Ericsson kernel installed.
Regards,
Mayazcherquoi.
Mayazcherquoi said:
Hi,
Attempt to restore your bootloader via this tool and attempt your unlock again.
NOTE: Make sure you have the stock Sony Ericsson kernel installed.
Regards,
Mayazcherquoi.
Click to expand...
Click to collapse
Ah crap..what if I had the free xperia kernel on? I just did a restore with that on and I can't flash the downgrade kernel..
Btw, I was able to flash doomlords kernel by trying it on another computer. But I think I messed up somewhere so I wanted to start over. And I restored w/out flashing back the stock kernel.
I just downloaded the kernel+baseband package from here and see if I can flash it via flashtool http://forum.xda-developers.com/showthread.php?t=1192152
Edit: ok, that was a close call. Now lets try all this again
Edit2: Okay bootloader unlocked. Flashed the free xperia custom kernel however when I get into CWM-based recovery I get the following error: "Can't mount /sdcard/" whenever I select choose zip from sd card. I was getting this before but I that thought that may be because I didn't flash the bootloader correctly but now I don't know what's causing it.
I have xperia x10 mini manufacturing date 10w40
Can i unlock my bootloader??
Please answer only if you are sure cause i dont wana brick my phone
Also tell me the easiest method to unlock my bootloader..
Or can i use any Rom on 2.3 without unlocking bootloader??
Yes you can, your manufacturing date is week 40 of 2010, the warnings only go out for manufacturing dates from week 29 in 2011.
The easiest way to unlock your bootloader is from the plugins-menu in flashtool.
You can still lose your radio-capability if your simlock-certificate is not recognised in S1Tool, but you can relock the bootloader with the Restore-button in S1Tool and your radio-capability SHOULD come back.
If you unlock your bootloader, boot the phone on stock firmware first and check for network connectivity, if your network is gone/sim not recognised, relock your bootloader. If everything works as it should you can go and flash custom kernels and roms.
SmG67 said:
Yes you can, your manufacturing date is week 40 of 2010, the warnings only go out for manufacturing dates from week 29 in 2011.
The easiest way to unlock your bootloader is from the plugins-menu in flashtool.
You can still lose your radio-capability if your simlock-certificate is not recognised in S1Tool, but you can relock the bootloader with the Restore-button in S1Tool and your radio-capability SHOULD come back.
If you unlock your bootloader, boot the phone on stock firmware first and check for network connectivity, if your network is gone/sim not recognised, relock your bootloader. If everything works as it should you can go and flash custom kernels and roms.
Click to expand...
Click to collapse
I'm getting Blue coloured Error "CANCELLED"
Why?
I don't know... maybe you could post the output from the identify button in S1Tool and the output from flashtool when you get that error, maybe that tells me a bit more of what is going wrong
SmG67 said:
I don't know... maybe you could post the output from the identify button in S1Tool and the output from flashtool when you get that error, maybe that tells me a bit more of what is going wrong
Click to expand...
Click to collapse
See here http://imageshack.us/photo/my-images/204/35480731.png/
The text is unreadable that way but i think at the bottom it says SEMC Simlock certificate? you should be ok then.
Please copy the text from flashtool when you choose the unlock-bootloader option from the plugins-menu and paste it here
SmG67 said:
The text is unreadable that way but i think at the bottom it says SEMC Simlock certificate? you should be ok then.
Please copy the text from flashtool when you choose the unlock-bootloader option from the plugins-menu and paste it here
Click to expand...
Click to collapse
18/000/2012 20:00:15 - INFO - <- This level is successfully initialized
18/000/2012 20:00:15 - INFO - Flashtool Version 0.7.1.0 built on 2012-05-01 22:07:23
18/000/2012 20:00:15 - INFO - You can drag and drop ftf files here to start flashing them
18/000/2012 20:00:21 - INFO - Device connected with USB debugging on
18/000/2012 20:00:22 - INFO - Connected device : E10
18/000/2012 20:00:22 - INFO - Installed version of busybox : N/A
18/000/2012 20:00:22 - INFO - Android version : 2.1-update1 / kernel version : 2.6.29
18/000/2012 20:00:22 - INFO - Root Access Allowed
18/000/2012 20:00:35 - INFO - Device disconnected
18/000/2012 20:00:46 - INFO - Device connected with USB debugging on
18/000/2012 20:00:47 - INFO - Connected device : E10
18/000/2012 20:00:47 - INFO - Installed version of busybox : N/A
18/000/2012 20:00:47 - INFO - Android version : 2.1-update1 / kernel version : 2.6.29
18/000/2012 20:00:47 - INFO - Root Access Allowed
18/000/2012 20:00:53 - INFO - Please connect your device into flashmode.
18/000/2012 20:00:57 - INFO - Device disconnected
18/001/2012 20:01:27 - INFO - Device connected in flash mode
18/001/2012 20:01:28 - INFO - Opening device for R/W
18/001/2012 20:01:28 - INFO - Reading device information
18/001/2012 20:01:28 - INFO - Phone ready for flashmode operations.
18/001/2012 20:01:28 - INFO - Flashing loader
18/001/2012 20:01:28 - INFO - Ending flash session
18/001/2012 20:01:28 - WARN - Cancelled
18/001/2012 20:01:28 - INFO - Device connected in flash mode
18/001/2012 20:01:29 - INFO - Device disconnected
18/001/2012 20:01:32 - INFO - Device connected in flash mode
18/001/2012 20:01:35 - INFO - Device disconnected
Install busybox with flashtool, reboot your phone and try again
SmG67 said:
Install busybox with flashtool, reboot your phone and try again
Click to expand...
Click to collapse
ok thanks wait don't go anywhere please i'm doing.
piousheart said:
ok thanks wait don't go anywhere please i'm doing.
Click to expand...
Click to collapse
lol i have to go to work in a few minutes, i'll check back later, but i think you'll be fine now (although i'm not entirely sure)
No success
What to do now? please help
SmG67 said:
Install busybox with flashtool, reboot your phone and try again
Click to expand...
Click to collapse
Thanks!! I did it with manual method and. . .BoOM bootloader is unlocked.!!
Please confirm the following things.
1.Currently i'm on Built No-2.0.A.0.504,can i flash latest Latest 2.1.1.A.0.6 with unlocked bootloader?
2.Will nAa kernel will work with the stock 2.1.1.A.0.6 firmware (i will flash stock 2.1.1.A.0.6 firmware and then nAa kernel because i want to use miniCM 7)
Give rating to miniCM7 x\5
If you still got network reception then you're ok
You could have flashed the 2.1.1.a.0.6 firmware with a locked bootloader too, so with an unlocked bootloader that shouldn't be a problem
You can flash the nAa-11 kernel for Gingerbread roms, but your phone won't boot, you have to go into CWM after flashing the kernel, and install MiniCM7 from your sd-card, so copy that first before you flash the Kernel.
Make sure you make a backup in CWM first,, then do a wipe data/factory-reset, wipe cache, go into advanced, wipe dalvik-cache, wipe battery stats, then back into the main menu and install zip from sd-card. select the MiniCM7 zip you copied and wait for it to finish.
Reboot your system, if it takes longer than 5 minutes to start up, press home and power buttons simultaneously, you'll get a restart, enter CWM again and do all the wipes again, it should work after that.
SmG67 said:
If you still got network reception then you're ok
You could have flashed the 2.1.1.a.0.6 firmware with a locked bootloader too, so with an unlocked bootloader that shouldn't be a problem
You can flash the nAa-11 kernel for Gingerbread roms, but your phone won't boot, you have to go into CWM after flashing the kernel, and install MiniCM7 from your sd-card, so copy that first before you flash the Kernel.
Make sure you make a backup in CWM first,, then do a wipe data/factory-reset, wipe cache, go into advanced, wipe dalvik-cache, wipe battery stats, then back into the main menu and install zip from sd-card. select the MiniCM7 zip you copied and wait for it to finish.
Reboot your system, if it takes longer than 5 minutes to start up, press home and power buttons simultaneously, you'll get a restart, enter CWM again and do all the wipes again, it should work after that.
Click to expand...
Click to collapse
Process Started...wish me luck.!!
Bro please provide me a link for 2.1.1.A.0.6 firmware for my E10i please..
I searched but failed..and by mistake i flashed another firmware and the phone is bricked so now again on 2.0.A.0.504
piousheart said:
Bro please provide me a link for 2.1.1.A.0.6 firmware for my E10i please..
I searched but failed..and by mistake i flashed another firmware and the phone is bricked so now again on 2.0.A.0.504
Click to expand...
Click to collapse
SE don't like to see their firmware all over the internet, that's why all the links are dead.
SmG67 said:
SE don't like to see their firmware all over the internet, that's why all the links are dead, check your inbox
Click to expand...
Click to collapse
Thanks a ton for the link
But i download the 2.1.1.C.0.0 from some site and it worked.!!
Now going one step further..!!
Installed MiniCM 7 but now SD card not dected..
What to do??
piousheart said:
Installed MiniCM 7 but now SD card not dected..
What to do??
Click to expand...
Click to collapse
How is it not detected? by the phone itself?
Boot back into CWM and Wipe everything (wipe data/facotory reset, wipe cache, wipe dalvik-cache), and reboot see if that helps
In storage there is option to unmount SD card so phone is detecting SD card.
When i use Camera,gallery etc it says SD card not present
I tried factory reset,cache,delvic cache...but not working!!
but file manager like root explorer is working and sowing contents of SD card
I installed a ROM with its kernel (concretely, THIS rom with the recommended kernel) using CWM, and when I reboot it gets stuck at Sony splash... It's been like that for almost two hours.
So the question is... is it bricked? (I think that's a stupid question, it sure is...) Can this be repaired? Or I have to ask Sony for help (if possible)?
if you can get into cwm ..... try to reflash the rom....follow the steps given by the dev...wipe delvic/data etc..
if it does not work or if you cannot get into CWM reflash with night-elf kernel...
u r phone is not bricked :good::victory:
Log in Flashtool shows me that...
04/058/2012 18:58:24 - INFO - <- This level is successfully initialized
04/058/2012 18:58:24 - INFO - Flashtool Version 0.6.8.0 built on 2012-02-26 19:26:25
04/058/2012 18:58:24 - INFO - You can drag and drop ftf files here to start flashing them
04/058/2012 18:58:35 - INFO - Device connected in fastboot mode
04/059/2012 18:59:05 - INFO - Launching Fastboot Toolbox 1.0 by DooMLoRD
04/059/2012 18:59:06 - INFO - Device Status: FASTBOOT mode
04/059/2012 18:59:25 - INFO - Selected kernel (boot.img or kernel.sin): C:\Users\Arnold\Downloads\boot_ics_cm9-127.img
04/059/2012 18:59:25 - INFO - Flashing selected kernel
04/059/2012 18:59:26 - INFO - FASTBOOT Output:
sending 'boot' (5114 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.001s
04/059/2012 18:59:26 - INFO - Please check the log before rebooting into system
Click to expand...
Click to collapse
do u have ur bootloader unlocked...???if not unlock it first...
Well, I guess it actually was unlocked... if not, how do I check it without entering the system or CWM?
if it is unlocked u will be able to flash it with other kernels
do you have latest version of flash tools??
try to download it and try again......if u have unlocked bootloader....it should work
if nothing happens use SEUS to restore
Arno-kun said:
I installed a ROM with its kernel (concretely, THIS rom with the recommended kernel) using CWM, and when I reboot it gets stuck at Sony splash... It's been like that for almost two hours.
So the question is... is it bricked? (I think that's a stupid question, it sure is...) Can this be repaired? Or I have to ask Sony for help (if possible)?
Click to expand...
Click to collapse
Firstly the good news is ur phone is not at all bricked ..i think u somehow installed the wrong kernel or something ..thats y the problem ..i had the same too about 3 days back ..u need to got back to the stock Rom ..and everything will be fine ..i think you knw it but i am telling u again : U need unlocked boot loader to flash custom ROMS
Now lets begin installing ur stock ROM
If u unlocked ur bootlaoder using the official method go here: http://forum.xda-developers.com/showthread.php?t=1134335&page=2 and relock it but DRM keys wont be back ..but u r bootlaoder will be locked again
1) Here : download the stock ROM http://talk.sonymobile.com/thread/35239?tstart=0 and install it through flashtool or go here http://forum.xda-developers.com/showthread.php?t=1678690 to download stock ROM
2) Follow the instructions in this thread : http://forum.xda-developers.com/showpost.php?p=26798415&postcount=141
3) Now u r on stock ROM with stock kernel ..root ur phone again using doomlords method given in the link above.
4) install CWM
5) Unlock ur boot loader again (u cannot unlock it using the official way unless u have the boot loader key that sony gave u when unlocking the boot loader )
samneov said:
if it is unlocked u will be able to flash it with other kernels
do you have latest version of flash tools??
try to download it and try again......if u have unlocked bootloader....it should work
if nothing happens use SEUS to restore
Click to expand...
Click to collapse
You know, using SEUS fixed my phone. Checked bootloader, and it's UNLOCKED. Thanks a lot to everyone! Thought I already lost my phone... Again, thank you all!
Hi,
Just looking for some advice really, I'm looking to root/flash my girlfriends's mini pro (SK17i), it's currently running GB (4.0.2.A.0.62) which as I understand cannot be rooted from that particular version? The phone was bought 2nd hand and the bootloader is already unlocked.
Questions I have are:
1. From reading the forums, I was going to go with stock ICS rom with rage kernel, as I'm looking for stability/battery life, or are there better combinations of custom ROM/kernel out there, for this purpose?
2. If I do stay with stock ICS is it necessary that I downgrade before rooting then flashing? Or can I flash directly to ICS?
I should be fine with the whole process of rooting flashing the phone, but would greatly appreciate the advice!!
Again Many Thanks
1. Since you have a unlocked bootloader it's possible to root .62 firmware by just flashing a prerooted kernel like the rage kernel for gb.
2.I've been using rage ics kernel with stock Sony ics Rom, it is very much stable and battery standby is really good.
3. First you flash the ics ftf using flashtool and boot the device. then power down the device and enter into flashmode and flash rage kernel for ics. You don't have to root your phone separately, once you flash the rage kernel for ics you're phone will be automatically rooted and busybox will be installed.
You don't have to downgrade at all! You have a unlocked bootloader man! Just flash the rage kernel and your phone will be rooted!
Just make sure you flash the correct version of rage kernel. 3.2 for ics. 3.0 for gingerbread.
hit thanks if I've helped!
sent from my smultron
Thanks for the swift reply!
So to clarify, am I right in thinking flash the ICS ROM first then once done reboot and flash the Kernel next?
I dont need to flash the kernel on GB first?
Also any opinions on Panic Kernel, is that also prerooted?
Cheers
nedsnurb said:
Thanks for the swift reply!
So to clarify, am I right in thinking flash the ICS ROM first then once done reboot and flash the Kernel next?
I dont need to flash the kernel on GB first?
Also any opinions on Panic Kernel, is that also prerooted?
Cheers
Click to expand...
Click to collapse
1. That`s the point. Normally, to install a custom rom via clockworkmod you flash the kernel first and after that you install the rom.
But now you don't install a custom rom, you flash the ftf and this ftf will overwrite the kernel (kernel is a boot.img). So after you have flashed the ftf you can just plug phone off, plug in in fastboot mode again and flash the custom kernel. Then just reboot (you can reboot before flashing kernel if you like, but that wouldn't change anything)
2. No you don't need, just flash the kernel for the rom you like.
3. Yes panic should be prerooted, too
Ya you are right! No need to flash gb kernel .
hit thanks if I've helped!
sent from my smultron
---------- Post added at 05:47 PM ---------- Previous post was at 05:44 PM ----------
mihahn said:
1. That`s the point. Normally, to install a custom rom via clockworkmod you flash the kernel first and after that you install the rom.
But now you don't install a custom rom, you flash the ftf and this ftf will overwrite the kernel (kernel is a boot.img). So after you have flashed the ftf you can just plug phone off, plug in in fastboot mode again and flash the custom kernel. Then just reboot (you can reboot before flashing kernel if you like, but that wouldn't change anything)
2. No you don't need, just flash the kernel for the rom you like.
3. Yes panic should be prerooted, too
Click to expand...
Click to collapse
Ya it wouldn't change anything but to make sure that the ftf is been flashed properly and the Rom boots. Just to go step by step.
hit thanks if I've helped!
sent from my smultron
Tbh if you're looking for good stabilty and battery life GB is still the go to....Rage kernel is DEfinitely not the best kernel for battery life
Panic is prerooted, its not harsh on battery life, but it has a few minor bugs, usb only connects in media transfer mode and the cmw 6 it has has reported some issues when doing nand backups...The best kernbel for stability and battery in my opinion (i tested them all) is Mesa kernel, rage and panic are more for performance and performance usually means less battery life
Okay guys, flashed stock ICS ROM fine!
But now trying to flash MESA kernel using Fastboot Toolbox within Flashtool and I'm getting the error that my device isn't rooted?
Tried with a few other kernels and the same problem? I was under the impression flashing the kernel would also root the device?
Here is the Flashtool log
09/016/2012 19:16:18 - INFO - <- This level is successfully initialized
09/016/2012 19:16:18 - INFO - Flashtool Version 0.9.8.0 built on 2012-10-01 19:35:32
09/016/2012 19:16:18 - INFO - You can drag and drop ftf files here to start flashing them
09/016/2012 19:16:28 - INFO - Device disconnected
09/016/2012 19:16:28 - INFO - Launching Fastboot Toolbox 1.0 by DooMLoRD
09/016/2012 19:16:30 - INFO - Device Status: NOT FOUND
09/016/2012 19:16:41 - INFO - Device connected in fastboot mode
09/017/2012 19:17:38 - ERROR - no kernel (boot.img or kernel.sin) selected!
09/018/2012 19:18:03 - INFO - Finished Fastboot Toolbox
09/019/2012 19:19:32 - INFO - Launching Fastboot Toolbox 1.0 by DooMLoRD
09/019/2012 19:19:32 - INFO - Device Status: FASTBOOT mode
09/019/2012 19:19:48 - INFO - Selected kernel (boot.img or kernel.sin): C:\Users\Johnny\Downloads\minipro_mesa_v1.8.img
09/019/2012 19:19:48 - INFO - Flashing selected kernel
09/019/2012 19:19:49 - INFO - sending 'boot' (7126 KB)...
09/019/2012 19:19:49 - INFO - FAILED (remote: The Device must be rooted first)
09/019/2012 19:19:49 - INFO - finished. total time: 0.003s
09/019/2012 19:19:49 - INFO - FASTBOOT Output:
sending 'boot' (7126 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.003s
Click to expand...
Click to collapse
Help!
nedsnurb said:
Okay guys, flashed stock ICS ROM fine!
But now trying to flash MESA kernel using Fastboot Toolbox within Flashtool and I'm getting the error that my device isn't rooted?
Tried with a few other kernels and the same problem? I was under the impression flashing the kernel would also root the device?
Here is the Flashtool log
Help!
Click to expand...
Click to collapse
Hmm the log looks like your phone's bootloader isn't unlocked yet. Please power phone on and type *#*#7378423#*#* and go to service info -> configuration -> rooting status and tell us what is written there. Cause it must work
Yeah it has bootloader unlock allowed: yes
Which I'm guessing it means it isn't unlocked at present?
Sorry was being stupid I thought it was already unlocked! I can just follow the tutorial sticky to unlock right? Then give it another go?
nedsnurb said:
Yeah it has bootloader unlock allowed: yes
Which I'm guessing it means it isn't unlocked at present?
Sorry was being stupid I thought it was already unlocked! I can just follow the tutorial sticky to unlock right? Then give it another go?
Click to expand...
Click to collapse
Okay you must know what you want, two options:
1. Just root phone, and uninstall the crap. This maybe won't void warranty, cause if you unroot you can bring it to service again.
2. Unlock bootloader:
1. You unlock via official method -> you void warranty but you can install a custom kernel for better performance or other custom roms (for example cyanogenmod)
2. You unlock via testpoint method, which can be relocked and maybe sony won't notice, but that's more dangerous and I wouldn't do it.
These are the methods you have, just choose one
Btw for rooting you needn't unlock bootloader, choose your current software version in my rooting guide and follow the steps to root
nedsnurb said:
Yeah it has bootloader unlock allowed: yes
Which I'm guessing it means it isn't unlocked at present?
Sorry was being stupid I thought it was already unlocked! I can just follow the tutorial sticky to unlock right? Then give it another go?
Click to expand...
Click to collapse
Ya it looks like you haven't unlocked your bootloader yet .
It's better to unlock via the official method. You'll lose DRM keys (google it) and remember all your phone data (except memory card data) will be erased To be on the safer side just remove the memory card prior to unlocking. Sync up your contacts to your google account or take a backup of your contacts in your memory card.
YOU'LL VOID YOUR WARRANTY. YOU CANNOT USE SEUS TO UPDATE YOUR PHONE SOFTWARE instead you have to use flashtool which is not a concern at all and after unlocking please do not accept any over the air (ota) Sony software updates, IT WILL BRICK YOUR DEVICE .
Just for your information there is also a guide to unbrick the device which is bricked due to fota update but you would not want to brick it in the first place would you? .
Look at Sony's official bootloader unlocking page for further instructions and keep your IMEI handy it'll ask for it (dial *#06# for your IMEI or look at the phone's packaging).
Happy unlocking!
hit thanks if I've helped!
sent from my smultron
Model: X10a
Country: Philippines
OS: Android 2.1 update1
Build Number: 2.0.2.A.0.24
Rooted: Yes
Unlock Bootloader: I don't know if my device is Unlocked.
Locked Bootloader: I don't know if my device is Locked.
The Steps before the Problem Stuck SE
* I was unsure about the posted requirements;
-- Any Bootloader (locked or unlocked)
-- Latest GB FeraKernel if you have unlocked bootloader (no need for drivers - they are included in ROM. Kernel for locked bootloader is included in ROM package).
*I downloaded the FeraLab_v27_~Fire~.zip
*I followed the steps;
* AROMA Installation wizard, I cant click the next button (or the screen is not responding)
*I successfully installed the Rom using the volume key and home key as the (ok and next back button)
*After the installation, I restart the device according to the instruction in the wizard
*Now I'am stuck on SE
Now my Questions Are;
* Do I download the Wrong FeraLab Rom?
* Is it Not Compatible with my Device? If Yes Compatible for FeraLab Rom. What version of FeraLab is Compatible with me?
*Do i need to use some kernels? Since I was not sure about the posted requirements
Last:
I really love those who will help me and those who will just passing by and got time to read this <3
Thanks in advance. I hope you can help me ma'am and sir =)
You need to download the locked bootloader kernel and flash it should be on his website
Sent from my X10 using xda premium
iCronqvist said:
Model: X10a
Country: Philippines
OS: Android 2.1 update1
Build Number: 2.0.2.A.0.24
Rooted: Yes
Unlock Bootloader: I don't know if my device is Unlocked.
Locked Bootloader: I don't know if my device is Locked.
The Steps before the Problem Stuck SE
* I was unsure about the posted requirements;
-- Any Bootloader (locked or unlocked)
-- Latest GB FeraKernel if you have unlocked bootloader (no need for drivers - they are included in ROM. Kernel for locked bootloader is included in ROM package).
*I downloaded the FeraLab_v27_~Fire~.zip
*I followed the steps;
* AROMA Installation wizard, I cant click the next button (or the screen is not responding)
*I successfully installed the Rom using the volume key and home key as the (ok and next back button)
*After the installation, I restart the device according to the instruction in the wizard
*Now I'am stuck on SE
Now my Questions Are;
* Do I download the Wrong FeraLab Rom?
* Is it Not Compatible with my Device? If Yes Compatible for FeraLab Rom. What version of FeraLab is Compatible with me?
*Do i need to use some kernels? Since I was not sure about the posted requirements
Last:
I really love those who will help me and those who will just passing by and got time to read this
I just remembered. There might be a chance that it's an at&t device and 2.3.3 might not be available via SEUS. What you can do is change the region of you build.prop to get the updated fw.
Click to expand...
Click to collapse
iCronqvist said:
Model: X10a
Country: Philippines
OS: Android 2.1 update1
Build Number: 2.0.2.A.0.24
Rooted: Yes
Unlock Bootloader: I don't know if my device is Unlocked.
Locked Bootloader: I don't know if my device is Locked.
The Steps before the Problem Stuck SE
* I was unsure about the posted requirements;
-- Any Bootloader (locked or unlocked)
-- Latest GB FeraKernel if you have unlocked bootloader (no need for drivers - they are included in ROM. Kernel for locked bootloader is included in ROM package).
*I downloaded the FeraLab_v27_~Fire~.zip
*I followed the steps;
* AROMA Installation wizard, I cant click the next button (or the screen is not responding)
*I successfully installed the Rom using the volume key and home key as the (ok and next back button)
*After the installation, I restart the device according to the instruction in the wizard
*Now I'am stuck on SE
Now my Questions Are;
* Do I download the Wrong FeraLab Rom?
* Is it Not Compatible with my Device? If Yes Compatible for FeraLab Rom. What version of FeraLab is Compatible with me?
*Do i need to use some kernels? Since I was not sure about the posted requirements
Last:
I really love those who will help me and those who will just passing by and got time to read this <3
Thanks in advance. I hope you can help me ma'am and sir =)
Click to expand...
Click to collapse
it is a typical problem with the feralab rom you must have chosen unlocked bootloader in the aroma while you have locked one or the opposite just reflash your phone to 2.3.3 and try again
If its stuck on SE means the kernel has not been flashed yet, actually before installing the rom you should flash the 2.3 ftf (do a Google search for it, it's there)
Sent from my X10i using xda premium
aymensx said:
it is a typical problem with the feralab rom you must have chosen unlocked bootloader in the aroma while you have locked one or the opposite just reflash your phone to 2.3.3 and try again
Click to expand...
Click to collapse
ROM is for both bootloader but follow kernel flashing according to your bootloader either locked or unlocked. It is available in feralab official site
FOR LOCKED BOOTLOADERS:
-- Download ZIP file called nearly same as [LB]FeraKernel-GB-xxx.zip and copy it to SDcard.
-- Boot to xRecovery and flash zip(all drivers are already in kernel zip).
-- Reboot your device twice and you're done.
FOR UNLOCKED BOOTLOADERS:
-- Download FTF file called nearly same as FeraKernel-GB-xxx.ftf and put it to /firmware folder in FlashTool root folder.
-- Download ZIP file with 'DRIVERS' label and put it to SDcard
-- Flash FTF kernel file using FlashTool, and boot directly to recovery (press BACK-Key on led light).
-- Flash 'DRIVERS' zip and reboot your phone twice. Done.
i have the same problem, but i can not do a thing. in flashtool i have this prob with every ftf i am trying
11/036/2013 09:36:27 - INFO - Preparing files for flashing
11/036/2013 09:36:27 - INFO - Please connect your device into flashmode.
11/036/2013 09:36:49 - INFO - Device connected in flash mode
11/036/2013 09:36:50 - INFO - Opening device for R/W
11/036/2013 09:36:50 - INFO - Start Flashing
11/036/2013 09:36:50 - INFO - Processing loader
11/036/2013 09:36:50 - INFO - Checking header
11/036/2013 09:36:50 - INFO - Ending flash session
11/036/2013 09:36:50 - ERROR -
11/036/2013 09:36:50 - ERROR - Error flashing. Aborted
11/036/2013 09:36:50 - INFO - Device connected in flash mod
and it is stucked at SE logo. and pc companion is not working and i can not enter xrecovery on sd card i have the last backup for rom but i can not enter to use is... what should i do???????
Sony pc companion will flash phone even phone is not getting detect(Repair phone) have u tried this?
Sent from my X10 using xda app-developers app
me? yes i have. nothing is working....
please help me to resolve x10 flashing feralab
--> Xperia x10, flashed with 2.3.3
--> Rooted , installed xrecovery
--> Locked boot loader
Steps followed to install FeraLab v29
-------------------------------------------
1. Booted into xRecovery
2. Install custom ROM
3. Chosen FeraKernel.zip
Failed on certification issue
then Installed CMW recovery, Could not flash ferakernel
Tried to flash Feravolt v29 ROM it works, but stays in SE logo in 1st reboot..
Please help me...
Mine too
Fera claims his new (v32) rom doesnt need a kernel as its already built in if you have an unlockedboot loader..
But now my phone appears to be bricked...