[GUIDE] Root your Nokia 5 - Nokia 5 Guides, News, & Discussion

Do not update to Android Oreo if you want to keep your phone rooted.
Latest Android Oreo Update for Nokia 6 TA-1000 blocked my method, because I found FIH modified aboot make OST LA 6.0.4 no longer usable for loading service bootloader.
Click to expand...
Click to collapse
Thanks @hikari_calyx
DO AT YOUR OWN RISK EVEN THOUGH IT WORKED FOR ME!
What you need:
-Nokia 5 TWRP: https://pan.baidu.com/s/1kVyzgvd
-ADB: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Firstly, you need to install ADB, the way that's most convenient for you. Then do as following
-Unlock bootloader like in this post: https://forum.xda-developers.com/nokia-5/development/guide-temporary-unlock-bootloader-to-t3746947
-Open command prompt in ADB folder, flash the recovery while still in download mode
fastboot flash recovery "PathToRecovery.img"
Click to expand...
Click to collapse
-When it says OKAY, hold vol up + power and reboot at the same time, it'll boot to recovery
fastboot reboot
Click to expand...
Click to collapse
-When it's done booting to recovery, click the 3-dotted circle, choose SuperSU root, slide, wait until finished, then reboot
-Boot to recovery again and do as above to get root access
Credit:
@blackpanther0582 for the firmware
@Quixote78 for OST LA and patch
@hikari_calyx for the OST method
@dimonolog2008 for the motivation for me to do this
@xinkid for the Nokia TWRPs
Anyone else that involved
WARNING:
-You have to boot to RECOVERY right AFTER FLASHING otherwise your phone won't boot
-DO NOT use any SuperSU zip outside of this recovery
POST INSTALLATION
-They have an English theme (https://forum.xda-developers.com/android/themes/theme-twrp-materialised-dark-light-play-t2915584). If you can't see the SuperSU option, flash the original theme in \sdcard\twrp\theme\ui.zip
-Use below zip file for SuperSU root instead of that on SuperSU homepage
-Power-on sound and bootanimation is in /system/CDA/600xx
-Change build.prop and add nexus.xml to /system/etc/ (and set permission rw-r--r--) for full AOSP vibe
-Turn of system update related services, activities and permission in LP, choose Change component (Google Play Services) --> pm disable --> search for "update"
-You can use Xposed, and GravityBox runs perfectly. As of version 88.2, some problems occured with Nov update
-Remove SuperSU that comes with the recovery and download it again from the Store if you want to
-Do not setenforce or reflash the Gapps unless you want to be locked out of your account
-Do not reflash data partition (with pattern lock) as bootloader is still locked
-The virtual drive with Driver is in /hidden/custom.iso
-Update partition dump
Code:
major minor #blocks name
7 0 98304 loop0
254 0 1048576 zram0
179 0 15388672 mmcblk0
179 1 1536 mmcblk0p1 modemst1
179 2 1536 mmcblk0p2 modemst2
179 3 1536 mmcblk0p3 fsg
179 4 1 mmcblk0p4 fsc
179 5 8192 mmcblk0p5 securefs
179 6 2048 mmcblk0p6 rf_nv
179 7 1024 mmcblk0p7 deviceinfo
179 8 86016 mmcblk0p8 modem
179 9 8 mmcblk0p9 ssd
179 10 512 mmcblk0p10 sbl1
179 11 512 mmcblk0p11 sbl1bak
179 12 512 mmcblk0p12 rpm
179 13 512 mmcblk0p13 rpmbak
179 14 2048 mmcblk0p14 tz
179 15 2048 mmcblk0p15 tzbak
179 16 256 mmcblk0p16 devcfg
179 17 256 mmcblk0p17 devcfgbak
179 18 16384 mmcblk0p18 dsp
179 19 32 mmcblk0p19 DDR
179 20 16 mmcblk0p20 sec
179 21 11264 mmcblk0p21 splash
179 22 1024 mmcblk0p22 aboot
179 23 1024 mmcblk0p23 abootbak
179 24 65536 mmcblk0p24 boot
179 25 65536 mmcblk0p25 recovery
179 26 1024 mmcblk0p26 devinfo
179 27 16384 mmcblk0p27 reserved
179 28 65536 mmcblk0p28 ftmboot
179 29 2048 mmcblk0p29 cust_nv
179 30 2048 mmcblk0p30 default_nv
179 31 1024 mmcblk0p31 hwcfg
259 0 1 mmcblk0p32 sutinfo
259 1 256 mmcblk0p33 systeminfo
259 2 32768 mmcblk0p34 ftmlog
259 3 8192 mmcblk0p35 box
259 4 16384 mmcblk0p36 multi_splash
259 5 40960 mmcblk0p37 hidden
259 6 8192 mmcblk0p38 cda
259 7 16384 mmcblk0p39 reserved_bak
259 8 32768 mmcblk0p40 persist
259 9 1024 mmcblk0p41 misc
259 10 512 mmcblk0p42 keystore
259 11 32 mmcblk0p43 config
259 12 262144 mmcblk0p44 oem
259 13 32 mmcblk0p45 limits
259 14 512 mmcblk0p46 mota
259 15 1024 mmcblk0p47 dip
259 16 32768 mmcblk0p48 mdtp
259 17 512 mmcblk0p49 syscfg
259 18 4096 mmcblk0p50 mcfg
259 19 256 mmcblk0p51 cmnlib
259 20 256 mmcblk0p52 cmnlibbak
259 21 256 mmcblk0p53 cmnlib64
259 22 256 mmcblk0p54 cmnlib64bak
259 23 256 mmcblk0p55 keymaster
259 24 256 mmcblk0p56 keymasterbak
259 25 256 mmcblk0p57 apdp
259 26 256 mmcblk0p58 msadp
259 27 8 mmcblk0p59 dpo
259 28 4193280 mmcblk0p60 system
259 29 262144 mmcblk0p61 cache
259 30 65536 mmcblk0p62 logdump
259 31 9490415 mmcblk0p63 userdata
179 32 4096 mmcblk0rpmb
179 64 15558144 mmcblk1
179 65 15549896 mmcblk1p1
253 0 9490399 dm-0
7 8 14512 loop8

wolfyapl said:
We can turn our phone into Nokia 6 by flashing a custom rom just to root amd TWRP-ize it. I'll write about it later because my laptop is not available now. Stay tuned!
Click to expand...
Click to collapse
Thanks bro please guide us to root our nokia 5 & install twrp....

Will it work on ta-1053 indian variant. If yes please make a video to show us how to root correctly. Thankyou

Birbal said:
Will it work on ta-1053 indian variant. If yes please make a video to show us how to root correctly. Thankyou
Click to expand...
Click to collapse
Yes, theorically. I typed this on my phone so...

Birbal said:
Will it work on ta-1053 indian variant. If yes please make a video to show us how to root correctly. Thankyou
Click to expand...
Click to collapse
The procedure is actually the same to Nokia 6.

hikari_calyx said:
The procedure is actually the same to Nokia 6.
Click to expand...
Click to collapse
Thanks...

Where to get the rom

Birbal said:
Where to get the rom
Click to expand...
Click to collapse
I also don't get that

daveve said:
I also don't get that
Click to expand...
Click to collapse
I think we have to download the official nokia 5 rom just google it..
But i have another what if offcial android 8.0 update arrives.. can we flash that or it will end up with a bricked phone.... Phewww...

mega.nz/#F!1ENgnThL!FyL9uYCC3Dq-16elThKAPg

wolfyapl said:
mega.nz/#F!1ENgnThL!FyL9uYCC3Dq-16elThKAPg
Click to expand...
Click to collapse
Thx! one quick question. The file is 10gb but I only need to download the Nokia 5 zip I think?

daveve said:
Thx! one quick question. The file is 10gb but I only need to download the Nokia 5 zip I think?
Click to expand...
Click to collapse
Correct.

I have seen another Excellent Guide from Google. So, I decided to share it on Xda to help people to root their smartphone in less than 15 minutes. So, To Root your Nokia 5 Without PC/laptop. Follow the steps given below.
First of all, Your device should have Custom Recovery installed. It can be TWRP/CWM Recovery.:
1. Download the Nokia 5 Package (Root) from the given URL Root Package
2. Then, Move the file to MicroSD card
3. Rename the download Root File as update.zip
4. Then, Turn OFF the Nokia 5 device and Turn ON by Pressing Power button + Volume Down Key at the same time.
5. Now, You successfully entered into Custom Recovery Mode. You can able to see a lot of options there.
6. You have to select Wipe Dalvik Cache and Come back.
7. Now, Select install Option and Select the root package file named update.zip from the downloaded folder (Remember the file should be in External SD card)
8. Wait for few seconds and Restart the Nokia 5 device. That's all You have successfully Rooted your phone without PC/Laptop.
I have collected this information from the Internet, and It worked for me. So, I have shared this with you guys. If you have any doubts. You can ask me here. I can help you.
source

vijaygopalbalasa said:
I have seen another Excellent Guide from Google. So, I decided to share it on Xda to help people to root their smartphone in less than 15 minutes. So, To Root your Nokia 5 Without PC/laptop. Follow the steps given below.
First of all, Your device should have Custom Recovery installed. It can be TWRP/CWM Recovery.:
1. Download the Nokia 5 Package (Root) from the given URL Root Package
2. Then, Move the file to MicroSD card
3. Rename the download Root File as update.zip
4. Then, Turn OFF the Nokia 5 device and Turn ON by Pressing Power button + Volume Down Key at the same time.
5. Now, You successfully entered into Custom Recovery Mode. You can able to see a lot of options there.
6. You have to select Wipe Dalvik Cache and Come back.
7. Now, Select install Option and Select the root package file named update.zip from the downloaded folder (Remember the file should be in External SD card)
8. Wait for few seconds and Restart the Nokia 5 device. That's all You have successfully Rooted your phone without PC/Laptop.
I have collected this information from the Internet, and It worked for me. So, I have shared this with you guys. If you have any doubts. You can ask me here. I can help you.
source
Click to expand...
Click to collapse
Thanks. Any help on how to install custom recovery ( preferably TWRP)? OP is a little unclear about this, 'specially the part about "holding the phone tightly while connecting to the PC to enter into download mode"..
Dead Cookies leave no trails...

Cookie Ninja said:
Thanks. Any help on how to install custom recovery ( preferably TWRP)? OP is a little unclear about this, 'specially the part about "holding the phone tightly while connecting to the PC to enter into download mode"..
Dead Cookies leave no trails...
Click to expand...
Click to collapse
Hold the phone to know when your phone reboots

what about the ta-1027 , chilean variant ? and if it bootloops how to force to turn off ? we cant remove the battery

pabloculiao123 said:
what about the ta-1027 , chilean variant ? and if it bootloops how to force to turn off ? we cant remove the battery
Click to expand...
Click to collapse
Hold Vol Up and Power and release when the screen goes black

worked a charm thanks

will it work with android 7.1.2 ?

novel1989 said:
will it work with android 7.1.2 ?
Click to expand...
Click to collapse
yes

Related

Format SD Card? How?

Hey,
i booted CM9 on my tablet. now it says "SD Card damaged". If i format it via CM9, it still says "SD CARD damaged..."...
Even CWM says that there was an error mounting SD Card when i want to mount it!
But i need it want to install CM10 on my touchpad...
i can access via adb, cat says:
~ # cat /proc/partitions
cat /proc/partitions
major minor #blocks name
179 0 31160320 mmcblk0
179 1 102400 mmcblk0p1
179 2 500 mmcblk0p2
179 3 1500 mmcblk0p3
179 4 1 mmcblk0p4
179 5 500 mmcblk0p5
179 6 750 mmcblk0p6
179 7 2500 mmcblk0p7
179 8 10240 mmcblk0p8
179 9 1500 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 4096 mmcblk0p12
179 13 32768 mmcblk0p13
179 14 30504960 mmcblk0p14
254 0 581632 dm-0
254 1 65536 dm-1
254 2 16384 dm-2
254 3 24576 dm-3
254 4 262144 dm-4
254 5 139264 dm-5
254 6 26877952 dm-6
254 7 409600 dm-7
254 8 311296 dm-8
254 9 204800 dm-9
254 10 1572864 dm-10
~ #
How to format/mount the sd card via adb that it works with CM9 so that i can copy files on it for flashing?
Thanks!
You should be able to format it from CWM or TWRP recovery. If that doesn't work you could always run ACMEUninstaller which will reset all Android partitions and you'll have to reinstall using ACMEInstaller.
When you re-install, use acmeinstaller 3.
Edit : on rereading your post, you might have to use this : http://forum.xda-developers.com/showthread.php?t=1426244
If you're having trouble with novaterm, on page 12 of the thread there's a good work around for that.
I know doctoring is a PITA, but you can update from 3.0.0 to 3.0.5 (in webOs) OTA.
Just do not do it through windows
Sent from my SAMSUNG-SGH-T989 using xda premium
chicle_11 said:
When you re-install, use acmeinstaller 3.
Edit : on rereading your post, you might have to use this : http://forum.xda-developers.com/showthread.php?t=1426244
If you're having trouble with novaterm, on page 12 of the thread there's a good work around for that.
I know doctoring is a PITA, but you can update from 3.0.0 to 3.0.5 (in webOs) OTA.
Click to expand...
Click to collapse
Worked for me thanks! =)

