Related
Hi everyone!
Got this Miphone A3 yesterday, and I been searching like a fool after information about this damn phone but it ain't a easy thing to find.
But hey, what do you expect from a cloned iphone
So here's my question:
Anyone sitting on a Miphone and have you done anything with it, most imporant for everything, ROOTED?
Phone info on the phone:
Model number:
A8
Where I bought it, it said A3 on the site (mobino1), same on the battery.
But instead of the iPhone Ui it has the Android Ui pretty sweet that it didnt have the iPhone Ui.
Firmware:
1.5
Don't have Android Market app, but everything looks like Android, also works to install . apk apps tried to install apps from 1.6+ but doesn't work.
Kernel:
2.6.25
Build number:
Linkworld Project .0002_A.1_01r_100129
Been looking for that build number for a while now, don't have any info at all on that one.
Hope some1 here has some info, would be a blessing for me!
EDIT:
I found my way into what i think is the recovery mode, came up a where is said enter flash mode put in usb cable, with red background. Then when i did that, the screen turn blue saying "Enter Flash mode, Begin to flash image..."
Been reading a lot, and i never came up with that kind of "bootloader" just saying that
hope some1 could give me some tips
hi, one of the stores provided firmware from A3, I do not know how fresh. ussd queries are unsuccessful, after ussd calls to hang up. In flash mode turns pressing the upper side volume buttons and switch.
depositfilescom/files/0po3pwcu6 - miphone A3 rom
thanks for that one!
flashed my phone, worked! but it wasnt the same version. this one was with the iphone ui (using ahome)
Model number:
A3
Build number: A3 Project.0001_18r_100411
Seems like my 3G connection does not work with this version. ussd, unsuccessful on this version too, same with previous version.
I was wondering, tried to open the one.bin (flash image) but cannot extract it. Any way to extract the image and try to reconfigure the build?
the phone using "tavor platform" flashing software, anyone know anything about tavor platform?
still trying 2 modify the rom I have, no luck so far.
I do also have this phone from mobino1...
how do you try to modify the firmware you have?
Regards,
xift
miphone a3
I too am with the same problem I have software for Tavor flashing but without success for updated the firmware is in a single bin file without being able to extract and modify
if anyone knows how do to then updated
xift said:
I do also have this phone from mobino1...
how do you try to modify the firmware you have?
Regards,
xift
Click to expand...
Click to collapse
I been trying to extract the .bin file MagicIso can read the file using it "missing files" but can't read the files when extracted. Trying to find a program that could read the rom file, have you done anything to update the phone? Do you have a rom file, if so could you upload it pls?
tried to get the firmware from mobino1 but they just ignore mig those bastards.
Ernest25
miphone a3
I too am with the same problem I have software for Tavor flashing but without success for updated the firmware is in a single bin file without being able to extract and modify
if anyone knows how do to then updated
Click to expand...
Click to collapse
Do you want to flash your phone with the .bin file you already have or do you want to know how to update the phone to android 1.6+?
To flash your phone with tavor flashing software, you need to run the flash program in XP and press "volume up" and "power" on the phone to get to flash mode, then plug in the usb with the flash program open, and it automatically flash the phone.
About updating the phone to a newer version of android I have not a solution.
I been trying to, get info on the hardware so I could try to cook a own rom with at least android 2.0
Cheers
sorry i don't have the firmware as a rom file either...
and these mobino1 bastards ignore me too ^^
although they admitted they could contact the developers...
new firmware would be nice... or at least the current firmware.
I did not downgrade it yet and I think I won't do that.
Another problem could be that the bootloader only runs signed firmware image (just guessing).
I know how to flash I want is a newer room the problem these Chinese are not then updated dependent on us for a updated
(question) has a possibility to use, one firmware and change to a bin file to MiPhone a3
xift said:
sorry i don't have the firmware as a rom file either...
and these mobino1 bastards ignore me too ^^
although they admitted they could contact the developers...
new firmware would be nice... or at least the current firmware.
I did not downgrade it yet and I think I won't do that.
Another problem could be that the bootloader only runs signed firmware image (just guessing).
Click to expand...
Click to collapse
Ernest25 said:
I know how to flash I want is a newer room the problem these Chinese are not then updated dependent on us for a updated
(question) has a possibility to use, one firmware and change to a bin file to MiPhone a3
Click to expand...
Click to collapse
If they just told me straight up, we just sell the phone, we don't have any contact what so ever with the manufacture or developers I would accept it. But this just pissed me off.
I've been asking around on other sites that sells the phone, waiting on answers from them. Hopefully they are more friendly.
Don't downgrade, that was a mistake for me (the rom file azat182 nicely posted).
I tried something yesterday, made a own .bin file with android 2.1 but the flash program wouldn't start with it (parse ini error) so I tricked the flash program that it would flash the one.bin (azat182) rom file.
After it opened I replaced the .bin file with mine. Everything seems to work fine, did every step it should like, root system etc finished 100% when I tried to turn the phone on I couldn't, maybe it didn't know were the power "button" source came from.
The android source was made for an other phone, so I wasn't surprised.
Plugged the usb back in, and luckily the phone connected somehow with the computer so I flash it with the (azat182) rom and I'm back at square -1
but now I think, if I could find out the hardware/drivers on this damn phone it would work to cook a own rom using that method.
Cheers
Oh hey, someone else with one of these phones. I've been messing with mine for a while, started out with the A8 rom (from fastcardtech), and have flashed the A3 rom to the device. I've noticed that the gps works a lot better in the A3 rom than the A8, so it's not much of a downgrade, imo. Recently I've made some headway with an android 2.1 port to the device.
Anyway, this device isn't hard to root. If you adb into it, you can get root from the device by remounting /system as RW and pushing a fixed su binary to /system/bin, or wherever it goes, it's been a while
The MTD partitioning in the Miphone's rom is a big giant mess. The rom is split into 25 partitions, the kernel isn't in boot.img like it's supposed to be, neither are the kernel parameters.
The bootloader is dumb, it doesn't check for signed images. The A3 image and A8 image are both engineering builds.
wow you seem to know a lot about it...
does 3g work for you in the a3 rom? also gps doesn't work for me in a8... so a3 could be a possibility if 3g worked.
how did you adb your phone? I could not connect... the driver just didn't show a phone. although I changed the vendor ids etc...
could you write a short tutorial of some sort? would be nice!
if you are root, couldn't you make a backup of your firmware?
is there a downloadable a8 rom at fastcardtech?
regards, xift
I haven't been able to get 3g working, just edge. I don't think the 3g will work in the US, as none of the carriers will work with just wcdma2100, but I'm no expert on the subject. I've had reasonably good luck with the gps with an app called Maverick, but I don't have a data plan currently, so no agps. With gps alone, it takes about a minute or so in an open area to acquire a lock.
For ADB, there's a driver in the android sdk, but don't bother with it. Instead, the phone's going to show up as a rndis/ethernet gadget. For windows, drivers for this can be found at webos-internals.org/wiki/USBnet_networking_setup, just the .inf is all you'll need; MacOS and Linux will just see the ethernet gadget. Once that's installed, the phone will show up on the PC side as a network interface that will need an IP address; I've been using 169.254.231.10 and subnet 255.255.255.0. Once your network interface is configured, you should be able to run adb connect 169.254.231.168:5555, assuming you've got your android sdk tool set up already. From there, you can adb shell in and poke around. Once you get an adb shell, you'll have a root prompt, but to get 'rooted' so that other android apps can make use of it, you'll want to run adb remount to remount /system as RW, then copy a working version of su over to the phone. I think superuser whitelist comes with one.
I don't usually go to that much trouble, as I end up cycling between the A3 firmware and my Eclair build a lot, and the A3 rom is jacked up to where it's a pain to get a terminal emulator running on it. Adb from my desktop seems to get the most mileage.
Fastcardtech didn't have any useful information about recovery firmware that they had, a release date for an android 2.1 rom, information on the manufacturer, anything.
Wow thanks a lot... I tried with the sdk driver.
port 5555 seemed blocked there although it was obviously responding (took much longer than other ports). Thanks for your help - I'll try that one.
Could you upload your eclaire build?
I don't have much time at the moment because of my bachelor's thesis. But I'd like to see that and maybe I could help a bit. Although I do not have any experience with mobile devices etc.
You may need to mess with the usb debugging option. After flashing to the a3 rom, it's enabled. I remember it being the same between the a8 and a3 roms.
At some point, yeah, I'll my eclair build up. I'd like to at least get bluetooth, gsm and wifi going again before I do. I don't have a rom that you'd be able to flash currently; more like a big pile of build scripts, and install scripts for the android system and ramdisk.
yeah I understand that. You could open a google code project or something.
nice to know that there is somebody working on this.
usb debugging is enabled by default. I'll just have to try again.
thanks for your help so far.
file inf
I not have disk only cd and dvd when I will install the drive without the disk says no drive found I save the file as usbnet-pre.inf
if anyone can help me pls
well I also had problems installing the driver in windows ...
It always said something like "No driver found at that location".
You could try on linux though... It worked like a charm for me.
I'm root now
@nsigma is there anything I could provide you from the a8 image?
xift said:
well I also had problems installing the driver in windows ...
It always said something like "No driver found at that location".
You could try on linux though... It worked like a charm for me.
I'm root now
@nsigma is there anything I could provide you from the a8 image?
Click to expand...
Click to collapse
linux complicated for me but thank you I hope good news from you about how root this bastard mobile
I have the A3 if you're interested I can pass to you
I made a clean ROM based on the factory ROM for the Lenovo A789, A660 and P700i
Cleaned up ROMs:
- A789_S227_cybermaus_V2 (below)
- A789_S228_cybermaus_V2.1 (further below)
Ported ROMs (ported from P700i):
- A789_ROW_S105_cybermaus_ICS_V3 (further below)
- A789_ROW_S106_cybermaus_ICS_V3.1 (Further below)(also for A660 and P700i)
- A789_ROW_S107_cybermaus_ICS_V3.2 (Further below)(also for A660 and P700i)
The current and advised rom to use is A789_ROW_S106_cybermaus_ICS_V3.21
Based on factory ROM A789_S227_120827, and located in my Dev-Host. It is as close to factory as possible, which I hope will be good for stability. It is a flash-utility ROM, because it also holds the latest preloader, uboot and recovery. Assuming those are OK, followup fixes will be update.zip style.
Summery of changes:
- Rooted the phone with Chainfire SuperSu
- Set to boot in US-english, changed name of ROM
- Added MoreLocale for extra languages in 3rd party apps
- Removed Chinese apps, incl Chinese keyboard, removed SmsReg.apk
- Left Lenovo Security (anti-malware) and Lenovo (Go) Launcher intact
- Added Google GAPPS, Play Store, Maps, etc
- Added MobileUncle toolbox, SManager (root explorer). Titanium backup (free version)
- Added fix for location services
- Added CWMT recovery image (modded from 593cn.com)
- Added Skype, Whatsapp, and some others, as auto-install into userdata upon wipe
- Prepared busybox (you need to run script /system/xbin/installbusybox as root if you want it)
- Replaced bootup animation with clean Lenovo butterfly
- Replaced all some audio files with english named ones (thanks mabuc)
- Caller ID bug still present, sorry
- Just as a reminder, these ROMS have English and Chinese only.
Instructions:
By default, the ROM will not overwrite USERDATA or FAT. If you want a clean slate, first extract empty.userdata.rar and/or empty.fat.rar
- Read bgcngm flash tutorial.
- Read it again
- Start Flash Tool (v3.1222, in my Dev-Host)
- Load scatter file
- Take out USB cable and replace battery
- Press the download button in the flash tool
- Connect the USB cable
- Wait for the flashing to complete
A789_S228_cybermaus_V2.1 (no longer current, Use V3 instead)
Based on factory ROM A789_S228_120913, and located in my Dev-Host. Similar to V2, but newer, and a few extra fixes. It should be noted that the S228 is listed to solve unexpected crashes, so an important update in itself.
I do not have a A789, so it is a blind build. Until I get positive feedback, consider untested. Don't be the first to try if you are not experienced.
Summery of changes:
- Same as on V2, and additional
- Removed 2 more chinese apps that I forgot last time
- Prepared busybox (you need to run script /system/xbin/installbusybox as root if you want it)
- Added a tweak so USB-Debug notification is no longer shown
- Added a tweak so Wifi works on all 14 international channels (rather than only the 11 US ones, may be undone if you set a different locale)
Instructions:
This is a update.zip type ROM. So you need the custom recovery, see post #3,
A789_ROW_S105_cybermaus_ICS_v3.03
Based on P700i_ROW_S105_120920, see this separate post.
A789_ROW_S106_cybermaus_ICS_v3.11
Based on P700i_ROW_S106_121001, see this separate post.
Please note that this ROM I also build for the P700i and A660. See same post.
A789_ROW_S107_cybermaus_ICS_v3.2
Based on P700i_ROW_S107_121221, see this separate post.
Please note that this ROM I also build for the P700i and A660. See same post.
Below:
Post #2: Small review and fix of location services
Post #3: Custom recovery image
Post #4: Root your phone / install GAPPS
Also, many issues for the A789 are similar to those of the A750, so if you have questions, do search that Lenovo A750 thread to.
Thanks
Also thanks to bgcngm for his help, and to jazzor for his help
=================
BTW: Due to new forum rules, resulting in a large number of people that cannot post into developer threads and that subsequently PM me, I open op a new Q&A thread.
I am not going to be policing, so you can post where you like, but I invite everyone to use this new thread for any Q&A, and this thread for ROM releases and deep development talk only.
Consequently, if you PM'ed me, look for your reply in this new thread
Thanks
====================
PS: do drop me a reply if you use or tried it! Or press the 'thanks' button.
So, I got my first glimps at the A789. So to speak. My colleague was holding it while we were audio-skype, so I did not actually see it.
His A789 came with a Etotalk ROM by Dean, which I now suspect is a reworked Smileyvvv ROM with Sony Experia interface. Not bad, but as you know, I am a 'factory ROM' guy. My colleague may also be, because he had already replaced the the SE launcher with GO Launcher, which is the default Lenovo one. Also my colleague said it jammed a few times, which it still has not done on my factory A750 ROM.
Most of the phone worked, but a few tips for others out there:
- The phone still has the Called-ID bug. Even though it is newer 4.0,4. I know some of you claim this is solved on ICS Mediatek, but I still claim it is solved in *some* of the cases, not all, it also depends on how your provider sends the caller ID info. Anyway, you can work around it with the prefixer app as reported before.
- It did not come with the MobileUncle tool, but with the Etotalk tool. Which was not updated for the new MT6577 chip, so it had no Engineer Mode. Install the latest MU tool (version 20120813v2.2.0 its in my Dev-Host), so you get one with MT6577 Engineer mode.
- Recovery Mode was hard to get into. Like the newest A750 preloader, you have to press the power putton *just before* you press both volume buttons. But it did came with the CWMR Touch, though its Touch function was broken, so buttons only. They probably simply tried recovery images of other models, and did not properly build one with the A789 kernel, but it does not matter, it works well enough.
- Location services did not work. Update the phone with the ICS_locationfix_v1.3 update using recovery mode. While you are in recovery, also wipe cache. And finally, go into MobileUncle tool, the MTK Engineer mode, and in location settings, change the NetLoc from MEDIATEK to GOOGLE. Now your location services should work.
Lenovo A789 Recovery
I created a recovery image for the Lenovo A789 based on ClockWorkMod Touch 5.5.0.4. However, I do not own a A789, so until I have reports of it working, consider it untested. You can download it from my Dev-Host: File A789_S22x_recovery_cybermaus.rar
NOTE: It has come to my attention this recovery works well, except the nandroid backup function, which is broken. If you value nandroid backup, install the APKHOT one below.
While doing this, I also found a full APKHOT distro which had what seems to be a CLockWorkMod (non-Touch) recovery in it, so I extracted that and also uploaded it. That too you can download from my Dev-Host: File A789_S22x_recovery_apkhot.rar
Both of them you will have to flash using the flash tool, using bgcngm's excellent manual, and the V3.1222 of the flash utilities and drivers, also in my Dev-Host. If you flashed my V2 ROM, you do not need to do this, as the recovery is already part of that.
Once you have the recovery installed, you can enter it by pressing both VolumeUp/Down while booting the phone. Due to an issue with the preloader, it may be needed to press the power button slightly before both volume buttons. If the phone seems stuck, it means the preloader messed up, remove battery and try again.
Inside the recovery (the Touch variant) you can navigate not only by its physical buttons, but also by screen buttons, and by gestures: swipe up/down for up/down, left for back and right for enter.
The first few people using this, please report your findings, good or bad.
PS: As alwasy, thanks to bgcngm for his unpack utilities, which I used to modify the recovery.img
Lenovo A789 Root; GAPPS, Location DIY
Its been mentioned before, but if you have a working recovery (like above, hopefully), you can always yourself root your phone. Simply install (from inside the recovery) chainfire's "CMW installable ZIP"
Link to his post: (ignore his big red requires root warning)
The file you need is labeled "CWM installable ZIP" at the bottom.
Direct link to the file you need to install via recovery update.zip
And while you are at it: You probably also want to install the latest Google Mobile Services (better known as GAPPS) from CyanogenMod V9:
Explaining wiki from CyanogenMod
The file you need is called gapps-ics-20120429-signed.zip and can be found here
You probably also want to wipe your cache partition after doing this.
To complete this DIY of fixing factory ROM: On Chine phone typically the location services do not work. Update the phone with my A750 V1.3 update using recovery mode. (it works on the A789 because it is a minor update, but *DO NOT* any of the other A750 updates on the A789. I repeat, do *NOT* flash A750 on A789). While you are in recovery, also wipe cache. And finally, go into MobileUncle tool, the MTK Engineer mode, and in location settings, change the NetLoc from MEDIATEK to GOOGLE. Now your location services should work.
Good luck
PS: If either update.zip refuses to install, remember to turn off the checksum and assert checks in the recovery.
And thanks to Chainfire for his work, and the team at CyanogenMod for theirs.
cybermaus said:
Before I can help, please provide some info:
Can you tell me what ROM you have?
Which flash tools did you use to root?
Also, do you have a working recovery?
Click to expand...
Click to collapse
hwonggc said:
I fix the proximity thingy. it's caused by my lousy screen protector. But i've got another bigger problem now. I've accidentally uninstalled the default system home screen. I cant assess anything now. I tried flashing a recovery inside but it still doesn't work as factory. I use SP flash tool v3.1.222.00
---------- Post added at 06:32 AM ---------- Previous post was at 06:18 AM ----------
dont think my recovery is working. Could you please provide me with a working recovery? =(
Click to expand...
Click to collapse
Yes, a recovery is on the todo.
But for now, you did not answer my questions yet:
- Can you tell me what ROM you have? Or had. Original Lenovo Factory, Etotalk-Dean, some other?
- Which flash tools did you use to root? Or rather, which files did you flash using that tool to deal with root. Actually, the fact that you had to root it yourself probably means you had factory ROM, but please confirm.
As stated, I am uploading S221 original to my Dev-Host. Flash that with the flash tool. On short notice, that is all I can do. On longer notice, I will help you, but give me some time.
Edit: In fact: You you already have messed up your recovery, and I do not have a A789 to play with myself, you may be my guinea pig for the recovery build. So I will work on that today. (as today is not a working day for me anyway). If you do not mind being a tester. After all, the damage is already done, and you apparently already know how to flash using the utility.
EDIT: @ hwonggc : Please test recovery in post#3. Just update your post below with results, or PM me. I would like to avoid too many new posts on this while we are testing.
cybermaus said:
Yes, a recovery is on the todo.
But for now, you did not answer my questions yet:
- Can you tell me what ROM you have? Or had. Original Lenovo Factory, Etotalk-Dean, some other?
- Which flash tools did you use to root? Or rather, which files did you flash using that tool to deal with root. Actually, the fact that you had to root it yourself probably means you had factory ROM, but please confirm.
As stated, I am uploading S221 original to my 4Shared. Flash that with the flash tool. On short notice, that is all I can do. On longer notice, I will help you, but give me some time.
Edit: In fact: You you already have messed up your recovery, and I do not have a A789 to play with myself, you may be my guinea pig for the recovery build. So I will work on that today. (as today is not a working day for me anyway). If you do not mind being a tester. After all, the damage is already done, and you apparently already know how to flash using the utility.
Click to expand...
Click to collapse
Yes yes. I had the factory rom. I got the phone just yesterday evening and this afternoon it's half dead already. I use smart phone flash tool to root using a file i got from http://www.fight.org.ua/publications...novo_A789.html. Everything was fine until I deleted the original home UI and the apex launcher also. So there isn't anything I can do. I'm downloading the S223 from some russian site and try, hopefully I can find some luck there. Downloading slowly~ sighhhh.
---------- Post added at 07:49 AM ---------- Previous post was at 07:40 AM ----------
BTW~ i'm willing to test out your rom too! I wouldn't want to sound too demanding, put please please put in the play store will ya?
I posted the custom build, see first post. It may take a while before I can get it uploaded, I am on a bad link.
Also, there have been 20 downloads on the recovery image. Come on guys, someone must be able to provide feedback about it working or not!
A789_S227_cybermaus_V2 ROM is working
Hello
Thanks for Your work.
Your A789_S227_cybermaus_V2 ROM is working.
Simple Flashing and start without problems. Now I must check some functions.
Thx again
basell
Edit:
The 3g connections don't work at first run. After restore they start but in My opinion with less sensitivity (compare to stock rom). It's look like A789 loose some frequency on witch can work.
Edit2:
And they have some strange behavior - After couple min of data connection (on 3G) they disconnect with information - "Restricted access changed" and the same is when I try to choose network manually. After that sometimes they login to 3G sometimes they change to EDGE.
In Stock version (S221) was not this kind of problems.
Edit3:
In place with good 3G signal I have no problem with data transfer.
How Can I check on witch frequency (2100,900,850) I have connected My data transfer?
Thanks for testing
Well, I definitely did not mess with any of the 3G stuff. So if it is true that 3G is less sensitive, then I would claim it is true for the factory S227 vs factory S221, and not directly related to my cleanup of it.
But (sorry to say so) I have learned to take claims of improved or degraded radio sensitivity with a grain of salt, even for the factory ones.
Having said that: Restoring S221 radio into S227 firmware is easy. The radio is separate firmware file, and I can extract the S221, S223 and S227 firmware in a separate file, so you can test. Were you actually using factory S221, or some other?
As to whether it is using 2100, 900 or 850: I can probably figure out how to get that info, *BUT* reality is that your provider most likely has only one frequency anyway. Most, pretty much all, EU providers are on 2100. The phone could not get to 900, simply because your provider does not have that frequency in the air (not for 3G anyway). And 850 is not supported at all on this phone.
Anyway, inside MU utility, engineer mode, bandmode, you can check/set the frequencies that are supported.
But please run a proper test if 3G is really degraded. As stated. it is so often a empty claim, I am somewhat careful to follow it. You want me to extract the 3 versions of firmware files in update.zip files?
Also, what country/vendor are you? please list the MMC and MNC from inside the APN settings.
Hi
If You will prepare this files I can test it tomorrow.
I'm from Poland and I have two frequency on data transfer - 2100 and 900. But I don't know if A789 use only one or change them. The place I'm test the signal is poor and I don't see if I work on 2100 or 900.
If You can, pleas tell me what kind of tests I can do to do that properly
Ok, here they are. update.zip type.
I only have S221 and S227, but the firmware files were indeed different, in more than just their timestamps. Of course, normally I would assume newer is better. So to make it clear: below files only replace the radio&dsp firmware, not the phone firmware.
Try to test honestly for yourself. Same conditions, same place, same time (because network load can make a difference)
It is possible that 3G really is degraded in S227, but as mentioned, I learned to not jump to conclusions just because the network is having a bad day.
WARNING: I retracted the two attachment, because I made a typo in the installer script. While the firmware is for the A789 (MT6577), the installer script is for the A750 (MT6575). Sorry. I will upload the correct ones in a moment.... Anyone that took a copy of these files before Oct 14, delete them!!!
I suspect the install would simply have failed, no harm done, but best to get rid of all copies anyway
BTW: basell, is that why you asked how to install? Really, if you ask for help, you should provide a bit more info. Anyway, I attached newer scripts, if you still want to try.
sorry for My question but :
How to install this firmware?
Like any update.zip on android. Go into recovery (see post #3) and apply the update.zip
i have the problem that the netlocation doesn't work with google maps, i flashed the cyber update 1.3, nothing changed, what should I do now?
And this is on what phone and ROM?
Anyway, to quote myself: "While you are in recovery, also wipe cache. And finally, go into MobileUncle tool, the MTK Engineer mode, and in location settings, change the NetLoc from MEDIATEK to GOOGLE. Now your location services should work."
many thanks, Cybermaus, netlocation works again after your instruction
Hi,
Thank you very much for building the ROM !!
I am using it for 3 days now and I am happy to report no problems with it. Everything works and most important: no more freezes !!!
my A789 came with the Etotalk by Dean ROM which was mostly OK, but was freezing from time to time (some days not at all, other days several times a day - most of the times when hanging up a call or, when trying to do wake it from standby: I was pressing the power button, but the screen would not light up).
Other things I like about this ROM:
- all phone functions work great
- Google Play works perfectly
- is rooted
- it has the Lenovo battery app, which is great! I am not 100% sure if this is the reason, but the battery life went from 1 day to 2 days
- I had no issues flashing it
- CWMT recovery works
Also, so far, I did not experience any 3G issues
I have written a small review of the Lenovo Security app, which you guys may want to put back on your phone if it was cooked out of it.
jman0 said:
Thinking it twice, I've remembered another reason. One of the things I like most about the apkhot rom I'm using is that the external sdcard is mounted on /sdcard and not /mnt/sdcard2, which avoids problems with many apps. I tried one of the newest apkhot roms, based on s227, and none of the tricks to exchange /sdcard and /mnt/sdcard2 worked with it.
Click to expand...
Click to collapse
Well, that is actually an easy change to perform, just change the /etc/fstab.vold
However, if you go into settings->storage, the first option is default write disk. Change it from USB storage(the internal SD) to SD (the external SD)
So no hacking is needed at all.....
I've been running your rom for around 6 hours now. Everything runs fine. The 3G connection worked without much trouble. The only thing I haven't been able to do is performing a backup with the CWM Touch Recovery. So, I've just flashed the recovery I had on the apkhot rom I was using, using Mobileuncle tools, and now I've been able to create a backup.
So far, so good, and I've noticed a slight performance increase, too.
Hello, first of all this is my first post, so im gonna introduce myself first,
I am a freelance web designer/developer and understands logical programming. Anyways i am basically new to android, and i want to learn how to edit/modify/customize stock roms. so first i want to learn extract these stock roms. I am currently on the starting phase and i only have some ideas about the terms / programs that is used in this forums. Basically, i am running a windows machine, OS is windows 7.
I find it hard to fix some bugs i encounter in my android which lead me to the goal of learning.
So for the device that i will use as a scapegoat for my learning venture, i am using a Skyworth x7010 tablet which have no more support, i think and not a very well known model, infact i cant seem to find any forums dedicated to the tablet itself.
I am technically knowledgable in computer hardware and windows OS, also i am able to write different type of websites in php, (forums, E-Commerce, social networking/networking website, company web based panels, etc.). As of now I am currently working alone in every web aspect of bagongpleion.com and bagongpleion.net.
So far this is what i have done, and done to the tablet. I have no backup as of now.
1. I have already bricked one, just made it perma bricked then returned for warranty, the staffs decided to mark it as defective motherboard (No response from anything including recovery mode and bootloader mode) ~ Bricked it while trying to flash cwm for rk30 device.
2. device is running a JB 4.1.1 for the android version, and kernel 3.0.36+ ([email protected] #48)
3. I have already started learning adb, well for the most part, i had used it in the past for unlocking devices that got locked out screen patterns, and rooting.
4. The Device has a rk3188 1.6ghz max quad (Box says 1.8 though), mali400mp(Quad), 2GB ddr3 ram, 8gb internal storage, partitioned in 2, nand and internal.
5. I have the usb drivers for adb and rktool, android sdk, currently downloading and installing cygwin but the download is so long, i am forced to close/pause it.
6. I have already rooted the device, and modified the applications, and removed some apps that is not required. I deleted the files in the /system/app thru adb. I also had edited the Build.prop already, Changed the heapsize to the best performance (I am comparing the performance with CPU Identifier and Passmark. ) Stability is tested with simultaenous apps (High end games, browser, root apps, benchmark). I also edited the pixel density and reduced it by 1 to make the resolution exactly 1280 x 800.
7, One bug i found is that it cant play NBA 2k13, I had almost tried every solution i can find in the internet, Used different version, i even copied the data and apk from a device that can play it. The game force closes automatically after the Black screen (Original apk) or muzhiwan or apkmania.com loading screen at the start. This is also one of the reasons why i wanted to edit/modify the device.
What i wanted to do.
-Backup Original Firmware/rom/img (i dont know which and what is the correct term)...
-upgrade jellybean to 4.2 if possible, or 4.3
-Tweak more the device to bring out the full potential of it,
-remove and clean the apps and everything, leaving only the necessary files and apps.
-learn more how much i can modify it.
NOTE: I am not asking for the people in this forum to spoonfeed me, i just wanted to know how and where to start, what to do, some keywords for searching, and the limitations that i have in my venture.
-i am a gambler and will take the risk to learn android much more )
Thank you
First of all, congrats that you are more of a researcher. That's a good thing because in the internet, answers to every questions are available. You just need to do the right search in the right way. :good:
Games not working on a device maybe because of various reasons such as the developer has made it limited to work on certain devices or processor architecture etc. If Play Store link shows not supported, then it needs more research and modifications to make it work, which is like 50-50.
And, as a learner you are good to start with XDA-University. It has countless tutorials in that section.
Good Luck and welcome to XDA!
thank you for the link and reply, i am actually suited best in researching, i learned every bit and pieces i know in building websites, programming web apps and system with php, even overclocking and advanced troubleshooting in researching the internet, anyways i have another question to ask,
what is nandroid?
is it an android device with nand storage? (I.E. Nand - internet - external - usb storage)
thank you again
th3f33 said:
what is nandroid?
is it an android device with nand storage? (I.E. Nand - internet - external - usb storage)
thank you again
Click to expand...
Click to collapse
Nandroid is referred to as Nandroid Backup (Backup being taken of ROMs) in ClockWorkMod recovery (Custom Recovery) for the most part.
coolsandie said:
Nandroid is referred to as Nandroid Backup (Backup being taken of ROMs) in ClockWorkMod recovery (Custom Recovery) for the most part.
Click to expand...
Click to collapse
i see, thank you again, as of now, i am still downloading cygwin packages, do you have an idea how big is the total file size of it?
and another thing, I have used romdump, and got the following..
boot.img (13mb+)
checksum.md5(265b)
config.gz
recovery.img(32mb)
systeminfo.gz(1.76kb)
system.tar(385MB)
how can these files help me and can i use them for backup?
th3f33 said:
i see, thank you again, as of now, i am still downloading cygwin packages, do you have an idea how big is the total file size of it?
and another thing, I have used romdump, and got the following..
boot.img (13mb+)
checksum.md5(265b)
config.gz
recovery.img(32mb)
systeminfo.gz(1.76kb)
system.tar(385MB)
how can these files help me and can i use them for backup?
Click to expand...
Click to collapse
Sorry, no idea about Cygwin.
boot.img is your Kernel, and its needed for modifying the kernel. config.gz is the configuration of your device, and its also used for kernel building. recovery.img is your recovery. system.tar is your system partition which contains all files related to ROM. Yes, you can use these as a backup, as actually you'll get these when you take a nandroid backup in CWM recovery.
coolsandie said:
Sorry, no idea about Cygwin.
boot.img is your Kernel, and its needed for modifying the kernel. config.gz is the configuration of your device, and its also used for kernel building. recovery.img is your recovery. system.tar is your system partition which contains all files related to ROM. Yes, you can use these as a backup, as actually you'll get these when you take a nandroid backup in CWM recovery.
Click to expand...
Click to collapse
basically, the system.img is the one that is mounted on /system right? and it contains all files related to rom, does it mean that the ROM is like the OS? if i am not mistaken, i had already edited the apps and build.prop in the /system before i had made the system.img. But i have pulled the whole /system folder before i deleted the apps thru adb.
now the recovery.img is the one that have the android with red triangle exclamation point on vol+ power (android system recovery 3e, this is stock right) ? this is what i need to use if i fail on flashing a custom recovery? is that right?
how important is the config.gz?
boot.img is the kernel, should i stay away from the kernel for the time being? or is it better to check the boot.img first?
am i lacking any file for backup or is this enough for backup?
i have installed rom manager but it says it unsupported device. does it mean that i cannot install CWM?
i think i can flash custom rom with rkbatchtool, i had tried it before (custom rom for a different type) and it ended up bricking the device
as of now, i have tried flashing the generic cwm for rockchip which ended in a black screen recovery,
i also tried flashing my recovery.img but it doesnt work, it get flash but nothing works
it is still working fine as of now except that it doesnt have a recovery!
i think i had corrupted the recovery partition, cause i used a 1.35 rk flash tool and the memory address was set for rk3066 which is 0x0010000 (i think) and mine was 0x0020000.....
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???
Hello
I've a Leagoo T5 wich use his own Nougat modifiied. TERRIFIC !!!
I'm looking for another ROM wich supporting all feature (also double rear camera and fingerprint reader) because it's impossible to use it.
T.I.A.
Paolo
You can use "MTK Extractor" to extract system.img and other files, you can then modify them, and flash them using "SP Flash".
I recently uploaded a clean stock ROM (LEAGOO_T5_OS2.1_E_20180116) to Mediafire and Needrom.
I've also uploaded a carepack if you are interested in the new ROM, or even for a custom.
The command for fast boot is: fastboot oem unlock
Ferather said:
You can use "MTK Extractor" to extract system.img and other files, you can then modify them, and flash them using "SP Flash".
I recently uploaded a clean stock ROM (LEAGOO_T5_OS2.1_E_20180116) to Mediafire and Needrom.
I've also uploaded a carepack if you are interested in the new ROM, or even for a custom.
The command for fast boot is: fastboot oem unlock
Click to expand...
Click to collapse
Do you mind sharing please? I'd love to get a working custom rom on this device.
I still can't add links yet, so you will have to Google search: "MTK Extractor". Download it, and then download the latest official ROM, which I have uploaded to Needrom and Mediafire, Google search: "OS2.1_E_20180116".
Extract the "system.img" file from the stock ROM using MTK Extractor, you can then go ahead and make your customization's. System apks are signed and locked, however they can be replaced.
When you have finished, you can use MTK Extractor to create a new system.img file with all of your modifications (including root, if you add it). The size for system.img is 4096mb.
The MTK Extractor tool uses a slider bar and text input for the partition size, the slider is limited, however enter 4096 into the text box (don't delete the text, it bugs).
Enter fastboot (Power + Volume up), third option, then using ADB with command prompt, type the command: "fastboot oem unlock", and then accept.
Now you have unlocked the phone, you can run your custom ROM. In a factory locked state, ROM's will install, but not run.
I forgot to mention my Needrom pack contains MTK Extractor. If you can make roms, there are 3 stock bugs that I would ask you to fix.
1: If the navigation bar is hidden, there is a window transition blip (bottom of the screen) if you swipe to recent apps.
2: If you select the first (bottom left) icon from the lock screen (voice, usually), you get a grey background.
3: Bluetooth scanning sometimes bugs (MAC instead of name), once paired there are no issues.*
* This may be due to my headset, but I remember my TV also displaying a MAC once.
Also, can you align or remove the 4G icon that shows even with data turned off.
Ok... So far this thread seems to be the only one on xda-dev about leagoo T5, which i just buy.
By the way thanks Ferather for pushing the rom on need rom.
Here the link :
https://www.needrom.com/category/leagoo/t5-leagoo/
Need help
Hi, could you please share the Mediafire link?
Since the last rom update (LEAGOO_T5_OS2.1_E_20180822 aka OS2.1_E_20181025) I post on needrom a moded rooted boot with magisk.
i have this leagoo t5 running this newest e_20181025 but im getting a problem with my front facing camera only displaying like an upsidedown image of the rear camera. please advise on what i can do to fix this
Maybe inconsistence between differents partitions (like boot and system)
If you know what you are doing I will advise reflashing all principal partitions.
But i don't think the phone came like this when new, so someone must have messed something.
https://www.mediafire.com/#3c2rnntnz3kw0
LEAGOO_T5_OS2.1_E_20181025.zip -- Original Leagoo T5 ROM
LEAGOO_T5_OS2.1_C_20181025.zip -- Custom Leagoo T5 ROM
No issues, other than the one I have mentioned, which is just an app default.
Enjoy!
hey cool rom bro.
Thank for sharing.
No problem, I thought I would start the ball rolling for customization of the rom, since adding ringtones does not work with the stock rom (media storage app issue I think).
You can permanently edit the rom yourself, which I found very easy. If you want to add apps, simply install them from sdcard or store, then navigate to "/data/app", you will find your installed app or update, with odex files and libs, if any.
I created a temp folder on "/data" called "Working" and copied everything into it, and then setup the correct permissions, and renames, and transferred to either "/system/app" or "/system/priv-app", depending on the app.
A better way to do it, is to use "Lubuntu" from live USB or DVD, and then mount the image and edit it as root: "sudo *file explorer*", in this case "sudo pcmanfm-qt", then create a folder in "/mnt" called "ROM".
Next copy "system.img" to "/tmp", and mount it "sudo mount /tmp/system.img /mnt/ROM", now you can do whatever you like, but make sure to "chown" and "chmod" all your modifications.
Make sure you delete anything you will replace when you transfer, else you might get old unused files (folder merged and non-replaced items remain).
----
If you make edits on the phone using an app, and want to make your own "system.img", use the readback option in "SP Flash Tool".
physical_start_addr: 0xe000000
partition_size: 0x100000000
----
Note: Most non-stock apps *do not* support the triple (3x) camera setup, and will either use the wrong camera or crash.
Yeah I encounter problems too to add custom ringtone and wallpaper but i manage to get over it by changing some files permissions
By the way I am "456456" on needrom, the boot img with magisk is from me
I know the time needed to make a custom rom and I'm glad to see that I'm not the only one trying to mess with this not-bad-at-all cheap phone
There is a possibility of an Oreo port, there is a Leagoo T8s with the the same chip that runs Oreo 8.1.0. I have checked over the rom and it looks possible (based on my basic knowledge).
Cygwin + Cmder, for Android. I made the pack myself, and thought it might help others using Windows who want various Linux tools.
I added Cmder for better console support and easy admin: ---- http://www.mediafire.com/folder/lzsf7xd2wwsm4/Commander
Quick update, will now self configure "/home", added ADB and Fastboot.
Ferather said:
There is a possibility of an Oreo port, there is a Leagoo T8s with the the same chip that runs Oreo 8.1.0. I have checked over the rom and it looks possible (based on my basic knowledge).
Click to expand...
Click to collapse
Hi, Running your ROM with no other mods, it's certainly better than original. Just curiousis there anyone working on an Oreo based ROM ?. ... J
Thanks, I did not manage to get the Oreo from the T8 to function, due to hardware changes.
Ferather said:
Thanks, I did not manage to get the Oreo from the T8 to function, due to hardware changes.
Click to expand...
Click to collapse
Ah !, C'est la vie, would have been interesting. Apologies for late reply was away from home and didn't have much spare time. ... Jack
please tell me how you can fix the inverted touchscreen Leegoo T5