[oreo]XZ1C-drmfix-root-ricoff
Available for any version of the official 8.0 oreo
First you have twrp https://forum.xda-developers.com/xp...t/recovery-twrp-3-1-1-stock-security-t3706704
Be sure to use the zip I provided,Make sure your rom is clean.If you want wipe data,cache and dalvik, please execute it first.
1，flash drmpatch.zip
2，flash SuperSU.zip
3，flash RicOff.zip
4，reboot
Perfect, please enjoy.
download
https://mega.nz/#F!s8QlGD7S!cSlNJcZArwwdvZGGE5sVdA
drmfix.so/drm****.so thank @sToRm// :good:
The secd of 47.1.A.12.34 is the same as 47.1.A.8.49.
secd original file（G8441_47.1.A.8.49_CE） https://mega.nz/#!IpYg1Q4Q!ONXXqHoP6JkrFQ9jGUHMMXlzHcPAfog3ISrMgogO8go
modify
E803003206000014E8031F3204000014E807003202000014E8031E32
for
08008052060000140800805204000014080080520200001408008052
drmpatch.zip
Install XperiFIX
In C:\XperiFIX\DATA\XZP\G8142\Oreo2
Modify the update binary
ui_print "******************************"
ui_print "Sony XZ Premium *OREO* DRM restore by //sToRm"
ui_print "******************************"
change
ui_print "******************************"
ui_print "Sony XZ1/XZ1C *OREO* DRM restore by //sToRm"
ui_print "******************************"
/ system
change
/vendor
And replace secd
Click to expand...
Click to collapse
SuperSU.zip
Modify init.supersu.rc.24 and init.supersu.rc.24.bindsbin
on post-fs
exec u:r:supersu:s0 root root -- /sbin/fbe_bypass.sh
export LD_PRELOAD drmfix.so:drm****.so
#RIC disable
mount securityfs securityfs /sys/kernel/security nosuid nodev noexec
write /sys/kernel/security/sony_ric/enable 0
Click to expand...
Click to collapse
RicOff.zip
The status of SELinux changes to permissive
Click to expand...
Click to collapse
The original machao44 account is lost
I do not know how to misunderstand me
MODEDIT by @gregbradley English Translation added
English is not good, then I say Chinese well! ! Turns 19 meters high wall came to support you. .
英语不好是吧，那我说中文好了！！特意翻19米的高墙过来支持你的。。
XDA Rules https://forum.xda-developers.com/announcement.php?a=81
4. Use the English language.
We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator. You're free to include your original message in your own language, below the English translation. (This rule covers your posts, profile entries and signature).
4.使用英語。
我們知道，不同的國籍，不是每個人都說英語，但請嘗試。如果您真的無法用英文發帖，請使用在線翻譯。您可以自由地將您的原始信息以您自己的語言包含在英文翻譯下。 （此規則涵蓋您的帖子，個人資料條目和簽名）。
Click to expand...
Click to collapse
So this seems to be storm// 's OREO DRM Fix?
So just to clarify, what did you change in the DRM FIX code to get it working?
EDIT: (tested it)
Ok I am on 47.1.A.5.51 with SuperSU (already installed).
So I flashed DRM FIX and RIC-OFF, wiped dalvic cache and rebooted.
Tried to make some pictures as mentioned by " N1ghtr08d":
"with the stock camera it "begins" to take the photo, as in the icons disappear from the frame, but it never actually snaps the photo or saves it to the gallery. It just stays at that state of looking through the viewfinder with the camera icon to take the photo floating at the bottom but never actually takes the picture."
So do you have any infos about your firmware you have tested this code?
---------- Post added at 12:14 PM ---------- Previous post was at 11:48 AM ----------
Sry for doublepost!
Ok I figured it out: I had to use the SuperSU of your zip. Now it is working! Thanks!
What I did:
First unzipped busybox as mentioned here:
https://forum.xda-developers.com/xperia-xz1-compact/how-to/how-to-root-xperia-xz1-compact-t3712385
After that, I flashed all 3 zip files and rebooted.
Using the Sock camera, by taking the first 3 pictured it seemed that no pics were taken, but taking the 4.th picture suddenly all pictures are visible in album! So no green pics anymore!!!
aikon96 said:
So this seems to be storm// 's OREO DRM Fix?
So just to clarify, what did you change in the DRM FIX code to get it working?
EDIT: (tested it)
Ok I am on 47.1.A.5.51 with SuperSU (already installed).
So I flashed DRM FIX and RIC-OFF, wiped dalvic cache and rebooted.
Tried to make some pictures as mentioned by " N1ghtr08d":
"with the stock camera it "begins" to take the photo, as in the icons disappear from the frame, but it never actually snaps the photo or saves it to the gallery. It just stays at that state of looking through the viewfinder with the camera icon to take the photo floating at the bottom but never actually takes the picture."
So do you have any infos about your firmware you have tested this code?
Click to expand...
Click to collapse
Do as I write, do not do anything else.
My XZ1C succeeded（47.1.A.8.49）, my friend also succeeded（47.1.A.5.51）.
M-Rom said:
[oreo]XZ1C-drmfix-root-ricoff
Available for any version of the official 8.0 oreo. . . . . .. . . . . . .. . . . .
. . . . . . . . . .. drmfix.so/drm****.so thank @sToRm// :good:
Click to expand...
Click to collapse
I don´t get it.
According to your attached screenshot you got an unlockable bootloader so you still have locked bootloader and are not effected by the issue at all, are you??????
Are you wasting time?
MODEDIT By @gregbradley, English translation added
pergoteborg said:
I don´t get it.
According to your attached screenshot you got an unlockable bootloader so you still have locked bootloader and are not effected by the issue at all, are you??????
你在浪费时间吗？
Click to expand...
Click to collapse
drmfix causes rooting status to display No
This is great! Does this mean that LineageOS will have the same camera quality as stock, or does the DRMFix only work on unlocked-BL stock ROM?
NadavCE said:
This is great! Does this mean that LineageOS will have the same camera quality as stock, or does the DRMFix only work on unlocked-BL stock ROM?
Click to expand...
Click to collapse
Not applicable to LineageOS
M-Rom said:
Do as I write, do not do anything else.
My XZ1C succeeded（47.1.A.8.49）, my friend also succeeded（47.1.A.5.51）.
Click to expand...
Click to collapse
Did the TWRP you linked in 1st post work with 47.1.A.8.49 as it has December patch? [RECOVERY] TWRP 3.2.1 (Security Patch Level 2017-11-05)
M-Rom said:
Not applicable to LineageOS
Click to expand...
Click to collapse
Who created this fix? What has been patched in secd?
smorgar said:
Did the TWRP you linked in 1st post work with 47.1.A.8.49 as it has December patch? [RECOVERY] TWRP 3.2.1 (Security Patch Level 2017-11-05)
Click to expand...
Click to collapse
I am using twrp-3.2.1-1-lilac-patchlevel-2017-11-05.img and can only read SD.
modpunk said:
Who created this fix? What has been patched in secd?
Click to expand...
Click to collapse
drmfix.so/drm****.so is @ sToRm //
I modified secd
M-Rom said:
drmfix.so/drm****.so is @ sToRm //
I modified secd
Click to expand...
Click to collapse
12-29 13:43:45.860 1016 1016 E suntory_get_blob_type: SuntoryTee_VerifyBlob failed -6
12-29 13:43:45.860 1016 1016 E suntory_get_blobs_status: Suntory_PopulateBlobStatusList(): SuntoryTee_VerifyBlob Error
12-29 13:43:45.860 1016 1016 E suntory_get_blobs_status: Suntory_PopulateBlobStatusList(): Failed with result -1
12-29 13:43:45.860 1016 1016 E suntory_get_blobs_status: Suntory_GetAllBlobStatus failed with result = -1
12-29 13:43:45.860 1016 1016 E suntory_convert_all_blobs: Suntory_ConvertAllBlobs failed -1
12-29 13:43:45.860 1016 1016 E secd : secd_backend_credential_manager.cpp:99 Suntory_ConvertAllBlobs failed (1) with error -1
drm*.so is just for secd or also needed by other processes?
M-Rom said:
I am using twrp-3.2.1-1-lilac-patchlevel-2017-11-05.img and can only read SD.
Click to expand...
Click to collapse
I guess I'm missing something...
How can you flash the zips if you can only read?
modpunk said:
12-29 13:43:45.860 1016 1016 E suntory_get_blob_type: SuntoryTee_VerifyBlob failed -6
12-29 13:43:45.860 1016 1016 E suntory_get_blobs_status: Suntory_PopulateBlobStatusList(): SuntoryTee_VerifyBlob Error
12-29 13:43:45.860 1016 1016 E suntory_get_blobs_status: Suntory_PopulateBlobStatusList(): Failed with result -1
12-29 13:43:45.860 1016 1016 E suntory_get_blobs_status: Suntory_GetAllBlobStatus failed with result = -1
12-29 13:43:45.860 1016 1016 E suntory_convert_all_blobs: Suntory_ConvertAllBlobs failed -1
12-29 13:43:45.860 1016 1016 E secd : secd_backend_credential_manager.cpp:99 Suntory_ConvertAllBlobs failed (1) with error -1
drm*.so is just for secd or also needed by other processes?
Click to expand...
Click to collapse
Project Treble LOS15? That drmfix can be used. I think of it, sorry.
M-Rom said:
Project Treble LOS15? That drmfix can be used. I think of it, sorry.
Click to expand...
Click to collapse
There is no reason why it shouldn't work. The question is how this exactly works. I would prefer to not have a global LD_PRELOAD but just have it for the service. So does only secd need the drm*.so or do other need it too?
For which firmware version exactly is this? Allways thought that the drm fix has do been made for every firmware new?
Edit: Works fine with 47.1.A.5.51
M-Rom said:
[oreo]XZ1C-drmfix-root-ricoff
Available for any version of the official 8.0 oreo
First you have twrp https://forum.xda-developers.com/xp...t/recovery-twrp-3-1-1-stock-security-t3706704
Be sure to use the zip I provided,Make sure your rom is clean.If you want wipe data,cache and dalvik, please execute it first.
1，flash drmpatch.zip
2，flash SuperSU.zip
3，flash RicOff.zip
4，reboot
Perfect, please enjoy.
download
https://mega.nz/#F!s8QlGD7S!cSlNJcZArwwdvZGGE5sVdA
drmfix.so/drm****.so thank @sToRm// :good:
Click to expand...
Click to collapse
modpunk said:
There is no reason why it shouldn't work. The question is how this exactly works. I would prefer to not have a global LD_PRELOAD but just have it for the service. So does only secd need the drm*.so or do other need it too?
Click to expand...
Click to collapse
I got it working on LineageOS.
I wouldn't really recommond flashing this until M-Rom fixed his stuff. It turns off SELinux so your device is pretty unprotected. The init file needs to be modified and SELinux rules added for init.
modpunk said:
I got it working on LineageOS.
I wouldn't really recommond flashing this until M-Rom fixed his stuff. It turns off SELinux so your device is pretty unprotected. The init file needs to be modified and SELinux rules added for init.
Click to expand...
Click to collapse
First off, great news! Second - is SELinux active on LOS w/ the DRM fix applied?
NadavCE said:
First off, great news! Second - is SELinux active on LOS w/ the DRM fix applied?
Click to expand...
Click to collapse
I've just got it working with SELinux in Enforcing mode. The same would be possible for stock if you set the LD_PRELOAD in init.secd.rc and allow noatsecure for secd.
Related
Basically, as we all know there is a delay when turning on the screen. I have been looking through various kernel files and trying to find the source of the problem. and I believe that I have found part of the problem!
The first errors that I found happened each time the screen was turned on, in the log it showed....
[ERROR] msm_i2c msm_i2c.0: error, status 63c8 (5C)
[ERROR] msm_i2c msm_i2c.0: Error during data xfer (-5) (5C)
[ERROR] msm_i2c msm_i2c.0: error, status e3c8 (34)
[ERROR] msm_i2c msm_i2c.0: Error during data xfer (-5) (34)
This lead me to believe that it was an issue with the msm files in the kernel...
I then found two of the errors in a file I found on the HD2 Kernel GitHub... the link to the file is also below....
https://github.com/charansingh/cm-kernel/blob/master/drivers/i2c/busses/i2c-msm.c
Code:
if (ret < 0) {
dev_err(dev->dev, "Error during data xfer (%d) @%02X\n", ret, msgs->addr);
msm_i2c_recover_bus_busy(dev);
}
Now I have started C robotics programming quite recently so I was hoping that it would help me here! This loop obviously checks if the variable ret is < 0 and if it is it will display an error message! Now earlier in the code ret was set using
ret = msm_i2c_poll_notbusy(dev, 1);
This led me onto the function
msm_i2c_poll_notbusy....
Code:
msm_i2c_poll_notbusy(struct msm_i2c_dev *dev, int warn)
{
uint32_t retries = 0;
while (retries != 200) {
uint32_t status = readl(dev->base + I2C_STATUS);
if (!(status & I2C_STATUS_BUS_ACTIVE)) {
if (retries && warn)
dev_warn(dev->dev,
"Warning bus was busy (%d)\n", retries);
return 0;
}
if (retries++ > 100)
usleep_range(100, 200);
}
dev_err(dev->dev, "Error waiting for notbusy (%d)\n", warn);
return -ETIMEDOUT;
}
As far as I can see, with no kernel programming history in my life, it sets the unsigned integer retries to 0, then starts a while loop testing
readl(dev->base + I2C_STATUS)& I2C_STATUS_BUS_ACTIVE
If the result of this is false it will return that the bus was busy for so many tries, it then exits out of the while loop returning control to the rest of the function...
otherwise ( in our case ) it will increase the variable retries by one and if there have been more than 100 retries it will have a 10 millisecond delay before returning control back to the top of the while loop. After 200 retries the while loop is no longer valid and then it will exit...
The cause for the around 2 second delay is partially due to the phone waiting until this loop has finished before it has turned the screen fully on! the 100 tries of the 10 millisecond delay equates for 1 second of the delay, so if we could fix the loop problem this WILL increase the speed at which the screen turns on... the other error is caused by
Code:
if (status & I2C_STATUS_ERROR_MASK)
goto out_err;
out_err:
dev_err(dev->dev, "error, status %x (%02X)\n", status, dev->msg->addr);
dev->ret = -EIO;
I do not believe that this error is causing a slowdown but they are related.
The problem always involves the variable status so this probably gives a good idea that whatever sets status must be incorrect...
Anyhow I have never touched kernel scripting in my life, I am 15, so I may be completely wrong, but from what I can see I hope that I am at least partially right!
Wow! Good stuff!
Wow nice find, perhaps you should talk to Tytung & Rafpigna about this as they are the most active kernel chefs @ HD2
patensas said:
Wow nice find, perhaps you should talk to Tytung & Rafpigna about this as they are the most active kernel chefs @ HD2
Click to expand...
Click to collapse
Thanks, I have now contacted them and am awaiting a reply
Kernel source code related to msm_i2c is done by the great dev Cotulla. (and maybe other devs)
I don't participate in his work.
And you're linking to a non-working kernel git in your first post.
but tytung please try to look into this ?
because this issue is really annoying and I dont think cotulla would mind if you do some modifications to his great work ?
Nice! now the only thing left to do is to fix it =))
Farrrk now what....??
-Wrong thread... sorry.
Well, I'm waiting for screen delay issue to be fixed since I installed MAGLDR on my HD2. So it will be just great.
What if just remove this loop and sleeps and recompile kernel? Madness? THIS! IS! SPARTA!
Great found kid!! We have great hope on this!
Hope it gets fixed soon...
I didn't understand anything you just said but .... This is great! And your only 15? That's amazing.
Hope we can fix this problem.
Sent from my HTC HD2 using XDA Premium App
nice work. especially if you are 15.
i would be so happy without the wakeup lag.. >.<
Hah ! That reminds me of an old trick to enable hackintoshes to use USB2...
The PC bios never gave back the bus ownership. So correctly programmed software could not use it.
The fix was to take bus ownership without asking "please".
Here it might be the same idea: just ignore (or need to call msm_i2c_recover_bus_busy earlier)
Once back home, if my kids give me spare time, I'll try to setup a compilation environment and give it a try.
john_duff said:
Hah ! That reminds me of an old trick to enable hackintoshes to use USB2...
The PC bios never gave back the bus ownership. So correctly programmed software could not use it.
The fix was to take bus ownership without asking "please".
Here it might be the same idea: just ignore (or need to call msm_i2c_recover_bus_busy earlier)
Once back home, if my kids give me spare time, I'll try to setup a compilation environment and give it a try.
Click to expand...
Click to collapse
Good idea, im sure that calling it earler and avoiding the loop will reduce the delay, after that is done we need to find a 'clean' hack as calling msm_i2c_recover_bus_busy would probably still add a delay, albeit not as much as if we just left it Good luck in your testing...
You guys speak like you've found the solution lol =D
Well not tonight... bad news came, I have to fix the dishwasher first.
I'll keep you informed.
john_duff said:
Well not tonight... bad news came, I have to fix the dishwasher first.
I'll keep you informed.
Click to expand...
Click to collapse
Hey can the dishwasher remove the screen delay? NO!
only joking ! Im just so excited for this !
white-energy said:
You guys speak like you've found the solution lol =D
Click to expand...
Click to collapse
ahah finding a problem isnt that hard but finding the solution is harder we will probably need some help from experienced kernel coders to help fix it properly
speedyracer5 said:
ahah finding a problem isnt that hard but finding the solution is harder we will probably need some help from experienced kernel coders to help fix it properly
Click to expand...
Click to collapse
Why are you using charansingh's HD2 Kernel GitHub to see the code? Just guessing, it may have .37 kernel code on which work is still going on as its still buggy...
Is there a similar error tytung or Rafpigna or ACA's kernel's git also?
speedyracer5 said:
[ERROR] msm_i2c msm_i2c.0: error, status 63c8 (5C)
[ERROR] msm_i2c msm_i2c.0: Error during data xfer (-5) (5C)
[ERROR] msm_i2c msm_i2c.0: error, status e3c8 (34)
[ERROR] msm_i2c msm_i2c.0: Error during data xfer (-5) (34)
Click to expand...
Click to collapse
Well, I can't argue with that.... I can't understand it either ..
Sounds like you did A tremendous piece of detective work. Nice one.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am going to fill this op with Questions and answers from all devices supported by Team Horizon. Please keep the respect and KEEP ALL NON DEVELOPMENT DISCUSSION HERE OR OUR
GOOGLE PLUS PAGE
Click to expand...
Click to collapse
.
Click to expand...
Click to collapse
Q. I came from 4.1.2 and I flashed your 4.2.1 and I can't access my files now?
A. Well this is because after the 4.2.1 update Google implemented a feature with in its ROM to allow for the use to apply user specific accounts. I suggest reflashing a 4.1.2 ROM, Then mount the phone once booted, Take all of the information you choose to keep and place it on your desktop, Once complete then reboot the phone into recovery and wipe the rm and reflash 4.2.1 once you have flashed rom and gapps, Before you leave recovery wipe the sd card. Once phone reboots then simply replace the information you placed on your desktop to its corresponding folder.
Click to expand...
Click to collapse
Q. my wifi is always on when in standby?
A.Disable wifi optimization, And avoid poor connections in wifi advanced options.. If you have Franco kernel, wifi fast pm helps too
Click to expand...
Click to collapse
Q. HELP I don't have a rom on my SD card and I am stuck in a boot loop what do I do?
A. You need to make sure you have a working adb setup along with all proper fastboot and device drivers installed. Place the rom you wish to flash in the root of the adb folder.
Make sure phone is in recovery mode and that it is plugged into the computer.
Open a command prompt and cd to the directory of the adb folder. ( or simply hold the shift key and right click your adb folder and choose to open command windows here)
now type: adb push (rom.zip) /sdcard/ (replace the (rom.zip) with the entire name of the rom.zip.)
Click to expand...
Click to collapse
Q. How come fast charge is not working or its enabled but not working?
A. Answer is simple, The roms stock kernel doesn't allow for fast charge. you may simply flash Franco kernel and or any other 4.2.1 kernel that supports to to gain functionality.
Click to expand...
Click to collapse
Q. Can I dirty flash (flash ROM without wipe)?
A Yes you may flash the ROM without wiping. YOU WILL HAVE TO REFLASH GAPPS. We don't recommend doing this but if you are pressed for time or its just too difficult then have at it. We will not support complaints from those that choose to go this route.
Click to expand...
Click to collapse
Warez Removed
Q. I have downloaded the ROM but it wont boot?
A. Please make sure you are downloading the correct ROM and completely wiping before flashing!
Crespo- http://d-h.st/users/iceandfire/?fld_id=9532#files
Grouper- http://d-h.st/users/iceandfire/?fld_id=8701#files
Maguro- http://d-h.st/users/iceandfire/?fld_id=8699#files
Mako- http://d-h.st/users/iceandfire/?fld_id=9438#files
Toro- http://d-h.st/users/iceandfire/?fld_id=8700#files
Toro Plus- http://d-h.st/users/iceandfire/?fld_id=9002#files
Click to expand...
Click to collapse
Q. Somebody know, how to disable waking up phone by pressing volume button?I dont like this feature.
A. Menu>settings>display>enable then disable the volume key MOD
Click to expand...
Click to collapse
Q. Where are my Chrono settings for weather and clock?
A. Menu>System Settings>Display>Clock widget
Click to expand...
Click to collapse
Q. Are the round widgets shown in the OP contained in the ROM? If not, are they available anywhere? Also, I cannot for the life of me figure out how to put a lockscreen widget. When I go into the Chronus settings, there are settings for the clock, weather and calendar widgets, but I can only add the clock widget to my device.
A. OK the widget is not included but called one more clock widget. To apply the clock. Lock the screen then place your finger on the clock and slide down till you reach the lock icon or the white outline is the write screen amd let go. Then long press the clock ad delete it. Then click the add widget . After you enabled everything in display then go to chrono in the options onthe lockscreen (the + sign from earlier) and add it. To add muliple widgets then slide down on clock to fill screen then swipe left or right.
Click to expand...
Click to collapse
Q. What is fast charge? what does it do for me? How do I get it to work?
A.
Fast charge is a option baked into the kernel that doesn't allow the phone to be mounted to the pc.
Keeps computer from mounting your sd card everytime its plugged in.
You need to install a kernel that supports it. Stock XennonHD doesn't allow for this. I suggest using Franco Kernel. found here: http://forum.xda-developers.com/showthread.php?t=1367341
Click to expand...
Click to collapse
Q. What gapps do i install on this rom? I installed the gapps from ice not all my apps are there?
A.
Download these gapps: http://goo.im/gapps/gapps-jb-20121212-signed.zip
Because all of the apps missing can be manually installed from the market. He did this to lighten the download.
Click to expand...
Click to collapse
Q. How to create a log cat
A. the code for logcat to output to a file is
adb logcat > name of problem.txt
you can also do
Click to expand...
Click to collapse
adb logcat -f name of problem.txt
how I prefer to do it is this way
Click to expand...
Click to collapse
:
adb logcat -v long > name of problem.txt
with the -v flag & the long argument, it changes output to long style, which means every line of logcat will be on its own line (makes it a little neater, imo)
Note: When outputting to a file, you will see a newline, but nothing printed, this is normal. To stop logcat from writting to a file, you need to press ctrl+c.
Click to expand...
Click to collapse
Here's where using logcat (via adb makes life really easy)
Lets say you find a problem you're having after looking at a logcat.
For example:
When I was trying to use a different ramdisk, wifi wouldn't work so I got a logcat that's almost 1300 lines long (a lot of stuff happens in the background)
So if you are searching for an error in the logcat file (it's always e/ for error, f/ for fatal. Those are the two main things that will break a system.)
D/dalvikvm( 871): GC_CONCURRENT freed 472K, 6% free 10224K/10823K, paused 1ms+6ms
V/AmazonAppstore.DiskInspectorServiceImpl( 871): Available blocks: 21981, Block size: 4096, Free: 90034176, Threshold: 5242880, withinThreshold? true
D/AmazonAppstore.UpdateService( 871): Received action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
W/AmazonAppstore.UpdateService( 871): Confused about why I'm running with this intent action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
D/dalvikvm( 890): GC_CONCURRENT freed 175K, 4% free 9375K/9671K, paused 2ms+3ms
V/AmazonAppstore.ReferenceCounter( 871): Reference (MASLoggerDB) count has gone to 0. Closing referenced object.
E/WifiStateMachine( 203): Failed to reload STA firmware java.lang.IllegalStateException: Error communicating to native daemon
V/AmazonAppstore.UpdateService( 871): runUpdateCommand doInBackground started.
V/AmazonAppstore.UpdateService( 871): Running UpdateCommand: digitalLocker
V/AmazonAppstore.UpdateCommand( 871): Not updating key: digitalLocker from: 1334228488057
V/AmazonAppstore.UpdateService( 871): Finished UpdateCommand: digitalLocker
V/AmazonAppstore.UpdateService( 871): Running UpdateCommand: serviceConfig
V/AmazonAppstore.MASLoggerDB( 871): performLogMetric: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
V/AmazonAppstore.MASLoggerDB( 871): onBackgroundTaskSucceeded: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
W/CommandListener( 118): Failed to retrieve HW addr for eth0 (No such device)
D/CommandListener( 118): Setting iface cfg
D/NetworkManagementService( 203): rsp
D/NetworkManagementService( 203): flags
E/WifiStateMachine( 203): Unable to change interface settings: java.lang.IllegalStateException: Unable to communicate with native daemon to interface setcfg - com.android.server.NativeDaemonConnectorException: Cmd {interface setcfg eth0 0.0.0.0 0 [down]} failed with code 400 : {Failed to set address (No such device)}
W/PackageParser( 203): Unknown element under : supports-screen at /mnt/asec/com.android.aldiko-1/pkg.apk Binary XML file line #16
D/wpa_supplicant( 930): wpa_supplicant v0.8.x
D/wpa_supplicant( 930): random: Trying to read entropy from /dev/random
D/wpa_supplicant( 930): Initializing interface 'eth0' conf '/data/misc/wifi/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
D/wpa_supplicant( 930): Configuration file '/data/misc/wifi/wpa_supplicant.conf' -> '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 930): Reading configuration file '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 930): ctrl_interface='eth0'
D/wpa_supplicant( 930): update_config=1
D/wpa_supplicant( 930): Line: 4 - start of a new network block
D/wpa_supplicant( 930): key_mgmt: 0x4
(mind you, that's 29 lines out of 1300ish, just for example)
Click to expand...
Click to collapse
I then could do the following with logcat:
adb logcat WifiStateMachine:E *:S -v long > name of problem.txt
and this will only print out any errors associated with WifiStateMachine, and anything which is fatal, which makes it about a million times easier to figure out what's going on!
Click to expand...
Click to collapse
In WifiStateMachine:E, the :E = to look for Errors, the full list of options is as follows:
V — Verbose (lowest priority)
D — Debug
I — Info (default priority)
W — Warning
E — Error
F — Fatal
S — Silent (highest priority, on which nothing is ever printed)
You can replace the :E with any other letter from above to get more info.
In order to filter out anything other than what you are looking for (in this case, WifiStateMachine) you must put a *:S after your last command (i.e. WifiStateMachine:E ThemeChoose:V ... ... AndroidRuntime:E *:S)
Click to expand...
Click to collapse
Q. I am in the download section but what rom is for my device?
A.
Crespo- nexus S
Grouper- Nexus 7
Maguro- gsm galaxy nexus t-mobile
Mako- galaxy nexus 4
Toro- Galaxy nexus Verizon Wireless
Toro Plus- sprint galaxy nexus
Click to expand...
Click to collapse
Click to expand...
Click to collapse
==================================================
Important please read
I. Appreciation
There are many ways to show your support to us. You can:
Press the "Thanks" button.
Hit the donation button and help support the team
Wear our specially prepared banner
Share your opinion about my work and write some feedback in our threads.
Advertise our work to your friends, family, anyone who owns this device.
Rate our threads with 5 stars.
We appreciate all the support you give us, but we don't expect anything
Click to expand...
Click to collapse
II. Sharing
XDA-Developers.com is all about sharing. If you would like to use any part of our work, please feel free to do so but remember to do the following beforehand:
Inform - Please send us a PM or email telling us
Permission - Please, if you do not have permission from us, don't use it. Most of the time, we will allow you to, but if you don't get our permission first, we will report.
Credits - No one wants their work stolen. Please remember to give proper credits when using our work.
Click to expand...
Click to collapse
:
III. Support
If you have any issues or questions, please feel free to post them in the our threads. However, because all of us have social lives outside of XDA, your questions may not always be answered right away. Members who are more experienced in our work, please help out the ones who don't.
If you want to get the fastest and the best answer - ask the question in our threads instead of PM'ing us. Chances are, other users will be able to help you when Team Members don't have the time to.
Click to expand...
Click to collapse
IV. Updates
We are a busy team! Every Team Member has lives outside of XDA. You cannot expect us to sit in front of the computer all day and develop Android. Please do not ask for ETA's. The update will come when we release it. Sometimes, there is a good reason for why we have not released an update in a while. Please be patient with us, we will do as we promise. Updates will come.
Click to expand...
Click to collapse
V. Responsibilities
We are not responsible for your device! We do not guarantee that everything will work the way it's supposed to. Not every device is created equal, what might work on our devices may not work on yours or vice versa. Please be a responsible person when it comes to flashing. This is a mature site, don't act immaturely when your device becomes problematic. If you cry and blame us for "destroying" your device, we will laugh at you. Your device is your responsibility, act like it.
Thanks for choosing Team Horizon, we hope you enjoy our works as much as we enjoy working with them.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
MOD Section
This is going to be a section where I post add ons for this ROM. Enjoy!
Click to expand...
Click to collapse
<---------http://dl.dropbox.com/u/44672998/supporter.png
My Dev-Host Account With All The Add On Downloads!
http://goo.gl/4rscI
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Invered Gapps! 4.2.1
CLICK ME
Click to expand...
Click to collapse
:highfive:
HELP!
Please Help Contribute To This Project. Either Post Question With Answer and I Will Add To OP or PM Me The Stoofz
:highfive:
Great idea Tory, You have been a real asset to the team, thanks for all you do.
Sent from my SCH-I535 using Tapatalk 2
I'm transferring this topic from the main page. I'm running 1.5 for Toro and had issues with WiFi tether. I dirty flashed from the prior version. I was running Franco 356. I wiped and restored 12-22 then dirty flashed again to 1.5. This time I'm still running the included kernel. I tested WiFi tether and it seems to work. Thusly, I think the issues may be related to Franco 356. Anybody got WiFi tether working with Franco?
Sent from my Galaxy Nexus using Tapatalk 2
crispy1 said:
I'm transferring this topic from the main page. I'm running 1.5 for Toro and had issues with WiFi tether. I dirty flashed from the prior version. I was running Franco 356. I wiped and restored 12-22 then dirty flashed again to 1.5. This time I'm still running the included kernel. I tested WiFi tether and it seems to work. Thusly, I think the issues may be related to Franco 356. Anybody got WiFi tether working with Franco?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I am on latest franco and fixing to test wifi tether. hold (on gsm tho)
crispy1 said:
I'm transferring this topic from the main page. I'm running 1.5 for Toro and had issues with WiFi tether. I dirty flashed from the prior version. I was running Franco 356. I wiped and restored 12-22 then dirty flashed again to 1.5. This time I'm still running the included kernel. I tested WiFi tether and it seems to work. Thusly, I think the issues may be related to Franco 356. Anybody got WiFi tether working with Franco?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I was able to connect wifi tether and usb tether with the latest franco. Keep in mind that I ALWAYS WIPE before flashing any updates to iron out those pesky little bugs.
pr0xy mAn1Ac said:
I was able to connect wifi tether and usb tether with the latest franco. Keep in mind that I ALWAYS WIPE before flashing any updates to iron out those pesky little bugs.
Click to expand...
Click to collapse
OK, good to know. I'll flash Franco and if it is still broken, I'll clean flash 1.5 followed by an update to Franco.
Sent from my Galaxy Nexus using Tapatalk 2
crispy1 said:
OK, good to know. I'll flash Franco and if it is still broken, I'll clean flash 1.5 followed by an update to Franco.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Please keep us posted on your progress. let me know if I can help.
Quick Unlock
Is quick unlock working? It has not worked for me for a while, but I saw one person say it works. I have done a full wipe with each version. Thanks!
pr0xy mAn1Ac said:
Please keep us posted on your progress. let me know if I can help.
Click to expand...
Click to collapse
I reflashed clean and am still unable to connect. Still on default kernel. I can see the network but I cannot connect even without security. Tried both an iPad and an Android tablet. Blue tooth tether works but that us too slow. I'm out of options. This is a show stopper for me.
Sent from my Galaxy Nexus using Tapatalk 2
crispy1 said:
I reflashed clean and am still unable to connect. Still on default kernel. I can see the network but I cannot connect even without security. Tried both an iPad and an Android tablet. Blue tooth tether works but that us too slow. I'm out of options. This is a show stopper for me.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I have to have tethering. Flashed back to CNA 3.8 and I got it back. May need to hang on to 4.1.2 a bit longer.
Sent from my iPad using Tapatalk HD
crispy1 said:
I have to have tethering. Flashed back to CNA 3.8 and I got it back. May need to hang on to 4.1.2 a bit longer.
Sent from my iPad using Tapatalk HD
Click to expand...
Click to collapse
edited
10char
Navigation bar opacity
I love the whole ROM, been using it for a while. I was very excited to see a translucent menu bar option in the 12/30/12 release. However im not sure of its functioning properly. On the home screen the nav bar is translucent however in any app its a solid black background again. When I zoom using accessibility feature (triple tap) the nave bar goes back to being all but invisible. Is this transparent effect only supposed to do what it does on my case? Thanks man, keep up the good work
Just a quick question pr0xy ... Do I have to wipe data in order to install inverted gapps or can i dirty flash over the 20121212 package? Thx in advance!
Just flash the gapps brother no wiping needed. Enjoy.
Sent from my Galaxy Nexus using Xparent ICS Tapatalk 2
Ok, another stupid question inc! :/ Proxy - do you know of any place where I could get "Black Facebook" to match the inverted gapps ? Since I kinda prefer it over the stock white FB app ... I could find only some lower versions which are slow and buggy, so ... Thx in advance
Doomhamma said:
Ok, another stupid question inc! :/ Proxy - do you know of any place where I could get "Black Facebook" to match the inverted gapps ? Since I kinda prefer it over the stock white FB app ... I could find only some lower versions which are slow and buggy, so ... Thx in advance
Click to expand...
Click to collapse
It is included with the inverted gapps. Enjoy.
Sent from my Galaxy Nexus using Xparent ICS Tapatalk 2
pr0xy mAn1Ac said:
It is included with the inverted gapps. Enjoy.
Sent from my Galaxy Nexus using Xparent ICS Tapatalk 2
Click to expand...
Click to collapse
No it's not ... That's why I asked
*DUMB NEWBIE QUESTION*
how to flash this rom ?
just tried to flash the rom using TWRP, but it stucks at bootlogo.
now restored the rom and N4 is working normal.
any solution ?
thx in advance.
Hello to everyone !
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Huawei Ascend P6
STATE - Stable version !
Unlocked Firmware : Android JellyBean 4.2.2 !
About :
builded from the last updated CyanogenMod 10.1 source ;
build safe to flash only if you follow the steps to Installation !
Not Working :
video camera working, but still there are some issues ;
H/W video decoder ;
settings/battery usage data ;
Changelog :
fixed Wi-Fi hostpot ;
custom ramdisk !
CPU Mode Switch on Advanced settings ;
enabled Switch Storage !
fix brightness issue !
enabled acceleratord !
enabled bluetooth audio a2dp profile ;
the whole base updated to B120 ;
POWER MANAGER with : Powersave, Normal & Performance Profiles ;
clean, fast & stable version ;
enabled stock aosp camera !
video camera working with some issues ! ( will be fixed soon )
HD video player working also on YouTube/Browser !
H/W video decoder enabled !
23/09/2014
enbale Doly Digital Plus ;
added Stock Huawei Camera & Gallery ;
added Gloves Mode Switch ;
fix HDR Mode ;
fix Camera Video Recording ;
Downloads :
New Update 23/09/2014
cm-10.1-20140422-UNOFFICIAL-hwp6_u06.zip
cm-10.1-20140123-UNOFFICIAL-hwp6_u06.zip
Mirror : cm-10.1-20140123-UNOFFICIAL-hwp6_u06.zip - 190.63 MB
cm-10.1-20140115-UNOFFICIAL-hwp6_u06.zip
cm-10.1-20140112-UNOFFICIAL-hwp6_u06.zip - 183.51 MB && CM_B118_kernel.zip
cm-10.1-20140108-UNOFFICIAL-hwp6_u06.zip
cm-10.1-20140103-UNOFFICIAL-hwp6_u06.zip
gapps-jb-20130812-signed.zip !
Installation :
make sure your device was already Unlocked !
root not require !
you must have already installed TWRP Recovery R03.1 !
copy cm build & gapps on your external sdcard !
put your device in recovery mod ;
Wipe -> Advanced Wipe -> select : Dalvik Cache, System, Cache, Cust & Data ! ( equivalent to "Clean Install" )
Swipe to Wipe ;
Install -> select : Storage : External Storage !
select cm-10.1-rom
Add More Zips
select gapps
Swipe to Confirm Flash !
Wipe cache/dalvik !
Reboot System !
Enjoy ...
If Gmail or other gapps cannot update from PlayStore, please navigate to Settings -> Apps -> search your app -> Clear data ! Now please try again to update !
Click to expand...
Click to collapse
Source :
GitHub !
Credit :
direct or indirect contributors :
CyanogenMod, AshRoller, scue, @kholk
special thanks to @PulseDroid
Screenshots :
Thank you very much to all donors - ! This helps to maintain and continue this project !
regards,
Surdu Petru
Older versions CM10.1 for Huawei Ascend P6
Test version : 26/12/2013 !
About :
builded from the last updated CyanogenMod 10.1 source ;
build safe to test only if you follow the steps to Installation !
Not Working :
sound ;
camera ;
gps ;
maybe some other small stuff
Downloads :
cm-10.1-20131225-UNOFFICIAL-hwp6_u06.zip SumMD5 : d8fc21ceef82704af19290aac52e41f7
Beta version : 29/12/2013 !
About :
builded from the last updated CyanogenMod 10.1 source ;
build safe to test only if you follow the steps to Installation !
Not Working :
camera ;
gps ;
maybe some other small stuff :
audio a2dp ;
USB mass storage ;
Changelog :
fixed browser issue ;
fixed external sdcard issue ;
improved wifi ;
enabled sound ;
fixed DSP fc ;
fixed volume up-down issue ;
added FmRadio - not working yet !
Downloads :
cm-10.1-20131229-UNOFFICIAL-hwp6_u06.zip SumMD5 : 06422bf2ec63db4601b546e2a201b425
gapps-jb-20130812-signed.zip !
Thanks a lot for awesome work. We are sure you will fix all bugs soon. Thanks again. Keep it up
Sent from my P6-U06 using xda app-developers app
husen4u said:
Thanks a lot for awesome work. We are sure you will fix all bugs soon. Thanks again. Keep it up
Sent from my P6-U06 using xda app-developers app
Click to expand...
Click to collapse
Thanks mate ...
But here we have some developers who could help us, that's why I released source code !
Sure, also source code should improved :good:
Good Job!
This is going to put the P6 on the map. I hope to do a kernel too.
PulseDroid said:
Good Job!
This is going to put the P6 on the map. I hope to do a kernel too.
Click to expand...
Click to collapse
Ok , you are welcome to do ... :good:
I thing also we need your help for sound issue , sure if you can and if you have time to develop something for us !
:good:
hope that this will improve P6 ROM development, and attract some devs
Hey, I tested this, really liked seeing clean Android on our device
I see a lot of little bugs which, I hope, will be fixed in due time.
Great work and keep on the good stuff!
In this rom could install this theme :
https://play.google.com/store/apps/details?id=com.jasonevil.theme.miuiv5dark
###
neodante said:
In this rom could install this theme :
https://play.google.com/store/apps/details?id=com.jasonevil.theme.miuiv5dark
###
Click to expand...
Click to collapse
Yes you could use that, but bare in mind that this rom lacks some major features, like sound etc.
It may not be usable as a daily driver..
It's good for us to have you in our forum. hehehe
Hope this could be a good chance to develop Ascend Mate's CM rom as well.
Sent from my HUAWEI MT1-U06 using xda app-developers app
euromusic said:
Yes you could use that, but bare in mind that this rom lacks some major features, like sound etc.
It may not be usable as a daily driver..
Click to expand...
Click to collapse
Of course that I only will put when it see almost 100% functional
###
so this is not emulated android?
benna said:
so this is not emulated android?
Click to expand...
Click to collapse
From what I gathered, the emulated Android was not a proven theory. Seeing the recovery working native also makes it look like it is not really emulated. So super good news
benna said:
so this is not emulated android?
Click to expand...
Click to collapse
The P6 was never emulated. Ever.
Goldfish is a script on every single Android, take any other Android, and you'll see.
The thing giving poor performance mostly is the kernel, which in this case is still stock with a few tweaks, it'll be faster as the ROM is lighter 188MB < +/- 1GB. Also the mods to the kernel will give it improved speed but still not full potential.
The P6 Development has started to take off, give some time and you'll have a great device.
euromusic said:
From what I gathered, the emulated Android was not a proven theory. Seeing the recovery working native also makes it look like it is not really emulated. So super good news
Click to expand...
Click to collapse
benna said:
so this is not emulated android?
Click to expand...
Click to collapse
the emulated theory was created by someone who have delusion about P6. no base at all.
@surdu_petru or anyone that use cm-10.1 ROM
can you provide me log cat and kmesg (when you use camera, music player or anything related to bugs) and make sure you're use verbose mode.
Thanks,
Best Regards
Sent from my GT-i9100 using Tapatalk
AshRoller said:
the emulated theory was created by someone who have delusion about P6. no base at all.
@surdu_petru or anyone that use cm-10.1 ROM
can you provide me log cat and kmesg (when you use camera, music player or anything related to bugs) and make sure you're use verbose mode.
Thanks,
Best Regards
Sent from my GT-i9100 using Tapatalk
Click to expand...
Click to collapse
Hi !
Here is a part of logcat on boot ( it seems audio.primary module is not loaded ! )
*********************
I/mediaserver( 135): ServiceManager: 0x40b80ee8
I/AudioFlinger( 135): Using default 3000 mSec as standby time.
I/CameraService( 135): CameraService started (pid=135)
E/CameraHalInterface( 135): could not dlopen libcamera_core.so: Cannot load library: soinfo_relocate(linker.cpp:1013): cannot locate symbol "_ZN18SkJPEGImageEncoder8onEncodeEP9SkWStreamRK8SkBitmapi" referenced by "libcamera_core.so"...
I/AudioPolicyManagerBase( 135): loadAudioPolicyConfig() loaded /system/etc/audio_policy.conf
W/AudioPolicyManagerBase( 135): could not open HW module primary
W/AudioPolicyManagerBase( 135): could not open HW module a2dp
W/AudioPolicyManagerBase( 135): could not open HW module usb
E/AudioPolicyManagerBase( 135): Not output found for attached devices 00000003
E/AudioPolicyManagerBase( 135): Failed to open primary output
E/AudioPolicyManagerBase( 135): getDeviceForStrategy() speaker device not found for STRATEGY_SONIFICATION
E/AudioPolicyManagerBase( 135): getDeviceForStrategy() speaker device not found for STRATEGY_SONIFICATION
E/AudioPolicyService( 135): couldn't init_check the audio policy (No such device)
********************
It is because I kept stock cm libaudioflinger.so !
If libaudioflinger.so is changed with stock Huawei firmware , audio.primary is loaded by device cannot boot cause :
*****************
W/AudioSystem( 718): AudioPolicyService not published, waiting...
I/ServiceManager( 718): Waiting for service media.player...
I/ServiceManager( 718): Waiting for service media.audio_policy...
I/ServiceManager( 718): Waiting for service media.player...
I/ServiceManager( 718): Waiting for service media.audio_policy...
W/IMediaDeathNotifier( 718): Media player service not published, waiting...
I/ServiceManager( 718): Waiting for service media.audio_policy...
I/ServiceManager( 718): Waiting for service media.player...
I/ServiceManager( 718): Waiting for service media.audio_policy...
I/ServiceManager( 718): Waiting for service media.player...
I/ServiceManager( 718): Waiting for service media.audio_policy...
****************
Update : it seems also libaudioflinger.so ( stock Huawei ) cannot be loaded cause mediaserver say :
[email protected]:/ # exec /system/xbin/su -c /system/bin/mediaserver
soinfo_link_image(linker.cpp:1673): could not load library "libaudioflinger.so" needed by "/system/bin/mediaserver"; caused by soinfo_relocate(linker.cpp:1013): cannot locate symbol "_ZN7android11AudioSystem11setFmVolumeEf" referenced by "libaudioflinger.so"...CANNOT LINK EXECUTABLE
Click to expand...
Click to collapse
Thanks !
Added fix issue volume up & down on github !
Added also "standard AOSP fused location provider" & "Google Network Location Services location provider" !
surdu_petru said:
Added fix issue volume up & down on github !
Added also "standard AOSP fused location provider" & "Google Network Location Services location provider" !
Click to expand...
Click to collapse
Good news! step by step all will do.
What is the most important that remains to be done ??
###
neodante said:
Good news! step by step all will do.
What is the most important that remains to be done ??
###
Click to expand...
Click to collapse
The most important thing that we need to enable is : sound ! Camera & gps can be done later !
Looking also on Honor2 , cm 10.1 by @kholk, I can not managed to enable sound, cause is there no source code for his cm10.1 !
He has already modified some standard cm librarys , I think was added or removed some dependency, but we can not know what was done , because code source was not pushed to github !
What it is
It is a self cm13 build from official cm sources with a lot of patches. This rom is not intended to be used as daily usages, it is under development! The idea is to share with the community, let know there is an (slow) active cm13 devel for D6603 and maybe have some real dev help
Disclaimer
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
Who can use it
it is only for z3 and unlocked bootloaders
Prerequisites
I highly recommend to upgrade your bootloader before, in case something goes wrong.
a twrp in the FOTAKernel/recovery partition
wipe data/cache (without wipe /data/media) in twrp (except coming from cm-12.x, upgrade should work)
Sources
manifest
Version Information
Created: 2016-08-16
Last Updated: 2017-01-27
Status: Fairly unstable / abandoned
Releases
z3:
2017-01-27:
Download
md5: 87ca5e27461647b649f0df315ef2ab81
sha1: d9a4cb6342d3b63e0de1bfefc0fb47520bd5e57e
Periodical rebuild.
2016-12-15:
Download
md5: 4f4e8c9ace63010bd5239855e1174fbc
sha1: efda3d8920398ae9c5daea11367b63432937bd5c
Periodical rebuild for securities updates.
2016-11-23:
Download
md5: 66ff7b6362c0d6d473e418bd7ee85c42
sha1: fe4b0a17dd2db3276c4036fc8d0d54d9c8054e80
Periodical rebuild
2016-10-03:
Download
md5: d1b1daa38aec25702c242f7110085eaf
sha1: 3767b63f47a3f582e4bf8b3012e8cf0f48cb4124
Correct wifi path
Correct bcmdhd.ko errors (wifi)
Correct missing libhardware_legacy include errors (wifi)
2016-09-14: kernel 3.10
Download
md5: 5078772453445a319640fde70aed1d50
sha1: b64feffda124c436b8f07a06faa445a7b755308b
build with kernel 3.10 and with sony aosp blobs 1 2.
screen flickering is present
camera not working and continuously reboot
2016-09-08:
Download
md5: 500fe665033704bc54954f1d2b7532ce
sha1: c184295d6784e2b93e58e3866419bcd073698c77
nothing specially changed
start to regress camera stuff. No more loading errors but not the right blobs
z3c:
2016-10-03:
Download
md5: 018593359aa7b221128905fd8f950ba9
sha1: 5fde92524b20796d777bb47f176c01bdb91ba0d5
[*] Initial release on xda
Correct wifi path
Correct bcmdhd.ko errors (wifi)
Correct missing libhardware_legacy include errors (wifi)
Older releases
P.S.: i'm not affiliated to CyanogenMod
Changelog
This rom is based on kernel 3.4 (cm-12.1) and build with the full cm-13.0 tree.
Some feature may be unstable, other usable. Please report back, it will give me guidelines.
▇ ▅ █ ▅ ▇ ▂ ▃ ▁ What is working ▁ ▅ ▃ ▅ ▅ ▄ ▅ ▇
Bluetooth
WiFi
otg
Music
System sounds
gsm seems working
Touchscreen: cp qwerty.idc for some non original touchscreens
▇ ▅ █ ▅ ▇ ▂ ▃ ▁ What is not working ▁ ▅ ▃ ▅ ▅ ▄ ▅ ▇
Camera
Some audio crash -> fixed since 2016-08-18
WiFi -> fixed
Annoying display glitches -> display perfect on 3.4 kernel
Data connection -> fixed since 2016-08-21
Off-mode charging
Built-in app for video
fm radio
nfc
bluetooth
Bug stays here, crossed-out, until confirmation it is really working
▇ ▅ █ ▅ ▇ ▂ ▃ ▁ What is not tested ▁ ▅ ▃ ▅ ▅ ▄ ▅ ▇
In global way, all features related to sim card
Radio/data
Battery performance
All my repo are on github, any help apreciated
This 3.4 kernel trick on cm-13.0 should work for every xperia shinano based. If other variant need test or information, feel free to contact me.
▇ ▅ █ ▅ ▇ ▂ ▃ ▁ Reporting problems ▁ ▅ ▃ ▅ ▅ ▄ ▅ ▇
To report problem, please provide logs.
If your device is not booting at all, we need information about how you flash and all the handling you do, the display status, light status, and if available a dump of /proc/last_kmesg*
If you have a non working peripheral (non-working radio/wifi/etc...) please provide a full logcat and full dmesg, example:
Code:
adb reboot
adb wait-for-device
adb shell dmesg > dmesg.log
adb logcat -d > logcat.log
If you have a non working app please provide a partial logcat:
Code:
adb reboot
adb wait-for-device
adb logcat -c
<launch your app>
adb logcat -d > logcat.log
then upload your files to a service like pastebin.com / paste.omnirom.org
* for > 3.8 kernels /proc/last_kmesg was replaced by /sys/fs/pstore/console-ramoops.
Thanks men!!!
Real thanks to you... I wait CM13 for xperia z3 for very long time... I hope you will continue update this rom... You great.. Thanks!!!
I just got my Sony z3 6603 a few days a ago. I was trying to build cm and never thought of the screen glitch as a kernel issue. Good catch.
aclegg2011 said:
I just got my Sony z3 6603 a few days a ago. I was trying to build cm and never thought of the screen glitch as a kernel issue. Good catch.
Click to expand...
Click to collapse
I try everything possible to get out of this. I read a lot of adreno drivers. From what i read my conclusion is for the same commercial chipset name (adreno 330) there is multiples qualcomm manufacture and our msm8974 only had a 3.4 driver released. Turning on all the possible debugs in the kernel and the display hal doesn't really help. Seems it is due to a 'timeout when idle' issue.
Btw all officials sony roms are released with kernel 3.4.
So i revert back the build tree to 3.4
Working on camera yet. Try to include a minimal working one for the today release.
nailyk said:
I try everything possible to get out of this. I read a lot of adreno drivers. From what i read my conclusion is for the same commercial chipset name (adreno 330) there is multiples qualcomm manufacture and our msm8974 only had a 3.4 driver released. Turning on all the possible debugs in the kernel and the display hal doesn't really help. Seems it is due to a 'timeout when idle' issue.
Btw all officials sony roms are released with kernel 3.4.
So i revert back the build tree to 3.4
Working on camera yet. Try to include a minimal working one for the today release.
Click to expand...
Click to collapse
Yea, I didn't see anything in the logs about the kernel glitch. I tried changing out the adreno drivers, but still had the screen glitch. I was thinking it was a kernel issue because my twrp recovery was showing the glitch too.
Fyi, wifi is still broken in the latest release.
Great to know that we have a working CM13 without those ugly glitches! Thank you so much, will definitely keep an eye on this one
aclegg2011 said:
Fyi, wifi is still broken in the latest release.
Click to expand...
Click to collapse
Sorry to read that
I just give a try: format system, download the file from android file host, install and wifi is working. I can try a full wipe if you think it is needed.
Can you provide me a full log?
Also the first time i got it working, i need to remove the /data/misc/wifi/wpa_supplicant.conf due to permission denied error. (something about wpa_supplicant failed repetitively in the logs).
nailyk said:
Sorry to read that
I just give a try: format system, download the file from android file host, install and wifi is working. I can try a full wipe if you think it is needed.
Can you provide me a full log?
Also the first time i got it working, i need to remove the /data/misc/wifi/wpa_supplicant.conf due to permission denied error. (something about wpa_supplicant failed repetitively in the logs).
Click to expand...
Click to collapse
No problems. I think wifi needs wpa_suppliant.conf. Could be a sepolicy issue. Setting the kernel to permissive mode should allow me to run catlog through adb and see if it's s sepolicy issue or not.
Actually the WiFi paths weren't set correctly, after fixing that WiFi works fine.
aclegg2011 said:
Actually the WiFi paths weren't set correctly, after fixing that WiFi works fine.
Click to expand...
Click to collapse
Oh! I think i got it. Are you building instead of installing my .zip?
If yes it is totally my bad! I have a lot of unpushed changes, especially in the vendor repo.
I replace the wifi blobs by the M one and they doesn't work in the new path.
Btw i also replace the modem blobs which increase a lot the agps accuracy and the speed of LTE.
I will try to push that as soon as i go home. Sorry for that.
Oops anyone use kakao talk? it isn't excute... wifi, data, music is okay.
Urban Crown said:
Oops anyone use kakao talk? it isn't excute... wifi, data, music is okay.
Click to expand...
Click to collapse
Thanks for feedback about data connection! Is LTE also working? I can't remember if the installed baseband is international.
Can you provide me a logcat when you launch the app after a fresh reboot please?
nailyk said:
Thanks for feedback about data connection! Is LTE also working? I can't remember if the installed baseband is international.
Can you provide me a logcat when you launch the app after a fresh reboot please?
Click to expand...
Click to collapse
Ooh... It isn't connect! apn is unperfectly. Sorry about wrong feedback.. and I will update titanium backup and restore data again. When I reboot my phone, this app says password data is broken. So I think restore data has something wrong..
Thanks to make useable CM13. keep your work, many people cheer you!
nailyk said:
Oh! I think i got it. Are you building instead of installing my .zip?
If yes it is totally my bad! I have a lot of unpushed changes, especially in the vendor repo.
I replace the wifi blobs by the M one and they doesn't work in the new path.
Btw i also replace the modem blobs which increase a lot the agps accuracy and the speed of LTE.
I will try to push that as soon as i go home. Sorry for that.
Click to expand...
Click to collapse
Yea, I have a dedicated Android build box. I can build z3 in 19 mins.
---------- Post added at 06:46 PM ---------- Previous post was at 06:31 PM ----------
The sooner we get cm13 fully working, the sooner I can start working on n for our z3. Our when Sony releases the n blobs and device tree.
aclegg2011 said:
Yea, I have a dedicated Android build box. I can build z3 in 19 mins.
The sooner we get cm13 fully working, the sooner I can start working on n for our z3. Our when Sony releases the n blobs and device tree.
Click to expand...
Click to collapse
Nice!
I fork the muppet repo and commit the blobs diffs. But i commit really quickly maybe there is some mistake, i'm currently trying to debug the boot of twrp.
N sources seems to be available on googlesources.
I also found this person / repo which seems to have interesting patches.
nailyk said:
Nice!
I fork the muppet repo and commit the blobs diffs. But i commit really quickly maybe there is some mistake, i'm currently trying to debug the boot of twrp.
N sources seems to be available on googlesources.
I also found this person / repo which seems to have interesting patches.
Click to expand...
Click to collapse
Yea, I'm downloading the 7.0 source to my build box now. We can actually pull the n blobs from the Sony dev preview ftf if we really wanna be crazy
aclegg2011 said:
Yea, I'm downloading the 7.0 source to my build box now. We can actually pull the n blobs from the Sony dev preview ftf if we really wanna be crazy
Click to expand...
Click to collapse
i already use some N blobs in this build
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am proud to present first Dualboot project For Redmi Pro. This will allow any number of ROMs to be installed at the same time. It works by patching the secondary ROM's installation scripts and boot image to load the ROM files from an alternate location (/system/multiboot, /cache/multiboot, and /data/multiboot). Because of the way this is implemented, no changes to the primary ROM are necessary
What is DualBootPatcher?
DualBootPatcher is an open-source app that allows multiple ROMs to be installed on a single Android device. It does its best to work with existing code and does not require explicit support from ROMs. There are currently 200+ supported devices and their variations.
Information:
I have managed to support for Redmi Pro to the DualBootPatcher App, I am not the creator, just the supporter.
It's awesome and useful for testing out roms or if you want, switching ROMS.
Disclaimer:
Code:
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
Requirements:
1. A Custom Recovery (TWRP)
2. A ROM
3. Dual Boot Patcher app and the DualBootUtilities.zip from the download section below.
What does the app do ?:
It patches...
Custom kernels for dual boot support
ROMs so that they can be installed as secondary
Google Apps packages for AOSP-based ROMs
SuperSU so that it can be used in the secondary ROM
What's supported ?
Except Toaster and Alarm clocks pretty much everything is supported.
Click to expand...
Click to collapse
How to use the App?
- Download, install and open the app.
- Swipe to the right to open the menu. Click "ROMS". Now if this is the first time you use it, it will ask you if you want to set kernel. Do so!
- After it has finished go to ROM Settings (primary ROM 3 dot menu) and select Update Ramdisk. It will update it and will ask you to reboot. Press Reboot Now, or Reboot later.
- Now Download any ROM you like and open the app again and open the menu and open Patch Zip File from the menu. Ensure that your Device is set to (eyeul) and under Partition configuration select secondary (will install 2nd ROM in /system) or data slot.
- Click continue and select where to save the patched file.
- You should see the file is being put in "Queue". Just click the confirm button to the upper right.
Note: If you want to go back, just swipe the ROM in queue to right and start over.
- The app will patch the zip. When done, go back to "ROMs".
- Click "Flash zip files" (the big pink button on the lower right). Click the pink plus button to add your previously patched zip file.
- Locate the file you have patched in step 7. Unless you have changed the name there, it should be something like ROM_name_partition_config_ID.zip (like RR-N-v5.8.3-20170707-omega-Unofficial_dual.zip).
- Click on that file and choose "Keep location". Now confirm the flash with the button on the upper right side.
Note: You can also install the patched zip files in recovery.
- It will now open the terminal and begin flashing the file. This requires some patience. After it has flashed the file you'll see success message in green.
- Now click back and you should see your newly installed ROM along with the Primary ROM.
Note: You can find more options by clicking on the three buttons on each ROM.
- Now reboot and wait till finishing 2nd ROM first boot. install DualBootPatcher apk so you can easily switch ROMs, there is another way to change ROMs: flash DualBootUtilities.zip and switch ROM manually.
Note: Using Bootui:
- Open app then select settings and press install (update) bootui. then Swipe to the right to open the menu. Click "ROMS" again and open secondary ROM Settings) and select Update Ramdisk, Now you can change ROMs simply using boot ui (something like grub bootloader but it works like twrp)
Partitions Configurations:
The patcher offers several locations for installing ROMs:
Primary: This is normally used for installing a zip to the primary ROM. It is not required, but is strongly recommended because it has code to prevent the zip from inadvertently affecting other ROMs.
Dual: Dual/Secondary is the first multiboot installation location. It installs to the system partition. This is a good spot for installing a second ROM because it doesn't take any space away from the internal storage.
Multi-slots: There are 3 multislots: multi-slot-1, multi-slot-2, multi-slot-3. These install to the cache partition. This is specifically for devices, like the Galaxy S4, that have a massive cache partition.
Data-slots: There can be an unlimited number of data slots. These install to the data partition and eat up space on the internal storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny. These slots are named "data-slot-[id]", where "id" is something you provide in the app.
Extsd-slots: There can be an unlimited number of extsd slots. These install to the external SD card, which is useful as it keeps the ROMs off of the internal storage. Note that the ROM's data files are still stored on the data partition.
How to boot to another ROM ?
This is simple ... There is no reboot to primary, secondary or whatever. So all you have to do is:
1) Go to ROMs section of the App.
2) Click on the ROM you want to boot to. You should see "Switching ROM" message. After few seconds, you should see a report message saying that "ROM successfully switched".
3) Now just do a normal reboot of your device. See the magic! It should boot to the ROM you have switched on step 2.
Note: You can find more options by selecting the three buttons on each ROMs (like creating reboot widgets for directly rebooting to specific rom).
You also need to install the App to all of the ROMs you install. Otherwise, you want be able to boot to other ROMs!
Apps and Data sharing:
DualBootPatcher very recently got support for sharing apps and their data across ROMs. Maybe sharing is somewhat of a misleading term. The feature actually makes Android load the shared apps and data from a centralized location, /data/multiboot/_appsharing. So you're not sharing apps from one ROM to another per se. The ROMs are just loading the apps from one shared location. Let me make this clearer with an analogy.
Think of the people in a company office as ROMs. You want to share with your coworkers some documents (apps). Instead of telling them to come over to your desk to see those documents (sharing apps from one ROM to another), everyone goes to the conference room to look at the documents together (loading apps from a shared location). That's how app and data sharing is implemented.
Click to expand...
Click to collapse
To use app sharing, follow these steps in every ROM that you want to use app sharing: (doesn't work with JB ROMs)
Install the app you want to share
Open DualBootPatcher and go to "App Sharing" in the navigation drawer
Enable individual app sharing
Tap "Manage shared applications" and enable APK/data sharing for the app
Reboot
When you uninstall an app that's shared, it simply become unshared for the current ROM. That way, other ROMs are not affected. To continue the analogy above, if you quit your job, you won't shred the documents that everybody else was looking at.
If you unshare an app's data, it will go back to using the data it had before it was shared. In other words, you leave the conference room and go back to work on your own documents at your desk.
Click to expand...
Click to collapse
Other How to ?
Wipe /cache, /data, /system, or dalvik-cache?
The easiest way is to do it from the app while booted in another ROM. Just go to "Roms" in the navigation drawer, tap the 3 dots options menu for the ROM you want to wipe, and tap "Wipe ROM".
Update the primary ROM?
Patch the zip for primary and flash it. The "primary" installation target is designed so that other ROMs won't be affected when you want to flash something for the primary ROM.
Update a non-primary ROM?
Patch and flash the zip exactly like how you did it the first time.
Flash a mod or custom kernel for the primary ROM?
Patch it for primary before flashing. If the zip does not wipe /cache, it is also safe to flash it directly.
Flash a mod or custom kernel for a non-primary ROM?
Just patch and flash it
Downloads:
All Downloads HereCheers ! we are officially supported
Note: You can download any version since "9.2.0.r295.g3b684238"
Screenshots:
No Screenshots, I need some
Sources:
DualBootPatcher: https://github.com/chenxiaolong/DualBootPatcher
DualBootUtilities: https://github.com/chenxiaolong/DualBootZips
Build instructions: https://github.com/chenxiaolong/DualBootPatcher/tree/master/docs
Redmi Pro Support:
https://github.com/chenxiaolong/DualBootPatcher/pull/707
Known issues:
- You tell me !
Credits:
@chenxiaolong for the awesome DualBootPatcher.
XDA:DevDB Information
[PATCHER][APP][OFFICIAL] Dualboot/Multiboot For Redmi Pro, Tool/Utility for the Xiaomi Redmi Pro
Contributors
yshalsager, chenxiaolong
Source Code: https://github.com/chenxiaolong/DualBootPatcher
Version Information
Status: Stable
Current Stable Version: 9.2.0.r295.g3b684238
Created 2017-08-19
Last Updated 2017-10-03
Notes
1- If flashing Custom ROM Fail (like LOS 14.1):
you have to edit "updater-script" and remove assert lines like:
Code:
assert(getprop("ro.product.device") == "omega" || getprop("ro.build.product") == "omega" || abort("E3004: This package is for device: omega; this device is " + getprop("ro.product.device") + "."););
ifelse(is_mounted("/system"), unmount("/system"));
2- To Flash AROMA ROMs flash patched zip from TWRP
Changelogs
-19/08/2017
Initial Release, waiting for adding officially
Much thanks
yshalsager said:
1- If flashing Custom ROM Fail (like LOS 14.1):
you have to edit "updater-script" and remove assert lines like:
2- To Flash AROMA ROMs flash patched zip from TWRP
Click to expand...
Click to collapse
Pls help me when trying to patch my ROM (Los 13) it says that it need documents enabled from settings. The problem is I already have...
Please help me I'm very keen to be the first to try
yshalsager said:
1- If flashing Custom ROM Fail (like LOS 14.1):
you have to edit "updater-script" and remove assert lines like:
2- To Flash AROMA ROMs flash patched zip from TWRP
Click to expand...
Click to collapse
daffa ZRN said:
Pls help me when trying to patch my ROM (Los 13) it says that it need documents enabled from settings. The problem is I already have...
Please help me I'm very keen to be the first to try
Click to expand...
Click to collapse
Here are the screenshots
yshalsager said:
-19/08/2017
Initial Release, waiting for adding officially
Click to expand...
Click to collapse
Ok now it works but when rebooting to enter secondary rom (using bootUI) it just boots to twrp.
I'm using resurrection remix as the secondary ROM, also when it's flashing (through the app) the message is red not green which means a fail. Maybe the that's the problem. Pls help so I can test it out and report back
daffa ZRN said:
Ok now it works but when rebooting to enter secondary rom (using bootUI) it just boots to twrp.
I'm using resurrection remix as the secondary ROM, also when it's flashing (through the app) the message is red not green which means a fail. Maybe the that's the problem. Pls help so I can test it out and report back
Click to expand...
Click to collapse
Yep red message means it didn't flash successfully. Can you take a look at second post? You need to remove assert lines
daffa ZRN said:
Pls help me when trying to patch my ROM (Los 13) it says that it need documents enabled from settings. The problem is I already have...
Please help me I'm very keen to be the first to try
Click to expand...
Click to collapse
You can choose zip using any explorer app like ES File
yshalsager said:
Yep red message means it didn't flash successfully. Can you take a look at second post? You need to remove assert lines
Click to expand...
Click to collapse
Sorry but can you show me how(I'm a noob)
Wow, dual boot patcher stops working when pressing ROMs, I am in a redmi note 3 pro kate, since version 277 no longer works but in 257 down function without errors, someone else happens to this?
Error log:
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'Xiaomi/kate/kate:6.0.1/MMB29M/V8.2.4.0.MHRMIDL:user/release-keys'
Revision: '0'
ABI: 'arm64'
pid: 13581, tid: 14315, name: pool-1-thread-1 >>> com.github.chenxiaolong.dualbootpatcher.snapshot <<<
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xdeadbaad
Abort message: 'invalid address or address of corrupt block 0x7fa60f0090 passed to dlfree'
x0 0000000000000000 x1 0000007faf7ba7d0 x2 0000000000000001 x3 00000000007fabf9
x4 0000000000000000 x5 00000000deadbaad x6 0000000000000000 x7 0000000000000010
x8 7f7f7f7fffff7f7f x9 6471656b631f6e73 x10 7f7f7f7f7f7f7f7f x11 0101010101010101
x12 0000007faf7ba7c8 x13 58934240ef78b85e x14 58934240ef78b85e x15 0030f907887041ba
x16 0000007faf7b4a58 x17 0000000000000000 x18 0000007faca2a000 x19 0000007fa60f0090
x20 0000007faf7bb000 x21 0000007fa60f00a0 x22 0000007faf7bba70 x23 00000055995187e8
x24 0000000000000002 x25 0000005599529258 x26 0000000000000000 x27 0000000032e3dbe0
x28 00000055995a5860 x29 0000007f93a7f060 x30 0000007faf753580
sp 0000007f93a7f060 pc 0000007faf753588 pstate 0000000060000000
backtrace:
#00 pc 0000000000047588 /system/lib64/libc.so (dlfree+408)
#01 pc 00000000000195a8 /system/lib64/libc.so (free+20)
#02 pc 0000000000029054 /data/app/com.github.chenxiaolong.dualbootpatcher.snapshot-2/lib/arm64/libmbcommon.so
#03 pc 0000000000029224 /data/app/com.github.chenxiaolong.dualbootpatcher.snapshot-2/lib/arm64/libmbcommon.so
#04 pc 0000000000011b40 /data/app/com.github.chenxiaolong.dualbootpatcher.snapshot-2/lib/arm64/libmbcommon.so (_ZN2mb8format_vERSsPKcSt9__va_list+132)
#05 pc 000000000000abd0 /data/app/com.github.chenxiaolong.dualbootpatcher.snapshot-2/lib/arm64/libmbbootimg.so (_ZN2mb7bootimg6Reader11set_error_vESt10error_codePKcSt9__va_list+84)
#06 pc 0000000000009588 /data/app/com.github.chenxiaolong.dualbootpatcher.snapshot-2/lib/arm64/libmbbootimg.so (_ZN2mb7bootimg6Reader9set_errorESt10error_codePKcz+108)
#07 pc 000000000000d300 /data/app/com.github.chenxiaolong.dualbootpatcher.snapshot-2/lib/arm64/libmbbootimg.so
#08 pc 000000000000c96c /data/app/com.github.chenxiaolong.dualbootpatcher.snapshot-2/lib/arm64/libmbbootimg.so
#09 pc 0000000000009ed8 /data/app/com.github.chenxiaolong.dualbootpatcher.snapshot-2/lib/arm64/libmbbootimg.so (_ZN2mb7bootimg6Reader4openEPNS_4FileE+308)
#10 pc 0000000000009a88 /data/app/com.github.chenxiaolong.dualbootpatcher.snapshot-2/lib/arm64/libmbbootimg.so (_ZN2mb7bootimg6Reader13open_filenameERKSs+216)
#11 pc 0000000000011ec8 /data/app/com.github.chenxiaolong.dualbootpatcher.snapshot-2/lib/arm64/libmiscstuff-jni.so (Java_com_github_chenxiaolong_dualbootpatcher_nativelib_libmiscstuff_LibMiscStuff_getBootImageRomId+300)
#12 pc 0000000000603934 /data/app/com.github.chenxiaolong.dualbootpatcher.snapshot-2/oat/arm64/base.odex (offset 0x35c000)
I've use it for a long time,but i changed my model into Redmi Note 4(MTK) then I can use dualbootpatcher.now pro can use it with out changing model.it's great!:good:
yshalsager said:
Yep red message means it didn't flash successfully. Can you take a look at second post? You need to remove assert lines
Click to expand...
Click to collapse
Ok now I know how to remove those line and I did it, I removed the 1st and the 3rd line.
But now Im facing another fail on flash please help
zhaodelin2002 said:
I've use it for a long time,but i changed my model into Redmi Note 4(MTK) then I can use dualbootpatcher.now pro can use it with out changing model.it's great!:good:
Click to expand...
Click to collapse
You know how to fix my issue?
daffa ZRN said:
You know how to fix my issue?
Click to expand...
Click to collapse
sorry,my way isn't same as yours......
Ivan Torres said:
Wow, dual boot patcher stops working when pressing ROMs, I am in a redmi note 3 pro kate, since version 277 no longer works but in 257 down function without errors, someone else happens to this?)
Click to expand...
Click to collapse
The problem is from app. Not from your device. For me r199 works perfectly. You can use version in this thread also
daffa ZRN said:
Ok now I know how to remove those line and I did it, I removed the 1st and the 3rd line.
But now Im facing another fail on flash please help
Click to expand...
Click to collapse
Remove from starting of file to the end of line 3
The file should be started with "package" line
zhaodelin2002 said:
sorry,my way isn't same as yours......
Click to expand...
Click to collapse
What's your way, maybe I can try
daffa ZRN said:
What's your way, maybe I can try
Click to expand...
Click to collapse
modify build.prop
yshalsager said:
Remove from starting of file to the end of line 3
The file should be started with "package" line
Click to expand...
Click to collapse
Still not working do you have a ROM already modified?