Database Users

[GUIDE] How to Root the Samsung Galaxy Tab 10.1 [Video Walkthrough]

A big thanks to RoboBear, tphillips, Lorddeff07, and anyone else that has helped make this happen.
I try to make my guides simple and straightforward so that the average user can root their device. I show every detail and walk you through the process. This guide is a complete video walkthrough on how to root the Galaxy Tab 10.1 WiFi with edits based on the issues that some may run into with previous guides. Without further ado, let's get started!
LINK TO MOD EDITutdated links
◄●REQUIRED DOWNLOADS●►
Just download, do not install or run anything yet.
◄●Instructions●►
This method is done on Windows. I recommend this way as its the easiest. If you don't have Windows, borrow from a friend.
◄●Downloading Files and Installing Drivers●►
Download the I have linked.
Extract the zip file by right clicking and selecting "Extract All," or by using an extracting program of your choice.
Open the folder and double click the driver file labeled "GT-p7510_USB_Driver_v1_3_2360_0-Escape.exe"
Install the driver. Its pretty much just Next, Next, Install, and Exit when its done.
◄●Connecting the Device●►
Turn on USB Debugging by going to Settings>Applications>Development and checking USB debugging. Click Okay to confirm
Power off the device by holding the power button and selecting Power off
Put the device into Downloading mode
Hold the Vol Down button (the left Volume button) and then hold the Power button as well.
Keep holding until you see two icons. First you'll see the Samsung Galaxy Tab 10.1 logo and then the icons will show up. Let go.
Press the Vol Up button (the right Volume button) to select Downloading mode.
Connect the device to your computer with the USB cable.
◄●Flashing a Custom Recovery●►
Go into the same root folder as before.
Double click the root application named "Odin3_v1.85.exe"
Select PDA
Double click the clockworkmod recovery file labeled "recovery-cwm_4.0.0.4-sam-tab-10.1.tar.md5" to select it.
Click Start
Once it is complete, you can close the program
◄●Completing the Root●►
Disconnect your USB cable
On your device, turn off USB Debugging by going to Settings>Applications>Development and unchecking USB debugging
Plug your USB cable back in
On your computer, go to the same root folder as before and transfer the zip file labeled "Samsung_Galaxy_Tab_10.1_root.zip" to your device. Don't put it inside any folder.
Confirm that it was transferred by clicking inside the device folder
Power off the device by holding the power button and selecting Power off
Put the device into Recovery mode
Hold the Vol Down button (the left Volume button) and then hold the Power button as well.
Keep holding until you see two icons. First you'll see the Samsung Galaxy Tab 10.1 logo and then the icons will show up. Let go.
Press the Vol Down button (the left Volume button) to highlight the left icon.
Press the Vol Up button (the right Volume button) to select Recovery mode.
You should see that you are in ClockworkMod Recovery. If not, start over
Use the volume buttons to highlight "Install zip from SD card" and hit the Power button to select it.
Use the volume buttons to highlight "Choose zip from SD card" and hit the Power button to select it.
Use the volume buttons to highlight "Samsung_Galaxy_Tab_10.1_root.zip" and hit the Power button to select it.
Use the volume buttons to highlight "Yes - Install..." and hit the Power button to select it.
When it finishes, the last line should say "Install from sdcard complete."
Use the volume buttons to highlight "*****Go Back*****" and hit the Power button to select it.
Hit the Power button to select "reboot system now"
Your device will reboot
You're now rooted!

Excellent Guide.
Thank you.
This one is Noob-Safe

I love how you have proper grammar and punctuation skills. Spacing is good, fonts are bold where they need to be, this is how a guide should look!
All guides should be written like this, can u offer classes for the uneducated?

EyeAndroid said:
I love how you have proper grammar and punctuation skills. Spacing is good, fonts are bold where they need to be, this is how a guide should look!
All guides should be written like this, can u offer classes for the uneducated?
Click to expand...
Click to collapse
Would there be a higher demand for that than my guides? lol. But thanks a lot, I appreciate it Just trying to make it easy for everyone.

