yashsingh1/xdaforums huggingface dataset:
[Honor 7 Android Development] samcro94:
H7 &H7+ use the same firmware

so they must accept the same TWRP
[Honor 7 Android Development] paulobrien:
Ah yes, sorry, misread it as the 7i. It'll work fine.

P
[Honor 7 Android Development] crislink89:
awesome
[Honor 7 Android Development] m_esser:
Suggestion

Hello,

first of all THANK YOU VERY MUCH for your great work regarding TWRP for Honor 7!

As non-toxic already mentioned in his thread your TWRP implementation is running smoothly on both potential partition (recovery and erecovery).

I am using the stock recovery on the primary recovery partition and using TWRP on the eRecovery partition.

Thus it would be a great improvment if you could enhance TWRP by the option to re-boot into the eRecovery partition as well.

Although I have already made a corresponding app (German speaking people can take a look at "xxx.android-hilfe.de/thema/twrp-und-stock-recovery-gleichzeitig-auf-dem-honor-7-installieren-und-nutzen.766728/"). In my opinion it would be helpful to get this option integrated into TWRP.

My app uses the shell command "svr power reboot erecovery" for that purpose. Thus I assume that the coding for TWRP should be simple as well.

Best regards from Germany

m_esser
[Honor 7 Android Development] paulobrien:
Thanks for the info, I'll look into it!

P
[Honor 7 Android Development] hackslash:
[MENTION=220328]paulobrien[/MENTION]

I know this is off topic but I just want to ask one thing.

The patch you submitted to Gerrit to make recovery work would work with all Kirin SoC or only Honor 7. (Honor 7 is Kirin + Mali GPU right?).

I have been using the jniklast FBIOPAN Display patch and it does works but running two displays isn't a feasible option.

So I just wanted to confirm if the patch is kind of, a universal one for all Kirin SoC.
[Honor 7 Android Development] paulobrien:
It's a generic patch related to touch not working after first recovery boot. It's needed for some devices, but not all!

P
[Honor 7 Android Development] hackslash:
Alright! So it's not the Black Screen patch. For some Kirin devices, the screen goes black when boot to recovery. However the touch is working fine but there is no display. I'll test your patch for my device.

Thanks a bunch! :good:
[Honor 7 Android Development] Icetea:
BTW: can anybody tell me why the TWRP file counter doesn’t count correctly? In progress it showed me more than 100% or more (104%)!! Not 100%

How difficult it is to calculate the correct number for files and size??? This problem already exists at all versions of TWRP.
[Honor 7 Android Development] inside!out:
[MENTION=220328]paulobrien[/MENTION] if add oeminfo partition in fstab. will it work?
[Honor 7 Android Development] paulobrien:
I would imagine so, what is that used for?

P
[Honor 7 Android Development] DigiGoon:
I think, for the boot logo/splash screen.
[Honor 7 Android Development] didier2012:
Hi, how to add adoptive partition on recovery.fstab because my sdcard is mixed and not automatically detected. I can mount it manually using dmsetup and mount from adb. Thanks.

Envoyé de mon PLK-L01 en utilisant Tapatalk
[Honor 7 Android Development] raghavhartz:
do this work for B160 (Indian version)...??
[Honor 7 Android Development] Icetea:
i think yes. Try it out, more as you have to flash stock recovery again, could not be happen.

suggestion: flash twrp to recovery2 at first to try it out! You can start TWRP with pressing vol up with power on together if usb cable is connected to a pc. Recovery2 is normally unused. If you follow this suggestion your OTA functionality will persist. (if you have no root or system changes!!)

If it work for you, you can flash TWRP to recovery later.
[Honor 7 Android Development] raghavhartz:
hey dude actually right now i hve only my bootloader unlocked...that's it.....and just giving permission through tht king root app...so wanted to know do this actually works for all h7 devices or i would be in bootloop..??

ps- don't hve any firmware too...!!
[Honor 7 Android Development] Icetea:
ok, it is a little bit risky, but this is this reason i told you to use recovery2 to flash TWRP at first. (fastboot flash recovry2 twrp.img) If it fails, stock recovery isn’t changed and should work as expected to reboot into your system. Recovery2 is for repairing broken systems via OTA. Normally it is completely unused by the other users. So it will be your decision now.

see my signature:D
[Honor 7 Android Development] t-ryder:
First I got say thank you again, [MENTION=220328]paulobrien[/MENTION]. Having a Honor 7 would be very boring without your work.

The TWRP you provided works good, only bug I have to mention is that when booting into TWRP sometimes I got

no touch input at all. I have to reboot TWRP again and then it works. Sometimes I have to reboot TWRP two times so it works again.

