yashsingh1/xdaforums huggingface dataset:
[Upgrading, Modifying and Unlocking] OfficerJimLahey:
From what I remember, every version of Windows has had some sort of problem with ADB when (Windows is) first installed. That is, an update always seems to catch up to the problem (except they may still be fighting with it on Win10).

I would try with Ubuntu. At worst, as [MENTION=5545101]xdajog[/MENTION] mentioned, you may need a udev rule. Here is what mine looks like (disregard the other OEM's - if you like):

joel@cybaryme:/etc/udev/rules.d$ ls
10-local.rules 51-android.rules 51-garmin.rules 56-hpmud.rules 70-persistent-net.rules
joel@cybaryme:/etc/udev/rules.d$ cat 51-android.rules
#Acer
SUBSYSTEM=="usb", ATTR{idVendor}=="0502", MODE="0664", GROUP="plugdev"
#ASUS
SUBSYSTEM=="usb", ATTR{idVendor}=="0b05", MODE="0664", GROUP="plugdev"
#Fujitsu & Fujitsu Toshiba
SUBSYSTEM=="usb", ATTR{idVendor}=="04c5", MODE="0664", GROUP="plugdev"
#Garmin-Asus
SUBSYSTEM=="usb", ATTR{idVendor}=="091e", MODE="0664", GROUP="plugdev"
#Google
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0664", GROUP="plugdev"
#HTC
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0664", GROUP="plugdev"
#Huawei
SUBSYSTEM=="usb", ATTR{idVendor}=="12d1", MODE="0664", GROUP="plugdev"
#Lenovo
SUBSYSTEM=="usb", ATTR{idVendor}=="17ef", MODE="0664", GROUP="plugdev"
#LG
SUBSYSTEM=="usb", ATTR{idVendor}=="1004", MODE="0664", GROUP="plugdev"
#Motorola
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", MODE="0664", GROUP="plugdev"
#Nook
SUBSYSTEM=="usb", ATTR{idVendor}=="2080", MODE="0664", GROUP="plugdev"
#Nvidia
SUBSYSTEM=="usb", ATTR{idVendor}=="0955", MODE="0664", GROUP="plugdev"
#OTGV
SUBSYSTEM=="usb", ATTR{idVendor}=="2257", MODE="0664", GROUP="plugdev"
#Philips
SUBSYSTEM=="usb", ATTR{idVendor}=="0471", MODE="0664", GROUP="plugdev"
#Qualcomm
SUBSYSTEM=="usb", ATTR{idVendor}=="05c6", MODE="0664", GROUP="plugdev"
#Samsung
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0664", GROUP="plugdev"
#Sony
SUBSYSTEM=="usb", ATTR{idVendor}=="054c", MODE="0664", GROUP="plugdev"
#Sony Ericsson
SUBSYSTEM=="usb", ATTR{idVendor}=="0fce", MODE="0664", GROUP="plugdev"
#Toshiba
SUBSYSTEM=="usb", ATTR{idVendor}=="0930", MODE="0664", GROUP="plugdev"
#ZTE
SUBSYSTEM=="usb", ATTR{idVendor}=="19d2", MODE="0664", GROUP="plugdev"
joel@cybaryme:/etc/udev/rules.d$
[Upgrading, Modifying and Unlocking] AndyYan:
Is this still being maintained? I've been frustrated by the root experience on my newly bought LG Enact which has the same codename as the F3Q: fx3q, so I thought the two devices aren't that different and maybe I could risk trying this one, but 1) installing via loki_tool gives "Loki aboot version does not match device." and it refuses to flash, and 2) the DD method flashes alright, but after using "reboot recovery" it goes in some sort of fastboot mode instead of recovery (fastboot command recognizes the phone). Can I get it working on my device somehow?
[Upgrading, Modifying and Unlocking] steadfasterX:
Hi AndyYan

You need to extract the aboot partition from your device and send that to me. This is needed to provide a matching boot/recovery image for your device.

You can all do this on your own if you like: compile twrp with my device tree, extract the aboot partition, loki the twrp build with that aboot image and flash it.

Greetings

Xdajog

.
[Upgrading, Modifying and Unlocking] AndyYan:
Copy that. How would I do it? Using DD command maybe? I'm rooted so that wouldn't be a problem if you have the exact command.

Sent from Google Nexus 6P @ CM13

[WARNING: XDA One have not implemented "mark forum as read" - do not use]
[Upgrading, Modifying and Unlocking] steadfasterX:
Well the main part is described in FAQ #5 in this thread:

http://xdaforums.com/showpost.php?p=60832650&postcount=2