Partition Table for P7300 or P7310

Can someone please provide the output of the below in adb shell or Terminal Emulator, for P7300 or P7310?
Code:
cat /proc/partitions
Yup
ameer1234567890 said:
Can someone please provide the output of the below in adb shell or Terminal Emulator, for P7300 or P7310?
Code:
cat /proc/partitions
Click to expand...
Click to collapse
On my p7310 running discovery rom v6, in terminal emulator (these were 4 columns, and I can't figure out an easy way to put them into a forum post, so I'm just gonna do each column with a break in between.):
major
179
179
179
179
179
179
179
179
259
259
259
179
179
minor
0
1
2
3
4
5
6
7
0
1
2
16
8
#blocks
15387648
12288
5120
8192
694272
356352
2048
12288
13969920
8192
307200
512
512
name
mmcblk0
mmcblk0p1
mmcblk0p2
mmcblk0p3
mmcblk0p4
mmcblk0p5
mmcblk0p6
mmcblk0p7
mmcblk0p8
mmcblk0p9
mmcblk0p10
mmcblk0boot1
mmcblk0boot0
Are you working on something good for the 8.9?
I am working on adding support for Samsung Galaxy Tab 8.9, in Online Nandroid.
Very cool, glad I could help. Let me know if you need anything. I only have 16gb to work with, so I would love to put my nandroids online.
upconvert said:
Very cool, glad I could help. Let me know if you need anything. I only have 16gb to work with, so I would love to put my nandroids online.
Click to expand...
Click to collapse
Online Nandroid is not for saving nandroids online, but rather for doing backups while phone is online / running, without having to reboot into recovery mode. There are apps built on Online Nandroid script, one of which has the capability to store nandroid backups online too. See the link in my signature.

