Got my Z Ultra yesterday (£235 C6806) bargain!
I've rooted many a phone in the past and dealt with the dreaded S-OFF that HTC had but for the first time I actually had a brown trousers moment and I'm wondering if anyone could explain a couple of things for me?
I accidentally flashed a 4.4.2 ROM, this booted up but failed to connect to wifi and had a load of wierd issues, I then re-flashed the recovery img file which ended up in the device not booting, all i got was a colourful 'pacman roms' image. With enough manic button pushing I got back into recovery but found the USB mount storage option does not show the device up on my PC, Thank god its got an SD slot as without this I guess it would have been a flash to stock ordeal. I finally managed to install the 4.4.4 GPe Rom after getting into the recovery and now when I power up it has the usual 'google' logo.
So if I want to flash a ROM etc. I have to flash the .img file for a recovery? It's not permanent? Or should I have the recovery on there all the time?
Im assuming I will have fastboot access if required?
Thanks for any help just dont want to get into another panic attack with this thing!
Ed
Its not a HTC device , recovery is not flashed separate like on those devices.
You simply flash a SONY based kernel file with recovery in fastboot if you are right now on a SONY rom. And away you go. You will then be able to reboot in to recovery. After you flash a rom, the kernel and recovery will be changed out to what is included in the .zip file. :good:
Related
Hi,
I traded a phone with someone and the rom they had was acting up.. the Infected Rom (cdma verizon)... When I got the phone, I told him he could keep his SD card and I could keep mine.. i guess the P something image file was on there and now Im just rooted with Teamwin recovery and not able to flash any rom or restore the Infected rom i nandroid backed up.
I have fastboot 1.50 S On but unlocked
Now imma be at work and not have a working phone. This isn't cool. PLEASE GET BACK TO ME IF YOU CAN HELP peeps. I would really appreciate it.
I also tried the unlocking method all over again but the Java SDK wont install.. it tells me to disable my virus protection (I did) and then it says unable to install it. This is just a mess man.
stepinmyworld said:
Hi,
I traded a phone with someone and the rom they had was acting up.. the Infected Rom (cdma verizon)... When I got the phone, I told him he could keep his SD card and I could keep mine.. i guess the P something image file was on there and now Im just rooted with Teamwin recovery and not able to flash any rom or restore the Infected rom i nandroid backed up.
I have fastboot 1.50 S On but unlocked
Now imma be at work and not have a working phone. This isn't cool. PLEASE GET BACK TO ME IF YOU CAN HELP peeps. I would really appreciate it.
I also tried the unlocking method all over again but the Java SDK wont install.. it tells me to disable my virus protection (I did) and then it says unable to install it. This is just a mess man.
Click to expand...
Click to collapse
If you're interested in reverting back to completely stock, the RUU files are available at http://www.goo-inside.me/shooter/ruu . Both the PG86IMG.zip and the .exe files are available there.
Interesting the device is flashed to verizon, at least you mention the device is on CDMA verizon. The only issues I can forsee here will be 3G data/MMS might not work via Verizon if using a stock Sprint ROM.
Of course, these *might* work and they can also be *tweaked* but I doubt, out of the box, they will work. Phone calls and SMS should work over verizon using the stock sprint ROM.
Here is my usual lecture, reading this will save you a lot of time and headache, regarding flashing a ROM and kernels on the EVO 3D with hboot 1.5 and htc's unlock method:
Essentially, if you're looking to flash a kernel or ROM (which many times also include a kernel), there are three basic methods (two seem the easier) with hboot 1.50 and htc's unlock method:
1) For Kernel Flashing: From Android mode, using my application, Flash Image GUI. Put the kernel .zip file on your sdcard, select from inside the application and flash.
For ROM Flashing: Pull out the kernel file (usually named boot.img) out of the ROM .zip and push to sdcard. Flash using Flash Image GUI.
If you're away from a computer and want to flash any kernel, this is a great tool!
2) Load the custom recovery, NOT using the traditional method (reboot recovery, bootloader -> recovery, etc), but a specific method for Hboot 1.5. From the prompt use: fastboot boot c:\downloads\cwm-recovery.img.
This will temporarily boot the custom recovery image and the HTC unlock method will grant it write access to the boot partition while in this mode.
In this temporarily booted recovery mode, when a full ROM (with kernel included) is flashed, the kernel will flash correctly.
3) Boot into recovery using the traditional methods, reboot recovery, bootloader -> recovery, etc, and after the custom recovery has loaded, flash the ROM. Reboot into fastboot mode and then separately flash the kernel from the computer: fastboot flash boot c:\boot.img.
Downside to this method would be if a zImage is included instead of the boot.img for the kernel, won't flash correctly.
Being without a phone is rough now a days! Hope that helps and points in the right direction!
so sorry.. i meant to say CDMA Sprint.. i probably was so frustrated and typed verizon. I am about to read what you post completly.
Thank you so much for the reply! I purchased the GUI App from the market a few days ago and I wasnt sure if it would work on my phone because that PG86IMG.zip wasn't on the root of my SD card (it's on the other guy's sd card) I will try your method to flash a ROM.
I was able to get the Rom restored from the nandroid backup someone last night.. I still need a new rom because this one has touch screen problems. Thanks again
I got my DNA back in December, unlocked with S-ON, rooted, and flashed a lightly modified stock ROM. It's been super stable, so I figured I wouldn't mess with it, and I've been running it since.
Yesterday, I was trying to free up some space on my device by integrating updates of system apps through Titanium Backup, and it jacked stuff up pretty royally. I figured, this is a great chance to install a new Sense 5 ROM.
I went through TWRP, installed the new ROM, cleared data, and when it restarted, it hung at the white HTC screen. Undeterred, I tried again through recovery. Then through sideloading a different ROM. Then by restoring a backup, downloading a new ROM and trying through recovery. Then installing CWM instead of TWRP and trying that way. Then by sideloading through CWM.
Every single method by which I've tried to install a new ROM has resulted in the phone hanging indefinitely at the white HTC screen.
I have obviously searched repeatedly for a fix for the white screen issue, and while I can restore an old backup and get the phone running, I can't seem to find a solution that gets me up and running on a new ROM. I'd hate to go through all the work (my phone's been unusable since around 8 PM last night) and not come out of it with a new ROM.
Am I missing something? Maybe I should be installing a new kernel before installing the ROM?
you are s-on you must flash the kernel boot.img via fastboot then flash kernel modules via recovery
copy boot.img from rom.zip
in command prompt goto folder with boot.img and enter
fastboot flash boot boot.img
then create a flashable module.zip and flash via recovery or adb eacxh module into system folder or just s-off your device and re flash rom.zip
The best way to fix ur phone now is to go through RUU, first relock the bootloader through fastboot, then enter RUU again through fastboot nd run the RUU from ur pc, ur good to go.
The reason it's getting stuck thr is becoz the system partition isn't getting mounted
As soon as I typed "S-On" in that original post, I started getting suspicious that might be the problem, but none of the ROMs I was trying specifically mentioned the need to be S-Off. But that does make sense.
So I spent the afternoon getting it S-Off, which was a bit of a hassle, and now in about three minutes, I see if I can indeed flash a ROM. I feel pretty optimistic, though.
Update: Success. I am now a very happy person.
congrats hope you enjoy
now no need for anything special to flash roms or kernels.
Hello. As the title says, I need help flashing a recovery to my Sony Xperia Z Ultra (c8606) with unlocked bootloader. I have tried using FlashTool to flash the TWRP img file found on their website. I connect the phone to fastboot mode, click on Select Kernel to Flash, and select the file labeled: twrp-2.8.5.0-togari. The file flashes, but always softbricks my phone (The LED light flashes red when it is plugged in, and holding down the power button only causes the phone to vibrate briefly every couple seconds). This forces me to re-flash a FTF file (C6806_14.5.A.0.242_Customized USA.ftf) to unbrick. I have tried flashing other kernels (108_DualRec_Jackie099) and other FTF files (C6806_14.3.A.0.681 US_Unbranded.ftf), with the same result.
Can anyone tell me what the problem is and what do I do? I want TWRP recovery installed on my phone (preferably the one found on their website), but everything I have tried just bricks my phone.
Please help me!
Okay, this is a bit complicated TWRP must be flashed to the fota partition of the phone, either using the fastboot command "fastboot flash FOTAKernel image.img" or, if you have rooted your ZU, then install an app called Rashr, open it and install TWRP from the app, just follow the instructions BUT it is useless on stock roms because the stock kernel doesn't support loading a recovery from the fota partition, although all AOSP and CM based roms supports it and there also was a stock kernel that supported it, I have forgotten its name. You were trying to flash the recovery as the main kernel but the system obviously can't boot from it, that is the root of the problem, it would be perfect if it were working that way
Regards
If you're trying to flash recovery or kernels you can use rashr on the play store. If you want twrp download nuts flushable recovery and flash it with twrp manager on the play store.
Hi guys,
Just unlocked my bootloader and began the root process.
I followed part of this guide but without backing up my DRM keys. http://forum.xda-developers.com/z5-compact/general/summary-tutorial-root-sony-xperia-z5-t3360515
I flashed my kernel and the recovery O.K.
fastboot flash recovery recovery.img
flashboot flash boot boot.img
I've tried two versions of TWRP and two different versions of the kernel AndroPlus.
When performing fastboot reboot after flashing both files my phones LED blinks RED once and then does nothing.
Dramatic and scary. What can I do to fix this? When trying to boot without the cable in my phone just vibrates once and does nothing. Screen doesn't light up at all. I'm so worried.
MatMew said:
Hi guys,
Just unlocked my bootloader and began the root process.
I followed part of this guide but without backing up my DRM keys. http://forum.xda-developers.com/z5-compact/general/summary-tutorial-root-sony-xperia-z5-t3360515
I flashed my kernel and the recovery O.K.
fastboot flash recovery recovery.img
flashboot flash boot boot.img
I've tried two versions of TWRP and two different versions of the kernel AndroPlus.
When performing fastboot reboot after flashing both files my phones LED blinks RED once and then does nothing.
Dramatic and scary. What can I do to fix this? When trying to boot without the cable in my phone just vibrates once and does nothing. Screen doesn't light up at all. I'm so worried.
Click to expand...
Click to collapse
did you try to flash first the boot.img and after the recovery ?
acabreram said:
did you try to flash first the boot.img and after the recovery ?
Click to expand...
Click to collapse
I've tried another kernel and it's booting but hanging at the three dots. (bootscreen) been waiting a few minutes. hopefully it gets to system.
MatMew said:
I've tried another kernel and it's booting but hanging at the three dots. (bootscreen) been waiting a few minutes. hopefully it gets to system.
Click to expand...
Click to collapse
Ok yo can try this too
Y tried and working fine root & xposed
It's tus stock kernel but with the habilita to support root
Similar issue for me
I've had almost exactly the same issue today:
- I unlocked boatloader using Sony standard process
- I followed the steps under 'How to Install CM13' within CTXz's guide here
- After flashing the Kernel and THEN the TWRP, I reboot and the phone flashes red LED, then green, then off, then red and then stays on green for a while (screen is blank). My computer registers that there is a new connection by making a sound but doesn't show up any devices that I can see.
- Periodically, I get the device disconnection sound and the green LED goes off, then red comes on, then solid green again until next cycle.
- If I disconnect the cable, the LED goes off. When I try to turn the phone on without cable attached, it buzzes but does nothing - no LEDs. I can't tell whether it is on or not, except that doing hard reset with PWR+Vol.Up gives no reaction.
- When I re-attach cable normally, the red/green LED sequence starts immediately with no need to turn PWR on, which would suggest that the phone is perhaps on.
- I am able to get into bootloader as normal and fastboot registers the device just fine.
- There is no yellow LED
I started with Kernel AndroPlus v24 and TWRP 3.0.0.0.
Failing that, I tried Kernel v20. Then I tried AndroPlus' twrp-2.8.7.0-E5823-32.0.A.6.152.
Have also tried Kernels v20 and v21 with TWRP 3.0.0.0.
I haven't had any fast boot errors - all flashes come back 'OKAY'.
I'd be very grateful for any help? Have I missed something?!
update to my post above:
I used: 'fastboot boot recovery.img' and this fired up the Sony logo with white screen and blue LED. However, after 10 mins of waiting, there was no change in status and I still couldn't get into TWRP with pressing Vol buttons, even after several restarts and unplugging, replugging etc.
Then, I realised the stock ROM on my phone before this whole process was Lollipop 5.1.1 Build 32.0.A.6.200. So, I flashed older versions of the Kernel and TWRP. Now, I can boot into the ROM and use the phone (almost) as normal except, being plugged in, it keeps re-detecting the USB cable. I now also get the Sony boot screen followed by yellow LED.
If I don't touch anything, it boots into the ROM. However, if I press a Vol button while the yellow LED is on during boot, then it just resets.
Thus, I still cannot get into the TWRP interface. Perhaps I need a TWRP version that is specific to my build - the one I have is from AndroPlus website and refers to the previous build (twrp-2.8.7.0-E5823-32.0.A.6.152.img)?
okay, further update (to save someone replying!)
I managed to boot into the system using AndroPlus Kernel v05a (I had Lollipop build ###.200), but still couldn't get into any TWRP.
I then followed the general process explained in this thread, albeit had to do a heck of a lot of research to understand the detail that is omitted from that (otherwise very useful and concise) original post. For example:
- how to actually use Flashtool (installing drivers and then getting hold of the right firmware from within the program);
- the difference between Fastboot and Flashmode;
- having to plug in the phone while it is loaded into the system before then flashing the selected firmware with Flashtool and ONLY THEN unplugging, switching off and booting into Flashmode.
- loading up the system after flashing the Kernel and TWRP so that I connect to computer and re-copy the erased SuperSU .zip file back onto storage, and then re-booting into TWRP and how to flash a zip file with TWRP.
Having now got a stock Marshmallow firmware rooted, my next step is to go back to the original guide I was following and try to install Cyanogen!
Thank you to all the people who have posted help guides throughout this site so that I could piece together what I needed to do - even though it has still taken me about 30 hours of my life to learn all this!
Hopefully my experience might help someone else in due course...
robledog said:
okay, further update (to save someone replying!)
I managed to boot into the system using AndroPlus Kernel v05a (I had Lollipop build ###.200), but still couldn't get into any TWRP.
I then followed the general process explained in this thread, albeit had to do a heck of a lot of research to understand the detail that is omitted from that (otherwise very useful and concise) original post. For example:
- how to actually use Flashtool (installing drivers and then getting hold of the right firmware from within the program);
- the difference between Fastboot and Flashmode;
- having to plug in the phone while it is loaded into the system before then flashing the selected firmware with Flashtool and ONLY THEN unplugging, switching off and booting into Flashmode.
- loading up the system after flashing the Kernel and TWRP so that I connect to computer and re-copy the erased SuperSU .zip file back onto storage, and then re-booting into TWRP and how to flash a zip file with TWRP.
Having now got a stock Marshmallow firmware rooted, my next step is to go back to the original guide I was following and try to install Cyanogen!
Thank you to all the people who have posted help guides throughout this site so that I could piece together what I needed to do - even though it has still taken me about 30 hours of my life to learn all this!
Hopefully my experience might help someone else in due course...
Click to expand...
Click to collapse
I had the same problem and solution is as is written here.
I had to flash Stock Firmware Marshmallow via Flashtool. After this I flashed kernel(boot) and recovery without problems and yellow icon will displayed.
Don't want to warm up this kind of old thread, but I have exactly the same issue (E8523). Would any of you mind to post their (stock) ROM versions which finally worked? I tried almost every combination that came to my mind (Customized CE1 32.2.A.0.224 => v31, several LP versions => more or less 20 to 32...).
Currently after installing the MM I mentioned the stock kernel worked, but when I flash the AndroPlus kernel (fastboot flash boot /path/to/boot.img) it won't boot up, black screen, looks like no dtb found (doesn't even try to load). This is also the message I get when I try to boot this img via fastboot directly.
I am sure I am missing something really stupid (quite new to android devices), but what?
IGNNE said:
Don't want to warm up this kind of old thread, but I have exactly the same issue (E8523). Would any of you mind to post their (stock) ROM versions which finally worked? I tried almost every combination that came to my mind (Customized CE1 32.2.A.0.224 => v31, several LP versions => more or less 20 to 32...).
Currently after installing the MM I mentioned the stock kernel worked, but when I flash the AndroPlus kernel (fastboot flash boot /path/to/boot.img) it won't boot up, black screen, looks like no dtb found (doesn't even try to load). This is also the message I get when I try to boot this img via fastboot directly.
I am sure I am missing something really stupid (quite new to android devices), but what?
Click to expand...
Click to collapse
Pro tip: hold shift and right click inside folder with recover.IMG or voot.IMG to open command prompt from that folder. Then all you have to do is type fastboot flash boot boot.IMG. I suggest trying to put a custom recovery like twrp on and flashing the xpower ROM from that, it will give you everything in one package.
Edit: fwiw I'm pretty sure custom recoveries have been able to flash .IMG fils for a few years now but I've never actually tried it. Might be worth a shot.
Thanks, but I haven't found cmd.exe on my linux machine yet^^ (I suppose wineconsole is cheating )
I know how to flash *stuff* to my phone, but that *stuff* seems only to work if some specific version of stock rom was installed previously. My best guess is the bootloader changes and supports different dtb formats on every version.
Stock Marshmallow 6.0.1 Customized CE1 32.2.A.0.224 does _not_ work for installing any version of AndroPlus kernel (tried a few...). It fails at boot (does not even load system, probably dtb).
Just in case someone might run into similar issues: What finally worked was Stock MM 6.0.1 Customized DE 32.2.A.0.224 with AndroPlus v31. It seems to be some older release (?), it says R2C instead of R9C for Customized CE1.
I could not find this information anywhere on the net (maybe its me), so for those with a slow internet connection the above version should work. You don't have to actually boot it, flashing is enough.
Thanks for sharing the information in this tread, it really helped me to unbrick my phone!
I started with Lollipop on my brand new Z3C and tried to root using AndroPlusKernel v31 / TWRP 3.0. This resulted in a softbick state, only being able to boot in fastboot mode.
After many hours struggling, an upgrade to stock Marshmallow (E5823_32.2.A.0.224) did the trick. This somehow seems ta make the device ready for the new kernel and recovery (I guess it has to do with the partitions in the filesystem).
Anyway, from stock Marshmallow I could start all over and succeeded to flash a custom bootloader, recovery and now have the ability to flash any desired rom! Thanks again.
To updrade to stock MM I used the instructions in this thread:
[GUIDE][18th Dec][4Noobs] Flashing A FTF File Using Flashtool
To set up TWRP recovery I used the instructions in this thread:
[ROM][UNOFFICIAL][6.0.1][E5823/E5803] CyanogenMod 13 for the Sony Xperia Z5C [ALPHA]
The stock rom I used for my E5823 is "E5823_32.2.A.0.224_R1C_CIS Generic_1298-5167.ftf" from xperiablog.net
Since I'm a new registered member I can't post external links
Google it and you're set!
IGNNE said:
Just in case someone might run into similar issues: What finally worked was Stock MM 6.0.1 Customized DE 32.2.A.0.224 with AndroPlus v31. It seems to be some older release (?), it says R2C instead of R9C for Customized CE1.
I could not find this information anywhere on the net (maybe its me), so for those with a slow internet connection the above version should work. You don't have to actually boot it, flashing is enough.
Click to expand...
Click to collapse
I'm having the same problem, where did you get that MM stock version from?
And what do you mean by "you don't have to actually boot it"?
Search for XperiaFirm and Flashtool. There is plenty.
You don't have to start your freshly installed Stock Rom version "...". You just have to flash it (write it to your phone) Now you boot your phone in fastboot mode and flash your custom kernel and mod rom of your choice. Seems to be some incompatible whatever between not matching kernel versions and the "stuff" flashing installs (suspect sth like bootloader, but no idea).
I have flased boot.img nd recovery.img on android 7.1.1 z5 compact my phone won't pass the sony logo
any help ?
---------- Post added at 11:05 AM ---------- Previous post was at 10:54 AM ----------
starchild78 said:
I have flased boot.img nd recovery.img on android 7.1.1 z5 compact my phone won't pass the sony logo
any help ?
Click to expand...
Click to collapse
I've just discovered I can boot into twrp
anything I can do to fix this from there ?
Hello,
I started on a quest last week to try and make my long forgotten Xperia tablet z LTE SGP321 more user friendly.
I stopped using it after being frustrated by the bloatware and its lack of customisation.
So I thought flashing a custom rom might help and wanted a bit of a technological challenge. Boy do I feel like I've got one.
I used kingroot, which worked fine. I tried to install SuperSu but it wont update the binaries.
I've managed to unlock the bootloader (forgot to do the backup TA woops!).
I downloaded TWRP app, flashed pollux_windy to recovery. Now there doesn't seem to be a combination of keys that I can find to boot the sony xperia tablet Z into recovery?? Power and volume up or down or jamming both keys...nothing seems to work. I've found one forum post suggesting it isnt possible and that I need to flash a kernel which is where I'm getting stuck.
SO this is where I am now and was wondering if I should use CWM instead or if there is another way to open recovery?
My main aim is to completely clear the tablet hard drive and start again with a custom rom.
Thanks!
>>>>>>
NEW info
So i've managed to use the ADB to reboot into the boatloader. All that happens is a black screen. I want to try and flash CWM or TWRM but it doesnt seem to work.
Im beginning to think there's something strange about the sony xperia tablet z in that it doesnt have a bootloader in its stock firmware. i've seen something about using a Kernel approach but the guides are unclear.
Any help on flashing a CWM or TWRM into recovery would be much appreciated!!
harpix42 said:
Hello,
I started on a quest last week to try and make my long forgotten Xperia tablet z LTE SGP321 more user friendly.
I stopped using it after being frustrated by the bloatware and its lack of customisation.
So I thought flashing a custom rom might help and wanted a bit of a technological challenge. Boy do I feel like I've got one.
I used kingroot, which worked fine. I tried to install SuperSu but it wont update the binaries.
I've managed to unlock the bootloader (forgot to do the backup TA woops!).
I downloaded TWRP app, flashed pollux_windy to recovery. Now there doesn't seem to be a combination of keys that I can find to boot the sony xperia tablet Z into recovery?? Power and volume up or down or jamming both keys...nothing seems to work. I've found one forum post suggesting it isnt possible and that I need to flash a kernel which is where I'm getting stuck.
SO this is where I am now and was wondering if I should use CWM instead or if there is another way to open recovery?
My main aim is to completely clear the tablet hard drive and start again with a custom rom.
Thanks!
>>>>>>
NEW info
So i've managed to use the ADB to reboot into the boatloader. All that happens is a black screen. I want to try and flash CWM or TWRM but it doesnt seem to work.
Im beginning to think there's something strange about the sony xperia tablet z in that it doesnt have a bootloader in its stock firmware. i've seen something about using a Kernel approach but the guides are unclear.
Any help on flashing a CWM or TWRM into recovery would be much appreciated!!
Click to expand...
Click to collapse
Flash boot.img of any latest custom ROM with TWRP integrated.
Rootk1t said:
Flash boot.img of any latest custom ROM with TWRP integrated.
Click to expand...
Click to collapse
Thanks for your help. I thought I'd start simple and just try and flash TWRP to recovery.
i downloaded the latest TWRP pollux windy img and then used the command fastboot flash recovery twrp.img
It says FAILED (remote: command not allowed)
adb fastboot devices displays my tablet
(by the way in configuration in service info it says bootloader unlocked: Yes)
>>>>>>UPDATE
so i managed to flash a cyanogenmod img using "fastboot flash boot boot.img"
The device then soft bricked and went into a boot loop. Is this because I used the wrong version of cyanogenmod?? Any other I can try that work?
I panicked a bit, mamanged to get the tablet into fastboot somehow andthen flashed a TWRM img to the boot using the same command above which now loads TWRM.
fastboot reboot now caused the device to go into TWRP but its in recovery mood
How can i undo that step i did when I flashed the boot img of the cyanogen mod. I want to put the old boot.img back!
Rootk1t said:
Flash boot.img of any latest custom ROM with TWRP integrated.
Click to expand...
Click to collapse
also can I ask another quick question of you, what do you do to boot into recovery on your xperia tablet Z device?
Thanks!
Sorry about all the updates.
I decided to see what you had installed on your signature and tried resurrection remix. Version 5.8 caused Error 7??
So i went for version 6.9 which i installed successfully.
Only way i know how to get into recovery is to use adb terminal command "adb reboot recovery"
Also before I installed resurrection remix would you recommend a complete wipe of everything or does it not really matter?
Thanks and hopefully that's me all sorted!
Use VOL+ or VOL- on boot to enter recovery.
harpix42 said:
what do you do to boot into recovery on your xperia tablet Z device?
Click to expand...
Click to collapse
2 way for me:
- usually you can set an "advanced reboot menu" under developer option or the ROM customization panel (depends on which ROM do you use)
- turn off your tablet, now push the power button until your screen just turn on, leave the power button and start pressing vol+ and vol- alternately until you boot into recovery