Database Develop

experts help me here with htc one m7 running on 5.0.2

Tried rooting my htc one m7 running on android 5.0.2 with kingroot 4.5 and processed like 67% everytime and reboots and after reboot, it shows an error like "0 ppls have submitted research request" ..please help me here...i also tried framaroot,universal androot,towel root etc
Thebn i tried kingo root and lost all data and yet not got rooted...(i think bootloader got unlocked by which i lost my all datas)..it goes till i have something like cw recovery option on my phone screen which is in chinese...so i just gone for 1st option(dont know which 1 to be selected) and reboots..kingo root show "root suceeded" in pc but i checked with root checker and found it still aint rooted...i really dont have much idea on android modding n rooting....so please somebody help me root my phone..thanks

akon143 said:
Tried rooting my htc one m7 running on android 5.0.2 with kingroot 4.5 and processed like 67% everytime and reboots and after reboot, it shows an error like "0 ppls have submitted research request" ..please help me here...i also tried framaroot,universal androot,towel root etc
Thebn i tried kingo root and lost all data and yet not got rooted...(i think bootloader got unlocked by which i lost my all datas)..it goes till i have something like cw recovery option on my phone screen which is in chinese...so i just gone for 1st option(dont know which 1 to be selected) and reboots..kingo root show "root suceeded" in pc but i checked with root checker and found it still aint rooted...i really dont have much idea on android modding n rooting....so please somebody help me root my phone..thanks
Click to expand...
Click to collapse
You don't need any of the tools you mentioned to root the m7. If the bootloader is unlocked just flash TWRP recovery with fastboot. Load into recovery then Reboot system. TWRP will then give you the option to root. Select yes.
Once it reboots launch the SuperSU app from your app draw to check binaries are upto date.
If binaries need updating again you will be prompted to select one of 2 options. Either should work fine but TWRP method is recommended.
That's it. Twrp can handle the entire rooting process for you
Sent from my SM-T230 using Tapatalk

Danny201281 said:
You don't need any of the tools you mentioned to root the m7. If the bootloader is unlocked just flash TWRP recovery with fastboot. Load into recovery then Reboot system. TWRP will then give you the option to root. Select yes.
Once it reboots launch the SuperSU app from your app draw to check binaries are upto date.
If binaries need updating again you will be prompted to select one of 2 options. Either should work fine but TWRP method is recommended.
That's it. Twrp can handle the entire rooting process for you
Sent from my SM-T230 using Tapatalk
Click to expand...
Click to collapse
Well my bootloader is unlocked(showing tampered-unlocked in boot menu)...but i really dont know any of these things like flashing,modding and all...so if anybody here can help me get me a full working tutorial, that would be very helpful.please help me here
Thanks for the reply

akon143 said:
Well my bootloader is unlocked(showing tampered-unlocked in boot menu)...but i really dont know any of these things like flashing,modding and all...so if anybody here can help me get me a full working tutorial, that would be very helpful.please help me here
Thanks for the reply
Click to expand...
Click to collapse
Ok well first of all you need an sdk on your pc. This is the software that allows you to manually flash things to your handset. Download one suitable for your pc os at the below link. And install it. http://forum.xda-developers.com/showthread.php?t=2317790
This will give you 2 command line protocol's "adb" and "fastboot"
Adb for use in recovery mode and while booted to Android (with usb debbugging enabled)
And fastboot for use only in the bootloader.
Once that's installed you can use fastboot to flash a custom recovery which can be used to root your stock Rom or flash custom roms as well as a whole host of other stuff.
Get the sdk setup boot the device to the bootloader and connect your usb cable and make sure the phone is in fastboot usb mode.
You should see and option for fastboot in the bootloader. If not but it says fastboot usb in red it's already in fastboot usb mode. Start your ask which will open a command window. And type this command
Code:
fastboot getvar all
This will give you a list of version information about your device. Which will show me which variant of m7 you have. We need to know this so you can know which files (Roms, Recovery) are safe for you to flash
Copy and paste it to a post here but edit out the IMEI an Serial Number before posting. Those 2 numbers should be kept private for security.
Sent from my M7 ARHD 84-Kitkat

Danny201281 said:
Ok well first of all you need an sdk on your pc. This is the software that allows you to manually flash things to your handset. Download one suitable for your pc os at the below link. And install it. http://forum.xda-developers.com/showthread.php?t=2317790
This will give you 2 command line protocol's "adb" and "fastboot"
Adb for use in recovery mode and while booted to Android (with usb debbugging enabled)
And fastboot for use only in the bootloader.
Once that's installed you can use fastboot to flash a custom recovery which can be used to root your stock Rom or flash custom roms as well as a whole host of other stuff.
Get the ask setup boot the device to the bootloader and connect your usb cable and make sure the phone is in fastboot usb mode.
You should see and option for fastboot in the bootloader. If not but it says fastboot usb in red it's already in fastboot usb mode. Start your ask which will open a command window. And type this command
Code:
fastboot getvar all
This will give you a list of version information about your device. Which will show me which variant of m7 you have. We need to know this so you can know which files (Roms, Recovery) are safe for you to flash
Copy and paste it to a post here but edit out the IMEI an Serial Number before posting. Those 2 numbers should be kept private for security.
Sent from my M7 ARHD 84-Kitkat
Click to expand...
Click to collapse
Done as you told and results are as
Bootloader:1.61.0000
Baseband: 4T.35.3218.16
Cpid:none
Microp:none
Main:7.21.707.121
Misc: pvt Ship s-on
Serialno:xxxxxxxxxxxxx
Imei:xxxxxxxxxxx
Meid:00000000000000
Product:m7_u
Platform:HBOOT-8064
MODEL IDN0711000
CIDNUM:HTC_038
BATTERY-STATUS:GOOD
BATTERY-VOLTAGE:4004mV
Partition-layout:generic
Security: on
Build-mode:SHIP
BOOT-MODE:FASTBOOT
COMMITNO_BOOTLOADER: Dirty-0e2a13e5
hbootpreupdate:11
Gencheckpt:0
All:done!
Finished total time 0.234 s

akon143 said:
Done as you told and results are as
Bootloader:1.61.0000
Baseband: 4T.35.3218.16
Cpid:none
Microp:none
Main:7.21.707.121
Misc: pvt Ship s-on
Serialno:xxxxxxxxxxxxx
Imei:xxxxxxxxxxx
Meid:00000000000000
Product:m7_u
Platform:HBOOT-8064
MODEL ID[emoji14]N0711000
CIDNUM:HTC_038
BATTERY-STATUS:GOOD
BATTERY-VOLTAGE:4004mV
Partition-layout:generic
Security: on
Build-mode:SHIP
BOOT-MODE:FASTBOOT
COMMITNO_BOOTLOADER: Dirty-0e2a13e5
hbootpreupdate:11
Gencheckpt:0
All:done!
Finished total time 0.234 s
Click to expand...
Click to collapse
next thing you need to do is flash TWRP Recovery.
Downloads here http://techerrata.com/browse/twrp2/m7
Download TWRP 2.8.5.0 And put the image file in your fastboot folder.
Connect fastboot usb in the bootloader the same as when you did the getvar all. Then flash it with fastboot
Code:
fastboot erase cache
fastboot flash recovery openrecovery-twrp-2.8.5.0-m7.img
fastboot reboot-bootloader
After it reboots select recovery from the bootloader menu and it will load TWRP. Then from the twrp menu choose Backup. And make a backup. Then reboot the device from twrp. You will get a notification asking if you want to install root. Select yes. The phone will reboot and will be rooted :good:
Sent from my M7 ARHD 84-Kitkat

