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.
HOW TO PERMANENTLY FIX THE Wi-Fi PROBLEM OF YOUR SAMSUNG DEVICE- DESCRIPTION -This is a GUIDE on how to repair the Wi-Fi problem characterized by not having the ability to TURN ON the Wi-Fi after flashing:
1. A new firmware;
2. A new custom rom;
3. Anything else that may interfere with the /system folder of your device.- WARNING -This tutorial is based on the I9505 phone, but if you have this problem on another Samsung device you just need to find the specified BOOTLOADER and MODEM related to YOUR MODEL.- YOUTUBE VIDEO - To understand the whole process completely I have made an YouTube video, because I think it's a better way of understanding what you should or shoudn't do. Video is recorded at 1080p @60fps so it will take longer to process on YouTube, be patient, it will be worth waiting.
- EXPLANATIONS -THERE ARE 3 THINGS OVERALL THAT YOU SHOULD DO IN ORDER TO FIX THE PROBLEM:
1 - UPDATE THE BOOTLOADER - YOU CAN ONLY FLASH A BOOTLOADER THAT IS ONLY BUILT FOR YOUR DEVICE = S4 USES A BOOTLOADER, S5 ANOTHER BOOTLOADER AND SO ON;
2 - UPDATING THE MODEM - YOU CAN ONLY FLASH A MODEM THAT IS ONLY BUILT FOR YOUR DEVICE = S4 USES A MODEM, S5 ANOTHER MODEM AND SO ON;
3 - ONLY FOR ROOTED I9505 - YOU CAN ONLY FLASH THIS FILE ONLY IF YOU ARE RUNNING 4.4.2 OFFICIAL TW ON I9505. NO OTHER EXCEPTIONS.
Neccesary step - You need to edit the build.prop file of your phone with an app like Root Explorer, situated in /system folder and find the line containing ro.securestorage.support=true and change it to false then save the file.
- DOWNLOADS - WARNING! - I9505 FILES ONLY -DROPBOX FOLDER WITH ALL THE FILES YOU WILL NEED
Let me be the first so anyone spam the thread again and again, will this work on chinesse leak lollipop? Although i know(READ) that it wont work B)
Guihardrock said:
Let me be the first so anyone spam the thread again and again, will this work on chinesse leak lollipop? Although i know(READ) that it wont work B)
Click to expand...
Click to collapse
No, it won't work on Chinese lollipop.
Hello
Seeing there is very little info about this model, I decided to make available my findings. Initially I was a bit annoyed with the phone in the start. The "stock" rom was a disaster (malware-ridden, non-official). First I tried to de-bloat that but the whole rom was just bad and unstable. Since then I've learned some things, and newer official builds have surfaced.
Also I should say; this phone is basically a K3 Note with 720p screen (another difference is MT6752M cpu instead of MT6752 in the K3 Note) and it's very similar to the A7000 model.
The best rom I have tried so far is this : VIBEUI_V2.5_1532_5.1797.1_ST_A7600_CU ---> DL - This is latest official stock Rom for the 7600 (not 7600M which is Chinese version)
Here is also TWRP recovery with english + chinese language: DL
Rename ROM to "update.zip", use stock recovery and flash (probably best to use stock lenovo recovery first to make sure everything gets flashed, can be flashed with twrp but I suspect it only flashes boot and system), boot it up, finish the setup wizard, turn it off. Use SPflashtool to flash TWRP, turn off again.
Start phone in recovery mode (Press volume Up + Down, and power button. Hold until recovery appears). Now you can flash Gapps (arm64, lollipop 5.0, opengapps.org), SuperSU, xposed arm64 lollipop, etc.
I have been able to get a very pleasing phone doing this. I don't really feel right now that much is missing, and I'm not annoyed by various other problems. Using xposed modules gravity box, GEL settings, Lollipop memory fix, etc.
This Rom has very little bloatware, there are some chinese apps, but they can easily be uninstalled - don't even need root. There are a few more you can uninstall using root if you want, but be careful not to break the system.
I'm not going to explain everything in great detail here. Using SPFlashTool is explained so many other places. Getting supersu and xposed also explained everywhere.
If I could I would integrate all in to one flashable package, but I'm not a rom cooker. Sorry
PS: As you can see in the image, i use iFONT xposed. But I don't enable it as xposed module, that caused problems. I just used it to download a font and applied it. It's system wide, and it works
There's a newer link in post #6 with the latest firmware
There's a newer link in post #10 with TWRP 3.0.2.3
Hi,do you have custom rom for lenovo s8 a7600?
askermk2000 said:
Hello
The best rom I have tried so far is this : VIBEUI_V2.5_1532_5.1797.1_ST_A7600_CU ---> - This is latest official stock Rom for the 7600 (not 7600M which is Chinese version)
Here is also TWRP recovery with english + chinese language:
Click to expand...
Click to collapse
sorry, I had to remove your links, because I have small amount of posts and I am not allowed to submit post with urls - even if quoted.
Hi!
Do you know way to install other languages into ROM (or add them and somehow rebuild ROM), I am searching informations for last few days with no succes. The main problem is when international apps using EN for directory, when all information in directory should be in my language (polish). Changing locale helps, but settings are crashing with changed locales..
Also I installed xposed, but system tells me that xposed is not installed... I heard about it from your post and found only version v79 for sdk 21. I need to remove search box from desktop at google now.
Any custom rom for this device ?
Hi everyone, hi @askermk2000
I just received my Lenovo S8 A7600 "Golden Warrior" phone from an Asian vendor, it came with VIBEUI_V2.5_1524_5.1460.1_ST_A7600_CU and SuperSU was seemingly installed when I first turned on phone (asked me to update binary).
Specs are MTK6752M 64-bit OctaCore, 2GB RAM, 8GB storage.
Can I install your version VIBEUI_V2.5_1532_5.1797.1_ST_A7600_CU through the Lenovo stock recovery/flash (phone) as you suggest?
You mention "not 7600M" so I am not sure...
I also see in other places that there's even a newer VibeUI version VIBEUI_V2.5_1537_5.1978.1_ST_A7600_CU, any idea where to get it and if it is compatible? I cannot find any download link...
Thanks...
konsti said:
Hi everyone, hi @askermk2000
I just received my Lenovo S8 A7600 "Golden Warrior" phone from an Asian vendor, it came with VIBEUI_V2.5_1524_5.1460.1_ST_A7600_CU and SuperSU was seemingly installed when I first turned on phone (asked me to update binary).
Specs are MTK6752M 64-bit OctaCore, 2GB RAM, 8GB storage.
Can I install your version VIBEUI_V2.5_1532_5.1797.1_ST_A7600_CU through the Lenovo stock recovery/flash (phone) as you suggest?
You mention "not 7600M" so I am not sure...
I also see in other places that there's even a newer VibeUI version VIBEUI_V2.5_1537_5.1978.1_ST_A7600_CU, any idea where to get it and if it is compatible? I cannot find any download link...
Thanks...
Click to expand...
Click to collapse
Hello
It's wise of you to remove that dubious vendor firmware.
Since "A7600M" is a model number, or simply name of the phone, I would be surprised if it doesn't say so anywhere. Look at the packaging, phone and battery compartment etc. If you don't see A7600M anywhere, it's likely not that model.
See here: Lenovo Inquiry Page
At the bottom there you'll find link for the latest official (Full) firmware.
Thank you @askermk2000 for your kind and immediate reply.
This known asian vendor on their page mentions: Lenovo "Golden Warrior" S8 A7600, 4G, LTE, MTK6752M @1.5GHz 64bit OctaCore, 2GB RAM, 8GB storage, 5.5inch HD IPS screen, OTG, Android 5.0 Phone
In settings, the ROM version is: VIBEUI_V2.5_1524_5.1460.1_ST_A7600_CU, no bloatware; was surprised to see SuperSU pre-installed but the vendor does have a service (at a cost) to provide pre-rooted phones (which I did NOT order but maybe got).
The (Lenovo) box doesn't mention much, even under the phone I can see a lot of Chinese, so it's definitely for China -- vendor wrote it's unlocked for world use on their page.
The mentioned model is A7600 on the rear, there's only a A838 reference besides model (i.e. QQ-A838-xxxxxx) but not much more than that.
I suspect these may be older stock they wanted to get rid of.
As you can see, the model is (S8) A7600, not A7600M. The chipset has "M" i.e. is MTK6752M.
So can I not use the official latest (full) firmware that you posted, via stock recovery?
Is this not for MTK6752M processor? Will this firmware brick the phone, you think?
Thank you very much in advance!
konsti said:
Thank you @askermk2000 for your kind and immediate reply.
This known asian vendor on their page mentions: Lenovo "Golden Warrior" S8 A7600, 4G, LTE, MTK6752M @1.5GHz 64bit OctaCore, 2GB RAM, 8GB storage, 5.5inch HD IPS screen, OTG, Android 5.0 Phone
In settings, the ROM version is: VIBEUI_V2.5_1524_5.1460.1_ST_A7600_CU, no bloatware; was surprised to see SuperSU pre-installed but the vendor does have a service (at a cost) to provide pre-rooted phones (which I did NOT order but maybe got).
The (Lenovo) box doesn't mention much, even under the phone I can see a lot of Chinese, so it's definitely for China -- vendor wrote it's unlocked for world use on their page.
The mentioned model is A7600 on the rear, there's only a A838 reference besides model (i.e. QQ-A838-xxxxxx) but not much more than that.
I suspect these may be older stock they wanted to get rid of.
As you can see, the model is (S8) A7600, not A7600M. The chipset has "M" i.e. is MTK6752M.
So can I not use the official latest (full) firmware that you posted, via stock recovery?
Is this not for MTK6752M processor? Will this firmware brick the phone, you think?
Thank you very much in advance!
Click to expand...
Click to collapse
No, your phone is the right model, as you said "Unlocked for world use", the A7600M only works in china.
MTK6752M is the chipset used - it has nothing to do with A7600M, that there are two M's there is a coincidence.
So you can go ahead and use the latest firmware.
OK for the sake of information to everyone, I did the following:
0. Formatted SD card from within the phone (just to be sure). Then charged battery fully to 100%.
1. Copy (via PC) the latest firmware zip file (currently is VIBEUI_V2.5_1628_5.2186.1_ST_A7600_CU_WC5DAF1811.zip about 1GB size) to root of my SD card. This file looks like a recovery type, but files inside (some IMG, DAT and scatter files) could be flashable from PC (i.e. like SP Flash Tool etc.).
2. Renamed it update.zip
3. Put SD and battery back to phone.
4. Started phone in recovery mode: Pressed Volume Up + Down and Power buttons simultaneously; held them until recovery screen appeared. First, Lenovo logo, then a screen to choose language (Chinese/English); pressed English.
5. Selected the Install Upgrade Pack menu and pressed "YES" to the warning about encrypted phones.
6. Waited for update with circle-type update progress; for some reason it got seemingly stuck at 75% for some period. Waited patiently to finish.
7. I selected "Back" to go and clean user data.
8. Once done, I pressed back touch-button and selected "Restart".
9. Waited to see what happens. Was curiously greeted with a white chinese splash-screen saying "4G" something. Waited...
10. Phone next booted to the usual Lenovo logo, with some chinese text at the bottom and three dots [...] flashing with thin white progress-line (most likely "rebuilding apps"?). This took a while, too.
11. The phone finally went into the wizard in Chinese, and then offered choice of English or Chinese as wizard language.
Wizard finished OK, then went to Settings -> About device -> ROM is upgraded indeed to VibeUI v2.5-1628 and Android 5.0.2.
NOTE: There's a LOT of chinese stuff, unfortunately, I guess it's part of the ROM; obviously this ROM is non-rooted...
However, the asian vendor installed/shipped ROM (VIBEUI_V2.5_1524_5.1460.1_ST_A7600_CU) was very light and fast -- I guess a deodex version? Or a VibeUI port?
Many thanks @askermk2000 for your help nevertheless.
Any idea, compared to your experience., if...
a) if your URL for latest firmware is maybe only for China? Your first post photos/screenshots don't have such Chinese apps On this ROM version, the shutdown logo is again that white chinese splash-screen with a big red "4G". Perhaps there's some other version for non-Chinese region?
b) if there's a stock, deodex ROM like that one? How did the Asian vendor find such light ROM, I am curious -- in that shipped ROM version, I had many menu languages. Now I only have English and Chinese as choices
c) if I need TWRP so I can flash Play Store, gapps and SuperSU? I don't think stock Recovery allows for these, any idea?
Cheers mate.
konsti said:
OK for the sake of information to everyone, I did the following:
0. Formatted SD card from within the phone (just to be sure). Then charged battery fully to 100%.
1. Copy (via PC) the latest firmware zip file (currently is VIBEUI_V2.5_1628_5.2186.1_ST_A7600_CU_WC5DAF1811.zip about 1GB size) to root of my SD card. This file looks like a recovery type, but files inside (some IMG, DAT and scatter files) could be flashable from PC (i.e. like SP Flash Tool etc.).
2. Renamed it update.zip
3. Put SD and battery back to phone.
4. Started phone in recovery mode: Pressed Volume Up + Down and Power buttons simultaneously; held them until recovery screen appeared. First, Lenovo logo, then a screen to choose language (Chinese/English); pressed English.
5. Selected the Install Upgrade Pack menu and pressed "YES" to the warning about encrypted phones.
6. Waited for update with circle-type update progress; for some reason it got seemingly stuck at 75% for some period. Waited patiently to finish.
7. I selected "Back" to go and clean user data.
8. Once done, I pressed back touch-button and selected "Restart".
9. Waited to see what happens. Was curiously greeted with a white chinese splash-screen saying "4G" something. Waited...
10. Phone next booted to the usual Lenovo logo, with some chinese text at the bottom and three dots [...] flashing with thin white progress-line (most likely "rebuilding apps"?). This took a while, too.
11. The phone finally went into the wizard in Chinese, and then offered choice of English or Chinese as wizard language.
Wizard finishedOK, then went to Settings -> About device -> ROM is upgraded indeed to VibeUI v2.5-1628 and Android 5.0.2.
There's a LOT of chinese stuff, unfortunately, I guess it's part of the ROM; obviously this ROM is non-rooted.
But the installed/shipped ROM (VIBEUI_V2.5_1524_5.1460.1_ST_A7600_CU) was very light and fast -- I guess a deodex version? Or a VibeUI port?
Many thanks @askermk2000 for your help nevertheless. Your photos/screenshots however don't have such Chinese apps...
Any idea, compared to your experience., if...
a) if your linked latest firmware is maybe only for China? The shutdown logo is again that white chinese splash-screen with a big red "4G". Perhaps there's some other version for non-Chinese region?
b) if there's a stock, deodex ROM like that one? How did the Asian vendor find such light ROM, I am curious -- in that shipped ROM version, I had many menu languages. Now I only have English and Chinese as choices
c) if I need TWRP so I can flash Play Store, gapps and SuperSU? I don't think stock Recovery allows for these, any idea?
Cheers mate.
Click to expand...
Click to collapse
Hello again
Yes, the official Chinese rom only has Eng/Chinese language. There may be a way to add more, idk because I only need English. The 4G boot logo is normal, was there on the rom linked in the first post also.
All the Chinese apps (or almost all) can be uninstalled without root permission. I never experience the rom to be less than fast and good, but I always immediately uninstalled the chinese apps, they do me no good anyways.
The rom you where supplied with is what is called ROW (international). If it's possible to get an updated ROW rom idk. All I know is that if you want a clean unhampered ROM, then the one I've shown you is the way to go.
PS: Yes you need custom recovery to flash the other stuff. Here is an updated TWRP: TWRP-3.0.2.3
^^This recovery has wrong device description in build.prop (actually it uses Lenovo K3) as a consequence you will receive error if trying to flash ROM's. So try the old one if you get these errors.
HI everyone, hi @askermk2000 and many many thanks for sharing your TWRP version 3.0.2.3 with us.
I followed this thread on how to root the Lenovo S8 A7600 phone and downloaded the tools needed (SP Flash Tool v5.1452.00 and VCOM drivers) on my Windows 7 laptop; then, installed them accordingly. Many thanks to @XxpikaachuuxX for providing links and steps on his thread!
1. Started up SP Flash Tool with administrator rights.
2. Chose the scatter file that was inside your shared TWRP-3.0.2.3 zip file; recovery image is automatically selected.
3. Shut down phone, remove battery.
4. Made sure all boxes in list were unchecked, except "recovery" then pressed "Download" button.
5 . Plugged phone on USB cable to PC, then inserted battery under the phone, as instructed.
6. Windows made a "USB plugged" sound, then SP Flash Tool detected phone OK and flashed recovery fine (there was the green tick-mark shown!)
7. Removed cable, removed battery, waited 10 seconds, re-inserted battery.
Then, copied to my SD card root folder, via PC (card reader) the following:
a) UPDATE-SuperSU-v2.46.zip
b) gapps-lp-20150211-signed.zip from this thread (lp=Lollipop)
(I had downloaded and installed wrong Gapps for 5.1 Android, but we need 5.0 version for this ROM--silly me. I just re-flashed via TWRP the correct package).
Went into recovery by pressing briefly Power then when the short vibration was felt, pressed VOL+ and VOL- and POWER simultaneously; the pleasant splash-screen of TWRP was shown!
1. Installed the needed SuperSU; then went back.
2. Installed gapps.
3. Wiped cache and Davlik (inside TWRP) then rebooted phone i.e. "system".
4. Waited patiently as it took a few minutes to go on the main Home screen.
5. Created Google account in "Settings" then went straight to "PlayStore" to update all applications, including SuperSU.
6. Ran SuperSU and upon request, updated the binary "normally" and rebooted just fine.
NOTE: In the Wi-Fi detected lists, since my first ever boot of this phone, I get a (fake?) SSID entry "NVRAM WARNING: Err = 0x10" which is apparently easily fixed for other phones. Do you guys you also got that?
A bunch of final questions to you, @askermk2000 when you have time to reply.
1) Does the stock weather display on a Home page work for you? I only get Chinese cities, location doesn't work as it says "city not found". Manual input of e.g. Europe cities doesn't show results, either.
2) Despite removing most via "Settings -> App Manager", any suggestions oh how to remove some further chinese apps that are marked "system app"? This article suggests NoBloat Free, Titanium Backup, System App Remover and App Master. I am not familiar with this approach but for example, "LenovoStore" could be removed...
3) Do you have by any chance the original, black b/g, folding (yes, boring) Lenovo animation boot logo to share? I see there's a file logo.bin for SP Flash Tools but others talk about /system/media/bootanimation.zip file... I ask if you have it, as the "Boot Animations" PlayStore app may not have the stock Lenovo boot. Perhaps flashing it via SP Flash Tool is better?
4) Will you kindly share any updates here to TWRP versions, whenever released? Do you anticipate any update in the coming 1-2 months, for example? (not sure there are bugs in TWRP-3.0.2.3, if any)
5) If there is a newer Lenovo official ROM available (than today) we obviously lose the TWRP recovery if we flash it all via SP Flash Tools; but we keep TWRP recovery if we update to the new ROM via TWRP, correct?
Thank you.
konsti said:
HI everyone, hi @askermk2000 and many many thanks for sharing your TWRP version 3.0.2.3 with us.
I followed this thread on how to root the Lenovo S8 A7600 phone and downloaded the tools needed (SP Flash Tool v5.1452.00 and VCOM drivers) on my Windows 7 laptop; then, installed them accordingly. Many thanks to @XxpikaachuuxX for providing links and steps on his thread!
1. Started up SP Flash Tool with administrator rights.
2. Chose the scatter file that was inside your shared TWRP-3.0.2.3 zip file; recovery image is automatically selected.
3. Shut down phone, remove battery.
4. Made sure all boxes in list were unchecked, except "recovery" then pressed "Download" button.
5 . Plugged phone on USB cable to PC, then inserted battery under the phone, as instructed.
6. Windows made a "USB plugged" sound, then SP Flash Tool detected phone OK and flashed recovery fine (there was the green tick-mark shown!)
7. Removed cable, removed battery, waited 10 seconds, re-inserted battery.
Then, copied to my SD card root folder, via PC (card reader) the following:
a) UPDATE-SuperSU-v2.46.zip
b) gapps-lp-20150211-signed.zip from this thread (lp=Lollipop)
(I had downloaded and installed wrong Gapps for 5.1 Android, but we need 5.0 version for this ROM--silly me. I just re-flashed via TWRP the correct package).
Went into recovery by pressing briefly Power then when the short vibration was felt, pressed VOL+ and VOL- and POWER simultaneously; the pleasant splash-screen of TWRP was shown!
1. Installed the needed SuperSU; then went back.
2. Installed gapps.
3. Wiped cache and Davlik (inside TWRP) then rebooted phone i.e. "system".
4. Waited patiently as it took a few minutes to go on the main Home screen.
5. Created Google account in "Settings" then went straight to "PlayStore" to update all applications, including SuperSU.
6. Ran SuperSU and upon request, updated the binary "normally" and rebooted just fine.
NOTE: In the Wi-Fi detected lists, since my first ever boot of this phone, I get a (fake?) SSID entry "NVRAM WARNING: Err = 0x10" which is apparently easily fixed for other phones. Do you guys you also got that?
A bunch of final questions to you, @askermk2000 when you have time to reply.
1) Does the stock weather display on a Home page work for you? I only get Chinese cities, location doesn't work as it says "city not found". Manual input of e.g. Europe cities doesn't show results, either.
2) Despite removing most via "Settings -> App Manager", any suggestions oh how to remove some further chinese apps that are marked "system app"? This article suggests NoBloat Free, Titanium Backup, System App Remover and App Master. I am not familiar with this approach but for example, "LenovoStore" could be removed...
3) Do you have by any chance the original, black b/g, folding (yes, boring) Lenovo animation boot logo to share? I see there's a file logo.bin for SP Flash Tools but others talk about /system/media/bootanimation.zip file... I ask if you have it, as the "Boot Animations" PlayStore app may not have the stock Lenovo boot. Perhaps flashing it via SP Flash Tool is better?
4) Will you kindly share any updates here to TWRP versions, whenever released? Do you anticipate any update in the coming 1-2 months, for example? (not sure there are bugs in TWRP-3.0.2.3, if any)
5) If there is a newer Lenovo official ROM available (than today) we obviously lose the TWRP recovery if we flash it all via SP Flash Tools; but we keep TWRP recovery if we update to the new ROM via TWRP, correct?
Thank you.
Click to expand...
Click to collapse
About that Wi-Fi problem. No I don't have it, and I was reading that page with the fix. It seems it's caused by using wrong settings in SPFlashtool, so likely the vendor did this when applying his trash firmware.
If you wifi is not working (as some reported in that thread) I would of course try to get a refund.
Weather gadget only has Chinese cities, yes I noticed that so I was using yahoo weather instead on my phone.
I would suggest Titanium Backup, it's what I use.
No, sorry I don't have any boot logos or animations.
This phone is a bit slow on the updates. But if there's an update, you can do it through the OTA update function which only downloads the changes as a patch. Though If your phone is heavily modified it might not work correctly. Could try a factory reset first, or simply start a fresh.
Then you would probably need to download the original recovery and flash that first.
PS: You can break the system by removing too much of the lenovo stuff. Remember VibeUi is heavily integrated and impossible to remove completely. Also, for gapps go to www.opengapps.org
help
Can you help me a bit? I got an infected phone and i need to install a new rom to keep myself safe. (im kinda noob to installing stuff like these)
First bootanimation "china4Gchina", second ok and poweroff ok.
Please help to change to first animation or delete.
Thanks.
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??
So i tried rooting my huawei y5 prime 2018 and then i got a red warning on boot (awhile ago) so the only thing that fixed it was to use the download & format all option through spflash, Now my phone there is no keyboard, and many other apps are missing (like files app), plus imei, mac address, serial code is gone
so is there possible ways to fix it and also get latest update from huawei?
ty