yashsingh1/xdaforums huggingface dataset:
[Huawei MediaPad, T-Mobile SpringBoard] xan1242:
You should dd using the ones in "by-name" since it's kind of broken or just use TWRP.

Besides, it seems it's just the addresses there for the kernel, the rest is padding.

http://puu.sh/fhpXv/45b3326285.7z

Check this file out and tell me if it differs from yours. If it does in any case, then there are the addresses for the kernels in the other two partitions. If not, then it's something else I don't know about. I don't think I've ever touched this file even.

By the way, the ROM I'm using is this one:

http://4pda.ru/forum/index.php?showtopic=395683&st=840#entry23349533

It's based off of the stock one and it's basically just a cleaned up ROM. Only thing is you'd need to survive through is the Russian. To fix that you just need to get MoreLocale and change the languages.

There you can find some info about flashing 'n' other stuff.

I just looked into the images from the ROM as well - misc is just random padding again, kernel is the same thing I got and the partition table is defined in a single file called parameter. You can edit that file with any text editor.

There you will find the CMDLINE where the partition table is defined as well under mtdparts.

parameter

FIRMWARE_VER:0.2.3
MACHINE_MODEL:MediaPad 7 Lite
MACHINE_ID:007
MANUFACTURER:HUAWEI
MAGIC: 0x5041524B
ATAG: 0x60000800
MACHINE: 2929
CHECK_MASK: 0x80
KERNEL_IMG: 0x60408000
COMBINATION_KEY: 0,6,A,1,0
CMDLINE: quiet console=ttyS1,115200n8n androidboot.console=ttyS1 init=/init initrd=0x62000000,0x800000 mtdparts=rk29xxnand:0x00002000@0x00002000(misc),0x00004000@0x00004000(kernel),0x00008000@0x00008000(boot),0x00008000@0x00010000(recovery),0x00002000@0x00018000(backup),0x00006000@0x0001a000(oeminfo),0x00004000@0x00020000(vrcb),0x00008000@0x00024000(reserved),0x00100000@0x0002c000(cust),0x000e6000@0x0012c000(system),0x00080000@0x00212000(cache),0x00008000@0x00292000(userdata),0x00002000@0x0029a000(kpanic),-@0x0029c000(user)

Format is

length@offset
[Huawei MediaPad, T-Mobile SpringBoard] :
xan1242

I wish I knew this early as I had made a number of flashing with modified TWRPS, all not booting and always thought it was just me not being good enough to know what I am doing with a Rockchip.

So I plan to redo one of my better efforts just to see if it boots later.

2) I downloaded and inspected your file here

md5sum kernel.img
c497d0e079117e8a08c3e3894237811d kernel.img
gordon@asus:~/Downloads$ ls -al
total 8208
drwxr-xr-x 2 gordon gordon 4096 Feb 1 06:53 .
drwxr-xr-x 21 gordon gordon 4096 Feb 1 06:45 ..
-rw-rw-r-- 1 gordon gordon 5529 Feb 1 06:53 kernel.7z
-rw-rw-r-- 1 gordon gordon 8388608 Jan 31 23:10 kernel.img

strings kernel.img gives me
RKOEM10
RKOEM10

That size looks to me to be padded already. As the size/ erase size from stock mtd output is

the 8 number I believe means 8 megs or 8 x 1024 x 1024 = 8388608 bytes and so we agree

but it does not help me know if we have same kernel or not sorry. Can you at least tell me what kernel version the Russian ROM is please?

I use Linux tool imgrepackerrk from here

http://xdaforums.com/showthread.php?t=2257331
[Huawei MediaPad, T-Mobile SpringBoard] :
ignore my next bit.....its just a whine by me.....after I pull my fist out of the monitor

I have found 3 main methods.....ignoring adb....to flash recovery from within normal bootup

dd if=newimagename of=/dev/mtd/md3

dd if=newimagename of=/dev/block/mtd/by-name/recovery

dd if=newimagename of=/dev/block/mtdblock3

