yashsingh1/xdaforums huggingface dataset:
[Honor 8 Guides, News, & Discussion] zinko_pt:
Thanks!

I thought Magisk and TWRP were already working in B380, from what I've read.

He's not much into trying out things. He just wanted adaway+Google Pay, Other adaway solutions work without root, but consume a lot of battery.

For the time being I'll advise him to hold his pants and bare with the ads.
[Honor 8 Guides, News, & Discussion] N01tra:
TWRP is, but Magisk an 'normal' root isn't due to kernel limitations.

As for getting rid of the ads, I've heard good things about https://f-droid.org/repository/browse/?fdid=org.jak_linux.dns66 / https://android.gadgethacks.com/how...pps-without-root-extra-battery-drain-0174614/
[Honor 8 Guides, News, & Discussion] martincg:
Thank you N01tra, I flashed second file and NFC + bluetooth works fine. I already flashed that file before, but maybe monday is better day for flashing.
[Honor 8 Guides, News, & Discussion] zinko_pt:
Thank you. I'll have his phone for testing DNS66 later. Need to check battery also. Probably might avoid rooting altogether. ;)
[Honor 8 Guides, News, & Discussion] thierrybla:
That's funny! :D
[Honor 8 Guides, News, & Discussion] surdu_petru:
Are you sure, about TWRP version ?

I already installed "rooted_b378_boot.img" via Honor 8 TWRP 3.1.0-0 from here !
[Honor 8 Guides, News, & Discussion] AnDrOiiiD_YT:
+1 Installed it also with the TWRP from [MENTION=2335078]surdu_petru[/MENTION] with no problems. You should change that [MENTION=8141896]thierrybla[/MENTION] for people not getting any misunderstanding.
[Honor 8 Guides, News, & Discussion] thierrybla:
Sorry, I had been busy but I changed it now! :)

Thanks!
[Honor 8 Guides, News, & Discussion] Telperion:
I got root on FRD L04B360 by flashing phh r310, has anybody else done similar? I didn't need a patched boot image.
[Honor 8 Guides, News, & Discussion] SolarisSixth:
Did you really get root?

I've noticed that if you use a root checker, sometimes it will say you have root, but you won't actually be able to read/write to your system partition.
[Honor 8 Guides, News, & Discussion] N01tra:
He has build number B360, NOT B380.

So his situation isn't relevant to this thread.

(To be fair, the buildnumber B380 isn't mentioned in the OP. But if all the steps are executed, B380 is the buildnumber you end up with)
[Honor 8 Guides, News, & Discussion] Skogstobbe:
I followed the guide and Everything worked fine for like a Week. Now Bluetooth and nfc dont work. I dont get it.

tried to install update.zip and the other file again but its says failed to mount /data
[Honor 8 Guides, News, & Discussion] Telperion:
Yes and no -- some root apps will execute, some won't. I flashed the SuperSU uninstaller which clears out PHH also, flashed stock boot image, then flashed the modified SuperSU zip and gained full root with r/w on system.
[Honor 8 Guides, News, & Discussion] Skogstobbe:
do u have some download links for SuperSU uninstaller and the stock boot image? . and what do u mean with "r/w on system". thanks
[Honor 8 Guides, News, & Discussion] Serpentdrago:
with the new version of twrp modified boot image is NO LONGER REQURED and you can just flash SUPER SU!
[Honor 8 Guides, News, & Discussion] N01tra:
Yup.

Info & guide can be found here: https://xdaforums.com/honor-8/development/twrp-t3566563
[Honor 8 Guides, News, & Discussion] Tapekiller:
I have few questions:

1. I messed up with my data partition and I am not able to mount it, is there a way to solve it in order to be able to flash these zips from twrp?

2. I previously flashed a prerooted img, is there any place where I can just download a stock one for FRD L09432 (western europe) ?

3. Generally speaking is there any way to force an old update.app file to install so I can make a clean update from the phone and then follow this procedure? I tried doing a rollback via power+down+up which gave me an ok (but when I booted I found the same exact thing as before) and installing a firmware from the honor website (which failed to verify update package).

I'm a bit desperate now because I would use the phone as it is if it wasn't for the missing keyboard, missing update section and crashing settings when I go to developer setting...

Thanks in advance for any help
[Honor 8 Guides, News, & Discussion] mawi86:
Someone has already tested this with FRD-L19?
[Honor 8 Guides, News, & Discussion] univoid:
I have tried flashing those two files using twrp but I get an error, does anyone know the reason? I have twrp frd not the one for the p9

I would like to have bt and NFC... Thank a lot
[Honor 8 Guides, News, & Discussion] aureliomilitao:
I have the unlock code

But, no appear the option in developer.....OEM unlock...
[Honor 8 Guides, News, & Discussion] Serpentdrago:
someone needs to update this guide its out of date ,
[Honor 8 Guides, News, & Discussion] Hillterpty:
As i know, the kingRooter and AnyRooter ,Mobile phone root can be choosed for us
[Honor 8 Guides, News, & Discussion] aureliomilitao:
Enable OEM unlock in the Development menu.

My Honor nougat, no have the option ^^^^^^
[Honor 8 Guides, News, & Discussion] N01tra:
Your best bet would be to return to 4.1(MM) and then upgrade to 5.0(N) again (it's what I had to do).

You can find the Rollback package and info here:

https://community.hihonor.com/docs/DOC-1752

After that OTA update to 5.0, re-unlock the bootloader, flash the latest TWRP, etc etc etc

"Could someone update the guide? It seems to be out of date" sounds a lot nicer and might actually get it done ;)

It would also be helpfull if you mention what part, according to you, is out of date. And since you're the one who noticed it, you could also give the OP the up-to-date info. That would get things done even faster!
[Honor 8 Guides, News, & Discussion] Tapekiller:
I actually managed to solve the issue last friday.

The rollback didn't work and somehow it rebooted into the same old problematic emui 5 even after a "success" message. Trying to update via dload/UPDATE.APP also failed (couldn't verify the package)

