Im not gonna beat around the bush im a New Dev trying to Make a ROM im not 100% knowledgable on this but learning.
Rom Base 4.1.1-STock- from upndwn4par
what i wants to do with this?
1st Make it a LITE rom<trying to cut on the stock Fatness
2nd Make Simple mods(hold back to kill, Center Clock, bootanimation,23 toggle mod etc You get my point)
so far ive trim Down to the nest knowledge of Debloating- ive been using THIS LIST from another forum(and comparing to other gs3 the bloat is thesame)
So far ive only cut down the rom in bloat not to heavy but fairly a decent amount by 100mbs EST.
Here so far i think what is preventing my flash from workin>Since im new i though i would start using android Kitchen what ive done with this is: boot animation,data/app enable,The rest was done by the rom provider root,busybox deodex.
Now i compile in android kitchen but when i flash i get this error
Installing '/external_sd/redone.zip'... Checking for MD5 file... I:Cannot find file /external_sd/redone.zip.md5 Skipping MD5 check: no MD5 file found. mount: failed to mount /dev/block/mmcblk0p17 at /cache: Device or resource busy mount: failed to mount /dev/block/mmcblk0p15 at /data: Device or resource busy script aborted: format() expects 4 args, got 3 format() expects 4 args, got 3 E:Error executing updater binary in zip '/external_sd/redone.zip' Error flashing zip '/external_sd/redone.zip' Updating partition details... Iata backup size is 0MB, size: 12335MB, used: 16MB, free: 12161MB, in data/media: 16MB. I:Unable to mount '/usb-otg' I:Actual block device: '', current file system: 'vfat' I:Set page: 'flash_done' I:Set page: 'clear_vars'
i just need someone more advanced in this than me to help me out when i did a search to try and fix it stated to replace the update-binary so i did with the orignal stock binary and no go
HERE IS EVERYTHING REMOVE FROM ROM AND ALSO THE BUILD
https://www.dropbox.com/sh/jm0btla9iaxkj6r/0Q_XOBbGn4?v=0mcns
Much thanks
DEV CAN WE MOVE THIS TO THIS THREAD http://forum.xda-developers.com/showthread.php?t=2182496
crashpsycho said:
Im not gonna beat around the bush im a New Dev trying to Make a ROM im not 100% knowledgable on this but learning.
Rom Base 4.1.1-STock- from upndwn4par
what i wants to do with this?
1st Make it a LITE romSince im new i though i would start using android Kitchen what ive done with this is: boot animation,data/app enable,The rest was done by the rom provider root,busybox deodex.
Now i compile in android kitchen but when i flash i get this error
Installing '/external_sd/redone.zip'... Checking for MD5 file... I:Cannot find file /external_sd/redone.zip.md5 Skipping MD5 check: no MD5 file found. mount: failed to mount /dev/block/mmcblk0p17 at /cache: Device or resource busy mount: failed to mount /dev/block/mmcblk0p15 at /data: Device or resource busy script aborted: format() expects 4 args, got 3 format() expects 4 args, got 3 E:Error executing updater binary in zip '/external_sd/redone.zip' Error flashing zip '/external_sd/redone.zip' Updating partition details... Iata backup size is 0MB, size: 12335MB, used: 16MB, free: 12161MB, in data/media: 16MB. I:Unable to mount '/usb-otg' I:Actual block device: '', current file system: 'vfat' I:Set page: 'flash_done' I:Set page: 'clear_vars'
i just need someone more advanced in this than me to help me out when i did a search to try and fix it stated to replace the update-binary so i did with the orignal stock binary and no go
HERE IS EVERYTHING REMOVE FROM ROM AND ALSO THE BUILD
https://www.dropbox.com/sh/jm0btla9iaxkj6r/0Q_XOBbGn4?v=0mcns
Much thanks
DEV CAN WE MOVE THIS TO THIS THREAD http://forum.xda-developers.com/showthread.php?t=2182496
Click to expand...
Click to collapse
If you want to make a base its actually a bit more frustrating than building the ROM as a cook. I wish you I could help you but I got the same error while using the kitchen. Ive been told that the kitchen can be a bit tricky for our devices so.... I suggest you get upndwn4par's stock base and build your ROM with that. Its already done and you can now tinker just like I did.
I would then hit up loserskaters how to thread and search out any ofher ones you like.
Do you know how to compile and decompile?
Also copy the text from this thread to. your new one and I can copy my response over there. Devs will read the other one more often and its less clutter.
Have any questions I can help however I can but I'm just a cook too
Sent from my SAMSUNG-SGH-I747 using xda premium
I have never tried the kitchen so I do not know there. But what I usually have done is get a ROM that you know can be flashed and works on your phone.
Then do whatever you are wanting to change from your base ROM your using (stock deodexed works best usually since it hasn't been modified at all yet). Make all your changes to the .apk's after decompiling them, then recompile all the .apk's
Next take all your NEWLY recompiled .apks and move them into the working ROM that is recovery flash able. Put them in all the same locations where you find them.
Make changes to the updater-script only where needed for things like your ROM name and etc. and save it.
So once your done you should have a working flashable in recovery zip that now has all your .apks inside of it. Make a nandroid and then flash your newly created ROM. Give Thanks to whichever ROM dev you used the flashable zip from for use of their scripting.
Again all the above is after you know how to decompile/recompile the .apks without any errors. I also test each .a pk by pushing it to the phone first, overwriting the original apps .a pk Reboot the phone to make sure the .apks work correctly and the mods you changed in the .apks works correctly. I am not a dev but did some cooking and changing things to add whatever functionality I wanted. Then I started just wanting to theme things and got away from making as many mods (since usually the ROM I am running at the time they have/had already implemented many of the things I liked). If I can be of any help shoot me a pm.
Also as stated above, Losersk8ter has made a few How To threads for the things your asking about that you want to change/add. Some of his mods have really gone over the top lately with some REALLY cool features all put together like I haven't seen in a TW based ROM. So I am sure once you hit the ground running a bit you can pm him for advice if needed.
Sent from My Spiderman Themed I747
Related
I have a rooted Find 7a with TWRP based recovery and tried to install the system updates on Color OS 1.2.4i.
Unfortunately the update fails after rebooting into recovery
I:Inserting 'install /storage/sdcard0/.OTA/FIND7WX_12_OTA_INT_009_patch_svn9441.zip'
I:Copying file /cache/recovery/log to /cache/recovery/last_log
I:Attempt to load settings from settings file...
I:Loading settings from '/sdcard/TWRP/.twrps'.
I:Backup folder set to '/external_sd/TWRP/BACKUPS/X9007'
I:Copying file /etc/recovery.fstab to /cache/recovery/recovery.fstab
I:Version number saved to '/cache/recovery/.version'
I:TWFunc::Fixup_Time: Setting time offset from file /data/time/ats_2, offset 1406831189202
I:Switching packages (TWRP)
I:Set page: 'action_page'
Processing AOSP recovery commands...
I:Skipping screen timeout threads: TW_NO_SCREEN_TIMEOUT is set
I:command is: 'install' and I:value is: '/storage/sdcard0/.OTA/FIND7WX_12_OTA_INT_009_patch_svn9441.zip'
I:Trying to find zip '/storage/sdcard0/.OTA/FIND7WX_12_OTA_INT_009_patch_svn9441.zip' on '/external_sd'...
I:Looking for zip at '/sdcard0/.OTA//FIND7WX_12_OTA_INT_009_patch_svn9441.zip'
I:Looking for zip at '/external_sd//sdcard0/.OTA//FIND7WX_12_OTA_INT_009_patch_svn9441.zip'
I:Looking for zip at '/.OTA//FIND7WX_12_OTA_INT_009_patch_svn9441.zip'
I:Looking for zip at '/external_sd//.OTA//FIND7WX_12_OTA_INT_009_patch_svn9441.zip'
I:Looking for zip at '//FIND7WX_12_OTA_INT_009_patch_svn9441.zip'
I:Looking for zip at '/external_sd///FIND7WX_12_OTA_INT_009_patch_svn9441.zip'
I:Trying to find zip '/storage/sdcard0/.OTA/FIND7WX_12_OTA_INT_009_patch_svn9441.zip' on '/sdcard'...
I:Looking for zip at '/sdcard0/.OTA//FIND7WX_12_OTA_INT_009_patch_svn9441.zip'
I:Looking for zip at '/sdcard//sdcard0/.OTA//FIND7WX_12_OTA_INT_009_patch_svn9441.zip'
I:Looking for zip at '/.OTA//FIND7WX_12_OTA_INT_009_patch_svn9441.zip'
I:Looking for zip at '/sdcard//.OTA//FIND7WX_12_OTA_INT_009_patch_svn9441.zip'
Installing zip file '/sdcard//.OTA//FIND7WX_12_OTA_INT_009_patch_svn9441.zip'
Installing '/sdcard//.OTA//FIND7WX_12_OTA_INT_009_patch_svn9441.zip'...
Checking for MD5 file...
I:Cannot find file /sdcard//.OTA//FIND7WX_12_OTA_INT_009_patch_svn9441.zip.md5
Skipping MD5 check: no MD5 file found.
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: Device or resource busy
delete /data/dalvik-cache/firstboot.flag in Incremental OTA Package.
script aborted: assert failed: getprop("ro.product.device") == "FIND7" ||
getprop("ro.build.product") == "FIND7"
assert failed: getprop("ro.product.device") == "FIND7" || getprop("ro.build.product") == "FIND7"
E:Error executing updater binary in zip '/sdcard//.OTA//FIND7WX_12_OTA_INT_009_patch_svn9441.zip'
E:Error installing zip file '/sdcard//.OTA//FIND7WX_12_OTA_INT_009_patch_svn9441.zip'
Done processing script file
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Switching packages (TWRP)
I:Set page: 'advanced'
I:Set page: 'confirm_action'
I:Set page: 'action_page'
I:Copying file /tmp/recovery.log to /external_sd/recovery.log
Click to expand...
Click to collapse
Can somone tell me what do I need to do?
I thank you for your help!
This won't work anyway! You'll have to flash the actual stock recovery, cause these updates are patching and hashing for correct stock recovery! And therefore you'll have to install latest stock recovery or your update won't succeed.
Greets Zoltan-X
No!
If you use the latest official TWRP recovery you be able to flash oppo firmware. I tested with my x9077 and the latest firmwares, the international and chinese versions.
Ok thank you for the answers
With the stock recovery the update bar goes about 40 or 50%. So the update fails.
With the latest TWRP i get this:
Installing '/sdcard///FIND7WX_12_OTA_INT_009_patch_svn9441.zip'...
Checking for MD5 file...
I:Cannot find file /sdcard///FIND7WX_12_OTA_INT_009_patch_svn9441.zip.md5
Skipping MD5 check: no MD5 file found.
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: Device or resource busy
delete /data/dalvik-cache/firstboot.flag in Incremental OTA Package.
Verifying current system...
file "/system/build.prop" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("/system/build.prop", "7aaf71a86e547a831410c135070a74207d3e4b67", "30bcce162d9df0d85dc64fac97673d6442ac8515")
assert failed: apply_patch_check("/system/build.prop", "7aaf71a86e547a831410c135070a74207d3e4b67", "30bcce162d9df0d85dc64fac97673d6442ac8515")
E:Error executing updater binary in zip '/sdcard///FIND7WX_12_OTA_INT_009_patch_svn9441.zip'
E:Error installing zip file '/sdcard///FIND7WX_12_OTA_INT_009_patch_svn9441.zip'
Done processing script file
Click to expand...
Click to collapse
For additional info: I have rooted the Find 7a with the updated method here: http://forum.xda-developers.com/showthread.php?t=2739102. But newest superSu worked fine for me
Any other ideas what i could do?
dextructor said:
No!
If you use the latest official TWRP recovery you be able to flash oppo firmware. I tested with my x9077 and the latest firmwares, the international and chinese versions.
Click to expand...
Click to collapse
I'm assuming it's 2.7.1.2 right? I'm still on 2.7.1.0. Haven't tried 2.7.1.1 either.
Yes i tried 2.7.1.2.
I found a solution that worked for me.
After I backed up my actual phone I have installed per TWRP the full zip thats for download on Oppo News Page about the Find 7.
Sent from my X9006 using XDA Free mobile app
I keep getting an error message every time I try to update my nexus 7
i have picture of error message but wont let me post
imgur com/a/43Iwv
You're going to have to do better...
here's the log
I:command is: 'install'
I:value is: '/cache/df43279bcf6bb6a0ae403249c3e6f314d0a7eb77.signed-razor-KTU84L-from-KOT49H.df43279b.zip'
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
I:Trying to find zip '/cache/df43279bcf6bb6a0ae403249c3e6f314d0a7eb77.signed-razor-KTU84L-from-KOT49H.df43279b.zip' on '/data/media/0'...
I:Looking for zip at '/df43279bcf6bb6a0ae403249c3e6f314d0a7eb77.signed-razor-KTU84L-from-KOT49H.df43279b.zip'
I:Looking for zip at '/data/media/0/df43279bcf6bb6a0ae403249c3e6f314d0a7eb77.signed-razor-KTU84L-from-KOT49H.df43279b.zip'
Installing zip file '/cache/df43279bcf6bb6a0ae403249c3e6f314d0a7eb77.signed-razor-KTU84L-from-KOT49H.df43279b.zip'
Installing '/cache/df43279bcf6bb6a0ae403249c3e6f314d0a7eb77.signed-razor-KTU84L-from-KOT49H.df43279b.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
Verifying current system...
file "/system/framework/core.odex" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: "/system/framework/core.odex" has unexpected contents.
"/system/framework/core.odex" has unexpected contents.
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/cache/df43279bcf6bb6a0ae403249c3e6f314d0a7eb77.signed-razor-KTU84L-from-KOT49H.df43279b.zip'
E:Error installing zip file '/cache/df43279bcf6bb6a0ae403249c3e6f314d0a7eb77.signed-razor-KTU84L-from-KOT49H.df43279b.zip
Me Too
My Nexus 7 [2013] is not updating to KTU84L from KOT49H. The downloader complains that there is not enough space in /cache. The download is 77MB in size, my cache partition is 35M. I have over 10G of free space in /data and /sdcard. I think the download tool is broken.
damn i actually had the same problem i ended up just using the factory restore straight to the 4.4.4 image but hey the 5.0 image is out today ya can try to flash it to 5.0 the only problem i have is that i dont know how to set up the flash-all script for 5.0 ill post a link how to factory restore it to 4.4.4 if ya need it http://forum.xda-developers.com/showthread.php?t=2382051 just read through it the post have all the tools u need to dl for it
Hi all,
I need some help.
My wife have an Samsung i747 phone which she used to store there all the pictures of our boys from the past 2 years. She never backuped the pictures.
Starting two weeks ago the phone got stuck very often, and became very hot. Last week the phone didn't power on anymore.
I could enter to download mode, but didn't succeed to go Recovery mode except of few times (I know it sounds weird, but I try a lot.. most of the times the text "Recovery Booting" for one second, and than I got the "Samsung S III" logo and the device shut down..).
So if I understood right, the was soft brick.
The few times i succeeded enter recovery mode it always print errors of something like "e: mount /system | /data | /cache failed".
I saw this thread and decide to give it a chance.
I didn't know what is the version of the bootloader (or anything else... my wife neither) so I go on the 4.3 bootloader.
I flashed the twrp 2.6.3.0 recovery and I saw there in backup section that the data is about 12giga. I couldn't make any backup of anything. I tried to reset to factory settings (without wiping the user data) and it failed(I even tried to backup the recorvery and boot partition that weights 10 mb and it failed).
I tried to flash from my sd card the:
d2att_I747UCUEMJB_bootloader
d2att_I747UCUEMJB_modem
d2att_Kernel_Stock_init.d_4.3_MJB_v1.0
AT&T_I747UCUEMJB
and everything worked but the AT&T_I747UCUEMJB.zip .
I tried flash newer twrp version, at first 2.6.3.1 and lastly 2.8.7.0. In all the same result - I can't flash the AT&T_I747UCUEMJB.zip file. the error says something about the updater (I can't read the whole error, the screen cutting the line).
Still when I open the recovery it says it couldn't load /system /cache /data partitions. I tried to change the fs type, wiping the partition, formatting - but nothing worked.
Can any one help me get the pictures out? They mean a lot to us, except the pictures from the I747 we only have a few pictures from the last 2 years.
Thanks!
p.s
I thinks that this is the log from twrp when I tried to install the AT&T_ rom:
Code:
Installing '/external_sd/AT&T_I747UCUEMJB.zip'...
Checking for MD5 file...
I:Cannot find file /external_sd/AT&T_I747UCUEMJB.zip.md5
Skipping MD5 check: no MD5 file found.
I:Zip does not contain SELinux file_contexts file in its root.
Creating filesystem with parameters:
Size: 1572864000
Block size: 4096
Blocks per group: 32768
Inodes per group: 8000
Inode size: 256
Journal blocks: 6000
Label:
Blocks: 384000
Block groups: 12
Reserved block group size: 95
Created filesystem with 11/96000 inodes and 12609/384000 blocks
error: file_write: write: I/O error
E:Error executing updater binary in zip '/external_sd/AT&T_I747UCUEMJB.zip'
Error flashing zip '/external_sd/AT&T_I747UCUEMJB.zip'
Updating partition details...
I:Can't probe device /dev/block/mmcblk0p14
E:Unable to mount '/system'
I:Actual block device: '/dev/block/mmcblk0p14', current file system: 'ext4'
I:Can't probe device /dev/block/mmcblk0p17
E:Unable to mount '/cache'
I:Actual block device: '/dev/block/mmcblk0p17', current file system: 'ext4'
I:Set page: 'flash_done'
I:Set page: 'confirm_action'
I:Set page: 'action_page'
I:Can't probe device /dev/block/mmcblk0p17
E:Unable to mount '/cache'
I:Actual block device: '/dev/block/mmcblk0p17', current file system: 'ext4'
Updating partition details...
I:Can't probe device /dev/block/mmcblk0p14
E:Unable to mount '/system'
I:Actual block device: '/dev/block/mmcblk0p14', current file system: 'ext4'
I:Can't probe device /dev/block/mmcblk0p17
E:Unable to mount '/cache'
I:Actual block device: '/dev/block/mmcblk0p17', current file system: 'ext4'
I:Set page: 'action_complete'
Updating partition details...
I:Can't probe device /dev/block/mmcblk0p14
E:Unable to mount '/system'
I:Actual block device: '/dev/block/mmcblk0p14', current file system: 'ext4'
I:Can't probe device /dev/block/mmcblk0p17
E:Unable to mount '/cache'
I:Actual block device: '/dev/block/mmcblk0p17', current file system: 'ext4'
I:Set page: 'clear_vars'
I:Set page: 'flash_done'
I:Set page: 'rebootcheck'
I:Set page: 'confirm_action'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'wipe'
I:Set page: 'advancedwipe'
I:Set page: 'wipe'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'install'
I:Set page: 'flash_confirm'
I:Set page: 'flash_zip'
I:Set page: 'flash_zip'
Did you try mounting that data partition in TWRP? I assume you did and that didn't work for you.
You mentioned that you tried chnaging the fs, wiping, formatting. Which partitions are you referring to?
audit13 said:
Did you try mounting that data partition in TWRP? I assume you did and that didn't work for you.
You mentioned that you tried chnaging the fs, wiping, formatting. Which partitions are you referring to?
Click to expand...
Click to collapse
I tried to mount the partitions. It didn't work. In the Mount section of twrp when I clicking the system and cache partition nothing happens. And in the backup section it shows that the size of system and cache partitions is 0MB.
I tried to change the /system /cache partitions. I didn't try the /data partition because I'm afraid losing all my data.
I forgot to mention that right now, the only way I can boot to recovery and download mode is by the sd card with the debrick image.
Since you can boot with the debrick image, did you try reflashing a bootloader or modem to the phone?
Sounds like you have the same problem as this XDA member: http://forum.xda-developers.com/galaxy-s3-att/help/failed-to-mount-data-frozen-factory-t3181035
audit13 said:
Since you can boot with the debrick image, did you try reflashing a bootloader or modem to the phone?
Sounds like you have the same problem as this XDA member: http://forum.xda-developers.com/galaxy-s3-att/help/failed-to-mount-data-frozen-factory-t3181035
Click to expand...
Click to collapse
If I understand correctly, its not the same problem. He couldn't mount just the /data while I can't /data /system /system. Another differnce is that his problems occured after he flashed things, mine was with the original recovery, and I can't do a factory reset.
Please tell me if I'm wrong.
The other user could only boot his phone using a debrick image in the phone. Will your phone boot without the sdcard?
The other user had to flash a bootloader in order to boot without the sdcard in the phone.
audit13 said:
The other user could only boot his phone using a debrick image in the phone. Will your phone boot without the sdcard?
The other user had to flash a bootloader in order to boot without the sdcard in the phone.
Click to expand...
Click to collapse
I can't boot when the sdcard isn't there.
Should I try to flash another bootloader? If so, can you tell me what bootloader should I install.
The most important thing to me right now is to get my pictures back, so currently I don't care booting with the sd card. After I get my pictures I would like to make the phone work without the sd card.
Thanks!
Do you know which bootloader was on the phone before you started flashing bootloaders?
I am not sure if flashing a bootloader and recovery will get you access to the pictures. I have never experienced a bricked s3.
audit13 said:
Do you know which bootloader was on the phone before you started flashing bootloaders?
I am not sure if flashing a bootloader and recovery will get you access to the pictures. I have never experienced a bricked s3.
Click to expand...
Click to collapse
I don't know. But what I do know is that the first time I used the debrick sd card it shows in the download mode the "warranty bit: 0" that wasn't there before. The second time I powered on the device it shows that the warranty bit is 1.
If thats help somehow recognizing the bootloader version.
I flashed (via recovery) the bootloader maximum 2 time, and via Odin few times (every time I tried another version of the recovery..something like 5 times).
I've notice that if I trying to get into download mode and release the buttons fast, the next time the device booting its showing this screen:
And when I'm going into Recovery mode its showing this screen:
Before I did the debrick the screen I has is the first one.
I thinks the second one is the debrick, because it always shows the first image for 1-2 seconds and it is rebooting and shows the second picture.
The screen without twrp is the first screen. The second screen is how the phone would look with twrp.
The fact that the warranty bit exists in download mode means the phone has at least a 4.3 bootloader.
If the phone had a kit kat bootloader before you flashed anything, flashing the mjb bootloader is probably what bricked the phone.
Are you able to confirm which rom version was on the phone before you flashed anything? This will help determine which bootloader and modem should be flashed to the phone.
audit13 said:
The screen without twrp is the first screen. The second screen is how the phone would look with twrp.
The fact that the warranty bit exists in download mode means the phone has at least a 4.3 bootloader.
If the phone had a kit kat bootloader before you flashed anything, flashing the mjb bootloader is probably what bricked the phone.
Are you able to confirm which rom version was on the phone before you flashed anything? This will help determine which bootloader and modem should be flashed to the phone.
Click to expand...
Click to collapse
I didn't have the warranty bit in download mode before I used the debrick image, and I didn't flash anything before, the warranty bit appears only after I used the debrick image. So I guess I had the 4.1.2 bootloader (I remmeber that we were updating the phone once using Kies..about 2 years ago or something like that..).
I never flashed anything to this phone before the twrp last week after the brick happened. And My wife was using the Stock rom.
But 2 days ago when I tried following this thread I do flash (using twrp install section) a bootloader.(when the sd card inserted). I took the bootloader he recommended:
Use this bootloader for the AT&T i747 ONLY https://www.dropbox.com/s/vbyeorrxapwrots/d2att_I747UCUEMJB_bootloader.zip the one in the tread where I got mine hasn't been working so use this bootloader it is the same one just hosted by a different person.
Click to expand...
Click to collapse
Thanks for trying helping!
It's also possible that the internal memory in the phone is damaged. It does happen on occasion.
Sorry, but I am out of ideas at this point.
audit13 said:
It's also possible that the internal memory in the phone is damaged. It does happen on occasion.
Sorry, but I am out of ideas at this point.
Click to expand...
Click to collapse
I thought damaged memory is the case at first, but if so the twrp 2.6.X version wouldn't recognize that my data is about 12 giga.
How can I assure this is the case?
A couple of ideas that may be of some help.
If you can boot into TWRP again you can go to >> Advanced >> Terminal Command >> Select
and enter these commands to determine current installed bootloader and modem
Code:
getprop ro.bootloader
getprop | grep version.baseband
Also, IIRC, once you are booted into your recovery, TWRP, you should be able to remove the sdcard with the debrick image and replace it with a blank card. Then, from with the Advanced menu of TWRP can you use the File Manager to copy folders/directories.
dawgdoc said:
A couple of ideas that may be of some help.
If you can boot into TWRP again you can go to >> Advanced >> Terminal Command >> Select
and enter these commands to determine current installed bootloader and modem
Code:
getprop ro.bootloader
getprop | grep version.baseband
Also, IIRC, once you are booted into your recovery, TWRP, you should be able to remove the sdcard with the debrick image and replace it with a blank card. Then, from with the Advanced menu of TWRP can you use the File Manager to copy folders/directories.
Click to expand...
Click to collapse
getprop ro.bootloader returns I747UCUEMJB (I thinks this is because I flashed the bootloader in @theramsey3 thread when I tried to follow his instrucions.)
getprop | grep version.baseband returns nothing. I tried "getprop | grep baseband" and it returns 2 result :
[ro.baseband]: [msm]
[ro.boot.baseband]: [msm]
I already tried the File Manager option. There is nothing in /data and /sdcard directories.
Thanks!
Sorry I wasn't of more help.
i believe TWRP (at least in version 2.8.x.x and newer) it will connect to your pc as a media device, which (at least on my i747) includes both the internal sd card (including the part i imagine your worried about, pictures and videos) as well as the external storage
at which point you should be able to copy files from your phone to your pc
logoster said:
i believe TWRP (at least in version 2.8.x.x and newer) it will connect to your pc as a media device, which (at least on my i747) includes both the internal sd card (including the part i imagine your worried about, pictures and videos) as well as the external storage
at which point you should be able to copy files from your phone to your pc
Click to expand...
Click to collapse
I thinks it called MTP. I don't have the internal sd card. I have the external sd card only, so I can't copy my files.
Do you have any other idea?
Added the log of twrp if it will help somehow.
reading the log, it complains about not being able to mount the data, system, and cache partition
which to me reads as the phones internal storage is dead or almost dead, or heavily corrupted.
while i'm no expert, you may have to go to an actual expert to get the data recovered, because if recovery can't mount it then i don't really know how you could get any consumer hardware to do so
Ok, so I'm new here and I'm having problems updating my Mi5 32Gb to newest nightlies of Lineage OS 15.1
It all started in the beginning of May when I was having trouble with the 07.05 build (my Google account refused to work) and downgraded back to the latest April one. After the new build came out I've decided to update again multiple times but with no success.
Here's a raw piece of log for you guys:
I:Set page: 'install'
I:Set page: 'flash_confirm'
I:Set page: 'flash_zip'
Iperation_start: 'Flashing'
Installing zip file '/sdcard/lineage-15.1-20180528-nightly-gemini-signed.zip'
Checking for Digest file...
Skipping Digest check: no Digest file found
I:Update binary zip
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment not used in updater.
selinux_android_file_context: Error getting file context handle (No such file or directory)
Warning: No file_contextsscript aborted: assert failed: xiaomi.verify_modem("2018-04-20 15:21:31") == "1"
assert failed: xiaomi.verify_modem("2018-04-20 15:21:31") == "1"error: 25
Updater process ended with ERROR: 7
I:Install took 0 second(s).
Error installing zip file '/sdcard/lineage-15.1-20180528-nightly-gemini-signed.zip'
Updating partition details...
Iata backup size is 7575MB, free: 4786MB.
I:Unable to mount '/usb_otg'
I:Actual block device: '', current file system: 'vfat'
...done
I do have a basic understanding of what's written here and if I were to have enough time to look into it, maybe I would have solved it already, but something tells me it'd be better to seek guidance. Any help would be appreciated. Thanks in advance.
MiCrush said:
Ok, so I'm new here and I'm having problems updating my Mi5 32Gb to newest nightlies of Lineage OS 15.1...
Click to expand...
Click to collapse
I don't have this device but, your best bet is to post this question within the following Official LineageOS 15.1 thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3669247
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
I have tested 2 GSI's so far, phh's AOSP and AndyYan's LineageOS 19.1.
Everything works so far except:
MTP file transfer
Fingerprint reader
File encryption (GSIs don't boot if you dont disable encryption)
So, if you wanna install one, here's what I did:
Install Prove N's Unofficial TWRP and follow his guide. DONT INSTALL MAGISK, IT HAS THE IMEI PROBLEM AND ITS NOT TESTED WITH GSIs
Download your preferred GSI, I recommend lineage-19.1-20220320-UNOFFICIAL-arm64_bvS.img.xz, comes without GAPPS (Use bgS if you want em).
Extract it and rename the .img file to system.img
(Optional) Download this vendor.img, I made a treble overlay and added it to the image. The rom should be more stable and power management should be fixed with that. I still have to push the changes to github.
Download ChonDoe_Flasher.zip, it's a tool to flash dynamic partitions. It checks your storage for system.img and vendor.img.
Get a microSD card, and copy to the root of it the ChonDoe_Flasher.zip, system.img and vendor.img.
Boot to TWRP, and install the ChonDoe zip, wait till it finishes flashing.
Reboot to TWRP again, so it can mount the vendor partition again, go to the terminal and type multidisabler, so we remove encryption.
Format data, internal storage and reboot, you should be ready to go.
Settings in PHH Treble Settings
Go to Samsung features and check "Enable extended brightness range" and "Enable access to all cameras".
Go to Misc features and check "Use alternate way to detect headsets"
To get the display working at 90hzs go to "Force FPS" and check the option.
On camera check "Expose Aux cameras" and "Force Enable Camera2API HAL3" (In theory you should get better photos with that but I didn't go outside today lol)
For the lack of MTP file transfer, I'm using ADB instead of MTP with this tool for uploading and getting files from internal storage: Python ADB File Explorer. Suprisingly it's faster than MTP for some reason...
I know MTP can be fixed changing the kernel driver, I have compiled the kernel from @Prove N. , he had some USB fixes, but I don't know how to pack it for Samsung, It could be nice to have it for GSIs. If anyone wants to help me with these small issues it would be awesome.
Report bugs, workarounds and fixes here in this thread, let's try to make this phone usable!
I've recently bought this phone and installed LineageOS straight away. I used my alternative method without TWRP, by repacking super.img using my script, which I've modified to support SM-A325F. Too bad the fingerprint sensor does not work. Can anyone confirm it does not work regardless of on which Android version a GSI is based on?
I already have TWRP on my A32 and have Magisk. Followed the guide, unfortunately phone didn't boot up. Instead it reboots to recovery. The hereunder error appears while flashing.
Code:
PARTITIONS FLASHER
| Released at 2021, January 10
| Developed by ChonDoe
Archive: /external_sd/ChonDoe_Flasher.zip
inflating: /tmp/busybox-arm
Archive: /external_sd/ChonDoe_Flasher.zip
inflating: /tmp/e2fsck
Archive: /external_sd/ChonDoe_Flasher.zip
inflating: /tmp/installer.sh
Archive: /external_sd/ChonDoe_Flasher.zip
inflating: /tmp/resize2fs
ENVIRONMENT SETUP
| Unmount System
umount: can't unmount /system: Invalid argument
umount: can't unmount /system_root: Invalid argument
umount: can't unmount /system_ext: No such file or directory
umount: can't unmount /product: Invalid argument
umount: can't unmount /vendor: Invalid argument
| Detecting Partition Layout
| Dynamic partition detected
| System Block: /dev/block/dm-0
| Product Block: /dev/block/dm-2
| Vendor Block: /dev/block/dm-1
FLASHING SYSTEM IMAGE
Invalid sparse file format at header magic
Failed to read sparse file
703357+0 records in
703357+0 records out
2880950272 bytes (2.7GB) copied, 34.579540 seconds, 79.5MB/s
| System flashed as raw image
| Attempt to Resize Partition
e2fsck 1.45.6 (20-Mar-2020)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 3A: Optimizing directories
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/: ***** FILE SYSTEM WAS MODIFIED *****
/: 7386/7744 files (12.1% non-contiguous), 684040/692238 blocks
resize2fs 1.45.6 (20-Mar-2020)
Resizing the filesystem on /dev/block/dm-0 to 1217099 (4k) blocks.
The filesystem on /dev/block/dm-0 is now 1217099 (4k) blocks long.
| Done
FLASHING PRODUCT IMAGE
| Cant find product.img
FLASHING VENDOR IMAGE
| Vendor flashed as sparse image
| Attempt to Resize Partition
e2fsck 1.45.6 (20-Mar-2020)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Padding at end of inode bitmap is not set. Fix? yes
/dev/block/dm-1: ***** FILE SYSTEM WAS MODIFIED *****
/dev/block/dm-1: 1140/41760 files (0.0% non-contiguous), 124955/166988 blocks
resize2fs 1.45.6 (20-Mar-2020)
Resizing the filesystem on /dev/block/dm-1 to 185664 (4k) blocks.
The filesystem on /dev/block/dm-1 is now 185664 (4k) blocks long.
| Done
I:TWFunc::Set_Brightness: Setting brightness control to 5
| Enjoy
I:Updater process ended with RC=0
I:Install took 59 second(s).
E:Unable to unlock /dev/block/mmcblk0p42 for flashing: (null)
E:Unable to unlock /dev/block/mmcblk0p14 for flashing: (null)
E:Unable to unlock /dev/block/mmcblk0p18 for flashing: (null)
E:Unable to unlock /dev/block/mmcblk0p8 for flashing: (null)
E:Unable to unlock /dev/block/mmcblk0p11 for flashing: (null)
E:Unable to unlock /dev/block/mmcblk0p4 for flashing: (null)
E:Unable to unlock /dev/block/mmcblk0p15 for flashing: (null)
E:Unable to unlock /dev/block/mmcblk0boot0 for flashing: (null)
E:Unable to unlock /dev/block/mmcblk0p5 for flashing: (null)
E:Unable to unlock /dev/block/mmcblk0p7 for flashing: (null)
E:Unable to unlock /dev/block/mmcblk0p13 for flashing: (null)
E:Unable to unlock /dev/block/mmcblk0p10 for flashing: (null)
E:Unable to unlock /dev/block/mmcblk0p12 for flashing: (null)
E:Unable to unlock /dev/block/mmcblk0p9 for flashing: (null)
E:Unable to unlock /dev/block/mmcblk0 for flashing: (null)
E:Unable to unlock /dev/block/mmcblk0p6 for flashing: (null)
Updating partition details...
I:checking for twrp app
I:Data backup size is 0MB, free: 108145MB.
...done
I:Set page: 'flash_done'
I:TWFunc::Set_Brightness: Setting brightness control to 200
I:operation_end - status=0
I:TWFunc::Set_Brightness: Setting brightness control to 5
I:TWFunc::Set_Brightness: Setting brightness control to 0
I:TWFunc::Set_Brightness: Setting brightness control to 200
I:Set overlay: ''
I:Set page: 'clear_vars'
I:Set page: 'install'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'advanced'
I:Set page: 'copylog'
I:Set page: 'action_page'
I:operation_start: 'Copy Log'
uluruman said:
I've recently bought this phone and installed LineageOS straight away. I used my alternative method without TWRP, by repacking super.img using my script, which I've modified to support SM-A325F. Too bad the fingerprint sensor does not work. Can anyone confirm it does not work regardless of on which Android version a GSI is based on?
Click to expand...
Click to collapse
upload firmware plz
jasurshoir said:
upload firmware plz
Click to expand...
Click to collapse
Ok, I'll try not to mess it all up this time...
Here is the link to download: {Mod edit: Link removed. ufile.io is not accepted as file host on XDA}. That is super.img I've created using my script, it is packed into a tar archive and zipped to reduce the size for file sharing. It is specifically for SM-A325F, based on the NPB (Nepal/Butan) version of the firmware and contains LiR v3.16. After unzipping it is ready to be flashed using Odin into the AP slot over the stock NPB firmware. That means, you have to download and flash it first, then flash the super.img. After each flashing go straight into the Recovery mode and do factory reset, only then boot the system.
But that's not all, additionally you have to extract and flash optics.img from your regional firmware. Here is how to do it. Changing optics.img to your regional one is not compulsory but with the Nepalese/Butanese one you'll only have a few major cellular providers working. You can do it at any time after flashing the system, it does not require factory reset.
I have chosen the NPB stock firmware as the basis because after analyzing contents of other regional firmware I've found that it is probably the most non-bloated and privacy-respecting of all (the worst were Russian and European).
uluruman said:
Ok, I'll try not to mess it all up this time...
Here is the link to download: .... That is super.img I've created using my script, it is packed into a tar archive and zipped to reduce the size for file sharing. It is specifically for SM-A325F, based on the NPB (Nepal/Butan) version of the firmware and contains LiR v3.16. After unzipping it is ready to be flashed using Odin into the AP slot over the stock NPB firmware. That means, you have to download and flash it first, then flash the super.img. After each flashing go straight into the Recovery mode and do factory reset, only then boot the system.
But that's not all, additionally you have to extract and flash optics.img from your regional firmware. Here is how to do it. Changing optics.img to your regional one is not compulsory but with the Nepalese/Butanese one you'll only have a few major cellular providers working. You can do it at any time after flashing the system, it does not require factory reset.
I have chosen the NPB stock firmware as the basis because after analyzing contents of other regional firmware I've found that it is probably the most non-bloated and privacy-respecting of all (the worst were Russian and European).
Click to expand...
Click to collapse
all good please create one ui firmware
jasurshoir said:
all good please create one ui firmware
Click to expand...
Click to collapse
Do you really need it? First, OneUI is not to be trusted as it's proprietary and not fully open-source, second, the only GSI version of it I can find (repacked by erfanoabdi) is very old (2019).
uluruman said:
Do you really need it? First, OneUI is not to be trusted as it's proprietary and not fully open-source, second, the only GSI version of it I can find (repacked by erfanoabdi) is very old (2019).
Click to expand...
Click to collapse
Yes, I really need this one, I saw on the Internet nippon gsi one oh 4.0 downloaded installed but did not start
add please play servise
my log after install nippon gsi one ui 4.0 keep reboot
jasurshoir said:
Yes, I really need this one, I saw on the Internet nippon gsi one oh 4.0 downloaded installed but did not start
add please play servise
Click to expand...
Click to collapse
Ok, here it is: {Mod edit: Link removed. ufile.io is not accepted as file host on XDA}
It's the same Nippon GSI you mentioned, I've just repacked it into super.img. I don't know whether it's gonna work or not. Sometimes the system is just incompatible with the phone hardware or the kernel. All I can do is to repack it all, analyzing logs or tweaking the kernel is currently beyond my abilities.
Here is also the version of LiR with GApps (Google Play, etc.): {Mod edit: Link removed. ufile.io is not accepted as file host on XDA}
I've also updated my script, besides other improvements now it supports GZ-packed GSI images.
P.S.: I really don't recommend using any of the Google services. Don't let corporations gather your usage data. You bought the phone and from now on it should be all yours, with all of its data, like a PC in the good old days. You own your device, and nobody has the right to stick their nose into how you use your phone, gather any statistics and push you any ads. You always have a choice to turn down privacy-unfriendly stuff, the price of that "inconvenience" is actually ridiculous. From my point of view, there is simply no point in using non-stock systems if they are still littered with the privacy-unfriendly bloatware.
uluruman said:
Ok, here it is: ...
It's the same Nippon GSI you mentioned, I've just repacked it into super.img. I don't know whether it's gonna work or not. Sometimes the system is just incompatible with the phone hardware or the kernel. All I can do is to repack it all, analyzing logs or tweaking the kernel is currently beyond my abilities.
Here is also the version of LiR with GApps (Google Play, etc.): ...
I've also updated my script, besides other improvements now it supports GZ-packed GSI images.
P.S.: I really don't recommend using any of the Google services. Don't let corporations gather your usage data. You bought the phone and from now on it should be all yours, with all of its data, like a PC in the good old days. You own your device, and nobody has the right to stick their nose into how you use your phone, gather any statistics and push you any ads. You always have a choice to turn down privacy-unfriendly stuff, the price of that "inconvenience" is actually ridiculous. From my point of view, there is simply no point in using non-stock systems if they are still littered with the privacy-unfriendly bloatware.
Click to expand...
Click to collapse
thank you one ui not working play market worked youre new lineage firmware
does it also work with the PixelExpierence GSI?
Franzyy said:
does it also work with the PixelExpierence GSI?
Click to expand...
Click to collapse
Probably. Try it: {Mod edit: Link removed. ufile.io is not accepted as file host on XDA}
uluruman said:
Probably. Try it: ...
Click to expand...
Click to collapse
I have a question. Is this file linked above different than the PixelExpirence GSI from GitHub? Because the file is about 1GB larger than the "PixelExperience_arm64-ab-12.1-20220516-UNOFFICIAL.img.xz" from https://github.com/ponces/treble_build_pe/releases?page=1
Franzyy said:
I have a question. Is this file linked above different than the PixelExpirence GSI from GitHub? Because the file is about 1GB larger than the "PixelExperience_arm64-ab-12.1-20220516-UNOFFICIAL.img.xz" from https://github.com/ponces/treble_build_pe/releases?page=1
Click to expand...
Click to collapse
It is different, although based on it. It is the full Super partition, while "PixelExperience_arm64-ab-12.1-20220516-UNOFFICIAL.img" is only the System dynamic sub-partition within it. Besides System there are also Vendor, Product and ODM dynamic partitions included (taken directly from the NPB U2 stock firmware). Basically that's all the work my script is doing: repacking all the dynamic partitions inside super.img altogether, after which it contains another GSI but is still directly flashable with Odin.
There is an alternative way of installing a GSI, although it is far less straightforward. See this and this post. The latter deals with dynamic partitions, without which you cannot flash a GSI.
uluruman said:
It is different, although based on it. It is the full Super partition, while "PixelExperience_arm64-ab-12.1-20220516-UNOFFICIAL.img" is only the System dynamic sub-partition within it. Besides System there are also Vendor, Product and ODM dynamic partitions included (taken directly from the NPB U2 stock firmware). Basically that's all the work my script is doing: repacking all the dynamic partitions inside super.img altogether, after which it contains another GSI but is still directly flashable with Odin.
Click to expand...
Click to collapse
Ok thx for explaining it
I followed your guide so that i can get PixelExpirence on my A32 but my wired headphones doesnt work when plugged in, it just plays music on the speaker on the phone. Do you know a fix?
Franzyy said:
I followed your guide so that i can get PixelExpirence on my A32 but my wired headphones doesnt work when plugged in, it just plays music on the speaker on the phone. Do you know a fix?
Click to expand...
Click to collapse
Open "Phh Treble Settings" from the settings, then "Misc features" and check "Use alternative way to detect headsets" in the Audio section.
Franzyy said:
I followed your guide so that i can get PixelExpirence on my A32 but my wired headphones doesnt work when plugged in, it just plays music on the speaker on the phone. Do you know a fix?
Click to expand...
Click to collapse
how it works PE? I saw it is still in beta, does it works with 2 sim? thank you