But if booted and touch is working there are no problems at all. Maybe this happens only if I reboot into TWRP using flashify - I can not

remember since I boot into recovery quite a lot. :silly:
[Honor 7 Android Development] m_esser:
Hi [MENTION=220328]paulobrien[/MENTION],

That's a problem that I have as well...

... btw, some days ago I have asked whether there is a chance to integrate an additional boot option (into /recovery2) . Do you have any kind of intermediary result regarding this aspect?

Best regards

m_esser
[Honor 7 Android Development] paulobrien:
Updated test release posted.

P
[Honor 7 Android Development] t-ryder:
Flashed twrp-3.0.2-0-plank-modaco-rc3.img using flashify, rebooted to recovery in flashify - touch working. Rebooted recovery using TWRP reboot menu

- booted; no touch input. Waited a minute inside TWRP (until screen turned off), turned screen on and could swipe to unlock TWRP, touch working then again.
[Honor 7 Android Development] m_esser:
After a timeout period of 3 weeks I have now tested the version rc3 as well and unfortunately I have the same problems like [MENTION=3705546]t-ryder[/MENTION].

Best regards

m_esser
[Honor 7 Android Development] t-ryder:
I am getting no touch input fails (or is it freezes?) more and more often.

Sometimes I have to reboot my device up to 4 or 5 times until I can use the recovery.
[Honor 7 Android Development] samcro94:
Hi, Did you tried to flash it with the MultiTool ?
[Honor 7 Android Development] t-ryder:
Yup. Same.
[Honor 7 Android Development] samcro94:
Strange, we use it daily and never had this issue
[Honor 7 Android Development] hachuwaka:
For the first time I've started having issues like the mentioned above. No touch input in TWRP. It has happened to me twice already...

Edit: three times now [MENTION=220328]paulobrien[/MENTION] you know something about that?

Enviado desde mi PLK-L01 mediante Tapatalk
[Honor 7 Android Development] Icetea:
don’t know why...

since i have changed the custom rom on my Honor7, i am not able to recover new twrp backups with password protection!

Every time i try to enter, i get a notification that my password was wrong!!!! I’m not stupid, i use this pw since 3 years without problems!

Any suggestions?
[Honor 7 Android Development] SoulSeekerHS:
I can't use the "fastboot boot twrp-3.0.2-0-plank-modaco-rc3.img" command. Always results in a "Command not allowed" error. I used this with all my phones before to do a nandroid backup including the stock recovery. Why doesn't it work with the Honor 7? Bootloader is unlocked, drivers installed, adb and fastboot work... I tried with other versions of twrp, same result.

Any idea what could be the issue? Or does this just not work with this phone?

fastboot boot twrp-modaco-rc3.img

downloading 'boot.img'...

OKAY [ 0.594s]

booting...

FAILED (remote: Command not allowed)

finished. total time: 0.606s

PS: I don't want to try and flash the recovery before I pulled a full stock backup. :( But maybe that will fail, too, anyway. Hoping for some input if other have the same issue.
[Honor 7 Android Development] zinko_pt:
I think H7 does not allow booting live bootloaders. You have to install it.

I wanted to do the same: do not install TWRP, just boot it to install SuperSU and do the normal operations.
[Honor 7 Android Development] t-ryder:
All OTAs, stock images and stock recoveries are available for download somewhere. Download all you need now (to be safe just in case), and use Honor Multitool to do your stuff.

Before I unlocked my bootloader using DC unlocker I downloaded everything so I can go back to complete stock with locked BL without hustle.
[Honor 7 Android Development] paulobrien:
Huawei phones don't support fastboot boot.

P
[Honor 7 Android Development] SoulSeekerHS:
OK, thanks for the answers. Thought as much, but figured I might just be missing something. Weird that Huawei would block booting a recovery, but alas, as long as I can flash it...
[Honor 7 Android Development] Ing.King:
Sorry for silly question. Can I boot fastboot boot twrp.img without unlocking of bootloader ?
[Honor 7 Android Development] Icetea:
this really silly question was answered only a few post back my friend!!!:p

look here -> http://xdaforums.com/showpost.php?p=67828469&postcount=83
[Honor 7 Android Development] Ing.King:
my lazy ass didn´t read 2 posts earlier... my bad
[Honor 7 Android Development] m_esser:
Hello [MENTION=220328]paulobrien[/MENTION];

thanks again for your effort regarding TWRP for Honor 7 devices. I have a question regarding the USB OTG support of TWRP 3.0.2.

Currently I strive to enhance my custom rom H7cROM so that it will store several files to an usbotg device (if one is attached).

