Database Info

[ROM] Smartoonay V1.0 - Acer Iconia Smart as it should be !

Hello,
this ROM is designed for the Acer Iconia Smart. Acer's latest flagship Androphone.
All credits goes to Vache for making this great ROM !​
Here is the changelog from Vache :
Code:
T1
Based on Acer_S300_1.000.19_EMEA-GEN1
Rooted
Busybox, nano, bash...
Unsecure boot (adb remount)
semiTransparent notif
Transparent dock background
removed pagination bubble on the homescreens
Stock Lockscreen
Disable Debug USB icon
Smoother Launcher transitions
Disable camera sound
disable some useless Acer services
Removed many apps
Added TerminalEmulator
Updated all apps
SD speed tweak
Lowmemkiller tweak
Zipalign at boot for new apps
Using Google DNS
Removed craps on homescreen (widgets)
Added SpeechSynthetizer
Network tweaks
Ice Cream Sandwich bootanimation
Added compatibility swith in Settings app
Disable some animations
Disable bubble tooltip at first start
Added GoLauncher & LauncherPro (edited to fit the screen)
Added EStrong File Exploer and Task Manager
T2
Fix Phone.apk FC when calling
Fix /data mount during flash
...
T3
Fix WiFi error
AOSP Dialer
T4
Fix HotReboot when installing app that can be move to SD
ICS Market v3.2
T5
Fix typo in the update script
Back to stock Music (for notification widget)
Removed nemoPlayer
Updated SU binary and app
Updated Terminal Emulator
Updatd Youtube
ICS UI sounds
ICS Theme
T6
Removed GooglePlus 2.0 (make the contact FC when FB sync is active)
Fix Google Account disappear after some reboots
T7
Added TabooTools for Iconia Smart
Easy change Acer/Stock Contact/Lockscreen/Notifications
Updated SU binary
Fix TalkBack Keyboard FC
T8
Fix SU binary
Fix Acer Contact file name
T9
Modded hosts file for ads filter
Updated VoiceSearch
More ICS theme for framework and apps
T10
Fixed GPS and Batterie icons
Fixed ICS progress bar
Optimized automatic LCD backlight values
Added 1% batterie step in the framework
Added QuickSettings for stock notif
Fix notif switching from TabooTools
Even more ICS theme
T11
Fix Fast Dormancy
Custom kernel with OC/UV (up to 1.9Ghz)
Requirements :
- Acer Iconia Smart... obviously
- Acer drivers available HERE
- CWM recovery files for Iconia Smart. HERE
I) First Step
Update to latest Acer revision available HERE
WARNING this update will erase all your data
II) Install the custom Recovery
Plug your Iconia Smart to your PC.
Unpack the zip file containing the recovery.
Execute install_recovery.cmd and just follow the steps.
III) Preparing
Copy the ROM ( Smartoonay-1.0.zip) to your sdcard (this has to be an external sdcard, not the phone memory).
IV) Almost there
Switch off the phone and boot to recovery by pressing [vol+] + [focus] + [power]. Keep pressing the buttons until you're in the recovery (yellow text on black screen)
(You get "focus" by half pressing the camera button).
V) WIPE !
Once in the recovery choose "wipe data/factory reset" and validate (pressing camera button).
Also "wipe cache partition"
And then in "Advanced" choose "Wipe Dalvik Cache"
VI) Installing the ROM !
Go back to home menu of the recovery, choose "install zip from sd card" then "choose zip from sdcard". Find the file Smartoonay-1.0.zip (you just copied it on your sdcard) and validate to launch the installation.
Once done just reboot the phone and you're good to go !

You have just convinced me to buy this phone. I was torn between this and the Note, it's refreshing to see some Development on this.
Thankyou very much, your instructions are excellent BTW!

FYI, for me it worked once (after reset) and then went into a bootloop after installing this rom. Never got into fixing it as Vache did not respond anymore... you haven't had that issue?
Regards,
Nika.

Hi,
It bootloops on the bootanimation ? It can happen and usually it works if you remove the battery for 5min.
Can you describe where it stopped working and what you did just before it bootlooped ?

I haven't tried removing the batt, it just bootlooped after my first softreset in the morning. I did try several times, tried resetting all caches, and then reverted back to 1.000.19 eventually and gave up...
I may try again soon... too much work right now
Regards,
Nika.

Going to give it a go this evening.
Really excited to try it out.

So how did it go ?

In my case it keeps displaying the Acer / Android logo... it does not boot (just Android logo)...

Thank´s for me works well

Well...I have tried like 10 times, still nothing.
I started by installing cwm & making a backup (good step to add to your steps in the OP). Then I started install of smartoonay:
1. install 1.000.19
2. boot 1.000.19 once (& configure next, next, finish)
3. install new cwm
4. factory defaults from cwm
5. clear cache from cwm
6. clear dalvic cache from cwm
7. install smartoonay from cwm
Boot wail stop at the acer/android screen (with the 3 green androids).
I have tried fact/def from vol+/- and from cwm. I have tried clearing caches before and after smartoonay. I've downloaded smartoonay rom from vache several 3 times to make sure it's not a faulty rom... nothing...
Restored the backup: everything fine again...but still no smartoonay
Regards,
Nika.

Sorry to read that it doesn't work for you. Have you tried with the .24 official update? It did work for several people.
If it still doesn't work you might have to wait for a next release from vache that will take the smart to a new level ;-)

paugustin said:
Sorry to read that it doesn't work for you. Have you tried with the .24 official update? It did work for several people.
If it still doesn't work you might have to wait for a next release from vache that will take the smart to a new level ;-)
Click to expand...
Click to collapse
Downloading now:
http://global-download.acer.com/GDF... SMART (S300)&OS=a06&LC=nl&BC=Acer&SC=EMEA_18
Regards,
Nika.

Nope... for whatever reason it doesn't work for me.
1. Install .24 version (link see above)
2. Install cwm (4.0.0.8 version from S300-recovery.img 14/07/2011)
3. factory defaults from cwm
4. clear cache from cwm
5. clear dalvic cache from cwm
6. install smartoonay from cwm
Still only see my little Android friends

That's disapointing. Keep yourhopes up as Vache is working on a whole new ROM for the Iconia Smart. It's time consuming but it's going forward and it should be worth the wait
For the current ROM I think we tried everything (removing the battery and all) already and it might be an issue with you model.

paugustin said:
That's disapointing. Keep yourhopes up as Vache is working on a whole new ROM for the Iconia Smart. It's time consuming but it's going forward and it should be worth the wait
For the current ROM I think we tried everything (removing the battery and all) already and it might be an issue with you model.
Click to expand...
Click to collapse
I really hope he's able to give us something that'll work on all devices! I love Vache's work and was really disappointed when the only custom ROM we have didn't boot.

FloatingFatMan said:
I really hope he's able to give us something that'll work on all devices! I love Vache's work and was really disappointed when the only custom ROM we have didn't boot.
Click to expand...
Click to collapse
It doesn't work on yours either? Did you try it? Remember my device has a defect (touchscreen top is defective), so possibly it works on yours... (and I really did everything I can think of, including formatting system, etc., manually)...