Wow. A guide that is easy to follow, in plain and understandable English, and thorough!
Thanks a lot! I'll be following this when I get my Tab this week.

perfect instructions! Thanks!

just rooted this way. It was the easiest root I have ever done!
I have rooted two different androids and the rooted process took really long on my other phones. This took me the same amount of time as your video.
Very good guide.

1,000,000 points for not hosting your files on one of the uber-annoying file hosting sites. I used your video to root my EVO phone as well, have been waiting for your guide for the 10.1. great job....

All done, started after posting my thanks and now I am all rooted..(sp?) Just need an Easy Button boot screen after the root.

Perfect guide

Does this work with 16GB WIFI UEKME 3.1 tab?

djR3Z said:
A big thanks to RoboBear, tphillips, Lorddeff07, and anyone else that has helped make this happen.
I try to make my guides simple and straightforward so that the average user can root their device. I show every detail and walk you through the process. This guide is a complete video walkthrough on how to root the Galaxy Tab 10.1 WiFi with edits based on the issues that some may run into with previous guides. Without further ado, let's get started!
Click to expand...
Click to collapse
Thanks for the detail root instruction, it is very clear easy to understand (I have clicked the thank button).
Question: Just want to confirm whether this root method only applied to wifi only tab or applied to all wifi and 3G tab and with different version.

bdejong11129 said:
1,000,000 points for not hosting your files on one of the uber-annoying file hosting sites. I used your video to root my EVO phone as well, have been waiting for your guide for the 10.1. great job....
Click to expand...
Click to collapse
Haha yeah I hate that too, which is why I will always host files myself. But thanks a lot man, I really appreciate the support.
yongck7 said:
Thanks for the detail root instruction, it is very clear easy to understand (I have clicked the thank button).
Question: Just want to confirm whether this root method only applied to wifi only tab or applied to all wifi and 3G tab and with different version.
Click to expand...
Click to collapse
Unfortunately this is just for the Wifi only version. I could probably make a written guide for the others, but I don't have the devices to support that. Sorry dude.

Moderator, please make this sticky !!!
Thx.

MagicOnline said:
Moderator, please make this sticky !!!
Thx.
Click to expand...
Click to collapse
Ohhh, that'd be nice Hopefully I can get my hands on a 3G and 4G version. Someone PM'd me that this worked on their 3G but their gtab is now unlocked so hopefully I can figure that out blind

Sticky this thread!

Boot loop and no recovery mode ability
Sorry in advance for the long thread.
Great documentation. I hope you can help me. I posted the below at the stickied root thread but I haven't received any responses. It seems I blew away recovery mode. My tablet consistently boot loops. I have the option to choose recovery but when selected the screen goes blank for several seconds then reboots. I can get into download mode but my PC doesn't recognize the hardware and will not install the proper Samsung drivers. After reading your thread I'm wondering if this is because I didn't set debugging mode properly.
"Hi all I need some help. Verizon LTE 10.1 tab is boot looping after attempting bone head maneuver. Attempted root per Lorddeff07's method. Installed recovery file, system rebooted. Installed kernel file, system rebooted. Installed clockwork mod premium from market. Installed clockwork mod recovery for galaxy tab. Initiated backup via cwm, system rebooted and started boot looping. I can get into downloading mode but when I try to access recovery mode the tablet starts to boot loop.
I tried odin but the USB drivers are not installing properly. If I force the driver to install as Samsung ADB the tablet will display "start odin" when in downloading mode. However the odin app does not recognize the tablet. I'm running W7 pro Sp1 x64.
I also tried to use nvflash per shep211's tutorial but that didn't work. I get to section 2 step 17 when the command fails and the tablet will disconnect from the PC.
I know there has to be a way to fix my fUP. can anyone asist?"
FIXED: Removed the Verizon SIM card. Booted into download mode. Manually added the unrecognized driver as Samsung Mobile USB Serial Port. Opened odin flashed the ltecwm.tar.md5 file. Rebooted. All is good. Rebooted into recovery and installed root using Samsung_Galaxy_Tab_10.1_root.zip. Everything is up and running.