I have also apppended those lines with bs=512 count=32768, giving a total of 6 commands

all of them show output of records in matching records out

but I am not getting recovery on boot up for any of them, consistenly so sorry if that looks bad.

2) it may be that I have been long pressing to turn off on failure and other pressing buttons.......that my device is spanking me for treating it without respect

b) but then if what I just said is true, this device is unreliable. I mean no great disrespect here either as it only costs A$50 in australia

end of grumble
[Huawei MediaPad, T-Mobile SpringBoard] :
ok so had modest success on a TWRP mod and flash using mtd3 method

the working bits are in images hidden, the really bad bits I am too shy to show but mount is not getting access to my fstab entries such as for system which in showing as 0 MB to backup

Yes.....thats not good.

Also I added some more flags to show more options in the mount area of TWRP but inserting usb-otg after boot or on reboot.....does not allow me to CHECK the box and mount it.

In first image, removeable sdcard means the microsd card you push into slot and the bottom entry is for OTG, I might amend the flags later but only when I resolve the fstab to mount issue.

working fstab entry is

/sdcard2 vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0 flags=display="removeable sdcard";wipeingui;storage;removable;backup=0

OTG failure line is currently

/usb-otg vfat /dev/block/sda1 flags=display="USB Storage";storage;wipeingui;removable

and yes I must make that auto instead of vfat

system faulure line is attempt to use block style and yes I must try by name

/system	ext4 /dev/block/mtdblock9 flags=display=system;wipeingui;backup=1

Drat I should I think remove wipingui for sdcards

#######################

heck I think I just found a gremlin?

in normal boot up the command

cat /proc/mtd

gives me the mtd list including this line

mtd9: 1cc00000 00004000 "system"

looks good but we know that our current TWRP has this entry for its fstab line

/system	ext4	/dev/block/mtdblock10

WT?

well I know and am fairly sure pogs24ever has done a TWRP backup and restore so mtd10 must be for system and not mt9

only way to confirm is for me to try a new image with corrected fstab
[Huawei MediaPad, T-Mobile SpringBoard] :
well well well

lets go and have a peek at the current TWRP backup log created when doing a backup. I backed up only boot, data and system

Q If anyone thinks I should back up more, please say so.

############

now let me focus on mtd.....which I know scant about.....in normal boot up......recovery is mtd3

in twrp log its not the same!!

and others also have changed. so frustrated I am with this blinkin mtd system I thought I would share a link to my log and maybe some kind soul can tell me where to go.....LOL

https://www.dropbox.com/s/xa6uy8f4akauffo/twrp-current-recovery.txt?dl=0

if not thanks for reading.

Just to repeat ......this is the current TWRP not my mod as my mod contains more errors than current.
[Huawei MediaPad, T-Mobile SpringBoard] pogs24ever:
Hi Guys...

You can check my conversation with abdul on his page... here's the first page........ http://www.freaktab.com/showthread.php?10466-Unofficial-TWRP-2-7-0-0-for-Rockchip-s/page4
[Huawei MediaPad, T-Mobile SpringBoard] :
pog2rever

I can see your recovery log from that other site.......so in case it helps others let me take a snip from yours that our friend also saw at post 95, page 5

now from our post 5.....with a normal boot up, I used cat /proc/mtd giving us

I still have no idea why a twrp boot up uses different numbers from our normal boot up.

I am now forced to use a "by-name" etc/recovery.fstab, but have yet to resolve USB-OTG

################

adbul_pt discusses some of this issue at post 100,

at post 126 it is claimed TWRP does not support fuse........I can see on normal boot /dev/fuse so will have to check that out later.

thanks for reading
[Huawei MediaPad, T-Mobile SpringBoard] :
hi

Having read 60 odd pages at freaktab I have a new test, for USB-OTG

boot current TWRP, insert usb stick into hub and hub into OTG cable into device

check mount and try to check the box for usb storage.....fails

choose right hand side, it names a storage device and changes to a dialog box........usb storage shows as 0 Mb......result ......fails