I just went full retard, flashed update.zip and update_data_full_hw_eu.zip via the modified 3.1.0-1 twrp (it worked even if other operations couldn't work because no /data access), booted into emui5, rebooted in twrp and flashed superSU (if I could go back I would have tried phh instead).
[Honor 8 Guides, News, & Discussion] Serpentdrago:
Its easy now . Its all in the TWRP post in the Dev section . Nothing fancy , no need to flash prerooted images , nothing . just twrp > superSU like any other phone .

Makes sure you are completely stock

1. Unlock bootloader

2. Flash TWRP from here > https://xdaforums.com/honor-8/development/twrp-t3566563

3.Boot into TWRP immediately after flashing

4. Flash SuperSU from here > https://drive.google.com/open?id=0BxWP2gF_0Bd_UmQ2Zm9ZRGxBTUE

5. Profit . Enjoy your perfectly working SuperSU rooted Honor 8 running EMUI 5.0
[Honor 8 Guides, News, & Discussion] shashankj150:
how to flash supersu ? its not zip file ?
[Honor 8 Guides, News, & Discussion] Serpentdrago:
just rename it to .zip ! Sorry , the OP/DEV of that TWRP thread needs to add that step !
[Honor 8 Guides, News, & Discussion] rjan22:
How about the L14 64gb us version?
[Honor 8 Guides, News, & Discussion] drbernardi:
Thanks for the guide, I just followed one of the sticky from this forum specifically for the Honor 8, everything works well but no BT :(

Will following your guide wipe my device? It's been 3 times I restore everything XD
[Honor 8 Guides, News, & Discussion] drbernardi:
The themes app is curiously not installed, system updater works, meaning that it opens and can check for updates. Build is B392SP01.
[Honor 8 Guides, News, & Discussion] venugopalu007:
Reset won't work he has to install the region zip again .
[Honor 8 Guides, News, & Discussion] drbernardi:
I was stuck in who know what firmware where I couldn't update anything because it didn't recognize anything as compatible (my FW number was B130).

I have no idea how but after a whole afternoon of trying like 15 FW I got the right one, and now installing this makes everything work, well I hope :)

Does anybody know if I have to take any particular step to install Viper4Android with this method? (or is the installed busybox enough already?)
[Honor 8 Guides, News, & Discussion] venugopalu007:
If you have twrp flash the viper4A mod , available in themes section.
[Honor 8 Guides, News, & Discussion] gopinaidu77:
He can also install the viper from magisk and install the extracted app, no need to flash. and he can also remove the viper easily ,If he wants.
[Honor 8 Guides, News, & Discussion] venugopalu007:
This works , i every time uses this guide.
[Honor 8 Guides, News, & Discussion] gopinaidu77:
Great one then
[Honor 8 Guides, News, & Discussion] gopinaidu77:
Why not make one bro?
[Honor 8 Guides, News, & Discussion] venugopalu007:
There is one already , i think.
[Honor 8 Guides, News, & Discussion] gopinaidu77:
Where?
[Honor 8 Guides, News, & Discussion] giasc:
Good morning thierrybla

I ask you for help

I have successfully performed all the steps, I arrived at this post because of the malfunction

of the Bluetooh (remained off)

Now the system works, but, I'm told an update of the operating system, under the details

Current version: FRD-L09C432B380

New version: FRD-L09C432B389

the problem is this, after downloading the 716MB, the cell will reboot, part the twrp-3.1.1-1-frd installs, but,

after restarting the system is not updated, it remains the FRD-L09C432B380 version

you can help me to update the system, certainly the fault and mine that I have to enable or disable something

Thanks 1000

Hello

Giampaolo
[General Questions and Answers] CrazyNik:
I want to increase size of recovery partition on Lenovo K30W so I can flash larger recovery image created for Lenovo A6000. I have devised a way, but I would be grateful if someone could look it over and spot possible flaws.

Here is the current partition table.

Model: MMC Q8XSAB (sd/mmc)
Disk /dev/block/mmcblk0: 15634268160B
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number Start End Size File system Name Flags
1 67108864B 134217727B 67108864B fat16 modem
2 134217728B 134742015B 524288B sbl1
3 134742016B 135266303B 524288B sbl1bak
4 135266304B 136314879B 1048576B aboot
5 136314880B 137363455B 1048576B abootbak
6 137363456B 137887743B 524288B rpm
7 137887744B 138412031B 524288B rpmbak
8 138412032B 138936319B 524288B tz
9 138936320B 139460607B 524288B tzbak
10 139460608B 139984895B 524288B hyp
11 139984896B 140509183B 524288B hypbak
12 140509184B 141557759B 1048576B pad
13 141557760B 143130623B 1572864B modemst1
14 143130624B 144703487B 1572864B modemst2
15 144703488B 145752063B 1048576B misc
16 145752064B 145753087B 1024B fsc
17 145753088B 145761279B 8192B ssd
18 145761280B 156247039B 10485760B splash
19 201326592B 201359359B 32768B DDR
20 201359360B 202932223B 1572864B fsg
21 202932224B 202948607B 16384B sec
22 202948608B 219725823B 16777216B boot
23 219725824B 1830338559B 1610612736B ext4 system
24 1830338560B 1863892991B 33554432B ext4 persist
25 1863892992B 1998110719B 134217728B ext4 cache
26 1998110720B 2014887935B 16777216B recovery
27 2014887936B 15634251263B 13619363328B ext4 userdata

Luckily, recovery and data partition are next to each other. Here is the procedure, please tell me if it is viable.

1. Boot into recovery

2. Create nandroid backup of data partition

3. Make sure that data partition is unmounted in recovery

4. Using parted, delete recovery and data partitions, and then recreate them with new sizes

5. Format data partition

6. Make sure that "use rm -rf instead of formatting" is enabled in recovery settings

7. Restore nandroid backup

8. Flash new recovery

9. Reboot

These are the commands I would use:

adb shell

parted /dev/block/mmcblk0

unit b
rm 27
rm 26
mkpart primary 1998110720 2031665151
mkpart primary 2031665152 15634251263
name 26 recovery
name 27 userdata
quit

mke2fs -t ext4 /dev/block/mmcblk0p27
[General Questions and Answers] CrazyNik:
As there were no replies, I took a risk and went ahead with resizing the partitions. The described procedure worked without problems.
[General Questions and Answers] addict1337:
Could you make a guide on how you did this exactly for noobs? :)

I understand that you posted the steps you used, but i'm not familiar with what you did.

Also, what rom are you using currently?

I got a rom working for this phone, It works well, but is not ideal.

https://xdaforums.com/general/help/k3-note-question-k30w-t3531158
[General Questions and Answers] CrazyNik:
Well, making an even more detailed guide will take some effort. I'll do it when I find the time.

I am using this ROM: https://xdaforums.com/lenovo-a6000/development/rom-resurrectionremix-5-8-1-t3555184

It's great, but I do have problems with updating it. Hopefully it'll be resolved soon.
[General Questions and Answers] CrazyNik:
Here is a more detailed procedure. However, if you are not familiar with Linux command line and the Android partition layout, I strongly recommend that you stay away from this.

First, you need Android platform tools from here. Download for your platform (I am going to assume Windows) and extract to a folder of your choosing (for example C:\Android).

You also need parted utility, download from here. It's best to extract it to the same folder as Android platform tools.

Next, open Windows command prompt and go to the platform tools folder. The easiest way to do it is to open the folder in Windows Explorer, right click in the empty space while holding shift and choose "Open command window here". Reboot your device in recovery mode and connect it to the computer USB port.

While in recovery, make a backup of your data partition.

Copy the new recovery image to external SD if you have one, or else to internal memory. You can do it using Windows Explorer.

Copy parted utility to the device.

adb push parted /.

Next, enter device shell.

adb shell

Make parted executable.

chmod a+x parted

Start parted utility.

./parted /dev/block/mmcblk0

Be extremely careful from now on. Every parted command is executed immediately, so if you type something wrong, you could brick your device.

Change size unit to byte.

unit b

Print your current partition layout. If it's not the same as in my original post, abort now as you'll mess things up.

p

Remove recovery and data partitions.

rm 27
rm 26

Recreate partitions with new sizes (recovery is now 32MB instead of previous 16MB).

mkpart primary 1998110720 2031665151
mkpart primary 2031665152 15634251263

Give partitions the same names as before.

name 26 recovery
name 27 userdata

Exit parted utility.

quit

Format the data partition.

mke2fs -t ext4 /dev/block/mmcblk0p27

Make sure that "use rm -rf instead of formatting" is enabled in recovery settings. This may not be necessary, but I've seen it in some tutorial, and it can't hurt.

Restore data partition from backup.

Flash new recovery using current recovery (go to install and choose "install image").

Reboot and hope for the best.
[General Questions and Answers] addict1337:
Thank you very much :)

I will give it a try.
[General Questions and Answers] addict1337:
All worked well, however I am never able to boot into recovery from my phone itself (before i attempted this, and after).

I always need to use my pc/usb to boot into recovery via a batch file.

Even if I install recovery from the recovery I just booted.

Getting into recovery is holding volume up and the power button right?

I installed the software you mentioned, however it is stuck at the bootscreen :(
[General Questions and Answers] CrazyNik:
To get into recovery, you need to keep BOTH up and down volume keys, and then power on. After a few seconds, you can release volume keys.

As far as the ROM is concerned, make sure you wipe data and cache before installing it. That's all I can think of.
[General Questions and Answers] addict1337:
Thanks.

I managed to install a CWM recovery for A6000, witch is working fine now (32MB) :)

I had problems with GPS on my Cyanongenmod Rom modified for K30-W, but after installing gapps all is working fine now.

Thank you for your help!
[General Questions and Answers] addict1337:
I hate to bother you any more, but I would like to use the same rom you are using, however I can't get it to flash.

