11
HTML:
adb shell su -c "dd if=/dev/block/mmcblk0p6 of=/sdcard/aboot
adb shell su -c "dd if=/dev/block/mmcblk0p1 of=/sdcard/apnhlos"
adb shell su -c "dd if=/dev/block/mmcblk0p17 of=/sdcard/backup"
adb shell su -c "dd if=/dev/block/mmcblk0p14 of=/sdcard/boot"
adb shell su -c "dd if=/dev/block/mmcblk0p24 of=/sdcard/cache"
adb shell su -c "dd if=/dev/block/mmcblk0p4 of=/sdcard/dbi"
adb shell su -c "dd if=/dev/block/mmcblk0p5 of=/sdcard/ddr"
adb shell su -c "dd if=/dev/block/mmcblk0p11 of=/sdcard/efs"
adb shell su -c "dd if=/dev/block/mmcblk0p16 of=/sdcard/fota"
adb shell su -c "dd if=/dev/block/mmcblk0p19 of=/sdcard/fsc"
adb shell su -c "dd if=/dev/block/mmcblk0p18 of=/sdcard/fsg"
adb shell su -c "dd if=/dev/block/mmcblk0p2 of=/sdcard/modem"
adb shell su -c "dd if=/dev/block/mmcblk0p12 of=/sdcard/modemst1"
adb shell su -c "dd if=/dev/block/mmcblk0p13 of=/sdcard/modemst2"
adb shell su -c "dd if=/dev/block/mmcblk0p9 of=/sdcard/pad"
adb shell su -c "dd if=/dev/block/mmcblk0p10 of=/sdcard/param"
adb shell su -c "dd if=/dev/block/mmcblk0p22 of=/sdcard/persdata"
adb shell su -c "dd if=/dev/block/mmcblk0p21 of=/sdcard/persist"
adb shell su -c "dd if=/dev/block/mmcblk0p15 of=/sdcard/recovery"
adb shell su -c "dd if=/dev/block/mmcblk0p7 of=/sdcard/rpm"
adb shell su -c "dd if=/dev/block/mmcblk0p3 of=/sdcard/sbl1"
adb shell su -c "dd if=/dev/block/mmcblk0p20 of=/sdcard/ssd"
adb shell su -c "dd if=/dev/block/mmcblk0p23 of=/sdcard/system"
adb shell su -c "dd if=/dev/block/mmcblk0p8 of=/sdcard/tz"
adb shell su -c "dd if=/dev/block/mmcblk0 of=/sdcard/N900V_1G bs=512 count=2097152"
DOWNLOAD LINK： http://pan.baidu.com/s/1bnelwkB PASSWORD: bdss
My twitter is :https://twitter.com/WarlockCN
Before people get too excited, you can't flash this.
What's this.....
Sent from my SM-N900V using XDA Premium 4 mobile app
Rootuser3.0 said:
What's this.....
Click to expand...
Click to collapse
Looks like the August 2013 operating system.
Frank
SGH-I717(AoCP6.4), SM-N900V/MI9(dlV), XDA Premium
Its the 4.4.2 test build dump
Sent from my Galaxy Note 3 using Tapatalk 4
TechSavvy2 said:
Its the 4.4.2 test build dump
Click to expand...
Click to collapse
I guess my guess has been wrong then. I guessed that the three unique characters of the build ID were a date code:
MI9
M=13=year 2013
I=9=month 9
9=9=day 9
MI9=2013-09-09
MJ7=2013-10-07
MJE=3013-10-14
So I would expect 4.4.2 to be later than MJE. Today (2014-01-18) would be NAI. MH9 would be 2013-08-09. Maybe it is a testbed of 4.4.x which they began back then.
ADDED;
Oh, I just noticed that you called it a "test dump". So it's probably a 2013-08-09 test.
Frank
SGH-I717(AoCP6.4), SM-N900V/MI9(dlV), XDA Premium
My real questoin is how he has a unlocked bootloader for the verizon note 3?
Brandonrz said:
My real questoin is how he has a unlocked bootloader for the verizon note 3?
Click to expand...
Click to collapse
It looks like an engineering build. Probably an engineering device.
Brandonrz said:
My real questoin is how he has a unlocked bootloader for the verizon note 3?
Click to expand...
Click to collapse
+1
Brandonrz said:
My real questoin is how he has a unlocked bootloader for the verizon note 3?
Click to expand...
Click to collapse
Maybe the dev edition? :silly::laugh:
sbreen94 said:
Maybe the dev edition? :silly::laugh:
Click to expand...
Click to collapse
I accidently liked your post, I don't want to confuse anybody. But he said he had the at&t note 3 with a unlocked bootloader. Same with Verizon one. Someone should contact him
Sent from my SM-N900V using Tapatalk
Write in the ATT thread, he's active in there
Sent from my Galaxy Note 3 using Tapatalk 4
Brandonrz said:
I accidently liked your post, I don't want to confuse anybody. But he said he had the at&t note 3 with a unlocked bootloader. Same with Verizon one. Someone should contact him
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
romup said:
the QCN is nv buckup by QPST
and this version isnot have bl lock，on this version，i can flash all MSM8974 ROM，such as N9005 N900T N900X
Click to expand...
Click to collapse
Sure, the ROM might be, but how are you going to get it on your device? Your device is locked, and there is no sys version in these files, so you will not be able to use them. Also, if you attempt to flash boot or recovery, you will void your warranty and trigger 0x1. Be warned.
ryanbg said:
Sure, the ROM might be, but how are you going to get it on your device? Your device is locked, and there is no sys version in these files, so you will not be able to use them. Also, if you attempt to flash boot or recovery, you will void your warranty and trigger 0x1. Be warned.
Click to expand...
Click to collapse
Who cares about knox. I will trip away
Sent from my SM-N900V using Xparent BlueTapatalk 2
to make a long story short what does this mean for the Verizon Galaxy Note 3?
Sent from my SM-N900V using XDA Premium 4 mobile app
mwebb34 said:
to make a long story short what does this mean for the Verizon Galaxy Note 3?
Sent from my SM-N900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I think they found that this is a bs to be short. Check the Att thread but hey I could be wrong.
Sent from my G2 using Tapatalk
dadsterflip said:
I think they found that this is a bs to be short. Check the Att thread but hey I could be wrong.
Sent from my G2 using Tapatalk
Click to expand...
Click to collapse
DELETED!
mwebb34 said:
I wiped data factory reset then reflashed hyperdrive 6 and reinstalled framwork rebooted went to hyper tweaks and set softkeys it automatacly rebooted once rebooting finished looked down andd bam soft keys are there im in buisness. Now all i need to do is figure out how to change some of the soft keys to my liking.
Click to expand...
Click to collapse
...um, cool? Are you in any way referring to something in this thread?
Sent from my Galaxy Note 3 using Tapatalk 4
TechSavvy2 said:
...um, cool? Are you in any way referring to something in this thread?
Sent from my Galaxy Note 3 using Tapatalk 4
Click to expand...
Click to collapse
No sorry about that i posted in the wrong place. My apologies
freefalling0411 said:
Who cares about knox. I will trip away
Sent from my SM-N900V using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
You can trip it, and the files won't flash. Even after tripping.
Sent from my SM-N900V using Tapatalk
Related
What's the easiest way to root the phone, fresh out of the box from Sprint, on a Mac?
And can I do it with TWRP instead of CWM?
The simplest guide I've seen is here: http://www.androidrootz.com/2012/10/how-to-root-galaxy-s3-on-mac-osx.html
Just not sure if that's current/safe for Sprint version.
Basically it just runs this script:
Code:
adb wait-for-device
adb push debugfs /data/local/
adb push su /data/local/
adb push debugfsinput /data/local/
adb shell mv /data/local/tmp /data/local/tmp.bak
adb shell ln -s /dev/block/mmcblk0p14 /data/local/tmp
adb reboot
adb wait-for-device
adb shell chmod 777 /data/local/debugfs
adb shell "/data/local/debugfs -w /dev/block/mmcblk0p14 < /data/local/debugfsinput"
adb shell rm /data/local/tmp
adb shell mv /data/local/tmp.bak /data/local/tmp
adb shell rm /data/local/su
adb shell rm /data/local/debugfs
adb shell rm /data/local/debugfsinput
Why you don't use Boot Camp with some Win version? I did that when I had my MacBook Pro.
Sent from my O=O
Says it works for sprint.. I'd try it.. flash cwm with ROM manager then you can go to twrp if you want
Sent from my SPH-L710 using xda app-developers app
DrKaotica said:
Says it works for sprint.. I'd try it.. flash cwm with ROM manager then you can go to twrp if you want
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Why do I need to flash CWM first? Can't I just root and then install TWRP from GooManager?
When you root you get a custom recovery. Almost always is CWM.
Sent from my O=O
Hi, all I've done since getting the 8.9 was boot into FastBoot, and use the KFID System.Img to flash the rooted system.img (option 3 I think).. I'm wanting to return now to 100% unrooted stock, what are the steps I need to take? I don't have a 2nd bootloader installde or anything like that.
Haloman800 said:
Hi, all I've done since getting the 8.9 was boot into FastBoot, and use the KFID System.Img to flash the rooted system.img (option 3 I think).. I'm wanting to return now to 100% unrooted stock, what are the steps I need to take? I don't have a 2nd bootloader installde or anything like that.
Click to expand...
Click to collapse
Code:
adb shell su -c "rm /system/app/Superuser.apk"
Code:
adb shell su -c "rm /system/xbin/su"
Then factory reset it.
Thepooch said:
Code:
adb shell su -c "rm /system/app/Superuser.apk"
Code:
adb shell su -c "rm /system/xbin/su"
Then factory reset it.
Click to expand...
Click to collapse
I was able to do it by downloading official firmware update from amazon and used their instructions for upgrading removed root.
Thank you!
Sent from my SCH-I605 using Tapatalk 2
T^T
Sent from my GT-S5300 using xda app-developers app
Hi,
After my experiments with root, backup, change ROM etc. I've lost all my sensors:
Accelerometer, light sensor, orientation sensor, proximity, gyroscope, magnetic.
Pressure works fine.
Phone had one fall, but I think it's not a cause.
Back to stock rom (F180K20K_00.kdz) is not a solution (with LG mobile support tool - emergency firmware recovery). I did it few times - without effect.
To read sensors, I use this 2 apps:
https://play.google.com/store/apps/details?id=de.onyxbits.sensorreadout
https://play.google.com/store/apps/details?id=imoblife.androidsensorbox
I think, problem can be in backup tool:.
http://forum.xda-developers.com/showthread.php?t=2139861
after restore backup I've lost SD card (after flash E975 ROM), but I'm not sure, because I didn't check sensors with every step I make.
Most of my "activity" is in topic (I doubt that anyone will read this):
http://forum.xda-developers.com/showthread.php?p=43675111#post43675111
What can I do ?
Ganz.Conrad said:
Hi,
After my experiments with root, backup, change ROM etc. I've lost all my sensors:
Accelerometer, light sensor, orientation sensor, proximity, gyroscope, magnetic.
Pressure works fine.
Phone had one fall, but I think it's not a cause.
Back to stock rom (F180K20K_00.kdz) is not a solution (with LG mobile support tool - emergency firmware recovery). I did it few times - without effect.
To read sensors, I use this 2 apps:
https://play.google.com/store/apps/details?id=de.onyxbits.sensorreadout
https://play.google.com/store/apps/details?id=imoblife.androidsensorbox
I think, problem can be in backup tool:.
http://forum.xda-developers.com/showthread.php?t=2139861
after restore backup I've lost SD card (after flash E975 ROM), but I'm not sure, because I didn't check sensors with every step I make.
Most of my "activity" is in topic (I doubt that anyone will read this):
http://forum.xda-developers.com/showthread.php?p=43675111#post43675111
What can I do ?
Click to expand...
Click to collapse
May be a kernel fault , did you try flashing a different kernel? ( Don't know if you have other kernels than stock one for your version , since I have the international version E-975)
However ,good luck!
You may mess up with your efs partition.
You need a efs backup from another f180k.
Sent from my LG-E975 using xda app-developers app
I think I broke my phone when I made recovery from backup, and maybe it's EFS partition.
Is any of these files a part of kernel or EFS?:
adb.exe shell su -c "dd if=/sdcard/System/30DDR.img of=/dev/block/mmcblk0p30"
adb.exe shell su -c "dd if=/sdcard/System/20BNR.img of=/dev/block/mmcblk0p20"
adb.exe shell su -c "dd if=/sdcard/System/7BOOT.img of=/dev/block/mmcblk0p7"
adb.exe shell su -c "dd if=/sdcard/System/15DRM.img of=/dev/block/mmcblk0p15"
adb.exe shell su -c "dd if=/sdcard/System/22eksst.img of=/dev/block/mmcblk0p22"
adb.exe shell su -c "dd if=/sdcard/System/21encrypt.img of=/dev/block/mmcblk0p21"
adb.exe shell su -c "dd if=/sdcard/System/29fsg.img of=/dev/block/mmcblk0p29"
adb.exe shell su -c "dd if=/sdcard/System/36grow.img of=/dev/block/mmcblk0p36"
adb.exe shell su -c "dd if=/sdcard/System/12m9kefs1.img of=/dev/block/mmcblk0p12"
adb.exe shell su -c "dd if=/sdcard/System/13m9kefs2.img of=/dev/block/mmcblk0p13"
adb.exe shell su -c "dd if=/sdcard/System/14m9kefs3.img of=/dev/block/mmcblk0p14"
adb.exe shell su -c "dd if=/sdcard/System/18misc.img of=/dev/block/mmcblk0p18"
adb.exe shell su -c "dd if=/sdcard/System/10modemst1.img of=/dev/block/mmcblk0p10"
adb.exe shell su -c "dd if=/sdcard/System/11modemst2.img of=/dev/block/mmcblk0p11"
adb.exe shell su -c "dd if=/sdcard/System/16sns.img of=/dev/block/mmcblk0p16"
adb.exe shell su -c "dd if=/sdcard/System/32mpt.img of=/dev/block/mmcblk0p32"
adb.exe shell su -c "dd if=/sdcard/System/9pad.img of=/dev/block/mmcblk0p9"
adb.exe shell su -c "dd if=/sdcard/System/26persist.img of=/dev/block/mmcblk0p26"
adb.exe shell su -c "dd if=/sdcard/System/35reserved.img of=/dev/block/mmcblk0p35"
adb.exe shell su -c "dd if=/sdcard/System/6rpm.img of=/dev/block/mmcblk0p6"
adb.exe shell su -c "dd if=/sdcard/System/34rpmbak.img of=/dev/block/mmcblk0p34"
adb.exe shell su -c "dd if=/sdcard/System/16sns.img of=/dev/block/mmcblk0p16"
adb.exe shell su -c "dd if=/sdcard/System/17ssd.img of=/dev/block/mmcblk0p17"
adb.exe shell su -c "dd if=/sdcard/System/8tz.img of=/dev/block/mmcblk0p8"
adb.exe shell su -c "dd if=/sdcard/System/33tzbak.img of=/dev/block/mmcblk0p33"
adb.exe shell su -c "dd if=/sdcard/System/27tombstones.img of=/dev/block/mmcblk0p27"
adb.exe shell su -c "dd if=/sdcard/System/1modem.img of=/dev/block/mmcblk0p1"
Click to expand...
Click to collapse
And the most important: which one I shouldn't move from other phone to avoid change IMEI or other individual data?
I'm asking because I think, that moving EFS from other phone with FreeGee will change IMEI or other stuff.
Does Root can damage kernel?
anyone?
Ganz.Conrad said:
anyone?
Click to expand...
Click to collapse
I have the same problem.. if freegee was the problem, how to reapir it?
harvester said:
I have the same problem.. if freegee was the problem, how to reapir it?
Click to expand...
Click to collapse
My phone was in LG repair Service (warranty), they changed main board, software, and said "it's unrepairable". I don't have my phone now - changed to new one.
I'm pretty sure, that it can be repaired (i think it's software problem ), but i didn't found way to do it.
Hello!
The title says it all! Is it possible to make a Nandroid backup directly to PC connected via USB? If yes, how?
Thanks!
amagalma said:
Hello!
The title says it all! Is it possible to make a Nandroid backup directly to PC connected via USB? If yes, how?
Thanks!
Click to expand...
Click to collapse
ADB pull can do almost anything. Step one of this OP http://forum.xda-developers.com/showthread.php?t=2128848 will show you how to backup everything.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
LinearEquation said:
ADB pull can do almost anything. Step one of this OP http://forum.xda-developers.com/showthread.php?t=2128848 will show you how to backup everything.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank you for your answer!
The code in step 1 is:
Code:
adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot of=/sdcard/stock-boot.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery of=/sdcard/stock-recovery.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/system of=/sdcard/stock-system.img" # This will take a few minutes
adb pull /sdcard/boot0block.img
adb pull /sdcard/stock-boot.img
adb pull /sdcard/stock-recovery.img
adb pull /sdcard/stock-system.img # This will take a few minutes
What should I change in order to specify the exact path where to backup in my PC? And another question: will this create images that are exact copies in size? Which is to say, will I need 16GB of free space in my PC's hard drive? (I have the Nexus 2 16GB Wi-Fi)
Thanks!
What should I change in order to specify the exact path where to backup in my PC?
Click to expand...
Click to collapse
adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot of=/sdcard/stock-boot.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery of=/sdcard/stock-recovery.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/system of=/sdcard/stock-system.img"
mkdir C:\name-of-the-file-you-made-on-your-pc-here
adb pull /sdcard/stock-boot.img/ [C:\name-of-your-file-make-on-on-your-PC-first)]
adb pull /sdcard/stock-recovery.img/ [C:\name-of-your-file]
adb pull /sdcard/stock-system.img/ [C:\name-of-your-file]
And another question: will this create images that are exact copies in size?
Click to expand...
Click to collapse
Yes
Which is to say, will I need 16GB of free space in my PC's hard drive?
Click to expand...
Click to collapse
What ever memory is in use is what you will need space wise for your nandroid. Look at the storage available and minus it from 16GB. That's the space you will need.
Find the name of the image to pull it. It may be labeled just plain recover.img, boot.img and (usually is.) What ever they are, just plug that info into the code. It all works the same you just have to tell (command) the computer what to pull. Sorry about the KFHD reference. I was on my tablet and that's where most of my help is focused at.
LinearEquation said:
adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot of=/sdcard/stock-boot.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery of=/sdcard/stock-recovery.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/system of=/sdcard/stock-system.img"
mkdir C:\name-of-the-file-you-made-on-your-pc-here
adb pull /sdcard/stock-boot.img/ [C:\name-of-your-file-make-on-on-your-PC-first)]
adb pull /sdcard/stock-recovery.img/ [C:\name-of-your-file]
adb pull /sdcard/stock-system.img/ [C:\name-of-your-file]
Yes
What ever memory is in use is what you will need space wise for your nandroid. Look at the storage available and minus it from 16GB. That's the space you will need.
Find the name of the image to pull it. It may be labeled just plain recover.img, boot.img and (usually is.) What ever they are, just plug that info into the code. It all works the same you just have to tell (command) the computer what to pull. Sorry about the KFHD reference. I was on my tablet and that's where most of my help is focused at.
Click to expand...
Click to collapse
Thank you very much for your help!
Hi Everybody
can someone backup 1 GB of emmcblk0 from working One M8 Model 0P6B130
phone must be rooted
this is the command via adb :
Code:
adb shell su -c "dd if=/dev/block/mmcblk0 of=/data/local/tmp/temp bs=512 count=2097152"
adb shell su -c "chmod 0755 /data/local/tmp/temp"
adb pull /data/local/tmp/temp C:\adbBackup\mmcblk0
adb shell su -c "rm /data/local/tmp/temp"
file will be created in c:\adbBackup
thanks in advaned
can some one do it for me please???
M-taheri said:
can some one do it for me please???
Click to expand...
Click to collapse
What is this for? Is it not something you could pull out of an RUU?
do you still need this?
M-taheri said:
Hi Everybody
can someone backup 1 GB of emmcblk0 from working One M8 Model 0P6B130
phone must be rooted
this is the command via adb :
Code:
adb shell su -c "dd if=/dev/block/mmcblk0 of=/data/local/tmp/temp bs=512 count=2097152"
adb shell su -c "chmod 0755 /data/local/tmp/temp"
adb pull /data/local/tmp/temp C:\adbBackup\mmcblk0
adb shell su -c "rm /data/local/tmp/temp"
file will be created in c:\adbBackup
thanks in advaned
Click to expand...
Click to collapse
bradley_e_smith said:
do you still need this?
Click to expand...
Click to collapse
Yes I need it
Thanks
M-taheri said:
Yes I need it
Thanks
Click to expand...
Click to collapse
okay will try it tomorrow at work.
I am waiting, thanks
bradley_e_smith said:
do you still need this?
Click to expand...
Click to collapse
File to large to post even if zip'd up.
-brad
bradley_e_smith said:
File to large to post even if zip'd up.
-brad
Click to expand...
Click to collapse
what about if you read 256mb??
adb shell su -c "dd if=/dev/block/mmcblk0 of=/data/local/tmp/temp bs=512 count=524288"
adb shell su -c "chmod 0755 /data/local/tmp/temp"
adb pull /data/local/tmp/temp C:\adbBackup\mmcblk0
adb shell su -c "rm /data/local/tmp/temp"
see attachment
M-taheri said:
what about if you read 256mb??
adb shell su -c "dd if=/dev/block/mmcblk0 of=/data/local/tmp/temp bs=512 count=524288"
adb shell su -c "chmod 0755 /data/local/tmp/temp"
adb pull /data/local/tmp/temp C:\adbBackup\mmcblk0
adb shell su -c "rm /data/local/tmp/temp"
Click to expand...
Click to collapse
bradley_e_smith said:
see attachment
Click to expand...
Click to collapse
thank you very much
does this will work for 0P6B11000? anyone can extract me hboot of that model pls thanks
Will this work on the opkV100?
---------- Post added at 04:26 PM ---------- Previous post was at 04:04 PM ----------
Is ur device an m8s??
bradley_e_smith said:
do you still need this?
Click to expand...
Click to collapse
where do i enter these commands?
skooter32 said:
where do i enter these commands?
Click to expand...
Click to collapse
from a dos prompt on your computer. you need to adb working on your computer