Related
I made a clean ROM based on the factory ROM for the Lenovo A789, A660 and P700i
Cleaned up ROMs:
- A789_S227_cybermaus_V2 (below)
- A789_S228_cybermaus_V2.1 (further below)
Ported ROMs (ported from P700i):
- A789_ROW_S105_cybermaus_ICS_V3 (further below)
- A789_ROW_S106_cybermaus_ICS_V3.1 (Further below)(also for A660 and P700i)
- A789_ROW_S107_cybermaus_ICS_V3.2 (Further below)(also for A660 and P700i)
The current and advised rom to use is A789_ROW_S106_cybermaus_ICS_V3.21
Based on factory ROM A789_S227_120827, and located in my Dev-Host. It is as close to factory as possible, which I hope will be good for stability. It is a flash-utility ROM, because it also holds the latest preloader, uboot and recovery. Assuming those are OK, followup fixes will be update.zip style.
Summery of changes:
- Rooted the phone with Chainfire SuperSu
- Set to boot in US-english, changed name of ROM
- Added MoreLocale for extra languages in 3rd party apps
- Removed Chinese apps, incl Chinese keyboard, removed SmsReg.apk
- Left Lenovo Security (anti-malware) and Lenovo (Go) Launcher intact
- Added Google GAPPS, Play Store, Maps, etc
- Added MobileUncle toolbox, SManager (root explorer). Titanium backup (free version)
- Added fix for location services
- Added CWMT recovery image (modded from 593cn.com)
- Added Skype, Whatsapp, and some others, as auto-install into userdata upon wipe
- Prepared busybox (you need to run script /system/xbin/installbusybox as root if you want it)
- Replaced bootup animation with clean Lenovo butterfly
- Replaced all some audio files with english named ones (thanks mabuc)
- Caller ID bug still present, sorry
- Just as a reminder, these ROMS have English and Chinese only.
Instructions:
By default, the ROM will not overwrite USERDATA or FAT. If you want a clean slate, first extract empty.userdata.rar and/or empty.fat.rar
- Read bgcngm flash tutorial.
- Read it again
- Start Flash Tool (v3.1222, in my Dev-Host)
- Load scatter file
- Take out USB cable and replace battery
- Press the download button in the flash tool
- Connect the USB cable
- Wait for the flashing to complete
A789_S228_cybermaus_V2.1 (no longer current, Use V3 instead)
Based on factory ROM A789_S228_120913, and located in my Dev-Host. Similar to V2, but newer, and a few extra fixes. It should be noted that the S228 is listed to solve unexpected crashes, so an important update in itself.
I do not have a A789, so it is a blind build. Until I get positive feedback, consider untested. Don't be the first to try if you are not experienced.
Summery of changes:
- Same as on V2, and additional
- Removed 2 more chinese apps that I forgot last time
- Prepared busybox (you need to run script /system/xbin/installbusybox as root if you want it)
- Added a tweak so USB-Debug notification is no longer shown
- Added a tweak so Wifi works on all 14 international channels (rather than only the 11 US ones, may be undone if you set a different locale)
Instructions:
This is a update.zip type ROM. So you need the custom recovery, see post #3,
A789_ROW_S105_cybermaus_ICS_v3.03
Based on P700i_ROW_S105_120920, see this separate post.
A789_ROW_S106_cybermaus_ICS_v3.11
Based on P700i_ROW_S106_121001, see this separate post.
Please note that this ROM I also build for the P700i and A660. See same post.
A789_ROW_S107_cybermaus_ICS_v3.2
Based on P700i_ROW_S107_121221, see this separate post.
Please note that this ROM I also build for the P700i and A660. See same post.
Below:
Post #2: Small review and fix of location services
Post #3: Custom recovery image
Post #4: Root your phone / install GAPPS
Also, many issues for the A789 are similar to those of the A750, so if you have questions, do search that Lenovo A750 thread to.
Thanks
Also thanks to bgcngm for his help, and to jazzor for his help
=================
BTW: Due to new forum rules, resulting in a large number of people that cannot post into developer threads and that subsequently PM me, I open op a new Q&A thread.
I am not going to be policing, so you can post where you like, but I invite everyone to use this new thread for any Q&A, and this thread for ROM releases and deep development talk only.
Consequently, if you PM'ed me, look for your reply in this new thread
Thanks
====================
PS: do drop me a reply if you use or tried it! Or press the 'thanks' button.
So, I got my first glimps at the A789. So to speak. My colleague was holding it while we were audio-skype, so I did not actually see it.
His A789 came with a Etotalk ROM by Dean, which I now suspect is a reworked Smileyvvv ROM with Sony Experia interface. Not bad, but as you know, I am a 'factory ROM' guy. My colleague may also be, because he had already replaced the the SE launcher with GO Launcher, which is the default Lenovo one. Also my colleague said it jammed a few times, which it still has not done on my factory A750 ROM.
Most of the phone worked, but a few tips for others out there:
- The phone still has the Called-ID bug. Even though it is newer 4.0,4. I know some of you claim this is solved on ICS Mediatek, but I still claim it is solved in *some* of the cases, not all, it also depends on how your provider sends the caller ID info. Anyway, you can work around it with the prefixer app as reported before.
- It did not come with the MobileUncle tool, but with the Etotalk tool. Which was not updated for the new MT6577 chip, so it had no Engineer Mode. Install the latest MU tool (version 20120813v2.2.0 its in my Dev-Host), so you get one with MT6577 Engineer mode.
- Recovery Mode was hard to get into. Like the newest A750 preloader, you have to press the power putton *just before* you press both volume buttons. But it did came with the CWMR Touch, though its Touch function was broken, so buttons only. They probably simply tried recovery images of other models, and did not properly build one with the A789 kernel, but it does not matter, it works well enough.
- Location services did not work. Update the phone with the ICS_locationfix_v1.3 update using recovery mode. While you are in recovery, also wipe cache. And finally, go into MobileUncle tool, the MTK Engineer mode, and in location settings, change the NetLoc from MEDIATEK to GOOGLE. Now your location services should work.
Lenovo A789 Recovery
I created a recovery image for the Lenovo A789 based on ClockWorkMod Touch 5.5.0.4. However, I do not own a A789, so until I have reports of it working, consider it untested. You can download it from my Dev-Host: File A789_S22x_recovery_cybermaus.rar
NOTE: It has come to my attention this recovery works well, except the nandroid backup function, which is broken. If you value nandroid backup, install the APKHOT one below.
While doing this, I also found a full APKHOT distro which had what seems to be a CLockWorkMod (non-Touch) recovery in it, so I extracted that and also uploaded it. That too you can download from my Dev-Host: File A789_S22x_recovery_apkhot.rar
Both of them you will have to flash using the flash tool, using bgcngm's excellent manual, and the V3.1222 of the flash utilities and drivers, also in my Dev-Host. If you flashed my V2 ROM, you do not need to do this, as the recovery is already part of that.
Once you have the recovery installed, you can enter it by pressing both VolumeUp/Down while booting the phone. Due to an issue with the preloader, it may be needed to press the power button slightly before both volume buttons. If the phone seems stuck, it means the preloader messed up, remove battery and try again.
Inside the recovery (the Touch variant) you can navigate not only by its physical buttons, but also by screen buttons, and by gestures: swipe up/down for up/down, left for back and right for enter.
The first few people using this, please report your findings, good or bad.
PS: As alwasy, thanks to bgcngm for his unpack utilities, which I used to modify the recovery.img
Lenovo A789 Root; GAPPS, Location DIY
Its been mentioned before, but if you have a working recovery (like above, hopefully), you can always yourself root your phone. Simply install (from inside the recovery) chainfire's "CMW installable ZIP"
Link to his post: (ignore his big red requires root warning)
The file you need is labeled "CWM installable ZIP" at the bottom.
Direct link to the file you need to install via recovery update.zip
And while you are at it: You probably also want to install the latest Google Mobile Services (better known as GAPPS) from CyanogenMod V9:
Explaining wiki from CyanogenMod
The file you need is called gapps-ics-20120429-signed.zip and can be found here
You probably also want to wipe your cache partition after doing this.
To complete this DIY of fixing factory ROM: On Chine phone typically the location services do not work. Update the phone with my A750 V1.3 update using recovery mode. (it works on the A789 because it is a minor update, but *DO NOT* any of the other A750 updates on the A789. I repeat, do *NOT* flash A750 on A789). While you are in recovery, also wipe cache. And finally, go into MobileUncle tool, the MTK Engineer mode, and in location settings, change the NetLoc from MEDIATEK to GOOGLE. Now your location services should work.
Good luck
PS: If either update.zip refuses to install, remember to turn off the checksum and assert checks in the recovery.
And thanks to Chainfire for his work, and the team at CyanogenMod for theirs.
cybermaus said:
Before I can help, please provide some info:
Can you tell me what ROM you have?
Which flash tools did you use to root?
Also, do you have a working recovery?
Click to expand...
Click to collapse
hwonggc said:
I fix the proximity thingy. it's caused by my lousy screen protector. But i've got another bigger problem now. I've accidentally uninstalled the default system home screen. I cant assess anything now. I tried flashing a recovery inside but it still doesn't work as factory. I use SP flash tool v3.1.222.00
---------- Post added at 06:32 AM ---------- Previous post was at 06:18 AM ----------
dont think my recovery is working. Could you please provide me with a working recovery? =(
Click to expand...
Click to collapse
Yes, a recovery is on the todo.
But for now, you did not answer my questions yet:
- Can you tell me what ROM you have? Or had. Original Lenovo Factory, Etotalk-Dean, some other?
- Which flash tools did you use to root? Or rather, which files did you flash using that tool to deal with root. Actually, the fact that you had to root it yourself probably means you had factory ROM, but please confirm.
As stated, I am uploading S221 original to my Dev-Host. Flash that with the flash tool. On short notice, that is all I can do. On longer notice, I will help you, but give me some time.
Edit: In fact: You you already have messed up your recovery, and I do not have a A789 to play with myself, you may be my guinea pig for the recovery build. So I will work on that today. (as today is not a working day for me anyway). If you do not mind being a tester. After all, the damage is already done, and you apparently already know how to flash using the utility.
EDIT: @ hwonggc : Please test recovery in post#3. Just update your post below with results, or PM me. I would like to avoid too many new posts on this while we are testing.
cybermaus said:
Yes, a recovery is on the todo.
But for now, you did not answer my questions yet:
- Can you tell me what ROM you have? Or had. Original Lenovo Factory, Etotalk-Dean, some other?
- Which flash tools did you use to root? Or rather, which files did you flash using that tool to deal with root. Actually, the fact that you had to root it yourself probably means you had factory ROM, but please confirm.
As stated, I am uploading S221 original to my 4Shared. Flash that with the flash tool. On short notice, that is all I can do. On longer notice, I will help you, but give me some time.
Edit: In fact: You you already have messed up your recovery, and I do not have a A789 to play with myself, you may be my guinea pig for the recovery build. So I will work on that today. (as today is not a working day for me anyway). If you do not mind being a tester. After all, the damage is already done, and you apparently already know how to flash using the utility.
Click to expand...
Click to collapse
Yes yes. I had the factory rom. I got the phone just yesterday evening and this afternoon it's half dead already. I use smart phone flash tool to root using a file i got from http://www.fight.org.ua/publications...novo_A789.html. Everything was fine until I deleted the original home UI and the apex launcher also. So there isn't anything I can do. I'm downloading the S223 from some russian site and try, hopefully I can find some luck there. Downloading slowly~ sighhhh.
---------- Post added at 07:49 AM ---------- Previous post was at 07:40 AM ----------
BTW~ i'm willing to test out your rom too! I wouldn't want to sound too demanding, put please please put in the play store will ya?
I posted the custom build, see first post. It may take a while before I can get it uploaded, I am on a bad link.
Also, there have been 20 downloads on the recovery image. Come on guys, someone must be able to provide feedback about it working or not!
A789_S227_cybermaus_V2 ROM is working
Hello
Thanks for Your work.
Your A789_S227_cybermaus_V2 ROM is working.
Simple Flashing and start without problems. Now I must check some functions.
Thx again
basell
Edit:
The 3g connections don't work at first run. After restore they start but in My opinion with less sensitivity (compare to stock rom). It's look like A789 loose some frequency on witch can work.
Edit2:
And they have some strange behavior - After couple min of data connection (on 3G) they disconnect with information - "Restricted access changed" and the same is when I try to choose network manually. After that sometimes they login to 3G sometimes they change to EDGE.
In Stock version (S221) was not this kind of problems.
Edit3:
In place with good 3G signal I have no problem with data transfer.
How Can I check on witch frequency (2100,900,850) I have connected My data transfer?
Thanks for testing
Well, I definitely did not mess with any of the 3G stuff. So if it is true that 3G is less sensitive, then I would claim it is true for the factory S227 vs factory S221, and not directly related to my cleanup of it.
But (sorry to say so) I have learned to take claims of improved or degraded radio sensitivity with a grain of salt, even for the factory ones.
Having said that: Restoring S221 radio into S227 firmware is easy. The radio is separate firmware file, and I can extract the S221, S223 and S227 firmware in a separate file, so you can test. Were you actually using factory S221, or some other?
As to whether it is using 2100, 900 or 850: I can probably figure out how to get that info, *BUT* reality is that your provider most likely has only one frequency anyway. Most, pretty much all, EU providers are on 2100. The phone could not get to 900, simply because your provider does not have that frequency in the air (not for 3G anyway). And 850 is not supported at all on this phone.
Anyway, inside MU utility, engineer mode, bandmode, you can check/set the frequencies that are supported.
But please run a proper test if 3G is really degraded. As stated. it is so often a empty claim, I am somewhat careful to follow it. You want me to extract the 3 versions of firmware files in update.zip files?
Also, what country/vendor are you? please list the MMC and MNC from inside the APN settings.
Hi
If You will prepare this files I can test it tomorrow.
I'm from Poland and I have two frequency on data transfer - 2100 and 900. But I don't know if A789 use only one or change them. The place I'm test the signal is poor and I don't see if I work on 2100 or 900.
If You can, pleas tell me what kind of tests I can do to do that properly
Ok, here they are. update.zip type.
I only have S221 and S227, but the firmware files were indeed different, in more than just their timestamps. Of course, normally I would assume newer is better. So to make it clear: below files only replace the radio&dsp firmware, not the phone firmware.
Try to test honestly for yourself. Same conditions, same place, same time (because network load can make a difference)
It is possible that 3G really is degraded in S227, but as mentioned, I learned to not jump to conclusions just because the network is having a bad day.
WARNING: I retracted the two attachment, because I made a typo in the installer script. While the firmware is for the A789 (MT6577), the installer script is for the A750 (MT6575). Sorry. I will upload the correct ones in a moment.... Anyone that took a copy of these files before Oct 14, delete them!!!
I suspect the install would simply have failed, no harm done, but best to get rid of all copies anyway
BTW: basell, is that why you asked how to install? Really, if you ask for help, you should provide a bit more info. Anyway, I attached newer scripts, if you still want to try.
sorry for My question but :
How to install this firmware?
Like any update.zip on android. Go into recovery (see post #3) and apply the update.zip
i have the problem that the netlocation doesn't work with google maps, i flashed the cyber update 1.3, nothing changed, what should I do now?
And this is on what phone and ROM?
Anyway, to quote myself: "While you are in recovery, also wipe cache. And finally, go into MobileUncle tool, the MTK Engineer mode, and in location settings, change the NetLoc from MEDIATEK to GOOGLE. Now your location services should work."
many thanks, Cybermaus, netlocation works again after your instruction
Hi,
Thank you very much for building the ROM !!
I am using it for 3 days now and I am happy to report no problems with it. Everything works and most important: no more freezes !!!
my A789 came with the Etotalk by Dean ROM which was mostly OK, but was freezing from time to time (some days not at all, other days several times a day - most of the times when hanging up a call or, when trying to do wake it from standby: I was pressing the power button, but the screen would not light up).
Other things I like about this ROM:
- all phone functions work great
- Google Play works perfectly
- is rooted
- it has the Lenovo battery app, which is great! I am not 100% sure if this is the reason, but the battery life went from 1 day to 2 days
- I had no issues flashing it
- CWMT recovery works
Also, so far, I did not experience any 3G issues
I have written a small review of the Lenovo Security app, which you guys may want to put back on your phone if it was cooked out of it.
jman0 said:
Thinking it twice, I've remembered another reason. One of the things I like most about the apkhot rom I'm using is that the external sdcard is mounted on /sdcard and not /mnt/sdcard2, which avoids problems with many apps. I tried one of the newest apkhot roms, based on s227, and none of the tricks to exchange /sdcard and /mnt/sdcard2 worked with it.
Click to expand...
Click to collapse
Well, that is actually an easy change to perform, just change the /etc/fstab.vold
However, if you go into settings->storage, the first option is default write disk. Change it from USB storage(the internal SD) to SD (the external SD)
So no hacking is needed at all.....
I've been running your rom for around 6 hours now. Everything runs fine. The 3G connection worked without much trouble. The only thing I haven't been able to do is performing a backup with the CWM Touch Recovery. So, I've just flashed the recovery I had on the apkhot rom I was using, using Mobileuncle tools, and now I've been able to create a backup.
So far, so good, and I've noticed a slight performance increase, too.
This ROM has some FCs on third party apps (such as Facebook, some Bank apps, etc.), so I deleted all the ROM files because they are useless at this time. Due te fact I have no more time to spend on this project, a moderator can close this thread!
Thank you!
Very well done! I just have one question: what does the CellBroadcastReceiver package do, and why is it installed if we don't need it?
gvlfm78 said:
Very well done! I just have one question: what does the CellBroadcastReceiver package do, and why is it installed if we don't need it?
Click to expand...
Click to collapse
In many Countries they use it to broadcast anything useful/vital to people life. In Italy it's used by Vodafone to broadcast the Province/CellID in GSM, channel 50, and TIM for the "Arancione" plans (does it exist anymore?) to bill by Province/CellID (I don't remember the channel ID).
The -> real <- thing, in Italy, is the battery drain!
The modified Twrp does not work for me... the original twrp link is offline and the standard 2.8.7.0 is not working on fever, and the working version of twrp that i found online (that is 3.0.something) is not able to install this rom for the error "signal 11" Then i do not know how to install this rom... if someone has advice, or has installed it, let me know.
Melkor_98 said:
The modified Twrp does not work for me... the original twrp link is offline and the standard 2.8.7.0 is not working on fever, and the working version of twrp that i found online (that is 3.0.something) is not able to install this rom for the error "signal 11" Then i do not know how to install this rom... if someone has advice, or has installed it, let me know.
Click to expand...
Click to collapse
What problems do you have with the modified Twrp? By the way, the Twrp itself was not modified, only the kernel (stock V39 Fever LL) and I deleted the last page asking to install SuperSu everytime... not so useful, because I use to install it separately, or with the Rom with scripts!
The only issue I have with Twrp 2.8.7.0 (vs. 3.x) is that it's continuosly flickering in upper screen, but it's useable for the two/three items it has to do (format/wipe/install).
These problems doesn't appear on Twrp 3.x, but we can not use it, because it expects MarshMallow filesystem paths format and support,... vs we are using Lollipop format. You got signal #11 because the scripts cannot mount and find the /system filesystem were they expects to find in LL format while you are using Twrp 3.x in MM format!
If you'll try to start Twrp 3.x on kernel 3.10.x (LL), if it starts for whatever miracle, you'll get tons of signal #7 errors bacause the /rootfs of the Recovery image is based on MM files and libraries, while Twrp 2.8.7.0 is based on LL files and libraries and does not start on kernels 3.18.x (MM).
Lastly, have you clicked on the "d-h.st/82jl" link? I clicked on it, now, and I downloaded it with no problems... (the original 2.8.7.0 twrp!)...
@Melkor_98 @sun75 When I installed RR for the Canvas 5 on my Wiko Fever I first had to install the Canvas 5 TWRP recovery. This was because otherwise I got a signal 11 error as the updater-script was setup for the Canvas 5 (changing it cause some other errors...). With the Canvas 5 TWRP I had the strange black lines flickering at the top of the screen and some other minor bugs. But then, when I had to reinstall it because the IMEIs were not working, I first flashed the stock Canvas 5 LL firmware ROM and then the recovery. This time it worked perfectly as if I had a Canvas 5. So this could possibly be related as the issue appears to be similar.
gvlfm78 said:
@Melkor_98 @sun75 When I installed RR for the Canvas 5 on my Wiko Fever I first had to install the Canvas 5 TWRP recovery. This was because otherwise I got a signal 11 error as the updater-script was setup for the Canvas 5 (changing it cause some other errors...). With the Canvas 5 TWRP I had the strange black lines flickering at the top of the screen and some other minor bugs. But then, when I had to reinstall it because the IMEIs were not working, I first flashed the stock Canvas 5 LL firmware ROM and then the recovery. This time it worked perfectly as if I had a Canvas 5. So this could possibly be related as the issue appears to be similar.
Click to expand...
Click to collapse
Yes, it can be true, but the problem is Wiko and Canvas have different partition schemes: Wiko has one partition more (Apedata) and different partition sizes and entrypoints vs. Canvas. (refer scatter file...). If you change your phone to Canvas, make sure to FIRST, make a *complete* ROM backup of all 26 partitions to files with SP Flash Tool!
Then you can format all the flash eprom, and restore the Canvas Rom. So you will need the SN Write Tools to restore IMEI/WIFI/BAR Code/BT mac addr using the Canvas mddb database.
Then you have to restore all the Wiko hidden partitions except the system, boot and recovery, but from now on, you have to use the Canvas scatter file, because you changed the partition scheme!
Hidden partitions are important because they contain calibration data, security keys, crts, etc... For sure they are used on Stock Roms, ... I don't know if custom Roms use them...
So, be careful on mixing the correct scatter file being on Canvas or on Wiko type Rom...
sun75 said:
What problems do you have with the modified Twrp? By the way, the Twrp itself was not modified, only the kernel (stock V39 Fever LL) and I deleted the last page asking to install SuperSu everytime... not so useful, because I use to install it separately, or with the Rom with scripts!
The only issue I have with Twrp 2.8.7.0 (vs. 3.x) is that it's continuosly flickering in upper screen, but it's useable for the two/three items it has to do (format/wipe/install).
These problems doesn't appear on Twrp 3.x, but we can not use it, because it expects MarshMallow filesystem paths format and support,... vs we are using Lollipop format. You got signal #11 because the scripts cannot mount and find the /system filesystem were they expects to find in LL format while you are using Twrp 3.x in MM format!
If you'll try to start Twrp 3.x on kernel 3.10.x (LL), if it starts for whatever miracle, you'll get tons of signal #7 errors bacause the /rootfs of the Recovery image is based on MM files and libraries, while Twrp 2.8.7.0 is based on LL files and libraries and does not start on kernels 3.18.x (MM).
Lastly, have you clicked on the "://d-h.st/82jl" link? I clicked on it, now, and I downloaded it with no problems... (the original 2.8.7.0 twrp!)...
Click to expand...
Click to collapse
I thank you for the answer, yes that link after some ads bring me to a page that do not load... about twrp i should try to bring back to LL the phone with the official tool of wiko and with that situation restart to unlock bootload /flash twrp 2.8.7/ install rom? For exemple i use the tool taken from andoidiani (i can not post link...) that should bring back everything to android 5.1 status? ps on the last version of MM for fever (the one that i have) if i flash a different version of twrp that is not the 3.0.something the recovery do not start, the phone remain on the "wiko" screen and stop here...
Melkor_98 said:
I thank you for the answer, yes that link after some ads bring me to a page than do not load... about twrp i should try to bring back to LL the phone with the official tool of wiko and with that situation restart to unlock bootload /flash twrp 2.8.7/ install rom? For exemple i use the tool taken from andoidiani (i can not post link...) that should bring back everything to android 5.1 status?
Click to expand...
Click to collapse
No, you shouldn't bring back to LL the phone nor unlock anything! I was on MM, and simply flashed with SP flash tool the boot.img & recovery.img. Once in recovery, I erased all except the microSD, and then, installed the Rom.zip. Done.
What problems do you have with recovery flashing it with SP flash tool? It does not start? Let me know!
For the original TWRP you can see here (Twrp Beta1 for LL): Link! I'm correcting the OP!
sun75 said:
No, you shouldn't bring back to LL the phone nor unlock anything! I was on MM, and simply flashed with SP flash tool the boot.img & recovery.img. Once in recovery, I erased all except the microSD, and then, installed the Rom.zip. Done.
What problems do you have with recovery flashing it with SP flash tool? It does not start? Let me know!
For the original TWRP you can see here (Twrp Beta1 for LL): Link! I'm correcting the OP!
Click to expand...
Click to collapse
I was using adb Fastboot, to first unlock the bootloader (that with the wiko tool return locked if you recover the phone) after i use the fastboot command to flash the recovery img, with the classic "fastboot flash recovery" Should i use SP flash tool to flash the twrp 2.8.7? (the reason of why i was using adb fastboot is becouse fever has not the removable battery and sp flash tool have difficulty do detect him)
Melkor_98 said:
I was using adb Fastboot, to first unlock the bootloader (that with the wiko tool return locked if you recover the phone) after i use the fastboot command to flash the recovery img, with the classic "fastboot flash recovery" Should i use SP flash tool to flash the twrp 2.8.7?
Click to expand...
Click to collapse
Yes, you'll bypass the OS, flashing directly the recovery.img to the flash! I never used adb fastboot, etc. commands on Wiko,... and I never unlocked the bootloader! Maybe with other phones it's mandatory, but with the Wiko Fever, you can flash directly on top with SP Flash Tool!
sun75 said:
Yes, you'll bypass the OS, flashing directly the recovery.img to the flash! I never used adb fastboot, etc. commands on Wiko,... and I never unlocked the bootloader! Maybe with other phones it's mandatory, but with the Wiko Fever, you can flash directly on top with SP Flash Tool!
Click to expand...
Click to collapse
Okay i will try Sp flash tool, could you just explain better how to make the fever detect by the program? becouse i used it for older phones and i always removed they're battery, but with fever i can not do this and connecting it to the usb it will start the charging screen, i need some particular drivers?... anyway thank you a lot for your help
Melkor_98 said:
Okay i will try Sp flash tool, could you just explain better how to make the fever detect by the program? becouse i used it for older phones and i always removed they're battery, but with fever i can not do this and connecting it to the usb it will start the charging screen, i need some particular drivers?... anyway thank you a lot for your help
Click to expand...
Click to collapse
The first time you use the official Wiko Update (V34 MM or V39 LL, it doesn't matter) it installs the Wiko drivers (unsigned drivers, so if you use Win 8/8.1/10 you have to reboot in "allow unsigned drivers install mode" by using the Windows recovery menu' and by pressing F7 (If I remember)) and unpacks the original Rom, then it asks to install it: do not install it, you don't need it!
Once installed the drivers, use the SP Flash Tool (it uses the same drivers installed by the Wiko Update!) to update the required images of the Flash! The phone must be completely off, attach it to the pc after you have started the download process in SP Flash Tool and it will start by itself!
sun75 said:
The first time you use the official Wiko Update (V34 MM or V39 LL, it doesn't matter) it installs the Wiko drivers (unsigned drivers, so if you use Win 8/8.1/10 you have to reboot in "allow unsigned drivers install mode" by using the Windows recovery menu' and by pressing F7 (If I remember)) and unpacks the original Rom, then it asks to install it: do not install it, you don't need it!
Once installed the drivers, use the SP Flash Tool (it uses the same drivers installed by the Wiko Update!) to update the required images of the Flash! The phone must be completely off, attach it to the pc after you have started the download process in SP Flash Tool and it will start by itself!
Click to expand...
Click to collapse
It worked perfectly, thank you for everything
I've got huge battery drain especialy when the phone is used (I think it's correct on sleep mode) and I already set up kernel audiutor to 1040 max CPU speed...
Is it normal ?
Two others minor bugs :
Settings app crash at first boot, need to force stop it and re-launch the app to get it to work (I'm in France if it's matter).
Mobile data on LTE can't connect directly at phone boot, I have to switch to 3G then set it back to LTE and it's good.
Also, I deleted superSU from the rom to be able to install magisk 14.0 + xposed 87.3 + gravitybox 7.0.0 alpha1 and it works great but maybe it cause the battery drain ?
pakrett-bm said:
I've got huge battery drain, only 8 hours and I already set up kernel audiutor to 1040 max CPU speed...
Is it normal ?
Also Settings app crash at first boot, need to kill it and re-launch the app to get it to work.
Mobile data on LTE can't connect directly, I have to switch to 3G then set it back to LTE but this is minor.
Click to expand...
Click to collapse
Huge battery drain? Are you using this rom or the 5.8.4_r29 for Canvas?
If you're on this Rom, why you have set kernel audiutor to 1040 max cpu speed? I can achieve a normal day full battery chargeless whith no particular settings!
The Settings app never crashed at first boot to me (anyone else?), but, instead, with SuperSu installed, it asked for Root permissions!
For mobile data: I think it depends on where you live! I adapted /system/etc/firmware and /system/etc/mddb for SE (Southern Europe, Italy, etc.) Region. If you live elsewhere, you have to simply replace or adapt the contents of these two folders with the data you can copy from your Stock Rom (same paths). One more config, there is a "ro.telephony.default_network=10" in build.prop in /system that works for sure in Italy..., maybe in other countries the LTE default network is not 10 but another value...
sun75 said:
Huge battery drain? Are you using this rom or the 5.8.4_r29 for Canvas?
If you're on this Rom, why you have set kernel audiutor to 1040 max cpu speed? I can achieve a normal day full battery chargeless whith no particular settings!
The Settings app never crashed at first boot to me (anyone else?), but, instead, with SuperSu installed, it asked for Root permissions!
For mobile data: I think it depends on where you live! I adapted /system/etc/firmware and /system/etc/mddb for SE (Southern Europe, Italy, etc.) Region. If you live elsewhere, you have to simply replace or adapt the contents of these two folders with the data you can copy from your Stock Rom (same paths). One more config, there is a "ro.telephony.default_network=10" in build.prop in /system that works for sure in Italy..., maybe in other countries the LTE default network is not 10 but another value...
Click to expand...
Click to collapse
I have a Wiko Fever 4G and I use the rom you recommended : "RR-N-v5.8.3-20170527-l5460-Official" installed from stock Wiko Fever lollipop v22. (What's better ? Installing from lollipop or marshmallow, and which version ? I can't find lollipop v39 anymore)
I deleted superSU from the rom to be able to install magisk 14.0 + xposed 87.3 + gravitybox 7.0.0 alpha1 and it works great but maybe it cause the battery drain ?
Also why we need superSU ? Can't we use lineage/cm integrated root ?
Mobile data isn't a problem for me, I use a tasker task that send an intent to gravitybox at system start to switch to 3G then switch back to LTE. I'm in France and LTE default network is also 10 I think, it also work with 9 if I remember correctly.
Do you know if I can sent an intent to the system to do the same thing, I mean without needing of gravitybox ?
The Settings app doesn't crash at first boot but sometimes (often) at system start. Same thing, I use a shell command with tasker to open settings in background at system start then another command to force close it, and it works.
Another thing, why there is two camera app exactly ?
pakrett-bm said:
I have a Wiko Fever 4G and I use the rom you recommended : "RR-N-v5.8.3-20170527-l5460-Official" installed from stock Wiko Fever lollipop v22. (What's better ? Installing from lollipop or marshmallow, and which version ? I can't find lollipop v39 anymore)
I deleted superSU from the rom to be able to install magisk 14.0 + xposed 87.3 + gravitybox 7.0.0 alpha1 and it works great but maybe it cause the battery drain ?
Also why we need superSU ? Can't we use lineage/cm integrated root ?
Mobile data isn't a problem for me, I use a tasker task that send an intent to gravitybox at system start to switch to 3G then switch back to LTE. I'm in France and LTE default network is also 10 I think, it also work with 9 if I remember correctly.
Do you know if I can sent an intent to the system to do the same thing, I mean without needing of gravitybox ?
The Settings app doesn't crash at first boot but sometimes (often) at system start. Same thing, I use a shell command with tasker to open settings in background at system start then another command to force close it, and it works.
Another thing, why there is two camera app exactly ?
Click to expand...
Click to collapse
It's not a problem what version of LL or MM did you came from...: the problem, maybe is the Region you are for the Baseband. I "statically linked" the SE Baseband (in the Stock MM Rom it is chosen by reading the NVRAM for the suffix _XX and then it loads the right files from /etc/firmware and ../mddb directories). Now, with the custom ROM, all the scripts reading the NVRAM for the suffix are gone, so it loads everytime the _n modem and mddb databases, whatever they are! So I overvritten the generic _n modem and mddb databases with the _SE ones. For your region to work correctly, I suggest you to upgrade to MM Stock, go in Factory Mode Menu and select Version Info -> check your Region Zone! If it's SE, ok, otherwise you have to copy/paste the zone modem/mddb _XX files to _n overwriting it for each group!
I don't know magisk and the other software you mentioned... so I can not help you for the battery drain with them!
For SuperSu... I tried to use /xbin/su but it doesn't work for all apps... Something works, most not! So, because are years I used SuperSu for all, I installed it solving the rooting problems for all apps requesting it!
Idem with Settings: it's requesting SuperSu with Root Permissions from the first start... maybe not installing SuperSu breaked something. You can check it by logging the boot process "adb shell logcat > log.txt" and looking for the cause of the crash! I can not replicate the problem...
For LTE,... in Italy I'm attaching LTE with no problems with two distinct network operators... it switchs automatically from H+ to 4G and viceversa without any interaction from me! I suspect you are on the wrong Baseband Zone... By the way, I got the Baseband from the MM V.34 ROM (the latest!).
Two cameras? Yes... only because every app has some nice features the other app does not have! Feel free to delete the one you don't like/don't use!
Some Bugs...
Hi,
I found some bugs in this Rom and/or port on Wiko Fever. I'll describe them so you can confirm them!
- In these days I'm working in a DataCenter at floor -1. Well, there is no GSM/data available here. The problem is that when coming back on ground or upper floors, the phone correctly reattach itself to H+/LTE data connection, but it never establishes an ip connection to the Internet, with the "x" in the LTE signal fixed as no ip was negotiated. This is true until a reboot is done! Once a reboot is done, the problem is solved: data connection and ip connection to the Internet are established automatically! I think it's the MM baseband that is not fully compatible with this Nougat Rom based on LL...: I'll try to substitute the Baseband with the LL V39 one and test it!
- FM radio module: I fixed it. BUT... : it's complaining about a "Alsasound: no defined handler specified for .... " forever (draining battery) and info on radio stations and RDS is not working (but radio and audio is working ok!). I'll investigate more on this!
- AudioFX mixer: apparently working,... but ... it's making no difference on sound, no matter on settings you select on its panel! So it's useless! I'll investigate to correct it, to change it, or the like. There is something wrong on the mixer config.
- As someone suggested me, I found that flashing TWRP 2.8.x and the Rom from MM results in some screen glitches and flickering on kernel boot, on charge and on TWRP operation. These can be annoying! To solve them, flash the Fever LL V39 Stock Rom before flashing anything else. Then flash the TWRP 2.8.x, and then the Rom. Doing so, you will never experience screen glitches and flickering on boot and TWRP operation. I think the big difference from the two versions (LL and MM) is the bootloader.bin that is different from the two releases.
- I added some MTK Engineer Mode Modules... someone asked me to do so....: some modules are crashing, e.g. the audio interface test suite, maybe for the Alsasound interface.
- I updated the OpenGLES driver library with the Fever V39 one: more stability.
- I updated all the audio/mixer interface to make FM Radio module work. Maybe this breaks AudioFX, maybe not...
- I updated the installer scripts to look for /gapps/gapps.zip and for /supersu/supersu.zip, so you can download them separately (the version you want) and integrate them yourself. Zip the Rom, and flash!
- Settings -> Backup & Restore -> Factory Reset : is NOT working (if you press "restore", it does NOTHING!!). Ok ok...you can hard reset by TWRP... I Know!
I think it's all... for now!
I'll update the Rom .zip once I'll solve the major issues here explained.
I finally saw someone interested in making a rom for wiko fever and here i am. I would like to know if i can install this rom in the wiko fever 16gb/2g ram version. I noyticed by the stock systems version that this is for wiko fever with 3gb ram. Anyways thank you for your goooooooood work!!
Edit: i have an hanuna twrp already installed in my phone, will it work or i have to install the version metion in the rom description??
Hello fairly new here, I found a post relating to Android sensors breaking during the upgrade to Android 10 and I also have all of my sensors broken currently.
A post on the Pixel 3 forum has the solution: https://forum.xda-developers.com/pixel-3-xl/how-to/android-10-sensors-bug-t3964904
Does anyone have working sensors that would be willing to provide their persist.img for me to dd and fix my sensors?
If there are any other solutions I'd appreciate it!
jkent900 said:
Hello fairly new here, I found a post relating to Android sensors breaking during the upgrade to Android 10 and I also have all of my sensors broken currently.
A post on the Pixel 3 forum has the solution: https://forum.xda-developers.com/pixel-3-xl/how-to/android-10-sensors-bug-t3964904
Does anyone have working sensors that would be willing to provide their persist.img for me to dd and fix my sensors?
If there are any other solutions I'd appreciate it!
Click to expand...
Click to collapse
Are you talking about broken sensors on the 7/Pro?
TheKnux said:
Are you talking about broken sensors on the 7/Pro?
Click to expand...
Click to collapse
Correct. I was having issues with broken sensors.
I had saved my original boot/EFS/modem files in TWRP. Restoring them also restored my sensors. Caution as it also made it so my sim would not connect so I went back and did the unbrick/edl msm tool and now everything is back up and working!
if your sensors are broken after android 10 it has nothing to do with persist partition
the persist partition is never written, so if its broken its a problem with android 10 not reading persist properly.
wait for the fix instead of messing with partitions you cant restore if you break it.
jkent900 said:
Correct. I was having issues with broken sensors.
I had saved my original boot/EFS/modem files in TWRP. Restoring them also restored my sensors. Caution as it also made it so my sim would not connect so I went back and did the unbrick/edl msm tool and now everything is back up and working!
Click to expand...
Click to collapse
I had a similar problem with broken sensors when I tried updating (I rolled back to Pie for now)
That thread is in regards to TWRP saving logs to /persist causing the tiny partition to fill.
I would recommend using a terminal emulation app with the 'df' command and look for persist in the results. My persist partition is only 15% utilised and doesn't contain any twrps files or a cache folder (as the Pixel guys are seeing), so I presume that our problem is something different.
If you're adamant about trying to flash it anyway, you can find the images and commands here...but I wouldn't recommend it if you don't absolutely know what you're doing:
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
(fyi... if you use the flash-all.bat included in that thread, it will wipe your storage if you don't edit out the -w flag)
Yeah I had used that tool to rollback to pie. I think that might have been where my problems started.
Using the msm tool I believe my phone is completely back to stock and currently just have twrp/magisk and going to wait until either the official Android 10 or maybe the next beta. Dark mode is the biggest feature I'm looking forward to.
Hmm I have a bit of a similar problem but not in this scenario.
Had Oxygen OS 10, all was good.
Flashed OOS 9 (prerequisite for Havoc OS 2.9 based on Android Pie).
Then I discovered no sensor works anymore in Havoc OS (also with sensor test app).
> adb shell
> su -
> mount | grep persist --> found sda2
> df -kh ---> have just 15% used on it
I flashed a persist just out of curiosity if it brings any benefit (files are the same after).
Sensors still do not work.
Is using MSM tool the only way to bring my sensors back?
I'm a bit reluctant to have to restore all my data again and lose half a day but if it's the only way...then I will proceed.
hey guys want to write this guide to show you steps and fixes to get Android 10 working good on our dead htc u11+ (working with both QuackPhh and Havoc releases from treble project)
1. flash stock PIE rom, you can find it here: https://androidfilehost.com/?w=search&s=2Q4DIMG you must flash it from download mode by placing the .zip inside SD card after preparing it with RUU Decryption Tool.
2. install TWRP (this version: https://github.com/sabpprook/androi...es/download/0.0.1/twrp-3.3.1-0-ocm_190501.img ) with fastboot using this command: fastboot flash recovery XXX.img (where XXX.img is name of twrp image you just downloaded)
3. inside TWRP wipe data, system, dalvik cache
4. download Havoc 3.5 rom here: https://sourceforge.net/projects/ha...ficial-arm64-aonly-gapps-nosu.img.xz/download (if you want to choose another rom you can, just check is variant ARM64 A-Only) then place it on SD card and flash from TWRP (don't reboot)
5. download PhhMagisk here: https://drive.google.com/file/d/1ZgYuaN-sklg0ycDue08WtKsMFmzWsI6F/view (standard magisk won't work) then place it on SD card and flash from TWRP (don't reboot)
6. inside TWRP go to wipe -> system -> resize file system (do this 2 times as at first try you will get error)
7. reboot
8. rom is now booting and working.
FIXES:
-for better camera quality i suggest you to download this GCam version: https://f.celsoazevedo.com/file/cfiles/gcm1/GCam_7.3.018_Urnyx05-v1.7-fix.apk and then go to Phh Treble Settings -> Qualcomm features and tick Use alternate camera profile (this will make phone recording video at correct quality 1080p/4k)
-to make earpiece audio during call and bluetooth multimedia audio working you must place the 3 files included in htc_audio_bt_fix.rar i attached inside /root/vendor/etc and be sure to set permissions properly (look how permissions are set in original files before replacing, you can use Root Explorer or any other file browser with root support that allow to check and edit permissions) then you must disable from the paired bluetooth device Call Audio
now you have a working android 10 htc u11+ :victory::victory: i am using it as daily rom... you will love android 10!
only bugs i faced at the moment are:
- bluetooth audio not working with calls
- some rare freezes after unlocking phone from lockscreen
I keep getting stuck on ROM loading screen, I try reflashing the havoc os system image, then PhhMagisk, but still no luck!
I had to follow this guide all the way from the start and got the phone to boot, but once I copied the htc_audio_bt_fix.rar files to /vendor/etc/ and edited its permissions and rebooted the phone and stuck at the loading screen all over again :/
Now I have the phone running but no luck with any sound on my bluetooth earphones
I have placed the rar files as stated and the permissions are exactly as the files before had them rw--r--r, for all 3 of them.
Does the quack build support Bluetooth audio calls? I don't want to go back to pie, anyone know a working GSI Android 10 for the U11+ with BT call support?
Slok 00 said:
hey guys want to write this guide to show you steps and fixes to get Android 10 working good on our dead htc u11+ (working with both QuackPhh and Havoc releases from treble project)
1. flash stock PIE rom, you can find it here: https://androidfilehost.com/?w=search&s=2Q4DIMG you must flash it from download mode by placing the .zip inside SD card after preparing it with RUU Decryption Tool.
2. install TWRP (this version: https://github.com/sabpprook/androi...es/download/0.0.1/twrp-3.3.1-0-ocm_190501.img ) with fastboot using this command: fastboot flash recovery XXX.img (where XXX.img is name of twrp image you just downloaded)
3. inside TWRP wipe data, system, dalvik cache
4. download Havoc 3.5 rom here: https://sourceforge.net/projects/ha...ficial-arm64-aonly-gapps-nosu.img.xz/download (if you want to choose another rom you can, just check is variant ARM64 A-Only) then place it on SD card and flash from TWRP (don't reboot)
5. download PhhMagisk here: https://drive.google.com/file/d/1ZgYuaN-sklg0ycDue08WtKsMFmzWsI6F/view (standard magisk won't work) then place it on SD card and flash from TWRP (don't reboot)
6. inside TWRP go to wipe -> system -> resize file system (do this 2 times as at first try you will get error)
7. reboot
8. rom is now booting and working.
FIXES:
-for better camera quality i suggest you to download this GCam version: https://f.celsoazevedo.com/file/cfiles/gcm1/GCam_7.3.018_Urnyx05-v1.7-fix.apk and then go to Phh Treble Settings -> Qualcomm features and tick Use alternate camera profile (this will make phone recording video at correct quality 1080p/4k)
-to make earpiece audio during call and bluetooth multimedia audio working you must place the 3 files included in htc_audio_bt_fix.rar i attached inside /root/vendor/etc and be sure to set permissions properly (look how permissions are set in original files before replacing, you can use Root Explorer or any other file browser with root support that allow to check and edit permissions) then you must disable from the paired bluetooth device Call Audio
now you have a working android 10 htc u11+ :victory::victory: i am using it as daily rom... you will love android 10!
only bugs i faced at the moment are:
- bluetooth audio not working with calls
- some rare freezes after unlocking phone from lockscreen
Click to expand...
Click to collapse
So I have asked at the relevant threads regarding any word on when a bluetooth fix should be expected, but do you by any chance have any idea about that?
Because I have to decide whether to wait (if the fix maybe right around the corner or smth) or revert back to a stable pie build.
usmantahir said:
So I have asked at the relevant threads regarding any word on when a bluetooth fix should be expected, but do you by any chance have any idea about that?
Because I have to decide whether to wait (if the fix maybe right around the corner or smth) or revert back to a stable pie build.
Click to expand...
Click to collapse
unfortunately bt call audio isn't working atm only multimedia audio works... try playing with bluetooth workaround option inside treeble settings-> misc but i don't know if you will solve it
Slok 00 said:
unfortunately bt call audio isn't working atm only multimedia audio works... try playing with bluetooth workaround option inside treeble settings-> misc but i don't know if you will solve it
Click to expand...
Click to collapse
That's a bummer, I guess I'll revert to pie, i tried flashing Havoc (pie) to my phone for a change, it just wont flash. Error 255. It's been a day of disappointments :crying:
usmantahir said:
That's a bummer, I guess I'll revert to pie, i tried flashing Havoc (pie) to my phone for a change, it just wont flash. Error 255. It's been a day of disappointments :crying:
Click to expand...
Click to collapse
man i am using havoc 3.5 and i am loving it, far better than pie htc rom that is too old now
Slok 00 said:
man i am using havoc 3.5 and i am loving it, far better than pie htc rom that is too old now
Click to expand...
Click to collapse
It really is great! Too bad about the Bluetooth bug! I spend hours on-call, and I just cant go back to holding my phone to my ear :/
usmantahir said:
It really is great! Too bad about the Bluetooth bug! I spend hours on-call, and I just cant go back to holding my phone to my ear :/
Click to expand...
Click to collapse
yes i got your point, try contact phhusson (quack phh creator) is a very good guy maybe it can help you
Slok 00 said:
yes i got your point, try contact phhusson (quack phh creator) is a very good guy maybe it can help you
Click to expand...
Click to collapse
Great idea! I'll find him and hit him up. I'll post here and let you guys know if it works for me.
Hey, this is great news for me, but there's one, very important question - is there a way to use Edge Sense with this? I've seen some Magisk module re-activating the analogue feature on modded Pixels, but I haven't seen anything like that for HTC - could that work? I use Edge Sense regularly and losing it would stop me from any modding.
I downloaded the stock PIE rom from the URL provided by you, and decrypt it by RUU Decryption Tool. And now I got some img files inside two folders - firmware and system.
But then how to convert them into zip file so that I can place it inside SD card? Can you tell me in details? Sorry I'm a newbie in flashing roms.
openopentw said:
I downloaded the stock PIE rom from the URL provided by you, and decrypt it by RUU Decryption Tool. And now I got some img files inside two folders - firmware and system.
But then how to convert them into zip file so that I can place it inside SD card? Can you tell me in details? Sorry I'm a newbie in flashing roms.
Click to expand...
Click to collapse
I flashed the boot.img and system.img by fastboot into my phone instead of placing some zip into SD card, and followed the remaining steps including fixes. Now my phone is working!
However my phone can not recognize if I have plugged in the earphone or not, and of course no sound from earphone. Do you guys have any suggestions about it? Maybe I should flashed vendor.img in the first step as well?
openopentw said:
I flashed the boot.img and system.img by fastboot into my phone instead of placing some zip into SD card, and followed the remaining steps including fixes. Now my phone is working!
However my phone can not recognize if I have plugged in the earphone or not, and of course no sound from earphone. Do you guys have any suggestions about it? Maybe I should flashed vendor.img in the first step as well?
Click to expand...
Click to collapse
Flashing the vendor.img would change nothing, it is the same as it was before. The fix for earphone audio has been in the post for a long time, but there is no fix for using earphones/headphones.
Did you find the earpiece speaker fix?
---------- Post added at 03:52 PM ---------- Previous post was at 03:46 PM ----------
This is incredible, I've been following phhuson's Treble GSI development for 2 years now hoping that someone would find a fix for the earpiece speaker during calls.
I tried doing everything at once and got a bootloop, but then I tried every step separately and after a few days my U11+ is working great!
How long did it take you to find that GCam port? I've been using Arnova's for ages and could never find a good one for the U11+ before trying the one you've linked.
I'm really glad we got the earpiece fix, the U11+ still has really great hardware and the poorly made Android Pie port and old security patch was tempting me to upgrade to something new. Now I think I can hold onto it for an extra year.
My camera doesn't work...
After enable "Use alternate camera profile" then reboot , it still not working....
Is there any solution?
Please help me , camera is really important to me...
Pineapplemilk said:
My camera doesn't work...
After enable "Use alternate camera profile" then reboot , it still not working....
Is there any solution?
Please help me , camera is really important to me...
Click to expand...
Click to collapse
What's your vendor version?
I use Android Pie vendor with Havoc OS 3.7 work fine.
Maybe you should flash Pie RUU first then install the Havoc OS.
---------- Post added at 10:51 PM ---------- Previous post was at 10:41 PM ----------
Here is the way to use Edge Sense with Havoc OS.
1. Install com.htc.sense.edgesensorservice.apk (Resigned with Havoc OS keystore)
2. Install App Systemizer in Magisk
3. Systemize EdgeSensorService
4. Reboot
Now Edge Sense work fine.
And if you want to setup Edge Sense, open terminal
Code:
su
am start com.htc.sense.edgesensorservice/.ui.SettingsMainActivity
Recommended to use Edge Sense Plus to manage it so you don't need to setup in this dirty(?) way every time.
james35022000 said:
What's your vendor version?
I use Android Pie vendor with Havoc OS 3.7 work fine.
Maybe you should flash Pie RUU first then install the Havoc OS.
Click to expand...
Click to collapse
I flashed 2.15.709.1 Pie Ruu before install the "Phh AOSP Android 10"
(Havoc based on Phh)
TWRP Version : 190501
And it still can't encrypt data
Pineapplemilk said:
I flashed 2.15.709.1 Pie Ruu before install the "Phh AOSP Android 10"
(Havoc based on Phh)
TWRP Version : 190501
And it still can't encrypt data
Click to expand...
Click to collapse
Oh TWRP can't decrypt data is normal.
The thing you can do is to prevent system from encrypting data.
This thread:
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Just wipe data in TWRP and flash the zip file upon
---------------------------------------------------------------------
And wait, I see XDDD
I flashed Phh AOSP before, the camera don't work neither.
You can find the issue on the Phh's github, it seems never work and no fix for our device.
So....please use Havoc OS
james35022000 said:
Oh TWRP can't decrypt data is normal.
The thing you can do is to prevent system from encrypting data.
This thread:
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Just wipe data in TWRP and flash the zip file upon
Click to expand...
Click to collapse
Thank you for this information :good:
---------------------------------------------------------------------
james35022000 said:
And wait, I see XDDD
I flashed Phh AOSP before, the camera don't work neither.
You can find the issue on the Phh's github, it seems never work and no fix for our device.
So....please use Havoc OS
Click to expand...
Click to collapse
Really strange.....
Thank you for the information again~
Does Havoc os running smooth on U11+?
Phh AOSP has some bugs but it's smooth tho.
Pineapplemilk said:
Does Havoc os running smooth on U11+?
Phh AOSP has some bugs but it's smooth tho.
Click to expand...
Click to collapse
It runs smooth for me, but for the first week I kept crashing at the lock screen randomly and had to do a reset. Sometimes a normal reset would just bootloop or crash on the lockscreen again. So I had to specifically go into download mode -> bootloader mode -> recovery mode (TWRP) -> "reboot to system" which would let me get past the lockscreen without crashing.
The battery life and thermal performance is MUCH better, it's too early for me to say but I think it's pretty close to Oreo battery life and heat management might be EVEN BETTER.
I still think that HTC Oreo was smoother, but most phones weren't as smooth as the U11+ on Oreo.
The camera performance is definitely worse though, that could just be because we're forced to use the GCam port instead of the stock HTC app but it's inconsistent with lighting and sometimes crushes black levels on people's faces too much. If I find improved settings or a better GCam port then I'll link it here for you guys to use
I'm pretty sure that TWRP not being able to decrypt data is a bug with that specific version of TWRP, but I don't think there's another TWRP image that will work on the U11+ so we have to deal with it.
---------- Post added at 07:24 PM ---------- Previous post was at 07:12 PM ----------
james35022000 said:
What's your vendor version?
I use Android Pie vendor with Havoc OS 3.7 work fine.
Maybe you should flash Pie RUU first then install the Havoc OS.
---------- Post added at 10:51 PM ---------- Previous post was at 10:41 PM ----------
Here is the way to use Edge Sense with Havoc OS.
1. Install com.htc.sense.edgesensorservice.apk (Resigned with Havoc OS keystore)
2. Install App Systemizer in Magisk
3. Systemize EdgeSensorService
4. Reboot
Now Edge Sense work fine.
And if you want to setup Edge Sense, open terminal
Code:
su
am start com.htc.sense.edgesensorservice/.ui.SettingsMainActivity
Recommended to use Edge Sense Plus to manage it so you don't need to setup in this dirty(?) way every time.
Click to expand...
Click to collapse
How do you do step 1? I couldn't find any information about where to find the HavocOS Keystore or what it is? I assume it's an app to resign APKs for HavocOS?
Thanks for helping an ignorant person like me
I have installed Caos 11 on my Blackview BV9900Pro. The strange thing is I have to use the a/b version to make it work while it's an a-only device. I got Magisk and exposed to work.
To get the Flir camera to work I installed the MyFlir APK from the original Android 10 ROM from Blackview and I created a Magisk module that 'installs' the libraries and leptonserver bin file. It also starts the leptonserver at boot.
To get the heart rate sensor working I did the same but then for healthcare.
When I have time I will create a manual on how to install Caos 11 on the Blackview 9900(Pro). The only things I noticed up to now is that Volte doesn't work, the Flir camera doesn't work and the heart rate sensor doesn't work. O yeah, after first boot I had to factory reset to make it see/use all storage. Without factory reset Android storage shows just 2GB while it has 128GB.
Attached you find the Magisk Modules and the APK's. Let me know if it works for you on any custom ROM.
Edit 10-09-21:
I changed the MyFlir module. Now it wil also install the MyFlir app. No manual installation of the app anymore. I will do the same for HealthCare later.
edit 11-09-21:
Did the same with HealthCare. No manual installation of the app anymore.
[email protected] said:
I have installed Caos 11 on my Blackview BV9900Pro. The strange thing is I have to use the a/b version to make it work while it's an a-only device. I got Magisk and exposed to work.
To get the Flir camera to work I installed the MyFlir APK from the original Android 10 ROM from Blackview and I created a Magisk module that 'installs' the libraries and leptonserver bin file. It also starts the leptonserver at boot.
To get the heart rate sensor working I did the same but then for healthcare.
When I have time I will create a manual on how to install Caos 11 on the Blackview 9900(Pro). The only things I noticed up to now is that Volte doesn't work, the Flir camera doesn't work and the heart rate sensor doesn't work. O yeah, after first boot I had to factory reset to make it see/use all storage. Without factory reset Android storage shows just 2GB while it has 128GB.
Attached you find the Magisk Modules and the APK's. Let me know if it works for you on any custom ROM.
Edit 10-09-21:
I changed the MyFlir module. Now it wil also install the MyFlir app. No manual installation of the app anymore. I will do the same for HealthCare later.
edit 11-09-21:
Did the same with HealthCare. No manual installation of the app anymore.
Click to expand...
Click to collapse
Thanks for this! MyFlir works now on my BV9900pro with LineageOS 18 GSI. Only issue: App is closing just after pressing the shoot button. No images stored in the gallery. Happy anyway as I can now use at least the Flir thermal camera with my custom rom!
backtoroot said:
Thanks for this! MyFlir works now on my BV9900pro with LineageOS 18 GSI. Only issue: App is closing just after pressing the shoot button. No images stored in the gallery. Happy anyway as I can now use at least the Flir thermal camera with my custom rom!
Click to expand...
Click to collapse
Healthcare App works, too - without any issue. Thanks again! If I ever get TWRP installed on this device but that's another story...
backtoroot said:
Thanks for this! MyFlir works now on my BV9900pro with LineageOS 18 GSI. Only issue: App is closing just after pressing the shoot button. No images stored in the gallery. Happy anyway as I can now use at least the Flir thermal camera with my custom rom!
Click to expand...
Click to collapse
Thank @backroot,
backtoroot said:
Thanks for this! MyFlir works now on my BV9900pro with LineageOS 18 GSI. Only issue: App is closing just after pressing the shoot button. No images stored in the gallery. Happy anyway as I can now use at least the Flir thermal camera with my custom rom!
Click to expand...
Click to collapse
Great it works for you 2. Concerning saving I noticed I had the same issue. I almost never take pictures myself is why I haven't noticed myself. I got this resolved by installing myflir.apk again, without removing myflir app, from the following location:
/system/app/myflir
or
/system/priv-app/myflir
Hope this works 4u2.
Yeaahhhh! To re-install the APP over the old one did the trick! No issue with the save function anymore! Thanks again for your help!
Last issue I discovered with myFlir:
the calibration tool (the last point at settings - not the one on top with the flower/MSX) to adjust the real and thermal camera to be on same focus doesn't work at all. Nothing happens if I try to choose that function. As it's called something like "Picture Adjusting-Tool" it sounds too me like a separate APP or so which is probably missing in my installation.
I can't really tell if it ever worked as this was never an issue with the stock rom but since it works with my custom rom the position of the two pictures is quite different which makes the overlay of the thermal image a bit useless.
Any advice on this?
backtoroot said:
Yeaahhhh! To re-install the APP over the old one did the trick! No issue with the save function anymore! Thanks again for your help!
Last issue I discovered with myFlir:
the calibration tool (the last point at settings - not the one on top with the flower/MSX) to adjust the real and thermal camera to be on same focus doesn't work at all. Nothing happens if I try to choose that function. As it's called something like "Picture Adjusting-Tool" it sounds too me like a separate APP or so which is probably missing in my installation.
I can't really tell if it ever worked as this was never an issue with the stock rom but since it works with my custom rom the position of the two pictures is quite different which makes the overlay of the thermal image a bit useless.
Any advice on this?
Click to expand...
Click to collapse
I've noticed that too and have been searching how to resolve this but haven't been able to find a solution. I know it works on the original rom from Blackview.
How to install twrp?
1x23 said:
How to install twrp?
Click to expand...
Click to collapse
i got TWRP to install by treating the phone as if it had ramdisk.
fastboot devices
fastboot flash boot boot.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash recovery recovery.img
fastboot reboot recovery
TWRP is installed, but read-only. And I couldn't connect an sd card. Thank you for your help.
1x23 said:
TWRP is installed, but read-only. And I couldn't connect an sd card. Thank you for your help.
Click to expand...
Click to collapse
Hey, I'm running an eBay business, had a request to work on the BV9900Pro. I have ported a twrp build from the BV9900, but cannot test because I am not currently in possession of the device. Could you maybe test it for me?
1x23 said:
TWRP is installed, but read-only. And I couldn't connect an sd card. Thank you for your help.
Click to expand...
Click to collapse
If you are trying to flash a GSI, you don't need it. You can do fastboot flash system GSI.img in the bootloader and it will flash. I have booted CAOS and LineageOS. Make sure you download the ab versions because the a only versions do not work for some reason. You could possibly do adb sideload in twrp afterwards for root.
[email protected] said:
I have installed Caos 11 on my Blackview BV9900Pro. The strange thing is I have to use the a/b version to make it work while it's an a-only device. I got Magisk and exposed to work.
To get the Flir camera to work I installed the MyFlir APK from the original Android 10 ROM from Blackview and I created a Magisk module that 'installs' the libraries and leptonserver bin file. It also starts the leptonserver at boot.
To get the heart rate sensor working I did the same but then for healthcare.
When I have time I will create a manual on how to install Caos 11 on the Blackview 9900(Pro). The only things I noticed up to now is that Volte doesn't work, the Flir camera doesn't work and the heart rate sensor doesn't work. O yeah, after first boot I had to factory reset to make it see/use all storage. Without factory reset Android storage shows just 2GB while it has 128GB.
Attached you find the Magisk Modules and the APK's. Let me know if it works for you on any custom ROM.
Edit 10-09-21:
I changed the MyFlir module. Now it wil also install the MyFlir app. No manual installation of the app anymore. I will do the same for HealthCare later.
edit 11-09-21:
Did the same with HealthCare. No manual installation of the app anymore.
Click to expand...
Click to collapse
Good afternoon and what a good afternoon that is.
I have accidentality formatted and downloaded stock ROM by SF Format tool on my BV9800pro phone. I was looking for ways to fix it, even instaled a custom rom.
I'm quoting this user because his file saved me. "MM-Myflir.zip" - so to anyone please make a copy and don't let it get lost.
Now I have again a working phone with thermal cam, that isn't crushing when taking a picture or anything.
Did any of You did it on a stock ROM after crushing it? I don't have much time to explain how I did it (and it took many approaches to do so). So I'll write what I did. I don't know it was the right way to approach it but it works and it's all that matters.
Thanks again
I'm a bit sad. That TWRP on my BV9800pro works only before booting for the first time to the system. I can't decrypt it even if I know the pin that I used.
So I made the stupid mistake of formatting and flashing stock ROM on my phone. Who knew, before having this problem that it will mess up my thermal camera.
Anyway what I did was, unlocking bootloader. Installed TWRP.IMG.
Before first boot to system I went to recovery mode. On my SD card I had my copy of MM-Myflir.zip, and it was decompressed to a folder in Windows.
All I did was transfer files from "lib64", "bin" and "app" folders to those on /system/app/Myflir /system/bin and /system/lib64.
I did not coppy those .sh files.
Now I didn't change any chmod on files, I also didn't use any "getenforce" on those files to make them enforced or permissive.
So here what happened. I didn't check if those files got replaced or not, but the one thing I wanted to replace was the Myflir.apk. I have forgotten to name it properly so it was like in the zip folder Myflir.apk and not Myflir-2.3.8.... (can't remember it whole, because I'm writing this on a bus).
After reboot there was no Myflir apk. That was the moment I understood my mistake. Installed es manager. Went to /system/app/bin directory and installed the app (no root). The app came up on desktop of phone, now it can be uninstalled. But the most important thing is that it WORKS!!!
I wonder if the only step that I could have made was add an app in the same location and to the above, or copying those files was necessary.
Maybe I'll check it out. But I think I'll leve it like this since all works.
Please report on your successes. I would like to know what it took for You.
I did test the phone. On newest stock rom. All above for me is not needed. I don't need to copy all those files. Only thing to copy is the Myflir.app.
But my phone is not formatted again. I lef the recovery partition for TWRP.
Again after booting first time and going trough all those windows. I didn't have my stock Myflir apk installed. So I installed after going to /system/app/Myflir-bv2.3.8...
That did the trick.
I won't go trough format restoring the Tee and google services by sw write tool again just to check if we all could do what I wrote in all my posts....
I hope it is a solution for all people that would like to stay by the stock rom.