Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Testers needed! #5

Open
XePeleato opened this issue Mar 19, 2016 · 24 comments
Open

Testers needed! #5

XePeleato opened this issue Mar 19, 2016 · 24 comments

Comments

@XePeleato
Copy link
Owner

Alright, I have finally built TWRP 3.0 so I need some people to test it.

Just drop a comment if you'd like to provide feedback!

recovery

@FelipeBR28
Copy link

I can't test it yet (because it's being repaired) but when it's finished, I'd like to test it.

@olrak2
Copy link
Contributor

olrak2 commented Mar 19, 2016

Very good news, how did you solve the black screen?

I'm very excited to test it :)

@XePeleato
Copy link
Owner Author

Well, I had to edit a graphics file.

http://error404software.com/android/recovery.zip

Unzip and run "fastboot flash recovery recovery.img"

@olrak2
Copy link
Contributor

olrak2 commented Mar 19, 2016

Installation without problem :)

All settings are working for the moment.

Will test other settings in the couple of days.

Very good job. Keep up the good work

@Mast3rPK
Copy link

Hii, TWRP is perfect 💃

TWRP 3 Test

@FelipeBR28
Copy link

And, @XePeleato , can it be flashed by Flashify? It's easier 😅

@XePeleato
Copy link
Owner Author

@Tuentista At the moment, it can't, since I just released it here to get a few people to provide some feedback, so far I am pretty happy with it, so I might release a .zip

@Mast3rPK Thank you for your feedback! I really appreciate it.

@olrak2
Copy link
Contributor

olrak2 commented Mar 20, 2016

If you can't flash it with fastboot you are not worth of being a tester 😜

@XePeleato hope development on your AOSP rom is going well

@FelipeBR28
Copy link

Obviously I can, just said that it's easier, not else.

@debbiche
Copy link

@XePeleato is there a source for this somewhere? Would love to try to build it for the P8 ;)

@XePeleato
Copy link
Owner Author

@debbiche I am talking with the members of TeamWin, so they can provide me with an 'official' recovery tree, the problem was that since the graphics are now coded in C++ instead of C, the graphics.c patch by jniklast became obsolete and I had to adapt it. Whenever that change is pushed you'll be able to build it.

@bboci80
Copy link

bboci80 commented Mar 23, 2016

help me please!
possible to, installing the Android6.0. marshmallow on the huawei P8 Lite Dual SIM(ALE-L21)?
if the answeris yes, then how i beginning andme it;;m?

@XePeleato
Copy link
Owner Author

@bboci80 There are some posts on XDA about it, however I won't update until Huawei releases it officially.

@muhammadfahadbaig
Copy link

@XePeleato Recovery works great 👍

@muhammadfahadbaig
Copy link

@XePeleato I can't seem to reboot to system from TWRP. It just powers off the device instead of rebooting.

@XePeleato
Copy link
Owner Author

@muhammadfahadbaig Have you played with the kernel? Did that happen with 2.8.7 version?

@muhammadfahadbaig
Copy link

It's the same with 2.8.7.0. (I built both of them myself using your device tree for Android 5.1.1 version with my own kernel built from source). I want to stay away from kernel sources as far as I can. I'll now use the Image from stock boot.img...

@XePeleato
Copy link
Owner Author

Have you tried with the file I released above?

@muhammadfahadbaig
Copy link

Same with your recovery.img...

@olrak2
Copy link
Contributor

olrak2 commented Mar 28, 2016

@XePeleato , probably not your recovery's fault but wanted to share my experience.

I had a backup of my rom: version B188 in TWRP (external SD Card)

I installed version B052 (did a full wipe, all also internal memory etc.) and then with OTA to B170.

Installed your recovery TWRP to go back to my backup of the B188.

Once my backup did install i booted up to my backup, no problem but my rom asked to make an OTA update to B188.

So there must be a partition or a file that did not got backup by TWRP. Maybe cust.img or something else but i think that can cause for problem when you restore a stock rom.

@muhammadfahadbaig
Copy link

@olrak2 You're right about the partition. Cust.img holds all current firmware information. That's why if you want to downgrade from lets say Android 6.0 to Android 5.1.1 you need to flash cust.img of Android 5.1.1 and then the whole stock ROM. It would be easy to add Cust partition to the Backup menu. Let me see it and I'll try to build one with this option.

@muhammadfahadbaig
Copy link

@olrak2 Just add this line in recovery.fstab (either before compiling from source or decompiling the recovery.img and editing this file in /ramdisk/etc/).
/cust ext4 /dev/block/platform/hi_mci.0/by-name/cust flags=backup=1;display="Cust";wipeingui

@muhammadfahadbaig
Copy link

@XePeleato As for the black screen patch for HiSilicon SoC,
does FBIOPUT_VSCREENINFO always passes or fails for our chipset?

@XePeleato
Copy link
Owner Author

I've never tried it , the custom graphics file works fine for me

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants