[Kernel][24/04] Perseus - Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve

Identical kernel to the i9300 one. Only difference is:
CMA device memory allocation is gone as we don't need the hacks used in it for larger memory, 2GB with the default setting will suffice.
You apparently have no FM radio.
The port is trivial and everything else should work flawlessly.
Please refer to the I9300 thread for changelogs, bug-reports and other issues. Kernel itself will be posted here.

waiting to try.. thx

We are actually contemplating the fm radio because one user actually had it on his firmware working so we wanted to compile a kernel with fm radio .
Can we actually try?
Sent from my GT-I9305 using xda app-developers app
---------- Post added at 04:04 PM ---------- Previous post was at 04:02 PM ----------
I can upload if you tell me where I can get it
Sent from my GT-I9305 using xda app-developers app

AndreiLux said:
Identical kernel to the i9300 one. Only difference is:
CMA device memory allocation is gone as we don't need the hacks used in it for larger memory, 2GB with the default setting will suffice.
LCDFreq might not work [WIP]
You apparently have no FM radio.
The port is trivial and everything else should work flawlessly.
Please refer to the I9300 thread for changelogs, bug-reports and other issues. Kernel itself will be posted here.
__________
The kernel is compiled and ready, now, if somebody would please upload the stock kernel only somewhere, so I don't have to wait 2 hours on downloading the SamMobiles whole firmware zip from Hotfile (I'm at the daily traffic limit, eh.), it would be appreciated. I just need to check the ramfs to see if there's any dramatic changes and eventually adapt that. Apparently nobody on the internet or this forum thought of uploading this yet.
Click to expand...
Click to collapse
I only have ZHALI8 this firmware

This is probably the best one to use its the latest http://d-h.st/AMs Boot.img from the base firmware XXLI9 latest,
Thanks to prodigiez
I cannot wait to get our first custom kernel which we can over clock and turn our Gems into Weapons

I tried to compile with FM radio but it fails due to platform dependencies, there is something weird going on with the 9305 in that regard, I'll check it out later.
Anyway, here we go: Please test and report back.

Thanks dude I will try this now... It would be great if someone could figure this FM thing out, As even samsung said It is up to the carrier if they wish to include FM radio which to me means there is capability

Thanks dude I will try this now... It would be great if someone could figure this FM thing out, As even samsung said It is up to the carrier if they wish to include FM radio which to me means there is capability
ALL I CAN SAY IS IT WORKS PERFECTLY I AM NOW OVERCLOCKED TO 1704MHZ Just like I was on my favourite Nandroid I9300 ICS
Check out my Quadrant screenshot
LIKE A BOSS!

Here is something 4 u .. thank you
Confirmation number: 4B258375FK2191426.

If there are no reported issues I'll put it up in the first post together with a CWM soon. Also, somebody needs to check if the partition is still mmcblk0p5 for the kernel. On the Note 2 they changed the partition to mmcblk0p8 and I didn't know about it and the CWM didn't work.

AndreiLux said:
If there are no reported issues I'll put it up in the first post together with a CWM soon. Also, somebody needs to check if the partition is still mmcblk0p5 for the kernel. On the Note 2 they changed the partition to mmcblk0p8 and I didn't know about it and the CWM didn't work.
Click to expand...
Click to collapse
how do I check? Could we also have something like stweaks so we can tweak our stuff? without the need to download other random apps
---------- Post added at 04:38 AM ---------- Previous post was at 04:32 AM ----------
So far Everyhing works perfect, AND SUPER SUPER FAST WOOOOO this is a WEAPON now...
Only thing different i noticed is a TINY (2mm) exclamation mark in the top left hand corner, when you boot up stays on for like 5 secs then goes away... It only used to show when I was going into recovery mode before

AndreiLux said:
If there are no reported issues I'll put it up in the first post together with a CWM soon. Also, somebody needs to check if the partition is still mmcblk0p5 for the kernel. On the Note 2 they changed the partition to mmcblk0p8 and I didn't know about it and the CWM didn't work.
Click to expand...
Click to collapse
hope this helps you
lrwxrwxrwx root root 2012-10-08 21:43 BOOT -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2012-10-08 21:43 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2012-10-08 21:43 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2012-10-08 21:43 CACHE -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2012-10-08 21:43 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2012-10-08 21:43 HIDDEN -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2012-10-08 21:43 OTA -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2012-10-08 21:43 PARAM -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2012-10-08 21:43 RADIO -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2012-10-08 21:43 RECOVERY -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2012-10-08 21:43 SYSTEM -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2012-10-08 21:43 TOMBSTONES -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2012-10-08 21:43 USERDATA -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2012-10-08 21:43 m9kefs1 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2012-10-08 21:43 m9kefs2 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2012-10-08 21:43 m9kefs3 -> /dev/block/mmcblk0p6

btemtd said:
Only thing different i noticed is a TINY (2mm) exclamation mark in the top left hand corner, when you boot up stays on for like 5 secs then goes away... It only used to show when I was going into recovery mode before
Click to expand...
Click to collapse
Probably because you're running a kernel not signed by Samsung. This thread talks of the same happening on the I9300. Please don't flash any bootloaders from that thread...

Thanks for the kernel, it's a great start - and it works well on my device as well. Much appreciated!:good::good:

Any reason this wouldn't work on a i9305T? ie the Telstra version?