Thank you so much nice eay guide just rooted my tab thanks to you!!1 I pass you a beer sir

jobless said:
Sorry in advance for the long thread.
Great documentation. I hope you can help me. I posted the below at the stickied root thread but I haven't received any responses. It seems I blew away recovery mode. My tablet consistently boot loops. I have the option to choose recovery but when selected the screen goes blank for several seconds then reboots. I can get into download mode but my PC doesn't recognize the hardware and will not install the proper Samsung drivers. After reading your thread I'm wondering if this is because I didn't set debugging mode properly.
"Hi all I need some help. Verizon LTE 10.1 tab is boot looping after attempting bone head maneuver. Attempted root per Lorddeff07's method. Installed recovery file, system rebooted. Installed kernel file, system rebooted. Installed clockwork mod premium from market. Installed clockwork mod recovery for galaxy tab. Initiated backup via cwm, system rebooted and started boot looping. I can get into downloading mode but when I try to access recovery mode the tablet starts to boot loop.
I tried odin but the USB drivers are not installing properly. If I force the driver to install as Samsung ADB the tablet will display "start odin" when in downloading mode. However the odin app does not recognize the tablet. I'm running W7 pro Sp1 x64.
I also tried to use nvflash per shep211's tutorial but that didn't work. I get to section 2 step 17 when the command fails and the tablet will disconnect from the PC.
I know there has to be a way to fix my fUP. can anyone asist?"
FIXED: Removed the Verizon SIM card. Booted into download mode. Manually added the unrecognized driver as Samsung Mobile USB Serial Port. Opened odin flashed the ltecwm.tar.md5 file. Rebooted. All is good. Rebooted into recovery and installed root using Samsung_Galaxy_Tab_10.1_root.zip. Everything is up and running.
Click to expand...
Click to collapse
Glad you got it fixed! Did you use the Samsung_Galaxy_Tab_10.1_root.zip in my pack or from the LTE section in lord's thread?

I used the Samsung_Galaxy_Tab_10.1_root.zip that you provided.

[TUT][i9001] HOW TO UNBRICK YOUR SOFTBRICKED I9001

