Database Info

[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.

[ROM][Omni] OmniROM 7.1.2 for Samsung Galaxy SL i9003

NOTE: Development has been shifted to a LineageOS port: here.
First, the usual disclaimer
Code:
/*
* Your probably long expired 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 features included in this ROM
* before flashing 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
* and point my finger right back at you.
*/
About the ROM
This is a build of OmniROM 7.1.2 (Nougat) for the Samsung Galaxy SL (GT-I9003)
Things to take a note of
This ROM is still a Work In Progress. As such, some features do not work, as listed ahead
GApps is NOT RECOMMENDED as there is very low amount of /system partition space
Make sure you keep a backup of your files. If flashing from stock, this WILL wipe every partition
This ROM does not come with CJK fonts to make it fit in the /system partition. Therefore, Chinese text rendering will be broken
This ROM does not come with AOSP WebView or Chromium. They will be offered separately
This ROM is not rooted. Flash a root zip manually.
Steps to flash
Reboot to Recovery.
Wipe Data / Factory Reset.
Select the ROM zip from your SD Card and flash.
Reboot
Downloads
ROM: https://drive.google.com/file/d/0BwV3ZBepyFp0WXAtUkJhZ1FmUG8/view?usp=sharing
AOSP WebView: https://drive.google.com/open?id=0BwV3ZBepyFp0VllqcmdJVVd4TFU
Chromium: https://github.com/omnirom/android_vendor_omni/raw/android-7.1/prebuilt/app/Chromium/32bit/ChromePublic.apk
Things that work
WiFi
Bluetooth
Things that don't work
RIL
Adopted storage
Internal storage (detected as portable storage)
Vibrator control
XDA:DevDB Information
Samsung Galaxy SL Forward Ports, ROM for the Samsung Galaxy SL i9003
Contributors
Technohacker1995
Source Code: https://github.com/Technohacker/android_device_samsung_galaxysl
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.0.x
Based On: OmniROM
Version Information
Status: Alpha
Created 2017-05-06
Last Updated 2017-08-26

Great work, I suggested this to be considered for a shoutout from XDA.
Contact me if you want me to edit the stickied thread in General and update it to reflect your Nougat port

Skander1998 said:
Great work, I suggested this to be considered for a shoutout from XDA.
Contact me if you want me to edit the stickied thread in General and update it to reflect your Nougat port
Click to expand...
Click to collapse
Thanks for the support!
You could add this thread to the post, but currently I'm in the process of moving towards LineageOS which happens to be a much better home for the Galaxy Sl. Many of the missing features are present in Lineage

WoOooOow, This is so cool!
Waiting for the LineageOS Version to try

Very happy, you have all my support. cheer up

Yehia2amer said:
WoOooOow, This is so cool!
Waiting for the LineageOS Version to try
Click to expand...
Click to collapse
The LineageOS version is available on my Drive, but it needs some prerequisite setup before installing. If you're ready to mess with the Linux/Android terminal, you can message me

waiting to try LOS, can you post the instruction & the download link thanks.

blacklist3d said:
waiting to try LOS, can you post the instruction & the download link thanks.
Click to expand...
Click to collapse
Sure
LineageOS: https://drive.google.com/open?id=0BwV3ZBepyFp0NV9oX3lTdTNUZDA
GApps recommended: https://opengapps.org Pico package
In case it doesn't print my messages:
1. WARNING! This update removes the Internal SD card for a bigger /system and /data. Make a backup of everything present in your Internal SD card.
2. This update uses a different logical partitioning scheme (LVM, for those who know it). Reverting back to an old ROM is non-trivial.
3. The first time you flash the update package, it checks if you're on the new partitioning scheme. If not (like on older ROMs), it will reboot into this ROM's TWRP build. Reflash the package from TWRP.
4. Before applying the new partitioning scheme, it warns you of data loss (due to formatting of partitions) and exit with an error. Make sure you have backed up any important data and reflash the ROM file to accept the procedure. It will format the Internal SD Card and continue installing.
5. ***EFS IS BACKED UP TO THE EXTERNAL SD CARD***. If there is no External SD card, it should warn you and ask you to pull the efs folder to your computer via adb (adb pull /tmp/efs /some/place/safe)
Note:
1. I'm still fixing issues related to GApps, currently the Google Sign In page does not load (and so doesn't Jelly [Browser]). To access the internet, you'll need to install a different browser. Firefox and Chrome work nicely
2. Camera doesn't work
3. Connectivity is complete. Phone is usable, SMSes can be received. I couldn't test Mobile Data, however.
4. GPS is non-working
5. After I'm done fixing issues with GApps, you should format /data (WARNING: Contains the emulated SD card. Make a backup), install the update and without exiting recovery, install GApps (Cited from the OpenGApps wiki).
Cheers!