Should work fine on I9305 & i9305t
Sent from my GT-I9305 using xda app-developers app

should i backup my current kernel? what's the best way to do this?

btemtd said:
Should work fine on I9305 & i9305t
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
NO. It wont work on the T model, the hardware is different, it didn't have a different model number for nothing. If anything, I'll do a separate kernel, but don't try it on anything else than the I9305.

AndreiLux said:
NO. It wont work on the T model, the hardware is different, it didn't have a different model number for nothing. If anything, I'll do a separate kernel, but don't try it on anything else than the I9305.
Click to expand...
Click to collapse
You think telstra had their own version developed? I dont think so. I installed the optus rom on my telstra phone and it worked flawless. Unless there is something very minor....
Edit: Now installed on my 9305T. Never used a custom kernal without having a whole new rom also. So not sure what its actually meant to be doing....
Sent from my GT-I9305 using xda premium

Exactly what I thought when I had the i9300t everything worked exactly like the i9300 I was able to intexchange modem roms kernel etc.... now we have users with i9305t which flashed i9305 Rom and kernel with no problem at all. I dont see why it wouldn't work.
And the hardware is actually the same I am pretty sure of it.
Sent from my GT-I9305 using xda app-developers app
---------- Post added at 09:51 AM ---------- Previous post was at 09:44 AM ----------
singlecell83 said:
You think telstra had their own version developed? I dont think so. I installed the optus rom on my telstra phone and it worked flawless. Unless there is something very minor....
Edit: Now installed on my 9305T. Never used a custom kernal without having a whole new rom also. So not sure what its actually meant to be doing....
Sent from my GT-I9305 using xda premium
Click to expand...
Click to collapse
Now you can modify and enhance your cpu and gpu and other tweaks best of to know what u are doin before playing.
SO THERE YOU HAVE IT WORKING ON I9305T AND I9305 JUST LIKE I THOUGHT
Sent from my GT-I9305 using xda app-developers app

Related

[Q] Go back to stock kernel?

Hi all
I have been experimenting with Bricked and faux123 kernels but I've had terrible stability with both of them.
Now I want to go back to stock kernel but I'm unable to find it, is it available somewhere?
An alternative is of course to flash an entire RUU but if that's not necessary I'd like to avoid it. Also my nand-backup is now a bit out of date so I don't want to go back to that either.
The phone is original HTC Sensation w/ SW 1.45.401.3.
Thanks
Konstigt said:
Hi all
I have been experimenting with Bricked and faux123 kernels but I've had terrible stability with both of them.
Now I want to go back to stock kernel but I'm unable to find it, is it available somewhere?
An alternative is of course to flash an entire RUU but if that's not necessary I'd like to avoid it. Also my nand-backup is now a bit out of date so I don't want to go back to that either.
The phone is original HTC Sensation w/ SW 1.45.401.3.
Thanks
Click to expand...
Click to collapse
Extract rom from original RUU first. Then you can extract boot.img from rom package.
I suppose you don't have backup with original kernel?
I think the best way is to find custom ROM based on this RUU and look into adoons section. Very often stock kernel is provided by ROM author.
Insomnis said:
I suppose you don't have backup with original kernel?
I think the best way is to find custom ROM based on this RUU and look into adoons section. Very often stock kernel is provided by ROM author.
Click to expand...
Click to collapse
I have a nandroid backup. I looked around in it but was unable to find the kernel. The most interesting file was boot.img (16MB) but I could not find how to open that image-file.
I looked at Bricked/faux123 threads but could not find the stock kernel there.
Aha, is boot.img the image that I should flash?
Then I will try do do that with fastboot..
Yep boot.img has kernel & ramdisk
Fuses said:
Yep boot.img has kernel & ramdisk
Click to expand...
Click to collapse
It was the file size that tricked me... 16MB compared to ~ 3-4MB for just zImage. But I guess it's the ramdisk that adds on size.
nandroid backup has done so called raw backup from boot partition. If you extract that 16 MB partition dump, you propably get ~3.5MB zimage and ~1 MB ramdisk.
Fuses said:
nandroid backup has done so called raw backup from boot partition. If you extract that 16 MB partition dump, you propably get ~3.5MB zimage and ~1 MB ramdisk.
Click to expand...
Click to collapse
Aha... thanks for setting me straight.
I did this operation today. Did the restore via fastboot (./fastboot flash boot.img) but after that I had one problem, no WiFi.
I remembered that I'd seen a bcm4329.ko in the custom kernel zip's so I also replaced that from a nandroid-backup (first went to recovery, then adb shell).
Now also WiFi worked.
/system/lib/modules # ls -al
drwxr-xr-x 2 root root 4096 Mar 3 12:18 .
drwxr-xr-x 8 root root 12288 Oct 6 18:54 ..
-rwxrwxrwx 1 root root 278688 Mar 3 12:18 bcm4329.ko <-- Stock module
-rw-r--r-- 1 root root 279875 Aug 1 2008 bcm4329.custom <-- Included with faux123 kernel, now renamed by me
-rwxrwxrwx 1 root root 154871 Mar 3 12:18 kineto_gan.ko <-- Some other module which was present in the nandroid-backup which I also restored
Konstigt said:
I did this operation today. Did the restore via fastboot (./fastboot flash boot.img) but after that I had one problem, no WiFi.
I remembered that I'd seen a bcm4329.ko in the custom kernel zip's so I also replaced that from a nandroid-backup (first went to recovery, then adb shell).
Now also WiFi worked.
/system/lib/modules # ls -al
drwxr-xr-x 2 root root 4096 Mar 3 12:18 .
drwxr-xr-x 8 root root 12288 Oct 6 18:54 ..
-rwxrwxrwx 1 root root 278688 Mar 3 12:18 bcm4329.ko <-- Stock module
-rw-r--r-- 1 root root 279875 Aug 1 2008 bcm4329.custom <-- Included with faux123 kernel, now renamed by me
-rwxrwxrwx 1 root root 154871 Mar 3 12:18 kineto_gan.ko <-- Some other module which was present in the nandroid-backup which I also restored
Click to expand...
Click to collapse
Me too. please guide me . Thaks