I got TWRP 2.8.6.1 working (any other version I tried will not work)

I wipe DATA DALVIK and CACHE

When I try to install: 20170403-a6000-Official it gets stuck on:

Patching system image unconditionally....

I am able to flash Cyanogenmod, but that's a much older version.

If you could help me with what I am doing wrong, that would be much appriciated.

There are not many people running this phone.

I am also interested in the recovery you are using.
[General Questions and Answers] CrazyNik:
You must use TWRP 3.1.0, but even with it, RR 20170403 will not install on K30W firmware, I don't know why. I managed to install it by flashing A6000 firmware first. I will post the tutorial on RR thread when I find the time.
[General Questions and Answers] CrazyNik:
I've posted the tutorial here.
[General Questions and Answers] addict1337:
Awesome, I was waiting for it :D

Thank you very much.
[Xperia Z3 Compact Original Android Development] tomascus:
Installation guide for new users:

Things you need:

- Stock firmware (if you're not on .291): https://xdaforums.com/showpost.php?p=56046548&postcount=2

- TWRP Recovery image: Above in OP, downloads area

- The ROM: Above in OP, downloads area

Make sure you're on the latest stock firmware, version 23.5.A.1.291

If you're not:

1. Download the firmware from the above link or somewhere else, it doesn't matter which region you pick

2. Flash the FTF file with Flashtool, latest version obtainable here: http://www.flashtool.net/index.php

3. Power off the phone after completion

Flashing TWRP Recovery:

1. Download from above

2. Enter fastboot mode - while the phone is off, hold the vol up button and insert your USB cable (connected to PC), blue led light should appear

3. Enter the following command: fastboot flash FOTAKernel twrp_z3c_2017-04-26.img (or whatever the file is called)

Flashing the ROM:

1. To enter recovery, hold the power and vol-down keys while the phone is powered off

2. Wipe system, data, cache, dalvik cache

3. Select the ROM zip and flash away

4. OPTIONAL: Flash any extras, Gapps (open gapps work well) and root from here: https://download.lineageos.org/extras use addonsu-arm-signed.zip for ROOT, not SuperSU

5. Reboot

If coming from previous version:

What I recommend is full wipe. No support for those who dirty flash.

- Backup apps with Titanium Backup or other alternatives.

- Backup SMS/call log with SMS backup app.

Known Issues

* Bluetooth connection issues

* Mobile data reconnection issues

* Encryption and adoptable storage leads to bootloops

How to report bugs:

- Attach any

relevent

logs: dmesg or logcat (clear logs with "adb logcat -c" first, then reproduce issue)

- For random reboots, provide a last_kmsg

- Screenshots or written

explanations

of how to reproduce
[Xperia Z3 Compact Original Android Development] tomascus:
Snap Camera Mod

Simply exposures (pun not intended) Sony variables for the Snap camera app (default one).

- Capture prio modes (ISO/Shutter speed/Manual/Auto)

- More ISO values selectable

- Sony metering modes

- Sony video stabilisation control

Download:

https://androidfilehost.com/?fid=673791459329051895

Instructions:

1. Flash ZIP in TWRP

2. Clear data for Camera
[Xperia Z3 Compact Original Android Development] mcgi5sr2:
First

Thoroughly tested, everything works. Great Job on this one

link removed
[Xperia Z3 Compact Original Android Development] Rhonin86:
Oh yeah :D I'm downloading right now to give it a try later.... If i succeed and find the time i'll report

For now A REAL BIG THX

Rhonin
[Xperia Z3 Compact Original Android Development] :
One more ovation for [MENTION=6979267]nailyk[/MENTION] and [MENTION=4675360]tomascus[/MENTION]
[Xperia Z3 Compact Original Android Development] panzerox123:
[MENTION=6979267]nailyk[/MENTION] [MENTION=4675360]tomascus[/MENTION] great work!

Now, for those of you getting the Error7 in TWRP, delete these lines from META-INF>com>google>android>updater-script

(!less_than_int(1490124938, getprop("ro.build.date.utc"))) || abort("E3003: Can't install this package (Tue Mar 21 19:35:38 UTC 2017) over newer build (" + getprop("ro.build.date") + ").");
assert(getprop("ro.product.device") == "D5803" || getprop("ro.build.product") == "D5803" || getprop("ro.product.device") == "D5833" || getprop("ro.build.product") == "D5833" || getprop("ro.product.device") == "z3c" || getprop("ro.build.product") == "z3c" || getprop("ro.product.device") == "aries" || getprop("ro.build.product") == "aries" || abort("E3004: This package is for device: D5803,D5833,z3c,aries; this device is " + getprop("ro.product.device") + "."););
ui_print("Target: Sony/D5803/D5833:6.0.1/23.5.A.1.291/2769308465:user/release-keys");
ifelse(is_mounted("/system"), unmount("/system"));

If anyone asks about how to fix error 7... I will personally send hand them over to cannibals XD
[Xperia Z3 Compact Original Android Development] snaky90:
This version uses stock blobs ?
[Xperia Z3 Compact Original Android Development] mcgi5sr2:
yes uses stock blobs
[Xperia Z3 Compact Original Android Development] gr8st:
Great work guys! :svetius:
[Xperia Z3 Compact Original Android Development] Pisiont:
So no working version yet? The one mcgi5sr2 posted couldn't go through setup after booting, didn't respond to anything other than power menu.
[Xperia Z3 Compact Original Android Development] nailyk:
It is an issue when you doesn't have gapps. Reboot should work.
[Xperia Z3 Compact Original Android Development] Pisiont:
Reboot doesn't help, but I'll try with gapps. Hope that works
[Xperia Z3 Compact Original Android Development] vooR9er:
Thank you,mcgi5sr2, nailyk Yes, it really takes a very long time to install the firmware. Camera does not work. Black screen, the first launch of the camera with the button, now without a button on the display, very sorry. :(

P.S. Gapps is not set
[Xperia Z3 Compact Original Android Development] panzerox123:
Guys, just to clear out any misconceptions, the ROM is fully working and stable for daily use . The build was taken down because of a model specific issue. A new fixed build will be out soon. (No I am not developing it. Just testing the builds)
[Xperia Z3 Compact Original Android Development] Pisiont:
Is that model specific issue a not working camera? Expect that seems stable, some lineageos settings crash also but that's not a big deal.
[Xperia Z3 Compact Original Android Development] panzerox123:
Yes. My device has a front camera that is used in Leo, that's why camera apps crashed for me
[Xperia Z3 Compact Original Android Development] Pisiont:
leo has different camera than our compact? don't really understand what you mean
[Xperia Z3 Compact Original Android Development] panzerox123:
In a nutshell... There are 2 difference front cameras... There was only one driver in the build
[Xperia Z3 Compact Original Android Development] Bluestar01:
I am a little confused: Is camera working or not?
[Xperia Z3 Compact Original Android Development] skaterbub2003:
Do I have to flash the SU-package everytime, I flash an update?
[Xperia Z3 Compact Original Android Development] madvinegar:
First of all thank you very much for your reply.

We are half way there! I did as you said and I now my device is rooted (both adb and apps)!

The only problem now is that I still cannot access twrp. It takes me straight to lineage bootloader.

I flashed twrp 3.0.2.1 because that's the only one I can find. Do you have a link for twrp 3.2.0.0 ?
[Xperia Z3 Compact Original Android Development] skaterbub2003:
I guess, they meant the 3.0.2.0.
[Xperia Z3 Compact Original Android Development] panzerox123:
Because you need to enter TWRP by holding vol down + power
[Xperia Z3 Compact Original Android Development] shrazy:
If you have root now you can download twrp manager from play store and try to install it with the app. Give us reply if it works.
[Xperia Z3 Compact Original Android Development] panzerox123:
Nope
[Xperia Z3 Compact Original Android Development] madvinegar:
Yes that's what I did and it worked!

Thank you all for your kind assistance.

You rock!