My S300 also stuck in booting screen (Acer logo with 3 android idol) after flash the Smartoonay ROM...
I forgot backup my ROM before flashing it, does any one can help me how can flash back the official ROM without backup?

nikagl said:
It doesn't work on yours either? Did you try it? Remember my device has a defect (touchscreen top is defective), so possibly it works on yours... (and I really did everything I can think of, including formatting system, etc., manually)...
Click to expand...
Click to collapse
I actually had it before general release. Alas, my device just hangs until I take out the battery. Shame really, the root & cwm part worked great.

edmundtsang said:
My S300 also stuck in booting screen (Acer logo with 3 android idol) after flash the Smartoonay ROM...
I forgot backup my ROM before flashing it, does any one can help me how can flash back the official ROM without backup?
Click to expand...
Click to collapse
Hi edmund,
Just download the official ROM from somewhere (OS_Acer_1.000.24.EMEA.GEN1_A23G_S300), see above post. Or find yourself another ROM (I also used EUUs_Acer_S300_1.000.19_EMEA-GEN1_01.05.00 in the past, just google for it).
Connect your device with USB and install it using the setup.exe in the download.
In my case the installer crashed btw, because I have the android sdk installed which has a newer (incompatible) version of adb. Just make sure the PATH variable does not contain the ADB.EXE (use "for %I in (adb.exe) do echo %~dp$PATH:I" to figure that out).
Good luck!
Regards,
Nika.

Dear all,
I have been trying to get this ROM going but still no success.
I have compared the two boot images, and they are almost the same. It looks like it should be possible to run the Smartoonay rom with the stock boot image. That gives the highest success as well, because when I try to use the default Smartoonay rom it will get stuck at the first Android page (so it never shows the ICS boot animation). I also tried using the Smartoonay boot image with the stock ROM, but it then also gets stuck at the Android screen (see above image)
When I use the stock boot image, it finally displays the ICS boot animation, but it will get stuck in a bootloop. Usually caused by not clearing cache and such, but no solution in my case.
When I look at recovery.log, I do see one thing that I've never seen before:
Code:
Formatting /system...
[COLOR=Red][B]mtd: not erasing bad block at 0x08e00000[/B][/COLOR]
Done.
I wonder whether this one bad block may be the cause?
Anyone any other suggestions? Or maybe some instructions (a kitchen???) on how to make a new ROM like Smartoonay did? Any new Smartoonay ROMs to look forward to?
Regards,
Nika.
---------- Post added at 10:22 AM ---------- Previous post was at 10:16 AM ----------
FloatingFatMan said:
I actually had it before general release. Alas, my device just hangs until I take out the battery. Shame really, the root & cwm part worked great.
Click to expand...
Click to collapse
By the way... I fixed my screen by getting a new Touch Screen Digitizer for Acer S300 Iconia Smart Device is difficult to take apart (first take off top cover where the power button is in, which is a flat plastic, then take the screw out, then take the entire top cover off, remove two screws, open battery department cover, remove battery & screws, and then you can use a soft plastic pull tool to take the screen out...)

[ROM][2013.01.09] Lenovo A789,P700i,A660 custom ROM (ICS)

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.

[FIX] FED-Patcher v8 (ForceEncrypt Disable Patcher)

Hello everybody,
I created a tool - initially for the nexus 9 (flounder|flounder_lte) - that gets rid of the ForceEncrypt flag in a generic way (meaning it should work no matter what rom you are on). It does that by patching the currently installed boot.img.
I enhanced that tool to make it work for other devices too. (See the list below to see if your device is supported)
Disclaimer
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about the features in this tool
* before using it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
*/
Background
The Android CDD (Compatibility Definition Document) suggests demands that all devices with the appropriate horse power SHOULD MUST enable full disk-encryption (FDE) by default. Even though I support every step towards more security I have to criticize this approach. Full-disk-encryption comes at a price. Encryption takes time because some component has to de- and encrypt the stuff on the disk at some point and in current devices it's the CPU's task. Even though modern devices have quite fast CPU cores you can still easily feel the difference between FDE in the on- or off-state. The I/O is faster and boot-times take only half as long. (I did not do any scientific measurements though)
There is an ongoing discussion about this topic in cyanogenmod's gerrit for the nexus 9. Although it's a fun read it is pretty clear that this exchange of views is not going anywhere near a useful outcome. Additionally, Google's stock ROMs always have forced encryption enabled on newer devices.
Because performance is important to me and at least my tablet does not need the extra security I created the FED-Patcher (ForceEncrypt Disable Patcher).
How does it work?
FED-Patcher is a simple flashable ZIP that is supposed to be run in a recovery that has busybox integrated (like TWRP or CWM). This is what it does:
Checks if your device is compatible
Dumps the currently installed boot.img.
Unpacks the dump of your currently installed boot.img. The unpacking process is done via a self-compiled, statically linked version of unmkbootimg.
It patches the filesystem tables which include the force-encrypt flags. This process will change "forceencrypt" to "encryptable".
Then, if necessary, it patches the filesystem tables to not use dm-verity. This is done by removing the "verify" mount-parameter.
Creates a new boot.img. The unpacking process is done via a self-compiled, statically linked version of mkbootimg.
Flashes the modified boot.img
Supported devices
HTC Nexus 9 WiFi (flounder)
HTC Nexus 9 LTE (flounder_lte)
Motorola Nexus 6 (shamu)
LG Nexus 5X (bullhead)
Huawei Nexus 6P (angler)
Version History
v1 - Initial version with HTC Nexus 9 WiFi (flounder) support
v2 - Added Motorola Nexus 6 (shamu) support
v3 - Added support for HTC Nexus 9 LTE (flounder_lte)
v4 - Added support for signed boot-images
v5 - Changed error handling to compensate for missing fstab files. Some roms seem not to ship with the complete set of boot-files from AOSP.
v6 - FED-Patcher will enforce the same structure for the patched boot.img that the original boot.img had. Additionally, the kernel commandline will also be taken over. This should fix pretty much every case where devices would not boot after patching.
v7 - FED-Patcher will now disable dm-verity in fstab to get rid of the red error sign on marshmallow roms.
v8 - Added support for LG Nexus 5X (bullhead) and Huawei Nexus 6P (angler)
What do I need to make this work?
A supported device
An unlocked bootloader
An already installed ROM with forceencrypt flag. (like cyanogenmod CM12.1)
A recovery that includes busybox (TWRP, CWM)
How do I use it?
Make a thorough, conservative backup of your data if there is any on your device
Go into your recovery (TWRP, CWM)
Flash fed_patcher-signed.zip
If your device is already encrypted (You booted your ROM at least once) you need to do a full wipe to get rid of the encryption. This full wipe will clear all your data on your data-partition (where your apps as well as their settings are stored) as well as on your internal storage so please, do a backup before. If you don't do a backup and want to restore your data... well... Call obama.
How do I know if it worked?
Go into your "Settings"-App. In "Security", if it offers you to encrypt your device it is unencrypted. If it says something like "Device is encrypted" it indeed is encrypted.
IMPORTANT: If you update your ROM you have to run FED-Patcher again because ROM-updates also update the boot-partition which effectively removes my patch. So, if you are on CM12.1 for example and you used my patch and do an update to a newer nightly you have to run FED-Patcher again. If you don't do so Android will encrypt your device at the first boot.
Is it dangerous?
Well, I implemented tons of checks that prevent pretty much anything bad from happening. But, of course, we're dealing with the boot-partition here. Even though I tested FED-Patcher quite a lot there is still room for crap hitting the fan.
Screenshot
Scroll down to the attached thumbnails.
Credits
* pbatard for making (un)mkbootimg (dunno if he is on xda)
* @rovo89 for his xposed framework - I used some of his ideas by reading the source of his xposed installer flashable ZIP for FED-Patcher.
GibHub: https://github.com/gladiac1337/fed-patcher
XDA:DevDB Information
FED-Patcher, Tool/Utility for all devices (see above for details)
Contributors
gladiac, rovo89
Version Information
Status: Beta
Current Beta Version: v8
Beta Release Date: 2015-10-27
Created 2015-10-27
Last Updated 2016-10-23