Orange Yumo aka Huawei Ascend G740 Rooting, General Discussion Thread

Quadrant ~ 5000.
Antutu ~ 14000.
http://consumer.huawei.com/en/mobile-phones/features/g740-l00-en.htm
Rooting:
1. Install latest Framaroot 1.6.1 from here http://forum.xda-developers.com/showthread.php?t=2130276
2. Launch and choose Gandalf. It will be rooted in a second.
3. Reboot and enjoy.
Battery screenshots, 100% to 8%, GREAT screen on time, 5h 41m.
Here is the partition table, i've backuped the recovery.img using this command dd if=/dev/block/mmcblk0p14 of=/sdcard/recovery.img bs=4096 but when trying to generate cwm recovery here http://builder.clockworkmod.com/ it failed.
If anyone is interested in getting a working cm with this device, i can provide the necessary files from my device.
[email protected]:/ # parted /dev/block/mmcblk0 print
parted /dev/block/mmcblk0 print
Model: MMC SEM08G (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 17.4kB 280kB 262kB sbl1
2 280kB 542kB 262kB sbl2
3 542kB 1066kB 524kB sbl3
4 1066kB 1328kB 262kB rpm
5 1328kB 2377kB 1049kB tz
6 2377kB 4474kB 2097kB aboot
7 4474kB 6571kB 2097kB aboot2
8 6571kB 6579kB 8192B ssd
9 8389kB 12.6MB 4194kB fsg
10 12.6MB 16.8MB 4194kB modemst1
11 16.8MB 21.0MB 4194kB modemst2
12 21.0MB 54.5MB 33.6MB oeminfo
13 54.5MB 122MB 67.1MB fat16 modem
14 122MB 138MB 16.8MB recovery
15 138MB 155MB 16.8MB recovery2
16 155MB 159MB 4194kB misc
17 159MB 164MB 4194kB splash
18 164MB 172MB 8389kB ext4 persist
19 172MB 180MB 8389kB tombstones
20 180MB 181MB 655kB pad
21 185MB 197MB 12.6MB boot
22 197MB 466MB 268MB ext4 cust
23 466MB 667MB 201MB ext4 cache
24 667MB 1741MB 1074MB ext4 system
25 1741MB 2923MB 1183MB ext4 userdata
26 2923MB 7818MB 4895MB fat32 grow
Click to expand...
Click to collapse
Hello, a just installed an app from the playstore that bricked my yumo. It just show the orange logo and doesn't boot up. Anybody knows where can i download the firmware to reinstall it or should i go to for repair? Tried factory reset from recovery but still nothing. Thanks.
ione2380 said:
Hello, a just installed an app from the playstore that bricked my yumo. It just show the orange logo and doesn't boot up. Anybody knows where can i download the firmware to reinstall it or should i go to for repair? Tried factory reset from recovery but still nothing. Thanks.
Click to expand...
Click to collapse
If factory reset doesn't work, return it for repair, there isn't a custom recovery for it yet, if it was i would backup my device and give you the backup for a restore. I've checked the huawei website, there isn't a firmware to download from them.. so no luck this way. What app did you install?
Ask orange for the firmware maybe they will give it if we will have future problems...
I have tested it successfully with a Huawei Ascend G740 from Yoigo (Spain).
Thank you!
GeekRMX said:
Thank you!
I have tested it successfully with a Huawei Ascend G740 from Yoigo (Spain) following this tutorial
Great device!
Click to expand...
Click to collapse
why do you post a link with the same method described by me in the op over 2 weeks ago? please remove the link because it's advertising.
ione2380 said:
Hello, a just installed an app from the playstore that bricked my yumo. It just show the orange logo and doesn't boot up. Anybody knows where can i download the firmware to reinstall it or should i go to for repair? Tried factory reset from recovery but still nothing. Thanks.
Click to expand...
Click to collapse
Try the Nandroid backup / rrestore method. This method is used for backing up the original ROM and recover it when something wrong occures.
I assume that you do not have a backup image of your original ROM.
What you can do is ask someone to do a full Nandroid Backup of their Huawei G740/Orange Yumo and send it to you or get a custom working ROM.
I suggest flashing the custom ROM or someones else's Nandroid Backup using ADB.
search google for : simple-adb-backup-backs-up-your-android-phone-from-the-desktop-no-root-required
search google for: nandroid-backup-restore-for-android-4-2
After you solve this, if you solve it please post how you did it step by step.
full nandroid backup requires a cwm recovery which we do not have for yumo/g740, if we had i could have helped him.
also the bootloader is locked...
i think he sent it to service.
I had no other way but sent it to service. I don't know why but they gave me a new one? Maybe orange doesn't have firmware either?
For anyone who has root just stay away from an app called srs manager from google play. It will brick your yumo.?
Sent from my Note 3 SM-N9005 using Tapatalk.
ione2380 said:
I had no other way but sent it to service. I don't know why but they gave me a new one? Maybe orange doesn't have firmware either?
For anyone who has root just stay away from an app called srs manager from google play. It will brick your yumo.?
Sent from my Note 3 SM-N9005 using Tapatalk.
Click to expand...
Click to collapse
Did it came also with 4.1.2? Of course they have it because it is customized with lots of orange applications.
Yes, still 4.1.2
Send from my Note 3.
hey all,i just upload full backup from my orange yumo,the backup is compatible in TWRP recovery tool https://docs.google.com/file/d/0B4VVn6aokJwXVmFSOUlmcmlfT3c/edit
can you add please twrp recovery for our orange yumo ?
Well..there more to do..yumo has locked bootloader. This will have to be unlocked first,then we can talk about custom recovery. I'm interested in this too.
Sent from Omega pwd GT-I9505/smart phones,dumb people.
kimitza said:
Well..there more to do..yumo has locked bootloader. This will have to be unlocked first,then we can talk about custom recovery. I'm interested in this too.
Sent from Omega pwd GT-I9505/smart phones,dumb people.
Click to expand...
Click to collapse
we know that bootloader is locked, you can try this method to unlock it, http://www.huaweidevice.com/worldwide/servicePolicy.do?method=getUnlockStep .. maybe it works...
True,it can be done, but as long as we don't have an image with the original firmware,i'll take no chances. it's my gf's phone )..
I need some files
Hey all.I need some folders from main root ..Can anyone zip the following folders ""/system/app""and ""/xbin""from main sistem?i deleted some files and i dont want to send it back in service.You can use ES file explorer
emilutzzu said:
Hey all.I need some folders from main root ..Can anyone zip the following folders ""/system/app""and ""/xbin""from main sistem?i deleted some files and i dont want to send it back in service.You can use ES file explorer
Click to expand...
Click to collapse
/system/app https://mega.co.nz/#!Wddw2RqQ!Iszumj2H3mCzGnefl7mKhiAhSkZ79fJh_G3i64wwoeE
/system/xbin https://mega.co.nz/#!DE0VFYYa!ZV-2Tg4ZmFvDc9ZviMIi0kp6-alpASvY2lI3m4-uupY
there is no /xbin folder
to unlock bootloader send a mail to [email protected] with this content:
Dear sir/madam,
I tried applying for a bootloader unlock code at unlock url which I cannot post because of XDA forum restricting me, but my device (Ascend G740) was not listed. I supply the data via this mail in the hope to get a bootloader unlock code via this way instead.
Product Model: Huawei Ascend G740-L00
SN: xxxxxxxxxxxxxxxxxxx
IMEI: xxxxxxxxxxxxxxxxx
ProductID: xxxxxxxx
I hope to hear from you soon.
Yours sincerely,
Click to expand...
Click to collapse
filling your details in a couple days shall receive an answer with the unlock code and podreis follow the process explained on the website of huawei
PS: it works, I already have unlocked
i just go a new update, from L00V100R001C109B140_JB to L00V100R001C109B146_JB, still 4.1.2, don't know the changes because they are not specified.

