Related
I have a GS2 I9100XWLSW, suffering the EMMC brick bug. Still with stock kernel and recovery. Rooted with Framaroot.
First of all I'd want to flash a recovery, and a safe kernel - to avoid any possibile brick bug.
Later on I plan to flash Cyanogen or Omnirom, once a Lollipop stable versions is out.
Looking around I've found many ways to do this, but I'm unsure which one is safes (and possibly easier too):
- Installing Philz through Odin? Surely the kernel is safe, but CWM is and old version, not supporting KitKat ROM, right? Would I then need to flash an updated CWM + Kernel once I update to Lollipop? How?
- Using Clockwork mod install app to install a CWM? Can I install last CWM and still run on JB? But what about the unsafe, still not patched, stock kernel? Would still need to later update with a new Kernel for Lollipop? How?
- Others?
In particular, there's something concerning my GS2 that I didn't fully understand.. seems like differently from other phones, CWM needs to be installed together with a specific Kernel to work. Is this something true only for Philz's version, or is it so for CWM itself?
Malhavoc Blackdrake said:
I have a GS2 I9100XWLSW, suffering the EMMC brick bug. Still with stock kernel and recovery. Rooted with Framaroot.
First of all I'd want to flash a recovery, and a safe kernel - to avoid any possibile brick bug.
Later on I plan to flash Cyanogen or Omnirom, once a Lollipop stable versions is out.
Looking around I've found many ways to do this, but I'm unsure which one is safes (and possibly easier too):
- Installing Philz through Odin? Surely the kernel is safe, but CWM is and old version, not supporting KitKat ROM, right? Would I then need to flash an updated CWM + Kernel once I update to Lollipop? How?
- Using Clockwork mod install app to install a CWM? Can I install last CWM and still run on JB? But what about the unsafe, still not patched, stock kernel? Would still need to later update with a new Kernel for Lollipop? How?
- Others?
In particular, there's something concerning my GS2 that I didn't fully understand.. seems like differently from other phones, CWM needs to be installed together with a specific Kernel to work. Is this something true only for Philz's version, or is it so for CWM itself?
Click to expand...
Click to collapse
Sincw you are on stock jelly bean rom, use apolo kernel 4.14 as it uses TWRP which supports most zips and doesnt have to be updated that often. Lollipop roms only require cwm versions 6.0.4.8+ or TWRP 2.7.1.0+. Usually i don't recommend using cwm manager to install cwm as the app installs an old version of cwm anyway and requires people to pay if they want the latest version.
If your cwm is out of date, you will need to update the kernel (not just the recovery).
Installing a newer cwm will not modify the kernel to make it unsafe.
gsstudios said:
Sincw you are on stock jelly bean rom, use apolo kernel 4.14 as it uses TWRP which supports most zips and doesnt have to be updated that often. Lollipop roms only require cwm versions 6.0.4.8+ or TWRP 2.7.1.0+. Usually i don't recommend using cwm manager to install cwm as the app installs an old version of cwm anyway and requires people to pay if they want the latest version.
If your cwm is out of date, you will need to update the kernel (not just the recovery).
Installing a newer cwm will not modify the kernel to make it unsafe.
Click to expand...
Click to collapse
Thank you! Ok, let's see if I got everything right:
- First I need to flash Apolo, but I can't find the 4.14 version. Do I still use Odin? Instructions are unclear. The official thread seems this: http://forum.xda-developers.com/galaxy-s2/development-derivatives/kernel-t2291756/post41742325
- By flashing Apolo 4.14 I should get a new kernel (EMMC safe) and TWRP (which version?)
- With the above, I can still run my stock JB 4.1.2, right?
Then, once I want to flash a Lollipo ROM:
- Do I need to update TWRP? Does this break my ability to run my current JB 4.1.2 ?
- Flashing the Lollipop ROM will overwrite the Apolo Kernel 4.14 with a suitable Lollipop kernel, right? Or am I forced to also flash a Lollipop kernel manually (either Apolo or anoter)?
Thank you in advance!
Malhavoc Blackdrake said:
Thank you! Ok, let's see if I got everything right:
- First I need to flash Apolo, but I can't find the 4.14 version. Do I still use Odin? Instructions are unclear. The official thread seems this: http://forum.xda-developers.com/galaxy-s2/development-derivatives/kernel-t2291756/post41742325
- By flashing Apolo 4.14 I should get a new kernel (EMMC safe) and TWRP (which version?)
- With the above, I can still run my stock JB 4.1.2, right?
Then, once I want to flash a Lollipo ROM:
- Do I need to update TWRP? Does this break my ability to run my current JB 4.1.2 ?
- Flashing the Lollipop ROM will overwrite the Apolo Kernel 4.14 with a suitable Lollipop kernel, right? Or am I forced to also flash a Lollipop kernel manually (either Apolo or anoter)?
Thank you in advance!
Click to expand...
Click to collapse
What I said before about apolo requires the usage of CWM. If you can, flash philz kernel (through odin)first then you can flash apolo 4.14 (TWRP) using cwm. All kernels for the s2 are safe from the emmc brickbug (just make sure you read the first post of the kernel threads). TWRP version should be 2.7.0.0, but it should work fine with all zip files.
When you flash a lollipop rom, you most likely will not have to update TWRP (unlikely as the source code for lollipop isn't going to change). You can still flash back stock JB from a backup with no problems. Yes, flashing lollipop will replace apolo with a compatible kernel.
gsstudios said:
Sincw you are on stock jelly bean rom, use apolo kernel 4.14 as it uses TWRP which supports most zips and doesnt have to be updated that often. Lollipop roms only require cwm versions 6.0.4.8+ or TWRP 2.7.1.0+. Usually i don't recommend using cwm manager to install cwm as the app installs an old version of cwm anyway and requires people to pay if they want the latest version.
If your cwm is out of date, you will need to update the kernel (not just the recovery).
Installing a newer cwm will not modify the kernel to make it unsafe.
Click to expand...
Click to collapse
gsstudios said:
What I said before about apolo requires the usage of CWM. If you can, flash philz kernel (through odin)first then you can flash apolo 4.14 (TWRP) using cwm. All kernels for the s2 are safe from the emmc brickbug (just make sure you read the first post of the kernel threads). TWRP version should be 2.7.0.0, but it should work fine with all zip files.
When you flash a lollipop rom, you most likely will not have to update TWRP (unlikely as the source code for lollipop isn't going to change). You can still flash back stock JB from a backup with no problems. Yes, flashing lollipop will replace apolo with a compatible kernel.
Click to expand...
Click to collapse
All right, so, to recap, is this right?
- Flash Philz (of course the version for my kernel and JB) with Odin. This will also install CWM (an old version, not supporting KitKat and Lollipop)
- With the above, I can do a nandroid backup, which also includes Philz's kernel. Does it also include the recovery itself?
- Flash Apolo 4.14 through CWM. This will change both the Philz Kernel and the CWM recovery with Apolo Kernel and TWRP. Jelly Bean will still run, right?
- From this TWRP, I can flash and run both the current JB and future Lollipop without changing recovery, right?
Malhavoc Blackdrake said:
All right, so, to recap, is this right?
- Flash Philz (of course the version for my kernel and JB) with Odin. This will also install CWM (an old version, not supporting KitKat and Lollipop)
- With the above, I can do a nandroid backup, which also includes Philz's kernel. Does it also include the recovery itself?
- Flash Apolo 4.14 through CWM. This will change both the Philz Kernel and the CWM recovery with Apolo Kernel and TWRP. Jelly Bean will still run, right?
- From this TWRP, I can flash and run both the current JB and future Lollipop without changing recovery, right?
Click to expand...
Click to collapse
You are 100% correct with all of your questions. Happy flashing!
gsstudios said:
You are 100% correct with all of your questions. Happy flashing!
Click to expand...
Click to collapse
Thank you very much! Also found the Apolo version you were talking about. BTW, the reason I have to pass through Philz to flash Apolo is just because that Apolo version is available in .zip format only, right? Because if there was a .tar, I could just flash the stock rom with Apolo through Odin, without going through Philz first, right?
Malhavoc Blackdrake said:
Thank you very much! Also found the Apolo version you were talking about. BTW, the reason I have to pass through Philz to flash Apolo is just because that Apolo version is available in .zip format only, right? Because if there was a .tar, I could just flash the stock rom with Apolo through Odin, without going through Philz first, right?
Click to expand...
Click to collapse
Wow, you sound like you have flashed custom roms before. You are correct again.
gsstudios said:
Wow, you sound like you have flashed custom roms before. You are correct again.
Click to expand...
Click to collapse
Never before, but being a software developer I get these things not too hardly. Also, I'm really reading a LOT of guides everywhere to avoid doing a mess! :laugh:
Thank you again for your help.
gsstudios said:
Wow, you sound like you have flashed custom roms before. You are correct again.
Click to expand...
Click to collapse
I finally did all of the above, and I can confirm that everything worked perfectly. I just skipped during the Apolo flashing the clean script suggested, and just did Clean Cache + Dalvik Cache.
Now I have TWRP and Apolo v4.15.
Noticed however that TWRP is v2.6.3 , while you said that I would probably need 2.7.1.0+ to later flash Omnirom or CM12
Is it okay anyway, or do I need to flash a new one? Can I risk breaking something if I try to flash a new TWRP? I mean: may I end up flashing a TWRP not supported with my kernel / JB and get bootloops or something bad?
Malhavoc Blackdrake said:
I finally did all of the above, and I can confirm that everything worked perfectly. I just skipped during the Apolo flashing the clean script suggested, and just did Clean Cache + Dalvik Cache.
Now I have TWRP and Apolo v4.15.
Noticed however that TWRP is v2.6.3 , while you said that I would probably need 2.7.1.0+ to later flash Omnirom or CM12
Is it okay anyway, or do I need to flash a new one? Can I risk breaking something if I try to flash a new TWRP? I mean: may I end up flashing a TWRP not supported with my kernel / JB and get bootloops or something bad?
Click to expand...
Click to collapse
You will need to flash a newer recovery. If you use philz recovery, you can install all lollipop roms and kikat roms without a problem
Link to download latest philz recovery: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/i9100/philz_touch_6.48.4-i9100.zip
Flash it with TWRP. Cheers.
gsstudios said:
You will need to flash a newer recovery. If you use philz recovery, you can install all lollipop roms and kikat roms without a problem
Link to download latest philz recovery: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/i9100/philz_touch_6.48.4-i9100.zip
Flash it with TWRP. Cheers.
Click to expand...
Click to collapse
That link is indeed philz's latest version for i9100 (also from size it seems with just the recover, and no kernel, right?), but does it still run on JB with Apolo kernel? On Philz's thread I read something about latest versions supporting only kitkat / lollipop. Does it mean I have to flash this Philz's update just before flashing Lollipop, or I can flash it already and running my JB + Apolo, without problems?
Also, I heard that Philz is no longer updating his recover (is it?), so if possible I would prefer to stick with TWRP.. if there is a TWRP version which suits my needs with my device, of course!
Hello everyone,
I updated to the latest version 6.0.1. 572
I also unlocked the Bootloader and rooted with King root (Temporary root)
But what I can't boot to the stock recovery, and whenever I try to, it automatically boots to system
And I tried to install twrp, I ended up getting it soft bricked and I had to reinstall lastest firmware
So, is there any way I can install a custom recovery?
Thanks
Do not use standalone recoveries at the moment. Use ROMs that has recovery else you'l end up in bootloop.
For now, rcovery fix is an issue with 6.0.1. So i suggest you simply stick with a ROM like Existenz MM V1 or any other, by downgrading and installing recovery with root AND then flashing 6.0.1(with recovery & root). That way you can have recovery.
I too am waiting for a recovery fix so just managing without recovery for now as non of the fixes are working for me.
Good Luck buddy!
XDA
"Xcites: Develop: Achieve"
---------- Post added at 11:29 PM ---------- Previous post was at 11:26 PM ----------
Or...
Use a custom kernel.
You will have recovery and much more.
XDA
"Xcites: Develop: Achieve"
nagaGuy said:
Do not use standalone recoveries at the moment. Use ROMs that has recovery else you'l end up in bootloop.
For now, rcovery fix is an issue with 6.0.1. So i suggest you simply stick with a ROM like Existenz MM V1 or any other, by downgrading and installing recovery with root AND then flashing 6.0.1(with recovery & root). That way you can have recovery.
I too am waiting for a recovery fix so just managing without recovery for now as non of the fixes are working for me.
Good Luck buddy!
XDA
"Xcites: Develop: Achieve"
---------- Post added at 11:29 PM ---------- Previous post was at 11:26 PM ----------
Or...
Use a custom kernel.
You will have recovery and much more.
XDA
"Xcites: Develop: Achieve"
Click to expand...
Click to collapse
Well, thanks for the help, downgraded to 5.1.1 (or should I downgrade to something more older?)
But I need help to choose a custom kernel (I know how to flash kernels using fastboot ) can you suggest me a kernel that has a custom recovery
Sent from my D6503 using Tapatalk
5.1.1 is fine as you can root it. Just install Recovery( nuts dual recovery/ choose your version carefully & Follow instructions). if you'r going to upgrade to 6.0.1, i would suggest this kernel -http://forum.xda-developers.com/showthread.php?t=2965480.
Just follow the instructions carefully and you'l be fine.
BTW, if you only want recovery, you can easily install in 5.1.1 after geting it rooted using kingroot.
XDA
"Xcites: Develop: Achieve"
nagaGuy said:
5.1.1 is fine as you can root it. Just install Recovery( nuts dual recovery/ choose your version carefully & Follow instructions).
Click to expand...
Click to collapse
Done, thanks!
After converting from kingroot to SuperSU (permanent root) and flashing dual recovery, then flashing a prerooted 6.0.1 ROM, now I have everything I need :good: :victory:
Hi everyone. I was read a lot off discussions about i9100 with CM12.1 but I still don't know how to do it without some problems.
My phone actually running CM13.1 latest nightly build with Team Win TWRP recovery v 2.8.XXX and maybe DorimanX kernel? I don't know how to find Kernel name and version... I would like to ask you how to go to Cm12.1 build with pico or nano GAPPS (And what build I should download). I need the most stable build for daily use. Next how to replace CM recovery with TWRP 3.0.2. . I am totally confused. I'll be glad for any help.
Oh. I have that problem too. CM 13.1 not stable!
Jaccob25 said:
Hi everyone. I was read a lot off discussions about i9100 with CM12.1 but I still don't know how to do it without some problems.
My phone actually running CM13.1 latest nightly build with Team Win TWRP recovery v 2.8.XXX and maybe DorimanX kernel? I don't know how to find Kernel name and version... I would like to ask you how to go to Cm12.1 build with pico or nano GAPPS (And what build I should download). I need the most stable build for daily use. Next how to replace CM recovery with TWRP 3.0.2. . I am totally confused. I'll be glad for any help.
Click to expand...
Click to collapse
Firstly look under settings -> about device and it will tell you the kernel version. If it says 3.0.101-CM------, you have the stock CM13 kernel. You said you have TWRP 2.8.x.x and not CM recovery?? This means you already have the isorec recovery enabled. All you need to do is flash the 3.0.2-1 .img from this recovery and you will have the newer one installed. And just do normal backup/wipes and install CM12.1 as you would any other rom. Just remember to use 5.1 gapps(arm;5.1;pico/nano)
Here is the last official CM12.1 I uploaded
Here is a more up to date unofficial CM12.1
noppy22 said:
Firstly look under settings -> about device and it will tell you the kernel version...
Click to expand...
Click to collapse
Yes I have stock cm13 kernel and TWRP flashed. Can I flash new TWRP via Odin?
Thank you very much!
Jaccob25 said:
Yes I have stock cm13 kernel and TWRP flashed. Can I flash new TWRP via Odin?
Thank you very much!
Click to expand...
Click to collapse
I don't think you can flash a .img file with odin. Honestly if you want to downgrade to 5.1.1 it would be easier to do it in one go.
Flash CM12.1, gapps, then TWRP 3.0.2-1.img all from TWRP 2.8
noppy22 said:
I don't think you can flash a .img file with odin. Honestly if you want to downgrade to 5.1.1 it would be easier to do it in one go.
Flash CM12.1, gapps, then TWRP 3.0.2-1.img all from TWRP 2.8
Click to expand...
Click to collapse
Ohh I thought that TWRP can't flash img file.
Thanks for advice. I try it today.
So I try that and almost everything works fine. Only GPS fixing seems like a little bit problematic. But I don't know my testing was short. I will see.
May I ask a supplementary question - I am in a similar position, I have an i9100 which I upgraded from stock 4.1.2 Jelly Bean to CM13 following (most of) djibe's guide here
So I now have CM13 ROM with kernel version 3.0.101, re-partitioned with Lanchons repit, and with recovery TWRP 3.1.0 installed and functioning.
I want to revert from CM13 to CM12.1. From above, I believe that I can simply backup, wipe, then flash the CM12.1 ROM (I'll be using the last nightly, cm-12.1-20160203-NIGHTLY-i9100.zip) - is that correct?
My question/confusion is, do I also need to flash an isorec-compatible kernel (ie kernel-Lanchon-TRIM-IsoRec-20160111-cm-12.1-i9100.zip)? The isorec thread (here) says that the "Official CyanogenMod 12.1 and 13 kernels are now IsoRec-compatible", so it seems to me unnecessary, but many threads/guides on XDA say to flash one of Lanchon's kernels.
Please could someone advise, and my apologies for what is probably an ignorant question.
teraghik said:
May I ask a supplementary question - I am in a similar position, I have an i9100 which I upgraded from stock 4.1.2 Jelly Bean to CM13 following (most of) djibe's guide here
So I now have CM13 ROM with kernel version 3.0.101, re-partitioned with Lanchons repit, and with recovery TWRP 3.1.0 installed and functioning.
I want to revert from CM13 to CM12.1. From above, I believe that I can simply backup, wipe, then flash the CM12.1 ROM (I'll be using the last nightly, cm-12.1-20160203-NIGHTLY-i9100.zip) - is that correct?
My question/confusion is, do I also need to flash an isorec-compatible kernel (ie kernel-Lanchon-TRIM-IsoRec-20160111-cm-12.1-i9100.zip)? The isorec thread (here) says that the "Official CyanogenMod 12.1 and 13 kernels are now IsoRec-compatible", so it seems to me unnecessary, but many threads/guides on XDA say to flash one of Lanchon's kernels.
Please could someone advise, and my apologies for what is probably an ignorant question.
Click to expand...
Click to collapse
You are correct. Isorec support was implemented before that last nightly iirc. No need to flash any kernels.
Note: Only use the official TWRP 3.1 from the TWRP website or the.gangster's one which is basically the same. They are compatible with the earlier android versions.
Hi Noppy,
Thanks very much for taking the time to reply and help - I am using "the gangsters" TWRP 3.1 from djibe's thread, appreciate the heads up. I can confirm that I flashed CM12.1, and it works fine!
Why don't you follow my tutorial to get the perfect smooth Android 7.1 for SGS2 ?
Here it is : https://forum.xda-developers.com/galaxy-s2/help/guide-tutorial-samsung-galaxy-s2-i9100-t3538601
Hi ll,
I am on Exodus which is on the old bootloader currently.Could anybody guide me as to which twrp to use for
1. Flashing the new 3.1.4 oos3 on my onyx?.I guess i currently have 3.0.2 or something
2. After flashing 3.1.4 which twrp to install and which super su to use for rooting?
Regards,
Sandeep
sand87ch said:
Hi ll,
I am on Exodus which is on the old bootloader currently.Could anybody guide me as to which twrp to use for
1. Flashing the new 3.1.4 oos3 on my onyx?.I guess i currently have 3.0.2 or something
2. After flashing 3.1.4 which twrp to install and which super su to use for rooting?
Regards,
Sandeep
Click to expand...
Click to collapse
1.
Ok, use stock recovery for OOS 2.2.x to flash OOS 3.1.4 found here: http://oxygenos.oneplus.net.s3.amazonaws.com/OPX_recovery.img
2.
Then after you have flashed OOS 3.1.4 you flash this twrp recovery by blu_spark for the new bootloader found here: http://forum.xda-developers.com/devdb/project/dl/?id=20236
3.
Then in the new twrp by blu_spark you flash a modified SuperSU provided by me:
Link in next post below.
Ok, here's the link
ferk said:
1.
Ok, use stock recovery for OOS 2.2.x to flash OOS 3.1.4 found here: http://oxygenos.oneplus.net.s3.amazonaws.com/OPX_recovery.img
2.
Then after you have flashed OOS 3.1.4 you flash this twrp recovery by blu_spark for the new bootloader found here: http://forum.xda-developers.com/devdb/project/dl/?id=20236
3.
Then in the new twrp by blu_spark you flash a modified SuperSU provided by me:
Link in next post below.
Click to expand...
Click to collapse
i am already on 3.0.2 TWRP official version.Can i flash 3.1.4 from there.I plan to install the deodexed 3.1.4.So is it possible that i can flash it from my existing twrp
sand87ch said:
i am already on 3.0.2 TWRP official version.Can i flash 3.1.4 from there.I plan to install the deodexed 3.1.4.So is it possible that i can flash it from my existing twrp
Click to expand...
Click to collapse
Shouldn't be an issue but just do a backup first.
sand87ch said:
i am already on 3.0.2 TWRP official version.Can i flash 3.1.4 from there.I plan to install the deodexed 3.1.4.So is it possible that i can flash it from my existing twrp
Click to expand...
Click to collapse
Did you read the answer given.
No, the safer way is to use the OOS 2 recovery.
Or use the guide on the topic of the rom you want to install :
http://forum.xda-developers.com/oneplus-x/development/rom-modified-oos-t3491602
sand87ch said:
i am already on 3.0.2 TWRP official version.Can i flash 3.1.4 from there.I plan to install the deodexed 3.1.4.So is it possible that i can flash it from my existing twrp
Click to expand...
Click to collapse
ok go here and use the guide to update your BL,and while you are flashing the OPXBLupdater.zip flash MOoSv3.zip after it.Then flash the recovery as stated in guide.
This way you'll be upgraded to new BL along with the MOoS.:good:
Note: remember to wipe your data and system partition before flashing the MOoS or else it'll bootloop.
Also please don't create unnecessary threads,if you could just have browsed the general section or the MOoS thread you should have been fine.
twrp can't flash 3.1.4
ferk said:
1.
Ok, use stock recovery for OOS 2.2.x to flash OOS 3.1.4 found here: http://oxygenos.oneplus.net.s3.amazonaws.com/OPX_recovery.img
2.
Then after you have flashed OOS 3.1.4 you flash this twrp recovery by blu_spark for the new bootloader found here: http://forum.xda-developers.com/devdb/project/dl/?id=20236
3.
Then in the new twrp by blu_spark you flash a modified SuperSU provided by me:
Link in next post below.
Click to expand...
Click to collapse
twrp can't flash 3.1.4
variravitejareddy said:
twrp can't flash 3.1.4
Click to expand...
Click to collapse
Yep. I did it.
There is official twrp for new bootloader
Kéno40 said:
Did you read the answer given.
No, the safer way is to use the OOS 2 recovery.
Or use the guide on the topic of the rom you want to install :
http://forum.xda-developers.com/oneplus-x/development/rom-modified-oos-t3491602
Click to expand...
Click to collapse
ferk said:
1.
Ok, use stock recovery for OOS 2.2.x to flash OOS 3.1.4 found here: http://oxygenos.oneplus.net.s3.amazonaws.com/OPX_recovery.img
2.
Then after you have flashed OOS 3.1.4 you flash this twrp recovery by blu_spark for the new bootloader found here: http://forum.xda-developers.com/devdb/project/dl/?id=20236
3.
Then in the new twrp by blu_spark you flash a modified SuperSU provided by me:
Link in next post below.
Click to expand...
Click to collapse
Hi, I followed this Guide to update bootloader and flash blu_spark twrp and Tesla N is installed on my OPX.
If I'm willing to flash 3.1.4 is it safe to flash oos 2.x.x recovery directly when I'm still on rooted custom rom??
Thanks in advance..
Official version here :
https://dl.twrp.me/onyx/twrp-3.0.2-1-onyx.img.html
Note I didn't tested it...
---------- Post added at 10:58 AM ---------- Previous post was at 10:56 AM ----------
rez4dh said:
Hi, I followed this Guide to update bootloader and flash blu_spark twrp and Tesla N is installed on my OPX.
If I'm willing to flash 3.1.4 is it safe to flash oos 2.x.x recovery directly when I'm still on rooted custom rom??
Thanks in advance..
Click to expand...
Click to collapse
With the new bootloader and TWRP for it, you should be able to wipe all & flash full 3.1.4 rom zip.
But, I've seen people with relojed BL without reason .Just check it before proceeding.
Hi all,
I'm a bit of a Noob when it comes to this phone and rooting it, and i've been following a Rooting guide by theunlockr. My phone has stock 3.1.4 on it. I've installed adb on my PC and when flashing recovery.img (fastboot boot recovery.img), I get an error dtb not found. It appears that I need the modified TWRP.
So from fastboot, should I just be doing steps 2 and 3 in post #2 above ?
Sorry but I have no idea as to what bootloader I have. If necessary, how can I check this ?
championc said:
Hi all,
I'm a bit of a Noob when it comes to this phone and rooting it, and i've been following a Rooting guide by theunlockr. My phone has stock 3.1.4 on it. I've installed adb on my PC and when flashing recovery.img (fastboot boot recovery.img), I get an error dtb not found. It appears that I need the modified TWRP.
So from fastboot, should I just be doing steps 2 and 3 in post #2 above ?
Sorry but I have no idea as to what bootloader I have. If necessary, how can I check this ?
Click to expand...
Click to collapse
Bump
Sent from my LG-D855 using Tapatalk
You need to have an unlocked bootloader to use fastboot.
To verify, fastboot command is (you need to have your phone on fastboot mode and usb connected to the computer)
"fastboot devices"
It should retturn a number DFGKCK999
= it's OK, recognized
"fastboot oem device-info"
Should give 4 or 5 lines. One is Device unlocked "true" or "false"
If true, it's OK.
Just flash the recovery here :
http://forum.xda-developers.com/oneplus-x/development/unofficial-twrp-3-0-2-0-recovery-onyx-t3471584
Reboot directly to recovery with the buttons to be sure he's sticked
Thanks
And to root it, which version of SuperSU ?
Sent from my LG-D855 using Tapatalk
Flash SR5 Super su version.
Link here :
http://forum.xda-developers.com/oneplus-x/general/discussion-how-to-root-oneplus-x-t3242830
I installed TWRP which worked OK but I have installed SuperSU v2.79 that you referred to and now I have a bootloop. What can I do ?
[EDIT] Needed the proper version on SuperSU found in post #2 here - https://forums.oneplus.net/threads/oos3-0-twrp-root-make-mm-great-again.440706/
In fact, the last post in the XDA link from Keno40 confirmed that SR5 didn't work. If only I had read that before getting close to heart failure !!!
hello xda community..im new with this device and want to install custom recovery and root my device..i cant find any method how to do it on miui 10.3.5.0..i afraid iff i mess with my device..please point me how to do it..thanks you..
It should be the same method to previous versions.
thanks you..seems like previous version of twrp work with 10.3.5..im already flash twrp and rooted now..