Hi,
I've been looking for a solution for my tablet on net for long time but unfortunately couldnt find any. I have reduced version of k012 (FE7010CG) for my country and it is k012_2 (FE7010CG) which supports 3G. It is almost same device but has single simcard slot and doesnt support phone calls via simcard. FE7010CG is phone pad but k012_2 is tablet only so its general issue about k012_2. It can make calls with apps but i want to use my simcard for calls. When i call my own number while simcard is in tablet,it calls but no sign on tablet so cant answer. I installed numpad apps and when i try to call,android system says device doesnt support phone calls.Still i have Telephony Service,ASUS Phone and Call(Android) apps installed in my tablet but i can't open or delete them from device. I read many threads about this issue and ASUS doesnt support rooting and installing ROM and they dont help about it,only thing they say is device will be out of warranty with rooting(even if you use its own official ROM). So my question is; is it possible to turn my k012_2 to k012 with installing k012 ROM and make phone calls via my simcard? I dont care about it going out of warranty but I dont wanna kill my device either. Will it cause any permanent harm on device if i try k012 ROM ?
Vigilon said:
Hi,
I've been looking for a solution for my tablet on net for long time but unfortunately couldnt find any. I have reduced version of k012 (FE7010CG) for my country and it is k012_2 (FE7010CG) which supports 3G. It is almost same device but has single simcard slot and doesnt support phone calls via simcard. FE7010CG is phone pad but k012_2 is tablet only so its general issue about k012_2. It can make calls with apps but i want to use my simcard for calls. When i call my own number while simcard is in tablet,it calls but no sign on tablet so cant answer. I installed numpad apps and when i try to call,android system says device doesnt support phone calls.Still i have Telephony Service,ASUS Phone and Call(Android) apps installed in my tablet but i can't open or delete them from device. I read many threads about this issue and ASUS doesnt support rooting and installing ROM and they dont help about it,only thing they say is device will be out of warranty with rooting(even if you use its own official ROM). So my question is; is it possible to turn my k012_2 to k012 with installing k012 ROM and make phone calls via my simcard? I dont care about it going out of warranty but I dont wanna kill my device either. Will it cause any permanent harm on device if i try k012 ROM ?
Click to expand...
Click to collapse
Word of advice, do NOT flash firmware that is not specific for your device. You will end up bricked for sure. Also, there are several generic root methods available. However, if they don't support your device, there's not much you can do. Try Kingo or farmaroot. Search is your friend.
Evolution_Tech said:
Word of advice, do NOT flash firmware that is not specific for your device. You will end up bricked for sure. Also, there are several generic root methods available. However, if they don't support your device, there's not much you can do. Try Kingo or farmaroot. Search is your friend.
Click to expand...
Click to collapse
I saw a guide that roots my device successfully with using adb driver and asus intel root kit but it roots to k102_2 again(on site they have links for all required stuff also) but there is not any info if it gets call option and probably it doesnt get it with new k012_2 ROM. I dont have any experience with rooting but having phone call option for my device will be so great for me. It will save me from buying a new smart phone so giving it a chance sounds so reasonable. But if you say it will be bricked for sure i will have to give up
Vigilon said:
I saw a guide that roots my device successfully with using adb driver and asus intel root kit but it roots to k102_2 again(on site they have links for all required stuff also) but there is not any info if it gets call option and probably it doesnt get it with new k012_2 ROM. I dont have any experience with rooting but having phone call option for my device will be so great for me. It will save me from buying a new smart phone so giving it a chance sounds so reasonable. But if you say it will be bricked for sure i will have to give up
Click to expand...
Click to collapse
If it's built for your SPECIFIC device model, then it's OK. Otherwise, steer clear. If your device is WiFi capable, try using Hangouts and Hangouts Dialer. Or possibly Google voice.
Evolution_Tech said:
If it's built for your SPECIFIC device model, then it's OK. Otherwise, steer clear. If your device is WiFi capable, try using Hangouts and Hangouts Dialer. Or possibly Google voice.
Click to expand...
Click to collapse
My device has everything but phone calls Hangouts is really expensive in my country compared to gsm calls. So its not a good option for me . Thanks for advices. Hope someone had experience with similar issue and can help me.
Any new idea for the topic?
I realized that I should install WW SKU type of ROM . I tried several methods but I could not change the SKU of the ROM of the tablet (FE7010CG). There is a protection. Can you suggest a method that can be applied to lollipop.
Related
Hi I succesfully flashed my brother in laws Lenovo A369i with the latest firmware Lenovo_A369i_4.2.2_(by_xdafirmware.com).zip found at http://firmwarefile.com/lenovo-a369i
I followed this guide and used the flash tool included in the firmware package above, and the latest usb drivers from below:
http://www.modifyandroid.com/stock-roms/lenovo/how-to-install-stock-rom-in-lenovo-a369i/
https://androidmtk.com/download-lenovo-usb-drivers
According to the phone, this version is A369I_S110_140108 - and when checking for updates it says that this is the latest one - but how can I be sure?
I searched on google and most of the times there are sites that claim to have the latest but they don't write which version it is(very anoying) so I can spend many hours(very slow internet connection) on downloading the one I already have or one older.
The information and guides on here Xda has not been updated for a while.
The Phone works with both phone calls and sms, but the IMEI is not written - so should I do that with SN_Write_Tool_v2.1504.00.zip, MTK Droid Tools or is there an easier way to do it - or should I just forget about it?
UPDATE: I got this sorted out now, by rooting with framaroot and using Chamelephon to first make random IMEI then reboot and change the IMEI to the correct ones.
-----------------------------------------------------------------------------------------------------------
My second problem is that the phone were unlocked before I flashed it and now its locked again - are there a guide to unlock it?
The phone were not bought with subscription, we bought it here in the philippines from Lenovo Mobile( not real Lenovo company but dealer/importer allowed to use the name(for god sake stay away from them)) and after repair the dealer sent back different older model(this A369i) with less battery and locked to Globe. After trying for 2 months to get them to give us the unlock code, I gave up fighting them and had it unlocked at phone repair shop were they had to use a box to do it, so I never got any code.
---------------------------------------
Third problem: I need to root it but not sure which tool to use?
Update: This is sorted out, see above.
--------------------------------------------------------------------------
Fourth problem: I like to install custom recovery on it - but which one work best and allow to flash from SD card?
As this is the first time I have flashed an Mediatek phone, are there anything else that I need to do?
Hope an expert can help me
JBJ
UPDATE:
I have now installed the manual update for Android 7.0 and this helped to resolve some of the issues:
-I can now make and receive calls fully with voice enabled
-Bootloader updated from 1.26 to 3.11
BUT:
-Fingerprint Recognition still not working
-Device serial number still shows as 111111111111111
-Device shows as encrypted- could this be the cause and how?
If anyone has any suggestions please assist.
MY ORIGINAL POST RE ISSUES:
Following release of Android 7 for ZF3U, I updated and then wanted to unlock the bootloader and carry out root. All went fine but now after unlocking the bootloader and root I have a major problem. My ZF3U does not show the correct device serial number in the initial setup wizard and in about phone section of settings. All I get is "111111111111111". Secondly, whilst all other functions are working fine, I can no longer hear the sound of any made or received phone calls.
I also tried to use the ASUS Flash Tool to reinstall the firmware but could not and at one point I saw a message stating that the device was being encrypted . I have no idea what implications this has but I my phone does not allow use of internal speakers or microphone for the other side to hear me. It appears that the serial number issue started with my use of the Asus Flash Tool. I am also not sure if this encryption issue caused the issue as it may have locked certain parts of the device.
Also, as a result I am unable to set the fingerprint recognition in initial setup or after setup. Pin code, pattern etc can be setup but not fingerprint security.
Tried to use TWRP to reinstall the firmware. All installs fine but the problem is still there. I pressed the decrypta button inside TWRP settings but still no fix. Also, did all the usual wipes etc.... still no fix. I don't know what to do. I now wish I had not played around with the phone and simply used it as it was. With the bootloader unlocked no Android 7 anymore until manual firmware becomes available. My device serial number still shows as "111111111111111" but when I launch the fastboot/recovery mode I do see the correct serial number but the device boots to UI with the incorrect serial number. My theory is that the Asus Flash Tool caused the problem but I am not sure how.
Also if anyone has the original factory boot.img and other relevant .img files for me to fix the bootloader in case this is the problem thatI would be very appreciated. Also, I have read that the .raw firmware files for this device could fix the problem but not sure and the files cannot be found anywhere online.
I also by removed the root and did a fresh install of the previous firmware Android 6.0 and the problems still exist. I am not sure if the downgrade from Android 7 could have caused these problems too but I am trying to pinpoint the problem somehow. So if anyone has a full manual .Raw or normal .zip version of the Android 7.0 firmware then please provide a download link. If all fails then I would have to see if I could get Asus to fix it for me.
All suggestions and workarounds desperately welcome. Thanks.
1. Try posting about your issues in Taiwanese Asus forums under this topic:
https://www.asus.com/zentalk/tw/thread-216020-4-2.html
Use Google Translator in order to navigate the Taiwenese forum. Post your message in English.
2. Try posting about your issues in XDA Asus Zenfone 3 forums (regular Zenfone 3, not Zenfone 3 ultra), because regular Zenfone 3 community is larger, however devices should be quite similar:
https://forum.xda-developers.com/zenfone-3
As always, keep Zenfone 3 ultra community informed with your future findings, so we all could learn something new and help each other.
i have mate 9 and i wanted to root it.
i have rooted the device using twrp and flashed the SuperSu and the device reboot with totally different theme and with full internal Storage(which was in fact empty).
when ever u try to download a picture from whatsapp or using any other way or even restore ur data. the apps will be restored but nothing will be restored to the gallery or to the music and the phone will asks you to free up some space.
any way i got frustrated as i was new to this, so i was trying to just get my phone back to stock. So what i stupidly did was locking the bootloader. and by doing that the phone deleted the twrp and locked the FRP. till this point i knew that i bricked the phone.
i tried many ways to get the phone but i could not. i found DC phoenix and they offering you flashing anything with no matter of ur device situation. so i went with their offer and i got the phone working on the last version i was having before looking the bootloader.
but i have a new problem now which is IMEI is 0000000000000. and the serial number is 0123456789ABCDEF.
they also offer a service called HCU to restore IMEI and SN. but it all lies and the software will never even run.
so im stuck in this stage and i dont dont know how to fix my phone. as the sim cards has been locked as the problem above appears.
anyone can help.
Sorry, but you've got a big problem. Even if you were to restore your IMEI using something like HCU, which, by the way, I think is not allowed to be discussed on this forum, it doesn't do a good enough job, and you end up without 3G connectivity or the ability to make phone calls, from my experience.
You might get better answers talking to DC directly?
im sorry if this is in the wrong section but ,ok so i bought an open box galaxy s6 from becetech online and it would not let me update the firmware past 5.1.1 which made me a bit suss, downloaded root checker app and it came too me rooted. apart from not being able to update the firmware past 5.1.1 as far as im aware the phone has no issues and works perfectly fine. i downloaded the *samsung* phone info app, in general under manufacturer it says Samsung/verizon so im assuming that is part of the reason they rooted the phone as it needed to be unlocked from verizon to be refurbished? so what i want to know is how do i find out exactly what becetech have done to the phone and is there an easy way for me to update the firmware to nougat or at least marshmallow without stuffing the phone, like i said the phones running fine its just really bugging me not being to update. obviously im not able to work it out myself but i can follow instructions so any help from someone would be greatly appreciated so thank you in advance.
Benno81 said:
im sorry if this is in the wrong section but ,ok so i bought an open box galaxy s6 from becetech online and it would not let me update the firmware past 5.1.1 which made me a bit suss, downloaded root checker app and it came too me rooted. apart from not being able to update the firmware past 5.1.1 as far as im aware the phone has no issues and works perfectly fine. i downloaded the *samsung* phone info app, in general under manufacturer it says Samsung/verizon so im assuming that is part of the reason they rooted the phone as it needed to be unlocked from verizon to be refurbished? so what i want to know is how do i find out exactly what becetech have done to the phone and is there an easy way for me to update the firmware to nougat or at least marshmallow without stuffing the phone, like i said the phones running fine its just really bugging me not being to update. obviously im not able to work it out myself but i can follow instructions so any help from someone would be greatly appreciated so thank you in advance.
Click to expand...
Click to collapse
Could someone with a bit more knowledge please tell me if the reason I can't update the firmware is because the firmware csc is TGY when I'm in Australia or just because it's rooted or what? I'm getting no answers from the company who I bought it off
Benno81 said:
Could someone with a bit more knowledge please tell me if the reason I can't update the firmware is because the firmware csc is TGY when I'm in Australia or just because it's rooted or what? I'm getting no answers from the company who I bought it off
Click to expand...
Click to collapse
Are you trying to update via the phone update feature? If so this won't work as rooting disabled the ability Update using ota
First I tried OTA then downloaded samsung smart switch and gave that a go both no good. What I want to know is, if they had to root the phone to refurbish it will it brick it if I try to update? Won't it reset all the company I bought it off has done to it to refurbish it? Which I'm guessing is quite a process as when I look at the open source licenses there's a long list of files that have been changed. It just sucks that it's locked to a three year old version of the firmware that I'm worried apps will start to stop supporting in the near future? Apart from that I can not fault the phone there's been no problems, maybe I'm asking a bit much for a $400 phone?
Benno81 said:
First I tried OTA then downloaded samsung smart switch and gave that a go both no good. What I want to know is, if they had to root the phone to refurbish it will it brick it if I try to update? Won't it reset all the company I bought it off has done to it to refurbish it? Which I'm guessing is quite a process as when I look at the open source licenses there's a long list of files that have been changed. It just sucks that it's locked to a three year old version of the firmware that I'm worried apps will start to stop supporting in the near future? Apart from that I can not fault the phone there's been no problems, maybe I'm asking a bit much for a $400 phone?
Click to expand...
Click to collapse
From what I can tell you have a g920v variant if the phone Shows Verizon but the sure fire way to know what variant you have is turn the phone off once off hold home-power-volume down, this will take you to download mode but should tell you your variant. You don't need to root a phone to refurbish It, you can flash Stock firmwares via Odin. I really don't know why they would have Rooted It tbh, you'd need to contact them, but I know for sure you can manually download the latest Verizon firmware and the phone should work. Maybe they Rooted it as part of making it network unlocked, o really can't say
Ok I tried that and a bright blue screen came up warning about custom OS then press up volume for download and down volume for reset? I just pressed down as there was no other info on the screen but it does say it's a sm-g920v in the settings as well as the root checker app. Another thing was I did ring samsung support gave them the serial number and IMEI and they said an authorized modification had been done on the phone but could offer no other support as it wasn't an Australian phone. I'll keep trying to get some info out of the company I bought it off and try to sort it out thanks for your help :good:
I don't know if it's permitted or not but I'm in search of the system firmware so if anyone could help I'd be grateful. I know it's unreleased but let's just say I've got the prototype lying around. Thanks in advance.
Doesn't exist. Ideally, you would dump the firmware yourself from the phone.
Now that the phone is released, stock images should be available soon here:
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
kobiandy said:
I don't know if it's permitted or not but I'm in search of the system firmware so if anyone could help I'd be grateful. I know it's unreleased but let's just say I've got the prototype lying around. Thanks in advance.
Click to expand...
Click to collapse
Since Google bricked your phone remotely with the hardware ID (since you got one of the dev models before release), it will be quite difficult to get it running again, a simple firmware flash will probably not do the trick.
And even if you'd manage to get a firmware running, you will not be able to go online, since Googles system has flagged your hardware ID and just brick it again. The only hope you have really is to wait for a custom kernel/OS and use that, IF you can actually manage to flash any sort of data on that phone. Was the bootloader still locked when Google bricked your device?
Morgrain said:
Since Google bricked your phone remotely with the hardware ID (since you got one of the dev models before release), it will be quite difficult to get it running again, a simple firmware flash will probably not do the trick.
And even if you'd manage to get a firmware running, you will not be able to go online, since Googles system has flagged your hardware ID and just brick it again. The only hope you have really is to wait for a custom kernel/OS and use that, IF you can actually manage to flash any sort of data on that phone. Was the bootloader still locked when Google bricked your device?
Click to expand...
Click to collapse
No it was never locked to begin with. Does this mean even original stock firmware( when released) won't work?
kobiandy said:
Does this mean even original stock firmware( when released) won't work?
Click to expand...
Click to collapse
That is highly likely, but don't let me stop you from trying. Maybe you will have success. Also keep your eyes out for the Android Flash tool or the Pixel Repair tool, once Google updates them for the P7 Pro. Big companies usually not have all the tools interconnected, so chances are that the Repair tool won't check for blacklisted hardware IDs, it's just important that under no circumstances you may connect to the Internet with that thing, IF you manage to get it running and as long as it runs stock.