File request aboot

I have an LG Motion and I would like a copy of your aboot file to try to see if I can get the bootloader unlocked while it's flashed on the motion.
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/aboot.img
and send that file to me please
Thanks in advaced.
Screw LG's locked bootloaders!!!
Also this may be in the wrong place. If it belongs in development, I'm sorry.
dev/block/platform/msm_sdcc.1/by-name/aboot: cannot open for read: No such file
or directory
reas0n said:
dev/block/platform/msm_sdcc.1/by-name/aboot: cannot open for read: No such file
or directory
Click to expand...
Click to collapse
tegra platform...and we have no partition named aboot
i have x-loader.img and u-boot.img. here:
https://www.box.com/s/a6pyad63qwauos7zdw2b
Tim_Pan said:
tegra platform...and we have no partition named aboot
Click to expand...
Click to collapse
Hmmmm, you think it will still work?
Edit: what are the blocks and names of your partitions?
Sent from my LG-MS770
[email protected]:/ # cat proc/partitions
major minor #blocks name
179 0 15267840 mmcblk0
179 1 10240 mmcblk0p1
179 2 10240 mmcblk0p2
179 3 1572864 mmcblk0p3
179 4 393216 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 81920 mmcblk0p6
179 7 2048 mmcblk0p7
179 8 13062144 mmcblk0p8
179 9 16384 mmcblk0p9
179 10 16384 mmcblk0p10
179 11 20480 mmcblk0p11
179 12 16384 mmcblk0p12
179 13 47104 mmcblk0p13
179 32 2048 mmcblk0boot1
179 16 2048 mmcblk0boot0
179 48 15645696 mmcblk1
179 49 15644672 mmcblk1p1
Code:
ls -l /dev/block/platform/sdhci-tegra.3/by-name
lrwxrwxrwx root root 2013-03-10 23:24 APP -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2013-03-10 23:24 CAC -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2013-03-10 23:24 CAL -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2013-03-10 23:24 DRM -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2013-03-10 23:24 FOT -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2013-03-10 23:24 LNX -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2013-03-10 23:24 MLT -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2013-03-10 23:24 MSC -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2013-03-10 23:24 NVA -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2013-03-10 23:24 SOS -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2013-03-10 23:24 UDA -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2013-03-10 23:24 UDB -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2013-03-10 23:24 USP -> /dev/block/mmcblk0p6
reas0n said:
[email protected]:/ # cat proc/partitions
major minor #blocks name
179 0 15267840 mmcblk0
179 1 10240 mmcblk0p1
179 2 10240 mmcblk0p2
179 3 1572864 mmcblk0p3
179 4 393216 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 81920 mmcblk0p6
179 7 2048 mmcblk0p7
179 8 13062144 mmcblk0p8
179 9 16384 mmcblk0p9
179 10 16384 mmcblk0p10
179 11 20480 mmcblk0p11
179 12 16384 mmcblk0p12
179 13 47104 mmcblk0p13
179 32 2048 mmcblk0boot1
179 16 2048 mmcblk0boot0
179 48 15645696 mmcblk1
179 49 15644672 mmcblk1p1
Click to expand...
Click to collapse
No name of partitions?
Guess I'll have to figure out which partition is which on my own
I figure if your bootloader even does boot, I gotta make sure the partitions are still the same, and if not the same, flash things to the correct partitions according to your bootloader.
Sent from my LG-MS770
Can't flash the file given....our bootloader is 512KBs...yours is 10MBs............
sammyz said:
Can't flash the file given....our bootloader is 512KBs...yours is 10MBs............
Click to expand...
Click to collapse
i dont know if u still need, but download .tot or kdz for your phone and use lg binextractor(is not from lg,search google)extract the tot or kdz and get the aboot.i only have the nexus 4 and l5 so i cant help u much.
Our bootloader cannot be dumped from partitions. It's built into a lower level on the device. The two devices are in no way similar. Ours has a Tegra 3 chipset, yours is MSM.
If you really want to take a look at our bootloader, you can find a dump somewhere in the development section. But even if you find it and it fits for your device, DO NOT flash it by any means!!! It's one of the worst ideas one can come up with. You can very easily brick your device.
reas0n said:
i have x-loader.img and u-boot.img. here:
https://www.box.com/s/a6pyad63qwauos7zdw2b
Click to expand...
Click to collapse
Where did you get these from? It's not for the O4X.
Sent from my OmniROM-powered LG Optimus 4X HD

