Related
Im currently upgrading my 4.4.4 to a 6.0, to be exact, I use the Kali Nethunter ROM, however I ran into trouble, since it requires a CM 13 as a template. The problem is the following : no matter how many times I've tried, the TWRP just don't want to install the only CM 13 image I could found (which is to be exact a Lineage 13 17-06-10 by kutep0v)
The TWRP-s I've used are ranging from 3.1.2.0 to the last tried and often mentioned 2.8.7.0
The exact model is a bacon with 64GB
And also I use the bacon root toolkit by wugfresh
The two possible cause of this was pointed out in certain other forums said that, there either is a compatibility error with the firmware (which currently displays : UNKNOW, and neither the wifi or sim card is working), or the twrp reads a compatibility error with the image (somehow doesn't gets that A0001 is the same as bacon) I downloaded (there were a forum post about a custom modified twrp, which fixes this error, but the link is broken, and the forum article has been closed in 2015)
Could someone link me the proper firmwares for the Lineage (or CM) 13, and the proper TWRP, which are validated to be working with together?
Or any other thoughts would be helpful
randoomkiller said:
Im currently upgrading my 4.4.4 to a 6.0, to be exact, I use the Kali Nethunter ROM, however I ran into trouble, since it requires a CM 13 as a template. The problem is the following : no matter how many times I've tried, the TWRP just don't want to install the only CM 13 image I could found (which is to be exact a Lineage 13 17-06-10 by kutep0v)
The TWRP-s I've used are ranging from 3.1.2.0 to the last tried and often mentioned 2.8.7.0
The exact model is a bacon with 64GB
And also I use the bacon root toolkit by wugfresh
The two possible cause of this was pointed out in certain other forums said that, there either is a compatibility error with the firmware (which currently displays : UNKNOW, and neither the wifi or sim card is working), or the twrp reads a compatibility error with the image (somehow doesn't gets that A0001 is the same as bacon) I downloaded (there were a forum post about a custom modified twrp, which fixes this error, but the link is broken, and the forum article has been closed in 2015)
Could someone link me the proper firmwares for the Lineage (or CM) 13, and the proper TWRP, which are validated to be working with together?
Or any other thoughts would be helpful
Click to expand...
Click to collapse
Since you're on KitKat,you need to flash new firmware in order to flash any newer android version ROM.
https://www.androidfilehost.com/?fid=24389512218018449
Wipe everything except internal storage,then flash the firmware,then the ROM and then gapps(optional) and reboot.
About recovery,official twrp will work fine,
https://dl.twrp.me/bacon/
Edit-AFAIK,Kali Nethunter only works with cm 12.1 build as of now as mentioned in the latest thread about Kali nethunter.
Mr.Ak said:
Since you're on KitKat,you need to flash new firmware in order to flash any newer android version ROM.
link
Wipe everything except internal storage,then flash the firmware,then the ROM and then gapps(optional) and reboot.
About recovery,official twrp will work fine,
link
Edit-AFAIK,Kali Nethunter only works with cm 12.1 build as of now as mentioned in the latest thread about Kali nethunter.
Click to expand...
Click to collapse
Update I : I just hard bricked it, so I have to rebuilt the whole from scratch (color os and stuff, probably the firmware is wrong too) I had 5.1, but the mobile network somehow didnt worked for me, and I wanted to downgrade to the previously used 4.4, unfortunately not from twrp but just simple flashing, and it somehow did not responded after a certain amount of time. (that won't be a problem)
BUT, I'm sorry to say that, but you are wrong
there are official builds for CM 13 / Marshmallow
they just don't update the main page
look at here : github slash offensive-security slash kali-nethunter slash wiki (sorry, newcomer and I cant post a proper link )in the builds you can find official and nightly packages for it (I can install the kernel, and when I want to install the whole package of marshmallow kali, it says, 'please install a regular Android system first')
that works far better than the Lineage or CM 13, and those are the problematic ones(with the firmware), not the Kali
randoomkiller said:
Update I : I just hard bricked it, so I have to rebuilt the whole from scratch (color os and stuff, probably the firmware is wrong too) I had 5.1, but the mobile network somehow didnt worked for me, and I wanted to downgrade to the previously used 4.4, unfortunately not from twrp but just simple flashing, and it somehow did not responded after a certain amount of time. (that won't be a problem)
BUT, I'm sorry to say that, but you are wrong
there are official builds for CM 13 / Marshmallow
they just don't update the main page
look at here : github slash offensive-security slash kali-nethunter slash wiki (sorry, newcomer and I cant post a proper link )in the builds you can find official and nightly packages for it (I can install the kernel, and when I want to install the whole package of marshmallow kali, it says, 'please install a regular Android system first')
that works far better than the Lineage or CM 13, and those are the problematic ones(with the firmware), not the Kali
Click to expand...
Click to collapse
Good...
Mr.Ak said:
Good...
Click to expand...
Click to collapse
Okay, so since (at least in my opinion) the bottleneck is the CM 13 / Lineage 13, do you have any experience with it?
could you give me a fine working firmware and ROM combo please?
I'll have no problem unbricking it, and after that I'll probably solve the kali installation (since its documented, and seems like working), but due broken links I can't really get the recommended ones at github
Mr.Ak said:
Since you're on KitKat,you need to flash new firmware in order to flash any newer android version ROM.
https://www.androidfilehost.com/?fid=24389512218018449
Wipe everything except internal storage,then flash the firmware,then the ROM and then gapps(optional) and reboot.
About recovery,official twrp will work fine,
https://dl.twrp.me/bacon/
Edit-AFAIK,Kali Nethunter only works with cm 12.1 build as of now as mentioned in the latest thread about Kali nethunter.
Click to expand...
Click to collapse
randoomkiller said:
Okay, so since (at least in my opinion) the bottleneck is the CM 13 / Lineage 13, do you have any experience with it?
could you give me a fine working firmware and ROM combo please?
I'll have no problem unbricking it, and after that I'll probably solve the kali installation (since its documented, and seems like working), but due broken links I can't really get the recommended ones at github
Click to expand...
Click to collapse
This...
Oh, thank you.
I just didn't realised, sorry for that.
BTW do you have any idea why does my opo is undetectable for everything I've tried?
How I hard bricked was the following :
Bacon toolkit, Downgrading to Kitkat
the console was writing the stuff it flashed to the device, and suddenly stopped and said <waiting for device>
after that, nothing
I unplugged after 15 mins, and after that the only lifesign was that, it got how when I plugged it charging (not too hot, just the standard "oneplus one is charging" hot)
I have an xp machine with the proper drivers and the rescue toolkit, but it cannot detect, not even as an unrecognizable usb device which lacks driver
I think the bottleneck is the phone now, but I just don't know what should I do
randoomkiller said:
Oh, thank you.
I just didn't realised, sorry for that.
BTW do you have any idea why does my opo is undetectable for everything I've tried?
How I hard bricked was the following :
Bacon toolkit, Downgrading to Kitkat
the console was writing the stuff it flashed to the device, and suddenly stopped and said <waiting for device>
after that, nothing
I unplugged after 15 mins, and after that the only lifesign was that, it got how when I plugged it charging (not too hot, just the standard "oneplus one is charging" hot)
I have an xp machine with the proper drivers and the rescue toolkit, but it cannot detect, not even as an unrecognizable usb device which lacks driver
I think the bottleneck is the phone now, but I just don't know what should I do
Click to expand...
Click to collapse
Fastboot drivers are not installed correctly...try uninstalling and installing again.
Mr.Ak said:
Fastboot drivers are not installed correctly...try uninstalling and installing again.
Click to expand...
Click to collapse
That could be possible, however I've tried with at least 3 drivers on 2 laptops(Win10 and an old XP), and neither picked it up even as an unrecognisable device (So basically there is literally no difference wheter I plug in or not plug in, from the computers view, or at least I didn't find it at the device manager, neither was there an alert of a device not recognisable). The drivers were :
- QUD.WIN.1.1 10037.3 - Latest from androidbrick
- Driver from colorOS
- The one I've been using before bricking it (and I had no problem with it before)
I've been digging up threads, and the only one I could find so far, where the device wasnt recognised even as an unrecognisable device was due a discharged battery.
randoomkiller said:
That could be possible, however I've tried with at least 3 drivers on 2 laptops(Win10 and an old XP), and neither picked it up even as an unrecognisable device (So basically there is literally no difference wheter I plug in or not plug in, from the computers view, or at least I didn't find it at the device manager, neither was there an alert of a device not recognisable). The drivers were :
- QUD.WIN.1.1 10037.3 - Latest from androidbrick
- Driver from colorOS
- The one I've been using before bricking it (and I had no problem with it before)
I've been digging up threads, and the only one I could find so far, where the device wasnt recognised even as an unrecognisable device was due a discharged battery.
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?t=2588979
Try this.
Update :
a friend of mine had an OPO to sell for ~100 USD, so to have a working phone, I bought that
it had Lineage 14.1, with firmware 0241, and TWRP, BUT, when I've tried to install the lineage 13, it said the same error 7
I've updated its firmware to 0011, and same thing happened, error 7 when I've tried to install lineage 13
now its on a factory reset lineage 14.1
maybe my image is bad
any idea where could I find the CM 13 or lineage 13?
and also I've tried the old phone with the adb drivers you've suggested, but no update with that one
randoomkiller said:
Update :
a friend of mine had an OPO to sell for ~100 USD, so to have a working phone, I bought that
it had Lineage 14.1, with firmware 0241, and TWRP, BUT, when I've tried to install the lineage 13, it said the same error 7
I've updated its firmware to 0011, and same thing happened, error 7 when I've tried to install lineage 13
now its on a factory reset lineage 14.1
maybe my image is bad
any idea where could I find the CM 13 or lineage 13?
and also I've tried the old phone with the adb drivers you've suggested, but no update with that one
Click to expand...
Click to collapse
https://www.google.co.in/amp/s/foru.../rom-lineageos-13-0-oneplus-one-t3549203/amp/
Oh, then the problem is not with that
I've used the exact same
what do you thing, what would cause the error 7? how can I overcome with the problem, and finally install cm13? ( or at least some diagnostical features I should check to find the problem )
and do you have any idea what could I do with the bricked one?
randoomkiller said:
Oh, then the problem is not with that
I've used the exact same
what do you thing, what would cause the error 7? how can I overcome with the problem, and finally install cm13? ( or at least some diagnostical features I should check to find the problem )
and do you have any idea what could I do with the bricked one?
Click to expand...
Click to collapse
It's probably a bad download,redownload the zip.
About the bricked one,you have to figure out the fastboot drivers issue.
This is a list of Nougat ROMs for this device and it's clones.
The list will be in the following format:
ROM : Version : Device : Tested/Untested
LineageOS : 14.1 : MMXC5 / E481 : Untested
Resurrection Remix : 5.8.4 : MMXC5 / E481 : Tested
crDROID : v3.5 : MMXC5 / E481 : Tested
AOSGPX : 7.1.2 : MMXC5 / E481 : Untested
There are also ROMs for the Elephone P8000, however the first time I tried one I got into a bootloop. It could just have been that I didn't wipe my caches, or it could have been a fault in the ROM; nonetheless I haven't tried any others from that device.
I couldn't find any for other devices, let me know if you see others.
Here is the factory firmware, as according to this post (Direct Download).
Also, the stock recovery: Original Post | Direct Download.
Im currently running crDroid and I couldn't be happier. Runs far better than the original firmware and the useless marshmallow update.
elbastardo1 said:
Im currently running crDroid and I couldn't be happier. Runs far better than the original firmware and the useless marshmallow update.
Click to expand...
Click to collapse
Have you encountered any bugs with crDroid? Did screen on time and standby increase by any good margin because doze and other os optimizations? With stock I get 7hrs SOT with LTE half the day. 5hrs if Skype calls and such.
BereiBlue said:
Have you encountered any bugs with crDroid? Did screen on time and standby increase by any good margin because doze and other os optimizations? With stock I get 7hrs SOT with LTE half the day. 5hrs if Skype calls and such.
Click to expand...
Click to collapse
Only bug so far is the kill app button not working (long press the back button) and sometimes after reboot sim cards not being detected. Usually it corrects itself after a few minutes. If not, I'll just re-flash the fix
Battery gets drained pretty fast compared to lollipop, but then again I used lollipop with xposed, greenify and amplify.
elbastardo1 said:
Only bug so far is the kill app button... and sometimes after reboot sim cards not being detected...
Battery gets drained pretty fast compared to lollipop, but then again I used lollipop with xposed, greenify and amplify.
Click to expand...
Click to collapse
Happy to hear only minor bugs. I'm waiting on black Friday SD card to ship and then I'll be able to test too.
On lollipop all I needed to use was power nap to kill unwanted wake locks. I'll definitely try to get it to work because batter life is important to me. Only reason I'm upgrading is because of older exploits that stock didn't get updates for. Other than that stock with xposed is extremely stable for me.(30-60 days between reboots)
Do you know if crDroid is using stock lollipop kernel or is it a ported kernel? That would effect battery life greatly I suppose.
review of roms
Review time. Installed and tested these roms by wiping dalvik cache, system, data, cache and internal storage. Flashed ROM then gapps then "front camera flash" patch lastly flashed sim patch. Afterwards I wiped cache and dalvik cache again before rebooting. Once I had access to settings I disabled display live/night mode/blue filter for all ROMs.
All the roms tested used about 1GB of ram (and stock ROM being around <600MB.).
Resurrection Remix : 5.8.4 : Looks to me a part of this rom was made by another group of people that were not given credit.. Default browser loads the homepage of the other group. The system FM radio app was asking for root permission(denied it). Also it had email services running before I added any accounts can't remember this being the norm. Other than that this ROM ran the best in terms of speed and ui. Uninstalled because of security concerns.
LineageOS : 14.1 : This ROM has about the same speed as resurrection which is good but the ui stuttered/not smooth. Uninstalled because ported by same user as resurrection.
crDROID : v3.5 : This one ran the worse. It was slow and stuttered throughout the ui. Missed some customizations that Resurrection had so not sure why any one would want to use this instead.
AOSGPX : Didn't bother installing because last I heard they copied and pasted code from crDRoid.
At the end of the day I reverted back to stock because of security concerns. As well as having more ram available for apps. If I had more than one phone phone I would wireshark/test connections of the ROMs to confirm but I do not have. Hopfully this helps someone.
BereiBlue said:
Review time. Installed and tested these roms by wiping dalvik cache, system, data, cache and internal storage. Flashed ROM then gapps then "front camera flash" patch lastly flashed sim patch. Afterwards I wiped cache and dalvik cache again before rebooting. Once I had access to settings I disabled display live/night mode/blue filter for all ROMs.
All the roms tested used about 1GB of ram (and stock ROM being around <600MB.).
Resurrection Remix : 5.8.4 : Looks to me this was made by some Russians. Default browser loads RU homepage. The system FM radio app was asking for root permission(denied it). Also it had email services running before I added any accounts can't remember this being the norm. Other than that this ROM ran the best in terms of speed and ui. Uninstalled because of security concerns.
LineageOS : 14.1 : This ROM has about the same speed as resurrection which is good but the ui stuttered/not smooth. Uninstalled because ported by same user as resurrection.
crDROID : v3.5 : This one ran the worse. It was slow and stuttered throughout the ui. Missed some customizations that Resurrection had so not sure why any one would want to use this instead.
AOSGPX : Didn't bother installing because last I heard they copied and pasted code from crDRoid.
At the end of the day I reverted back to stock because of security concerns. As well as having more ram available for apps. If I had more than one phone phone I would wireshark/test connections of the ROMs to confirm but I do not have. Hopfully this helps someone.
Click to expand...
Click to collapse
Just wondering with the ROM testing, did you disable the LiveDisplay nonsense? It drops my FPS to about 10, and is enabled by default.
Sorry, didn't read your whole post. I didn't find UI stuttering unless I enabled weird kernel stuff, or had L Speed installed.
Does anyone happen to know if any of these ROMs fix the problem that the official MM caused which was that all camera apps created a very dark image and took extremely dark photos?
tinpanalley said:
Does anyone happen to know if any of these ROMs fix the problem that the official MM caused which was that all camera apps created a very dark image and took extremely dark photos?
Click to expand...
Click to collapse
Im using crDroid and yes, it fixes it. That is one of the main reasons why I decided to keep it and got rid of Marshmallow.
elbastardo1 said:
Im using crDroid and yes, it fixes it. That is one of the main reasons why I decided to keep it and got rid of Marshmallow.
Click to expand...
Click to collapse
Hmm... sounds good. Any issues with that ROM? Slow downs, wonky USB port, minijack works ok, etc?
tinpanalley said:
Hmm... sounds good. Any issues with that ROM? Slow downs, wonky USB port, minijack works ok, etc?
Click to expand...
Click to collapse
sucktastic battery life (not like the original firmware was good to begin with) no compass (gmaps will point north regardless of your orientation) as soon as you install the google app (okay google!) the device will run a bit slower.
elbastardo1 said:
sucktastic battery life (not like the original firmware was good to begin with) no compass (gmaps will point north regardless of your orientation) as soon as you install the google app (okay google!) the device will run a bit slower.
Click to expand...
Click to collapse
Oh, ok... well in that case, that doesn't exactly help things. I'm gonna go back to Lollipop rooted to take out the bloatware. Can you recommend a way of doing that that is known to work well?
tinpanalley said:
Oh, ok... well in that case, that doesn't exactly help things. I'm gonna go back to Lollipop rooted to take out the bloatware. Can you recommend a way of doing that that is known to work well?
Click to expand...
Click to collapse
SP flash tool, scatter file and the original firmware (not a flashable zip). It's all in the original BLOX thread, buried somewhere there. Flash TWRP recovery using adb fastboot and flash super su with twrp recovery for root access.
elbastardo1 said:
SP flash tool, scatter file and the original firmware (not a flashable zip). It's all in the original BLOX thread, buried somewhere there. Flash TWRP recovery using adb fastboot and flash super su with twrp recovery for root access.
Click to expand...
Click to collapse
Wow, thorough, thanks. Don't know what half those things are but I'll look them up. I guess there's no way to go straight back to Lollipop without flashing a stock ROM. I mean, by rooting it now maybe and then downgrading or something?
tinpanalley said:
Wow, thorough, thanks. Don't know what half those things are but I'll look them up. I guess there's no way to go straight back to Lollipop without flashing a stock ROM. I mean, by rooting it now maybe and then downgrading or something?
Click to expand...
Click to collapse
You could flash a lollipop twrp backup, if anyone uploaded one or if you made one before. But if you don't have it, only way is by sp flash tool and original firmware (which is not a recovery flashable zip).
Been using the Crdroid rom for a few weeks now. Havn't had any lag or extreme battery issues. Im interested in trying the resurrection remix rom since it was tested to be the fastest, tho them security issues are kinda holding me back. One thing im lookin for is front camera flash and back aswell. on Crdroid u cannot toggle it in the camera app, tho the flash works.
Teblakuda4o4 said:
Been using the Crdroid rom for a few weeks now. Havn't had any lag or extreme battery issues. Im interested in trying the resurrection remix rom since it was tested to be the fastest, tho them security issues are kinda holding me back. One thing im lookin for is front camera flash and back aswell. on Crdroid u cannot toggle it in the camera app, tho the flash works.
Click to expand...
Click to collapse
What are these security issues people are mentioning? Isn't a ROM a ROM? I don't get it.
Also, if crDroid works fine, you could just try any other camera app. There are several that are quite good. I wish there were videos of crDroid.
tinpanalley said:
What are these security issues people are mentioning? Isn't a ROM a ROM? I don't get it.
Also, if crDroid works fine, you could just try any other camera app. There are several that are quite good. I wish there were videos of crDroid.
Click to expand...
Click to collapse
I mean with what's going on with Kaspersky being investigated for allowing certain trogens to work undetected and Kaspersky is own by Russians and since when does fm radio need root access.
Just a bit sketchy you know... But it could be just over-thinking it.
Teblakuda4o4 said:
I mean with what's going on with Kaspersky being investigated for allowing certain trogens to work undetected and Kaspersky is own by Russians and since when does fm radio need root access.
Just a bit sketchy you know... But it could be just over-thinking it.
Click to expand...
Click to collapse
I'd just not use the radio. [emoji4]
tinpanalley said:
I'd just not use the radio. [emoji4]
Click to expand...
Click to collapse
But the thing is you don't know what else has been tampered with.
As the title says, here's a list of some GSI's i have tested so far... but first for some story.
Bought the phone in summer, it's quite nice but has its own issues like no kernel source BUT since we can unlock the device and actually play around, oh boy it has been fun.
On the course of few hours and many downloads later I have a small list of GSI's that worked!
Every GSI I have mentioned REQUIRE device specific patch(es)!!!
For that you have to root.
----------------------WORKING GSI's-------------------------
BlissROM - It boots and functions quite fast
Cons: no included Gapps
Flashing any system editing patch results in "Phone is booting" homescreen.
https://sourceforge.net/projects/treblerom/files/BLESS/2020.09.21/
3.5 jack, VoLTE, Bluetooth, ComboFix patches are required, flash with Magisk manager
DO NOT USE FixLagSmooth
HavocOS 3.7 and 3.6 - Work and can be daily driven
3.6 requires FixLagSmooth patch
MUST root and apply all linked patches (don't use FixLagSmooth on 3.7, you can but no need)
https://forum.xda-developers.com/mi...rom-how-to-install-android-10-gsi-mi-t4126223
AOSP Android 10 based - Also does work and requires patching
https://forum.xda-developers.com/mi...rom-how-to-install-android-10-gsi-mi-t4126223
HydrogenOS Android 10 - Works
Has few bugs
No Google services
https://mirrors.lolinet.com/firmware/gsi/HydrogenOS/
----------------------COMMUNITY REPORTED GSI's-------------------------
Android 11 GSI - Reported to be functional by HumptyPotato47, thanks mate!
No Gapps as of now NikGapps exist for Android 11, search XDA for it!
Requires more testing...
https://github.com/phhusson/treble_experimentations/releases/tag/v300.f
----------------------MAYBE WORKING GSI's-------------------------
OxygenOS 10 GSI - Seems to work.. sorta
First boot after exiting fastboot causes the phone to reboot
Second boot will loop
https://mirrors.lolinet.com/firmware/gsi/OxygenOS/
----------------------NON FUNCTIONAL GSI's-------------------------
You tell me
...I did find a very nice list of GSI ROMs to try out more, here's the link:
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
----------------------FLASHING GSI-------------------------
If you test one then don't hesitate with replying which one, about the experience, bugs and how you installed it.
My method of installing was this:
1. Make sure to have the new adb commandline that supports fastbootd mode
2. Drop the GSI .img file in /adb directory for ease
3. Make sure you're running MIUI with unlocked bootloader and USB debugging enabled
3.5 MAKE SURE you get a GSI ROM with Gapps as existing TWRP isn't fully functional
4. GSI you should have must be AB partition!!!
Once all set then follow the next commands
>adb reboot bootloader
>fastboot -w
>fastboot reboot fastboot
>fastboot erase system
>fastboot flash system "GSI-ROM-name-without-quotes".img
>fastboot reboot bootloader
>fastboot reboot
----------------------SETTING UP GSI-------------------------
Once all that is complete it should boot, if not then that specific GSI does not work.
Also a thing worth mentioning! Whenever I boot this phone to fastbootd Windows keeps forgetting what driver it was which requires
few extra clicks in device manager to set it up for fastbootd use. Including an image with simple to follow instructions if you have the same issue.
>fastboot boot twrp.img
Once in TWRP you should be able to access internal storage with your computer, drag Magisk.zip over and flash. Don't forget to wipe cache!
If it boots normally then root was successful, now apply the linked patch and reboot once again. Since we are playing with GSI:
Head to Settings
Find Phh Treble Settings
Misc features
Check Disable audio effect. -- DISABLE IT AFTER PATCHING!!!
IMPORTANT!!! I only tested Havoc and Bliss for a long period, IF one of my mentioned GSI's or others require more patches then I have linked headphone jack and Bluetooth audio patches too.
Combo fix should do the trick thought so your mileage may vary.
----------------------HELP US-------------------------
IF you find more working GSI's then tell us and I will make sure to add them to the main post so it won't get clogged under other comments!
Update on 05.10.2020 GMT+3
Bliss ROM GSI
As only a day or two have passed I already encountered few issues.
> You cannot remove screenshot sounds, even when fully muted
> Data drain is something interesting I've noticed, consumption compared to MIUI is higher.
> When using the gesture navigation it is a bit buggy when using quick side swipe for multitasking.
Positive notes!
> It is stupid fast
> Battery life is good
> GCam is amazing
> 99% of the customization options work perfectly
> Fast charging modes and such work perfectly
Neutral stuff...
> No FOD, thanks for closed source
> whenever you take a picture or a screenshot and have Blutetooth audio connected, it pauses and plays out loud via speaker. No music leaks out
this phone is born dead, no developer cares about it.
alsartawi said:
this phone is born dead, no developer cares about it.
Click to expand...
Click to collapse
Sad truth but won't stop others from working on it. Eventually we might get a kernel source
Kevin Soosaar said:
Sad truth but won't stop others from working on it. Eventually we might get a kernel source
Click to expand...
Click to collapse
i would pay to see a stable custom rom for this phone, i really loved it.
alsartawi said:
i would pay to see a stable custom rom for this phone, I really loved it.
Click to expand...
Click to collapse
Havoc OS and Bliss ROM are both quite stable, albeit with Bliss you don't get Gapps which is a huge bummer to most users.
Personally I just installed MicroG services and use Aurora store with anonymous "account".
When I tried to flash Gapps with TWRP I ended up soft bricking ROM so it was required to restore stock and try again. Of course there's no need if you can still use fastbootd.
Kevin Soosaar said:
Havoc OS and Bliss ROM are both quite stable, albeit with Bliss you don't get Gapps which is a huge bummer to most users.
Personally I just installed MicroG services and use Aurora store with anonymous "account".
When I tried to flash Gapps with TWRP I ended up soft bricking ROM so it was required to restore stock and try again. Of course there's no need if you can still use fastbootd.
Click to expand...
Click to collapse
does FOD works on Havoc OS?
edit: sorry i just read that it's not working.
alsartawi said:
does FOD works on Havoc OS?
Click to expand...
Click to collapse
FOD is not working as the driver sources are not public, reverse engineering is not possible too afaik. Everything else works.
Should i send this phone back to Amazon?
Seriously, last night i bought it, thinking about to install some custom rom, but if there are no developers caring of it, i might returb the phone to the seller...
IMO MIUI EU is better then GSI roms. Everything works. Got rid of most chinese crap. You can use Magisk.
Have nice features (MIUI in general). The only thing i dont like -mine turns on WIFI byitself dotn know how it happens... but it happens when i sleep. china collecting logs?
https://www.scmp.com/abacus/tech/ar...earch-and-browsing-data-china-researcher-says
afigienas said:
IMO MIUI EU is better then GSI roms. Everything works. Got rid of most chinese crap. You can use Magisk.
Have nice features (MIUI in general). The only thing i dont like -mine turns on WIFI byitself dotn know how it happens... but it happens when i sleep. china collecting logs?
https://www.scmp.com/abacus/tech/ar...earch-and-browsing-data-china-researcher-says
Click to expand...
Click to collapse
Literally the main reason I made this post is to help others who are interested to use GSI ROM's on their devices. I do agree that MIUI has some decent features and I did use Xiaomu.eu before but it was so buggy. In the end I love customizing the device however I like it so MIUI is just not for me. Either way I might try to negotiate with Amazon to get a refund as touch and Bluetooth problems still persist. Fun fact, on Bliss the edge detection is pretty good and not as aggressive or straight out bad.
Simon_19 said:
Seriously, last night i bought it, thinking about to install some custom rom, but if there are no developers caring of it, i might returb the phone to the seller...
Click to expand...
Click to collapse
Actually there are plenty of people ready to build ROMs for Toco (Mi Note 10 Lite) and Tucana (Mi Note 10) but there just isn't any kernel source available. Making things worse is the cancelled release of Toco in India and we know that they are one of the biggest Android ROM builders next to Russians. No one there is gonna import a device like this because better phones for money exist. If you don't like it then yeah I recommend returning otherwise give GSI a try for now and see what happens.
You won't lose warranty as there is no E-fuse like on Samsung phones so locking bootloader and flashing back to stock is enough.
Is anyone try oos gsi ?
HumptyPotato47 said:
Android 11 GSI of phh is working fine. It is very smooth. But i switched back to miui because i can't find any android 11 gapps.
Click to expand...
Click to collapse
can you give the link of the rom?
HumptyPotato47 said:
Android 11 GSI of phh is working fine. It is very smooth. But i switched back to miui because i can't find any android 11 gapps.
Click to expand...
Click to collapse
Hi, there are gapps for Android 11, look for NikGapps here in XDA
Kevin Soosaar said:
Actually there are plenty of people ready to build ROMs for Toco (Mi Note 10 Lite) and Tucana (Mi Note 10) but there just isn't any kernel source available. Making things worse is the cancelled release of Toco in India and we know that they are one of the biggest Android ROM builders next to Russians. No one there is gonna import a device like this because better phones for money exist. If you don't like it then yeah I recommend returning otherwise give GSI a try for now and see what happens.
You won't lose warranty as there is no E-fuse like on Samsung phones so locking bootloader and flashing back to stock is enough.
Click to expand...
Click to collapse
who said its cancelled?
Dr. DoubtReaper said:
who said its cancelled?
Click to expand...
Click to collapse
The mentioned Mi Note 10 Lite for India was supposed to be called Mi 10i or something like that. It quickly disappeared and is not happening.
Of course I might be wrong by this date but looking for now there is no 10i, only speculation videos and threads.
Mi Note 10 Lite for India would've been code named "tocoin", same hardware and everything else so just a rebadge in old Xiaomi fashion... :laugh:
anyone tried new version of blissROM? feedback?
GaryFisher88 said:
anyone tried new version of blissROM? feedback?
Click to expand...
Click to collapse
Not sure if the one I linked is up do date, give it a try yourself as my device went in for warranty repairs.
Hello, I am currently using Xiaomi.eu based on MIUI 12 and I would like to know how to flash HAVOC OS GSI. Should I flash back to Global Rom then flash the GSI as indicated? Answer is greatly appreciated.
I just flashed Resurrection Remix ROM and then my wifi doesn't turn on and when I watch youtube videos no sound will come out from the speakers. Please help.
Mine doesn't work too. Tried Evolution X (10), Lineage (11), Nitrogen (11), Pixel Experience (10). Tried also flashing the original persist.img, none of them makes wifi work.
Hey guys, I found the solution to those of you who still haven't fixed it. You should be flashing a vendor image/Xiaomi Miui rom and then flashing the custom rom on top of it and everything should work from there. The instructions are somewhat unclear as wiping data on my end completely wiped the original vendor image/rom. Once you do that you should be golden.
The process to my understanding is
install vendor/miui rom
install custom rom
format data
and you should be fine
https://sourceforge.net/projects/nitrogen-project/files/surya/10.0/firmware+vendor/
If I'm too vague, please reply and I'll try clarifying it to the best of my ability.
ZenovajXD said:
install vendor/miui rom
install custom rom
format data
and you should be fine
https://sourceforge.net/projects/nitrogen-project/files/surya/10.0/firmware+vendor/
If I'm too vague, please reply and I'll try clarifying it to the best of my ability.
Click to expand...
Click to collapse
Unfortunately flashing NOS fw is sometimes not enough, at least for me I needed to flash whole xiaomi.eu rom and then it worked for me with steps you posted... After you flash xiaomi.eu rom you will have working wifi...
i try Lineage-OS 18 with your process and it worked
thanks
After researching and researchig and RESEARCHINNG, I have (I think) found the solution. I also do have this problem and I did not solve even until now (maybe tomorrow?). So here is my Story:
I flashed Lineage OS 14 by Dev. Andi on my Samsung Galaxy Tab 2 P5110. The custom ROM does work although sound and youtube videos don't. I downloaded build.prop editor from the PlayStore. I looked at it and it seems the audio has less properties than before. So I was like, "Let me try another ROM, it might work". Tried Oni ROM (something like that) and its faster than the Lineage OS ROM but can't play youtube videos and no AUDIO AGAIN! So I researched for about 5 hrs? Then so I concluded that I need to install the stock ROM of my device to basically regain all the audio and media properties on my device. I hope this helps and might work for me as well. Also, don't forget to backup your previous ROM so that if its fixed, try restoring it in Recovery Mode. That's all & thanks!
SoIomon said:
After researching and researchig and RESEARCHINNG, I have (I think) found the solution. I also do have this problem and I did not solve even until now (maybe tomorrow?). So here is my Story:
I flashed Lineage OS 14 by Dev. Andi on my Samsung Galaxy Tab 2 P5110. The custom ROM does work although sound and youtube videos don't. I downloaded build.prop editor from the PlayStore. I looked at it and it seems the audio has less properties than before. So I was like, "Let me try another ROM, it might work". Tried Oni ROM (something like that) and its faster than the Lineage OS ROM but can't play youtube videos and no AUDIO AGAIN! So I researched for about 5 hrs? Then so I concluded that I need to install the stock ROM of my device to basically regain all the audio and media properties on my device. I hope this helps and might work for me as well. Also, don't forget to backup your previous ROM so that if its fixed, try restoring it in Recovery Mode. That's all & thanks!
Click to expand...
Click to collapse
Wrong forum
its the same method as the Xiaomi phones
SoIomon said:
its the same method as the Xiaomi phones
Click to expand...
Click to collapse
Not really. People having problems with WiFi or audio on their X3 are using the wrong Vendor. Flashing the correct Vendor fixes the problem
Noter2017 said:
Not really. People having problems with WiFi or audio on their X3 are using the wrong Vendor. Flashing the correct Vendor fixes the problem
Click to expand...
Click to collapse
isn't that the point? I will go back to Stock ROM to retrieve all the properties I lost when I installed a Custom ROM.
not sure, but thats what works for me.
SoIomon said:
isn't that the point? I will go back to Stock ROM to retrieve all the properties I lost when I installed a Custom ROM.
Click to expand...
Click to collapse
I use a custom ROM and everything works. The opening post of each custom ROM actually tells you which firmware/vendor the ROM needs and when you use it, WiFi and audio and everything else will work.
it works now with what I did.
hi everyone, I am new to this forum.
i've been interested in rooting / mods for my old Samsung s9 to give it a new life.
I did so by rooting it using the TWRP app in combination with the Magisk V23.0
now what happened was that i was downloading some random apps yesterday and for some reason the phone went on bootloop...
i accidentally deleted the system without making a backup lol... a little stupid of me...
now it keeps telling me that i've no OS on my phone. i was thinking that i could easily find the ''un-edited'' or simple version of my original OS. but i've looked through many sites without succes.. either looks 2 good to be true or just fake...
is there anyone who can advise me on what to do? i just want my phone to work with any OS right now... but which one is the cleanest or best to use? i do prefer a newer os like 10
thanks in advance!
If you still have access to recovery mode, your best choice would probably be installing LineageOS. It's the most lightweight ROM and many ROMs are based on Lineage. From what i can see, your phone is no longer officially supported.
I found this one based on Lineage 18.1 (Android 11). Before installing, take a look at the bugs, working, and installing sections.
And don't forget to install the Google Apps after installing the system and before rebooting.
that looks crispy. i appreciate your quick & good advise. can you tell me wether i can still run Magisk on it?
Yes, you can still flash Magisk or any type of root with both the OS and the GApps.
what i'm consider about is, wether a region code CRC matters?