Related
Hi, as someone who jumped over to Windows phone some while ago, I am now looking toward Android based again, mainly due to the fact I don't like the way windows is heading.
I have my eye on the Wileyfox swift http://wileyfox.com/ at the moment, it looks good bang for bucks and I like the fact it's UK manufactured.
I'm a little unsure when it's released as I have read some articles saying it's released today and others saying toward the end of September, I can't find it on Amazon or Ebay and the Wileyfox website although gives good information on the phones they are some what lacking in purchasing info, which I find a shame.
My other concern is there is no contact information on the website of the manufacturer, which always makes me a little uncomfortable.
Any thoughts on this phone?
Phone sites almost always wont have pricing details, because of the diff country models, and diff prices in diff places
Thank me if i helped ... ?
pandollar said:
I'm a little unsure when it's released as I have read some articles saying it's released today and others saying toward the end of September?
Click to expand...
Click to collapse
I just received this info from Wileyfox:
We are pleased to announce that the Wileyfox Swift will be available to buy online from 22nd September.
Click to expand...
Click to collapse
alienhead13 said:
I just received this info from Wileyfox:
Click to expand...
Click to collapse
Preorders already started at Amazon for Swift only
https://www.wileyfox.com/swift/
pandollar said:
Hi, as someone who jumped over to Windows phone some while ago, I am now looking toward Android based again, mainly due to the fact I don't like the way windows is heading.
I have my eye on the Wileyfox swift http://wileyfox.com/ at the moment, it looks good bang for bucks and I like the fact it's UK manufactured.
I'm a little unsure when it's released as I have read some articles saying it's released today and others saying toward the end of September, I can't find it on Amazon or Ebay and the Wileyfox website although gives good information on the phones they are some what lacking in purchasing info, which I find a shame.
My other concern is there is no contact information on the website of the manufacturer, which always makes me a little uncomfortable.
Any thoughts on this phone?
Click to expand...
Click to collapse
Also consider Xiaomi Mi 4i and Micromax Yu Yureka Plus.
Hit thanks if i helped you!
I went for OPO 64gb in the end. My concerns around the Wileyfox were there was no contact information on the web site, no info on release date although I did receive an email saying it had been delayed until 30 Sept, but looking at the site it's still not released, so lost some faith in them. Something didn't seem right about ordering from a company where there was no contact info for or even details on release.
Anyway, I feel I made the right decision with the OPO and am well impressed, good service from ordering direct and received quite a few extra's that I wasn't expecting ie case, screen protectors.
pandollar said:
I went for OPO 64gb in the end. My concerns around the Wileyfox were there was no contact information on the web site, no info on release date although I did receive an email saying it had been delayed until 30 Sept, but looking at the site it's still not released, so lost some faith in them. Something didn't seem right about ordering from a company where there was no contact info for or even details on release.
Anyway, I feel I made the right decision with the OPO and am well impressed, good service from ordering direct and received quite a few extra's that I wasn't expecting ie case, screen protectors.
Click to expand...
Click to collapse
I just bought a Wileyfox Swift through Amazon pre-order. It came as promised and is a sweet device. It is a shame that the Wileyfox home page has no contact details. I wanted to find out how to root the device. As it's Cyanogen, I thought it would have come pre-rooted but it's not.
Also, because of delivery delays, Wileyfox offered me a year's screen replacement cover free. To avail of their kind offer I have to enter the device IMEI on Wileyfox home page but.....there's no option there....yet.
Amazon,as usual, got everything right but Wileyfox seem tardy. Maybe they'll catch up soon.
The Swift is a nice device but I want to root it. Does anyone have any information about that?
I have made a big mistake. Try to flash a new official rom somebody posted in needrom, and I got hardbrick (qhsusb_buld detect when i connect). I am asking for any kind of advice. I have found some different methods to repair it with qualcomm tools but i dont have the required files.
Thanks for your answers.
dyegop said:
I have made a big mistake. Try to flash a new official rom somebody posted in needrom, and I got hardbrick (qhsusb_buld detect when i connect). I am asking for any kind of advice. I have found some different methods to repair it with qualcomm tools but i dont have the required files.
Thanks for your answers.
Click to expand...
Click to collapse
https://download.cyanogenmod.org/?device=crackling&type=nightly
rooting the wileyfox swift
Hi all,
found out how to root this device!
Here the steps:
1) download supersu zip from here
https://download.chainfire.eu/696/supersu/
2) save it to your external sdcard
3) follow the steps on this site until recovery is started.
Do NOT flash the Cyanogenmod, only the recovery!!!
https://wiki.cyanogenmod.org/w/Install_CM_for_crackling
4) reboot directly into recovery. Normal system boot reinstalls stock recovery.
5) install supersu update zip from recovery menu
6) reboot and enjoy root access
olli_o said:
Hi all,
found out how to root this device!
Here the steps:
1) download supersu zip from here
https //download.chainfire.eu/696/supersu/
2) save it to your external sdcard
3) follow the steps on this site until recovery is started.
Do NOT flash the Cyanogenmod, only the recovery!!!
https //wiki.cyanogenmod.org/w/Install_CM_for_crackling
4) reboot directly into recovery. Normal system boot reinstalls stock recovery.
5) install supersu update zip from recovery menu
6) reboot and enjoy root access
Sorry for the inconvenience with the text links, I'm not yet allowed to post external links.
Click to expand...
Click to collapse
Thanks olli_o. Has anyone else been brave enough to try this yet?
This query is aimed at Swift owners using CyanogenOS: Is the pulsing of notification LED natively supported? If not, have you tried apps that enable this feature?
NigelLHooper said:
Thanks olli_o. Has anyone else been brave enough to try this yet?
Click to expand...
Click to collapse
I have successfully rooted my Wilefox swift using that method. I did not even flash the new recovery - I simply booted into it and flashed supersu
---------- Post added at 06:45 PM ---------- Previous post was at 06:44 PM ----------
arvinquilao said:
This query is aimed at Swift owners using CyanogenOS: Is the pulsing of notification LED natively supported? If not, have you tried apps that enable this feature?
Click to expand...
Click to collapse
It has native LED support, which actually works very well. On my Nexus 4 I used to use Lightflow, but with the Wileyfox I've not needed to use a separate app.
fractiousg said:
I have successfully rooted my Wilefox swift using that method. I did not even flash the new recovery - I simply booted into it and flashed supersu
Click to expand...
Click to collapse
That's intersting. My stock recovery always complained about wrong signature of the update, so I had to use the CM recovery.
Now as I've got root I can read out the ROM. Does anybody know how to build the ROM image so that it could be flashed by recovery to restore the device?
olli_o said:
That's intersting. My stock recovery always complained about wrong signature of the update, so I had to use the CM recovery.
Now as I've got root I can read out the ROM. Does anybody know how to build the ROM image so that it could be flashed by recovery to restore the device?
Click to expand...
Click to collapse
The stock recovery does complain about the wrong signature...so I did USE the CM recover, but I did not flash it, I simply booted into it with:
Code:
fastboot boot recovery.img
This allowed me to flash without replacing the stock recovery
Hey guys, I've followed all the instructions (adb, fastboot etc, fastboot is installed and working correctly etc), but when I try installing the recovery (for cm12.1) it says the system cannot find the file specified?
Any suggestions?
Or is there any other way that I could install the recovery?
I'd really like to start using the 12.1 nightlies
Kind Regards
Why do you guys want to root an official Cyanogen phone?
jjl5590 said:
Why do you guys want to root an official Cyanogen phone?
Click to expand...
Click to collapse
Because it's CyanogenOS which has no root option. Only CyanogenMod has this option.
---------- Post added at 01:28 PM ---------- Previous post was at 01:19 PM ----------
r3d3mpt10n said:
Hey guys, I've followed all the instructions (adb, fastboot etc, fastboot is installed and working correctly etc), but when I try installing the recovery (for cm12.1) it says the system cannot find the file specified?
Click to expand...
Click to collapse
What do you mean with installing the recovery? You download the recovery image to your PC and flash the img file using fastboot. Then reboot and press the power and vol- buttons together.
Any joy with SuperSU on the storm?
NigelLHooper said:
Thanks olli_o. Has anyone else been brave enough to try this yet?
Click to expand...
Click to collapse
Thanks, Nigel and Olli_o - great work...
Has anyone been able to successfully do this on the Storm (not the swift)? If not, does anyone have any reason to believe it will/wont work?
Loving my new phone, but screwed by it not having root, and really don't want to brick it after 3 days...
TIA,
Neon
Seems that the Wileyfox Swift still has the Stagefright bug number CVE-2015-6602. Does anybody know if Wileyfox will deliver a CyanogenOS update for that?
Just thought would leave this here.
The Alcatel 3v supports project treble it's probably the cheapest on the market that supports this
If there is a way to unbrick it, I might try flashing a GSI to see if it will actually work. The thing is that for some reason my 3v has a MT6735
nintendobuster420 said:
If there is a way to unbrick it, I might try flashing a GSI to see if it will actually work. The thing is that for some reason my 3v has a MT6735
Click to expand...
Click to collapse
Ok just to give you guys an update, GSIs actually work! I managed to unlock the bootloader by typing in fastboot oem unlock and ticked oem unlock in developer options. Then I followed XDA's guide on flashing a GSI and it actually worked. Now we have stock android on the alcatel 3v. The only problem is that the phone is really slow and the stock camera app is upside down so its probably best to stay on stock
Have you had any luck trying out different gsi's, perhaps there's a certain one that works better? Also, would you happen to have a stock rom for an Alcatel 3v 5099a? Or at least a boot.img?
Laney613 said:
Have you had any luck trying out different gsi's, perhaps there's a certain one that works better? Also, would you happen to have a stock rom for an Alcatel 3v 5099a? Or at least a boot.img?
Click to expand...
Click to collapse
Oreo seems to be less laggy also I have a 5099y which is the nfc version I could try and dump my rom
I just really want to fix the youtube lag on this phone as it always lags at 1080p or 720p
how did you unlock the bootloader ? i have the 5099y, i tried adb fastboot oem unlock,i have adb installed ,i have google usb installed,ive got updated drivers, but it still says waiting for device,it boots into fastmode fine ,but then once i do adb devices it doesnt see it,it does show in the device manager as alcatel,usb debugging is allowed, oem unlock is ticked
CrunchyKevlar said:
how did you unlock the bootloader ? i have the 5099y, i tried adb fastboot oem unlock,i have adb installed ,i have google usb installed,ive got updated drivers, but it still says waiting for device,it boots into fastmode fine ,but then once i do adb devices it doesnt see it,it does show in the device manager as alcatel,usb debugging is allowed, oem unlock is ticked
Click to expand...
Click to collapse
It's fastboot OEM unlock, when in fastboot
The procedure was fairly easy and I'm now running phhussons AOSP 9 v114 on my 5099Y.
Very smooth and much faster than stock 8.0.
No camera issues at all.
Google play verification was an issue but soon sorted
This device needs further development though, it has a few random glitches running pie, but nothing than stops it working well.
After reading @ivan1972 comments I've today also flashed a couple of gsis on my 5099Y and had good success all round.
I unlocked the bootloader, this device has the easiest unlocking bootloader ever!
I then tried lineage 15.1 with Go gapps and that worked really well.
I tried Descendants 3.0 and flashed via fast boot (fastboot flash system system.img - I obviously renamed the GSI to "system.img") I have that installed on my Moto E5 play but it was far too glitchy on the Alcatel and I had huge problems trying to get the play store certification working, so I was bombarded with notifications about my 3V not being Google play verified almost every three seconds!!!
I'm also using AOSP 9 v114.
The battery life is double that of stock oreo, the phone works twice as fast as it did on stock, and I had no issue with Google device certification.
I suggest any user wanting to flash a Gsi on a 3V spectrum should aim to install lineage 15.1 or AOSP 9 as they are both great gsis.
Edit, the Gsi was flashed in fastboot as I haven't rooted or flashed (found) a twrp for the 3v yet.
Some screenshots from my 3V Spectrum (using the latest Lawn chair V2 as default launcher)
You will note the status bar is glitchy and doesn't show until a notification is received, then it appears in the middle of the screen, not at the top.
The only major issue I've seen so far.
The device is listed as "PHH treble" in device settings
After a week's usage Ive found one major flaw.
Whilst you can make an out going call with no problems, with good clarity and good service, no one can actually phone you.....!
Incoming calls are diverting straight to voicemail, nothing in settings to explain why.
Everything else is perfect on pie, flawless and way better than stock.
But this phone is no use if you cannot use it for its primary function - to receive a phone call :crying:
Edit - I'm told it's an AOSP issue on mediatek chips, and it's not an easy fix.
And as there is no way to go back to stock, I'm now stuck with a device that cannot receive any calls.
Just putting that out here incase anyone does read this and feels the need to flash pie.
Don't bother!
I'm done with this Alcatel - no one really seems that interested in this device anymore.
Edit.
My Alcatel has been traded in (as non functional) for a Nokia 4.2
I'm not quite sure why are people sending me private messages asking if I can send them the custom recovery for the Alcatel 3V?
I have quite clearly stated in my previous posts that I flashed the GSIs I tried via FASTBOOT - there is NO custom recovery for 3V that I can find - so please don't message me requesting the custom recovery.
*WARNING*
I also recommended users do not flash android pie gsis on this device as it breaks RIL / modem function and there is no current fix - but for a strange reason people are still asking me about the process and any bugs / issues.
Please read things properly before posting private messages - whilst I'm happy to help anyone, I'm not prepared to keep unnecessarily repeating myself for the sake of repeating myself when the information is already there for everyone to see.......
bubba1601 said:
After reading @ivan1972
I unlocked the bootloader, this device has the easiest unlocking bootloader ever!
Click to expand...
Click to collapse
I wish that was easy to believe, but I have an Alcatel 3v (5032W) and I CANNOT unlock the bootloader for the life of me!
@mattchusquirtle420
I'm not sure why you find what I said one year ago so hard to believe, but I'll explain it to you.
Are you sitting comfortably?
Then I'll begin.....
This thread deals with the 2018 Alcatel 3v (5099Y)
It's a 2gb ram 16gb ROM / 3gb ram 32gb ROM on Android 8.0 (Oreo)
That had a standard MTK (Mediatek) chip so was super easy to bootloader unlock.
All you had to do was enter fastboot and use the "fastboot OEM unlock" command and press enter.
The bootloader was now unlocked, no unlock codes were needed or necessary.
https://www.gsmarena.com/alcatel_3v-9004.php
********************
You have the 2019 Alcatel 3v (5032w) which is a 3gb ram 32gb ROM device running Android 9 (pie)
Which has a MTK Helio chip and a locked bootloader that cannot be unlocked.
None of the Helio or Snapdragon Alcatel 2019 devices can be bootloader unlocked, infact the only 2019 Alcatel device than can be bootloader unlocked is the 1C.
I'm not being rude to you here, but this thread began back in May 2018 - and you also just replied to a comment I made in July 2019 - That's a whole SIX months before your 3v 2019 became commercially available.....so I don't understand why you even commented, your device isn't relevant, or even has the same processor / chip as the 2018 version, so how can you honestly disbelieve our experience if you have a completely different device?
I now have this device.
Alcatel 3 (2019) 5053Y (Snapdragon 439 chip with 3gb ram and 32gb ROM on Android 9 pie)
https://www.gsmarena.com/alcatel_3_(2019)-9599.php
It's not possible to unlock this device because bootloader unlocking is not supported.
I'm going to ask you now very politely and without being rude to NOT private message me about your device.
Your device is not relevant or related to our discussion or this post.
You are going to have to find a dedicated thread for the 3v 2019 because posting and commenting in the 2018 device thread is not really very clever and achieves nothing, and helps no one, including you.
Oh dear.
You seem to be annoyed and disbelieve what we are saying.....
Well how about you actually read the post properly first before you start telling people you find it hard to believe what they say?
Did it occur to you at any point that we may have been discussing a different device to one you have?
There is more than one version of the Alcatel 3v and they are all different.
Nothing annoys me more than comments from people who don't take time to read the information Infront them properly.
You've commented here saying you can't believe us but you've commented in a device thread that you don't have or have any experience of at all, so your comments are completely unfair and totally unnecessary.
I thought how old the the thread was it would have been completely obvious to you that we were not discussing the same device as yours, or you were just stupid and assumed it was the same.
@bubba1601
@ivan1972
Y'all should go easy on the dude. I made the same mistake thinking this was a 5032w thread simply bc it's the leading search result on Google. He's just a newb and probably linked in to this thread from a Google search and there is NOT distinguishing information that this thread is specifically for the 2018 version. Until you two fire off at a new member bc he annoyed you.
Aballamis said:
USER=7682183]@bubba1601[/USER]
@ivan1972
Y'all should go easy on the dude. I made the same mistake thinking this was a 5032w thread simply bc it's the leading search result on Google. He's just a newb and probably linked in to this thread from a Google search and there is NOT distinguishing information that this thread is specifically for the 2018 version. Until you two fire off at a new member bc he annoyed you.
Click to expand...
Click to collapse
Really?
Don't you think it's just a bit sad that you felt the need to take me to task over comments I make 16 months ago?
Who cares now?
It's not my fault or my problem if you blindly follow Google links.
It's not my fault you made a mistake, at least you admitted to it, so many here don't.
I'm sorry you made the same mistake but rather than sound off to me about it a year and 4 months later, learn from your mistake, move on and forget about it.
What happened here is none of your business, the "new" guy concerned made a heartfelt and genuine apology privately to me and we both moved on 16 months ago, but now you come along and you have to have the audacity to tell me off!
I can always refer you to the mods here if you are really concerned and upset about my comments, but seeing as it was resolved so long ago I don't really see the point.
Or I could just report you for harassing me, the choice is yours
Aballamis said:
@bubba1601
@ivan1972
Y'all should go easy on the dude. I made the same mistake thinking this was a 5032w thread simply bc it's the leading search result on Google. He's just a newb and probably linked in to this thread from a Google search and there is NOT distinguishing information that this thread is specifically for the 2018 version. Until you two fire off at a new member bc he annoyed you.
Click to expand...
Click to collapse
No one has annoyed me only you.
I don't take kindly to getting XDA notifications at 3 am, especially for something I said here so long ago.
So what I need to know is why are you replying to something I said almost 2 years ago?
So you really think I care what you think?
I think it's absurd you come here telling me and the other guy off for something we said 16 months ago - AND after you admit to making a mistake and follow Google links without checking.
That's just stupid.
Did you actually read the thread properly? I think not, you come charging in here with all guns blazing without knowing the full facts.
The other guy apologized to me for his mistake privately and there was no problems between us.
So why are you telling me off now 16 months later without knowing the full facts?
When did you check the facts?
You just charged in here telling people off.
I'm not happy about this as it was resolved 16 months ago with good intentions privately, amicably and in good spirits.
I will be reporting this matter to the moderation team here, as I certainly don't take kindly to being told off by people who cannot check the facts first.
Hello, can someone please send me the official recovery of the alcatel 3v 5099a?
.
read this 3 times from start to finish before you start asking questions....itll help with most of your questions...also...
When your unlocking your bootloader using the "fastboot flashing unlock" command....after the system has booted.... boot back into fastboot and also run the "fastboot flashing unlock_critical” this makes this device nearly unbrickable.... please do it you won't regret it.
Next twrp is in boot.img with a/b devices..so if you flash twrp and want to root you have to reflash the stock boot.img of your rom before you flash magisk....if you don't you'll have a bootloop that gets you nowheres
http://mata.readthedocs.io/en/latest/
Also, welcome to the forums! Hopefully posts this don't scare away people and potential new devs since it's dead enough around here already.
Feel free to message me if you have questions, I won't jump down your throat.
Thank you for this.
Switched over from a Nexus 6P (that is still working great, to be honest). can't wait to start flashing
Thanks for the link to the document. Didn't realize there are two partitions.
I'm sure this question has been answered before but I'll ask here again for the newbies.
If I root the device with Magisk but stay with the stock ROM, does the OTA updates work? If the updates do work, do I have to root each time after the update?
TIA.
csrow said:
Thanks for the link to the document. Didn't realize there are two partitions.
I'm sure this question has been answered before but I'll ask here again for the newbies.
If I root the device with Magisk but stay with the stock ROM, does the OTA updates work? If the updates do work, do I have to root each time after the update?
TIA.
Click to expand...
Click to collapse
They don't work if rooted, however I, and many others, have issues with the OTAs in general anyhow.
It's super quick to just fastboot flash the firmware files yourself anyhow (modify a boot.img beforehand with magisk), and then flash the modified boot.img at the end.
I got in on the Amazon deal...should be here next week. Will be coming from a Nexus6.
Quick question for a Prime Deal newbie. Do you have to unlock the bootloader if you are just side loading the OTA file? I know you have to in order to fastboot any images but I thought the ota file would be fine. No biggie if not just curious.
After another search it looks like you do not have unlock the bootloader just to flash the ota.
Really helpful and it definitely going to keep the rest of the section tidy!
Picked one up also. Coming from/still have a Pixel 2 xl and previously a first gen pixel, so I'm familiar with a/b slots. Not having a perm twrp suuuuuucks. I got my ph1 on Sept security patch and it's updated twice now to the Jun patch will that cause issues with any root or roming?
Also coming from the Nexus 6. Looking forward to this phone.
thank you for the heads up.
Sent from my SD4930UR using XDA Free mobile app (Yep Firephone)
crixley said:
Also, welcome to the forums! Hopefully posts this don't scare away people and potential new devs since it's dead enough around here already.
Feel free to message me if you have questions, I won't jump down your throat.
Click to expand...
Click to collapse
Thanks for the welcome everyone!!
Coming from a Nexus 6 running PureNexus. Phone is still rocking, but my goodness you should see how busted my screen is.
I'm excited to get the Essential set up and flash some ROM and camera goodies!
Tech_Savvy said:
read this 3 times from start to finish before you start asking questions....itll help with most of your questions...also...
When your unlocking your bootloader using the "fastboot flashing unlock" command....after the system has booted.... boot back into fastboot and also run the "fastboot flashing unlock_critical” this makes this device nearly unbrickable.... please do it you won't regret it.
Next twrp is in boot.img with a/b devices..so if you flash twrp and want to root you have to reflash the stock boot.img of your rom before you flash magisk....if you don't you'll have a bootloop that gets you nowheres
http://mata.readthedocs.io/en/latest/
Click to expand...
Click to collapse
Thanks for the heads up, wonder if it will help the people who don't know which hole to put the sim card removal tool into.
[emoji23] I watched my brother keeps poking the microphone hole for like the 5th time until he figured it out. It is kind of a bad design imho tho.
Sent from my PH-1 using Tapatalk
This seems a welcome thread. I haven't tweaked Android for about 2½ years. From 2010 on I always had custom recovery and root and ROMs, but my last device (htc10) I didn't root, life got too busy.
Just got essential from Amazon, and trying to figure out what this AB slot stuff is is confusing the hell out of me. Also, this phone seems laggier than any device I've had, and I also just noticed a lot if the text is outlined with black, like on the LG get. Gotta get rid of that.
Sorry if this is the wrong place for those comments.
If anyone could give an explanation to what the AB slot is, to someone who is already pretty familiar with using custom recoveries, and understanding the partions (to a degree), I'd super appreciate it.
Again, I've been away from xda and customizing Android for about 3 years.
Anyone else feeling like this device isn't quite what they hoped? I always saw it at sprint stores and couldn't put it down. Now it's in my hand, doesn't seem so great. Think my htc10 is better, but maybe I'm missing how to make it great.
I hope this is in the right place.
scottspa74 said:
Anyone else feeling like this device isn't quite what they hoped? .
Click to expand...
Click to collapse
you can't beat it for $250, but I think I'm getting the OnePlus 6T or OnePlus 7 when it comes out.
installing TWRP and customs roms is such a chore on this device. I had AOSiP installed...but for some reason which I couldn't explain, it didn't feel like AOSiP on my Nexus 6P or OnePlus5 (that I just gave to my mom). Substratum worked...Magisk worked. But something didn't feel right. If I'm going to have to be on a stock ROM, I'd rather be on OxygenOS with its additional customizations.
only one of my 9 USB-C to USB-A cables seem to work for file transfer AND fastboot AND charging. It also happens to be the shortest cable I have.
See this weirdness where text is surrounded by black outline? That happened on LG g stock rom. It was fixed. Is a custom rom only way to fix this on ph1. ? Much thanks.
scottspa74 said:
See this weirdness where text is surrounded by black outline? That happened on LG g stock rom. It was fixed. Is a custom rom only way to fix this on ph1. ? Much thanks.
Click to expand...
Click to collapse
I think your phone high contrast text mode is on. Uncheck that under accessibility
scottspa74 said:
This seems a welcome thread. I haven't tweaked Android for about 2½ years. From 2010 on I always had custom recovery and root and ROMs, but my last device (htc10) I didn't root, life got too busy.
Just got essential from Amazon, and trying to figure out what this AB slot stuff is is confusing the hell out of me. Also, this phone seems laggier than any device I've had, and I also just noticed a lot if the text is outlined with black, like on the LG get. Gotta get rid of that.
Sorry if this is the wrong place for those comments.
If anyone could give an explanation to what the AB slot is, to someone who is already pretty familiar with using custom recoveries, and understanding the partions (to a degree), I'd super appreciate it.
Again, I've been away from xda and customizing Android for about 3 years.
Anyone else feeling like this device isn't quite what they hoped? I always saw it at sprint stores and couldn't put it down. Now it's in my hand, doesn't seem so great. Think my htc10 is better, but maybe I'm missing how to make it great.
I hope this is in the right place.
Click to expand...
Click to collapse
I am with ya on that...I started with Samsung devices, So using Odin for flashing was my cup of Tea. The Nexus6 was my first device using Fastboot, but I ended up using Wug's toolkit most of the time.
From what I gather the A/B slot partitions are the same thing. You basically have a kernel and ramdisk on both partitions. The ramdisk is now your recovery. You just have to make sure when you flash anything, it's to the active partition. The point of A/B slots is so Android can install upgrades seamlessly while still running by installing them to the inactive partition. Click the link in the OP, it explains things pretty well.
I have been pretty happy with the PH-1 so far. I really like the form factor and the notch hasn't bothered my at all. Coming from Note 3/4 and the 6P which was super easy to flash by the extra steps on the Essential don't seem to bad. Sucks that you need a computer most times to flash but not the end of the world.
I haven't flashed a custom ROM yet but I did bump to the P preview for a day or two and then back to stock with EX and Magisk. No issues there but I'm comfortable with ADB and fastboot. No issues with various cables as well whatever I used on my 6P seem fine for this phone as far as charging, adb and file transfers go.
Overall pretty happy.
Hello, I've tried to install multiple roms on my phone and none of them work.
I tried to install many versions of twrp without success. Some of them include twrp for Ulefone Armor 6, Armor 2, twrp for mediatek mt6750, mt6739, and even supposedly twrp for Ulephone Armor 5 (not to be confused with my model, which is 5s) and others.
I even tried orangefox, philz, redwolf and clockworkmod.
None of them worked. What happened is when I tried to boot into recovery, it would turn on, turn off, turn on again and boot into the stock OS.
I even tried to install ROMS without a custom recovery, using fastboot.
I tried a custom version of lineage os, supposedly made for ulefone armor 5 (I tried the arm64 a only version.) : https [column//] sourceforge [dot] net/projects/andyyan-gsi/files/lineage-16.x/
I tried resurrection remix too (oreo arm64 a only)
the command I used is fastboot flash system custom_rom.img
After installing each rom, each time I tried to boot a custom rom, it would turn on, show me the message that my device is in the orange state, shut off, reboot and repeat. So yeah, I bricked my phone. Then, I installed the firmware for ulefone armor 5s with SP flash tool and I'm back to square one.
I don't know if I should try graphene os, since inside a folder containing the image files, there is a text file which states that a sargo board is required, whatever that means. ("require board=sargo")
So yeah, I don't know what to do. I need a rom that is open source, and without gapps.
Any help is appreciated.
I'm even willing to try ubuntu touch, if that works
I'm even willing to try ubuntu touch, if that works
3simplex said:
This phone is a tank, I don't want to be stuck with Android 9 forever.
Click to expand...
Click to collapse
Do a Google search for:
"Custom ROMs for (your specific model number)"
If there are any ROMs for your device, that search will find them, if it does not find anything then there is nothing for your device. This means that if you want to use custom ROMs on your device, you will have to build your own TWRP or port TWRP from a similar device to work on your device then you will have to build your own custom ROMs or port custom ROMs from a similar device. If you're wanting or waiting for someone to build them for you, you are in for a very long wait. Developers build ROMs for the devices they personally own, they do not build ROMs for devices that other people own if the developer does not own the device. In other words, around here, we help people find what they are looking for but we will not do the work for them. If you want it but it doesn't exist, you will have to be the one to create it for yourself, not someone else.
Sent from my SM-S767VL using Tapatalk
3simplex said:
Great advice we are obviously idiots, thanks for pointing it out for us. I will Google search and see if I can find your balls. Hmm, nope I guess they don't exist. Troll elsewhere douche.
Click to expand...
Click to collapse
Who is trolling? Trolls get reported here, which I could do to you for the words you are using. I'll give you a pass this time because I'm a nice guy but that is your only freebie from me, your next disrespectful post will not receive the same exception.
What I posted is how things go here and what to expect, you just didn't want the truth. If that offends you, then that is a failing on your part. You're more than welcome to find another android website where they are willing to lead you by the hand and spoonfeed you when you want something that you are too lazy to find, do for yourself or have the ability to achieve on your own mental merit, because you surely won't find that here at XDA. If you choose to stay at XDA, be prepared to do the real work yourself.
Accept it or not, that is the way it is. Spouting childish insults won't change that.
Sent from my SM-S767VL using Tapatalk
I've got the Oukitel WP16 which a 64 bit and has an octa-core MediaTek Helio P60 MT6771V on Android 11. Actually a pretty decent rugged phone. Originally tried to root it through fastboot and bricked it about 2 weeks after getting it. For the life of me, I couldn't bring it back to life. Finally after 4 months of it just sitting in a drawer, I went about flashing it to bring it back to life a little differently than I was before and it stuck. Very thankful that it was working again because in those months I had destroyed 3 of your average break if you touch them phones. However me being me, getting it going again wasn't enough. So I gave rooting it a try again. Got it! Rooted with Magisk. Now because I have one of those devices I believe is under rated and under developed, I can't find any kind of development done on it whatsoever and want to build/port TWRP so I'm able to try a GSI ROM. My problem is that every tutorial I read or watch has nothing like what is my stock ROM. Either names of files are different or I find the files in other folders, I've got more folders than what I'm trying to port, and, I would need to double check again, but I wanna say that I've even found them in different partitions. So my question is, what do I do? Like fstab is not in the recovery but in something else. That something else that has fstab in it, my port doesn't have that folder at all. And there are others like that. I've tried several, I repeat SEVERAL different tutorials and cannot figure out what to do. I know it's beyond the capabilities of the tool, but I even tried one of those Hovatek port tools. Obviously didn't work because of the kernel. So to say I'm lost is an understatement. This isn't the first phone I've tried this with. Had another 64 bit with the same chipset that actually had a unofficial TWRP built for it. But when it came to try to port a ROM, I was left with files in different folders and things that weren't in the ROM i was trying to port. I eventually just have up because I kind of had to since scuba diving with the phone here in the Mexican Caribbean finally took it's toll on the phones external hardware. But yeah, back to my only question. What do I do in this situation? I'm mainly concerned about it because this WP16 has a night vision camera on it which I use quite often and don't want to lose that. Recovery has nothing to do with the camera but the ROM I'd like to port will. So figuring out what to do with the recovery could eventually lead me to my answer with the ROM. Anyway, kind of a long winded explanation just to get to what may seem like a simple question to some. Any help would be greatly appreciated.
finnroth69 said:
I've got the Oukitel WP16 which a 64 bit and has an octa-core MediaTek Helio P60 MT6771V on Android 11. Actually a pretty decent rugged phone. Originally tried to root it through fastboot and bricked it about 2 weeks after getting it. For the life of me, I couldn't bring it back to life. Finally after 4 months of it just sitting in a drawer, I went about flashing it to bring it back to life a little differently than I was before and it stuck. Very thankful that it was working again because in those months I had destroyed 3 of your average break if you touch them phones. However me being me, getting it going again wasn't enough. So I gave rooting it a try again. Got it! Rooted with Magisk. Now because I have one of those devices I believe is under rated and under developed, I can't find any kind of development done on it whatsoever and want to build/port TWRP so I'm able to try a GSI ROM. My problem is that every tutorial I read or watch has nothing like what is my stock ROM. Either names of files are different or I find the files in other folders, I've got more folders than what I'm trying to port, and, I would need to double check again, but I wanna say that I've even found them in different partitions. So my question is, what do I do? Like fstab is not in the recovery but in something else. That something else that has fstab in it, my port doesn't have that folder at all. And there are others like that. I've tried several, I repeat SEVERAL different tutorials and cannot figure out what to do. I know it's beyond the capabilities of the tool, but I even tried one of those Hovatek port tools. Obviously didn't work because of the kernel. So to say I'm lost is an understatement. This isn't the first phone I've tried this with. Had another 64 bit with the same chipset that actually had a unofficial TWRP built for it. But when it came to try to port a ROM, I was left with files in different folders and things that weren't in the ROM i was trying to port. I eventually just have up because I kind of had to since scuba diving with the phone here in the Mexican Caribbean finally took it's toll on the phones external hardware. But yeah, back to my only question. What do I do in this situation? I'm mainly concerned about it because this WP16 has a night vision camera on it which I use quite often and don't want to lose that. Recovery has nothing to do with the camera but the ROM I'd like to port will. So figuring out what to do with the recovery could eventually lead me to my answer with the ROM. Anyway, kind of a long winded explanation just to get to what may seem like a simple question to some. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Your device already have TWRP [Firmware version: OUKITEL_WP16_RU_V04_20220621 ] but you not need Custom Recovery for install GSI. Use stock recovery.
About GSI with a night vision camera support so is much expensive solving that. You can try but need very experience and patience of the tests and solutions.
lopestom said:
Seriously? Thank you! I'm guessing the link is gonna be in 4pda being that it's Russian? I've spent a month searching and haven't found anything whatsoever. And since I don't read Russian, I always overlook 4pda even though it's been a great resource in the past. And yes, I'm aware you don't "need" custom recovery for GSI's. It does make things a little easier for me though.
Click to expand...
Click to collapse
The recovery issue will be solved since there is a recovery out there. That still doesn't solve the mystery and problem i have of files being in different places though. In that case what do I do if the files isn't in the same place in the port as it is in the stock, or the other way around? Add the stock file to the same folder it is in for the port? Or should I make a new folder in the port that's name is the same as in the stock? If neither, what do I do?
finnroth69 said:
Seriously? Thank you! I'm guessing the link is gonna be in 4pda being that it's Russian? I've spent a month searching and haven't found anything whatsoever. And since I don't read Russian, I always overlook 4pda even though it's been a great resource in the past. And yes, I'm aware you don't "need" custom recovery for GSI's. It does make things a little easier for me though.
Click to expand...
Click to collapse
No! Search my repository in the github in the release option.
finnroth69 said:
The recovery issue will be solved since there is a recovery out there. That still doesn't solve the mystery and problem i have of files being in different places though. In that case what do I do if the files isn't in the same place in the port as it is in the stock, or the other way around? Add the stock file to the same folder it is in for the port? Or should I make a new folder in the port that's name is the same as in the stock? If neither, what do I do?
Click to expand...
Click to collapse
As I wrote before, it is very difficult to solve issues like the original stock ROM camera. There are even one or two people who managed to get this to work.
Now what you don't understand: If you want a Custom ROM, use GSI and adapt, solve, analyze and test by changing some stock ROM files in GSI. You must understand that you need experience and time. You can even compile a Custom ROM - any GSI - specifically for your device. So you just need to have the source code of your device, have the GSI source code and know how to compile the file so that you can do the tests. Again, you must understand that you need experience and time.
If you haven't researched what is GSI and still think that Custom ROMs portability that happened before until Android 7.1 then look, read and update yourself.
In your questions, be as detailed as possible. You write a lot of parts and you scramble the words.
As for having GSI normally I already wrote where there is an instruction to install and you follow. As for TWRP, look it up on my github.
As for solving something in the GSI, if you managed to install it and still used the phh options to try to fix any bad part, then it is only you who will be able to solve any error/adaptation/bug/extra installations that there.
Trust me when I say I understand what you're saying. I have done some testing I have watched tutorials, I have studied. but everything that I have seen is basically switching a file from a folder on the stock ROM to a folder in the ported ROM with the same name as what's in the stock ROM, and possibly adding a little script to something. What I'm trying to figure out is what I asked. Fstab is not in recovery on my phone's stock ROM. It is in something else. But fstab is in and a part of recovery for TWRP. So even though there might be a TWRP for my phone doesn't help me to know if I should be creating that same folder that's in my stock ROM in the ported one for fstab or other files that are like it. I have downloaded the TWRP from your profile and I've gone to the 4pda and discovered that you're the dev who ported it with and without encryption. Nice work and thank you! I would like to move beyond being a flash baby though. So I'm simply trying asking that one specific question to help me learn because it is something I am lost on. Whether it is to port recovery, port a ROM, or whatever, I don't know what to do when the location of the files I need to port from the stock aren't matching with the with the location of the files in the port itself. Fstab is just one example. I'm gonna send you a friend request. Later when I fire up my laptop, I'll take screenshots to physically show you exactly what I mean. Please be patient and don't get upset at me for trying to learn. As well as please take your time in responding. It's no rush since I've got a business to run and this is something I'm trying to teach myself on the side. It really is something I'm lost on, and if I'm lost on it, how many others has it confused as well?
As for the camera app issue. We can forget I asked that also. I understand completely what you're saying about it being far beyond my reach right now. Thank you for the heads up on that.
Mr. Lopestom can you please help me with your recovery images? I cannot seem to get any of them to boot. I've tried the with script found on 4pda, without that script, I've tried flashing an empty vbmeta, but nothing is getting the images to boot. See attachment for script I'm talking about. Attachment only shows me running it, but I have tried without.
What sense does it make to flash an empty VBMETA ? You typically pull the existing VBMETA and pass this file to Fastboot what rewrites 2 bytes in that file.
finnroth69 said:
Mr. Lopestom can you please help me with your recovery images? I cannot seem to get any of them to boot. I've tried the with script found on 4pda, without that script, I've tried flashing an empty vbmeta, but nothing is getting the images to boot. See attachment for script I'm talking about. Attachment only shows me running it, but I have tried without.
Click to expand...
Click to collapse
The problem is not in the vbmeta file. You can use this one if you can: Post in thread 'Looking for a walkthrough on installing a custom ROM on a BLU G90 PRO' https://forum.xda-developers.com/t/...om-rom-on-a-blu-g90-pro.4253737/post-85180967
The big fact is that the company put a recovery.img stock file inside /vendor/etc/ and you should know how to deal with it. So only removing this recovery.img and repacking modified vendor.img made by u; install that in your device so you can have TWRP.
jwoegerbauer said:
What sense does it make to flash an empty VBMETA ? You typically pull the existing VBMETA and pass this file to Fastboot what rewrites 2 bytes in that file.
Click to expand...
Click to collapse
I'm not sure to be honest with you. Like I told lopestom, I'm just trying to teach myself as I can in my free time. A lot of what I do is imitate what I see or read. While reading post about flashing twrp i had read something about flashing an empty vbmeta file.