Oky so i have xperia u with root(obviously ) and eXperience rom installed.
I tried flashing many kernal(boot.img) but every time i do that its the same (Uanble to flash root required)
Plz help
lols21.10 said:
Oky so i have xperia u with root(obviously ) and eXperience rom installed.
I tried flashing many kernal(boot.img) but every time i do that its the same (Uanble to flash root required)
Plz help
Click to expand...
Click to collapse
You mean with fastboot mode? Root is not enough, bootloader must be unlocked.
ChikeD said:
You mean with fastboot mode? Root is not enough, bootloader must be unlocked.
Click to expand...
Click to collapse
+1
Open flashtool, enter fastboot, look for the .iso file, and flash it.
If it doesn't work, you should try to do it with adb.
manudo said:
+1
Open flashtool, enter fastboot, look for the .iso file, and flash it.
If it doesn't work, you should try to do it with adb.
Click to expand...
Click to collapse
My bootloader is unlocked
lols21.10 said:
My bootloader is unlocked
Click to expand...
Click to collapse
Great, so you can flash custom kernels.
Try to flash with the method at the right side (three buttons) in the kernel flashing screen in flashtool.
manudo said:
Great, so you can flash custom kernels.
Try to flash with the method at the right side (three buttons) in the kernel flashing screen in flashtool.
Click to expand...
Click to collapse
I did't really understand what you saying.
But man its irritating me so much i also tried a " Xperia u tool " to flash kernal but still no successsss
:crying::crying::crying::crying:
AlexDroid00\Kernels\boot.img
30/002/2013 23:02:51 - INFO - Flashing selected kernel
30/002/2013 23:02:51 - INFO - sending 'boot' (9112 KB)...
30/002/2013 23:02:51 - INFO - FAILED (remote: The Device must be rooted first)
30/002/2013 23:02:51 - INFO - finished. total time: 0.002s
30/002/2013 23:02:51 - INFO - FASTBOOT Output:
sending 'boot' (9112 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.002s
Its shows this error everytime even with rooted and unlocked bootloader
AlexDroid00\Kernels\boot.img
30/002/2013 23:02:51 - INFO - Flashing selected kernel
30/002/2013 23:02:51 - INFO - sending 'boot' (9112 KB)...
30/002/2013 23:02:51 - INFO - FAILED (remote: The Device must be rooted first)
30/002/2013 23:02:51 - INFO - finished. total time: 0.002s
30/002/2013 23:02:51 - INFO - FASTBOOT Output:
sending 'boot' (9112 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.002s
Its shows this error everytime even with rooted and unlocked bootloader
lols21.10 said:
AlexDroid00\Kernels\boot.img
30/002/2013 23:02:51 - INFO - Flashing selected kernel
30/002/2013 23:02:51 - INFO - sending 'boot' (9112 KB)...
30/002/2013 23:02:51 - INFO - FAILED (remote: The Device must be rooted first)
30/002/2013 23:02:51 - INFO - finished. total time: 0.002s
30/002/2013 23:02:51 - INFO - FASTBOOT Output:
sending 'boot' (9112 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.002s
Its shows this error everytime even with rooted and unlocked bootloader
Click to expand...
Click to collapse
Are you sure bootloader is unlocked?
Root does not matter, does it show Bootloader unlocked: yes, in service configuration?
YES!
lols21.10 said:
YES!
Click to expand...
Click to collapse
Did you try doing it via cmd?
"fastboot flash boot boot.img"
Anthrax said:
Did you try doing it via cmd?
"fastboot flash boot boot.img"
Click to expand...
Click to collapse
Need the Google USB Drivers first.
Sent from my Xperia Sola using xda premium
manudo said:
Need the Google USB Drivers first.
Sent from my Xperia Sola using xda premium
Click to expand...
Click to collapse
need fastboot drivers and you are good to go...
This dude has the same problem as I did, I just turn off the phone and connect in fastboot mode.
But in cmd it's easier.
Sent from my Xperia Sola using xda premium
No fastboot is also not working(i have fastboot drivers installed)
But My problem is now fixed
I installed kernal via terminal emulator
and it installed it
Anyway thanks for your advice
lols21.10 said:
No fastboot is also not working(i have fastboot drivers installed)
But My problem is now fixed
I installed kernal via terminal emulator
and it installed it
Anyway thanks for your advice
Click to expand...
Click to collapse
You mean, cmd, right?
Sent from my Xperia Sola using xda premium
Related
I recently discovered this, and I thought it would be of some benefit to those who are wanting to unlock, modify partitions, etc without the need to flash derpunlock.sbf or modify your photon in any way. What you need to do this:
1) fastboot for Windows or Linux
2) unlocked RDL3 (ramloader) which I am providing
The process is very simple, reboot your Motorola Photon, and hold the volume down button and power button. You will see "fastboot" on the screen, now press volume up. Connect your phone to your computer, and issue the following command which I discovered:
[email protected]:~$ fastboot flash rdl.bin RDL3_unlocked.smg
sending 'rdl.bin' (3072 KB)...
OKAY [ 0.193s]
writing 'rdl.bin'...
OKAY [ 0.000s]
finished. total time: 0.193s
This will load the unlocked ramloader (unlocked will be displayed at the top even if your phone is locked) which is normally only loaded into ram when flashing an SBF! Amazing, I know. Now you can do all kinds of stuff and you've made no modifications, just issue a "fastboot reboot" and nothing has been modified. Now you are able to erase boot, recovery, oem unlock, etc. Here is an example after you have executed the above. This is just me restoring my default boot and recovery partitions which you can't do from your locked bootloader:
[email protected]:~$ fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.739s]
finished. total time: 0.739s
[email protected]:~/Desktop/SMG$ fastboot flash recovery CG58_0x00000120.smg sending 'recovery' (8192 KB)...
OKAY [ 8.760s]
writing 'recovery'...
OKAY [ 1.013s]
finished. total time: 9.773s
[email protected]:~/Desktop/SMG$ fastboot erase boot
erasing 'boot'...
OKAY [ 0.761s]
finished. total time: 0.761s
[email protected]:~/Desktop/SMG$ fastboot flash boot CG59_0x00000130.smg
sending 'boot' (8192 KB)...
OKAY [ 8.800s]
writing 'boot'...
OKAY [ 0.697s]
finished. total time: 9.497s
good progress on it
You can actually unlock the radio with the stock locked bootloader still in place (derpunlock.sbf flashing no longer needed):
[email protected]:~/Desktop/SMG_derpunlock$ fastboot flash rdl.bin RDL3_unlocked.smg
sending 'rdl.bin' (3072 KB)...
OKAY [ 0.193s]
writing 'rdl.bin'...
OKAY [ 0.000s]
finished. total time: 0.193s
[email protected]:~/Desktop/SMG_derpunlock$ fastboot oem unlock
...
(bootloader) Unlocking your device can permanently VOID your warranty.
(bootloader) This process cannot be reversed. If you wish to proceed,
(bootloader) reissue the unlock OEM command containing the unique ID
(bootloader) of your device: XXXXXXXXXXXXXXXX
OKAY [ 0.006s]
finished. total time: 0.006s
[email protected]:~/Desktop/SMG_derpunlock$ fastboot oem unlock XXXXXXXXXXXXXXXX
...
(bootloader) Device is already unlocked
OKAY [ 0.003s]
finished. total time: 0.003s
[email protected]:~/Desktop/SMG_derpunlock$
4G ?
Has anyone tried this method and retained 4G?
scottgl9 said:
You can actually unlock the radio with the stock locked bootloader still in place (derpunlock.sbf flashing no longer needed):
[email protected]:~/Desktop/SMG_derpunlock$ fastboot flash rdl.bin RDL3_unlocked.smg
sending 'rdl.bin' (3072 KB)...
OKAY [ 0.193s]
writing 'rdl.bin'...
OKAY [ 0.000s]
finished. total time: 0.193s
[email protected]:~/Desktop/SMG_derpunlock$ fastboot oem unlock
...
(bootloader) Unlocking your device can permanently VOID your warranty.
(bootloader) This process cannot be reversed. If you wish to proceed,
(bootloader) reissue the unlock OEM command containing the unique ID
(bootloader) of your device: XXXXXXXXXXXXXXXX
OKAY [ 0.006s]
finished. total time: 0.006s
[email protected]:~/Desktop/SMG_derpunlock$ fastboot oem unlock XXXXXXXXXXXXXXXX
...
(bootloader) Device is already unlocked
OKAY [ 0.003s]
finished. total time: 0.003s
[email protected]:~/Desktop/SMG_derpunlock$
Click to expand...
Click to collapse
what would be the process coming from locked stock _6, would i just flash clock work mod, flash rom.zip then OP's inputs?
bigslanki said:
what would be the process coming from locked stock _6, would i just flash clock work mod, flash rom.zip then OP's inputs?
Click to expand...
Click to collapse
The process of loading the unlocked ramloader is the same regardless of your firmware, even if the bootloader is 'locked'. The ramloader is just that, its written to ram, and so when the phone is reset the code is cleared out of memory. This means to unlock your radio, you don't have to flash anything to your ram, flashing rdl.bin basically just loads the ramloader to executable memory, then jumps to it. I'm still working on figuring out how to use this to chain load a custom recovery.
Love this! Keep up the good work!
So can I flash CWM after this kind of unlock the bootloader and then custom rom.
Sent from my SPH-D710 using XDA
Will this be useful for the ones that flash the electrify rom on the photon?
Sent from my MB855 using XDA
may you attach stock recovery here? thanks
rrusek said:
Has anyone tried this method and retained 4G?
Click to expand...
Click to collapse
+1
4G confirmed working or not?
I like what I m reading. Sounds like this would be the saving grace for those photon users stuck on an electrify rom (and yeah I m one of them!). Please let us know when you get to rewrite system with a custom rom with this method!
dito33 said:
So can I flash CWM after this kind of unlock the bootloader and then custom rom.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
Not yet, you can flash it but it is not yet bootable since I haven't figured out yet how to jump to recovery from the ramloader (you'll probably get an error 2 if you flash CWM then boot to recovery). After you reset your phone, rdl.bin gets cleared out so the same protection mechanisms are still in the bootloader. It's something I'm working on.
firtermish said:
I like what I m reading. Sounds like this would be the saving grace for those photon users stuck on an electrify rom (and yeah I m one of them!). Please let us know when you get to rewrite system with a custom rom with this method!
Click to expand...
Click to collapse
I already can. just do the following:
fastboot flash rdl.bin RDL3_unlocked.smg
fastboot erase system
fastboot flash system your_system_file.smg
fastboot erase boot
fastboot flash boot your_boot.smg
fastboot reboot
EDIT: file extension doesn't really matter, can be smg or img
Theres also updating from fastboot using a zip file, I'm not 100% sure if this works the same as in recovery:
update <filename> reflash device from update.zip
jortiz12885 said:
Will this be useful for the ones that flash the electrify rom on the photon?
Sent from my MB855 using XDA
Click to expand...
Click to collapse
Nope. I just tried and it doesn't work. I get error on phone like below.
1c10d60
SVF:106:1:2
sec_exception: b655, eddc, eb
Anyone knows what that is?
herach said:
Nope. I just tried and it doesn't work. I get error on phone like below.
1c10d60
SVF:106:1:2
sec_exception: b655, eddc, eb
Anyone knows what that is?
Click to expand...
Click to collapse
At what point did you receive the error?
scottgl9 said:
At what point did you receive the error?
Click to expand...
Click to collapse
After the Fastboot. It does Fastboot successfully but it gives the error on the phone screen.
herach said:
After the Fastboot. It does Fastboot successfully but it gives the error on the phone screen.
Click to expand...
Click to collapse
It looks like it is some sort of security error(possibly a failed sigcheck or something).
Lightsword1942 said:
It looks like it is some sort of security error(possibly a failed sigcheck or something).
Click to expand...
Click to collapse
I'm pretty sure the reason you're receiving this error is because this RDL is from derpunlock.sbf from photon_pudding.rar. I'll post the unlocked pudding electrify ramloader.
Attached is the unlocked pudding electrify ramloader, run:
fastboot flash rdl.bin RDL3_unlocked_electrify.smg
scottgl9 said:
I'm pretty sure the reason you're receiving this error is because this RDL is from derpunlock.sbf from photon_pudding.rar. I'll post the unlocked pudding electrify ramloader.
Attached is the unlocked pudding electrify ramloader, run:
fastboot flash rdl.bin RDL3_unlocked_electrify.smg
Click to expand...
Click to collapse
Tried that. It reboots the device and the device stays on Moto Logo Dual-core Screen with nothing written on it and nothing else works.
Hey guys, I can't seem to flash a kernel via fastboot.
Here's my info
Phone : Xperia Mini Pro
Root : Rooted
Bootloader : Unlocked
Android Version : 2.3.4 (but have tried with 4.0.4 too)
USB debugging on
MSC mode activated
Unknown souces : checked
LOG :
17/012/2012 14:12:13 - INFO - FASTBOOT Output:
sending 'boot' (4926 KB)...
FAILED (remote: Unrecognized command, bork!)
finished. total time: 0.000s
I'm trying to install CM9, I extracted boot.img
fastboot detects device but fails when trying to flash
Any ideas please?
(if you need more info, more than welcome)
Try to redownload the kernel,Maybe that will work Or try to use Flashtool to flash the kernel
Sent from my Xperia Mini using XDA Premium
Singgih4050 said:
Try to redownload the kernel,Maybe that will work Or try to use Flashtool to flash the kernel
Sent from my Xperia Mini using XDA Premium
Click to expand...
Click to collapse
I've tried several different kernels and I've tried with flashtool and Command Prompt
Mikeboss71 said:
I've tried several different kernels and I've tried with flashtool and Command Prompt
Click to expand...
Click to collapse
Do you have tried to install other kernel?
Sent from my Xperia Mini using XDA Premium
Singgih4050 said:
Do you have tried to install other kernel?
Sent from my Xperia Mini using XDA Premium
Click to expand...
Click to collapse
yeah i've tried to flash different kernels but still the same problem :/
which method you are using?
Try with my tool' in my signature
Sent from my WT19a using xda app-developers app
Did you unlock your bootloader via sony or via testpoint method?
Have you checked *#*#7378423#*#* and then Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, it's another problem...
To all the ppl who replied before - Did you even read the log?
Mikeboss71 said:
17/012/2012 14:12:13 - INFO - FASTBOOT Output:
sending 'boot' (4926 KB)...
FAILED (remote: Unrecognized command, bork!)
finished. total time: 0.000s
Click to expand...
Click to collapse
"Unrecognized command"
You need to use the following command:
Code:
fastboot flash boot boot.img
or
Code:
fastboot -i 0x0fce flash boot boot.img
Someguyfromhell said:
To all the ppl who replied before - Did you even read the log?
"Unrecognized command"
You need to use the following command:
Code:
fastboot flash boot boot.img
or
Code:
fastboot -i 0x0fce flash boot boot.img
Click to expand...
Click to collapse
But normally it should have worked, cause with flashtool it should work. Doesn't flashtool do same command like
Code:
fastboot flash boot boot.img
?
Mikeboss71 said:
Hey guys, I can't seem to flash a kernel via fastboot.
Here's my info
Phone : Xperia Mini Pro
Root : Rooted
Bootloader : Unlocked
Android Version : 2.3.4 (but have tried with 4.0.4 too)
USB debugging on
MSC mode activated
Unknown souces : checked
LOG :
17/012/2012 14:12:13 - INFO - FASTBOOT Output:
sending 'boot' (4926 KB)...
FAILED (remote: Unrecognized command, bork!)
finished. total time: 0.000s
I'm trying to install CM9, I extracted boot.img
fastboot detects device but fails when trying to flash
Any ideas please?
(if you need more info, more than welcome)
Click to expand...
Click to collapse
I believe it is a problem with your controller manager kernel. This can occur because of a problem with the remote connections with the driver files. Try flashing your ROM STOCK then do root and then try to apply the kernel
Sorry guys I've been away for a while so I've kinda had to put this on the back burner. but I'm back now
@daydu19
I've tried both methods, Flashtool and through Command Prompt using
Code:
fastboot flash boot boot.img
&
Code:
fastboot -i 0x0fce flash boot boot.img
but no joy
EDIT: I can't unlock my phone with testpoint because of the new securities, my phone is "12W27" :/
@mihahn
I'm not quite sure how I unlocked it I tried several ways, testpoint & sony, the weird thing is that I didn't think that either of them worked but I'm able to flash FTF files with flashtool and also Flashtool says that my bootloader is already unlocked...
Code:
Loader : S1_Loader_Root_773f - Version : R4A066 / Bootloader status : ROOTED
And lastly
Have you checked *#*#7378423#*#* and then Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, it's another problem...
Click to expand...
Click to collapse
It says that it is allowed
@xdevilium
Thanks, I'll try this out and let you know if that helps
EDIT: Nope, doesn't work either
@eltonpestana
I've flashed my device multiple times back to stock to 2.3.4 and 4.0.4, they're FTF files that I found on here but that was the only way I managed to get my phone to work again, When I tried flashing the kernels through fastboot, it came up the errors I mentioned and by so Bricked my phone...
The one thing I haven't tried yet is to use Sony PC companion to "reset" my phone (mainly due to my painfully slow internet connection) but I'm not sure that will do much good seeing as it will restore it to 4.0.4 making it impossible to root and I'll end up having to flash the other FTF again.. no?
is it possible to download a custom kernel as a FTF file and then flash it rather than going through fastboot?
because I can flash the stock kernels (that are in the FTF files) that I got
Worst case scenario are there any good ICS ROMS that will work with the stock kernel?
Try flashing stock ftf and then it should get work done.
Sent from my WT19i using xda app-developers app
---------- Post added at 05:58 PM ---------- Previous post was at 05:51 PM ----------
Apparently not . But cm 7.2 works with stock kernel.
Sent from my WT19i using xda app-developers app
I've already tried :/
thanks, CM 7.2 is gingerbread though, ICS is nicer
anyone?
Heres the new log
C:\Users\Mike\Desktop\fastboot>fastboot devices
YT9001KGWM&ZLP fastboot
C:\Users\Mike\Desktop\fastboot>fastboot -i 0xfce flash boot boot.img
sending 'boot' (4926 KB)...
FAILED (remote: Unrecognized command, bork!)
finished. total time: 0.001s
C:\Users\Mike\Desktop\fastboot>fastboot -i 0xfce flash boot boot.img
sending 'boot' (4926 KB)...
(bootloader) USB download speed was 2505kB/s
OKAY [ 2.030s]
writing 'boot'...
FAILED (remote: Unrecognized command, bork!)
finished. total time: 2.032s
C:\Users\Mike\Desktop\fastboot>fastboot -i 0xfce flash boot boot.img
sending 'boot' (4926 KB)...
(bootloader) Flash of partition 'boot' requested
(bootloader) S1 partID 0x00000003, block 0x00000280-0x000002e3
(bootloader) Erase operation complete, 0 bad blocks encountered
(bootloader) Flashing...
(bootloader) Flash operation complete
FAILED (unknown status code)
finished. total time: 1.005s
mihahn said:
But normally it should have worked, cause with flashtool it should work. Doesn't flashtool do same command like
Code:
fastboot flash boot boot.img
?
Click to expand...
Click to collapse
I wonder can anyone help me with this? I recently unlocked my bootloader (with wotanserver.com - test point method) and have since been trying out new kernels.
Unfortunately, I've had some problems with Sirkay's Advanced Stock .587 Kernel when I flash it. http://forum.xda-developers.com/showthread.php?t=1544513
I followed his flashing with flashtool instructions (standard procedure). My phone appears to boot up as normal at first, (the kernel's preinstalled CWM recovery works too) but after the initial boot logo & brightening screen that indicates CWM is present - the screen then just goes black with white LED on (with screen backlight v. slightly on) and nothing else happens, i.e. the phone is well and truly stuck.
The end result is that I have to flash back to the kernel I was previously using. There's nothing in the Flashtool log to suggest any problem with the flashing either, and there's been no problem flashing any .img or .sin files until now - so I assume I have all the correct drivers etc.
Am I overlooking something obvious here? Would be very glad to someone's opinion, this is driving me nuts!
Device: ST18i (unlocked bootloader)
ROM version: Iced Bean 2.1 [.587] - Can be used with any kernel (according to the author)
Baseband version: .77
I'm having problem flashing a kernel on my SK17i device on my Windows 7 32 bit. When I flash kernel using fasboot mode in my device, it says (error phone not rooted) but my phone is already rooted. I have CWM and superuser in my phone which means it is rooted. But it keeps saying (error phone not rooted) in flashtool using fastboot mode. I also have installed the S1 fastboot driver so my phone can enter fasboot mode. It really gets me frustrated because I wanna install a custom ROM on my phone for the first time. can someone help me?
ActuallyGab said:
I'm having problem flashing a kernel on my SK17i device on my Windows 7 32 bit. When I flash kernel using fasboot mode in my device, it says (error phone not rooted) but my phone is already rooted. I have CWM and superuser in my phone which means it is rooted. But it keeps saying (error phone not rooted) in flashtool using fastboot mode. I also have installed the S1 fastboot driver so my phone can enter fasboot mode. It really gets me frustrated because I wanna install a custom ROM on my phone for the first time. can someone help me?
Click to expand...
Click to collapse
can u post the log from flashtool ?
are u trying to flash custom kernel?
my guess is u doesn't unlock bootloader yet.
dont bother to reinstall driver even a thousand time, it aint gonna happen with locked bootloader.
Your phone is not rooted means you phone's bootloader is still locked! So stop trying to flash custom kernels and unlock the bootloader first. You need a unlocked bootloader to flash custom kernels.
Sent from my ST15i using xda app-developers app
ActuallyGab said:
I'm having problem flashing a kernel on my SK17i device on my Windows 7 32 bit. When I flash kernel using fasboot mode in my device, it says (error phone not rooted) but my phone is already rooted. I have CWM and superuser in my phone which means it is rooted. But it keeps saying (error phone not rooted) in flashtool using fastboot mode. I also have installed the S1 fastboot driver so my phone can enter fasboot mode. It really gets me frustrated because I wanna install a custom ROM on my phone for the first time. can someone help me?
Click to expand...
Click to collapse
Please read the pinned posts for all information and instructions to unlock bootloader if you want (but remember it voids warranty) :good:
an0nym0us_ said:
are u trying to flash custom kernel?
my guess is u doesn't unlock bootloader yet.
dont bother to reinstall driver even a thousand time, it aint gonna happen with locked bootloader.
Click to expand...
Click to collapse
My phone has now unlocked bootloader. It's already rooted. I am now using a custom music player via CWM and using root permission apps.
gouthamthemostwanted said:
Your phone is not rooted means you phone's bootloader is still locked! So stop trying to flash custom kernels and unlock the bootloader first. You need a unlocked bootloader to flash custom kernels.
Sent from my ST15i using xda app-developers app
Click to expand...
Click to collapse
It has already unlocked bootloader. I have a custom music player flashed in my phone via CWM and I have root permission apps in my phone so I'm pretty sure it has unlocked bootloader. My problem is that in flashtool when using fastboot mode and when I'm trying to flash custom kernel in my phone, it says (error: phone not rooted)
MoonBlade said:
can u post the log from flashtool ?
Click to expand...
Click to collapse
01/028/2012 21:28:48 - INFO - <- This level is successfully initialized
01/028/2012 21:28:48 - INFO - Flashtool Version 0.6.9.1 built on 2012-04-09 19:22:19
01/028/2012 21:28:48 - INFO - You can drag and drop ftf files here to start flashing them
01/028/2012 21:28:54 - INFO - Launching Fastboot Toolbox 1.0 by DooMLoRD
01/028/2012 21:28:54 - INFO - Device Status: FASTBOOT mode
01/028/2012 21:28:55 - INFO - Device connected in fastboot mode
01/029/2012 21:29:01 - INFO - Selected kernel (boot.img or kernel.sin): C:\Users\Gab\Desktop\boot.img
01/029/2012 21:29:01 - INFO - Flashing selected kernel
01/029/2012 21:29:01 - INFO - sending 'boot' (7262 KB)...
01/029/2012 21:29:01 - INFO - FAILED (remote: The Device must be rooted first)
01/029/2012 21:29:01 - INFO - finished. total time: 0.002s
01/029/2012 21:29:01 - INFO - FASTBOOT Output:
sending 'boot' (7262 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.002s
01/029/2012 21:29:01 - INFO - Please check the log before rebooting into system
01/029/2012 21:29:04 - INFO - Finished Fastboot Toolbox
(The kernel is rage kernel ICS and my OS in xperia mini pro is SK17i)
(and P.S. it is a rooted phone and has unlocked bootloader. I have already flashed a custom music player in my xperia via CWM and I have superuser and root permission apps working in my phone)
ActuallyGab said:
01/028/2012 21:28:48 - INFO - <- This level is successfully initialized
01/028/2012 21:28:48 - INFO - Flashtool Version 0.6.9.1 built on 2012-04-09 19:22:19
01/028/2012 21:28:48 - INFO - You can drag and drop ftf files here to start flashing them
01/028/2012 21:28:54 - INFO - Launching Fastboot Toolbox 1.0 by DooMLoRD
01/028/2012 21:28:54 - INFO - Device Status: FASTBOOT mode
01/028/2012 21:28:55 - INFO - Device connected in fastboot mode
01/029/2012 21:29:01 - INFO - Selected kernel (boot.img or kernel.sin): C:\Users\Gab\Desktop\boot.img
01/029/2012 21:29:01 - INFO - Flashing selected kernel
01/029/2012 21:29:01 - INFO - sending 'boot' (7262 KB)...
01/029/2012 21:29:01 - INFO - FAILED (remote: The Device must be rooted first)
01/029/2012 21:29:01 - INFO - finished. total time: 0.002s
01/029/2012 21:29:01 - INFO - FASTBOOT Output:
sending 'boot' (7262 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.002s
01/029/2012 21:29:01 - INFO - Please check the log before rebooting into system
01/029/2012 21:29:04 - INFO - Finished Fastboot Toolbox
(The kernel is rage kernel ICS and my OS in xperia mini pro is SK17i)
(and P.S. it is a rooted phone and has unlocked bootloader. I have already flashed a custom music player in my xperia via CWM and I have superuser and root permission apps working in my phone)
Click to expand...
Click to collapse
I would suggest to follow close this steps: http://wiki.cyanogenmod.com/wiki/Sony_Ericsson_Xperia_Mini_Pro:_Full_Update_Guide
If your phone is already unlocked, no damages. If not, you will have your issue fix.
I had the same problem and don't know how solved ut
Sent from my Live With Walkman using xda premium
Hmmmm......
1.Update Superuser Binary....
2.Install Titanium Backup To Fixed Root Error On Your Devices.....
3.Problem Should Be Solved....
Hey bro, I am facing with same problem, I have sk17i too. Did you solved problem, and if so, how did you solved it?
bokivaol said:
Hey bro, I am facing with same problem, I have sk17i too. Did you solved problem, and if so, how did you solved it?
Click to expand...
Click to collapse
how did you solved it?
jotacito said:
how did you solved it?
Click to expand...
Click to collapse
Read post #11 of this thread.....
ActuallyGab said:
01/028/2012 21:28:48 - INFO - <- This level is successfully initialized
01/028/2012 21:28:48 - INFO - Flashtool Version 0.6.9.1 built on 2012-04-09 19:22:19
01/028/2012 21:28:48 - INFO - You can drag and drop ftf files here to start flashing them
01/028/2012 21:28:54 - INFO - Launching Fastboot Toolbox 1.0 by DooMLoRD
01/028/2012 21:28:54 - INFO - Device Status: FASTBOOT mode
01/028/2012 21:28:55 - INFO - Device connected in fastboot mode
01/029/2012 21:29:01 - INFO - Selected kernel (boot.img or kernel.sin): C:\Users\Gab\Desktop\boot.img
01/029/2012 21:29:01 - INFO - Flashing selected kernel
01/029/2012 21:29:01 - INFO - sending 'boot' (7262 KB)...
01/029/2012 21:29:01 - INFO - FAILED (remote: The Device must be rooted first)
01/029/2012 21:29:01 - INFO - finished. total time: 0.002s
01/029/2012 21:29:01 - INFO - FASTBOOT Output:
sending 'boot' (7262 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.002s
01/029/2012 21:29:01 - INFO - Please check the log before rebooting into system
01/029/2012 21:29:04 - INFO - Finished Fastboot Toolbox
(The kernel is rage kernel ICS and my OS in xperia mini pro is SK17i)
(and P.S. it is a rooted phone and has unlocked bootloader. I have already flashed a custom music player in my xperia via CWM and I have superuser and root permission apps working in my phone)
Click to expand...
Click to collapse
Dial *#*#7378423#*#* in ur phone the go to service info->Configuration then tell me the rooting status.
Best Regards,
AJ
Sorry, bad post
I can't delete
Hi
I want Going back to stock for official Jelly Bean update and I followed this tutorial:
http://forum.xda-developers.com/showthread.php?p=36138808 # post36138808
I try to flash the recovery with the attached file: http://forum.xda-developers.com/showpost.php?p=35031493&postcount=25
fastboot flash recovery recovery.img
sending 'recovery' (4272 KB)...
OKAY [ 1.813s]
writing 'recovery'...
OKAY [ 1.609s]
finished. total time: 3.422s
fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.531s]
finished. total time: 0.531s
fastboot erase cache
erasing 'cache'...
OKAY [ 0.266s]
finished. total time: 0.266s
When I returned to the fastboot and I select "recovery" the phone gets stuck on the following picture: http://s13.postimage.org/6hy5sfs2f/IMG_20120530_193934_1.jpg (photo found on google on another device)
This is my configuration :
Desire X
--> Bootloader unlocked
PROTO PVT SHIP S-ON RL
HBOOT-1.24.0000
RADIO-1.12.40.03
eMMC-boot
Oct 30 2012,20:09:09
Android : 4.0.4
HTC sense 4.1
N° 1.18.401.3
API HTC SDK : 4.24
HTCExtension_403_1_GA_24
Kernel :
3.0.21-g6c11713
[email protected]#1
Radio : 10.21.40.06U_1.12.40.03
Build : 1.18.401.3 CL128557 release-keys
Anyone know why my recovery doesn't work ?
Have you tried another another links for recovery? or the one from hansoons kit?
you could have just bad luck and flash buggy one
btw your question is wrong, from what you said, recovery was flashed in ok way, so there must be something wrong with recovery you flashed
Eliastux said:
I want Going back to stock for official Jelly Bean update
I try to flash the recovery with the attached file: http://forum.xda-developers.com/showpost.php?p=35031493&postcount=25
When I returned to the fastboot and I select "recovery" the phone gets stuck on the following picture: http://s13.postimage.org/6hy5sfs2f/IMG_20120530_193934_1.jpg (photo found on google on another device)
Anyone know why my recovery can not be flashed?
Click to expand...
Click to collapse
Your recovery is flashed fine.
But why do you need to go to fastboot and recovery again when your aim is getting the JB update ?
Thank you for this quick answer !
mindlesSheep said:
Have you tried another another links for recovery? or the one from hansoons kit?
you could have just bad luck and flash buggy one
Click to expand...
Click to collapse
Okey I have tried this one :
http://forum.xda-developers.com/attachment.php?attachmentid=1618686&d=1357387592
fastboot.exe flash recovery stock_recovery.img
sending 'recovery' (4272 KB)...
OKAY [ 1.297s]
writing 'recovery'...
OKAY [ 1.641s]
finished. total time: 2.938s
fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.250s]
finished. total time: 0.250s
fastboot erase cache
< waiting for device >
erasing 'cache'...
OKAY [ 0.648s]
finished. total time: 0.650s
--> When I returned to the fastboot and I select "recovery" and now I see the same picture : http://s13.postimage.org/6hy5sfs2f/I...0_193934_1.jpg
And after 5 sec the phone reboot : Is it normal ?
mindlesSheep said:
btw your question is wrong, from what you said, recovery was flashed in ok way, so there must be something wrong with recovery you flashed
Click to expand...
Click to collapse
Ok I will edit my first post
mindlesSheep said:
or the one from hansoons kit?
Click to expand...
Click to collapse
Ok I try this immediately
ckpv5 said:
Your recovery is flashed fine.
But why do you need to go to fastboot and recovery again when your aim is getting the JB update ?
Click to expand...
Click to collapse
When I want to apply the Jelly Bean 2.20.401.5 update the phone reboot on the buggy recovery and the phone gets stuck on the same picture
ckpv5 said:
Your recovery is flashed fine.
But why do you need to go to fastboot and recovery again when your aim is getting the JB update ?
Click to expand...
Click to collapse
I thought I had to go back to stock recovery for the update of Jelly Bean I'm wrong?
Am I also wrong about the fact that we can apply the update without relock the bootloader?
Eliastux said:
I thought I had to go back to stock recovery for the update of Jelly Bean I'm wrong?
Am I also wrong about the fact that we can apply the update without relock the bootloader?
Click to expand...
Click to collapse
1. Must have stock recovery installed
2. Must have a complete stock ROM (nothing is deleted)
3. Not necessary to flash a stock boot.img but it is advisable to have one
4. Not necessary to relock bootloader
5. If no.4 still brings problem then relock the bootloader but you will lose all data when unlocking again.
Eliastux said:
Okey I have tried this one :
http://forum.xda-developers.com/attachment.php?attachmentid=1618686&d=1357387592
fastboot.exe flash recovery stock_recovery.img
sending 'recovery' (4272 KB)...
OKAY [ 1.297s]
writing 'recovery'...
OKAY [ 1.641s]
finished. total time: 2.938s
fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.250s]
finished. total time: 0.250s
fastboot erase cache
< waiting for device >
erasing 'cache'...
OKAY [ 0.648s]
finished. total time: 0.650s
--> When I returned to the fastboot and I select "recovery" and now I see the same picture : http://s13.postimage.org/6hy5sfs2f/I...0_193934_1.jpg
And after 5 sec the phone reboot : Is it normal ?
Click to expand...
Click to collapse
--> When I apply the update with this recovery, the phone boot on the recovery and I see the same picture and after 5 sec the phone shut down (no picture on the screen)... and the only way to boot after this is to remove/put the battery.
ckpv5 said:
1. Must have stock recovery installed
2. Must have a complete stock ROM (nothing is deleted)
3. Not necessary to flash a stock boot.img but it is advisable to have one
4. Not necessary to relock bootloader
5. If no.4 still brings problem then relock the bootloader but you will lose all data when unlocking again.
Click to expand...
Click to collapse
1 --> NOK
2 --> OK
3 --> I have to install first a stock recovery if I want to flash a stock boot.img...
4,5 --> OK not necessary
Thanks for your reply
Eliastux said:
or the one from hansoons kit?
Ok I try this immediately
Click to expand...
Click to collapse
I've tried to install TWRP 2.4.3.0 from the HTC Desire X All-In-One Kit (Hasoons kit) :
(I made it with command line because v2.1 of this tool is a little buggy :
astboot.exe flash recovery TWRP.img
< waiting for device >
sending 'recovery' (6158 KB)...
OKAY [ 5.680s]
writing 'recovery'...
OKAY [ 6.375s]
finished. total time: 12.055s
fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.563s]
finished. total time: 0.563s
fastboot erase cache
< waiting for device >
erasing 'cache'...
OKAY [ 1.834s]
finished. total time: 1.874s
--> When I returned to the fastboot and I select "recovery" and now I see the same picture !! ( the phone gets stuck ! )
Is the recovery of my phone bricked ?
Ok guys I found the solution ( after 4hours of research ! ) flashing my phone with this RUU : RUU_PROTO_U_ICS_40A_HTC_Europe_1.18.401.1_Radio_10.21.40.06U_1.10.40.23_release_295191_signed.exe
Unfortunately (grr) I was not able to use the RUU normally (maybe because my recovery was buggy, I had a signature error) and I follow theses steps to install it :
1) fastboot erase cache
2) fastboot oem rebootRUU
3) fastboot flash zip rom.zip --> the rom.zip was extracted from the RUU.exe
4) fastboot reboot-bootloader
5) fastboot reboot
After that I could make two consecutive updates ( 1.18.401.3 and Jelly Bean update )
I hope it can help others who have the same problem :good:
Hello guys,
I tried to root my sony xeperia z4 tablet+ lte and I followed this instruction:
theunlockr.com/2015/09/19/how-to-root-the-sony-xperia-z4-tablet
After I unlocked the bootloader and I did the following step:
"6. Type in the following command into the Command Prompt Window and press Enter:
fastboot flash boot boot.img"
C:\Users\Gmer07\Desktop>fastboot flash boot boot.img
target didn't report max-download-size
sending 'boot' (17056 KB)...
OKAY [ 0.390s]
writing 'boot'...
OKAY [ 0.167s]
finished. total time: 0.562s
does my tablet not start anymore... I dont know what to do.. I bought the tablet this week
syrius007 said:
Hello guys,
I tried to root my sony xeperia z4 tablet+ lte and I followed this instruction:
theunlockr.com/2015/09/19/how-to-root-the-sony-xperia-z4-tablet
After I unlocked the bootloader and I did the following step:
"6. Type in the following command into the Command Prompt Window and press Enter:
fastboot flash boot boot.img"
C:\Users\Gmer07\Desktop>fastboot flash boot boot.img
target didn't report max-download-size
sending 'boot' (17056 KB)...
OKAY [ 0.390s]
writing 'boot'...
OKAY [ 0.167s]
finished. total time: 0.562s
does my tablet not start anymore... I dont know what to do.. I bought the tablet this week
Click to expand...
Click to collapse
Android version ?
Firmware version ?
@AndroPlus kernel version?(make sure you downloaded the correct version for you tablet model: SGP 771 for the LTE)
Windows version
In command prompt Type fastboot Devices, if there is no number the windows driver not correctly installed
After unlocking the bootloader did you make a reboot ? (If so you should not enable MyXperia)
you better follow the advice on Androplus' website
There are different kernels for SONYs ROMs.
You should first update to the latest SONY ROM.
Then flash a recovery (also from Androplus) and then the latest kernel (aka boot.img, easier from recovery).
You also need to flash SuperSU - follow the instructions on Androplus' website.