In order to check if a device is attached to usbotg I wanted to use a little trick as part of the updater-script file:

simply create a folder on /usbotg and copy a file to that folder

ignoring potential error messages

checking whether the file exists

.

During my tests I had to find out that I can store/write file to the /usbotg (under TWRP) even if there is no device attached. The attached screen was made when no usbotg device was attached :confused:

Because of that I am asking myself now

Where are files stored when no usbotg device is attached?

How can I implement a valid check to find out whether a device is attached or not?

Perhaps you could provide a useful hint? Thank you in advance!

Best regards

m_esser
[Honor 7 Android Development] DigiGoon:
[MENTION=7354493]m_esser[/MENTION] maybe, try checking the partition size? If it's equal to 0 then not attached, but if you get some value then it is attached. Just a thought, don't know if this works. :)
[Honor 7 Android Development] m_esser:
Thanks for the hint ... will check it ;)

Best regards

m_esser
[Honor 7 Android Development] DigiGoon:
Yes, and do report back so that we can know if it works. :) :D
[Honor 7 Android Development] hackslash:
[MENTION=7354493]m_esser[/MENTION]

I don't know if it would work but you could try it.

Try the Mount applet from Busybox. You can check the status of the mount command by looking at the return codes:

RETURN CODES
mount has the following return codes (the bits can be ORed):
0 success
1 incorrect invocation or permissions
2 system error (out of memory, cannot fork, no more loop devices)
4 internal mount bug
8 user interrupt
16 problems writing or locking /etc/mtab
32 mount failure
64 some mount succeeded

You can use echo $ to display the error code.

What you can basically do is write a script that first unmounts the USB OTG (will unmount if present, will fail if not mounted) and then try to remount it. Read the return code for the remount part. If it's "0", then that means USB is mounted successfully and you can continue whatever you were initially thinking to do and if it returns any other code, you can simply display a message like "USB not inserted" or error basically referring to the reason why the mount failed. Now this has some obvious flaws such as if the script is being executed from the USB itself, then you know...

I took this information from here http://unix.stackexchange.com/questions/38870/how-to-check-if-a-filesystem-is-mounted-with-a-script and there is a nice little bash script in the answer which can help you achieve what you want to.

The second method which you can also use is to use df applet in busybox. Executing command:

df -h

will list the partition, mount point, size and other stuff about all mounted partitions. Channel the output to a text file:

df -h > output.txt

Then try to search for the USB OTG mount point or the partition itself and if it's found, execute the commands you want to:

File=output.txt
if grep -q /usbotg "$File"; then
>> commands to execute
fi

Well it could be as simple as checking the size of the directory, but I wanted to add more insight to the topic and give how I may tackle the same issue. I haven't tested both the methods but since the all commands are available via Busybox, I think it might work.
[Honor 7 Android Development] m_esser:
[MENTION=6435663]hackslash[/MENTION] and [MENTION=5391886]DigiGoon[/MENTION]: Thank you very much for your suggestions:good:! Both hints were very helpful for me.

I have played around with several "approaches" considering your input. At the end I have found the following solution for my issue:

by using the function 'getdisksize("/usbotg","m")' I am getting the size of the partition /usbotg (as part of the aroma config file)

if no usb otg device is attached the funktions returns "-1" and otherwise the size of the partition

the value gets stored in an aroma prop file so that it can be accessed during the core installation

during the core installation (execution of updater-script file) I am using the function "file_getprop" to read the parition size and to find out whether there is a device attached via USB OTG

So, my main issue is solved ... thanks to your input.

But I am still a bit surprised that a script can create folders and write files to /usbotg even though there is no phyiscal device attached:confused:.

Best regards

m_esser
[Honor 7 Android Development] DigiGoon:
Yes that's a bit strange, it should store it somewhere, did you try to explore any temp directory after the installation?
[Honor 7 Android Development] m_esser:
To be honest - I didn't because I wanted to focus on the solution and not on the problem. Perhaps paulobrien can fix that issue very fast (e. g. by making this "virtual" partition read-only or something similar).

Best regards

m_esser
[Honor 7 Android Development] DigiGoon:
It will take sometime, as he has to manage all the Honor devices. :) :D
[Honor 7 Android Development] hackslash:
[MENTION=7354493]m_esser[/MENTION]