Danny201281 said:
next thing you need to do is flash TWRP Recovery.
Downloads here
Download TWRP 2.8.5.0 And put the image file in your fastboot folder.
Connect fastboot usb in the bootloader the same as when you did the getvar all. Then flash it with fastboot
Code:
fastboot erase cache
fastboot flash recovery openrecovery-twrp-2.8.5.0-m7.img
fastboot reboot-bootloader
After it reboots select recovery from the bootloader menu and it will load TWRP. Then from the twrp menu choose Backup. And make a backup. Then reboot the device from twrp. You will get a notification asking if you want to install root. Select yes. The phone will reboot and will be rooted :good:
Sent from my M7 ARHD 84-Kitkat
Click to expand...
Click to collapse
Where can i find fastboot folder to put the downloaded img file ?

akon143 said:
Where can i find fastboot folder to put the downloaded img file ?
Click to expand...
Click to collapse
If you have used the link above to install adb and fastboot (minimal adb and fastboot) then your fastboot folder is the installation folder of "minimal adb and fastboot" most likely C:/programs/minimal adb and fastboot/save_your_recovery_here

I put the img in that folder..connected to usb started bootloader.flashed with those code ,rebooted then i selected recovery and loaded TWRP.i did choose backup and made a backup.after 100% backup it showed reboot below..i pressed on it and phone reboots...it never asked for installing root
Wot did i miss? Whole of process was done connecting usb.that really make the problem?

akon143 said:
I put the img in that folder..connected to usb started bootloader.flashed with those code ,rebooted then i selected recovery and loaded TWRP.i did choose backup and made a backup.after 100% backup it showed reboot below..i pressed on it and phone reboots...it never asked for installing root
Wot did i miss? Whole of process was done connecting usb.that really make the problem?
Click to expand...
Click to collapse
Boot in recovery again and from the main menu select "reboot" then "reboot to system" it should ask you for root, not sure if it should ask for root when rebooting from the backup menu. If it still doesn't work I'll explain you how to flash the required files.

Danny201281 said:
next thing you need to do is flash TWRP Recovery.
Downloads here
Download TWRP 2.8.5.0 And put the image file in your fastboot folder.
Connect fastboot usb in the bootloader the same as when you did the getvar all. Then flash it with fastboot
Code:
fastboot erase cache
fastboot flash recovery openrecovery-twrp-2.8.5.0-m7.img
fastboot reboot-bootloader
After it reboots select recovery from the bootloader menu and it will load TWRP. Then from the twrp menu choose Backup. And make a backup. Then reboot the device from twrp. You will get a notification asking if you want to install root. Select yes. The phone will reboot and will be rooted :good:
Sent from my M7 ARHD 84-Kitkat
Click to expand...
Click to collapse
I put the img in that folder..connected to usb started bootloader.flashed with those code ,rebooted then i selected recovery and loaded TWRP.i did choose backup and made a backup.after 100% backup it showed reboot below..i pressed on it and phone reboots...it never asked for installing root
Wot did i miss? Whole of process was done connecting usb.that really make the problem?
Bro help me here please

akon143 said:
I put the img in that folder..connected to usb started bootloader.flashed with those code ,rebooted then i selected recovery and loaded TWRP.i did choose backup and made a backup.after 100% backup it showed reboot below..i pressed on it and phone reboots...it never asked for installing root
Wot did i miss? Whole of process was done connecting usb.that really make the problem?
Bro help me here please
Click to expand...
Click to collapse
It's possible that one of your previous attempts has left something on the device which make TWRP belive the device is rooted already.
Check in your app drawer. Do you have a super user or SuperSU app in there?
Sent from my M7 ARHD 84-Kitkat

alray said:
Boot in recovery again and from the main menu select "reboot" then "reboot to system" it should ask you for root, not sure if it should ask for root when rebooting from the backup menu. If it still doesn't work I'll explain you how to flash the required files.
Click to expand...
Click to collapse
I pressed fastboot then reboot.phone reboots..there is no option like "reboot to system"

Danny201281 said:
It's possible that one of your previous attempts has left something on the device which make TWRP belive the device is rooted already.
Check in your app drawer. Do you have a super user or SuperSU app in there?
Sent from my M7 ARHD 84-Kitkat
Click to expand...
Click to collapse
No there is no super user app in app drawer.. i did installed root checker,titanium backup to check phones rooted or not before...its still there

akon143 said:
I pressed fastboot then reboot.phone reboots..there is no option like "reboot to system"
Click to expand...
Click to collapse
Boot to TWRP then Reboot like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you still don't get the notification. Check your app draw like I said in my previous post. :good:
Sent from my M7 ARHD 84-Kitkat

akon143 said:
I pressed fastboot then reboot.phone reboots..there is no option like "reboot to system"
Click to expand...
Click to collapse
From twrp, not from fastboot.
Boot in twrp recovery, from the main menu select the "reboot" menu then reboot to system.
edit: like in the pictures posted above by danny :good:
If it doesn't work, download and save supersu2.46 at the root of your phone storage, reboot in twrp recovery. Select the "install" menu and then browse your phone storage to find supersu2.46.zip. select it and swipe the bottom slider to confirm you want to flash this file. Then reboot to the system and your phone is rooted.

Danny201281 said:
Boot to TWRP then Reboot like this
View attachment 3442047
View attachment 3442049
If you still don't get the notification. Check your app draw like I said in my previous post. :good:
Sent from my M7 ARHD 84-Kitkat
Click to expand...
Click to collapse
Just tried like u said but no notification came in and there is no super SU app instatlled in app drawer

akon143 said:
No there is no super user app in app drawer.. i did installed root checker,titanium backup to check phones rooted or not before...its still there
Click to expand...
Click to collapse
alray said:
From twrp, not from fastboot.
Boot in twrp recovery, from the main menu select the "reboot" menu then reboot to system.
edit: like in the pictures posted above by danny :good:
If it doesn't work, download and save supersu2.46 at the root of your phone storage, reboot in twrp recovery. Select the "install" menu and then browse your phone storage to find supersu2.46.zip. select it and swipe the bottom slider to confirm you want to flash this file. Then reboot to the system and your phone is rooted.
Click to expand...
Click to collapse
So if there's no app and you don't get the notification. Use TWRP to install the supersu app from @alrays post. Just copy the zip to you phone storage then install it with the "Install" option in Twrp.
It does seem that Towel root or one of the other tools you tried has done something that is interfering with it. But flashing the zip manually should do the job :good:
Sent from my M7 ARHD 84-Kitkat

akon143 said:
Just tried like u said but no notification came in and there is no super SU app instatlled in app drawer
Click to expand...
Click to collapse
so proceed with the supersu2.46.zip like said above.
@Danny201281 you were faster than me again

akon143 said:
Just tried like u said but no notification came in and there is no super SU app instatlled in app drawer
Click to expand...
Click to collapse
Alternatively you could do a factory reset in Twrp. That will reset your system partition and then rebooting from twrp should give you the notification. Warning!!! If you try this DO NOT use "Format Data" this is not the same as Factory Reset it will wipe everything off your phone. It's a common mistake just wanted to warn you of it
Sent from my M7 ARHD 84-Kitkat