Soft bricking often happens in when you try to install a ROM which is not optimized for your phone e.g:Installing i9100 SII ROM on your i9001.
Here is a basic tutorial on how to unbrick a i9001.
Requirements:
For unbricking your phone you are going to need these:
1.An official Samsung firmware
2.ODIN downloader
3.AriesVE.ops for ODIN usage.
4.USB cable
5.Samsung KIES drivers installed
6.Patience!!!
OK.first of all you need to check things above and make sure you have them all.
Fortunately when your phone is soft bricked(when soft bricked your phone doesn't boot into the OS And instead of that you'll see picture of a phone connected to a computer and on the connection line there's a warning sign) can get yo the download mode. So first get your phone in download mode by pressing this button combination: volume down+ home key+ power button
So then get set to use ODIN.
Connect your phone to the PC and make sure you have installed drivers and also killed every KIES process.(If you have done well till now you can see one black gets yellow and in Terminal you'll see 2 lines "detected","added") So start ODIN and place AriesVE.ops as the ops file then use your official firmware (extension should be like this |..... .tar.md5|).To get your firmware working tick "one package" and place you "MD5" file in "one package" location. Then after MD5 checking start the process and go grab a beer.
Wait about 7 to 10 minutes to see PASS on the block.
Then your phone would automatically reboot into your android OS. Then you can start rooting, Tweaking and other stuff again.
At least one you have your phone and your warranty back.
FAQs:
1.my phone gets stuck at setup connection. what should I do?
Chill out! Don't panic! Simply remove your battery for 10 seconds then do these things all again and proceed!
2.my phone boot loops what do I do?
Simply reboot your phone in the Recovery mode "volume down+ power" and wipe cache/dalvik cache if you can.
(Once I installed FOTA from stock recovery and that worked for me)(I suggest you install the official TWRP recovery from SDcard to have more options)
3.you tell me your questions!I'll edit the topic later!
At last feel free to ask any dumb question. Dumb questions are muck more valuable than dumb mistakes!
Please hit thanks button if I helped you out!
Sent from my GT-I9001 using xda premium

[Q] Please help guys

I have installed 4.2.2 on nexus 7. As I had skipped account login at welcome screen, i could not login the account. I altered the apk of login. After factory reset my device has hanged on setup on welcome screen. I tried installing custom rom through stock bootloader but the bootloader says installation failed. How do I solve thia problem guys???

subin.nexus7 said:
don't know the exact steps, but i got it out of the APX mode and into the bootloader.
1. Tablet plugged into computer.
2. Held Volume Down + Volume Up + Power (simultatenously) for three seconds
3. And then released all, and pressed Power again.
4. Tablet booted into bootloader.
I thought that unlocking the bootloader ALWAYS voided the warranty, but in anycase I flashed reflashed ALL stock and locked the bootloader. Will be sending it to ASUS now. Thanks again!
EDIT:
So I wanted to verify that it was a CPU problem, and I downloaded StabilityTest again and ran the CPU load test. It crashed within two minutes, and went into AXP mode again. To get it out of AXP mode, the correct instructions:
1. Plug in the usb into computer
2. Hold Volume Down + Volume Up + Power simultaneously for like 15 seconds
3. The bootloader should show up.
4. If it doesn't, unplug the usb cable, and plug it back in and then repeat the these procedures.
Click to expand...
Click to collapse
Very helpful! I don't have a problem but I've read about others stuck in APX mode. This should be pinned if it works for those stuck in APX. Maybe you should change the thread title to something about APX solution so it draws some attention.

kieso said:
Very helpful! I don't have a problem but I've read about others stuck in APX mode. This should be pinned if it works for those stuck in APX. Maybe you should change the thread title to something about APX solution so it draws some attention.
Click to expand...
Click to collapse
Well... being stuck in APX doesn't necessarily mean your hardbricked. (Corrupt or erased bootloader).
But being hardbricked DOES mean your device will default to APX mode.
To use a mathematical metaphor, one is a SUBSET of the other.
-------
bftb0 has posted an exhaustive list of Nexus 7 button press combos here...
http://forum.xda-developers.com/showthread.php?t=2133986
... which includes how to pro-actively get into APX mode... although until somebody figures how to nvFlash the N7, APX is sort of redundant.
Rgrds,
Ged.

Delete

subin.nexus7 said:
I have installed 4.2.2 on nexus 7. As I had skipped account login at welcome screen, i could not login the account. I altered the apk of login. After factory reset my device has hanged on setup on welcome screen. I tried installing custom rom through stock bootloader but the bootloader says installation failed. How do I solve thia problem guys???
Click to expand...
Click to collapse
I'm sort of confused about the relationship between your edited post and what (apparently ?) kieso quoted, but I'll throw out a few suggestions:
1) AFAIK, there is no way to flash a dev ROM using fastboot (only the boot image of a dev ROM can be flashed this way). You said "bootloader", not "custom recovery" ... so that implies using fastboot. If that is not the case, then your use of terminology is not correct. (It's a computer - reporting details correctly is incredibly important).
2) If you bypass the WiFi login, an account can be added at any time later using the settings menu or simply by launching the Google Play (market) app - there is no need to "alter the apk of login", whatever that means.
3) I would recommend at this point that you start completely over by flashing a factory ROM using fastboot - see the sticky thread about returning to stock using fastboot. If you already have the 4.18 bootloader installed, I recommend you avoid like the plague any operation involving flashing the bootloader.
4) It should be obvious from the trouble that you got yourself into that you should learn what nandroid backups are and that you START USING THEM. The first thing you do after rooting is "make a backup", not "flash a ROM"
good luck

