Related
For 4 weeks ive been looking at KK and playing with source... 4.4 images Build (ota zip fails)
4.4 images are building im coming here for developers help on getting this rom working
i will continually post here my sources (this is an awesome forum) and my progress as i go on.. been at this for over 4 weeks developing my first rom...
this post will get more colorful and easier to read over time:
Below is a quote from my google+ post on Xoom Community (join it.. its a great place)
STATUS UPDATE:
Xoom Wifi - LIFESTREAM ROM by LOGMD
Build 17 - Failed BUT we have:
-boot.img
-system.img
-kernel (supposedly)
I have managed to extract the system.img into a flashable Zip... but i KNOW the permissions are F*%#ked
I installed boot.img manually using fastboot but its left me in bootloops (not actually getting to the boot animation, looping on the moto logo)
i flashed the 4.2.2 EOS4 BigPart image because its compatible with the new partition layout and it doesnt bootloop... but it also doesnt get to bootanimation either...
BUT it did respond to ADB devices and came up as unauthorized device so obviously when i ADB SHELL it says device unauthorized...
I THINK that i need to build the boot.img with the BigPart patch but im not sure even if the kernel is just not working properly. if ive built it properly or whatever...
IF ANYONE knows any xoom developers or you are a xoom developer and know how to build kernels on a version of android thats not supported officially or if you think you could help me out then im all ears
Click to expand...
Click to collapse
BIG THANKS to the BigPart & 4.3/4.4 dev thread (will add links later) would have been stuck at one of the many roadblocks if it wasnt for these people!
we are getting closer to getting a rom working i can feel it! lets make it happen! loving how live the threads are in this forum for the xoom!
PROGRESS
I will update here the overall progress towards a working rom WHEN i get time as work can get very busy. I will not be selfish and steal peoples ideas if they are the ones who invented it then i will give credit where it is due, and it is possible that this rom could never be built or someone beats me to it. I may end up collaborating with someone with more experience on thier rom but ill do my best to get an edition of my own working.. IF all fails for now with 4.4 i will spend time on a 4.2 rom/kernel
DISCLAIMER
I (LOGMD) 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 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. Your warranty will be void if you tamper with any part of your device / software. In saying that Enjoy a respectful development environment, expect no ETA's and help me where necessary
REPARTITION
SYSTEM.IMG
BOOT.IMG (kernel, ramdisk etc)
THREADS OF LIFE (words stolen from Shadows Fall Album)
This is where you and I should use as a starting point for homework using the communities are a great way to learn the newest up to date developments! I do not read fiction books but I sure as hell read technology!
GOOGLE+
+LOGMD | +XDADevelopers | +XoomOwners
XDA-Forums
BLOG
OTHER (follow me)
Twitter | Facebook
I wish you luck. As your skill and luck is our luck.
Sent from my Xoom using XDA Premium HD app
subbed! anticipating great things!
way to be!! Super excited. Need guinea pigs? I'll help
sbeaber4 said:
way to be!! Super excited. Need guinea pigs? I'll help
Click to expand...
Click to collapse
ill start uploading some system img zips soon. see if i can take anything more out of android that is not essential to makeing it work i.e. NO BROWSER NO PLAY STORE everything gone, i was told by another developer they have managed to get the rom small enough for fastboot (~251MB) so ill try the same so it will be easier to flash!
I stupidly did not reserve posts so heres one more
boot.img
For the kernel, why don't ask to ElementalX ?
If we have a system.img but it's to large to flash through fastboot,
thinking out loud but could we get it connected via adb in recovery and do the dd if=/location/of/system/img of=/dev/block/mmcblkpXXX
would that work?
---------- Post added at 11:52 AM ---------- Previous post was at 11:48 AM ----------
Another thought on trying to get the img into a flashable zip, not sure if you've heard of dsixda kitchen! http://forum.xda-developers.com/showthread.php?t=633246
I've used it before in regard to the Xperia T and it's compatible with many devices and can turn system imgs into zips I believe
If using bigPart Kernel than you can not use fastboot as fastboot does not know the new partition layout.
Incredible news!!
Love to see KitKat on Motorola Xoom!
Sent from my Xoom using Tapatalk 4
Have you tried using Motorola's mfastboot.exe? I've had to use that instead of the regular fastboot to flash large system images to my Moto X, I'm curious if it would work for the repartitioned Xoom. Apparently it breaks the image down into two parts to get around size limitations with the regular fastboot.
I uploaded it here if you'd like to test it out
TWRP
So we partitioned the Tab with 1000 Mo for system, i'm not sure it's necessary, i read it's possible to reduce the size of the ROM under 256 Mo
I have a old Samsung Galaxy Ace and for this old tool on Jenkins the 4.4 cooper is compiled but not flashable because no recovery adapted to flash it.
I visit a lot of site like Mclaw studio and see for each ROM kitkat it's a special TWRP dedicate specialy to kitkat ROM.
So do you thing we need another TWRP or the TWRP big part is ok?
pots22 said:
So we partitioned the Tab with 1000 Mo for system, i'm not sure it's necessary, i read it's possible to reduce the size of the ROM under 256 Mo
I have a old Samsung Galaxy Ace and for this old tool on Jenkins the 4.4 cooper is compiled but not flashable because no recovery adapted to flash it.
I visit a lot of site like Mclaw studio and see for each ROM kitkat it's a special TWRP dedicate specialy to kitkat ROM.
So do you thing we need another TWRP or the TWRP big part is ok?
Click to expand...
Click to collapse
I managed to shrink to 209 MB which flashes =] it may not have anything but core android but thats all we care about right now i dont care about FC... next is kernel follow this link will be more active about kernel updates. im gonna post some nvidia drivers i just found
Elemental-X seems to have updated to beta with support for big partition.
4.4
hawkstorm said:
Elemental-X seems to have updated to beta with support for big partition.
Click to expand...
Click to collapse
Exactly, http://www.androidfilehost.com/?fid=23252070760974877
Now we have a bigpart partitioning, a bigpart Kernel
So what needed for start a 4.4 kitkat test build?
pots22 said:
Exactly, http://www.androidfilehost.com/?fid=23252070760974877
Now we have a bigpart partitioning, a bigpart Kernel
So what needed for start a 4.4 kitkat test build?
Click to expand...
Click to collapse
Technically we didn't even need the big part
Sent from my SAMSUNG-SGH-T989 using Tapatalk
Cameron581 said:
Technically we didn't even need the big part
Sent from my SAMSUNG-SGH-T989 using Tapatalk
Click to expand...
Click to collapse
Well, the dev said that he needed to remove a few things to get it to flash. Maybe now he can reinsert whatever he removed and check whether it can flash.
hawkstorm said:
Well, the dev said that he needed to remove a few things to get it to flash. Maybe now he can reinsert whatever he removed and check whether it can flash.
Click to expand...
Click to collapse
That makes no sense he removed apps and was on a parted kernel
Sent from my SAMSUNG-SGH-T989 using Tapatalk
Experimental X was just updated to support Bigpart. It is not the update that Logmd is looking for to support KK 4.4. The new kernel needs a lot more upgrading involving drivers for the Tegra Chip.
They are probably trying to see if they can get KK 4.4 working without bigpart first. And if successful it can blossom from there with ROM developers taking advantage of BigPart to create more custimized ROMS.
4.4
Cyanogenmod launch from yesterday and today a lot of ROM CM11 4.4.2
http://download.cyanogenmod.org/
All ROM don't exceed 200 Mo, so i'm really not sure about the necessity of Bigpart.
1)ROOT-
NO root for 4.3 directly for locked bootloaders
For unlocked here you go http://forum.xda-developers.com/showthread.php?t=2583805
Downgrade to 4.2 to get root
http://forum.xda-developers.com/showthread.php?t=2494134 for 6503
http://forum.xda-developers.com/showthread.php?t=2335306 for 6502
Flashtool
latest flashtool download
http://www.flashtool.net/download.php
Flash .ftf using flashtool
http://forum.xda-developers.com/showthread.php?t=2054486
root 4.2.2:
doomlords rooting toolkit
http://forum.xda-developers.com/showthread.php?t=2327472
install cwm
http://forum.xda-developers.com/showthread.php?t=2251093
to get root for 4.3 and dual recovery for 4.3 upgrade by nuts method
http://forum.xda-developers.com/showthread.php?t=2567266
2) Bootloader-
Backup ta partition so that you dont loose bravia engine
http://forum.xda-developers.com/showthread.php?p=41763438
Unlock bootloader
-get your code from here
http://unlockbootloader.sonymobile.com/
Unlock bootloader using flashtool
http://forum.xda-developers.com/showthread.php?t=2447319
3)Rom index:
Stock:
-4.2 stock link given above
-4.3 stock
http://forum.xda-developers.com/showthread.php?t=2640151 for 6503
-4.3 stock
http://forum.xda-developers.com/showthread.php?t=2655100 for 6502
Stock based
Existenz rom(4.3)-
http://forum.xda-developers.com/showthread.php?t=2352237
sky dragon rom (4.2)-
http://forum.xda-developers.com/showthread.php?t=2407411
Lg g2 rom(4.2)
http://forum.xda-developers.com/showthread.php?t=2550147
Custom roms-
Kitkat:
Cm11-
http://forum.xda-developers.com/showthread.php?t=2540671
Codename lungo-
http://forum.xda-developers.com/showthread.php?t=2650316
Omni rom-
http://omni.cmxlog.com/4.4/odin/
Avatar rom-
http://forum.xda-developers.com/showthread.php?t=2243238
Liquidsmooth rom-
http://forum.xda-developers.com/showthread.php?t=2656019
Jellybean:
Illusion rom-
http://forum.xda-developers.com/showthread.php?t=2381901
Cm10.x
http://forum.xda-developers.com/showthread.php?t=2436626
4)Kernels:
stock kernel based for 4.3 .569
http://forum.xda-developers.com/showthread.php?t=2599619
doom kernel stock based 4.3
http://forum.xda-developers.com/showthread.php?t=2594479
advanced stock kernel 4.4 .101:
http://forum.xda-developers.com/showthread.php?t=2641695
78 kernel-
http://forum.xda-developers.com/showthread.php?t=2624339
All spark kernel-
http://forum.xda-developers.com/showthread.php?t=2596496
5)Scripts
Pure performances x for any rom (actually any device)
http://forum.xda-developers.com/showthread.php?t=2630170
6)Gapps:
paranoid 0 day gapps art compatible
http://forum.xda-developers.com/showthread.php?t=2397942
Note:
all instructions are provided in repective links
installing a rom of different region wont make much difference
i m not responsible for any damage to your devices i m just sharing the links
Credits:
to all the ops in the respective thread
1. Good job
2. Deserves to be sticky in general
3. Unlocked bootloader with 4.3 can be rooted (downgrading is pain in arse)
4. We know that 6502/3 stock/rom works on each other still it is not advisable to do
For example consider me (globaly recognized noob) flashed it wrongly i know its ally mistake but they will blame you cause you advised them
5. We have one thread like this so ask mods to merge that and this thread to avoid confusion
6. You missed all spark's AOSP kernel, 78kernel.
7. You missed hell lot of things
8. Nuts recovery is good one
9. The cwm you linked is for unlockedbootoader only
10. There are two cm from fxp and cm both have same source but different release pattern so provide link to threads
11. Add work in progress in title so you can sort everything out
No offense just helping you to sort things out if you need my help throw me a PM.
Add a faq section below my post or you can use my post so everything is in line.
You tried to do something helpful so kudos
Always there to help
Globally recognized N00B
thread updated
Needs layout.
DoubleYouPee said:
Needs layout.
Click to expand...
Click to collapse
what sort of layout ?
bhavstech said:
what sort of layout ?
Click to expand...
Click to collapse
Paragraphs..punctuation..etc..?
This thread is work in progress so friends please dont post till it is complete
Regards
Globally recognized N00B
alkesh95 said:
This thread is work in progress so friends please dont post till it is complete
Regards
Globally recognized N00B
Click to expand...
Click to collapse
+1
it would be a good help if people would provide more material to add instead of complaing :fingers-crossed
ask the mods to make it a sticky thread
Advanced stock kernel 4.3 FW .101
http://forum.xda-developers.com/showthread.php?t=2641695
I'm aiming to build kernel 3.4.0 (1.52.1540.5) from the Source Code Released by www.htcdev.com last year
I Need your help, Can't do it all alone. So, please if anyone have some time,
do spare it here sharing the knowledge about building it from Source Code, once we get the New Kernel we can Easily Compile the New ROM for Example Android 4.4.2 for the Device.
Hoping to have some Assistance
Thanks
V_Singh
Hello my friend, please send me the CWM backup
Please I'm Begging
tanaydin123 said:
Hello my friend, please send me the CWM backup
Please I'm Begging
Click to expand...
Click to collapse
You Want the ROM backup or Just the CWM?
Unfortunately, you don't have backup ROM nice and fast ROM you are using please, I want to backup my ROM please don't Flash ROM HTC 616 quick and useful mod please ...I'm so boring
Sent from my HTC 616 Dual Sim using XDA Free mobile app
Hey bro, as i know you cannot compile rom without device and vendor tree but if you have a device and vendor tree you can compile rom and for kitkat rom required 3.4.67 kernel if i remember true also i am working compile 3.4.67 kernel for d616 and trying the find or create a new device and vendor tree with my friend but i don give 100% guarantee if i make a kitkat rom for d616 i will share at xda-developers and i will build cyanogenmod for d616 but i dont give any 100% guarantee because i am student and i have a exams but i try @v_singh and i have a d616
I too was thinking to do that , but was busy for last few months . Maybe we can build up a team first (Development is faster that way) .
Forget about it i will not make kitkat for we device because yesterday i received a call from htc and says to me "kitkat for desire 616 will get but now in development proccess" and if kitkat release for we device i will port cm11 for we devices but with a little bugs (video recording, second... sim etc.)
ritikchanna said:
I too was thinking to do that , but was busy for last few months . Maybe we can build up a team first (Development is faster that way) .
Click to expand...
Click to collapse
Nice !dea @ritikchanna , but Sometimes I really Don't have time, and also its gone complicated Since I Upgraded my PC to WIN10, things aren't working on it as expected
Ozanerd said:
Forget about it i will not make kitkat for we device because yesterday i received a call from htc and says to me "kitkat for desire 616 will get but now in development proccess" and if kitkat release for we device i will port cm11 for we devices but with a little bugs (video recording, second... sim etc.)
Click to expand...
Click to collapse
Well, that's their Job Bro but, I'm not really sure they will spare time on our Device, and I don't have money to Buy new phone, so i'm just trying to do things on my own with your help, I'm still not sure I can manage it, but its always good to give a shot!
Ozanerd said:
Hey bro, as i know you cannot compile rom without device and vendor tree but if you have a device and vendor tree you can compile rom and for kitkat rom required 3.4.67 kernel if i remember true also i am working compile 3.4.67 kernel for d616 and trying the find or create a new device and vendor tree with my friend but i don give 100% guarantee if i make a kitkat rom for d616 i will share at xda-developers and i will build cyanogenmod for d616 but i dont give any 100% guarantee because i am student and i have a exams but i try @v_singh and i have a d616
Click to expand...
Click to collapse
Thanks, for the Information bro, its good to know what n what I can do with the available resources, and of now, I have Downloaded the SOURCE CODE from www.htcdev.com for HTC 616D and I also have the Device with me, now can you tell me, what n what I need next?
tanaydin123 said:
Unfortunately, you don't have backup ROM nice and fast ROM you are using please, I want to backup my ROM please don't Flash ROM HTC 616 quick and useful mod please ...I'm so boring
Click to expand...
Click to collapse
Hey Pal! don't get stressed, and also pardon me for getting so late, if I upload my whole rom backup, it would be long and idk if my slow internet can handle that much big file to Upload, well well! just make your ROM DE-ODEXED and download this and follow the README inside :good:
Sent from my HTC 616 Dual Sim using XDA Free mobile app[/QUOTE]
You need the vendor, device and kernel source for desire 616 but kernel must be 3.4.67 if i know true for kitkat @v_singh
Update: Success on compiling
I got Success On Compiling the New Kernel (zImage) from the Source Code (Special thanks to @op3n_sourc3), and Building the BOOT.IMG,
but the Problem is When I'm flashing it, the Device doesn't boots up,
a little help would be Appreciated, Anyone?
v_singh said:
I got Success On Compiling the New Kernel (zImage) from the Source Code (Special thanks to @op3n_sourc3), and Building the BOOT.IMG,
but the Problem is When I'm flashing it, the Device doesn't boots up,
a little help would be Appreciated, Anyone?
Click to expand...
Click to collapse
Please share the download links or PM me I will look into it
v_singh said:
I got Success On Compiling the New Kernel (zImage) from the Source Code (Special thanks to @op3n_sourc3), and Building the BOOT.IMG,
but the Problem is When I'm flashing it, the Device doesn't boots up,
a little help would be Appreciated, Anyone?
Click to expand...
Click to collapse
That's a great news. Does it show the htc logo or stuck on black screen? Could you capture the log? If yes, capture the Log with ALV(Advanced Logcat Viewer) and upload it here.
We are too lucky to get Devs like you guys
@arun483 please check the attached file :good:
@abhatia1435 actually I have messed up with my boot logo, so I can't see if anything going on underneath, but when I power on, it shows the broken boot n then reboots again (same like bootloop) but will try to capture the log.
And also I have a Question "do we need newer Rom to boot newer version of Kernel?"
Caution: for the other users , this file is only for Development Purpose, Do Not Flash it until you Know what you are doing. BE SMART, STAY SAFE.
Any Update @arun483 ?
v_singh said:
We are too lucky to get Devs like you guys
@arun483 please check the attached file :good:
@abhatia1435 actually I have messed up with my boot logo, so I can't see if anything going on underneath, but when I power on, it shows the broken boot n then reboots again (same like bootloop) but will try to capture the log.
And also I have a Question "do we need newer Rom to boot newer version of Kernel?"
Caution: for the other users , this file is only for Development Purpose, Do Not Flash it until you Know what you are doing. BE SMART, STAY SAFE.
Click to expand...
Click to collapse
Sorry I just got busy in some family functions I will look into it and let you know what we can do.
---------- Post added at 06:47 PM ---------- Previous post was at 06:39 PM ----------
@v_singh so first things first you messed up with boot and stuck in boot loop? NP you can easily find stock boot.img flash it using spflashtool
Need boot logo? I can make one and link you through pm
"do we need newer Rom to boot newer version of Kernel?" No it's actually visa versa, you need newer kernel to boot newer rom. We can port upto Android MarshMallow based on 3.4.67 kitkat kernel but not on jelly bean kernel. I can port some mediamods based on jellybean if you want
arun483 said:
Sorry I just got busy in some family functions I will look into it and let you know what we can do.
---------- Post added at 06:47 PM ---------- Previous post was at 06:39 PM ----------
@v_singh so first things first you messed up with boot and stuck in boot loop? NP you can easily find stock boot.img flash it using spflashtool
Need boot logo? I can make one and link you through pm
"do we need newer Rom to boot newer version of Kernel?" No it's actually visa versa, you need newer kernel to boot newer rom. We can port upto Android MarshMallow based on 3.4.67 kitkat kernel but not on jelly bean kernel. I can port some mediamods based on jellybean if you want
Click to expand...
Click to collapse
the boot logo is another Cause that i have solved already
but the Kernel is not Still Booting, Did you guys found anything ?
v_singh said:
the boot logo is another Cause that i have solved already
but the Kernel is not Still Booting, Did you guys found anything ?
Click to expand...
Click to collapse
I don't have device in my hands right jow so I am waiting till device arrives so that I can start work on kernel
hello v singh
Hello v singh have u got the reason of why the kernel is not booting
Good
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..?
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
What's new in 3.2.2-0:
</> CHANGELOG : ? </>
Code:
Code:
* adb backup fixes
* OTA style update zips will now install automatically without prompting for decrypt
* minor tweaks to handling date/time on Qualcomm devices
* updates to some language translations
</> DOWNLOAD ? </>
https://twrp.me
$ TIP $
You can update it from previous TWRP recovery if you already have it installed, else install it as fresh by using adb or Official TWRP Installer app from google play store or similar
To flash with Fastboot/Adb:
Code:
Code:
make sure OEM-Unlocking is ON
$ adb reboot bootloader
$ fastboot flash recovery twrp-3.2.2-0-woods.img
To contribute:
TWRP Code Review
TeamWin
XDAevDB Information
Moto E4 ROMs, Kernels, Recoveries, & Other Development
Contributors
iykeDROID™ {dumbDevpr*}
Source Code: https://github.com/TeamWin
Version Information
Status: Stable
Created: 2018-07-12
Last Updated: 2018-07-13
Great news. Now I'm waiting for stable and fully working Oreo ROM and start flashing.
ka4o_pi4a said:
Great news. Now I'm waiting for stable and fully working Oreo ROM and start flashing.
Click to expand...
Click to collapse
from the looks of things on my side, i don't think that will happen in anytime too soon.
let's just hope for a God sent dev to take over the Moto E4(woods) development .
if any bug with the TWRP, create/open an issue regarding such bug on GitHub :
https://github.com/omnirom/android_bootable_recovery
( make sure to see how other issues were created and follow such trend )
thanks
I am getting a wrong architecture error (error 64 in twrp) when trying to flash ARM gapps.
EstebanxZ said:
I am getting a wrong architecture error (error 64 in twrp) when trying to flash ARM gapps.
Click to expand...
Click to collapse
wait for next update or use this at your own risk
https://t.me/motoe4woods/12179
Same here. Wrong architecture. Even the backup was corrupted and I wasn't able to flash back my stock ROM. This is my last Motorola device.
ka4o_pi4a said:
Same here. Wrong architecture. Even the backup was corrupted and I wasn't able to flash back my stock ROM. This is my last Motorola device.
Click to expand...
Click to collapse
i used it to install Both XOSP & Gapps Pico today.
Few days ago I was spent my day on trying to flash some ROM, but didn't manage to flash any (Pico,nano, micro, etc) gapps... All finished with the same error 64. Then I install last beta of twrp and successfuly install gapps, but can't boot into system (boot into recovery every time).
ka4o_pi4a said:
Few days ago I was spent my day on trying to flash some ROM, but didn't manage to flash any (Pico,nano, micro, etc) gapps... All finished with the same error 64. Then I install last beta of twrp and successfuly install gapps, but can't boot into system (boot into recovery every time).
Click to expand...
Click to collapse
please your issues on that specific ROM's thread.
As far as i know, the TWRP recovery works fine even before the unofficial beta... woods has come to it's best so far.
thanks.
Already do that. Also try with two or three different ROMs and get the same error. Doesn't matter, I'LL wait for some more stable version of twrp and some ROM.
Tks
Thanks man!
Laruzzo said:
Hi, this TWRP version to Moto E4 woods is not good.
It does not install GAPPS, and do not install SUPER SU.
With GAPPS the error is about 64 bits version. And with supersu it says that "Bad recovery no Unzip."
I tried with a unnoficial version and worked everything.
Please update in TWRP site to a new version with bug fix.
Look a this thread with the version that worked with Moto E4 woods.
https://forum.xda-developers.com/mo...rp-3-1-1-r1-port-xt1760-t3772249/post76177524
Click to expand...
Click to collapse
Dude,
learn how to read a full post with instructions & proper way of reporting an issue anywhere you find yourself.
Know you device SoC, Architecture, etc ... don't just talk any how.
also, commits has not been merged
see on gerrit.twrp.me :=> https://gerrit.twrp.me/#/c/android_device_motorola_woods/+/63/
Finally, always check to see if no one has report similar issue and been solved before you start writing sh*t into the air
https://postimages.org/
https://forum.xda-developers.com/showpost.php?p=77250466&postcount=6
NOTE : MOTO E4 SERIES IS ARM(32bit) Architecture Device, stop trying to flash/install ARM64 Gapps as you stop being dumb.
OK
Ok, I´m sorry you are the developer and I should thanks for your great work. May you please share here the alternative file that works with gapps? Because I cannot access telegram at the momment. Thank you very much and sorry again if my words was not good. I respect and admire your work.
Laruzzo said:
Ok, I´m sorry you are the developer and I should thanks for your great work. May you please share here the alternative file that works with gapps? Because I cannot access telegram at the momment. Thank you very much and sorry again if my words was not good. I respect and admire your work.
Click to expand...
Click to collapse
Download ⍖ ?
TWRP-323.0-Unofficial-woods.img
iykeDROID™ said:
TWRP is an open source, community project.
..
..iykeDROID™[/URL] {dumbDevpr*}
Source Code: https://github.com/TeamWin
[/SIZE][...his other way cause I doubt about official ¿‽
Click to expand...
Click to collapse
Abish4 said:
Format Data Partition with F2FS format is not available which is usually available with every Moto Device Kernel
Click to expand...
Click to collapse
please deal with the kernel source here : https://github.com/MotorolaMobilityLLC/kernel-mtk/tree/nougat-7.1.1-release-woods
Abish4 said:
Can you help with this other way cause I doubt about official ¿‽
Click to expand...
Click to collapse
due to negligence, you couldn't check the source code here : https://github.com/TeamWin/android_device_motorola_woods
also check the twrp site : https://twrp.me/motorola/motorolamotoe4.html
I cannot flash gapps arm 7.1.x
Hi. I have one MotoE4 XT1763 Mediatek MT6735 with unlocked bootload.
would you recommend flashing the
twrp-3.2.3-0-woods.img 15.1M
Or the
TWRP-323.0-Unofficial-woods.img 15.5M
for the Lenovo Moto E4(XT1762)
?
Thank you peoples. TWRP unofficial working fine
Hey peoples. Accidentally i wiped my system. I have a backup in pc. I dont have sd card right now. How can i put the backup wich is in pc back to TWRP backup folder in order to restore ?