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>
/*
* Your warranty is now void.
*
* 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.
*
*/
Features:
All function in a normal TWRP
Multi-language support
MTP
Backup/Restore
Install guide:
1. Install fastboot tools from google's sdk on your PC
2. Enter fastboot mode
3. Unlock your bootloader
4. Run "fastboot flash recovery imgfilename.img" in command line ( if you want you can go in recovery from bastboot using this command "fastboot boot imgfilename.img" )
5. Reboot and enjoy it
Download:
Official Pace TWRPs
TWRP 3.2.3-6 Pace A1602 Full
TWRP 3.2.3-7 Pace A1612 Full
TWRP 3.2.3-5 Stratos Full
TWRP 3.2.3-5 Verge Full
Source code:
https://github.com/omnirom/android_bootable_recovery
https://github.com/mauronofrio/android_device_huami_huanghe-twrp
https://github.com/mauronofrio/android_device_huami_everest-twrp
https://github.com/mauronofrio/android_device_huami_qogir-twrp
Thanks to @TingyiChen for the base
DONATE LINK
If you want to support the project please consider making a donation, thanks.
Created 2018-11-28
Many thanks!
Can you provide images
tiago199988 said:
Can you provide images
Click to expand...
Click to collapse
and this what is?
mauronofrio said:
Download:
TWRP 3.2.3-3 Pace
Click to expand...
Click to collapse
Would some pictures not be?
Do not use, it ****s up the serial of the watch
1immortal said:
Do not use, it ****s up the serial of the watch
Click to expand...
Click to collapse
Yes unfortunately there was this bug in the older one, with the new one this bug is solved.
Please all use this twrp check if they have the serial number, if you have not it please follow this guide:
https://forum.xda-developers.com/smartwatch/amazfit/guide-restore-null-sn-locked-t3775998
Could I use this recovery image on Stratos CN version (1609)?
Thanks.
Vandriod said:
Could I use this recovery image on Stratos CN version (1609)?
Thanks.
Click to expand...
Click to collapse
Yes
1immortal said:
Do not use, it ****s up the serial of the watch
Click to expand...
Click to collapse
Pace or Stratos ?
---------- Post added at 20:21 ---------- Previous post was at 20:20 ----------
Can we flash SuperSU with this ?
AFAIK We have MIPS ,not arm ,also supersu wasn't ported to Android Wear (If that matters).
The4anoni said:
Pace or Stratos ?
---------- Post added at 20:21 ---------- Previous post was at 20:20 ----------
Can we flash SuperSU with this ?
AFAIK We have MIPS ,not arm ,also supersu wasn't ported to Android Wear (If that matters).
Click to expand...
Click to collapse
The serial problem is solved
mauronofrio said:
The serial problem is solved
Click to expand...
Click to collapse
I know ,but I just want to ask
Thank you for the builds! May I ask why there is a "small" and "full" versions? Both img's have the same size.
Regards
lfom said:
Thank you for the builds! May I ask why there is a "small" and "full" versions? Both img's have the same size.
Regards
Click to expand...
Click to collapse
Full is a full size without corners, the small have corners so it smaller than full img
mauronofrio said:
Full is a full size without corners, the small have corners so it smaller than full img
Click to expand...
Click to collapse
It's related to the screen resolution then, right? OK, I got it.
Once again, thanks a lot for the build. I have installed it on Pace and it seemed to work fine. A few remarks:
1. The identifiers for "device" and "model" are different from the normal firmware, so it's not possible to install stock firmware or OTAs, probably it can be fixed easily:
Code:
getprop("ro.product.device") == "watch"
getprop("ro.build.huami.model") == "A1602"
2. The touchscreen seems to need some calibration, sometimes the button identified as touched isn't the correct one, it's even harder with smaller options.
3. It seems that sometimes the screen doesn't update: after I tap a button, I need to swipe the screen so it is refreshed and you can see the new content. It's kinda dangerous because you can tap somewhere you don't want to when doing this... No idea how this can be improved, tho.
4. After a installing, I could do a backup, etc, but the next reboot the recovery was replaced by the stock one (it shows "No command" after boot). Do you know how to prevent this? Never mind, I found the cause.
Keep it up! Regards.
lfom said:
It's related to the screen resolution then, right? OK, I got it.
Once again, thanks a lot for the build. I have installed it on Pace and it seemed to work fine. A few remarks:
1. The identifiers for "device" and "model" are different from the normal firmware, so it's not possible to install stock firmware or OTAs, probably it can be fixed easily:
Code:
getprop("ro.product.device") == "watch"
getprop("ro.build.huami.model") == "A1602"
2. The touchscreen seems to need some calibration, sometimes the button identified as touched isn't the correct one, it's even harder with smaller options.
3. It seems that sometimes the screen doesn't update: after I tap a button, I need to swipe the screen so it is refreshed and you can see the new content. It's kinda dangerous because you can tap somewhere you don't want to when doing this... No idea how this can be improved, tho.
4. After a installing, I could do a backup, etc, but the next reboot the recovery was replaced by the stock one (it shows "No command" after boot). Do you know how to prevent this? Never mind, I found the cause.
Keep it up! Regards.
Click to expand...
Click to collapse
New twrps pubblished, also verge supported now.
Now you can flash stock roms, for the touch i can't do nothing, is a kernel problem.
mauronofrio said:
New twrps pubblished, also verge supported now.
Now you can flash stock roms, for the touch i can't do nothing, is a kernel problem.
Click to expand...
Click to collapse
I am sorry, but it didn't change anything (I am still getting the same IDs with 3.2.3-5 installed on Pace) . Anyway, Huami updates also check for the installed version signature, so unless there is a way to read device's build.prop during boot, I think it won't work.
Another question: I could not get "show_progress(fraction, time)" to work correctly in any flashing script, it always goes to 100%. It works fine when backuping/restoring tho. Known bug?
Thanks again. Regards.
lfom said:
I am sorry, but it didn't change anything (I am still getting the same IDs with 3.2.3-5 installed on Pace) . Anyway, Huami updates also check for the installed version signature, so unless there is a way to read device's build.prop during boot, I think it won't work.
Another question: I could not get "show_progress(fraction, time)" to work correctly in any flashing script, it always goes to 100%. It works fine when backuping/restoring tho. Known bug?
Thanks again. Regards.
Click to expand...
Click to collapse
Can you share a stock rom zip?
mauronofrio said:
Can you share a stock rom zip?
Click to expand...
Click to collapse
They can be downloaded from Huami's Pan Disk online:
http://bbs.huami.com/thread-4934-1-1.html
I have attached an update.zip script too (delta OTA update).
lfom said:
They can be downloaded from Huami's Pan Disk online:
http://bbs.huami.com/thread-4934-1-1.html
Click to expand...
Click to collapse
I'm unable to download roms from baidu, please reupload one stock rom on another cloud service and give me the link
Good afternoon everyone.
I got interested in putting a custom rom on my Galaxy Note 8 I have laying around (Current Daily driver has been upgraded to a Note 20 Ultra so I have no hurry to fix this issue.)
I followed the steps from one of the forum guides and installed TWRP, the first thing I noticed was that my Note 8 had 2 System directories while this is supossed to be a A only model. (Which struck me as odd.) After installing a android 11 Rom (A Only) I was stuck on the boot screen not loading any further. I found this logical as Android 11 is not really supported as of yet on this model.
I then decided to grab Havoc OS seeing as that was a stable version that should run properly i've seen people on Youtube install it on their S8's without a hitch. After installing this the way the guide told me I got stuck in a boot loop. (Also used an A only ROM) My final attempt will be downloading an A/B ROM and see if that works (Which i genuinly doubt.) but will update this post when that's finished.
On the post I also have added a screenshot of what I see when trying to install an Image. My question to you guys is, does this phone have a A/B configuration after all or am I doing something wrong?
Edit: AB was also not the solution.
After rummaging around a bit more with the phone I found out that i was using an extremely out of date version of the Pie Vendor. I looked at download by Version number instead of by date. Reinstalled Havoc, installed pie vendor.
Now the phone reboots into downloading mode. It's been this way around 10 minutes now will post an update in about an hour or so of leaving it in that state.
QuirkyTechGuy said:
After rummaging around a bit more with the phone I found out that i was using an extremely out of date version of the Pie Vendor. I looked at download by Version number instead of by date. Reinstalled Havoc, installed pie vendor.
Now the phone reboots into downloading mode. It's been this way around 10 minutes now will post an update in about an hour or so of leaving it in that state.
Click to expand...
Click to collapse
Odd. Truly. It could be due to the first install of GSI version. Here's what I suggest.
I hope u have a back up of your old rom, if so, flash it back. If not, check your twrp version. Update it to latest. Flash a non gsi rom. Boot the phone. If it boots and you have it running, then flash a gsi rom .
maxed4901 said:
Odd. Truly. It could be due to the first install of GSI version. Here's what I suggest.
I hope u have a back up of your old rom, if so, flash it back. If not, check your twrp version. Update it to latest. Flash a non gsi rom. Boot the phone. If it boots and you have it running, then flash a gsi rom .
Click to expand...
Click to collapse
I sadly forgot to make a back up of the rom which in hindsight is stupid of me. I did check and have the latest TWRP version, and managed to get LineAge OS 17.1 working without it being Treblized .
Should i now go on with the procedure of trying to flash a GSI rom with the Treble Convert?
QuirkyTechGuy said:
I sadly forgot to make a back up of the rom which in hindsight is stupid of me. I did check and have the latest TWRP version, and managed to get LineAge OS 17.1 working without it being Treblized .
Should i now go on with the procedure of trying to flash a GSI rom with the Treble Convert?
Click to expand...
Click to collapse
Let's take a back up first and then try. Which tutorial are u following.
Install Android 11 (R) On Any Treble Device ( Detailed Guide)
This way you can install Android 11 On any device without the need of waiting for your manufacturer to push the latest update.
xtremedroid.com
And try Google or aosp gsi from here https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
Here's @corsicanu thread for instructions.
But it's for android 9? M not sure though
[AOSP][Treble][G95*F/FD] hadesTreble [03.09.2019]
Disclaimer I am 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...
forum.xda-developers.com
I have an old Fire and I want to install a custom ROM on it but I need some help figuring out how to proceed. I've been reading a lot of threads around here (primarily this one, this one, this one, and this one) and I've successfully unlocked the bootloader but I'm hesitant to start flashing things without knowing what's current and correct. I've seen a lot of different approaches and different files and commands in various threads and some of those commands don't work anymore (e.g. any fastboot command with -i flag) and some of the links to files are dead (both goo.im and teamw.in seem to be defunct and pretty much all the links here are broken) and just the sheer volume of information here is a bit overwhelming. I also read somewhere that TWRP v. 2.7 would be better for this device than 2.8 but now it's in version 3.5 I think and I'm not sure if I should still try to find 2.7 or not?
So, I guess the main thing I'm trying to figure out is what versions of FFF and TWRP I should be using and where I can get them. It would also be great if someone could point me to the guide or guides that will be most current and relevant for my device.
Thanks!
Kindle Fire HDX (3rd Gen, Thor)
Fire OS 4.5.5.3
Windows 10 Pro 21H1
I would install latest TWRP:-
[RECOVERY][UNLOCKED BL] TWRP 3.5.0_9-1
/* * I am 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 the products you find here...
forum.xda-developers.com
Best 2 custom Roms in my opinion are LineageOS 14.1 & Divest OS, both are based on Android 7.1.2
Divest OS i think has bit better battery life and performance but you wont be able to use some apps that require google. LineageOS can have root if you want and install google playstore.
I use DivestOS and installed Aurora Services to go with Aurora Store (great alternative to google playstore, i think this is way better). And i have F-droid. Slight glitch with DivestOS is you cant switch it off via power button and tapping on power off, you have to press down on power button for about 20 seconds so its not an issue really.
The creator of LineageOS 14.1 is apparantly going to continue with it with some updates. DivestOS has monthly updates.
Thanks! I went with LineageOS.
Hello everybody! They brought me the OnePlus Nord 2 with the problem that it can't flash. According to the man, he first set himself Arrow 12.1 via TWRP and everything worked fine. Then he decided to install PixelOS via fastboot. First, he cleared the memory via Fastboot and after that, when he started flashing, his phone restarted at 40 percent. And now the smartphone is trying to start a system that does not exist and the computer does not see the phone in fastboot mode. What to do? Is there any way to restore the device?
Yes. Use mtkclient to flash the original firmware.
[STOCK][FULL-ROM] OxygenOS_11.3_A.20 EU DN2103 | Unbrick guide
/* * Your warranty is... still valid! * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. * Please do some research yourself before asking or use anything on this...
forum.xda-developers.com
Downgrade from oos 12 beta 2 or stable to oos 11: The MTK client tutorial
All of us knows that we upgraded to OxygenOS 12 stable or beta but OnePlus didn't given roll back package so who are stucked on OOS 12 can now downgrade using this process. This is downgrade process by using relive dvd based MTK client Tutorial...
forum.xda-developers.com
maliczech said:
Yes. Use mtkclient to flash the original firmware.
[STOCK][FULL-ROM] OxygenOS_11.3_A.20 EU DN2103 | Unbrick guide
/* * Your warranty is... still valid! * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. * Please do some research yourself before asking or use anything on this...
forum.xda-developers.com
Downgrade from oos 12 beta 2 or stable to oos 11: The MTK client tutorial
All of us knows that we upgraded to OxygenOS 12 stable or beta but OnePlus didn't given roll back package so who are stucked on OOS 12 can now downgrade using this process. This is downgrade process by using relive dvd based MTK client Tutorial...
forum.xda-developers.com
Click to expand...
Click to collapse
And what instructions to use? 1 or 2?
So if I were to install a rom on an hdx,
Would the correct procedure be sideload the rom zip wiping dalvik/cache? Then sideloading gapps zip or whatever for apks?
Or would pushing the rom and gapps to sdcard and installing the 2 zips with twrp be alright?
Am I missing anything important? I read people talk about safestrap but oblivious as to what it is or if it matters.
I tried searching for a guide on the correct way to flash custom rom but didnt find anything.
Is there only 1 rom option these years for hdx? I only found 2 lineage options.
I read of AEX, aospextended, etc. but couldnt find them or links 404d. since those files are absent now I guess they are discontinued or deleted by their creator?
Any advice is appreciated.
AstralA said:
So if I were to install a rom on an hdx,
Would the correct procedure be sideload the rom zip wiping dalvik/cache? Then sideloading gapps zip or whatever for apks?
Or would pushing the rom and gapps to sdcard and installing the 2 zips with twrp be alright?
Am I missing anything important? I read people talk about safestrap but oblivious as to what it is or if it matters.
I tried searching for a guide on the correct way to flash custom rom but didnt find anything.
Is there only 1 rom option these years for hdx? I only found 2 lineage options.
I read of AEX, aospextended, etc. but couldnt find them or links 404d. since those files are absent now I guess they are discontinued or deleted by their creator?
Any advice is appreciated.
Click to expand...
Click to collapse
Hi, flashing ROMs usually will come device specific instructions. It can depend on the generation of your device. I searched flash custom ROM on HDX and got this. I hope it helps or at least gets the ball rolling for you.
flash custom rom on hdx - Google Search
[ROM][apollo, thor] Lineage-14.1 [17 MAR 2022]
Disclaimer /* * I am 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 the products you find...
forum.xda-developers.com
Does seem like theres directions but the directions seem to presume I know enough before hand. Lol
I dont know how to wipe data, it doesnt say much specifically.
Guess I can just go for it and see what happens.
But id rather know exactly so I know my ignorance wont end in a brick or faulty rom install.
I did read ggow say dirty flash was alright. But im not even sure what constitutes dirty flash.
Total green noob here. The only thing im not a noob at is bricking phones by modifying root files. Lol
Thanks for the quick response jonpjingleheimler. Awesome name btw.
Well if I ever figure out the proper way to do this I will write a guide with every possible specific I can muster.
AstralA said:
[ROM][apollo, thor] Lineage-14.1 [17 MAR 2022]
Disclaimer /* * I am 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 the products you find...
forum.xda-developers.com
Does seem like theres directions but the directions seem to presume I know enough before hand. Lol
I dont know how to wipe data, it doesnt say much specifically.
Guess I can just go for it and see what happens.
But id rather know exactly so I know my ignorance wont end in a brick or faulty rom install.
I did read ggow say dirty flash was alright. But im not even sure what constitutes dirty flash.
Total green noob here. The only thing im not a noob at is bricking phones by modifying root files. Lol
Thanks for the quick response jonpjingleheimler. Awesome name btw.
Well if I ever figure out the proper way to do this I will write a guide with every possible specific I can muster.
Click to expand...
Click to collapse
a lot of us started out not knowing a dirty flash from a clean flash. I think if you are serious about installing a custom ROM it would wise to locate the stock ROM for your device first. Most if not all stock roms for amazon tablets are available for download by Amazon. This way you can at least get back to stock usually without much hassle. YouTube is also a great resource for device specific instructions and sometimes a bit easier to follow. just keep that stock rom on hand. If you get into a bootloop or other crappy situation it's usually possible to get into the stock recovery perform a factory reset or use ADB sideload to flash the stock ROM.
Good to know. Thanks for the advice. I will definitely do that.
I look forward to getting to use apps that are from more recent years that actually work alongside website development.
Its rough finding functional apps when relegated to android kitkat.