Try the following command to get an aboot image:

dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/storage/external_SD/aboot20160305.img

Adjust the of= when you do not have an external sdcard like this:

dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/storage/sdcard/aboot20160305.img

This will work only if the enact handles partitions the same way as the F3Q which I don't know so it may not work.

.
[Upgrading, Modifying and Unlocking] AndyYan:
1024+0 records in
1024+0 records out
524288 bytes transferred in 0.097 secs (5405030 bytes/sec)

Generated aboot img:

View attachment aboot20160305.img

Hopefully this could result in a usable package.

The Enact is running on KitKat, by the way - this might involve some extra trouble.
[Upgrading, Modifying and Unlocking] steadfasterX:
Quite small image but well it seems it could work. The problem is that loki is not able to patch a recovery for the enact device. I tried it with the aboot you provided but it doesn't worked. Loki is the hack needed to unlock the bootloader 'on-the-fly' to be able to boot a custom recovery or a custom ROM.

I can try to force patching but that needs some time because I need to compile loki first etc.

.
[Upgrading, Modifying and Unlocking] AndyYan:
Roger. Take your time, this ain't priority stuff, and even if it doesn't succeed, it only means I'll stick with my current setup (temp root), no loss.
[Upgrading, Modifying and Unlocking] Be Jammin:
For method 2 I am getting stuck at step one:

Entering "adb shell dd if=/storage/external_SD/twrp_vXXXXX_fx3q_FR-OFF.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery"

results in "Error no such file or directory"

Root is installed and device show up under 'adb devices' I have the twrp.img on the sd card. I thought maybe the XXXXXX's were supposed to be replaced by the exact version number, but that didn't work either. Help is appreciated.
[Upgrading, Modifying and Unlocking] steadfasterX:
Have you renamed the twrp image to "twrp.img"??

If that is the case you need to replace:

adb shell dd if=/storage/external_SD/twrp_vXXXXX_fx3q_FR-OFF.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery

with

adb shell dd if=/storage/external_SD/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
[Upgrading, Modifying and Unlocking] Be Jammin:
I was just abbreviating, I didn't change the file name.
[Upgrading, Modifying and Unlocking] steadfasterX:
Ah ok ;)

Can you please execute the following:

adb shell mount

And:

adb shell ls-la /dev/block/platform/msm_sdcc.1/by-name/

.
[Upgrading, Modifying and Unlocking] Be Jammin:
My recovery partion is given at

lrwxrwxrwx root root 1970-01-04 10:24 recovery -> /dev/block/mmcblk0p17

So I tried editing your command into this

adb shell su dd if=/storage/external_SD/twrp_v2.8.1.0_build5_fx3q_FR-OFF.img of=/dev/block/platform/msm_sdcc.1/mmcblk0p17

Which seems to result in the file flashing, but when I reboot into recovery it just shows the broken android.
[Upgrading, Modifying and Unlocking] steadfasterX:
Well lets go one step back:

Boot into the normal ROM.

Then execute from your PC:

adb shell

Then (!!!):

su

Then (you should be root user now):

adb shell dd if=/storage/external_SD/twrp_vXXXXX_fx3q_FR-OFF.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery

(Replace it with the correct image name)

I think the "su" part was missing before and if you use the one liner you need "su -c" instead of "su" only.

Nevertheless please use the above steps and please paste the whole output.

.
[Upgrading, Modifying and Unlocking] Be Jammin:
This worked:

adb shell su -c dd if=/storage/external_SD/twrp_v2.8.1.0_build5_fx3q_FR-OFF.img of=/dev/block/mmcblk0p17

When I tried adb shell then su the device kept being unmounted for some reason.
[Upgrading, Modifying and Unlocking] steadfasterX:
So you can boot into twrp now?

.
[Upgrading, Modifying and Unlocking] Be Jammin:
Yes I followed the rest of the instructions successfully, thanks.
[Upgrading, Modifying and Unlocking] AndyYan:
[MENTION=5545101]xdajog[/MENTION] Any progress with the Enact? If you're too busy with other devices I might as well kiss my Enact goodbye and end the headache.

Sent from Google Nexus 6P @ CM13

[WARNING: XDA One have not implemented "mark forum as read" - do not use]
[Upgrading, Modifying and Unlocking] steadfasterX:
well I'm too busy with RL ;) but you have luck I had 30 minutes of free time today so try this one:

BACKUP your current recovery partition!!!!

If you do not know how find out by executing this from your pc (requires adb, see FAQ on the first thread page):

