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.
Related
Hello guys!
Im trying to change my stock kernel (2.3.3 stock rom) with the Paolo 2.6.35.14_v6-touch3 version (for overclocking purposes).
I have enabled Fastboot ok in my P500h phone (using this threads), and when i boot into it the screen show me:
Fastboot mode started
udc_start()
-- suspend --
-- reset --
-- portchange --
-- reset --
Click to expand...
Click to collapse
After that, i run a CMD command prompt (windows 7 x64) inside the "platform-tools" folder of the SDK, wich contains the fastboot.exe and the zImage too, and i put the following command:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash zimage
zImage
sending 'zimage' (2621 KB)...
OKAY [ 0.700s]
writing 'zimage'...
FAILED (remote: unknown partition name)
finished. total time: 0.744s
Click to expand...
Click to collapse
At this point i know that the zImage was send it successfuly to my P500h, but some problem occur with the "writing process". Can any of you help me with this?
Thanks a lot!!
Xmas comes Xmas comes...!
EDIT 1: I'm trying the "fastboot devices" command and the results on my CMD was this:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot devices
? fastboot
Click to expand...
Click to collapse
Is strange, because i already have the drivers updated correctly...What appears to them after you apply the command "fastboot devices"?
EDIT 2: I tried another way, using the command:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot boot recovery-ra-thunderg-3.06-gnm.img
downloading 'boot.img'...
OKAY [ 1.214s]
booting...
OKAY [ 0.239s]
finished. total time: 1.454s
Click to expand...
Click to collapse
and my P500 boot ok the recovery, but the menu doesnt work (with the volume key) and i cant enter to any option listed. With this way, i thought upgrading the kernel using the "zip method" (i refuse to install a permanent custom recovery) :[.
I thought the "FAILED (remote: unknown partition name)" bug appear because my P500 tries to write to the "zimage" partition...and that not exist. In which partition should I install?
EDIT 3: Hi Guys!, after the above...i decided to install the new kernel using the Custom Recovery but installed in my system (because the "live boot" doesn't work :[... too bad). So, i applied the following commands for doing that:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash recovery recovery-ra-thunderg-3.06-gnm.img
sending 'recovery' (4682 KB)...
OKAY [ 1.214s]
writing 'recovery'...
OKAY [ 1.286s]
finished. total time: 2.500s
Click to expand...
Click to collapse
and then...
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.085s
Click to expand...
Click to collapse
After that, my Custom Recovery works like a charm and now i have Franco Kernel for official 2.3.3 at [320,672]mhz with SmartAssV2 governor (upper frequencies hang up my P500h).
I hope we can discuss how to achieve "live boot" of recovery or flashing the kernel via Fastboot directly. Now, i dont know how uninstall the Custom Recovery (i never wanted permanently installed on my P500). Inside the Custom Recovery exist an option to "revert to de stock recovery" but doesn't work.
Best regards for all of you!
asrhael
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:
Hi.
After I've tried to install a custom rom, I've done a very big mistake. Now I can't boot the tab, and if I try to go in recovery or wipe data through fastboot i get the fatally error "unrecoverable bootloader error 0x00000000". I haven't any nvflash backup and have the JB bootloader (10.6.1.8). The only thing that works are the APX mode and the fastboot. I'm feeling a very idiot because i bought it yesterday.
Now, what can I do? Dump it and f**k myself? :crying:
Sorry for my bad english, thank you for your help.
I realized I'm screwed. But I've tried something...
When I go run the fastboot mode and delete a partition, for example:
Code:
fastboot erase recovery
works, and after I can run other command. But if I use:
Code:
fastboot flash recovery recovery.img
seems it works, in fact the output is
Code:
sending 'recovery' (5378 KB)...
OKAY [ 2.431s]
writing 'recovery'...
OKAY [ 1.739s]
finished. total time: 4.170s
but it's stucked and I need to reboot manually.
Any idea?
Kito92 said:
I realized I'm screwed. But I've tried something...
When I go run the fastboot mode and delete a partition, for example:
Code:
fastboot erase recovery
works, and after I can run other command. But if I use:
Code:
fastboot flash recovery recovery.img
seems it works, in fact the output is
Code:
sending 'recovery' (5378 KB)...
OKAY [ 2.431s]
writing 'recovery'...
OKAY [ 1.739s]
finished. total time: 4.170s
but it's stucked and I need to reboot manually.
Any idea?
Click to expand...
Click to collapse
I have the same. Im on an ICS bootloader due to having to run nvflash to get it back to that point.
I have fastboot access i can send a recovery image over to it (twrp 2.5 ics.img) however when i reboot it i dont see the recovery!
PLEASE PLEASE PLEASE Someone help
Hello. Today i tried to flash the phone to the stock ROM twice but it didnt work probably cause unlocked bootloader and custom recovery (TWRP).
So i brick the phone and now i cant access the rom or the recovery. All i can do is access the fastboot mode. I tried to install the new recovery through fastboot but it doesnt work.
I tried the twrp 3.0.2.0 and 3.0.1.0 for yuga.
Code:
C:\Users\Kubo\Downloads\platform-tools>fastboot flash recovery recovery.img
target didn't report max-download-size
sending 'recovery' (10704 KB)...
OKAY [ 0.342s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.347s
Tried various of commands that i found on google and this forum but nothing worked. I unlocked the bootloader before when i was installing various of custom roms. Could somehow stock rom affect the bootloader when i was flashing through flashtool ? I tried to only boot the recovery from the img, the command worked but the recovery did not boot.
Code:
C:\Users\Kubo\Downloads\platform-tools>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.341s]
booting...
OKAY [ 0.033s]
finished. total time: 0.378s
Tried to check the status of bootloader but the command is just showing ... and nothing happend. Tried to get the IMEI through fastboot getvar command but no output is given. Im desperate. Sorry for english not my native language. I'll appreciate all the help.
this is a message of the error that I have
my device is a tablet xperia z sgp311
C:\Users\4lph4\Appdata\Local\android\android-sdk\platform-tools>
fastboot devices
CB5A1U3D5J fastboot
fastbot flash recovery twrp-3.0.2-0-pollux_windy.img
Target didn't report max-download-size
sending 'recovery' (10688)
OKAY [ 0,343]
writing 'recovery'
FAILED (remote: Commnand not allowed)
finished, total time : 0.347
I want to use flashtool to do a relock and unlock again but I do not know if that would cause hard brick
novatosuper said:
this is a message of the error that I have
my device is a tablet xperia z sgp311
C:\Users\4lph4\Appdata\Local\android\android-sdk\platform-tools>
fastboot devices
CB5A1U3D5J fastboot
fastbot flash recovery twrp-3.0.2-0-pollux_windy.img
Target didn't report max-download-size
sending 'recovery' (10688)
OKAY [ 0,343]
writing 'recovery'
FAILED (remote: Commnand not allowed)
finished, total time : 0.347
I want to use flashtool to do a relock and unlock again but I do not know if that would cause hard brick
Click to expand...
Click to collapse
I got that problem too with an Experia tablet Z. I used the Xperia Companion's "repair" function (from sonys product support page) to restore my device that was unable to boot.
novatosuper said:
this is a message of the error that I have
my device is a tablet xperia z sgp311
C:\Users\4lph4\Appdata\Local\android\android-sdk\platform-tools>
fastboot devices
CB5A1U3D5J fastboot
fastbot flash recovery twrp-3.0.2-0-pollux_windy.img
Target didn't report max-download-size
sending 'recovery' (10688)
OKAY [ 0,343]
writing 'recovery'
FAILED (remote: Command not allowed)
finished, total time : 0.347
I want to use flashtool to do a relock and unlock again but I do not know if that would cause hard brick
Click to expand...
Click to collapse
tablet z doesn't have separate recovery partititon, so you have to use kernel with built-in recovery (fastboot flash boot twrp-3.0.2-0-pollux_windy.img)
or you can try to install it permanently to FOTA partition.
by typing: dd if=/sdcard/twrp-3.0.2-0-pollux_windy.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
is resolved thank you
is resolved thank you