Related
Hi
I have a Samsung Galaxy GT-I5801 with me for past couple of years.
Its current OS spec are:
Firmware version- 2.2
Baseband version- I5801DDJP2
Kernel version- 2.6.32.9 [email protected] #2
Build Number- FROYO.DDJP6
My phone has become kind of slow, like for even basic tasks like opening call log or messaging app, it takes good 10-15 seconds. Sometimes it even goes unresponsive when trying to end a call thus causing call to continue thus carrier balance reduction. There are no 3rd party apps installed on it. Even updating the pre-installed apps gives the message of memory being low.
Now my query is:
Will flashing it to a custom ROM will improve its working at least in the basic areas of call and texting?
If so, then which is the most suitable custom ROM?
Is it necessary to root the phone before flashing it ?
Which tool is best/easiest for said purposes?
Please go easy on me, I've been out of the IT and tech game since past 1 year and bit rusty on these things
RudraP said:
Will flashing it to a custom ROM will improve its working at least in the basic areas of call and texting?
If so, then which is the most suitable custom ROM?
Is it necessary to root the phone before flashing it ?
Which tool is best/easiest for said purposes?
Click to expand...
Click to collapse
I would say yes. I don't know what is causing the freezes, but (beside that this could also be a hardware problem) a custom ROM should fix that.
Any GB-based ROM should do a fine job. There are also Froyo-based ROMs for our device. The CM7.2 build by marcellusbe does a very good job.
Nope. If you flash via Odin (Flash-Software for Windows) you just need a usb-connection. If you flash it via recovery, you may need to flash a custom recovery first.
Derp - another proud Galaxy3 user :highfive:
DerpyDerp said:
I would say yes. I don't know what is causing the freezes, but (beside that this could also be a hardware problem) a custom ROM should fix that.
Any GB-based ROM should do a fine job. There are also Froyo-based ROMs for our device. The CM7.2 build by marcellusbe does a very good job.
Nope. If you flash via Odin (Flash-Software for Windows) you just need a usb-connection. If you flash it via recovery, you may need to flash a custom recovery first.
Derp - another proud Galaxy3 user :highfive:
Click to expand...
Click to collapse
I tried SuperOneClick but it failed to even detect my phone, let alone root. Tried rooting directly through phone by installing z4root on it. It too failed to root my device, just a blue screen saying "Running Exploit" with z4mod logo kept on displaying for 10-15 minutes, after which phone switched off itself. Had to power it back on myself. Tried it couple of times more but no success.
So now if I use Odin to directly flash the firmware to a modded one, would it work, considering the fact that the phone hasn't been rooted. More importantly, would it be wise to do so? Don't want to hard brick the device as its my backup device after my Xperia SP took a plunge in the water and now fails to even boot, just vibrates thrice and that's it.
Update:
Took a leap of faith with Odin and Cyanogen & now the device is rockin' like a grandma with a new hip replacement Lags no more, operation is smooth, but a 2nd minor problem has cropped up.
It now refuses to install any app from Play Store citing Insufficient Space. I changed the default installation space to external but still the problem persists.
Update 2:
For my above mentioned problem, looks like something to do with Gapps but I don't know what it is and what to do about it. Moreover as today I tried to make calls or send messages, I found out I'm unable to do so. The dialler dials after good 2-3 minutes of pressing/selecting the dial option for a number while message inbox is empty but it refuses the receive any sms citing Inbox is full. I thought just flashing the firmware should do the trick but looks like it just was the tip of the iceberg.
You can find the gapps (Google Apps - like Play Store, Gmail, ...) here:
http://goo.im/gapps/
Assuming you're on Gingerbread (CM 7.x) it's this package: http://goo.im/gapps/gapps-gb-20110828-signed.zip
Put this zip-file on your SD card, power off your phone and/or reboot to recovery. Navigate to "Select zip from sd card" -> select your gapps.zip and flash. Then "wipe cache" and "wipe dalvik cache" anywhere in the submenus Just to make sure the gapps get recognized correctly.
Another trick for expanding the internal storage is Link2SD. You need a 2-partition sd-card for this. 1. partition with FAT and 2. one with ext2/3/4
Link2SD will mount this second partition to the internal storage to expand your storage for apps and other system stuff.
You know... Getting the most of a half-dead low-end device needs a bit of geekiness
bad zip
Well I selected erase all data option in the phone which booted it into recovery mode. Here I cleared the cache and the user data. When I tried to install zip file from sd card it gave the following error message, "Can't open /sdcard/gapps-gb-20110828-signed.zip (bad) Installation Aborted"
What seems to be the problem now?
Update:
Tried again and this time it worked. Now everything is running fine. Thanks a ton for the help mate, can't express my gratitude through words.
I do want to ask one thing here.
If I install this, http://forum.xda-developers.com/showthread.php?t=1803180, will the JB experience be coupled with performance drop ?
Honestly Cyanogen has turned me into a junkie, now I want to try on the new but stable mods. Moreover as my Xperia SP is now out of warranty, I'm planning to get it fixed and then root and flash it too!
This is the link to the guide for flashing cm 12.1 on our Honor 3C - H30-U10. I don't own any of these builds or fixes, i just wanted to make this thread so that these things are easily available to people who CRAVE for Cyanogenmod on their honor 3c devices like me and ask for some help regarding the installation of apks. http://www.carbontesla.com/2015/08/install-honor-3c-cyanogenmod-12-1-lollipop-custom-rom-unofficial/
this is the link to the various builds of cm 12.1 https://cloud.mail.ru/public/3SBd/vVnPaUJ4C/ , however the one which has 20150923 in its name doesn't seem to boot up after flashing so i have flashed the one with 20150309 in its name which boots up fine and works pretty well.
Flash the Gapps also for the play store and google play services to work. Here is the link for it - http://www.carbontesla.com/download-google-apps-gapps/
Now, i tried PA Gapps mini and cyanogen 12.1 Gapps but they didnt work for me but AFH Gapps did work. You guys can try the former ones as there might have been some issue at my side.
The IMEI lost problem is there which can be solved by either restoring IMEI numbers using MTK or this zip http://1drv.ms/1FNtZUj. This may not be a permanent fix and the SIM not detected error may start showing up after a reboot but, it can be fixed by re-flashing this zip at recovery OR another rather stupid looking workound XD XD by turning on the airplane mode before rebooting and then switching it off after the boot up has finished.
I couldn't find the "Select default storage option" in the storage settings nor could i find the select preferred app installation location option in the Apps settings, so i found a workaround for linking the /sdcard in the root folder to /storage/sdcard1. Here is the script for it which has to be run everytime after booting the device in the terminal emulator:
1. first gain root privileges by entering su int the terminal.
2. type: mount -o bind /storage/sdcard1 /sdcard
That's it!! Now the default storage is your external sd card, one drawback of this is that you can't access the internal storage. If you want to access it, reboot your device and everything will revert back. if you want to set the default storage to the ext sd card, follow the above steps again.
THE PROBLEM: Apparently apks dont get installed most of the times even after enabling Unknown sources in the developer options, i don't know if this is the problem of google services or something, i would like someone to help out with this issue.
EDIT 1: The one which has 20150923 in its name boots up just fine, it needs more than one time dalvik cache deletion and factory resets.
Thanks for sharing ... some upgrade or new information in the last days...
This rom has several bugs. The only one version i still prefer to use is 151129 version
The latest 151202 doesn't booting after flash. Seems there's something wrong with boot.img
Anyway, i wish the developers will keep research and improve this rom to fix the bugs
Nothing new has happened mate
internauta2000 said:
Thanks for sharing ... some upgrade or new information in the last days...
Click to expand...
Click to collapse
No new updates have been release
I'll check the builds again and report back if i find any fixes for the bugs ASAP
Thanks for notifying!
Rayquaza said:
This rom has several bugs. The only one version i still prefer to use is 151129 version
The latest 151202 doesn't booting after flash. Seems there's something wrong with boot.img
Anyway, i wish the developers will keep research and improve this rom to fix the bugs
Click to expand...
Click to collapse
could you please provide the link for these builds? these couldn't be found on cloud.ru site
CM 12.1 ROM Development:
http://forum.xda-developers.com/android/development/rom-cyanogenmod-12-1-port-huawei-honor-t3307520
Great WORK!!
kernel.killer said:
CM 12.1 ROM Development:
http://forum.xda-developers.com/android/development/rom-cyanogenmod-12-1-port-huawei-honor-t3307520
Click to expand...
Click to collapse
Your Thread is amazing! Great work @kernel.killer !! Love your work! The ROM worked perfectly on my phone after flashing the modemFix zip
STOCK ANDROID 6.0 MARSHMALLOW ROM
FOR THE LENOVO TAB 3 8"/TB3-850F
TWRP FLASHABLE ZIP
FORCE ENCRYPTION & DM-VERITY DISABLED
DISCLAIMER: Your warranty will be voided by installing this ROM, unlocking your bootloader, or flashing a custom recovery. You hereby assume sole responsibility for any positive or negative consequences incurred by flashing this ROM. As always, flashing your Android device or otherwise altering its file system & partitions involves an inherent risk. I am not responsible for any devices which are bricked or otherwise rendered inoperable as a result of flashing this ROM. However, in such scenarios,
I will provide all support feasibly possible. Follow the simple instructions carefully and you should experience no adverse affects.
Lenovo's open source code for this ROM encompasses both the 850F & 850M variants of this tablet. Therefore, this ROM should be completely compatible with the TB3-850M as well.
NOTES:
This Stock Android 6.0 ROM is virtually unmodified. However, it should be noted that dm-verity (device mapping) and force encryption have been disabled via patched boot image. This is the most current stock OS for the Lenovo Tab 3 8"; therefore, no OTAs will need to be installed subsequent to flashing this ROM. In order to ensure that force encryption gets disabled, it is imperative that the /userdata (Data) partition is formatted in TWRP prior to Installation. Please carefully follow the below instructions.
For those members who want a pure stock experience, but also want root access of the stock OS, I'm currently compiling a deodexed & zipaligned version of this ROM, fully rooted with Magisk 14.0 & BusyBox binaries pre-installed.
SPECIFICATIONS:
Android Version: 6.0 Marshmallow
Build No: TB3-850F_S100031_171010_ROW
Kernel Version: 3.18.19
SDK Version: 23
Software Version: TB3-850F_160412
Build ID: MRA58K
Android Security Patch Level: 9/05/2017
Runtime Version: ART 2.1.0
Hardware Version: LenovoPad TB3-850F
Board Platform: MediaTek MT6735M
CPU: 64-Bit, Quad-Core Cortex A-53 - 1.0GHz
GPU: Mali T720 - 450MHz
RAM: 1GB
OS Build Date: 10/10/2017
Source Code: http://pcsupport.lenovo.com/us/en/products/tablets/a-series/tab3-8/downloads/ds112711
REQUIREMENTS:
1. Unlocked bootloader;
2. TWRP recovery;
This is a pure stock, unmodified, TWRP flashable Android 6.0 Marshmallow ROM for the Lenovo Tab 3 8". This ROM was compiled from the most recent stock /boot and /system images. However, as noted previously, the boot image has been unpacked, patched, and repacked in order to disable dm-verity and force encryption. Because raw firmware images were used in compiling this ROM, the file size is in excess of 1GB (approximately 1.35GB).
INSTRUCTIONS:
1. Download the ROM from the link provided and save it to your external micro SD card. Do not save to internal storage, as your /data partition will need to be formatted prior to installation;
2. Boot your tablet into TWRP recovery;
3. Wipe /system, /data, /cache & /Dalvik-ART cache. Also, select "Wipe", then "Format Data." This step is crucial to ensure disabling of force encryption. Please note that once installed, you may go to SETTINGS>>SECURITY and opt to encrypt the userdata on the tablet;
4. Select INSTALL, navigate to the location in which you saved the ROM zip file, and initiate installation. Flashing will complete in approximately 3 - 4 minutes;
5. Reboot system.
You should now have unmodified stock Android 6.0 installed on your Tab 3, as well as disabled dm-verity and disabled force encryption.
DOWNLOAD LINKS:
Stock Android 6.0 ROM --
TB3-850F_S100031_171010_ROW: https://drive.google.com/file/d/1iMf0Ns_XWGpYlNmXCvUsW_1DfaRMeIuO/view?usp=drivesdk
Stock Recovery Image: https://drive.google.com/file/d/1D6A7b080luzsSf0xLJSCqPBNeQLSWo94/view?usp=drivesdk
Unpatched Stock Boot Image: https://drive.google.com/file/d/1azgIrPbfJHBzZF9R4IUMxIGNga6vjipD/view?usp=drivesdk
Lenovo File Manager (APK): https://forum.xda-developers.com/android/general/app-lenovo-file-manager-lenovo-tab-3-8-t3706161
Lenovo Tab 3 8" User Guide --
TB3-850F & TB3-850M (English)(PDF): https://drive.google.com/file/d/18gCTfuZecJnlB0ddBIN02YPaDpuvmzov/view?usp=drivesdk
Older Build(s):
TB3-850F_S100030_161209_ROW: https://drive.google.com/file/d/0B1Sfod4HWfk2aTNtVmJHZGpWZEE/view?usp=drivesdk
BUGS: Please report any and all bugs, no matter how seemingly trivial or insignificant. For those members with the knowledge, please submit a proper bug report. If you are not sure how, simply provide as many facts & details as possible. If you are having problems with apps, please specify as to whether the app is from Google Play. Also, please DO NOT submit bug reports unless you are utilizing this ROM in its present form -- unmodified, pure stock. Custom kernels, mods & tweaks (e.g. Xposed framework) & any deviations from pure stock will make it futile to analyze bug reports. Instead, provide with detail the precise nature of the problem. If reporting a bug, please specify if you are rooted (systemless or system-mode) and/or have BusyBox binaries installed. Submit screenshots of bugs if possible.
Brilliant! Will download now and report back later. Thank you.
My custom ROM for this tablet should be coming out of the Android Kitchen later this evening. I've dubbed it Ethereal OS v1.1 [Android 6.0.1]. Extremely lightweight yet moderately feature packed.
MotoJunkie01 said:
My custom ROM for this tablet should be coming out of the Android Kitchen later this evening. I've dubbed it Ethereal OS v1.1 [Android 6.0.1]. Extremely lightweight yet moderately feature packed.
Click to expand...
Click to collapse
Nice!
After flashing the stock zip TWRP says unknown error. It booted up fine to where you login to your gmail and "bluetooth sharing has stopped working" pops up. Bluetooth can not be turned on within settings. I can not double swipe down to get to the notifications and the "Home" and "Recents" buttons do not seem to work although they both vibrate when pressed.
I will flash stock with SPFT and try your stock rom again.
stonedpsycho said:
Nice!
After flashing the stock zip TWRP says unknown error. It booted up fine to where you login to your gmail and "bluetooth sharing has stopped working" pops up. Bluetooth can not be turned on within settings. I can not double swipe down to get to the notifications and the "Home" and "Recents" buttons do not seem to work although they both vibrate when pressed.
I will flash stock with SPFT and try your stock rom again.
Click to expand...
Click to collapse
I got the same error with Bluetooth Share force closing two times at the setup screen. Probably a corruption issue during archiving the ROM. I'll do an md5 and archive the ROM again.
Seemed to work, however the loading images and screen is still lenovo. Also they lenovo apps are still there.
rongallant said:
Seemed to work, however the loading images and screen is still lenovo. Also they lenovo apps are still there.
Click to expand...
Click to collapse
This is not a custom ROM. This is pure stock. The Lenovo boot logo, boot animation & apps are supposed to be there. Like the title implies this an "Unmodified" stock ROM.
MotoJunkie01 said:
This is not a custom ROM. This is pure stock. The Lenovo boot logo, boot animation & apps are supposed to be there. Like the title implies this an "Unmodified" stock ROM.
Click to expand...
Click to collapse
My bad, understood.
On another note, I am finding it very buggy. The home and overview buttons do not work. They show you clicked it along with the haptic feedback, but nothing happens. The back button works and is the only way I know to get back to the home screen.
Also the tool panel you pull from the top stops working after a little while until I reboot. Then works for a little while.
The Play store downloads barely work. They show pending and nothing happens. I force quite, cleared the cache, disabled, reverted to the stock app and it works for a little bit. Then the other Play Store app comes back. Anyways, I am not complaining. I appreciate the work you put into this. It's awesome we get to do it at all. Just giving my feedback. P.S. It's a new TB3-850F.
rongallant said:
My bad, understood.
On another note, I am finding it very buggy. The home and overview buttons do not work. They show you clicked it along with the haptic feedback, but nothing happens. The back button works and is the only way I know to get back to the home screen.
Also the tool panel you pull from the top stops working after a little while until I reboot. Then works for a little while.
The Play store downloads barely work. They show pending and nothing happens. I force quite, cleared the cache, disabled, reverted to the stock app and it works for a little bit. Then the other Play Store app comes back. Anyways, I am not complaining. I appreciate the work you put into this. It's awesome we get to do it at all. Just giving my feedback. P.S. It's a new TB3-850F.
Click to expand...
Click to collapse
Yes. Very buggy indeed. I have determined that the bugs are due to corruption during the unpacking of the system image. I'm repacking the ROM now to alleviate the bugs. Thanks for your input...
I've managed to fix the major bugs reported upon initial install of the ROM -- Recents & Home Buttons, Quick Pulldown Menu, Google Framework bugs, New App Shortcut bugs, etc. Simply corruption during packing (archiving) the ROM zip. I will try my best to get a new build posted sometime today.
MotoJunkie01 said:
I've managed to fix the major bugs reported upon initial install of the ROM -- Recents & Home Buttons, Quick Pulldown Menu, Google Framework bugs, New App Shortcut bugs, etc. Simply corruption during packing (archiving) the ROM zip. I will try my best to get a new build posted sometime today.
Click to expand...
Click to collapse
Dear MotoJunkie
İs it possible to upload stock Fm Radio Aplication(offline radio) of Tab3 8? İn my Turkish model, theres no Fm radio aplication. I need it to use tablet in my car.
Thanks
MotoJunkie01 said:
I've managed to fix the major bugs reported upon initial install of the ROM -- Recents & Home Buttons, Quick Pulldown Menu, Google Framework bugs, New App Shortcut bugs, etc. Simply corruption during packing (archiving) the ROM zip. I will try my best to get a new build posted sometime today.
Click to expand...
Click to collapse
Did you get around to uploading it? I am unable to use the OTA update file. Says its missing 'android-info.txt'
Also, anyone care to point me to a way to get back to stock/unrooted?? Nooooo, I didn't backup my ROM first. That would have made way to much sense.
I've been out of commission, unfortunately, due to impending health issues once again. I know that hospital food sucks, that the pretty nurses don't typically put out easy, and that the hospital WiFi restrictions can easily be bypassed with a proxy server address. Lol. And that's all I've learned in the past ten days. Anyway, hope to be back in my daily routine in the next day or so and finishing some stuff up for this device.
Hi, is this thread alive? I'm interested in solution because i have about 60 tablets and need a solution to clone form one source tablet (config, apps, wlan, users, etc.) to other 59. I have tried adb backup --twrp and it went ok, but when i tried restore it gave errors with system partition and now i can only recover tablet with factory ROM from this thread (but it is buggy and cannot put it int to production like this). Is it possible to create system rom from other working tablet? Iwill be very pleased If You can write step by step, how to create zipped rom from working device so i can then upload it to share with others.
spiker_80 said:
Hi, is this thread alive? I'm interested in solution because i have about 60 tablets and need a solution to clone form one source tablet (config, apps, wlan, users, etc.) to other 59. I have tried adb backup --twrp and it went ok, but when i tried restore it gave errors with system partition and now i can only recover tablet with factory ROM from this thread (but it is buggy and cannot put it int to production like this). Is it possible to create system rom from other working tablet? Iwill be very pleased If You can write step by step, how to create zipped rom from working device so i can then upload it to share with others.
Click to expand...
Click to collapse
The thread is alive and I'm currently ironing out the errors on the posted ROM. The errors are due to a couple of permissions which are omitted on my updater-script file. I'll be posting an updated and hopefully error free release this week. Thanks for your interest and sorry for the delay in development. I've had a number of health issues of late and I'm now recovering.
Problem after wiping /system
Hi,
I´m new right here. I bought a new TB3-850F and wanted to flash the Original Stock Rom. After opening the Bootloader and booting into twrp like this way https://forum.xda-developers.com/android/general/guide-lenovo-tab3-8-tb3-850f-t3559786 I wiped the /data /System /dalvic and /Cache. After that I rebooted the system.
But it only shows after starting the Lenovo-Logo. No more booting. Because of this I can´t start the fastboot modus with Minimal ADB and Fastboot.
Is there some idea how I can boot into fastboot?
Many thanks for your help,
sailor1977
sailor1977 said:
Hi,
I´m new right here. I bought a new TB3-850F and wanted to flash the Original Stock Rom. After opening the Bootloader and booting into twrp like this way https://forum.xda-developers.com/android/general/guide-lenovo-tab3-8-tb3-850f-t3559786 I wiped the /data /System /dalvic and /Cache. After that I rebooted the system.
But it only shows after starting the Lenovo-Logo. No more booting. Because of this I can´t start the fastboot modus with Minimal ADB and Fastboot.
Is there some idea how I can boot into fastboot?
Many thanks for your help,
sailor1977
Click to expand...
Click to collapse
I´ve got a solution: After powering down, press power, wait 1 sec then hold both vol up & down also (all 3 Buttons) until vibrates. After starting in recovery Modus hold power button und press once the vol up.
With help of: https://forum.xda-developers.com/android/help/lenovo-tab3-8-2016-custom-recovery-t3483454 post #66
Ok. I've debugged the Stock 6.0 ROM in the OP. Fixed the Bluetooth force close issue at startup and the bugs involving the hardware buttons and the pull down menu. I'm traveling for work at the moment. Soon as I'm back home Monday I'll post the fixed build in the OP.
MotoJunkie01 said:
Ok. I've debugged the Stock 6.0 ROM in the OP. Fixed the Bluetooth force close issue at startup and the bugs involving the hardware buttons and the pull down menu. I'm traveling for work at the moment. Soon as I'm back home Monday I'll post the fixed build in the OP.
Click to expand...
Click to collapse
Cheers buddy. Good stuff ??
@Hemphiz, I hope all is well my friend. Something I wanted to get your input on. It seems that a few members have been experiencing boot loops and other problems after following the TWRP & Root thread I revised. I'm sort of at a brick wall in terms of figuring out what's going on. I'm thinking that maybe there are regional variants that are incompatible with the TWRP we use. Or, it could be one of those situations where instructions are not being closely followed. What are your thoughts? Thanks.
LineageOS 13 for Life One X2 Mini
This Rom was ported from the Unofficial LineageOS 13 for the Yureka Black. First I need to give credit for all the hard work the developers put into their Rom, I only modified it to work on the Blu Life One X2 Mini.
Note: Please remember I'm doing this on my own time and using my own money to cover expenses.
What Works:
(please let me know)
Camera
Fingerprint
SIM
Data
GPS
Audio
Video Playback
Sensors
Led
Not Working Yet:
(Please let me know)
FM Radio
Bluetooth
Latest Build: https://drive.google.com/open?id=0BzMHnGbQH3bheWVUNlFDNjljcEE
Builds: https://drive.google.com/drive/folders/0BzMHnGbQH3bhRXNUWi1jaGhDR3M?usp=sharing (list view recommended)
TWRP: https://drive.google.com/file/d/0BzMHnGbQH3bhTERvcGxlSkZFa2M/view?usp=sharing
Kernel:
Gapps: http://opengapps.org
Screenshots:
Changelog
Troubleshooting
Encryption Unsuccessful Screen:
Boot into TWRP and format Data (not wipe)
reserved 4
OK--it installs correctly, but after reboot it starts optimization & then screens up with encryption unsuccessful & wants to reset phone-goes to an open script to reformat/reset in TWRP--executes it & then reboots to the same again---this repeats as long as you allow it to. I tried installing twice-- the second time I wiped the phone completely---same result.
debianmain1 said:
OK--it installs correctly, but after reboot it starts optimization & then screens up with encryption unsuccessful & wants to reset phone-goes to an open script to reformat/reset in TWRP--executes it & then reboots to the same again---this repeats as long as you allow it to. I tried installing twice-- the second time I wiped the phone completely---same result.
Click to expand...
Click to collapse
Boot into TWRP and format Data (not wipe)
srgrusso said:
Boot into TWRP and format Data (not wipe)
Click to expand...
Click to collapse
Better choice , imho, would be to unpack the boot.img and change fstab to remove "forceencript"
edit:
sorry spoke too soon.
Just looked at fstab.qcom in boot.img and it is not set to "forceencrypt"
mrmazak said:
Better choice , imho, would be to unpack the boot.img and change fstab to remove "forceencript"
Click to expand...
Click to collapse
this is the current entry:
Code:
/dev/block/bootdevice/by-name/userdata /data ext4 nosuid,nodev,noatime,noauto_da_alloc wait,formattable,check,encryptable=footer;length=-16384
If I wanted to do that what would I change it too?
Thanks
OK--everything loaded & the phone booted normally. Wi-Fi is not working (deal-breaker for me--I use cellular data as little as possible--I have Wi-Fi everywhere I normally go.) Camera works-looks normal (using Google Camera)--works normally. Bluetooth is also not working.. (notice that Bluetooth Share has stopped). Screen & touch work normally. Right now I don't have cell service (that's the reason I use Wi-Fi quite a bit--all cell service is spotty where we live) & can't check cell data. If You could get the Wi-Fi to work, I could check quite a bit more......
More about the Wi-Fi: the MAC address looks like giberish---02:00:00:00:00:00
srgrusso said:
this is the current entry:
Code:
/dev/block/bootdevice/by-name/userdata /data ext4 nosuid,nodev,noatime,noauto_da_alloc wait,formattable,check,encryptable=footer;length=-16384
If I wanted to do that what would I change it too?
Thanks
Click to expand...
Click to collapse
I added an edit to my earlier post.
The way it is looks ok.
It can be encrypted, (encryptable=footer) but not being forced to be. (forceencrypt=)
The length and location of the encryption key would be important to get right, if force is used.
debianmain1 said:
OK--everything loaded & the phone booted normally. Wi-Fi is not working (deal-breaker for me--I use cellular data as little as possible--I have Wi-Fi everywhere I normally go.) Camera works-looks normal (using Google Camera)--works normally. Bluetooth is also not working.. (notice that Bluetooth Share has stopped). Screen & touch work normally. Right now I don't have cell service (that's the reason I use Wi-Fi quite a bit--all cell service is spotty where we live) & can't check cell data. If You could get the Wi-Fi to work, I could check quite a bit more......
More about the Wi-Fi: the MAC address looks like giberish---02:00:00:00:00:00
Click to expand...
Click to collapse
if your ready to do some more testing I should be able to get wifi working.
debianmain1 said:
OK--everything loaded & the phone booted normally. Wi-Fi is not working (deal-breaker for me--I use cellular data as little as possible--I have Wi-Fi everywhere I normally go.) Camera works-looks normal (using Google Camera)--works normally. Bluetooth is also not working.. (notice that Bluetooth Share has stopped). Screen & touch work normally. Right now I don't have cell service (that's the reason I use Wi-Fi quite a bit--all cell service is spotty where we live) & can't check cell data. If You could get the Wi-Fi to work, I could check quite a bit more......
More about the Wi-Fi: the MAC address looks like giberish---02:00:00:00:00:00
Click to expand...
Click to collapse
That type of address could be sign of either a corrupted NVRAM or incorrect radio firmware.
What do you have on the about screen for "baseband version"
and also on the about device/ status / IMEI information (do not list your numbers, just wheather or not they are there)
mrmazak said:
That type of address could be sign of either a corrupted NVRAM or incorrect radio firmware.
What do you have on the about screen for "baseband version"
and also on the about device/ status / IMEI information (do not list your numbers, just wheather or not they are there)
Click to expand...
Click to collapse
The rom is missing the kernel modules from the base rom. should be an easy fix. I already been through all this porting the same rom to th X2.
I might need to edit the boot image and build a script in bin to automaticly load the modules. I don't have a mini but as far as I can tell there is not much diffference from the X2.
srgrusso said:
The rom is missing the kernel modules from the base rom. should be an easy fix. I already been through all this porting the same rom to th X2.
I might need to edit the boot image and build a script in etc to automaticly load the modules. I don't have a mini but as far as I can tell there is not much diffference from the X2.
Click to expand...
Click to collapse
Sounds good---I need the phone for tomorrow, so I'm restoring it right now---will be ready to do more testing tomorrow night. As soon as I get working Wi-Fi I can get logcat up + the normal app load I use....then I could really test it---It looks real good so far.
mrmazak said:
That type of address could be sign of either a corrupted NVRAM or incorrect radio firmware.
What do you have on the about screen for "baseband version"
and also on the about device/ status / IMEI information (do not list your numbers, just wheather or not they are there)
Click to expand...
Click to collapse
This phone's kernel uses external modules, instead of built in like most kernels, odd choice by manufacture. system/lib/modules is missing, once the modules are added, and loaded wifi should work, just fine.
vampirefo said:
This phone's kernel uses external modules, instead of built in like most kernels, odd choice by manufacture. system/lib/modules is missing, once the modules are added, and loaded wifi should work, just fine.
Click to expand...
Click to collapse
So I would guess that will close the Wi-Fi & Bluetooth issues at the same time.
debianmain1 said:
Sounds good---I need the phone for tomorrow, so I'm restoring it right now---will be ready to do more testing tomorrow night. As soon as I get working Wi-Fi I can get logcat up + the normal app load I use....then I could really test it---It looks real good so far.
Click to expand...
Click to collapse
I have a new rom uploading now. It will be waiting for you when you are ready. Since you are using the stock rom could you please post the result of "lsmod" it will help me. Also after you boot the new rom could you please put the output of "dmesg" in a text file and post me a link or else just post it in pastbin. In order to get the adb shell working you'll need to change "the usb used for" from charging to file transfer.
Thanks
srgrusso said:
I have a new rom uploading now. It will be waiting for you when you are ready. Since you are using the stock rom could you please post the result of "lsmod" it will help me. Also after you boot the new rom could you please put the output of "dmesg" in a text file and post me a link or else just post it in pastbin. In order to get the adb shell working you'll need to change "the usb used for" from charging to file transfer.
Thanks
Click to expand...
Click to collapse
No problem---I also contacted the other guy that is interested in helping---should hear from him soon. Will download the new one & be ready for tomorrow.
Here is the new build. Hopefully it fixes Wifi.
https://drive.google.com/file/d/0BzMHnGbQH3bhenZNVE5MeEttVFk/view?usp=sharing
Unified support thread for Pie Xperia XZ ROMs
You can discuss the following here:
Unofficial OmniROM 9.0 for Xperia XZ
Project Treble for Xperia XZ
AOSP Nightly Pie builds for Xperia XZ
Please keep the development threads clean and help each other out in this thread instead.
Telegram Group for General Discussion
Reporting bugs
Important: Read the bug list before posting. Anyone can add bugs to the list, just follow the rules.
DO NOT REPORT ISSUES WITH GSIs! Ask the GSI maintainer to fix them!
I will repeat the rules again here:
Rules:
New bugs must include version where error popped up and which oem version you are using
Only reproducible errors
Should include adb logcat, we CANNOT help you otherwise! (linked in a pastebin service like https://del.dog)
Must include clear description what is wrong
If it is a visual/SystemUI bug, only report it here
If it is an internal bug(e.g. fingerprint crashes device), report it to the Sony bugtracker as well!
Always try to fix the bug yourself first! Then submit a pull request to Sony
Must search if error has already been reported (bug tracker, this document, dev buglist)
If you've reported the issue somewhere else already and just want to track it here as well, add a link
Before reporting a bug, always make sure to isolate it. That means, wipe everything, install only the ROM without GApps and Magisk and see if the problem still exists. Only then report the bug!
Reserved #2
Im a hour ago flashed an newest Omni build and its stucks on bootanimation ? I had flashed: OEM Tone V5, Omni 24-01-2019, Magisk 18.0 and Open Gapps Pico 27-01-2019
---------- Post added at 08:04 PM ---------- Previous post was at 07:13 PM ----------
Now i have the answer. With gapps is smthg not good for Omni. I used RR Treble with that and there it was working :/
How about camera? Still dark photos or maybe something change in New builds?
i just flashed aosp_f8331_2019-02-06-NIGHTLY.zip.
then... my telephone receiver and microphone not work (no voice)
delichik said:
i just flashed aosp_f8331_2019-02-06-NIGHTLY.zip.
then... my telephone receiver and microphone not work (no voice)
Click to expand...
Click to collapse
Post logs or we can't help you. Are you running GApps? Do you mean you can't call at all? Or just no sound? This level of information you're providing is useless for helping you.
Slawek1995 said:
How about camera? Still dark photos or maybe something change in New builds?
Click to expand...
Click to collapse
You can help out with the calibration of the RGBC-IR sensor(named "CASH"
Stick this into /vendor/etc/cash_expcol_calibration.xml https://git.ix5.org/felix/device-sony-kagura/commit/a0253f3de75c52bccb9275ee7eda6cd2f9db539c and tweak the values. You need to restart the CASH server via "stop cashsvr" and then "start cashsvr" after you've modified the values. You can then grep the logcat for "cash" and see the generated values.
The "clear" value is for brightness, you can then adjust the exposure and ISO for the individual steps.
local__hero said:
Post logs or we can't help you. Are you running GApps? Do you mean you can't call at all? Or just no sound? This level of information you're providing is useless for helping you.
You can help out with the calibration of the RGBC-IR sensor(named CASH
Stick this into /vendor/etc/cash_expcol_calibration.xml and tweak the values. You need to restart the CASH server via "stop cashsvr" and then "start cashsvr" after you've modified the values. You can then grep the logcat for "cash" and see the generated values.
The "clear" value is for brightness, you can then adjust the exposure and ISO for the individual steps.
Click to expand...
Click to collapse
oh sorry, i found it is my mistake.
i flashed the official ftf, then flash your rom. now its alright.
thanks for your work
I didn't try aosp roms since long time. Still front camera focus problems(stuck on macro)? Gcam mod works? If yes wich version is adviced? Thanks.
porting of xperia xz3 (pie)
why are developers not make porting of xperia xz3 (pie) to xperia xz dual and use it for stock and unlocked stock?
Which of the 3 versions is the most stable and could be the candidate to remove the official ROM? ... or would I have to wait a little longer? ... I'm tired of not receiving updates, and I get the feeling that the phone is getting slower
When headset connected and playing music (blackplayer) if a notification comes up music stops giving sound but playing. After trying opening volume up & down closing all applications it comes back. Same thing happens if a call comes in when listening music. Music stops but i can't hear any voice from call, doing some things and closing call waiting for the another or i call back it fixes.
Anyone having same problems?
Using oem5 f8331, feb 06 build android 9.0 from sx.ix5.org
RGBC-IR sensor corrects when? The camera quality is really bad
Hey guys!
Sorry if I write in the wrong place. But I flashed OmniROM 9.0 and have some problems:
- If I call they don't hear me and I don't hear them (Not even calling sounds, tried with 100% working Bluetooth headset too)
- Microphone not work in any apps
- Only the lower speaker works
- When phone turn on the first thing I see after boot animation is an error message; "There is an internal problem with your device" or something like this in my language
- IDK why but the phone slows down extremly for no reason sometimes. But the bigger plreblem is the call problem.
Xperia XZ Single SIM
Hello
I have problems with the call audio disappearing.
I installed the system and checked yesterday that everything worked, but for whatever reason today I have no sound during calls.
I have attached the dmesg and logcat Hello
I have problems with the call audio disappearing.
I installed the system and checked yesterday that everything worked, but for whatever reason today I have no sound during calls.
I have attached the dmesg and logcat on del.dog <slash> arepacivaf.coffeescript
(seems I cannot post links due to forum rules)
Based on the output from dmesg, it looks like there might be something SElinux related going on.
I have the same problem with or without bluetooth headset connected.
I am running the latest FTF for my region (192) and OEM version 6.
If you need more info or I should be posting this somewhere else, please point me in the right direction
Thank you
Based on the output from dmesg, it looks like there might be something SElinux related going on.
I have the same problem with or without bluetooth headset connected.
I am running the latest FTF for my region (192) and OEM version 6.
If you need more info or I should be posting this somewhere else, please point me in the right direction
Thank you
Okay... I installed latest rom, latest oem, the old (working) TWRP and...
It's okay now. Everything seems to work.
SoulJahN2 said:
When headset connected and playing music (blackplayer) if a notification comes up music stops giving sound but playing. After trying opening volume up & down closing all applications it comes back. Same thing happens if a call comes in when listening music. Music stops but i can't hear any voice from call, doing some things and closing call waiting for the another or i call back it fixes.
Anyone having same problems?
Using oem5 f8331, feb 06 build android 9.0 from sx.ix5.org
Click to expand...
Click to collapse
Please give us a clean log and file a bug report at the sonyxperiadev bug tracker.
Make a clean re-install without Magisk or GApps and get a logcat and dmesg from boot until your calling issue.
Botchcamp said:
I have problems with the call audio disappearing.
I installed the system and checked yesterday that everything worked, but for whatever reason today I have no sound during calls.
I am running the latest FTF for my region (192) and OEM version 6.
Click to expand...
Click to collapse
What ROM are you running? Which version? Did you wipe/format userdata before installing the ROM?
Botchcamp said:
I have attached the dmesg and logcat on del.dog/arepacivaf.coffeescript
Based on the output from dmesg, it looks like there might be something SElinux related going on.
I have the same problem with or without bluetooth headset connected.
Click to expand...
Click to collapse
It looks like you are running Magisk and GApps. Please clean-install without them and get us a clean log.
Then open an issue at the sonyxperiadev bug tracker.
xda is a horrible place to to actual development, so please try to follow the guides and report bugs in the appropriate places, we cannot monitor everything here.
Se Neo said:
why are developers not make porting of xperia xz3 (pie) to xperia xz dual and use it for stock and unlocked stock?
Click to expand...
Click to collapse
For a number of reasons, here are some examples:
Copyright. Sony software is copyrighted and if we "ported" it, we could get sued.
Different platforms: The Xperia XZ is based on the Snapdragon 820 chipset. The XZ3 is based on the SDM845 chipset. They have different CPU architectures and capabilities.
It's hard when you don't have the source. We compile everything from open-source projects here. If you try to port stuff from the XZ3, you have to decompile the binaries to make them work with the Xperia XZ.
Hello there, i have a problem here about installing aosp rom on my XZ F8831 phone, can i ask it here? So i followed everything on your page including latest tft, flashing oem, flashing dsp, but my phone stuck on white sony logo without installing magisk/gapps. When i try to reinstall it but with gapps, i got this message when i try to flash the gapps, "this gapps is for device that have 9.0 android, your device is 8.0" something like that, so i assume anything i do before is useless, because my phone still on 8.0. Please can someone help me? Im sorry for the bad english
Hey guys!
I have problem with Treble on XZ (Single SIM)
I want to try some interesting GSIs but I never able to make any of them work. I tried like 10 different GSIs already.
So if someone can help me telling what I do wrong and someone can help me to make even one GSI work I would be super happy.
So I started everything from the beggining so reflashing the stock rom with flashtool, then flash the modded TWRP oem-vendor and then flash AOSP treble.
Then wipe everything (I tried without wipe and wipe system too not just caches and data. Every combination)
Then "fastboot flash system gsi.img"
When done I turn on phone SONY logo then restart and loop
So I read need to fix dsp (I not really understand this part) but I don't know how to use the codes or if I use them I got errors (I will write down errors if need)
So I used this;
https://sx.ix5.org/files/builds/kagura/misc/dsp-label-fixer.zip
After I installed gsi I turn on phone in recovery mode then flash dsp-label-fixer.zip. Is this ok? Need to do after every single flash or not even need?
Or if I need to use the codes where to write to make it work?;
Code:
[COLOR="DimGray"]su
# It might be either /system/vendor/dsp or /vendor/dsp depending on your device
# Just try both until one succeeds
mount -o remount,rw /system/vendor/dsp
chcon -R u:object_r:adsprpcd_file:s0 /dsp[/COLOR]
When I ask help last time you I get an answer about selinux. I don't really know if it's help or not, but I downloaded permissiver and flashed it. Same question than with dsp. Need to flash every time or after every rom install and before boot it?
What can be wrong? Why I never make trough the SONY logo with GSIs?
I already isntalled OmniROM and Pie 9.0 rom without problem. Even Treble is boot but without GSI, after installing a GSI image bootloop.
I read a lot and watched videos but still the same problem.
I hope someone will help me, I want to learn but I don't know what I do wrong and what to learn exactly. ?
Sorry for a lot long questions and bad English and being dumb.
Thank you for the answer!
KikiGames