Thanq so much.But still some clarification needed
Now What do I do? My nexus 7 can't pass through at welcome screen saying saying unfortunately setup wizard has stopped. and in recovery{i have no custom recovery, I use bootloader 4.18} i cant flash any rom. I just want to start device any how.. any way.. Is there any way??

subin.nexus7 said:
Now What do I do? My nexus 7 can't pass through at welcome screen saying saying unfortunately setup wizard has stopped. and in recovery{i have no custom recovery, I use bootloader 4.18} i cant flash any rom. I just want to start device any how.. any way.. Is there any way??
Click to expand...
Click to collapse
I guess I am having trouble understanding the sum total of information you have provided - I guess you have omitted some information or mis-stated something. No custom recovery sort of implies a full stock device, but yet you previously mentioned modifying/changing an .apk in /system... normally that would be possible only with a rooted ROM or a custom recovery to do that.
If your tablet is 100% stock, a factory reset of the tablet should allow you to boot once again - at the cost of deleting everything you put on the device, including all files you put on the (pseudo-) SD card.
If that is the case:
- press and hold power+vol-down until the bootloader screen shows up
- use vol-up/vol-down to select "start recovery" and press the power button
- an android lying on it's back should show up; this is the stock recovery splash screen, so
- press power+vol-up simultaneously for about one second - the stock recovery menu should show up
- select factory reset (with vol-up/vol-down) and press the power button.
good luck

bftb0 said:
I guess I am having trouble understanding the sum total of information you have provided - I guess you have omitted some information or mis-stated something. No custom recovery sort of implies a full stock device, but yet you previously mentioned modifying/changing an .apk in /system... normally that would be possible only with a rooted ROM or a custom recovery to do that.
If your tablet is 100% stock, a factory reset of the tablet should allow you to boot once again - at the cost of deleting everything you put on the device, including all files you put on the (pseudo-) SD card.
If that is the case:
- press and hold power+vol-down until the bootloader screen shows up
- use vol-up/vol-down to select "start recovery" and press the power button
- an android lying on it's back should show up; this is the stock recovery splash screen, so
- press power+vol-up simultaneously for about one second - the stock recovery menu should show up
- select factory reset (with vol-up/vol-down) and press the power button.
good luck
Click to expand...
Click to collapse
when you say at the cost of deleting everything, does this include deleting everything in the bootloader because thats what I did when I used the command "fastboot erase bootloader"

[Q] Secure Boot Error, No Download Mode, No Fastboot, No Regular Boot.

