Related
Since there isn't much information (in English) about how to upgrade the Zopo ZP100 phone to ICS I've now done it myself (after reading a lot of Russian forums using Google Translate I finally took the plunge into the deep end of the pool and just did it).
Files needed
ICS ROM (b79):
http://narod.ru/disk/48456521001.ee...T75_h932_b79_pulid_sw 20120428-14151.rar.html
Root:
http://files.dangerd.org/pub/ZP100//zopo zp100 4.0ROOT by008.rar
Flashtool:
http://narod.ru/disk/44888871001.ee...6c3e795/SP_Flash_Tool_exe_v3.1206.01.zip.html
USB Drivers (and a flashtool I didn't use):
http://chinamobiles.org/downloads/zap/ZP100fix.zip
CWM Recovery:
http://files.dangerd.org/pub/ZP100//recovery.img
First of all: Make a note of your IMEI-number(s)
Download the files and unpack all (in seperate folders).
Shutdown the phone and plug it in via USB, Windows will search for a driver which you find in the package ZP100fix.zip (different inf-files depending on windows version).
Unplug phone, remove the battery.
Replace the recovery.img from the ICS ROM with the one downloaded seperately.
Start flashutil.
Load Scatter-file: MT6575_Android_scatter_emmc2.txt
Make sure that Options -> USB Mode is selected.
Click Download
Connect phone (still with no battery, at least I had to leave it out).
Flashing begins.
When all is done it displays an "OK window".
Now reboot the phone and when booted connect to USB again and run Root.bat from the package: zopo zp100 4.0root by008"
Follow on-screen instructions.
I did not need to install any separate Google Apps, it was included in the ROM.
Now you need to add some IMEI-numbers to your phone.
In the original ROM I could only ever see one IMEI for my zp100, so I wrote that down.
IMEI2 I took from an old Nokia I hadn't used for a few years.
Use terminal app or adb shell or whatever to execute the following (replace IMEI_1 and IMEI_2 with your IMEI's):
echo 'AT + EGMR = 1,7, "IMEI_1"'> /dev/pttycmd1
echo 'AT + EGMR = 1,10, "IMEI_2"'> /dev/pttycmd1
Update: Zopo IMEI Tool in English can be downloaded from here: http://depositfiles.com/files/wi41lcuvb (should eliminate the need for the terminal-hack above). If the system language on your phone isn't set to English the utility will be displayed in Chinese by default, so setup your phone to use English before running it.
If you want your external sdcard mounted as /sdcard (/mnt/sdcard) instead of /mnt/sdcard2 you have to replace the /etc/vold.fstab with the following:
http://www.cactuz.net/files/zp100/vold.fstab
Use root-explorer (make a backup of the old one) to replace it, then shutdown your phone and remove the battery, then plug it all back in and start again and your external sdcard shoudl be mounted on /sdcard (/mnt/sdcard) instead.
Hope this helps.
I'll report back here with any bugs etc.
To use RecoveryMod I have to chose it from the menu in MobileUncle Tools or ClockWorkMod Rom Manager, I have not been able to boot to CWM using VolUp+Power.
Some of my favorite apps can't be downloaded from Google Play Market:
Vignette
Endomondo Pro
Snowstorm Weather Widget
GPS Status
I have been able to restore them all using MyBackup Pro and they are running fine, they just aren't compatible according to Play Market.
So any app you really need is good to make a backup of using MyBackup (or Titanium or any other backup app of your choice) so you can restore it if it can't be installed using market after the ICS upgrade.
Note that all these apps can be installed fine on my other devices using ICS (HTC Desire with CM9 and Samsung Galaxy Tab P1000 with CM9 or AOKP) so it's this ROM that is the issue AFAIK.
Thank you ... I'll follow up in a couple weeks
Ordered my zopo yesterday (for the second time -- waited 2 weeks from the first store (merimobiles) and then cancelled when they still hadn't shipped it. Hopefully I'll have better luck this time.)
I appreciate you posting this info and will try it out when I get the phone.
Good luck Dave,
I ordered mine from etotalk.com, got it in about a week with DHL used for shipping.
I've updated the first post with some more info in regards to RecoveryMod and mounting external SDcard as /mnt/sdcard (/sdcard).
Since I use this phone daily I will probably not experiment much with it until any new official release is available. But the current one (b79) is good enough.
There are quite a lot of crappy chinese apps (crappy since I don't know what they do and they aren't translated into a language I can understand) installed with this ROM bit they can all be removed using the normal App-menu in the system settings.
imei no.
hello, u said that u have write the imei no. of old nokia phone which u don't use. i want to know that can i also change both the imei no. as i m from india and in india only valid imei no. works, and i m planning to purchase this phone but i am afraid that if the imei no. are not according to india then it will not work so i just wanted to know that if i write my old dual sim phone imei to zopo zp100, will it work without any problem.
rohit: I can't say for sure if the phone actually reports two IMEI's to the service provider, but at least it displays two IMEI's when I check "About phone" in the sytem settings.
Sorry I can't say if it works or not in India.
hello
hyy , i have ihtc one x aka b79 , followed your procedure it works gr8. but i am facing a problem with usb mass storage and am not able to lock into gps any possibilities to fix this error? and does anyone has an access to orignal android 2.3.4 rom for b79 , to restore to previous bug free state?
DaveKnowsAll said:
Ordered my zopo yesterday (for the second time -- waited 2 weeks from the first store (merimobiles) and then cancelled when they still hadn't shipped it. Hopefully I'll have better luck this time.)
I appreciate you posting this info and will try it out when I get the phone.
Click to expand...
Click to collapse
hiii from which website did u ordered this phone i am also planning to ordere thinking to order from ttmalls.com is it trustable
official android 4.0 is announced.
Newby with ZP100
I have bought a ZP100 with Pandawill.
Received yesterday. Wait around 10 days from China to France
It seems to be ok but there is no Android Market application (or Android Play store)
So i cannot download my applications that i bought with older phone and my phone is not interesting without applications
There is a chinese application looks like a chinese android market but ... i am french and chinese is only beautiful drawings for me.
I difficultly download some but cannot find others
If i change ICS (what is ICS ? System ?) will i resolve my problem ?
I download 2 files (http://www.zopomobile.com/xiazai.php) this morning but i don't know how to install it and afraid there is only chinese language
MP_MT75_h932_h5500_zwx_20120419-203646_ZYQ_PC.rar
ZP100_20120510new4.0.rar (think is the last android version)
I flashed ROM very often on Windows mobile samsung phones i900 and GTi8000 but i don't know Android (just install Android as 2nd system on GTi8000 Samsung). Hope someone can explain me what to do to improve the basic system
Other problem : sometimes i have no network on the 2 SIMs, all stop. I must stop and reboot the phone. Has somebody the same problem ?
Last : how to switch to recovery mode ?
Thanks
@cuctaz
Can you execute nandroid backup/restore in the recovery mode?
E:Can't mount /cache/recovery
ZP100 and ICS upgrade experiences
Hi Guys,
I bought the ZP100 1,5 weeks ago from etotalk.com.
After 1 week i tried to upgrade to ICS about this and Colonel ZAP's description.
My experiences with the ICS upgrade:
When i received the phone, on that was etotalk v1.0 firmware.
It is a very good customized rooted ROM, works fast and it has just some minor bugs.
The only problem was, it could only read the internal storage, when i insert an external SD card. It was strange, but i accept it programming defects.
I downloaded the official 2.3.6 and this B79 ICS, VCOM (Flash) drivers and the flash program.
At first, i downloaded the ClockWorkMod Recovery for chinese phones.
Unfortunately it is make a factory reset on the phone, but after you customize it, you can make full backup about your ROM.
IMPORTANT! Copy the backup to your computer, because the ICS ROM formatted my external SD
This is very recommended, because...
At first i installed the linked B79 ICS ROM.
The default language is chinese, but it contains english, so if you know the android, it is not a challenge to change it. It couldn't read the internal memory neither, just after format it.
It wasn't rooted, and deleted IMEI. When i tried to root (different way as 2.3.6, need USB debug mode and ADB) the Windows doesn't recognize the ADB driver. The driver wasn't in Android SDK, and i can't download it (i haven't tried it on Linux yet). For a moment Windows showed it found HTC Dream device. I downloaded HTC drivers, but it didn't work with it neither.
Without this you can't restore the IMEI.
Ok, go back to the official 2.3.6.
I flashed it back. Almost the same effects. Default chinese language, the internal memory cannot readable. I could root it and install CWM recovery back.
Basically it doesn't contains Play store, but you can install it.
The ROM full of chinese programmes and my experience was it is very unstable.
I uninstalled the chinese programmes, and installed Play store. When i wanted make a call, the phone restarts. The Google Play Store froze every time.
Finally i restore back the etotalk ROM, and i use it.
Maybe if i have time/mood i will install the official ICS, but about my experiences i have doubts with it.
p.s.: in about 30C outside temperature i used the phone (installing programmes). After 10 minutes using it sings that the battery is too hot, remove it from the phone.
Is any other better quality battery what is compatible with this phone? thanks
---------- Post added at 10:34 AM ---------- Previous post was at 10:19 AM ----------
Hi jbctiong,
I used CWM recovery 5.5.0.4.
Just carefully, because it make a full factory reset.
And you need to insert an external SD card
carabaothai said:
I have bought a ZP100 with Pandawill.
Received yesterday. Wait around 10 days from China to France
It seems to be ok but there is no Android Market application (or Android Play store)
So i cannot download my applications that i bought with older phone and my phone is not interesting without applications
There is a chinese application looks like a chinese android market but ... i am french and chinese is only beautiful drawings for me.
I difficultly download some but cannot find others
If i change ICS (what is ICS ? System ?) will i resolve my problem ?
I download 2 files (http://www.zopomobile.com/xiazai.php) this morning but i don't know how to install it and afraid there is only chinese language
MP_MT75_h932_h5500_zwx_20120419-203646_ZYQ_PC.rar
ZP100_20120510new4.0.rar (think is the last android version)
I flashed ROM very often on Windows mobile samsung phones i900 and GTi8000 but i don't know Android (just install Android as 2nd system on GTi8000 Samsung). Hope someone can explain me what to do to improve the basic system
Other problem : sometimes i have no network on the 2 SIMs, all stop. I must stop and reboot the phone. Has somebody the same problem ?
Last : how to switch to recovery mode ?
Thanks
Click to expand...
Click to collapse
go to this link you will be able to fix android market
http://colonelzap.blogspot.in/2012/04/zopo-zp100-rooting-and-market-fix.html
@rohit_shah000
Thanks for the link i will check
@vzzoli
Thanks for your experiences
What is the ClockWorkMod Recovery for chinese phones.
WHy you needed it ?
Now we can download the 4.0 official
Somebody try it ?
hello carabaothai,
I used it for backup/restore my ROM.
But you can use nandroid backup too.
Sorry for my abscence from this thread, I've been busy all weekend actually tuning a car instead of my phone
buntybauva: I've got no problems with USB Mass Storage, could you explain what problems you experience?
I made a nandroid backup of the old ROM, but I haven't used it so don't actually know if it works.
rohit: I ordered mine from etotalk.com
carabaothai:I forgot to mention that the ICS-rom I linked to (and flashed myself) is in Chinese as default, but can be changed to English using the System Settings, luckily there are icons in there so you can find the symbol for language (hint for anyone who doesn't know: It's an "A").
ICS = Ice Cream Sandwich (Android 4.0)
I have not experienced problems with loosing network on the SIM cards.
jbctiong: I had not tried any nandroid backup/recovery yet, tested right now and it doesn't seem to be able to actually do any backup. Some mount errors for sdcard.
vzzoli: Thank you for sharing your experiences.
I agree that the etotalk-ROM is quite good, but I always want the latest stuff on my gadgets
I have not had any issues with reading my sdcard nor in etotalk-rom or in the later ICS-rom.
The ICS rom did not format my external SD. But one should always make a backup of course (I backup my SDcard before every flash I try).
One bug I found in the current ROM is that the Cam/Videocam-switch on the phone doesn't make any difference what position it's in.
I'm going to see what the russian forum says about the official release, I'm quite happy with the one I'm currently running so no real need to change, but there could be performance reasons to change or maybe something else.
I downloaded to the "official" ROM and updated my phone
I think this is the same ROM as B79, just renamed the version.
Remove the IMEI, not rooted, other MTP driver needed etc.
@cactuz:
What operating system did you use for root the phone?
I'm using Windows, and the new official ICS ROM wants different ADB drivers than the 2.3.6.
Without this, i can't root it, and restore IMEI.
Buntybauva's mass storage problem maybe that the Windows recognize the ICS phone as media device, but can't mount as usb mass storage without a third party program
vzzoli: I used Win7 32bit when I rooted the phone, used the scripts supplied in one of the links in my initial post.
When I restored the IMEI I used Linux since that is my prefered choice whenever using ADB.
I can't check right now what version because I've apparently forgot my VPN-password so I can't connect to my computer at work
Does the camera-switch work for changing between Camera and VideoCam on the new official rom?
hyy
after ics upgrade is anyone facing problem with gps lock?
buntybauva: Not worse than before, the GPS was terrible for me before as well as after (but I do get a fix after quite some time). Though some of the guys on the russian forum has modified the antenna as far as I know.
Maybe DangerD could help us out because I think he has been involved in it.
Hello everyone,
I have bought various Android TV boxes in the past, and haven't had problems getting them up and running.
I recently ordered 2 chinese models from eBay however, which are giving me nothing but grief. I apologize in advance for such a loooong post, but I am at my wits end and I am really hoping someone can help me out.
The action was for this model here:
www.ebay.com.au/itm/231275032090
It appeared to be a pretty standard model, like a Justop 4.0, but with a hard switch where the optical should be, and a cut down remote.
Firstly, the Specifications according to the auction:
1GB ddr3
4GB nand flash
Allwinner A20 dual core 1GHz CPU
On closer inspection after receiving the unit, an additional physical difference is that the reset button appears to be between the USB ports, instead of behind the AV out - not a big deal.
After powering it up, I am having huge problems with them.
Firstly though, what the software says about the hardware:
Advanced Settings/About Tablet:
Model Number : BBA22
Android Version : 4.2.2
Firmware Version : V2.0
Kernel Version : 3.4.39 [email protected] #10 Wed May 14 22:36:36 CST 2014
Build Number : BBA22-UI4-V2.0.1
And what Droid Info says about the (relevant)hardware:
Model : BBA22 (sdk-normal)
Manufacturer : unknown
Chipset : sun7i
RIL version : sw-dataonly-ril-0.5
Build Number : BBA22-UI4-V2.0.1
Build Bingerprint : softwinners/ninss/ninss4.2.2/NinssSoftware/20140521:eng/test-keys
OS Version : Jelly Bean MR1 (4.2.2)
SDK : 17
CPU Architecture : ARMv7 Processor rev 4 (v71)
Now, the BIGGEST issue these things have, is that at random points of use, it comes up with a message "Warning - System configuration is inconsistent with the production configuration, please contact your supplier, thank you!". This message will flash over and over again for anything from 30 seconds to half an hour. I half suspect it has tablet code SOMEwhere in it also, as it keeps coming up with 'touch the circle' walkthroughs for applications like avia. This might be unrelated though, I have no idea.
So anyway, I have tried doing the Justop 4.0 flash method with a SD card, however it will not turn on if there is a card in the slot. Also, when you hold the reset button down and power it up, it does not seem to go into the diagnostic mode so I can't flash it that way either. I am guessing the ONLY way I can update short of soldering in a serial port, is to use the backup/restore function.
I read through this whole thread here, but cound not fine anything to help me:
http://forum.xda-developers.com/showthread.php?t=2398632
If anyone has any ideas, please let me know, I seriously can't get anything to work. I thought maybe the 'hotspot' being enabled was causing the incinsistency problem, but I used a process killer to stop that at startup, still no luck. Doing a system reset through advanced config didn't help either, I got the error almost as soon as turning the unit back on.
I've attached pictures of the error I am getting, the top of the board, and the back if the board.
Cheers,
Smak
PS - I am yet to hear back from the seller, but if I ever do, I will post the result here...
Smakky said:
Advanced Settings/About Tablet:
Model Number : BBA22
Android Version : 4.2.2
Firmware Version : V2.0
Kernel Version : 3.4.39 [email protected] #10 Wed May 14 22:36:36 CST 2014
Build Number : BBA22-UI4-V2.0.1
Click to expand...
Click to collapse
I seem to be in a very similar situation. My device also reports as being "BBA22" but it's a different form factor and the identification on the board is "TXCZ_A20_v1.0". I tried contacting the people that made the board (Shenzhen Tianxing Chuangzhan Electronic Co.) but they refused to help. I also tried contacting the company that made the firmware images (Shenzhen NINSS Technology Ltd.) and they also refused. The supplier I bought the device from says they have the image file but they can't seem to figure out how to get it to me (they tried emailing the +200mb file then they gave up and stopped responding). The build number on my device is "BBA22-UI4-V2.0.4" so apparently there's an update available that may work on your device.
I'm pretty sure you need to flash the image using the Phoenixsuit program to make a special sdcard that you place in the device and boot from to reflash the device.
Please post your image file if you ever get it!
tisdall said:
I seem to be in a very similar situation. My device also reports as being "BBA22" but it's a different form factor and the identification on the board is "TXCZ_A20_v1.0". I tried contacting the people that made the board (Shenzhen Tianxing Chuangzhan Electronic Co.) but they refused to help. I also tried contacting the company that made the firmware images (Shenzhen NINSS Technology Ltd.) and they also refused. The supplier I bought the device from says they have the image file but they can't seem to figure out how to get it to me (they tried emailing the +200mb file then they gave up and stopped responding). The build number on my device is "BBA22-UI4-V2.0.4" so apparently there's an update available that may work on your device.
I'm pretty sure you need to flash the image using the Phoenixsuit program to make a special sdcard that you place in the device and boot from to reflash the device.
Please post your image file if you ever get it!
Click to expand...
Click to collapse
That is good to know, I might email them again now. Will let you know the outcome!
OK, so I got a reply from the seller.
I've attached the patch file and the instructions to this message, but theres a few things to note.
- Its only like 20 meg big, so it isnt a full firmware update
- The instructions talk about pressing the reset button at the start.., I don;t think this is neccesary if its rooted already
- The instructions are VERY engrish-y, basically just dump the update.zip onto a sd card, and apply the patch through the settings menu
- The default language is changed to some form of Chinese after applying, theres plenty pictorials on how to change the android language though.
- The version has been updated from BBA22-UI4-V2.0.1, to BBA22-UI4-V2.0.3 - This is still lower than the one you mentioned @ BBA22-UI4-V2.0.4
So far though, I have re-installed all my apps, and haven't seen the error.. yet. I was a little concerned it is still giving me touchpad tutorials, but mouse mode on the remote is making short work of those.
I'll just have to wait and see, I guess.
Smakky said:
OK, so I got a reply from the seller.
I've attached the patch file and the instructions to this message, but theres a few things to note.
- Its only like 20 meg big, so it isnt a full firmware update
- The instructions talk about pressing the reset button at the start.., I don;t think this is neccesary if its rooted already
- The instructions are VERY engrish-y, basically just dump the update.zip onto a sd card, and apply the patch through the settings menu
- The default language is changed to some form of Chinese after applying, theres plenty pictorials on how to change the android language though.
- The version has been updated from BBA22-UI4-V2.0.1, to BBA22-UI4-V2.0.3 - This is still lower than the one you mentioned @ BBA22-UI4-V2.0.4
So far though, I have re-installed all my apps, and haven't seen the error.. yet. I was a little concerned it is still giving me touchpad tutorials, but mouse mode on the remote is making short work of those.
I'll just have to wait and see, I guess.
Click to expand...
Click to collapse
That seems very promising for you! Unfortunately it probably won't help me at all... It sounds like it's a sort of update patch instead of a whole image. Starting the device with the reset button causes it to load the recovery partition instead of the regular partition (I'm guessing you saw a green android with a text menu with options for recovery). I full flashing would/could involve an SDcard, but I think you would have to create it with Phoenixsuit and not just copy the file contents over (it would then just boot directly from the SDcard and you wouldn't need to press the reset button).
In my case, both the regular boot partition and the recover partition are wrecked so I couldn't even try this patch if I wanted to.
Thanks for posting, though... Hopefully it helps someone else out.
tisdall said:
That seems very promising for you! Unfortunately it probably won't help me at all... It sounds like it's a sort of update patch instead of a whole image. Starting the device with the reset button causes it to load the recovery partition instead of the regular partition (I'm guessing you saw a green android with a text menu with options for recovery). I full flashing would/could involve an SDcard, but I think you would have to create it with Phoenixsuit and not just copy the file contents over (it would then just boot directly from the SDcard and you wouldn't need to press the reset button).
In my case, both the regular boot partition and the recover partition are wrecked so I couldn't even try this patch if I wanted to.
Thanks for posting, though... Hopefully it helps someone else out.
Click to expand...
Click to collapse
Hmm, is clockworkmod still a thing? I could try taking a backup of my ROM and see if that's something you can use.., only problem is I will need a bit of time. If I get a chance, I'll do it over the weekend. I will need a place to dump the image though, it will be too big to attach here, can sort that out later though.
Smakky said:
Hmm, is clockworkmod still a thing? I could try taking a backup of my ROM and see if that's something you can use.., only problem is I will need a bit of time. If I get a chance, I'll do it over the weekend. I will need a place to dump the image though, it will be too big to attach here, can sort that out later though.
Click to expand...
Click to collapse
I'd appreciate that... Your board seems to have a completely different layout, but all the same components. I'm not familiar with clockworkmod, though, so I'm not sure how that backup would work. I guess I'd need to get clockworkmod flashed on to the recovery partition first and then I could flash the backup to the NAND from there?
tisdall said:
I'd appreciate that... Your board seems to have a completely different layout, but all the same components. I'm not familiar with clockworkmod, though, so I'm not sure how that backup would work. I guess I'd need to get clockworkmod flashed on to the recovery partition first and then I could flash the backup to the NAND from there?
Click to expand...
Click to collapse
I'm not actually too sure. The last timed I used clockworkmod was for flashing a galaxy s2 phone, so I'm not even too sure if its still around or compatible with tv boxes. There will definately be SOME sort of tool though, that can take a full backup suitable for restoring. I'm about at the limit of my knowledge, so I am sort of playing by ear and going into a google-learn-try sort of cycle as I try different things. Maybe someone with more experience will stumble in here and let us know what we need to do
This is interesting... I found another device with an identical PCB board: YBKJ_A20 (I can't post links yet, but a Google search will find it) Several chips are different so the firmware would differ. It's so hard to work with these devices when no one claims credit for making a lot of these things!
What is J4?
http://dl-1.va.us.xda-developers.com/2/9/3/6/8/3/3/DSC_0207s.jpg
I was wondering what the upper left 2 pin connector is for? (the little white 2 pin plug next to the USB)
Is it SPDIF? Power input? output? Something else? I see in this picture a cable connected so i'm hoping you can tell.
Ask BBA22-V.1.50 TV BOX Model Android 4.2 Firmware
Smakky said:
OK, so I got a reply from the seller.
I've attached the patch file and the instructions to this message, but theres a few things to note.
- Its only like 20 meg big, so it isnt a full firmware update
- The instructions talk about pressing the reset button at the start.., I don;t think this is neccesary if its rooted already
- The instructions are VERY engrish-y, basically just dump the update.zip onto a sd card, and apply the patch through the settings menu
- The default language is changed to some form of Chinese after applying, theres plenty pictorials on how to change the android language though.
- The version has been updated from BBA22-UI4-V2.0.1, to BBA22-UI4-V2.0.3 - This is still lower than the one you mentioned @ BBA22-UI4-V2.0.4
So far though, I have re-installed all my apps, and haven't seen the error.. yet. I was a little concerned it is still giving me touchpad tutorials, but mouse mode on the remote is making short work of those.
I'll just have to wait and see, I guess.
Click to expand...
Click to collapse
Hello
Thank You For This Firmware But It Work For BBA22-UI4-V2.0.1, to BBA22-UI4-V2.0.3.
My Device Model is ((BBA22-V.1.50)) with Android 4.2 and I had to update it with your firmware file to fix problem black page after boot.
after update my device with your firmware, black page broblem is solved but device not work properly and it show Error message for (android.process.acore) systematically in loop!
also I can not make very actions because this error message show repeatedly.
also the default device language is china and i can not change language (error message show repeatedly)
have you original firmware for ((BBA22-V.1.50)) with Android 4.2 device???
thank you for help me...
H.SHAFAGHI said:
have you original firmware for ((BBA22-V.1.50)) with Android 4.2 device???
Click to expand...
Click to collapse
So... For everyone looking for a full firmware for this box, and stumbled upon this thread from google like I did: DESPAIR NO MORE.
I found a compatible firmware for this device (exacly as described and same board as the one OP has) It will work even if your box came preinstalled with another software version, but its the same hardware
Found it in another thread, posted by @daaviles30 Its not EXACLY the same as the one I had originally loaded but appears to work without any issue whatsoever (even the remote works), if a little bit better.
So here it is:
daaviles30 said:
A20_V20_SDK_EN_XBMC_0703-2.img*491.4 MB
*https:/ /mega.co.nz/#!XAIRiD5Q!aIb0tvvjvzUdaf11vIR7PAadeXPV8XizYJ9X2mAzpQI
RH46-update-a20.zip*582 KB
*https:/ /mega.co.nz/#!HZwTgQIT!LQGxb6R-lCIKe58RgIGROfufY-aq5PODSAq3-NPKOeo
PhoenixCard_V309
*http:/ /mega.co.nz/#F!HAIhBJyS!L_UQPNnYdPyHTD3ggnJ6OA
After flashing update and then go to the play store and download SuperSU update that and your ready to go.
---------- Post added at 03:57 PM ---------- Previous post was at 03:29 PM ----------
Titanium Backup Pro v6.1.5.3.apk*6.2 MB
*https:/ /mega.co.nz/#!vAAWRJga!vOFKlAq_25ssrG5kvwa3-oC-d0saL06YGBIWIyN2jss
You can delete all the unwanted system apps with this app.
Hope this helps Happy New Years.
Click to expand...
Click to collapse
The flashing process is exacly as described earlier in this thread. Use phoenix card to burn the img to an SD card, turn the device on with the card inserted in the slot and enjoy your restored android box.
It Working Only With Booting From Memory Card Slot...
amedeh123 said:
So... For everyone looking for a full firmware for this box, and stumbled upon this thread from google like I did: DESPAIR NO MORE.
I found a compatible firmware for this device (exacly as described and same board as the one OP has) It will work even if your box came preinstalled with another software version, but its the same hardware
Found it in another thread, posted by @daaviles30 Its not EXACLY the same as the one I had originally loaded but appears to work without any issue whatsoever (even the remote works), if a little bit better.
So here it is:
The flashing process is exacly as described earlier in this thread. Use phoenix card to burn the img to an SD card, turn the device on with the card inserted in the slot and enjoy your restored android box.
Click to expand...
Click to collapse
Hello My Friend And Thank You For Replay...
This Android is Working And is Very Good But i Can Not Install This To My Device. I Copy The IMG File To A External Memory Card (Using PhonixCard Application) and put the Memory Card To My Device And PowerOn My Device. My Device Automatically Boot From Memory Card And New Android is Appear. It Is Very Fast And Have No Errors.
Now...
HOW I CAN INSTALL THE IMG FILE TO MY DEVICE (INTERNAL MEMORY) AND BOOT MY DEVICE WITHOUT USING MEMORY CARD (FOR ALL TIMES)???
H.SHAFAGHI said:
Hello My Friend And Thank You For Replay...
This Android is Working And is Very Good But i Can Not Install This To My Device. I Copy The IMG File To A External Memory Card (Using PhonixCard Application) and put the Memory Card To My Device And PowerOn My Device. My Device Automatically Boot From Memory Card And New Android is Appear. It Is Very Fast And Have No Errors.
Now...
HOW I CAN INSTALL THE IMG FILE TO MY DEVICE (INTERNAL MEMORY) AND BOOT MY DEVICE WITHOUT USING MEMORY CARD (FOR ALL TIMES)???
Click to expand...
Click to collapse
Wow.
The Phoenixsuite makes an sdcard that flashes the internal memory. After it's finished flashing, you take the card out and it runs off of the internal NAND. That's it. It never runs the Android from the sdcard.
My device can boot from sd-card!!! I need to flash this to install your android!
tisdall said:
Wow.
The Phoenixsuite makes an sdcard that flashes the internal memory. After it's finished flashing, you take the card out and it runs off of the internal NAND. That's it. It never runs the Android from the sdcard.
Click to expand...
Click to collapse
Hello My Friend And Thank You For Replay...
1- My Device Can Boot From SD-CARD With A Bootable Memory Card! (Such As OpenSuse Linux)
2- I Use PhonixCard Application That You Send.
(PhoenixCard_V309
*http:/ /mega.co.nz/#F!HAIhBJyS!L_UQPNnYdPyHTD3ggnJ6OA
3- I Can Not Use PhonixSuit Application And I Don't Know How To Use PhonixSuit. When I Connect My Device To My Computer To Use PhonixSuit, My Computer Don't Find Any Hardware And Can Not Connect!
4- I Copy The IMG File To A SD-CARD (Using PhonixCard Application) and put the Memory Card To My Device And PowerOn My Device. My Device Automatically Boot From Memory Card And New Android is Appear. If Unplug The SD-CARD And Power On My Device, Old Android Is Appear!!! Master Android Software Is In My Device And I Need To Clear This From My Device And Install Your Android!
HOW I CAN INSTALL YOUR ANDROID TO MY DEVICE (INTERNAL MEMORY) AND BOOT MY DEVICE WITHOUT USING MEMORY CARD???
I need help!!!!
no any answer???
First attempt at making a guide for this, so please feel free to make suggestions on how to clean it up (I feel like it doesn't lend itself well to step-by-step but you're welcome to try).
Great news everyone! (well, all three of us with T-Mobile/MetroPCS in the USA...)
I got VoWiFi to work last night on a couple custom ROMs and successfully made wifi calls. It doesn't require many pieces, but it can be complicated (not just a step-by-step) to get the required pieces into the right places.
- You need a copy of /system/priv-app/CNEService/CNEService.apk from a stock OOS install (I did it with the one from 9.0.3).
To get that, you might be looking at booting into TWRP with the other slot active or temporarily using something like @mauronofrio's fastboot install ROM from https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 and just flashing the system image to one slot to grab the file before restoring back to the one you had. Anyway, use caution, be sure of which slot you're on and what you're flashing to, and copy the apk from /system/system/priv-app (the path when you're booted from TWRP instead of inside the active system slot). You'll probably have to use ADB commands to push/pull the file directly to/from a computer if you already have a custom rom installed on one slot with screen lock set up, since /data will likely be encrypted and unavailable when you're booted up in TWRP with the other stock slot active.
- You need to be able to install a rando apk as a privileged system app to get this apk back into /system/priv-app/ correctly on your custom ROM.
There are ways to do this manually that involve lots of permissions and editing XML files for privileged app permissions in a couple places, but realistically you're using a custom ROM so you probably have Magisk (otherwise what the hell are you doing with custom ROMs?) so you should just use https://forum.xda-developers.com/apps/magisk/module-terminal-app-systemizer-ui-t3585851 and pick option 3 to install it. You'll need Magisk, a terminal emulator, and some ability to type a file path to use this module.
- You'll need to make sure that your /system/build.prop file contains the line "persist.vendor.cne.feature=1" (AEX doesn't at first, XenonHD does, not sure about others).
We've got the requisite stuff in /vendor already, this just enables the ability to use it. You'll need to have root access and a file manager/text editor (Amaze is FOSS and available through F-Droid, MixPlorer through XDA Labs is also nice, or use TWRP and a text editor that knows unix line endings on your computer to copy things back & forth via MTP and remember to set permissions after, I think it's chmod 644).
Reboot, unlock, and try to make a test call. Successfully got it to work on AEX & XenonHD last night, I suspect it works for Omni and others as well.
Try some more ROMs out and report back below if it works for you too!
Now if only you could fix the Android Auto bug.
I'm totally kidding. This is awesome. Thank you!
Tested Omni and it works too; just needed the APK added/systemized, already has the correct entry in build.prop.
hello
my op 6 running oxygen ob 10. vo lte work. but when I connect to wifi. vowifi not work ? how to fix it ??
Any chance someone could upload and share the CNEService.apk? Would make life a lot easier...
brmbjn said:
hello
my op 6 running oxygen ob 10. vo lte work. but when I connect to wifi. vowifi not work ? how to fix it ??
Click to expand...
Click to collapse
If it's not working in OOS, I don't know what to tell you. Might just be that the connection isn't reliable enough for it to decide to enable... but I never used OB10; I switched back to stable 9.0.3 after OB9.
Great work!
After many hours of trial and error, I now understand how to get RR and Lineage to boot with latest firmware updates. NO MORE BLINKING BLACK/GREY SCREEN!
Tested with Resurrection Remix 16.1 and Lineage 15.1 (Oreo)
Simply flash the boot and vendor images to their corresponding partitions using fastboot. Find the proper images from this Tmobile firmware,. https://androidfilehost.com/?fid=11410963190603878004 This method preserves IMEI and Baseband.
Nano/pico gapps work as well. HideProps magisk module can set your fingerprint to Moto E5 Play and get around that unregistered Google sh**. I edit /vendor/etc/fstab.qcom myself with vi and inside TWRP terminal shortly after flashing vendor partition. I do this because zips and other copies held me up. All I change is forceencrypt to encryptable in the data line of the fstab. Magisk 19.3 patches for verity. Another thing I do is move /vendor/lib/libeffects.so to /vendor/lib/soundfx/libeffects.so. Doing this will keep music/audio from studdering when screen is off. Last thing, TWRP 3.3.1 formats data as ext4 by default. We want to format with f2fs or you get corrupted data messages at boot. Happy flashing!
##
I find the earliest of these metro pcs firms have a working vendor image.
https://mirrors.lolinet.com/firmware/moto/james/official/Metropcs/
I got bluetooth working today, and lots of clues where I found the fix...
####Bluetooth
Now that I can set it up from a clean install, here's the basics for Bluetooth...
You'll need files from the stock system image. You can use a backup to get these or also use simg2img with dd and 7zip, I'll make a zip installer when I have more time.
1. Copy the following files, from stock image directory "/system/etc/" to the "/vendor/etc/" directory on device
mixer_paths* (14 files)
audio_* (5 files)
media_profiles* (3 files)
Edit the file /system/etc/ld.config.26.txt
add this text to the very end of line 61 :/system/${LIB}/vnd-sp/hw
You're done! If you did everything as described, and it doesn't work, check the permissions of the files you add to vendor partition with other xml files in same directory. I did mine on the device while running, it worked in place, without rebooting device. The GSI system is new to me, however the "Same Proccess HAL(hardware abstraction layer)" voodoo can likely be configured correctly to fix screen and port other GSIs' to our device.
Any chance of getting lamens terms step by step instructions on how to do this? That is the model I have and really liked those roms when I tried unsuccessfully to make them work last year.
edit: 9/21 6pm
I think it's because mine is TMO variant.
Mattswad said:
Any chance of getting lamens terms step by step instructions on how to do this? That is the model I have and really liked those roms when I tried unsuccessfully to make them work last year.
Click to expand...
Click to collapse
Trying based on this now. I'll update you.. been trying for TOO LONG lol it's almost the same time you posted 2 days ago!
---------- Post added at 04:12 AM ---------- Previous post was at 03:45 AM ----------
I've been up all night trying to get either one to work.. I think I came close but I am stuck at a looping blank screen.
If you could step through a bit more for us? I'd REALLY love to have lineageOS on it.
mrbox23 said:
After many hours of trial and error, I now understand how to get RR and Lineage to boot with latest firmware updates. NO MORE BLINKING BLACK/GREY SCREEN!
Tested with Resurrection Remix 16.1 and Lineage 15.1 (Oreo)
Simply flash the boot and vendor images to their corresponding partitions using fastboot. Find the proper images from this Tmobile firmware,.
Nano/pico gapps work as well. HideProps magisk module can set your fingerprint to Moto E5 Play and get around that unregistered Google sh**. I edit /vendor/etc/fstab.qcom myself with vi and inside TWRP terminal shortly after flashing vendor partition. I do this because zips and other copies held me up. All I change is forceencrypt to encryptable in the data line of the fstab. Magisk 19.3 patches for verity. Another thing I do is move /vendor/lib/libeffects.so to /vendor/lib/soundfx/libeffects.so. Doing this will keep music/audio from studdering when screen is off. Last thing, TWRP 3.3.1 formats data as ext4 by default. We want to format with f2fs or you get corrupted data messages at boot. Happy flashing!
Click to expand...
Click to collapse
I have the Metro PCS version
Moto e5 Play XT1921-3
Mattswad said:
I have the Metro PCS version
Moto e5 Play XT1921-3
Click to expand...
Click to collapse
Ahh That is excellent news. I am about to take a focus supplement, and dive into trying again I'll let you know. I found a few more of MrBox23's posts and I think I MAYBE onto something.... wish me loads of luck. If it works for me I THINK it should work for you, but you might need to start with a diff image than me, or use a different boot and vendor img than I will.. not sure if I can help you find those files or not..
I'll be back later to update what I find.
Sorry I haven't been on for awhile. I'll go ahead and post my working vendor and boot images. On Google drive for download. Doing this will trash your speaker if you play music very loud at all, expect that. I do not understand how to fix it. Other than that it's a daily driver. I have been asked about encryption this and that.. You have to modify fstab.qcom within vendor partition. Also the TWRP for this device will format your data partition as ext4 while the ramdisk and init stack are configured for f2fs(if you try and boot with ext4 data, you get corrupted/encrypted data message). You have to change data partition back to f2fs in TWRP every time you format that partition. Or you could modify the TWRP image like I did to fix it permanent.
Files will be uploaded soon, make sure you understand what's involved before getting into this. I'll answer questions best I can, but this is for those who are dediced and willing to get down on some bootloops to figure it out, especially if you're not used to this sort of thing. Some magisk modules will cause bootloops, do those one at a time and gapps separately. I seriously recommend taking apart the firmware from OP and focus on getting to the aosp boot animation, THEN take care of verity/root and fstab. You're formatting data partition anyway you might as well successfuly backport the graphics first.
Vendor image TWRP backup, put this on its own with boot image. I keep it as vendor_fixed for easy reference. The fstab is already patched if you use mine.
Boot image TWRP backup, it is patched with magisk (19.4 likely) install magisk on your own anyhow. KEEP YOUR ORIGINAL VENDOR/BOOT PARTITIONS! There's stuff in there that you might want later on. Like the /vendor/etc/wifi folder for example or the pieces from the original ramdisk.
Vendor and boot with md5 sums to verify integrity.
https://drive.google.com/folderview?id=1-2KO_iRFTjLv6pyx-7Qmhi8kWZBpVIWD
Wipe everything, including internal storage(after backing up a working system).
Format data partition back to f2fs in advanced wipe options.
Get LineageOS 15.1 beta or RR you can find these here on XDA.
Flash Lineage zip its the old style zip install that copies idividual files, not an image, the boot image it installs needs to be replaced per instructions that follow.
Or flash RR system image from official repository link is found here on XDA.
If you flash a system image with TWRP you'll need to reboot back into recovery right after and resize the system partition in advanced wipe options or your system partion will be incorrect size afterwards, if flashing system with fastboot(recommended) then skip the resize instruction.
After you have a system installed, restore the vendor and boot images from the link. A good approach would be to backup your existing boot/vendor as a pair, then replace originals with downloaded images.
The first time I got this to work, I used fastboot to flash partitions, like this.... I followed instructions within Metro PCS firmware(one of those xml files has the fastboot commands, including some oem options that specify a particular mode) Then i flashed ...RR system, followed by boot/vendor images from firmware referenced in OP. I finished that with fastboot -w option, that was when it worked for me. I dealt with the fstab and boot verity patching AFTER I first saw the default Android boot animation. Once you see that plain white "android" with the slow moving left to right animation, your in. From what I can tell our device needs the older kernel within the boot image and the libs/binaries from the vendor image to get the screen working correctly. Your trading your working speaker, for a working screen. I have attempted to find exactly what it is that's different between the two, but it's over my head. Overall it's relatively stable, go easy with magisk modules, some of them will cause kernel panic(bootloop) use a recovery based magisk tool to disable offending module if this happens. Sometimes the device will not boot normally, usually this means the cache was erased(its okay) for whatever reason and I wait it out, otherwise I restore the vendor_fixd backup I made. I have not had gone back to stock ROM, however I have had to flash the vendor partition to get it booting, usualy happens if i flash a module or when updates break substratum theme.
Good luck!
Oh email me for quick response, within reason.
mrbox24 at gmail
Bonus screenshot and the TWRP 3.1.1 I modified with correct data format. If you have an sdcard with second partition it will show up as "linux" named after the chroot partition from mine.
Screenshot shows LSM kernel found here, yes it works.
mrbox23 said:
The first time I got this to work, I used fastboot to flash partitions, like this.... I followed instructions within Metro PCS firmware(one of those xml files has the fastboot commands, including some oem options that specify a particular mode) Then i flashed ...RR system, followed by boot/vendor images from firmware referenced in OP. I finished that with fastboot -w option, that was when it worked for me.
.
Click to expand...
Click to collapse
thank you for this! (and the files)
questions...
1.) Your files in your zip extract as boot.emmc.win and vendor_image.emmc.win ...
Should we rename them to boot.img and vendor_image.img before flashing?
2.) Is your file TWRP-3.1.1_JAMES_T_f2fs-data.img already fixed to format data as f2fs?
3.) where is the option in Twrp to backup vendor and boot images?
I'm almost ready to dive in...
aka.bugle said:
thank you for this! (and the files)
questions...
1.) Your files in your zip extract as boot.emmc.win and vendor_image.emmc.win ...
Should we rename them to boot.img and vendor_image.img before flashing?
2.) Is your file TWRP-3.1.1_JAMES_T_f2fs-data.img already fixed to format data as f2fs?
3.) where is the option in Twrp to backup vendor and boot images?
I'm almost ready to dive in...
Click to expand...
Click to collapse
Yes TWRP is fixed for f2fs data, also the correct version is 3.3.1 latest for device.
Those files are ready to be RESTORED, not flashed in TWRP. You would replace files in an existing backup with those. I have a fresh backup made from from the earliest metro pcs firmware. I am about to upload. What device do you have?
mrbox23 said:
Yes TWRP is fixed for f2fs data, also the correct version is 3.3.1 latest for device.
Those files are ready to be RESTORED, not flashed in TWRP. You would replace files in an existing backup with those. I have a fresh backup made from from the earliest metro pcs firmware. I am about to upload. What device do you have?
Click to expand...
Click to collapse
Cool. thanks.. So far I have three, 1921-2 At&t (new, prepaid, bootloader unlockable so far, daily phone), an xt1921-5 unlocked bootloader, sim locked to sprint, so far been unable to get another rom to boot, and an xt1921-3 metropcs Gsm unlocked, boot loader unlocked, and now booted to lineage 15.1 thanks to you and phh. Wifi works, and gapps go seem to not crash, I did the register a non-stock rom hoop jump with google. Camera nothing but gray or crashes. Everytime it boots, clock time is wrong. haven't really tested much yet.
Really want to be able to get camera functioning, and test an At&t sim in it before switching it to my daily device. I read that the camera fix was committed to 15.1 but I'm lost as how to apply those patches even if I could find them.
aka.bugle said:
Cool. thanks.. So far I have three, 1921-2 At&t (new, prepaid, bootloader unlockable so far, daily phone), an xt1921-5 unlocked bootloader, sim locked to sprint, so far been unable to get another rom to boot, and an xt1921-3 metropcs Gsm unlocked, boot loader unlocked, and now booted to lineage 15.1 thanks to you and phh. Wifi works, and gapps go seem to not crash, I did the register a non-stock rom hoop jump with google. Camera nothing but gray or crashes. Everytime it boots, clock time is wrong. haven't really tested much yet.
Really want to be able to get camera functioning, and test an At&t sim in it before switching it to my daily device. I read that the camera fix was committed to 15.1 but I'm lost as how to apply those patches even if I could find them.
Click to expand...
Click to collapse
I think those patches are applied at source code level. meaning it would be in a future release. My camera works running Resurrection Remix, on xt-1921-3 try copying [email protected] from stock /system/lib/hw to /vendor/lib/hw, making sure to keep permissions same as others in vendor/lib. im willing to read logs, does your att run lineage? if so, does bluetooth work?
I make custom scripts and have a custom build.prop, for example this.....
resetprop 'media.camera.ts.monotonic' 0
resetprop 'persist.camera.HAL3.enabled' 1
resetprop 'audio.deep_buffer.media' true
Those three lines are saved to a file called mediafix.sh in /data/adb/service.d to be ran at boot. it helps with media and camera issues. As well as a one line file called led-chg.sh
echo battery-charging > /sys/class/leds/charging/trigger
Which turns on the light, otherwise never used, in front of phone when charging.
I think it's important to use a/the real fingerprint from an e5 device along with other properties. To get the best out of the hardware and least error messages during boot. I go through logcat/dmesg and attempt to fix what's broken, like the camera on lineage(works without trouble on rr remix btw). I used hidepropsconf module at first and a sprint fingerprint, but later began using the one found in info.txt of firmware zip.
ill post my work in progress build.prop(hosting it with new vendor and boot images on gdrive) which noticeably improves overall performance and lends to less log errors, or lags and crashes.
I find the vendor/boot firmware here(oldest 2018) https://mirrors.lolinet.com/firmware/moto/james/official/Metropcs/ to work best. Audio is completely a loss though. My speaker is blown now and no Bluetooth unless running stock, not even the headphone jack works. All sound comes from the one speaker, even with headphones plugged in I'm at a loss with that issue.
I also modify the boot image. turns out the 1921-3(possibly others?) uses the sdk26 8.0 android ld(library config) instead of the ld.config.27.txt that matches its sdk level. in fact if i try to force the 27 lib config, the gray/black screen comes back. it boots up, i know because my charger light comes on, but no screen. Anyhow i change the os level in boot config to 8.1.0, this gets me to where i am now with only bluetooth(mixerpath/lib issues i suspect) and a couple missing ui features due to what i imagine originate from missing whitelists in /system/etc/permissions xml files.
Another thing of note is how i spoof the mac adress for wifi, this(and other things) is done by modifying the kernel command line config in boot.img. my second e5 play xt-1921-3 has a broken screen, and serves exclusively as a wifi-repeater, captive-portal, and ssh server/tunnel. i spoof the busted screen wifi mac, with an old device mac address that is still registered on xfininity wifi network. it repeats that connection to my other devices. very efficiciently at that. with 3+MiB/s average. it took some hacking but after i found out the oem partition on this device can be formatted, and removed from the ramdisk/system all together, without consequence(not to lineage, bootleggers, or rr remix that is) and be re-purposed to whatever else. its roughly 700MB in size perfect for a debian chroot with my custom wifi repeater and misc servers. running in its own dedicated internal(FAST)partition. This device, and its kernel level mac spoofing with the now almost phased out WCNSS qualcom configurable wifi firmware, is incredible. the busted screen one has been on every day non stop functioning as a repeater, router with captive portal, and dhcp service, for almost two months. it automatically connects to wifi, kills the android zygote/system server, kills its backlight and starts up a hotspot and sshserver/captive portal, all without cell service, and without any interaction.
Anyway, new mpcs files up soon.....
mrbox23 said:
I think those patches are applied at source code level. meaning it would be in a future release. My camera works running Resurrection Remix, on xt-1921-3 try copying [email protected] from stock /system/lib/hw to /vendor/lib/hw, making sure to keep permissions same as others in vendor/lib. im willing to read logs, does your att run lineage? if so, does bluetooth work?
###bugle added### my Att is an xt1921-2, can't even unlock the bootloader... But 30 bucks isn't bad for a new screen and a new speaker. ###
Another thing of note is how i spoof the mac adress for wifi, this(and other things) .
Anyway, new mpcs files up soon.....
Click to expand...
Click to collapse
Years ago, I used to compile Gentoo to run on some archaic hp tablets... Now I just run Linux mint on somewhat newer hardware. This gave me a limited skillset to get an old Moto mb300 running with gingerbread and CyanogenMod. Everything worked, had them for over 4-5 years, just started really messing up over the summer. Miss the real keyboard.
Thanks so much for the tips and insights. It'll take some time to absorb everything in your post.
aka.bugle said:
Years ago, I used to compile Gentoo to run on some archaic hp tablets... Now I just run Linux mint on somewhat newer hardware. This gave me a limited skillset to get an old Moto mb300 running with gingerbread and CyanogenMod. Everything worked, had them for over 4-5 years, just started really messing up over the summer. Miss the real keyboard.
Thanks so much for the tips and insights. It'll take some time to absorb everything in your post.
Click to expand...
Click to collapse
My first "Android" phone was the HTC HD2 wich was actually a Windows phone that can boot linux from the sdcard. I came across it while learning how to get linux booting on laptops. I was fascinated with booting a mini linux on a portable device. I learned about Android and linux in that way, at the same time. Kernel, ramdisk, java machine, broadband cellular modem, and wifi radio in my pocket. I abandoned windows entirely, to this day lol
Right you are! @mrbox23 ... I've got camera on RRemix on the metro 1921-3!
I'm gonna put the lineage/no camera issue on the back burner for when I try to use your older boot/vendor img trick (boot Lineage 15.1) on the unlocked 1921-5.
(I only have a 1Mb/s dsl connection here, takes about 4-5 hours for a 1 gig file to dl)
So, for the Metro 1921-3, I can't find libeffects.so or even the soundfx folder to copy into. (studder fix)
Your script 2 files for media/camera and charge led, other than making them executable (0755? 0700?) will they be called (without any other mod) being in /data/adb/service.d ?
I think it's important to use a/the real fingerprint from an e5 device along with other properties. To get the best out of the hardware and least error messages during boot. I go through logcat/dmesg and attempt to fix what's broken, like the camera on lineage(works without trouble on rr remix btw). I used hidepropsconf module at first and a sprint fingerprint, but later began using the one found in info.txt of firmware zip.
Click to expand...
Click to collapse
I pulled one out of my Att phone that is a james xt1921-2 but has a locked bootloader, all stock ... I used #getprop ro.build.fingerprint.. not sure if i should use this, or wait to see your build.prop...
ill post my work in progress build.prop(hosting it with new vendor and boot images on gdrive) which noticeably improves overall performance and lends to less log errors, or lags and crashes.
Click to expand...
Click to collapse
All the best to you and yours in 2020. Meeeerrrry eXksMix, hic up'
Yes to service.d with those three. I ditched the camera ones though, footej or another camera is nice. Im close to figuring out what the vndk library thing.
hosting current prop setups, between resetprop in service.d and modifying build prop. other goodies too. I turned oem partition into swap space, and added permissions to priv-app xml's enabling more RR features, like hold back to kill app.
mrbox23 said:
Yes to service.d with those three. I ditched the camera ones though, footej or another camera is nice. Im close to figuring out what the vndk library thing.
hosting current prop setups, between resetprop in service.d and modifying build prop. other goodies too. I turned oem partition into swap space, and added permissions to priv-app xml's enabling more RR features, like hold back to kill app.
Click to expand...
Click to collapse
mediafix line 2... set or resetprop?
1 resetprop 'media.camera.ts.monotonic' 0
2 setprop 'persist.camera.HAL3.enabled' 1
what are these last lines in mediafix for?
16 resetprop net.dns1 1.1.1.1
17 resetprop net.dns2 1.0.0.1
and i'm guessing the deb.sh is for your wifi repeater? swap space in oem?
how is mpcs.prop called? where is its proper folder?
can you host a copy of libeffects.so ?
@mrbox23 Bluetooth working! check.
aka.bugle said:
@mrbox23 Bluetooth working! check.
Click to expand...
Click to collapse
something I just noticed here recently is that's all the audio output now. I can't test cellular calls, Hangouts only works when i restore that vendor path Back to where it was. My camera broke again to. I want to reach out to phh here or github.
Well that's a big bug, sorry. I've reverted the metro 1921-3 to stock for now, but on the positive side, I tried using your older boot/vendor imgs trick on the 1921-5 (Sprint)... and success! it boots Lineage 15.1 and bluetooth works, I haven't tried using the GSM Att Sim yet and still no camera, (I haven't tried your other camera recommendations yet.) One step closer for the 1921-5.
Hi,
I bought an IMEI changed Samsung Galaxy Note 9. Its rooted using Magisk, I m not a familiar with android ROM installations.
I want to upgrade android version from currently running 9 to android 10. But I dont want to loose the Changed IMEI.
What will happen if I flash official android 10 ROM onto my device, will the IMEI be changed to the factory one?
Thanks
Backup /EFS partition before changing ROM.
FYI:
EFS stands for Encrypted File System. Imagine the EFS as a big folder containing all of the important stuff that makes the "phone" part of your phone (i.e. what lets you communicate from one person with a phone to another) tick. It contains your IMEI, lots of files revolving around your SIM card and Wifi/Bluetooth (this includes your MAC address for all the radios of your phone), and lots of other things that should never ever under any circumstance be deleted or touched. It's sensitive, it's devastatingly important, and it's a huge pain. If you lose your EFS folder, you lose pretty much any chance of your phone being able to use data, Wifi, Bluetooth, and ( probaby) your phone will just not want to respond and reboot quite a lot.