Soft bricked Nexus 6? - "Your device is corrupt. It can't be trusted and may not work

Soft bricked Nexus 6? - "Your device is corrupt. It can't be trusted and may not work
I unlocked the bootloader using the Nexus Toolkit (wugfresh) succesfully. However, while installing TWRP Recovery my device now appears soft bricked and I am unable to boot up nor get into Recovery mode.
This is the message I get:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It comes on briefly for a second or two, and then the phone shuts down. I attempted the suggestions listed here (
Dismiss the warning
The warning message should go away on its own after about 10 seconds and your device will continue starting up.
If you still see the warning message, you can choose to continue starting up your device by pressing the power button once.)
but they do not work. The phone will not continue to boot into System.
Help?
EDIT: I can get into Recovery Mode now. However, it wont go into TWRP (it did before), it now just has the Android on it's back with the red exclamation triangle reading "No command".

reflash twrp
flash a custom rom

Unlocking the bootloader shouldn't cause that message to show up. What were you expecting the toolkit to do? And do you know what it successfully did?

It happens whenever I try to root the device. I am able to get into the bootloader, and then reflashing to stock resolves the issue. But every time I try to root the device, it refuses to continue to boot into system after flashing the message. In summary, it successfully unlocked the bootloader but wont root/ flash TWRP.

Consult the guy who made the toolkit that ****ed up your phone. You clicked his button, rather then run a short list of well known commands we could help you with, so we have no idea what you did right or wrong... Maybe you didn't click hard enough.
Alternatively, read one of the many many many guides here, and use the single command needed, and if there are any errors copy and paste the console output (using code tags) here and we can sort you out in a minute or two.

Caebron said:
It happens whenever I try to root the device. I am able to get into the bootloader, and then reflashing to stock resolves the issue. But every time I try to root the device, it refuses to continue to boot into system after flashing the message. In summary, it successfully unlocked the bootloader but wont root/ flash TWRP.
Click to expand...
Click to collapse
What root are you using? That is probably the issue. If you use the older style root you need a modified boot image. I suggest the new systemless root.
So to fix this lets do this:
1 Use the toolkit to flash stock and unroot.
2 Flash TWRP
3 Copy the systemless root 2.65 to the !readytoflash folder. Delete the three files that are in there. The are from the old root way.
4 Reboot into TWRP and use it to flash the new root.
When you exit TWRP it will offer to root your phone. Say no. And stop after each step and make sure the phone is ok. So we can tell what went wrong if there are issues.

Thanks, I will give that a shot. FWIW, wugfresh Nexus Toolkit is an established tool and worked like a charm on my Nexus 5. But I also understand that things might be different for the 6 and the toolkit may not be the best option anymore. My fault for that assumption.
I will try TonikJDK's suggestion and report back.

Hi,
Had the same thing...
Really DONT know what the hack with with these wonderful people who developet these tools that do not mention ANYTHING regarding the issu in the main page of their tools here.
I think that you should follow the instructions:
1) Download shamu-mra58k => extract => take bootloader + radio + boot + cache + recovery + system + userdata => compy to platform-tools folder (under SDK).
2) Open CMD (open command prompt...) from platform-tools folder.
3) Type: fastboot devices (to know that pc recognized your N6) & than type the commands as shown at the attached screenshot.

That looks like a Wugfresh NRT log...
But why not go the whole way and use the latest 6.0.1 MMB29K?
https://developers.google.com/android/nexus/images?hl=en#shamu

Caebron said:
Thanks, I will give that a shot. FWIW, wugfresh Nexus Toolkit is an established tool and worked like a charm on my Nexus 5. But I also understand that things might be different for the 6 and the toolkit may not be the best option anymore. My fault for that assumption.
I will try TonikJDK's suggestion and report back.
Click to expand...
Click to collapse
Your not along in getting that message after using the Wugfresh Nexus Root Toolkit as I got the same message on my brand new Nexus 6. The toolkit installed TWRP fine, but somewhere in the three files it asked me to install in TWRP (beta superSU, busybox, and another file), there was a problem. I ended up clicking flash stock + unroot and I did this twice and it worked the second time. Then I locked the bootloader and did a factory reset. So far so good. I will root the device again, but by another method.
However do note that I have used that Toolkit for a Galaxy Nexus, Nexus 7 & very recently with a Nexus Player and its worked great every other time. I think it has something to do with Marshmallow, but I'm not sure.