Hi @gladiac and first of all thanks for the work and time spent developing this amazing tool.
I'm currently running stock Marshmallow on my Nexus 6 and i plan to stay like that, but would like to test my device with ForceEncrypt disabled. Here are my doubts.
1 - Does this work on stock?
2 - Would i be able to flash the monthly security update images without having to wipe my device every time?
3 - In your opinion, do the speed gains justify the all the work?
Thanks in advance.

cyberon said:
Hi @gladiac and first of all thanks for the work and time spent developing this amazing tool.
I'm currently on stock Marshmallow and i plan to stay like that, but would like to test my device with forcencrypt disabled. Here are my doubts.
1 - Does this work on stock?
2 - Would i be able to flash the monthly security update images without having to wipe my device every time?
3 - In your opinion, do the speed gains justify the all the work?
Thanks in advance.
Click to expand...
Click to collapse
Hi @cyberon,
good questions!
Yes, FED-Patcher works on stock! Marshmallow made it necessary to do a new release, v7, to get rid of an error message at boot but other than that, FED-Patcher works just fine on Android 6.
Well, I don't know how the monthly security-updates will be deployed. I guess it will be done by OTA (Over the Air) updates. OTA will probably not work after modifying the boot-image. However, flashing factory images should work just fine. Additionally, most of the time, OTA-zips are being posted here on xda or androidpolice whenever they become available so doing manual OTA updates is another possibility to do updates.
To get back to your question - wiping should not be necessary after an upgrade - be it via OTA or factory images. Google did a fantastic job with the upgrade-functionality in newer Android versions. However, whenever you do an update, be sure to run FED-Patcher afterwards because, in case the boot-partitions got updated, forced encryption will be in place again and on the first boot it will encrypt you device.
Well, I do all my tests on a HTC Nexus 9 (flounder). It is a pretty fast beast. However, on an unmodified stock rom, it was clearly tangible that the GUI had more latency than necessary. Apps loaded pretty slowly - compared to my Sony Xperia Z1 (honami) it took like twice as long to start youtube - and in general it just did not behave like a beast. This was why I started writing FED-Patcher. In my opinion it was worth my time. (it wasn't that much actually)
I hope I could help.
Enjoy, gladiac

Thanks for the quick and detailed answer @gladiac, now regarding point number 2.
I never wait for the OTA, but always flash the images manually.
As far as i understand from your answer, it would it be ok to flash all the img files manually, then flash TWRP and finally flash FED without booting the OS.
Am i missing something?

cyberon said:
Thanks for the quick and detailed answer @gladiac, now regarding point number 2.
I never wait for the OTA, but always flash the images manually.
As far as i understand from your answer, it would it be ok to flash all the img files manually, then flash TWRP and finally flash FED without booting the OS.
Click to expand...
Click to collapse
That's pretty much how I would do it. You don't even have to flash TWRP if you just skip flashing the recovery.img which is included in the factory-image package.

Thanks @gladiac, will try that way.
PS: I have a feeling that if we had this option added to a toolkit like Wugfresh Nexus Root Toolkit, it would be an instant success.

hi @gladiac
first of all thanks for your patch
I'm on Nexus 6 with stock Marshmallow and all I want to do is disable encryption and enable root.
Is your patch + SuperSU enough or I need something else?
Thanks a lot

Worked on my N9 - thanks!

provolinoo said:
hi @gladiac
first of all thanks for your patch
I'm on Nexus 6 with stock Marshmallow and all I want to do is disable encryption and enable root.
Is your patch + SuperSU enough or I need something else?
Thanks a lot
Click to expand...
Click to collapse
Hi @provolinoo,
well, FED Patcher will disable the forced encryption for you. However, SuperSU will not work so easily. The reason for that is that the stock ROM has SeLinux enabled in "enforcing" mode. SuperSU does not work without adding more SeLinux Policies to the stock ROM. Unfortunately, it's not in the scope of FED Patcher to add SeLinux policies for SuperSU. This should be done inside the flashable ZIP of SuperSU instead.
The last time I tested SuperSU with marshmallow stock was with version 2.52 BETA. It did not work. The result was a boot-loop because of one or more SeLinux denials. A little more info on that matter is here.
So, to get SuperSU working you would have to set SeLinux to "permissive" mode. Alternatively, you can use @Chainfire's boot.imgs to make SuperSU work.
Have fun, gladiac

Thank you gladiac. Your FED patcher (v8) works flawlessly on my Nexus 9. Edit: I am using TWRP 2.8.7.1
The gerrit conversation you linked is interesting. I am grateful that someone with your skills decided to support our ability to choose whether or not to encrypt. CM thinks I am smart enough for root priveleges but I am too stupid to be trusted with decryption?
Don't some major vendors allow the disabling of encryption from within Android?
Anyway, thanks for the patcher.

dmantilal said:
Thank you gladiac. Your FED patcher (v8) works flawlessly on my Nexus 9.
The gerrit conversation you linked is interesting. I am grateful that someone with your skills decided to support our ability to choose whether or not to encrypt. CM thinks I am smart enough for root priveleges but I am too stupid to be trusted with decryption?
Don't some major vendors allow the disabling of encryption from within Android?
Anyway, thanks for the patcher.
Click to expand...
Click to collapse
I agree, I love CM roms but their decision to force encryption when most of cm users are power-user is a nonsense

Sooo....basically, I cannot use a stock Marshmallow that is FEDpatched and with root (using SuperSU, unless there is alternative)? If I want those, I have to get one of the custom ROMs?
EDIT: also, I tried using Chainfire's modified boot. It is stated that it will disable the forceencrypt. It didn't work in mine, still encrypted.

jamesalfred said:
Sooo....basically, I cannot use a stock Marshmallow that is FEDpatched and with root (using SuperSU, unless there is alternative)? If I want those, I have to get one of the custom ROMs?
EDIT: also, I tried using Chainfire's modified boot. It is stated that it will disable the forceencrypt. It didn't work in mine, still encrypted.
Click to expand...
Click to collapse
Did you follow the directions and format the entire "data" partition?

dmantilal said:
Did you follow the directions and format the entire "data" partition?
Click to expand...
Click to collapse
I too have the same problem didnt work for me.
im on the the new 6.0 L build but went ahead and flashed the modified boot image for K build just so I could flash the TWRP img.
Once TWRP was installed, I installed the Fed path ZIP and that went well supposedly. and then after that I did a factory reset, then I WIPED the DATA, CACHE and Dalvik.. I rebooted setup my device and it still shows encrypted.

nextelbuddy said:
I too have the same problem didnt work for me.
im on the the new 6.0 L build but went ahead and flashed the modified boot image for K build just so I could flash the TWRP img.
Once TWRP was installed, I installed the Fed path ZIP and that went well supposedly. and then after that I did a factory reset, then I WIPED the DATA, CACHE and Dalvik.. I rebooted setup my device and it still shows encrypted.
Click to expand...
Click to collapse
It did not work because you did not follow the directions.
Flash TWRP. Flash FED. Full wipe (or format, depending on your choice of terminology). OP goes on to clarify by saying "This full wipe will clear all your data on your data-partition (where your apps as well as their settings are stored) as well as on your internal storage so please, do a backup before.", meaning if you did not lose everything on data, which includes "/sdcard", you most likely did it wrong.
Give us more info so we can help (assuming you fid it right initially).
P.S. - 6.0 is M(arshmallow), not L(ollipop).

dmantilal said:
Did you follow the directions and format the entire "data" partition?
Click to expand...
Click to collapse
dmantilal said:
It did not work because you did not follow the directions.
Flash TWRP. Flash FED. Full wipe (or format, depending on your choice of terminology). OP goes on to clarify by saying "This full wipe will clear all your data on your data-partition (where your apps as well as their settings are stored) as well as on your internal storage so please, do a backup before.", meaning if you did not lose everything on data, which includes "/sdcard", you most likely did it wrong.
Give us more info so we can help (assuming you fid it right initially).
P.S. - 6.0 is M(arshmallow), not L(ollipop).
Click to expand...
Click to collapse
i solved my issue. i was wiping DATA but not choosing internal storage. i did that and rebooted and now it says ENCRYPT not ENCRYPTED
THANKS!
so currently I have a modified boot image from the K build, TWRP and now a modifier boot.img kernel for no force encrypt BUT I am not rooted and dont plan on it. does this mean I can still get OTAs?> i would guess not since my boot image has been modified and i am unlocked? would i even want an OTA? wouldnt that just give me a stock boot.img again causing me to get encrypted on the next boot after OTA?

nextelbuddy said:
i solved my issue. i was wiping DATA but not choosing internal storage. i did that and rebooted and now it says ENCRYPT not ENCRYPTED
THANKS!
so currently I have a modified boot image from the K build, TWRP and now a modifier boot.img kernel for no force encrypt BUT I am not rooted and dont plan on it. does this mean I can still get OTAs?> i would guess not since my boot image has been modified and i am unlocked? would i even want an OTA? wouldnt that just give me a stock boot.img again causing me to get encrypted on the next boot after OTA?
Click to expand...
Click to collapse
Side-loading the OTA then following that with a FED flash seems much safer.
Loading an OTA directly would over-write the boot.img with a ForceEncrypt boot.img, logically Forcing Encryption (derp) at boot.

I am using chroma ROM which doesn't force encryption and my device is still encrypted. Can I still use this?

jamespat93 said:
I am using chroma ROM which doesn't force encryption and my device is still encrypted. Can I still use this?
Click to expand...
Click to collapse
You can if you want But if you want to unencrypt your phone, backup your ROM, copy sd content to your computer, wipe everything! in recovery (twrp) including Format Data, Factory reset, internal storage etc. Connect your phone while in recovery to your computer (you'll see 25.98GB instead of 23.03GB), copy sd content back to your phone, restore your rom backup and you'll be fine.

I can't get it work on Nexus 6 and chroma rom r26.
My steps: wipe everything, push folder (rom,patcher and gapps), flash chroma, flash gapps, flash patcher, wipe everything but system
after boot in setting/security it is again encrypted. what I am doing wrong?

[ROM][7.1.2][UNOFFICIAL][PORT] Resurrection Remix 5.8.5 for Lenovo A7600-F [MT6582]

Hello A7600-F Tablet owners, It's been awhile since there has been an updated ROM for this tablet. I have released ported ROMs for this tablet before, however they all had some annoying bugs and many of you reported issues with corrupted SD card partitions. The goal of this ROM is to provide as close to daily driver material for this old tablet as possible.
What better ROM than Resurrection Remix to do the job! :good:
Instructions:
Follow carefully! This process involves going back to STOCK firmware FIRST! This is to ensure your Internal storage gets properly formatted.
SAVE YOUR PERSONAL DATA! (Some where other than your tablet) You will lose it when flashing stock firmware. Don't worry about the struggles of getting ROOT on stock firmware, I have expedited the process greatly.
STEP 1: Get back to stock firmware. THIS STEP ERASES EVERYTHING, so save your data!!! Don't skip this step.
- Get any stock firmware file from here and follow the tutorial also in this link!
- The SP-Flash tool and drivers are all conveniently included with the firmware download.​- Don't worry about taking the battery out when the tutorial says to.​- If you have issues with the driver provided in the download, try these. (Run dpinst.exe)​ - Once completed boot into the new firmware just to ensure that you were successful. (Don't worry about going through initial setup we don't need it)
STEP 2: Install TWRP without root. You should now have a stock A7600-F Tablet, lets put TWRP back on.
- We will install TWRP with the same SP-Flash tool so that root is not required.
- Download the SP-Flashable TWRP image and scatter file from here.
- Follow the instructions in the tutorial linked in step 1 again but use the extracted TWRP scatter file you just downloaded instead of the stock firmware scatter file.
- You should only see "RECOVERY" listed in SP Flash Tool instead of all the stock partitions like last time​ - Once complete unplug the USB and use Vol-UP and Power buttons to get into TWRP
STEP 3: Wiping Instructions. THIS IS IMPORTANT! You should have TWRP installed and running at this point.
- DO NOT WIPE INTERNAL STORAGE! Doing so will cause the Corrupt SD-Card errors!
- Just don't do it! There is never any need to wipe internal storage on most devices.
- Go to Wipe -> Advanced Wipe
- Select only: Dalvik/Art Cache, System, Cache, and Data
- Wipe it.
STEP 4: Installing RR 7.1.2. You should now have an A7600-F with the stock partitions restored, and no ROM installed, sitting in the TWRP main menu.
- ROM Download: here
- GAPPS Download: here (Select Arm, 7.1, and whatever size you want)
- Now simply flash the ROM ZIP followed by the Gapps ZIP.
Reboot and Enjoy!
Things I improved over previous ROM PORTS:
- Better Audio quality
- Smoother Substratum OMS Support
- Camera Fixes
- FM Radio (Headphones only)
Kernel Source: here

Just yesterday I've dusted off this tablet, and so I was browsing the forums to see what rom I can put inside, and lickily, about the same time this thread was created! Installing it right now, gonna post a follow-up once I'm finished tinkering with it.

OK, firstly wanna thank you for this awesome rom, it's stable and fast, no major issue with it. What I did find, however, is that the camera flash is not working along with the night mode which is not turning on. Besides those two issues, everything seems to be in working order
Cheers!

LukaHM said:
OK, firstly wanna thank you for this awesome rom, it's stable and fast, no major issue with it. What I did find, however, is that the camera flash is not working along with the night mode which is not turning on. Besides those two issues, everything seems to be in working order
Cheers!
Click to expand...
Click to collapse
Thanks for the report.
Camera flash? My A7600 Does not have a flash. No actual LED to produce a flash.
As for the Night mode, I have ported a lot of ROMS to this device and I havn't ever seen the night mode work right. If I even do get it to turn on, it lags the whole device.

SaberShip said:
Thanks for the report.
Camera flash? My A7600 Does not have a flash. No actual LED to produce a flash.
As for the Night mode, I have ported a lot of ROMS to this device and I havn't ever seen the night mode work right. If I even do get it to turn on, it lags the whole device.
Click to expand...
Click to collapse
Haha, I've turned the damn thing over, looked at the sensor, and you're right. Havent actually used this device previously to know about it, so glad we have that one sorted out!

Thanks SaberShip. The ROM works great for general use and apps but I'm having an issue downloading files. It says SD card not found Download to default folder. I attempt to download to Downloads folder where it says I have 10.43gb stroage available but it keeps telling me SD card not found. I don't use an SD card for storage on the device. Do I need to use one or can you offer any other advice? I've carefully gone through above installation steps 3 times.
---------- Post added 08-02-2019 at 12:38 AM ---------- Previous post was 07-02-2019 at 11:57 PM ----------
caoiveen said:
Thanks SaberShip. The ROM works great for general use and apps but I'm having an issue downloading files. It says SD card not found Download to default folder. I attempt to download to Downloads folder where it says I have 10.43gb stroage available but it keeps telling me SD card not found. I don't use an SD card for storage on the device. Do I need to use one or can you offer any other advice? I've carefully gone through above installation steps 3 times.
Click to expand...
Click to collapse
So I put in an sd card and I then had option to save to downloads or sd. I still could not select downloads but I could select sd card which is worrying for me now. Thanks again Sabership. Nice work

caoiveen said:
Thanks SaberShip. The ROM works great for general use and apps but I'm having an issue downloading files. It says SD card not found Download to default folder. I attempt to download to Downloads folder where it says I have 10.43gb stroage available but it keeps telling me SD card not found. I don't use an SD card for storage on the device. Do I need to use one or can you offer any other advice? I've carefully gone through above installation steps 3 times.
---------- Post added 08-02-2019 at 12:38 AM ---------- Previous post was 07-02-2019 at 11:57 PM ----------
So I put in an sd card and I then had option to save to downloads or sd. I still could not select downloads but I could select sd card which is worrying for me now. Thanks again Sabership. Nice work
Click to expand...
Click to collapse
What app are you using? I have not seen any issues with downloading yet. If you see 10.43Gb it sounds like your internal storage is formatted correctly. I haven't seen any download issues with Firefox and ES-File Explorer.

Unable to flash firmware - because unable to install Android USB driver on Windows 10
Thank you for the new firmware. However, the instructions to install the Android USB driver in smartphone flash tool (link below) the link below does not work.. There is a signature error and everyone (as per youtube video comments) is having same problem.
https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
Pls advise.

D2sx34 said:
Thank you for the new firmware. However, the instructions to install the Android USB driver in smartphone flash tool (link below) the link below does not work.. There is a signature error and everyone (as per youtube video comments) is having same problem.
https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
Pls advise.
Click to expand...
Click to collapse
Main post updated with signed drivers. Please try it now.

Thank you @SaberShip!
The installation of Resurrection Remix 5.8.5 was successful after installing the signed Android USB driver!. System is stable and fast. Thank you again.
App issues:
1. Netflix app (not available on playstore, but at netflix web site) works online, but does not allow video downloads.
Netflix diagnostic error for download is OF.NA.4 -which probably means device does not meet security requirements. ? any workarounds?
// Amazon Prime video works, with offline video downloads as well. Google chrome works. Tried other apps as well.
Documentation issues (minor):
1. "- GAPPS Download: here (Select Arm, 7.1, and whatever size you want)" --> Google Apps Super package did not install since the device ran out of space (error 70). Google Apps "Nano" worked.
System issues:
1. Wifi still does not auto-reconnect after Wireless Access Point is rebooted, but given that this has happened with different ROMs I am concluding it is due to a hardware issue with this device (and not ROM specific).
// Skype camera issue fixed. Camera image is NO longer upside down.
D2sx34 said:
Thank you for the new firmware. However, the instructions to install the Android USB driver in smartphone flash tool (link below) the link below does not work.. There is a signature error and everyone (as per youtube video comments) is having same problem.
https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
Pls advise.
Click to expand...
Click to collapse

Netflix app not working on ROM due to Widevine DRM
Great job on the ROM!! - it is fast and stable.
I have been investigating why the <latest> Netflix app with offline download capability does not work with Resurrection Remix 5.85 ROM.
I found that some other ROM has similar problem, and it was caused because Widevine DRM was not supported. Netfix (latest app and offline download) started working after Widevine DRM support was added to that ROM.
Is it possible to support Widevine DRM in this ROM?
Here is the quote from another ROM:
"Quote:
Originally Posted by Federek
I recently found out the reason why after opening the Netflix app it shows the error "this app is not compatible with your device". The only workaround right now is to download an old APK directly from Netflix website (it doesn't support the feature of downloading movies). After some digging, I'm pretty sure the error is due to the fact that on, I think any Oreo rom available for bacon, Widevine Drm is not supported (as u can see in the screenshot below). I think it's connected to the files in the screenshot below, but I didn't manage to find a solution. I believe it must be implemented by someone directly in the rom code (I'm absolutely not an expert). I'm also sure it's not connected with root or anything else (the Netflix app is available in the play store for me).
(sorry is my first post)
[/IMG]"
SaberShip said:
Hello A7600-F Tablet owners, It's been awhile since there has been an updated ROM for this tablet. I have released ported ROMs for this tablet before, however they all had some annoying bugs and many of you reported issues with corrupted SD card partitions. The goal of this ROM is to provide as close to daily driver material for this old tablet as possible.
What better ROM than Resurrection Remix to do the job! :good:
Instructions:
Follow carefully! This process involves going back to STOCK firmware FIRST! This is to ensure your Internal storage gets properly formatted.
SAVE YOUR PERSONAL DATA! (Some where other than your tablet) You will lose it when flashing stock firmware. Don't worry about the struggles of getting ROOT on stock firmware, I have expedited the process greatly.
STEP 1: Get back to stock firmware. THIS STEP ERASES EVERYTHING, so save your data!!! Don't skip this step.
- Get any stock firmware file from here and follow the tutorial also in this link!
- The SP-Flash tool and drivers are all conveniently included with the firmware download.
- Don't worry about taking the battery out when the tutorial says to.
- If you have issues with the driver provided in the download, try these. (Run dpinst.exe)​ - Once completed boot into the new firmware just to ensure that you were successful. (Don't worry about going through initial setup we don't need it)
STEP 2: Install TWRP without root. You should now have a stock A7600-F Tablet, lets put TWRP back on.
- We will install TWRP with the same SP-Flash tool so that root is not required.
- Download the SP-Flashable TWRP image and scatter file from here.
- Follow the instructions in the tutorial linked in step 1 again but use the extracted TWRP scatter file you just downloaded instead of the stock firmware scatter file.
- You should only see "RECOVERY" listed in SP Flash Tool instead of all the stock partitions like last time​ - Once complete unplug the USB and use Vol-UP and Power buttons to get into TWRP
STEP 3: Wiping Instructions. THIS IS IMPORTANT! You should have TWRP installed and running at this point.
- DO NOT WIPE INTERNAL STORAGE! Doing so will cause the Corrupt SD-Card errors!
- Just don't do it! There is never any need to wipe internal storage on most devices.
- Go to Wipe -> Advanced Wipe
- Select only: Dalvik/Art Cache, System, Cache, and Data
- Wipe it.
STEP 4: Installing RR 7.1.2. You should now have an A7600-F with the stock partitions restored, and no ROM installed, sitting in the TWRP main menu.
- ROM Download: here
- GAPPS Download: here (Select Arm, 7.1, and whatever size you want)
- Now simply flash the ROM ZIP followed by the Gapps ZIP.
Reboot and Enjoy!
Things I improved over previous ROM PORTS:
- Better Audio quality
- Smoother Substratum OMS Support
- Camera Fixes
- FM Radio (Headphones only)
Click to expand...
Click to collapse

SaberShip, thank you for all your work and caring about the A7600-F! Your instructions are clean and elegant. It's great to be able to install your ROM without root. It looks and performs great.
I installed your ROM a week ago. Unfortunately, I've spent much time since then trying to get NordVPN to work. It worked fine on the stock version of my tablet. Now, it connects to NordVPN servers, but fails to adopt the remote IP address (whatismyv6.com reports my ISP IP).
I've exhausted [email protected] I'd be grateful for any pointers you might have.

Hello,
so i will thank Sabership, too, for his new build. I went the way as most builds are normally flashed - reboot from AIM build into TWRP, did a factory reset, and flashed RR and a new GApps build. Everything went fine, i am just typing on it. The bug with WiFi not connecting automatically i am hoping will be gone, it was the only bug i found in AIM for me.
One question: the security patch date is of November 2017. Will there be an update (as asked in AIM, too)?
Regards

jfaheyfan said:
SaberShip, thank you for all your work and caring about the A7600-F! Your instructions are clean and elegant. It's great to be able to install your ROM without root. It looks and performs great.
I installed your ROM a week ago. Unfortunately, I've spent much time since then trying to get NordVPN to work. It worked fine on the stock version of my tablet. Now, it connects to NordVPN servers, but fails to adopt the remote IP address (whatismyv6.com reports my ISP IP).
I've exhausted [email protected]. I'd be grateful for any pointers you might have.
Click to expand...
Click to collapse
I believe VPN connectivity may have been one of the issues with the original ROM even before I ported it to the A7600F. Therefore, there isn't much I can do unfortunately.
If you absolutely need VPN, your options are to use Stock ROM or find a different ROM that has VPN working. Another possible workaround is to setup NordVPN on your router or whatever gateway is between you and the internet: https://support.nordvpn.com/Connectivity/Router/1047409322/Setting-up-a-router-with-NordVPN.htm
Catfish78 said:
Hello,
so i will thank Sabership, too, for his new build. I went the way as most builds are normally flashed - reboot from AIM build into TWRP, did a factory reset, and flashed RR and a new GApps build. Everything went fine, i am just typing on it. The bug with WiFi not connecting automatically i am hoping will be gone, it was the only bug i found in AIM for me.
One question: the security patch date is of November 2017. Will there be an update (as asked in AIM, too)?
Regards
Click to expand...
Click to collapse
I have witnessed wifi disconnection issues on every ROM I've ever ported/used for this device aside from Stock I wish there was more that I could do. As mentioned in the title and before, this ROM is ported from another device. What this means is that I don't have the source code and therefore cannot update things like Android security patch dates. If this were a ROM built from source, I would simply have to sync with updated RR sources to get the new patches and RR bugfixes/features. To do it with a port, I need to find a whole new ROM with the updated sources and then port the whole ROM over to this device again. That is just too much work.
As a side note, I had intended this to be the last ROM I ported for this device due to its age, however If there is enough demand and I can find one, maybe someday I will port a more updated Oreo ROM to this device. Good quality MT6582 Oreo ROMs built from source are still not really common.

SaberShip said:
I believe VPN connectivity may have been one of the issues with the original ROM even before I ported it to the A7600F. Therefore, there isn't much I can do unfortunately.
If you absolutely need VPN, your options are to use Stock ROM or find a different ROM that has VPN working. Another possible workaround is to setup NordVPN on your router or whatever gateway is between you and the internet: https://support.nordvpn.com/Connectivity/Router/1047409322/Setting-up-a-router-with-NordVPN.htm
I have witnessed wifi disconnection issues on every ROM I've ever ported/used for this device aside from Stock I wish there was more that I could do. As mentioned in the title and before, this ROM is ported from another device. What this means is that I don't have the source code and therefore cannot update things like Android security patch dates. If this were a ROM built from source, I would simply have to sync with updated RR sources to get the new patches and RR bugfixes/features. To do it with a port, I need to find a whole new ROM with the updated sources and then port the whole ROM over to this device again. That is just too much work.
As a side note, I had intended this to be the last ROM I ported for this device due to its age, however If there is enough demand and I can find one, maybe someday I will port a more updated Oreo ROM to this device. Good quality MT6582 Oreo ROMs built from source are still not really common.
Click to expand...
Click to collapse
Thanks for your answer. If only i could do something like that of my own... i have so much interests, i don't know if i could learn that in a usefull time!
By the way, why did you call it "old"? i'm using the Galaxy S2 build 2011, with LineageOS 16. I think this is an old device , like my Galaxy Tab 1 and 2.
But anyway, thanks for your work. After some time i'll write again about issues i found, if it will be helpful.
Regards

Thank you, SaberShip. It's been on my list to get a DD-WRT enabled router, so maybe now's the time.
I've had no problems with WiFi.
If you build an updated Oreo ROM, I volunteer to test it. I'm fond of my A7600-F.

SaberShip said:
Hello A7600-F Tablet owners, It's been awhile since there has been an updated ROM for this tablet. I have released ported ROMs for this tablet before, however they all had some annoying bugs and many of you reported issues with corrupted SD card partitions. The goal of this ROM is to provide as close to daily driver material for this old tablet as possible.
What better ROM than Resurrection Remix to do the job! :good:
Instructions:
Follow carefully! This process involves going back to STOCK firmware FIRST! This is to ensure your Internal storage gets properly formatted.
SAVE YOUR PERSONAL DATA! (Some where other than your tablet) You will lose it when flashing stock firmware. Don't worry about the struggles of getting ROOT on stock firmware, I have expedited the process greatly.
STEP 1: Get back to stock firmware. THIS STEP ERASES EVERYTHING, so save your data!!! Don't skip this step.
- Get any stock firmware file from here and follow the tutorial also in this link!
- The SP-Flash tool and drivers are all conveniently included with the firmware download.
- Don't worry about taking the battery out when the tutorial says to.
- If you have issues with the driver provided in the download, try these. (Run dpinst.exe)
- Once completed boot into the new firmware just to ensure that you were successful. (Don't worry about going through initial setup we don't need it)
STEP 2: Install TWRP without root. You should now have a stock A7600-F Tablet, lets put TWRP back on.
- We will install TWRP with the same SP-Flash tool so that root is not required.
- Download the SP-Flashable TWRP image and scatter file from here.
- Follow the instructions in the tutorial linked in step 1 again but use the extracted TWRP scatter file you just downloaded instead of the stock firmware scatter file.
- You should only see "RECOVERY" listed in SP Flash Tool instead of all the stock partitions like last time
- Once complete unplug the USB and use Vol-UP and Power buttons to get into TWRP
STEP 3: Wiping Instructions. THIS IS IMPORTANT! You should have TWRP installed and running at this point.
- DO NOT WIPE INTERNAL STORAGE! Doing so will cause the Corrupt SD-Card errors!
- Just don't do it! There is never any need to wipe internal storage on most devices.
- Go to Wipe -> Advanced Wipe
- Select only: Dalvik/Art Cache, System, Cache, and Data
- Wipe it.
STEP 4: Installing RR 7.1.2. You should now have an A7600-F with the stock partitions restored, and no ROM installed, sitting in the TWRP main menu.
- ROM Download: here
- GAPPS Download: here (Select Arm, 7.1, and whatever size you want)
- Now simply flash the ROM ZIP followed by the Gapps ZIP.
Reboot and Enjoy!
Things I improved over previous ROM PORTS:
- Better Audio quality
- Smoother Substratum OMS Support
- Camera Fixes
- FM Radio (Headphones only)
Click to expand...
Click to collapse
Does usb otg work?

thierry_w said:
Does usb otg work?
Click to expand...
Click to collapse
Just tested, It works perfectly with my USB wireless Keyboard and mouse combo.
When I tried a USB flash drive it did not mount automatically, however "SDA" does appear in the /dev/block/ directory so you can likely mount the flash storage manually with some terminal commands. YMMV

USB OTG works with both my wired and wireless trackballs (Logitech).
I mount/unmount flash drives with StickMount and explore them with Total Commander.

excellent. Works very well

[Treble GSI] [Umidigi One Max] GSI Experiments

Now that the Umidigi One Max has TWRP, it is now very easy to flash GSI ROMs.
I will try to keep track of different GSI that works (or not !) here, alongside with bugs. Testers are welcome !
I highly recommend GSI based off phhhuson's work, as he did great job to fix MTK issues. Some other GSI may work better. We definitely need testing !
10
Apparently it works as shown here: https://forum.xda-developers.com/showpost.php?p=80319007&postcount=13 credits to @4ctiv_
9.0 Pie
phhusson's AOSP :
Everything works as expected. Notification bar is of the wrong size, may need to create a patch for it. Tethering doesn't work with data ON !
Camera is good ! All cameras are recognized. Fingerprint sensor OK. Torch not working under 15% like in stock, this seems like a hardware thing.
Ongoing calls and SMS will not work first boot. Just reboot and it'll work.
Magisk 19+ doesn't show root prompts. Fix here
Pixel Launcher crashes, but it seems that it's the only google app that doesn't work. Google Phone works.
NFC doesn't appear at all. There is a fix with magisk tho ! See here (NFC4PRA)
ctsProfile doesn't pass. Using MagiskHidePropsConfig fixes the issue, but choosing "vendor fingerprint" bootloops​
Testers needed
8.1 Oreo
Testers needed
Do not hesitate to post what you find or your testing.
NOTE : Installing a GSI can be done via 3 methods : TWRP Image Flash, SP Flash Tool, or fastboot (needs unlocked bootloader)
For the first two methods, unlocked bootloader is not required ! TWRP can be flashed via SPFT aswell.
Enjoy your beautiful and modded phone

Make sure to check out my guide on installing GSIs at https://forum.xda-developers.com/android/development/umidigi-one-max-custom-rom-modding-t3942521/

I downloaded system-arm64-ab-gapps-su.xz, extracted the file, booted into TWRP, did a full wipe, and installed "image" system-arm64-ab-gapps-su.img. TWRP asks which partition to install it to. I selected "system". However, after install I go to reboot, and TWRP complains there is no OS. Am I missing something?
I did a complete backup in TWRP of all important partitions first (nvram, modem, system Etc.), so going back to my stock setup was not difficult. Those trying this, backup all important partitions from TWRP on to microsd!

For everyone, make sure you download AONLY images, not AB !

_cab13_ said:
Now that the Umidigi One Max has TWRP, it is now very easy to flash GSI ROMs.
I will try to keep track of different GSI that works (or not !) here, alongside with bugs. Testers are welcome !
I highly recommend GSI based off phhhuson's work, as he did great job to fix MTK issues. Some other GSI may work better. We definitely need testing !
10 Q Beta
Beta 4 : Probably not working, as our device is not system-as-root (but is VNDK isolation compatible)
Still needs testing
9.0 Pie
phhusson's AOSP :
Everything works as expected. Notification bar is of the wrong size, may need to create a patch for it. Wifi access point doesn't work.
Camera is good ! All cameras are recognized. Fingerprint sensor OK. Torch not working under 15% like in stock, this seems like a hardware thing.
Ongoing calls and SMS will not work first boot. Just reboot and it'll work.
Magisk 19+ doesn't show root prompts. Fix here
Pixel Launcher crashes, but it seems that it's the only google app that doesn't work. Google Phone works.
ctsProfile doesn't pass. Using MagiskHidePropsConfig fixes the issue, but choosing "vendor fingerprint" bootloops​
Testers needed
8.1 Oreo
Testers needed
Do not hesitate to post what you find or your testing.
NOTE : Installing a GSI can be done via 3 methods : TWRP Image Flash, SP Flash Tool, or fastboot (needs unlocked bootloader)
For the first two methods, unlocked bootloader is not required ! TWRP can be flashed via SPFT aswell.
Enjoy your beautiful and modded phone
Click to expand...
Click to collapse
I posted this in another forum, but for the life of me I do not know what is causing this issue. I installed RR rom located here:
https://get.resurrectionremix.com/?dir=gsi/
system-190120-arm64-aonly-vanilla-nosu.img
I also install, Gapps (pico), and Magisk.
It runs great, for the most part. However, if I start streaming a video from any app or start streaming music, after a short amount of time my Umidigi One Max:
A.) Announces, "Powering Down"
B.) Boots directly into TWRP
C.) If I reboot, it again boots directly into recovery. Almost as if the partition became corrupted.
D.) Try to recover a backup I made in twrp, reboot, again boots straight into recovery.
E.) If SP Flash can communicate with the phone, I can usually push all the stock images back to the phone. If not, I have to push the images via fastboot with my Ubuntu PC.
If I do any other CPU intensive task under a GSI ROM, it doesn't have this issue, only when I stream video. I haven't tried any games to see if it causes this behavior.
I have tried multiple GSI Roms located here too, same problem:
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
I do not believe the device is overheating, it's usually around 32-34C from the TWRP menu at that point. I really like the RR Rom, but if I cannot figure out what is causing this, I'll have to stray away from GSI for now.
As a sidenote, this issue of the device suddenly powering down after starting to stream a video, does not happen with the stock ROM. I am kind of at a loss on this one.
Weirdest thing I have experienced running a custom ROM.

