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 recovery
* 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.
* I am not your help desk.
Prerequisites
1. Unlocked bootloader
2. Patience (even i was unable to unlock for 4-6 hours and also fastboot was hanging while flashing twrp for testing, changing USB port worked. My first build was stuck in splash screen for infinite time, it happens keep patience)
Bugs
1. Maybe under your bed !
2. If you have found a bug/issue, please consider posting it to my GitHub Issues.
Instructions
1. Boot into fastboot mode by adb reboot bootloader or key combo, doesn't matter.
2. Download the twrp image following the link in the download section and transfer it to the adb folder (or add adb to PATH for universal access).
3. Open the cmd/terminal and change directory into the adb folder (or where you downloaded twrp image).
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, linux users may need to change connection type to transfer files from charging only.
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 select recovery mode by pressing vol down/up and boot into twrp mode.
Note: Right after flashing twrp & booting into it, format data and flash Disable_Dm-Verity_ForceEncrypt for persistence twrp. Otherwise as soon as you boot to system, it's gonna replaced by stock recovery. Another option is to flash PBRP zip, if Disable_Dm-Verity_ForceEncrypt didn't work, PBRP by default have decryption patch.
Downloads
Android File Host: https://www.androidfilehost.com/?w=files&flid=298214
Official TWRP Page: https://build.twrp.me/twrp-3.3.1-0-RMX1901.img
Screenshots
Check screenshots section
XDA:DevDB Information
TWRP For Realme X, Kernel for the Realme X
Contributors
chankruze
Source Code: https://github.com/N00bTree/android_device_realme_RMX1901
Kernel Special Features:
Version Information
Status: Stable
Created 2019-09-20
Last Updated 2019-09-22
Thank you ?
Orange fox now TWRP its good to see some officials coming...now just waiting for pixel experience or Some aosp builds...
Can used on RMX1903?
Hi OP,
What's the difference between your one and this one?
https://forum.xda-developers.com/re...very-unofficial-twrp-realme-x-stable-t3959556
And please do not label unofficial TWRP as official, "going to be supported officially soon". I have changed title for you.
jerryhou85 said:
Hi OP,
What's the difference between your one and this one?
https://forum.xda-developers.com/re...very-unofficial-twrp-realme-x-stable-t3959556
And please do not label unofficial TWRP as official, "going to be supported officially soon". I have changed title for you.
Click to expand...
Click to collapse
Oh, you are the moderator who asked for answer. I missed it untill oswald's PM. Very busy in real life and also for this device kernel. Also to be noted suffering from severe back pain.
Let me ask you one question: What is the difference between TWRP images, let's say you compiled and i compiled both from omni android-9.0. The thing is this post you are seeing could be here 33 days ago but i waited for the device so that i don't brick others device. There will be some changes later, when kernel is ready. for now it's working.
With due respect and humble submission, i want a small declaration from you, if you are going to update the new build links, add a FAQ section i won't have to write official or unofficial in future. You are going to update it right ? At the moment the gerrit patch got merged, i expect you to change title from unofficial to official.
I can't say same thing to each and every mod ... (i am stupid i could have added you as cc/bcc for the PM i answered).
A few last words, "Respect Should Be Earned, Not Given".
Regards,
chandan
chankruze said:
Oh, you are the moderator who asked for answer. I missed it untill oswald's PM. Very busy in real life and also for this device kernel. Also to be noted suffering from severe back pain.
Let me ask you one question: What is the difference between TWRP images, let's say you compiled and i compiled both from omni android-9.0. The thing is this post you are seeing could be here 33 days ago but i waited for the device so that i don't brick others device. There will be some changes later, when kernel is ready. for now it's working.
With due respect and humble submission, i want a small declaration from you, if you are going to update the new build links, add a FAQ section i won't have to write official or unofficial in future. You are going to update it right ? At the moment the gerrit patch got merged, i expect you to change title from unofficial to official.
I can't say same thing to each and every mod ... (i am stupid i could have added you as cc/bcc for the PM i answered).
A few last words, "Respect Should Be Earned, Not Given".
Regards,
chandan
Click to expand...
Click to collapse
Bhai dhyan diani karma kari chala.
Keep up the good work?
Thanks for TWRP. Any Idea when would custom ROMs start rolling in? I recently read that XDA sent out devices to devs for development.
chankruze said:
Oh, you are the moderator who asked for answer. I missed it untill oswald's PM. Very busy in real life and also for this device kernel. Also to be noted suffering from severe back pain.
Let me ask you one question: What is the difference between TWRP images, let's say you compiled and i compiled both from omni android-9.0. The thing is this post you are seeing could be here 33 days ago but i waited for the device so that i don't brick others device. There will be some changes later, when kernel is ready. for now it's working.
With due respect and humble submission, i want a small declaration from you, if you are going to update the new build links, add a FAQ section i won't have to write official or unofficial in future. You are going to update it right ? At the moment the gerrit patch got merged, i expect you to change title from unofficial to official.
I can't say same thing to each and every mod ... (i am stupid i could have added you as cc/bcc for the PM i answered).
A few last words, "Respect Should Be Earned, Not Given".
Regards,
chandan
Click to expand...
Click to collapse
Hi, fully understand your point. When this one is merged, you could change the title from unofficial to official by yourself. :highfive:
Thanks for your hard work and development.
Hi this should also work in OPPO K3 I suppose. Everything is same except camera. Anyone tried?
HI Chandan,
Good work on the TWRP for X, Is there a possibilty for XT as well for the TWRP
Regards,
Diaz M
Related
This thread is for CM7 RC releases for HD2. These are unofficial RC.
I will be maintaining CM stuff for HD2 all unofficially. They are compiled from source and not ported/kanged from other devices.
CyanogenMod is a free, community built distribution of Android 2.3 (Gingerbread) which greatly extends the capabilities of your phone.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* 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! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Please do NOT post bug reports on any issue tracker for these builds. Report bugs here code.google.com/p/cm7leo
All source code is available at the CyanogenMod Github! If you'd like to to contribute to CyanogenMod, checkout Gerrit instance.
These builds REQUIRE ClockworkMod Recovery 3.x. If you use ClockworkMod Recovery 2.x to flash, it will not boot.
Additionally, ClockworkMod Recovery 3.x CAN NOT BE USED to flash CM6. You will have to downgrade ClockworkMod Recovery to 2.x if you want to switch back to CM6.
INSTRUCTIONS:
- First time flashing CM 7 to your HD2 (or coming from another ROM)?
1. Unlock/root your device and install MAGLDR
2. Flash ClockworkMod Recovery 3.x
3. Do a Nandroid backup!
3. WIPE
4. Install the ROM
5. Optionally install the Google Addon
- Upgrading from earlier CM7?
1. Do a Nandroid Backup!
2. Install the ROM (your Google apps will be backed up automatically)
Download link
http://www.megaupload.com/?d=QATMMXF6
For CLK
http://www.megaupload.com/?d=C7QK5I92
Gapps -
http://goo-inside.me/gapps/gapps-gb-20110120-signed.zip
needed only after first flash, after concurrent flashes gapps will persist
Link to ClockworkMod-3 - http://www.multiupload.com/41E9UMRO45
Thx RaiderX303
You can flash any Clockwork but 150mb version is recommended
Should be MAGDLR/CLK compatible
Follow me on Twitter for Updates - charansingh
Nice..thanks!
Will try this in a jiffy!
sweet. cant wait to flash it!
thx charnsingh
edit:
any news on getting this official?
Here is the link to the cLK patch, that I did earlier
Forum Link: http://forum.xda-developers.com/showpost.php?p=12414534&postcount=1634
Scan or click the image to download:
with the following in the update zip
* boot.img
* PPP files/fixed
* 02recov to mount cache/recovery correctly to get ROM Manager working
After flashing the ROM, you need to flash the file in the attached file in the above post, to get it to work with cLK. This is with with charans kernel, and not any other
Can anyone else confirm this doesn't work out the box for CLK. I had to install tytung_r8 to get this to boot.
ubuntu, have a look @ post 4
this doesn't work out of the box with cLK, nope.
seadersn said:
ubuntu, have a look @ post 4
this doesn't work out of the box with cLK, nope.
Click to expand...
Click to collapse
Without wanting to look too much of a numpty, the second part of post 4 is an edit
When I asked it wasn't there.
nice work Charansingh. Thanks for all your work- amazing you have been able to do all this without a hd2 yourself.
I look forward to trying it out tomorrow- too late here now
I just dont get the dont post any bugs part... in the other theme I felt urged to do so. I am sure there is a reason for this, - should we stick to the older thread for bug reports??? Anyway, as usual thank you for the great hard work, trying it now
He's saying not to post bugs in issue trackers because we're not official CM7, this forum is not an issue tracker.
Thanks a lot Charnsingh!
deckoff said:
I just dont get the dont post any bugs part... in the other theme I felt urged to do so. I am sure there is a reason for this, - should we stick to the older thread for bug reports??? Anyway, as usual thank you for the great hard work, trying it now
Click to expand...
Click to collapse
post bugs here code.google.com/p/cm7leo
Reserved for future use.
CPU Settings in the Performance menu not working, WiFi still errors. Apart from that, it seems to work pretty well, though I suspect the ambient light sensor isn't working too well either, it seems overly bright.
arif-ali said:
This i the same as the other post, as the MD5SUM cane out to be the same
Here is the link to the cLK patch, that I did earlier
Forum Link: http://forum.xda-developers.com/showpost.php?p=12414534&postcount=1634
Scan or click the image to download:
with the following in the update zip
* boot.img
* PPP files/fixed
* 02recov to mount cache/recovery correctly to get ROM Manager working
After flashing the ROM, you need to flash the file in the attached file in the above post, to get it to work with cLK. This is with with charans kernel, and not any other
Click to expand...
Click to collapse
Hmmm...so is it a new release, or the same one from yest. since MD5 is same
Mafioso said:
Hmmm...so is it a new release, or the same one from yest. since MD5 is same
Click to expand...
Click to collapse
I would presume, the other thread is a dev thread for testing purposes, and this is a release thread
No, thats a release thread too but thats for daily builds n this for RC and Major releases for those who dont want to flash everyday
100% load
I have a 100% cpu usage with rc2 due to the system_server process.
Am I the only one, because nobody else mentions this??
The GPS doesn't appear to work
Sent from my HTC HD2 using XDA App
RC4 is out, Also Available on ROM Manager
Everything Except GPS libs are compiled from source
This google profile is outdated http://code.google.com/p/cm7leo/
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.1.x (Lollipop), which is designed to increase performance and reliability over stock Android for your device.
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.
*
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Instructions
First time flashing CyanogenMod 12.1 on your device, or coming from another ROM?
Download the zip(s).
Install a compatible Recovery
Perform a NANDroid backup of your current ROM (Optional)
Wipe data & cache partitions of your device (required when coming from stock!).
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Broken Features / Known Issues
audio lag in some games
dialer shows an ugly screen on incoming calls
drm support is broken (e.g. play movies)
package manager sometimes installs x86 libs when it needs arm libs (causes some apps to not work at all)
selinux enforcing mode
sim 2 cannot be disabled
sim 2 audio quality issues when also on a call on sim 1 (unconfirmed)
USB UMS (Mass Storage) - Killed off for now, MTP works just fine
Other Issues?
Before posting on this thread, make sure of a few things:
You've utilized the search function of the forums. Nothing irritates me more than lazy people who do not search for an answer before asking or ask the same question over and over again.
If you are the only one having a problem. Boot into recovery, wipe data/factory reset, reflash the rom/gapps and nothing else. Boot up and see if the problem persists.
Make sure your post is relevant to this thread. "I'm having problems rooting/unlocking" is NOT relevant here.
LOGS LOGS LOGS!!!! Use this: SysLog by Tortel
As the Zenfone2 has multiple models from multiple countries please include the following information in your report:
model #
CPU Speed / RAM Size
device state when errors occur (BT/wifi/nfc on ? On a call ? sitting idle on shelf ? )
method to reproduce if you've found something consistent
Download Links
CyanogenMod for Z00A/ ze551ml: ROM @ download.crpalmer.org
CyanogenMod for Z008/ ze550ml: ROM @ download.crpalmer.org
Recovery Links
Z00A
CM Recovery CM Recovery @ download.codefi.re/jrior001
theSSJ's TWRP: XDA thread
Official TWRP: TWRP.ME
Unofficial F2FS TWRP: jrior001's unofficial twrp
Z008
CM Recovery CM Recovery @ download.codefi.re/jrior001
Unofficial F2FS TWRP: jrior001's unofficial twrp
theSSJ's TWRP: XDA thread
Official TWRP: TWRP.ME - PENDING ACCEPTANCE
Google apps addon:
Recommend GAPPS for now as the updated x86 gapps.
Flashable Modem updates:
Currently only supported in jrior001's unofficial TWRP
May or may not work in others
** see this post for more info **
Intel stores some modem firmware in the OTA's in a file labeled "ifwi.zip"
These are flashable zips to receive the updated firmware while staying on custom ROMS
**THIS IS A ONE WAY PROCEDURE, JUST LIKE THE OTA's THERE IS NO KNOWN WAY
TO FLASH BACK TO EARLIER MODEM FIRMWARE, PROCEED WITH CAUTION**
IF you still wish to proceed, current flashable ifwi zips are available HERE for Z00A AND Z008
XDA:DevDB Information
Unofficial CyanogenMod 12.1 Nightly Bulids (Z00A/Z008), ROM for the Asus ZenFone 2
Contributors
crpalmer, jrior001, hharte
Source Code: https://github.com/CM-zenfone2
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
ROM Firmware Required: 2.19.40.22 stock base
Version Information
Status: Beta
Created 2015-07-24
Last Updated 2015-10-02
Reserved
Known issues are know in the first post so that all the maintainers can updated it and keep it current.
FAQ
Does Official TWRP work?
* Only if they have the device called Z00A. As of the initial release the official TWRP did not but will likely soon be named properly.
* If it doesn't work,arecovery from the OP.
Can I use a custom kernel with these builds?
* No, there are no custom kernels build based off of our source tree, using our defconfig and which contain the proper ramdisk.
*Also, doing so makes any feedback useless to us because the kernel and the ROM are a complete package and changing part of that means you may have broken something beyond our control.
Will this be an Official ROM?
* When all the show stopping bugs are fixed and all the upstream commits are merged, yes.
* Until then, no because CyanogenMod has very high standards for accepting new devices.
What about the Z008 aka ze550ml?
* Right now none of the developers who are working on the development own one and therefore we can't support it.
* One of the developers working on this said he was purchasing one (even though he already owns the ze551ml). When he gets it and has time to work on it we may see it. Without us owning the device though, there will never be support for it.
Do I need to unlock the bootloader?
* Yes.
thanx Chris, a zillion people have been waiting for your hard work and quality as always , thankyou chris,,steve
Finally !!!!!!! Damm Finally !!! Thanks a lot man !! been waiting for this so long !! Finally some development !! Thank You
Finally.....cm 12.1 has landed on zenfone 2
knitesh813 said:
Finally.....cm 12.1 has landed on zenfone 2
Click to expand...
Click to collapse
This TWRP recovery work??
http://forum.xda-developers.com/zenfone2/development/alpha-tethered-twrp-asus-zenfone-2-t3123532
Thank You for your work!
john_petrucci said:
This TWRP recovery work??
http://forum.xda-developers.com/zenfone2/development/alpha-tethered-twrp-asus-zenfone-2-t3123532
Click to expand...
Click to collapse
Cannot confirm but there should be an official twrp update later today that will for sure.
Sent from my ASUS_Z00A using XDA Free mobile app
Just as info and to avoid questions: My TWRP should be working here as ro.product.device is set to Z00A
OMG....OMG......can't wait to flast it....!
Please someone give me a review.
How about memory leak?
How about battery?
Thankyou very much
Ready to Flash... Thxxx Guyss. was waiting for soo long
---------- Post added at 05:39 PM ---------- Previous post was at 05:38 PM ----------
allasca said:
Please someone give me a review.
How about memory leak?
How about battery?
Thankyou very much
Click to expand...
Click to collapse
Give it a try...
Cheers for the hardwork.
Accept donations?
allasca said:
Please someone give me a review.
How about memory leak?
How about battery?
Thankyou very much
Click to expand...
Click to collapse
I am using the 2gb/16gb ZE551ML and I have around 600-1gbmb free at any given time (OS is only doing around 800mb-1gb so I'd imagine the 4gb should have 3gb+ free). Now battery life, loving it, around 1% every 5-7 minutes with the screen on
crpalmer said:
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.1.x (Lollipop), which is designed to increase performance and reliability over stock Android for your device.
Click to expand...
Click to collapse
Whoop, there it is! :thumbup:
jrior001 said:
Cannot confirm but there should be an official twrp update later today that will for sure.
Sent from my ASUS_Z00A using XDA Free mobile app
Click to expand...
Click to collapse
Whoop, there it is!
FINALLY, thank you both so much for all your hard work, including @TheSSJ!
Sent from the Ace's MB865 using Tapatalk
Please provide a google drive link please...
Download is becoming unsuccessful
Does the second sim card work? From what I understand this is not supported by Cyanogen.
All set up using twrp on z00a..had to factory reset and then a reboot to get sim recognised..46,000 in antutu on this build...
Yahoooooo!!!!
Thank you very much devs...bloody amazing
working
ok i can confirm that @TheSSJ twrp flashed CM successfully[made a clean wipe other than microsd]
mtp is buggy for me sadly,cant transfer more than 1 file
camera totally black..maybe i doing something wrong.. my bad,have to wait for few seconds,,camera working
as said by op,first boot not showing sims,,have to restart
wifi,bluetooth,network,message,settings are working....others didnt check
and thanks for everyone who made the hardwork for this CM12.1
using ZE551ML 2gb version
maback said:
Does the second sim card work? From what I understand this is not supported by Cyanogen.
Click to expand...
Click to collapse
I have two sim cards and both work for telephony. You can even call yourself to and from your phone!
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.
*
*/
This is an unofficial TWRP 3.x build for the Huawei Honor 3C (h30u10/H30-U10)
This project is abandoned! I'll reopen the thread if I have any progress in the future... If you want anything from me you can contact me in my email address, in Telegram (@iamnotstanley) or in private message.
Only use this binary with your own responsibility, and please read the "known issues" list.
Working:
Everything, except the things in the "known issues" list.
TWRP functional checklist, but in this list not everything applies for our device
Known issues:
flash/restore image (boot&recovery) (installing with a zip [if you're using codelover's fixed update-binary] and backup working correctly) **need help **
Download:
Latest and older versions: See the DevDB Downloads page or click here. (Mirror)
Install:
You can install this recovery in 4 way:
Using an another version of TWRP: install the downloaded zip
Using an another version of TWRP: extract the zip and flash the image
Using SP Flash Tools: extract the zip and flash the image
Using Flashify or other flashing app: extract the zip and flash the image
Revert easily to codelover's TWRP:
Download from here the UPDATE-TWRP-2.8.6.0_H30-U10.zip or the UPDATE-TWRP-2.8.6.0_V2_H30-U10_EU.zip and install it inside the TWRP, after that if you reboot to recovery, you will see the old version.
Changelog:
TWRP changelog: here
Device changelog:
3.1.1-0:
Updated to the latest version.
We still have the the "image flash" problem!
3.1.0-0:
First release for Huawei Honor 3C (h30u10)
Built with omnirom android-5.1 tree
Prebuilt kernel: EU B306 (3.4.67)
Screenshots: See the DevDB Screenshots page or click here.
Credits:
iamnotstanley
codelover
carliv for his bootimg module
MSF-Jarvis for his initial device tree
TeamWin team
omnirom team
XDA:DevDB Information
TWRP for Huawei Honor 3C, Device Specific App for the Honor 3C
Contributors
iamnotstanley, codelover, carliv, MSF-Jarvis, TeamWin team & omnirom team
Source Code: https://github.com/iamnotstanley/android_device_huawei_h30u10/tree/android-5.1
Version Information
Status: Abandoned
Current Beta Version: 3.1.1-0
Beta Release Date: 2017-05-13
Created 2017-04-01
Last Updated 2018-01-29
Reserved
Nice woork bro
why did not you patch it bro for img files flashing??
Can you Send Me sources
hassanjavaid8181 said:
Nice woork bro
why did not you patch it bro for img files flashing??
Can you Send Me sources
Click to expand...
Click to collapse
Thanks.
I'm working on the image flashing fix, but I'm building from source code and nearly scratch, and now I finding the cause of the problem. I'll fix it as soon as I can.
My source code (TWRP device tree) is in the post: https://github.com/iamnotstanley/android_device_huawei_h30u10
iamnotstanley said:
Thanks.
I'm working on the image flashing fix, but I'm building from source code and nearly scratch, and now I finding the cause of the problem. I'll fix it as soon as I can.
My source code (TWRP device tree) is in the post: https://github.com/iamnotstanley/android_device_huawei_h30u10
Click to expand...
Click to collapse
really appreciate your efforts:good:
good luck
Bro can we flash magisk by this version.
mnumaher said:
Bro can we flash magisk by this version.
Click to expand...
Click to collapse
If Magisk doesn't work in the older or other recoveries, it won't work in this recovery.
I think, because Magisk modify the boot image and MT6582 phones has a boot image with a special MTK header, and I think Magisk currently doesn't support this format. (Like the "new" systemless SuperSU.)
Thanks bro bringing twrp 3x to our device!!
I'm hoping you keep maintain this project as well till reach bugless
iamnotstanley said:
If Magisk doesn't work in the older or other recoveries, it won't work in this recovery.
I think, because Magisk modify the boot image and MT6582 phones has a boot image with a special MTK header, and I think Magisk currently doesn't support this format. (Like the "new" systemless SuperSU.)
Click to expand...
Click to collapse
Thanks.
Is touch working correctly in this version?
mnumaher said:
Thanks.
Is touch working correctly in this version?
Click to expand...
Click to collapse
For me, yes. This version has B306 kernel. If your phone's touch is working on B306, it'll work, but it's not, you will need to change kernel. You can try this first, but if isn't working, tell me which kernel has working touch for your phone and I'll make a version for that.
Kernels: https://forum.xda-developers.com/showpost.php?p=60721740&postcount=861
Rayquaza said:
Thanks bro bringing twrp 3x to our device!!
I'm hoping you keep maintain this project as well till reach bugless
Click to expand...
Click to collapse
Thanks for your support. I'll maintain this project while I have this phone. I'm trying to fix the img flash issue, but I think I need help with it.
iamnotstanley said:
For me, yes. This version has B306 kernel. If your phone's touch is working on B306, it'll work, but it's not, you will need to change kernel. You can try this first, but if isn't working, tell me which kernel has working touch for your phone and I'll make a version for that.
Kernels: https://forum.xda-developers.com/showpost.php?p=60721740&postcount=861
Thanks for your support. I'll maintain this project while I have this phone. I'm trying to fix the img flash issue, but I think I need help with it.
Click to expand...
Click to collapse
Ty bro it's working absolutely fine.
When we will be able to flash img.
mnumaher said:
Ty bro it's working absolutely fine.
When we will be able to flash img.
Click to expand...
Click to collapse
I'm working on it, but I think I need help to fix that. I hope maybe somebody can help me.
working fine cheers!
iamnotstanley said:
I'm working on it, but I think I need help to fix that. I hope maybe somebody can help me.
Click to expand...
Click to collapse
hi and great work, thanks for that
codelover maybe have a patch for that, past time he say i forget it, but can help you to know how solve that
Hi @iamnotstanley, to answer your question:
If i recall correctly i did explained about the problem in my thread earlier - the problem lies on 3C KK kernels. (MTK variant only)
H30-U10 stock KK kernels do not permit writing to the boot partition (/dev/bootimg) directly, the partition is mounted as read only.
Interestingly, there are some ported recoveries out there that doesn't work, and user doesn't even know about it. (eg: ROM appeared to be flashed successfuly but failed to boot because boot.img didn't get through, missing assert() to stop)
If you find a working H30-U10 recovery that can write to boot for 3C, it's likely using JB kernel or KK kernel from other 6582 compatible KK kernel, not sure if someone has compiled a fully working 3C kernel.
With JB kernel, you will be missing SELinux & some other features, while KK kernel from other device is dangerous IMHO, unless you are 100% sure it's compatible, sometimes i wonder whether those permanently bricked 3C with partition error were using these 'patched' recoveries...
My TWRP 2.8.6.0 has been customized to deal with this, i wrote a few C custom functions for twrp, it works like this;
1) read the partition table while flashing, loop through until you find the details for target partition that you need to write.
2) calculate the size and offset to write (you will need to convert the hex to int, then some math again to get the bs, skip, etc value for dd)
3) use 'dd' to write directly to mmcblock0, instead of C fwrite to the specific built-in partition mount point, eg: /dev/bootimg
Wish i could help more, unfortunately i don't have 3C data with me anymore (hdd crashed), and my work is killing me.
Good luck with that!
codelover said:
Hi @iamnotstanley, to answer your question:
...
Click to expand...
Click to collapse
Hi!
Thanks for your answer, I really appreciate your help.
So the problem is mainly in the kernel. I don't think I can fix this, but I'll try after my exams.
TWRP updated to 3.1.1-0
Hello guys!
I updated the TWRP to 3.1.1-0 yesterday. Unfortunately it still have the image flash issue. If you're interested you can download from the DevDB Downloads page or the Github mirror.
Huawei Honor 3C H30-U10
Hello guys
I m new on this site and want to know about my huawei honor 3c h30-u10
I want to root and install TWRP custom recovery in my cell without PC. .
I am using EMUI 3 and android ver 4.4.2 whereas build number is B310
Please any one give me detail with images.
Thanx in advance
SHBhatti said:
Hello guys
I m new on this site and want to know about my huawei honor 3c h30-u10
I want to root and install TWRP custom recovery in my cell without PC. .
I am using EMUI 3 and android ver 4.4.2 whereas build number is B310
Please any one give me detail with images.
Thanx in advance
Click to expand...
Click to collapse
Try rooting with root applications such as Baidu root and etc.
TamaziAce said:
Try rooting with root applications such as Baidu root and etc.
Click to expand...
Click to collapse
I was Try to root with king root, king root said that your device is rooted successfully but root checker said no root???? what should i do now..?
Lucky-KernelForExynos-Variant's
Code:
#include
/*
* Your warranty is now void.
*
* 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 Kernel
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
* If you dont like this Kernel, Stay away from this thread!
*/
What to say... I come from Samsung Galaxy Nexus and its development until the beginning of September 2016...
I did a one-year break from kernel programming, and I came back here for you. To bring you a good kernel for this device that still has a lot to give.
My work is on kernel source, I add, delete, modifing code, but with a criterion, that everything, must make sense
I consider the kernel as beta, although it is very stable, I will update the kernel when needed, with the necessary security patches, and a few extra grays
Android8.0
This kernel Boot on 8.0(lineage-buid) but I think also on AOSPExtended rom 8.0 it will Boot..
Android7.1
EDIT: Don't Boot.. thank's to @spookcity138 for news
Good download at all, and let me know your opinion
XDA:DevDB Information
[KERNEL] Lucky [O], Kernel for the Samsung Galaxy S5 Mini
Contributors
Fenix46, hennymcc, spookcity138
Source Code: https://github.com/Fenix46/android_kernel_samsung_kminilte
Kernel Special Features:
Version Information
Status: Beta
Beta Release Date: 2017-11-11
Created 2017-11-11
Last Updated 2017-11-12
Reserved
Del.
Good evening,
at first I had the patched twrp from the LineageOS 15.0 thread installed and flashing your kernel it produced a fault 11 error. Then I flashed the official twrp and the installation on AOSPExtended 8.0 worked just fine.
Could you please elaborate a little bit more what you did to the kernel sources or if there is something special included? Nevertheless: Thank you for contributing!
Best regards
Hey,
Great to have another developer working on the S5 Mini! I can confirm that the kernel does not boot on 7.x ROMS (Slim7 at least,but I imagine all) I expected this though as my kernel build doesn't boot on Android 8. I can also confirm issues flashing with the Oreo compatible TWRP version. I just recently flashed a test build of TWRP by Ayke and got this same error 11,so I extracted the boot.img and flashed that. I also tried to flash my kernel after yours to get my system back up and also got an error flashing in TWRP,so something has changed there apparently.
tester02 said:
Good evening,
at first I had the patched twrp from the LineageOS 15.0 thread installed and flashing your kernel it produced a fault 11 error. Then I flashed the official twrp and the installation on AOSPExtended 8.0 worked just fine.
Could you please elaborate a little bit more what you did to the kernel sources or if there is something special included? Nevertheless: Thank you for contributing!
Best regards
Click to expand...
Click to collapse
Yep, with official twpr, flash without problem, this error 11 is related to the twpr for Oreo... however, I've add some commit on kernel source, and my work is this, add commit, and update the kernel
spookcity138 said:
Hey,
Great to have another developer working on the S5 Mini! I can confirm that the kernel does not boot on 7.x ROMS (Slim7 at least,but I imagine all) I expected this though as my kernel build doesn't boot on Android 8. I can also confirm issues flashing with the Oreo compatible TWRP version. I just recently flashed a test build of TWRP by Ayke and got this same error 11,so I extracted the boot.img and flashed that. I also tried to flash my kernel after yours to get my system back up and also got an error flashing in TWRP,so something has changed there apparently.
Click to expand...
Click to collapse
@spookcity138 thank's for welcome However Thannk's again for feed on 7.x rom... this error is related at updater-script.. on Oreo the first line "assert" is not present, so cause this.. but with official twpr flash go fine, I think to change the updater-script if cause another problem
I would't call this development or a kernel which offers something over the stock LOS kernel (that's the reason why no changes are mentioned in the OP - because there none). I only see 1 rename commit. So overall it doesn't change anything which deserves to call it 'your' kernel. This entire repo are upstream commits only. If you only provide such 'development' I highly suggest to work directly on the official kernel and submit pull request instead which then would help everyone and not only people which using this kernel here.
CHEF-KOCH said:
I would't call this development or a kernel which offers something over the stock LOS kernel (that's the reason why no changes are mentioned in the OP - because there none). I only see 1 rename commit. So overall it doesn't change anything which deserves to call it 'your' kernel. This entire repo are upstream commits only. If you only provide such 'development' I highly suggest to work directly on the official kernel and submit pull request instead which then would help everyone and not only people which using this kernel here.
Click to expand...
Click to collapse
what changes did you want to find on the kernel? did you see the commit series I added? Do you think the changes are all in the name of who works on the kernel? for those who work on ROMs as @hennymcc or @spookcity138 or other's they can very well take my base and insert it to build the ROM..
I expect some changes which improving the kernel e.g. in performance otherwise I stick with the LOS kernel because you 'commit series' I found so far are years old now and pointless in Oreo. I'm not sure what's the point to create an thread when there are seriously no changes, I not deny that you might work on it but that should be mentioned as 'work in process' or something here but since there is no changelog, downloadable release or explanation on this kernel I think I have the right to ask what's going on here.
And just because someone else might contribute to your project doesn't mean this is relevant, as said I checked it and there was no change. I haven't chedckd all branches but master and the asop-8.0 branch was not really what I expected to see when someone announce a kernel. As said earlier I think it would be better to contribute to LOS directly instead of making another kernel.
Please explain or show why someone should use your kernel or in other words - what's wrong with the LOS one?! Thanks.
CHEF-KOCH said:
I expect some changes which improving the kernel e.g. in performance otherwise I stick with the LOS kernel because you 'commit series' I found so far are years old now and pointless in Oreo. I'm not sure what's the point to create an thread when there are seriously no changes, I not deny that you might work on it but that should be mentioned as 'work in process' or something here but since there is no changelog, downloadable release or explanation on this kernel I think I have the right to ask what's going on here.
And just because someone else might contribute to your project doesn't mean this is relevant, as said I checked it and there was no change. I haven't chedckd all branches but master and the asop-8.0 branch was not really what I expected to see when someone announce a kernel. As said earlier I think it would be better to contribute to LOS directly instead of making another kernel.
Please explain or show why someone should use your kernel or in other words - what's wrong with the LOS one?! Thanks.
Click to expand...
Click to collapse
What you saw, that you think is old, are needed on Nougat as well, because interfaces better the kernel, with the modules, because our kernel don't have support on kernel Device Three.. and it's just the beginning of this, because my main job will be to reformulate the theard for a rom. Nothing to take away from the kernel LOS, and I did not want to create useless controversies. if you do not want to use this kernel, it does not change anything. however if you look good on the download section, find the zip package to download.
Twrp 3.1.1 official, SM-G800F, AospExtended Oreo. Error 11 by flashing.
Where is the Download Link?
Open xda in Browser, under downloads
(look at the middle of my Screenshot)
MikeT. said:
Open xda in Browser, under downloads
(look at the middle of my Screenshot)
Click to expand...
Click to collapse
Thanks
. . .
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. Hard & a lot.
*
*/
This is a very early development version, only flash if you know what you're doing! I guarantee nothing.
Due to some unknown bug It could happen that you won't be able to enter twrp UI after installing. Then you need adb access to wipe the data partition.
This should allow a first look on Android 12 on the Z1 compact.
Download
SourceForge
Click to expand...
Click to collapse
Source Code: https://github.com/115ek/manifest
Changelog:
30.12.2021
initial release
reserved
I am amazed that you were able to do this. Thank you so much, and to the AICP team as well. I installed it and like to be able to see the new things even though the device is very old.
-FancyUsername- said:
I installed it and like to be able to see the new things
Click to expand...
Click to collapse
Did you find an appropriate GAPPS version?
tramp20 said:
Did you find an appropriate GAPPS version?
Click to expand...
Click to collapse
You could try https://github.com/BiTGApps/BiTGApps-Release/releases/tag/v1.7
However, I'm not sure if it still fits. Android gets bigger and bigger. No one thought about that 8 years back when amami was released.
Thank you.
This package has only 84 MB.
I will try LOS 19 with BiTGApps the next days.
No one has courage?
I tried the new ROM :-(
As usual: I made a backup of the system and a backup of the internal SDCard!
1. in TWRP (twrp-3.4.0-1-amami) factory reset and installing ROM + open_gapps-arm-12.0-pico-20211218-UNOFFICIAL_MOD.zip (at the same time)
2. reboot to LOS 19
3. configuring most things
noticed a not working bluetooth and missing NFC
missing "reboot to recovery" in extended power menu
4. shutting down and booted to recovery TWRP to make a first backup
TWRP showed only the welcome picture without menu and repeated this endless.
So I could not do a restore :-(
Then I flashed TWRP again with fastboot (even with a fastboot erase recovery) but this did not help.
After some tries I decided to flash the stock ROM with EMMA (all will be deleted incl. internal SDCard).
Flashed TWRP again and restored my LOS 18.1 backup and copied the int. SDCard back with MTP.
So after ~ 4 hours my Z1c was running again.
The next day I tried all again with the same disappointing result.
@tramp20 Sorry for the trouble.
If you get stuck at the TWRP bootscreen, connect an USB cable. Then
Code:
adb shell rm /data/system/storage.xml
adb reboot recovery
There's also a fix for this already. I just didn't pick it yet.
ref: https://github.com/chil360/android_...mmit/8016a9332ec85f05d539a892b2617517f9b3dbc1
Thank you.
I will wait for a new fixed ROM
Up front: Thanks a lot for still supporting this quite old but lovely phone.
As I am no pro I cannot say for sure, that I did not make any mistakes, but I can see the same issues regarding bluetooth and NFC as @tramp20. Also I can not find a camera in the system and therefore the flashlight is not available too.
I did not know, that there should be a button to reboot to recovery, but there is none on my amami right now with your ROM.
I am using the recommended BiTGApps.
I first flashed the ROM, then rebooted to recovery from twrp.
then i installed the BiTGApps and rebooted to recovery again. It just seemed right to me.
I rebooted to system and set everything up, then came across what i've described.
As I now know that there might be a fix for at least some of the issues I will wait for a possible new version of your ROM and try again.
Regards
spechaa
Hi, can anyone help how do I can fix lag issue on this rom?
Hello, i will be very glad to see new update ! If this ROM will rock stable like LOS 17.1/18.1 on my 6-7 years old Sony Xperia Z1c, it will be crazy awesome!
jurkoman said:
Hello, i will be very glad to see new update !
Click to expand...
Click to collapse
it looks not good :-(
[ROM][Unofficial][11.0][signed][OTA] Lineage OS 18.1 for Xperia Z1 compact
This thread aims at providing LineageOS 18.1 builds for the Sony Xperia Z1 compact with current security patches. You can consider this thread as a successor of our LineageOS 17.1 thread, where you may also find some useful information. This is...
forum.xda-developers.com
tramp20 said:
it looks not good :-(
[ROM][Unofficial][11.0][signed][OTA] Lineage OS 18.1 for Xperia Z1 compact
This thread aims at providing LineageOS 18.1 builds for the Sony Xperia Z1 compact with current security patches. You can consider this thread as a successor of our LineageOS 17.1 thread, where you may also find some useful information. This is...
forum.xda-developers.com
Click to expand...
Click to collapse
Hello, which one can you suggest more ? 18.1 or 17.1 ?
jurkoman said:
18.1 or 17.1 ?
Click to expand...
Click to collapse
Go for 18.1 it is very solid and receives updates. 17.1 is no longer maintained
has someone be able to get of that los recovery? its not detecting my phone via adb or fastboot to install twrp
ERIKW!§ said:
has someone be able to get of that los recovery? its not detecting my phone via adb or fastboot to install twrp
Click to expand...
Click to collapse
"los recovery" and "fastboot"? You know how to reboot your phone to the bootloader, and use fastboot, right?
You may want to study the installation instructions in the OP of this old thread - it's still valid afaik. Also the link to the relevant TWRP version and troubleshooting section in the same post could be of help
Good luck