Hi Guys, I'm super stoked to post that I have just modded my stock ASUS TF300TG 4.1.1 to enable voice calls from the on board sim. Not VOIP, not Groove IP or SIP from the mobile number from the sim!!!
I was one of the unfortunate few who purchased this device in hast when it was on special. I was searching for an all-in-one unit. 7” was too small, single core wasn’t enough, no expandable memory, no thank you. I read that this device had at one stage using Hydro 4.4 firmware which enabled voice. So I knew it was possible. Even though people who reported it working stated that it only truly works via a Bluetooth headset, but that’s what I wanted anyways. Besides, who wants to have a 10” tablet to the side of their face while on the phone, people might think you’re mad.
What I didn’t know in my hast, was the sleepless nights that would follow by simply pressing OK to an ASUS update from 4.0.3 to 4.1.1 would cause.
Here are some facts I have learnt along the way.
NVFLASH is unit specific.
NVFLASH can be install on JB, but because of the above, can’t go back to ICS anyway unless to installed it while you were on ICS and made the files then.
Why go back, once you update to JB, ASUS enables signing which prevents you from installing HYDRO 4.4 or stock ICS anyway.
No one makes ROMS for TF300TG, sad news get over it. I had to. If they do, none enable the phone function, or disabled 3G all together or have reported nothing but issues when it was enabled.
My only option was then clear, make my only rom or mod to do it myself with stock 4.1.1.
This is what I have installed currently, any other variation has not been tested and I will not be held responsible for bricking your device if you wish to test this on your device!!!
I have stock ASUS WW_epad-10.4.3.9 firmware
I have rooted my device via the motochopper method
I have unlocked my bootloader via the official unlocker from ASUS v7
I have installed openrecovery-twrp-2.6.3.0-tf300tg-JB and BACKED UP EVERYTHING BEFORE PROCEEDED!!
I will not bore you will all the different ways I tried, how many soft bricks or hours I spent learning from knowing nothing about Android or cooking as this is my first android device. So here is what worked.
I can’t attach the TWRP update.zip of the end result until I reach 10 posts, but if I give you a fish, you’ll eat for a day, but if I teach you how to fish, you’ll eat for a lifetime.
Hunt down the following tools on your PC (WILL POST SOURCE LOCATIONS ONCE AGAIN WHEN I REACH 10 POSTS) (ALSO I KNOW THIS SHOULD BE IN THE DEV SECTION, CAN’T POST THERE UNTIL 10 POSTS EITHER) Please don’t ask:
FrameworkFlasher-MOD 1.1.4 to generate installable zips to push changes
Apktool to decompile and recompile apk packages
JAVA JDK 1.7
WinRAR
Notepad++ (regular notepad / wordpad might add artifacts to your file and “F” with things)
Install the following on your tablet, FX with the root explorer add-on both free
Using FX on your device copy the following file located under /system/framework/framework-res.apk to a USB device.
Copy into the folder of Apktool on your PC and run the following commands from the command line:
apktool.bat if framework-res.apk
apktool.bat d framework-res.apk
(keep command prompt open)
This will create a folder called "framework-res", navigate to that folder and open "framework-res\res\values\bools.xml”
In here you’ll find a line "config_voice_capable">false
Change false to true
Save file.
Rebuild the apk by running from the command line
apktool.bat b framework-res framework-res-new.apk
Here is a trick I learnt to overcome the countless soft-bricks which followed and disappointment of being stuck on the boot screen.
Open "framework-res-new.apk" with a program such as WinRAR and extract out the file called "resources.arsc".
Once that’s done open the original unmodified framework-res.apk with WinRAR and replace "resources.arsc" with the one you extracted from the last step. (make sure you keep a backup of the original framework-res.apk before modifying it a.k.a framework-res-orig.apk)
Now create the update.zip or push via abd
It is kind of just making the shell zip to copy your mod into as I created this from a previous attempt at enabling phone functionality.
Copy your original framework-res-orig.apk into the FrameworkFlasher-MOD\place-framework-res-here folder
Run the RunMe.bat file and select option 1, then 2, then 3 and then 4. Signing kills the file, but we have to, to create a shell update.zip
Go into the FrameworkFlasher-MOD\final-zip-file
There you’ll find your ~5MB update file. Open this via WinRAR and head to \system\framework.
Override the framework-res.apk file with the file we created with apktools.
Side note: rename the framework-res-orig.apk to framework-res.apk and create another update.zip with your original framework-res.apk file a.k.a framework-res-orig.apk and call it updatefix.zip. This is just in case this doesn't work for you, you can just use this to reinstall your original file back. Saved me time and from having to restore my device repeatedly.
Copy to your Device and install via TWRP.
Note I did a wipe of cache and Dalvik, but for some reason google play had issues. Stating that google play had stopped, and whenever I tried to install would be stuck at installing for what appears to be infinity.
As this device is only a few days old had nothing on it, so I did a factory reset and everything including voice calls started working correctly.
You have been warned!!
Now shop for a bluetooth headset and happy voice calls.
Happy days 10 posts reached. Attached are the update files for 10.6.2.10 stock ASUS rom. I don't have them for 4.1.1. Please backup your framework-res.apk file first and place it in the updatefix.zip file under system/framework just in case. Update via recover install from zip method. Wipe cache and Dalvik.
Updateshell.zip is just an empty zip that you can't then use to install other changes.
Update
NVFLASH appears to require people to update as close to the JB Bootloader as possible before NVFLASH will work correctly. A handful of people have reported issues when not running 10.6 JB bootloader.
Will update to 10.6 JB and create a backup of my device. Will then trail my patch again if not, will run through the NVFLASH process to go back to 10.4 JB.
Moving forward, I will slowly as far as time permits, to add more features to the stock rom for TF300TG enabling the phone and other enhancements. Will keep you all posted.
Upgrading from 10.4.3.9 to 10.6.2.10
For those of you worried about having JB 4.1.1 with TWRP 2.6.3.0 JB installed and wanting to update to 4.2.X but fear that because you have a custom recovery installed not sure how to upgrade. The easiest way is to use fastboot and download the latest firmware from ASUS.
As part of the blob you download from ASUS contains the bootloader, system, recovery and boot partitions. So it doesn't matter what version you are running, all the before mentioned with be updated with stock 4.2.
All you have to now remember is to reflash your TWRP with the 4.2 version.
I will upgrade shortly and then reflash my patch and confirm whether it works with 4.2. If so I with move onto adding some other useful mods.
Flashed to 10.6.2.10 broke everything
Updated to 10.6.2.10 via fastboot to the staging partition. The blue bar filled and the command ended. Issue a fastboot reboot to reboot device.
Flashed TWRP 2.6.3.0 4.2 but this never made it into recovery. Reverted back to TWRP 2.5.0 4.2 and all is well.
Tried to update the framework-res.apk which broke everything. Bootloop
Had to recompile via the same method above, but also failed stating invalid resource directory. Still haven't found a solution to completely recompile back to an APK. Was told to simply remove the affected folder and later add to the APK via WinRAR. Removing the folder allowed me to recompile, however as this is a Value folder which gets complied into resources.arsc so you can't add it later.
Flashed with the newly created 4.2.2 and phone function is enabled, but still am working on completely compiling the APK.
Heard it could also be a aapt.exe issue. Downloading the SDK 17 to recompile again.
It's been a day now and I haven't seen any side effects from deleting the values-mcc454-mnc-1 folder so that I can't compile the apk. Still haven't found a solution to the problem. Framework-res.apk appears to be version specific so you will really have to compile it yourself following the steps in my first post, otherwise you'll get stuck with a bootloop device.
Has anyone come across a: invalid resource directory name when recompiling 10.6.2.10 framework-res.apk? If so could you please post a working aapt.exe and which compiler you used.
Thanks in advance.
Built the frame-res.akp in full
Just an update, was able to fully compile the framework-res.apk file.
Was looking at it all wrong. The build process only failed at one directory. Looked at all other value folders and noticed that it was only this folder that had a mnc-1 where others had a mnc1, mnc7, mnc10 none had a -1 or other number. Corrected the folder to values-mcc454-mnc1 compiled correctly. Must be a glitch when decompiling.
Cooking the TF300TG
Started cooking my first rom, some tips so far.
Followed http://forum.xda-developers.com/showthread.php?t=1801690
To set up the kitchen. Step 1 only
Downloaded 10.6.2.10 from ASUS Extracted both zips, as in the zip within the zip
Used http://forum.xda-developers.com/showthread.php?t=1890912 on the blob file
BlobUnpack.exe blob
This gives you a number of files
blob.HEADER – Header stuff (ignore it)
blob.APP – system.img
blob.LNX – boot.img
blob.SOS – recovery.img (e.g. regular boot.img)
blob.EBT – bootloader.bin (ignore)
Rename each the matching.
Past the renamed files into the kitchen original_update
Setup working directory... TBA
Boy who cried wolf
Hmmm....it appears that I have hit another road block. I finally got my Bluetooth earpiece, paired the two, made a call and no sound....
After another night of trolling the forums found that all I have really done is tell android that this device is voice enabled, which simply allows you to access the phone app and that there could be a lot more I have yet to discover which could be stopping this from working.
Now I love all the comments people have made in regards to the fact that similar devices have been out for a while now and that people much smarter then you have been trying to crack what appears to be the 'Da Vinci code' over this time and that if they can't do it, then essentially it isn't going to happen.
But I also love one comment I came across "Hope dies last"
I have read an interest forum http://forum.xda-developers.com/showthread.php?t=2025377 all 46 pages of what appeared to be a group of very clever people trying to get the Nexus 7 3G to do the same. From my understanding of the forum is that they started out with a device which has what appears to be no telephony beyond data via 3G. AKA no SMS or MMS or voice. They managed to get SMS and MMS but never VOICE.
Why not stop there then? Well from what would appear to be to the more experienced devs here as a simply party trick on my part to change one Boolean value in the framework-res.apk file to true I have learned the following a parts from the fact that SMS and MMS worked out of the box, but also that by putting in my mobile phone sim into my voice capable enable device the following works:
The phone apps loads
I can dial and the call reaches the other mobile and displays my number
I can call my mobile number and my tablet rings
I can answer and hang up
So most of the underlying functionality appears to be active. What doesn't work:
When I answer, there is no sound from the tablet or Bluetooth
The people on the other end can't hear me from the tablet or Bluetooth.
Why did I cry wolf, well with all the functionality appeared to working, with someone claiming to have had this working only via Bluetooth already and another device apparently having it working via a similar method got me over excited.
The road block currently is the follow:
Software
Or hardware AKA the connection between the 3G and sound hardware is not linked, which I thought that having a Bluetooth device would overcome as my thinking was the following. Bluetooth would create it's own software sound device which will send the audio to the 3G via software bypassing the hardware, but I could be wrong in this way of thinking. When I have the Bluetooth paired, when I dial I hear that the Bluetooth device activates and dis-activates when I hang up, so the tablet is communicating and I suspect transmitting sound.
Or the biggest problem, IMEI is black listed by the courier, which I didn't think was the case as why would I be able to dial and connect to another number if I was blacklisted?
So it kind of leaves me to wonder if it's only really software, a link of profile missing in the Bluetooth stack, the my device has my headset listed as "Use for phone audio"
Moving forward I will get NVFLASH and the blob files created as I fear flashing anything I have created myself without a fail-safe way of getting my device back. Play a little with the build.prop file and retrace the step then ended with the forum I read to see if I am about to get any further as as far as I can tell it's more software at this stage.
Anyone could shed some light on this?
It's nice job bro.
I admire you
you try hard to challenge with this issue
I learn many thing from you
tnx
sadly it doesn't work
continue your job I believe on you and I proud to you
freak4916 said:
Hi Guys, I'm super stoked to post that I have just modded my stock ASUS TF300TG 4.1.1 to enable voice calls from the on board sim. Not VOIP, not Groove IP or SIP from the mobile number from the sim!!!
I was one of the unfortunate few who purchased this device in hast when it was on special. I was searching for an all-in-one unit. 7” was too small, single core wasn’t enough, no expandable memory, no thank you. I read that this device had at one stage using Hydro 4.4 firmware which enabled voice. So I knew it was possible. Even though people who reported it working stated that it only truly works via a Bluetooth headset, but that’s what I wanted anyways. Besides, who wants to have a 10” tablet to the side of their face while on the phone, people might think you’re mad.
What I didn’t know in my hast, was the sleepless nights that would follow by simply pressing OK to an ASUS update from 4.0.3 to 4.1.1 would cause.
Here are some facts I have learnt along the way.
NVFLASH is unit specific.
NVFLASH can be install on JB, but because of the above, can’t go back to ICS anyway unless to installed it while you were on ICS and made the files then.
Why go back, once you update to JB, ASUS enables signing which prevents you from installing HYDRO 4.4 or stock ICS anyway.
No one makes ROMS for TF300TG, sad news get over it. I had to. If they do, none enable the phone function, or disabled 3G all together or have reported nothing but issues when it was enabled.
My only option was then clear, make my only rom or mod to do it myself with stock 4.1.1.
This is what I have installed currently, any other variation has not been tested and I will not be held responsible for bricking your device if you wish to test this on your device!!!
I have stock ASUS WW_epad-10.4.3.9 firmware
I have rooted my device via the motochopper method
I have unlocked my bootloader via the official unlocker from ASUS v7
I have installed openrecovery-twrp-2.6.3.0-tf300tg-JB and BACKED UP EVERYTHING BEFORE PROCEEDED!!
I will not bore you will all the different ways I tried, how many soft bricks or hours I spent learning from knowing nothing about Android or cooking as this is my first android device. So here is what worked.
I can’t attach the TWRP update.zip of the end result until I reach 10 posts, but if I give you a fish, you’ll eat for a day, but if I teach you how to fish, you’ll eat for a lifetime.
Hunt down the following tools on your PC (WILL POST SOURCE LOCATIONS ONCE AGAIN WHEN I REACH 10 POSTS) (ALSO I KNOW THIS SHOULD BE IN THE DEV SECTION, CAN’T POST THERE UNTIL 10 POSTS EITHER) Please don’t ask:
FrameworkFlasher-MOD 1.1.4 to generate installable zips to push changes
Apktool to decompile and recompile apk packages
JAVA JDK 1.7
WinRAR
Notepad++ (regular notepad / wordpad might add artifacts to your file and “F” with things)
Install the following on your tablet, FX with the root explorer add-on both free
Using FX on your device copy the following file located under /system/framework/framework-res.apk to a USB device.
Copy into the folder of Apktool on your PC and run the following commands from the command line:
apktool.bat if framework-res.apk
apktool.bat d framework-res.apk
(keep command prompt open)
This will create a folder called "framework-res", navigate to that folder and open "framework-res\res\values\bools.xml”
In here you’ll find a line "config_voice_capable">false
Change false to true
Save file.
Rebuild the apk by running from the command line
apktool.bat b framework-res framework-res-new.apk
Here is a trick I learnt to overcome the countless soft-bricks which followed and disappointment of being stuck on the boot screen.
Open "framework-res-new.apk" with a program such as WinRAR and extract out the file called "resources.arsc".
Once that’s done open the original unmodified framework-res.apk with WinRAR and replace "resources.arsc" with the one you extracted from the last step. (make sure you keep a backup of the original framework-res.apk before modifying it a.k.a framework-res-orig.apk)
Now create the update.zip or push via abd
It is kind of just making the shell zip to copy your mod into as I created this from a previous attempt at enabling phone functionality.
Copy your original framework-res-orig.apk into the FrameworkFlasher-MOD\place-framework-res-here folder
Run the RunMe.bat file and select option 1, then 2, then 3 and then 4. Signing kills the file, but we have to, to create a shell update.zip
Go into the FrameworkFlasher-MOD\final-zip-file
There you’ll find your ~5MB update file. Open this via WinRAR and head to \system\framework.
Override the framework-res.apk file with the file we created with apktools.
Side note: rename the framework-res-orig.apk to framework-res.apk and create another update.zip with your original framework-res.apk file a.k.a framework-res-orig.apk and call it updatefix.zip. This is just in case this doesn't work for you, you can just use this to reinstall your original file back. Saved me time and from having to restore my device repeatedly.
Copy to your Device and install via TWRP.
Note I did a wipe of cache and Dalvik, but for some reason google play had issues. Stating that google play had stopped, and whenever I tried to install would be stuck at installing for what appears to be infinity.
As this device is only a few days old had nothing on it, so I did a factory reset and everything including voice calls started working correctly.
You have been warned!!
Now shop for a bluetooth headset and happy voice calls.
Happy days 10 posts reached. Attached are the update files for 10.6.2.10 stock ASUS rom. I don't have them for 4.1.1. Please backup your framework-res.apk file first and place it in the updatefix.zip file under system/framework just in case. Update via recover install from zip method. Wipe cache and Dalvik.
Updateshell.zip is just an empty zip that you can't then use to install other changes.
Click to expand...
Click to collapse
I was wondering, the update files you uploaded, are they simply run and go?
I installed the update file you provided. I do, indeed, have a dialer. I recieve incomming calls and can make them too. but no audio. I have a bluetooth headset, is there anything else I can try?
how can that mod be for 4.2.2 if the last version asus released was 4.2.1 asus rom 10.2.6.11 ?
edit:
[changes the framework-res.apk and did changes ,got telephone app but i always get connection problem]
edit2:
[phonecalls are working at first i tried a mmi code *100# now i will retry with a bt headset]
edit3:
[get no sound if i get a call or place a call the call connectes fine but i cant hear me even with a bt headset, im going to backup via twrp now and then make a factory reset maybe that will help]
edit4:
[im drunk and i can report that its not working indded you can place a call the call connects but you cant hear one word or speak tried to call to my nexus 4 from tablet and other way around]
Hi, I have tf300tg and I was wondering too if I can make voice calls. I will try it and make you feedback I hope. My tablet is rooted and I have tested android 5.1 (cyanogenmod) but there is no 3G support. I have returned original 4.2 and try voice call. Sorry for bad english.
Related
I made this for all the people that seem to be having issues with rooting their phone, installing the recovery partition, and installing the new rom.
This is an all-in-one package. It's about 200MB. Includes the original root rom, recovery image, the new rom (2.1OTA rom that was just released today), as well as a few extras. It's a batch script to automate the entire process.
Here's the README file:
Code:
These are automated scripts to root your Eris phone with Android 1.5 (NOT 2.1 LEAK!!!!!)
YOU NEED THE ANDROID SDK IN ORDER FOR THIS TO WORK!
If you don't have the SDK working, visit guide on the forums for instructions.
INSTRUCTIONS:
Unzip this file to your \tools\ directory of your Android SDK. Then run one of the following files:
install_root.bat
------------------------
This script will do the following:
1) Install the root image onto your phone
2) Install the recovery partition onto your phone
3) Install the current rom using the recovery partition
install_extras.bat
------------------------
This script will do the following:
1) Install live wallpapers
2) Install the Nexus Launcher
3) Install the Nexus photo gallery
4) Remove HTC Lockscreen
5) Install wireless tethering
NOTE!
------------------------
1) NOT ALL LIVE WALLPAPERS YOU FIND IN THE MARKET WILL WORK!
2) You cannot use the Nexus photo gallery when in the Nexus Launcher, it will crash
These scripts were put together by GrdLock.
Credit for all of the included files goes to ivan, amon, jcase, and everyone else
who chipped in!
Install this by unzipping it into your \tools\ directory of your Android SDK, then run install_root.bat.
I'm not running Windows so I didn't test this, but I proof read it like 10 times, and I'm 99.99% sure it should work 100%. If anyone gets any errors using it, post and I'll fix them immediately. Make sure USB debugging is turned on before running it.
You can download the whole package here: http://www.multiupload.com/Y7UC8UU2JE
-------------------------------------------------------------------
If you just want the 2.1OTA rooted rom, you can download that here: http://www.multiupload.com/YP1BIUOF60 (this rom includes busybox, the otacert fix, and a few other minor things)
I also put together an update. This will update you to the new 2.1 OTA leak "official" without wiping. Wipe your dalvik and that's it. Do a nand backup first though just incase! http://www.multiupload.com/3OPZCD6NRA
GrdLock said:
I made this for all the people that seem to be having issues with rooting their phone, installing the recovery partition, and installing the new rom.
This is an all-in-one package. It's about 200MB. Includes the original root rom, recovery image, the new rom (2.1OTA rom that was just released today), as well as a few extras. It's a batch script to automate the entire process.
Here's the README file:
Code:
These are automated scripts to root your Eris phone with Android 1.5 (NOT 2.1 LEAK!!!!!)
YOU NEED THE ANDROID SDK IN ORDER FOR THIS TO WORK!
If you don't have the SDK working, visit guide on the forums for instructions.
INSTRUCTIONS:
Unzip this file to your \tools\ directory of your Android SDK. Then run one of the following files:
install_root.bat
------------------------
This script will do the following:
1) Install the root image onto your phone
2) Install the recovery partition onto your phone
3) Install the current rom using the recovery partition
install_extras.bat
------------------------
This script will do the following:
1) Install live wallpapers
2) Install the Nexus Launcher
3) Install the Nexus photo gallery
4) Remove HTC Lockscreen
5) Install wireless tethering
NOTE!
------------------------
1) NOT ALL LIVE WALLPAPERS YOU FIND IN THE MARKET WILL WORK!
2) You cannot use the Nexus photo gallery when in the Nexus Launcher, it will crash
These scripts were put together by GrdLock.
Credit for all of the included files goes to ivan, amon, jcase, and everyone else
who chipped in!
Install this by unzipping it into your \tools\ directory of your Android SDK, then run install_root.bat.
I'm not running Windows so I didn't test this, but I proof read it like 10 times, and I'm 99.99% sure it should work 100%. If anyone gets any errors using it, post and I'll fix them immediately. Make sure USB debugging is turned on before running it.
You can download the whole package here: http://www.multiupload.com/09DM1FI1D1
md5: 535c300411cd47acd319e667fee8cf16
-------------------------------------------------------------------
If you just want the 2.1OTA rooted rom, you can download that here: http://www.multiupload.com/5HH0H1M4T1 (this rom includes busybox, the otacert fix, and a few other minor things)
md5: 6d95e5e8846c6912fda42c54daa0cb34
I also made a kernel-only update that can be flashed without wiping anything: http://www.sendspace.com/file/5ptpmc
md5: cc4e95034dc7e8adaa776483251952bf
Click to expand...
Click to collapse
Thanks....I will be using this on the wifes (soon to be mine) phone tonite as with the new OTA update I now feel my phone is stable enough for her not to freak out over
appreciate your work....
does the script disable OTA's ?
rvpartsguy said:
Thanks....I will be using this on the wifes (soon to be mine) phone tonite as with the new OTA update I now feel my phone is stable enough for her not to freak out over
appreciate your work....
does the script disable OTA's ?
Click to expand...
Click to collapse
Yes, I built the otacert fix into the rom.
Thanks for all your work grid, and all the others that have worked on this. Just got a new refurb the other day and was going to tackle rooting this weekend, gonna make the task so much easier.
Can you please explain what was fixed? Thanks again for your work.
The current rom is a rooted rom using the new 2.1 leak that was just released today, which is SUPPOSEDLY the "official" 2.1 update from Verizon.
What setting should be used for the phone, HTC Sync, USB, Mount SD, or nothing?
Nothing. Just connect it to your USB, and enable USB debugging. Don't mount your sdcard.
Does the market work now?
(I recall hearing that the market wouldn't work because of the test/dev certificate that was in the leaked rom)
The market will work if it doesnt work now, itll work when the OTA comes out.
Grd, this looks fantastic. I've been patient so far, and haven't upgraded to the leaked or original rooted 2.1 builds, but with the news of the latest one (and initial reports saying that it's mostly bug-free), I'm ready to take the plunge. This should be a huge help to me.
A couple of questions:
Does the big package (the 200MB one) include jcase's ROM (bare-bones basic), or yours with the tweaks? I ask because you mentioned removing pdfviewer, which I use.
Also, has anyone else gone through this process yet? Call me timid, but I'm not too keen on being the first one.
K0CAW said:
Grd, this looks fantastic. I've been patient so far, and haven't upgraded to the leaked or original rooted 2.1 builds, but with the news of the latest one (and initial reports saying that it's mostly bug-free), I'm ready to take the plunge. This should be a huge help to me.
A couple of questions:
Does the big package (the 200MB one) include jcase's ROM (bare-bones basic), or yours with the tweaks? I ask because you mentioned removing pdfviewer, which I use.
Also, has anyone else gone through this process yet? Call me timid, but I'm not too keen on being the first one.
Click to expand...
Click to collapse
It includes my rom. You should be able to restore pdfviewer if you need it though. I can post the files in a bit.
Great. I was pretty sure that the apps could be reinstalled if needed, but wanted to confirm. I'm downloading the package now, so I'll keep you updated. I'm pretty excited about this, since I'm still at stock 1.5.
Issues, Well first It copied the PB image fine, it didnt reboot the phone i had to manually do it with vol -, now im on step two installing amons image, it transfers but it cant start files\flash_image, no such file or directory and then it cant chmod it cause its not there.
Could you copy/paste the command prompt text you're seeing? (you gotta right-click the cmd window and select Mark)
Installing Amon's Recovery Image.
1545 KB/s (3926016 bytes in 2.480s)
cannot stat 'files\flash_image': No such file or directory
Unable to chmod /system/bin/flash_image: No such file or directory
flash_image: not found
-
Finished
Your phone will now reboot and test the recovery partition.
Press any key to continue . . .
Ahh, crap...
http://www.sendspace.com/file/obtx2w
Download that file, put it in the \tools\files\ directory, then try again and let me know.
I think I got delete-happy removing some temp files and deleted flash_image by accident.
Worked great
I just went through the install.bat file and everything worked 100% just as promised. I have not installed any of the extras yet. Thanks for the great work!
flash_image was it worked a treat its in amon_ra now was trying manually and came across it missing, went to post it and you had just now
One suggestion before letting adb copy the 2.1 rooted img to the phone have it delete the PB so users dont accidently click on it. Just a lil cleanup to help things out. So far its flashing 2.1 rooted I will let you know about the first error, ill go back through it again and get it to recreate.
Hi just asking if anyone knows any links or archives or anything i can read through, im looking to build my own ROM. any help would be much appreciated and dont mind donating to someone that can help me start to learn.
Thanks
Well, first of all you need to be able to compile Android. This is pretty easy and it's explained directly in the developers google website. If you're not running a Nexus One or a Nexus S, you can't actually compile a working android copy for your own phone "as is" from AOSP. Because of this, you firstly need to change / create some dirs and files in order to add the support for your particular device. I'd start searching on CM repositories for this (I've got the Nexus One and thus I don't have such problems).
After you've compiled Android for your device and your changes (for example root), you'll have some disk images (you can find them all under out/target/product/PHONE_MODEL/, they are the .img files). You can directly flash them via fastboot ("fastboot flash boot boot.img" etc.). You can though create an update.zip file, and this can be made extracting the system.img file in a folder. Remember that you'll have to recreate the symlinks (to toolbox and/or busybox if you want to include it in your build) and set permissions, as zip doesn't save the permissions of the files once compressed.
Thus so far, if you succeed making every single step you should have your ROM on your phone
HI Guys,
Maybe somewhat can help me out here, in my attempt to update my Acer A500, I may have in a kind of way bricked my phone. I attempted to replace wpa_supplicant file as per some of the instructions, needless to say the update failed and me in my pure genius figure I would simply factory reset and reboot. Which I ended up doing, the problem now is that the WIFI does not turn on and my tab has been unrooted, I no longer have any file explorer app on the phone and I can't download anything. Does anybody know how I can gain access to the root files so that I may revert back the old file, or somehow install an apk file from the mini sdcard or even get access to the internet via bluetooth or USB. Anything would be helpful.
FYI - I am trying to gain access to my root files using Android SDK, but I've always had problems getting any of my pc to find any of the android stuff when plugged in.
Ph0tin0 said:
HI Guys,
Maybe somewhat can help me out here, in my attempt to update my Acer A500, I may have in a kind of way bricked my phone. I attempted to replace wpa_supplicant file as per some of the instructions, needless to say the update failed and me in my pure genius figure I would simply factory reset and reboot. Which I ended up doing, the problem now is that the WIFI does not turn on and my tab has been unrooted, I no longer have any file explorer app on the phone and I can't download anything. Does anybody know how I can gain access to the root files so that I may revert back the old file, or somehow install an apk file from the mini sdcard or even get access to the internet via bluetooth or USB. Anything would be helpful.
FYI - I am trying to gain access to my root files using Android SDK, but I've always had problems getting any of my pc to find any of the android stuff when plugged in.
Click to expand...
Click to collapse
I was in this court just yesterday, swearing up and down for some reason.
You'll need the root explorer apk, gingerbreak apk and the original wpa_supplicant file posted all over XDA.
Download and install Android SDK. It will also make you download the Java SDK too before you install the Android one. Start installing the Android SDK. It will seem like it's going to take forever, but you really only need what's in the folders 2 minutes in.
Go into the program files folder where the SDK stuff is and rip the 3 ADB files out and place them in their own folder. Mine were in: c:\program files\android\android-sdk\platform-tools\
I took the 3 files out and placed them in c:\and\
Place the apks in the c:\and\ folder
Make sure the driver files are installed from the Acer website.
Make sure USB bugging and apps from outside sources are enabled in settings on the tab.
Plug the tab into the PC via USB.
Open up the command prompt and go to the c:\and\ folder
then type
adb install c:\and\rootexplorer.apk
ENTER
then
adb install c:\and\gingerbreak-v1.20.apk
ENTER
The apps should be now installed on the tab.
Then just transfer the wpa_supplicant file over and you're right where you need to be.
Make sure you change the permissions on the wpa_supplicant file like you did the first time (enable everything read/write/etc etc) by holding on the wpa_supplicant file that you paste.
rorytmeadows said:
Open up the command prompt and go to the c:\and\ folder
then type
adb install c:\and\rootexplorer.apk
ENTER
then
adb install c:\and\gingerbreak-v1.20.apk
ENTER
The apps should be now installed on the tab.
Then just transfer the wpa_supplicant file over and you're right where you need to be.
Make sure you change the permissions on the wpa_supplicant file like you did the first time (enable everything read/write/etc etc) by holding on the wpa_supplicant file that you paste.
Click to expand...
Click to collapse
You are my new hero, all this time I've been trying to get Android ADK to recognize my tablet, but to no success. All I had to do was run ADB, which Ironically I had done, but only to see if it recognizes my unit. I was not aware I can install apps with it.
I'm not worthy... I'm not worthy
A million thank you's, now to try and get 3.1 installed and hopefully Googel/android was smart enough to put in a stock file explorer.
Not working wifi hardware
Somewhat similar to what happened to this guy. But to be specific, I am using an acer a500 originally on a rooted ics 4.0.3, i remember using lucky patcher and using the custom patch on adobe flash player then i saw an update regarding busybox and superSU...i was able to install the busybox updater but not the superSU since i remembered i already had superuser. I opened superuser and then it updated...from then on...I lost my wifi...at start it was still there but it can't connect. also, i lost my root because i no longer am able to use titanium backup. double checking it, i downloaded a root checker and it displayed not properly rooted. seeing this, i thought it's been a long time since i've updated my rom so i might as well upgrade everything...my bootloader, kernel, rom. So i first degraded it by flashing to the full package stock HC 3.1 ROM (it had an old HC 3.1 bootloader). Then i noticed i can no longer turn on my wifi and use my old apps...I flashed it back to a NON-rooted stock ics 4.0.3 thinking it might fix it...but it did not. HELP please...
Overview:
This thread is a guide on how to fix the apply_patch_check error message experienced during an upgrade of the Android OS. Specifically, this will detail the steps for an upgrade of Jelly Bean from 4.1.1 to 4.1.2 on the Nexus 7 with CWM Recovery for a user of Windows. I'm sure similar steps will work for other recoveries/upgrades/devices and PC OSes.
You should only bother with this if you don't want to flash the entire system.img file to your phone, which is way easier.
Here is an example of the error message I'm talking about:
Code:
assert failed: apply_patch_check("/system/app/Chrome.apk", "819b34b66335c6faec86404d736a002b8871600", "9d6b55e63b0bf20bea433fb1ee7089f88ab73fb6")
E: Error in /sdcard/03a4eaf95f73.signed-nakasi-JZO54K-from-JRO03D.03a4eaf9.zip
(Status 7)
Installation aborted.
A few notes about the error:
This doesn't have to happen with the Chrome.apk specifically -- it could happen with any app in /system/app or .so in /system/lib.
Those random strings of numbers/letters are SHA-1 hashes of the apk.
The first one is the hash of the apk installed on your device. In my example, this happens to be the version of Chrome that comes with JB 4.1.2.
The second one is the expected hash of the apk that comes with JB 4.1.1.
Cause of the problem:
The reason this error occurs is because the file was somehow modified from its original state. In my case -- and most likely your case -- this was done by Titanium Backup. TB has an option to "Integrate updates of system apps into ROM", which will cause the apk in /system/app (and associated library files in /system/lib, if needed) to be overwritten with the updated apk.
Solution:
Download this zip file which contains the full /system/app and /system/lib directory from the JB 4.1.1 factory image. *
Extract the zip to a location of your choosing on your PC.
In the extracted folder, locate the .apk or .so file referenced in the error message on your device.
Copy this file to your device via your preferred method (USB cable works fine). I put my file in /sdcard/Download.
On your device, use a root file explorer to move the file from /sdcard/Download to /system/app (or /system/lib).
If you don't have a program that can do this, I use ES File Explorer. Be sure to go to Settings > Root Settings and turn on Root Explorer, Up to Root, and Mount File System.
Reboot into your Recovery and try to install the update again.
Repeat steps 3-6 for each subsequent file that produces an error. You will basically need to do this for each app you integrated using TB and maybe a few library files, too. **
* Future updates (above 4.1.2):
Since I won't be keeping the zip file from step #1 up-to-date, here's how to get the directories that I included in the zip for yourself:
Obtain a factory image for your device's current Android version (the version you're updating from).
For JB 4.1.1, this file is called nakasi-jro03d-factory-e102ba72.tgz.
If you're reading this guide at a later date, the JB 4.1.2 file is called nakasi-jzo54k-factory-973f190e.tgz.
You can try your luck at the official Google site, but they seem to only provide the version you're trying to update to, not from.
Extract the .tgz file somewhere on your PC.
Locate the image-naksi-jro03d.zip file and extract that, as well.
In the folder you just extracted from the previous step, located the system.img file.
Download and use a program called sgs2toext4 (View attachment 645320) to convert the system.img to system.ext4.img. ***
Download and use a program called Linux Reader to open system.ext4.img.
Do this by going to Drives > Mount Image > Next > select your file.
It will then be listed under the Hard Disk Drives section in red as "Linux Ext Volume 1".
Navigate to: Linux Ext Volume 1/system.
Right-click on the app (or lib) directory and pick Save > Next > Output to dir of your choice.
You now have the directories that were included with the zip file from Solution step #1, so just follow those steps now.
** How to avoid repeating steps:
If you'd rather not have to try to reinstall after updating only one file, just to find another file that needs updating, try this:
Obtain the /system/app and /system/lib folders from the factory image and save them to your PC.
For the sake of this guide, let's say you save them to C:\factory_app and C:\factory_lib.
Copy the /system/app and /system/lib directories from your phone to your PC.
For the sake of this guide, let's say you saved them to C:\phone_app and C:\phone_lib.
Download the File Checksum Integrity Verifier utility from Microsoft.
Start > Run > cmd
fciv.exe -sha1 -xml factory_app.xml -wp C:\factory_app
fciv.exe -sha1 -xml factory_app.xml -v -bp C:\phone_app
Don't ask me why, but you need to use -bp instead of -wp for the second command.
Don't forget the -v on the second command.
The output of the last command will show you the list of files that are different. These are the files you need to take from C:\factory_app and put into the /system/app directory on your phone.
Do the same for the lib directories (just replace all instances of "_app" with "_lib" in the previous commands).
Summary:
I hope that this post helped some of you who really didn't want to have to flash the system.img or wipe your device just to update. In the future, use TB to back up the original.
I wouldn't normally bother writing up a guide like this (it took almost as long to write as it did to figure out how to do this) but I couldn't find this solution anywhere even though I saw that I wasn't the only person with the problem. Sorry for not posting this guide sooner (update has been out for a while now), but the forum required me to make a bunch of useless spam posts before I could include any links in my guide and I didn't get around to making those posts right away.
*** I would like to thank balamu96m for his guide on extracting data from the system.img file and drphrozen for making the sgs2toext4 program.
Thanks for this. Will try now.
Worked great. Had to copy the apk and odex file.
Good job! It's great to see the steps for Windows users!
Just a heads up that I simply extracted the files I needed from and on my N7 using Root Explorer, without using my PC at all.
Great guide! Method worked perfectly on my Nexus 7 going from 4.1.2 to 4.2, thanks
Please... is there some other way to update the files w/o installing Java on my Windoze PeeCee? I accidentally messed up my YouTube.apk with Titanium Backup... now I can't update from 4.1.2 --> 4.2 JB.
EDIT: JavaPortable FTW... updating (fingers crossed)
EDIT: SUCCESS TY OP!
For anyone who flashed the 4.2 clock/keyboard already
Hey, for anyone who flashed the 4.2 clock and keyboard on their Nexus 7 already and need to roll back to do the 4.2 update, I used OP's method to make a flashable zip that puts the 4.1.2 clock and keyboard back.
Worked perfectly for my Nexus 7 to get me up and running. Hope it helps anyone!
cantthinkofa.com/files/RestoreClockKeyboard.zip
galaxy nexus
Hi can you post a guide for galaxy nexus? Or if it is the same, can you post the link of JB factory image for galaxy nexus? Sorry, I can't find any thread for galaxy nexus, and I don't want to complete flash the stock image since I don't want to wipe my phone.
Thanks in advance!
Nice Guide
perfect, the guide works just fine. Now finally running 4.2.
Awesome guide... Thanks... Happily running 4.2 now aften beeing stuck at libutils.so...
Sent from my Nexus 7 using xda premium
damagno said:
Hi can you post a guide for galaxy nexus? Or if it is the same, can you post the link of JB factory image for galaxy nexus? Sorry, I can't find any thread for galaxy nexus, and I don't want to complete flash the stock image since I don't want to wipe my phone.
Thanks in advance!
Click to expand...
Click to collapse
I don't have a Galazy Nexus, but I think the steps should be the same. Here is a link to the factory images: https://developers.google.com/android/nexus/images#takju . It looks like they now have links for older versions, rather than just the newest images (which is how it was when I made my guide). So that's pretty sweet.
Thanks a lot man, i succeeded to "patch" my system files to update from 4.2 to 4.2.1. I first check what files didn't correspond with fciv (9 files counting both apks and odex) and then replaced them in system/app. In fact they were the apps I previously integrated with tb (learned lesson: never do it if you want to remain stock and receive OTAs). I also noticed many not-matching files in system/lib but i didn't touch them and the update went smooth the same.
Another thing: when in the OP you say it's way easier just to reflash the system.img you mean just run from bootloader "fastboot flash system system.img" (taken from the factory image as usual) or there's some other thing to do in order to fix the system partition in the right way?
GallStones said:
Thanks a lot man, i succeeded to "patch" my system files to update from 4.2 to 4.2.1.
Click to expand...
Click to collapse
I was wondering if you could tell me how you did it? I'm searching a way to install 4.2.1 with no avail as of yet :crying:
GallStones said:
Thanks a lot man, i succeeded to "patch" my system files to update from 4.2 to 4.2.1. I first check what files didn't correspond with fciv (9 files counting both apks and odex) and then replaced them in system/app. In fact they were the apps I previously integrated with tb (learned lesson: never do it if you want to remain stock and receive OTAs). I also noticed many not-matching files in system/lib but i didn't touch them and the update went smooth the same.
Another thing: when in the OP you say it's way easier just to reflash the system.img you mean just run from bootloader "fastboot flash system system.img" (taken from the factory image as usual) or there's some other thing to do in order to fix the system partition in the right way?
Click to expand...
Click to collapse
Yes. I am having the same issue. I cannot update mine from 4.2 to 4.2.1. I wonder to know which original stock image you have used. Can you list a detail procedure?
Thank you very much.
Ric
dev/block/param
legom said:
Overview:
This thread is a guide on how to fix the apply_patch_check error message experienced during an upgrade of the Android OS. Specifically, this will detail the steps for an upgrade of Jelly Bean from 4.1.1 to 4.1.2 on the Nexus 7 with CWM Recovery for a user of Windows. I'm sure similar steps will work for other recoveries/upgrades/devices and PC OSes.
You should only bother with this if you don't want to flash the entire system.img file to your phone, which is way easier.
Here is an example of the error message I'm talking about:
Code:
assert failed: apply_patch_check("/system/app/Chrome.apk", "819b34b66335c6faec86404d736a002b8871600", "9d6b55e63b0bf20bea433fb1ee7089f88ab73fb6")
E: Error in /sdcard/03a4eaf95f73.signed-nakasi-JZO54K-from-JRO03D.03a4eaf9.zip
(Status 7)
Installation aborted.
A few notes about the error:
This doesn't have to happen with the Chrome.apk specifically -- it could happen with any app in /system/app or .so in /system/lib.
Those random strings of numbers/letters are SHA-1 hashes of the apk.
The first one is the hash of the apk installed on your device. In my example, this happens to be the version of Chrome that comes with JB 4.1.2.
The second one is the expected hash of the apk that comes with JB 4.1.1.
Cause of the problem:
The reason this error occurs is because the file was somehow modified from its original state. In my case -- and most likely your case -- this was done by Titanium Backup. TB has an option to "Integrate updates of system apps into ROM", which will cause the apk in /system/app (and associated library files in /system/lib, if needed) to be overwritten with the updated apk.
Solution:
Download this zip file which contains the full /system/app and /system/lib directory from the JB 4.1.1 factory image. *
Extract the zip to a location of your choosing on your PC.
In the extracted folder, locate the .apk or .so file referenced in the error message on your device.
Copy this file to your device via your preferred method (USB cable works fine). I put my file in /sdcard/Download.
On your device, use a root file explorer to move the file from /sdcard/Download to /system/app (or /system/lib).
If you don't have a program that can do this, I use ES File Explorer. Be sure to go to Settings > Root Settings and turn on Root Explorer, Up to Root, and Mount File System.
Reboot into your Recovery and try to install the update again.
Repeat steps 3-6 for each subsequent file that produces an error. You will basically need to do this for each app you integrated using TB and maybe a few library files, too. **
* Future updates (above 4.1.2):
Since I won't be keeping the zip file from step #1 up-to-date, here's how to get the directories that I included in the zip for yourself:
Obtain a factory image for your device's current Android version (the version you're updating from).
For JB 4.1.1, this file is called nakasi-jro03d-factory-e102ba72.tgz.
If you're reading this guide at a later date, the JB 4.1.2 file is called nakasi-jzo54k-factory-973f190e.tgz.
You can try your luck at the official Google site, but they seem to only provide the version you're trying to update to, not from.
Extract the .tgz file somewhere on your PC.
Locate the image-naksi-jro03d.zip file and extract that, as well.
In the folder you just extracted from the previous step, located the system.img file.
Download and use a program called sgs2toext4 (View attachment 645320) to convert the system.img to system.ext4.img. ***
Download and use a program called Linux Reader to open system.ext4.img.
Do this by going to Drives > Mount Image > Next > select your file.
It will then be listed under the Hard Disk Drives section in red as "Linux Ext Volume 1".
Navigate to: Linux Ext Volume 1/system.
Right-click on the app (or lib) directory and pick Save > Next > Output to dir of your choice.
You now have the directories that were included with the zip file from Solution step #1, so just follow those steps now.
** How to avoid repeating steps:
If you'd rather not have to try to reinstall after updating only one file, just to find another file that needs updating, try this:
Obtain the /system/app and /system/lib folders from the factory image and save them to your PC.
For the sake of this guide, let's say you save them to C:\factory_app and C:\factory_lib.
Copy the /system/app and /system/lib directories from your phone to your PC.
For the sake of this guide, let's say you saved them to C:\phone_app and C:\phone_lib.
Download the File Checksum Integrity Verifier utility from Microsoft.
Start > Run > cmd
fciv.exe -sha1 -xml factory_app.xml -wp C:\factory_app
fciv.exe -sha1 -xml factory_app.xml -v -bp C:\phone_app
Don't ask me why, but you need to use -bp instead of -wp for the second command.
Don't forget the -v on the second command.
The output of the last command will show you the list of files that are different. These are the files you need to take from C:\factory_app and put into the /system/app directory on your phone.
Do the same for the lib directories (just replace all instances of "_app" with "_lib" in the previous commands).
Summary:
I hope that this post helped some of you who really didn't want to have to flash the system.img or wipe your device just to update. In the future, use TB to back up the original.
I wouldn't normally bother writing up a guide like this (it took almost as long to write as it did to figure out how to do this) but I couldn't find this solution anywhere even though I saw that I wasn't the only person with the problem. Sorry for not posting this guide sooner (update has been out for a while now), but the forum required me to make a bunch of useless spam posts before I could include any links in my guide and I didn't get around to making those posts right away.
*** I would like to thank balamu96m for his guide on extracting data from the system.img file and drphrozen for making the sgs2toext4 program.
Click to expand...
Click to collapse
my error 7 was generated by emmc: dev/block/mmdblk0p7 (the file is "param" any suggestions?
Thanks. After searching for a lot of time, this post helped me updating my SGS3.:victory: I previously tried to integrate youtube update into rom using titanium backup.
GallStones said:
Another thing: when in the OP you say it's way easier just to reflash the system.img you mean just run from bootloader "fastboot flash system system.img" (taken from the factory image as usual)
Click to expand...
Click to collapse
Yes, that's what I mean. The reason I didn't want to do this on my device is because I had modified some other system files that I wanted to keep the modifications for.
Wow, thanks a lot OP! Your guide helped me fixing an error during the update to 4.2.2 on my Nexus 4.
please include a video ,im getting lost in the details
solved.
Hello, I think I found what is the issue with WiFi - Vendor configs don't change WiFi Country code but they do change region and that causes the WiFi error. I was able to unpack the .RAW file to a normal folder and then the system.ISO where I was able to edit the build.prop and vendor props.
I prepared a few methods on how to edit the ROM to make WiFi work:
A) Changed the country code in the build.prop to a chosen country [you won't be able to use WiFi abroad of that country].
B) Edited all the vendor props to change WiFi country code to according countries [should work everywhere].
C) Removed the country code line from build.prop files [may work everywhere or nowhere]. -checked more files in the system and came to conclusion that this method won't work
The edited ROM will have to be flashed using Qualcomm flashing tool as there's no way to repack it to .RAW file.
For testers:
Before flashing copy all your files as they will be removed. Also mind the fact that I don't know if this will work or brick your device [if it does brick it then you can flash an unedited ROM to fix it].
Tutorial how to build your ROM:
1. Go to: https://drive.google.com/open?id=1Iph9eTL6dU_x_LAOt7Z9PN7KbwCAHACn
2. Download V570KL.rar
3. Go to Done2 folder and download system folder and IMG_EXTRACTOR_3.1 software from there. [For extractor software you'll have to download Java and Python]
4. Go to main folder and then go to Patch folder and go to Method C folder and download the folder with your country name [if it's not there contact me].
5. Locate your downloaded files and place them into one folder for easier work on them.
6. Unpack V570KL.rar
7. Copy build.prop file from country name folder and replace the build.prop in system folder with it.
PATCHING system.IMG
8. Open Img_Extractor [you need Python and Java for it to work], choose system.IMG and select Repack option. Now locate the edited system file. When it's selected check the byte number if it's the same as the one that system.IMG in V570KL folder has. If it's the same click Repack and wait till it does it's thing. [If the number is not the same edit it to the same number].
9. Replace the system.IMG in V570KL folder with our patched .IMG file.
PATCHING recovery.IMG
10. Reopen Img_Extractor software and choose recovery.IMG option.
11. Locate recovery.img [it's in V570KL folder].
12. Unpack the file, after unpacking locate the unpacked folder and go to initrd folder that's inside of it and there replace default.prop with default.prop located in country patch folder.
13. Go back to Img_Extractor and repack recovery.IMG
PATCHING ROM
14. Prepare edited system.IMG and recovery.IMG
15. Open V570KL folder and paste our patched IMGs in there [replace the old ones or remove them].
16. Our ROM is now ready.
*note - Img_Extractor has to be run with Admin rights to properly unpack/repack the files.
Flashing Tutorial:
QFIL flashing won't be possible as I couldn't get the needed Firehose file for it to work. There is however a Firehose file for V520KL [Asus Zenfone V] which might work but it's pretty risky to do.
A much safer method then will be to flash V570KL ENG rom first with Asus Flashing tool and on this rom we'll be able to unlock bootloader [open path to flashing edited roms].
There's also the VZW Repair Tool that could help us flash the phone, after the phone is detected the software will download OG Verizon ROM that can be replaced [in our case with the ENG ROM], after it's installed we will be able to flash the edited one.
Flashing tutorial downloads:
Asus Flashing Tool - https://www.asusflashtool.com/ [download version 2.0.1 and put your phone into recovery before connecting it to PC]
VZW Repair Tool - https://drive.google.com/drive/folders/15KAGi4XeKf8lwuJ46XO5LZ1mZLM7f5V1
V570KL ENG ROM - https://drive.google.com/open?id=1cizBJWHG1oDduMcImWAE_jSsbfQ5TJi6
Built ROM downloads:
MethodA - UA + camera2api + removed verizon features - https://drive.google.com/drive/folders/1g7jbq2UxQC1XFzqCUjfCa1XIVq23Vs14
MethodB - universal* + camera2api + removed verizon features - https://drive.google.com/drive/folders/1OYNjKjV8H2mhRpdyROgLCM7AeIxj0emw
MethodC - universal - not releasing
MethodC2 - universal + camera2api + removed verizon apps and features - not releasing
universal* - may not work in Ukraine and Russia as there were no vendor files for those countries in the system, however there was a file called EUCommon that may make it work
Update: I found a secret menu using this code in the dialer app which let's you turn OEM mode on [it should enable bootloader unlocking!].
Code: *#*#759#*#*
Hi friend, I have this phone. I will be glad to work together, I could not do everything according to your instructions. I guess I don't understand English well. I will be happy to work with you with the help of a team viewer. Please contact me
I edited the ROM but I don't know how to flash it, previous flashing methods for this model don't work anymore because of Asus disabling the only flashing tool with V570KL model, V2 doesn't support this model. I also thought of replacing the .RAW files in Verizon repair tool but I don't know if that would work, can't check that.
Anyway I added ENG rom link.
Hello!
So I just bought this phone online so my son could use Daydream. I'm not on Verizon and the plan was to just use WiFi. Well... I have the WiFi problem. I have worked though multiple other methods to try and find a fix and nothing has worked. I'm at the point where I'm about to try OP's method. Because of the possibility of bricking the device, wanted to check in first to see if anyone has continued to work on the problem or if there are any new developments. Once I make the decision to attempt, I will check in and after to let you know what happens.
Thanks!
Rk
Anyone know how to fix wifi issue on my v570kl without breaking it? I'm from ukraine.
Hi! I need your help solving WiFi problem for V570KL for country "UA". I downloaded your rar file from Google Drive along the path "Asus/Patch/Full_MethodA [Ukraine]/UA [Ukraine]/V570KL_edited.rar".
What do I do next? As I understand it, I need to launch the Asus Flash Tool, enter the phone in the recovery and connect the cable to the computer, then select the V570KL_edited.rar file and start flashing. I am asking for your help.
Well, I know this is a dead thread, still I'm coming here quite interested into recovering an investment in this phone I bought on Amazon, based in the replies of the questions of the product, saying it's unlocked... and surprise! As I placed a Movistar (VE) SIM on it for using, I found that I'm unable to use WiFi.
I've been following this steps for days (since Dec. 26, in fact) and everything has been dead end over dead end.
I can say that I've been looking for an stand-alone/offline version of AFT 1.0.0.72 with no success. I keep getting the error of 'Failed to download the version control file via FTP'.
I'm using 3 computers for this: a W7 32-bit notebook, a W10 64-bit desktop and a W11 64-bit laptop. I'm saying this, because... well, for some reason I've noticed about AFT v2:
In W7, it opens but doesn't recognize the phone battery
In W10, it doesn't even open
In W11, it goes smoothly and read phone battery
I'll add it is crucial AFT v2 reading phone battery (that means, phone turning on normally) because otherwise it doesn't do anything at all.
Anyway, when I tried flashing with AFT v2, it was a dead end because it did nothing (that was after program sending the phone into recovery mode). I tried to manually sideload it with 'adb sideload <filename>' with no success, getting an error message saying it can't read the file.
I opened the .zip files... surprise, .RAW files inside! I've used adb sideload before in Huawei phones, and I know the usual is to see .img files, so... I guess I need to decompress (somehow) the .RAW file. I'll take a look in that later.
Still, I want to attempt first the path suggested of VZWSUATool, just to see if I can somehow force it to install the ENG .RAW software. Right now I'm using the W11 64-bit laptop, but if compatibility problems arise, I'll jump back to W7 32-bit notebook.
Update 1 - 21:48 VET / 2023-01-03
Maybe VZWSUATool is another dead end. I've tried it first on the W11 64-bit laptop and it doesn't even starts (there are 2 library errors). I went back to W7 32-bit laptop, and... turned on normally does nothing, so I went into 'How to Repair...', put the phone into Fastboot but and after passing the FRP question, the "Unsupported device" window came up.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Update 2 - 22:19 VET / 2023-01-03
I decided to throw a risky attempt, basically crossing fingers at this point. I know the (sort of) equivalent model to our V570KL is ZS571KL. In AFT 1.0.0.45, the only option "close" to it is ZS570KL. Yeah, I was attempting something a bit absurd, but had not much to lose.
Another failed atttempt.
(Note: It was in Blue = Connected when it started)
Update 3 - 22:45 VET / 2023-01-03
Okay, apparently I'm heading into a new clue this time. Using the W11 64-bit laptop, I decided to force-choosing the .RAW file, and selected 'V570KL_all_VZW_user_V3.8.1.raw'
It recognized the file, rebooted into recovery, and this time recovery DID something. It was a failure, but what does surprise me is the file being, eh... succesfully sideloaded.
I'll try to sideload .RAW file 'V570KL_all_WW_eng_T3.0.6.raw' and see what happens.
Update 4 - 22:53 VET / 2023-01-03
Okay, I'll continue my attempts tomorrow. For now, with ASUS Zenfone Fash Tool V2.0.1.0, in the W11 64-bit Laptop (the only one in where it's working as it should, apparently) is giving the same error as in Update 3 for VZW .raw file, and WW .raw file does, ehm... nothing. I don't know what I'm skipping, I'll re-download the file and see what happens tomorrow after arriving home from work.
SlenderPL said:
Update: I found a secret menu using this code in the dialer app which let's you turn OEM mode on [it should enable bootloader unlocking!].
Code: *#*#759#*#*
Click to expand...
Click to collapse
After giving up for today, I decided to try this path, and...at least using standard unlocking methods, phone doesn't seem to understand what's happening, haha
ASUS guys really wanted to make this the most impossible, don't they?
Pedreo1997 said:
Well, I know this is a dead thread, still I'm coming here quite interested into recovering an investment in this phone I bought on Amazon, based in the replies of the questions of the product, saying it's unlocked... and surprise! As I placed a Movistar (VE) SIM on it for using, I found that I'm unable to use WiFi.
I've been following this steps for days (since Dec. 26, in fact) and everything has been dead end over dead end.
I can say that I've been looking for an stand-alone/offline version of AFT 1.0.0.72 with no success. I keep getting the error of 'Failed to download the version control file via FTP'.
I'm using 3 computers for this: a W7 32-bit notebook, a W10 64-bit desktop and a W11 64-bit laptop. I'm saying this, because... well, for some reason I've noticed about AFT v2:
In W7, it opens but doesn't recognize the phone battery
In W10, it doesn't even open
In W11, it goes smoothly and read phone battery
I'll add it is crucial AFT v2 reading phone battery (that means, phone turning on normally) because otherwise it doesn't do anything at all.
Anyway, when I tried flashing with AFT v2, it was a dead end because it did nothing (that was after program sending the phone into recovery mode). I tried to manually sideload it with 'adb sideload <filename>' with no success, getting an error message saying it can't read the file.
I opened the .zip files... surprise, .RAW files inside! I've used adb sideload before in Huawei phones, and I know the usual is to see .img files, so... I guess I need to decompress (somehow) the .RAW file. I'll take a look in that later.
Still, I want to attempt first the path suggested of VZWSUATool, just to see if I can somehow force it to install the ENG .RAW software. Right now I'm using the W11 64-bit laptop, but if compatibility problems arise, I'll jump back to W7 32-bit notebook.
Update 1 - 21:48 VET / 2023-01-03
Maybe VZWSUATool is another dead end. I've tried it first on the W11 64-bit laptop and it doesn't even starts (there are 2 library errors). I went back to W7 32-bit laptop, and... turned on normally does nothing, so I went into 'How to Repair...', put the phone into Fastboot but and after passing the FRP question, the "Unsupported device" window came up.
Update 2 - 22:19 VET / 2023-01-03
I decided to throw a risky attempt, basically crossing fingers at this point. I know the (sort of) equivalent model to our V570KL is ZS571KL. In AFT 1.0.0.45, the only option "close" to it is ZS570KL. Yeah, I was attempting something a bit absurd, but had not much to lose.
Another failed atttempt.
(Note: It was in Blue = Connected when it started)
Update 3 - 22:45 VET / 2023-01-03
Okay, apparently I'm heading into a new clue this time. Using the W11 64-bit laptop, I decided to force-choosing the .RAW file, and selected 'V570KL_all_VZW_user_V3.8.1.raw'
It recognized the file, rebooted into recovery, and this time recovery DID something. It was a failure, but what does surprise me is the file being, eh... succesfully sideloaded.
I'll try to sideload .RAW file 'V570KL_all_WW_eng_T3.0.6.raw' and see what happens.
Update 4 - 22:53 VET / 2023-01-03
Okay, I'll continue my attempts tomorrow. For now, with ASUS Zenfone Fash Tool V2.0.1.0, in the W11 64-bit Laptop (the only one in where it's working as it should, apparently) is giving the same error as in Update 3 for VZW .raw file, and WW .raw file does, ehm... nothing. I don't know what I'm skipping, I'll re-download the file and see what happens tomorrow after arriving home from work.
Click to expand...
Click to collapse
Update 5 - 16:40 VET / 2023-01-07
I took a break for a couple days for returning to this hell, and... let's see the progress so far:
* ASUS Zenfone Flash Tool V2.0.1.0 is doing nothing to help.
* I investigated there is a way to flash manually (using fastboot) the whole system, so it should be helpful, I think.
* Using a tool our friend SlenderPL left in the GDrive folder 'Asus Tool (RC4)', I unpacked the whole .RAW file. That was at first thinking into creating a .zip file to attempt another way to flash the ROM, but then I did found apparently it has more success chances trying to flash the stock rom, file by file, using 'fastboot flash' command, file by file. However, of course I need the tree, the .xml, the .bat file that tells me the order of how flashing it. It doesn't exist.
Right now I have a folder with the whole .RAW totally unpacked.
* I tried to force flashing, entering into Recovery, and then using sideload, writing:
adb sideload V570KL_all_WW_eng_T3.0.3.raw
Click to expand...
Click to collapse
of course, after placing the .raw file in the same folder of platform-tools on the computer. The phone did read the file, but again I got an error 'E:signature verification failed'.
Let's see whay newer idea I get...
Hello, I am the owner of 5 gadgets of this model and I want to solve the issue with Wi-Fi. For a year now I have been studying different options and trying to do the same. The last idea remains, but advice is needed. What if you remove the cover, find the pins for direct connection of the memory to the PC and simply replace the files in the hdd editor to work Wi-Fi?
wivelt said:
Hello, I am the owner of 5 gadgets of this model and I want to solve the issue with Wi-Fi. For a year now I have been studying different options and trying to do the same. The last idea remains, but advice is needed. What if you remove the cover, find the pins for direct connection of the memory to the PC and simply replace the files in the hdd editor to work Wi-Fi?
Click to expand...
Click to collapse
I think it's on the edge of fantasy. Try to do it, and if it works, write a detailed guide. I will be extremely grateful!