This TWRP recovery Is compiled from source & also supported officially
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Prerequisites
1. Unlocked bootloader.
Bugs
1. No bugs
2. If you have found a bug, please consider posting it to my GitHub Issues.
Instructions
1. Go to the fastboot mode.
2. Download the recovery.img and transfer it to the adb folder.
3. Open the cmd/terminal and change directory into the adb folder.
4. Now confirm/check that device is connected by typing:-
Code:
fastboot devices
If you got your device seriel number there then you are ready to continue otherwise try connecting device again and make sure USB debugging is on and you have granted permission to the PC to debug.
5. After that we will flash this TWRP recovery to the recovery partition by below command:-
Code:
fastboot flash recovery twrp-name.img
BooM ! TWRP flashed successfully.
6. Now unplug your device and then hold power button untill the phone turned off,after that press power button while holding vol down(-) button simultaneously and you will boot into TWRP recovery mode.
Enjoy !
Downloads
Android File Host: https://androidfilehost.com/?w=files&flid=296466
Official TWRP Page: https://twrp.me/realme/realme3.html
XDA:DevDB Information
TWRP For Realme 3, Kernel for the Oppo Realme 3
Contributors
chankruze
Source Code: https://github.com/N00bTree/android_device_realme_spartan
Kernel Special Features:
Version Information
Status: Stable
Created 2019-05-27
Last Updated 2019-07-16
Awesome bro:good:
Have you tested it because you submitted your previous twrp for rm3 pro without testing
MayanKKaushik said:
Have you tested it because you submitted your previous twrp for rm3 pro without testing
Click to expand...
Click to collapse
Did i submitted this ?
There are more then 500 members and none reports back, so what should i do ? At least if that was published, people will test and bugs would be noted.
And please read both threads, i clearly mentioned in DevDB that it is testing build.
chankruze said:
This TWRP recovery Is compiled from source & will be supported officially soon
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Prerequisites
1. Unlocked bootloader.
Bugs
1. No bugs
2. If you have found a bug, please consider posting it to my GitHub Issues.
Instructions
1. Go to the fastboot mode.
2. Download the recovery.img and transfer it to the adb folder.
3. Open the cmd/terminal and change directory into the adb folder.
4. Now confirm/check that device is connected by typing:-
If you got your device seriel number there then you are ready to continue otherwise try connecting device again and make sure USB debugging is on and you have granted permission to the PC to debug.
5. After that we will flash this TWRP recovery to the recovery partition by below command:-
BooM ! TWRP flashed successfully.
6. Now unplug your device and then hold power button untill the phone turned off,after that press power button while holding vol down(-) button simultaneously and you will boot into TWRP recovery mode.
Enjoy !
Downloads
Android File Host:https://www.androidfilehost.com/?fid=6006931924117883150(new build)
Official TWRP Page: Not submitted yet
Unofficial GitHub Release : will be updated soon
XDA:DevDB Information
TWRP For Realme 3, Kernel for the Oppo Realme 3
Contributors
chankruze
Source Code:https://github.com/N00bTree/android_device_realme_spartan
Kernel Special Features:
Version Information
Status: Testing
Created 2019-05-27
Last Updated 2019-05-27
Click to expand...
Click to collapse
Any backup stock recovery.img ? For avoid device from bootloop..
chankruze said:
Did i submitted this ?
There are more then 500 members and none reports back, so what should i do ? At least if that was published, people will test and bugs would be noted.
And please read both threads, i clearly mentioned in DevDB that it is testing build.
Click to expand...
Click to collapse
Well you said that it was stable when a person softbricked its device. Atleast you could have written that it has not been tested yet.
Yes in last build column you wrote testing but in your thread you clearly mentioned that it had no bugs and stable means tgat it was well tested before.
haditriw said:
Any backup stock recovery.img ? For avoid device from bootloop..
Click to expand...
Click to collapse
Here is stock recovery:
https://www.androidfilehost.com/?fid=1395089523397966781
twrp not working, just boot to home screen..
1. flash twrp recovery - boot to twrp (power + vol up) => to homescreen
2. flash twrp recovery - boot to twrp (power + vol down) => fastboot mode
3. flash twrp recovery - boot to twrp (fastboot boot twrp.img) => to homescreen
Edit : size of the stock recovery.img and twrp.img that build, i think same..
how next? how about type "fastboot oem reboot-recovery" ??
EDIT : suck,, hardbrick,, when flashing twrp and command "fastboot oem reboot-recovery"
Microsoft Windows [Version 10.0.17134.345]
(c) 2018 Microsoft Corporation. All rights reserved.
C:\Users\COMPUTER 1>cd c:\adb\
c:\adb>fastboot devices
FUVW9H5SKJOFA67T fastboot
c:\adb>fastboot flash recovery twrp_r3_avbv1.img
target reported max download size of 134217728 bytes
sending 'recovery' (23957 KB)...
OKAY [ 1.101s]
writing 'recovery'...
OKAY [ 0.413s]
finished. total time: 1.513s
c:\adb>fastboot devices
FUVW9H5SKJOFA67T fastboot
c:\adb>fastboot flash recovery twrp_r3_avbv1.img
target reported max download size of 134217728 bytes
sending 'recovery' (23957 KB)...
OKAY [ 1.096s]
writing 'recovery'...
OKAY [ 0.334s]
finished. total time: 1.430s
c:\adb>fastboot boot twrp_r3_avbv1.img
downloading 'boot.img'...
OKAY [ 1.016s]
booting...
OKAY [ 0.047s]
finished. total time: 1.078s
c:\adb>fastboot flash recovery twrp_r3_avbv2.img
target reported max download size of 134217728 bytes
sending 'recovery' (65536 KB)...
OKAY [ 2.991s]
writing 'recovery'...
OKAY [ 0.856s]
finished. total time: 3.863s
c:\adb>fastboot flash recovery twrp_r3_avbv2.img
target reported max download size of 134217728 bytes
sending 'recovery' (65536 KB)...
OKAY [ 2.973s]
writing 'recovery'...
OKAY [ 0.866s]
finished. total time: 3.839s
c:\adb>fastboot boot twrp_r3_avbv2.img
downloading 'boot.img'...
OKAY [ 2.770s]
booting...
OKAY [ 0.063s]
finished. total time: 2.849s
c:\adb>fastboot oem reboot-recovery
...
OKAY [ -0.000s]
finished. total time: -0.000s
c:\adb>fastboot flash recovery twrp_r3_avbv1.img
target reported max download size of 134217728 bytes
sending 'recovery' (23957 KB)...
OKAY [ 1.100s]
writing 'recovery'...
OKAY [ 0.328s]
finished. total time: 1.444s
c:\adb>fastboot oem reboot-recovery
...
OKAY [ -0.000s]
finished. total time: -0.000s
c:\adb>fastboot devices
c:\adb>adb devices
List of devices attached
FUVW9H5SKJOFA67T recovery
c:\adb>adb rebootb-bootloader
adb: usage: unknown command rebootb-bootloader
c:\adb>adb reboot-bootloader
can reboot, i think to boot into recovery, use command "fastboot oem reboot-recovery", it will make blank screen but still can access adb, when it reboot by adb n boot again via "fastboot oem reboot-recovery", it will be replaced by stock recovery
Great. The rest is waiting for a stable custom rom.
Thanks for testing, it seems the flashing is not persistence. we are working on updating tree.
And fastboot oem reboot-recovery will replace stock recovery if executed right after flashing.
You can keep track of issues here: https://github.com/N00bTree/android_device_realme_spartan/issues
chankruze said:
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Prerequisites
1. Unlocked bootloader.
Bugs
1. Not tested yet, be the tester.
2. If you have found a bug, please consider posting it to my GitHub Issues.
Instructions
1. Go to the fastboot mode.
2. Download the recovery.img and transfer it to the adb folder.
3. Open the cmd/terminal and change directory into the adb folder.
4. Now confirm/check that device is connected by typing:-
If you got your device seriel number there then you are ready to continue otherwise try connecting device again and make sure USB debugging is on and you have granted permission to the PC to debug.
5. After that we will flash this TWRP recovery to the recovery partition by below command:-
BooM ! TWRP flashed successfully.
6. Now unplug your device and then hold power button untill the phone turned off,after that press power button while holding vol down(-) button simultaneously and you will boot into TWRP recovery mode.
Enjoy !
Downloads
Test build 002 => https://www.androidfilehost.com/?fid=6006931924117883150
Test build 001 with AVB v1 & v2 (separate twrp) => https://www.androidfilehost.com/?fid=6006931924117882957
Note: The stock recovery is signed with AVB v1. The generated twrp is v2 by default. @fawazahmed0 did signed twrp with v1. Both are packed in one archive and available at above link. Try v1 and report the issues.
XDA:DevDB Information
TWRP For Realme 3
Contributors
chankruze
@fawazahmed0
Source Code:https://github.com/N00bTree/android_device_realme_spartan
Version Information
Status: Testing
OS Version: 9.0
Based on : TWRP
Created 2019-05-27
Last Updated 2019-05-27
Click to expand...
Click to collapse
Thanks for sharing
Working P60 or P70 ???
Bombervikz said:
Working P60 or P70 ???
Click to expand...
Click to collapse
For Both
Has any one able to boot it ??
has anyone been successful
ViDroidL said:
Thanks for sharing
Click to expand...
Click to collapse
What about realme 3pro
After flashing the stock recovery.img from the file shared by @fawazahmed0 , I cannot boot into recovery with power button and volume buttons. Tried with both volume up and down. It still boots into family mode with power + volume up/down. Please help me flashing it correctly. I used the same command:
fastboot flash recovery recovery.img
Not Working on me
Power + Up = Reboot Normal
Power + Down = Bootloader
Related
This is for Re-locking and Un-Rooting the US WIFI Xoom BUILD HWI69 ONLY
This is for use only on the Wifi-Only Xoom HWI69 build. Check your build number before you install!!!
Please note the following information does contain official Motorola images from a non Motorola source. The information in this thread has been tested, however I can not confirm that it will work for every situation. In no way will I or xda-developers.com be held accountable for any damage resulting from using this information. Use the following with extreme caution.
1. Download the necessary files from here:
http://www.android.net/forum/downloads.php?do=file&id=39
2. Unzip the files to the directory you will be running ADB from.
3. Enter the following commands into the command prompt
adb reboot bootloader
Xoom will then reboot into bootloader screen
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
After the final reboot you should be back to stock, Locked and Un-Rooted.
note: If you are using Terminal on a mac your commands should include a ./ before every command like this:
./adb reboot bootloader
Xoom will then reboot into bootloader screen
./fastboot flash boot boot.img
./fastboot flash system system.img
./fastboot flash recovery recovery.img
./fastboot flash userdata userdata.img
./fastboot erase cache
./fastboot oem lock
Credits go to Steady Hawkin on xoomforums.com
first of all, there is no hw169, it's a hwi69!
second, did u try this? b-coz last time when i try it, my xoom die
third in os x terminal commands is same like windows one
Last login: Wed May 18 22:11:38 on ttys000
Hooligans:~ Hooligan$ ./adb reboot bootloder
-bash: ./adb: No such file or directory
Hooligans:~ Hooligan$ adb reboot bootloder
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Click to expand...
Click to collapse
HooliganBG said:
first of all, there is no hw169, it's a hwi69!
second, did u try this? b-coz last time when i try it, my xoom die
third in os x terminal commands is same like windows one
Click to expand...
Click to collapse
fixed build number, thanks for that! ya i just did it yesterday and worked no problem.
everytime i run commands in terminal on my mac i have to put the ./ or else it wont work, never worked for me just typing it in normally
I just tried this and it works great! Excellent work OP!
After unrooting and unlocking and My 3.1 updates kicked in right away..... I think I will be running stock for a while
I flashed 3.1 from clockwork. Will this still work? Does the Xoom check for version before booting? like some HTC and Motorola phones?
Buddhahb said:
I flashed 3.1 from clockwork. Will this still work? Does the Xoom check for version before booting? like some HTC and Motorola phones?
Click to expand...
Click to collapse
check your build number in settings>about phone, it has to be HWI69 in order for this to work
I have that model. I was just making sure it wouldn't be a problem that I hate flashed the 3.1 update
what format are these imgs in?
I am trying to unyaffs them but it is not the right format
Your trying to what?
The build number does not matter. All that matters is you flash official images for YOUR device. For example the US wifi images on a us wifi device. The same goes for the 3g. Just do not relock the bootloader with out those images flash onto the device.
In a year from now your device could be running ice cream sandwich with who knows what build number. Unlocked bootloader = flash back official images when ever you want.
Sent from my Xoom using Tapatalk
I am trying to get the data out (on my pc)
I lost all the default stuff that come with the xoom.
Does doing the ota to android 3.1 change build number from HWI69 to HMJ37?
worked nice thanks man... sad to say im taking this thing back today to get the less cool looking transformer for 200 dollars less... same thing just looks not as cool... supposedly screen display is better too... thanks again..
yes it does... ur wifi onnly us xoom should have been that to begin with before the ota...
Video for Noobs
Made a video using this Tutorial for anyone interested.
http://www.youtube.com/watch?v=pT8NF-_nLCo
Gave all credit to those it belongs to.
Tried this last night but used HMJ37 instead of HWI69 and got myself into a weird situation where it wouldn't boot (stuck on Dual Core screen). Had to power off and use vol+ to get to fast boot and unlock again.
Is HWI69 the only build that can be oem locked ?
-Matt
Thanks!
Worked perfectly, thank you for taking the time to post this useful thread.
Code:
c:\android-sdk-windows>adb reboot bootloader
* daemon not running. starting it now *
* daemon started successfully *
c:\android-sdk-windows>cd tools
c:\android-sdk-windows\tools>fastboot flash boot boot.img
sending 'boot' (8192 KB)... OKAY [ 1.039s]
writing 'boot'... OKAY [ 2.139s]
finished. total time: 3.179s
c:\android-sdk-windows\tools>fastboot flash system system.img
sending 'system' (262144 KB)... OKAY [ 27.063s]
writing 'system'... OKAY [ 14.166s]
finished. total time: 41.231s
c:\android-sdk-windows\tools>fastboot flash recovery recovery.img
sending 'recovery' (12288 KB)... OKAY [ 1.427s]
writing 'recovery'... OKAY [ 2.038s]
finished. total time: 3.466s
c:\android-sdk-windows\tools>fastboot flash userdata userdata.img
sending 'userdata' (139233 KB)... OKAY [ 13.288s]
writing 'userdata'... OKAY [ 21.292s]
finished. total time: 34.582s
c:\android-sdk-windows\tools>fastboot erase cache
erasing 'cache'... OKAY [ 1.615s]
finished. total time: 1.616s
c:\android-sdk-windows\tools>fastboot oem lock
... INFO To continue, follow instructions on the d
evice's display...
OKAY [101.907s]
finished. total time: 101.908s
I'm trying to flash twrp to my lg g4. I've reached the part where I run
Code:
fastboot flash recovery twrp.img
And everything seems to work fine, but when I try to enter recovery mode, I get the default lg recovery (restore factory mode options) and not twrp.
Here's what it prints out when I run the flash command:
Code:
target reported max download size of 536870912 bytes
sending 'recovery' (32060 KB)...
OKAY [ 0.827s]
writing 'recovery'...
OKAY [ 0.341s]
finished. total time: 1.168s
What am I doing wrong?
I tried doing it from a different computer and tried flashing older version of twrp.
No mate, you're not doing something wrong. You must overwrite the stock recovery, because it auto-flashes every time when phone starts. Best way is to use these commands :
adb reboot bootloader
fastboot boot recovery.img (rename recovery recovery.img , without .img (that's the extension, only "recovery", to make it clear)
I'm waiting the results....
Boot the image like. Azza_09 said then when TWRP has booted click on install then change to img instead of zip and select your twrp image. That should work, but Lg front end will be shown when booting to bootloader, simply answer both questions with yes then TWRP will load
Hi,
As per the links
https://twrp.me/devices/androidone.html; and
https://download.cyanogenmod.org/?device=sprout4;
TWRP 2.8.4 and cm-13.0-20160418-SNAPSHOT-ZNH0EAO2NL-sprout4 are compatible for Canvas A1 (AQ4501).
And I downloaded both and put them in C:\Users\Admin\AppData\Local\Android\sdk\platform-tools>
Then I started and I am getting following issues;
C:\Users\Admin\AppData\Local\Android\sdk\platform-tools>
C:\Users\Admin\AppData\Local\Android\sdk\platform-tools>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: no devices/emulators found
C:\Users\Admin\AppData\Local\Android\sdk\platform-tools>fastboot devices
JHFKSHOIER4HBYKJLR fastboot
C:\Users\Admin\AppData\Local\Android\sdk\platform-tools>fastboot oem unlock
...
(bootloader) Start unlock flow
OKAY [ 9.610s]
finished. total time: 9.625s
C:\Users\Admin\AppData\Local\Android\sdk\platform-tools>fastboot flash recovery
twrp-2.8.4.0-m8.img
target reported max download size of 134217728 bytes
sending 'recovery' (16092 KB)...
OKAY [ 0.640s]
writing 'recovery'...
FAILED (remote: size too large)
finished. total time: 0.671s
C:\Users\Admin\AppData\Local\Android\sdk\platform-tools>
I run these commands also:
fastboot flash –S 256M system twrp-2.8.4.0-m8.img and
fastboot -w
After this, whenever I turn on my mobile, I see Micromax Logo with OEM unlocked. And its stuck on the same screen.
If I turn on mobile by Power+Vol.Up, I see black screen with following options ..
Select Boot Mode:
[volume_up to select. Volume_down is ok.]
[Recovery Mode]
[Fastboot Mode]
[Normal Boot]
[Normal Boot +ftrace]
[Normal slub debug off]
If I select Normal Mode, it says, OEM unlocked with Micromax Logo and no further changes.
If I select Recovery Mode, it shows.. http://bit.do/anderror
I tried to flash Stock ROM. And I followed the steps of links:
http://firmwarefile.com/micromax-aq4501
https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
According to the steps mentioned in the link, when I click on download, No changes on the ‘Smart Phone Flash Tool’. It just says, Searching and no further changes.
I believe, I can use fastboot commands only. And not able to use any adb commands. In such case which fastboot command can fix it?
Please help me to resolve this issue.
Regards
Ugn10
Check the drivers it may not installed properly and if your phone is booting up then just use the Android one toolkit and flash custom recovery than flash the stock ROM through it
Hi All.
Just bought a Wileyfox Swift. I'd like to install Lineage OS.
Reboot into bootloader, fastboot sees correctly my phone.
I run "fastboot oem unlock-go", my data gets wiped, then "fastboot reboot" and Android starts optimizing apps. Fine.
I go back into bootloader, now I try to flash TWRP:
Code:
# fastboot flash recovery twrp-3.0.3-0-crackling.img
target reported max download size of 268435456 bytes
sending 'recovery' (16908 KB)...
OKAY [ 0.532s]
writing 'recovery'...
OKAY [ 0.284s]
finished. total time: 0.816s
I reboot, Android starts correctly, power off. Go back into recovery but I still have the original Cyanogen recovery, no TWRP. What I'm doing wrong?
Thanks in advance for any hint!
If you are on the fastboot screen after flashing you should just select recovery and go there
There's no selection menu in fastboot mode on this phone. To go back into recovery I have to power off the device and power on again with volume-down + power button; but the recovery I got into isn't the TWRP I flashed but still the original cyanogenos recovery.
Pull battery after flashing recovery via fastboot. Then boot straight into recovery (not fastboot, not normal ROM), TWRP should be there.
hello,
in Fastboot-mode I flash TWRP successfull, but when I want to boot recovery, it starts Redmi-Recovery 3.0.
No start of twrp-recovery.
Commands: (same commands I have tried with Windows 10, other TWRP-versions I tried too.)
$ fastboot devices
tkx4gm5575vod69p fastboot
$ fastboot flash recovery twrp-3.7.0_9-0-begonia.img
Sending 'recovery' (31380 KB) OKAY [ 0.876s]
Writing 'recovery' OKAY [ 0.248s]
Finished. Total time: 5.123s
Shutdown phone, Press Power On/off + Volume-Up, Press Volume-Up and it starts Redmi-Recovery 3.0.
Where is my mistake?
got done, used alternative twrp
"twrp-3.7.0_9-0-begonia.img"
I think this is official twrp, but this is for Android 9.0
I tried flash LineageOS20 by using twrp-3.5.0_10-UNIFIED_UNOFFICIAL.img.
I installed Lineage from twrp but now hard brick has happened... nothing boots, no bootloader/fastboot
so I will try windows connects with dead phone and flash Stock-Rom Begonia / Android 9.
edu.mc said:
I tried flash LineageOS20 by using twrp-3.5.0_10-UNIFIED_UNOFFICIAL.img.
I installed Lineage from twrp but now hard brick has happened... nothing boots, no bootloader/fastboot
so I will try windows connects with dead phone and flash Stock-Rom Begonia / Android 9.
Click to expand...
Click to collapse
which lineage did you flash?
There is no official as far as I can see. unofficial too.
lineage-20.0-20220822-UNOFFICIAL-begonia.zip
(I don't know from which address I download it. I searched unsuccessful)
https://sourceforge.net/projects/darkjoker360-developements/files/Xiaomi/Redmi%20Note%208%20Pro/ROM/20.x/lineage-20.0-20220822-UNOFFICIAL-begonia.zip/download?use_mirror=netcologne&use_mirror=netcologne&r=