Think of it as your Ubuntu drive where you can create folders and add data to it or mount a partition over that directory (which is basically a symlink, much advanced approach though). As far as I think of it, when you boot to recovery or you boot to system, all other partitions are mounted at one main partition at different directories. That main partition stores all the SoC related files and drivers, proc folders, etc. That main partition is still a partition and you can add data to it up to the storage limit of that partition. Remember that a folder is just a typical folder until a partition is mounted over it. That folder can store data and the space will be used from the partition the folder is created into. It's actually not a bug in any case. If a partition allows user to create folders, then hell yes, it would let it create (unless there are permissions issues which is not the case here because TWRP mounts partitions RW which allows it to actually create folders on that main partition and mount all partitions onto it).

My thoughts or knowledge of how it works can be really wrong but it's what I think it is.
[Honor 7 Android Development] m_esser:
[MENTION=6435663]hackslash[/MENTION]: I think that your explanation is not wrong - it is going into the right direction and it is explaining why folders and file scan be stored. If a device is attached via OTG the "symlink" is pointing to the device if not it is pointing to a folder of the "main partition".

Best regards

m_esser
[Honor 7 Android Development] DigiGoon:
[MENTION=6435663]hackslash[/MENTION]

Yes, you are correct, the main partition has various mount points of our device's partitions, defaults like /system, /boot, /cust, /data. etc so as you said, we can create folders in mount points, as basically the mount point is itself a folder, symlinked to the real partitions(that's why the use of recovery.fstab).

So, the files stored inside /usbotg should reside here: main_partition/usbotg/

Thanks for the explanation. :) :D
[Honor 7 Android Development] lakistrike95:
Does it works with PLK-TL01H? I have 4.0.1 EMUI, B380.

Is twrp-3.0.2-0-plank ok?
[Honor 7 Android Development] ASMstudent:
It should work with any ROM
[Honor 7 Android Development] bestfil:
Hello.

I've installed https://dl.twrp.me/plank/

but there is a huge problem with wiping /cache/ partition.

Have You got any updated version?
[Honor 7 Android Development] bestfil:
Is anybody here?

Regards!
[Honor 7 Android Development] Icetea:
this is the last TWRP from paulobrien because all developers have stop there support to this model and leave this area!

-> http://www.modaco.com/forums/topic/377169-official-twrp-recovery-3020-for-honor-7/
[Honor 7 Android Development] gopinaidu77:
It's sad that skilled devs leave.
[Honor 7 Android Development] thelous:
this one works for honor 7 lite aswell?
[Honor 7 Android Development] tomtomk99:
Charging when Off boots into recovery...

Works fine with the B380. Downloaded the latest version for Honor 7 (TWRP 3.0.2.0 Plank) via the TWRP Manager and flashed it with adb.

Just having 2 issues:

*first one was already mentioned a few times: Touch-Input isn't working all the time --> you just have to wait till the screen turns off, after turning it up again, it should work fine.

*i'm not quite sure if the second issue is related with TWRP but i do think so: when charging while the phone ist shut off, it automatically boots into TWRP recovery. I've googled around and found out, that this is related to TWRP, other recoveries doesn't have a bug like this. But since I didn't test it myself, I'm not quite sure if this bug isn't caused by e.g. the Unofficial CM13 for Honor 7 I'm running on. Does anyone else have this bug? Or does somebody know how to fix it? [MENTION=220328]paulobrien[/MENTION] Do you know this issue?

Other than that, I'm pretty happy :)
[Honor 7 Android Development] muradulislam:
The second one is present only in unofficial CM13. Was using TWRP with emui and never faced that issue.
[Honor 7 Android Development] BatChen:
could you please give me the link of unofficial cm13？thanks in advance.
[Honor 7 Android Development] muradulislam:
Follow this thread please

https://xdaforums.com/honor-7/development/unsupported-cyanogenmod-13-honor-7-plk-t3542627
[Honor 7 Android Development] beinfo:
plank on a PLK-AL10

Hi did it work at your PLK-AL10 ?

which Version did you use?

my PLK-AL10 is on Build 388

Andorid 6.0

Emui4.01

greetings

Frederic

fbeinfo@yahoo.de
[Honor 7 Android Development] wilsonj59:
Installed this and used fastboot to flash the twrp img on my Honor 7. Flashed just fine and I tried to reboot into recovery and it took me into the Huawei eRecovery and not TWRP, I searched online and saw that if you unplug the usb after it installs TWRP while in fastboot and power down + volume up into recovery will stop the phone from overwriting TWRP back to the eRecovery. I've tried multiple things onling, but nothing works. Also, before you ask; yes I do have unlocked my bootloader. I also tried the fastboot boot recovery.img method, but it said the command was denied. Can anyone help me?
[Honor 7 Android Development] Dattel01:
H7 does not allow booting into Recovery through "fastboot boot".....

