Develop Bugs

[jfltexx][jflte][CWM Advanced Edition] PhilZ Touch

Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
Now: one common recovery for all: jflte
The jfltexx variant is no more updated, use jflte common variant
i9505 (jfltexx ---> jflte)
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
Click to expand...
Click to collapse
Big thanks to @wanam and @ausdim for their great support with providing kernels and support in compiling them

Nice to see you in SGS4 Forums Phil Keep your awesome work on
Where's my thanks?

Great to see you here. Download and flashed now.

Great
Waiting for first feedback to remove the scary red warning

Awesome PhilZ!
Someone please confirm this works fine!

Not Working by me. Black Screen in recovery. See only the Button on the bottom but the rest is black.
Edit: Ok working. Wait 1 Minute and the Screen is coming but the touch not working correct. The Hardware button also not correct working.

Yes Phil it's in the house!!!!

Can you give more details
Touch is completely dead or it behaves bad. In that case, how does it act (a video would be helpful)
What issue with hardware buttons
And is the black screen delay on each start

Phil3759 said:
Can you give more details
Touch is completely dead or it behaves bad. In that case, how does it act (a video would be helpful)
What issue with hardware buttons
And is the black screen delay on each start
Click to expand...
Click to collapse
Black Screen on each start yes. After 10 seconds i see the recovery. With the hardware buttons louder and quieter i can not select ever entry. Only every second i can select. With Touch nothing correct working. In Arome the bottom bottons not working. The Font are very small.
Sorry my English is not so good.

Same problems like Schrotty. After choosing something by touch, it seems the screen doesn't refresh. If I go up or down, the screen appears.
Also I tried to format /cache ... it says Done, but from that point I get the messages "Can't mount /cache/*" ... the problem all the recent recoverys had.
On the right top I see time ... it shows me 02:14 ... no wonder the recent recoveries couldn't have a correct time in backup for me. Strange why some users have correct time/date ....

@Phil3759,you need to modify graphics.c.

Chenglu said:
@Phil3759,you need to modify graphics.c.
Click to expand...
Click to collapse
Ah, thank you
However, without a cm source (I use common jflte) and a device to test (still only an i9100), i have no idea where to start to fix it

Phil3759 said:
Ah, thank you
However, without a cm source (I use common jflte) and a device to test (still only an i9100), i have no idea where to start to fix it
Click to expand...
Click to collapse
I send a PM to you.

Sir Phil, great to see you here!
One question : it is possible to include an autoroot option in your cwm, like it is in the Note recovery?
On S2 only flash your kernel, got cwm, got root, got everything together. Niw it us a little bit different. That's why i ask for the autoroot option.
Gesendet mit meinem S IV

Mr.AFK said:
Sir Phil, great to see you here!
One question : it is possible to include an autoroot option in your cwm, like it is in the Note recovery?
On S2 only flash your kernel, got cwm, got root, got everything together. Niw it us a little bit different. That's why i ask for the autoroot option.
Gesendet mit meinem S IV
Click to expand...
Click to collapse
On N7000 and I9100 the kernel and recovery were one .img.
Kernel contained recovery. Since S3 and up, recovery is a separate partition.
Code:
lrwxrwxrwx root root 1970-01-09 01:56 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-09 01:56 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-09 01:56 backup -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-09 01:56 boot -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-09 01:56 cache -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-09 01:56 carrier -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-09 01:56 efs -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-09 01:56 fota -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-09 01:56 fsg -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-09 01:56 hidden -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-09 01:56 m9kefs1 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-09 01:56 m9kefs2 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-09 01:56 m9kefs3 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-09 01:56 mdm -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-09 01:56 modemst1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-09 01:56 modemst2 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-09 01:56 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-09 01:56 param -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-09 01:56 persdata -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-09 01:56 persist -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-09 01:56 recovery -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-09 01:56 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-09 01:56 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-09 01:56 sbl2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-09 01:56 sbl3 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-09 01:56 ssd -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-09 01:56 system -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-09 01:56 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-09 01:56 userdata -> /dev/block/mmcblk0p29

Mr.AFK said:
Sir Phil, great to see you here!
One question : it is possible to include an autoroot option in your cwm, like it is in the Note recovery?
On S2 only flash your kernel, got cwm, got root, got everything together. Niw it us a little bit different. That's why i ask for the autoroot option.
Gesendet mit meinem S IV
Click to expand...
Click to collapse
In new cwm 6.0.3.2, Koush added a function to prompt you to root on recovery restart if you loose root
It will copy su binary to where it should
After that, just install Koush CWM Superuser from market and you are rooted

Can I use this method initially?
So flash your recovery on stock rom, boot into it, "enable root procedure", boot up und go to play an install superuser app?
That's all?
Gesendet mit meinem S IV

Hey Phil, nice to see you here. Always used your recovery on my note2.
I also get the black screen, I think it's because I use a different kernel. Faux123.
Maybe this helps a bit
Sent from the gt9505 galaxy s4