[INFO] Partition List Nexus 5

Here is the partition list of all Nexus 5 partitions with parted:
Code:
C:\Users\cargo\tools>adb shell
~ # umount /cache
umount /cache
~ # umount /system
umount /system
~ # umount /data
umount /data
~ # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: MMC SEM32G (sd/mmc)
Disk /dev/block/mmcblk0: 31.3GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 524kB 67.6MB 67.1MB fat16 modem
2 67.6MB 68.7MB 1049kB sbl1
3 68.7MB 69.2MB 524kB rpm
4 69.2MB 69.7MB 524kB tz
5 69.7MB 70.3MB 524kB sdi
6 70.3MB 70.8MB 524kB aboot
7 70.8MB 72.9MB 2097kB pad
8 72.9MB 73.9MB 1049kB sbl1b
9 73.9MB 74.4MB 524kB tzb
10 74.4MB 75.0MB 524kB rpmb
11 75.0MB 75.5MB 524kB abootb
12 75.5MB 78.6MB 3146kB modemst1
13 78.6MB 81.8MB 3146kB modemst2
14 81.8MB 82.3MB 524kB metadata
15 82.3MB 99.1MB 16.8MB misc
16 99.1MB 116MB 16.8MB ext4 persist
17 116MB 119MB 3146kB imgdata
18 119MB 142MB 23.1MB laf
19 142MB 165MB 23.1MB boot
20 165MB 188MB 23.1MB recovery
21 188MB 191MB 3146kB fsg
22 191MB 192MB 524kB fsc
23 192MB 192MB 524kB ssd
24 192MB 193MB 524kB DDR
25 193MB 1267MB 1074MB ext4 system
26 1267MB 1298MB 31.5MB crypto
27 1298MB 2032MB 734MB ext4 cache
28 2032MB 31.3GB 29.2GB ext4 userdata
29 31.3GB 31.3GB 5632B grow
(parted)
Here is a simple list:
Code:
C:\Users\cargo\tools>adb shell
cat /proc/partitions~ #
cat /proc/partitions
major minor #blocks name
179 0 30535680 mmcblk0
179 1 65536 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 512 mmcblk0p3
179 4 512 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 2048 mmcblk0p7
179 8 1024 mmcblk0p8
179 9 512 mmcblk0p9
179 10 512 mmcblk0p10
179 11 512 mmcblk0p11
179 12 3072 mmcblk0p12
179 13 3072 mmcblk0p13
179 14 512 mmcblk0p14
179 15 16384 mmcblk0p15
179 16 16384 mmcblk0p16
179 17 3072 mmcblk0p17
179 18 22528 mmcblk0p18
179 19 22528 mmcblk0p19
179 20 22528 mmcblk0p20
179 21 3072 mmcblk0p21
179 22 512 mmcblk0p22
179 23 512 mmcblk0p23
179 24 512 mmcblk0p24
179 25 1048576 mmcblk0p25
179 26 30720 mmcblk0p26
179 27 716800 mmcblk0p27
179 28 28551146 mmcblk0p28
179 29 5 mmcblk0p29
179 32 4096 mmcblk0rpmb
~ #
Can I somehow reformat /system & /cache partitions to F2FS? (For the speeeeed )
przemo_li said:
Can I somehow reformat /system & /cache partitions to F2FS? (For the speeeeed )
Click to expand...
Click to collapse
You won't get much speed out of a hosed phone. No you can't.
jd1639 said:
You won't get much speed out of a hosed phone. No you can't.
Click to expand...
Click to collapse
Meaning, kernel must support F2FS otherwise it wont boot? Obvious (for me at least) Just wanted to know if I can find such kernels (already build), and if there are tools to convert existing partitions. (So that changes performed are not too invasive )
Or if there are some mods that already employ F2FS.
(Moto G is my inspiration here, btw)
Any info and specs on the MMC model?
eng.stk said:
Any info and specs on the MMC model?
Click to expand...
Click to collapse
Do not know what MMC is, but if it was question for me I will just assume its hw question about storage specs for my phone.
1) I do not have that phone yet
2) It will be internetional version of Nexus 5 (16GB or 32GB).
eng.stk said:
Any info and specs on the MMC model?
Click to expand...
Click to collapse
Row 16 of the first output in post 1 identifies the model as as "SEM32G" which if you google, is SanDisk iNand... You can see it referenced in this datasheet:
http://omapworld.com/iNAND_e_MMC_4_41_IF_data_sheet_v1_0[1].pdf
rootSU said:
Row 16 of the first output in post 1 identifies the model as as "SEM32G" which if you google, is SanDisk iNand... You can see it referenced in this datasheet:
Click to expand...
Click to collapse
404 error
przemo_li said:
404 error
Click to expand...
Click to collapse
Because the url has [1] in it. Try and copy / paste
rootSU said:
Because the url has [1] in it. Try and copy / paste
Click to expand...
Click to collapse
Did that before I posted 404
No [1], and still 404
przemo_li said:
Did that before I posted 404
No [1], and still 404
Click to expand...
Click to collapse
It works, don't forget [1].pdf in the end.
przemo_li said:
Did that before I posted 404
No [1], and still 404
Click to expand...
Click to collapse
OK I fixed the link.
rootSU said:
Row 16 of the first output in post 1 identifies the model as as "SEM32G" which if you google, is SanDisk iNand... You can see it referenced in this datasheet:
http://omapworld.com/iNAND_e_MMC_4_41_IF_data_sheet_v1_0[1].pdf
Click to expand...
Click to collapse
Sustained Read:15 MB/s​Sustained Write:9 MB/s​
Biggest bottleneck of this great device
"Why Google?" or "Why LG?"
przemo_li said:
Can I somehow reformat /system & /cache partitions to F2FS? (For the speeeeed )
Click to expand...
Click to collapse
Lol, i do
http://forum.xda-developers.com/google-nexus-5/orig-development/nexus-5-f2fs-t2668486
dennes544 said:
Lol, i do
http://forum.xda-developers.com/google-nexus-5/orig-development/nexus-5-f2fs-t2668486
Click to expand...
Click to collapse
I know you're trying to be helpful but why revive and answer a thread that's been dead for 3 months?
Sent from my Nexus 5 using Tapatalk
Partition Stock
Hi I have a problem a wipe system VOL, I have /sdcard/ /sdcard/0/ /sdcard/0/0/ When I use usb have to goo /sdcard/0/0/ to much problem my question .. How I cant reset all partitions? and leave my fone like new..?? So I have 28 Gb free but I didnt put any file.. I wanna clean all fone and start with OEM partition, Thx ...sorry for english
how do you get parted on your N5? I only get sh: parted: not found lol
Can you please post the table again using bits or sectors as units? That will be very helpful.
jd1639 said:
You won't get much speed out of a hosed phone. No you can't.
Click to expand...
Click to collapse
Formatting cache and data DOES provide a speed boost but not with system. System should stay EXT4 because F2FS improves the performance of write operations the most and, typically, system is read only. Stick LineageOS 13 and 14.1 support data and cache as F2FS. Be aware though that switching data to F2FS WILL wipe internal storage so back it up. If you wish to keep your data the backup the data partition in TWRP and then backup the entire internal storage directory to a computer. After you've backed up everything you can go to wipe, advanced wipe and select data and hit repair or change and change it to F2FS. Once that is done you should reboot back into TWRP, open settings and enable "use rm -rf instead of formatting". When in recovery you can copy your entire internal storage back to your phone, ensure you copy it right, the TWRP directory should be in the root of your internal storage, this is important because it contains your precious data backup. After that reboot back into TWRP and you may have to enable rm -rf in settings, make sure that is enabled! These reboots are for good measure, it's best to just do them. After that you can go to restore and restore your data backup. After it is fully restored you may disable rm -rf in settings and format cache as F2FS. Then reboot to system and enjoy!
Sent from my Pixel using XDA Labs

