OESF Portal | OESF Forum | OESF Wiki | LinuxPDA | #planetgemini chat on matrix.org | #gemini-pda chat on Freenode | #zaurus and #alarmz chat on Freenode | ELSI (coming soon) | Ibiblio

IPB

Welcome Guest ( Log In | Register )

6 Pages V  « < 4 5 6  
Reply to this topicStart new topic
> Rooting the Cosmo Communicator
TheProfessorNQ
post Dec 15 2019, 10:02 AM
Post #76





Group: Members
Posts: 15
Joined: 10-December 19
Member No.: 861,027



Not to worry! It has been a great instructional experience for us all! A real solid crash-course to re-learning android stuff for me. It'd been six years or so since I've had a device that wasn't super locked down (samsung flagships), and thus, fell worlds behind.
Go to the top of the page
 
+Quote Post
TauPan
post Dec 15 2019, 12:51 PM
Post #77





Group: Members
Posts: 29
Joined: 9-October 19
From: Germany
Member No.: 856,957



QUOTE(ZimbiX @ Dec 14 2019, 05:08 PM) *
In the interest of finding out which partitions are safe to share (e.g., not leaking device-specific keys) in order to create a full firmware for factory restore, here are the sizes and checksums of the partition images after my original extraction from WwR with the option that gave the most partitions (I can't remember what that was called, sorry!). It'd be great if someone with their own backup of these from the pre-OTA firmware could compare to see what's the same/different. We can then package up all the partitions that are the same between each device. TauPan? Hopefully posting checksums of the private partitions is not too much of an information leak tongue.gif



QUOTE(Ninji @ Dec 14 2019, 10:37 PM) *
I can confirm I have matches on the following partitions: boot, cam_vpu{1,2,3}, dtbo, lk, lk2, logo, md1dsp, md1rom, scp1/2, spmfw, sspm, trustzone1/2

Different: boot_para, frp, metadata, nvcfg, nvdata, nvram, para, persist, proinfo, protect1/2

My preloader dump (via SP FlashTool) is clipped slightly at the end for some reason, and my system and vendor dumps are far bigger (also done via SP FlashTool). I would expect these to have only one version though because the OTA updater expects them to be the same for everybody.


Ok, I finally got around to comparing those lengths and checksums and
I was a bit surprised by the results:

That's a bit strange. I have lots of mismatches. I've truncated my
images I dumped with SP flash tool and my scatter file with this
program:
https://www.unix.com/unix-for-beginners-que...nulls-file.html
(The c-programm in comment #4, not the clearly wrong tr command).

(I have backups of the untruncated versions in my Nextcloud, but I'm
very sure the program is correct and it probably hardly matters.)

Mismatches in boot_para, cache, nvdcfg, nvdata, boot_para, para,
persist are not surprising, as those are well known to contain device
specific information.

The same is probably true for expdb, frp, metadata, proinfo, protect.

sefcfg also appears to contain device specific information. (I've found a 32 byte string in the hexdump, which changes from locked to unlocked state, along with one byte which changes from 01 to 03)

Cache and userdata are highly volatile, so we don't even need to look
at them.

However my (unrooted) boot image is longer (and also has a different checksum).

I have different system and vendor images! Even the recovery is
different! Also the trustzone (tee) images differ.

The only matches I have are: cam_vpu1, 2, 3, dtbo, lk2, lk, logo,
md1dsp, md1rom, preloader, spmfw, sspm (1 and 2).

I have the following sizes and md5sums on files which would be
certainly be included in a flashable firmware:

a616f4eec2c67991587d7cedcaf7cf99 9536401 boot.img
5d684efa830778c340887ef9211db608 14789521 recovery.img
593cb99172165ed468f89ad7779d06a2 3221225472 system.img
ac95bc9994673c2e99b5d170d68474ac 897581056 vendor.img

The following are from my build.prop:

ro.product.first_api_level=28
ro.vendor.build.date=Tue Oct 29 14:01:27 CST 2019
ro.vendor.build.date.utc=1572328887
ro.vendor.build.fingerprint=Planet/Cosmo_Communicator/Cosmo_Communicator:9/PPR1.180610.011/1563439284:user/release-keys
ro.vendor.build.security_patch=2019-07-05
ro.vendor.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
ro.vendor.product.cpu.abilist32=armeabi-v7a,armeabi
ro.vendor.product.cpu.abilist64=arm64-v8a
# begin build properties
# autogenerated by vendor_buildinfo.sh
ro.product.board=k71v1_64_bsp
ro.board.platform=mt6771
ro.product.vendor.manufacturer=Planet
ro.product.vendor.model=Cosmo_Communicator
ro.product.vendor.brand=Planet
ro.product.vendor.name=Cosmo_Communicator
ro.product.vendor.device=Cosmo_Communicator
Go to the top of the page
 
+Quote Post
irukandji
post Dec 26 2019, 10:00 PM
Post #78





Group: Members
Posts: 8
Joined: 16-September 19
Member No.: 855,730



TauPan, don't checksum them, diff them. With checksumming even single byte of change will show as different... I'll join to the rooting party after NY, too busy with family ATM...
Go to the top of the page
 
+Quote Post
Oran
post Jan 19 2020, 09:44 PM
Post #79





Group: Members
Posts: 1
Joined: 11-July 18
Member No.: 825,923



Hi guys.
I've rooted my Cosmo successfully using the boot-magisk.img you provided (unlocked the bootloader and flushed it with fastboot).
Thanks!!

Now there's a firmware update ready and it fails to install.
I understand that if i'll flush the original boot.img that's provided in post #19, i'll be able to run the firmware upgrade?
but then i won't be able to root again, right? and even after Planet eventually release the pre-rooted image, i won't be able upgrade without loosing my data (and since i'll be un-rooted, i can't use Titanium for backup).

any advise?
Go to the top of the page
 
+Quote Post
PNuT
post Yesterday, 02:35 AM
Post #80





Group: Members
Posts: 13
Joined: 6-December 19
Member No.: 860,784



QUOTE(Oran @ Jan 20 2020, 05:44 AM) *
Hi guys.
I've rooted my Cosmo successfully using the boot-magisk.img you provided (unlocked the bootloader and flushed it with fastboot).
Thanks!!

Now there's a firmware update ready and it fails to install.
I understand that if i'll flush the original boot.img that's provided in post #19, i'll be able to run the firmware upgrade?
but then i won't be able to root again, right? and even after Planet eventually release the pre-rooted image, i won't be able upgrade without loosing my data (and since i'll be un-rooted, i can't use Titanium for backup).

any advise?


Reflash the first ota boot.img contained in this thread, it will need to be the correct one or it will fail.

post # 64 has the correct images.

Go to the top of the page
 
+Quote Post
mibry
post Yesterday, 04:49 AM
Post #81





Group: Members
Posts: 21
Joined: 18-May 18
Member No.: 822,788



Has anyone posted updated boot image from yesterdays update yet?
Go to the top of the page
 
+Quote Post
PNuT
post Yesterday, 08:09 AM
Post #82





Group: Members
Posts: 13
Joined: 6-December 19
Member No.: 860,784



QUOTE(mibry @ Jan 20 2020, 12:49 PM) *
Has anyone posted updated boot image from yesterdays update yet?


I have not seen any yet!
Go to the top of the page
 
+Quote Post
Ninji
post Today, 06:13 PM
Post #83





Group: Members
Posts: 25
Joined: 28-November 19
Member No.: 860,591



Here's images for the V19 update:

Boot partition, unmodified: https://drive.google.com/file/d/1PHL6IlE3lq...iew?usp=sharing
Boot partition, rooted with Magisk: https://drive.google.com/file/d/1UqXZHeuPjr...iew?usp=sharing
Full images (~1.2GB): https://drive.google.com/open?id=1A9K04eyaX...sVVt3e6pVZGRA0Y
Go to the top of the page
 
+Quote Post

6 Pages V  « < 4 5 6
Reply to this topicStart new topic
2 User(s) are reading this topic (2 Guests and 0 Anonymous Users)
0 Members:

 



RSS Lo-Fi Version Time is now: 21st January 2020 - 08:34 PM