Related
This is the latest ROM for P7500 available on sammobiles (Czech version) with the deepsleep / wakelock / battery drain issue fixed.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download link at the bottom of this post.
It's actually a mashup of two roms: P7500XWMPJ_P7500XEZMP1_XEZ (Czech) and P7500ZCLP9_P7500OZHLP9_CHN (China). See below for details.
Background
Since the ICS update, the P7500 tab drains the battery much faster than previous honeycomb versions. It is commonly accepted that this behavior is due to a bug in the kernel that prevents the CPU from deep sleeping. You can verify how much the tab spends in each CPU mode with the CpuSpy app.
How this was fixed
Stiffmeister, a member of a german forum (page 30 onwards) found out that the CHN firmware does NOT have this bug. Massive credit goes to him. His solution involves flashing the CHN firmware, then CWM recovery, then a CWM update that adds additional languages. It remains unknown why the Chinese ROM fixes the deepsleep issues, but so far it's the only one that does.
Phibs, a XDA member further found out that the problem can also be fixed by flashing the boot.img + kernel modules + wpa_supplicant from the chinese rom. It is explained here and there is even a zip file you can flash from CWM on top of an ICS stock rom. Massive credit to him, too.
About this ROM
This is essentally the latest ROM from sammobile (XWMPJ - Czech) with the following modifications:
Replaced boot.img with CHN's
Replaced /system/lib/modules/* with CHN's
Replaced /system/bin/wpa_supplicant with CHN's
Removed recovery.img to prevent overwrite of existing recovery.
No changes have been made other than these.
Flashing with odin won't destroy your current recovery nor your data so it's safe to flash on top of an existing stock ICS. Nandroid first if it feels safer. Wipe not needed if coming from stock ICS. Flashing on top of honeycomb not tested.
Root
This is a non-root rom. You can root it yourself if you want. Your options are:
Flash this
or use the XWMPJ ROM from Toldo's thread, bonus packed with deodex, zipalign, init.d and root.
Flash
As stated elsewhere in this post and throughout the thread, flash with Odin.
How to cook your own
If you want to use another (non-Czech) rom as a base and patch it with the china boot.img yourself, follow this procedure:
Grab the two roms (CHN and the one you want to patch) from sammobile.
Grab ext4_utils from here.
Go to linux
Unzip ext4_utils and make them:
Code:
make
Untar the roms in two separate folders (I used cn for china, cz for czech)
On cn and cz, use simg2img from ext4_utils to turn system.img into an ext4 raw file:
Code:
./simg2img cn/system.img cn/system.ext4
./simg2img cz/system.img cz/system.ext4
Mount both cn and cz images:
Code:
mkdir cn/fs
mkdir cz/fs
sudo mount -o loop cn/system.ext4 cn/fs
sudo mount -o loop cz/system.ext4 cz/fs
We will be replacing cz's kernel with cn's later, these are dependent files that need to be copied over from cn to cz:
Code:
sudo cp cn/fs/lib/modules/* cz/fs/lib/modules
sudo cp cn/fs/bin/wpa_supplicant cz/fs/bin/wpa_supplicant
sudo cp cn/fs/bin/wlandutservice cz/fs/bin/wlandutservice
Now, find out what the block size and count were in the original img. Size * count / (1024 * 1024) will give you the filesystem size in MB, we will use it in the next step.
Code:
tune2fs -l cz/system.ext4
Rebuild the android image with make_ext4fs (from ext4_utils). 578M is the size in MB, and 4096 is the block size from the above step:
Code:
rm cz/system.img
sudo ./make_ext4fs -s -l 578M -b 4096 -a system cz/system.img cz/fs
You can unmount and remove temporary stuff now:
Code:
umount cn/fs
umount cz/fs
rmdir cn/fs cz/fs
rm cz/system.ext4
Copy boot.img over from cn to cz:
Code:
cp cn/boot.img cz/boot.img
If you have a custom recovery such as CWM and don't want it to be destroyed by odin when flashing this, remove cz/recovery.img:
Code:
rm cz/recovery.img
Now, Odin needs all the img files packed into a tar file with a md5 checksum piggybacked at the end:
Code:
cd cz
tar -H ustar -c *.bin *.img > rom.tar
md5sum rom.tar >>rom.tar
mv rom.tar rom.tar.md5
That's it, go to Odin and flash rom.tar.md5. Do not rename "rom.tar.md5" or Odin will complain. If you want to give it a more meaningful name (for distribution or whatever), rename "rom.tar" before piggybacking the md5.
Download
P7500XWMPJ_deepsleep.7z (350.2 MB)
@ mega: https://mega.co.nz/#!BxU1iC6Y!Paaqp1C1KevBRA9caSAGVy-4ynwOxdxf2hWogk49nEg
@ hotfile: https://hotfile.com/dl/202781788/50a705c/P7500XWMPJ_deepsleep.7z.html
Odin tells this
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> P7500XWMPJ_deepsleep.tar.md5 is invalid.
<OSM> End...
when I try to flash your Rom
Thanks!
My only question is if I want to flash CM10, flashing this ROM with Odin before will fix the deepsleep in CM10?
S_Hammer said:
Odin tells this
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> P7500XWMPJ_deepsleep.tar.md5 is invalid.
<OSM> End...
when I try to flash your Rom
Click to expand...
Click to collapse
His ROM is not odin flash, you need to flash the zip it in recovery.
Sent from my Nexus 4 using xda app-developers app
---------- Post added at 06:34 AM ---------- Previous post was at 06:30 AM ----------
LluisAzm said:
Thanks!
My only question is if I want to flash CM10, flashing this ROM with Odin before will fix the deepsleep in CM10?
Click to expand...
Click to collapse
This ROM is not for Odin.
No it won't, when u flash cm10 it will replace the files. This only for flashing over the ROM.
You can't replace these files in cm10 it won't fix the problem, this only works for stock ROMs.
For cm10 try KK2 radio with latest nightly, been working great for me for over two days now, 0.6% loss per hour
Sent from my Nexus 4 using xda app-developers app
LluisAzm said:
My only question is if I want to flash CM10, flashing this ROM with Odin before will fix the deepsleep in CM10?
Click to expand...
Click to collapse
No, CM10 will overwrite the chinese kernel which fixes the bug.
S_Hammer said:
<OSM> MD5 hash value is invalid
<OSM> P7500XWMPJ_deepsleep.tar.md5 is invalid.
Click to expand...
Click to collapse
Fixed. The md5 didn't match the actual tar name...
I've updated the link, you can redownload.
... or just rename the file to "rom.tar.md5" and odin should be okay with it.
javideslomao said:
No, CM10 will overwrite the chinese kernel which fixes the bug.
Click to expand...
Click to collapse
Check http://live.samsung-updates.com/index.php?device=GT-P7500
Often besides full firmware, also the separate Kernel can be downloaded (often, not always). So you can combine your regional firmware with specific kernel (flashable via (mobile) odin)), like XWMPE, F, I, J, whatever.
Dead Silence said:
Often besides full firmware, also the separate Kernel can be downloaded (often, not always). So you can combine your regional firmware with specific kernel (flashable via (mobile) odin)), like XWMPE, F, I, J, whatever.
Click to expand...
Click to collapse
The problem is that the wireless module (dhd.ko) lives in /system (ie. not included in boot.img), so if the kernel has a different ABI, the modules must be updated for the wifi to work. Or, at least, that's what happens when merging czech + china.
tested on my tab for 5 days. it's true - sleeps like a baby.
40 % batery lost ofter 5 dayes
nice
is it a dream?
no i am awake!!!!
Could someone please mirror the ROM? Mega is really sucks!!! The download speed is 10 Kb/s instead of 370 Kb/s!!!
soroush0313 said:
Could someone please mirror the ROM? Mega is really sucks!!! The download speed is 10 Kb/s instead of 370 Kb/s!!!
Click to expand...
Click to collapse
You may try this, instead of installing a full rom.
Install CWM and then install the zip file.
http://forum.xda-developers.com/showthread.php?t=2164447&page=3
odeccacccp said:
This ROM is not for Odin.
No it won't, when u flash cm10 it will replace the files. This only for flashing over the ROM.
You can't replace these files in cm10 it won't fix the problem, this only works for stock ROMs.
For cm10 try KK2 radio with latest nightly, been working great for me for over two days now, 0.6% loss per hour
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Where could I find the KK2 radio to try it if it might work?
Phibs said:
You may try this, instead of installing a full rom.
Install CWM and then install the zip file.
http://forum.xda-developers.com/showthread.php?t=2164447&page=3
Click to expand...
Click to collapse
This does not work, i get "recovery bootloop". This is also confirmed in Toldo's thread: http://forum.xda-developers.com/showthread.php?t=1813651&page=131
Perfect Rom. Deep sleep working properly.
Thanx.
so, how do i install the rom? is by odin or cwm?
is it odex or de-odex?
thanks.
Hmm strange, I wanted to try this rom and I was on CM 10.1. I did go to recovery wipe system, data, cache and dalvik and now there is nothing on my internal storage and I can't see the rom in order to flash it
How is this possible?
Hello, I have flashed the ROM but i can't root it... I flash cwm and Samsung_Galaxy_Tab_10.1_root.zip but doesn't work...
Anyone have root it?
Thanks!
LluisAzm said:
Hello, I have flashed the ROM but i can't root it... I flash cwm and Samsung_Galaxy_Tab_10.1_root.zip but doesn't work...
Anyone have root it?
Thanks!
Click to expand...
Click to collapse
Worked for me.
cnn888 said:
so, how do i install the rom? is by odin or cwm?
is it odex or de-odex?
thanks.
Click to expand...
Click to collapse
Via Odin, read the OP. And ist pure Stock, means odexed.
Vertumus said:
Hmm strange, I wanted to try this rom and I was on CM 10.1. I did go to recovery wipe system, data, cache and dalvik and now there is nothing on my internal storage and I can't see the rom in order to flash it
How is this possible?
Click to expand...
Click to collapse
Its not a ROM, ist a firmware. So flash it via odin.
Please note that I held no responsibility if you damage your phone, brick it or anything! This was made based on my own experience.
Hi, just thought I share my experience in changing CSC code. Initially I purchased my S5 with XSE (Indonesian) CSC code. Not having the patient for lollipop, I flashed Kazakhastan ROM and my CSC code changed to SKZ. After several months, samsung decided to release lollipop for XSE region and I flashed to it but was stuck with XXV (Vietnam). Not sure what happened but it seems that it takes the first code in the multi-CSC rom. Anyway this had me frustrated for a couple of months. So without further ado, here is the steps:
1. Download requirements:
-Download the BOC3 indian ROM: G900HXXU1BOC3_G900HODD1BOC3_G900HXXU1BOAD_HOME.tar.md5 (must be this ROM - this rom allows change CSC code without root)
-Download your country ROM (for my example is G900HXXU1BOD3_G900HOLB1BOD1_G900HXXU1BOCA_HOME.tar.md5)
-Download and install Cygwin - or any app which can modify .tar files, but lets use Cygwin for this case
-Download and install Odin 3.09 or higher (to flash ROMs)
2. Flash the indian ROM (G900HXXU1BOC3_G900HODD1BOC3_G900HXXU1BOAD_HOME.tar.md5) to your device
3. While waiting for the ROM to flash, open your country rom, remove .md5 at the end so the name will be from G900HXXU1BOD3_G900HOLB1BOD1_G900HXXU1BOCA_HOME.tar.md5 to G900HXXU1BOD3_G900HOLB1BOD1_G900HXXU1BOCA_HOME.tar
4. Open the G900HXXU1BOD3_G900HOLB1BOD1_G900HXXU1BOCA_HOME.tar with winzip or winrar, extract cache.img and hidder.img and place in home folder of Cygwin
5. Open cygwin and type the following:
tar -H ustar -cf csc.tar cache.img hidden.img
6. Test the indian rom, open dialer and type *#272*your-imei-number# - a selection of CSC should appear meaning that the ROM can change CSC without root
7. Flash in Odin, put the csc.tar in CSC and flash - this will not trip knox - I have tried this myself
8. Boot your phone, open dialer and type *#272*your-imei-number# - from here more codes should appear including the ones included in the csc.tar file
9. Select your country code (in this case I selected XSE) and it will automatically reboot
10. Shut down and check your CSC in bootloader (hold power + up + home) it should be correct now
11. Flash your country rom, clear cache and everything and voila!
Please also note that this guide should work on other devices as long as the device has a rom with *#272*your-imei-number# enabled without root
Hope this helps!
adit said:
Please note that I held no responsibility if you damage your phone, brick it or anything! This was made based on my own experience.
Hi, just thought I share my experience in changing CSC code. Initially I purchased my S5 with XSE (Indonesian) CSC code. Not having the patient for lollipop, I flashed Kazakhastan ROM and my CSC code changed to SKZ. After several months, samsung decided to release lollipop for XSE region and I flashed to it but was stuck with XXV (Vietnam). Not sure what happened but it seems that it takes the first code in the multi-CSC rom. Anyway this had me frustrated for a couple of months. So without further ado, here is the steps:
1. Download requirements:
-Download the BOC3 indian ROM: G900HXXU1BOC3_G900HODD1BOC3_G900HXXU1BOAD_HOME.tar.md5 (must be this ROM - this rom allows change CSC code without root)
-Download your country ROM (for my example is G900HXXU1BOD3_G900HOLB1BOD1_G900HXXU1BOCA_HOME.tar.md5)
-Download and install Cygwin - or any app which can modify .tar files, but lets use Cygwin for this case
-Download and install Odin 3.09 or higher (to flash ROMs)
2. Flash the indian ROM (G900HXXU1BOC3_G900HODD1BOC3_G900HXXU1BOAD_HOME.tar.md5) to your device
3. While waiting for the ROM to flash, open your country rom, remove .md5 at the end so the name will be from G900HXXU1BOD3_G900HOLB1BOD1_G900HXXU1BOCA_HOME.tar.md5 to G900HXXU1BOD3_G900HOLB1BOD1_G900HXXU1BOCA_HOME.tar
4. Open the G900HXXU1BOD3_G900HOLB1BOD1_G900HXXU1BOCA_HOME.tar with winzip or winrar, extract cache.img and hidder.img and place in home folder of Cygwin
5. Open cygwin and type the following:
tar -H ustar -cf csc.tar cache.img hidden.img
6. Test the indian rom, open dialer and type *#272*your-imei-number# - a selection of CSC should appear meaning that the ROM can change CSC without root
7. Flash in Odin, put the csc.tar in CSC and flash - this will not trip knox - I have tried this myself
8. Boot your phone, open dialer and type *#272*your-imei-number# - from here more codes should appear including the ones included in the csc.tar file
9. Select your country code (in this case I selected XSE) and it will automatically reboot
10. Shut down and check your CSC in bootloader (hold power + up + home) it should be correct now
11. Flash your country rom, clear cache and everything and voila!
Please also note that this guide should work on other devices as long as the device has a rom with *#272*your-imei-number# enabled without root
Hope this helps!
Click to expand...
Click to collapse
will try this gan, not increase knox right?
hope it works.
Terima kasih..
noez92 said:
will try this gan, not increase knox right?
hope it works.
Terima kasih..
Click to expand...
Click to collapse
Knox remains 0x0 gan dijamin aman
adit said:
Knox remains 0x0 gan dijamin aman
Click to expand...
Click to collapse
so frustating to see XXV, festive effect, tiengviet lang :laugh:
---------- Post added at 12:37 AM ---------- Previous post was at 12:34 AM ----------
can you help for process in CYGWIN? because it says no directory
nvm, already do it in another directory.
omg!
i can confirm this method works on my G900H.
Nice job gan.
Thanks banyak...
Need available csc code for sgh-t889 on v4.3
How do i get the available csc code coz someone told me its what cozing my network &b data problems
Which ROM are you on? Does *#272*imei work?
Am on stock rom 4.3 & that code doesnt work on it
AFAIK, the only rom with working CSC change is BOC3 indian ROM: G900HXXU1BOC3_G900HODD1BOC3_G900HXXU1BOAD_HOME.tar .md5
That ROM is for S5 & mine is a Note 2
Please see the title and the forum, this is an S5 forum, better luck looking at note 2 forum.
adit said:
Please see the title and the forum, this is an S5 forum, better luck looking at note 2 forum.
Click to expand...
Click to collapse
Where we get this rom? Can you please give the link??
As you know, root has been achieved on this device. Now, let's move on to recovery. The recovery.img is a lot like the boot.img, in the way that you can boot from it. In theory, if we make a 3e recovery.bin for this device (TWRP/CWM), and we boot from it, we will be able to install any rom. Let's let the Recovery.bin development start!
THIS DEVICE DOES NOT SUPPORT FLASHING RECOVERIES. YOU HAVE TO BOOT FROM THEM IN FASTBOOT.
This device now has 2 custom recoveries, those 2 being TWRP (Team Win Recovery Project) and CM (CyanogenMod) Recovery. CyanogenMod recovery is much like the stock recovery, with the only difference being that CM Recovery can install files that don't have the Amazon ZIP Signature. TWRP, on the other hand, has a touchscreen display, and is much more user friendly than CM Recovery. The links to both are here:
CM Recovery
TWRP
You can do many things in a Custom Recovery, such as:
Install custom ROMs (Found here)
Install modifications to your current OS (XPosed Framework, Root, etc.)
Install GAPPS (Google Applications, including Play Store and Play Services)
Wipe your current ROM
Backup your current ROM
Restore a backup of a previous ROM
If you have any questions, ask them here.
Now, press the thank button here and thank the developers that made these recoveries and ROMs possible, and you are good to go.
Good Luck!
Im dumping the recovery partition right now as well as the boot as well and the other two extra bootloader stuff that may help us
I have attached the images we can use. I dont know if we need the system image file but if we do just let me know hopefully ill be able to upload it or someone else might cause its 1 GB it may take some time.
Awesomeslayerg said:
I have attached the images we can use. I dont know if we need the system image file but if we do just let me know hopefully ill be able to upload it or someone else might cause its 1 GB it may take some time.
Click to expand...
Click to collapse
Well, we just need someone to build a recovery for this device. Once that is bootable, we can install roms. Also, since we will most likely not be able to unlock the bootloader, Safestrap might be our best bet.
True.. it's a mediatek soc so there's gotta be a way to unlock the bootloader because most of the mediatek devices have unlocked bootloader I think. And besides it gives us an unlock code so we need to see what that deal is
Just leaving here partitions structure:
Model: MMC 8GND3R (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 1049kB 2097kB 1049kB KB
2 2097kB 3146kB 1049kB DKB
3 3146kB 21.4MB 18.2MB EXPDB
4 21.4MB 22.4MB 1049kB UBOOT
5 22.4MB 39.2MB 16.8MB boot
6 39.2MB 56.0MB 16.8MB recovery
7 56.0MB 56.5MB 524kB MISC
8 56.5MB 60.2MB 3670kB LOGO
9 60.2MB 65.4MB 5243kB TEE1
10 65.4MB 70.6MB 5243kB TEE2
11 70.6MB 1329MB 1258MB ext4 system
12 1329MB 1591MB 262MB ext4 cache
13 1591MB 7818MB 6227MB ext4 userdata
Hmm it looks like the MTK Droid Root and Tools V2.5.3 works now so we can flash images via that as well as recovery AND boot. But someone should get a 2nd fire and try it out because we have no scatter file.
We could possibly install a 2nd bootloader
Awesomeslayerg said:
Hmm it looks like the MTK Droid Root and Tools V2.5.3 works now so we can flash images via that as well as recovery AND boot. But someone should get a 2nd fire and try it out because we have no scatter file.
We could possibly install a 2nd bootloader
Click to expand...
Click to collapse
I have made this one and test ro readback partitions bug gets error 2004
Partition lists
storage, boot_channel & block_size maybe not good
Model: MMC 8GND3R (sd/mmc)
storage: SDMMC ????
Sometimes tablet wont boot and have to remove battery connector
Last SP Flash TOOL, linux version have much errors and force to remove battery
http://firmware.su/51343-sp-flash-tool.html
DO NO USE TO DOWNLOAD ANYTHING
UNDER CONSTRUCTION
scatter updated, UNTESTED
Lets go recovery!
idme print as su
unlock_code:
---------- Post added at 12:09 PM ---------- Previous post was at 11:52 AM ----------
There are 2 boads type and 2 preloaders......
Mine have preloader_prod.img board_id: 0025001040000015
Code:
# check if production device
if ("0025001000000015" == read_file_str("/proc/idme/board_id") ||
"0025001000010015" == read_file_str("/proc/idme/board_id") ||
"0025001010000015" == read_file_str("/proc/idme/board_id") ||
"0025001010010015" == read_file_str("/proc/idme/board_id") ||
"0025001020000015" == read_file_str("/proc/idme/board_id"))
then
ui_print("Copying preloader.img to boot partition 0 for unsecure device...");
package_extract_file("images/preloader.img", "/dev/block/platform/mtk-msdc.0/mmcblk0boot0");
else
ui_print("Copying preloader_prod.img to boot partition 0 for secure device...");
package_extract_file("images/preloader_prod.img", "/dev/block/platform/mtk-msdc.0/mmcblk0boot0");
endif;
my /proc/idme/board_id reads 0025001040000015
Can anyone try this: http://forum.xda-developers.com/showthread.php?t=2798257?
Sent from my KFFOWI using Tapatalk
I did yesterday didn't work
Awesomeslayerg said:
I did yesterday didn't work
Click to expand...
Click to collapse
Did you try Fastboot boot recovery.img with the one it gave?
Sent from my XT912 using Tapatalk
No I'll try today
Okay i used the MTK-TWRP thing right now and used it to unpack the recovery image and it looks like we can use this to our advantage to flash unverified files by editing some of the prop settings.
Can someone try this: http://xda-university.com/as-a-developer/porting-clockworkmod-recovery-to-a-new-device? It might work.
How would we flash it?
Awesomeslayerg said:
How would we flash it?
Click to expand...
Click to collapse
Zips are flashable in flashfire...
Awesomeslayerg said:
How would we flash it?
Click to expand...
Click to collapse
Use the following commands to flash the recovery
Code:
adb shell
su
dd if=/sdcard/recovery.img of=/dev/block/platform/mtk-msdc.0/by-name/recovery
- I have Cyanogenmod Recovery working except a few minor niggles
- Let you know once it's fully working
- It looks like we can't boot unsigned images that are flashed to the recovery partition
- If I boot the image from fastboot rather than flashing it then it works
- CVE-2014-0973 is patched in the bootloader
Hello
The mobile had the following error "Encryption unscuccessfull"
It was no longer possible to install a ROM.
Only after the in
mount and Storge Menu the partitions have been reformatted.
After that, the modem zip was still installed without success
Rome only runs the sim card is not recognized.
SIM card works in other mobile phone
Hardware error?
S III i9305
ClockworkMod Recovery V6.0.4.7
Rome
lineage-14.1
or
RR-N v5.8.5
@uzzoo If my reply sounds a bit "unstructired" I apologise but I'm not convinced if I completely grasp the whole issue.
In Settings => About phone, is the modem/baseband indicated by its version or does it states "unknown"?
I urgently suggest to replace your current recovery by TWRP 3.0.2-1! And please only use this version; any later one will again make trouble.
You are mentioning "Encryption unscuccessful", Did you try to encrypt your device? If I correctly remember RR (and I believe same applies to LOS) does not support encryption. Maybe @rodman01 can confirm?
Last but not least: The issue "SIM not recognised" was already reported several times in different threads and solutions provided. I assume your consent that I don't conduct the searches for you but I suggest to search these threads:
https://forum.xda-developers.com/ga...m-resurrection-remix-4-4-2-kitkat-v5-t2704828
https://forum.xda-developers.com/ga...resurrection-remix-4-4-2-kitkat-v5-1-t2950817
https://forum.xda-developers.com/ga...m-unofficial-lineageos-14-1-gt-i9305-t3542012
Yes encryption is not working with at least the latest RR versions on our phone.
Not sure whether it had been working on any not samsung stock based custom rom for the i9305. I never tested it or dived deeper in the topic to get it to work, so this might be not a very reliable post .
Have the phone with the error message encrypted.
Official LineageOS 14.1 Samsung Galaxy S III LTE GT-I9305
last version is running
modem / baseband will display "unknown"
Will continue with the following instructions.
1) Install TWRP:
TWRP 3.2.3-0 fails installing .zips here, 3.0.2-1 is fine.
https://dl.twrp.me/i9305/twrp-3.0.2-1-i9305.img.html
- Boot to bootloader (Power, Volume Down, Home)
As I'm running linux on my PC, I'm using heimdall for flashing:
- sudo heimdall flash --no-reboot --RECOVERY twrp-3.0.2-1-i9305.img
2) For a clean start, wipe everything in TWRP first:
- Boot to TWRP (Power, Volume Up, Home)
- Format data
- Mount everything but EFS and MicroSD, including System, not read-only
- Advanced wipe: Wipe everything but MicroSD card
- Reboot to download
3) Install stock ROM:
I found the current stock ROM here:
https://updato.com/firmware-archive-...r=desc&exact=1
At least for my country (Germany, DBT) the appropriate modem file ...UFOA1 is included!
- Boot to bootloader
- sudo heimdall flash --no-reboot --BOOTLOADER sboot.bin --TZSW tz.img --BOOT boot.img --TOMBSTONES tombstones.img --CACHE cache.img --RADIO modem.bin --RECOVERY recovery.img --SYSTEM system.img --HIDDEN hidden.img
4) Boot the stock Android!
Baseband did not work for me as long as I directly continued without booting Android.
So let Android boot until it says welcome (no need to continue with the initial setup).
5) Install TWRP again
- Boot to bootloader
- sudo heimdall flash --no-reboot --RECOVERY twrp-3.0.2-1-i9305.img
6) Install files in TWRP:
- Boot to TWRP
- Copy files to external SD-Card:
LineageOS from http://buildyourownandroid.selfhost..../daily-builds/
Open Gapps from https://opengapps.org/ (ARM, 7.1, pico)
system(sim_support).zip from https://forum.xda-developers.com/sho...&postcount=800
su (arm) 14.1 from https://download.lineageos.org/extras
- Wipe Data, Cache and Dalvik
- Install all the four files in the order given above
The installation runs fine besides two "E:unknown command [log]" messages.
7) Reboot to system, everything is working fine.
Click to expand...
Click to collapse
Have the phone with the error message encrypted.
Official LineageOS 14.1 Samsung Galaxy S III LTE GT-I9305
last version is running
modem / baseband will display "unknown"
Will continue with the following instructions.
1) Install TWRP:
TWRP 3.2.3-0 fails installing .zips here, 3.0.2-1 is fine.
https://dl.twrp.me/i9305/twrp-3.0.2-1-i9305.img.html
- Boot to bootloader (Power, Volume Down, Home)
As I'm running linux on my PC, I'm using heimdall for flashing:
- sudo heimdall flash --no-reboot --RECOVERY twrp-3.0.2-1-i9305.img
2) For a clean start, wipe everything in TWRP first:
- Boot to TWRP (Power, Volume Up, Home)
- Format data
- Mount everything but EFS and MicroSD, including System, not read-only
- Advanced wipe: Wipe everything but MicroSD card
- Reboot to download
3) Install stock ROM:
I found the current stock ROM here:
https://updato.com/firmware-archive-...r=desc&exact=1
At least for my country (Germany, DBT) the appropriate modem file ...UFOA1 is included!
- Boot to bootloader
- sudo heimdall flash --no-reboot --BOOTLOADER sboot.bin --TZSW tz.img --BOOT boot.img --TOMBSTONES tombstones.img --CACHE cache.img --RADIO modem.bin --RECOVERY recovery.img --SYSTEM system.img --HIDDEN hidden.img
4) Boot the stock Android!
Baseband did not work for me as long as I directly continued without booting Android.
So let Android boot until it says welcome (no need to continue with the initial setup).
5) Install TWRP again
- Boot to bootloader
- sudo heimdall flash --no-reboot --RECOVERY twrp-3.0.2-1-i9305.img
6) Install files in TWRP:
- Boot to TWRP
- Copy files to external SD-Card:
LineageOS from http://buildyourownandroid.selfhost..../daily-builds/
Open Gapps from https://opengapps.org/ (ARM, 7.1, pico)
system(sim_support).zip from https://forum.xda-developers.com/sho...&postcount=800
su (arm) 14.1 from https://download.lineageos.org/extras
- Wipe Data, Cache and Dalvik
- Install all the four files in the order given above
The installation runs fine besides two "E:unknown command [log]" messages.
7) Reboot to system, everything is working fine.
Click to expand...
Click to collapse
uzzoo said:
Have the phone with the error message encrypted.
Official LineageOS 14.1 Samsung Galaxy S III LTE GT-I9305
last version is running
modem / baseband will display "unknown"
Will continue with the following instructions.
Click to expand...
Click to collapse
Why didn't you accept the advice I already provided here? You are using a TWRP version that most likely leads to problems.
I do not have a twrp version on it
There is still an old ClockworkMod Recovery V6.0.4.7
The mobile phone has been running since 2016 with no problems
Had already tried the twrp on it.
Currently under Win10 / Linux
uzzoo said:
I do not have a twrp version on it
There is still an old ClockworkMod Recovery V6.0.4.7
The mobile phone has been running since 2016 with no problems
Had already tried the twrp on it.
Currently under Win10 / Linux
Click to expand...
Click to collapse
I can offer you to send me your phone with DHL or something. Ulm is not that far away from me, around 120 KM. Other possibility if you want to make a trip into the wonderful Allgäu you can come in for a coffee or 2 and we will have a look at your device. Last: I maybe can arrange a date with my sister who is living also in the near of Ulm. Btw I lived in Neu-Ulm for around 20 years . On Sunday the 4th of August I will visit my sister at their home, so that I can put the mobile from her. Or maybe we find a possibility to meet each other at that day and you pass me your device personally. No promise that I can solve the problem, but maybe it is worth a try.
uzzoo said:
I do not have a twrp version on it
There is still an old ClockworkMod Recovery V6.0.4.7
The mobile phone has been running since 2016 with no problems
Had already tried the twrp on it.
Currently under Win10 / Linux
Click to expand...
Click to collapse
Adding to @rodman01 generous offer that is most likely the most proper solution due to the vicinity of Ulm to his home, if you have plans to visit the most westerly part of Germany in the near future, I'd also be personal available to assist.
#######
And if you rather prefer to use the German language, just let me know and I'd place the German translation below the English version. You can also use Google Translate; just place the Englisg translation above your German post. Although German is my mother tongue, just wanted to show you how it looks like.
*****
Translated by Google Translate:
Und wenn Sie lieber die deutsche Sprache verwenden möchten, lassen Sie es mich einfach wissen und ich platziere die deutsche Übersetzung unter der englischen Version. Sie können auch Google Translate verwenden. Platzieren Sie einfach die englische Übersetzung über Ihrem deutschen Beitrag. Obwohl Deutsch meine Muttersprache ist, wollte ich Ihnen nur zeigen, wie es aussieht.
rodman01 said:
I can offer you to send me your phone with DHL or something. Ulm is not that far away from me, around 120 KM. Other possibility if you want to make a trip into the wonderful Allgäu you can come in for a coffee or 2 and we will have a look at your device. Last: I maybe can arrange a date with my sister who is living also in the near of Ulm. Btw I lived in Neu-Ulm for around 20 years . On Sunday the 4th of August I will visit my sister at their home, so that I can put the mobile from her. Or maybe we find a possibility to meet each other at that day and you pass me your device personally. No promise that I can solve the problem, but maybe it is worth a try.
Click to expand...
Click to collapse
Obligatory first post on the forums here so hopefully this is the right place!
I have been lurking on the forums for the past month or so and have been working on building a custom kernel from source for the SM-G780F/DSC(Exynos) edition. I've built some kernels from source before so I have some experience there, but actually getting the kernel to flash and run on the device is a different story. I have built the kernel with the modifications that I wanted, fixed some flashing issues I was running into, finally got the boot.img to flash succefully to the device, rebooted the device and the phone just hangs at the Samsung logo. (See "Image from iOS.png").
Here is the steps that I did:
Unlock Bootloader on the device.USB Debugging on, OEM Unlocking enabled in dev settings/ OEM Lock: OFF(U) in DL mode.
Checked to make sure KG State is not Prenormal, it is in checking state.
Device is currently running stock G780FXXS7CUI5, so I download this version source from https://opensource.samsung.com/uploadSearch?searchValue=SM-G780F
Extract Kernel.tar.gz, update toolchain paths in the Makefile/build_kernel.sh, and I make some modifications to the defconfig file.
Code:
./build_kernel.sh
; Fix compiler errors/warnings as they appear. Rinse and repeat until the kernel is built.
Now that the kernel is built I pull the stock ROM that this device is currently running from Sammobile. https://www.sammobile.com/samsung/g.../SM-G780F/MID/download/G780FXXS7CUI5/1583411/
Extract the AP directory from the Sammobile ROM download.
Extract the boot.img.lz4 from the AP directory so I now have the uncompressed boot.img.
Copy over the the stock boot.img to my AIK directory. (AIK-Kinux-V3.8)
Code:
./unpackimg.sh boot.img
, cd into split_img, rm the stock boot.img-kernel
Move my custom kernel image to the AIK directory,
Code:
mv kernel_source/out/arch/arm64/boot/Image /AIK-Linux/split_img/boot.img-kernel
Run AIK repackimage.sh
Now I have a SM-G780G(Snapdragon edition) S20_FE with Magisk installed. So I copy over my image-new.img to this device and patch the image-new.img with Magisk
Move back the patched image to my linux enviroment. Rename my patched image boot.img.
Compress my boot img with
Code:
lz4 -B6 --content-size boot.img boot.img.lz4
.
Replace the stock boot.img.lz4 in my AP directory with my modded boot.img.lz4
Pull down a clean vbmeta.img from https://dl.google.com/developers/android/qt/images/gsi/vbmeta.img
Compress this image as well
Code:
lz4 -B6 --content-size vbmeta.img vbmeta.img.lz4
Replace the stock vbmeta.img.lz4 in the AP directory with my clean vbmeta.img.lz4 in the
So the contents of the AP directory currently is
Code:
22556009 Apr 7 12:57 boot.img.lz4
1155 Sep 23 2021 dqmdbg.img.lz4
219753 Sep 23 2021 dtbo.img.lz4
4096 Sep 23 2021 meta-data
1148 Sep 23 2021 metadata.img.lz4
2773 Sep 23 2021 misc.bin.lz4
35115127 Sep 23 2021 recovery.img.lz4
5457239441 Sep 23 2021 super.img.lz4
822394050 Sep 23 2021 userdata.img.lz4
2375 Apr 7 12:57 vbmeta.img.lz4
2812 Sep 23 2021 vbmeta_samsung.img.lz4
tarball all these files with
Code:
tar -cvf Modded_AP.tar *
Spin up latest version of ODIN
Place Custom AP into AP slot, Stock BL into BL slot, Stock CP into CP slot, and Stock HOME_CSC into CSC slot
Start Flashing.
Flashing is successful.
Device reboots, and hangs at the Samsung Galaxy S20FE Screen with the warning "I am not running samsungs official software."
A couple of questions I am asking myself is the stock vbmeta_samsung.img.lz4 necessary, as well as some of the other stock files? Is patching my boot.img with Magisk running on a different
device giving me issues? Am i missing a step somewhere or is there still extra steps I need to take to get a modded kernel running on this device. Any help would be greatly appreciated or if I need to provide any more insight please let me know! Thanks again!
you'd be extremely welcome in our little group
S20 FE Modding
Exynos AOSP: https://t.me/S20FE_Exy TurboUI: https://t.me/projectxs20fe Prime Kernel Snap: https:/t.mes20fesnapdragon Prime Kernel Exynos: https://t.me+vpzEK9kPMc41MmY9 Bandido Kernel https://t.me/bandidokernel Klimbo Kernel https://t.me/klimbokernel
t.me
there's also a kernel dev there from time to time who has built kernels for all versions FE completely blind, i.e. without being able to flash them himself. maybe we can get you two talking.
it sounds like you've added two kernels to your AP archive. as I understand it once you've built your kernel, compressed it to .lz4 you can just archive it inside a tar file and flash that alone (as long as it matches your firmware).
Hi there Buddy, so answering your questions- we dont need vbmeta everytime, we only use it once to flash twrp after which flashing vbmeta not necessary. Now yes patching boot.img with other device other than the one you are running causes problems here and device doesnt like to boot. As per the last kernel dev he just used our stock boot.img and compiled his changes. And we flash hi kernel like normal flash.
S20 FE Modding
Exynos AOSP: https://t.me/S20FE_Exy TurboUI: https://t.me/projectxs20fe Prime Kernel Snap: https:/t.mes20fesnapdragon Prime Kernel Exynos: https://t.me+vpzEK9kPMc41MmY9 Bandido Kernel https://t.me/bandidokernel Klimbo Kernel https://t.me/klimbokernel
t.me
You can even join this group, there are many people willing to help others.
Also i have been developing stock based roms for all the variants, so would be happy to test them once they get stable enough to boot.
Thanks for the responses everyone! I'll take my follow up questions to the group!
Hi. There are some kernel changes that is needed to be applied in order to successfully boot the custom kernel. I suggest you post the kernel source so I can review it. You don't need to place everything inside the AP. You can just archive the boot.img.lz4 as tar.
Also, a lot of your steps can be simplified by making a twrp-flashable zip instead. You can use my template here:
android_kernel_samsung_s20fe/AnyKernel3 at exynos · pascua28/android_kernel_samsung_s20fe
Custom kernel for Samsung S20 FE (Snapdragon and Exynos variants) - android_kernel_samsung_s20fe/AnyKernel3 at exynos · pascua28/android_kernel_samsung_s20fe
github.com
Just move the arch/arm64/boot/Image as zImage and you can zip the AnyKernel3 folder and there you have a twrp-flashable zip. It's a lot more convenient this way as people do not need to carry around their computers whenever they need to flash custom stuffs plus, it's more universal this way as they don't have to have a matching firmware version; it will just use the existing boot image, unpack it, replace the kernel, repack and then flash it back to the device.
If you have any questions, feel free to contact me on telegram (pascua14). I hope you succeed
Regards