Altho this is no better than my earlier report, until someone says they have succeeded with OTG storage..............I think I have done enough testing of this and my brain hurts (joke)
[Huawei MediaPad, T-Mobile SpringBoard] xan1242:
Sorry for not replying, been a bit busy. ;V

I'll upload the recovery dump now. I have some files on my computer too (ramdisk and other stuff) so if you want those too I'll send em too.

EDIT: Link

http://puu.sh/fsBNP/4789c249eb.zip

This is the recovery I use. It really wasn't too hard to make. I even think I took the one for RK3xxx. Only bad things are - no internal SD and it's upside down lol
[Huawei MediaPad, T-Mobile SpringBoard] :
i tried a CWM and found it upside down

repacked with this string in default.prop

ro.sf.hwrotation=180

still upside down.....have not had a chance to look at your recovery but assume its based on the generic rk2918?

cheers
[Huawei MediaPad, T-Mobile SpringBoard] xan1242:
My pack is based on abdul's RK292x recovery since there wasn't any 2918 based with 1024x600 resolution.

On another note - I think the etna_viv driver can be ported to the Mediapad 7 Lite as the developer himself has a RK2918 based tablet. I think it's better than the regular Vivante driver. Apparently it handles things horribly and you can see it in games such as Table Top Racing or some games/3D apps not running at all such as Epic Citadel, which is quite disappointing. Besides games and apps, I think it can benefit the latest of CWM recoveries since the framebuffer didn't get updated at all when I ran it (and I'm not sure even if it ran since I need serial pins for that, I do own a RS232 interface though).

EDIT: I actually found the original image file I used. Instead of the link above (which has the extra unnecessary padding) use this one;

http://puu.sh/fta8X/824844a344.img
[Huawei MediaPad, T-Mobile SpringBoard] :
my apols on name of recovery I modded for CWM, I downloaded RK29GENERIC_CWM.zip

capitals are in name, I am not trying to shout.

I modded it with our kernel, modded default.prop and fstab and some minor things

I have taken the liberty of uploading mine mod here

https://www.dropbox.com/s/kh2ebfgmuu39yxv/cwm.img?dl=0

my mod is 5.7 Mb but I repeat I did not do any testing as it was upside down.

I did have a peek at your unpack and this was enjoyable after a long day......his default.prop

2) I have not had time to play many games on tablet so won't investigate video driver at this stage thanks

cheers

##################

rant starts

I decided to make a mod of our current TWRP making a change to just the default.prop.....NO other changes

Do you think any of my flash methods works..............nope.....booted up terminal proves I am in read-write mode

dd command shows records in match records out

reboot into recovery.......blank screen

I am running out patience with this device.......and yes I always check I have at least 60% battery.

end of rant
[Huawei MediaPad, T-Mobile SpringBoard] :
xan1242

I also note that your fstab in CWM is similar to TWRP but I know you don't have time to test USB-OTG, so this is just put out there for others to comment on

here is the line

I believe it should swap sda1 with the sda string, but I have failed to get anything in recovery mode in TWRP.
[Huawei MediaPad, T-Mobile SpringBoard] :
I have had a lot of trouble trying to flash recovery so grrrrr

anyhow I now have USB_OTG working on a modded TWRP using this fstab line

Naturally in init.rc you need a mkdir line that has "mkdir /usb-otg"

some images as proof of mount and then file manager peeking into usb stick mounted thru OTG cable.....just like normal boot up

bottom line....one happy camper

first you need to touch mount and the touch the usb-otg radio button

then you can go into advanced and file manager if you want to check it

I can't share this mod at the moment as I want to do lots more......and have yet to test other stuff.

thanks for reading

EDIT

lost mount of internal storage possibly becaused I forced otg onto sda1......will change otg to sdc1 when I get a flash to work again
[Huawei MediaPad, T-Mobile SpringBoard] :
never able to get both OTG and internal working on the same build so OTG now deleted from fstab and init.rc

work in progress still has issues.

EDIT AS PER NEXT POST