Yeah it happened to me sometimes as well... The phone goes straight into recovery and then never goes to system again. I haven't found the cause of it.

Did you try the NFC fix for the one pro (I got it from the umdigi forum one Pro and then the thread custom ROMs)

phhusson's AOSP is mostly good. But I noticed the wifi often gets disconnected and has performance issue too.

w1lh3lm3d said:
Did you try the NFC fix for the one pro (I got it from the umdigi forum one Pro and then the thread custom ROMs)
Click to expand...
Click to collapse
I posted a fix that works. Here it is if you didn't see : https://forum.xda-developers.com/p8...pment/flashable-nfc-kirin655-devices-t3811916
tomprc said:
phhusson's AOSP is mostly good. But I noticed the wifi often gets disconnected and has performance issue too.
Click to expand...
Click to collapse
I don't get any performance issue. The only issues is that some ongoing calls doesn't come, and sometimes 4G totally glitches out. Other than that it's pretty much all.

@ _cab13_
i cant find the vendor folder in twrp in the mount section or in the file manager.
what have i done wrong? ok i started from scratch and then it worked porfectly
thx you for your work and help

Engineering mode access or work around
On the 9.0 ROM I cant seem to access engineering mode via the keypad, I need to sort the handset speaker out. Is there any other way to access it or some way of tweaking the voice settings through the shell?
Any help would be appreciated.

