like other people's can not mount anything ,
use TWRP boot , press install show internal storage 0mb
Is it means the storage over ?
ft7823 said:
like other people's can not mount anything ,
use TWRP boot , press install show internal storage 0mb
Is it means the storage over ?
Click to expand...
Click to collapse
hello anybody can help me ?
just after charging , the device can not open and use cwm boot in , showed can not mount anything ,
include the sdcard. I think the internal storage was damaged , is there any good ideas to get back ?
and I saw NT have a tool to unbrick ,is there also same tools for HD+?
What ROM were you using?
Are you booting from SD?
It seems that your emmc is bricked, unfortunately this seems not to be recoverable...
If you have adb access, try those commands mentioned here:
http://wiki.cyanogenmod.org/w/EMMC_Bugs#How_do_I_check_my_device.27s_eMMC_details.3F
CM10.2, I think you are right ,EMMC bricked.
but the strange thing is I use 3 sd card ,all can not boot from sdcard or emmc.
I want to flash noemmc version's cm, but also impossible now ...
so strange ..
wait, but you can boot into sd-recovery?
Jann F said:
wait, but you can boot into sd-recovery?
Click to expand...
Click to collapse
thank you , yesterday the devices can mount sdcard , so I install CM10.1 NOEMMC to sdcard
just one thing is not suit for me , the sdcard'format is not FAT32 and computer can only find the first part
so I can only download the file to my sdcard but cannot use usb or tf cardreader to put my files in.
but anyway , I can use it without emmc , the better thing than nothing to do.
1. My nook still bricked and cannot use any cwm except no-emmc version
2.I checked again, my nook is MGB4GA , I think should not be emmc bug
now
I use no-emmc version CWM flash EMMC recovery V6.0.3.2 ,
but without sdcard can only boot in the logo and stop there
e:can't mount /cache/revoery/command
and I use adb to check , show like below
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 398228 48 398180 0% /dev
~ # cat /proc/partitions
cat /proc/partitions
major minor #blocks name
179 0 30535680 mmcblk0
179 1 128 mmcblk0p1
179 2 256 mmcblk0p2
179 3 15360 mmcblk0p3
179 4 16384 mmcblk0p4
179 5 49152 mmcblk0p5
179 6 49152 mmcblk0p6
179 7 458752 mmcblk0p7
259 0 688128 mmcblk0p8
259 1 475136 mmcblk0p9
259 2 28770304 mmcblk0p10
179 16 2048 mmcblk0boot1
179 8 2048 mmcblk0boot0
179 24 7761920 mmcblk1
179 25 7761888 mmcblk1p1
is this normal?
and is that able to restore from leapinlar's repari.zip?
Get yourself a 32gb class 4 sd card and you can boot into CWM recovery.
ft7823 said:
1. My nook still bricked and cannot use any cwm except no-emmc version
2.I checked again, my nook is MGB4GA , I think should not be emmc bug
now
I use no-emmc version CWM flash EMMC recovery V6.0.3.2 ,
but without sdcard can only boot in the logo and stop there
e:can't mount /cache/revoery/command
and I use adb to check , show like below
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 398228 48 398180 0% /dev
~ # cat /proc/partitions
cat /proc/partitions
major minor #blocks name
179 0 30535680 mmcblk0
179 1 128 mmcblk0p1
179 2 256 mmcblk0p2
179 3 15360 mmcblk0p3
179 4 16384 mmcblk0p4
179 5 49152 mmcblk0p5
179 6 49152 mmcblk0p6
179 7 458752 mmcblk0p7
259 0 688128 mmcblk0p8
259 1 475136 mmcblk0p9
259 2 28770304 mmcblk0p10
179 16 2048 mmcblk0boot1
179 8 2048 mmcblk0boot0
179 24 7761920 mmcblk1
179 25 7761888 mmcblk1p1
is this normal?
and is that able to restore from leapinlar's repari.zip?
Click to expand...
Click to collapse
Your emmc looks ok. Do as the previous user suggested and get a SanDisk class 4 SD and make a bootable CWM SD per the instructions in item 1a in my HD/HD+ CWM thread linked in my signature. Then use that to flash a plain stock zip from item 6.
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
Your emmc looks ok. Do as the previous user suggested and get a SanDisk class 4 SD and make a bootable CWM SD per the instructions in item 1a in my HD/HD+ CWM thread linked in my signature. Then use that to flash a plain stock zip from item 6.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
So i need a sandisk card.... unfortunately i have no such card in my hand.
use old card with no-emmc version cwm flash nook 2.1 ,random offset 0x29,final abort , other models unable to be flashed to the system.
use 6028 flash 2.1 or 2.2 can run half but then black screen and shut off.
flash CM10.1 CM10.2 can not run just at the beginning and then black screen and shut off.
so is that possible to use your repair.zip?
ft7823 said:
So i need a sandisk card.... unfortunately i have no such card in my hand.
use old card with no-emmc version cwm flash nook 2.1 ,random offset 0x29,final abort , other models unable to be flashed to the system.
use 6028 flash 2.1 or 2.2 can run half but then black screen and shut off.
flash CM10.1 CM10.2 can not run just at the beginning and then black screen and shut off.
so is that possible to use your repair.zip?
Click to expand...
Click to collapse
You do not want to use the noemmc CWM if you are wanting to flash to emmc. If the 2.2 will not flash with 6028 then any repair zip I make will not work either.
Sent from my SCH-i705 using XDA Premium HD app
168599699669
leapinlar said:
You do not want to use the noemmc CWM if you are wanting to flash to emmc. If the 2.2 will not flash with 6028 then any repair zip I make will not work either.
Sent from my SCH-i705 using XDA Premium HD app
Click to expand...
Click to collapse
ok , understood , anyway ,thank you for your reply.
Related
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! =)
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.
I have an early HD+ that had been updated to an Android 4.2 and then 4.4 using AndroidForNook's AFN semi-commercial SD cards.
It was slowing down and crashing more - I guess with Google's Chrome and other 'almost system' updates.
I decided to go for a CyanogenMod distro - many weeks ago now. I don't remember exactly which - not the most recent, Android 4.4 type, probably 10.xx. I made an SD card - I am a very competent Windows admin and CMD user. Know next to nothing of Unix/Linux/Android systems. Used the same SD card that worked with AFN. Consequently Nook would get as far as showing B&N Nook splash screen w/o SD card inserted; or AFN's menu that would respond to volume and N buttons, but stick at "loading ....." whatever I'd chosen with the ORIGINAL AFN image on the inserted SD.
Followed a couple of weeks of trying several 'recovery' images that mostly did not get as far as screen output. Apparent resolutions focused on SD card boot issues - which I followed at length, ordered new SD cards etc.
TWO things still produce results: a no-EMMC SD recovery that boots to TWRP - but that seemed to work only ONCE; and when part booted with the ORIGINAL AFN SD I can get a shell session as root via ADB. Below are some of my findings...
====================================
File system commands like mount, parted, dd hang when dealing with /dev/block/mmcblk0
====================================
Relevant parts from the kernel boot-up log???
<6>[ 2.412078] mmc0: new high speed DDR MMC card at address 0001
<6>[ 2.412567] mmcblk0: mmc0:0001 MAG2GA 14.5 GiB
<6>[ 2.412872] mmcblk0boot0: mmc0:0001 MAG2GA partition 1 2.00 MiB
<6>[ 2.413116] mmcblk0boot1: mmc0:0001 MAG2GA partition 2 2.00 MiB
<4>[ 2.415679] Alternate GPT is invalid, using primary GPT.
<6>[ 2.415863] mmcblk0: p1 p2 p3 p4 p5 p6 p7 p8 p9 p10
<6>[ 2.418334] mmcblk0boot1: unknown partition table
<6>[ 2.419281] mmcblk0boot0: unknown partition table
<4>[ 2.666687] mmc1: host does not support reading read-only switch. assuming write-enable.
<6>[ 2.685424] mmc1: new high speed SDHC card at address aaaa
<6>[ 2.686248] mmcblk1: mmc1:aaaa SU08G 7.40 GiB
<6>[ 2.705169] mmcblk1: p1 p2 p3
<4>[ 2.924194] mmc2: card claims to support voltages below the defined range. These will be ignored.
<4>[ 2.943786] mmc2: queuing unknown CIS tuple 0x91 (3 bytes)
<6>[ 2.944488] mmc2: new SDIO card at address 0001
===================================
Can not mount SDCARD in the current half-booted state. looks like fstab is not read at startup; however /etc/recovery.fstab exists and is readable.
~ # mount sdcard
mount sdcard
mount: can't read '/etc/fstab': No such file or directory
====================================
Don't really understand what below implies - can read an ACTUAL GPT partition table off an ACUTAL storage device?
cat /proc/partitions
major minor #blocks name
179 0 15267840 mmcblk0
179 1 128 mmcblk0p1
179 2 256 mmcblk0p2
179 3 15360 mmcblk0p3
179 4 16384 mmcblk0p4
179 5 49152 mmcblk0p5
179 6 49152 mmcblk0p6
179 7 458752 mmcblk0p7
259 0 688128 mmcblk0p8
259 1 475136 mmcblk0p9
259 2 13500416 mmcblk0p10
179 16 2048 mmcblk0boot1
179 8 2048 mmcblk0boot0
179 24 7761920 mmcblk1
179 25 306176 mmcblk1p1
179 26 613376 mmcblk1p2
179 27 6831104 mmcblk1p3
==============================================
SO - does the above imply a SERIOUS problem with the emmc MAG2GA memory device (thanks to a bug in some distro...); or do I need a proper rebuild of the GPT partitions that will finally allow the Nook to boot properly from a recovery SD and accept an original B&N 2.1 image?? I do have my serial number and don't mind a bogus MAC address in the /ROM directory.
Many thanks in advance. Chris
You probably are subject to the TRIM bug. It can happen even when running from SD since the SD install uses part of emmc for support and gets trimmed with a trim command. If so, there is no fixing it. Only solution is to try a noemmc SD install.
Sent from my SM-T707V using XDA Premium HD app
Thanks; and is there a known stable no-Emmc image?
Leap - you are a star on here for your quick responses. Thanks. Also what is a definitive diag I can run to confirm the Emmc is ruined?
I presume it is worth trying to find the fastest SD the Nook will reliably work with to run the OS from?
Chris
frankenstein30 said:
Leap - you are a star on here for your quick responses. Thanks. Also what is a definitive diag I can run to confirm the Emmc is ruined?
I presume it is worth trying to find the fastest SD the Nook will reliably work with to run the OS from?
Chris
Click to expand...
Click to collapse
No, fastest is not the best. Get a SanDisk class 4, which is probably what that SD you have is. And I don't really know the test for bricked emmc. Verygreen had a test I think in his noemmc thread.
Sent from my SM-T707V using XDA Premium HD app
Hello,
After a shutdown due to low battery, my tablet is soft bricked. :/ I suspect a corruption of the internal SD or the flash chip, I'm not really sure.
My tablet is unlocked, I have cwm 6.0.5.1 installed. If I remember correctly, I had some cromi-X rom.
I have access to the bootloader (11.4.1.29) and the recovery but the manipulations I'm doing aren't working.
When into recovery, I get the messages e: can't mount/open /cache/recovery/log (last_log, last_install).
I tried flashing all kind of roms, they all failed, the most successful install ended with an error creating symlinks.
Tried all the wipe/format/factory reset options in the recovery, most of the time, I get the "error mounting /data", "error mounting /sdcard/.android_secure".
I can mount /system but it doesn't work for /cache and /data.
I can fastboot boot other recoveries (other cwm, twrp) but somehow can't flash. I'm not getting any error, they're just not sticking.
I tried manually formatting with e2fsck commands but I get an error related with superblocks.
Here's my cat log /proc/partitions :
179 0 30535680 mmcblk0
179 1 8192 mmcblk0p1
179 2 4096 mmcblk0p2
179 3 8192 mmcblk0p3
179 4 2097152 mmcblk0p4
179 5 897024 mmcblk0p5
179 6 512000 mmcblk0p6
179 7 8192 mmcblk0p7
179 8 4096 mmcblk0p8
179 9 16384 mmcblk0p9
179 10 8192 mmcblk0p10
179 11 8192 mmcblk0p11
179 12 4096 mmcblk0p12
179 13 4096 mmcblk0p13
179 14 26916864 mmcblk0p14
179 32 4096 mmcblk0boot1
179 16 4096 mmcblk0boot0
Here's what "df" is showing :
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 960124 128 959996 0% /dev
/dev/block/platform/sdhci-tegra.3/by-name/APP
2064208 1110432 953776 54% /system
I've done so many things to try fixing this with all I could find googling, I may have done some mistakes in the process but I didn't spot any change. The only thing I haven't tried yet is to install/boot a rom from the external SD. But I'm not experienced enough for that, I prefer to keep as a last resort.
I just ran a dmesg command, there's several error messages there, maybe that'll help. As I can't post URLs yet, here's a sample :
<4>[ 12.192838] lost page write due to I/O error on mmcblk0p5
<3>[ 19.972559] mmcblk0: mmc_blk_err_check: general error sending status command, card status 0x80900
<4>[ 19.981660] mmcblk0: retrying write for general error
<4>[ 19.986857] lost page write due to I/O error on mmcblk0p14
<3>[ 20.217027] mmcblk0: packed cmd failed, nr 20, sectors 280, failure index: 0
<4>[ 20.693382] JBD2: recovery failed
<3>[ 20.696941] EXT4-fs (mmcblk0p14): error loading journal
I'm not sure how it works, maybe it's possible to manually wipe everything, keeping the bare minimum to recreate the partitions and push the files.
I may have missed something, some help would be really appreciated. ^^
Thanks in advance !
I have same problem!! Any solutions?
Same Problem here as well!
I have the same problem. Seems like the /cache and /data partitions are corrupt.
I have full CWM and Bootloader access with ADB and fastboot. I cannot flash new recoveries. Cannot mount /data or /cache.
Repairing the partitions with e2fsck get me nowhere as well.
I can shell in and run parted on the /data (mmcblk0p14) and /cache (mmcblk0p5) blocks. I attempted to recreate the partitions using parted but keep getting input/output error during write on /dev/block/mmcblk...
Can't even delete the old partitions in /data (mmcblk0p14) and /cache (mmcblk0p5) with fdisk. get failure error.
Any ideas how to overcome the partition recreation errors? Are we screwed?
Same problem here as well.
had cromix up and running, then suddenly black screen. Recovery working good, but mount errors. Cannot restore nandroid or flash any kind of rom.
realmastah said:
Same problem here as well.
had cromix up and running, then suddenly black screen. Recovery working good, but mount errors. Cannot restore nandroid or flash any kind of rom.
Click to expand...
Click to collapse
If you use TWRP, first try to wipe dalvik cache only and then try again to flash a rom or to restore a nandroid backup. This problem is TWRP related...
I had this exact issue when i was moving to lollipop. I tried to flash to zombi-x and it caused this issue. every time i turned the device on it would boot direct to recovery. I was unable to restore backups, flash new roms... nothing worked. In the end, i formatted my data partition and put blisspop on my external sd. After the format it took the new rom and has been running amazingly well since then.
Jerry1996 said:
If you use TWRP, first try to wipe dalvik cache only and then try again to flash a rom or to restore a nandroid backup. This problem is TWRP related...
Click to expand...
Click to collapse
thanks for the suggestion, tried it without success.
meanwhile i sent the device back as it was still under warranty, got refund.
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