Mr.AFK said:
Can I use this method initially?
So flash your recovery on stock rom, boot into it, "enable root procedure", boot up und go to play an install superuser app?
That's all?
Gesendet mit meinem S IV
Click to expand...
Click to collapse
You could simply flash a superuser CWM zip with any recovery and you`re rooted.
Sent from my Xperia Arc S using xda premium

I am downloading the whole ROM to check a bit more the stock boot.img
Also, I think it is better to move some exfat modules to the ramdisk to avoid mounting /system which always ends up in some issues
Also, need to look at some scripts that could be needed on start
When I am done, I will release another repack
Thabk you @Chenglu for the support, I appreciate it a lot
Note: this phone is a bit different from i9500, and since I do not own one to test, it could be we need some debugging until it is done

ZTE Z995 Overture custom recovery

EDIT: Here's the recovery thread.
Original post:
So, let me preface this with the following statements:
I'm using Windows 7 x64 (Will eventually install a Unbuntu VM and set up a CM10.1 fork for a ROM)
I have not done this before, ever. I've always been the guy that just follows guides of proper devs to root my devices
So, I first needed to find the recovery partition, I found this thread. My by-name folder was in msm_sdcc.1
Code:
ls -al /dev/block/platform/msm_sdcc.1/by-name
lrwxrwxrwx root root 1970-01-06 07:55 aboot -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-06 07:55 boot -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-06 07:55 cache -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-06 07:55 fsg -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-06 07:55 grow -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-06 07:55 misc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-06 07:55 modem -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-06 07:55 modemst1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-06 07:55 modemst2 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-06 07:55 persist -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-06 07:55 recovery -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-06 07:55 rpm -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-06 07:55 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-06 07:55 sbl2 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-06 07:55 sbl3 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-06 07:55 splash -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-06 07:55 ssd -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-06 07:55 system -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-06 07:55 tombstones -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-06 07:55 tz -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-06 07:55 userdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-06 07:55 ztecfg -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-06 07:55 ztelk -> /dev/block/mmcblk0p6
I then used:
Code:
dd if=/dev/block/mmcblk0p16 of=/sdcard/recovery.img
I then used the CWM Recovery Builder to build a basic recovery.
I took that image, pushed to /sdcard/rec.img and tried the following as root:
Code:
flash_image recovery /sdcard/recv.img
error scanning partitions: No such file or directory
flash_image mmcblk0p16 /sdcard/recv.img
error scanning partitions: No such file or directory
flash_image /dev/block/mmcblk0p16 /sdcard/recv.img
error scanning partitions: No such file or directory
So I tried dd instead:
Code:
dd if=/sdcard/rec.img of=/dev/block/mmcblk0p16
Then attempted to reboot into recovery with adb... no dice, I then redump the recovery to see if it's still ~8MB instead of 16MB. Nope, back to 16MB.
I also tried using fastboot flash recovery while it was in the bootloader, also failed with the same results.
So if someone wouldn't mind pointing me in the right direction, that would be awesome.

Nobody?

METDeath said:
Nobody?
Click to expand...
Click to collapse
If you could upload the recovery.img, boot.img, as well as the output of "cat /proc/partitions", I'll have a custom recovery for you in as long as it takes for my computer to build it!
Also, if you could get me /proc/config.gz, that would be awesome.

cooldudezach said:
If you could upload the recovery.img, boot.img, as well as the output of "cat /proc/partitions", I'll have a custom recovery for you in as long as it takes for my computer to build it!
Also, if you could get me /proc/config.gz, that would be awesome.
Click to expand...
Click to collapse
Sadly, I was going to sell the phone... did a factory reset, that didn't end up so well. So fighting with ZTE to get it repaired (boot loop, displays ZTE logo then black screen). I can get the phone into FTM mode, but not recovery. I even made it a point to flash the original factory.img after every failed attempt.
It was literally two days outside of the return to store window too.

METDeath said:
Sadly, I was going to sell the phone... did a factory reset, that didn't end up so well. So fighting with ZTE to get it repaired (boot loop, displays ZTE logo then black screen). I can get the phone into FTM mode, but not recovery. I even made it a point to flash the original factory.img after every failed attempt.
It was literally two days outside of the return to store window too.
Click to expand...
Click to collapse
If you still have the phone, I can probably still save it. I've already saved 4 devices that are based on the same hardware this phone is (ZTE Awe, ZTE Sourcex2, ZTE Warp4g), and they were worse off
Especially if you can get into FTM mode, that means the boot.img is still functioning properly, just there is something causing the phone to loop. I'm assuming it loops while trying to get into recovery? Where did you get the factory.img?
---------- Post added at 11:53 AM ---------- Previous post was at 11:43 AM ----------
METDeath said:
So, let me preface this with the following statements:
I'm using Windows 7 x64 (Will eventually install a Unbuntu VM and set up a CM10.1 fork for a ROM)
I have not done this before, ever. I've always been the guy that just follows guides of proper devs to root my devices
So, I first needed to find the recovery partition, I found this thread. My by-name folder was in msm_sdcc.1
Code:
ls -al /dev/block/platform/msm_sdcc.1/by-name
lrwxrwxrwx root root 1970-01-06 07:55 aboot -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-06 07:55 boot -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-06 07:55 cache -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-06 07:55 fsg -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-06 07:55 grow -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-06 07:55 misc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-06 07:55 modem -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-06 07:55 modemst1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-06 07:55 modemst2 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-06 07:55 persist -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-06 07:55 recovery -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-06 07:55 rpm -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-06 07:55 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-06 07:55 sbl2 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-06 07:55 sbl3 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-06 07:55 splash -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-06 07:55 ssd -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-06 07:55 system -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-06 07:55 tombstones -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-06 07:55 tz -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-06 07:55 userdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-06 07:55 ztecfg -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-06 07:55 ztelk -> /dev/block/mmcblk0p6
I then used:
Code:
dd if=/dev/block/mmcblk0p16 of=/sdcard/recovery.img
I then used the CWM Recovery Builder to build a basic recovery.
I took that image, pushed to /sdcard/rec.img and tried the following as root:
Code:
flash_image recovery /sdcard/recv.img
error scanning partitions: No such file or directory
flash_image mmcblk0p16 /sdcard/recv.img
error scanning partitions: No such file or directory
flash_image /dev/block/mmcblk0p16 /sdcard/recv.img
error scanning partitions: No such file or directory
So I tried dd instead:
Code:
dd if=/sdcard/rec.img of=/dev/block/mmcblk0p16
Then attempted to reboot into recovery with adb... no dice, I then redump the recovery to see if it's still ~8MB instead of 16MB. Nope, back to 16MB.
I also tried using fastboot flash recovery while it was in the bootloader, also failed with the same results.
So if someone wouldn't mind pointing me in the right direction, that would be awesome.
Click to expand...
Click to collapse
I figured I'd go ahead and answer you problems/questions here.
First off, flash_image isn't going to work, stop using it. Second, fastboot flash doesn't work on this line of devices, again, stop using it.
When using dd, you should always zero out the partition first to make sure you aren't leaving behind anything from what was there before:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p16
The reason it's 'back' to 16MB, is because that is the size of the partition. It's just got a lot of 0's on the end. Everytime you pull it, it will always end up as a 16MB image. If you still have a copy of the stock recovery.img you pulled, I would appreciate a copy

cooldudezach said:
If you still have the phone, I can probably still save it. I've already saved 4 devices that are based on the same hardware this phone is (ZTE Awe, ZTE Sourcex2, ZTE Warp4g), and they were worse off
Especially if you can get into FTM mode, that means the boot.img is still functioning properly, just there is something causing the phone to loop. I'm assuming it loops while trying to get into recovery? Where did you get the factory.img?
---------- Post added at 11:53 AM ---------- Previous post was at 11:43 AM ----------
I figured I'd go ahead and answer you problems/questions here.
First off, flash_image isn't going to work, stop using it. Second, fastboot flash doesn't work on this line of devices, again, stop using it.
When using dd, you should always zero out the partition first to make sure you aren't leaving behind anything from what was there before:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p16
The reason it's 'back' to 16MB, is because that is the size of the partition. It's just got a lot of 0's on the end. Everytime you pull it, it will always end up as a 16MB image. If you still have a copy of the stock recovery.img you pulled, I would appreciate a copy
Click to expand...
Click to collapse
Well, I dumped the stock img with dd, I am fairly sure I still the stock recovery (sooo many files, hopefully this is it, however, looking at the file size when zipped it may not be).
I also PM'd one of the guys from the root thread who may be able to help with .img files as well.
I still have the device, I'm using Win7 primarily, but have an Unbuntu VM that I was going to use to attempt to build a CM10 port for the phone.
Also, I have a fairly decent CPU (AMD Phenom II x6 2.8) so I don't mind doing the build work.

METDeath said:
Well, I dumped the stock img with dd, I am fairly sure I still the stock recovery (sooo many files, hopefully this is it, however, looking at the file size when zipped it may not be).
I also PM'd one of the guys from the root thread who may be able to help with .img files as well.
I still have the device, I'm using Win7 primarily, but have an Unbuntu VM that I was going to use to attempt to build a CM10 port for the phone.
Also, I have a fairly decent CPU (AMD Phenom II x6 2.8) so I don't mind doing the build work.
Click to expand...
Click to collapse
Thanks! So does your phone boot normally, or does it bootloop? I wasn't sure when you wrote that if you were just referring to the recovery boot or not. FTM is integrated with boot.img, which is why i am confused lol.
I'm just trying to figure out what's wrong exactly so I can get your phone up and running.
If you want to hop into irc chac #zte8930 on freenode, that's where I hang out, and where the devs for this group of phones also hangout.

For anyone looking in on this, the problem was fixed and there is now a PhilZ CWM for the phone.

METDeath said:
Well, I dumped the stock img with dd, I am fairly sure I still the stock recovery (sooo many files, hopefully this is it, however, looking at the file size when zipped it may not be).
I also PM'd one of the guys from the root thread who may be able to help with .img files as well.
I still have the device, I'm using Win7 primarily, but have an Unbuntu VM that I was going to use to attempt to build a CM10 port for the phone.
Also, I have a fairly decent CPU (AMD Phenom II x6 2.8) so I don't mind doing the build work.
Click to expand...
Click to collapse
is that can be use？i want to transplant a msm8960 device's rom so i need a custom recovery.

chongbos said:
is that can be use？i want to transplant a msm8960 device's rom so i need a custom recovery.
Click to expand...
Click to collapse
Since I'm not the creator of the port I won't post it here, and it's on another Androidforums so not sure how XDA feels about linking to another forum. There is a group of guys creating ports for lots of MSM8960 devices over there though.

METDeath said:
Since I'm not the creator of the port I won't post it here, and it's on another Androidforums so not sure how XDA feels about linking to another forum. There is a group of guys creating ports for lots of MSM8960 devices over there though.
Click to expand...
Click to collapse
so..can i flash this .img to my z995? is that offical or custom?
ATTACHED FILES
zte 995 stock recovery.zip - [Click for QR Code] (6.83 MB, 9 views)
thanks.sorry for my poor english!
---------- Post added at 10:13 AM ---------- Previous post was at 10:09 AM ----------
METDeath said:
Since I'm not the creator of the port I won't post it here, and it's on another Androidforums so not sure how XDA feels about linking to another forum. There is a group of guys creating ports for lots of MSM8960 devices over there though.
Click to expand...
Click to collapse
oh,i have been focus on this forum for a long time,and now i have found it.thank u a lot.
---------- Post added at 10:24 AM ---------- Previous post was at 10:13 AM ----------
METDeath said:
Well, I dumped the stock img with dd, I am fairly sure I still the stock recovery (sooo many files, hopefully this is it, however, looking at the file size when zipped it may not be).
I also PM'd one of the guys from the root thread who may be able to help with .img files as well.
I still have the device, I'm using Win7 primarily, but have an Unbuntu VM that I was going to use to attempt to build a CM10 port for the phone.
Also, I have a fairly decent CPU (AMD Phenom II x6 2.8) so I don't mind doing the build work.
Click to expand...
Click to collapse
btw.
can u help me?
i have an old device GT-i9008L.it's a custom-made device from GT-i9003.
For now im willing to transplant a custom rom so im making a custom recovery before it.
but i cant let recovery mount SDcard...maybe i dont know how to editor it.
can u help me?only transplant i9003's custom recovery can take it easy.
thanks. sorry for my poor english!

chongbos said:
so..can i flash this .img to my z995? is that offical or custom?
ATTACHED FILES
zte 995 stock recovery.zip - [Click for QR Code] (6.83 MB, 9 views)
btw.
can u help me?
i have an old device GT-i9008L.it's a custom-made device from GT-i9003.
For now im willing to transplant a custom rom so im making a custom recovery before it.
but i cant let recovery mount SDcard...maybe i dont know how to editor it.
can u help me?only transplant i9003's custom recovery can take it easy.
thanks. sorry for my poor english!
Click to expand...
Click to collapse
The attached is the official recovery for the ZTE Z995 Overture (code name becky) that was sold in the US, so it's in English, it's also not a flashable zip as it's just the output of the dd command from the shell compressed into a zip file for smaller size.
I'm afraid I'm not able to help much with creating your own custom recovery as I'm not a developer. Perhaps you should create your own thread with more details on your phone.
Your English is actually better than some native English speakers, so keep up the practice and good work!

METDeath said:
The attached is the official recovery for the ZTE Z995 Overture (code name becky) that was sold in the US, so it's in English, it's also not a flashable zip as it's just the output of the dd command from the shell compressed into a zip file for smaller size.
I'm afraid I'm not able to help much with creating your own custom recovery as I'm not a developer. Perhaps you should create your own thread with more details on your phone.
Your English is actually better than some native English speakers, so keep up the practice and good work!
Click to expand...
Click to collapse
hah，it's really funny to met u.
i will back contact u~~~~
thanks.

Hmmmm METdeath, perhaps you could enlighten me (pm) the whereabouts of said recovery and other useful info.
If wanted a custom recovery and ROM on this phone since day 1 . I kinda gave up on any hope for it. Please any information to lead me in the correct direction would be greatly appreciated.

METDeath said:
For anyone looking in on this, the problem was fixed and there is now a PhilZ CWM for the phone.
Click to expand...
Click to collapse
Where is a link to this recovery?

Does anybody know where to get a firmware for new ZTE devices, like Z995, Z993, z740 etc?

Hello Help PLZ!!
Hello, I have a softed bricked zte overture z995. I saw in one of your replies you are familiar with reflashing this ROM. Is there any possible way that you can help guide me in fixing this problem? I'm not too familiar with all the concepts. I will be forever grateful!!! THanks!
~Caleb
METDeath said:
Well, I dumped the stock img with dd, I am fairly sure I still the stock recovery (sooo many files, hopefully this is it, however, looking at the file size when zipped it may not be).
I also PM'd one of the guys from the root thread who may be able to help with .img files as well.
I still have the device, I'm using Win7 primarily, but have an Unbuntu VM that I was going to use to attempt to build a CM10 port for the phone.
Also, I have a fairly decent CPU (AMD Phenom II x6 2.8) so I don't mind doing the build work.
Click to expand...
Click to collapse

Updated first post with the URL to the recovery.

[Q] How to recover data and reset flash counter when phone won't boot

My S3 went haywire a few days ago and in my attempts to recover data I loaded the TWRP bootloader and a custom ROM hoping I could eventually reboot it and reset the flash counter. Unfortunately, it still won't reboot - it hangs on the pulsing SAMSUNG animation, after the "Samsung Galaxy SIII" splash screen and the Android blast-off animation.
I've already done a cache wipe and factory reset so ideally I'd like to get it into a state where I can run data recovery software to retrieve my deleted files. But if that can't be done, at the least I want to reset the flash counter so the phone will be replaced under warranty.
Since I received the last replacement in Oct 2013 I forgot to enable USB Debugging and I didn't root phone. In my searches, it looks like the power button is stuck (doesn't feel like it, though) and the phone randomly reboots when is Recovery Mode or Download Mode. About 10% of the time I can get it into either mode and remain stable.
Tools I downloaded & installed:
SkipSoft Android Toolkit (updated and registered)
Samsung USB Drivers v1.5.42.0
Google ADT (updated)
Odin 3.09
Here's what I haven/haven't done so far:
Haven't enabled USB Debugging in the OS
Haven't rooted phone
Installed TWRP 2.7.0.0
Installed root66_TMO_T999UVDMD5.tar, but device still won't boot completely
After TWRP installed, I had to updated driver in Device Manager to "Intel USB Flash Loader Utility" from Samsung. In the TWRP logs I see:
E: Could not mount /data and unable to find crypto footer.
E: Unable to mount '/data'
E: Unable to recreate /data/media folder.
Updating partition details...
E: Unable to mount '/data'
E: Unable to mount internal storage.
E: Unable to mount /data/media during GUI startup.
Full SELinux support is present.
Running boot script...
Finished running boot script.
E: Unable to mount /data/media/TWRP/.twrps when trying to read settings file.
E: Unable to mount '/data'
Do I have any hope of recovering the data or resetting the flash counter? I've also considered trying JTAG recovery through a local vendor, but still would like to reset the counter.
Thanks - any help would be GREATLY appreciated.

some progress
OK, with some persistence I managed to get the device to a bootable state. I managed to installed TWRP Bootloader and Chainfire's SuperUser, and that got the phone bootable. Android version is 4.1.2, USB Debugging is now ON, and I went through the setup process but disabled all antennas once I noticed it was downloading content.... PHEW...
For anyone dealing with this issue, here's what worked and didn't:
1 - Spraying CRC brand circuit cleaner on power button - didn't try it, too lazy/scared that I'd break something else
2 - Knocking Power button with a pencil eraser (found elsewhere in xda-developers forum) - this seemed to clear up the issue intermittently
3 - Loaded TWRP using Odin - this worked
4 - Loaded Chainfire AutoRoot - this failed when using miscellaneous tutorials online, BUT it worked when I went straight to the CF Autoroot site (autoroot.chainfire.eu) downloaded the specific file for my device, and loaded it via Odin
Now I'm trying to get data recovery software to recognize the device to analyze the drive and find any recoverable data. Any suggestions?
So far I've tried:
Recuva - unable to see phone
Asoftech Data Recovery - unable to see phone
Glary Undelete - unable to see phone
yodot - unable to see phone

Search xda for an app called Easy UMS. (I think). Then use it to connect as a USB Mass Storage device. If that doesn't help im not sure what else to tell you.

DocHoliday77 said:
Search xda for an app called Easy UMS. (I think). Then use it to connect as a USB Mass Storage device. If that doesn't help im not sure what else to tell you.
Click to expand...
Click to collapse
DocHoliday - thanks for the tip, but Easy UMS only allows access to the external SD card. I'm continuing my search. There must be something that at least allows a full bit-wise backup of the entire device to an SD card that I can then use for forensics.

maradamc said:
DocHoliday - thanks for the tip, but Easy UMS only allows access to the external SD card. I'm continuing my search. There must be something that at least allows a full bit-wise backup of the entire device to an SD card that I can then use for forensics.
Click to expand...
Click to collapse
It looks like BusyBox and the DD command can create a bit-by-bit partition dump but I'm not sure how to issue the commands. I have ADB and SU access, BusyBox installed.

dd if=/dev/block/mmcblk0p15 of=c:\path\saving\to
This will dump the entire userdata partition to an image file on your Windows computer. Note the direction of the /'s.

Thanks Doc! I reformatted my external SD Card to exFAT, then ran the DD command to dump the userdata partition. I'm using DiskInternals Linux Recovery right now to scan the image for any recoverable files.
Where can I find more info on those different partitions in /dev/block/? I think some of the files I want to recover are in /data/data/ and I don't know which partition that would be. I've tried "mount" and "ls -l /dev/block/platform/*/by-name/" but I can't find any reference to a /data/ mount.
My last shot will be to downgrade the OS to ICS version and try data recovery directly via the USB cable. All this stuff I'm finding sure will make a good tutorial afterwards.

The dump you created is the entire /data partition. So it should have everything you need. (Userdata/data, same thing in this case. Sorry if I wasn't more clear on that)
You can google t999 galaxy s3 partition layout and should be able to find the rest. Don't have time to look it up and write it ir I'd just post it here for you.

I did some digging and found I need to pull data from:
/sdcard/callrecorder/
/storage/emulated/0/sounds/
I'm trying to decipher if I need to dump any additional partitions. No luck finding much useful information on S3 partitions - this was the closest I found - http://forum.xda-developers.com/galaxy-s3/general/galaxy-s-iii-partition-layout-basic-efs-t1689623
In ADB, I retrieved the following, but none of them obviously map to sdcard or storage/emulated.
ls -l /dev/block/platform/*/by-name/
lrwxrwxrwx root root 1969-12-31 22:16 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1969-12-31 22:16 backup -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1969-12-31 22:16 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1969-12-31 22:16 cache -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1969-12-31 22:16 efs -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1969-12-31 22:16 fota -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1969-12-31 22:16 fsg -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1969-12-31 22:16 grow -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1969-12-31 22:16 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1969-12-31 22:16 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1969-12-31 22:16 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1969-12-31 22:16 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1969-12-31 22:16 param -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1969-12-31 22:16 persist -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1969-12-31 22:16 recovery -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1969-12-31 22:16 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1969-12-31 22:16 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1969-12-31 22:16 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1969-12-31 22:16 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1969-12-31 22:16 ssd -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1969-12-31 22:16 system -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1969-12-31 22:16 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1969-12-31 22:16 userdata -> /dev/block/mmcblk0p15
[email protected]:/ # mount
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,relatime,gid=1000,fmask=0006,dmask=0006,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
/dev/block/platform/msm_sdcc.1/by-name/efs /efs ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
Additionally, the DD for userdata is 12GB while the whole device is 16GB... still trying to figure out how to capture the remaining 4GB. And to complicate things, I've gotten data recovery software to recognize the image dump and scan it, but the files I want have uncommon file extensions (*.m4a, *.3ga) or no extensions at all. <sigh>... it's gonna be a long week...

The 4gb is reserved for the os and firmware. So a 16gb S3 will have 12gb allocated for /data.
The internal sdcard is not a partition of its own. Its simply part of the data partition.
Also, the link you provided is for the I9300, the international S3 which is a very different device with a different partition layout.
This is ours:
Code:
Number Start End Size FS-Type Name Flags
-------------------------------------------------------------------------------
1 4194304B 67108863B 62914560B modem
2 67108864B 67239935B 131072B sbl1
3 67239936B 67502079B 262144B sbl2
4 67502080B 68026367B 524288B sbl3
5 68026368B 70123519B 2097152B aboot
6 70123520B 70647807B 524288B rpm
7 70647808B 81133567B 10485760B boot
8 81133568B 81657855B 524288B tz
9 81657856B 82182143B 524288B pad
10 82182144B 92667903B 10485760B param
11 92667904B 106954751B 14286848B ext4 efs
12 106954752B 110100479B 3145728B modemst1
13 110100480B 113246207B 3145728B modemst2
14 113246208B 1686110207B 1572864000B ext4 system
15 1686110208B 30337400831B 28651290624B ext4 userdata
16 30337400832B 30345789439B 8388608B ext4 persist
17 30345789440B 31226593279B 880803840B ext4 cache
18 31226593280B 31237079039B 10485760B recovery
19 31237079040B 31247564799B 10485760B fota
20 31247564800B 31253856255B 6291456B backup
21 31253856256B 31257001983B 3145728B fsg
22 31257001984B 31257010175B 8192B ssd
23 31257010176B 31262253055B 5242880B grow
(Just thought it might be a little easier to read this way)
As for pulling the files you need from the .img and the unknown extensions, im not sure. Are you using linux or Windows?

Thanks for that table! I noticed that link wasn't for the T999, which is why I hesitated to rely on it. IDK why I'm having such a hard time finding info on the T999.
Anyway, I managed to DD every single partition by running:
dd if=/dev/block/mmcblk0p5 of=/storage/extSdCard/aboot.img
dd if=/dev/block/mmcblk0p20 of=/storage/extSdCard/backup.img
dd if=/dev/block/mmcblk0p7 of=/storage/extSdCard/boot.img
dd if=/dev/block/mmcblk0p17 of=/storage/extSdCard/cache.img
dd if=/dev/block/mmcblk0p11 of=/storage/extSdCard/efs.img
dd if=/dev/block/mmcblk0p19 of=/storage/extSdCard/fota.img
dd if=/dev/block/mmcblk0p21 of=/storage/extSdCard/fsg.img
dd if=/dev/block/mmcblk0p23 of=/storage/extSdCard/grow.img
dd if=/dev/block/mmcblk0p9 of=/storage/extSdCard/pad.img
dd if=/dev/block/mmcblk0p10 of=/storage/extSdCard/param.img
dd if=/dev/block/mmcblk0p16 of=/storage/extSdCard/persist.img
dd if=/dev/block/mmcblk0p18 of=/storage/extSdCard/recovery.img
dd if=/dev/block/mmcblk0p6 of=/storage/extSdCard/rpm.img
dd if=/dev/block/mmcblk0p2 of=/storage/extSdCard/sb11.img
dd if=/dev/block/mmcblk0p3 of=/storage/extSdCard/sb12.img
dd if=/dev/block/mmcblk0p4 of=/storage/extSdCard/sb13.img
dd if=/dev/block/mmcblk0p22 of=/storage/extSdCard/ssd.img
dd if=/dev/block/mmcblk0p14 of=/storage/extSdCard/system.img
dd if=/dev/block/mmcblk0p8 of=/storage/extSdCard/tz.img
dd if=/dev/block/mmcblk0p15 of=/storage/extSdCard/userdata.img
For data recovery, I'm running windows and have installed several tools so I'm able to mount the Linux image as a drive.
Cygwin - I've only played with basics in *nix terminal but am comfortable using command prompt
Ext2Fsd
DiskInternals (Linux Reader & Recovery)
OSFMount
I'll tally up the data recovery/carving tools I've downloaded and tried. Now that I have the images dumped, I'm installing ICS 4.0.4 in an attempt to get USB drive access and try the data recovery software directly against the device.

It may seem difficult to find info on the T999, but a lot of that is due to it being posted in other S3 forums. All US S3's are similar enough that most information applies to all of them. The partition table is one of these. They all are partitioned exactly the same.
Btw, when looking for the internal sdcard data, it will be in the /data/media folder. So in the image just look for the media folder.

I will remember that. Any suggestions where to track down /storage/emulated/0/sounds/ from a partition perspective?
I just finished flashing down to ICS 4.0.4. Even though Odin said it was successful, it's hanging on boot-up at the pulsing Samsung logo just like when this whole mess started. Time for another Factory Reset... not like I can do any more harm.

/storage/emulated/0 = /data/media

Nice! My list of pulled partitions matches the one you provided. Glad to know I was on the right track.
So now I have Android 4.0.4 installed on my device. The problem I have now is that the device isn't recognized in Windows and I can't find a driver for it to work. I've tried Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0 and v1.5.42.0 - no go. Also tried the ADT driver (android_winusb.inf), still no go. Also tried the driver bundled with the Unified Android Toolkit (by SkipSoft, an XDA dev'r) - no luck. Any suggestions? It must be a driver that supports the old USB Drive mode instead of MTP.
For others who might try this downgrade, I rebooted the device into Download mode and during installation, Odin kept getting an error before finishing. I think it was because I was trying to multitask on the computer because once I let Odin do its thing with and stepped away from the PC, the installation completed successfully. Reboots then kept freezing up but a Factory Reset resolved that.

The S3 never supported using UMS (USB drive), so using different driver versions won't make any difference there. Im honestly not sure if anyone's ever found a way to do this at all. Other than the Easy UMS app.

[APP] Boot Logo Changer [2016/04/05]

Boot Logo Changer
Change the boot image (NOT the bootanimation) that shows BEFORE the boot animation.
This has only been tested on the P901, but should work on other Galaxy Note Pro 12.2s.
If in doubt, check to see if your PARAM partition is mmcblk0p8.
There are programs on the Play Store that can show the partitions, there names and other info.
This app does make a backup of the original PARAM partition and stores it on your /sdcard as PARAM.bak.
MAKE SURE YOUR SDCARD IS MOUNTED WHEN YOU GET INTO TWRP or CWM.
(Have NOT tested in CWM as I have TWRP installed).
Many thanks to [email protected] for the original script for the Samsung Galaxy Tab 3 8.0.
He has kindly allowed me to modify his script for the Note Pro 12.2.
His xda page is: Samsung Galaxy Tab 3 8.0 Boot Logo
To change the logo (.jpg file), replace the logo.jpg in the tmp folder with your own .jpg file.
Remember the Galaxy Note Pro 12.2 display is 2560x1600.
Steps to install:
- Reboot into recovery
- Select Install from recovery menu
- Select P901-BootLogoChanger.zip
- Follow recovery install prompts
- Reboot and enjoy!
If you need a restore script, please contact me or post a message.
Downloads:
Google: P901-BootLogoChanger.zip
Mega: P901-BootLogoChanger.zip

Great work.

emremutlu said:
Great work.
Click to expand...
Click to collapse
Thanks!

It was working. Now unable to boot to twrp. Can get to download and Odin is flashing. Will a current firmware Odin flash get me booting again? Thank you
Sent from my Nexus 7 2013 using XDA-Developers mobile app

amityg said:
It was working. Now unable to boot to twrp. Can get to download and Odin is flashing. Will a current firmware Odin flash get me booting again? Thank you
Sent from my Nexus 7 2013 using XDA-Developers mobile app
Click to expand...
Click to collapse
Got it booting again by using the param t311 Odin file. Now I will fix with the backup file. Thank you. I still going to use custom logo.jpg as it looks clean.
Sent from my Nexus 7 2013 using XDA-Developers mobile app

gcrutchr said:
Boot Logo Changer
This has only been tested on the P901, but should work on other Galaxy Note Pro 12.2s.
If in doubt, check to see if your PARAM partition is mmcblk0p8.
Click to expand...
Click to collapse
On P900 can confirm PARAM is still partition mmcblk0p8.
[email protected]:/ $ ls -l /dev/block/platform/dw_mmc.0/by-name
lrwxrwxrwx root root 2016-07-13 15:11 BOOT -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2016-07-13 15:11 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2016-07-13 15:11 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2016-07-13 15:11 CACHE -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2016-07-13 15:11 CARRIER -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2016-07-13 15:11 CDMA-RADIO -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2016-07-13 15:11 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2016-07-13 15:11 HIDDEN -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2016-07-13 15:11 OTA -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2016-07-13 15:11 PARAM -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2016-07-13 15:11 PERSDATA -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2016-07-13 15:11 RADIO -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2016-07-13 15:11 RECOVERY -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2016-07-13 15:11 RESERVED2 -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2016-07-13 15:11 SYSTEM -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2016-07-13 15:11 TDATA -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2016-07-13 15:11 TOMBSTONES -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2016-07-13 15:11 USERDATA -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2016-07-13 15:11 m9kefs1 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2016-07-13 15:11 m9kefs2 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2016-07-13 15:11 m9kefs3 -> /dev/block/mmcblk0p6
So this should work, will try and report back.
Edit: worked just fine, p900 users are safe.

Gatsrom said:
On P900 can confirm PARAM is still partition mmcblk0p8.
[email protected]:/ $ ls -l /dev/block/platform/dw_mmc.0/by-name
lrwxrwxrwx root root 2016-07-13 15:11 BOOT -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2016-07-13 15:11 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2016-07-13 15:11 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2016-07-13 15:11 CACHE -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2016-07-13 15:11 CARRIER -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2016-07-13 15:11 CDMA-RADIO -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2016-07-13 15:11 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2016-07-13 15:11 HIDDEN -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2016-07-13 15:11 OTA -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2016-07-13 15:11 PARAM -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2016-07-13 15:11 PERSDATA -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2016-07-13 15:11 RADIO -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2016-07-13 15:11 RECOVERY -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2016-07-13 15:11 RESERVED2 -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2016-07-13 15:11 SYSTEM -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2016-07-13 15:11 TDATA -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2016-07-13 15:11 TOMBSTONES -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2016-07-13 15:11 USERDATA -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2016-07-13 15:11 m9kefs1 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2016-07-13 15:11 m9kefs2 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2016-07-13 15:11 m9kefs3 -> /dev/block/mmcblk0p6
So this should work, will try and report back.
Edit: worked just fine, p900 users are safe.
Click to expand...
Click to collapse
Great to here it worked!
Make sure you keep a backup of the original PARAM file just in case you want to go back to stock.

where do i locate tmp folder with logo.jpg to replace with another logo
gcrutchr said:
Boot Logo Changer
Change the boot image (NOT the bootanimation) that shows BEFORE the boot animation.
This has only been tested on the P901, but should work on other Galaxy Note Pro 12.2s.
If in doubt, check to see if your PARAM partition is mmcblk0p8.
There are programs on the Play Store that can show the partitions, there names and other info.
This app does make a backup of the original PARAM partition and stores it on your /sdcard as PARAM.bak.
MAKE SURE YOUR SDCARD IS MOUNTED WHEN YOU GET INTO TWRP or CWM.
(Have NOT tested in CWM as I have TWRP installed).
Many thanks to [email protected] for the original script for the Samsung Galaxy Tab 3 8.0.
He has kindly allowed me to modify his script for the Note Pro 12.2.
His xda page is: Samsung Galaxy Tab 3 8.0 Boot Logo
To change the logo (.jpg file), replace the logo.jpg in the tmp folder with your own .jpg file.
Remember the Galaxy Note Pro 12.2 display is 2560x1600.
Steps to install:
- Reboot into recovery
- Select Install from recovery menu
- Select P901-BootLogoChanger.zip
- Follow recovery install prompts
- Reboot and enjoy!
If you need a restore script, please contact me or post a message.
Downloads:
Google: P901-BootLogoChanger.zip
Mega: P901-BootLogoChanger.zip
Click to expand...
Click to collapse

anayajade said:
Click to expand...
Click to collapse
It's in the .zip file

Back up
Hi, thanks for thisgreat work. Running a modified version of stock rom lollipop, where can I find my tmp folder with logo.jpg to make a backup incase something goes wrong?
Edit: re-read the op and understood the second time. Works great on p900

bricked
hi, I think I bricked my p900 using this zip file. At first everything went good, then I tried a different logo.png in the temp file and now my p900 wont boot at all, it goes in download mode only, not even recovery works.
Tried odin back to stock but still nothing.
I was on civZ p900 lollipop 5.0.2 with latest twrp recovery before. Can anyone help me please

coco1476 said:
hi, I think I bricked my p900 using this zip file. At first everything went good, then I tried a different logo.png in the temp file and now my p900 wont boot at all, it goes in download mode only, not even recovery works.
Tried odin back to stock but still nothing.
I was on civZ p900 lollipop 5.0.2 with latest twrp recovery before. Can anyone help me please
Click to expand...
Click to collapse
Please explain what you did the 1st time.
What size is the new logo.png (2560x1600 ?) ; also what is the file size of the logo.png?
How did you replace the logo.png file?
How did you try to go back to stock? With a custom rom or a stock .md5 rom?

gcrutchr said:
Please explain what you did the 1st time.
What size is the new logo.png (2560x1600 ?) ; also what is the file size of the logo.png?
How did you replace the logo.png file?
How did you try to go back to stock? With a custom rom or a stock .md5 rom?
Click to expand...
Click to collapse
Hi, I manage to find a complete firmware including pit, bootloader and csc to install with odin and it's alive again.
The new logo was 2560x1600 but I can't recall the file size. I used ES File Explorer apk to copy the new logo image to the temp folder in the zip file and deleted the original logo.png.
I downloaded the latest stock firmare on Sam mobile for my p900 and used odin, everything went perfect with odin but it rebooted in download mode again, no access to recovery, I tried every methods I know to boot in recovery but it didn't work.
So I found a complete Arabic 4.4.2 stock firmware and used odin and boom everything is back an running now, got 5.0.2 OTA update up and running

coco1476 said:
Hi, I manage to find a complete firmware including pit, bootloader and csc to install with odin and it's alive again.
The new logo was 2560x1600 but I can't recall the file size. I used ES File Explorer apk to copy the new logo image to the temp folder in the zip file and deleted the original logo.png.
I downloaded the latest stock firmare on Sam mobile for my p900 and used odin, everything went perfect with odin but it rebooted in download mode again, no access to recovery, I tried every methods I know to boot in recovery but it didn't work.
So I found a complete Arabic 4.4.2 stock firmware and used odin and boom everything is back an running now, got 5.0.2 OTA update up and running
Click to expand...
Click to collapse
Good to hear you are back up and running ok. Make sure you copy the backup file of the logo partition to your PC for safe keeping.

coco1476 said:
Hi, I manage to find a complete firmware including pit, bootloader and csc to install with odin and it's alive again.
The new logo was 2560x1600 but I can't recall the file size. I used ES File Explorer apk to copy the new logo image to the temp folder in the zip file and deleted the original logo.png.
I downloaded the latest stock firmare on Sam mobile for my p900 and used odin, everything went perfect with odin but it rebooted in download mode again, no access to recovery, I tried every methods I know to boot in recovery but it didn't work.
So I found a complete Arabic 4.4.2 stock firmware and used odin and boom everything is back an running now, got 5.0.2 OTA update up and running
Click to expand...
Click to collapse
Any chance you can share this firmware? I'm in the same boat but I can't find a stock firmware that gets me running again. I've downloaded and flashed a couple but I can still only get to download mode.

Nikoli4 said:
Any chance you can share this firmware? I'm in the same boat but I can't find a stock firmware that gets me running again. I've downloaded and flashed a couple but I can still only get to download mode.
Click to expand...
Click to collapse
Sorry to hear that it happened to you also. I don't have this tablet anymore but if I remember correctly, this is the firmware I used,
https://www.androidfilehost.com/?fid=24269982087019604
Hope you will be good and running in no time

Awesome, thanks! Downloading now. I'd like to find a XAR version of this too, but hopefully this gets me working again.

coco1476 said:
Sorry to hear that it happened to you also. I don't have this tablet anymore but if I remember correctly, this is the firmware I used,
https://www.androidfilehost.com/?fid=24269982087019604
Hope you will be good and running in no time
Click to expand...
Click to collapse
That did the trick, I'm back up and running. Thanks again, I appreciate it.

Nikoli4 said:
That did the trick, I'm back up and running. Thanks again, I appreciate it.
Click to expand...
Click to collapse
Glad I can help and if wait a bit it will give you 2 or 3 system update that will bring you back to the latest firmware from Samsung, I think it's 5.0.1
Edit: it's 5.0.2

I created a bunch of splash screens and figured I'd share. I tested all of these on my p900 and they all worked for me. Check them out here. I also added the recovery software and Odin that I used to unbrick mine after a bad flash in case anyone else needs it. Thanks to coco1476 for the original link.

Question Implications of having both A/B slots and recovery partitions

I'm learning about A/B slots, and i have always seen it said that the recovery partitions were removed. Ex: "But the A/B approach gets rid of the separate recovery partition and integrates it into the boot partition."
OrangeFox gave me a warning that the phone has A/B slots but also recovery partitions.
I checked and can confirm:
ginna:/ # ls -la /dev/block/by-name/recovery*
lrwxrwxrwx 1 root root 21 1970-07-23 01:57 /dev/block/by-name/recovery_a -> /dev/block/mmcblk0p45
lrwxrwxrwx 1 root root 21 1970-07-23 01:57 /dev/block/by-name/recovery_b -> /dev/block/mmcblk0p46
1) How common is this?
2) In this case i guess it means the XT2052 cant lose it's recovery when flashing a boot image and boot doesn't need to be patched with a recovery beforehand, correct?
3) Anything else should i be aware of when reading discussions about devices without separate recovery partitions? Like some common steps that should NOT be done in my situation?