Please help
I'm trying to get the new phh Android q to boot and and I'm a newbiew

Just booted from Android 10 GSI 200 c. by PhhTrebble without any problems (flashed latest stock before). Just to let you guys know Will update bugs and working stuff tomorrow.
[Update]
Missing features
_________________
NFC missing and magisk patch did not work for me
Media playback in for exampel youtube/instagramm/reddit etc. not working in apps but in browser it workes.
Bugs:
_________________
Sometimes apps crash
SD-card "has to be formated to use" // I did not try formating yet
Sometimes Youtube playback fixes itself if you tab out and go back to the video or if you open the help page of YT (top right corner question mark symbol) and go back to the video
Be aware that the 200.c phh gsi i used is still in development but as you can see it is totally capable to use as daily driver
[UPDATE 2]
- Missing features is still NFC
- In PHHSolution "AOSP 10.0 v211" mediaplayback got fixed (Tested with "system-quack-arm64-aonly-gapps.img.xz" )

On Phh's 9 v119 Is the headphone jack sensor working for anyone. (If so how)

4ctiv_ said:
Just booted from Android 10 GSI 200 c. by PhhTrebble without any problems (flashed latest stock before). Just to let you guys know Will update bugs and working stuff tomorrow.
[Update]
Missing features
_________________
NFC missing and magisk patch did not work for me
Media playback in for exampel youtube/instagramm/reddit etc. not working in apps but in browser it workes.
Bugs:
_________________
Sometimes apps crash
SD-card "has to be formated to use" // I did not try formating yet
Sometimes Youtube playback fixes itself if you tab out and go back to the video or if you open the help page of YT (top right corner question mark symbol) and go back to the video
Be aware that the 200.c phh gsi i used is still in development but as you can see it is totally capable to use as daily driver
Click to expand...
Click to collapse
did you use the a only or ab image?

