Hello people, having a nightmare, first time I've ever tried this, limited knowledge in this area so go easy on me please!
So far I have - bought an unlockable phone, unlocked bootloader, enabled developer options usb debugging, basically followed all the steps on the Jolla site - I have installed android-tools-fastboot on my linux PC, extracted the SFOS file, put the SW binaries package in the same folder, opened a terminal as root, and ran the bash command, it sees my phone, runs through the processes, and keeps getting stuck at the same place:
Code:
dave-desktop Sailfish_OS-Jolla-3.0.0.8-h3113-0.0.7.11-FIXED # bash ./flash.sh
Detected Linux
Searching device to flash..
Found 1 devices: CQ30009HG8
Fastboot command: fastboot -s CQ30009HG8
Flashing boot_a partition..
target reported max download size of 536870912 bytes
sending 'boot_a' (17772 KB)...
OKAY [ 0.438s]
writing 'boot_a'...
OKAY [ 0.000s]
finished. total time: 0.438s
Flashing boot_b partition..
< waiting for device >
target reported max download size of 536870912 bytes
sending 'boot_b' (17772 KB)...
OKAY [ 0.448s]
writing 'boot_b'...
OKAY [ 0.000s]
finished. total time: 0.449s
Flashing userdata partition..
< waiting for device >
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 2.869s]
sending sparse 'userdata' (514030 KB)...
OKAY [ 12.609s]
writing 'userdata'...
OKAY [ 0.000s]
sending sparse 'userdata' (513031 KB)...
OKAY [ 13.990s]
writing 'userdata'...
OKAY [ 0.000s]
sending sparse 'userdata' (76364 KB)...
OKAY [ 4.710s]
writing 'userdata'...
OKAY [ 0.000s]
finished. total time: 34.179s
Flashing system_b partition..
< waiting for device >
target reported max download size of 536870912 bytes
erasing 'system_b'...
OKAY [ 0.495s]
sending sparse 'system_b' (524284 KB)...
OKAY [ 13.166s]
writing 'system_b'...
OKAY [ 0.000s]
sending sparse 'system_b' (61308 KB)...
OKAY [ 18.020s]
writing 'system_b'...
OKAY [ 0.000s]
finished. total time: 31.681s
Flashing vendor_a partition..
< waiting for device >
target reported max download size of 536870912 bytes
sending 'vendor_a' (340 KB)...
OKAY [ 0.015s]
writing 'vendor_a'...
OKAY [ 0.001s]
finished. total time: 0.016s
Flashing vendor_b partition..
< waiting for device >
I have a thread here also, but I'm struggling to find an answer despite several suggestions and I'm out of my depth....... Can anyone help me please?
https://together.jolla.com/question/194868/help-installing-on-xa2-stuck-at-flashing-vendor_b-partition-waiting-for-device/
Often, such errors appear when using the wrong cable for PC connection, or computer USB port.
That's, why I still use my ancient Nokia N8 (SymbianOS) micro USB cable (+ adaptor micro -> c) for flashing phones. Second, use only USB 2 Ports directly connected to PC mainboard (rear ports on access plate). May be, this is difficult on recent machines...
dieterhaack said:
Often, such errors appear when using the wrong cable for PC connection, or computer USB port.
That's, why I still use my ancient Nokia N8 (SymbianOS) micro USB cable (+ adaptor micro -> c) for flashing phones. Second, use only USB 2 Ports directly connected to PC mainboard (rear ports on access plate). May be, this is difficult on recent machines...
Click to expand...
Click to collapse
Thank you so much for pointing that out ! That, along with updating the version of FASTBOOT I had on my machine (running an LTS distro that DID NOT HAVE the latest/up to date version) did the trick and I have now got sailfish 3 running on my XA2, you're a legend . . . . . . . .
first time .................. back of the net .................
daveinuk said:
Thank you so much for pointing that out ! That, along with updating the version of FASTBOOT I had on my machine (running an LTS distro that DID NOT HAVE the latest/up to date version) did the trick and I have now got sailfish 3 running on my XA2, you're a legend . . . . . . . .
first time .................. back of the net .................
Click to expand...
Click to collapse
So 6 Months on, are you still using Sailfish? Care to share some real world feedback?
bretto_aus said:
So 6 Months on, are you still using Sailfish? Care to share some real world feedback?
Click to expand...
Click to collapse
I've contributed to the together.jolla 'forum' a fair few times, I tend to read it more than participate now as I find myself moaning lol............
I love SFOS don't get me wrong, but the developement is just so painfully slow, and always has been. I knew it was a 'niche' OS when they started out. But I, I suspect, like a lot of others imagined this to be the answer to privacy concerns and data harvesting/mining, that I really loathe with a passion, targeted ad's and all that's tied with it really grind my gears . . . . . . And yet that said, I really love it on the XA2, it's smooth, slick, I still think it's got the best UI and I love the way it works and the fact I can nerd about with it and SSH seamlessly from my laptop or desktop,just cos' I can
It's apps, especially native where it's lacking, still, after 5 years of my use. This is where the android layer appeals, but a lot of us I assume bought into it, assuming the native app's wouldn't be too far down the road, but we were wrong, and we still have to rely on android apps for functionality. Paypal, Airdroid, Waze to name just 3 that have absolutely no comparable SFOS app, I can live with facebook et al via browser shortcuts and make do with this that and the other, but really we shouldn't 'have to'.
Android is a far better experience than I recall from 6 years ago before I got my first Jolla phone, and in the meantime I've had a Sony XperiaX, and now an XA2 Ultra, to use as my 'daily' because I do a lot of images, shared on a facebook page and insta, and I just can't achieve the same with the native SFOS app's as easily. Now then, I bought the XperiaX to flash SFOS on, before I found it wasn't actually rootable, so had to use it with android, and that opened my eyes to what I'd been missing, now the XA2 Ultra I have is unlockable, but I haven't flashed it yet - I now have a third phone - another Sony XA2, and I've flashed that with LineageOS for MicroG, and I'm liking it, but I'm only 3 days in ! (and a much easier flashing experience 2nd time round, getting used to it now)
I considered /e/ - eelo - but it meant buying a much more expensive device to 'try' it out, and I quite like Sony's, and they can be bought at very very reasonable prices. I've only been actively 'playing' with me SFOS phone for the last 6 months and through a couple of updates because initially due to battery/software issues, you'd have never have got a days use out of it, now it gets 4 days quite easily., so I'm using it, but still not as my ' daily driver ' .
I've decided to keep an eye on developements with SFOS but I'm slowly losing the will to be as excited as I used to be about it, they seem to be in this transitional period when they're now getting business, but through a differing business model, and fair play to the boys and girls there, it can't have been an easy ride, but, people won't wait forever to get a functional product, and believe me, I'm an angler, I know all about 'patience' . I thought the new direction might have brought in developers and app's from other contributors due to the open source(ish) nature, but it's not seemingly happening, and that's disappointing. I can't be arsed with all these patches and fixes people do, I wan't the phone to work without having to remember to stop/uninstall/reinstall crap everytime a system update comes, that's just not for me I'm afraid, but fair play to all that get what they want out of it by doing so.
Still, I've not given up on it yet, but I think like all long term relationships, sometimes one of us needs to 'take a break ' or get some space, so maybe I'll have a play with LineageOS for a while, maybe if I like it I'll flash the XA2 Ultra, but the cameras on sony's are good, so I'm undecided, or I might look at PostmarketOS, there's another interesting take on things . . . . . . . . I kind of said to myself after the SFOS3 update that I'd give it til the end of the year on this XA2 to see if any major changes come along that make the app environment much more appealing, but the way they seem to be, slow and seemingly not very communicative with the community, I won't hold my breath !
I don't want to bash SFOS, and I've always wanted it to be that one I told my mates about that were mad not to try, and be proved right, but dipping a toe in the 'other side' feels a bit like the taste of humble pie lol . . . . . . .
daveinuk said:
I've contributed to the together.jolla 'forum' a fair few times, I tend to read it more than participate now as I find myself moaning lol............
I love SFOS don't get me wrong, but the developement is just so painfully slow, and always has been. I knew it was a 'niche' OS when they started out. But I, I suspect, like a lot of others imagined this to be the answer to privacy concerns and data harvesting/mining, that I really loathe with a passion, targeted ad's and all that's tied with it really grind my gears . . . . . . And yet that said, I really love it on the XA2, it's smooth, slick, I still think it's got the best UI and I love the way it works and the fact I can nerd about with it and SSH seamlessly from my laptop or desktop,just cos' I can
It's apps, especially native where it's lacking, still, after 5 years of my use. This is where the android layer appeals, but a lot of us I assume bought into it, assuming the native app's wouldn't be too far down the road, but we were wrong, and we still have to rely on android apps for functionality. Paypal, Airdroid, Waze to name just 3 that have absolutely no comparable SFOS app, I can live with facebook et al via browser shortcuts and make do with this that and the other, but really we shouldn't 'have to'.
Android is a far better experience than I recall from 6 years ago before I got my first Jolla phone, and in the meantime I've had a Sony XperiaX, and now an XA2 Ultra, to use as my 'daily' because I do a lot of images, shared on a facebook page and insta, and I just can't achieve the same with the native SFOS app's as easily. Now then, I bought the XperiaX to flash SFOS on, before I found it wasn't actually rootable, so had to use it with android, and that opened my eyes to what I'd been missing, now the XA2 Ultra I have is unlockable, but I haven't flashed it yet - I now have a third phone - another Sony XA2, and I've flashed that with LineageOS for MicroG, and I'm liking it, but I'm only 3 days in ! (and a much easier flashing experience 2nd time round, getting used to it now)
I considered /e/ - eelo - but it meant buying a much more expensive device to 'try' it out, and I quite like Sony's, and they can be bought at very very reasonable prices. I've only been actively 'playing' with me SFOS phone for the last 6 months and through a couple of updates because initially due to battery/software issues, you'd have never have got a days use out of it, now it gets 4 days quite easily., so I'm using it, but still not as my ' daily driver ' .
I've decided to keep an eye on developements with SFOS but I'm slowly losing the will to be as excited as I used to be about it, they seem to be in this transitional period when they're now getting business, but through a differing business model, and fair play to the boys and girls there, it can't have been an easy ride, but, people won't wait forever to get a functional product, and believe me, I'm an angler, I know all about 'patience' . I thought the new direction might have brought in developers and app's from other contributors due to the open source(ish) nature, but it's not seemingly happening, and that's disappointing. I can't be arsed with all these patches and fixes people do, I wan't the phone to work without having to remember to stop/uninstall/reinstall crap everytime a system update comes, that's just not for me I'm afraid, but fair play to all that get what they want out of it by doing so.
Still, I've not given up on it yet, but I think like all long term relationships, sometimes one of us needs to 'take a break ' or get some space, so maybe I'll have a play with LineageOS for a while, maybe if I like it I'll flash the XA2 Ultra, but the cameras on sony's are good, so I'm undecided, or I might look at PostmarketOS, there's another interesting take on things . . . . . . . . I kind of said to myself after the SFOS3 update that I'd give it til the end of the year on this XA2 to see if any major changes come along that make the app environment much more appealing, but the way they seem to be, slow and seemingly not very communicative with the community, I won't hold my breath !
I don't want to bash SFOS, and I've always wanted it to be that one I told my mates about that were mad not to try, and be proved right, but dipping a toe in the 'other side' feels a bit like the taste of humble pie lol . . . . . . .
Click to expand...
Click to collapse
Just the response I was hoping for, cheers for the honest feedback. Much Appreciated.
I'm currently using /e/ as my daily driver rom and its working out pretty well, its smooth, gets OTA's without all the flashing/reflashing/backing up/reinstalling etc so it's good compromise between going full goolag android and a non-android alternative like SFOS I guess. Though I have always been quite curious to pick up a used XA2 (not ultra) to give SFOS a shot, then worst case I can always flash /e/ on it if it doesn't work out.
bretto_aus said:
Just the response I was hoping for, cheers for the honest feedback. Much Appreciated.
I'm currently using /e/ as my daily driver rom and its working out pretty well, its smooth, gets OTA's without all the flashing/reflashing/backing up/reinstalling etc so it's good compromise between going full goolag android and a non-android alternative like SFOS I guess. Though I have always been quite curious to pick up a used XA2 (not ultra) to give SFOS a shot, then worst case I can always flash /e/ on it if it doesn't work out.
Click to expand...
Click to collapse
No worries, I think my take on things is not too unusual after 5 or 6 years around SFOS and I see a number of people bemoaning the slow pace and lack of communication from Jolla HQ. I like to try and see both sides, and I think I do, but it's hard to keep up enthusiasm when the potential seems so great, but the pace doesn't match it. I liked the look of the Librem5 until I saw the spec's and the price, and I liked the look of /e/ until I saw the price lol . . . . . . So having the experience with Sony's tipped the scales for me as I'm (fairly) new to flashing ROM's so I figured it wasn't a great loss if I bricked one, but I've done good so far! Plus.......... if I don't take to an OS, as you said, you can reflash, such is the beauty of Linux based systems...... but I am rather liking LOS so far and discovering a few things I'd not looked at before like KDE connect, great little app. I might even download /e/ at some point and try it......... nothing ventured nothing gained as they say . . . . . . . .
I love SailfishOS too if you want you can get Google Play Services or use MicroG
---------- Post added at 07:13 PM ---------- Previous post was at 07:08 PM ----------
daveinuk said:
No worries, I think my take on things is not too unusual after 5 or 6 years around SFOS and I see a number of people bemoaning the slow pace and lack of communication from Jolla HQ. I like to try and see both sides, and I think I do, but it's hard to keep up enthusiasm when the potential seems so great, but the pace doesn't match it. I liked the look of the Librem5 until I saw the spec's and the price, and I liked the look of /e/ until I saw the price lol . . . . . . So having the experience with Sony's tipped the scales for me as I'm (fairly) new to flashing ROM's so I figured it wasn't a great loss if I bricked one, but I've done good so far! Plus.......... if I don't take to an OS, as you said, you can reflash, such is the beauty of Linux based systems...... but I am rather liking LOS so far and discovering a few things I'd not looked at before like KDE connect, great little app. I might even download /e/ at some point and try it......... nothing ventured nothing gained as they say . . . . . . . .
Click to expand...
Click to collapse
On SFOS exist a simmilar app it call SailfishConnect and you can get notices from your SFOS on computer with Linux. from 2-3 months I use KDE Neon and SailfishOS on my XA 2 and I don`t think that I back to android soon.
iHusky said:
I love SailfishOS too if you want you can get Google Play Services or use MicroG
---------- Post added at 07:13 PM ---------- Previous post was at 07:08 PM ----------
On SFOS exist a simmilar app it call SailfishConnect and you can get notices from your SFOS on computer with Linux. from 2-3 months I use KDE Neon and SailfishOS on my XA 2 and I don`t think that I back to android soon.
Click to expand...
Click to collapse
Cheers for that I'll look it up
daveinuk said:
No worries, I think my take on things is not too unusual after 5 or 6 years around SFOS and I see a number of people bemoaning the slow pace and lack of communication from Jolla HQ. I like to try and see both sides, and I think I do, but it's hard to keep up enthusiasm when the potential seems so great, but the pace doesn't match it. I liked the look of the Librem5 until I saw the spec's and the price, and I liked the look of /e/ until I saw the price lol . . . . . . So having the experience with Sony's tipped the scales for me as I'm (fairly) new to flashing ROM's so I figured it wasn't a great loss if I bricked one, but I've done good so far! Plus.......... if I don't take to an OS, as you said, you can reflash, such is the beauty of Linux based systems...... but I am rather liking LOS so far and discovering a few things I'd not looked at before like KDE connect, great little app. I might even download /e/ at some point and try it......... nothing ventured nothing gained as they say . . . . . . . .
Click to expand...
Click to collapse
Have taken the plunge and picked up a very decently price XA2 to give SFOS 3 a go. I still have /e/ on my other device (essential phone) as the /e/ eco system is quite good with e.drive sync/contacts/mail etc. Though its on v0.7 so still technically a beta till v1 but I don't have any issues. If I wasn't using /e/ and now SFOS I would likely use a lineage.microg.org build as its based on pie with microG and is a newer build for the essential which /e/ is still based on nougat (with pie coming soon I've heard). For the XA2 /e/ is currently Oreo based where as lineage.microg is Pie.
iHusky said:
I love SailfishOS too if you want you can get Google Play Services or use MicroG
---------- Post added at 07:13 PM ---------- Previous post was at 07:08 PM ----------
On SFOS exist a simmilar app it call SailfishConnect and you can get notices from your SFOS on computer with Linux. from 2-3 months I use KDE Neon and SailfishOS on my XA 2 and I don`t think that I back to android soon.
Click to expand...
Click to collapse
I would only consider using MicroG as I never plan on going back to the Goolag And thanks for the app recommendation :good:
Related
Hi,
I'm from http://forum.xda-developers.com/nex...3-10-zen1-dollar-drink-night-bfs-msm-t3062814 and also on the nexus 9
It's cool to see somebody has noticed -zen kernel in a far off community such as the find 7.
Somebody noticed I mentioned I'd support -zen on a few flagships in addition to the nexus devices.
I explained the hurdle of having 3rd party testing for such a daunting task. My BFS work on android/3.10 has yielded nothing but positive feedback on the N6 and the 64-bit N9.
However, somebody here reached out to me and said "hey support us, we are active but we don't have enough developers here"
I would happily do this but I have observed the find 7 is using a 3.4 kernel. In order to do the work with BFS I will likely have to reboot and flash to it dozens of times per hour, pull logs constantly, test all situations for kernel errors, etc.
Before you say "oh he just wants us to buy him a new phone sick son of a b*&$&$&$"
No not at all, what I need to bring Zen to the find7 (and likely other devices like the N5 and N7 - who I have maintainers for a future BFS patch already in place, they just need the patches) is anybody who is willing to volunteer any 3.4 Linux kernel running android device, with an unlocked bootloader
It can be broken, damaged, hold no charge as long as the screen is mostly legible and runs 3.4, unlocked bootloader, etc. I will probably need no more than 1-2 weeks with it, so if anybody volunteered I will happily send it back to them as soon as I'm done with it.
Somebody here asked me, I told them I can't possibly do it on 2nd hand testing (not that itnisnt greatly appreciated) but for a task like this it isn't ideal. if I get 1 hour to work it's much faster to just do itnall myself and flash maybe dozens of times versus sending test builds and waiting for reply and secondary logs, etc.
Thanks,
B
My endeavor to bring it to the nexus 9, which I do not own was successful but finding testers for that thing was basically impossible. Little interest and little users overall (I almost backed out but since I finished the patch for tegra I released it blindly and it works well)
Someone give this man some help! I want a custom kernel for my Find 7a.
Have you tried the oppo forums? I'd let you use mine if you're in the Chicago/north west Indiana area
wergrun said:
Have you tried the oppo forums? I'd let you use mine if you're in the Chicago/north west Indiana area
Click to expand...
Click to collapse
If he is not living there, would you send it if I would pay for the parcel (both ways)?
Just want to make this happen so badly but this is all I can do as I dont have a device on me I could send ):
znarf2369 said:
If he is not living there, would you send it if I would pay for the parcel (both ways)?
Just want to make this happen so badly but this is all I can do as I dont have a device on me I could send ):
Click to expand...
Click to collapse
I might but I'll need a backup device. Closest is an old beat up iPhone 3gs who's apps don't even work!
I'll try to find something cheap with an sdcard or rough it out for two weeks
wergrun said:
I might but I'll need a backup device. Closest is an old beat up iPhone 3gs who's apps don't even work!
I'll try to find something cheap with an sdcard or rough it out for two weeks
Click to expand...
Click to collapse
alright just let me know (;
Just to ask quickly, which ROMs would u support with ur kernel? I have tried CM12 and I am now on NamelessROM which I am loving.
I know some kernel DEVs only like to work for one ROM, or only for the stock OS of the device.
Thank u for wanting to work on our device, it seems like all the DEVs went for the OnePlus One, and everyone forgot about the blatantly better Oppo (lolz)
wergrun said:
I might but I'll need a backup device. Closest is an old beat up iPhone 3gs who's apps don't even work!
I'll try to find something cheap with an sdcard or rough it out for two weeks
Click to expand...
Click to collapse
found anything so far?
the problem is I really would like to help but my device I could send is in germany (relatively high costs for shipping to usa and back to germany, about 130 $) and I am located in New Zealand right now so even if I would I cant because I dont have any access to the phone..
i would love to test it for you!
I recently got the a520f after a few years with the iPhone. I was happy enough but then released there is 2 roms, 1 in alpha and another which is abandoned then noticed the updates from Samsung are sparse at best.
I'm unlocked in UK and stuck on 6.0.1, they "used" to say unlocked got updates first, noticed the way I said "used to" because carriers seem to be releasing 7.0 before unlocked, and while on the point 7.0 at this stage when Oreo will soon be released, even bringing the phone out with 7.0 would have been slow when 7.1 was available.
I am thinking I have made the wrong decision with the a520, Samsung are slow with updates anyway yes but the a520 seems to be at the bottom of Samsungs list of priorities. Last years a510 even has 7 for a while now.
hi !
Yes ,all people here want updates with another android version but i think that the most important thing is to enjoy with this phone :
it's a device with MM6 have enought power for to play game , it have the best super amoled screen ,it have a fabulous battery life ! , a fingerprints and "near" 20 differents sensors ,he have a good modem and hardware for 4G , this MM + sansung adds have all useful functions and parameters ....and the middle economic mode is impressive for the battery life...
The phone is receiving updates slowly cause the phone has owners all around the world, it's probably to make sure that OTA servers are not overloaded. Imagine what would happen if they released it at the same time for the whole world, the servers couldn't deliver acceptable speeds. That's just my guess though.
Nah, Samsung kinda sucks. I mean they couldnt make a proper working fingerprint sensor on stock MM, had to install nougat for the bloody thing to work.
aoyanagi said:
The phone is receiving updates slowly cause the phone has owners all around the world, it's probably to make sure that OTA servers are not overloaded. Imagine what would happen if they released it at the same time for the whole world, the servers couldn't deliver acceptable speeds. That's just my guess though.
Click to expand...
Click to collapse
How does Apple cope then?
That's Samsung decision to release update or not, as user we can wait for it or complaints to Samsung
Sent from my SM-A520F using Tapatalk
It has nothing to do with "the server not able to cope" or anything. There are a few reasons building up to the devices being in literally the bottom of the pile as you put it:
1) Samsung has heavily skinned Android with a lot of added features, which all take a while to port to a new verison.
2) Costs of development, Q/A testing and everything else that needs to be done before the update gets released public (not doing the update obviously means a lot of saved money)
3) Most people don't care about updates or are even annoyed by them and think they are something evil. That's excluding heavy updates to a new version which slow down the phone by a large margin with features you could have lived without (Apple are doing this), those updates really are evil. Due to the lack of updates though, this rarely happens on Android in all fairness.
4) It's a mid range price device
5) Samsung's policy of not wanting to update the phones too much anyway so the user buys a new one
The phone is probably going to be updated to 7.0 within the next month or two. I doubt extremely it will get updated to 8.0.
This is unacceptable for a phone that has come out for 2017, to not got an update of an OS to a version that is released in 2017 just a little over an year later. We should definetly not put up with it and complain to Samsung however, not on XDA.
We should make sure OEM's take note that we want our phones updated to new Android versions fast for at least a few years, just like iOS devices. And on top of complaining, we should vote with our wallets also. That gets the chain moving.
aoyanagi said:
The phone is receiving updates slowly cause the phone has owners all around the world, it's probably to make sure that OTA servers are not overloaded. Imagine what would happen if they released it at the same time for the whole world, the servers couldn't deliver acceptable speeds. That's just my guess though.
Click to expand...
Click to collapse
That is tackled in another way. Your phone randomly receive updates in batch.
Yes you can get an update if you manually go into settings and download updates.
But again it is automatically provided in random batches.
Samsung is late at updates because they have a large number of models.
Not like Iphone that only support 3 models of past I think.
Samsung also needs to provide stable updates which take a lot of testing.
Again it depends on your country and provider when the start rolling updates.
By the way A5 got certified for oreo.
https://www.wi-fi.org/product-finder-results?keywords=A520f
It has Oreo in Russia now
https://forum.xda-developers.com/samsung-a-series-2017/how-to/sm-a520f-oreo-russia-t3779287
I'm looking into buying this phone but I like a device with a lot of rom support. Is there something I'm not aware of or is the device too new to have much development? Thanks!
No TWRP. Some ROMs supports this, and most of the Kernels does.
Sent from my OnePlus7TPro using XDA Labs
I'm new to this device but from everything I gathered, the lack of ROMs doesn't really have anything to do with the 7T. It's more of a problem with Android 10. Google changed a lot of system stuff with Android 10 which makes it harder for the TWRP developers to get a custom recovery working. As far as I know, even the new Pixels don't have TWRP yet. Once devs get a working recovery going, I'm sure the ROMs will be flowing through here.
Some of the Magisk roms like xXx have worked on it. If you're looking for a full blown rom, they'll be few and far between.
I don't think we'll see much happening in TWRP until more 10 phones come out. These were among the first, and most people already had plunked down on the 7 Pro.
jrodbrown58 said:
I'm looking into buying this phone but I like a device with a lot of rom support. Is there something I'm not aware of or is the device too new to have much development? Thanks!
Click to expand...
Click to collapse
I was really excited about this devices since i heard so much about the oneplus brand, coming from Nokias (900,920,1020), HTC (one m8), Huawei (p10),Samsungs (Note 8), Huawei (mate 10 pro) i heard so much about it and how fast the devices are etc. Ill give you my honest opinion about it, as far as development goes its starting to pick up like some other members have said there are a couple of roms out there, rooting is possible and super easy to do and there are a couple of custom kernel like blu spark and elemental X that work perfectly and gives you a great battery. Before rooting this devices i decided to give it a go without messing with it i have read and watched several reviewers that the battery wasnt that great that it would give you only five hour of SOT etc, my last device was a Mate 10 pro and that devices even tho i cant root anymore since there are no bootloader unlocking for huawei anymore was a great phone super fast an never stutter battery was perfect between 7 or 6 and a half hours. Knowing that the oneplus was "only" five i didnt really care, once I got my device and it settle it really impressed me, i was getting around 8 to 7 hours of sot with a smaller battery, that was awesome speed was great everything was going perfect till i found out that the screens on the OP7T are very faulty, more so then other screens of other phones i have owned. The OP7T greatest defect is the damn mura of greenish tint on grey backgrounds when nightmode is active on around 20-30% brightness in a dark environment. I am one of those with the issue, for me its fine i know ill get use to it but it is something that reviewers wont say or talk about, now keep in mind we are not talking about a small percentage of devices this is a big batch and it doesnt matter if you have the chine model EU model IN Model etc the are all affected, oneplus representatives know about the issues and the only thing you can do its get a replacement hoping for the best cause it might be that the replacement phone will be worse. i advice you to look into the issues read the forums and decide after that. i hoped i knew before i bought since my warranty wont cover where i live now all i can do is just make the best get use to it and just make sure next time its the first thing ill check, beside that the devices is great overall but keep that in mind. sorry for the long post.
I've posted this review on the c.mi forums, There isn't anywhere in the review section that I can find to post a full review so I'm posting it in discussion, mods feel free to move it if there is a better category.
But, I felt someone in the same situation as me that bought this phone to get [back] into android development might find this useful.
Hello all, After having a Redmi Note 8 Pro and using it as my daily driver for a little over a month, I've decided it's time for me to write a review.
First, I'll give you all a little background on me, I'm a developer of everything from webpages to hardware, and tech enthusiast of all kinds. I'm from the US(NA market) so my knowledge of the Indian and Chinese markets are a bit limited although I do know pretty much how the EU market works as they're normally marketed to the almost the same way as the NA market, at least when it comes to tech. I started developing for Android with my Google G1 way back in 2008 and have been on an off developing for different android phones since then on a variety of forums. From the now gone SDX-Developers to XDA and Android Forums.(Through many different accounts as everywhere but SDX seems to end with me getting in an argument and deleting my account.) This is my first Xiaomi phone. I will be giving a review both as a user and a developer.
Marketing:
In the NA market this phone is marketed as a budget flagship, or "flagship killer" if you will. Pushed mostly towards tech enthusiasts and developers.
Their marketing technique is very similar to that of OnePlus, however without the strong reputation behind it that OnePlus has. If Xiaomi wants to continue using this marketing technique here they have a lot of make up for, and a lot of work to do for reasons that will become apparent later in this review.
User Review:
As a user I'm moderately happy with my purchase, the phone itself feels quality and is beautiful(I have the pearl white one). The price was decent, costing me $225 USD for the 64GB/6GB version. The processor is quick and the UI is gorgeous and snappy. The screen has really nice Darks and the HDR implementation is really good looking....When it works(Fixed in the new A10/M11 release). However, the software is really buggy with MIUI optimizations turned on, which is a shame because they make quite a difference to the snappiness and feel of the device. Apps sometimes don't work properly, refuse to show in portrait mode, or just won't use the keyboard(such as the newegg app which I use to order hardware quite often). There are a significant lack of updates, having just now as of today(28th May 2020) recieved my first OTA(Which is useless to me, more on that later). This has been a problem that the community seems quite aware and little angry about for good reason, seeing as how my device is still on the Dec 2019 security patch, with multiple high-threat CVEs being released since then. The IR blaster is nice, but the Mi Remote app needs a lot of work. I remember it being much, much better when it was "Peel Smart Remote" and using it on my Samsung Galaxy S5. The gallery app misses most downloaded pictures, and is quite the pain to get working. This is a shame as it's the only way to change the lock screen background, other than the theme app. -1 point for broken DRM and bugs -2 points for lack of updates.
Oh I forgot there are Ads throughout the system. This is UNACCEPTABLE in the NA and EU markets, to date this is the only phone I HAVE EVER SEEN put ads in the system framwork. I have owned at least 150 different android phones. This is becoming more and more forced by tech companies throughout different devices, specifically Chinese oriented ones and will not fly for long in Western Markets(especially the EU which already limits advertising). We paid for our hardware, you've got your money, now it's just being greedy, intrusive, and posing a risk to device security. (e.g The "security" app that puts ads in your package installer) It's easy enough to disable, but not everyone is going to know how, or want to do that. -2 points just for the ads, and honestly should be more taken off, the quality of the hardware is what's stopping me from dropping it -4 points.
Overall User Rating: 5/10
Developer Review:
Let me start off by saying, once again, that in the NA market this phone is marketed as an Unlocked device for enthusiasts, or a budget flagship(Which personally I have seen very little of this advertising for) It's on the front page of the XDA forums. Rooting and development is an important part of the Android Community, in what I've seen ALL MARKETS globally. We will begin at the rooting process. Unlocking the bootloader comes with a wait time. This is due to unauthorized retailers flashing chinese and indian varients to global and selling them, filled with [more] ads. So the fact that there is a 168 hour wait time to unlock the bootloader is completely understandable and I will take away no points for that. They're protecting their reputation in the least intrusive way they could, you know what? I'll even give them an extra point for the way they handled that part, +1. Now let's go to install TWRP, where right on the website is says "WARNING: This device hard bricks really easily for unknown reasons. Restoring device without spending real money is impossible as of now. " -2 points. This should have been my first warning to buy a different device. A somewhat large, reputable, and rooting advocate development team is warning users not to use their product, that's a red flag, and should never be something you have associated with your device or company as a whole. TWRP has backlight bug which can be fixed with an adb command, and really isn't a big deal seeing as how TWRP probably went through multiple devices getting their recovery out. Then flash Magisk. That's it you're rooted. I have to give them a hand, rooting really isn't a big deal. But let's pretend we're a new user and accidentally flashed TWRP to the boot partition, well you're SOL now, you have a $225 brick. There is no coming back from this unless 1, You have an authorized MI account, which you almost certainly do not. or 2, you pay some sketchy person halfway across the world to RDP into your computer and use their authorized account to unbrick you, as well as the 80% chance they're going to drop a keylogger, ransomware or they're going to syskey your computer and now you're still SOL, but you might have your phone unbricked, not very useful without a computer and an empty bank account though. They handled the way unbricking works terribly, and without cause. -8 points To add salt on the wound they release the source code like they're doing the development community a favor when it's 100% useless without a reliable unbricking method. -2 points for putting on a show. Which is sad, because otherwise the phone would be a pleasure to develop for. For example, you're in a bootloop something in /system got messed up. You can just flash the system.img from twrp and recover without any data loss or bloatware reappearing. That's amazing! the phone is partitioned very well, and has lots of xml, props and stuff to tweak from the start. Also, a really cute fastboot screen as a plus. Unfortunately, Xiaomi.eu has dropped all support for this device, as well as any other MTK based phones.
Thankfully, some totally awesome person at Xiaomi "leaked" an engineering preloader which can help prevent bricks as long as it's not overwritten and you stay on android 9. But, the downside is, No Android 10, No MIUI 12, No anything other than MIUI 11 Pie. If they would release more lks along side the updates for developers this would be insanely helpful, and breath some life back into the RN8P/8/T development community.
Still, as a developer, and a normal person, I'm afraid to do too much to this device, or develop kernels, recoveries or ROMS because i'm terrified I'm going to be out $225 and my daily driver phone, that I can't afford to replace if something bad happens.
Development Score: 0/11
Guy who leaked preloader score: 10000/10
tl;dr If you're not into rooting or development this is a pretty decent phone with quality flagship hardware, if you can live with ads in your system, and the bug in some apps. There are ways to remove most of the ads without root, and it does still get updates, although rare. It's worth $180-$200 USD if you find it for a good deal. Although you could just get a used OnePlus 7 Pro for around the same price maybe $50-$100 USD more(depending on market) and be much happier all around.
Nice review, such detail
I wish i had read this before, i've bricked my phone trying to flash new ROM after i spent hours getting to a lower firmware and then getting TWRP to work, finally flashed android 11 rom to get a brick
0/10 rating by more than average user who was sick of MIUI
ezequielfilipesantos2000 said:
I wish i had read this before, i've bricked my phone trying to flash new ROM after i spent hours getting to a lower firmware and then getting TWRP to work, finally flashed android 11 rom to get a brick
0/10 rating by more than average user who was sick of MIUI
Click to expand...
Click to collapse
Well, What a cocindence, I just gave someone a solution to install TWRP and root their stock ROM. Not a custom one though.
Kenora_I said:
Well, What a cocindence, I just gave someone a solution to install TWRP and root their stock ROM. Not a custom one though.
Click to expand...
Click to collapse
Sure is, was that user using the latest miui version (android 10, miui. 12.0.5 i believe?)
I was also having problems flashing the TWRP ( latest one) recovery
I flashed but i didn't have sucess, it went into Redmi-Recovery 3.0
I had to get a old fastboot version of android 9.0 with muiu, flash it using miflashpro tools then, i had to flash the preloader ( https://forum.xda-developers.com/t/guide-info-psa-redmi-note-8-pro-megathread-cfw.4056527/ )
Then i was able to flash the TWRP recovery and it worked
After that I tried flashing (after a wipe obviously, not going to flash dirty) Pixel Experience (AOSP) rom and it resulted in a bricked phone
10/10 I highly recommend the drama
Yeah the latest one.
Kenora_I said:
Yeah the latest one.
Click to expand...
Click to collapse
How did you manage?
Was i doing something the wrong way? ( or all of it? ) ahahaha
As I'm sure we all know here, our beloved Pixel 3 XLs are officially getting dropped by Google in about three weeks. If history repeats itself, though, we will get the Android 12 release in October followed by one last OTA in December. My typical usage pattern with a phone is:
Get the phone and use the stock ROM until the phone reaches EOL.
Once EOL is reached, move to LineageOS.
I know that this is a pattern that some others more or less follow as well, but I was wondering about what variations there are to the pattern. Does anyone here use another ROM? As much as I like LineageOS, I would be more interested in using a ROM that is basically identical to stock Android. I have read about compiling AOSP from source so as to maintain my own ROM that does just that, but from what I understand, that does not work very well for unsupported devices. Does anyone have any suggestions?
Off the top of the head... EOL only means no more official updates or support, ie security fix's...
Your fone working on a custom rom will still work, since you'd think it was the custom rom updated...
If they do stop the fone calling, there's plenty other apks for 'near field' communication
Free wifi calling hint hint..
Pachacouti said:
Off the top of the head... EOL only means no more official updates or support, ie security fix's...
Click to expand...
Click to collapse
Oh yes, I know that functionality-wise the phone will continue working as before. What I want to know is, what are people considering in regards to custom ROMs?
David B. said:
Oh yes, I know that functionality-wise the phone will continue working as before. What I want to know is, what are people considering in regards to custom ROMs?
Click to expand...
Click to collapse
Kl, well, me, I'm wondering this too just now, because I'm stuck with a system-as-root fone thats a pain, and now there's too many different too choose from, and if they're of the best quality, they now have to cover at least 4 different styles of booting alone, I'd watch those for the ones updating quickest
Pachacouti said:
Kl, well, me, I'm wondering this too just now, because I'm stuck with a system-as-root fone thats a pain, and now there's too many different too choose from, and if they're of the best quality, they now have to cover at least 4 different styles of booting alone, I'd watch those for the ones updating quickest
Click to expand...
Click to collapse
Well, LineageOS certainly does that, but at the same time, it also takes them about 6 months to move to a new major release of Android. I was hoping that someone would know of a release that does it just as well, but is a little more flexible with migrating. I haven't found any myself.
I've yet to convince myself which version is for my fone lol
David B. said:
As I'm sure we all know here, our beloved Pixel 3 XLs are officially getting dropped by Google in about three weeks. If history repeats itself, though, we will get the Android 12 release in October followed by one last OTA in December. My typical usage pattern with a phone is:
Get the phone and use the stock ROM until the phone reaches EOL.
Once EOL is reached, move to LineageOS.
I know that this is a pattern that some others more or less follow as well, but I was wondering about what variations there are to the pattern. Does anyone here use another ROM? As much as I like LineageOS, I would be more interested in using a ROM that is basically identical to stock Android. I have read about compiling AOSP from source so as to maintain my own ROM that does just that, but from what I understand, that does not work very well for unsupported devices. Does anyone have any suggestions?
Click to expand...
Click to collapse
I've already moved to LineageOS, simply to get the monthly security updates. I have not seen any functional loss on LineageOS. If you don't feel you need security updates, just stay on the stock ROM, especially if you think you need any Android 12 features. IMO, new Android features simply add more bloat than I want or need. Your opinion may differ.
Not at all, they all sound excellent, however, my fone cant write to the actuall system, can mount, but no joy yet doing anything else, and no overlay works so far, the only custom os I could install was a chrooted nethunter, which was pretty lame and useless being my system as root is a pain... so I'm looking..
dcarvil said:
I've already moved to LineageOS, simply to get the monthly security updates. I have not seen any functional loss on LineageOS. If you don't feel you need security updates, just stay on the stock ROM, especially if you think you need any Android 12 features. IMO, new Android features simply add more bloat than I want or need. Your opinion may differ.
Click to expand...
Click to collapse
My plan, at least for now, is to ride on stock until the last update is pushed, and then once LOS gets updated to 12, I will migrate. The only problem with this, though, is that it would leave me without security updates from the end of December until either March or April, and I am not sure how I feel about that.
My experience might help...Last year I was using a Motorola 5Plus with Pixel Experience Rom and loved it. My phone was fast, stable and highly compatible to the "Pixel Experience". I had a hardware issue and decided I liked the PE so much, I went ahead and got a Pixel 3xl...I've never had such a seamless transition...was just faster with better hardware but almost no thought changing for different mechanisms of actions...
I'm hoping someone picks up PE and ports it to the 3XL and I'll use that....otherwise, any alternative suggestions for closest to "stock" Pixel would be appreciated...
S
spschneer said:
I liked the PE so much, I went ahead and got a Pixel 3xl...I've never had such a seamless transition...was just faster with better hardware but almost no thought changing for different mechanisms of actions...
Click to expand...
Click to collapse
Yeah I have seen PixelExperience and would really like to use it over LOS if the 3 XL gets support. As far as I know, the 2 XL did not receive support until it's EOL, so there's hope. Is the feature parity as spot-on as is claimed?
David B. said:
Yeah I have seen PixelExperience and would really like to use it over LOS if the 3 XL gets support. As far as I know, the 2 XL did not receive support until it's EOL, so there's hope. Is the feature parity as spot-on as is claimed?
Click to expand...
Click to collapse
For the features and functions I use, it was almost totally seamless...it was less than a typical release level amount of change (e.g.: 10->11 was more than I experienced PE -> P-3xl)
YMMV however...based on what features/functions you use most heavily.
S
spschneer said:
For the features and functions I use, it was almost totally seamless...it was less than a typical release level amount of change (e.g.: 10->11 was more than I experienced PE -> P-3xl)
YMMV however...based on what features/functions you use most heavily.
S
Click to expand...
Click to collapse
Great! I guess it's time for me to start researching building my own image.
"David B said he's gonna research building PE for 3xl....
GREAT...be sure to use the AOSP version ... there are a couple of flavors of PE but IMHO the AOSP version is the closest to the stock 3xl ...
If you don't mind guiding me a little over the rough patches, I'd be willing to help test your creation once you're out of alpha<G>...(my 3xl is my daily driver)... specifically, I'm used to having TWRP available for the maintenance/management of the ROM and if I understand it properly, TWRP isn't used / available for the 3xl ROM's...
Thanks
S.
spschneer said:
"David B said he's gonna research building PE for 3xl....
GREAT...be sure to use the AOSP version ... there are a couple of flavors of PE but IMHO the AOSP version is the closest to the stock 3xl ...
If you don't mind guiding me a little over the rough patches, I'd be willing to help test your creation once you're out of alpha<G>...(my 3xl is my daily driver)... specifically, I'm used to having TWRP available for the maintenance/management of the ROM and if I understand it properly, TWRP isn't used / available for the 3xl ROM's...
Thanks
S.
Click to expand...
Click to collapse
For now, I would like to hold off on it. I don't really see a point in putting effort in to building PE for the 3 XL when we're about two weeks away from the next major Android release, at which point, PE will need reworked by the dev team. If the 3 XL is not picked up by someone else in the modding community at release time, and I've seen some people that think it will be, then I will start researching it.
David B. said:
For now, I would like to hold off on it. I don't really see a point in putting effort in to building PE for the 3 XL when we're about two weeks away from the next major Android release, at which point, PE will need reworked by the dev team. If the 3 XL is not picked up by someone else in the modding community at release time, and I've seen some people that think it will be, then I will start researching it.
Click to expand...
Click to collapse
Sounds like a plan...will keep an eye on development threads for it once it goes out of support.
Even though the last update will be in Dec I'll probably keep using the 3XL until the 7 comes out (or 6a maybe). I just had the battery replaced a couple months ago, and there is nothing wrong with the phone. I usually use devices until EOL hits, and then upgrade when the next OS/phone comes out, so whatever device I'm using at any given time is on the current OS release (IE: 3XL on Android 12 until Android 13 drops, and then upgrade phone to get Android 13).
I would like to use that method, but I think it's too expensive, so I try to settle for "my phone's basically dead."
dcarvil said:
I've already moved to LineageOS, simply to get the monthly security updates. I have not seen any functional loss on LineageOS. If you don't feel you need security updates, just stay on the stock ROM, especially if you think you need any Android 12 features. IMO, new Android features simply add more bloat than I want or need. Your opinion may differ.
Click to expand...
Click to collapse
Does the unlimited Google Photos upload work on LineageOS?
quera said:
Does the unlimited Google Photos upload work on LineageOS?
Click to expand...
Click to collapse
I don't know how to tell if it is still in effect. I see photos counted against my storage allotment, but don't know if that is just for my previous phones, or if it includes the Pixel photos.
My guess is you would have to use the Google Camera and Photo apps to keep unlimited upload, if it can be kept with LineageOS.