I had hoped by removing some security app rc files I would no longer see multiple lines in my log such as

but this is a fail for me as is attempt to reload adb in LInux to fastboot when TWRP running

thanks for reading
[Huawei MediaPad, T-Mobile SpringBoard] :
ok so I put current TWRP back and did a factory reset......reboot still takes ages

roughly 5 minutes not 5 hours and it worked.

so put back my mod and did the same thing and its all good.
[Huawei MediaPad, T-Mobile SpringBoard] :
it was bound to happen I suppose?

I attempted to do a ROM mod but build it by tarring the system unpack etc.

it did not work, I was able to get back into TWRP and attemped an advance wipe to clear everything but still no good.

as this device is....um....a piece of junk.....I spent only milliseconds before opting to throw in bin.

good luck to others, I have a new phone so it is getting all my attention now.
[XDA Assist] :
I have a nokia lumia 925, about a month ago when i put the speaker on to speak to friends they could not her me, I could clearly here them but not the other way round. Now even with the speaker off when I make a call I can hear them but they cannot hear me, I have applied some updates, done a soft reset and still not fixed the problem anyone help??
[XDA Assist] It_ler:
Do you mean the phone's speakers or external speakers?

If external then check if they work with other phones.

And make sure to adjust the volume to maximum ... for testing.

If they work with other phones or you mean the phone's speakers, then it could be a hardware issue.

Best to ask in the Lumia 920 Q&A, Help & Troubleshooting forum, as your device is very similar to the 920. You just need to register on xda before.
[Xperia Z3 Q&A, Help & Troubleshooting] Hani88:
anyone successfully rooted Xperia Z3 D6653 with Giefroot ???

many people said that's only working on D6633 and D6603...

because I'm gonna buy this phone in the upcoming days and waiting for this info
[Xperia Z3 Q&A, Help & Troubleshooting] SwooshICE:
Yes works on D6653
[Xperia Z3 Q&A, Help & Troubleshooting] freddy1991:
Totally working

But with .93 ftf only
[Xperia Z3 Q&A, Help & Troubleshooting] Jstar22:
How to downgrade from .77 to .93.? I cannot find D6653 singtel .93 fw.
[Xperia Z3 Q&A, Help & Troubleshooting] rafhagunz:
i have a D6633 (z3 dual) and cant root with locked boot loader( last firmware)
[Xperia Z3 Q&A, Help & Troubleshooting] freddy1991:
Use Xperiafirm to download
[Upgrading, Modifying and Unlocking] bteljuice2:
plz can anyone link me to download the WM6 for JasJam?

thx a lot.appreciate it.
[Xperia Z3 Q&A, Help & Troubleshooting] kelvin99:
Hello Guys.. since I'm a nexus 4 user before...not familiar with this new phone want to ask if using Giefroot and successfully root my phone Can I still do a system update specially when lollipop comes..without any issues? my rooting purpose: just want to install root apps like titanium back up to uninstall bloatwares, greenify without xposed installer...
[Xperia Z3 Q&A, Help & Troubleshooting] freddy1991:
You will be notified by update center when Lollipop update is available even if your device is rooted or not, but not sure about if you will be able to install the system update or not.

I had seen some rooted devices could download the OTA but failed to install the update.

But there's nothing to worry since you can always flash the ftf file via flashtool, without wiping any of your data..
[Xperia Z3 Q&A, Help & Troubleshooting] kelvin99:
I can install any ftf.file right as long as it is for my device..also when ota is available the ftf. File is also release right?
[Xperia Z3 Q&A, Help & Troubleshooting] gregbradley:
Yes, someone will make and upload an FTF.

In an extreme circumstance it may need Flashtool to be updated, but Androxyde will do that and push another version.