Hello all!
Just a newbie here, but hopefully I don't break any forum rules.
Now, to the problem at hand. I have an LG D802 that cannot be booted normally, cannot be brought into fastboot or download mode.
When trying to power on, I get greeted with "boot verification error / secure boot error".
This happened after trying to flash the "Cloudy G2 3.0" (lollipop version) ROM onto my phone via TWRP. Everything seemed to be in working order until
I had rebooted the device. I think the problem stemmed from the fact that I didn't read that the ROM was only for a different variant of my phone.
I have had a look at one post ( http://forum.xda-developers.com/showthread.php?t=2582142 ) but found it too hard to actually follow the instructions,
so now, I am here, writing this post.
Please feel free to ask for any additional information!
Thank you in advanced.

bryyyyy said:
Hello all!
Just a newbie here, but hopefully I don't break any forum rules.
Now, to the problem at hand. I have an LG D802 that cannot be booted normally, cannot be brought into fastboot or download mode.
When trying to power on, I get greeted with "boot verification error / secure boot error".
This happened after trying to flash the "Cloudy G2 3.0" (lollipop version) ROM onto my phone via TWRP. Everything seemed to be in working order until
I had rebooted the device. I think the problem stemmed from the fact that I didn't read that the ROM was only for a different variant of my phone.
I have had a look at one post ( http://forum.xda-developers.com/showthread.php?t=2582142 ) but found it too hard to actually follow the instructions,
so now, I am here, writing this post.
Please feel free to ask for any additional information!
Thank you in advanced.
Click to expand...
Click to collapse
Guy, guy, guy..... It's clearly write in the FAQ section of CloudyG2 3.0 that the rom is ONLY for F320' series, but no, you still want to flash it in D802.. Anyway, do you have access to recovery mode? Key combination might be power key + volume down until LG logo appears, then those keys again or power key + volume down until lg logo, then volum down + volume up.
For download, try a simple thing: Press your power key for ~1 / 1min30, just to be sure it's poweroff, and then try volume up + plug USB cable

casual_kikoo said:
Guy, guy, guy..... It's clearly write in the FAQ section of CloudyG2 3.0 that the rom is ONLY for F320' series, but no, you still want to flash it in D802.. Anyway, do you have access to recovery mode? Key combination might be power key + volume down until LG logo appears, then those keys again or power key + volume down until lg logo, then volum down + volume up.
For download, try a simple thing: Press your power key for ~1 / 1min30, just to be sure it's poweroff, and then try volume up + plug USB cable
Click to expand...
Click to collapse
Yes... I know. Was very silly in doing so. I have no access to recovery mode using both of those methods you have stated. When trying to get into the download mode for the phone, I get the same error, it will say, secure boot error etc. then the screen will go black, and a bunch of drives pop up on my computer, from [A] - [K], and windows asks me to reformat all of them.

Update: When plugging device into computer, it says QHSUSB_BULK. Hopefully that helps a bit

(help) yotaphone 2 brick after update

Last week, my yotaphone 2 informed that there is a system update from yotaphone. I downloaded and updated but then my phone cannot work. It show only black start screen with word "Android" until battery empty.
I tried to android recovery mode (hold power and volume up),
it show that the error is "e:cannot load volume /misc!".
And I do not know how to solve that problem.
Please help me!

leviet4 said:
Last week, my yotaphone 2 informed that there is a system update from yotaphone. I downloaded and updated but then my phone cannot work. It show only black start screen with word "Android" until battery empty.
I tried to android recovery mode (hold power and volume up),
it show that the error is "e:cannot load volume /misc!".
And I do not know how to solve that problem.
Please help me!
Click to expand...
Click to collapse
You can probably recover.
To reflash a full firmware image you could try the relatively user-friendly yotaflasher application and ROM images from here. I haven't used this myself, but it's software by Yota, so should be safe. You can ask it not to touch /data, to preserve apps, settings etc.
A less user friendly way to reflash a full firmware image:
- Download a full firmware image (EU 1.60 flashable version here, let me know if you require a different one)
- With the phone off, press vol down + power until you see "Downloading ...."
- If you can't turn the phone off normally, keep vol down + power for at least 15 seconds till phone reboots, keep holding till you end up with "Downloading ...."
- connect to a PC with adb+fastboot with a USB cable
- You can now boot TWRP image (fastboot boot recovery_twrp_yd201_alpha2.img , see here.
- if you have important files on your phone, you can back them up now by using adb shell/adb pull (e.g. adb pull /sdcard/Pictures/yeti_sighting.jpg)
- In TWRP go to advanced -> sideload and confirm
- now you can sideload a ROM image from the PC with adb sideload <image>.zip, it should show progress while it's uploading the firmware. If it errors, you probably haven't confirmed initiating sideload in previous step.
- wipe cache&dalvik and reboot

thank you, the first way worked and my phone runs normally now.
thank you

Help please
SteadyQuad said:
You can probably recover.
To reflash a full firmware image you could try the relatively user-friendly yotaflasher application and ROM images from here. I haven't used this myself, but it's software by Yota, so should be safe. You can ask it not to touch /data, to preserve apps, settings etc.
A less user friendly way to reflash a full firmware image:
- Download a full firmware image (EU 1.60 flashable version here, let me know if you require a different one)
- With the phone off, press vol down + power until you see "Downloading ...."
- If you can't turn the phone off normally, keep vol down + power for at least 15 seconds till phone reboots, keep holding till you end up with "Downloading ...."
- connect to a PC with adb+fastboot with a USB cable
- You can now boot TWRP image (fastboot boot recovery_twrp_yd201_alpha2.img , see here.
- if you have important files on your phone, you can back them up now by using adb shell/adb pull (e.g. adb pull /sdcard/Pictures/yeti_sighting.jpg)
- In TWRP go to advanced -> sideload and confirm
- now you can sideload a ROM image from the PC with adb sideload <image>.zip, it should show progress while it's uploading the firmware. If it errors, you probably haven't confirmed initiating sideload in previous step.
- wipe cache&dalvik and reboot
Click to expand...
Click to collapse
I have yotaphone model YD206, but I am in the USA and would like to root and load the best rom I can for my device, it doesn't even have google apps on it. Thanks for any and all help

Kevinreid1 said:
I have yotaphone model YD206, but I am in the USA and would like to root and load the best rom I can for my device, it doesn't even have google apps on it. Thanks for any and all help
Click to expand...
Click to collapse
Root the phone using methods written on this forum > download build 1.60 flammable zip > flash that.
If all you want is Google apps then root the phone then download and flash a gapps package. The full Yota build zip is recommended though.

Can't download yotaflasher application from the link... does anybody have the exe file?
SteadyQuad said:
You can probably recover.
To reflash a full firmware image you could try the relatively user-friendly yotaflasher application and ROM images from here. I haven't used this myself, but it's software by Yota, so should be safe. You can ask it not to touch /data, to preserve apps, settings etc.
A less user friendly way to reflash a full firmware image:
- Download a full firmware image (EU 1.60 flashable version here, let me know if you require a different one)
- With the phone off, press vol down + power until you see "Downloading ...."
- If you can't turn the phone off normally, keep vol down + power for at least 15 seconds till phone reboots, keep holding till you end up with "Downloading ...."
- connect to a PC with adb+fastboot with a USB cable
- You can now boot TWRP image (fastboot boot recovery_twrp_yd201_alpha2.img , see here.
- if you have important files on your phone, you can back them up now by using adb shell/adb pull (e.g. adb pull /sdcard/Pictures/yeti_sighting.jpg)
- In TWRP go to advanced -> sideload and confirm
- now you can sideload a ROM image from the PC with adb sideload <image>.zip, it should show progress while it's uploading the firmware. If it errors, you probably haven't confirmed initiating sideload in previous step.
- wipe cache&dalvik and reboot
Click to expand...
Click to collapse

glax87 said:
Can't download yotaflasher application from the link... does anybody have the exe file?
Click to expand...
Click to collapse
Just click on the YotaPhoneFlasher folder then click the file (yotaphone2_flasher.exe), and save to your harddisk.
Or you can try this link straight to the yotaphone2_flasher.exe file.

https://drive.google.com/file/d/0B0KC5E0zkBYmcHAzMEFKaHRvZ3M/view?usp=sharing

HOW
leviet4 said:
thank you, the first way worked and my phone runs normally now.
thank you
Click to expand...
Click to collapse
Dude I've just bought my phone, and it has the same problem. But I'm a complete noob, how did you fix it? Please, i've just bought it.

On RU build 134 when I tried to swap users my user with Defaut user, the phone blocked, the display is on (time is the same when first happend - just a freeze image) but I can't do nothing on phone. Is a way to reset? because on a normal way I would remove battery but yota dont have this option.

queser.info said:
On RU build 134 when I tried to swap users my user with Defaut user, the phone blocked, the display is on (time is the same when first happend - just a freeze image) but I can't do nothing on phone. Is a way to reset? because on a normal way I would remove battery but yota dont have this option.
Click to expand...
Click to collapse
The analogue method of pulling out the battery is pressing the POWER button for at least 10 seconds. The phone will reboot.

Thanks, I pushed vol down + Power and the phone restarted normaly.
PS: If you know where to get a book from Алекса́ндр Солжени́цын - Aleksandr Solzhenitsyn to read on yota display, send me.

SteadyQuad said:
You can probably recover.
To reflash a full firmware image you could try the relatively user-friendly yotaflasher application and ROM images from here. I haven't used this myself, but it's software by Yota, so should be safe. You can ask it not to touch /data, to preserve apps, settings etc.
A less user friendly way to reflash a full firmware image:
- Download a full firmware image (EU 1.60 flashable version here, let me know if you require a different one)
- With the phone off, press vol down + power until you see "Downloading ...."
- If you can't turn the phone off normally, keep vol down + power for at least 15 seconds till phone reboots, keep holding till you end up with "Downloading ...."
- connect to a PC with adb+fastboot with a USB cable
- You can now boot TWRP image (fastboot boot recovery_twrp_yd201_alpha2.img , see here.
- if you have important files on your phone, you can back them up now by using adb shell/adb pull (e.g. adb pull /sdcard/Pictures/yeti_sighting.jpg)
- In TWRP go to advanced -> sideload and confirm
- now you can sideload a ROM image from the PC with adb sideload <image>.zip, it should show progress while it's uploading the firmware. If it errors, you probably haven't confirmed initiating sideload in previous step.
- wipe cache&dalvik and reboot
Click to expand...
Click to collapse
Sir, i can't even get into recovery mode, i get this problem like it suddenly happen and my battery was 38%.. i was on facebook and it hang and then reboot and then stuck at "POWERED BY ANDROID".
I try to get into recovery mode by pressing volume up + power button, it restart again to "POWERED BY ANDROID"
When i pressing volume down + power button, it show downloding... , and i try to flash it using yotaflasher with HK Firmware 5.0.
When it is done, the phone reboot.
And it still stuck at "POWERED BY ANDROID"
What is the real problem ?

Please help!!!
While trying to solve the network issue on my Yotaphone 2 I managed to brick my phone. He is dead! But since it is a Snapdragon inside it can be fixed.
I need a help from someone who has rooted his Yotaphone2!
I need files from Yotaphone2 software: rawprogram0.xml and patch0.xml
Please!!!

hlmboy said:
Sir, i can't even get into recovery mode, i get this problem like it suddenly happen and my battery was 38%.. i was on facebook and it hang and then reboot and then stuck at "POWERED BY ANDROID".
I try to get into recovery mode by pressing volume up + power button, it restart again to "POWERED BY ANDROID"
When i pressing volume down + power button, it show downloading... , and i try to flash it using yotaflasher with HK Firmware 5.0.
When it is done, the phone reboot.
And it still stuck at "POWERED BY ANDROID"
What is the real problem ?
Click to expand...
Click to collapse
You need to keep pressing the power up button after the showing of "POWERED BY ANDROID", the power does not need to be pressed after then.
If you can still not reach recovery, you probably have a broken recovery (maybe wrong version) and something else is messed up.
When you flash recovery, you need to instantly go into recovery mode by pressing +/up on calling the according command
(fastboot reboot).
It does not look like you changed file system related things, did you change anything on your system/with root permissions?
Are you sure the installation process went without failure etc?
Getting out the cause (kernel logs etc) would be a bit hard without getting into recovery mode[and maybe also nonworking kernel], like stated out here
https://android.stackexchange.com/q...n-i-recover-files-from-a-phone-that-wont-boot