[Recovery][p6800/p6810/i815] (5Apr2016 TWRP 3.0.2-0) Custom Recoveries

UpInTheAir · Nov 16, 2013

daniel_hk said:
The firmware bootloader (like the bios of an PC.) is not flashable. It can only be reload via JTAG. Download mode is in that bootloader. That's why it always shows p6810.

Recovery partition is in mmcblk0p6, Same for all 7.7 models. Odin doesn't have assert to recognize model.

Did you flash the p6800 recovery? If you use an p6800 PIT, you should use the p6800 recovery to match the partitions.Preload for p6800 is 11 and 10 for p6810. You can always backup the whole partiton with dd cmd. dd if=/dev/block/mmcblk0p11 of=<a file>. but it would be the whole partition size.

Don't know why my 2.6.0.0 can't boot on your tab. if your PIT is from stock roms, it should work. The only thing I think of may be recovery partition is resized.

There are data in /efs which is unique to p6800 and p6810 but only encrypted partition affected.

Try unpacking the initramfs of the recovery.img to study the mount points. The img is similar to a zImage or boot.img. It is probably the fstab not match.

Good luck!

Yes, you would think it would work. Partitions are identical to that of a P6800. The stock 3e recovery works. Flashing the P6810 recoveries were just an experiment to see what partitions were recognised, but as suspected, not useable. The official TWRP P6800 2.6.1.0 Recovery flashed ok and successfully backup system, data etc, but no option for the preload. I am sure your 2.6.0.0 does have that option (when I used for "P6810" parttioned device), It will flash but no boot. I tried studying the pit with the pit magic pc program, but my knowledge is limited there.

I thought a successful Odin flash would indicate the recovery parttion size size is ok (with other recoveries being able to load)? I might unpack the recovery just to see as you suggest, but I was really hoping for "flash and play" simplicity for users using the guide.

Users going to the trouble of using the guide probably don't want to backup/restore manually (PITA), custom recovery is the way to (if possible).

A little bewildering since my tab is effectively now a P6800 with same partitions.

Appreciate your time taken and input mate.

Cheers,

UpInTheAir

Sent from my GT-I9500 using XDA Premium 4 mobile app

daniel_hk · Nov 16, 2013

UpInTheAir said:
Yes, you would think it would work. Partitions are identical to that of a P6800. The stock 3e recovery works. Flashing the P6810 recoveries were just an experiment to see what partitions were recognised, but as suspected, not useable. The official TWRP P6800 2.6.1.0 Recovery flashed ok and successfully backup system, data etc, but no option for the preload. I am sure your 2.6.0.0 does have that option (when I used for "P6810" parttioned device), It will flash but no boot. I tried studying the pit with the pit magic pc program, but my knowledge is limited there.

I thought a successful Odin flash would indicate the recovery parttion size size is ok (with other recoveries being able to load)? I might unpack the recovery just to see as you suggest, but I was really hoping for "flash and play" simplicity for users using the guide.

Users going to the trouble of using the guide probably don't want to backup/restore manually (PITA), custom recovery is the way to (if possible).

A little bewildering since my tab is effectively now a P6800 with same partitions.

Appreciate your time taken and input mate.

Cheers,

UpInTheAir

Sent from my GT-I9500 using XDA Premium 4 mobile app

TWRP can assign extra partitions to backup but there is something missing in the source.
For my TWRP2.6.0.0, I only add the EFS partition to the backup list. Preload(HIDDEN) was not included.
To increase 4xxM to internal SD. I have already merged that partition to DATAFS....

When my tab was bricked, I dump the PIT file to study. This is the format of PIT I found out.
View attachment pitformat.txt

This is the stock PIT for p6800:
View attachment p6800_TGY_PIT.zip

Hope these might help

Daniel

UpInTheAir · Nov 16, 2013

daniel_hk said:
TWRP can assign extra partitions to backup but there is something missing in the source.
For my TWRP2.6.0.0, I only add the EFS partition to the backup list. Preload(HIDDEN) was not included.
To increase 4xxM to internal SD. I have already merged that partition to DATAFS....

When my tab was bricked, I dump the PIT file to study. This is the format of PIT I found out.
View attachment 2396335

This is the stock PIT for p6800:
View attachment 2396324

Hope these might help
Daniel

Thanks for that mate.

I'll take another look later on. Family time today and off to the beach

Sent from my GT-I9500 using XDA Premium 4 mobile app

daniel_hk · Nov 17, 2013

UpInTheAir said:
Thanks for that mate.

I'll take another look later on. Family time today and off to the beach

Sent from my GT-I9500 using XDA Premium 4 mobile app

I was thinking that you would be up in the air but not the beach... lol
Enjoy!

Sent from my GT-P6800 using xda app-developers app

MOBILGEEK · Nov 19, 2013

Hello,
to all of you.
Actually, I am totally new to all this android field, I have a question, actually, I have GALAXY TAB 7.7 running the 3.2 original version(BASEBAND VERSION P6800DDKL4), I want to load custom recovery into that, I want to know, Will this recovery work in that?
Thank You.
Regards,
MOBILGEEK

UpInTheAir · Nov 22, 2013

Hi daniel,

Unfortunately your pit was no better and made no difference.

Hoping to test out the new recovery for you. Seems Goo server is having it's issues again........

Edit, Goo is working again.

No luck, P6800 2.6.3.0 fails to flash on my re-parttioned P6810. Just hangs at recovery.img

Code:

<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> recovery.img

There must be some slight difference to that of the official 2.6.1.0 which has no problems with the re-partition

Will test the P6810 2.6.3.0 recovery tomorrow when I re-partition back to P6810 again.

Thanks for all your improvements here mate. :good:

Cheers

daniel_hk · Nov 22, 2013

UpInTheAir said:
Hi daniel,

Unfortunately your pit was no better and made no difference.

Hoping to test out the new recovery for you. Seems Goo server is having it's issues again........

Edit, Goo is working again.

No luck, P6800 2.6.3.0 fails to flash on my re-parttioned P6810. Just hangs at recovery.img

Code:

<ID:0/007> Added!! <ID:0/007> Odin v.3 engine (ID:7).. <ID:0/007> File analysis.. <ID:0/007> SetupConnection.. <ID:0/007> Initialzation.. <ID:0/007> Get PIT for mapping.. <ID:0/007> Firmware update start.. <ID:0/007> recovery.img

There must be some slight difference to that of the official 2.6.1.0 which has no problems with the re-partition

Will test the P6810 2.6.3.0 recovery tomorrow when I re-partition back to P6810 again.

Thanks for all your improvements here mate. :good:

Cheers

I think I might know why your re-partition p6810 didn't work.
To unify the fstab among different models, we use the by_name links in /dev/block/plactform
official twrp use cm9 kernel which use the old links. They are acturally paths in the file system.

New kernels has the new links
They are in /dev/block/platform/dw_mmc/by_name for partitions
For p6800:
FACTORYFS would be mmcblk0p09
DATAFS would be mmcblk0p10

These links seems defined in the firmware bootloader.

Even though you change the PIT, those link might not change. That is FACTORYFS still point to mmcblk0p8 as p6810
That means it can't access the proper /data partition and hang.

Browse the directory: /dev/block/platform
you might find different directory names and entries

If you upack the recovery.img you may change the mount points to your devices mount points

Good luck!

northender · Nov 22, 2013

No luck here updating with either file, mobile odin states - Partition could not be found in file
Using bodivas' JB rom.

Sent from my GT-P6810 using xda premium

Nuclear Blast · Nov 22, 2013

Could not flash new CWM 6.0.4.5 (Unofficial) 22/11/2013 via Mobile Odin

Partition could not be found in file

daniel_hk · Nov 22, 2013

northender said:
No luck here updating with either file, mobile odin states - Partition could not be found in file
Using bodivas' JB rom.

Sent from my GT-P6810 using xda premium

Nuclear Blast said:
Could not flash new CWM 6.0.4.5 (Unofficial) 22/11/2013 via Mobile Odin

Partition could not be found in file

I use dd to flash so I don't have problem.
I use the new tar to pack. May be there is compression issue.
Let me repack again.

Edit: If you have 7z, drag the file out. Mobile Odin recognize .img files

File is re-tared and updated to the upload site now. Please download again... Sorry for the inconvinence..

northender · Nov 22, 2013

Using the recovery.img file worked ...thanks.
...and may I also thank you for all the work you've done to keep our Tab7.7 alive.

Sent from my GT-P6800 using xda premium

UpInTheAir · Nov 23, 2013

daniel_hk said:
I think I might know why your re-partition p6810 didn't work.
To unify the fstab among different models, we use the by_name links in /dev/block/plactform
official twrp use cm9 kernel which use the old links. They are acturally paths in the file system.

New kernels has the new links
They are in /dev/block/platform/dw_mmc/by_name for partitions
For p6800:
FACTORYFS would be mmcblk0p09
DATAFS would be mmcblk0p10

These links seems defined in the firmware bootloader.

Even though you change the PIT, those link might not change. That is FACTORYFS still point to mmcblk0p8 as p6810
That means it can't access the proper /data partition and hang.

Browse the directory: /dev/block/platform
you might find different directory names and entries

If you upack the recovery.img you may change the mount points to your devices mount points

Good luck!

Hi daniel, once again, thanks for you reply and help.