In the meantime, you can always relock your bootloader and use PCComapnion to update officially, then unlock the boot again
[Xperia Z3 Q&A, Help & Troubleshooting] freddy1991:
You can also use Xperiafirm to dowload the ftf files.
[Xperia Z3 Q&A, Help & Troubleshooting] 3Shirts:
Doesn't the root process require downgrading though? So it'd make updating through PCCompanion redundant.
[Xperia Z3 Q&A, Help & Troubleshooting] gregbradley:
Not really, if you have an unlocked bootloader you can relock, upgrade, unlock, flash an insecure kernel**, flash SuperSU and you are done. no need to downgrade, that's a locked bootloader method.

**Someone will upload an advanced stock kernel within minutes of it hitting our devices, its not much of a tweak to make it insecure

(Just changing a 1 to a 0 in the right place)

Hell, they may even throw in recovery in a couple of minutes as well....
[Xperia Z3 Q&A, Help & Troubleshooting] 3Shirts:
Yes but I was replying in the context of the OP who said 'using giefroot' so I assume it's the locked bootloader method he is asking about.
[Moto E Q&A, Help & Troubleshooting] DummieZ:
Help! I just installed CM11 on my MOTO E and it doesn't read the SIM Card. Is there any way I can revert it to stock firmware? I don't have the Dual Sim one.
[Moto E Q&A, Help & Troubleshooting] Rohitagni:
This will help you.

http://xdaforums.com/showthread.php?t=2756609

Hit thanks if I helped u.
[Xperia Z Original Android Development] HeisenbergBB:
Some screen?
[Xperia Z Original Android Development] bhupalraut:
Let's Test

Let's flash it ;)
[Xperia Z Original Android Development] Daedroza:
I will port this to Xperia ZR. Waiting for official builds to be released for Xperia Z and ZR!
[Xperia Z Original Android Development] comax70:
Please report crash UI...other cm12 crash

---------- Post added at 09:42 PM ---------- Previous post was at 09:41 PM ----------

30 build
[Xperia Z Original Android Development] iKillCypher:
Push 10.5.1.A.0.292 Blobs For

https://github.com/TheMuppets/proprietary_vendor_sony/tree/cm-12.0/yuga

Thanks.
[Xperia Z Original Android Development] qsnc:
if you think it's worth it (and you actually have the illusion that updating blobs is just copying over some files), then please go ahead and do it, test it, and create a pull request. other than that, i would be thankful if you stop nagging me (and other devs) about it in forums, gerrit, and on irc.
[Xperia Z Original Android Development] macia10:
Hmm review.cyanogenmod.org/#/c/86923/ merged on jan 26
[Xperia Z Original Android Development] qsnc:
that's my commit, yes. he is talking about blobs, though, not the kernel patches.

anyway, it would be helpful if you guys could test this and report back with things that aren't working.
[Xperia Z Original Android Development] iKillCypher:
qsnc

I will test most of your updates for now I need you set selinux to enforcing. yes push blobs 10.5.1.A.0.292 Blobs since you have updated the kernel code based on sony.

after that we can hudson yuga to nightly :) same for odin :)

[MENTION=5145127]qsnc[/MENTION]

there are random reboot happening for yuga, possible due to the kernel changes you did, It seems to be affecting after 28 builds

also you seems to have set the selinux to enforcing there are some permission and denial you need to look at it seems to have messed up the base band etc
[Xperia Z Original Android Development] MafiaManV:
Started using this as a daily . Really nice job dev. Chrome beta sometimes crashed but it's not bothering me that much..

Is a solution to a working BT audio close :) ?
[Xperia Z Original Android Development] Hexchain:
Mobile signal & data works, but not after enabling SELinux. Currently waiting for build with new policy update.

UPDATE: codereview 87608 and 87609 fixes mobile signal and data, but no "3G" or "H+" on top right corner. There is network activity indicators, though.

Cannot hear or speak in call, even after applying http://review.cyanogenmod.org/#/c/86943/ .
[Xperia Z Original Android Development] qsnc:
http://review.cyanogenmod.org/#/c/86943/ also needs changes in the hal: http://review.cyanogenmod.org/#/c/86942/, that should help with in-call audio... policy update is on the way.
[Xperia Z Original Android Development] Hexchain:
Do I need to switch hardware/qcom/audio/default to cm-12.0-caf-8960 branch before cherry-picking this change?