thinkingbrian said:
Your not along in getting that message after using the Wugfresh Nexus Root Toolkit as I got the same message on my brand new Nexus 6. The toolkit installed TWRP fine, but somewhere in the three files it asked me to install in TWRP (beta superSU, busybox, and another file), there was a problem. I ended up clicking flash stock + unroot and I did this twice and it worked the second time. Then I locked the bootloader and did a factory reset. So far so good. I will root the device again, but by another method.
However do note that I have used that Toolkit for a Galaxy Nexus, Nexus 7 & very recently with a Nexus Player and its worked great every other time. I think it has something to do with Marshmallow, but I'm not sure.
Click to expand...
Click to collapse
Best and easiest method to root Marshmellow imo is to flash TWRP and CF`s latest systemless root zip 2.65.

dahawthorne said:
That looks like a Wugfresh NRT log...
But why not go the whole way and use the latest 6.0.1 MMB29K?
https://developers.google.com/android/nexus/images?hl=en#shamu
Click to expand...
Click to collapse
That's not the NRT log (just flahsed manually by fastboot without any script).
I think with up to 6.0.1 MMB29K(not included) there is no issues.

Just kidding...
I've been running MMB29K for a couple of weeks with no problems. I was just suggesting that if the OP was going to go to the effort of flashing then he/she may as wll use the most recent version. Or even hold off for a few days for the possible new one in January. Hey, that's today...

Caebron said:
Thanks, I will give that a shot. FWIW, wugfresh Nexus Toolkit is an established tool and
Click to expand...
Click to collapse
... it bricks your phone. Unless you know exactly what you're doing. But then you don't really need it anymore.
People, Marshmallow is already past the toolkits. It has an update once a month, and the toolkits don't have time to be updated fast enough. You'll be bricking your phones constantly if you don't learn your stuff.

Caebron said:
I unlocked the bootloader using the Nexus Toolkit (wugfresh) succesfully. However, while installing TWRP Recovery my device now appears soft bricked and I am unable to boot up nor get into Recovery mode.
This is the message I get:
It comes on briefly for a second or two, and then the phone shuts down. I attempted the suggestions listed here (
Dismiss the warning
The warning message should go away on its own after about 10 seconds and your device will continue starting up.
If you still see the warning message, you can choose to continue starting up your device by pressing the power button once.)
but they do not work. The phone will not continue to boot into System.
Help?
EDIT: I can get into Recovery Mode now. However, it wont go into TWRP (it did before), it now just has the Android on it's back with the red exclamation triangle reading "No command".
Click to expand...
Click to collapse
This error is the consequence of a " feature " of marshmallow that checks if your system is modified and issues this error message.
Here is how you "unbrick" your phone after running into a problem like this:
1- Download and flash a stock rom. Make sure all partitions are flashed (i.e. bootloader, radio, kernel (aka boot), recovery, cache, userdata, and system). If you don't know how to do it Google it.
2- Boot into the stock recovery and wipe data, cache, and factory reset.
Now that your system is restored, here is how you root it:
1- copy superSU 2.65 on your internal SD card.
2- reboot into bootloader
3- flash twrp
4- very important: do not boot from the bootloader back into Android, rather boot into recovery.
5- when you are booted into twrp recovery, flash superSU zip. It will both root your phone and patch the kernel so that it doesn't give you that curroptrd phone error.
One last thing, not to rub it in for the gentlemen who posted the question but for other who are considering the easy way of using a toolkit, and please don't get offended by this. No one is against convenience but if you are unable or unwilling to learn few simple commands to unlock and unroot your phone you probably are not the type of user who needs to root the phone and chances are that after using a toolkit something will go wrong and you will have to learn the steps the hard way after the effect. Toolkits are good intentioned tools that should be avoided at all cost.

najoor said:
This error is the consequence of a " feature " of marshmallow that checks if your system is modified and issues this error message.
Here is how you "unbrick" your phone after running into a problem like this:
1- Download and flash a stock rom. Make sure all partitions are flashed (i.e. bootloader, radio, kernel (aka boot), recovery, cache, userdata, and system). If you don't know how to do it Google it.
2- Boot into the stock recovery and wipe data, cache, and factory reset.
Now that your system is restored, here is how you root it:
1- copy superSU 2.65 on your internal SD card.
2- reboot into bootloader
3- flash twrp
4- very important: do not boot from the bootloader back into Android, rather boot into recovery.
5- when you are booted into twrp recovery, flash superSU zip. It will both root your phone and patch the kernel so that it doesn't give you that curroptrd phone error.
One last thing, not to rub it in for the gentlemen who posted the question but for other who are considering the easy way of using a toolkit, and please don't get offended by this. No one is against convenience but if you are unable or unwilling to learn few simple commands to unlock and unroot your phone you probably are not the type of user who needs to root the phone and chances are that after using a toolkit something will go wrong and you will have to learn the steps the hard way after the effect. Toolkits are good intentioned tools that should be avoided at all cost.
Click to expand...
Click to collapse
No offense taken I've rooted quite a few phones although I'm far from being an "expert". The toolkit was really just for convenience, and I went back to using it because it worked like a charm for the Nexus 5. It really was the go-to handy tool. To be sure: As I've stated above, I was able to recover the phone on my own. Still not rooted though, but I'm getting there. Sure, M is good enough on it's own, but frankly I can't wait to get back on a Cataclysm ROM.

najoor said:
Here is how you "unbrick" your phone after running into a problem like this:
1- Download and flash a stock rom. Make sure all partitions are flashed (i.e. bootloader, radio, kernel (aka boot), recovery, cache, userdata, and system). If you don't know how to do it Google it.
2- Boot into the stock recovery and wipe data, cache, and factory reset.
Now that your system is restored, here is how you root it:
1- copy superSU 2.65 on your internal SD card.
2- reboot into bootloader
3- flash twrp
4- very important: do not boot from the bootloader back into Android, rather boot into recovery.
5- when you are booted into twrp recovery, flash superSU zip. It will both root your phone and patch the kernel so that it doesn't give you that curroptrd phone error.
Click to expand...
Click to collapse
Just LOVE how you explain it!
Wish more users will explain these kinds of things in such an "user friendly" way

I used the Chain Fire method and ended up in the same place. I can still access TWRP and fastboot, I am in the process of downloading the stock image.

fyrmd said:
I used the Chain Fire method and ended up in the same place. I can still access TWRP and fastboot, I am in the process of downloading the stock image.
Click to expand...
Click to collapse
You have to flash back to stock first. Marshmallow is checking for system mods, so if you don't undo the previous changes it will trigger again. Flash stock, twrp then 2.65 chainfire.

Caebron said:
No offense taken I've rooted quite a few phones although I'm far from being an "expert". The toolkit was really just for convenience, and I went back to using it because it worked like a charm for the Nexus 5. It really was the go-to handy tool. To be sure: As I've stated above, I was able to recover the phone on my own. Still not rooted though, but I'm getting there. Sure, M is good enough on it's own, but frankly I can't wait to get back on a Cataclysm ROM.
Click to expand...
Click to collapse
... You don't need to root to install a rom.
In fact, while installing the rom you will likely wipe your /system partition and any other partition you mess with to root....
What is it you think rooting actually does? Why are you doing it? What part do you think it will actually play in you installing a rom? Don't just do random ****. Learn what things do, so you can do what you want. This is why people hate toolkits. They promote this kinda of mentality where you just do stuff you don't understand in the slightest.

[GUIDE][ROOT] HTC One X9 Android 6.0 ROOT Method

0x00 Preparation
Here are something you will need.
1. HTC Driver
2. adb & fastboot
PC:
Install HTC Driver the decompress ADB-Windows.zip.
Phone:
Go to (Settings -> About -> Software information -> More -> Build number), Tap it 7 times to enable developer options.
Go to (Settings -> Developer options), Check OEM unlocking and USB debugging options.
PC:
Go to ADB-Windows folder and hold Shift + Right Mouse Click the click open command windows here.
Input the command below to test adb function.
Code:
adb devices
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
0x01 Unlock Bootloader
Input the command to reboot to download mode.
Code:
adb reboot download
Download mode is same as fastboot in bootloader on old devices, so you must to do UNLOCK, FLASH or RUU in download mode.
Go to HTCdev website to unlock bootloader, you can search many guides on Google.
0x02 Flash TWRP Recovery
TWRP 3.0.2-0
Reboot to download mode and flash recovery.
Code:
adb reboot download
fastboot flash recovery twrp-3.0.2-0-e56ml.img
After flash recovery, reboot to bootloader then BOOT TO RECOVERY MODE.
0x03 Format Data
Wipe -> Format Data -> type yes to format data
Please reboot to recovery after formatting.
0x04 Install SuperSU
Please download SuperSU v2.78, i've test this version and work like a charm.
Before flashing su, please ensure that BOOT image is stock.

Looks good. Have to questions: Will that also work for the DualSim version?
Is the TWRP not the test version, where need a password?
Thx a lot.
Sent from my LG-H961N using XDA-Developers mobile app

schuertzi said:
Looks good. Have to questions: Will that also work for the DualSim version?
Is the TWRP not the test version, where need a password?
Thx a lot.
Sent from my LG-H961N using XDA-Developers mobile app
Click to expand...
Click to collapse
I have tested on dual-sim device (Taiwanese model) but single-sim devices, need volunteer to test it.
In this situation TWRP will request password, stock BOOT and boot into android once, in the meanwhile userdata will be encrypted.
BUT you won't do nothing if you flash TWRP, just format the userdata and install SuperSU, encryption doesn't matter anymore.

OK thx. So, you tried it with the DualSim version. That's great. But I don't know how to stock Boot and boot into Android? Can you help me with that? Thx a lot.
Sent from my LG-H961N using XDA-Developers mobile app

schuertzi said:
OK thx. So, you tried it with the DualSim version. That's great. But I don't know how to stock Boot and boot into Android? Can you help me with that? Thx a lot.
Sent from my LG-H961N using XDA-Developers mobile app
Click to expand...
Click to collapse
FORMAT userdata via TWRP
Reboot to download mode
Flash stock BOOT image
Reboot

Thx for your explanation. Will try, it when I am back home.
Thx again.
Sent from my LG-H961N using XDA-Developers mobile app

sabpprook said:
FORMAT userdata via TWRP
Reboot to download mode
Flash stock BOOT image
Reboot
Click to expand...
Click to collapse
Thank you very much for the instructions
I have done it the root very easy
But my phone is S-off So I used SD card method
It's very easy way than ADB methode also no need to unlock bootloader if you are S-off.

Dude...... Awesome tutorial........thank you.
Can some one direct me on how to get xposed up and running?????

dsjiffry said:
Dude...... Awesome tutorial........thank you.
Can some one direct me on how to get xposed up and running?????
Click to expand...
Click to collapse
DO IT YOURSELF
Install xposed framework here via TWRP, then install APK here

Thanks so much! I will test this on my single sim X9 :good:
One of the best How-To's I have seen posted on this site in a long time - great work! :laugh:

Do I have to root before I upgrade to the latest Android? 2.18.401.3
I have tried this and as soon as I install twrp the phone is soft bricked. It does not even start if I reinstall stock recovery.
Edit:
I tried again but this time I skipped this part:
0x03 Format Data
Wipe -> Format Data -> type yes to format data
Rooted and not soft bricked.

hello, when I wrote adb devices, it show for me 2 devices, one is htc and one is emulator, so how I can choose my device htc ?
please advice.

Now I use magisk.
I downgraded my phone to 2.17.401.1 (with RUU) and then updated via ota to 2.23.401.1.
Then installed TWRP. From there I installed all three files from the links in the magisk section. Booted into recovery and installed the two zip-files, this time I had to format data to be able to install.
When booted I installed magisk manager from my download directory and Phils superuser app from play store.
Checked root with Root checker to confirm.

Hi, when I try fastboot flash recovery part, I get cannot load 'twrp-3.0.2-0-e56ml.img' message. What should I do?

thank you so much, it worked greatly on my htc x9 dual sim.
---------- Post added at 05:46 PM ---------- Previous post was at 05:46 PM ----------
thank you so much, it worked greatly on my htc x9 dual sim.

after flashing twrp the phone is soft bricked
i flashed twrp and then stock boot.img
when i let twrp change system partition it soft bricks the phone

Hi, Please get backup before use this method!
My phone is die
can you help me ?
Please tell me to flash stock rom in this phone
thanks alot

-.- folllowed instructions on single sim wont boot past htc logo. great job. should have informed us of password or something to actually allow full access so this doesnt happen. how to restore the phone as it wouldnt even let me do a backup in recovery before hand.... and your comments just said do it anyway
edit:
i may have swiped factory reset not format data. this may be my issue. just gotta wait 3 hours to download my original boot image now -.- will post back withupdate
#update:
flashed stock bootimg, recoveryimg and systemimg then flashed decrypted firmware and then the twrp rebooted into recovery instantly it mounted everything fine no password asked. formatted flashed su then booted and seems to be working fine just turning phone on now and says updating apps. thanks will post back with or if any issues

ty ty sir i rooted my phone because of you

kgpp2293 said:
-.- folllowed instructions on single sim wont boot past htc logo. great job. should have informed us of password or something to actually allow full access so this doesnt happen. how to restore the phone as it wouldnt even let me do a backup in recovery before hand.... and your comments just said do it anyway
edit:
i may have swiped factory reset not format data. this may be my issue. just gotta wait 3 hours to download my original boot image now -.- will post back withupdate
#update:
flashed stock bootimg, recoveryimg and systemimg then flashed decrypted firmware and then the twrp rebooted into recovery instantly it mounted everything fine no password asked. formatted flashed su then booted and seems to be working fine just turning phone on now and says updating apps. thanks will post back with or if any issues
Click to expand...
Click to collapse
Hey can u help me? When I try fastboot flash recovery part, I get cannot load 'twrp-3.0.2-0-e56ml.img' message.

[Recovery] [YB1-X90L] TWRP

managed to get twrp working on YB1-X90L (Yoga Book - Android - LTE)
it's my very first try to create sth. like that, so I have absolutely no idea if everything works as it should. (took the twrp from yoga tab 3 pro root thread and changed it to fit my device mainly using this guide and some minor changes on my own)
if you want to try, you do it on your own risk. if sth. breaks, please don't blame me!
I strongly suggest not to flash it, but just boot it via fastboot:
1. download recovery
2. make sure adb is working
3. put the recovery into your adb folder
4. unlock bootloader (attention: unlocking the bootloader does a factory reset. so back up your data before) see here how to unlock bootloader
5. boot into bootloader (either: 'press power + volume up' or use adb typing 'adb reboot bootloader' in terminal
6. open terminal and naviagte to your adb folder (with recovery.img in it) then type: 'fastboot boot recovery_twrp.img' (adapt file name in case you changed it)
7. tablet should reboot and boot twrp
this method does not flash twrp permanently. your stock recovery remains untouched!
!!!BEFORE YOU USE TWRP TO CHANGE ANYTHING, PLEASE MAKE A FULL BACKUP!!!
download: View attachment recovery_twrp.zip
as always... I mainly relied on other people's work. so all credits go to them, e.g. twrp team, joesnose (twrp yoga tab 3pro) and HostZero
screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
as i said, it is a beginner's job. so here is what i noticed so far:
twrp freezes after a certain time when not used - I guess it is when twrp goes to 'standby', normally you wake it up again by sliding a button but it doesn't work here.

---reserved---

before you ask...
yes, of course, i have already tried to flash supersu, but unfortunately I had no luck so far. The script always aborts because it fails patching sepolicy of boot.img.
so if anyone knows a solution for this, feel free to help!
edit:
found another way to root, look here

Amazing! I never thought yb would have twrp. I've been looking for a way to install gapps since I bought yb. After my final I will definitely have a try.

Was it stable when you flashed some zip?

AndyVerne said:
Was it stable when you flashed some zip?
Click to expand...
Click to collapse
did backup 2 times and restored all partitions a several times which worked well.
only tried to install supersu, which in general went well although su couldn't patch boot.img (but has nothing to do with twrp I think)

danjac said:
did backup 2 times and restored all partitions a several times which worked well.
only tried to install supersu, which in general went well although su couldn't patch boot.img (but has nothing to do with twrp I think)
Click to expand...
Click to collapse
All right, I wil try to install supersu after take my final exam ,too .
I believe there will be a way to solve it .
(oh ,god , the root seems to have sloved , nice job!)

danjac said:
did backup 2 times and restored all partitions a several times which worked well.
only tried to install supersu, which in general went well although su couldn't patch boot.img (but has nothing to do with twrp I think)
Click to expand...
Click to collapse
I have one question, after I unlock the bootloader, it occurs the "intel ....untrusted,will boot in 5 seconds ", I wanna know how to lock the bootloader again.

AndyVerne said:
I have one question, after I unlock the bootloader, it occurs the "intel ....untrusted,will boot in 5 seconds ", I wanna know how to lock the bootloader again.
Click to expand...
Click to collapse
to lock the bootloader you must have stock recovery...hopefully you din't flash twrp.
I do not really know, whether locking the bootloader will work flawlessly due to the changes made by root
when you lock the bootloader it will once more wipe all data - so back it up before, normally root should stay (although I don't know for sure)
to lock the bootloader just use the following command in terminal:
Code:
fastboot flashing lock
if you are not sure, try to search xda for more information about relocking.

danjac said:
to lock the bootloader you must have stock recovery...hopefully you din't flash twrp.
I do not really know, whether locking the bootloader will work flawlessly due to the changes made by root
when you lock the bootloader it will once more wipe all data - so back it up before, normally root should stay (although I don't know for sure)
to lock the bootloader just use the following command in terminal:
if you are not sure, try to search xda for more information about relocking.
Click to expand...
Click to collapse
Oh, I gave it up... Thanks

Do not get me wrong but you say make a full back up with twrp before doing anything but based on your description twrp cant be installed without unlocking the bootloader which in return erases the device.
Is this catch22 or am I missing something here?
danjac said:
managed to get twrp working on YB1-X90L (Yoga Book - Android - LTE)
it's my very first try to create sth. like that, so I have absolutely no idea if everything works as it should. (took the twrp from yoga tab 3 pro root thread and changed it to fit my device mainly using this guide and some minor changes on my own)
if you want to try, you do it on your own risk. if sth. breaks, please don't blame me!
I strongly suggest not to flash it, but just boot it via fastboot:
1. download recovery
2. make sure adb is working
3. put the recovery into your adb folder
4. unlock bootloader (attention: unlocking the bootloader does a factory reset. so back up your data before) see here how to unlock bootloader
5. boot into bootloader (either: 'press power + volume up' or use adb typing 'adb reboot bootloader' in terminal
6. open terminal and naviagte to your adb folder (with recovery.img in it) then type: 'fastboot boot recovery_twrp.img' (adapt file name in case you changed it)
7. tablet should reboot and boot twrp
this method does not flash twrp permanently. your stock recovery remains untouched!
!!!BEFORE YOU USE TWRP TO CHANGE ANYTHING, PLEASE MAKE A FULL BACKUP!!!
download: View attachment 3994659
as always... I mainly relied on other people's work. so all credits go to them, e.g. twrp team, joesnose (twrp yoga tab 3pro) and HostZero
screenshots:
View attachment 3994696
View attachment 3994697
View attachment 3994698
as i said, it is a beginner's job. so here is what i noticed so far:
twrp freezes after a certain time when not used - I guess it is when twrp goes to 'standby', normally you wake it up again by sliding a button but it doesn't work here.
Click to expand...
Click to collapse
---------- Post added at 09:33 PM ---------- Previous post was at 09:30 PM ----------
So this process messed up your system? Not sure if I understand what is going on there.
AndyVerne said:
I have one question, after I unlock the bootloader, it occurs the "intel ....untrusted,will boot in 5 seconds ", I wanna know how to lock the bootloader again.
Click to expand...
Click to collapse

hajkan said:
Do not get me wrong but you say make a full back up with twrp before doing anything but based on your description twrp cant be installed without unlocking the bootloader which in return erases the device.
Is this catch22 or am I missing something here?
---------- Post added at 09:33 PM ---------- Previous post was at 09:30 PM ----------
So this process messed up your system? Not sure if I understand what is going on there.
Click to expand...
Click to collapse
to your first question:
1. well, here we are not talking about backing up your user data but your rom (stock rom so to speak). if anything goes wrong you can always go back to stock.
2. if you want to peform ota update you can't do it with modified system (ota will fail), so normally you must go back to stock, update, root again
to your second question:
it's just a warning that your bootloader is unlocked, nothing more. it shows with every boot and after 5secs just boots normally.
you can easily find out about the advantages and disadvantages of an unlocked bootloader e.g. here on xda.

I can't thank you enough for this. I live in China and was only able to buy the Chinese version of the Yoga Book, which doesn't come with Google Services installed. However, using this TWRP recovery I was able to flash Google Services (and get root) which makes my Yoga Book so much more useful! Thanks so much!

Have got as far as flashing TWRP, but find that any attempt to backup - to internal storage or sdcard - is cancelled. Have checked on googz but cannot find any specific info. Any help would be appreciated

zamzenos said:
Have got as far as flashing TWRP, but find that any attempt to backup - to internal storage or sdcard - is cancelled. Have checked on googz but cannot find any specific info. Any help would be appreciated
Click to expand...
Click to collapse
which yoga book version?
did you flash it or booted it?
how about a log (--> advanced --> copy to sdcard)?
is 'mount read-only' in 'mount' deactivated?

danjac said:
which yoga book version?
did you flash it or booted it?
how about a log (--> advanced --> copy to sdcard)?
is 'mount read-only' in 'mount' deactivated?
Click to expand...
Click to collapse
Left it overnight and tried again today. It's OK this time. I fiddled with settings, mainly to deselect the read-only system option. Each stage of this process has been pretty frustrating (I'm used to hacking sammy devices - this is first and last time with a lenny). Stuck now trying to get root - it will probably take until tomorrow! btw, ver is YB1 X90F (Europe/UK).
But thanks for taking the trouble to reply. And thanks for giving us the opportunity to hack the YB.

Worked on the wifi version too.
You may not be a developer but you are a pretty smart guy to be able to figure this out on your own, my hat is off to you. I rooted my wifi version of Yoga Book using your instruction and the only notable issue I ran into in the process was that i had to install new Android usb drivers in Windows to get the reboot-bootloader command to work, other than that little hiccup it worked like a charm. One other issue I ran into that was of my own making was that Titanium backup encouraged me to upgrade super user which led to a soft brick, thankfully I'd backed my book up and was able to restore it.
Thanks for taking the time to share this with us because rooting made this device a much better experience.

hi all, Im reslly happy to see the yb can really root. but all i want is to have the google app work on my yb china version.
am not a techy, hence most of the insturction mention here is very strange to me.
if anyone can help to write down the step by step on how to flash twrp and install google app to yb will be great thanks..
please...

kakit78 said:
hi all, Im reslly happy to see the yb can really root. but all i want is to have the google app work on my yb china version.
am not a techy, hence most of the insturction mention here is very strange to me.
if anyone can help to write down the step by step on how to flash twrp and install google app to yb will be great thanks..
please...
Click to expand...
Click to collapse
If you just want to install gapps, there is no need to root.
1. download gapps from opengapps.org. select x86_64 6.0 version. select nano or micro version if only want google play to be worked.
2. put the gapps zip file into your root of your YB.
3. just follow the instructions of this post to boot into TWRP
4. In TWRP, select install zip file from SD, then select the gapps to install
5. after finish, reboot to the system.
6. Done!
---------- Post added at 08:48 AM ---------- Previous post was at 08:44 AM ----------
The problem is that I fail to OTA updated after booting into TWRP and install gapps. Anyone can helps?

@danjac Hi, did you keep the boot to bios option in the reboot menu?

Potentially bricked device...is it fixable?

Hey guys,
I'll be honest...I'm a noob at all of this. I thought I would experiment with putting a custom ROM on an old Android phone I had (the SP), so googled around to find some guides on how to do it and tried to follow them. I successfully got the phone into fastboot (after using the Windows 8 driver workaround on Windows 10), and all seemed good. However, from then the issues (or what looked like them) started:
1. When entering into the bootloader (correct me if I'm wrong, but that's when you hold down the up volume as you connect it to the PC), the blue light would come on, but nothing would show on the screen. The guides I was looking at would suggest that the bootloader would load onto the screen. Was I just not loading into the bootloader?
However, I was still able to interact with the phone through the Cmd.exe, so something right was happening, so I pressed on (probably a mistake!) to attempt to install TWRP, as this was the next step in the guide I was following. This was where I ran into my next problem:
2. When trying to flash the TWRP.img to the recovery partition, I would get an error back saying the recovery partition could not be found. As far as I was concerned, there was also no way to verify whether the recovery partition was there or not, as I couldn't seem to load the bootloader either
Having googled around, I found an article that suggested I'd flash it to the boot partition instead, which I did. From that point, the device would no longer boot at all. It would enter fastboot/bootloader with the blue light, but unplugging the device and holding down the power button did nothing. At this point I decided "screw it" and decided to push on and see if I could install a ROM (I'd settled on LineageOS), so started following the steps, and flashed the Boot.img to the boot partition. The other instruction was to "flash the LineageOS zip from recovery", which I did not know how to do, and presumed was not possible, seeing as I thought I'd somehow broken that partition. At this point, the phone would turn on, the bar would flash green then red, and the Sony splashscreen would show. However, that is that would happen - it would stay frozen at that point. That is the point I'm at now
I appreciate that I've probably royally messed up this phone, and that's okay with me if that's the case - it was a learning experience. However, if this is recoverable, I'd really appreciate some help! I may be new to this, and not know much at all, but I want to try it, so if there is a way to get to a position where I can install TWRP and then flash a ROM to the phone, then please share your knowledge! I'm open to anything
Thanks in advance,
Meeb

MrMeeb said:
Hey guys,
I'll be honest...I'm a noob at all of this. I thought I would experiment with putting a custom ROM on an old Android phone I had (the SP), so googled around to find some guides on how to do it and tried to follow them. I successfully got the phone into fastboot (after using the Windows 8 driver workaround on Windows 10), and all seemed good. However, from then the issues (or what looked like them) started:
1. When entering into the bootloader (correct me if I'm wrong, but that's when you hold down the up volume as you connect it to the PC), the blue light would come on, but nothing would show on the screen. The guides I was looking at would suggest that the bootloader would load onto the screen. Was I just not loading into the bootloader?
However, I was still able to interact with the phone through the Cmd.exe, so something right was happening, so I pressed on (probably a mistake!) to attempt to install TWRP, as this was the next step in the guide I was following. This was where I ran into my next problem:
2. When trying to flash the TWRP.img to the recovery partition, I would get an error back saying the recovery partition could not be found. As far as I was concerned, there was also no way to verify whether the recovery partition was there or not, as I couldn't seem to load the bootloader either
Having googled around, I found an article that suggested I'd flash it to the boot partition instead, which I did. From that point, the device would no longer boot at all. It would enter fastboot/bootloader with the blue light, but unplugging the device and holding down the power button did nothing. At this point I decided "screw it" and decided to push on and see if I could install a ROM (I'd settled on LineageOS), so started following the steps, and flashed the Boot.img to the boot partition. The other instruction was to "flash the LineageOS zip from recovery", which I did not know how to do, and presumed was not possible, seeing as I thought I'd somehow broken that partition. At this point, the phone would turn on, the bar would flash green then red, and the Sony splashscreen would show. However, that is that would happen - it would stay frozen at that point. That is the point I'm at now
I appreciate that I've probably royally messed up this phone, and that's okay with me if that's the case - it was a learning experience. However, if this is recoverable, I'd really appreciate some help! I may be new to this, and not know much at all, but I want to try it, so if there is a way to get to a position where I can install TWRP and then flash a ROM to the phone, then please share your knowledge! I'm open to anything
Thanks in advance,
Meeb
Click to expand...
Click to collapse
First of all don't worry, Sony's phone doesn't brick that easy ?
All you need to do first is to repair your phone using official Xperia companion (Google how to repair your phone using Xperia companion).. After that you'll need to root your phone and unlock the bootloader to be able to install custom recovery like TWRP and use it to install any custom ROM.
Sent from my Xperia SP using Tapatalk

OsGhaly said:
First of all don't worry, Sony's phone doesn't brick that easy
All you need to do first is to repair your phone using official Xperia companion (Google how to repair your phone using Xperia companion).. After that you'll need to root your phone and unlock the bootloader to be able to install custom recovery like TWRP and use it to install any custom ROM.
Sent from my Xperia SP using Tapatalk
Click to expand...
Click to collapse
Thanks for the advice! I successfully got it to the point of being rooted (using towelroot) and the bootloader unlocked, using flashtool. All seemed good. I then downloaded TWRP Manager, and tried to install TWRP, but it failed, which was an issue I faced before. To confirm my theory, I tried doing it using the CMD fastboot, and, using "fastboot flash recovery twrp.img", and was met with the same error as before - recovery partition not found. How am I supposed to install TWRP to the recovery partition if I don't have a recovery partition?

MrMeeb said:
Thanks for the advice! I successfully got it to the point of being rooted (using towelroot) and the bootloader unlocked, using flashtool. All seemed good. I then downloaded TWRP Manager, and tried to install TWRP, but it failed, which was an issue I faced before. To confirm my theory, I tried doing it using the CMD fastboot, and, using "fastboot flash recovery twrp.img", and was met with the same error as before - recovery partition not found. How am I supposed to install TWRP to the recovery partition if I don't have a recovery partition?
Click to expand...
Click to collapse
You're more than welcome dear, glad to hear you've successfully did it :good:
Concerning TWRP flash, you can try one of these:
1- Use rasher tool to flash the TWRP img (the easiest way).
2- Adb Sideload:
AdrianDC said:
HOW TO INSTALL MANUALLY TO FOTA :
* Bootimage : Download the TWRP bootimage you want to flash
* File storage : Adapt the path and push the file to the device this way :
Code:
adb root
adb wait-for-device
adb push FullPathToTheRecovery.img /tmp/twrp.img
* Flash : Extract the TWRP image to the FOTA partition
Code:
adb shell dd if=/tmp/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
* Reboot to recovery : adb reboot recovery
​
Click to expand...
Click to collapse
3- Using terminal emulator app such as $cripter:
Place twrp.img in the root of your /sdcard folder then run the following commands using $cripter app:
Code:
su
dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
P.S. You can download the latest TWRP from here

OsGhaly said:
You're more than welcome dear, glad to hear you've successfully did it :good:
(Rest cut as I'm not allowed to post external links)
[/CODE]
Click to expand...
Click to collapse
Hmm, Rashr does not seem to work - I select it to flash recovery, select my twrp.img, it says flashing then nothing happens. When booting to recovery, nothing shows, and it goes through to a normal boot. When trying to flash TWRP using the official TWRP app, it says it has flashed successfully, but again, no luck when booting into recovery mode. I don't really want to try either of the other two techniques, for fear of breaking things again. I've seen talk elsewhere that this isn't possible on the stock Kernel, which I'm on. Is that correct?

MrMeeb said:
Hmm, Rashr does not seem to work - I select it to flash recovery, select my twrp.img, it says flashing then nothing happens. When booting to recovery, nothing shows, and it goes through to a normal boot. When trying to flash TWRP using the official TWRP app, it says it has flashed successfully, but again, no luck when booting into recovery mode. I don't really want to try either of the other two techniques, for fear of breaking things again. I've seen talk elsewhere that this isn't possible on the stock Kernel, which I'm on. Is that correct?
Click to expand...
Click to collapse
Ok then, you can't use custom recovery with the stock kernel ofc. but we don't want that!.. you will install the TWRP recovery then reboot to it and install the new ROM without booting to the stock ROM at all.
1- Download TWRP and the ROM you want to flash for example Lineage OS.
2- Use the second method mentioned in my previous post by Adrian DC to install TWRP then boot into recovery -> wipe all then install LineageOS ROM + GApps.
-----
Another workaround is to install XZDualRecovery to have Philz touch and TWRP recoveries working alongside with the stock kernel and use it to install LineageOS ROM.

Hi bro
neva mind wat happened to u ,do as wat i say
First search n find the proper (stock .tft) file as per your country and version.
Download FLASHTOOL
now paste ur stock.tft file (around 1-2 gb) in flash folder
open flashtool and connect ur sick brick SP-Xepria in fastboot
install ur stock onces it done successfullly u wil get ur phone as stock .
i too bricked now im on andriod 7
no worries bro
---------- Post added at 09:31 AM ---------- Previous post was at 09:24 AM ----------
Hi everybody welcome to my tutorial about Flashing with Flashtool. This thread is for those who want to reflash their device back to Sony Stock. See below for last details about this thread and the last build by Sony.
Note: I DO NOT OWN THIS DEVICE ANYMORE. PICTURES ARE REMOVED FROM MY DROPBOX AND THUS NOT VISEBLE. FOR NOW JUST RELY ON THE EXPLANATION PLEASE. ANY QUESTION CAN BE ASKED HERE. I DO NOT RESPOND TO TECHMAIL!
Created: 23-02-2014
Updated: 05-07-2014
Latest Android build released by Sony: 12.1.A.1.205
Let's begin shall we.. We shall!
First you need to download the correct ftf file for your device/operator or needs. This can be done here: http://forum.xda-developers.com/show....php?t=2311964 In there you can share and download firmware files in .ftf format..
You alsol need a program called Flashtool. You can download this here: http://forum.xda-developers.com/showthread.php?t=920746
For Windows 8 and 8.1 users I also recommend you to read this thread: http://forum.xda-developers.com/show....php?t=2095087 Microsoft has enhanced the security in Windows 8/8.1 and Windows won't install proper signed drivers.
When you are done with that you need to move your downloaded firmware file to the proper location for flashtool to be found:
C:\Flashtool\Firmwares
After that you are good to go, just remember the following:
Bootloader locked? If not you wont have BE2/OTA/PCC etc (for unlocking and relocking: http://forum.xda-developers.com/show....php?t=2354721 )
I've made backups of my important files that are stored on my phone?
Battery at atleast 50%?
I have patience?
I got something to do meanwhile?
The last two things are very important
Let's get started:
1: Open Flashtool:
Flashtool(.exe) for 32Bits systems and Flashtool64(.exe) for 64Bits systems
2: Press the Lightningbolt picture and select Flashmode
This will give another screen.
3: Select the downloaded ftf. (In this case 2.254)
Make sure that all the wipes are checked and the others are unchecked. This is to prevent any bootloops or other problems after downgrading.
4: Press Flash and the next two lines will be added to the flashtool log
The files are being prepared and checked. Have a bit of patience please.
5: Turn off your phone and turn it back on into Flashmode
After this the process will start.
After flashing you can disconnect your phone and boot it up.
Via Flashtool you can also reset your system after. For example:
You are running the latest ExistenZe ROM from our beloved Niaboc79 and you want to go back to stock for a reason WITHOUT losing data! Just flash the last Stock ROM and untick the following boxes:
Untick DATA and APPSLOG!! But keep CACHE to wipe the /cache (is the same as a wipe cache via CWM).
FAQ
- My Phone wont stay into flashmode
> Turn it off, wait a few minutes and turn it back into flashmode
- Flashtool wont recognise my phone
> Make sure you have the proper drivers installed. See C://Flashtool/Drivers
- Flashing failed
> Problem depends on the error code given by Flashtool. Post the problem here and perhaps we can help
- Got a bootloop
> Reflash again
- Even after reflash I got into a bootloop
> Turn off your phone via the small button behind the batterycover and wait a few minutes. Then try again. If that doesnt work you need to flash again.
- Booting takes ages
> This is normal. The entire cache needs to be rebuild. Patience my dear..
- After flashing and booting my phone is laggy.
> Reboot device and wait a bit. The phone needs to fully reset and boot itself. Have some patience dear.
- Do I need to unlock my bootloader to use flashtool
> NO!
- Can I unlock my bootloader with flashtool?
> NO!
- Can I relock my bootloader with flashtool?
> Yes

You too have Sony.yt procedure with s1boot in the last case...

OsGhaly said:
Ok then, you can't use custom recovery with the stock kernel ofc. but we don't want that!.. you will install the TWRP recovery then reboot to it and install the new ROM without booting to the stock ROM at all.
1- Download TWRP and the ROM you want to flash for example Lineage OS.
2- Use the second method mentioned in my previous post by Adrian DC to install TWRP then boot into recovery -> wipe all then install LineageOS ROM + GApps.
Click to expand...
Click to collapse
Oh, okay! I'm trying to do the command as stated, but (while rooted with SuperSU installed) I get the error about adb not being able to run root in production builds. So, I enter the shell with adb shell type su, but then when i type exit and then adb root I get an error saying device not found, even though it shows up when typing adb devices before entering into SU (suggesting I have the correct drivers installed). However, when looking in Device Manager there's a yellow triangle next to the device, with an option to update drivers. Any advice? If I need to update the drivers, what drivers are they and were do I find them?
Edit: Picture as described -
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

MrMeeb said:
Oh, okay! I'm trying to do the command as stated, but (while rooted with SuperSU installed) I get the error about adb not being able to run root in production builds. So, I enter the shell with adb shell type su, but then when i type exit and then adb root I get an error saying device not found, even though it shows up when typing adb devices before entering into SU (suggesting I have the correct drivers installed). However, when looking in Device Manager there's a yellow triangle next to the device, with an option to update drivers. Any advice? If I need to update the drivers, what drivers are they and were do I find them?
Edit: Picture as described -
Click to expand...
Click to collapse
Uninstall any driver installed + Xperia companion then install ADB drivers from here:
http://adbdriver.com/downloads/
Here you can find a guide how to install ADB drivers on Windows 8 or 10:
http://adbdriver.com/documentation/how-to-install-adb-driver-on-windows-8-10-x64.html
Also make sure you have enabled USB Debugging from Developer options menu on your phone before connecting it to PC.

OsGhaly said:
Uninstall any driver installed + Xperia companion then install ADB drivers from here:
http://adbdriver.com/downloads/
Here you can find a guide how to install ADB drivers on Windows 8 or 10:
http://adbdriver.com/documentation/how-to-install-adb-driver-on-windows-8-10-x64.html
Also make sure you have enabled USB Debugging from Developer options menu on your phone before connecting it to PC.
Click to expand...
Click to collapse
Thank you! We've done it! I initially managed to install LineageOS using the developer TWRP that could be flashed to boot partition, but after that wanted to have TWRP with LineageOS. Thanks to your advice I just managed to install TWRP using FOTA, so now I have TWRP and LineageOS. Hallelujah! I've given you all the thanks I can on this thread

MrMeeb said:
Thank you! We've done it! I initially managed to install LineageOS using the developer TWRP that could be flashed to boot partition, but after that wanted to have TWRP with LineageOS. Thanks to your advice I just managed to install TWRP using FOTA, so now I have TWRP and LineageOS. Hallelujah! I've given you all the thanks I can on this thread
Click to expand...
Click to collapse
You're welcome dear, glad to hear that you finally got lineage os and TWRP on your phone.. Well done
Sent from my Xperia SP using Tapatalk