I want to use an old i9003 for music player based on Google Music to play music via Bluetooth to my speakers.
I tested this rom.
1. install rom
2. flash gaaps aroma with choice to include Google Keyboard and Google music and with options to remove all obsolete apps
3. After login to google account and pairing to speakers everything working but after reboot I cant connect via Bluetooth to speakers and cant delete this speakers from BT menu
4. Flashed from scratch everything and after boot first time pairing working but after reboot again cant connect to speakers and cant delete speakers from menu.
My conclusion i something is broken in Bluetooth
Can You check this?
Technohacker1995 said:
Sure
LineageOS: https://drive.google.com/open?id=0BwV3ZBepyFp0NV9oX3lTdTNUZDA
GApps recommended: https://opengapps.org Pico package
In case it doesn't print my messages:
1. WARNING! This update removes the Internal SD card for a bigger /system and /data. Make a backup of everything present in your Internal SD card.
2. This update uses a different logical partitioning scheme (LVM, for those who know it). Reverting back to an old ROM is non-trivial.
3. The first time you flash the update package, it checks if you're on the new partitioning scheme. If not (like on older ROMs), it will reboot into this ROM's TWRP build. Reflash the package from TWRP.
4. Before applying the new partitioning scheme, it warns you of data loss (due to formatting of partitions) and exit with an error. Make sure you have backed up any important data and reflash the ROM file to accept the procedure. It will format the Internal SD Card and continue installing.
5. ***EFS IS BACKED UP TO THE EXTERNAL SD CARD***. If there is no External SD card, it should warn you and ask you to pull the efs folder to your computer via adb (adb pull /tmp/efs /some/place/safe)
Note:
1. I'm still fixing issues related to GApps, currently the Google Sign In page does not load (and so doesn't Jelly [Browser]). To access the internet, you'll need to install a different browser. Firefox and Chrome work nicely
2. Camera doesn't work
3. Connectivity is complete. Phone is usable, SMSes can be received. I couldn't test Mobile Data, however.
4. GPS is non-working
5. After I'm done fixing issues with GApps, you should format /data (WARNING: Contains the emulated SD card. Make a backup), install the update and without exiting recovery, install GApps (Cited from the OpenGApps wiki).
Cheers!
Click to expand...
Click to collapse

chudczan said:
I want to use an old i9003 for music player based on Google Music to play music via Bluetooth to my speakers.
I tested this rom.
1. install rom
2. flash gaaps aroma with choice to include Google Keyboard and Google music and with options to remove all obsolete apps
3. After login to google account and pairing to speakers everything working but after reboot I cant connect via Bluetooth to speakers and cant delete this speakers from BT menu
4. Flashed from scratch everything and after boot first time pairing working but after reboot again cant connect to speakers and cant delete speakers from menu.
My conclusion i something is broken in Bluetooth
Can You check this?
Click to expand...
Click to collapse
Yeah, I'm on it. Same occurs for me with my Sony Smartwatch SWR50.
Thanks for letting me know

I can not finish the assembly of the partition, possible small tutorial?
Enviado desde mi SM-G950F mediante Tapatalk

joam280 said:
I can not finish the assembly of the partition, possible small tutorial?
Enviado desde mi SM-G950F mediante Tapatalk
Click to expand...
Click to collapse
Sorry, I'm not sure as to what you mean by assembling the partitions, do you mean the LVM setup?

Technohacker1995 said:
Sorry, I'm not sure as to what you mean by assembling the partitions, do you mean the LVM setup?
Click to expand...
Click to collapse
sorry for my bad English.
My phone stayed in internal memory and does not recognize the micro sd.
Come back again and again to recovery