[Q] backup stock boot partition before flashing with CWM

Hi erveryone,
First of all, thank you for reading my post and trying to help me.
My cell is a Samsung Galaxy Ace II x (GT-S7560M); I didn't found more appropriate place to post this thread. It is a new cellphone : I bought it 3 weeks ago.
I would like to "play" a bit with my phone (change the ROM, root it and everything. It is mainly because I want the Universal Storage Mode back on my cell). But if I do so, I would void the warranty. Since I will probably sell back this phone in few months, I may cause me some problem to explain people that there is no warranty anymore. So, I need to do a complete backup of the phone, including the part which is erased by ClockWorkMod recovery! (once this backup is done, I have found pretty much everything I need on Internet).
My question is - how do I do a backup of the boot partition knowing that:
this cell doesn't work on mtd.
the file /dev/block/bml5 (or /dev/bml5) doesn't exist (so what is said in this page http://forum.xda-developers.com/showthread.php?t=1335548 can't be applied)
neither does the file /dev/emmc
So it seems to be a bit more complicated to do a dd backup as found at some place on the net.
Also, since I want to backup the ROM after all these operation, I didn't root my cellphone (It would have voided the warranty) and of course, didn't change my ROM.
For the sake of accuracy, there is the complete answer to the mtd:
Code:
[email protected]:/ $ cat /proc/mtd
dev: size erasesize name
It is a bit empty, I know. Samsung seems to prefer a proprietary format "bml".
I also looked into the partitions file:
Code:
[email protected]:/ $ cat /proc/partitions
major minor #blocks name
253 0 122880 zram0
179 0 3817472 mmcblk0
179 1 20 mmcblk0p1
179 2 150 mmcblk0p2
179 3 20480 mmcblk0p3
179 4 1 mmcblk0p4
179 5 1000 mmcblk0p5
179 6 1000 mmcblk0p6
179 7 2000 mmcblk0p7
179 8 12288 mmcblk0p8
179 9 3072 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 8192 mmcblk0p11
179 12 12288 mmcblk0p12
179 13 4096 mmcblk0p13
179 14 4096 mmcblk0p14
179 15 512 mmcblk0p15
179 16 1228800 mmcblk0p16
179 17 512000 mmcblk0p17
179 18 2048 mmcblk0p18
179 19 12288 mmcblk0p19
179 20 24576 mmcblk0p20
179 21 4096 mmcblk0p21
179 22 51200 mmcblk0p22
179 23 1000 mmcblk0p23
179 24 4096 mmcblk0p24
179 25 1901176 mmcblk0p25
So I got some information, but I can't use them. But all these files can be found in /dev/block. I also checked: it seems that adb knows the dd command (I think not all cells do have it right now).
I think I have said pretty much anything I think is important.
Do you have any idea to help me? :fingers-crossed: Or any questions?
By the way, I have seen there are some cellphones that have an embedded flag, that counts the number of time we flash the boot partition. I have not seen such information on this device, so there shouldn't have any, should it?
Thank you for your help and sorry if I miss anything that coulb be on the net/other post. I think I have done a quite wide range of them, but we are never sure we didn't miss anything.
Also, it is my first post on xda, so sorry if I miss any important rule of the forum, but you are welcome to let me know what they are.
It's not an easy one
I still did not manage to solve my problem. It's not an easy question...
Do not hesitate to ask questions (if you need some precisions) or add something in this post. I feel a bit alone on this post! And since it isn't the hottest device with brand new fesature, not much persons are interested in it!
But it seems I'm not the only one to face this problem... All major new Samsung cellphones seems to have that kind of nice proprietary "feature" (or bug) that hide the partitions and prevent to do whatever it is necessary to backup the boot partition... Soooo, it would be nice to find a workaround. But I did not find any solution.
Have you any idea, even a slicest possibility that might maybe, in a fantastic world, work? I'm willing to hear any suggestions, or even clue that may help me to understand how to pass over that. :fingers-crossed:
Thank you!
The solution
Thank you Codename13 that helped me a lot on this problem! It seems that we can get the original firmwares on http://www.sammobile.com/firmwares/ (I didn't tried it myself). So it seems there is no point to bother with the rom and boot backup. Keep doing it for the sake of precaution, in case there were a corrupted downoad, wrong firmware or whatever, but at least, there seems to be a way to get the stock ROM and stock boot (and even more).
Also, for those that might be interested and can't or don't want to use Odin, there is Heimdall http://glassechidna.com.au/heimdall/ that can do the trick. (it is useful for people following http://forum.xda-developers.com/showthread.php?t=2265803 tutorial for instance.
For the rest, we just need to follow http://forum.xda-developers.com/showthread.php?t=2265803 or http://forum.xda-developers.com/showthread.php?t=2451967
Have a nice one!

Categories

Resources