Related
Hi everybody,
after endless nights and days of experimenting and crying I ask for your help.
My Aim: rooting my HTC One S C2.
So here is my story:
In my first attempt I unlocked my bootloader and tried to put a Custom Recovery on my phone. It failed. I got always stuck at the HTC screen with the red writing underneath the logo ("This build is for ...").
I then found out that I need the superboot.bat to root my phone.
So I proceeded to re-lock my phone and put a RUU on it to get back to the original Recovery.
All went well, so I unlocked my phone again via htcdev.com.
After that I tried to run the superboot.bat but again I am stuck at the HTC screen with the red writing!
I know that this screen should only appear for a few seconds and the phone should go into recovery but I am always stuck endless in this screen. To get out of it I have to soft reset my phone.
So I am not able to root it.
In a video I saw that on other phones the HTC screen with red writing has some kind of a "loading bar" on the upper right which appears after trying to access the recovery.
Well this bar doesn't even appear on my phone
Please help me I really don't know what to do further
same issue here, so subscribing to thread!
If you can get to download mode try to flash stock firmware with Odin. Search for a guide on youtube.
--------------------------------------------
Sent from my GT-S5830 running ImaGinary ICS.
Thank if it helped.It's there for a reason
Ähm isn't Odin for Samsung devices?
This is about HTC... Or does it work for both?
i recommend reading through this guide to rooting the one s. i've rooted quite a few phones using this method and it has worked flawlessly every time
http://forum.xda-developers.com/showthread.php?t=1583427
@HidaKureku - thats where i've got stuck; end of part two.
the recovery image seems to flash fine (both of them), and i've done the CWM recovery multiple times (some sites sugest that it works on the second attempt).
try to boot to recovery, and as per the OP it just sits there saying that it's for "This build is for HTC use only..." or whatever it says. no further. I've left it for 10mins in this state have have to power it off.
i have found that when i boot back to the UK retail ROM, it comes up with an error and wants to send it to HTC (i haven't yet been able to grab the error though).
has anyone sucessfully flashed recovery with the hboot 9.02.0001 image? i've seen a post on modaco with a user having the same problems as in this thread....
are you sure you're model has the S4 processor? if not, try this thread
http://forum.xda-developers.com/showthread.php?t=1785777&highlight=twrp
looks like i'm on the s3 version! twrp2 doesn't work either - same issue. (using openrecovery-twrp-2.2.2.0-ville.img)
seems the UK is one of these 'select' countries.
anyway - even an S3 compatible recovery isnt working....
I hope in not threadjacking here. @OP - if im intruding let me know and i'll create my own thread
No you are not intruding as I have exactley the same problem as you!
I'm glad that I'm not the only one I started to think I'm doing something completely wrong.
It's like the stock recovery is damaged even with the RUU version.
I just cannot get past this screen with the red warning!
My HTC One S is kind of new (about 3 weeks old). Maybe something changed with new models?
good news; i'm recovery-ed
you need 'openrecovery-twrp-2.2.2.1-villec2.img'.
It was 'tricky' to find, as the 'villec2' image doesnt appear to have any public links. As per the thread http://forum.xda-developers.com/showthread.php?t=1785777, Get 'goomanager', allow it to find and download recovery image, however, it wont sucessfully apply with goomanager (you dont have root yet).
It will download this recovery image to to /mnt/sdcard/goomanager/ (you can change/confirm it in goomanager menu options)
mount storage & copy this to your computer. Use fastboot to flash as per the unlock/recovery/root guide.
i dont mind hosting the file, but the above should be the quickest way
Yes!!!
That's it!!
Thank you so much
You made my day
Thread can be marked as solved!
now that you know you have the s3 processor be careful which roms you flash, make sure they are compatible with your version. the rom i'm running (check my signature for the link) is supposed to be compatible with both. but just read carefully and flash responsibly
HidaKureku said:
now that you know you have the s3 processor be careful which roms you flash, make sure they are compatible with your version. the rom i'm running (check my signature for the link) is supposed to be compatible with both. but just read carefully and flash responsibly
Click to expand...
Click to collapse
Thanks for the heads up, although that JB ROM in your sig says S4 in the title (thats about as far as i got )
@Schlengge - glad your sorted too i didnt even realise i was on s3 untill tonight; i thought all UK HOS's were s4's - seems not.
yeah XD i went back and looked at it and realized i got it confused with one rom i saw that was supposedly compatible with both processors (which struck me as odd) but there are a few roms out there for the s3, sadly not as many as for the s4, but you should be able to find one you're happy with. best of luck
veehexx said:
good news; i'm recovery-ed
you need 'openrecovery-twrp-2.2.2.1-villec2.img'.
It was 'tricky' to find, as the 'villec2' image doesnt appear to have any public links. As per the thread http://forum.xda-developers.com/showthread.php?t=1785777, Get 'goomanager', allow it to find and download recovery image, however, it wont sucessfully apply with goomanager (you dont have root yet).
It will download this recovery image to to /mnt/sdcard/goomanager/ (you can change/confirm it in goomanager menu options)
mount storage & copy this to your computer. Use fastboot to flash as per the unlock/recovery/root guide.
i dont mind hosting the file, but the above should be the quickest way
Click to expand...
Click to collapse
well, thanks for that advice. It is kinda confusing to find a recovery for c2 version of the ONE S, cause any other recovery will not work with it. The twrp-team should definatly add the link to that on their website.
Tried to root my phone that just came in the mail today. I am stuck at the mi screen.
Tried to download from official site but the download keeps failing.
A mirror to the new update so I can flash stock and any advice would be great!
Thanks all
Which version are you talking about?
Latest is 6.6.6.0 as far as i know.
The version with 6.6.8.0 is only for Asia and not released for the world.
About rooting: use the toolkit v4 (and not v3)
First install TWRP via that toolkit and only then start the root proces.
Worked for me, but if you do in another order, you will get stuck.
http://en.miui.com/thread-117336-1-1.html
Thanks for the reply and the quick guide to rooting it. I may have been trying it with something other than V4 which could have caused the stall at the "mi" screen.
I think I might just have to wait until their servers are back up because I'm pretty sure ill have to do the fastboot flashing method.
@gotmicah
I had problems downloading too the last days...slow speed and after a few MB it kept failing. In miui forum i found a tip about this tool http://www.freedownloadmanager.org/
Just copy the download link in there, worked great
And i think if you install twrp and flash your Rom, it should be enough.
Yeah, and one more thing. Xposed doesn't work in MIUI, but it does work on my build of CM12.1. Don't try using Xposed, caused a lot of problems for me (like apps disappearing etc) and don't use OTA. Download the update zip from the website and flash manually. Just thought I'd put this out there
rob rich said:
@gotmicah
I had problems downloading too the last days...slow speed and after a few MB it kept failing. In miui forum i found a tip about this tool freedownloadmanager
Just copy the download link in there, worked great
And i think if you install twrp and flash your Rom, it should be enough.
Click to expand...
Click to collapse
Thanks dude, you're the true MVP here! I used something similar to freedownloadmanager and was able to get the newest fastboot version in around 2 hours! Sounds slow, but better than a failed DL (I had to remove the link in the quote because im a new member)
Evil Tak said:
Yeah, and one more thing. Xposed doesn't work in MIUI, but it does work on my build of CM12.1. Don't try using Xposed, caused a lot of problems for me (like apps disappearing etc) and don't use OTA. Download the update zip from the website and flash manually. Just thought I'd put this out there
Click to expand...
Click to collapse
This is useful, thanks!
ALSO
I just want to let everyone know that may be searching because of a bad flash or similar situation...
If your flash keeps failing, switch computers and try again. My flash would only take a few seconds, say successful but the phone would be stuck in fastboot mode. I installed the same exact files/ drivers on another laptop, tried again and within a few minutes had a perfectly function phone again. Of course this was after hours of frustration and it ended up just being the computer I was flashing it on...
I'm in the middle of trying to install TWRP tried multiple versions and different sites and flashed at least 5 different TWRP images and cannot boot into TWRP. I just end up at the EMIU recovery. Is TWRP not functioning for this model?
EMUI: 5.0
Android: 7.0
Hi there @WillDaBeast69. I actually purchased one of these and want to root it and such. I'm gonna be in your thread a bit trying to help you find a way and also help me and everyone else in the process to find a solution. If a solution is already available then hopefully someone else will post it.
AFAIK - currently I don't see anything regarding the L14 which is the 64GB version.
What I'd like you to do first is get back on the stock firmware. Unless you know where to find one, I'm going to say look for an UPDATE.APP somewhere for the L14. I'm going to do some searching as well. If you find it please post the link. If you find one that works and it's not on an official site (Honor site) then I'll also download it and upload to a central location that everyone can get to it.
Once you're back on the stock firmware, I'm going to ask you to try and get a TWRP image booted on the device. Not installed but booted. Once we have that up we can proceed.
*EDIT*
So after doing a bit of digging I found a link in someone's sig.
All thanks go to @Dominikrod for his sig which lead to this post.
https://forum.xda-developers.com/showpost.php?p=70396400&postcount=547
Full thread: https://forum.xda-developers.com/ho...-to-nougat-t3510275/post70396400#post70396400
But before we can proceed, we will need to get your phone back up and running if it's not already in a working state.
*EDIT*
So after following the instructions I got one of the L14's I have up and running rooted. The other one is giving me some trouble because I can't unlock the bootloader for some reason. Keeps telling me the code is wrong. Once I get it up and running I'll make sure I post pics of the process.
Confirmed working on EMUI5 - Android OS 7.
THANK YOU!!
khat17 said:
Hi there @WillDaBeast69. I actually purchased one of these and want to root it and such. I'm gonna be in your thread a bit trying to help you find a way and also help me and everyone else in the process to find a solution. If a solution is already available then hopefully someone else will post it.
AFAIK - currently I don't see anything regarding the L14 which is the 64GB version.
What I'd like you to do first is get back on the stock firmware. Unless you know where to find one, I'm going to say look for an UPDATE.APP somewhere for the L14. I'm going to do some searching as well. If you find it please post the link. If you find one that works and it's not on an official site (Honor site) then I'll also download it and upload to a central location that everyone can get to it.
Once you're back on the stock firmware, I'm going to ask you to try and get a TWRP image booted on the device. Not installed but booted. Once we have that up we can proceed.
*EDIT*
So after doing a bit of digging I found a link in someone's sig.
All thanks go to @Dominikrod for his sig which lead to this post.
https://forum.xda-developers.com/showpost.php?p=70396400&postcount=547
Full thread: https://forum.xda-developers.com/ho...-to-nougat-t3510275/post70396400#post70396400
But before we can proceed, we will need to get your phone back up and running if it's not already in a working state.
*EDIT*
So after following the instructions I got one of the L14's I have up and running rooted. The other one is giving me some trouble because I can't unlock the bootloader for some reason. Keeps telling me the code is wrong. Once I get it up and running I'll make sure I post pics of the process.
Confirmed working on EMUI5 - Android OS 7.
Click to expand...
Click to collapse
khat17 said:
Hi there @WillDaBeast69. I actually purchased one of these and want to root it and such. I'm gonna be in your thread a bit trying to help you find a way and also help me and everyone else in the process to find a solution. If a solution is already available then hopefully someone else will post it.
AFAIK - currently I don't see anything regarding the L14 which is the 64GB version.
What I'd like you to do first is get back on the stock firmware. Unless you know where to find one, I'm going to say look for an UPDATE.APP somewhere for the L14. I'm going to do some searching as well. If you find it please post the link. If you find one that works and it's not on an official site (Honor site) then I'll also download it and upload to a central location that everyone can get to it.
Once you're back on the stock firmware, I'm going to ask you to try and get a TWRP image booted on the device. Not installed but booted. Once we have that up we can proceed.
*EDIT*
So after doing a bit of digging I found a link in someone's sig.
All thanks go to @Dominikrod for his sig which lead to this post.
https://forum.xda-developers.com/showpost.php?p=70396400&postcount=547
Full thread: https://forum.xda-developers.com/ho...-to-nougat-t3510275/post70396400#post70396400
But before we can proceed, we will need to get your phone back up and running if it's not already in a working state.
*EDIT*
So after following the instructions I got one of the L14's I have up and running rooted. The other one is giving me some trouble because I can't unlock the bootloader for some reason. Keeps telling me the code is wrong. Once I get it up and running I'll make sure I post pics of the process.
Confirmed working on EMUI5 - Android OS 7.
Click to expand...
Click to collapse
Hoping you're still monitoring this thread or get a notification. I also just purchased the L14 and was disappointed to find that it is "special" as all the guides, firmware, etc that are available are for the L04. I was wondering what progress you've made since this post? Have you had any other issues, flashed custom ROMs, and if so, how did they work?
Also, have you had any luck finding current update.app/zip files for the L14? I found posts directing to an app called Firmware Finder which seems to pull up multiple copies but also read that those might somehow be locked and result in a brick/soft brick. Any help would be appreciated!
Thanks!
Sticky92 said:
THANK YOU!!
Click to expand...
Click to collapse
No problem. Anytime.
dsEVOlve said:
Hoping you're still monitoring this thread or get a notification. I also just purchased the L14 and was disappointed to find that it is "special" as all the guides, firmware, etc that are available are for the L04. I was wondering what progress you've made since this post? Have you had any other issues, flashed custom ROMs, and if so, how did they work?
Also, have you had any luck finding current update.app/zip files for the L14? I found posts directing to an app called Firmware Finder which seems to pull up multiple copies but also read that those might somehow be locked and result in a brick/soft brick. Any help would be appreciated!
Thanks!
Click to expand...
Click to collapse
From what's been happening to me, I think Huawei may be clamping down on allowing persons to unlock their bootloader and root the phones. I've not been able to get into the site at all - I've managed to root my wife's phone but mine.............nothing. Nothing works. I got the info directly from their site and it just won't work. I emailed them and they say that they don't assist individuals with bootloader unlock nor do they allow it - which seems to be new policy.
The instructions that are in the link I have works. As long as you got your bootloader unlocked you can install TWRP, SuperSU and root. If you go through the instructions in the link and need step-by-step assistance then just post back.
Error on FRD-L14 and B388
khat17 said:
No problem. Anytime.
From what's been happening to me, I think Huawei may be clamping down on allowing persons to unlock their bootloader and root the phones. I've not been able to get into the site at all - I've managed to root my wife's phone but mine.............nothing. Nothing works. I got the info directly from their site and it just won't work. I emailed them and they say that they don't assist individuals with bootloader unlock nor do they allow it - which seems to be new policy.
The instructions that are in the link I have works. As long as you got your bootloader unlocked you can install TWRP, SuperSU and root. If you go through the instructions in the link and need step-by-step assistance then just post back.
Click to expand...
Click to collapse
I try to install all the TWRP imgs on the links, I´m using the FRD-L14 B388, but after I reboot the phone after flashing the TWRP recovery pressing VOL + and VOL - , I received the message "Your device has been unlocked and cant be trusted.... Your device is booting now..." after some minutes it goes to EMUI recovery instead of TWRP.
Is there something I can do it to solve this issue?
Thanks in advanced!
sammyrano said:
I try to install all the TWRP imgs on the links, I´m using the FRD-L14 B388, but after I reboot the phone after flashing the TWRP recovery pressing VOL + and VOL - , I received the message "Your device has been unlocked and cant be trusted.... Your device is booting now..." after some minutes it goes to EMUI recovery instead of TWRP.
Is there something I can do it to solve this issue?
Thanks in advanced!
Click to expand...
Click to collapse
This is normal after you unlock the bootloader. Unless you re-lock it you won't get rid of that error AFAIK. Small annoyance to pay for full root.
khat17 said:
This is normal after you unlock the bootloader. Unless you re-lock it you won't get rid of that error AFAIK. Small annoyance to pay for full root.
Click to expand...
Click to collapse
Hi, so I can live with this message not a big deal in the mean time is just a normal information alert.
Thank you so much for the information!
sammyrano said:
Hi, so I can live with this message not a big deal in the mean time is just a normal information alert.
Thank you so much for the information!
Click to expand...
Click to collapse
I also got honor 8 FRD-L14 version rooted with Magisk and stock EMUI 5.0.1. You should try Dolby atmos audio mod from this thread https://forum.xda-developers.com/android/apps-games/soundmod-axon-7-dolby-atmos-t3412342 and also Google dose for Magisk to improve battery life.
Best wishes sir.
khat17 said:
No problem. Anytime.
From what's been happening to me, I think Huawei may be clamping down on allowing persons to unlock their bootloader and root the phones. I've not been able to get into the site at all - I've managed to root my wife's phone but mine.............nothing. Nothing works. I got the info directly from their site and it just won't work. I emailed them and they say that they don't assist individuals with bootloader unlock nor do they allow it - which seems to be new policy.
The instructions that are in the link I have works. As long as you got your bootloader unlocked you can install TWRP, SuperSU and root. If you go through the instructions in the link and need step-by-step assistance then just post back.
Click to expand...
Click to collapse
Any chance that step by step assistance is still on the table? I'm revisiting the notion of unlocking and rooting but your previous post and the threads linked to it have me quite a bit lost. Do I have to go all the way back to build B162 to get it to work properly? I know my way around ADB and have unlocked every phone I've had going back to the first HTC Evo but all the different versions of this phone has me all turned around. :/
A walkthrough with direct links to files used would be greatly appreciated if you have the time.
Thanks in advance for any help you can provide!
Not a problem. I'll see what I can do. Will need a little time to compile the info.
dsEVOlve said:
Any chance that step by step assistance is still on the table? I'm revisiting the notion of unlocking and rooting but your previous post and the threads linked to it have me quite a bit lost. Do I have to go all the way back to build B162 to get it to work properly? I know my way around ADB and have unlocked every phone I've had going back to the first HTC Evo but all the different versions of this phone has me all turned around. :/
A walkthrough with direct links to files used would be greatly appreciated if you have the time.
Thanks in advance for any help you can provide!
Click to expand...
Click to collapse
khat17 said:
Not a problem. I'll see what I can do. Will need a little time to compile the info.
Click to expand...
Click to collapse
Any progress?
dsEVOlve said:
Any progress?
Click to expand...
Click to collapse
Apologies. Vehicle issues that I'm sorting out have taken up my time.
So first thing we're gonna do is this. Go to this thread.
https://forum.xda-developers.com/ho...-to-nougat-t3510275/post70396400#post70396400
Download the files there. You have an L14 and this thread I've linked to has files for that phone.
Next you want an SD card. An 8GB card should work. You will also need a hash checker like the one in the link below.
http://getmd5checker.com
Once you have all of those post back and we can proceed.
I used this guide to install TWRP on my FRD-L14 without a hitch:
https://forum.xda-developers.com/honor-8/how-to/guide-unlock-bootloader-tested-root-t3443946
Is there a certain step you get caught up on? I just reverted back to stock after being on a custom ROM for a day so it is fresh in my mind.
This is the TWRP I used:
https://forum.xda-developers.com/honor-8/development/twrp-t3566563
@dsEVOlve - you can try the link that @Deemo13 posted. I'll still be here to go through the step by step process. If you're available tonight I will also give you remote assistance in getting it done if you'd like the help that way.
https://www.teamviewer.com/en/download/previous-versions/
Go there and download version 11 if you'd like the remote assistance in getting this done. If we can agree on a time then I'll ask you to PM me the ID and PW.
Let's go through and see if we can get you setup.
Deemo13 said:
I used this guide to install TWRP on my FRD-L14 without a hitch:
https://forum.xda-developers.com/honor-8/how-to/guide-unlock-bootloader-tested-root-t3443946
Is there a certain step you get caught up on? I just reverted back to stock after being on a custom ROM for a day so it is fresh in my mind.
This is the TWRP I used:
https://forum.xda-developers.com/honor-8/development/twrp-t3566563
Click to expand...
Click to collapse
Did you flash SuperSU or magisk? If SuperSU, did you flash it or simply install from Play Store?
---------- Post added at 04:39 AM ---------- Previous post was at 04:36 AM ----------
khat17 said:
@dsEVOlve - you can try the link that @Deemo13 posted. I'll still be here to go through the step by step process. If you're available tonight I will also give you remote assistance in getting it done if you'd like the help that way.
https://www.teamviewer.com/en/download/previous-versions/
Go there and download version 11 if you'd like the remote assistance in getting this done. If we can agree on a time then I'll ask you to PM me the ID and PW.
Let's go through and see if we can get you setup.
Click to expand...
Click to collapse
Thanks for the offer of assistance. I think I've got the process now and the files needed to root. I was just wary before because nothing I came across specifically said it was for the L14 variant.
Just trying to figure out if I want to go the SuperSU or Magisk route. Any suggestions?
And the first link you provided utilizes build 360. How do I go about getting the latest build to flash? Firmware finder?
dsEVOlve said:
Did you flash SuperSU or magisk? If SuperSU, did you flash it or simply install from Play Store?
---------- Post added at 04:39 AM ---------- Previous post was at 04:36 AM ----------
Thanks for the offer of assistance. I think I've got the process now and the files needed to root. I was just wary before because nothing I came across specifically said it was for the L14 variant.
Just trying to figure out if I want to go the SuperSU or Magisk route. Any suggestions?
And the first link you provided utilizes build 360. How do I go about getting the latest build to flash? Firmware finder?
Click to expand...
Click to collapse
I did not flash or root the phone, so unfortunately I can't give any advice on this front
I am reading conflicting things trying to figure this out. Can someone who is absolutely sure please let me know? I can't afford to waste another entire day making educated guesses.
It doesn't seem like the TWRP version numbers correspond to the Android builds, but if they do please correct me.
Thank you
You don't need to figure it out, there's only 2 threads about working TWRP, One for Android 9 & 10 and One for 11 and in the OP of each thread are specified what are working and what doesn't and how to install/boot it properly.
RokCruz said:
You don't need to figure it out, there's only 2 threads about working TWRP, One for Android 9 & 10 and One for 11 and in the OP of each thread are specified what are working and what doesn't and how to install/boot it properly.
Click to expand...
Click to collapse
Oh ****, thank you! I totally missed these searching. Believe it or not I really did look, quite a bit. Anyway, thanks again.
Edit: That 9&10 thread I've read, but I didn't know it was for "9 & 10" exactly. I just kinda assumed since it doesnt work with 11 which I had to figure out the hard way. That 11 thread though is super helpful.
didymus said:
Oh ****, thank you! I totally missed these searching. Believe it or not I really did look, quite a bit. Anyway, thanks again.
Edit: That 9&10 thread I've read, but I didn't know it was for "9 & 10" exactly. I just kinda assumed since it doesnt work with 11 which I had to figure out the hard way. That 11 thread though is super helpful.
Click to expand...
Click to collapse
It's specified in the name of the twrp
And another thing, this type of question should go in the section Questions and answers
RokCruz said:
It's specified in the name of the twrp
And another thing, this type of question should go in the section Questions and answers
Click to expand...
Click to collapse
Yeah, I wasn't sure about where to post it since it was directly about recovery. Sorry about that. I won't make the same mistake again.
Also, I'm just now figuring out what is what, but I don't see how any of those files designate they are for 11 in that screenshot you posted. I've seen all those files actually. I've also spent time on the TWRP website and read mostly everything. The only thing I could find was a post that said it (11 support) was coming, but I tried the newest one there and it bricked the phone. I also read in an article that the lad(s) who wrote those is working officially with TWRP, so I thought the TWRP website would be "the horse's mouth".
I know I installed it correctly too because in the past week I've installed TWRP so many times I could practically do it blindfolded now.
I don't mean to take a bunch of your time, but where in that screenshot does it designate "11"? I know `Pie` is an older Android, but I thought `Q` was too. Maybe I'm just wrong and it's 11. I was just getting confused because the OOS version numbers are right there in the boot image file name for Magisk, so when I saw those numbers on the TWRP files I just thought they were all for much older Android years ago.
Anyway, thank you, sorry for the n00b post, but I definitely am reading and searching and not just posting immediately when I encounter a problem. I've actually learned a ****load in the past week struggling with all of this though so I can't really complain. Eventually I will get up to speed and be able to write some things. I just hope yall don't ban me before then, lol.
didymus said:
Yeah, I wasn't sure about where to post it since it was directly about recovery. Sorry about that. I won't make the same mistake again.
Also, I'm just now figuring out what is what, but I don't see how any of those files designate they are for 11 in that screenshot you posted. I've seen all those files actually. I've also spent time on the TWRP website and read mostly everything. The only thing I could find was a post that said it (11 support) was coming, but I tried the newest one there and it bricked the phone. I also read in an article that the lad(s) who wrote those is working officially with TWRP, so I thought the TWRP website would be "the horse's mouth".
I don't mean to take a bunch of your time, but where in that screenshot does it designate "11"? I know `Pie` is an older Android, but I thought `Q` was too. Maybe I'm just wrong and it's 11. I was just getting confused because the OOS version numbers are right there in the boot image file name for Magisk, so when I saw those numbers on the TWRP files I just thought they were all for much older Android years ago.
Anyway, thank you, sorry for the n00b post, but I definitely am reading and searching and not just posting immediately when I encounter a problem. I've actually learned a ****load in the past week struggling with all of this though so I can't really complain. Eventually I will get up to speed and be able to write some things.
Click to expand...
Click to collapse
That screenshot was for this
didymus said:
Edit: That 9&10 thread I've read, but I didn't know it was for "9 & 10" exactly.
Click to expand...
Click to collapse
If you're in android 11 forget the thread about android 9 & 10
RokCruz said:
That screenshot was for this
If you're in android 11 forget the thread about android 9 & 10
Click to expand...
Click to collapse
Yeah, so, this one for 11 I've tried before. Once I install it how the thread says then I can only boot into TWRP. I'm just unsure what to do now because all the threads just say "flash rom, flash magisk". I didn't even know you could flash Magisk via TWRP.
I have the OTA of the new update downloaded. I have the boot.img extracted. I just have no idea how to fix this. I've done this before and I thought I bricked it and that's why I thought this wasn't for 11. :/
Edit: I'm guessing that I `adb push` the OTA to the device and see if I can flash that in TWRP?? Then once I am in the OS use Magisk to patch the boot? I'm unsure because places use the term "Magisk Manager" like its different from Magisk and I've never seen an app called exactly "Magisk Manager". I'm just assuming that was like... the old name of the app, but I don't know that could just be me filling in the blanks incorrectly.
Edit:Edit: I'm attempting to sideload the OTA. I think I've read of people doing this. *crosses fingers*
didymus said:
Yeah, so, this one for 11 I've tried before. Once I install it how the thread says then I can only boot into TWRP. I'm just unsure what to do now because all the threads just say "flash rom, flash magisk". I didn't even know you could flash Magisk via TWRP.
I have the OTA of the new update downloaded. I have the boot.img extracted. I just have no idea how to fix this. I've done this before and I thought I bricked it and that's why I thought this wasn't for 11. :/
Edit: I'm guessing that I `adb push` the OTA to the device and see if I can flash that in TWRP?? Then once I am in the OS use Magisk to patch the boot? I'm unsure because places use the term "Magisk Manager" like its different from Magisk and I've never seen an app called exactly "Magisk Manager". I'm just assuming that was like... the old name of the app, but I don't know that could just be me filling in the blanks incorrectly.
Edit:Edit: I'm attempting to sideload the OTA. I think I've read of people doing this. *crosses fingers*
Click to expand...
Click to collapse
Wait, what? Im not sure what are you trying to do.
I guess you're new in all of this right?
My work here was the twrp thing.
RokCruz said:
Wait, what? Im not sure what are you trying to do.
I guess you're new in all of this right?
My work here was the twrp thing.
Click to expand...
Click to collapse
Im trying to install TWRP. I do it exactly how the thread says and then system never boots into OOS again and I just have fastboot and TWRP. Basically bricked. Then when I try to reboot to recovery which should be TWRP (right?) it just boots me into the regular "recovery".
Thats why I think this is broken and I resigned to just not updating into 11.
I've never had this much trouble doing this. Ever. Not even close.
Edit: Yeah, so I patched the 11 boot.img and now I have root again, but no TWRP. I don't know how to keep both in 11. When I was 9.5.3 I used the Magisk A/B retention script and kept it, but once it became 11 it bricked the phone and the TWRP logo just flashed. I had to reflash the OTA to boot again. Thats another reason why I thought it didn't work for OOS11.
Starting to think I have a learning disability, lmao. Wish I was joking.
I just try.
When I flashed official TWRP and used it to flash any ROM(including OOS), it will lose or replace it by ROM's recovery...
caca12357 said:
I just try.
When I flashed official TWRP and used it to flash any ROM(including OOS), it will lose or replace it by ROM's recovery...
Click to expand...
Click to collapse
Yeah, exactly what is happening with me. The closest I ever had it working was with using the A/B Retention script within Magisk Modules, but the second I hit OOS11 it **** the bed. I think "official TWRP" is different than what he linked up there for 11. I mean, I know they are, as it says "unofficial", but that's kind of why I'm confused because the images on TWRP.me use the similar numbering nomenclature and imply there are newer version for my device, so why would a newer version not work, but an older version work?
And if this particular TWRP does actually support 11 then why hasn't TWRP Official incorporated it into their releases? It's just little things like that which led me to believe it's not working. Also, I read a bunch of articles saying it wasn't working, but they could have been old. However, one of them was on Reddit and a few months old, but maybe they were wrong.
I feel like I went on a wild goose chase today, but I really hope didn't.
@RokCruz Just out of curiousity, do you actually have a OnePlus 7 Pro right now with OOS11 and working TWRP/root? I'm not saying you're just making this up or anything, but maybe something has changed since the last time you tried? If you currently have an OOS 11.0.11 device with TWRP/root atleast I'll know it's possible.
@caca12357 I'm going to try to do a local OTA upgrade then before I reboot run the A/B retention script and then Magisks option for OTA and see if that does anything. If TWRP works for 11 something like that should make it work, but who knows. Have you messed with A/B Retention at all?
If you want to PM me we can figure it out together.
Thread moved to proper section
didymus said:
Yeah, exactly what is happening with me. The closest I ever had it working was with using the A/B Retention script within Magisk Modules, but the second I hit OOS11 it **** the bed. I think "official TWRP" is different than what he linked up there for 11. I mean, I know they are, as it says "unofficial", but that's kind of why I'm confused because the images on TWRP.me use the similar numbering nomenclature and imply there are newer version for my device, so why would a newer version not work, but an older version work?
And if this particular TWRP does actually support 11 then why hasn't TWRP Official incorporated it into their releases? It's just little things like that which led me to believe it's not working. Also, I read a bunch of articles saying it wasn't working, but they could have been old. However, one of them was on Reddit and a few months old, but maybe they were wrong.
I feel like I went on a wild goose chase today, but I really hope didn't.
@RokCruz Just out of curiousity, do you actually have a OnePlus 7 Pro right now with OOS11 and working TWRP/root? I'm not saying you're just making this up or anything, but maybe something has changed since the last time you tried? If you currently have an OOS 11.0.11 device with TWRP/root atleast I'll know it's possible.
Click to expand...
Click to collapse
Yes, and do you know how I flash TWRP to my OP7P? First, I flashed Pixel Experience recovery by fastboot, and I used Pixel Experience recovery to sideload the official TWRP. (In other words, I never can temporarily or permanently flash TWRP directly). If I did not want to convert my /data to the f2fs file system I will not do this meaningless work...
I tried putting the beta of OOS13 on my Oneplus and now i get that error message and ive been trying for so long.
the serial number is fb7b98a9
Flash by edl if you can't do it then pm I'll fix it by tv
Could you elaborate a little further? Are you just not able to flash OO13 beta or has the attempt of doing so corrupted your device completely?
If the latter, You will most likely need to flash an emergency MSMToolkit. It is an Indian OP9Pro variant but will bring your device back from the dead. Once that is done, you will just run a proper MSMToolkit and be right as rain.
EtherealRemnant wrote up an amazing guide on how to carry this out. SO amazing that its the only guide stickied on the 9 forums, currently.
- Here is a mega hosted copy of the Indian OP9Pro MSMToolkit,
I can personally vouch for the guide, as my 9 went into a bricked state with vague errors about corrupted system. I tried every toolkit, recovery and ROM and nothing worked. Thats when EthRem came to my rescue. Hopefully his work can come to yours as well.
and if that isn't what you meant and are just dying to get into OOS13, id just stick with one of the many A13 ROMs currently available. OOS13 is beautiful but, i just cant honestly suggest using Oneplus software anymore.
Good luck
applyscience said:
Could you elaborate a little further? Are you just not able to flash OO13 beta or has the attempt of doing so corrupted your device completely?
If the latter, You will most likely need to flash an emergency MSMToolkit. It is an Indian OP9Pro variant but will bring your device back from the dead. Once that is done, you will just run a proper MSMToolkit and be right as rain.
EtherealRemnant wrote up an amazing guide on how to carry this out. SO amazing that its the only guide stickied on the 9 forums, currently.
- Here is a mega hosted copy of the Indian OP9Pro MSMToolkit,
I can personally vouch for the guide, as my 9 went into a bricked state with vague errors about corrupted system. I tried every toolkit, recovery and ROM and nothing worked. Thats when EthRem came to my rescue. Hopefully his work can come to yours as well.
and if that isn't what you meant and are just dying to get into OOS13, id just stick with one of the many A13 ROMs currently available. OOS13 is beautiful but, i just cant honestly suggest using Oneplus software anymore.
Click to expand...
Click to collapse
applyscience said:
Could you elaborate a little further? Are you just not able to flash OO13 beta or has the attempt of doing so corrupted your device completely?
If the latter, You will most likely need to flash an emergency MSMToolkit. It is an Indian OP9Pro variant but will bring your device back from the dead. Once that is done, you will just run a proper MSMToolkit and be right as rain.
EtherealRemnant wrote up an amazing guide on how to carry this out. SO amazing that its the only guide stickied on the 9 forums, currently.
- Here is a mega hosted copy of the Indian OP9Pro MSMToolkit,
I can personally vouch for the guide, as my 9 went into a bricked state with vague errors about corrupted system. I tried every toolkit, recovery and ROM and nothing worked. Thats when EthRem came to my rescue. Hopefully his work can come to yours as well.
and if that isn't what you meant and are just dying to get into OOS13, id just stick with one of the many A13 ROMs currently available. OOS13 is beautiful but, i just cant honestly suggest using Oneplus software anymore.
Good luck
Click to expand...
Click to collapse
The tool that you linked doesnt have o2 as he is saying in the guide.
Also yes, i tried flashing OOS13 and it just corrupted my device i've been endlessly working to fix it all day
SubColdSnow said:
The tool that you linked doesnt have o2 as he is saying in the guide.
Also yes, i tried flashing OOS13 and it just corrupted my device i've been endlessly working to fix it all day
Click to expand...
Click to collapse
1st of all flash with op9pro india msm with uncheck sah and check lite firehorse if u have hard bricked ur device then the next steps as mention above
rizzmughal said:
1st of all flash with op9pro india msm with uncheck sah and check lite firehorse if u have hard bricked ur device then the next steps as mention above
Click to expand...
Click to collapse
i tried and just get device does not match image
SubColdSnow said:
i tried and just get device does not match image
Click to expand...
Click to collapse
try it again. if anything, you will be attempting on the other slot. Many haves had issues and it just started working.
it could have been slot related, or possibly some minor detail that is finicky. (ex. you usually want to start the msmtoolkit and let it stay in the "waiting for device" phase and plug in your phone (which should be in EDL mode . youll know by the peeps of it habitually connecting/disconnecting on your PC)
assure you have india selected, assure you have the proper conditionals on/off per the guide's explication.
Assure you have the qualcom drivers installed, and they reflect the naming convention.
follow along the guide again and Just keep attempting it and don't get discouraged. Part of the reason people offer guides here is that they themselves failed many times until they got they figured it out and are trying to save people from it.
youll get it, dont worry.
I had this problem because I flashed a custom kernel on a custom rom today
SubColdSnow said:
i tried and just get device does not match image
Click to expand...
Click to collapse
try the modded msm tool. it worked for me.