Gear S3 Root and Kernel Source! (Android Wear Port Thread)

Hey guys! Some of you might know me from the LG G5 scene, but I have since moved on from there and am hoping to make some progress with the Gear S3
After doing some digging and paying zero attention in class today, I came across the kernel source files for the Exynos 7270 and the combination firmwares for the Gear 3 Classic and Frontier versions.
If you don't know what combination files are here (link removed) is a great explanation but the TL;DR is that this is the internal firmware Samsung uses to reset devices, so it gives you full read/write access to the device including root access. So basically this is a pre-rooted firmware, and I assume that it is bootloader unlocked as it appears to flash an engineer sboot (bootloader), so I believe this would be the first step towards porting Android Wear/TWRP!
The kernel source is what we will actually use to port over AW/TWRP. It does not seem to have been posted before, and took me a few hours of digging to find. My watch comes in tomorrow, and after I flash this firmware I will pull the boot.img and start making a device/vendor tree to attempt and make a kernel!
Here is the kernel source for the Exynos 7270: https://github.com/HonestlyAnnoying/tizen_kernel_exynos7270
Here is the kernel source for the Gear S3 (all versions) (will upload to GitHub in the morning): Samsung Opensource
Here is the SM-R770 (Classic) combination firmware [R770XXU2BQC2]: link
Here is the SM-R760 (Frontier) combination firmware [R760XXU2BQC2]: link
The road to porting Android Wear is going to take a lot of work, and any help developing (not testing for now!) would be EXTREMELY appreciated (looking at you guys @cipherswitch @biktor_gj !). If you would like to help with development or would like to contribute in any way, please PM me or hit me up on Skype (honestly.annoying)!
Here is a Google Drive folder with all files I have for this, it will be updated as new things are found
The one thing that might persuade me to try a sammy product! Thanks for your efforts @Honestly Annoying
Update: have flashed this, can confirm it has root access!! Pulling images now
Wow!!! Fingers crossed!!
@Honestly Annoying
Please, can you tell us what you see on Screen?
Maybe screenshot if posible...
I have flashed just for fun the older Z1 Combination I have... AOC1... and my SM-Z130H shows testmode Icons...
Later I can upload Screenshot... I have to remove something...
But in this Firmware I can enter all testmode Codes via Keys... like:
*#197328640#
And more... this is blocked in normal Firmware...
Cool. su work nice...
I can enter su in Shell and Super User is active... instead SDB Command:
sdb root on
Best Regards
Edit 1.
Screenshot from Combination Firmware AOC1 I have added in this Post:
https://forum.xda-developers.com/showpost.php?p=71744490&postcount=413
adfree said:
@Honestly Annoying
Please, can you tell us what you see on Screen?
Maybe screenshot if posible...
I have flashed just for fun the older Z1 Combination I have... AOC1... and my SM-Z130H shows testmode Icons...
Later I can upload Screenshot... I have to remove something...
But in this Firmware I can enter all testmode Codes via Keys... like:
*#197328640#
And more... this is blocked in normal Firmware...
Cool. su work nice...
I can enter su in Shell and Super User is active... instead SDB Command:
sdb root on
Best Regards
Edit 1.
Screenshot from Combination Firmware AOC1 I have added in this Post:
https://forum.xda-developers.com/showpost.php?p=71744490&postcount=413
Click to expand...
Click to collapse
I'm just going to start dumping information I find in this thread
this is the partition scheme
Code:
sh-3.2# ls -l /dev/disk/by-partlabel
total 0
lrwxrwxrwx 1 root root 15 Apr 6 09:52 boot -> ../../mmcblk0p8
lrwxrwxrwx 1 root root 15 Apr 6 09:52 cm -> ../../mmcblk0p7
lrwxrwxrwx 1 root root 15 Apr 6 09:52 cpnvcore -> ../../mmcblk0p3
lrwxrwxrwx 1 root root 15 Apr 6 09:52 csa -> ../../mmcblk0p2
lrwxrwxrwx 1 root root 16 Apr 6 09:52 csc -> ../../mmcblk0p11
lrwxrwxrwx 1 root root 16 Apr 6 09:52 module -> ../../mmcblk0p10
lrwxrwxrwx 1 root root 15 Apr 6 09:52 param -> ../../mmcblk0p6
lrwxrwxrwx 1 root root 15 Apr 6 09:52 ramdisk1 -> ../../mmcblk0p5
lrwxrwxrwx 1 root root 15 Apr 6 09:52 ramdisk2 -> ../../mmcblk0p4
lrwxrwxrwx 1 root root 15 Apr 6 09:52 recovery -> ../../mmcblk0p9
lrwxrwxrwx 1 root root 16 Apr 6 09:52 rootfs -> ../../mmcblk0p14
lrwxrwxrwx 1 root root 16 Apr 6 09:52 steady -> ../../mmcblk0p15
lrwxrwxrwx 1 root root 16 Apr 6 09:52 system-data -> ../../mmcblk0p12
lrwxrwxrwx 1 root root 15 Apr 6 09:52 tup -> ../../mmcblk0p1
lrwxrwxrwx 1 root root 16 Apr 6 09:52 user -> ../../mmcblk0p13
Code:
sh-3.2# ls -l /dev/disk/by-label
total 0
lrwxrwxrwx 1 root root 16 Apr 6 09:52 modules -> ../../mmcblk0p10
lrwxrwxrwx 1 root root 10 Apr 6 09:52 ramdisk -> ../../ram0
lrwxrwxrwx 1 root root 15 Apr 6 09:52 ramdisk-recovery -> ../../mmcblk0p4
lrwxrwxrwx 1 root root 16 Apr 6 09:52 rootfs -> ../../mmcblk0p14
lrwxrwxrwx 1 root root 16 Apr 6 09:52 tizen -> ../../mmcblk0p13
Honestly Annoying said:
Update: have flashed this, can confirm it has root access!! Pulling images now
Click to expand...
Click to collapse
Did it erase the serial number of the device?
10urshin said:
Did it erase the serial number of the device?
Click to expand...
Click to collapse
nope
Honestly Annoying said:
nope
Click to expand...
Click to collapse
How about knox trip?
10urshin said:
How about knox trip?
Click to expand...
Click to collapse
how can I check?
Honestly Annoying said:
how can I check?
Click to expand...
Click to collapse
Good question. I don't know. I thought it might show on download mode but it doesn't.
This is the boot.img and recovery.img. The Tizen does not seem to extract like an Android kernel, will have to look into this more...
Also, they are both 16.8MB in size, possibly the same image?
Check this path:
/home/developer
Here is device-profile.xml inside...
This allow Privileges of all 3 Levels:
Public
Partner
Platform
But for now only if this Combination Firmware is flashed... it ignores Serial Number/DUID... maybe by these 0 Byte Flag file(s) in CSC...
Best Regards
Edit 1.
... seems my fault...
All Certs are inside...
Code:
usr/share/cert-svc/certs/code-signing/tizen
So fingerprint should be similar like in Reference devices...
Code:
usr/share/wrt-engine
Will later check with open eyes... now better sleep...
adfree said:
Check this path:
/home/developer
Here is device-profile.xml inside...
This allow Privileges of all 3 Levels:
Public
Partner
Platform
But for now only if this Combination Firmware is flashed... it ignores Serial Number/DUID... maybe by these 0 Byte Flag file(s) in CSC...
Best Regards
Click to expand...
Click to collapse
here ya go
Thank you for device-profile.xml...
Should be same here...
https://forum.xda-developers.com/showpost.php?p=71737611&postcount=18
And maybe in all FTMA Combination files... all Gear... all Z-Mobiles...
But reason for working seems not this file...
Sorry, my fault...
But difference in these 2 folders...
Code:
usr/share/wrt-engine/fingerprint_list.xml
and in commercial devices... Certs missing...
Code:
usr/share/cert-svc/certs/code-signing/tizen
This is what I did long time ago in my rooted Zseries Firmware...
By "mistake"... :laugh:
I have nuked device-profile.xml... because I was tooo lazy to register my Email and Certs...
Best Regards
Currently trying to extract the boot.img... should be studying for the SAT but screw it
I did lose Samsung Pay, but to me that is not a big deal. Waiting for a USA firmware to be released to reflash
EDIT: JUST KIDDING. It's still there! I'm an idiot lol
This is great to see! Good luck guys, hope you get this all worked out. Android Wear on the Gear S3 would be the perfect combination! :good:
I have the S3 Frontier, but not all that knowledgeable with Android dev unfortunately.
the_scotsman said:
This is great to see! Good luck guys, hope you get this all worked out. Android Wear on the Gear S3 would be the perfect combination! :good:
I have the S3 Frontier, but not all that knowledgeable with Android dev unfortunately.
Click to expand...
Click to collapse
Honestly at this point any help would be greatly appreciated. Do you have any interest/time available to help out?