All mounts are identical, and I had posted a terminal screenshot previously in my guide.

I don't usually use Mobile Odin, but just installed it. SUCCESS, I have your P6800 2.6.3.0 on my P6810 re-partition and it shows mounts correctly (and sizes) in the backup menu. Will backup all (device) partitions and FULL wipe to test pre-load is ok. I will check in File manager if they are wiped first to be sure, and before retoring.

Possibly just a bad tar..........

Anyway :
Backup success, but failed to restore system . Trying again, nope failed

Also, pre-load is forgotten in Advanced Wipe menu.......

Please find attached the recovery.log. Maybe itt was just a bad backup, will test again another time, need to reflash my firmware to get the tab up and running again.

Damm attachments aren't working, will upload to dropbox.... https://dl.dropboxusercontent.com/u/19780267/recovery.log

.

ColBill · Nov 23, 2013

daniel_hk said:
I use dd to flash so I don't have problem.
I use the new tar to pack. May be there is compression issue.
Let me repack again.

Edit: If you have 7z, drag the file out. Mobile Odin recognize .img files

File is re-tared and updated to the upload site now. Please download again... Sorry for the inconvinence..

I used Mobile Odin and 6.0.4.5 seems to have installed with out problem. i am currently running a backup and will report back if it fails or i can not get it to restore.:fingers-crossed: I am using [ROM][4.2.2r1]p6800/p6810/i815](5OCT2013)PAC-Man ROM 4.2 Milestone1 release and attempting to back up to a micro SD 64gb card formatted exfat. :cyclops:

Thanks for everything. I would be installing CM11 again but my tab does not see a sim card detected and no 3g, Some are reporting their sim cards are detected but others have the same with sim card detection problem I have experienced.

The movement on ROM updates you guys have made on this tab is fantastic and am looking forward to using 4.4.

mellovicious · Nov 23, 2013

why the downloaded file is only 10kb

im confused

daniel_hk · Nov 23, 2013

UpInTheAir said:
Hi daniel, once again, thanks for you reply and help.

All mounts are identical, and I had posted a terminal screenshot previously in my guide.

I don't usually use Mobile Odin, but just installed it. SUCCESS, I have your P6800 2.6.3.0 on my P6810 re-partition and it shows mounts correctly (and sizes) in the backup menu. Will backup all (device) partitions and FULL wipe to test pre-load is ok. I will check in File manager if they are wiped first to be sure, and before retoring.

Possibly just a bad tar..........

Anyway :
Backup success, but failed to restore system . Trying again, nope failed

Also, pre-load is forgotten in Advanced Wipe menu.......

Please find attached the recovery.log. Maybe itt was just a bad backup, will test again another time, need to reflash my firmware to get the tab up and running again.

Damm attachments aren't working, will upload to dropbox.... https://dl.dropboxusercontent.com/u/19780267/recovery.log

.

Attachment only accept a few formats. Next time you may zip it first.

I'll take a look. The twrp source only handle the 4 standared partitions. Other partition need to handle seperately. I already report that something is missing to them months ago. Anyway, test If you can do it in the original p6810 PIT. I'll take a look at your log.

daniel_hk · Nov 23, 2013

mellovicious said:
why the downloaded file is only 10kb

im confused

There are 3 links. Next time check them all.

You must have click the official links. Their links are 10k and that's why I built this.
Try the first two links which are mine.

Good luck!

Mike02z · Nov 23, 2013

Daniel, I have an issue with the latest TWRP. I assume it may be me but here is the scenario:

I have an i815. I was running 4.4 Homemade but was unable to get mobile data working. I originally flashed 4.4 with TWRP 2.3.1.1 as the links for 2.6.3.0 were down at the time. After flashing 4.4 I was able to get version 2.6.3.0 so I flashed it. After flashing 2.6.3.0 I was no longer able to flash any ROM that was not 4.4 other than the stock ROM. I would get a signature error during flash. I flashed back to stock with 2.6.3.0 and it worked. I then flashed 2.3.1.1 and was then able to flash 4.2.2 back and my mobile data came back.

Two questions:
1.) Any idea why I can't get service on 4.4? I tried both Homeade and CM11?
2.) Is there some incompatibility with TWRP 2.6.3.0 that won't let you flash a 4.1 or 4.2 ROM?

Thanks for keeping our tablet alive and current!
Regards,
-Mike

daniel_hk · Nov 23, 2013

Mike02z said:
Daniel, I have an issue with the latest TWRP. I assume it may be me but here is the scenario:

I have an i815. I was running 4.4 Homemade but was unable to get mobile data working. I originally flashed 4.4 with TWRP 2.3.1.1 as the links for 2.6.3.0 were down at the time. After flashing 4.4 I was able to get version 2.6.3.0 so I flashed it. After flashing 2.6.3.0 I was no longer able to flash any ROM that was not 4.4 other than the stock ROM. I would get a signature error during flash. I flashed back to stock with 2.6.3.0 and it worked. I then flashed 2.3.1.1 and was then able to flash 4.2.2 back and my mobile data came back.

Two questions:
1.) Any idea why I can't get service on 4.4? I tried both Homeade and CM11?
2.) Is there some incompatibility with TWRP 2.6.3.0 that won't let you flash a 4.1 or 4.2 ROM?

Thanks for keeping our tablet alive and current!
Regards,
-Mike

It is always glad to receive the report from i815 owner's. I don't have an i815 and I relies on these reports.Thanks Mike!

1) for cm11 and OmniROM, the ril lib can not recognize the SIM card even if you can made calls. (I think calls are done inside the blobs). You can't change APN if no sim is there. That is most likely the reason. I just updated the kernel modem driver and use the lastest blob. Problem persist. Looking at the source for that bug now. Another needle in the Haystack as usual....:cyclops:

2) Seems it is the signature verification. Stock rom's are always signed and custom are always not. Stock recovery can only flash signed package. In TWRP, there is an option "zip file signature verification" in Settings. Don't know if it is check for some reason. If you have time, please check if it's check when flashing fail.

Good lcuk to all of us...
Daniel

Mike02z · Nov 23, 2013

daniel_hk said:
It is always glad to receive the report from i815 owner's. I don't have an i815 and I relies on these reports.Thanks Mike!

1) for cm11 and OmniROM, the ril lib can not recognize the SIM card even if you can made calls. (I think calls are done inside the blobs). You can't change APN if no sim is there. That is most likely the reason. I just updated the kernel modem driver and use the lastest blob. Problem persist. Looking at the source for that bug now. Another needle in the Haystack as usual....:cyclops:

2) Seems it is the signature verification. Stock rom's are always signed and custom are always not. Stock recovery can only flash signed package. In TWRP, there is an option "zip file signature verification" in Settings. Don't know if it is check for some reason. If you have time, please check if it's check when flashing fail.

Good lcuk to all of us...
Daniel

Thanks Daniel. I understand for number 1. For number 2, I did a test and re-flashed 2.6.3.0. I verified the signature verification was not on but suspect I just reported the error wrong the first time. When I try to flash 4.2.2 I get the following error:

"assert failed: getprop ("ro.product.device") = = "i815" || get prop("ro.build.product
getprop("ro.product.device") == "SCH-I815" || getprop("ro.build.product") =
E:Error executing updater binary in zip '/external_sd/i815_PAC_JB_4.2.2-v23.0.0_20
Error flashing zip '/external_sd/i815_PAC_JB4.2.2-v23.0.0_20130717-031646a.zip"
Updating partition details.

Keep in mind that it lets me flash either of the 4.4 ROM's fine. Will not let me flash a 4.1 or 4.2 ROM

daniel_hk · Nov 24, 2013

Mike02z said:
Thanks Daniel. I understand for number 1. For number 2, I did a test and re-flashed 2.6.3.0. I verified the signature verification was not on but suspect I just reported the error wrong the first time. When I try to flash 4.2.2 I get the following error:

"assert failed: getprop ("ro.product.device") = = "i815" || get prop("ro.build.product
getprop("ro.product.device") == "SCH-I815" || getprop("ro.build.product") =
E:Error executing updater binary in zip '/external_sd/i815_PAC_JB_4.2.2-v23.0.0_20
Error flashing zip '/external_sd/i815_PAC_JB4.2.2-v23.0.0_20130717-031646a.zip"
Updating partition details.

Keep in mind that it lets me flash either of the 4.4 ROM's fine. Will not let me flash a 4.1 or 4.2 ROM

I got your answer now. The twrp recovery source requires 4.4 to compile. The old update-binary is no longer supported.

In the mean time, you may following my other post to change the update-binary of you old ROMs and gapps.
http://xdaforums.com/showthread.php?t=2532300

This one is backward compatible. You can flash the updated zip in old recoveries too.

We are in the transition period. Things will get better soon...

[Recovery][p6800/p6810/i815] (5Apr2016 TWRP 3.0.2-0) Custom Recoveries

Account currently disabled

Inactive Recognized Contributor

Account currently disabled

Inactive Recognized Contributor

Senior Member

Account currently disabled

Inactive Recognized Contributor

Member

Senior Member

Inactive Recognized Contributor

Member

Account currently disabled

Senior Member

Member

Inactive Recognized Contributor

Inactive Recognized Contributor

Senior Member

Inactive Recognized Contributor

Senior Member

Inactive Recognized Contributor

Similar threads

Top Liked Posts