joam280 said:
sorry for my bad English.
My phone stayed in internal memory and does not recognize the micro sd.
Come back again and again to recovery
Click to expand...
Click to collapse
I'm assuming you've flashed my update zip, and it rebooted to TWRP.
TWRP should have an option in the Install menu to choose from where to select the zip file. Choose Micro SD Card in that and you should be able to install the ROM again
This time you try to install, it will warn you of data loss [1] and exit with an error. Just flash the zip file again and it should continue
[1]: (which, now that I think of it, is no longer useful, considering you can't access those partitions)

joam280 said:
sorry for my bad English.
My phone stayed in internal memory and does not recognize the micro sd.
Come back again and again to recovery
Click to expand...
Click to collapse
I had similar symptoms before reformatting sd card

Great work! I will try as soon as possible.
Can I suggest to open a new thread, with lineage is in the title. It will be useful for other people to find this ROM ( it will be more easy also from google search)
Best Regards and good work

ILCAMPIONE said:
Great work! I will try as soon as possible.
Can I suggest to open a new thread, with lineage is in the title. It will be useful for other people to find this ROM ( it will be more easy also from google search)
Best Regards and good work
Click to expand...
Click to collapse
Thanks for the compliments
Yeah, I'm planning to start another thread (and possibly delete this one) after I've got a few features fixed (Bluetooth in particular)
Cheers!

Status update on LineageOS port:
Bluetooth seems to be working fine now.
Mobile Data doesn't work
GPS works (tested with Google Maps)
Performance is (as expected) slow.
No hardware decoding of video is available at the moment
Cheers!

Please download link
Technohacker1995 said:
Status update on LineageOS port:
Bluetooth seems to be working fine now.
Mobile Data doesn't work
GPS works (tested with Google Maps)
Performance is (as expected) slow.
No hardware decoding of video is available at the moment
Cheers!
Click to expand...
Click to collapse

chudczan said:
Please download link
Click to expand...
Click to collapse
Could take a while, I was patching files on my phone so I'll need to build an update zip
EDIT: Since the build and upload could take a lot of time, here's the file to replace. Place this file as /system/lib/hw/bluetooth.default.so
https://drive.google.com/file/d/0BwV3ZBepyFp0VGlsUG16M3ZWZHc/view?usp=sharing

[ROM][6.0][STOCK]{UPDATED} Lenovo Tab 3 8"/TB3-850F

STOCK ANDROID 6.0 MARSHMALLOW ROM
FOR THE LENOVO TAB 3 8"/TB3-850F
TWRP FLASHABLE ZIP
FORCE ENCRYPTION & DM-VERITY DISABLED​
DISCLAIMER: Your warranty will be voided by installing this ROM, unlocking your bootloader, or flashing a custom recovery. You hereby assume sole responsibility for any positive or negative consequences incurred by flashing this ROM. As always, flashing your Android device or otherwise altering its file system & partitions involves an inherent risk. I am not responsible for any devices which are bricked or otherwise rendered inoperable as a result of flashing this ROM. However, in such scenarios,
I will provide all support feasibly possible. Follow the simple instructions carefully and you should experience no adverse affects.
Lenovo's open source code for this ROM encompasses both the 850F & 850M variants of this tablet. Therefore, this ROM should be completely compatible with the TB3-850M as well.
NOTES:
This Stock Android 6.0 ROM is virtually unmodified. However, it should be noted that dm-verity (device mapping) and force encryption have been disabled via patched boot image. This is the most current stock OS for the Lenovo Tab 3 8"; therefore, no OTAs will need to be installed subsequent to flashing this ROM. In order to ensure that force encryption gets disabled, it is imperative that the /userdata (Data) partition is formatted in TWRP prior to Installation. Please carefully follow the below instructions.
For those members who want a pure stock experience, but also want root access of the stock OS, I'm currently compiling a deodexed & zipaligned version of this ROM, fully rooted with Magisk 14.0 & BusyBox binaries pre-installed.
SPECIFICATIONS:
Android Version: 6.0 Marshmallow
Build No: TB3-850F_S100031_171010_ROW
Kernel Version: 3.18.19
SDK Version: 23
Software Version: TB3-850F_160412
Build ID: MRA58K
Android Security Patch Level: 9/05/2017
Runtime Version: ART 2.1.0
Hardware Version: LenovoPad TB3-850F
Board Platform: MediaTek MT6735M
CPU: 64-Bit, Quad-Core Cortex A-53 - 1.0GHz
GPU: Mali T720 - 450MHz
RAM: 1GB
OS Build Date: 10/10/2017
Source Code: http://pcsupport.lenovo.com/us/en/products/tablets/a-series/tab3-8/downloads/ds112711
REQUIREMENTS:
1. Unlocked bootloader;
2. TWRP recovery;
This is a pure stock, unmodified, TWRP flashable Android 6.0 Marshmallow ROM for the Lenovo Tab 3 8". This ROM was compiled from the most recent stock /boot and /system images. However, as noted previously, the boot image has been unpacked, patched, and repacked in order to disable dm-verity and force encryption. Because raw firmware images were used in compiling this ROM, the file size is in excess of 1GB (approximately 1.35GB).
INSTRUCTIONS:
1. Download the ROM from the link provided and save it to your external micro SD card. Do not save to internal storage, as your /data partition will need to be formatted prior to installation;
2. Boot your tablet into TWRP recovery;
3. Wipe /system, /data, /cache & /Dalvik-ART cache. Also, select "Wipe", then "Format Data." This step is crucial to ensure disabling of force encryption. Please note that once installed, you may go to SETTINGS>>SECURITY and opt to encrypt the userdata on the tablet;
4. Select INSTALL, navigate to the location in which you saved the ROM zip file, and initiate installation. Flashing will complete in approximately 3 - 4 minutes;
5. Reboot system.
You should now have unmodified stock Android 6.0 installed on your Tab 3, as well as disabled dm-verity and disabled force encryption.
DOWNLOAD LINKS:
Stock Android 6.0 ROM --
TB3-850F_S100031_171010_ROW: https://drive.google.com/file/d/1iMf0Ns_XWGpYlNmXCvUsW_1DfaRMeIuO/view?usp=drivesdk
Stock Recovery Image: https://drive.google.com/file/d/1D6A7b080luzsSf0xLJSCqPBNeQLSWo94/view?usp=drivesdk
Unpatched Stock Boot Image: https://drive.google.com/file/d/1azgIrPbfJHBzZF9R4IUMxIGNga6vjipD/view?usp=drivesdk
Lenovo File Manager (APK): https://forum.xda-developers.com/android/general/app-lenovo-file-manager-lenovo-tab-3-8-t3706161
Lenovo Tab 3 8" User Guide --
TB3-850F & TB3-850M (English)(PDF): https://drive.google.com/file/d/18gCTfuZecJnlB0ddBIN02YPaDpuvmzov/view?usp=drivesdk
Older Build(s):
TB3-850F_S100030_161209_ROW: https://drive.google.com/file/d/0B1Sfod4HWfk2aTNtVmJHZGpWZEE/view?usp=drivesdk
BUGS: Please report any and all bugs, no matter how seemingly trivial or insignificant. For those members with the knowledge, please submit a proper bug report. If you are not sure how, simply provide as many facts & details as possible. If you are having problems with apps, please specify as to whether the app is from Google Play. Also, please DO NOT submit bug reports unless you are utilizing this ROM in its present form -- unmodified, pure stock. Custom kernels, mods & tweaks (e.g. Xposed framework) & any deviations from pure stock will make it futile to analyze bug reports. Instead, provide with detail the precise nature of the problem. If reporting a bug, please specify if you are rooted (systemless or system-mode) and/or have BusyBox binaries installed. Submit screenshots of bugs if possible.

Brilliant! Will download now and report back later. Thank you.

My custom ROM for this tablet should be coming out of the Android Kitchen later this evening. I've dubbed it Ethereal OS v1.1 [Android 6.0.1]. Extremely lightweight yet moderately feature packed.

MotoJunkie01 said:
My custom ROM for this tablet should be coming out of the Android Kitchen later this evening. I've dubbed it Ethereal OS v1.1 [Android 6.0.1]. Extremely lightweight yet moderately feature packed.
Click to expand...
Click to collapse
Nice!
After flashing the stock zip TWRP says unknown error. It booted up fine to where you login to your gmail and "bluetooth sharing has stopped working" pops up. Bluetooth can not be turned on within settings. I can not double swipe down to get to the notifications and the "Home" and "Recents" buttons do not seem to work although they both vibrate when pressed.
I will flash stock with SPFT and try your stock rom again.

stonedpsycho said:
Nice!
After flashing the stock zip TWRP says unknown error. It booted up fine to where you login to your gmail and "bluetooth sharing has stopped working" pops up. Bluetooth can not be turned on within settings. I can not double swipe down to get to the notifications and the "Home" and "Recents" buttons do not seem to work although they both vibrate when pressed.
I will flash stock with SPFT and try your stock rom again.
Click to expand...
Click to collapse
I got the same error with Bluetooth Share force closing two times at the setup screen. Probably a corruption issue during archiving the ROM. I'll do an md5 and archive the ROM again.

Seemed to work, however the loading images and screen is still lenovo. Also they lenovo apps are still there.

rongallant said:
Seemed to work, however the loading images and screen is still lenovo. Also they lenovo apps are still there.
Click to expand...
Click to collapse
This is not a custom ROM. This is pure stock. The Lenovo boot logo, boot animation & apps are supposed to be there. Like the title implies this an "Unmodified" stock ROM.

MotoJunkie01 said:
This is not a custom ROM. This is pure stock. The Lenovo boot logo, boot animation & apps are supposed to be there. Like the title implies this an "Unmodified" stock ROM.
Click to expand...
Click to collapse
My bad, understood.
On another note, I am finding it very buggy. The home and overview buttons do not work. They show you clicked it along with the haptic feedback, but nothing happens. The back button works and is the only way I know to get back to the home screen.
Also the tool panel you pull from the top stops working after a little while until I reboot. Then works for a little while.
The Play store downloads barely work. They show pending and nothing happens. I force quite, cleared the cache, disabled, reverted to the stock app and it works for a little bit. Then the other Play Store app comes back. Anyways, I am not complaining. I appreciate the work you put into this. It's awesome we get to do it at all. Just giving my feedback. P.S. It's a new TB3-850F.

rongallant said:
My bad, understood.
On another note, I am finding it very buggy. The home and overview buttons do not work. They show you clicked it along with the haptic feedback, but nothing happens. The back button works and is the only way I know to get back to the home screen.
Also the tool panel you pull from the top stops working after a little while until I reboot. Then works for a little while.
The Play store downloads barely work. They show pending and nothing happens. I force quite, cleared the cache, disabled, reverted to the stock app and it works for a little bit. Then the other Play Store app comes back. Anyways, I am not complaining. I appreciate the work you put into this. It's awesome we get to do it at all. Just giving my feedback. P.S. It's a new TB3-850F.
Click to expand...
Click to collapse
Yes. Very buggy indeed. I have determined that the bugs are due to corruption during the unpacking of the system image. I'm repacking the ROM now to alleviate the bugs. Thanks for your input...

I've managed to fix the major bugs reported upon initial install of the ROM -- Recents & Home Buttons, Quick Pulldown Menu, Google Framework bugs, New App Shortcut bugs, etc. Simply corruption during packing (archiving) the ROM zip. I will try my best to get a new build posted sometime today.

MotoJunkie01 said:
I've managed to fix the major bugs reported upon initial install of the ROM -- Recents & Home Buttons, Quick Pulldown Menu, Google Framework bugs, New App Shortcut bugs, etc. Simply corruption during packing (archiving) the ROM zip. I will try my best to get a new build posted sometime today.
Click to expand...
Click to collapse
Dear MotoJunkie
İs it possible to upload stock Fm Radio Aplication(offline radio) of Tab3 8? İn my Turkish model, theres no Fm radio aplication. I need it to use tablet in my car.
Thanks

MotoJunkie01 said:
I've managed to fix the major bugs reported upon initial install of the ROM -- Recents & Home Buttons, Quick Pulldown Menu, Google Framework bugs, New App Shortcut bugs, etc. Simply corruption during packing (archiving) the ROM zip. I will try my best to get a new build posted sometime today.
Click to expand...
Click to collapse
Did you get around to uploading it? I am unable to use the OTA update file. Says its missing 'android-info.txt'
Also, anyone care to point me to a way to get back to stock/unrooted?? Nooooo, I didn't backup my ROM first. That would have made way to much sense.

I've been out of commission, unfortunately, due to impending health issues once again. I know that hospital food sucks, that the pretty nurses don't typically put out easy, and that the hospital WiFi restrictions can easily be bypassed with a proxy server address. Lol. And that's all I've learned in the past ten days. Anyway, hope to be back in my daily routine in the next day or so and finishing some stuff up for this device.

Hi, is this thread alive? I'm interested in solution because i have about 60 tablets and need a solution to clone form one source tablet (config, apps, wlan, users, etc.) to other 59. I have tried adb backup --twrp and it went ok, but when i tried restore it gave errors with system partition and now i can only recover tablet with factory ROM from this thread (but it is buggy and cannot put it int to production like this). Is it possible to create system rom from other working tablet? Iwill be very pleased If You can write step by step, how to create zipped rom from working device so i can then upload it to share with others.

spiker_80 said:
Hi, is this thread alive? I'm interested in solution because i have about 60 tablets and need a solution to clone form one source tablet (config, apps, wlan, users, etc.) to other 59. I have tried adb backup --twrp and it went ok, but when i tried restore it gave errors with system partition and now i can only recover tablet with factory ROM from this thread (but it is buggy and cannot put it int to production like this). Is it possible to create system rom from other working tablet? Iwill be very pleased If You can write step by step, how to create zipped rom from working device so i can then upload it to share with others.
Click to expand...
Click to collapse
The thread is alive and I'm currently ironing out the errors on the posted ROM. The errors are due to a couple of permissions which are omitted on my updater-script file. I'll be posting an updated and hopefully error free release this week. Thanks for your interest and sorry for the delay in development. I've had a number of health issues of late and I'm now recovering.

Problem after wiping /system
Hi,
I´m new right here. I bought a new TB3-850F and wanted to flash the Original Stock Rom. After opening the Bootloader and booting into twrp like this way https://forum.xda-developers.com/android/general/guide-lenovo-tab3-8-tb3-850f-t3559786 I wiped the /data /System /dalvic and /Cache. After that I rebooted the system.
But it only shows after starting the Lenovo-Logo. No more booting. Because of this I can´t start the fastboot modus with Minimal ADB and Fastboot.
Is there some idea how I can boot into fastboot?
Many thanks for your help,
sailor1977

sailor1977 said:
Hi,
I´m new right here. I bought a new TB3-850F and wanted to flash the Original Stock Rom. After opening the Bootloader and booting into twrp like this way https://forum.xda-developers.com/android/general/guide-lenovo-tab3-8-tb3-850f-t3559786 I wiped the /data /System /dalvic and /Cache. After that I rebooted the system.
But it only shows after starting the Lenovo-Logo. No more booting. Because of this I can´t start the fastboot modus with Minimal ADB and Fastboot.
Is there some idea how I can boot into fastboot?
Many thanks for your help,
sailor1977
Click to expand...
Click to collapse
I´ve got a solution: After powering down, press power, wait 1 sec then hold both vol up & down also (all 3 Buttons) until vibrates. After starting in recovery Modus hold power button und press once the vol up.
With help of: https://forum.xda-developers.com/android/help/lenovo-tab3-8-2016-custom-recovery-t3483454 post #66

Ok. I've debugged the Stock 6.0 ROM in the OP. Fixed the Bluetooth force close issue at startup and the bugs involving the hardware buttons and the pull down menu. I'm traveling for work at the moment. Soon as I'm back home Monday I'll post the fixed build in the OP.

MotoJunkie01 said:
Ok. I've debugged the Stock 6.0 ROM in the OP. Fixed the Bluetooth force close issue at startup and the bugs involving the hardware buttons and the pull down menu. I'm traveling for work at the moment. Soon as I'm back home Monday I'll post the fixed build in the OP.
Click to expand...
Click to collapse
Cheers buddy. Good stuff ??

@Hemphiz, I hope all is well my friend. Something I wanted to get your input on. It seems that a few members have been experiencing boot loops and other problems after following the TWRP & Root thread I revised. I'm sort of at a brick wall in terms of figuring out what's going on. I'm thinking that maybe there are regional variants that are incompatible with the TWRP we use. Or, it could be one of those situations where instructions are not being closely followed. What are your thoughts? Thanks.

[GUIDE][AOSP][7.1.2][HLTE][Rev11][11-Mar-18]Resurrection Remix - Rock Stable Setup

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.

[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