This is not a formal release, because i dont have the phone and anything posted here is completely untested, by using it you agree that anything that happens to your phone, you are to blame.
While adapting the z7 max kernel to work on the z7 mini, i had an idea, i could do the same for the original z7, that has not got even one custom rom on its lifespan, and this is the result. I managed to build resurrection remix 5.7.3 for the z7 using an adapted z7 max kernel source, device tree, and binary blobs from the latest 3.83 firmware for the z7(nx506j).
I have to repeat, this is completely untested. Even if it works, it is very hard to maintain and fix bugs on it. If it at least boots, i will release the source on my git for someone else to pick it up and perfect it.
The mega folder here: https://mega.nz/#F!s0YBSSLY!s6fX3aLbvvOaFj9otI_wDA , contains the rom, a zip file to flash a newly built recovery(twrp 3.0.2 for the z7, that is untested as well) and a recovery.img if you prefer to flash the new recovery by fastboot. For anyone willing to test this, BACKUP EVERYTHING and mostly you efs and nv partitions, so that if the worst happens, you can fix your phone. Have fun, and remember the popular xda saying: if anything bad happens and you point the finger at me, i will laugh at you. So anyone with the nx506j crazy enough to try this, go ahead.
pchatzop said:
This is not a formal release, because i dont have the phone and anything tested here is completely untested, by using it you agree that anything that happens to your phone, you are to blame.
While adapting the z7 max kernel to work on the z7 mini, i had an idea, i could do the same fro the original z7, that has not got even one custom rom on its lifespan, and this is the result. I managed to build resurrection remix 5.7.3 for the z7 using an adapted z7 max kernel source, device tree, and binary blobs from the latest 3.83 firmware for the z7(nx506j).
I have to repeat, this is completely untested. Even if it works, it is very hard to maintain and fix bugs on it. If it at least boots, i will release the source on my git for someone else to pick it up and perfect it.
The mega folder here: https://mega.nz/#F!s0YBSSLY!s6fX3aLbvvOaFj9otI_wDA , contains the rom, a zip file to flash a newly built recovery(twrp 3.0.2 for the z7, that is untested as well) and a recovery.img if you prefer to flash the new recovery by fastboot. For anyone willing to test this, BACKUP EVERYTHING and mostly you efs and nv partitions, so that if the worst happens, you can fix your phone. Have fun, and remember the popular xda saying: if anything bad happens and you point the finger at me, i will laugh at you. So anyone with the nx506j crazy enough to try this, go ahead.
Click to expand...
Click to collapse
The bad thing about this phone, is that it has no qfil rom to flash, if it bricks
Enviado do meu LeTv 1 Pro através de Tapatalk
It has a working twrp to take a full backup, and i think there is the nx506j updater that can restore it if something goes wrong.
I will try this weekend maybe
Enviado do meu LeTv 1 Pro através de Tapatalk
pchatzop said:
This is not a formal release, because i dont have the phone and anything tested here is completely untested, by using it you agree that anything that happens to your phone, you are to blame.
While adapting the z7 max kernel to work on the z7 mini, i had an idea, i could do the same fro the original z7, that has not got even one custom rom on its lifespan, and this is the result. I managed to build resurrection remix 5.7.3 for the z7 using an adapted z7 max kernel source, device tree, and binary blobs from the latest 3.83 firmware for the z7(nx506j).
I have to repeat, this is completely untested. Even if it works, it is very hard to maintain and fix bugs on it. If it at least boots, i will release the source on my git for someone else to pick it up and perfect it.
The mega folder here: https://mega.nz/#F!s0YBSSLY!s6fX3aLbvvOaFj9otI_wDA , contains the rom, a zip file to flash a newly built recovery(twrp 3.0.2 for the z7, that is untested as well) and a recovery.img if you prefer to flash the new recovery by fastboot. For anyone willing to test this, BACKUP EVERYTHING and mostly you efs and nv partitions, so that if the worst happens, you can fix your phone. Have fun, and remember the popular xda saying: if anything bad happens and you point the finger at me, i will laugh at you. So anyone with the nx506j crazy enough to try this, go ahead.
Click to expand...
Click to collapse
i have bricked my smarthphone, nothing comes up, not even serial port
dont ask if i have the drivers, i do
any help
Try using the nx506j updater from here: http://www.androidiani.com/forum/mo...-z7-nx506j-stock-lollipop-lang-pack-bb72.html . The power+volup+voldown trick for some seconds might help.
I want to know exactly what you did, in order to be able to help you, i will search the nx506j board schematics later to find a testpoint, for jumpstarting the board in download mode.
I also removed the rom from mega, i am building one that does not flash the baseband.
pchatzop said:
I also removed the rom from mega, i am building one that does not flash the baseband.
Click to expand...
Click to collapse
have you found anything to help me?
Nubia ToolStudio
twd123 said:
have you found anything to help me?
Click to expand...
Click to collapse
Sorry about your phone
Can you put it in the recovery mode?
Try NubiaToolStudio or QPST you find references here
Since dear user @komplot confirmed that the build is booting and mostly working, i decided to take a further look, and i will have a new build up in the mega folder a few hours, for anyone with the device willing to test. Bugs mentioned was audio and orientation, and i did a lot of work on them, hope they are squashed. If my recovery is not working, try this one: https://mega.nz/#!ctkxlabD!rPlcL4mrCz8oNwZ_JqmR1Or2XXYThAQcX-38D_ABNa0 (found it at androidiani forum)
@twd123 please tell me what steps you took to lead to this outcome for the phone(if you still have it), and its current state, to try and think of a way to unbrick it. Unfortunately, i can not find schematics for the nx506j board online, to find the download mode testpoints, but removing the battery and using the combination volup+voldown+power while the phone is connected to the computer could be of help. The guides for lg g3 might also be of help(if you use toolstudio once you get to download mode), the points used are kinda similar.
Nubia Z7 nx506j RR Experimental
Thank you Pchatzop for your effort! I am glad you reply on my comments.
So, to be more specific about topic, I have try to flash your custom ROM a few times from I left the comment here. I try to use TWRP 3.0.2-0 to flash the latest RR (....2016115), however this build doesnt boot at all even when I try to use previous chinese TWRP based on TWRP 2.8... It looks the chinese TWRP works better than 3.0.2 because I have found the 3.0.2 doesnt flash even RR build 20160925, which previously works with errors I have described in my comment.
So, the resume is: I have found working only ResurrectionRemix-M-v5.7.4-20160925-nx506j.zip flashed by chinese TWRP.
Thank you, and I will test your build as soon as you publish it.
Have a nice day.
Try using the kernel from the 0925 release with the new release. Like replacing with boot.img from the 1105 release with the one from 0925. If it boots, i will know what to fix next.
Experimental RR nx506j
pchatzop said:
Try using the kernel from the 0925 release with the new release. Like replacing with boot.img from the 1105 release with the one from 0925. If it boots, i will know what to fix next.
Click to expand...
Click to collapse
Hi, I try to use boot.img from 0925 with 1115 release as you advice, and it works. That means, I can boot, the problem with gyroscope senzor (or with switching from portrait to landscape) dissapear. However the mic and speakers are still def, even if I overwrite the file "mixer_paths.xml" with the version you provide me. There are trouble with camer as well. Start camera ends with message "Cant connect to camera". I have used TWRP 3.0.2 which I have found at the forum. I have boot from build 0925, wipe dalvik and etc... There are some minor things as the diode of aside virtual butons arround middle button doesnt light. The knock wakeup doesnt works, but as i mention, those things are only minor. I have try as well to go back to version 3.88, but it ends with complete mess and even recovery doesnt works. So I wouldnt like to use stock ROM with lots of bloatware any more.
Would the provided information helps? Please feel free to ask me to check something else. As soon as possible with as many effort what I could, I will help.
Thank you.
Thanks for the feedback, now i know this is a kernel issue i have to fix(hopefully i can get you a bootable build soon without patches). The camera issue was there on the 0925 release? Because i used the drivers from 3.88 release on the 1115 build, and they could cause some problems with camera(had problems making them working on z7 max and mini). If camera works on the 0925 build(which contains 3.86 drivers), let me know. The audio problem is probably from the ak4961 dac chip on the z7 that the max and the mini are missing. I have send 2 emails to zte requesting the lollipop source for the z7, no response yet, hope they get back to me, as that is the key to getting this audio chip working. Please get me some logcats when you try to playback music, and try to use the nubia camera apps i have in the mega folder, could make a difference with the camera.
After the other tests, you can try this boot.img(with the last release), hope the kernel is fixed and booting now.
pchatzop said:
After the other tests, you can try this boot.img(with the last release), hope the kernel is fixed and booting now.
Click to expand...
Click to collapse
Hi.
I try camera functionality from 0925 build and it works flawlessly. The camera apk, you provide me from 3.88 drivers, doesnt work at all. It just blink after start, nothing happens, no error message.
I cant provide you with a log about mic and speakers functionality. After start to play music file or youtube everything looks OK, except there is no sound. No error messages. Have I missed something?
Tell me please what to check and I will dig it.
Thanks.
So camera works with the 3.86 blobs, that is really great to know. I have a new build, 3.88 blobs, hope you can try it and report what works and what does not. Camera is pretty easy to fix(by rolling back the blobs) so dont fret if it does not work with the latest build. I think the audio chip is working correctly, just the audio path was wrong in the kernel(i attempted to fix that in the latest build) and did not lead the decoded audio to the speaker or headset. Please try the last build without any patch and report back. Hopefully we will have a pretty much working build, with only minor bugs.
pchatzop said:
So camera works with the 3.86 blobs, that is really great to know. I have a new build, 3.88 blobs, hope you can try it and report what works and what does not. Camera is pretty easy to fix(by rolling back the blobs) so dont fret if it does not work with the latest build. I think the audio chip is working correctly, just the audio path was wrong in the kernel(i attempted to fix that in the latest build) and did not lead the decoded audio to the speaker or headset. Please try the last build without any patch and report back. Hopefully we will have a pretty much working build, with only minor bugs.
Click to expand...
Click to collapse
I have try 1119 build (3.88 blobs) you provide me. Many thanks. I flash it by TWRP (doing standard wipe before), everything seems right, no error messages or something suspicious. However after re-boting to system, the screen looks strange. Display was black, but turned on, no message of life after 5 mins I turned it on/off, after that, phone starts, but situation was strange again. After first show of logo, sreeen is fade out to 5 white strips left on. No signs of life again. I have seen very similar situation when I try update to official 3.88 drivers, but at that time a half of screen stay in wide blue strip turned on. After restart, the phone was not possible even to start in to recovery mode. I solve the situation "accidentaly" when I try to use the Nubia emergency tool. It was not a big time, because the phone could not connect to PC because of some trouble with snapdragon USB drivers... After few trays the phone was possible start at least to recovery. Any idea?
Thank you.
Im sorry it got you to that big trouble. Can you please try replacing the boot.img from the last release with the one from the yesterdays post and report back? Thank you for testing!
I created a new boot.img, this one is based on the booting and working configuration of 0925 builds, with only my attempted audio fixes included, hope you can try it with the last release. If you still get problems, i will roll back the blobs to 3.86 as well, seems the new 3.88 update caused many problems for many users of the nubia z7. Our priority is getting a working custom rom for the z7, and it doesnt matter much if the 3.86 or the 3.88 blobs are used.
Related
Hi all,
Since i'm unable to start a thread in the android development forum I try here. Hopefully Arrrrgh won't get Arrrrgh'd at me for posting this..
I have a problem which I hopefully get support for. I have tried all Android roms for the touch pro2 which none will boot or get past the ACL bootlogo.
I've tried every imaginable way to get it working but all are resulting in a kernel panic. I tried the NAND versions and the SD versions but both options results in the same kernel panic.
First I thought it was the SD formatting problem but after trying 4 different sizes and brands I excluded this as a possible cause.
It seems after looking at it a bit more thoroughly I got a Vario V version of the TP2 - Rhodium 100 (please correct me if i'm wrong)
I'm able to pull logs i'm ready and willing to pass the logs for supporting this device. I've found a similar thread by Z!nk / Z1nk but he gave up on the device before the developers could get to it.
So hopefully there is a developer willing to add this version to the android roms.
Thanks for reading and hope to hear from anyone soon.
Cheers,
Alchedin
[edit] The device has security unlocked and is HSPL'd [/edit]
Alchedin said:
It seems after looking at it a bit more thoroughly I got a Vario V version of the TP2 - Rhodium 100 (please correct me if i'm wrong)
Click to expand...
Click to collapse
How can we correct you if you're wrong - you need to tell us what phone variant you have. There's a surefire way to know as well...
It's kind of the first question in the FAQ...
Either way, the fact that you can't boot either makes me think you have a clone. There was another fellow with a clone (perhaps the one you mentioned?) that was unable to boot XDAndroid because he didn't have the same hardware. If you run HaRET.exe with no startup.txt, what does it say?
Edit - Regardless, I would focus on one build and try to get that to work. FRX07.1 is probably the "simplest" from that perspective.
Edit2 - Also, you seem to indicate it's a kernel panic. Why no logs?
Dear Arrrghhh,
Thanks for replying.
Ok, looking at the faq it states my phone should be a Rhod100 (complete: NM8RHOD100) which seems, when googeling, to be some kind of T-Mobile version. At the moment i'm running a deepshining
I ran the rom without a startup.txt and it gave me the following message: Found machine Rhodium. Hope this is the info you needed?
Placed in the Rhodium100 startup.txt a started haret again, which resulted in a kernel panic.
Will keep you informed since I'm not at home.
Alchedin said:
Placed in the Rhodium100 startup.txt a started haret again, which resulted in a kernel panic.
Click to expand...
Click to collapse
Logs? How do you know it's a kernel panic? What kernels have you tried?
arrrghhh said:
Logs? How do you know it's a kernel panic? What kernels have you tried?
Click to expand...
Click to collapse
Hi Arrrghhh,
Attached are the adb logs, which I hope is the info you need. This is what I get when using FRX07.1 like you advised.
But I have three questions if i'm not too bold:
1. Did you advise this version because it's more thoroughly when it comes to finding a issue?
2. When looking at the logs, is there something wrong with sound or something?
3. I'm able to pull logs of NAND builds if you like? They seem to be more complete when it comes to information on boot.
Cheers,
Alchedin
Today I tried the GBX0C version of XDandroid and this is the first working android on my phone. Boot-animation started and it just worked! Still can't believe it.
Any idea how this rom differs from the FRX07.1?
Cheers
Alchedin said:
Today I tried the GBX0C version of XDandroid and this is the first working android on my phone. Boot-animation started and it just worked! Still can't believe it.
Any idea how this rom differs from the FRX07.1?
Cheers
Click to expand...
Click to collapse
Well there's a few things, besides the whole FroYo vs. Gingerbread. The acoustic code/routing is the 'main' one. Not sure what else off the top of my head, but there's changelogs in the GBX0C thread. There's not a huge difference since some of it was backported to FRX...
Either way, glad GBX is working.
Edit - the logs you posted from the FRX failures don't really give me much to go off of either, unfortunately.
arrrghhh said:
Well there's a few things, besides the whole FroYo vs. Gingerbread. The acoustic code/routing is the 'main' one. Not sure what else off the top of my head, but there's changelogs in the GBX0C thread. There's not a huge difference since some of it was backported to FRX...
Either way, glad GBX is working.
Edit - the logs you posted from the FRX failures don't really give me much to go off of either, unfortunately.
Click to expand...
Click to collapse
Today I tested different kernels using GBX0C and found out the following:
2.6.27.46(original GBX0C) - boots up
2.6.39.3 - boots up - Buttons / keyboard not functioning correctly
3.0.18 - boots up - buttons / keyboard not functioning correctly
3.3.8 - Not booting - Stuck on calibration (message: X & Y the same)
3.4.3 - Not booting - Stuck on calibration (message: X & Y the same)
Hope I did it right, replaced the zimage and module with every kernel switch. Also created a new data.img every time.
Cheers,
Alchedin
Alchedin said:
Today I tested different kernels using GBX0C and found out the following:
2.6.27.46(original GBX0C) - boots up
2.6.39.3 - boots up - Buttons / keyboard not functioning correctly
3.0.18 - boots up - buttons / keyboard not functioning correctly
3.3.8 - Not booting - Stuck on calibration (message: X & Y the same)
3.4.3 - Not booting - Stuck on calibration (message: X & Y the same)
Hope I did it right, replaced the zimage and module with every kernel switch. Also created a new data.img every time.
Cheers,
Alchedin
Click to expand...
Click to collapse
Sounds like for one reason or another, your device is different from all other RHOD's. There seems to be an infinite number of RHOD100 variants, and supporting all of them equally is impossible.
Unfortunately you're going to have to troubleshoot these issues. We don't have a lot of devs left, and without having the device in hand, it makes such development 1,000x harder. Good luck.
arrrghhh said:
Sounds like for one reason or another, your device is different from all other RHOD's. There seems to be an infinite number of RHOD100 variants, and supporting all of them equally is impossible.
Unfortunately you're going to have to troubleshoot these issues. We don't have a lot of devs left, and without having the device in hand, it makes such development 1,000x harder. Good luck.
Click to expand...
Click to collapse
If I supply you with the information you need through video, logs, dmesg, logcat etc. you can implement it correct? Too bad you're in the USA so shipping it will be costly.
Walter79 lives in Germany which country is next to where I live, maybe he can/is willing to extract the required info from the phone? I'm willing to go the extra mile if it helps the whole TP2 community.
Thanks a lot anyway :good:
Cheers,
Alchedin
Alchedin said:
Today I tested different kernels using GBX0C and found out the following:
2.6.27.46(original GBX0C) - boots up
2.6.39.3 - boots up - Buttons / keyboard not functioning correctly
3.0.18 - boots up - buttons / keyboard not functioning correctly
3.3.8 - Not booting - Stuck on calibration (message: X & Y the same)
3.4.3 - Not booting - Stuck on calibration (message: X & Y the same)
Hope I did it right, replaced the zimage and module with every kernel switch. Also created a new data.img every time.
Cheers,
Alchedin
Click to expand...
Click to collapse
Have you tried plugging a known working calibration file into the rom and using the kernels that are giving a calibration error?
Alchedin said:
If I supply you with the information you need through video, logs, dmesg, logcat etc. you can implement it correct? Too bad you're in the USA so shipping it will be costly.
Walter79 lives in Germany which country is next to where I live, maybe he can/is willing to extract the required info from the phone? I'm willing to go the extra mile if it helps the whole TP2 community.
Thanks a lot anyway :good:
Cheers,
Alchedin
Click to expand...
Click to collapse
I would not be a good candidate as I am far from a developer. As I stated previously, we don't really have any devs actively working on the project. walter79 just created the CM build, unfortunately he was not part of the original XDAndroid development team.
Again, your phone seems like it is a one-off, and development efforts for a one-off device are always difficult. I'd say you're going to have to pick up the effort yourself, or be happy with where the development is left at.
wizardknight said:
Have you tried plugging a known working calibration file into the rom and using the kernels that are giving a calibration error?
Click to expand...
Click to collapse
I used the same ts-calibration file that was created during the first boot of gbx0c. Like I stated earlier, I only replaced/removed the zimage, module and data.img file every time I switched kernel.
Should I also re-calibrate every time when switching kernels?
arrrghhh said:
I would not be a good candidate as I am far from a developer. As I stated previously, we don't really have any devs actively working on the project. walter79 just created the CM build, unfortunately he was not part of the original XDAndroid development team.
Again, your phone seems like it is a one-off, and development efforts for a one-off device are always difficult. I'd say you're going to have to pick up the effort yourself, or be happy with where the development is left at.
Click to expand...
Click to collapse
Many thanks for your interest and pointers arrrghhh, I will look into kernel stuff and such, maybe i'll get some of it working :fingers-crossed:
I have little to no development/linux/android skills but I can at least try to learn it.
Cheers
P.S: In a earlier stage playing around with NAND builds I managed to use the boot.img of the CM9-ICS_X1_testbuild1 in combination with the CM7.2 of walter79 and got it running in landscape mode, if this worked for me I can go from there.
Bit by bit i'm getting a hang of it.
Alchedin said:
Should I also re-calibrate every time when switching kernels?
Click to expand...
Click to collapse
No, as I state in all my threads about calibration - once you get a good calibration file, save 15,000 copies of it and re-use it constantly. There's no need to constantly recalibrate.
Ok here we go, sorry for the big read..
I hope I can be as precise as possible. This is about the NAND builds i've tested.
I installed ICS like in my last post again and made a CWM backup of the whole phone.
After this I did a new task29 and reflashed everything till I got back into CWM.
This time I installed the OMGB stable release with the kernelpatch + gapps.(seems the most advised build) Factory reset/data/cache/etc just to be sure.
Rebooted the device and let OMGB do it's thing, thus resulting in a kernel panic - can not sync issue. This is clearly a default message on this phone which I am in peace with. (log1)
Now for the fun part, I had this ICS testbuild backup up earlier and only did a restore of the boot part. Cleared the data/cache/etc again and rebooted.
This time it just boots fine into OMGB... (log2) previous attempts resulted in a landscape layout which i wasn't able to adjust myself, but this time I got the portrait mode correct! The only part which isn't working is the keyboard and hardware buttons.
Seems the "default" startup process is hanging in the part of the AudioFlinger? I compared the 2 logs but I can't see anything really which normally would result in a kernel panic.
Attached are the logs for the default OMGB boot (log1.txt) and the ICS modified boot + OMGB system (log2.txt)
Is this still different from any other Rhod100 or just a small adjustment? If this is really unknown I will break the phone to pieces and give up on it :silly:
I'll keep this config on the phone a bit longer since data and phone is working.
Thanks for reading
Cheers
-No sound
[Update]
Made a finding myself, the problem for my phone lies within the libhtc_acoustic.so removing this file made NAND boot up for the first time on this phone. Now looking for a compatible acoustic replacement which generates sound.
Going to try copying/pushing the file from FRX0.7 to NAND CM7.2 and see what it does. Including replacing my csv's from WinMo in the /system/etc folder.
[Update2]
Installed CM7.2 2.6.27 version today and used the FRX0.7 aucoustic.so, which resulted in a perfectly working android without sound...
now going after the csv's, which I hope gets me sound.
arrrghhh said:
[snip]...
Again, your phone seems like it is a one-off, and development efforts for a one-off device are always difficult. I'd say you're going to have to pick up the effort yourself, or be happy with where the development is left at.
Click to expand...
Click to collapse
I did a bit myself yesterday and today, the problem lies in the libhtc_acoustic.so, removing only this file made nand boot for me finally. See above post.
Alchedin said:
I did a bit myself yesterday and today, the problem lies in the libhtc_acoustic.so, removing only this file made nand boot for me finally. See above post.
Click to expand...
Click to collapse
Hrm, perhaps the new acoustic code jb started and detule 'finished' if you will isn't compatible with your device.
I don't know 'why'... on GBX0C did you copy the CSV's from your phone? I don't know how that build worked for you, because OMGB uses the same acoustic code.
arrrghhh said:
Hrm, perhaps the new acoustic code jb started and detule 'finished' if you will isn't compatible with your device.
I don't know 'why'... on GBX0C did you copy the CSV's from your phone? I don't know how that build worked for you, because OMGB uses the same acoustic code.
Click to expand...
Click to collapse
The interesting parts were the updates I posted. I did copy the csv's from the WinMo earlier, which were instructed by you (using total commander and such), but can't remember if it did produced sound.
But then...
I switched over to NAND CM7.2 by Walter79 and replaced the csv's in the CM7.2 zip file at location /system/etc (audioparatable.csv etc.)
Also I used the libhtc_acoustic.so from here
And ADB pushed the .so into the /system/lib folder.
When running logcat I see that the csv's are used and the audio routing is ok, but still didn't produce sound. Thought there were some other locations were the csv's are stored which I will also replace with mine. But didn't get to that yet.
Just tinkering with files really.. that's as far as I can go since I'm no developer.
What you mean by "perhaps the new acoustic code jb started and detule 'finished' if you will isn't compatible with your device" ?
Alchedin said:
What you mean by "perhaps the new acoustic code jb started and detule 'finished' if you will isn't compatible with your device" ?
Click to expand...
Click to collapse
I don't know how else to phrase that...
Although, I might have misread your statement. I thought you said you replaced a lib from FRX07.1 - which wouldn't boot for you. GBX0C did boot, so it seems the new acoustic code actually helps your phone.
So now I'm not sure what the deal is. I know OMGB uses the new acoustic, and I was under the impression that the CM ROM did as well. Did you try GBX0*? Basically the NAND version of GBX0C.
I have the resurrection 5.8.0 installed (30 Dec build) and my phone takes about 5 minutes to boot. Initially it is stuck in the MI logo for about 4 minutes before the animation starts. I have used several ROMS and kernals and they all seem to do the same thing. I never had this issue with MIUI. Once the phone has booted, the phone is totally fine however I would prefer to identify and fix the problem. Any suggestions? I have already done a complete wipe, and tried various verions of TWRP with no joy. Thanks
I suggest you to flash the latest version of MIUI latest china dev, then from fastboot flash twrp, then clean flash rom + kernel. It takes about 30 minutes if you know what you're doing.
So basically restore then start from scratch? That did cross my mind... I will give it a go. Thanks. I will report back here.
ginohabibi said:
So basically restore then start from scratch? That did cross my mind... I will give it a go. Thanks. I will report back here.
Click to expand...
Click to collapse
Hi if you find a fix for this problem please share it with me, I tried latest china dev rom, latest global dev rom and latest global stable rom with all versions the boot time goes to 4-5 minutes...
ufoshop said:
Hi if you find a fix for this problem please share it with me, I tried latest china dev rom, latest global dev rom and latest global stable rom with all versions the boot time goes to 4-5 minutes...
Click to expand...
Click to collapse
Try method in my signature.. it should work for you
khajiit said:
Try method in my signature.. it should work for you
Click to expand...
Click to collapse
Where do i find that method?
https://forum.xda-developers.com/redmi-note-3/how-to/kate-guide-install-lineage-os-locked-t3546154
Alright, im going to try that method and i will report my results here.
Followed all the steps within your guide, but that guide didnt work and has nothing to do with our slowboot issue.
Hardware related then
ginohabibi said:
I have the resurrection 5.8.0 installed (30 Dec build) and my phone takes about 5 minutes to boot. Initially it is stuck in the MI logo for about 4 minutes before the animation starts. I have used several ROMS and kernals and they all seem to do the same thing. I never had this issue with MIUI. Once the phone has booted, the phone is totally fine however I would prefer to identify and fix the problem. Any suggestions? I have already done a complete wipe, and tried various verions of TWRP with no joy. Thanks
Click to expand...
Click to collapse
Didnt you change recently some parts of the phone? Like display/baterry and so...?
i think dat guy replaced display module
same problem here, touchscreen cant initialize on boot
4-5mins to go... all rooms.
to solve/ n - use old Santosh kernel, mm - use neon kernel, lp - elementalx
on this cores phone starts on 20-40s
and about recovery - use twrp+ 3.0.2-2 by mr_root
paladzin said:
i think dat guy replaced display module
same problem here, touchscreen cant initialize on boot
4-5mins to go... all rooms.
to solve/ n - use old Santosh kernel, mm - use neon kernel, lp - elementalx
on this cores phone starts on 20-40s
and about recovery - use twrp+ 3.0.2-2 by mr_root
Click to expand...
Click to collapse
So you say there is no solution to run the official rom without waiting 4-5 mins on boot, I have the phone from fastcardtech and maybe is a refurbished unit because they have very low prices compared to other resellers...the phone came in sealed box...
Dwnld links plzz..
Hay anybody here ...is there any other kernal for andriold n ROMs...
paladzin said:
i think dat guy replaced display module
same problem here, touchscreen cant initialize on boot
4-5mins to go... all rooms.
to solve/ n - use old Santosh kernel, mm - use neon kernel, lp - elementalx
on this cores phone starts on 20-40s
and about recovery - use twrp+ 3.0.2-2 by mr_root
Click to expand...
Click to collapse
Mine to, it 2 time I had to replace screen. I'll give a test right now and report back.
Im not using the device anymore, but i think i had to replace the screen like 3-4 times, its very fragile, even a drop from small height makes it crack. Also without case its very slippy device, but none of that matters. From the 4 displays i used, which all have been touchscreen + lcd + the frame (as i dont like to glue the display, i pay 10 dollars more and its better) had that exact same problem, which is very long waiting for the device to boot. The custom kernel solved it, but another (probably better quality) display does solve it too.
Hi,
I am running RR 5.8.3, v. from 23-04-17.
I was forced to set fluencetype for the past few flashes to null or something, because otherwise I did not have sound during calls.
Right now the call quality is unbearably bad. It was not THAT bad on older ROMs, before I had to disable this fluence-thingie.
I want to upgrade the ROM, but what else am I supposed to improve the voice quality? I could not find a decent source.
Factory reset -> VoLTE patch -> RR ROM -> GAPPS?
Anything else? Some people wrote "updade your firmware" - how am I supposed to interpret it? Install MIUI Rom? So, like flash it from TWRP and replace it with RR 2 minutes later? I am alergic to MIUI.
This topic kind of explains it, but links are down and content might be outdated:
https://forum.xda-developers.com/redmi-note-3/how-to/android-n-permanent-volte-fix-10000-t3541922
Up
Up.
Right now I am stuck on a bootloop with rom's logo. I can access TWRP and flash stuff just fine, but I cannot load the system. Restoring from backup has failed.
I have installed 7.7.7 firmware - https://www.androidfilehost.com/?fid=673368273298969813
and booted to the system. It did not recognize my PIN and locked my card. Unlocked it with PUK on another device, but still the same.
Flashed newest RR with GAPPS and reflashed the firmware. Bootlooping begun.
Tried different ROMs, tried a different firmware - https://www.androidfilehost.com/?fid=673368273298969055
What should be the "next step"?
I was able to fix it, but man this was my last flash of this device. My next step was to brick the device, had to start from stratch after that. Never had so many different issues... I will rot on current ROM till Pixel 2 arrives.
Hey guys! I recently downloaded Lineageos 14.1 Rom on my Meizu M2 Note, but after the upgrade, the sound volume is very low that i can barely hear anything from my earphones. I even googled this bug and founds out that After latest build? for 14.1 and 13.0 Lineageos has some kind of newest sound update that makes the sound more quiter. There were even 2 guides about fixing this.
The first one was by changing configurations in /device/etc/sound and changing to3g file, but sadly i do not have sound folder with to3g file.
The second one was by changing configurations in device/etc and changing this mixer_paths.xml file, but again i do not have it.
Is there any fix to this? because this low sound audio is annoying.
bump
emils2235 said:
Hey guys! I recently downloaded Lineageos 14.1 Rom on my Meizu M2 Note, but after the upgrade, the sound volume is very low that i can barely hear anything from my earphones. I even googled this bug and founds out that After latest build? for 14.1 and 13.0 Lineageos has some kind of newest sound update that makes the sound more quiter. There were even 2 guides about fixing this.
The first one was by changing configurations in /device/etc/sound and changing to3g file, but sadly i do not have sound folder with to3g file.
The second one was by changing configurations in device/etc and changing this mixer_paths.xml file, but again i do not have it.
Is there any fix to this? because this low sound audio is annoying.
Click to expand...
Click to collapse
Were you able to solve it? I'm the same situation. I don't have any of these folders or files... and it's really annoying
mdabar said:
Were you able to solve it? I'm the same situation. I don't have any of these folders or files... and it's really annoying
Click to expand...
Click to collapse
Nah, as much as i tried, unfortunately i couldn't solve it. Probably because it was custom rom idk really. I tried all the possible roms that i could use but no one didn't helped me to fix it. Later i tried to get back to stock rom, so i had to reinstall stock recovery. In the end I hard bricked my phone (completely dead, not a chance even by customer support because phones mobo died) Because of the stock recovery which i got Anyways i now have Xiaomi Redmi 4A, really cheap phone but at the same time even better than meizu m2 note. The only cons are that camera is bit worse, screen is smaller by .5 and screen can only support up to 720p. Anyways, maybe you could try to fix it by getting the phone to stock rom, but don't screw up like i did!
emils2235 said:
Nah, as much as i tried, unfortunately i couldn't solve it. Probably because it was custom rom idk really. I tried all the possible roms that i could use but no one didn't helped me to fix it. Later i tried to get back to stock rom, so i had to reinstall stock recovery. In the end I hard bricked my phone (completely dead, not a chance even by customer support because phones mobo died) Because of the stock recovery which i got Anyways i now have Xiaomi Redmi 4A, really cheap phone but at the same time even better than meizu m2 note. The only cons are that camera is bit worse, screen is smaller by .5 and screen can only support up to 720p. Anyways, maybe you could try to fix it by getting the phone to stock rom, but don't screw up like i did!
Click to expand...
Click to collapse
Thanks for your answer. I'm sorry you had the hard brick Did you trying re flashing everything with SP Flash Tools? It happened to me in the past and I was able to solve it with an old ROM v4.5 or so.
Now I'm with Lineage 14.1-20180523 and despite I followed all the steps (Magisk + Dolby...) The sound is still way too low :crying:
I've tried manually searching the files and sound config, but nothing, they're not. And even tried modifying some of the existing files related to volume... But no changes either.
So I'll keep looking and trying for the moment.
mdabar said:
Thanks for your answer. I'm sorry you had the hard brick Did you trying re flashing everything with SP Flash Tools? It happened to me in the past and I was able to solve it with an old ROM v4.5 or so.
Now I'm with Lineage 14.1-20180523 and despite I followed all the steps (Magisk + Dolby...) The sound is still way too low :crying:
I've tried manually searching the files and sound config, but nothing, they're not. And even tried modifying some of the existing files related to volume... But no changes either.
So I'll keep looking and trying for the moment.
Click to expand...
Click to collapse
Well, i did try to unbrick it, but since the mobo was dead, even the usb port didnt gave me any life. The phone was just bricked so bad that it wasn't possible to revive it. Atleast in my case. One thing that you could try is to check the motherboard of your phone(thats is if you are willing to) and see if you have anything damaged from the software. Because software can damage hardware. I was gonna say if you want you could actually change the motherboard with new replacement, but then it would probably ruin the Rom itself, because the system storage itself is built in the mobo. At this point im just clueless. Anyways good luck solving it!
emils2235 said:
Well, i did try to unbrick it, but since the mobo was dead, even the usb port didnt gave me any life. The phone was just bricked so bad that it wasn't possible to revive it. Atleast in my case. One thing that you could try is to check the motherboard of your phone(thats is if you are willing to) and see if you have anything damaged from the software. Because software can damage hardware. I was gonna say if you want you could actually change the motherboard with new replacement, but then it would probably ruin the Rom itself, because the system storage itself is built in the mobo. At this point im just clueless. Anyways good luck solving it!
Click to expand...
Click to collapse
At the end I could solve it by trying and trying...
Yesterday I found out that once I installed the last version of Magisk (the suggested one) it's when the some things didn't work properly. Following some other user advice I used an older version of Magisk.
Summary: with Magisk 16 I can download the Atmos package but cannot apply anything because the root was lost. With Magisk 14 the root works well, but then Atmos cannot be installed because of dependencies... finally Magisk 15.3 maintains the root and let you install and apply Atmos :highfive:
I just explained all that in case anyone else is having the same trouble.
Steps:
Install TWRP on your Meizu m2 Note
Install Lineage OS last version. I have 14.1-20180523 -> check here
Flash GAPPS (check your version on Open-GAPPS -> Arm64) -> here
Flash Magisk 14 (not a newer one! it lost the root for me) -> Magisk versions here
Wipe cache and Dalvik
Reboot the phone (it takes a few minutes)
Open Magisk (don't update it!) and check the root is ok, you can validate by opening ES Explorer or other app that asks for root permission
Reboot in recovery and flash Magisk 15.3
Wipe cache and Dalvik, it will take a few minutes again
Open Magisk (dont update!) and go to Modules (left menu)
Click on "+" and with the browser go to "Downloads"
Select the Atmos downloaded file, press and hold over the file until it's selected, then "Open" it. It will flash the version and reboot. You can download it from here
After Rebooting. Open "Audio FX" and disable it on top right. Then close the app.
Open "Dolby Atmos" enable the options you want/like and you'll see the difference
Are their any projects related to the Oukitel K9 phone? I purchased one and use it on the AT&T network here in the USA.
The phone is decent but the built in Android is very generic and buggy.
I would love to unlock the potential of this phone with a custom ROM.
Let me know if this isn't the right place to ask and point me in the right direction!
Lannie
No custom roms at this time, why bother when you can custom Android 9 using Magisk , Xposed and Substratum. Although having a Lineage 17 would be nice.
I ask because the Android on this phone is so buggy and lacking features. I don't see how the options you gave will add features I need. They might as I'm new to these apps and don't know much about them.
lschafroth2 said:
I ask because the Android on this phone is so buggy and lacking features. I don't see how the options you gave will add features I need. They might as I'm new to these apps and don't know much about them.
Click to expand...
Click to collapse
If you private message me I cannot get to the messages here. If I click on messages it takes me to the register or reset password every time. I have no way to read them.
At this point it's useless to try since the mediatek drivers no longer work on Windows 10. Not a single guide on installing on Windows 10 64 bit work anymore. If anyone knows how to get the Oukitel drivers to work, let me know. No amount of driver sign or advanced boot works. Every time I plug in the phone it says the previous device malfunctioned.
It worked once and I have never connected the phone since. Will not work.
lschafroth2 said:
At this point it's useless to try since the mediatek drivers no longer work on Windows 10. Not a single guide on installing on Windows 10 64 bit work anymore. If anyone knows how to get the Oukitel drivers to work, let me know. No amount of driver sign or advanced boot works. Every time I plug in the phone it says the previous device malfunctioned.
It worked once and I have never connected the phone since. Will not work.
Click to expand...
Click to collapse
This might seem obvious, but could never get my PC (Windows10 64bit) to even recognize my Oukitel K9 until I (out of desperation, and to try to prove a point to someone) reinstalled Minimal ADB & Fastboot 1.4.3 from here:
https://androidmtk.com/download-minimal-adb-and-fastboot-tool
It's the same thing I had previously installed, and I didn't expect it to suddenly/miraculously start working, but it did.
I'll pm you.
lschafroth2 said:
Are their any projects related to the Oukitel K9 phone? I purchased one and use it on the AT&T network here in the USA.
The phone is decent but the built in Android is very generic and buggy.
I would love to unlock the potential of this phone with a custom ROM.
Let me know if this isn't the right place to ask and point me in the right direction!
Lannie
Click to expand...
Click to collapse
Best rom floss october edition with buildprop tweaks transformed this phone into next level. Thanks to phherguson
nation888888 said:
Best rom floss october edition with buildprop tweaks transformed this phone into next level. Thanks to phherguson
Click to expand...
Click to collapse
Thanks, but I sold this phone and went to a Pixel 4 XL. I needed something reliable and InTune refused to work on the old Oukitel.
Has anyone worked out ramdisk partition for Magisk?
Discovery,
Thanks to Phh has developed the perfect ROM for the Oukitel K9. Strangely I have had to try many ROMs to find the perfect one. The Lineage ROM; I had GPS issues, the Recent app button not working, and signal loss. Wanted the latest OS and this one is the winner below.
https://github.com/phhusson/treble_experimentations/releases/download/v400.e/system-squeak-arm64-ab-vndklite-gapps-secure.img.xz
Llevo un par de semanas probando la rom y no funciona el detector de huellas,se puede mejorar?hay alguna rom(Android 12) mas estable y que todo funcione?,gracias
MOD Edit: I've been testing the rom for a couple of weeks and the fingerprint sensor doesn't work, can it be improved? Is there a more stable rom (Android 12) that makes everything work? Thanks
Try the updated version https://github.com/phhusson/treble_experimentations/releases/tag/v402
Should resolve the fingerprint issue. I have also tried the AOSP 12.1 v410 and the result is the phone goes into a boot loop. Not sure why when the previous version installs so easily. I have built a custom TWRP 3.6.1 and will be trying it soon. The reason why we need to update; that the TWRP 3.3.1 version is limited and could be the reason why there are install issues with some GSIs out there. The encryption keeps reactivating even if I use scripts, flash no verify-verity. Hopefully, this will work. I'm enjoying the new version too much to start again I will keep you posted.
This one is supreme V411 and distracts me away from my Note 20 Ultra. https://github.com/phhusson/treble_experimentations/releases/tag/v411 .Works well with the Oukitel K9, recommend to use swapram module for boosting memory 4gb to 8gb. Searching for a working TWRP 3.6.
nation888888 said:
This one is supreme V411 and distracts me away from my Note 20 Ultra. https://github.com/phhusson/treble_experimentations/releases/tag/v411 .Works well with the Oukitel K9, recommend to use swapram module for boosting memory 4gb to 8gb. Searching for a working TWRP 3.6.
Click to expand...
Click to collapse
Have you found better rom for k9? I've used several gsi images but system is very laggy. Yet to find a good fast custom rom for k9.
[email protected]@ said:
Have you found better rom for k9? I've used several gsi images but system is very laggy. Yet to find a good fast custom rom for k9.
Click to expand...
Click to collapse
I found this one is the best;
https://www.mediafire.com/file/74b5bgfu0vsjcvg/CherishOS_A13-arm64-bgS-slim_20221121.img.xz/file
nation888888 said:
I found this one is the best;
https://www.mediafire.com/file/74b5bgfu0vsjcvg/CherishOS_A13-arm64-bgS-slim_20221121.img.xz/file
Click to expand...
Click to collapse
Thanks a lot. I will give it a try!
nation888888 said:
I found this one is the best;
https://www.mediafire.com/file/74b5bgfu0vsjcvg/CherishOS_A13-arm64-bgS-slim_20221121.img.xz/file
Click to expand...
Click to collapse
I've flashed this one and found it is as laggy as CrDroid. I thought it might be due to not wiping data before flashing. Decided to reboot to recovery to wipe data. And.. phone stuck at twrp logo. No go further. Do you have any better TWRP than mine 3.3.1?
Try using the "Yet another Kernel Tweaker" module in Magisk. Through all my searches I could only find the TWRP 3.3.1. Tried building using kitchen but failed. Sometimes the TWRP will take up to 5 to 10 minutes, remember it is trying to decrypt. If it takes longer then SPflash, assuming done correctly with vbmeta. After the initial install the updates and synchronization starts processing. This causes a slow-down. I thought the same. Leave the device for a day to update and synchronize then should be faster.
nation888888 said:
Try using the "Yet another Kernel Tweaker" module in Magisk. Through all my searches I could only find the TWRP 3.3.1. Tried building using kitchen but failed. Sometimes the TWRP will take up to 5 to 10 minutes, remember it is trying to decrypt. If it takes longer then SPflash, assuming done correctly with vbmeta. After the initial install the updates and synchronization starts processing. This causes a slow-down. I thought the same. Leave the device for a day to update and synchronize then should be faster.
Click to expand...
Click to collapse
TWRP logo is for hours here.
Now I can't even enter fastboot after I've chosen reboot to recovery from cherishos power menu.
I hit volup+pwr and boot menu doesn't even show up. Tried 20+ times already.
I'm stuck. The last hope is to wait for it to discharge on twrp logo and try my luck with fastboot menu again.
Otherwise I have no idea. Now I question myself why on Earth I would even try to better something that works at least average ))))
nation888888 said:
Try using the "Yet another Kernel Tweaker" module in Magisk. Through all my searches I could only find the TWRP 3.3.1. Tried building using kitchen but failed. Sometimes the TWRP will take up to 5 to 10 minutes, remember it is trying to decrypt. If it takes longer then SPflash, assuming done correctly with vbmeta. After the initial install the updates and synchronization starts processing. This causes a slow-down. I thought the same. Leave the device for a day to update and synchronize then should be faster.
Click to expand...
Click to collapse
I've managed to revive it. But still on cherishos and few other A13 roms screen is flickering. Have you got something like that?