It seem impossible to find any useful root tools for the Huawei Nova (EU edition).
This thread is in hope to collect some more info on this device, in order to give people better instruction on how to Root it.
Getting the boot-loader unlocked is easy as its unlock code is given by Huawei, and described
elsewhere. (1st 6 steps.) The problem appears to be to find an easy and persistent method for
root. It is very possible that I have missed something as I have not had much time to look
around very hard. So any input and links would be greatly appreciated.
If you do find the FULL firmware, please upload it and post a new link. It seem that most links I've found are
either fake, behind a long chain of ad-walls or on Chinese hard to navigate websites.
First of all the phone (I am interested in) has the following Firmware properties:
Code:
[ro.build.cust.id]: [CAN-L11C432B100CUSTC432D004]
[ro.product.fingerprintName]: [HUAWEI-MILAN]
[ro.product.CustCVersion]: [C432]
[ro.product.CustDVersion]: [D004]
[ro.product.board]: [CAN-L11]
[ro.product.hardwareversion]: [HL1CANL01M]
The update available so far is incomplete since it's an OTA to patch and resolve some
minor issues. So don't take it. Other OTAs can be found with this tool.
The processor (MSM8953) is exactly the same as for the following devices:
Code:
Asus Zenfone 3 (ZE520KL)
Asus Zenfone 3 (ZE552KL)
Asus Zenfone 3 Deluxe 5.5"
Huawei G9 Plus
Huawei Nova
Huawei Nova plus
Lenovo Vibe P2
Motorola Moto Z Play
Oppo R9s
Qiku 360 N4S
Samsung Galaxy C7
Samsung Galaxy On7 (2016)
Vivo X9
Xiaomi Redmi 4 Prime(32GB)
ZTE Axon Max 2
ZTE Axon 7 MAX
This means, that anything root that works on these, may also have a better success on this device.
But be careful, since these are just common names of devices and not exact model numbers!
For the bootloader unlock you need to provide this info:
Code:
Product Model: [ro.product.model]:
Product Serial number* [ro.boot.serialno]:
Product IMEI || MEID: (*#06#):
Product ID: (*#*#1357946#*#*):
All it takes is for someone to compile twrp. Knowing the differences in the models is important. I am in China so looking at the 64g internal 4gb memory. It is listed as CAZ-AL10. The partitions seem different, as the twrp developed does not support other models. Build it with you partition breakdown and it will work.
wangdaning said:
All it takes is for someone to compile twrp. Knowing the differences in the models is important. I am in China so looking at the 64g internal 4gb memory. It is listed as CAZ-AL10. The partitions seem different, as the twrp developed does not support other models. Build it with you partition breakdown and it will work.
Click to expand...
Click to collapse
Yeah, I was thinking to do that since nobody else seem interested, but since I'm not rooted yet, I can't even get a proper partition layout as standard partition layout "by-name" is unreadable for non-root, at least not from simple shell. Is your device using the same processor (see my post above)? (I doubt it.) However, it was compiled with kernel debug fs, so perhaps something can be used there. I was also asking elsewhere if we can use the recent full AOS 7.0 (EMUI 5.0) update posted by @lgstoian and use it to build TWRP also for the original 6.0 (EMUI 4.1)?
By the way, where does Huawei post their sources? And who to contact to make them post it? Do they normally comply with open-source requirements?
The partition table seem to look as follows:
Code:
$ cat /proc/partitions
major minor #blocks name
254 0 524288 zram0
179 0 30535680 mmcblk0
179 1 512 mmcblk0p1
179 2 512 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 256 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 256 mmcblk0p6
179 7 256 mmcblk0p7
179 8 256 mmcblk0p8
179 9 512 mmcblk0p9
179 10 512 mmcblk0p10
179 11 2048 mmcblk0p11
179 12 256 mmcblk0p12
179 13 8192 mmcblk0p13
179 14 256 mmcblk0p14
179 15 256 mmcblk0p15
179 16 256 mmcblk0p16
179 17 65536 mmcblk0p17
179 18 4096 mmcblk0p18
179 19 4096 mmcblk0p19
179 20 4096 mmcblk0p20
179 21 163840 mmcblk0p21
179 22 1 mmcblk0p22
179 23 8 mmcblk0p23
179 24 16384 mmcblk0p24
179 25 32 mmcblk0p25
179 26 16 mmcblk0p26
179 27 8192 mmcblk0p27
179 28 11264 mmcblk0p28
179 29 4096 mmcblk0p29
179 30 81920 mmcblk0p30
179 31 81920 mmcblk0p31
259 0 81920 mmcblk0p32
259 1 1024 mmcblk0p33
259 2 262144 mmcblk0p34
259 3 7168 mmcblk0p35
259 4 65536 mmcblk0p36
259 5 65536 mmcblk0p37
259 6 512 mmcblk0p38
259 7 512 mmcblk0p39
259 8 32 mmcblk0p40
259 9 512 mmcblk0p41
259 10 1024 mmcblk0p42
259 11 32768 mmcblk0p43
259 12 512 mmcblk0p44
259 13 4096 mmcblk0p45
259 14 128 mmcblk0p46
259 15 128 mmcblk0p47
259 16 256 mmcblk0p48
259 17 256 mmcblk0p49
259 18 8 mmcblk0p50
259 19 16384 mmcblk0p51
259 20 524288 mmcblk0p52
259 21 3788800 mmcblk0p53
259 22 25178095 mmcblk0p54
179 32 4096 mmcblk0rpmb
253 0 3758932 dm-0
253 1 520124 dm-1
253 2 25178079 dm-2
But we need the correct mapping to the files as given in the full update.
They usually drop their sources here for international : http://consumer.huawei.com/en/support/mobile-phones/index.htm and here for chinese : http://consumer.huawei.com/cn/support/mobile-phones/index.htm
From what I saw they pop up there 2 - 3 months after the phones launch date.
Looking forward for the root of the Huawei nova urgently. I think it needs more time for this newly device to get one great dev to compile twrp and get a root method to work.
I just switched from HTC 10 to nova and I'm very impressed. Huawei emui did so much better than HTC.
Everything is working out of the box and looks great. The only thing I really miss is root for using adblock and a network speed indicator.
Getting my popcorn bowl !! :laugh:
Nova Plus
E:V:A said:
It seem impossible to find any useful root tools for the Huawei Nova (EU edition).
This thread is in hope to collect some more info on this device, in order to give people better instruction on how to Root it.
Getting the boot-loader unlocked is easy as its unlock code is given by Huawei, and described
elsewhere. (1st 6 steps.) The problem appears to be to find an easy and persistent method for
root. It is very possible that I have missed something as I have not had much time to look
around very hard. So any input and links would be greatly appreciated.
If you do find the FULL firmware, please upload it and post a new link. It seem that most links I've found are
either fake, behind a long chain of ad-walls or on Chinese hard to navigate websites.
First of all the phone (I am interested in) has the following Firmware properties:
Code:
[ro.build.cust.id]: [CAN-L11C432B100CUSTC432D004]
[ro.product.fingerprintName]: [HUAWEI-MILAN]
[ro.product.CustCVersion]: [C432]
[ro.product.CustDVersion]: [D004]
[ro.product.board]: [CAN-L11]
[ro.product.hardwareversion]: [HL1CANL01M]
The update available so far is incomplete since it's an OTA to patch and resolve some
minor issues. So don't take it. Other OTAs can be found with this tool.
The processor (MSM8953) is exactly the same as for the following devices:
Code:
Asus Zenfone 3 (ZE520KL)
Asus Zenfone 3 (ZE552KL)
Asus Zenfone 3 Deluxe 5.5"
Huawei G9 Plus
Huawei Nova
Huawei Nova plus
Lenovo Vibe P2
Motorola Moto Z Play
Oppo R9s
Qiku 360 N4S
Samsung Galaxy C7
Samsung Galaxy On7 (2016)
Vivo X9
Xiaomi Redmi 4 Prime(32GB)
ZTE Axon Max 2
ZTE Axon 7 MAX
This means, that anything root that works on these, may also have a better success on this device.
But be careful, since these are just common names of devices and not exact model numbers!
For the bootloader unlock you need to provide this info:
Code:
Product Model: [ro.product.model]:
Product Serial number* [ro.boot.serialno]:
Product IMEI || MEID: (*#06#):
Product ID: (*#*#1357946#*#*):
Click to expand...
Click to collapse
Hi man! I bought my Nova but it didn't arrive yet. But I'm following this thread and searched a bit. It seems that there is a source for Zenfone 3 ZE520KL here. Don't know if something can be done from here.
Sadly, Huawei G9 Plus isn't even listed at the site that @lgstoian sent. For more accurated source, we will have to wait for Huawei to put the source code on the site =/
EDIT: in fact, I noticed that g9 plus isn't to be found anywhere in Huawei website. And it seems that G9 Plus has the same specs of Nova Plus, So they might be the same device.
As I stated in the bootloader thread, I'm really interested in compiling TWRP for the device, but I'm on L01. I put together some files and if everything goes well, I'll give it a try at the end of the week. This isn't a promise, but I try to..
The difference between the L-01 and the L-11 should only the modem because the dual sim.
Tell new hat you need.
That's right..but let me start with L01-Version..at the moment I've some problems to solve for compiling, but the files should be complete..
If you read with compile, send me a copy I will try it on my L-11. (I bricked it with manual flash a system img from the 7.0 Update xD )
And with a working TWRP i can flash a backup from another phone, to get it work again.
Let me guess you tried the C900 one? Have you tried to flash also recovery and boot from this package?
Vinnom said:
...And it seems that G9 Plus has the same specs of Nova Plus, So they might be the same device.
Click to expand...
Click to collapse
It probably is the same device. I would guess it is a test release device, possibly even a developer device from a very limited release.
-=MoRpH=- said:
The difference between the L-01 and the L-11 should only the modem because the dual sim.
Click to expand...
Click to collapse
Yep, I think so too, because both firmware and and ro.product.hardwareversion are often referring to L01.
What we need is a working partition table, to know what can be flashed where. ATM I can't even read the partitions, since I have no working root. I'm closely following the developments on the dirtycow thread. However, the full AOS 7 update contain all partitions, but I need to get the mappings.
Running 7zip on the UPDATE.APP give you these 61 image files:
Code:
$ ls -1
aboot.img*
abootbak.img*
apdp.img*
boot.img*
bootfail_info.img*
cache.img*
cmnlib.img*
cmnlib64.img*
cmnlib64bak.img*
cmnlibbak.img*
config.img*
cust.img*
DDR.img*
devcfg.img*
devcfgbak.img*
devinfo.img*
dip.img*
dpo.img*
dsp.img*
erecovery.img*
fsc.img*
fsg.img*
keymaster.img*
keymasterbak.img*
keystore.img*
limits.img*
lksecapp.img*
lksecappbak.img*
log.img*
mcfg.img*
mdtp.img*
misc.img*
modem.img*
modemst1.img*
modemst2.img*
mota.img*
msadp.img*
nff.img*
oeminfo.img*
pad0.img*
pad1.img*
pad2.img*
patch.img*
persist.img*
product.img*
recovery.img*
rpm.img*
rpmbak.img*
rrecord.img*
sbl1.img*
sbl1bak.img*
sec.img*
splash.img*
ssd.img*
syscfg.img*
system.img*
tz.img*
tzbak.img*
userdata.img*
vendor.img*
version.img*
However, using 7z to unpack give you an error for each, even though the names (and number of partitions) now seem correct. This is because the image packaging contain additional non-standard data. Although there are some differences, it's something like this:
Code:
1. First 92 bytes are 0x00
2. Each file are started with 55AA 5AA5
3. Then 4 bytes for Header Length
4. Then 4 bytes for Unknown1
5. Then 8 bytes for Hardware ID
6. Then 4 bytes for File Sequence
7. Then 4 bytes for File Size
8. Then 16 byts for File Date
9. Then 16 byts for File Time
10.Then 16 byts for File Type
11.Then 16 byts for Blank1
12.Then 2 bytes for Header Checksum
13.Then 2 bytes for BlockSize
14.Then 2 bytes for Blank2
15.Then ($headerLength-98) bytes for file checksum
16.Then data file length bytes for files.
17.Then padding if have
18.Then repeat 2 to 17
So you need to use a Huawei specific unpacker. Trying to use any previous and outdated split_updata.pl (or splitupdate) scripts, does not give all the partitions without modifications. There are some hope for the better maintained Huawei Updater Extractor tool by @worstenbrood.
Mapping this back to /proc/partitions, should be fairly straight forward...
What is note worthy is that the mmcblk0p54 partition is 16 bytes larger than dm-2 (verity?), and /system is mounted on dm-2.
The question here is, how got the Chinese guy the mounting point or the partition table for the 64gb version? My Chinese is to bad, so I can't ask him.
Gesendet von iPhone mit Tapatalk
@morph wich Chinese guy do you mean?
I think he is referring to this thread : http://club.huawei.com/thread-11271738-1-1.html
Yes @lgstoian That's what I mean.
The recovery boot on my L11 but can't mount the partitions.
Gesendet von iPhone mit Tapatalk
Google's translation of the link:
Code:
NovaTWRP for XiaoWang_v1.1
UPDATE:
1. Added the king su_v3.64, integrated with the recovery file
2. Perfect support sub-f2fs
3. Solved the previous version of the bug
Boot file also improved, to solve the last version of the small probability
of the collapse of the phenomenon, be sure to use the new version
Because the system can not support supersu, will not start, so the use
of the kingroot team file (kingroot program is really high, I looked
directly on the ignorant of), and by the kingroot implementation of
the root. This program needs to format the data, please make a backup
As the screenshot upload it is too slow, so do not upload, and then
pass on the following text with a very detailed description of it
Before operation, please charge the battery to 60 or more, just in
case
1. First of all, please back up good data, first of all, please back
up good data, first back up good data, I have said important three times
2. Your phone needs to unlock the OEM before follow-up operation
3. Press the power button to restart, hold down the black screen of the moment the volume down, it will enter fastboot
4. Then extract the downloaded file, click the brush into the boot,
brush into the recovery, will be prompted to brush into the general impossible to error
5. Unplug the USB, press the power button to shut down,
press and hold the volume after the black screen, until you see a
large English, and so on 3 seconds to release, entered the Nova
special TWRP latest version
6. Go to Main> Clear> Format data partition> enter yes>
7. Main interface> Restart> Recovery
8. The main interface> mount> the system hook
9. Main interface> Advanced> File management> Select su folder> Select su> Copy> system> xbin> Point to the lower right corner of the hook> Slide button to confirm >>>> Back to system / xbin / Select su file>
10. Main interface> Restart> System>
11. Restart to the system, do not set the fingerprint and account
12. Install KingRoot.apk just downloaded, be sure to this version, do not download other versions, and do not download other software will be error, will become a serious brick
13.root after he turned around and then complete the point that the blue immediately deal with
14. Do not ask me why always the middle of the night post
15. Cherish the fruits of labor, reproduced, please indicate the source
If the operation failed, please do not lose heart, I also prepared the
original document, under any circumstances, as long as BootLoader
is not formatted, you can save the brick paste is a virtue, to
download the file, please reply " My brother "file 118.92M, it is
recommended to use WiFi download
Pan.baidu.com/s/1eRTkmsi
This link was updated on November 26, 2016 at 22:37:36
Xelfmade said:
Let me guess you tried the C900 one? Have you tried to flash also recovery and boot from this package?
Click to expand...
Click to collapse
First i tried the L11 EMUI 5 Beta (Yes boot, recovery and system.img). After that i got a boot loop and tried to wipe user data... that fails at 30%.
Than i tried the full firmware for the C900 (dload and fastboot) doesn't work too. Right now i can only boot the recovery and erecovery.
@lgstoian does that mean, he has successfully rooted the nova and we only have to translate his description correct to get a working root?
Related
Hi!
Today i got my LG P970 Optimus Black. But unfortunately there is not yet a ClockworkRecovery Image or any custom Roms availible. So i decived to build Clockworksmod myself. Now i got a little Problem on setting up the recovery.fstab.
cat /proc/partitions shows the following:
Code:
179 0 1912832 mmcblk0
179 1 128 mmcblk0p1
179 2 512 mmcblk0p2
179 3 6144 mmcblk0p3
179 4 6144 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 2048 mmcblk0p6
179 7 8192 mmcblk0p7
179 8 660480 mmcblk0p8 <-- System
179 9 1161088 mmcblk0p9 <-- Data
179 10 65536 mmcblk0p10 <-- Cache
179 11 128 mmcblk0p11
179 12 128 mmcblk0p12
179 16 1955840 mmcblk1 <-- SD-Card
So now my Question is how can i find out, which Partitions are the Recovery and Boot? And what are all the other ones?
I tried the mkvendor.sh Script on all Dumps i didn´t know what they are. The only ones the Script runs through without any errors are mmcblk0p3 & mmcblk0p4.
It seems nobody is interested in developing this phone
So I was on koush IRC channel asking somneone to try and compile a recovery and voila "jcase" agreed to do it if I could procure some reliable testers!
I can't do it as I am in South Africa on vacation and havent rooted my phone but please help you coud help in a huge way and ake a change for development on our devices!
All you have to do is head over to the IRC channel #koush and say "primo" and then jcase will ask you all that he needs!
EDIT: Post result of this!
adb shell cat /proc/emmc
adb shell cat /proc/partitions
FAST HE TOLD ME HE ISN'T GOING TO BE THERE FOR LONG
EDIT2: Post output in thread only because he has gone from IRC and I have to contact him elsewhere.
I'm currently in the process of compiling it aswell, we will have to wait some time for beta testers as very few people have the device (very new)
I have all details as attached:
mount
cat proc/emmc
cat /proc/partitions
ls -l /dev/block
Bump
Sent from my HTC One V using Tapatalk 2
Anyone managed to get successfull compilation of CWM recovery?
handryg555 said:
Anyone managed to get successfull compilation of CWM recovery?
Click to expand...
Click to collapse
No..
Sent from my HTC One V using XDA
i have the phone and i want try the recovery but im not that professional , so tell me how to do it simply and i'll try
Whenever I try to create the device tree I get error message 'unpackbootimg not found is you android environment setup?'. Any suggestions?
Sent from my Desire S
mmmcfc said:
Whenever I try to create the device tree I get error message 'unpackbootimg not found is you android environment setup?'. Any suggestions?
Sent from my Desire S
Click to expand...
Click to collapse
Even madmaxx82 told me that he would have to change his entire build environment as the One series was different from others...
Sent from my HTC One V using XDA
shubhamchamaria said:
Even madmaxx82 told me that he would have to change his entire build environment as the One series was different from others...
Sent from my HTC One V using XDA
Click to expand...
Click to collapse
I think I've got past that problem now . In school now .. will do next step later
Sent from my Desire S using xda premium
mmmcfc said:
I think I've got past that problem now . In school now .. will do next step later
Sent from my Desire S using xda premium
Click to expand...
Click to collapse
Thanks...
Sent from my HTC One V using XDA
emmc and partitions
Here's my output from my One V.
I have it rooted according to the steps described in the General post.
cat /proc/emmc
dev: size erasesize name
mmcblk0p17: 00040000 00000200 "misc"
mmcblk0p21: 0087f400 00000200 "recovery"
mmcblk0p22: 00400000 00000200 "boot"
mmcblk0p25: 31dffe00 00000200 "system"
mmcblk0p28: 0afffe00 00000200 "cache"
mmcblk0p26: 3cfffe00 00000200 "userdata"
mmcblk0p29: 017ade00 00000200 "devlog"
mmcblk0p31: 00040000 00000200 "pdata"
mmcblk0p30: 00011c00 00000200 "extra"
mmcblk0p32: 05ffe000 00000200 "fat"
mmcblk0p27: 07fffe00 00000200 "swap"
cat /proc/partitions
major minor #blocks name
7 0 2111 loop0
7 1 10427 loop1
179 0 2396160 mmcblk0
179 1 500 mmcblk0p1
179 2 64 mmcblk0p2
179 3 4500 mmcblk0p3
179 4 1 mmcblk0p4
179 5 30000 mmcblk0p5
179 6 12500 mmcblk0p6
179 7 2048 mmcblk0p7
179 8 3072 mmcblk0p8
179 9 2048 mmcblk0p9
179 10 1024 mmcblk0p10
179 11 1024 mmcblk0p11
179 12 8751 mmcblk0p12
179 13 3072 mmcblk0p13
179 14 3072 mmcblk0p14
179 15 1024 mmcblk0p15
179 16 8957 mmcblk0p16
179 17 256 mmcblk0p17
179 18 1024 mmcblk0p18
179 19 1024 mmcblk0p19
179 20 1280 mmcblk0p20
179 21 8701 mmcblk0p21
179 22 4096 mmcblk0p22
179 23 256 mmcblk0p23
179 24 2047 mmcblk0p24
179 25 817151 mmcblk0p25
179 26 999423 mmcblk0p26
179 27 131071 mmcblk0p27
179 28 180223 mmcblk0p28
179 29 24247 mmcblk0p29
179 30 71 mmcblk0p30
179 31 256 mmcblk0p31
179 32 98296 mmcblk0p32
179 64 7772160 mmcblk1
179 65 6715392 mmcblk1p1
179 66 1048576 mmcblk1p2
254 0 2110 dm-0
254 1 10426 dm-1
Good luck with the CWM-building
shubhamchamaria said:
Thanks...
Sent from my HTC One V using XDA
Click to expand...
Click to collapse
Unfortunately my laptops hard drive crashed while I was compiling the recovery. As a result I am without a laptop at the moment. I would very grateful towards anyone who donates towards replacing the hard drive. If anyone wants to help just click here
Hi,
I will try to build the recovery for this device.But need testers.I have successfully build touch based CWM for Optimus Me and Optimus One.This is my first time working with HTC device.I have downloaded the boot.img from TITTANIUM KERNEL .I hope that kernel is working on your devices.
I need to know how to flash the recovery to this device.is Root available for this device??
Yes:
[TUT] How to Unlock Bootloader and Root your Htc One V
I have compiled CWM for this device(recovery.img) .it is about 4.7 MB size.is it supported?
How is this flashed ?
Through fastboot?
hey one v owners. Im looking to get one v official support from koush for CWM. All I need is a tester for the recovery. I built it from source. So that way koush will support it.
Just flash like you would any recovery. I need any tester to go to mounting and mount every partition. Then flash a rom, backup a rom, and restore a rom without rebooting. Then connect phone to computer and run "adb pull /tmp/recovery.log" and post that here. If everything looks good I will submit to koush for official rom manager support and future updates from him.
For testing I would suggest running the command fastboot boot recovery.img
http://tinyw.in/2DqY
Yet another WFS user shows up on the One V forum. Welcome, JMZ! Give me a little time and I'll see if I can't get through your list and give some feedback.
CafeKampuchia said:
Yet another WFS user shows up on the One V forum. Welcome, JMZ! Give me a little time and I'll see if I can't get through your list and give some feedback.
Click to expand...
Click to collapse
Well I don't have device. Just heard this device needs some love. And I'm bored with the ones I have.
Sent from my PG86100 using xda premium
Can't flash it.
Code:
FAILED (remote: image error! (BootMagic check fail))
My bad. The download was corrupt. Reflashing in a bit.
Hi guys I got Xperia T3 D5102 few days back.
I rooted it & deodexed rom & now making few mods.
I tried making advance reboot Mod with restart options to recovery, system restart & soft reboot.
Reboot & soft reboot option is working fine but reboot to Recovery is not working. It ends up in just normal reboot of phone.
Also I tried to go the hardware way by trying key combinations in many ways
Power + Volume up/down doesn't work
Power + Volume both btns also didn't work.
Also tried using ADB commands for Advance power menu . But no luck then too.
I suspect there is no recovery partition and hence didn't boot.
The below table shows the partition table
Code:
Number Start End Size File system Name F
1 131kB 2228kB 2097kB TA
2 2228kB 2753kB 524kB sbl1
3 2753kB 3015kB 262kB s1sbl
4 3015kB 3080kB 65.5kB dbi
5 3080kB 3604kB 524kB aboot
6 3604kB 4129kB 524kB rpm
7 4129kB 4653kB 524kB tz
8 4653kB 5177kB 524kB alt_sbl1
9 5177kB 5439kB 262kB alt_s1sbl
10 5439kB 5505kB 65.5kB alt_dbi
11 5505kB 6029kB 524kB alt_aboot
12 6029kB 6554kB 524kB alt_rpm
13 6554kB 7078kB 524kB alt_tz
14 8389kB 9961kB 1573kB fsg
15 12.6MB 14.2MB 1573kB modemst1
16 16.8MB 18.4MB 1573kB modemst2
17 21.0MB 37.7MB 16.8MB ext4 persist
18 37.7MB 105MB 67.1MB fat16 modem
19 105MB 126MB 21.0MB boot
20 126MB 136MB 10.5MB fat32 ramdump
21 136MB 153MB 16.8MB FOTAKernel
22 153MB 153MB 32.8kB DDR
23 153MB 170MB 16.8MB ext4 LTALabel
24 172MB 180MB 8389kB apps_log
25 180MB 2248MB 2068MB ext4 system
26 2248MB 2458MB 210MB ext4 cache
27 2458MB 7818MB 5360MB ext4 userdata
(parted)
[email protected]:/ $ cat /proc/partitions
cat /proc/partitions
Code:
major minor #blocks name
179 0 7634944 mmcblk0
179 1 2048 mmcblk0p1
179 2 512 mmcblk0p2
179 3 256 mmcblk0p3
179 4 64 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 256 mmcblk0p9
179 10 64 mmcblk0p10
179 11 512 mmcblk0p11
179 12 512 mmcblk0p12
179 13 512 mmcblk0p13
179 14 1536 mmcblk0p14
179 15 1536 mmcblk0p15
179 16 1536 mmcblk0p16
179 17 16384 mmcblk0p17
179 18 65536 mmcblk0p18
179 19 20480 mmcblk0p19
179 20 10240 mmcblk0p20
179 21 16384 mmcblk0p21
179 22 32 mmcblk0p22
179 23 16384 mmcblk0p23
179 24 8192 mmcblk0p24
179 25 2019328 mmcblk0p25
179 26 204800 mmcblk0p26
179 27 5234671 mmcblk0p27
179 32 512 mmcblk0rpmb
179 64 7761920 mmcblk1
179 65 7760896 mmcblk1p1
[email protected]:/ $
Need help from developers /modders on how to proceed further and lemme know some hint to proceed.
I suspect recovery partition missing. Anyone can confirm the same ? The above table would give a clear layout of the memory partitions of the phone.
Request someone to throw light on this !
Thanks
Hello, just a question : how did you root your T3 ? are you allways on .14 ?
dan15 said:
Hello, just a question : how did you root your T3 ? are you allways on .14 ?
Click to expand...
Click to collapse
Yes my Android version is 4.4.2 build version is 18.2.A.1.14
ok, as my D5103 is ugrade to .17, i have to wait for a solution, if i don't want to downgrade, but i'm not sure that the rot will stay if i upgrade after root on .14...
Xperia devices don't have a recovery partition. Neither do they have any stock recovery.
AJ
Abhinav2 said:
Xperia devices don't have a recovery partition. Neither do they have any stock recovery.
AJ
Click to expand...
Click to collapse
You wrong, only a few xperia devices does NOT have a recovery partition, all others have it
CreasingMass Dev said:
You wrong, only a few xperia devices does NOT have a recovery partition, all others have it
Click to expand...
Click to collapse
None of them has AFAIK. Can u give some example of device which might have? Because recovery is basically flashed in FOTA partition
AJ
Al parecer no existe recovery
Xenon1978 said:
Hi guys I got Xperia T3 D5102 few days back.
I rooted it & deodexed rom & now making few mods.
I tried making advance reboot Mod with restart options to recovery, system restart & soft reboot.
Reboot & soft reboot option is working fine but reboot to Recovery is not working. It ends up in just normal reboot of phone.
Also I tried to go the hardware way by trying key combinations in many ways
Power + Volume up/down doesn't work
Power + Volume both btns also didn't work.
Also tried using ADB commands for Advance power menu . But no luck then too.
I suspect there is no recovery partition and hence didn't boot.
The below table shows the partition table
Code:
Number Start End Size File system Name F
1 131kB 2228kB 2097kB TA
2 2228kB 2753kB 524kB sbl1
3 2753kB 3015kB 262kB s1sbl
4 3015kB 3080kB 65.5kB dbi
5 3080kB 3604kB 524kB aboot
6 3604kB 4129kB 524kB rpm
7 4129kB 4653kB 524kB tz
8 4653kB 5177kB 524kB alt_sbl1
9 5177kB 5439kB 262kB alt_s1sbl
10 5439kB 5505kB 65.5kB alt_dbi
11 5505kB 6029kB 524kB alt_aboot
12 6029kB 6554kB 524kB alt_rpm
13 6554kB 7078kB 524kB alt_tz
14 8389kB 9961kB 1573kB fsg
15 12.6MB 14.2MB 1573kB modemst1
16 16.8MB 18.4MB 1573kB modemst2
17 21.0MB 37.7MB 16.8MB ext4 persist
18 37.7MB 105MB 67.1MB fat16 modem
19 105MB 126MB 21.0MB boot
20 126MB 136MB 10.5MB fat32 ramdump
21 136MB 153MB 16.8MB FOTAKernel
22 153MB 153MB 32.8kB DDR
23 153MB 170MB 16.8MB ext4 LTALabel
24 172MB 180MB 8389kB apps_log
25 180MB 2248MB 2068MB ext4 system
26 2248MB 2458MB 210MB ext4 cache
27 2458MB 7818MB 5360MB ext4 userdata
(parted)
[email protected]:/ $ cat /proc/partitions
cat /proc/partitions
Code:
major minor #blocks name
179 0 7634944 mmcblk0
179 1 2048 mmcblk0p1
179 2 512 mmcblk0p2
179 3 256 mmcblk0p3
179 4 64 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 256 mmcblk0p9
179 10 64 mmcblk0p10
179 11 512 mmcblk0p11
179 12 512 mmcblk0p12
179 13 512 mmcblk0p13
179 14 1536 mmcblk0p14
179 15 1536 mmcblk0p15
179 16 1536 mmcblk0p16
179 17 16384 mmcblk0p17
179 18 65536 mmcblk0p18
179 19 20480 mmcblk0p19
179 20 10240 mmcblk0p20
179 21 16384 mmcblk0p21
179 22 32 mmcblk0p22
179 23 16384 mmcblk0p23
179 24 8192 mmcblk0p24
179 25 2019328 mmcblk0p25
179 26 204800 mmcblk0p26
179 27 5234671 mmcblk0p27
179 32 512 mmcblk0rpmb
179 64 7761920 mmcblk1
179 65 7760896 mmcblk1p1
[email protected]:/ $
Need help from developers /modders on how to proceed further and lemme know some hint to proceed.
I suspect recovery partition missing. Anyone can confirm the same ? The above table would give a clear layout of the memory partitions of the phone.
Request someone to throw light on this !
Thanks
Click to expand...
Click to collapse
No se si alguno de ustedes o tengo instalar un gestor de recuperación (Recovery) anteriormente a este modelo
Ahora he intentado hacerlo y puff.. el paquete ABD me dice que no EXISTE
Code:
FAILED <remote: Recovery partición doesn't founded>
Hi guys
I have a best method for Nokia x liquid smooth lollipop developers for flashing this ROM without DAT.
________________________
System folder of this rom is compressed into DAT file.....developers easily extract system folder but sometimes they face some errors for Compressing To DAT.
For fix these errors.I build a updater-script for flahing this ROM like a kitkat roms flashing method.
so let's start for the hack
for accept this method you have to download the script from the given link....
you only want
Meta-Inf folder (go to the given link)
Boot.IMG
System folder (not DAT)
file_contexts
compress these files into zip and flash the ROM
that's it you flashed liquid lollipop without having DAT
remember
this script is only use for liquid smooth lollipop ROM by Ahmed hady
please press the thanks button
thank you
Link
http://www74.zippyshare.com/v/EhmIGNdK/file.html
Has the ril bug fixed?
we are truing to fix......by this updater-script I don't waste my time to compress system folder to DAT
Thanks Man ,,,
you welcome
hope you fix the ril soon , goodluck
okay
l.k said:
okay
Click to expand...
Click to collapse
Hey bro do you have knowledge of partitions of nokia x if yes then please explain
Share information about partitions I.e, which is boot partition,system partition etc
Here is my nokia x partitions list
[email protected]:/ $ cat /proc/partitions
major minor #blocks name
179 0 3817472 mmcblk0
179 1 20 mmcblk0p1
179 2 250 mmcblk0p2
179 3 51200 mmcblk0p3
179 4 1 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 3072 mmcblk0p6
179 7 3072 mmcblk0p7
179 8 3072 mmcblk0p8
179 9 2048 mmcblk0p9
179 10 4096 mmcblk0p10
179 11 1024 mmcblk0p11
179 12 768 mmcblk0p12
179 13 3072 mmcblk0p13
179 14 13576 mmcblk0p14
179 15 10240 mmcblk0p15
179 16 10240 mmcblk0p16
179 17 13576 mmcblk0p17
179 18 471040 mmcblk0p18
179 19 102400 mmcblk0p19
179 20 20 mmcblk0p20
179 21 1228800 mmcblk0p21
179 22 1370112 mmcblk0p22
179 23 40960 mmcblk0p23
179 24 10240 mmcblk0p24
179 25 399360 mmcblk0p25
179 26 59099 mmcblk0p26
179 32 15558144 mmcblk1
179 33 15554048 mmcblk1p1
253 0 102400 zram0
[email protected]:/ $
I don't know about that
Nokia X/XL Partitions
matrixex said:
Hey bro do you have knowledge of partitions of nokia x if yes then please explain
Share information about partitions I.e, which is boot partition,system partition etc
Click to expand...
Click to collapse
Bootloader 179 3 51200 mmcblk0p3
Persist 179 16 10240 mmcblk0p16
Boot 179 17 13576 mmcblk0p17
System 179 18 573440 mmcblk0p18
Cache 179 19 102400 mmcblk0p19
Storage 179 21 1172480 mmcblk0p21
Data 179 22 1267712 mmcblk0p22
YSH ALSAGER said:
Bootloader 179 3 51200 mmcblk0p3
Persist 179 16 10240 mmcblk0p16
Boot 179 17 13576 mmcblk0p17
System 179 18 573440 mmcblk0p18
Cache 179 19 102400 mmcblk0p19
Storage 179 21 1172480 mmcblk0p21
Data 179 22 1267712 mmcblk0p22
Click to expand...
Click to collapse
Thanks
I was searching for it
Well please also explain how did you find it
I'm working on cm13 compiled by thinhx2
ROM have a script error.....some symlink failed status 7....trying to fix it...
matrixex said:
Thanks
I was searching for it
Well please also explain how did you find it
Click to expand...
Click to collapse
Using Parition app
I've tried many times to fix the ril problem, but I can not. is there any other way to fix this problem ?
the rom using huawei device tree and the rom only for single rom bro,,,
we want twrp 3.0.0 for flashing cm13.....inches twrp 2.8.7.0 gave me error
some symlinks failed......
l.k said:
we want twrp 3.0.0 for flashing cm13.....inches twrp 2.8.7.0 gave me error
some symlinks failed......
Click to expand...
Click to collapse
That happens with me too I have created Nokia x stock rom after symlinking I have flashed it ,TWRP error displays "some symlink failed"
yeah as well as twrp 3.0.0 also isn't working
your rom file is not match with your sript,,
no twrp recovery isn't have complete symlinks which r used in cm13's script
Hi,
I own a OP3 with broken screen and am not able to retrieve some photos from the device.
As I already bought a new phone, I'd like to avoid having to repair the display.
Phone facts:
-Rooted Stock Rom, Bootloader unlocked
-Screen totally black, not sure if touch works, at least home key LED lights up when touched
- MTP not working (was recognized by PC, but no files displayed)
What works:
- Boot into stock recovery and fastboot
- adb and fastboot both work (I'm using android-tools-adb with Ubuntu 18.04)
- adb root shell
However, when browsing through the system, both /data and /storage are empty.
mount -a or mount /storage does not work.
When I do a
Code:
cat /proc/partitions
I get something similar to this:
Code:
major minor #blocks name
7 0 98304 loop0
8 16 4096 sdb
8 17 4052 sdb1
8 0 56582144 sda
8 1 8 sda1
8 2 32768 sda2
8 3 262144 sda3
8 4 1024 sda4
8 5 512 sda5
8 6 128 sda6
8 7 128 sda7
8 8 512 sda8
8 9 10240 sda9
8 10 10240 sda10
8 11 1024 sda11
8 12 8096 sda12
8 13 16192 sda13
8 14 512 sda14
8 15 56238572 sda15
8 48 131072 sdd
8 49 32 sdd1
8 50 4 sdd2
8 51 1024 sdd3
8 64 4194304 sde
8 65 512 sde1
8 66 512 sde2
8 67 2048 sde3
8 68 2048 sde4
8 69 512 sde5
8 70 512 sde6
8 71 2048 sde7
8 72 16 sde8
8 73 512 sde9
8 74 512 sde10
8 75 97280 sde11
8 76 16384 sde12
8 77 1024 sde13
8 78 32768 sde14
8 79 8192 sde15
259 0 8192 sde16
259 1 16384 sde17
259 2 65536 sde18
259 3 65536 sde19
259 4 3080192 sde20
259 5 65536 sde21
259 6 4 sde22
259 7 1024 sde23
259 8 512 sde24
259 9 512 sde25
259 10 256 sde26
259 11 256 sde27
259 12 256 sde28
259 13 256 sde29
259 14 256 sde30
259 15 256 sde31
259 16 4 sde32
259 17 33424 sde33
259 18 2048 sde34
8 32 4096 sdc
8 33 4052 sdc1
8 80 1572864 sdf
8 81 2048 sdf1
8 82 2048 sdf2
8 83 4 sdf3
8 84 512 sdf4
Is there any way I can mount the correct partitions to /storage and /data to get access to the the photos using adb / fastboot?
or any other way, maybe like flashing new Stock Rom (without wiping) using adb sideload and then let it boot and access the files via MTP?
@HansiT4 Maybe this tool: https://github.com/Genymobile/scrcpy
Never used it myself as I've never had the need though.