EDIT: nvm, found the correct path. Building.

EDIT2: 86942 and 86943 fixed calling issue!

EDIT3: userinit does not function due to selinux.

from /data/misc/audit/audit.log:

type=2000 msg=audit(1.010:1): initialized
type=1403 msg=audit(1422959102.743:2): policy loaded auid=4294967295 ses=4294967295
type=1404 msg=audit(1422959102.763:3): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295
type=1400 msg=audit(1422959111.141:4): avc: denied { execute } for pid=273 comm="logwrapper" name="busybox" dev="rootfs" ino=4489 scontext=u:r:sysinit:s0 tcontext=u:object_r:rootfs:s0 tclass=file op
_res=-13 ppid=272 pcomm="logwrapper" tgid=272 tgcomm="logwrapper"
type=1400 msg=audit(1422959111.141:5): avc: denied { read } for pid=273 comm="busybox" name="userinit.d" dev="mmcblk0p26" ino=718083 scontext=u:r:sysinit:s0 tcontext=u:object_r:system_data_file:s0 t
class=dir op_res=-13 ppid=272 pcomm="logwrapper" tgid=272 tgcomm="logwrapper"
type=1400 msg=audit(1422959111.151:6): avc: denied { write } for pid=275 comm="setprop" name="property_service" dev="tmpfs" ino=5902 scontext=u:r:sysinit:s0 tcontext=u:object_r:property_socket:s0 tc
lass=sock_file op_res=-13 ppid=271 pcomm="90userinit" tgid=271 tgcomm="90userinit"
[Xperia Z Original Android Development] qsnc:
make sure you pulled in all the latest updates, especially http://review.cyanogenmod.org/#/c/87609/

should you still have trouble booting, please post it, and ill update the sepolicy.
[Xperia Z Original Android Development] Hexchain:
No problem with 87609, because before this I have completely no radio. Phone boots, only custom init scripts (in /data/local/userinit.d, called by /system/etc/init.d/90userinit) isn't invoked at all due to SELinux denials.

Here is the script content if relevant (something like MarketEnabler to enable Google Play Service Location Reporting): https://gist.github.com/hexchain/f4c8a3583abe0214922a

Some other minor problem:

Carrier name does not show on lockscreen left up corner (see attachment), and sometimes there is "No service. - <actual carrier name>".
[Xperia Z Original Android Development] qsnc:
you have something funky in your init scripts... because in the "stock" cm12 init scripts, i removed all calls to logwrapper... are you using old scripts or have you modified them in some way?

the userscript does seem to get invoked, as you can see by the setprop denial it "only" is denied access to set a property... you can find out which exactly by searching for the inode on your phone... anyway i am not aware why a "fake carrier id" script should be required? then again, i dont even have a yuga...
[Xperia Z Original Android Development] Hexchain:
Thanks for the quick reply, and thanks for maintaining CM for yuga!

There are still calls to logwrapper: https://github.com/CyanogenMod/andr...2.0/prebuilt/common/etc/init.d/90userinit#L13

The setprop denial is for line 14, relevant file is /dev/socket/property_service. If it really was in my script, there should be 4 denials instead of 1.

As I've said, Location Reporting is disabled by Google in my region (by detecting carrier MCCMNC) so I need this to make it available.

Again, thank you for maintaining CM for yuga!
[Xperia Z Original Android Development] SuperHanss:
Can any CM12 users confirm WiFi disconnecting during deep sleep? I need to know if it's my derp or not :p
[Xperia Z Original Android Development] hutilicious:
it does. but Im kinda used to it, as I got the same problem in CM 11. But this time it seems to happen more frequently. Cant find the option "Wifi Optimization" anymore in CM 12. Disabling it in CM 11 fixed it.
[Xperia Z Original Android Development] TheAvngrZ:
I'm wondering evry time, why my yuga gets that extremly warm, when using camera, installting and booting new rom and so on.. :/