I've tried flashing multiple android 10 GSIs from the phhusson GSI wiki list.
I've tried phhusson's AOSP ROM, CAOS, Lineage 17.1 and POSP. It seems like they all freeze at the splash screen and get stuck loading forever (confirmed, I left it on all night last night). I've tried disabling force encryption, I've tried not installing magisk. Not really sure where to go from here with Android 10.
I've also tried Android 9 with much more success: it boots, it works, but the only thing I can't seem to get is NFC. Has anyone found a way to get NFC to work on any android version with this device? Or do I have to go back to stock android 8?
Thanks!

seiyria said:
I've tried flashing multiple android 10 GSIs from the phhusson GSI wiki list.
I've tried phhusson's AOSP ROM, CAOS, Lineage 17.1 and POSP. It seems like they all freeze at the splash screen and get stuck loading forever (confirmed, I left it on all night last night). I've tried disabling force encryption, I've tried not installing magisk. Not really sure where to go from here with Android 10.
I've also tried Android 9 with much more success: it boots, it works, but the only thing I can't seem to get is NFC. Has anyone found a way to get NFC to work on any android version with this device? Or do I have to go back to stock android 8?
Thanks!
Click to expand...
Click to collapse
I'm in the same boat bro. I've just tried both the latest phhusson AOSP 10 ROM as well as an older version of the same ROM, and both time I get caught in a loop after install. Completely wiped beforehand, tried installing with and without Magisk/Disable-Force-Encryption. Going to have to bring it back down to Android 9. I wonder how 4ctiv_ got it working?