adb shell ls -la /dev/block/platform/msm_sdcc.1/by-name/

If this do not give back meaningful results (recovery obviously) try to find out like this:

adb shell ls -la /dev/block/platform/*/by-name

If all this not show your recovery partition you could use parted: http://xdaforums.com/showthread.php?t=2450045

when you find out the recovery partition backup it by the "dd" tool (see FAQ on the first thread page - adapt it to your Enact partition, of course)

Download the attached file and DO NOT unzip or open the file! It is a lokied / patched version of TWRP for the Enact already.

(The "LOG" extension is needed for uploading here as attachment only)

Flash the image file (by using dd again) to your recovery partition (again you need to know which / where your recovery partition is)

If you get stuck on dd backup or flashing of your recovery partition try to use /dev/block/xxxx123 (replace with the real device name) instead of "by-name".

Always use "adb shell

su -c

COMMAND" for any flashing or backup operations!!!!

Again I'm not a C coder like djrbliss who creates the loki tool for patching so the attached twrp image may damage your device or it simply does not work or... well ok.. and... it could also simply work - who knows ;)

Let us know your results, hints and everything else which could help other LG Enact users..

.
[Upgrading, Modifying and Unlocking] AndyYan:
And the result is... it simply doesn't work. When given the command to reboot to recovery, it will strangely boot into fastboot mode - I don't think fastboot is normally accessible for LG devices. Some lines will say fastboot started and connected, but no more than that - no options to choose except a manual reboot via fastboot command. I've restored the stock 3e recovery and things are back to normal.
[Upgrading, Modifying and Unlocking] steadfasterX:
That's funny :) For the F3Q I cannot go into fastboot!

But when you get into fastboot mode try the oem unlock command:

fastboot oem unlock

It would be really funny if that would work - if so you should see a disclaimer which needs to get accepted

.
[Upgrading, Modifying and Unlocking] AndyYan:
I can see what this implies, LOL.

This is the screen output on the phone when it first boots into fastboot:

Fastboot mode started
udc_start()
-- reset --
-- portchange --
fastboot: processing commands

And when I execute oem unlock:

C:\Users\CrossGate>fastboot oem unlock
...
OKAY [ 0.002s]
finished. total time: 0.003s

But I don't even need oem unlock! Even without unlocking I can flash a partition via this mode! :eek:

At least, I tried flashing the stock recovery I backed up previously, and guess what, it flashed successfully - I verified by rebooting into system and then into recovery again, and I see the 3e recovery :eek: What the hell is this...

So what possibility do we have under this situation? A modified system image?
[Upgrading, Modifying and Unlocking] steadfasterX:
What is "3e recovery"? I believe you mean the enact recovery right?

For flashing itself you do not need an unlocked device/bootloader but for booting a custom recovery or booting a custom kernel or custom ROM.

If you have an unlocked bootloader (you maybe(!) have one now - after the fastboot oem unlock cmd) you do not need a patched twrp image anymore because that one may not boot afterwards. If(!) You have unlocked the bootloader you need an unpatched twrp image only. I can upload it here in the next hours.

.
[Upgrading, Modifying and Unlocking] AndyYan:
3e recovery is what the stock recovery calls itself.

Even when I didn't run oem unlock (yesterday), I can still flash recovery images. It's just I can't boot into one, as I said before...

Waiting for your unpatched one. Still gonna use the DD method, or just use the (accidentally gained) fastboot mode?

Sent from Google Nexus 6P @ CM13

[WARNING: XDA One have not implemented "mark forum as read" - do not use]
[Upgrading, Modifying and Unlocking] steadfasterX:
ah ok ;)

unlocking has nothing to do with flashing. You can flash by fastboot with a locked bootloader this is not a problem but as you see you will not able to boot from custom images.

unlock means you will be enabled to boot custom (so unsigned) images.

you may can unlock by fastboot (if LG has implemented this / not preventing this). There may be a little chance that unlock works because the fastboot was entered by accident ;) so maybe LG may not prevent unlocking there.

Here you go: LG-ENACT_NOTPATCHED_twrp --> View attachment twrp_v2.8.1.0_build5_fx3q_FR-OFF.img.noloki.log

It doesn't matter. Try the one which works best for you and by the way: Could you please tell the full recovery partition name (/dev/block ....) ? would be good to know.

.
[Upgrading, Modifying and Unlocking] AndyYan:
Unfortunately we hit a wall on booting recovery:

------------------------------
Secure booting Error!
Cause : boot certification verify
------------------------------

The system boots just fine, and I can restore the stock recovery just fine.

I guess LG simply locked it without even implementing a proper unlock method (remember how oem unlock returned "..."?).

Full partition for your reference:

lrwxrwxrwx root root 1970-01-08 06:59 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-08 06:59 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-08 06:59 cache -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-08 06:59 drm -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-08 06:59 eksst -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-08 06:59 encrypt -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-08 06:59 eri -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-08 06:59 fota -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-08 06:59 fsg -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-08 06:59 grow -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-08 06:59 misc -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-08 06:59 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-08 06:59 modemst1 -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-08 06:59 modemst2 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-08 06:59 mpt -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-08 06:59 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-08 06:59 persist -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-08 06:59 rct -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-08 06:59 recovery -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-08 06:59 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-08 06:59 rpmbak -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-08 06:59 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-08 06:59 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-08 06:59 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-08 06:59 sns -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-08 06:59 ssd -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-08 06:59 system -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-08 06:59 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-08 06:59 tzbak -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-08 06:59 userdata -> /dev/block/mmcblk0p15

Recovery is still 0p17 - same codename, after all.
[Upgrading, Modifying and Unlocking] steadfasterX:
ok it is still locked. so we need loki here to "hack" the boot process in order to boot a custom recovery.

Thanks.

So to sum up the patched twrp version should have worked but it boots into fastboot. Strange enough but currently I have not the time to investigate this further sorry..

Maybe try to re-flash the patched (!) one by using fastboot :) That's one last resort..

.
[Upgrading, Modifying and Unlocking] AndyYan:
I have done just that last night, but it still goes into fastboot.

Don't worry, I guess I'll just sell this thing cheaply to someone else, so that we both don't get to deal with more Verizon cr@p. I'd not buy anything not confirmed to be unlockable from Verizon again.

Thanks button spammed :D
[Upgrading, Modifying and Unlocking] steadfasterX:
yeah really a crap. good luck with selling ;)

you make my day ;)
[8525, TyTN, MDA Vario II, JasJam General] jannen:
I just been starting taking pics more seriously with my Vario II. But npt until now when I tried take some portraits of friends (to add to my contacts) I see the pics Vario II takes are 'flat'. The porportions are not correct. So a skinny face looks fat etc.. I notice it now more and more. The only thing I can imagine is the lens is bad or something ... but guess not much I can do about it? Anyone else had this problem?

Its possible to edit the pics like Photoshop, but weird eh?
[8525, TyTN, MDA Vario II, JasJam General] MikeChannon:
Mmmm Not heard of this before. Yes you can edit pictures in the likes of photoshop but if its just to reshape a little, the bog standard paintbrush programme that comes with windows will do this using its "stretch and skew" function. You can change the horizontal stretch or compression independantly from the vertical.

Pressumably if you rotate the camera by 90 degrees you can make fat folks thin. "does my bottom look big in this?" Not with Jannen's Hermes. You'll be popular:)

Mike

Mike
[Huawei Ascend P6, Mate] ikroll:
Hello everybody , there are some problems in B634 but i fixed them.

This will fix that problems.

- FMRadio

- Audio Output

- Hide Virtual Keys button

- Fixing lag at opening animation

- Others

Firstly you have been rooted and you will need Root Explorer [Pro] and try it at your own risk.

Open Root Explorer [ Pro] then open

cust

folder and delete everything in this folder.After that copy everything in

Cust

folder which you downloaded.

Note : If you are living other regions then just edit folder name in cust folder which named "neeurope" to your region.

Here regions list : in , mdasia , mdeast , namerica , nlamerica , northafrica , ru , samericas , seasia , spacific and weurope.

Cust (New) : http://www30.zippyshare.com/v/97420499/file.html

Open Root Explorer [Pro] then open

data/cust

folder and delete everything in this folder.After that copy everything in

Cust-Data

folder which you downloaded.

Cust-Data : http://www24.zippyshare.com/v/74777576/file.html

If there is no animation while opening then do this solution.

Open Root Explorer [Pro] then open system folder and copy media folder which you downloaded and apply all changes.This will fix your problem too.

Media : http://www67.zippyshare.com/v/73069715/file.html
[Huawei Ascend P6, Mate] blueIBI:
is the fmradio fix necessary?

what is the problem about audio output?

virtual keys hide option like in the proper versions (by tweaking build.prop)?

Gesendet von meinem P6-U06
[Huawei Ascend P6, Mate] ikroll:
- Somebody ask about radio and others so i did it.

- B634 has audio limit because there is a law about audio output for people's health in Turkey .

- Hide virtual keys does not appear with editing build.prop in B634.There are two way fixing hide virtual keys first is mine and other way is editing with SQLite Editor application.
[Huawei Ascend P6, Mate] blueIBI:
ok..so no problem in usual sense..just law limitations like in germany/europe in general..

Gesendet von meinem P6-U06
[Huawei Ascend P6, Mate] viskerelv:
I have stock B634 and i don't have any audio limits. FM radio also working.
[Huawei Ascend P6, Mate] ikroll:
Some regions have this problems for example when you use headset , system limits audio output about %60 in Turkey and it is really bad because you cannot hear any sounds if you have simple headset.

I am using high-end headset which i made it myself therefore it does not matter for me but you know , there are a lot of people using simple headset so they will need this solution :)
[Huawei Ascend P6, Mate] Ottomaani0:
Thank you! But cust-data link doesn't seem to work for me?

Edit: Seemed to be a problem with Zippyshare, working now :)
[Huawei Ascend P6, Mate] ikroll:
It is working , try again :)
[Huawei Ascend P6, Mate] Ottomaani0:
Yeah, just Edited my post :P

---------- Post added at 10:55 AM ---------- Previous post was at 10:43 AM ----------

My bootanimation is gone, only Android text now. Is it normal? Not a big deal for me but just wanted to know :)
[Huawei Ascend P6, Mate] ikroll:
This is unusual so i am going to look for what is going wrong.I'll repost tonight or tomorrow.
[Huawei Ascend P6, Mate] Bloobik:
Same here, huawei bootlogo is gone, only Android, no hide virtual keys button, just get FM radio, but my phone is in Orange Poland, so I think this is a problem.
[Huawei Ascend P6, Mate] antmatr:
Dear ikroll, in fact I have the B513 that I find good in everything. The only problem, in my opinion, is the audio for phone calls (in music instead everything is ok, I use Viper4Android FX). But, in my opinion, the phone calls (capsule and speaker) have a volume that can be increased. Could you tell me what are the parameters to be changed? And in what files (system setting.db?)? Thank you!
[Huawei Ascend P6, Mate] ikroll:
New Cust File For Europe

Hello everybody , i fixed opening animation and i have to say that i am sorry that was my fault because i have added wrong cust file for europe and i changed it now.Although you can do everything if you still have same problem , i added a solution for that too.
[Huawei Ascend P6, Mate] Ottomaani0:
Could someone try if they can use speaker in call? I tried today but my friend said he can hear only static.

We tried a few times.

I'm trying to pin out what caused this before reflashing whole rom.
[Huawei Ascend P6, Mate] hama2:
Big Problem : no folder /cust/ in folder data only /cust/ in head of root
[Huawei Ascend P6, Mate] mlsvcbbn:
DOWNLOAD THIS bootanimation.zip https://mega.co.nz/#!Al0nFQAK!caZNFPdrIqlUlhcpxi2UbVQjQfxK_7E2d-dNCX0jXmM

copy to SD CARD and then move or copy with root browser or root explorer to SYSTEM---MEDIA....reboot phone and bootanimation will apear.

---------- Post added at 11:18 PM ---------- Previous post was at 11:07 PM ----------

you can set sound volume from SQLITE EDITOR too as well as hide navigation key.
[Huawei Ascend P6, Mate] Stefan662:
I also update to B634 but only the first part.

The folder structure in the /cust/ folder is very different to your cust.rar.

On my P6 I have:

/cust/hw/

/cust/lost+found/

/cust/vodafone/

In /cust/vodafone/ there are folders for different languages (au, cy, cz, de...).

Is it save to paste your cust onto my P6?
[Other SmartWatches] simple1i:
Greetings All,

If you all would be kind enough to post any smartwatch clones and Shenzhen types.details here, so its easier to find. Its seems that some clones are actually better the the 'original' ones :D

You may either post all the info here or just the link to the watch and the rest in your own post.

Thanks.
[Other SmartWatches] atti_clearw:
It is a shame when somebody asking something, and nobody answer... I can't because I am in the same shoes , I am looking for one, but come on guys I can't believe it nobody unable to answer...
[Other SmartWatches] simple1i:
Most of the above mentioned watches are already posted in the 'Other smartwatch' section, so you'll have to trawl thru the threads and posts to find the info, it takes a while and somtimes puts people off, some of the watches are not even noticed so informed choices can't be made ...sometimes.

That's why it would be easier to just briefly mention it here and then add a link to the post.

Its be also very helpful if all the key info (such as new firmware, steps to rooting, important news ...etc) would be re-add/updated to the first post so it can be accesses easily.

But i understand it generates more work and people are busy.