Related
Hi guys,
I am in desperate need of a raw img of mmcblk0. All I need one of you to do is get an adb shell or in terminal emulator with root type:
dd if=/dev/block/mmcblk0 of=/sdcard/unbrick.img count=524288
This creates a raw image dump I can use to help unbrick my device. It does NOT contain any sensitive data like IMEI or ESN, etc... I need MJE on Verizon Note 3 specifically. Thank you very much in advanced!
EDIT: 2/14 11:15am CST I am still in need of MJE N900V image. Surely would appreciate anyone with the time.
ryanbg said:
Hi guys,
I am in desperate need of a raw img of mmcblk0. All I need one of you to do is get an adb shell or in terminal emulator with root type:
dd if=/dev/block/mmcblk0 of=/sdcard/unbrick.img
This creates a raw image dump I can use to help unbrick my device. It does NOT contain any sensitive data like IMEI or ESN, etc... I need MJE on Verizon Note 3 specifically. Thank you very much in advanced!
Click to expand...
Click to collapse
Dev Edition matter? I can offer one up if that is acceptable
TechSavvy2 said:
Dev Edition matter? I can offer one up if that is acceptable
Click to expand...
Click to collapse
It's worth a shot, I sure would appreciate it.
/dev/mmcblk0 is the entire device - 32 GB
Is that really what you mean?
ryanbg said:
It's worth a shot, I sure would appreciate it.
Click to expand...
Click to collapse
aight, give me a minute
Edit: Sorry give me another minute, had to re-root really quick
Edit: PS, any other dd's you want me to run for you while I'm at it?
---------- Post added 14th February 2014 at 12:12 AM ---------- Previous post was 13th February 2014 at 11:58 PM ----------
bftb0 said:
/dev/mmcblk0 is the entire device - 32 GB
Is that really what you mean?
Click to expand...
Click to collapse
This.
TechSavvy2 said:
aight, give me a minute
Edit: Sorry give me another minute, had to re-root really quick
Edit: PS, any other dd's you want me to run for you while I'm at it?
---------- Post added 14th February 2014 at 12:12 AM ---------- Previous post was 13th February 2014 at 11:58 PM ----------
This.
Click to expand...
Click to collapse
Cancel that!!! I gave you a bad command. Just delete unbrick.img
ryanbg said:
Cancel that!!! I gave you a bad command. Just delete unbrick.img
Click to expand...
Click to collapse
Already cancelled it out when I realized the size and time it was gonna take. Another memory block you need perhaps?
Code:
major minor #blocks name Label
7 0 21861 loop0
7 1 3150 loop1
7 2 26019 loop2
7 3 9387 loop3
7 4 2111 loop4
7 5 4190 loop5
7 6 26019 loop6
179 0 30535680 mmcblk0
179 1 15360 mmcblk0p1 apnhlos
179 2 58816 mmcblk0p2 modem
179 3 512 mmcblk0p3 sbl1
179 4 32 mmcblk0p4 dbi
179 5 32 mmcblk0p5 ddr
179 6 2048 mmcblk0p6 aboot
179 7 512 mmcblk0p7 rpm
179 8 512 mmcblk0p8 tz
179 9 10240 mmcblk0p9 pad
179 10 10240 mmcblk0p10 param
179 11 14336 mmcblk0p11 efs
179 12 3072 mmcblk0p12 modemst1
179 13 3072 mmcblk0p13 modemst2
179 14 11264 mmcblk0p14 boot
179 15 13312 mmcblk0p15 recovery
179 16 13312 mmcblk0p16 fota
179 17 7159 mmcblk0p17 backup
179 18 3072 mmcblk0p18 fsg
179 19 1 mmcblk0p19 fsc
179 20 8 mmcblk0p20 ssd
179 21 8192 mmcblk0p21 persist
179 22 9216 mmcblk0p22 persdata
179 23 2777088 mmcblk0p23 system
179 24 1048576 mmcblk0p24 cache
179 25 26521583 mmcblk0p25 userdata
179 32 512 mmcblk0rpmb
179 64 30702592 mmcblk1
179 65 30701568 mmcblk1p1
254 0 21861 dm-0
254 1 3150 dm-1
254 2 26019 dm-2
254 3 9387 dm-3
254 4 2110 dm-4
254 5 4189 dm-5
254 6 26019 dm-6
TechSavvy2 said:
Already cancelled it out when I realized the size and time it was gonna take. Another memory block you need perhaps?
Code:
major minor #blocks name Label
7 0 21861 loop0
7 1 3150 loop1
7 2 26019 loop2
7 3 9387 loop3
7 4 2111 loop4
7 5 4190 loop5
7 6 26019 loop6
179 0 30535680 mmcblk0
179 1 15360 mmcblk0p1 apnhlos
179 2 58816 mmcblk0p2 modem
179 3 512 mmcblk0p3 sbl1
179 4 32 mmcblk0p4 dbi
179 5 32 mmcblk0p5 ddr
179 6 2048 mmcblk0p6 aboot
179 7 512 mmcblk0p7 rpm
179 8 512 mmcblk0p8 tz
179 9 10240 mmcblk0p9 pad
179 10 10240 mmcblk0p10 param
179 11 14336 mmcblk0p11 efs
179 12 3072 mmcblk0p12 modemst1
179 13 3072 mmcblk0p13 modemst2
179 14 11264 mmcblk0p14 boot
179 15 13312 mmcblk0p15 recovery
179 16 13312 mmcblk0p16 fota
179 17 7159 mmcblk0p17 backup
179 18 3072 mmcblk0p18 fsg
179 19 1 mmcblk0p19 fsc
179 20 8 mmcblk0p20 ssd
179 21 8192 mmcblk0p21 persist
179 22 9216 mmcblk0p22 persdata
179 23 2777088 mmcblk0p23 system
179 24 1048576 mmcblk0p24 cache
179 25 26521583 mmcblk0p25 userdata
179 32 512 mmcblk0rpmb
179 64 30702592 mmcblk1
179 65 30701568 mmcblk1p1
254 0 21861 dm-0
254 1 3150 dm-1
254 2 26019 dm-2
254 3 9387 dm-3
254 4 2110 dm-4
254 5 4189 dm-5
254 6 26019 dm-6
Click to expand...
Click to collapse
Sorry I'm in a bit of a panic. Trying to remember how to piece together a debrick image. Appreciate your patience again.
EDIT: Here we go Link
ryanbg said:
Hi guys,
I am in desperate need of a raw img of mmcblk0. All I need one of you to do is get an adb shell or in terminal emulator with root type:
dd if=/dev/block/mmcblk0 of=/sdcard/unbrick.img
This creates a raw image dump I can use to help unbrick my device. It does NOT contain any sensitive data like IMEI or ESN, etc... I need MJE on Verizon Note 3 specifically. Thank you very much in advanced!
Click to expand...
Click to collapse
Actually it DOES contain sensitive data since it contains ALL 32GB of the internal flash
You need to be rooted and with a decent busybox and do more like:
dd if=/dev/block/mmcblk0 of=/sdcard/unbrick.img count=524288
(this will create a 256MB image).
IMHO you also need to create the debrick image on the same family product - it would be VERY interesting if that would work from a verizon developer edition model (and I would really want to see that tested) but I have some doubts. I would also be interested if any other debrick image would work - I assume you have N900V but IMHO it would be again VERY interesting to try with a N900W8 debrick image (but be very, very careful when you later write stuff with the modem-related stuff, which is very different in N900W8 and you really want to keep your N900V modem and stuff ).
xclub_101 said:
... it would be VERY interesting if that would work from a verizon developer edition model (and I would really want to see that tested) but I have some doubts. I would also be interested if any other debrick image would work ...
Click to expand...
Click to collapse
I guess I need to go looking for the right threads, but is it correct to say that the SDcard unbrick method (Qualcomm phone versions) only provides a kind of volatile boot scaffolding so that the device owner can enter Odin/download mode... and that no flashing of the device occurs until the owner actually performs the subsequent flash operation using Odin? (That is, none of the content of the unbrick image is ever written to the device being rescued?)
A second question is whether version locking occurs - I thought I saw someone claiming that a prior release unbrick image, even if taken from the same device (e.g. MI9 or MJ7 prior to a MJE upgrade) will not launch into download mode - is that right?
bftb0 said:
I guess I need to go looking for the right threads, but is it correct to say that the SDcard unbrick method (Qualcomm phone versions) only provides a kind of volatile boot scaffolding so that the device owner can enter Odin/download mode... and that no flashing of the device occurs until the owner actually performs the subsequent flash operation using Odin? (That is, none of the content of the unbrick image is ever written to the device being rescued?)
A second question is whether version locking occurs - I thought I saw someone claiming that a prior release unbrick image, even if taken from the same device (e.g. MI9 or MJ7 prior to a MJE upgrade) will not launch into download mode - is that right?
Click to expand...
Click to collapse
That is somehow true, but IMHO if all relevant partitions are wiped on the internal flash (from SBL1 to ABOOT) then all those will be read from microSD and have the code and signatures from there, and the "Odin mode" itself will be the version from microSD.
And here we have a number of interesting paths:
- the signature/hash on SBL1 itself is similar among Note 3 versions - that would result on all steps up to and including ABOOT being valid, so the "special Odin mode" will be entered; if the signature/hash on SBL1 is NOT similar between Note 3 families (or even before and after a major bootloader version) not even the "special Odin mode" will be started;
- if "special Odin mode" is started we can see another fork - if the "downgrade limitations" are part of the microSD code itself then you will be able to write any single firmware you were able to write when the internal SBL1/ABOOT was at the same version as the microSD SBL1/ABOOT - in other words you will be able to downgrade as far back as the microSD SBL1/ABOOT will let you!
- however there are some reports that the "downgrade restrictions" are actually stored in the internal flash in the "invisible/protected" regions there - and can be reset with special JTAG-like hardware:
http://forum.gsmhosting.com/vbb/f672/regarding-knox-s4-1775213/
Even in that last case there would still be a small chance that the "downgrade restrictions" might be skipped when booting from microSD since the internal flash could be considered at that point "less reliable" (or hopefully somebody at Samsung forgot to read that extra info on this special path - we can all hope )
So yes, I have also seen some people claiming stuff but I would still like to see more detailed tests on it with detailed reports on what is failing at what point! And especially on the microSD with the N900W8 "happy bootloader" or even with some much earlier "early development bootloader" (I have seen something like that mentioned somewhere)!
bftb0 said:
I guess I need to go looking for the right threads, but is it correct to say that the SDcard unbrick method (Qualcomm phone versions) only provides a kind of volatile boot scaffolding so that the device owner can enter Odin/download mode... and that no flashing of the device occurs until the owner actually performs the subsequent flash operation using Odin? (That is, none of the content of the unbrick image is ever written to the device being rescued?)
A second question is whether version locking occurs - I thought I saw someone claiming that a prior release unbrick image, even if taken from the same device (e.g. MI9 or MJ7 prior to a MJE upgrade) will not launch into download mode - is that right?
Click to expand...
Click to collapse
My theory on this (for public, bftb0 already knows) is you can boot anything that isn't fused to a lower binary counter, and since these values are inconsistent with firmware updates, it gives you a little wiggle room. AKA if A flag in ODIN is A2, you can not use an A1 aboot (MI9), but I (think) could use MJ7 since it's counter value is 2, same as MJE. These values are stored in AP RAW ANTI ROLLBACK in QFPROM. It is my belief that these values are also accessed from the shadow register as opposed to being read every time, since I was able to downgrade and replicate. I'm almost positive it's pulling these flags from RPMB. I'm extremely curious what P is since I may have full control. P1 changed to P0 when I downgraded my SBL1, TZ, and RPM to the testbit bootloader leaked by designgears, which doesn't make much since I believe all three of those have their own counters.
well ryanbg can summarize when he gets some free time (and I think that there are further experiments in the queue) but an initial attempt at performing a rescue of his bricked retail SM-900V phone (which was on MJE prior to hard bricking by a TZ partition mod) using a 200 MiB dump of mmcblk0 from a MJ7 device resulted in .... nothing.
I haven't seen anything in any of the posts so far about folks talking extra precautions involving repair of the secondary GPT (after doing a raw dump of the unbrick.img to their SDcard media), so I suppose that means that the SDCard unbrick method is - when it works - supposed to be insensitive to the fact that the unbrick SD Card does not have a complete UEFI set of primary & secondary GPTs - and might even have garbage sitting at the secondary GPT offsets.
For the MJ7 trial, we used dd if=/dev/block/mmcblk0 bs=4096 count=50000 (200 MiB) which is sufficiently large to capture everything including some amount of slop at the beginning of /system (p23). I thought I saw a post where someone was using 300 MB unbrick images, making the claim that smaller sizes didn't seem to work. Doesn't make much sense though, as only about ~ 180 MB are needed for everything up to and including p22. (p1 - p22 are ordered contiguously in LBA address space on the SM-900V, and p23 is 2.7GB, so clearly an intact copy of /system can't be needed).
any ideas welcome
sorry to resurrect this thread, but I can't seem to find a sm-n900v debrick/unbrick img anywhere. i've found the 900T, 900A, 9005 images, but nothing for 900v.
my retail edition n900v is definitely hard bricked and I could use some assistance.
Does any one have a note 3 verizon mj7 debrick/unbrick.img
THREAD IS NOW AT ->
http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518
I will help out. I have been reading all the threads about bricking. I have a working phone running skop and elemental. My computer is a little netbook running windows 7 32. I wont have access to it till later though.
Sent from my Nexus 6
Casper34 said:
I will help out. I have been reading all the threads about bricking. I have a working phone running skop and elemental. My computer is a little netbook running windows 7 32. I wont have access to it till later though.
Sent from my Nexus 6
Click to expand...
Click to collapse
sure no problems, i will need some comands to be run, not flashing or anything.
and thanks
opssemnik said:
sure no problems, i will need some comands to be run, not flashing or anything.
and thanks
Click to expand...
Click to collapse
I will PM you when I get near my computer, or can I run them in terminal emulator?
Sent from my Nexus 6
Casper34 said:
I will PM you when I get near my computer, or can I run them in terminal emulator?
Sent from my Nexus 6
Click to expand...
Click to collapse
which you prefer, tho the output will be a bit big
opssemnik said:
which you prefer, tho the output will be a bit big
Click to expand...
Click to collapse
Check PMs
Sent from my Nexus 6
Casper34 said:
Check PMs
Sent from my Nexus 6
Click to expand...
Click to collapse
can you show me the output of:
ls /dev/block
cat /proc/partitions
ls /dev/block/platform
So we just need to flash 5.0 bootloader before we flash cm Roms? can we still flash asop 5.0?
Sent from my Nexus 6 using Tapatalk
kenbrownstone said:
So we just need to flash 5.0 bootloader before we flash cm Roms? can we still flash asop 5.0?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
once you flash the 5.1 bootloader you can not go back to 5.0.x bootloader. i tried and got a motorola error saying mismatch. so if you flash the 5.1 bootloader that's what you're stuck on. what i want to know is, can you still flash a 5.0.x system/boot image even though you're on 5.1 bootloader?
I flashed back to stock other day after running it ..Should that have been affected
Sent from my Nexus 6 using Tapatalk
looking foward to unbricking it. Thanks a lot
opssemnik said:
can you show me the output of:
ls /dev/block
cat /proc/partitions
ls /dev/block/platform
Click to expand...
Click to collapse
Here you go...... this from 5.0.1
Spoiler
[email protected]:/ $ su
[email protected]:/ # ls /dev/block
bootdevice
dm-0
loop0
loop1
loop2
loop3
loop4
loop5
loop6
loop7
mmcblk0
mmcblk0p1
mmcblk0p10
mmcblk0p11
mmcblk0p12
mmcblk0p13
mmcblk0p14
mmcblk0p15
mmcblk0p16
mmcblk0p17
mmcblk0p18
mmcblk0p19
[email protected]:/ # cat /proc/partitions
major minor #blocks name
179 0 30535680 mmcblk0
179 1 114688 mmcblk0p1
179 2 16384 mmcblk0p2
179 3 384 mmcblk0p3
179 4 56 mmcblk0p4
179 5 16 mmcblk0p5
179 6 32 mmcblk0p6
179 7 1024 mmcblk0p7
179 8 256 mmcblk0p8
179 9 512 mmcblk0p9
179 10 500 mmcblk0p10
179 11 4156 mmcblk0p11
179 12 384 mmcblk0p12
179 13 1024 mmcblk0p13
179 14 256 mmcblk0p14
179 15 512 mmcblk0p15
179 16 500 mmcblk0p16
179 17 4 mmcblk0p17
179 18 512 mmcblk0p18
179 19 1024 mmcblk0p19
179 20 1024 mmcblk0p20
179 21 1024 mmcblk0p21
179 22 1024 mmcblk0p22
179 23 16384 mmcblk0p23
179 24 16384 mmcblk0p24
179 25 2048 mmcblk0p25
179 26 32768 mmcblk0p26
179 27 256 mmcblk0p27
179 28 32 mmcblk0p28
179 29 128 mmcblk0p29
179 30 8192 mmcblk0p30
179 31 1024 mmcblk0p31
259 0 2528 mmcblk0p32
259 1 1 mmcblk0p33
259 2 8 mmcblk0p34
259 3 16400 mmcblk0p35
259 4 9088 mmcblk0p36
259 5 16384 mmcblk0p37
259 6 262144 mmcblk0p38
259 7 65536 mmcblk0p39
259 8 1024 mmcblk0p40
259 9 2097152 mmcblk0p41
259 10 27807616 mmcblk0p42
179 32 4096 mmcblk0rpmb
254 0 27807616 dm-0
[email protected]:/ # ls /dev/block/platform
msm_sdcc.1
[email protected]:/ #
Sent from my Nexus 6
My nexus is also bricked after flash cm12 on top of the 5.2 bootloader. I hit reboot in TWRP and the phone shut down and hasn't done anything since. I cannot get anything to show on the screen and my computer is not recognizing it through fastboot or adb commands. I am running Ubuntu if that helps but again, I cannot see the device connected at all. I am starting to think I need to send this in for RMA
Any help is appreciated.
EDIT: When I run "lsusb" command, I get the following line when my phone is plugged in-
Bus 002 Device 006: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
Casper34 said:
Here you go...... this from 5.0.1
Spoiler
[email protected]:/ $ su
[email protected]:/ # ls /dev/block
bootdevice
dm-0
loop0
loop1
loop2
loop3
loop4
loop5
loop6
loop7
mmcblk0
mmcblk0p1
mmcblk0p10
mmcblk0p11
mmcblk0p12
mmcblk0p13
mmcblk0p14
mmcblk0p15
mmcblk0p16
mmcblk0p17
mmcblk0p18
mmcblk0p19
[email protected]:/ # cat /proc/partitions
major minor #blocks name
179 0 30535680 mmcblk0
179 1 114688 mmcblk0p1
179 2 16384 mmcblk0p2
179 3 384 mmcblk0p3
179 4 56 mmcblk0p4
179 5 16 mmcblk0p5
179 6 32 mmcblk0p6
179 7 1024 mmcblk0p7
179 8 256 mmcblk0p8
179 9 512 mmcblk0p9
179 10 500 mmcblk0p10
179 11 4156 mmcblk0p11
179 12 384 mmcblk0p12
179 13 1024 mmcblk0p13
179 14 256 mmcblk0p14
179 15 512 mmcblk0p15
179 16 500 mmcblk0p16
179 17 4 mmcblk0p17
179 18 512 mmcblk0p18
179 19 1024 mmcblk0p19
179 20 1024 mmcblk0p20
179 21 1024 mmcblk0p21
179 22 1024 mmcblk0p22
179 23 16384 mmcblk0p23
179 24 16384 mmcblk0p24
179 25 2048 mmcblk0p25
179 26 32768 mmcblk0p26
179 27 256 mmcblk0p27
179 28 32 mmcblk0p28
179 29 128 mmcblk0p29
179 30 8192 mmcblk0p30
179 31 1024 mmcblk0p31
259 0 2528 mmcblk0p32
259 1 1 mmcblk0p33
259 2 8 mmcblk0p34
259 3 16400 mmcblk0p35
259 4 9088 mmcblk0p36
259 5 16384 mmcblk0p37
259 6 262144 mmcblk0p38
259 7 65536 mmcblk0p39
259 8 1024 mmcblk0p40
259 9 2097152 mmcblk0p41
259 10 27807616 mmcblk0p42
179 32 4096 mmcblk0rpmb
254 0 27807616 dm-0
[email protected]:/ # ls /dev/block/platform
msm_sdcc.1
[email protected]:/ #
Sent from my Nexus 6
Click to expand...
Click to collapse
Thanks, im preparing the QPST / Drivers zip, im also looking into the factory images
ccb1208 said:
My nexus is also bricked after flash cm12 on top of the 5.2 bootloader. I hit reboot in TWRP and the phone shut down and hasn't done anything since. I cannot get anything to show on the screen and my computer is not recognizing it through fastboot or adb commands. I am running Ubuntu if that helps but again, I cannot see the device connected at all. I am starting to think I need to send this in for RMA
Any help is appreciated.
EDIT: When I run "lsusb" command, I get the following line when my phone is plugged in-
Bus 002 Device 006: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
Click to expand...
Click to collapse
yep, in that mode we need a program that acts as QPST (or QPST itself) a 2nd_loader.hex (new bootloader) and a APQ8974_image hex that matches ours nexus 6, once there we can send the basic stuff and get rsd mode / fastboot to work, then we just flash factory images
Your best bet would be to try the Moto X/G blankflash program. It uses an executable called qboot which is a USB loader. It may be possible to use the 8226 programmer to flash the bootloader image back to the device from bulk mode. I'd doubt it'd work, but worth checking out.
freebee269 said:
once you flash the 5.1 bootloader you can not go back to 5.0.x bootloader. i tried and got a motorola error saying mismatch. so if you flash the 5.1 bootloader that's what you're stuck on. what i want to know is, can you still flash a 5.0.x system/boot image even though you're on 5.1 bootloader?
Click to expand...
Click to collapse
Yes, you can go back to the 5.0.x system after updating to 5.1
I just flashed the ENTIRE 5.0.1 factory image, minus the bootloader.
You must obviously already be bootloader unlocked to do so.
No ill-effects whatsoever.
If you do go back to 5.0.x, make sure you flash the radio for it as well. There's a chance you'll not be able to receive calls if on LTE with 5.1's radio, as was the case for me. Only on 3g/4g did calls go through (I'm on TMO, btw)
I had the same calls issue on T-Mobile, I was on a 5.0.2 ROM and had flashed the 5.1 bootloader and radio and a friend said she called me but I didn't get a call. When she came over I had her call me again but got nothing, I could call her though. I booted to a 5.1 rom and had her call me and my phone rang.
Hey I have a fully working N6 running stock 5.1, what can I do to help?
opssemnik said:
can you show me the output of:
ls /dev/block
cat /proc/partitions
ls /dev/block/platform
Click to expand...
Click to collapse
swimdude1120 said:
Hey I have a fully working N6 running stock 5.1, what can I do to help?
Click to expand...
Click to collapse
Run those commands if you are rooted and quote opssemnik, the one with the commands, so he can see them.
If you do, put the word SPOILER in brackets [] and then the output, the /SPOILER in the brackets []
Sent from my Nexus 6
NOTE: Testers no longer required, now confirmed working for both kitkat and lollipop
This is for the T800/T805/T807 Exynos version only
Basically I have fixed some issues with the official build:
It is not possible to get root access to the shell with adb in the official version, you will get an error. I have fixed this as it is important for adb to be able to get shell access, you never know when it might be needed.
The reboot options have been corrected to change the reboot option from BOOTLOADER to DOWNLOAD . Reboot to Download mode now works.
TWRP still uses outdated Supersu and root files, so I have updated these to the latest versions.
Please use Odin 10.6 for installing: Odin 10.6
unofficial-twrp-2.8.6.0-chagall.tar
Anybody? just 2mins of your time. It won't brick your device. If it flashes with Odin and doesn't boot just reflash the official twrp or stock recovery.
ashyx said:
Anybody? just 2mins of your time. It won't brick your device. If it flashes with Odin and doesn't boot just reflash the official twrp or stock recovery.
Click to expand...
Click to collapse
Had some time before I do chores Fails in odin and flashify. In odin it would say name write start... then fail! And yet official twrp flashes fine
Right this is silly. I'm gonna do a simple repack of the official twrp, no changes. Can you test that? If that fails then at least I know where the problem lies!
ashyx said:
Right this is silly. I'm gonna do a simple repack of the official twrp, no changes. Can you test that? If that fails then at least I know where the problem lies!
Click to expand...
Click to collapse
Yep sure can!
DUHAsianSKILLZ said:
Yep sure can!
Click to expand...
Click to collapse
ok here you go.
https://www.androidfilehost.com/?fid=95916177934548161
ashyx said:
ok here you go.
https://www.androidfilehost.com/?fid=95916177934548161
Click to expand...
Click to collapse
Works!
DUHAsianSKILLZ said:
Works!
Click to expand...
Click to collapse
Good stuff, I have a feeling the lollipop update has changed the size of the recovery partition which is why it was being rejected.
If the link below works then I will see if I can reduce the size, but could really need to know what size the new partition is.
https://www.androidfilehost.com/?fid=95916177934548184
ashyx said:
Good stuff, I have a feeling the lollipop update has changed the size of the recovery partition which is why it was being rejected.
If the link below works then I will see if I can reduce the size, but could really need to know what size the new partition is.
https://www.androidfilehost.com/?fid=95916177934548184
Click to expand...
Click to collapse
Yep this one works also. Rebooting into download mode from twrp works fine. Seems to be the one!
Great, looks like we've discovered the problem. Just need to fix the adb shell issue and if size allows update supersu. Thanks your a great help. I'll update tomorrow.
ashyx said:
Great, looks like we've discovered the problem. Just need to fix the adb shell issue and if size allows update supersu. Thanks your a great help. I'll update tomorrow.
Click to expand...
Click to collapse
When you post the update tomorrow, or whenever you post it. Ill give it a try. Sorry I couldnt be much help on the testing stage at this time. I have been so busy with my own mods that I dont have much time for others at the time.
But I will try it out on your next update.. for sure... thanks for your support on this Machine...
Of course I realise you are busy with other things so appreciate the time.:good:
I have reduced the size of the files below, the first one is slightly large than the second. I cant reduce any more without reducing functionality, so if the first one doesn't work the second should, but at least 2 of the main issues, the adb shell problem and wrong reboot option will be fixed in both.
twrp2860v1
twrp2860v2
thanks again.
ashyx said:
Of course I realise you are busy with other things so appreciate the time.:good:
I have reduced the size of the files below, the first one is slightly large than the second. I cant reduce any more without reducing functionality, so if the first one doesn't work the second should, but at least 2 of the main issues, the adb shell problem and wrong reboot option will be fixed in both.
twrp2860v1
twrp2860v2
thanks again.
Click to expand...
Click to collapse
Hi I have just flashed the first one and it failed but the second one flashed ok.
ashyx said:
Of course I realise you are busy with other things so appreciate the time.:good:
I have reduced the size of the files below, the first one is slightly large than the second. I cant reduce any more without reducing functionality, so if the first one doesn't work the second should, but at least 2 of the main issues, the adb shell problem and wrong reboot option will be fixed in both.
twrp2860v1
twrp2860v2
thanks again.
Click to expand...
Click to collapse
I flashed the 2nd one, and it seemed to work. Matter of fact I just flashed my updated rom with it. Worked so far.
Thanks for taking the time to bring us yet another working TWRP...
Thanks for testing guys. First post updated with final version.
I'm curious as to what the size of the recovery partition has been changed to. Could someone run the following command either in Terminal or ADB if you're running Lollipop?:
cat /proc/partitions
ashyx said:
Thanks for testing guys. First post updated with final version.
I'm curious as to what the size of the recovery partition has been changed to. Could someone run the following command either in Terminal or ADB if you're running Lollipop?:
cat /proc/partitions[/QUOTE
Just sent you a email message.
Click to expand...
Click to collapse
ashyx said:
Thanks for testing guys. First post updated with final version.
I'm curious as to what the size of the recovery partition has been changed to. Could someone run the following command either in Terminal or ADB if you're running Lollipop?:
cat /proc/partitions
Click to expand...
Click to collapse
Here you go:
Code:
cat /proc/partitions
major minor #blocks name
7 0 4180 loop0
7 1 32380 loop1
7 2 32380 loop2
253 0 1048576 vnswap0
179 0 30535680 mmcblk0
179 1 4096 mmcblk0p1
179 2 4096 mmcblk0p2
179 3 20480 mmcblk0p3
179 4 4096 mmcblk0p4
179 5 4096 mmcblk0p5
179 6 4096 mmcblk0p6
179 7 4096 mmcblk0p7
259 0 8192 mmcblk0p8
259 1 8192 mmcblk0p9
259 2 10240 mmcblk0p10
259 3 10240 mmcblk0p11
259 4 4096 mmcblk0p12
259 5 20480 mmcblk0p13
259 6 4096 mmcblk0p14
259 7 4096 mmcblk0p15
259 8 12288 mmcblk0p16
259 9 4096 mmcblk0p17
259 10 2467840 mmcblk0p18
259 11 204800 mmcblk0p19
259 12 337920 mmcblk0p20
259 13 27385856 mmcblk0p21
179 24 4096 mmcblk0rpmb
179 16 4096 mmcblk0boot1
179 8 4096 mmcblk0boot0
179 32 124868096 mmcblk1
179 33 124863488 mmcblk1p1
254 0 4180 dm-0
254 1 32380 dm-1
254 2 32380 dm-2
Eliminater74 said:
Here you go:
Code:
cat /proc/partitions
major minor #blocks name
7 0 4180 loop0
7 1 32380 loop1
7 2 32380 loop2
253 0 1048576 vnswap0
179 0 30535680 mmcblk0
179 1 4096 mmcblk0p1
179 2 4096 mmcblk0p2
179 3 20480 mmcblk0p3
179 4 4096 mmcblk0p4
179 5 4096 mmcblk0p5
179 6 4096 mmcblk0p6
179 7 4096 mmcblk0p7
259 0 8192 mmcblk0p8
259 1 8192 mmcblk0p9
259 2 10240 mmcblk0p10
259 3 10240 mmcblk0p11
259 4 4096 mmcblk0p12
259 5 20480 mmcblk0p13
259 6 4096 mmcblk0p14
259 7 4096 mmcblk0p15
259 8 12288 mmcblk0p16
259 9 4096 mmcblk0p17
259 10 2467840 mmcblk0p18
259 11 204800 mmcblk0p19
259 12 337920 mmcblk0p20
259 13 27385856 mmcblk0p21
179 24 4096 mmcblk0rpmb
179 16 4096 mmcblk0boot1
179 8 4096 mmcblk0boot0
179 32 124868096 mmcblk1
179 33 124863488 mmcblk1p1
254 0 4180 dm-0
254 1 32380 dm-1
254 2 32380 dm-2
Click to expand...
Click to collapse
The recovery partition size hasn't changed it's still 10mb -
2 10240 mmcblk0p10
The strange thing is, as a test I have somehow been able to flash a working 28mb recovery image to a 10mb partition under kitkat. Not sure how this is even possible!
ashyx said:
The recovery partition size hasn't changed it's still 10mb -
2 10240 mmcblk0p10
The strange thing is, as a test I have somehow been able to flash a working 28mb recovery image to a 10mb partition under kitkat. Not sure how this is even possible!
Click to expand...
Click to collapse
Hey buddy. I've flashed your version in the first post ( which was updated in 6th April right? ) but I can't reboot into twrp. Any update on that?
Regards
d3xtr0 said:
Hey buddy. I've flashed your version in the first post ( which was updated in 6th April right? ) but I can't reboot into twrp. Any update on that?
Regards
Click to expand...
Click to collapse
How are you trying to boot into recovery and which version tab s do you have?
You can also try the updated version here: http://forum.xda-developers.com/gal...p-2-8-6-1-unofficial-sm-t800-805-807-t3074633
Here is the stock partition table from the Xperia Z3 D6603
Code:
major minor #blocks name
253 0 524288 zram0
179 0 15388672 mmcblk0
179 1 2048 mmcblk0p1 TA
179 2 512 mmcblk0p2 sbl1
179 3 256 mmcblk0p3 s1sbl
179 4 64 mmcblk0p4 dbi
179 5 512 mmcblk0p5 aboot
179 6 512 mmcblk0p6 rpm
179 7 512 mmcblk0p7 tz
179 8 512 mmcblk0p8 alt_sbl1
179 9 512 mmcblk0p9 alt_s1sbl
179 10 64 mmcblk0p10 alt_dbi
179 11 512 mmcblk0p11 alt_aboot
179 12 512 mmcblk0p12 alt_rpm
179 13 512 mmcblk0p13 alt_tz
179 14 20480 mmcblk0p14 boot
179 15 10240 mmcblk0p15 ramdump
179 16 16384 mmcblk0p16 FOTAKernel
179 17 32 mmcblk0p17 DDR
179 18 16384 mmcblk0p18 LTALabel
179 19 1536 mmcblk0p19 modemst1
179 20 1536 mmcblk0p20 modemst2
179 21 1536 mmcblk0p21 fsg
179 22 8192 mmcblk0p22 apps_log
179 23 2609152 mmcblk0p23 system
179 24 204800 mmcblk0p24 cache
179 25 12359663 mmcblk0p25 userdata
179 32 4096 mmcblk0rpmb ?
179 64 31260672 mmcblk1 ?
179 65 31256576 mmcblk1p1 ?
This partition table may also work for the D6633, D6653, and D6616. But not having these devices I do not know.
I think mmcblk1 is SD card. Mine has two partitions and I have mmcblk1p2 too.
Hello, Last Night I Powered on My Phone in It Got Stuck at Starting Apps For About an Hour (Nexus Experience ROM)
So I Just Wiped Data and Cache and Rebooted But Now It Struck at Lenovo Log. I Went Again To Wipe But This Time Got Error
Unable to Mount Data/Cache.Tried To Mount It in TWRP But It Didnt only Able To Mount System. Tried To Install Custom Rom and Now Got Error Unable To Mount System/Cache/Data/Davlik Invalid Argument and So On.Now Even My System Partition Cant Be Mount. Tried To Flash Stock Firmware But Same Error and Even Flash From ADB Sideload Didnt Worked.in TWRP only Boot Partition is shown as 32 MB and Every Other is 0 MB. TWRP Says There is No OS Installed and Its stuck at Reboot Loop
TWRP Version 3.0
EDIT : Even Tried To Flash Using QFIL Tool and it Was Done Without any Error But When Phone Booted Up It Had Same Issue and Still Has TWRP.
I Was Able To Push Zip of a Custom Rom Into Data/Media Using Fastboot
Upon Applying Command
cat /proc/partitions it lists 34 Items
/proc # ←[6ncat /proc/partitions
major minor #blocks name
179 0 15392768 mmcblk0
179 1 65536 mmcblk0p1
179 2 512 mmcblk0p2
179 3 512 mmcblk0p3
179 4 1024 mmcblk0p4
179 5 1024 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 512 mmcblk0p9
179 10 512 mmcblk0p10
179 11 512 mmcblk0p11
179 12 1024 mmcblk0p12
179 13 1536 mmcblk0p13
179 14 1536 mmcblk0p14
179 15 1024 mmcblk0p15
179 16 1 mmcblk0p16
179 17 8 mmcblk0p17
179 18 10240 mmcblk0p18
179 19 32 mmcblk0p19
179 20 1536 mmcblk0p20
179 21 16 mmcblk0p21
179 22 32768 mmcblk0p22
179 23 1843200 mmcblk0p23 (System Partition)
179 24 32768 mmcblk0p24
179 25 268288 mmcblk0p25 (Cache)
179 26 32768 mmcblk0p26
179 27 512 mmcblk0p27
179 28 32 mmcblk0p28
179 29 65536 mmcblk0p29
179 30 12836847 mmcblk0p30 (Data)
179 32 4096 mmcblk0rpmb
179 64 31260672 mmcblk1
179 65 31256576 mmcblk1p1
df shows
/proc # ←[6ndf
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 971956 12 971944 0% /dev
tmpfs 971956 20 971936 0% /tmp
/dev/block/mmcblk1p1 31248384 30779296 469088 98% /external_sd
/dev/block/mmcblk1p1 31248384 30779296 469088 98% /and-sec
/proc # ←[6n
Any Help Would Be Highly Appreciated
zhee9130 said:
Hello, Last Night I Powered on My Phone in It Got Stuck at Starting Apps For About an Hour (Nexus Experience ROM)
So I Just Wiped Data and Cache and Rebooted But Now It Struck at Lenovo Log. I Went Again To Wipe But This Time Got Error
Unable to Mount Data/Cache.Tried To Mount It in TWRP But It Didnt only Able To Mount System. Tried To Install Custom Rom and Now Got Error Unable To Mount System/Cache/Data/Davlik Invalid Argument and So On.Now Even My System Partition Cant Be Mount. Tried To Flash Stock Firmware But Same Error and Even Flash From ADB Sideload Didnt Worked.in TWRP only Boot Partition is shown as 32 MB and Every Other is 0 MB. TWRP Says There is No OS Installed and Its stuck at Reboot Loop
TWRP Version 3.0
EDIT : Even Tried To Flash Using QFIL Tool and it Was Done Without any Error But When Phone Booted Up It Had Same Issue and Still Has TWRP.
I Was Able To Push Zip of a Custom Rom Into Data/Media Using Fastboot
Upon Applying Command
cat /proc/partitions it lists 34 Items
/proc # ←[6ncat /proc/partitions
major minor #blocks name
179 0 15392768 mmcblk0
179 1 65536 mmcblk0p1
179 2 512 mmcblk0p2
179 3 512 mmcblk0p3
179 4 1024 mmcblk0p4
179 5 1024 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 512 mmcblk0p9
179 10 512 mmcblk0p10
179 11 512 mmcblk0p11
179 12 1024 mmcblk0p12
179 13 1536 mmcblk0p13
179 14 1536 mmcblk0p14
179 15 1024 mmcblk0p15
179 16 1 mmcblk0p16
179 17 8 mmcblk0p17
179 18 10240 mmcblk0p18
179 19 32 mmcblk0p19
179 20 1536 mmcblk0p20
179 21 16 mmcblk0p21
179 22 32768 mmcblk0p22
179 23 1843200 mmcblk0p23 (System Partition)
179 24 32768 mmcblk0p24
179 25 268288 mmcblk0p25 (Cache)
179 26 32768 mmcblk0p26
179 27 512 mmcblk0p27
179 28 32 mmcblk0p28
179 29 65536 mmcblk0p29
179 30 12836847 mmcblk0p30 (Data)
179 32 4096 mmcblk0rpmb
179 64 31260672 mmcblk1
179 65 31256576 mmcblk1p1
df shows
/proc # ←[6ndf
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 971956 12 971944 0% /dev
tmpfs 971956 20 971936 0% /tmp
/dev/block/mmcblk1p1 31248384 30779296 469088 98% /external_sd
/dev/block/mmcblk1p1 31248384 30779296 469088 98% /and-sec
/proc # ←[6n
Any Help Would Be Highly Appreciated
Click to expand...
Click to collapse
CAN SOMEONE With A6000 PLus Upload Complete Image of emmc ? Thats The Hope of Reviving My Device. Thanks