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.
Hello :- 1st post from newbie... :fingers-crossed:
Background :
Asus TF101 - c4/2012 - S/n starts with BC0K..... - with dock, working but reboots every 10 mins, lots of non-responsive apps, slow performance.
c120 apps installed - for whenever I need them. Frustrated by about c20 that run that I didn't start up - I don't need them until I need them....
Task killers kill some but some just restart... ...so decided to root and load Cyanogen for more control over apps, esp. permissions, and hopefully improved performance.
My skills : - newbie to Android dabbling, but used to minor registry tweaks and driver installs in Windoze, and programming many years ago in DOS, Basic, IPL2, and even Fortran (yes, really ). Never got into OO stuff....
Rooting and Flash so far :
Tried Chanxxxx's routine but couldn't get it to work.
Tried Asus unlock routine - doesn't work on TF101 any more.
Tried ViperMod but most image sites and mirrors are smoke and dust. 1 image found wouldn't unpack - corrupted.
Finally found PERI v0.42 which worked after many attempts in fixing adb drivers and out of date server problems.
(Only one site thread mentioned turning off Asus Synch on the PC and the tablet too...).
All very frustrating, esp. given the age of most of the threads and links - but I'm persistent, if nothing else..
... ...am I the last human bean on the planet who wants to root an old TF101?
So, now got :
Rooted OK
SuperUser OK
TWRP 2.5.0.0 under the hood - came wth PERI routine (thanks Thing o Doom).
Cyanogen 9.1
Loaded CWM ROM Manager but when I ran it it said I should stick with TWRP installed already (?) - so I did.
So I used TWRP to flash Cyanogen 9.1 and GAPPs.
Now running fine apparently - first day - still need to reload all apps...
Issues
Q1) - Since tried to use PERI to install TWRP 2.8.1.1. over current 2.5.0.0 - replaced the 2.5 recoveryblob with the 2.8 blob.
- renamed 2.8 blob, also tried changing batch file to suit other name - but all failed.
- pushes ok with push command, but dd to of mmcblk0p4 fails - permission denied.
Any thoughts please on why permissions have changed?
- I didn't include the md5 file from 2.8.1.1 - as 2.5 didn't have one anyway.
- what could have changed to stop me replacing mmcblk0p4 ?
- I did run TWRP 'Fix Permissions' - though not really sure what that does....
- is my approach too simplistic and other skullduggery required?
[- Didn't use TWRP 2.8.1.1 install that came with it as I don't know how to run it. Noticed that the script referred to Busybox which I don't have].
[ Have installed Android SDK but no idea what to do with it ...].
Q2 - Has anyone tried Cyanogen 10.x on a TF101 - I see there is one but it was a Nightly?
- if you did, is it stable?
- what would be the main benefits - presumably JB improvements?
Q3 - New Problem - MSD and SD slots both report 'Damaged SD Card' when you pop one in - and corrupt it. So when I put it back in my Windows PC card reader it is unreadable and needs reformatting. Does it with Micro slot on tablet and full sized slot on keyboard dock. Just tried brand new SD card and banjaxed that.
Both USB slots are fine and don't corrupt the USB flash drive.
Could it be :
- TWRP setting? - TWRP doesnt let me mount the ext SD Card - but probably because it sees it as corrupted?
- CyanogenMod 9.1 issue?
- Other something in the stack that can be fixed with an adb push or...?
Thanks
TF
Hi there !
The tf101 is an old device , and Asus have took down the download links for the factory files i believe now. I do have a copy of it on my tf101 sd card. Do you want me to upload it for you ? .
When all of these reboot problems and app crashes started , do you think anything specific caused it ? And has your device always been like it ? Also , why did you need to replace mmcblk0p4?
I personally think it is a kernel problem . All cm nightly buids are pretty stable in my opinion ! So there is nothing to worry about there. Be aware you will need to flash a new twrp build if your planning to install lollipop although lollipop is v e r y slow in my opinion.. So don't bother . Anyway i hope that this info has helped you , and if you could give more information i will be happy to help further. Please click like on this post ! It means alot
---------- Post added at 01:14 AM ---------- Previous post was at 01:13 AM ----------
And welcome to XDA !
Thank you for the welcome!
therealduff1 said:
Asus have took down the download links for the factory files i believe now. I do have a copy of it on my tf101 sd card.
Click to expand...
Click to collapse
I have it already from the Asus site, thanks - but it doesn't work anymore. Asus have disabled the backend server bit that lets it continue to run the tweak on the TF101 apparently.
therealduff1 said:
When all of these reboot problems and app crashes started , do you think anything specific caused it ? And has your device always been like it ? Also , why did you need to replace mmcblk0p4?
Click to expand...
Click to collapse
It just got progressively worse 2014-2015 until I abandoned it as unusable. Sometimes it would stay up for a few hours... ..but not often.
The PERI routine, as with some others, replaces it for some reason - is it a whole partition?
therealduff1 said:
although lollipop is v e r y slow in my opinion..
Click to expand...
Click to collapse
I thought CyanogenMod 10.x was JellyBean, no? - I believe from some thread I read somewhere that the TF101 can't go beyond that?
Cheers.
---------- Post added at 01:14 AM ---------- Previous post was at 01:13 AM ----------
Hi there,
The factory images is not a "tweak" as you described it , and require no backend server to install(as far as I'm aware) because I have installed stock rom without internet before , which would not connect to any backend server you are describing .
Try using easyflasher instead of peri to do flash stuff to your device. I have never had problems with easyflasher in the past.
Type katkiss lollipop tf101. There is a lollipop build for the device , although I don't recommend it
If you are still unable to get things going, don't hesitate to send me a private message , or email me at [email protected] , and Il assist you with anything like installing the apx drivers for your device if you need the help !
---------- Post added at 12:50 AM ---------- Previous post was at 12:47 AM ----------
Does stock rom work ok on the device ?
Do you have the stock kernel or modded kernel?
This will help isolate the issue between the device or the software.
Please hit thanks on anything in my profile that you think could be useful to you sometime ! It only takes a moment , and it means alot !
therealduff1 said:
Hi there,
The factory images is not a "tweak" as you described it , and require no backend server to install(as far as I'm aware) because I have installed stock rom without internet before , which would not connect to any backend server you are describing .
Try using easyflasher instead of peri to do flash stuff to your device. I have never had problems with easyflasher in the past.
Type katkiss lollipop tf101. There is a lollipop build for the device , although I don't recommend it
If you are still unable to get things going, don't hesitate to send me a private message , or email me at [email protected] , and Il assist you with anything like installing the apx drivers for your device if you need the help !
---------- Post added at 12:50 AM ---------- Previous post was at 12:47 AM ----------
Does stock rom work ok on the device ?
Do you have the stock kernel or modded kernel?
This will help isolate the issue between the device or the software.
Please hit thanks on anything in my profile that you think could be useful to you sometime ! It only takes a moment , and it means alot !
Click to expand...
Click to collapse
Kat kiss is running g decently on my eeepad once I have over cclocked to 1500 mhz. Still a little slow but not to bad for an older device. Also if you want to install the new twrp you can just grab the zip file and flash it in the twrp you already have and follow the instructions and it will be updated from 2.5 to 2.8
Edit: yeah never mind I see what your saying I just downgraded to katkiss 4.4.4 and it's running so much smoother
xSilas43 said:
Kat kiss is running g decently on my eeepad once I have over cclocked to 1500 mhz. Still a little slow but not to bad for an older device. Also if you want to install the new twrp you can just grab the zip file and flash it in the twrp you already have and follow the instructions and it will be updated from 2.5 to 2.8
Edit: yeah never mind I see what your saying I just downgraded to katkiss 4.4.4 and it's running so much smoother
Click to expand...
Click to collapse
Awesome !
Good to know that your device is running well
therealduff1 said:
Hi there,
The factory images is not a "tweak" as you described it , and require no backend server to install(as far as I'm aware) because I have installed stock rom without internet before , which would not connect to any backend server you are describing .
Click to expand...
Click to collapse
Ah- crossed porpoises - I meant the ability to run the boot unlocker tweak (not the KitKat ROM image) - unlocker still available but disabled at Asus server - which it has to reference to note your CPU #, according to posts on various forums...... - solved by Peri now.
therealduff1 said:
Try using easyflasher instead of peri to do flash stuff to your device. I have never had problems with easyflasher in the past.
Click to expand...
Click to collapse
I'll try it next time I need to flash something from the PC, ta.
therealduff1 said:
[/COLOR]Does stock rom work ok on the device ?
Do you have the stock kernel or modded kernel?
This will help isolate the issue between the device or the software.
Click to expand...
Click to collapse
I'm not planning to use a stock ROM - I wanted to try out Cyanogen - as may also get a phone with it on.
- so the kernel is whatever came in the CyanogenMod9.1 pack.
xSilas43 said:
Also if you want to install the new twrp you can just grab the zip file and flash it in the twrp you already have and follow the instructions and it will be updated from 2.5 to 2.8
Click to expand...
Click to collapse
Thanks - I'll look at that later - once I'm sure it's all stable now on all fronts.
ROM version 1.0.7 available through OTA update. See post #93 for instructions. Most of these issues have been fixed.
I have bought Nomu S20 which in principle is a great smartphone by hardware but is plagued with many problems. I have started this thread to discuss possible solutions, as part of the problem is that Nomu does not provide any OTA (it looks like a face FOTA), and there is no suppor from their website nomu.hk, not even to supply a downloadable stock ROM. So here are the problems I have found:
1. Stock ROM comes prepacked with Android Triada Virus*. The virus is very persistent, and imune to antivrus programs. It silently installs a fake "Settings" app in the background. Antivirus scan software can detect the app and delete it, but it will be installed again silently later on. See attached files for some of the related processes/apps. There is also the com.chunmei.calculator publicity Spam/virus. It's possible to uninstall it, but it will come up again on the background, at some trigger event. * For possible fixes/workarounds specific to this ROM see posts #32, #53 and #57. Also read the other posts.
2. GPS software is very glitchy¹: it's necessary to reset all GPS data at almost every restart of the GPS service. I have tried many tweakings, but the problem seems to be really in the ROM, how it communicates with the GPS chipset. Using an app like GPS Reset COM before using an app which requires geolocation helps with solving the problem by forcing a full, cold start. Using GPS Up in the background also helps with keeping the service functioning while it's been used by or a fix is not gotten by other navigation software. ¹ The GPS problem is fixed in ROM version 1.0.6 -- Link --- (Also available on Needrom.com.) See post #96 for further tips on how to possibly stabilize the GPS/GLONASS fix. See post #93 for instructions on how to update your ROM.
3. Microphone volume level is low: microphone volume is low when used in apps like Whatsapp to record a message. One has to speak very close to the microphone so that the one receiving the message might hear it in a good, reasonable volume. I've had other phones and this is a problem specific to Nomu S20.
4. No support from their website: there is no support from their website nomu.hk. They do not even supply stock ROMs for those who might want to update their phone or fix a bricked one. One has to rely on websites like needrom.com or this XDA forum to get the stock ROMs.
5. OTA/FOTA is fake: it really doens't work. I had installed version 1.0.2 and 1.0.3. In both cases the wireless update feature gives the message that the phone already has the latest software. So OTA/FOTA is most likely a fake , non responsive service.
6. Charger doesn't work when the phone is off: the phone doesn't recognize the plugged charger when the phone is off.
7. Android translations not complete: specially in version 1.0.2, several languages are missing. Systems apps like the dialer may not have an accurate translation in version 1.0.3.
There's a new official ROM on needrom.com which purportedly solves the Triada Trojan problem: NOMU_S20_COMMON_V1.0.6_2017_05_18_FQ5C23WTE1D.XWP_.NOMU_.M0.HB_.H.SM_.0518.V3.06 mod edit - link removed I shall be testing it in the coming days.
Update: the uploader himself tried already and states that the ROM is also infected: "Tried already…. no help, All Nomu ROMs are still infected… anybody can help?".
JVitor said:
5. OTA/FOTA is fake: it really doens't work. I had installed version 1.0.2 and 1.0.3. In both cases the wireless update feature gives the message that the phone already has the latest software. So OTA/FOTA is most likely a fake , non responsive service.
Click to expand...
Click to collapse
Maybe it's because "Wireless Update" app is infected by itself (Android/Trojan.Downloader.Fota.e) as reported by Malwarebytes Anti-Malware scanner.
Nice thread btw! :good:
navigatoras said:
Maybe it's because "Wireless Update" app is infected by itself (Android/Trojan.Downloader.Fota.e) as reported by Malwarebytes Anti-Malware scanner.
Click to expand...
Click to collapse
Indeed. Perhaps if we delete, disable or uninstall files assciated with FOTA (Wireless Update), we might "cure" the ROM. I have noticed that the "Seetings" app (com.chunmei.calculator) is installed through a temporary installer at /storage/emulated/0/.jm/com.android.vending/8949_1004_1495532446456.xde.apk If the trigger event or process of origin is located, we might "cure" it. It could be the Wireless Update feature/FOTA as well. I will experiment with that.
Also, there seems to be an alternative ROM, from a rebrand called MTT IDEAL: https://forum.xda-developers.com/showpost.php?p=72467315&postcount=19 Official website: https://www.mttmobiles.com/fr/mtt-ideal If we can get the official ROM from MTT IDEAL, it might work on Nomu S20 and if from a different developer, it might also be clean and better.
I have already tried deleting the following folders and still the /storage/emulated/0/.jm/com.android.vending/8949_1004_1495532446456.xde.apk processs is injected randomly and the fake Settings app is installed. So it doesn't seem to be related with Wireless Update/FOTA.
Code:
/system/priv-app/SecurityService
/system/app/AdupsFota
/system/app/AdupsFotaReboot
JVitor said:
I have already tried deleting the following folders and still the /storage/emulated/0/.jm/com.android.vending/8949_1004_1495532446456.xde.apk processs is injected randomly and the fake Settings app is installed. So it doesn't seem to be related with Wireless Update/FOTA.
Code:
/system/priv-app/SecurityService
/system/app/AdupsFota
/system/app/AdupsFotaReboot
Click to expand...
Click to collapse
Does this mean you found a way to root the phone?
I have contacted a Nomu representative and supposedly the company tried "to clean the malware from their rom" with the 1.0.6 update. I am not sure that the company put the malware there on purpose (for some extra cache) and was not fooled by a third party (as a lot of other Chinese manufacturers have the same issue).
I am not familiar flashing ROMs with MediaTek based phones (not even sure if the method is CPU based) but are we sure that ROM 1.0.6 is also infected, according to the user in the 'needrom' forum and the result is not dependent on the flashing method (ie a partial vs a full wipe of the storage area)?
Let's hope that we'll be able to also try the official ROM from MTT IDEAL at some time..
navigatoras said:
Does this mean you found a way to root the phone? I have contacted a Nomu representative and supposedly the company tried "to clean the malware from their rom" with the 1.0.6 update. I am not sure that the company put the malware there on purpose (for some extra cache) and was not fooled by a third party (as a lot of other Chinese manufacturers have the same issue).
Click to expand...
Click to collapse
Yes. I have rooted the phone. I had to install first TWRP recovery and then flash SuperSU via TWRP. A little complicated: 1) First unlock bootloalder via Fastboot; 2) Flash TWRP and reboot into recovery; 3) Flash SuperSU flashable zip file; 4) Rewrite IMEI numbers using SN Write tool (click here).
When I flash a new ROM I have to do it all over again (except if IMEI was backed up before, but then root might be necesssary for this anyway). I will try and test the 1.0.6 update next week, with a full wipe/format command.
All right! Thanks for confirming that the above mentioned method works. As I am planning a motorbike trip (the reason I bought the phone in the first place) I don't feel comfortable to follow the procedure at this time but I will definitely be more experimental after the trip.
I will eagerly wait for your results, as you 've already said "this is an otherwise good device", and report back if the company representative communicates to me any more info!
navigatoras said:
I will eagerly wait for your results, as you 've already said "this is an otherwise good device", and report back if the company representative communicates to me any more info!
Click to expand...
Click to collapse
Thanks. I will post results here. Hopefully meanwhile the representatives or someone else provide some other solution, if version 1.0.6 is not the final one. Have a nice trip. You can use some antivirus scanner/monitor to keep the Settings spammer/trojan in check and uninstall it when it comes up.
I have flashed and tested ROM version 1.0.6 and although antivirus programs don't detect any threats, the Triada virus is still there. The fake "Seetings" app (com.chunmei.calculator) is installed through a temporary installer at /storage/emulated/0/.jm/com.android.vending/8949_1004_1495532446456.xde.apk. It's installed on the background, at some random event. I am not able to determine the process of origin.
Mega.nz link:
NOMU_S20_COMMON_V1.0.6_2017_05_18_FQ5C23WTE1D.XWP_.NOMU_.M0.HB_.H.SM_.0518.V3.06
I wonder if message #19 posted on the thread about com.chunmei.calculator (link in your first post) about removing and replacing the USIM card has something to do with the persistence of the above mentioned malware. Is it possible that some code is stored in the USIM card?
navigatoras said:
Is it possible that some code is stored in the USIM card?
Click to expand...
Click to collapse
Very unlikely: https://security.stackexchange.com/questions/121571/can-a-sim-card-propagate-malware Triada is a very sophisticated malaware: http://news.softpedia.com/news/triada-trojan-infects-android-s-zygote-core-process-501304.shtml
In fact, developers/hackers have plenty of options to infect a phone ROM with malaware/viruses. To my mind it's the manufacturer's responsibility to make sure that the ROM they are supplying is clean of viruses and other malaware. In this case it's Nomu's fault not to make sure their phones are free of malaware or viruses. Even if they might have been fooled by the developer which supplied the software, it shows poor quality and safety controls. And they should at the least fix it immediately once a problem has been detected.
Update: the below fix doesn't work. Fake "Settings" came up again.
But this time, it seems that the developer (or hacker) which supplied the ROM has been just joking/fooling with us. In version 1.0.6 the FOTA feature was removed, as well as the other files which were associated with malaware, some of them mentioned in this thread. Then they added an app called "Software Updates". It has this icon:
It's a system app meant purportedly to apply software updates to the ROM. I suspected that this app was injecting the malaware when pretending to look for updates. So I uninstalled it with System app remover (requires root). I also deleted the temporary file at /storage/emulated/0/.jm/com.android.vending/8949_1004_1495532446456.xde.apk (with Root Browser). Since then the fake "Seetings" app (com.chunmei.calculator) has not come up again. I will be monitoring in the next couple of days and report back if it shows up (or another suspect process).
Unfortunately the above fix doesn't work. Fake "Settings" came up again this morning after starting YouTube app. Hackers are not kidding.
For those who might be interested, attached follows the the installer of the fake "Settings" app which is injected by some unknown process at /storage/emulated/0/.jm/com.android.vending/8949_1004_1495532446456.xde.apk (it looks like it's renamed or changed after install so that antivrus programs will not see it or detect it).
I suppose that there isn't any custom rom for this phone that is clean, right? :crying:
Boys, let's go to spam this problem on their official Facebook page, maybe they will wake up and take this problem seriously.
https://www.facebook.com/nomumobile/
---------- Post added at 12:07 PM ---------- Previous post was at 12:07 PM ----------
Boys, let's go to spam this problem on their official Facebook page, maybe they will wake up and take this problem seriously.
https://www.facebook.com/nomumobile/
Can you post a screenshot of the rom/software version your device is using? Have you scanned your device with Malwarebytes' scanner?
My firmware version is 1.0.3, but the virus is still there in versione 1.0.6.
Anyway, Nomu just released the S30 mini which would seem to have exactly the same hardware of nomu s20. Maybe that the firmware is compatible? Even if there are no viruses also in this one...
---------- Post added at 12:44 PM ---------- Previous post was at 12:40 PM ----------
Kiloplt said:
I own one too. But have no virus appearing untill now.
Click to expand...
Click to collapse
This virus seems that remain "hidden" for a while... I've used my phone for about 4 mounths until the first ads appeared.
I've updated my phone to the latest ota firmware, rooted and deleted virus with demo license of Dr.Web.
No virus so far...
LeonKillah said:
I've updated my phone to the latest ota firmware, rooted and deleted virus with demo license of Dr.Web.
No virus so far...
Click to expand...
Click to collapse
I deleted it with avira and created a file with the exact name and changed to read only (rooted phone). It seems like It's worked. Yet.
---------- Post added at 08:03 PM ---------- Previous post was at 07:13 PM ----------
Btw for me the 1.0.6 zip is corrupted says the TWRP when I try to install. I successfully installed the chamelephone os.
During the last few months I have been testing several Nougat rom/kernel/modem/su combinations for the hlte N9005 international.
I created this thread to share my setup, hoping it will help others to save the many hours of research, trial, error and frustration I had before reaching the jackpot.
I have 3 hlte phones at my disposal, two myself and one my wife. All three are running trouble free.
By using my setup you will get:
Absolutely no freezes, reboots or FCs
Stable root and Safetynet checks ok
GPS fast and stable fix - average 5 seconds worst 20 seconds
Low battery drain (of course actual drain depends heavily on your apps and usage)
Everything works (AFAIK - you tell me what does not)
Keep in mind my main goal is to provide a stable setup. I will do my best to update this thread regularly, but it is very unlikely I will be using the very latest builds available, mainly because before I adopt a new build it must be thoroughly tested.
If you're interested head to the guide in Post #2
Why Resurrection Remix?
RR has, IMHO, the best combination of features and stability. The RR team has been around for a long time without the ups and downs of other roms. For the Note 3 we are in a very fortunate time, with an official build and many unofficial builds to choose from.
Since RR is based on LineageOS, it is available for most devices. It is very likely when we finally retire our Note 3 and move to another flagship, RR will be there for it.
Why Not Oreo?
Well, thread title says it all.
Credits and Thanks:
@vidwhal for the current RR build
@gj86 for Synergy kernel
@Jairus980 for Xenial kernel
@Hereiwas and @jcadduono for modems and bootloaders
@topjohnwu for Magisk
@stangri and @kantjer for Magisk unofficial daily beta builds
@Deic for the Safetynet fix Magisk module and @NovelliJack for finding the module
@MastahF and all other contributors that made the Open GApps project possible
Special thanks to @tarkzim for the RRN build used in initial setups.
and everyone else I forgot to mention.
>>>>>>> I know - screenshots below are from a previous setup. I will update then sometime in the future.
Rock Stable Setup
Using Resurrection Remix
Revision 11 - 11-Mar-2018
Phase 1 - Prepare for install
Here I am assuming you have a Windows PC. If not you will need to use google search to adapt my instructions to your available OS/hardware. The PC is only required for this phase.
1 - Samsung USB Driver:
Make sure you have the Samsung USB driver installed in your Windows PC.
If not download and install the latest driver:
- SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.65.0.exe
2 - Odin:
If you do not have Odin, get it here, unpack to any folder and create a shortcut pointing to Odin3 v3.09.exe.
There are newer versions of Odin, but they may have issues with our Note 3. Odin v3.09 is the one to use.
3 - TWRP
New to TWRP? Read this guide: TWRP: the complete guide to using Recovery on Android.
If you do not already have it, install TWRP 3.2.1-0. Download it from https://dl.twrp.me/hlte. More info here.
If you no not have TWRP installed download the .tar file and flash with Odin.
If you have an older version download the .img file and use your current TWRP to flash the image into recovery partition.
4 - Update Bootloader and Modem:
You have to install latest Nordic Countries Bootloader and Modem. I have prepared a "tar.md5" with both.
And yes, modem is not country or region dependent. Rest assured Nordic will work no matter where you are.
Get it from here: N9005_Nordic_XXUGPQB1-Modem_XXSGBQD1-Bootloader.tar.md5
Updating bootloader and modem is a must!
If you don't you may get the "SIM Card not detected" error and GPS fix will be slow or not work at all.
There are many sure ways to flash modem and bootloader so that they "stick". What always works for me is:
- Restart into Recovery (TWRP)
- Select Reboot->Power off
- Turn on directly into download mode by holding Down Arrow+Home+Power at the same time
- Connect phone to PC
- Flash with Odin using the AP slot
Now you should check if update was successful. The best way is to install the app Phone INFO, run it and select the Firmware tab. The correct Bootloader and Baseband (modem) above should be displayed. There is a screenshot in first post.
If the update did not work repeat the steps carefully until it does. You may, as a last resort, after powering off remove the battery, wait for about 30 seconds, reinsert the battery and then turn on directly into download mode.
Thanks to @Hereiwas for the files I have used in previous setups. Check out in his thread Bootloader and Baseband for SM-N9005.
If you need more info on flashing modems and bootloaders also take a look at @jcadduono thread [Direct Download] Latest Bootloaders & Modems.
PHASE 2 - Download the necessary installation files
1 - Resurrection Remix Nougat rom - thanks @vidwhal:
Download from here: RR-N-v5.8.5-20180101-hlte-Official-vidwhal.zip.
Please note that I am not the rom builder or developer. All credits go to @vidwhal and the RR Team.
This is the rom thread: [ROM][HLTE][UNOFFICIAL][OMS]Resurrection Remix N.
Please note this build may not be the latest available. The goal here is to have a stable rom that you will be able to use as a daily driver with no issues for a long time. Only after a lot of testing a new build makes into my setup.
I modified the zip to remove Magisk. This will make it easier to use newer or beta Magisk builds if necessary in the future. Remember Safetynet is a cat and mouse game and changes happen fast.
Special thanks to @tarkzim, who produced the RR builds used in earlier setups. He did a fantastic job of producing a very stable build without a Note 3 device for tests. His builds led me to create this thread.
2 - Magisk v16.0 Official - thanks @topjohnwu):
Magisk Installer: Magisk-v16.0.zip
Magisk Manager: MagiskManager-v5.6.1.apk (optional - you might need it in the future)
Magisk Uninstaller: Magisk-uninstaller-20180222.zip (optional - you might need it in the future)
if you decide to use newer builds do it at your own risk. I strongly recommend to keep these.
3 - Gapps:
Open Gapps Pico: open_gapps-arm-7.1-pico-20180311.zip
Not much to say here. Open GApps FTW.
Again the above build is the one I tested. Use this for a failproof installation, but feel free to use a newer build. Usually it will not be a problem.
I prefer Pico Gapps so I have the bare minimum as system apps. And I live by the KISS Principle. All other gapps I need are installed as user apps so I am allowed to use Titanium Backup to backup/restore them with data.
If you would rather use another Gapps package just pick the one you want. All packages should work but the Aroma. Aroma does not work in TWRP 3.
4 - Xenial Kernel - thanks @Jairus980:
Xenial Kernel: [Hlte][Xenial-b26x][02.01.18][N7.1-GSM].zip
Kernel thread: [Kernel][Xenial][Hlte].
With Xenial you have some fixes like the correct charging current in lock screen and working Gravity, Linear acceleration and Orientation sensors. Of course there is a lot more under the hood. If you plan to do some kernel tweaking Xenial offers more options.
If you do flash Xenial kernel do not report any bugs in RR thread. To report a bug you must first go back to stock kernel by dirty flashing RR and Magisk. If you are still able to reproduce the bug then you may post it in RR thread.
Even if there is a newer kernel release, you should keep using the build I posted here to have my tested stable setup.
Special thanks to @gj86 for his Synergy Kernel, used in my previous setup. It is also a great option.
5 - GPS Fix:
In this setup there is no need for a GPS fix. GPS is fast and rock stable as it should always have been.
But you really must update your modem to my recommend Nordic QB1 or GPS will be slow or not work at all.
Do not worry about your current location. The modem will work not matter where you are.
Latest RR builds somehow made GPS fix slower. I checked the gps.conf file and it is exactly the same as in previous builds.
I have my own optimized gps.conf, prepared originally for Marshmallow CM13, with a few more adjustments for Nougat.
After installing my gps.conf in latest RR build, gps fix is back to normal, taking only a few seconds.
I prepared a flashable zip to install my gps.conf. It saves existing gps.conf and put mine in its place.
Download it from here: Fix-GPS-for-hlte-la14.1-based-roms-v1.zip.
PHASE 3 - Backup!!
Now it is time to make backups of your current setup.
Use TWRP to make a nandroid backup. You will need it if something goes wrong. If you are paranoid like me make two and save them on your PC hard drive.
If you use Titanium make also a Titanium full backup. Remember that you should never restore system apps or settings. Use Titanium only to restore user apps and xml backups of wifi passwords, call log and sms messages.
The steps to install the new ROM will not erase your internal storage, but why not make a backup of everything to your PC or an OTG USB Drive.
PHASE 4: Install
- Make sure you have updated TWRP and your bootloader and modem as instructed in phase 1
- Make sure you have all files downloaded from phase 2 in your phone - preferably in external sdcard
- Make sure you have backups!!
- Reboot into Recovery (TWRP)
- Use advanced wipe to wipe System, Data and Cache
- Flash RR-N-v5.8.5-20180101-hlte-Official-vidwhal.zip
- DO NOT WIPE ANYTHING
- Reboot System (be patient - it will take a while, around 3-4 minutes)
- Pick your preferred launcher
- Check Settings->Date & Time and make sure it is ok
- Reboot into Recovery (TWRP)
- Flash [Hlte][Xenial-b26x][02.01.18][N7.1-GSM].zip
- Flash Magisk-v16.0.zip
- Flash open_gapps-arm-7.1-pico-20180311.zip (or the one you prefer)
- DO NOT WIPE ANYTHING
- Reboot System (this time it will be faster)
- Go to Settings->Accounts and add your google account
- Customize your other settings
- Run Magisk Manager and check if SafetyNet passes
- If not disable/reenable "Magisk Hide" option in Magisk Manager Settings and try again
- Restore/install apps/data
- PROFIT!
[Reserved]
wow, nice to see that someone using and "sharing" my builds
but a little tip for you, maybe you can ask me first before you post something are modified from me, no offense and i saw that includes my name on it.
just remind you and i think i will keep building this when i'm free, anyway, thank you for posing this. all good.
EDIT: also i think there is no need for removing magisk separately, it's fine for flashing newer magisk over the older one.
tarkzim said:
wow, nice to see that someone using and "sharing" my builds
but a little tip for you, maybe you can ask me first before you post something are modified from me, no offense and i saw that includes my name on it.
just remind you and i think i will keep building this when i'm free, anyway, thank you for posing this. all good.
EDIT: also i think there is no need for removing magisk separately, it's fine for flashing newer magisk over the older one.
Click to expand...
Click to collapse
Sorry, you are absolutely right.
Thanks for being cool with it.
The main point in changing the rom zip is removing the magisk manager system app. It is a little tricky for noobs to remove the system app to be able to install the v5 beta Magisk Manager.
And thanks again for making your fantastic RR build available.
Thank's for your work. I installed all, but then I had a problem. When I try to open settings/apps, it crashes everytime....
sperug said:
Thank's for your work. I installed all, but then I had a problem. When I try to open settings/apps, it crashes everytime....
Click to expand...
Click to collapse
This does not happen in my phones.
In my work phone I have 600+ apps installed. It takes a while to open but no crashes.
If you post a logcat I may be able to help.
I reinstalled everything, and before made a full wipe, also of the internal storage. And the problem was no more present! Wow! And thank you again...
I checked AFH and have 30+ downloads of installation files.
Any more success or failure cases? Please let me know.
This might be a silly question: You wrote I should download the latest NORDIC COUNTRY Bootloader and Modem.
Is this also correct if im not living in an other region or should I download the one from my Country? Thanks.
BobbyKa said:
This might be a silly question: You wrote I should download the latest NORDIC COUNTRY Bootloader and Modem.
Is this also correct if im not living in an other region or should I download the one from my Country? Thanks.
Click to expand...
Click to collapse
AFAIK it should work for you no matter where you are.
I live in Rio de Janeiro, Brasil and use it.
If it does not work for you just flash another one.
I tried the Nordic ones and everything seems to work. Not a killer but would be great: is there a way to get SPen functions inclidung Air Command? Thanks for the help.
BobbyKa said:
I tried the Nordic ones and everything seems to work. Not a killer but would be great: is there a way to get SPen functions inclidung Air Command? Thanks for the help.
Click to expand...
Click to collapse
To use Sammy Spen apps/features you need a Touchwiz based stock rom.
There are some apps with similar features for AOSP roms.
Many users say the best is SPenCommand developed by @emandt. It is paid but users say that the app is well worth the price.
Check the SPenCommand Google+ Comunity.
Great post. I don't see google assistant working, any clue?
Sent from my Pixel using Tapatalk
---------- Post added at 09:22 PM ---------- Previous post was at 09:10 PM ----------
Please ignore, I installed nano gapps and it worked
Sent from my Pixel using Tapatalk
what about battery life ?
has anyone tried this on Sprint Note 3 sm-n900p ?
svbarbosa said:
Check the SPenCommand Google+ Comunity[/URL].
Click to expand...
Click to collapse
I installed SPenCommand but the App doesn't open. When clicking the Icon nothing happens. Anyone knows about this Problem or knows another app for this?
Beside that everything (incl. Batterylife) seems great on this first day of testing.
I have followed your step to instal, wipe dalvik/art, system, data & chache. Flash ROM then reboot.
I got 'Could not do normal boot'.
Enter TWRP again and instal synergy kernel and reboot, I still got 'Could not do normal boot'.
My phone:
Samsung Galaxy Note 3 SM-N900S (Korea)
TWRP 2.8.7.0 hlteskt
CP N900SKSU0GPC5
BL N900SKSU0GPB1
sent from my Galaxy Note 3 using XDA Labs
BobbyKa said:
I installed SPenCommand but the App doesn't open. When clicking the Icon nothing happens. Anyone knows about this Problem or knows another app for this?
Beside that everything (incl. Batterylife) seems great on this first day of testing.
Click to expand...
Click to collapse
I have never used SPenCommand myself. Just read good things about it many times in other threads. Try to search and get help from people who are using it.
You may also check these apps: Note Buddy (S Pen Helper) and CM S Pen Add-on(ROOT).
And this guide on them: The Ultimate S Pen Customization Tool for Your Galaxy Note 3.
But be advised that I have no experience using these apps. Just found them using google.
opexblue said:
I have followed your step to instal, wipe dalvik/art, system, data & chache. Flash ROM then reboot.
I got 'Could not do normal boot'.
Enter TWRP again and instal synergy kernel and reboot, I still got 'Could not do normal boot'.
My phone:
Samsung Galaxy Note 3 SM-N900S (Korea)
TWRP 2.8.7.0 hlteskt
CP N900SKSU0GPC5
BL N900SKSU0GPB1
sent from my Galaxy Note 3 using XDA Labs
Click to expand...
Click to collapse
Sorry I can not be of help here. I only have the hlte N9005 international Note 3.
Maybe you could replace Synergy RC9 by a kernel that you are sure works with your N900S.
svbarbosa said:
Sorry I can not be of help here. I only have the hlte N9005 international Note 3.
Maybe you could replace Synergy RC9 by a kernel that you are sure works with your N900S.
Click to expand...
Click to collapse
Thank you for fast response. I will try other kernel.
LineageOS 14.1 Port ROM
Lenovo Tab 3 8"/TB3-850F
•WARNING:
You are installing this custom Android ROM at your own discretion and risk. If you are unclear on anything, please stop and do some research before proceeding further. This is not a Q & A thread, so please post comments on topic with subject matter relating directly to this ROM. I will not be held responsible for devices which become bricked or damaged as a result of installing this ROM. You are encouraged to read and re-read the OP prior to installing this ROM on your device. Please visit this thread for now to make general inquiries about this ROM or about any other questions or issues you may have regarding the 850F. Either myself or XDA Senior Member @pndwal, who is very knowledgeable about this device and Android in general, will try to address your questions. https://forum.xda-developers.com/android/general/guide-lenovo-tab3-8-tb3-850f-t3559786 User input and feedback are essential in making improvements, fixing bugs, and in helping development for this device to continue to evolve.
Any skilled devs interested in contributing in any way to development for the 860F, please use the above thread to contact @pndwal and coordinate with him in that area.
I am not a developer, nor did I contribute to the porting of this LineageOS 14.1 custom ROM for the TB3-850F. I merely packaged up the files, added GApps Pico, made a few minor tweaks, and created a TWRP flashable zip installer for this ROM. Please do not request updates or make ETA type inquiries on this thread. Whether or not this ROM will be maintained is still up in the air. Please give any and all credit to the individuals I have listed below under Mentions & Credits.
LineageOS 14.1 is a free, aftermarket distribution of Android 7.1.2 Nougat, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many individuals within the Android community. Although this particular LineageOS build does have GApps Pico preinstalled, it can be used without any need to have any Google application installed. LineageOS does still include various hardware specific code, which is nonetheless slowly being open-sourced anyway.
SOURCES:
LineageOS Source Code: https://github.com/LineageOS
Kernel Source Code: https://support.lenovo.com/us/en/downloads/ds112711
LineageOS Gerrit Code Review: https://review.lineageos.org/q/status:open
FEATURES & SPECS:
•LineageOS Version: 14.1
•Android Base Version: 7.1.2_r8 Nougat
•Build ID: N2G470
•SDK Version: 25
•Build Date: May 15, 2017
•Security Patch Level: May 5, 2017
•Kernel Version: 3.18.19 (mods by @wezroot2k)
•LineageOS API Level: Guava (7)
•GApps Pico Pre-installed
•Insecure Boot Image Support
•Force Encryption Disabled (Opt-Encrypt)
•AVB/dm-verity Disabled
•Fully Deodexed
•Fully Zip-aligned
•User Opt Root or Non-Root
•Status: Unofficial/Stable
WORKING:
•Booting
•WiFi
•Bluetooth
•Graphics/Video Playback
•Audio
•GPS/Location Services
•GApps
•Magisk Universal Systemless Interface
BUGS:
I am presently working on Settings UI to omit the mobile networks/telephony entries. These are present because this ROM was originally a smartphone port. Otherwise, please feel free to submit a proper bug report or, at a minimum, a clear description of the bug or instability, including screenshots if possible.
A bug has been reported for apps that require superuser permissions (Greenify, root file managers, etc), and I have determined that installing the latest Magisk systemless root will alleviate that bug.
Upon initial boot, during setup, you may experience an issue with Setup Wizard force closing. I have posted a quick workaround for this below under the Installation Instructions heading.
REQUIREMENTS:
You need an unlocked bootloader and TWRP custom recovery installed. If you need help with either of these topics, please visit this thread for guidance: https://forum.xda-developers.com/android/general/guide-lenovo-tab3-8-tb3-850f-t3559786
INSTALLATION INSTRUCTIONS:
1. Download the ROM zip from the below download link and save it to your device storage...
2. Boot your device into TWRP recovery mode...
3. Wipe Data, Cache & Dalvik/ART (my installer automatically formats the /system partition)...
4. Select Install, navigate to saved location of the ROM zip, select it and swipe the action bar to begin installation...
5. Reboot system (installation will take around three minutes).
*Because this ROM is fully deodexed, first boot can take several minutes to complete while the Dalvik/ART directories are being written for the first time. The second and subsequent boot times will be much faster. Also, on first boot, select your language then choose SKIP on the Insert SIM Card screen. You will then be prompted to set up your device as new or copy data from another device as part of setup. At this stage, if the Setup Wizard force closes, swipe down from the top of the screen to access Quick Settings and go ahead and connect to a WLAN/WiFi network. Now, go back to the previous screen and Setup Wizard should function normally and allow you to proceed with setup of your device. I am presently working on removing SIM/Mobile Network settings on this device, so hopefully this will be fixed soon, and a true WiFi-only tablet port will be yielded.
**As mentioned supra, this ROM is packaged with GApps Pico, which provides the bare bones minimum for Google Play functionality. If you want a GApps package other than the one preinstalled, visit https://opengapps.org/, choose ARM64, Android 7.1, and select your preferred package. Simply install the GApps package after Step 4 above. If you want root, visit the official Magisk release & announcement thread here https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445, and download the latest Magisk Manager apk. Install the apk, go to Developer Options and enable Apps & ADB in the root options menu. Open Magisk Manager, select Install, pick the direct install option, and systemless root will be installed via patched boot image. Reboot and systemless root should be properly installed & stable. Be sure and hit the Thanks button on @topjohnwu's thread if you use Magisk.
MENTIONS & CREDITS:
This port was made possible by a number of individuals both here at XDA and abroad:
- Credit goes to 4PDA (Russian Development site) member chipa76 for the original TB3-850M port, and to 4PDA member al_rus for his contributions to, and for posting that port.
- Credit and thanks for the breakthrough moment for TB3-850F users must go to XDA member @wezroot2k who, after others tried for many months, was finally able to stabilise this ROM for our device by recompiling the ported boot image with TB3-850F stock kernel. Also, he has worked on tweaks to streamline the ROM for TB3-850F.
- TWRP flashable ROM package as well as some tweaks to streamline the ROM for TB3-850F have been made by the OP, @AeonFlux1603, who will continue to work on a few further improvements, insomuch as spare time will allow
- Thanks to XDA Senior Member @pndwal for his dedication to this device and for passing on suggestions from the 4PDA Devs regarding the adopted method of stabilising ROM for TB3-850F.
- Last but not least, thanks and credit goes to the entire LineageOS Dev Team for making this custom aftermarket distribution of Android possible for low-grade, mid-grade & flagship devices alike.
DOWNLOAD LINK:
LineageOS 14.1 for TB3-850F: https://drive.google.com/file/d/1bbpwyvP_S4k1PJaLa6RN3dFDF8UYEcNj/view
@wezroot2k, I just wrote up a full thread for the ROM and hit the post button. It posted the first paragraph and that's it. Two hours of work and my XDA Labs app deleted everything.
AeonFlux1603 said:
•WARNING:
You are installing this custom Android ROM at your own discretion and risk. If you are unclear on anything, please stop and do some research before proceeding further. This is not a Q & A thread, so please post comments on topic with subject matter relating directly to this ROM. I will not be held responsible for devices which become bricked or damaged as a result of installing this ROM. You are encouraged to read and re-read the OP prior to installing this ROM on your device.
•LineageOS
Click to expand...
Click to collapse
I wonder why that is?
I think you should talk to PW
---------- Post added at 08:49 AM ---------- Previous post was at 08:46 AM ----------
AeonFlux1603 said:
@wezroot2k, I just wrote up a full thread for the ROM and hit the post button. It posted the first paragraph and that's it. Two hours of work and my XDA Labs app deleted everything.
Click to expand...
Click to collapse
Y would the app do that?
Maybe you would have to create the thread from a PC.
wezroot2k said:
I wonder why that is?
I think you should talk to PW
Click to expand...
Click to collapse
Oh. Did I do something wrong?
wezroot2k said:
I wonder why that is?
I think you should talk to PW
---------- Post added at 08:49 AM ---------- Previous post was at 08:46 AM ----------
Y would the app do that?
Maybe you would have to create the thread from a PC.
Click to expand...
Click to collapse
I'll redo the work in the morning. That's got me as aggravated as you can get. I posted full sources, credits, instructions, specs, etc. All got erased.
AeonFlux1603 said:
Oh. Did I do something wrong?
Click to expand...
Click to collapse
No man,just saying PW might know why the app would just post part of the thread and not the full thing.
---------- Post added at 09:08 AM ---------- Previous post was at 09:07 AM ----------
AeonFlux1603 said:
I'll redo the work in the morning. That's got me as aggravated as you can get. I posted full sources, credits, instructions, specs, etc. All got erased.
Click to expand...
Click to collapse
Sorry to hear about that man.
App could've timed out. Similar to chrome. I copy/select all before confirming just incase (with pretty much every hefty message I write)
Hemphiz said:
App could've timed out. Similar to chrome. I copy/select all before confirming just incase (with pretty much every hefty message I write)
Click to expand...
Click to collapse
Oh ok. Between that, copy/pasting and backspacing a lot, that's likely what happened. Working on reworking the thread now. Thanks for the insight. I'm editing in a little at a time to play it safe.
AeonFlux1603 said:
Oh ok. Between that, copy/pasting and backspacing a lot, that's likely what happened. Working on reworking the thread now. Thanks for the insight. I'm editing in a little at a time to play it safe.
Click to expand...
Click to collapse
Just read this new thread! Well done n many thanks.
As I explained in other thread (not sure if you understood properly - please read it carefully again to avoid heartache), XDA Labs does have a serious fault. Simply put, posts are shortened to a point where '*' symbol occurs, and because copying and pasting often swaps spaces (between words) for this symbol, the post gets truncated and your efforts are lost!
I said:
Frustrating to lose all that typing . Sorry to hear that.
Beware of accidently hitting 'backspace' after highlighting text!
***Also, please be aware (if you use it,) that XDA Labs app is flawed, and will often unexpectedly truncate your post when sending. This usually happens when you've copied and pasted info - you'll find '*' substituted for spaces in places, and the first one will be near the point the post is truncated. I always highlight and copy complete post before sending, and if I lose text I repost it from browser, which doesn't have these issues.
Click to expand...
Click to collapse
Sounds like @Hemphiz and others have all learned the hard way as I did, and take the same precautions.
Hope it helps in future, and bravo for your efforts and hard work for us! Regards, PW
:highfive: Hey AF just read the thread and I love and thanks for the kudos and well done.
I have installed your LOS 14.1 packages and must say it is stable very smooth and love your installer :highfive: I am using it right now and loving it
Also I did notice I minor thing and this for all user of this rom ,this is maybe not the ROM port fault but maybe the specific app bug or compatibility issue. I notice that the Greenify app does not do well with the default SU add-on of this ROM Greenify just does not load. Keeps crashing at getting su root access screen, but it does work with other root method so maybe something to look into.
Also I think you should edit the build.prop values for things like model number should be changed to 850F and not 850m and so fourth.
I have a build.prop file I can send you to look at.
Otherwise everything else is good
Excellent work AF
pndwal said:
Just read this new thread! Well done n many thanks.
As I explained in other thread (not sure if you understood properly - please read it carefully again to avoid heartache), XDA Labs does have a serious fault. Simply put, posts are shortened to a point where '*' symbol occurs, and because copying and pasting often swaps spaces (between words) for this symbol, the post gets truncated and your efforts are lost!
I said:
Sounds like @Hemphiz and others have all learned the hard way as I did, and take the same precautions.
Hope it helps in future, and bravo for your efforts and hard work for us! Regards, PW
Click to expand...
Click to collapse
Yeah. And I did take your advice, but instead of using my notebook, I used Labs again, except this time I posted every time a section was complete, fully copying all my text before hitting the post button. Thank you for the warnings and info. I will know in the future.
wezroot2k said:
:highfive: Hey AF just read the thread and I love and thanks for the kudos and well done.
I have installed your LOS 14.1 packages and must say it is stable very smooth and love your installer :highfive: I am using it right now and loving it
Also I did notice I minor thing and this for all user of this rom ,this is maybe not the ROM port fault but maybe the specific app bug or compatibility issue. I notice that the Greenify app does not do well with the default SU add-on of this ROM Greenify just does not load. Keeps crashing at getting su root access screen, but it does work with other root method so maybe something to look into.
Also I think you should edit the build.prop values for things like model number should be changed to 850F and not 850m and so fourth.
I have a build.prop file I can send you to look at.
Otherwise everything else is good
Excellent work AF
Click to expand...
Click to collapse
That's good to know on Greenify. Flashing a Magisk v18.1 systemless root installer zip via TWRP would likely fix the issue. I have noticed a similar problem using MiXplorer in root file manager mode. The problem like you said is likely the LOS 14.1 su_addon.
Glad you're loving it my friend. After working so hard to help make it possible, you are deserving indeed.
AeonFlux1603 said:
That's good to know on Greenify. Flashing a Magisk v18.1 systemless root installer zip via TWRP would likely fix the issue. I have noticed a similar problem using MiXplorer in root file manager mode. The problem like you said is likely the LOS 14.1 su_addon.
Glad you're loving it my friend. After working so hard to help make it possible, you are deserving indeed.
Click to expand...
Click to collapse
Not sure if you're using adoptive storage, or where MiXplorer (or Greenify) loads by default, but generally apps requiring root access lose functionality or won't load at all if installed on SD storage.
I use ES File explorer which installs to SD by default, but it must be moved to internal to enable its inbuilt root explorer, otherwise its root test fails and root explorer toggles off.
This just may be your problem too. - Pays to check SuperUser enabled apps in manager, and ensure each of these is on internal storage. PW.
---------- Post added at 09:49 AM ---------- Previous post was at 09:42 AM ----------
wezroot2k said:
Y would the app do that?
Maybe you would have to create the thread from a PC.
Click to expand...
Click to collapse
Yet the Labs app does this often . I've explained in my last post on page 1. PW
---------- Post added at 09:57 AM ---------- Previous post was at 09:49 AM ----------
wezroot2k said:
...I notice that the Greenify app does not do well with the default SU add-on of this ROM Greenify just does not load. Keeps crashing at getting su root access screen
Click to expand...
Click to collapse
My post to AF above re storage may help here, but could be SU used as you say. PW
pndwal said:
Not sure if you're using adoptive storage, or where MiXplorer (or Greenify) loads by default, but generally apps requiring root access lose functionality or won't load at all if installed on SD storage.
I use ES File explorer which installs to SD by default, but it must be moved to internal to enable its inbuilt root explorer, otherwise its root test fails and root explorer toggles off.
This just may be your problem too. - Pays to check SuperUser enabled apps in manager, and ensure each of these is on internal storage. PW.
---------- Post added at 09:49 AM ---------- Previous post was at 09:42 AM ----------
Yet the Labs app does this often . I've explained in my last post on page 1. PW
---------- Post added at 09:57 AM ---------- Previous post was at 09:49 AM ----------
My post to AF above re storage may help here, but could be SU used as you say. PW
Click to expand...
Click to collapse
I'm not running adoptive storage now. I had previously tried it to ensure operability. But, you actually just helped me troubleshoot a problem I was having on my LG G4 with root. It was due to adoptive storage. Haha. Man PW you know your Android for sure. Thanks.
So on our 850F I'm going to try Magisk or phh-superuser systemless root (or maybe SuperSU v2.82-SR5) to see if that fixes root access of the OS.
Also, I'll be posting the stock 6.0 firmware this evening sometime, with fastboot instructions. I was wrong about it being the most current build. It is actually one of the initial builds that shipped with the 850F in mid to late April, 2016. Hard to believe this device is nearly three years old now. So, once installed, the user will be prompted to install a series of OTA updates subsequent to initial boot and setup.
Hemphiz said:
App could've timed out. Similar to chrome. I copy/select all before confirming just incase (with pretty much every hefty message I write)
Click to expand...
Click to collapse
I've found even if it times out, or can't connect when sending, things are generally handled properly by Labs app, a message appears that 'send failed', and text is all still there allowing further attempts.
However, the space-substituted-for-*-symbol problem (when copying and pasting) will truncate the post and successful send in one operation. This means a large portion of text is often lost and irretrievable. (Also, the * symbol still shows as a space while editing, so one doesn't realise that the space has been substituted until its too late.)
Great advice to copy all before sending. PW
---------- Post added at 06:17 AM ---------- Previous post was at 05:22 AM ----------
@wezroot2k, @AeonFlux1603
TB3-850F users are privileged, blessed, ecstatic, proud, happy and very thankful to have two budding (though clearly possessed of valuable experience and practical knowledge) developers on board the Good Ship TB3-850F, and its been a long time coming!
Thank you both especially for Stable and Virtually Bug Free Port to LOS14.1 for TB3-850F, as well as for other valuable resources we are gaining - including this new thread for our brand new Lineage Operating System!
Your sincere expressions of thanks / praise for helpful posts are also much appreciated.
Just a small heads-up (and sorry to spell it out) - Please don't neglect the 'thanks' (thumb up) button when a post is useful, or a sincere attempt to help is made. This is kind of the expected / default expression of thanks around here, and is possibly the most sincere form of flattery as it also elevates a members XDA profile. It's a simple and immediate way to say 'thanks', and often makes further comment unnecessary. (Incidentally, thanked posts are indexed, and are often perused for helpful information.)
Many thanks, and loving your work! PW :good::good::good::good::good:
It looks like I have the Settings UI ironed out, with all mobile networks/SIM options removed in the Settings menu. I'm going to to repackage the Settings apk, implement it back into the /system directory and see if it works. If so I will update the OP with a new build.
Also, Magisk systemless root appears to be a fully stable root protocol on this LOS build. . Oddly, after flashing the Magisk v18.1 systemless root installer zip with TWRP, the Magisk Manager app doesn't appear upon reboot. But, once you manually install Magisk Manager v7.0.0 (185), root shows as properly installed and up to date. Thus far, I have noticed no instabilities or bugs with Magisk.
So, the recommended method of installing Magisk systemless root on this ROM is to first install the latest Magisk Manager v7.0.0 (185) apk, select Install from the app, and choose the direct install option. Reboot and Magisk v18.1 systemless root should be properly installed and stable. Go here to visit the official Magisk release and announcement thread https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 where you can download the latest Magisk Manager apk and systemless root installer zip. Be sure and thank @topjohnwu if you use Magisk.
Update on Settings UI. After repackaging the Settings apk and framework-res.apk, I am experiencing force closes every time Settings is opened. It is probably something as simple as an encoding issue or an error during repacking but I'll keep progress posted.
Update on the Settings UI. I now realize that my issues were due to my failure to properly encode my edits of the relevant .XML files with UTF-8 encoding prior to repackaging. As I may have mentioned previously, I am interested in bringing this port up to date with the latest upstream sources. So my next build release will hopefully include current LOS sources and have the Settings UI ironed out. While progress is not nearly as quick as I'd like, I am working on it.
I don't know about you guys as far as audio preferences, but I was really partial to the stock Dolby Atmos app that ships preinstalled on this device. I done a little testing to find a comparable audio setup. There is a Magisk Module titled Collective Dolby Atmos (ZTE Axon 7) v1.8 (2.2.1.7_r1), last updated on January 15, 2019, that works great on this ROM, with nearly exactly the same features and UI as the stock Lenovo version of Dolby Atmos. To install it, of course, you can simply download the Module and install it via Magisk Manager or via TWRP. There are several different Dolby ports available. This is the official support and release thread: https://forum.xda-developers.com/android/apps-games/soundmod-axon-7-dolby-atmos-t3412342
AeonFlux1603 said:
I don't know about you guys as far as audio preferences, but I was really partial to the stock Dolby Atmos app that ships preinstalled on this device. I done a little testing to find a comparable audio setup. There is a Magisk Module titled Collective Dolby Atmos (ZTE Axon 7) v1.8 (2.2.1.7_r1), last updated on January 15, 2019, that works great on this ROM, with nearly exactly the same features and UI as the stock Lenovo version of Dolby Atmos. To install it, of course, you can simply download the Module and install it via Magisk Manager or via TWRP. There are several different Dolby ports available. This is the official support and release thread: https://forum.xda-developers.com/android/apps-games/soundmod-axon-7-dolby-atmos-t3412342
Click to expand...
Click to collapse
Quite like ViPER4AndroidFX ( @ahrion, @Zackptg5) Magisk module. I think it auto-installs AML - Audio Modification Library - Magisk module (by @ahrion, @Zackptg5) also. (Used to anyway.)
AML currently supports all these mods too, so its a smörgåsbord:
- AM3D
- AudioWizard
- V4AFX
- V4AXhifi
- Dolby Atmos (ahrion's ports)
- Dolby Atmos Axon 7 Oreo (guitardedhero's port)
-Dolby Digital Plus
-Bang&Olufsen ICEPower (only tested ainur version)
- Arkamys (only tested ainur version)
- Dirac (only tested ainur version)
- Dirac Hexagon (only tested ainur version)
- JamesDSP
- MaxX Audio 3
- Audio Compatibility Patch (formerly universal deep_buffer remover)
- Ainur Sauron
- SquareSound
- DTS Wizard
- Sony Xperia Z2 Sound System
I see Dolby Atmos Axon 7 Oreo in this list too. Haven't tried it, but I know guitardedhero's a bit of a genius with these mods. PW.