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.
Related
I was talking about this problem over in the trickdroid thread, simply because it was trickdroid I was flashing but in fairness to that thread I don't want to clutter it with an endless amount of questions, repeating myself over and over, when people are simply there to review the rom/tweaks. I will give my issues in the correct order as best as I can remember, bottom line is I'm caught in a TWRP bootloop.
1) Picked up phone and unlocked bootloader and rooted via all-in-one toolkit. Confirmed root by downloading Titanium, so at this point I am stock rooted with zero issues.
2) Having installed latest TWRP at time of root I immiedietly backed up the stock rom, which I then copied to computer, so I do have this backed up and it's also visible (though unflashable) in TWRP under internal storage.
3) Flashed Trickdroid, which hung on 'install,' and I've since found out there is an issue with aroma installer. Tried 100 times (no exageration)since then to flash that rom and it gets to 30% installed and then reboots into TWRP. TWRP won't then let me do anything of substance. TWRP is also telling me I am now unrooted when I attempt to reboot into recovery from within twrp.The exact order is, flash rom - gets to 30% - reboots into a white screen (not recovery) that says HTC One, quietly brilliant, and then within 10 seconds it automatically reboots into TWRP.
4) On recomendation from rom developer, attempted to flash CWM via fastboot and it flashed fine, fastboot states the flash is sucessful but then when I reboot into recovery it's still TWRP. So CWM appears to have flashed but hasn't for some reason.
And that's where I am. Tried to flash CWM, tried to push rom to sd card, no luck.
Any ideas?
Try to flash without aroma... Replace the meta inf folder with the one linked in the op so it doesn't utilize aroma
Sent from my HTC One using Tapatalk 2
thesparky007 said:
Try to flash without aroma... Replace the meta inf folder with the one linked in the op so it doesn't utilize aroma
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Tried to do that yesterday and it wouldn't push. Trying again right now so I can give an exact error message.
What do u mean it wouldn't push?
Sent from my HTC One using Tapatalk 2
OK, I've followed the instructions and now have a zip ready to be pushed/flashed.
My question is, would you reccomend flashing it directly to device in fastboot or push to sd card and flash from there?
thesparky007 said:
What do u mean it wouldn't push?
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Kept getting errors whenever I tried to flash or push to sd card
When u extract the meta inf folder what all do u see in the root of that folder
Sent from my HTC One using Tapatalk 2
losangeles100 said:
I was talking about this problem over in the trickdroid thread, simply because it was trickdroid I was flashing but in fairness to that thread I don't want to clutter it with an endless amount of questions, repeating myself over and over, when people are simply there to review the rom/tweaks. I will give my issues in the correct order as best as I can remember, bottom line is I'm caught in a TWRP bootloop.
1) Picked up phone and unlocked bootloader and rooted via all-in-one toolkit. Confirmed root by downloading Titanium, so at this point I am stock rooted with zero issues.
2) Having installed latest TWRP at time of root I immiedietly backed up the stock rom, which I then copied to computer, so I do have this backed up and it's also visible (though unflashable) in TWRP under internal storage.
3) Flashed Trickdroid, which hung on 'install,' and I've since found out there is an issue with aroma installer. Tried 100 times (no exageration)since then to flash that rom and it gets to 30% installed and then reboots into TWRP. TWRP won't then let me do anything of substance. TWRP is also telling me I am now unrooted when I attempt to reboot into recovery from within twrp.The exact order is, flash rom - gets to 30% - reboots into a white screen (not recovery) that says HTC One, quietly brilliant, and then within 10 seconds it automatically reboots into TWRP.
4) On recomendation from rom developer, attempted to flash CWM via fastboot and it flashed fine, fastboot states the flash is sucessful but then when I reboot into recovery it's still TWRP. So CWM appears to have flashed but hasn't for some reason.
And that's where I am. Tried to flash CWM, tried to push rom to sd card, no luck.
Any ideas?
Click to expand...
Click to collapse
Okay LA. One quick and very basic question? You said you rooted the phone and you know because you downloaded and installed Titanium. Titanium does NOT need root for simple backups so that is no way to make sure you have root. To verify root, when you boot into bootloader/recovery, make sure it says "unlocked" and "tampered" at the top. I know it is basic but nothing will work without it. If it shows that, we can work from there. You should be able to just copy the file over to your SD card on the phone if your computer sees it.
frodoboy said:
Okay LA. One quick and very basic question? You said you rooted the phone and you know because you downloaded and installed Titanium. Titanium does NOT need root for simple backups so that is no way to make sure you have root. To verify root, when you boot into bootloader/recovery, make sure it says "unlocked" and "tampered" at the top. I know it is basic but nothing will work without it. If it shows that, we can work from there. You should be able to just copy the file over to your SD card on the phone if your computer sees it.
Click to expand...
Click to collapse
Good points, and yes, i'm unlocked and tampered. What I actually meant was TB stated 'rooted.'
thesparky007 said:
When u extract the meta inf folder what all do u see in the root of that folder
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
The new meta.inf now contains: com folder, CERT.RSA, CERT.SF, MANIFEST.MF
losangeles100 said:
The new meta.inf now contains: com folder, CERT.RSA, CERT.SF, MANIFEST.MF
Click to expand...
Click to collapse
Make sure it zips up properly and try again. If that doesn't flash try flashing the original zip
Sent from my HTC One using Tapatalk 2
Hey, Mike
We can take this here from PMs
Not sure on the zip you are trying to do, but would still try to get off twrp 2.5.0.0.
and fastboot the 2.3.3.0 twrp image i sent you. then try flashing rom after all wipes in recovery, not aroma. and make sure you fastboot the boot image from command window right after you flash rom. then erase cache then reboot to bootloader then reboot system. usually after first boot I reboot again wipe caches then reboot system--
losangeles100 said:
Good points, and yes, i'm unlocked and tampered. What I actually meant was TB stated 'rooted.'
Click to expand...
Click to collapse
I take it that letting the battery drain didn't help? Does ADB find the phone now? by the way, without S-OFF, it is almost impossible to brick your phone so we'll get there eventually!
Rug, firstly, thanks for going above and beyond, you're a credit to XDA and I for one really appreciate your help.
Now the weirdness: flashed the TWRP image you gave me and erased cache and rebooted into recovery and it's the original twrp. It definetly flashed correctly, said 'flashed' 'ok' so that is really weird. It simply isn't sticking. And just to clarify, fastboot sees the phone and everything went as it always has, except the end result.
frodoboy said:
I take it that letting the battery drain didn't help? Does ADB find the phone now? by the way, without S-OFF, it is almost impossible to brick your phone so we'll get there eventually!
Click to expand...
Click to collapse
Letting the battery drain is easier said than done on this bad boy
I'm down to 45% and not charging at all so as soon as I get to zero I will let you know. I'm actually starting to pin too much god damned hope on that! lol
Ok when you flashed CWM in the bootloader you complained that it still booted into TWRP, did you try flashing it again and then erasing cache while still in fastboot then booting into the recovery?
losangeles100 said:
Letting the battery drain is easier said than done on this bad boy
I'm down to 45% and not charging at all so as soon as I get to zero I will let you know. I'm actually starting to pin too much god damned hope on that! lol
Click to expand...
Click to collapse
boy this is a stumper! Can you reflash the original stock ROM and relock the bootloader and see if you go back to at least a working phone? Then you can unlock the bootloader again choosing CWM this time and then try to reflash TrickDroid? Also, do you have Superuser installed? I think you said you did. Just see if you can start over to at least recover your phone. Something went wrong with the initial steps to cause it to freeze up like that.
When flashng zip without aroma I get this error in cmd:
{
"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"
}
bobruels44 said:
Ok when you flashed CWM in the bootloader you complained that it still booted into TWRP, did you try flashing it again and then erasing cache while still in fastboot then booting into the recovery?
Click to expand...
Click to collapse
I believe I did but you make a valid point.
frodoboy said:
boy this is a stumper! Can you reflash the original stock ROM and relock the bootloader and see if you go back to at least a working phone? Then you can unlock the bootloader again choosing CWM this time and then try to reflash TrickDroid? Also, do you have Superuser installed? I think you said you did. Just see if you can start over to at least recover your phone. Something went wrong with the initial steps to cause it to freeze up like that.
Click to expand...
Click to collapse
Superuser was installed but when I reboot into recovery I get a message from twrp saying 'you're not rooted, would you like to flash SU now.' When I swipe to flash it does nothing, although SU is on internal storage.
Just to add, the backup I made is visible in the TWRP folder in storage but cannot be accessed, and when I hit the restore button nothing is listed.
Regarding reflashing stock original, I'd pay 100 bucks to anyone in this thread who could get me back to stock.
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?
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
Hello Everybody !!
I'm not a developer but I successfully rooted my HTC Desire 10 Pro and since many people seem to have problems,I decided to make a guide. The computer OS I used was Windows 10 but if you use linux, I'm sure you can adapt to the method.
1. First install device drivers and download ADB fastboot from this thread
2. Dowload TWRP 3.1 for your phone variant from here and move it to the ADB fastboot folder and rename the img file to "twrp"
twrp-3.1.1-a56dj_pro_uhl.img Desire 10 Pro Single SIM
twrp-3.1.0-a56dj_pro_dugl.img Desire 10 Pro Dual SIM
3. Press shift + right click and select open command window here.
4. Go to developer options on your phone and select Allow USB debugging and Allow bootloader to be unlocked.
(Very important step)
5. Connect the phone to your PC and check the connection by typing the following in the command prompt.
adb devices
If it shows only one device, you're good to go!!
Otherwise remove any other connected phones/devices and disable any Android emulators if you have them. (Like Bluestacks)
6. Go to HTCDev website and unlock your bootloader, (HTCDev will give those instructions), the phone model isn't shown but select "other supported models".
(Warning - This will erase all your data so make a backup)
7. Type the following into the command window to boot your device into bootloader/fastboot mode:
adb reboot bootloader
8. Once your device boots into bootloader mode, type this into the command line.
fastboot flash recovery twrp
9. Once TWRP is successfully flashed on your device, type this final command to reboot your device.
fastboot reboot
10. Download SuperSu latest version
SuperSu v2.82
11. Copy the SuperSu zip file to your phone internal storage
12. Then type this command to go to TWRP,
fastboot reboot recovery
13. Wait for TWRP to load and tap Install
14. Select the SuperSu zip file and flash it
15. After flashing finishes, tap on Reboot System
16. Congradzz !!! Your HTC Desire 10 Pro is rooted now.
Now you can further customize if you like by installing Xposed.
Thanks for following and please reply in the comments if I have made any mistake or if you need more help.
And I'm NOT responsible for any damages even though it's unlikely to happen.
Edit : This was confirmed to be working on version 1.18.400.20 and it doesnt seem to work on 2.13.709.20. Please have a RUU if you're trying on a version in between, just to be on the safe side.
Credit to
@sabpprook and @jemmini for the TWRP variants
@Snoop05 for the ADB Fastboot Installer
@Chainfire for SuperSu
And all of XDA for being awesome ?
Any chance on doing a full backup before installing TWRP, as I don't have a default recovery of 1.18.400.20 dugl dual sim and still hope for OTA?
I hoped for "fastboot boot recovery" but I think only with nougat firmware was reimplemented.
Thanks
I think HTC disabled remote recovery booting so you'll have to replace the stock recovery.img
But I think I saw the stock recovery.img for our phone in another thread. You can download it and flash in case of a new update.
And what do u mean nougat firmware was reimplemented? Did you get the Nougat update ?
FireStorm919 said:
I think HTC disabled remote recovery booting so you'll have to replace the stock recovery.img
But I think I saw the stock recovery.img for our phone in another thread. You can download it and flash in case of a new update.
And what do u mean nougat firmware was reimplemented? Did you get the Nougat update ?
Click to expand...
Click to collapse
Can u redirect me to that stock recovery, pls?
The nougat firmware for the m9 had implemented boot to recovery...
process failed
Hi everyone,
tried this process on a A56DJ_PRO_DUGL with system OS-2.13.709.20 and the last step (supersu 2.82) failed, it said unable to modify boot image and aborted.
Used magisk 15 and it was able to modify boot but it did not boot, always asked for password for encrypted data, even after factory reset. I tried to restore the backup I previously made with twrp 3.1.1.0 (boot + system) but now it does not boot. Download, bootloader and twrp works anyway.
I will try to fix it, hope it serves as guidance to anyone trying to root the same 10 Pro version.
david_montes said:
Hi everyone,
tried this process on a A56DJ_PRO_DUGL with system OS-2.13.709.20 and the last step (supersu 2.82) failed, it said unable to modify boot image and aborted.
Used magisk 15 and it was able to modify boot but it did not boot, always asked for password for encrypted data, even after factory reset. I tried to restore the backup I previously made with twrp 3.1.1.0 (boot + system) but now it does not boot. Download, bootloader and twrp works anyway.
I will try to fix it, hope it serves as guidance to anyone trying to root the same 10 Pro version.
Click to expand...
Click to collapse
Try flashing the uninstall zip for magisk.
Also, if u have a backup, try to wipe boot and system partitions before restoring.
Good luck
Fain11 said:
Try flashing the uninstall zip for magisk.
Also, if u have a backup, try to wipe boot and system partitions before restoring.
Good luck
Click to expand...
Click to collapse
I did try to uninstall magisk but it gets stuck in the boot process (only htc logo), the same thing happens with the backup I made with twrp (only htc logo), the best result so far is applying magisk to the boot, then the system starts but keeps asking me to decrypt the storage, the exact message is "The password you have entered is correct, but unfortunately your data is corrupt" I did factory reset but does not solve the problem, it keeps asking for the password.
Also RUU for my OS-2.13.709.20 is not available so I'm currently stuck.
These things get harder and harder every day
Desire 10 Pro recovered
Finally the last option was to fully stock flash with RUU 2.13.709.20, but now I am back to step one.
At least it works
---------- Post added at 04:20 PM ---------- Previous post was at 04:08 PM ----------
Been human means to keep trying, so I tried again, now I did full factory wipe before applying supersu 2.82 (not working) or magisk 15 (works but keeps asking for a password to decrypt storage).
So I can confirm this procedure does not work with OS-2.1.3.709.20.
If any of you is able to root this version I will be glad to try again in the future but by now I'm done with htc 10 pro.
Happy new year everyone!
thanks for the guide, I was waiting for it and just came in time
I am wondering if this method will work on a56dj_pro_dugl software number 1.18.401.20 ?
what software number did you tried it on ?
thanks for the help
thekingomar said:
thanks for the guide, I was waiting for it and just came in time
I am wondering if this method will work on a56dj_pro_dugl software number 1.18.401.20 ?
what software number did you tried it on ?
thanks for the help
Click to expand...
Click to collapse
It has been confirmed to be working on 1.18.400.20
Please make a backup before u try because this doesnt seem to work on newer ones like 2.13.709.20
Please leave a reply here if u get it working.
?
Fain11 said:
Can u redirect me to that stock recovery, pls?
The nougat firmware for the m9 had implemented boot to recovery...
Click to expand...
Click to collapse
Sorry for the delay,
I couldn't find that link either so I extracted it from a RUU for variant a56dj_pro_dugl
Here you go
https://drive.google.com/file/d/1FxKDDOXISNTf5uQJT90nlw6tuClJaX9o/view?usp=drivesdk
Hope this helps
???
thanks for the guide again,
after pulling my courage together I decided to do it on my a56dj_pro_dugl software number 1.18.401.20
everything worked fine from the top to step 14 but there is one problem, flashing the SuperSU zip file is failed,
I tried to re-download it and not renaming it but still the same, here is the log
{
"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"
}
any suggestions ?
never mind
just rooted it using Magisk , apparently SuperSU is not applicable on my device
I used the same method as SuperSU zip
downloaded the latest version of Magisk (v 15.3) zip file and install it using TWRP
and everything is fine ever since
thanks folks for being awsome developers :laugh:
Required Video
Hi Member,
Can you please upload step by step video for root the HTC Desire 10 pro.
waiting
warnning !!! htc desire 10 pro os 2.13.709.23 taiwan
Don't try to root,
it seem rooted but no , if you wipe your soft brick, and difficult or impossible,
to fine the stosk rom os 2.13.709.23 !!!!
No body can help !!!
Mykyzo007 said:
Don't try to root,
it seem rooted but no , if you wipe your soft brick, and difficult or impossible,
to fine the stosk rom os 2.13.709.23 !!!!
No body can help !!!
Click to expand...
Click to collapse
Did you manage to unbrick?
yes
dearbasheer said:
Did you manage to unbrick?
Click to expand...
Click to collapse
yes i manage to unbrick, i'am waiting to see the rom .
But i need help
Unable to flash recovery
When unlocking bootloader I selected any other supported since desire 10 pro isn't listed. Process went through but when flashing twrp I'm getting error. Commad not allowed whereas it shows unlocked
FireStorm919 said:
Hello Everybody !!
I'm not a developer but I successfully rooted my HTC Desire 10 Pro and since many people seem to have problems,I decided to make a guide. The computer OS I used was Windows 10 but if you use linux, I'm sure you can adapt to the method.
1. First install device drivers and download ADB fastboot from this thread
2. Dowload TWRP 3.1 for your phone variant from here and move it to the ADB fastboot folder and rename the img file to "twrp"
twrp-3.1.1-a56dj_pro_uhl.img Desire 10 Pro Single SIM
twrp-3.1.0-a56dj_pro_dugl.img Desire 10 Pro Dual SIM
3. Press shift + right click and select open command window here.
4. Go to developer options on your phone and select Allow USB debugging and Allow bootloader to be unlocked.
(Very important step)
5. Connect the phone to your PC and check the connection by typing the following in the command prompt.
adb devices
If it shows only one device, you're good to go!!
Otherwise remove any other connected phones/devices and disable any Android emulators if you have them. (Like Bluestacks)
6. Go to HTCDev website and unlock your bootloader, (HTCDev will give those instructions), the phone model isn't shown but select "other supported models".
(Warning - This will erase all your data so make a backup)
7. Type the following into the command window to boot your device into bootloader/fastboot mode:
adb reboot bootloader
8. Once your device boots into bootloader mode, type this into the command line.
fastboot flash recovery twrp
9. Once TWRP is successfully flashed on your device, type this final command to reboot your device.
fastboot reboot
10. Download SuperSu latest version
SuperSu v2.82
11. Copy the SuperSu zip file to your phone internal storage
12. Then type this command to go to TWRP,
fastboot reboot recovery
13. Wait for TWRP to load and tap Install
14. Select the SuperSu zip file and flash it
15. After flashing finishes, tap on Reboot System
16. Congradzz !!! Your HTC Desire 10 Pro is rooted now.
Now you can further customize if you like by installing Xposed.
Thanks for following and please reply in the comments if I have made any mistake or if you need more help.
And I'm NOT responsible for any damages even though it's unlikely to happen.
Edit : This was confirmed to be working on version 1.18.400.20 and it doesnt seem to work on 2.13.709.20. Please have a RUU if you're trying on a version in between, just to be on the safe side.
Credit to
@sabpprook and @jemmini for the TWRP variants
@Snoop05 for the ADB Fastboot Installer
@Chainfire for SuperSu
And all of XDA for being awesome
Click to expand...
Click to collapse
Could u do me a favor ?
I just need an .apk from a system app called "sangam IME" it's a keyboard & u can extract the .apk with lucky patcher or any other similar apps
I need it like hell , caused I removed it & then realised it's the only keyboard that pops up in encryption page at startup & not having it means I can only reset my phone when I have a physical keyboard connected with otg ! Thanks alot
Sangam IME
seyyed.april said:
Could u do me a favor ?
I just need an .apk from a system app called "sangam IME" it's a keyboard & u can extract the .apk with lucky patcher or any other similar apps
I need it like hell , caused I removed it & then realised it's the only keyboard that pops up in encryption page at startup & not having it means I can only reset my phone when I have a physical keyboard connected with otg ! Thanks alot
Click to expand...
Click to collapse
Hi!
Sorry for the delay, I havent checked my inbox for quite some time.
I searched around for this Sangam IME everywhere in,
/system/app
/system/priv-app
/data/app
/data/app-private
But I couldnt find it. I even tried using 3rd party apps like you suggested but it simply doesnt seem to exist.
Even a quick Google search didnt give me any leads.
So are you sure the name is correct ?
Or maybe any more ideas on where to look for the apk ?
Sorry I couldnt be of more help
Hello,
I post here after 12 hours of continuous search and attempts at fixing things on my own, which may have dug me deeper into trouble than if I've asked for a tailored solution to this issue. Apologies for repetitiveness if I've failed to find answers elsewhere.
I was running LOS 15.1 with custom kernel and maybe the 5.0.8 firmware or lower. I don't recall the version.
In an attempt to flash LOS 16.0, I performed a nandroid backup, but didn't back up my internal storage. That was stupid of me
I grabbed all the files needed, and started by flashing the firmware version stated in the flashing guide for LOS 16., which was 9 point something.
Phone bricked, blank screen.
Got hold of a factory reset tool from an unbrick guide here, followed their steps to completion despite repeated failures in the MSMDownloader.
Now my phone boots in fastboot mode only, adb on PC neither can detect nor interact with the phone, and it is stuck in a md5 checksum bootloop with "modem" and "dsp" in the red, and all attempts to boot into recovery lead back to the md5 checksum screen.
On fastboot mode, "Bootloader version" and "baseband version" are both blank.
This is all I know to provide at the moment. If there is any way to salvage the phone with the internal storage intact, I would prefer that please. But I won't look a gift horse in the mouth at this point if I ultimately have to wipe everything clean to fix the phone.
bump pls
even bad news is appreciated
Even fastboot cant saw your device thru "fastboot devices"? Do your ADB drivers up-to-date?
Javellinh said:
Even fastboot cant saw your device thru "fastboot devices"? Do your ADB drivers up-to-date?
Click to expand...
Click to collapse
Thank you for answering.
Fastboot can see and use the device. Flashing is possible through it.
ADB cannot. I'm not sure if it's the latest version on my PC, but I recently had the phone connected to a different PC with a recent ADB installation and the results were the same. ADB doesn't see the phone.
Hmm.. does phone in TWRP works like USB storage?
Phone fails to boot into recovery.
I flashed TWRP but it always boots into the failed md5 checksum anyway.
Recovery doesn't work.
{
"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"
}
swumo said:
Phone fails to boot into recovery.
I flashed TWRP but it always boots into the failed md5 checksum anyway.
Recovery doesn't work.
Click to expand...
Click to collapse
Worth noting is that TWRP flashing causes the recovery: ok message to also read as recovery:failed.
Flashing the stock recovery that came with the unbrick tool using fastboot makes it recovery: ok
swumo said:
Worth noting is that TWRP flashing causes the recovery: ok message to also read as recovery:failed.
Flashing the stock recovery that came with the unbrick tool using fastboot makes it recovery: ok
Click to expand...
Click to collapse
you can boot to stock recovery?
vinoxflame said:
you can boot to stock recovery?
Click to expand...
Click to collapse
It won't boot into any recovery, stock or otherwise. Only brings up the screen pictured above.
EDIT: By "stock recovery" I mean whatever the unbrick tool had flashed into the phone using the MSMDownloader utility.
The version of OOS included in the tool is mentioned as 3.2 or some dated system. Maybe a more recent recovery might work?
I can't find a standalone, recent stock recovery image. I'd flash one if I found it.
swumo said:
It won't boot into any recovery, stock or otherwise. Only brings up the screen pictured above.
EDIT: By "stock recovery" I mean whatever the unbrick tool had flashed into the phone using the MSMDownloader utility.
The version of OOS included in the tool is mentioned as 3.2 or some dated system. Maybe a more recent recovery might work?
I can't find a standalone, recent stock recovery image. I'd flash one if I found it.
Click to expand...
Click to collapse
are you using op3 or 3t?
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
vinoxflame said:
are you using op3 or 3t?
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Click to expand...
Click to collapse
I'm using a OP3T.
The link you provided points to a similar guide to the one I used. https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-tool-3t-unbrick-data-babloo-t3737791
I've already performed these steps, and the md5 problem happened after the process mentioned was completed.
swumo said:
Fastboot can see and use the device. Flashing is possible through it.
ADB cannot. I'm not sure if it's the latest version on my PC, but I recently had the phone connected to a different PC with a recent ADB installation and the results were the same. ADB doesn't see the phone.
Click to expand...
Click to collapse
Fastboot and adb will never work at the same time, by definition. If Fastboot works, you are in fastboot mode. adb only works in OS or alternately in TWRP, and will never work in fastboot mode.
redpoint73 said:
Fastboot and adb will never work at the same time, by definition. If Fastboot works, you are in fastboot mode. adb only works in OS or alternately in TWRP, and will never work in fastboot mode.
Click to expand...
Click to collapse
In this case, how would I get into ADB if neither the OS nor TWRP want to boot past the the error?
Are there steps in fastboot that I can take to fix this phone?
swumo said:
In this case, how would I get into ADB if neither the OS nor TWRP want to boot past the the error?
Click to expand...
Click to collapse
You simply can't. adb will only work in OS or TWRP, period. Nothing you can do can change that fact. You're stuck with fastboot.
swumo said:
Are there steps in fastboot that I can take to fix this phone?
Click to expand...
Click to collapse
I can't personally think of anything. I just wanted to point out the fruitlessness of trying to use adb, so you don't waste time trying to get it to work (since it never will).
swumo said:
Hello,
I post here after 12 hours of continuous search and attempts at fixing things on my own, which may have dug me deeper into trouble than if I've asked for a tailored solution to this issue. Apologies for repetitiveness if I've failed to find answers elsewhere.
I was running LOS 15.1 with custom kernel and maybe the 5.0.8 firmware or lower. I don't recall the version.
In an attempt to flash LOS 16.0, I performed a nandroid backup, but didn't back up my internal storage. That was stupid of me
I grabbed all the files needed, and started by flashing the firmware version stated in the flashing guide for LOS 16., which was 9 point something.
Phone bricked, blank screen.
Got hold of a factory reset tool from an unbrick guide here, followed their steps to completion despite repeated failures in the MSMDownloader.
Now my phone boots in fastboot mode only, adb on PC neither can detect nor interact with the phone, and it is stuck in a md5 checksum bootloop with "modem" and "dsp" in the red, and all attempts to boot into recovery lead back to the md5 checksum screen.
On fastboot mode, "Bootloader version" and "baseband version" are both blank.
This is all I know to provide at the moment. If there is any way to salvage the phone with the internal storage intact, I would prefer that please. But I won't look a gift horse in the mouth at this point if I ultimately have to wipe everything clean to fix the phone.
Click to expand...
Click to collapse
I forgot a detail in the middle of the story.
Right after I flashed the pie firmware, it restarted and I was given a prompt that said something along the lines of "Flash successful and everything, but decryption failed. You will lose all data if you boot, are you sure?"
I turned off the phone, from there it bricked with a blank screen. It was then that I got the unbrick tool and went through the rest of the earlier story.
redpoint73 said:
You simply can't. adb will only work in OS or TWRP, period. Nothing you can do can change that fact. You're stuck with fastboot.
I can't personally think of anything. I just wanted to point out the fruitlessness of trying to use adb, so you don't waste time trying to get it to work (since it never will).
Click to expand...
Click to collapse
I appreciate you reaching out and offering closure. It seems this phone is fried.
Thank you.
I got past the MD5 checksum hurdle, and I flashed TWRP. It works.
I can't access internal storage to flash anything from the phone, not even the TWRP nandroid backup, but ADB is an option again.
Decryption refuses to take my password even though it's correct.
I do have a backup of the nandroid on my PC. Could I flash that via ADB?
swumo said:
I got past the MD5 checksum hurdle, and I flashed TWRP. It works.
I can't access internal storage to flash anything from the phone, not even the TWRP nandroid backup, but ADB is an option again.
Decryption refuses to take my password even though it's correct.
I do have a backup of the nandroid on my PC. Could I flash that via ADB?
Click to expand...
Click to collapse
It would help others who get into the same situation if you post how you got passed the MD5 checksum hurdle.
If you can get into TWRP I would suggest you use the latest version 3.3.1-0 and use wipe>format data (not wipe>advanced wipe) which will clear the encryption. It will give you an ext4 data partition, which is fine. If you want to change it back to f2fs use wipe>advanced wipe to reformat it to f2fs.
I don't recommend using an unencrypted phone so my next step is to copy from your PC to the phone the ROM zip file and anything else you need to flash. I would flash the full OOS zip and let it boot up as this will automatically encrypt your data. It will also replace TWRP with the stock recovery but you can flash TWRP again using fastboot. You can then go back to TWRP and set things up the way you want, including restoring the backup you have.
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
It would help others who get into the same situation if you post how you got passed the MD5 checksum hurdle.
If you can get into TWRP I would suggest you use the latest version 3.3.1-0 and use wipe>format data (not wipe>advanced wipe) which will clear the encryption. It will give you an ext4 data partition, which is fine. If you want to change it back to f2fs use wipe>advanced wipe to reformat it to f2fs.
I don't recommend using an unencrypted phone so my next step is to copy from your PC to the phone the ROM zip file and anything else you need to flash. I would flash the full OOS zip and let it boot up as this will automatically encrypt your data. It will also replace TWRP with the stock recovery but you can flash TWRP again using fastboot. You can then go back to TWRP and set things up the way you want, including restoring the backup you have.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
Thank you for dropping by.
Regarding the couple of errors in the MD5 checksum, "modem" and "dsp", the problem lied in that I didn't know which files I'm supposed to flash using fastboot to fill their spots.
By referring to the forum post of the firmware here, I found one workaround was to "consult META-INF/com/google/android/updater-script in the flashable zip of the firmware ... to check which file from the firmware-update directory goes to which partition."
From there, I inferred that "modem" takes the file named NON-HLOS.bin, and that "dsp" takes adspso.bin
Flashed them via fastboot, and I was greeted by a successful boot to stock OOS 3.1.2, the version provided by the unbrick tool I used.
However, it seems that the damage done to the phone (either by the failed firmware flash or the unbrick tool) has led to the internal storage being corrupted, or perhaps the damage was done to how the system decrypts internal storage. I am a medical student, so most of these intricacies are way out of my league.
I was hoping to recover the internal storage, but would gladly part with the data if it means I can use the phone again. There was nothing particularly important on the phone that the TWRP backup didn't have.
Pardon me, but which file system would be most suitable for each partition?
The Wipe>Advanced Wipe menu offers several file systems for several partitions. I'm inclined to leave everything as it is, but should I perhaps format the /system partition as f2fs for instance?