so first you have to no encryption then erase and format data
flash android 10 arm 64 a without gapps build (image) to system i use havoc 3.5 and everything exept nfc works
then install gapps (it failed for me so i had to resize system in twrp and install gapps again
last step is to flash the custom phhson magisk
then just reboot wihout wipping

Thank you so much for your work...
Hi, I'm a long time Android user and I used to code apps, if I can be of any help please let me know but I'm now disabled wheel chair user with dystonia so I find it extremely difficult to type now so I use voice to text... I really enjoy using the umidigi one max it has the storage and usability of a much more expensive phone, also functionally for me the wireless charging and NFC make my life so much easier as I find cables akward and payments at shops much easier.
I read about the Treble programmea while ago and recently read this article and if it is possible to get the NFC working on this update, I will be so greatful as it will extend the life of this great phone for me.
Good luck with your work and thank you in advance.
4ctiv_ said:
Just booted from Android 10 GSI 200 c. by PhhTrebble without any problems (flashed latest stock before). Just to let you guys know Will update bugs and working stuff tomorrow.
[Update]
Missing features
_________________
NFC missing and magisk patch did not work for me
Media playback in for exampel youtube/instagramm/reddit etc. not working in apps but in browser it workes.
Bugs:
_________________
Sometimes apps crash
SD-card "has to be formated to use" // I did not try formating yet
Sometimes Youtube playback fixes itself if you tab out and go back to the video or if you open the help page of YT (top right corner question mark symbol) and go back to the video
Be aware that the 200.c phh gsi i used is still in development but as you can see it is totally capable to use as daily driver
[UPDATE 2]
- Missing features is still NFC
- In PHHSolution "AOSP 10.0 v211" mediaplayback got fixed (Tested with "system-quack-arm64-aonly-gapps.img.xz" )
Click to expand...
Click to collapse