To boot into TWRP you need to unplug H7 from USB first and than use POWER & VOL+

If the H7 is pluged in, the same keykombination brings up the eRecovery...

If you need more help on button combinations, visit the guid on https://xdaforums.com/honor-7/general/honor-7-button-combinations-clarified-t3320467
[Honor 7 Android Development] r4n69a:
Ask you guys if there is twrp for honor 7a, thanks

Ask you guys if there is twrp for honor 7a, thanks
[Honor 7 Android Development] vikingmax:
I've just one question here! Is this recovery good enough to be used with Honor Play 7 (Chinese version of Honor 7S)? I'm asking this because I couldn't find any support base for this phone on XDA as yet.

Looking forward, cheers.
[Honor 7 Android Development] spirtix:
Honor 7S Is totally different phone. It is very similar to Huawei Y5 Prime (2018) though.
[Honor 7 Android Development] Bluscream:
I need to know that too. Help please!
[Xperia Z2 Tablet General] chitshiv:
I downloaded Geekbench 3 App to know my Tablet Z2 Benchmark Score and the results are :

Xperia Tablet Z2 Geekbench 3 Score :​

Single Core 892

Multi Core 2532

[YOUTUBE]P9cyz4AQnZg[/YOUTUBE]​

I wanna know that weather Marshmallow scores are better than Kitkat and Lollipop's. You guyz also do the Benchmark and post your SCORES here.
[Xperia Z2 Tablet General] defim:
the scores depend on the hardware not software ;)
[Sony Xperia M2] SuperDalibor96:
Are those Sony Xperia M2 and Sony Xperia M2 aqua the same about custom rom?? I wanna try to flash my M2 Aqua and i don't know is there any custom rom for it?
[Sony Xperia M2] SuperDalibor96:
i guess ill need to find out solo
[Sony Xperia M2] aidy.lucas:
Should be OK, there are two types of M2 though guessing aqua is the same, a early version and a late version and the latter was giving problem's you'll need to read up on the cm and omni threads.

D2303 5.1 deodexed z2 port+z5+X apps+themes, be,xr,sv,ad,XZRt2urecovery,xposed,z5 cam2.0,xLOUD,S-Force,viperaudio+more
[Remix OS for PC] Bayu_Achmed:
help me how to fix usb wifi in remix os please
[G3 Q&A, Help & Troubleshooting] Thomas1897:
I have a LG G3 D855 with the marshmallow KDZ flashed with flash tool everything was good and had no problems. Two weeks ago i rooted my phone and the next day i wanted to install Xposed and after searching for a bit i installed it and got stuck in the bootloop. I managed to recover it by using the .tot method and since then my phone is messed up, like when im using it it restart for no reason at all, or just when it restarts i unlock it and 6/10 times it restarts again. I don't know what's wrong with it and i was hoping someone knows what to do since this is very anoying Thank you :)

On i've asked for help on Reddit, but maybe someone here knows a solution for it. I really don't know what to do anymore. :(
[G3 Q&A, Help & Troubleshooting] halekhonza:
Hello,

do you want to backup your app data? Easiest way is flash KDZ via flash tool with CSE flash (format all).
[Verizon Samsung Galaxy S7 Edge Guides, News, & Dis] geoff5093:
That's interesting - When I get some time I'll give it a shot. I just did a factory reset on my phone, and this time did not install Package Disabler Pro, and instead just disabled some annoying bloatware like NFL, some Verizon crap, Amazon, etc., none of the processes that I had disabled before. It's early on, but I actually see the performance of the phone to be much more responsive than before, and it actually looks like doze is working. I think there is definitely something to be said for blindly disabling a bunch of services thinking it's only for the better.
[Verizon Samsung Galaxy S7 Edge Guides, News, & Dis] dajmanjt:
Absolutely agree. I definitely spent way too much time trying to figure out exactly what apps I should disable lol. But in the end it has definitely been worth it.

If you try it let me know your results. I will be attempting this on my dad's s7 edge when I see him next so I can try and verify it on my end as well. My dad lives 4 hours away so I don't see him very often.
[Verizon Samsung Galaxy S7 Edge Guides, News, & Dis] geoff5093:
At least your mom isn't on an S3 still and perfectly happy lol
[Verizon Samsung Galaxy S7 Edge Guides, News, & Dis] dajmanjt:
lol could be worse..... my mom is on an iphone 6
[Verizon Samsung Galaxy S7 Edge Guides, News, & Dis] Jonbelloguzman:
Thank you for the awesome tip. I'm going to give those suggestions a try. Can you please tell me how to enable doze? I though t the S7 Edge automatically went to doze when not in use?