Looking for most complete reset possible

Hi,
my S6 (g920f) has slowly and steadily spiraled down and lost functionality over the many custom ROMs that I flashed (which I totally don't get because wiping should clear the gunk and fix broken things, at least it did for my S1). First I lost USB connectivity with the computer (apart from download mode), then I lost 4G, then I lost my boot logo and it became white noise, and now I lost wifi which is the point where I'd say this device is becoming useless.
All I want now is the most complete reset possible, including boot, partitiontables, everything that can ever be reset. Ideally to the exact software that it ran when I bought the phone. Does anyone know how to do this the best way?
I'm a bit sad, I feel like Samsung put so much effort into crap like KNOX and does nothing to make my life easier if I want open source android with no google spyervices framework, just my device being mine. :crying:
Cheers
Alternatively, could someone upload a full TWRP backup of a clean empty phone? Without EFS for privacy reasons, and I have my own EFS and MODEM backed up since a long time. Much appreciated!
pingguo said:
Hi,
my S6 (g920f) has slowly and steadily spiraled down and lost functionality over the many custom ROMs that I flashed (which I totally don't get because wiping should clear the gunk and fix broken things, at least it did for my S1). First I lost USB connectivity with the computer (apart from download mode), then I lost 4G, then I lost my boot logo and it became white noise, and now I lost wifi which is the point where I'd say this device is becoming useless.
All I want now is the most complete reset possible, including boot, partitiontables, everything that can ever be reset. Ideally to the exact software that it ran when I bought the phone. Does anyone know how to do this the best way?
I'm a bit sad, I feel like Samsung put so much effort into crap like KNOX and does nothing to make my life easier if I want open source android with no google spyervices framework, just my device being mine. :crying:
Cheers
Click to expand...
Click to collapse
I am also in the same situation
pingguo said:
Alternatively, could someone upload a full TWRP backup of a clean empty phone?
Click to expand...
Click to collapse
Code:
~$ ls -al /dev/block/platform/15570000.ufs/by-name/
total 0
drwxrwxr-x 2 system radio 460 2018-09-02 20:39 .
drwxr-xr-x 4 root root 560 2018-09-02 20:39 ..
lrwxrwxrwx 1 root root 15 2018-09-02 20:39 BOOT -> /dev/block/sda8
lrwxrwxrwx 1 root root 15 2018-09-02 20:39 BOTA0 -> /dev/block/sda1
lrwxrwxrwx 1 root root 15 2018-09-02 20:39 BOTA1 -> /dev/block/sda2
lrwxrwxrwx 1 root root 16 2018-09-02 20:39 CACHE -> /dev/block/sda19
lrwxrwxrwx 1 root root 16 2018-09-02 20:39 CARRIER -> /dev/block/sda20
lrwxrwxrwx 1 root root 16 2018-09-02 20:39 DNT -> /dev/block/sda13
lrwxrwxrwx 1 root root 15 2018-09-02 20:39 EFS -> /dev/block/sda3
lrwxrwxrwx 1 root root 16 2018-09-02 20:39 OTA -> /dev/block/sda10
lrwxrwxrwx 1 root root 15 2018-09-02 20:39 PARAM -> /dev/block/sda7
lrwxrwxrwx 1 root root 16 2018-09-02 20:39 PERSDATA -> /dev/block/sda16
lrwxrwxrwx 1 root root 16 2018-09-02 20:39 PERSISTENT -> /dev/block/sda14
lrwxrwxrwx 1 root root 16 2018-09-02 20:39 RADIO -> /dev/block/sda11
lrwxrwxrwx 1 root root 15 2018-09-02 20:39 RECOVERY -> /dev/block/sda9
lrwxrwxrwx 1 root root 16 2018-09-02 20:39 SBFS -> /dev/block/sda17
lrwxrwxrwx 1 root root 16 2018-09-02 20:39 STEADY -> /dev/block/sda15
lrwxrwxrwx 1 root root 16 2018-09-02 20:39 SYSTEM -> /dev/block/sda18
lrwxrwxrwx 1 root root 16 2018-09-02 20:39 TOMBSTONES -> /dev/block/sda12
lrwxrwxrwx 1 root root 16 2018-09-02 20:39 USERDATA -> /dev/block/sda21
lrwxrwxrwx 1 root root 15 2018-09-02 20:39 m9kefs1 -> /dev/block/sda4
lrwxrwxrwx 1 root root 15 2018-09-02 20:39 m9kefs2 -> /dev/block/sda5
lrwxrwxrwx 1 root root 15 2018-09-02 20:39 m9kefs3 -> /dev/block/sda6
~$
All of them?
Any "reset" really cleans USERDATA as the maximum.
Any firmware file flashes less than a half of these.
pingguo said:
Hi,
my S6 (g920f) has slowly and steadily spiraled down and lost functionality over the many custom ROMs that I flashed (which I totally don't get because wiping should clear the gunk and fix broken things, at least it did for my S1). First I lost USB connectivity with the computer (apart from download mode), then I lost 4G, then I lost my boot logo and it became white noise, and now I lost wifi which is the point where I'd say this device is becoming useless.
All I want now is the most complete reset possible, including boot, partitiontables, everything that can ever be reset. Ideally to the exact software that it ran when I bought the phone. Does anyone know how to do this the best way?
I'm a bit sad, I feel like Samsung put so much effort into crap like KNOX and does nothing to make my life easier if I want open source android with no google spyervices framework, just my device being mine. :crying:
Cheers
Click to expand...
Click to collapse
Hey! I have found a website that provides stock roms. I have installed one and my phone is factory new. I even get OTA updates and everything is official. the only thing about my phone is that i tripped knox lol. the website is
updato
I then found a "how to install an officialsamsung stock firmware using odin" and followed that guide
The rom I downloaded and flashed using Odin is here (just copy and paste this at the end of updato
firmware-archive-select-model?record=583A76F4915811E89F15FA163EE8F90B
the way i did it was wipe the usual stuff when you want to flash a custom rom but instead you use the stock ROM. only down point is that it puts your recovery back to stock to. So if you want twrp again just flash it and it should be good to go
if i could post links i would so if you want them then message me and i will link things to you
Staritegaming said:
I am also in the same situation
Click to expand...
Click to collapse
Good news dude, I got everything fixed. I'll post the solution below.
bbsc said:
Code:
~$ ls -al /dev/block/platform/15570000.ufs/by-name/
All of them? [...] [/QUOTE]
I got it done, but thanks a lot for offering help! Would have really needed it if my way didn't work out.
[QUOTE="Staritegaming, post: 77539800, member: 9368858"]Hey! I have found a website that provides stock roms. [...] [/QUOTE]
Also my thanks to you for this, it was part of the solution, in fact.
---
The solution to all the problems for me was:
[LIST=1]
[*]Wiped NAND and repartitioned in Odin using the G920F-2BOG8_EUR_OPEN.pit - This might be risky or stupid but anyways, that's what I did. I was mad.
[*]Installed most recent official firmware with XEU (French) country code with Odin
[*]Odin-flashed most recent TWRP recovery (3.2.3 as of that time)
[*]Opted for FrankensteinS6 SR v4.5 because I need my customization! It came with its own skin included but you can disable and delete it if you like, that's what I did. I recommend to use a TW-based ROM like this one.
[*]Flashed Magisk, reboot, flashed xposed standard/non-magisk, reboot, flashed microG, reboot. (I experienced issues chainflashing without reboots... Also I didn't get the ROM to run very reliably when xposed was loaded as magisk module, same for NanoDroid-microG)
[*][COLOR="Red"]TO FIX USB[/COLOR] - Here's the mindf**k: The only way is to dial *#0808# and to opt for AP mode, and in the list that opens you can select what you need, I just enabled everything. Don't press reboot, just go with OK. You will also have to repeat this after every reboot. Thanks for nothing Samsung.
[*]That's it. WiFi, 4G, USB working again, bootscreen is still pixel mash but that's not too essential anyways. My phone runs very reliably, alarms always trigger correctly and wake me up in time, and I'm happy to keep this device. I might even replace the battery to prolong its life.
[/LIST]
I know that the instructions are a bit on the sparse/expert-level and that I haven't provided download links so far. If you need more information PM me, I can upload any of those files with checksums and everything, and I can elaborate on the instructions. Just thought probably nobody is reading this or whoever is here already threw their phone out of the window. :silly:
Click to expand...
Click to collapse

Request: Source (and possibly Recovery) for HTC Desire 709d (cp5dwg ChinaTelecom variant)?

My goal in this post is simple: I would like to ask anyone if they have a copy of the source code for the China Telecom variant for HTC Desire 709d (cp5dwg), or if they could contact HTC effectively, directly for this source. The only source available for this device on HTCdev is for a variant in India and would never boot on my device(tested over and over and over again). If anyone could possibly offer a copy of a custom recovery I'd be also appreciated. Note that this model uses a Spreadtrum SoC instead of a Qualcomm one.
If someone is to contact HTC for this here is some possibly relevant information for accurate search:
KERNEL VERSION: 3.4.5-gec07fd6
OTHER KERNEL INFO: SMP PREEMPT
ROM VERSION: 1.80.1401.11
Thanks.
can you tell me what spreadtrum chipset it is? and can you give me a stock recovery image?
notnoelchannel said:
can you tell me what spreadtrum chipset it is? and can you give me a stock recovery image?
Click to expand...
Click to collapse
from CPU Info (got from f-droid since aida64 cant install on android 4.1) it shows "Spreadtrum SC8830."
Recovery image (boot2.img) attached in post. It's from software version 1.80.1401.9
*this device seems to use the old board files method instead of device trees, according to this india source i have.
MightyPandora8 said:
from CPU Info (got from f-droid since aida64 cant install on android 4.1) it shows "Spreadtrum SC8830."
Recovery image (boot2.img) attached in post. It's from software version 1.80.1401.9
*this device seems to use the old board files method instead of device trees, according to this india source i have.
Click to expand...
Click to collapse
hmm i looked into this and i found recovery fstab:
Code:
# mount point fstype device
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/system ext4 /dev/block/mmcblk0p48
/data ext4 /dev/block/mmcblk0p50
/cache ext4 /dev/block/mmcblk0p49
/misc emmc /dev/block/mmcblk0p25
/boot emmc /dev/block/mmcblk0p23
/recovery emmc /dev/block/mmcblk0p24
/sprd_fix_nv_w emmc /dev/block/mmcblk0p28
/sprd_fix_nv_t emmc /dev/block/mmcblk0p30
/sprd_runtime_nv_w emmc /dev/block/mmcblk0p32
/sprd_runtime_nv_t emmc /dev/block/mmcblk0p33
This might be useful in the future
Recovery fstab is the same as the Walton Primo EF4+ phone, so if it had any lineage rom i could port it (not possible though)
Anyway, i ported TWRP 3.2.0, can you try to flash it?
Download below attachments
you ported twrp for my device in 20 minutes???
you ported twrp for my device in 20 minutes???
oh my goodness
notnoelchannel said:
hmm i looked into this and i found recovery fstab:
Code:
# mount point fstype device
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/system ext4 /dev/block/mmcblk0p48
/data ext4 /dev/block/mmcblk0p50
/cache ext4 /dev/block/mmcblk0p49
/misc emmc /dev/block/mmcblk0p25
/boot emmc /dev/block/mmcblk0p23
/recovery emmc /dev/block/mmcblk0p24
/sprd_fix_nv_w emmc /dev/block/mmcblk0p28
/sprd_fix_nv_t emmc /dev/block/mmcblk0p30
/sprd_runtime_nv_w emmc /dev/block/mmcblk0p32
/sprd_runtime_nv_t emmc /dev/block/mmcblk0p33
This might be useful in the future
Recovery fstab is the same as the Walton Primo EF4+ phone, so if it had any lineage rom i could port it (not possible though)
Anyway, i ported TWRP 3.2.0, can you try to flash it?
Download below attachments
Click to expand...
Click to collapse
No. My phone bootlooped in recovery
like it's ENDLESS. it keeps trying to boot into recovery as long as there's adequate power to go into the phone's hardware
i had to pull the battery to stop it from continuing to reboot
MightyPandora8 said:
you ported twrp for my device in 20 minutes???
Click to expand...
Click to collapse
yeah but it has a chance that it will not boot:
MightyPandora8 said:
No. My phone bootlooped in recovery
like it's ENDLESS. it keeps trying to boot into recovery as long as there's adequate power to go into the phone's hardware
Click to expand...
Click to collapse
i can try to port CWM recovery from an other device, maybe it'll boot
I recommend also not flashing it to the recovery partition if you have fastboot then type:
fastboot boot <recovery image here>
notnoelchannel said:
I recommend also not flashing it to the recovery partition if you have fastboot then type:
fastboot boot <recovery image here>
Click to expand...
Click to collapse
uhh it doesnt seem like my phone likes full boot.img to be sent via fastboot boot.
only works when sending a single kernel...
also, i asked for the kernel source - is all this useful for my india code to work on my china telecom device?
MightyPandora8 said:
uhh it doesnt seem like my phone likes full boot.img to be sent via fastboot boot.
only works when sending a single kernel...
also, i asked for the kernel source - is all this useful for my india code to work on my china telecom device?
Click to expand...
Click to collapse
i don't have the kernel source for your device, you have to email to HTC and request the kernel source of your device, give them your model number, processor, and variant. it would violate GPL if they don't release the kernel source.
notnoelchannel said:
i don't have the kernel source for your device, you have to email to HTC and request the kernel source of your device, give them your model number, processor, and variant. it would violate GPL if they don't release the kernel source.
Click to expand...
Click to collapse
the big problem here is the email address. I can't find anywhere with a proper email address that you send an email to it youre sending directly to the HQ and would be taken directly to relevant departments like [email protected]. all i find is some indirect tech support forms thats not going to help at all. no htc global contact/site at all either.
i doubt that the source is gone forever - for i have a samsung, which is also a CT variant from 8-9 years ago and samsung is still able to put it up on their site. htc, as the number one in android back in those good old days, shouldn't be unable to do so like samsung did. but if it's htc's policy in obsoletion then... well.

Categories

Resources