Hello guys! Lets test if anybody still here...)
What is latest fully functional TWRP recovery for Lollipop 5.1.1 stock firmware, where to get it and in what partition do I need to flash it?
Does installing some zips or firmwares on different roms needs supported recovery version? If so, please tell what ROMs need what recovery versions.
I've seen even TWRP 3.1.1 build but have concerns in its functionality and stability. Is it working normal?
Last, wanted to say thanks for all developers that made us using such a great device for so long period of time.
Hope people are still subscribed to this forums.
That TWRP 3.1.1 was never fixed as you can read in the thread.
First flash latest .236 stock rom with flashtool if you have not done this before.
And then you flash this recovery in fastboot:
https://forum.xda-developers.com/xp...ent/twrp-recovery-2-8-7-0-2016-02-03-t3307043
You never need to touch the recovery again once you flashed this recovery all roms from kitkat and up works with this one.
Related
Hi again,
I kind of feel bad for almost only asking questions, but this place has been and continues to be a fantastic resource for learning when my search results turn up dry.
I'm running my Z2 on the generic, international .402 firmware with a locked bootloader, rooted via the easy root tool. I have Nut's PhilZ/TWRP dual-recovery installed, but the rest of the phone is stock.
As explained in this thread, the dual-recovery from Nut works on both locked and unlocked bootloaders, so long as you're using the stock Sony kernel (which is the case here). I'm planning on unlocking my bootloader and flashing either Carbon or CM11 soon, but I don't know what will happen to the recovery: will the dual-recovery no longer work because a new ROM (and new kernel) have been flashed? Will this version of TWRP work in its place?
If anybody has flashed an AOSP ROM onto a Z2 and could provide some insight, it would be a big help. Thanks.
Hi.
All you have to do is flashing NUTs dual recovery right after flashing your custom rom. Then you should keep your dual recovery.
More information could be found in the following thread.
http://forum.xda-developers.com/showthread.php?t=2785598
Hello everyone, i know i am really late in the game here by playing with this phone but my friend has one and wants me to fix it up for him. it is completely stock running android 2.3.6. I can't seem to make heads or tails of how to stick a recovery on this thing and flash a rom. can anyone point me in the right direction as how to do this? thanks mates
First thing you need to know is that the recovery is compiled into the kernel, so you don't flash a recovery separately, you just flash a custom kernel and you will have a custom recovery after.
The latest stock firmware for this phone is 4.1.2 Jelly Bean, but since the phone is still on the original 2.3.6 firmware, you could flash the old Siyah kernel and use it's recovery to flash custom firmware.
You need to root the phone first. You can root this phone with Framaroot using the Aragorn exploit. Then go to this post and download the Tar version of Siyah 2.6.14 Kernel. Flash it in PDA without ticking Re-Partitioning.
Stable custom Touchwiz based firmware available in the development forum are SHOstock or Cooked. Both are based on 4.1.2, and neither are currently supported but both are stable.
If you want something more recent, there are various aosp based firmwares available in the development forum. You may not be able to flash some of them directly from that old recovery in Siyah 2.6.14, but if you need help, you'll have to try to get some help in their threads, because I don't use those.
Happy flashing, and if you need help, ask.
creepyncrawly said:
First thing you need to know is that the recovery is compiled into the kernel, so you don't flash a recovery separately, you just flash a custom kernel and you will have a custom recovery after.
The latest stock firmware for this phone is 4.1.2 Jelly Bean, but since the phone is still on the original 2.3.6 firmware, you could flash the old Siyah kernel and use it's recovery to flash custom firmware.
You need to root the phone first. You can root this phone with Framaroot using the Aragorn exploit. Then go to this post and download the Tar version of Siyah 2.6.14 Kernel. Flash it in PDA without ticking Re-Partitioning.
Stable custom Touchwiz based firmware available in the development forum are SHOstock or Cooked. Both are based on 4.1.2, and neither are currently supported but both are stable.
If you want something more recent, there are various aosp based firmwares available in the development forum. You may not be able to flash some of them directly from that old recovery in Siyah 2.6.14, but if you need help, you'll have to try to get some help in their threads, because I don't use those.
Happy flashing, and if you need help, ask.
Click to expand...
Click to collapse
If you don't mind me asking, what's the benefit of having the recovery compiled into the kernel. Do you think it is better than having them separately, and if so, can you explain why?
azeem40 said:
If you don't mind me asking, what's the benefit of having the recovery compiled into the kernel. Do you think it is better than having them separately, and if so, can you explain why?
Click to expand...
Click to collapse
You'd have to ask the Samsung engineers why they did that. Since the more common standard is to have the recovery in it's own separate partition, it suggests that is the better solution, I would think.
Having been on a device for a while that has a separate partition for recovery (N5), it's a feature that is extremely comforting in that it is virtually impossible to brick those types of devices.
The way I see it is that having the kernel on the same partition as the recovery is beneficial as more kernels can be built, instead of it being ignored.
OK. I'm on stock 4.0.4 , ucll6 and I wanna directly root and install LP and mm roms. What's best method? All threads seem to be unmaintained and outdated. Thanks.
Did root via arogon method. Now what recovery do I flash? Figuring kernels are flashed with it.
My name says it all. That said I'm pretty sure that you are going to have to increase your space to be able to install MM with the appropriate gapps package. Same holds true for most LP roms on here.
You might can try this thread for a LP rom with a pico gapps package http://forum.xda-developers.com/gal.../cyanogenmod-12-unofficial-i777-call-t3211103 (note: I'm not sure it requires resizing partitions since it does not specify.) Should be able to also find a version of TWRP 2.7.1.0 or newer floating around here. I also add that though lots of these threads on here haven't been posted in in a couple of years, the information you find is still uptodate. GL
AnotherFreakinNoob said:
My name says it all. That said I'm pretty sure that you are going to have to increase your space to be able to install MM with the appropriate gapps package. Same holds true for most LP roms on here.
You might can try this thread for a LP rom with a pico gapps package http://forum.xda-developers.com/gal.../cyanogenmod-12-unofficial-i777-call-t3211103 (note: I'm not sure it requires resizing partitions since it does not specify.) Should be able to also find a version of TWRP 2.7.1.0 or newer floating around here. I also add that though lots of these threads on here haven't been posted in in a couple of years, the information you find is still uptodate. GL
Click to expand...
Click to collapse
If I flash that twrp 2.7, wouldn't I need a certain kernel?
Honestly man I can't say for sure. Sorry.
I'm running a s959g and followed the guide in the help forum laid out by Mr.cook (you'd likely find more/better help in the help forum). I will say that from what I gathered the kernel and recovery are linked in the S2. That said when I flashed my 1st recovery I was on stock 2.3.6 Gingerbread and went straight to the TWRP 2.7 version. From there I flashed Rogersb11's 4.4.4 ROM that had the shift kernel (awesome kernel btw check it out) built in. GL
ETA: I'd almost say that as long as you find a i777 version of the TWRP and installed it you'd be good to go.
Hi Devs,
I have tried to unlock bootloader [SD] by Mi Official method but got no success. :crying:
Always stuck at 50%.
I am wondering if the BL is unlocked via an unofficial way then can I flash AOSP based roms right away.
If yes, kindly suggest a way to unlock BL because I came across with so many threads each is somewhat different.
I have changed MIUI roms to try my luck say global -> global beta -> (soft brick) -> china beta.
Got confused, currently I am on China Dev Rom.
My Understanding till now ---
1. Unlock BL
2. FLash TWRP
3. Wipe All
4. Flash CM firmware -> Flash AOSP rom
5. Success...:silly:
Kindly guide if anyone had done this before.
i was having something similar to you.
i wanted to flash cyanogen roms but i didnt waited until i get the unlocker code from xiaomi.
i followed this tutorial
https://forum.xda-developers.com/redmi-note-3/how-to/method-to-flash-twrp-recovery-unlock-t3473294
it makes you flash a dev/beta global miui rom (i suggest you 6.9.29) with a custom recovery (you delete the stock recovery and replace it with a custom one like aika recovery or zcx recovery). then use the app miflash (latest version support windows 32 &64 bit, olders ones only 64 bit) to flash the entire miui rom.
When you finished you will have a miui rom with custom twrp. Then you boot to recovery (dont let the phone boot to system) and twrp will overwrite stock recovery) then you reboot to system and there you go. You will have miui and a fully working custom recovery (there you can flash supersu, cyanogen roms, xposed, and every other zip you want)
BraianV said:
i was having something similar to you.
i wanted to flash cyanogen roms but i didnt waited until i get the unlocker code from xiaomi.
i followed this tutorial
https://forum.xda-developers.com/redmi-note-3/how-to/method-to-flash-twrp-recovery-unlock-t3473294
it makes you flash a dev/beta global miui rom (i suggest you 6.9.29) with a custom recovery (you delete the stock recovery and replace it with a custom one like aika recovery or zcx recovery). then use the app miflash (latest version support windows 32 &64 bit, olders ones only 64 bit) to flash the entire miui rom.
When you finished you will have a miui rom with custom twrp. Then you boot to recovery (dont let the phone boot to system) and twrp will overwrite stock recovery) then you reboot to system and there you go. You will have miui and a fully working custom recovery (there you can flash supersu, cyanogen roms, xposed, and every other zip you want)
Click to expand...
Click to collapse
I have gone through full thread. https://forum.xda-developers.com/redmi-note-3/how-to/method-to-flash-twrp-recovery-unlock-t3473294
For some it works, but no one has widely used it to flash custom kernal or rom. All again stayed on MiUI.
It seems that nobody is quite clear about how this stuff works because members have asked questions like
How would official TWRP boot on locked BL
Working of Custom kernals
Modified BLs
I am planning to flash Unofficial LineageOS 7.1.1 or RR.
kindly confirm If you did this on Kenzo itself with some custom kernal and rom.
anurag86 said:
I have gone through full thread. https://forum.xda-developers.com/redmi-note-3/how-to/method-to-flash-twrp-recovery-unlock-t3473294
For some it works, but no one has widely used it to flash custom kernal or rom. All again stayed on MiUI.
It seems that nobody is quite clear about how this stuff works because members have asked questions like
How would official TWRP boot on locked BL
Working of Custom kernals
Modified BLs
I am planning to flash Unofficial LineageOS 7.1.1 or RR.
kindly confirm If you did this on Kenzo itself with some custom kernal and rom.
Click to expand...
Click to collapse
I did. After i flashed dev 6.9.29 miui rom with zxc twrp i flashed rr 5.8.0 (Android 7.1) with cm14 firmware, gapps and custom kernel (radon 3.5).
Not a single problem. Try it
---------- Post added at 07:54 PM ---------- Previous post was at 07:52 PM ----------
anurag86 said:
I have gone through full thread. https://forum.xda-developers.com/redmi-note-3/how-to/method-to-flash-twrp-recovery-unlock-t3473294
For some it works, but no one has widely used it to flash custom kernal or rom. All again stayed on MiUI.
It seems that nobody is quite clear about how this stuff works because members have asked questions like
How would official TWRP boot on locked BL
Working of Custom kernals
Modified BLs
I am planning to flash Unofficial LineageOS 7.1.1 or RR.
kindly confirm If you did this on Kenzo itself with some custom kernal and rom.
Click to expand...
Click to collapse
I did it with Kate. The only difference is that i change "cm14 firmware" to put Kate módem (original cm14 firmware has kenzo modem).
You are missing drivers on PC thats why you are getting 50% error... Sign in i.mi and locate...install MiFlash on PC 64bit, win7+, if you are on china dev ->turn on usb debbugging-> boot in fastboot mode,use original cable run MiUnlock and unlock, it will work 100%. I have unlocked BL so many times on different computers...and it always worked...if done all right
Denis:) said:
You are missing drivers on PC thats why you are getting 50% error... Sign in i.mi and locate...install MiFlash on PC 64bit, win7+, if you are on china dev ->turn on usb debbugging-> boot in fastboot mode,use original cable run MiUnlock and unlock, it will work 100%. I have unlocked BL so many times on different computers...and it always worked...if done all right
Click to expand...
Click to collapse
Hi Denis, I have installed MIPcSuite. I think it contains all drivers for our device.
Further drivers from MIFlash tool are also present in my PC.
If you have a specific version kindly tell me.
Say ver of - MiFlash , China Dev or Global Dev , MiUnlock.
off course I am using Mi Cable shipped with device.
@BraianV - I have flashed Lineage. Votle Issues. :good:Hitted Thanks for help.
Hi everyone,
Well, I came to you because actually I'm out of idea.
I was since 3 years on custom ROM (CM and Lineage OS) and due to substratum, I had a bootloop.
My problem is quite particular, after a total clean of my device and flashing the stock ROM, custom recovery cause me some trouble.
Whatever I try (CWM touch 6 or TWPR 3.1.1), I can't flash custom ROM (Lineage OS 14.1), TWPR or CWM crash 1 second after the flash command and reboot, with disable touchscreen and even by using old navigation way and try again, same problem.
Tried also to disable file signature check but no effect.
Quick summary about what I did:
- Device: Samsung Galaxy S4 (GT-I9505)
- ROM stock used: I9505XXUHOJ2 ( the build which is based on the CF-Root file i used)
- Tried to install CWM by ROM Manager and ODIN (v3.09)
- TWPR installed by TWPR App using file in .img and not the second option (tar.img) for LTE Internationnal Qualcomm.
-Checked the root before last attemptwith root checker and it was ok.
In advance thanks for your help and I really hope it's not too serious.
By the way, sorry for my english, it's not my native language
Sinistros said:
Hi everyone, Well, I came to you because actually I'm out of idea. I was since 3 years on custom ROM (CM and Lineage OS) and due to substratum, I had a bootloop.
My problem is quite particular, after a total clean of my device and flashing the stock ROM, custom recovery cause me some trouble. Whatever I try (CWM touch 6 or TWPR 3.1.1), I can't flash custom ROM (Lineage OS 14.1), TWPR or CWM crash 1 second after the flash command and reboot, with disable touchscreen and even by using old navigation way and try again, same problem...
Click to expand...
Click to collapse
I don't have this variant but, this looks like it may be a recovery issue so your best bet is to post this question within the following Official TWRP thread for your device.
https://forum.xda-developers.com/showthread.php?t=2468187
If it's a LineageOS issue, then your best bet is to post this question within the following Official LineageOS thread for your device.
https://forum.xda-developers.com/showthread.php?t=3573386
If all else fails, you can try posting your question within the following Q&A thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=2192886
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Thanks for advice
I will post in the S4 forum section hoping someone already know a fix or a way to dodge this problem.
But I have small questions before:
I saw some threads about CWM and TWPR recovery "for" I9505, is there a huge difference between them and their basic version ?
And finally, I saw some threads on TWPR 3.+ issue for some devices.
An installation of an older version of TWPR or CWM could be a good way to explore the problem source ? (the stock ROM I use even after updates is quite old in terms of Android versions and patch)
Have a good day
Edited*
Sorry had a bug and got a double post