Database Users

TF300TG Voice Calls enabled on 4.1.1 now 4.2.2 also

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.

Guide for updating to 4.4 KitKat

Hello,
i have been reading guides all the day and no-one had a solutions to my problems so i would like to write my own to help out others who are encountering my same issues.
----------------------------------------------------------------------------------------
This guide is for Windows and explains everything you need to update your Nexus 7 (2013) Wifi (flo) from 4.3 JSS15R to 4.4 KRT16O
----------------------------------------------------------------------------------------
1) disconnect table from USB cables if it is connected to the pc
2) go http://developer.android.com/sdk/index.html and download the SDK
3) unzip the SDK in C\
4) go in C:\adt-bundle-windows and start the SDK Manager
let is load and scan for all possible updates.. when it has finished click on Deselect All then choose only these to packages:
Tools --> Android SDK Platform Tools
Extra --> Google USB Driver
if the Android SDK Platform tools are updated then you will only have 1 package to download else you will see Install 2 Packages, click it, then select Accept Licence and click Install.. wait it to finish and then close
5) let's now download the factory image
Nexus 7 2013 only WIFI (flo) "razor" is here: https://developers.google.com/android/nexus/images#razorkrt16o and download the first link of the page (4.4 (KRT16O) Link)
Nexus 7 2013 MOBILE/LTE (deb) "razorg" is here: https://developers.google.com/android/nexus/images#razorgkrt16o and download the first link of the page (4.4 (KRT16O) Link)
for some reason the MD5 checksum and SHA1 for the flo version dont match but i read people have been able to install this image anyway (i installed the OTA so i did'nt try this install)
unzip the downloaded file and you should get a .tar file.. unzip it again and you should get a bunch of files.. i got the following ones:
1)bootloader-flo-flo-03.14.img
2)flash-all.bat
3)flash-all.sh
4)flash-base.sh
5)image-razor-krt16o.zip
place all these files in C:\adt-bundle-windows\sdk\platform-tools\
6) now let's install the drivers correctly and flash the update
First thing, keep the Nexus 7 not connected to the USB cable. Then switch it on and go into Settings --> Storage click on the Options and choose USB computer connection and make sure to have the CAMERA (PTP) selected.
Now go into developer options and select Stay Awake and USB Debugging
Go back to the home screen and connect the tablet to the PC.. let the PC try to install it by himself.
Now press WINDOWS+R and run devmgmt.msc
If you see a device called Nexus 7 with a yellow sign then right click on it and choose Update software driver.
Then select the second option (find a driver on the computer), then select the second option (choose manually a driver from a list), now click first option (show all the devices), then click Driver disk button, then browse to C:\adt-bundle-windows\sdk\extras\google\usb_driver\ and choose android_winusb.inf and do ok.
The box should fill with a device called Android Composite ADB Interface, choose that and do next
To check if you have done right do:
WINDOWS+R and run cmd
in cmd do cd.. until you get into C:\
then do cd adt-(tab) to autocompile and enter
then do cd sdk enter
cd platform-tools enter
adb.exe devices enter
the daemon should start and you should get a list of devices attached showing you a code made of numbers and letters.. this is your nexus 7.
if cmd says the device is unauthorized then look at your tablet and allow the computer to operate
let's now install the driver also in fastboot so to do this always in cmd type
adb.exe reboot-bootloader
the tablet will reboot into the bootloader and you will see an android with the open tummy
now inside the command prompt window run the following commands:
fastboot flash bootloader bootloader-flo-flo-03.14.img
fastboot reboot-bootloader
fastboot -w update image-razor-krt16o.zip
if everything has gone right you should have updated using the factory image and the tablet should reboot by now...
else continue reading:
if you had any issues we can then try to update through OTA which means you will need to download another package
the nexus 7 ONLY WIFI OTA: http://android.clients.google.com/p....signed-razor-KRT16O-from-JSS15R.3a3951e8.zip
not sure if the nexus 7 LTE OTA url has been released or not because i can't find it.. if anyone has the link and can point it out to me i would be glad to add it here
download it and place it always in
C:\adt-bundle-windows\sdk\platform-tools\
rename it to something easier and redo
adb.exe sideload ota_zipfilename (enter)
everything should go fine now, so it will reboot.. configure the tablet again if it is the case
7) changing recovery
download latest recovery from here http://techerrata.com/browse/twrp2/flo
place the download img into C:\adt-bundle-windows\sdk\platform-tools\
then reboot to bootloader using adb or simply switch the table on keep vol down down
in cmd type
fastboot.exe flash recovery recoveryimagefile
8) rooting the tablet
btw sideloading the zip for rooting requires a custom recovery such as TWRP so step 7 must be achieved in order to root this way
download the latest superSU from here http://download.chainfire.eu/supersu
go into recovery mode passing by the bootloader
do another adb sideload passing this time the zip for supersu
everything done hopefully
hope this helps others which had issues with drivers and had issues with the original factory image 4.4 (KRT16O) giving the E: signature verification failed

Great guide!
The package for the link https://developers.google.com/android/nexus/images#razorkrt16o fails verification for me as well and does not install once its side loaded. So it's probably beneficial to just point to the other link.:good:

haet said:
Great guide!
The package for the link https://developers.google.com/android/nexus/images#razorkrt16o fails verification for me as well and does not install once its side loaded. So it's probably beneficial to just point to the other link.:good:
Click to expand...
Click to collapse
The factory image isn't meant to be side loaded. It needs to be installed using fastboot/bootloader.

If I understand this correctly, it fails because ADB sideload is intended for zips and not image files.
If you use the flash_all.bat (or whatever it is, slips my mind at the moment) it will flash a complete factory image.
The zip on the other hand is intended for sideloading and should update the OS no problem.

cincibluer6 said:
If I understand this correctly, it fails because ADB sideload is intended for zips and not image files.
If you use the flash_all.bat (or whatever it is, slips my mind at the moment) it will flash a complete factory image.
The zip on the other hand is intended for sideloading and should update the OS no problem.
Click to expand...
Click to collapse
Gotcha.
There is quite a size difference between the the zip and the tgz format. Is this only because of compression format? Or is it more beneficial to flash one over the other?

cincibluer6 said:
If I understand this correctly, it fails because ADB sideload is intended for zips and not image files.
If you use the flash_all.bat (or whatever it is, slips my mind at the moment) it will flash a complete factory image.
The zip on the other hand is intended for sideloading and should update the OS no problem.
Click to expand...
Click to collapse
There are zips and then there are ZIPS
It isn't the type of archive that is critical but the contents of the zip. Zip is just a generic archive format and can store anything.
The OTA zips include specific content. In particular they are
signed by google
include an install script to handle patching, replacing files, and setting up permissions
include an install utility to run the script
include individual patch files
include whole files if the patches would be too large
have a specific directory structure where everything is supposed to be located
The factory images are also delivered in an archive. They are first archived in a tar format, which just collects a bunch of files and doesn't compress. Then they are gzip'd which is a Gnu archiver which performs a similar job to zip, but uses a different format and algorithm. Within the original tar archive there is also a zip archive. That zip contains images of the kernel, recovery, rom, user and data partitions, but it doesn't include the aforementioned items that make a zip into an OTA-style zip.
The factory images are NOT meant to be flashed in recovery. Recovery will be expecting the stuff above that OTA-style zips have. If you try to flash the factory image, the first point of failure is the signature verification fails, because it isn't signed (and even if it were signed, it wouldn't be signed in the way recovery is expecting)
So what is the difference between flashing via Recovery and the OTA-style zip vs running flash-all and the factory image?
The OTA-style flash will go and examine each file it needs to patch to make sure it is stock JSS15R. It must do this because it doesn't have the complete KRT16O file, only a patch (difference between the JSS15R and KRT16O versions of the file) that only makes sense if applied to the original JSS15R file. Even if there is a one space difference in the file, the patch would fail.
Since the OTA-style patches files (in general) it will leave files you have added in place. In particular the files installed to keep root are left in place and so are apps, sounds, images, etc. you added to the ROM (/system) partition. So you ask why do you lose root? You don't lose the root files that were installed, they are neutered because at the end of the OTA-style install, it resets the permissions in all the directories to what they are supposed to be. This drops the special permissions you gave the root files to do their job. Also the OTA-style patch does not directly overwrite your recovery. Upon first boot, there is a script that runs which builds the new recovery using the installed kernel. This is why if you immediately (prior to reboot) run the SuperSU install script after the installation of the OTA-style update.zip, you can restore root and keep your recovery. The SuperSU install script replaces the script that builds the new recovery, with its own file. It also reinstalls and sets the permissions on the root files. So in effect, you have root and have prevented stock recovery from being installed over your custom recovery.
The Recovery that you use to run the OTA-style update.zip is just special program that boots up on the linux kernel and accepts certain actions. The source code for Recovery along with the kernel is published. People can easily replace Recovery with their own custom program and that is why you have custom recoveries.
The factory images on the other hand install through the bootloader. This is a low-level program similar to BIOS on PCs. It has more limited functions and the code is proprietary. It is harder to do custom bootloaders because the source code isn't published.
The bootloader has a more limited set of functionality and you communicate with bootloader using a different program called fastboot.
The bootloader expects the files you give it to be .img files or you can give it a zip archive full of .img files. These are not patches of files like the OTA. These are complete images to replace the existing partitions. It is like a Norton Ghost image (factory image style) of your entire hard drive vs an incremental backup (OTA-style) of just the files that changed.
Given they are full images, they will overwrite the partitions completely so anything you had on them before is wiped out and overwritten.
Also full images are always larger than OTA patch-style updates because they contain everything rather than just the changed file patches.
By default they use the -w option in the fastboot install instructions, which will wipe your user data as well, but you can remove the -w option and keep your user data, though there are always a small percentage of upgrades where it won't work to keep your user data (same with the OTA).
Anyway that is just a brief summary. There are many more details and nuances I didn't list.

^^ I won't go ahead and quote you but thanks for the full on summary. I knew what .tgz was and all that (using Linux for a few years now) but I'm new to most of the Android like stuff.
Thanks for clarifying and explaining it so well.

Just gave the sideload of SuperSU a shot and was given two errors:
failed to verify whole-file signature
signature verification failed

haet said:
Just gave the sideload of SuperSU a shot and was given two errors:
failed to verify whole-file signature
signature verification failed
Click to expand...
Click to collapse
You cannot sideload the SuperSU update.zip using stock recovery because it isn't signed by Asus/Google.
It is signed, but using a generic cert.
You need to use custom recovery like TWRP or CWM to install it. You can use their menu system to choose the file or if they have sideload, you can sideload using custom recovery.

sfhub said:
You cannot sideload the SuperSU update.zip using stock recovery because it isn't signed by Asus/Google.
It is signed, but using a generic cert.
You need to use custom recovery like TWRP or CWM to install it. You can use their menu system to choose the file or if they have sideload, you can sideload using custom recovery.
Click to expand...
Click to collapse
Makes sense. Thanks for the help!

Windows 2008 server usb drivers?
This guide was great, and everything worked fine until I reboot into recovery and choose to adb sideload an image. Then, the device doesn't get recognized, and the google drivers don't work. So, I can't see the device with the ADB interface driver.
Does any have experience with this? Am I out of luck? I couldn't find anyone talking about drivers for windows server 2008 anywhere -- but usually win7 drivers work fine -- just not here.
I don't have another windows installation anywhere, so if there isn't an answer, I will just have to wait for OTA
** UPDATE **
I found some universal drivers from Koushik Dutta: https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH
Those drivers worked! Then I used the OTA download (your second option), sideloaded it, and got the update. Now running KitKat, so thanks a bunch! hopefully someone else will find this driver option useful.

I'll give those universal drivers a go. Hell, I've tried everything else on the Internet with complete failure. One last try before I give up.
Sent from my SM-P600 using XDA Premium HD app

jbwray said:
This guide was great, and everything worked fine until I reboot into recovery and choose to adb sideload an image. Then, the device doesn't get recognized, and the google drivers don't work. So, I can't see the device with the ADB interface driver.
Does any have experience with this? Am I out of luck? I couldn't find anyone talking about drivers for windows server 2008 anywhere -- but usually win7 drivers work fine -- just not here.
I don't have another windows installation anywhere, so if there isn't an answer, I will just have to wait for OTA
** UPDATE **
I found some universal drivers from Koushik Dutta: https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH
Those drivers worked! Then I used the OTA download (your second option), sideloaded it, and got the update. Now running KitKat, so thanks a bunch! hopefully someone else will find this driver option useful.
Click to expand...
Click to collapse
You sir are a genius (and the driver author). I had the exact problem and looked everywhere. I am low tech, too. So following these two guides;
http://phandroid.com/2013/11/13/how-to-install-kitkat-nexus-7/
http://www.droid-life.com/2013/02/1...date-a-nexus-without-root-or-custom-recovery/
I am now on 4.4. And everything is intact. Thank you!

I also ran into Google USB driver problems after the Nexus dropped into recovery mode. So I gave up trying to use Windows 8 and switched over to using Ubuntu workstation. Getting ADB to run on Ubuntu is very easy and so flashing the Kit Kat OTA file was a breeze.
On Ubuntu there's no need to install the full SDK just to get ADB and Fastboot; the process is outlined here: http://forum.xda-developers.com/showthread.php?t=1860108. From there it's just simple command line entries from a terminal i.e. "adb devices."
I was disappointed to see Google has kept the black top and bottom bars for tablets. I usually run Teslacoil's launcher and installed their beta launcher with transparent bars a welcome relief.

doorunrun said:
I also ran into Google USB driver problems after the Nexus dropped into recovery mode. So I gave up trying to use Windows 8 and switched over to using Ubuntu workstation. Getting ADB to run on Ubuntu is very easy and so flashing the Kit Kat OTA file was a breeze.
On Ubuntu there's no need to install the full SDK just to get ADB and Fastboot; the process is outlined here: http://forum.xda-developers.com/showthread.php?t=1860108. From there it's just simple command line entries from a terminal i.e. "adb devices."
I was disappointed to see Google has kept the black top and bottom bars for tablets. I usually run Teslacoil's launcher and installed their beta launcher with transparent bars a welcome relief.
Click to expand...
Click to collapse
If you install the latest Google search apk and GEL from the nexus 5, you will have transparent nav bar.
{
"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"
}
Sent from my Nexus 7 using Tapatalk 4

Hi. This will wipe the device right? We should have a backup before proceeding?

ganstar said:
You sir are a genius (and the driver author). I had the exact problem and looked everywhere. I am low tech, too. So following these two guides;
http://phandroid.com/2013/11/13/how-to-install-kitkat-nexus-7/
http://www.droid-life.com/2013/02/1...date-a-nexus-without-root-or-custom-recovery/
I am now on 4.4. And everything is intact. Thank you!
Click to expand...
Click to collapse
You should also know that Google has drivers as well located at http://developer.android.com/sdk/win-usb.html, which is what you would have downloaded right after you installed the SDK package.

For those who can't get their devices recognised even after doing everything correctly. Just boot the tablet and change from MTP to PTP. Worked for me.
Sent from my Nexus 7 (2013)

I was on PTP. still didn't work
BreakShadow said:
For those who can't get their devices recognised even after doing everything correctly. Just boot the tablet and change from MTP to PTP. Worked for me.
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
I was on PTP. Still didn't work until I found those drivers. The drivers from Google were what I was using, but they didn't support the device in fastboot mode for the version of windows I was using. (2008 server R2)

haet said:
You should also know that Google has drivers as well located at http://developer.android.com/sdk/win-usb.html, which is what you would have downloaded right after you installed the SDK package.
Click to expand...
Click to collapse
I had those, they didn't work for me, as others have noted as well.

[Guide] Tired of EMUI ? Here's a full guide on how to install a Treble Rom

So I was tired of EMUI, the UI design isn't really that bad but it really clashed with Android's Material Design, so since our Mate 9 is Treble compatible, I decided to try a few Treble ROMs. After many fails and factory resets, I finally settled on Havoc-OS. Here I made a guide on how to switch to a Treble Rom.
So a few things to note :
There's no (fully) compatible TWRP recovery for Kirin devices. Either they work but cannot flash OpenGApps or they simply don't work with Treble ROMs.
Huawei's eRecovery seems to work. For me at least, it didn't work before. So as usual, BACKUP ALL OF YOUR DATA(Titanium Backup or HiSuite for apps if needed). You can also use TWRP with stock EMUI if you want to backup your partitions in case something goes really bad.
Make sure you're using stock kernel, ramdisk and recovery_ramdisk before starting anything.
A Micro SD card is optional but useful for restoring things or if you don't want to transfer all of your backup data to your PC
USB Debugging isn't really needed.
-------------------Requirements-------------------
- Your phone, obviously. Has to be a Mate 9 (Pro) updated to Android 8.0 Oreo.
- An unlocked bootloader (Since Huawei stopped giving unlock codes, I can't help you on that one. Sorry boys)
- A PC and a USB Type-C cable.
-------------------A. First things first-------------------
Enable OEM Unlocking
An easy thing to do, otherwise you won't be able to flash anything on your phone (FRP will be "Lock" on bootloader screen). You may think that this is kind of a mandatory thing to do since you've unlocked your bootloader, but you can get it back to disabled and greyed out anytime, so here's a reminder.
1. Enable developer options by going to Settings > System > About Phone and taping multiple times on Build Number
{
"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"
}
2. Once that's done, go to Developer Options and enable OEM Unlocking.
-------------------B. Downloads-------------------
1. Download and install Minimal ADB
Click here to download Minimal ADB
2. Download your ROM, right now there are two fully compatible ROMs :
- OpenKirin Builds : https://openkirin.net/download/
- Havoc-OS : https://forum.xda-developers.com/mate-9/development/rom-havoc-os-t3826470
You'll get an img file that you must put inside where you installed Minimal ADB.
3a. For later : Download Huawei Firmware Finder and Huawei Update Extractor
- Huawei Firmware Finder
- Huawei Update Extractor > If you're not running Windows (Mac, Linux) (Thanks to irony_delerium)
- Also download Magisk Manager (This is an APK)
--- OR ---
3b. Download this patched Ramdisk with Magisk included so that you don't have to download all of the above. CREATED WITH BUILD NUMBER MHA-L29 8.0.0.370(C432). USE AT YOUR OWN RISK IF IT DOESN'T EXACTLY MATCH YOUR PHONE BUILD.
Here (name is patched_boot.img)
-------------------C. Installation-------------------
Now that you've got your Rom img and Minimal ADB, we can start installing it.
1. Turn off your phone.
2. Plug your phone into your PC AND hold down the volume down button until you get a (terrible) white screen saying you're in fastboot&rescue mode.
3a. Open a command prompt (with admin rights if possible) on your PC and get to your Minimal ADB directory. By default, it should look like this :
Code:
cd C:\Program Files (x86)\Minimal ADB and Fastboot
3b. If you installed Minimal ADB on a different drive, then type this :
Code:
cd /d {DRIVELETTER}:/{MINIMAL ADB DIRECTORY/}
4. Make sure your phone is detected by typing :
Code:
fastboot devices
This should show up.
5. Now you can start flashing your ROM by typing :
Code:
fastboot flash system {IMGFILE}.img
Your ROM should start flashing with the message 'target reported max download size of 494927872 bytes'
It should take a minute.
Once you see 'finished. total time: times', that means your ROM has been flashed.
Don't reboot just yet. Things won't work
6. Reboot to recovery by turning off your phone (hold down power button for ~5 seconds) and holding volume up.
7. Now that you are in EMUI recovery, do the following :
- Wipe cache
- Wipe data/factory reset
You MUSTdo this otherwise you will have multiple issues.
8. You're done for the installation. Now reboot to system and start your phone first config (again).
-------------------D. Root-------------------
Your Treble Rom isn't rooted by default. But the Treble Rom itself triggers the SafetyNet flag, which means even if your phone is super clean, it is not certified. So it is obviously completely optional, by it is extremely recommended to install Magisk.
If you downloaded the patched_boot.img file in the attachment
The install process will be extremely easy. It will install Magisk 16.7 (only Beta works with Treble right now). So all you have to do is :
Get to fastboot mode by turning off your phone, plugging it to your PC while holding volume down button. Then, type the following command in the same command prompt window :
Code:
fastboot flash recovery_ramdisk patched_boot.img
It should take around 5 seconds. Now you can reboot and download Magisk Manager. But Safetynet will still trigger (if it doesn't, tell me). You'll have to follow E. SAFETYNET.
If you're not using the attachment
1. Check your phone Android version and build number. It is in Settings > About phone. Write it down, you'll need it.
2. (Install and) Open Huawei Firmware Finder. Get in the 'Common Base' tab and type in your phone build number.
3. Find the matching build number in the list. Make sure its type is 'FullOTA-MF' and its size is 2Go+. Then click on the blue link in the 'Filelist' column. Copy paste the first (ending with 'update.zip') in your browser to download the zip file. It should take some time.
4. Once it's downloaded, open it with 7Zip/WinRar and extract the file named 'UPDATE.APP'.
5. Open Huawei Update Extractor, go to the Settings tab and untick everything.
6. Now, go to the Extract tab and click on the dots on the right and select your extracted 'UPDATE.APP'. A ton of files should appear.
7. Right click on 'RAMDISK', and 'Extract selected'. Put it somewhere on your PC, you'll need it.
8. Plug your phone on your computer and put your RAMDISK.IMG in a folder on your phone.
9. On your phone, download and install Magisk Manager. If it prompts you to do so, do not install it. Then go to Settings tab and change 'Update Channel' to 'Beta'.
10. Now go back and tap 'Install', then choose 'Patch Boot Image File' and select your RAMDISK.IMG that you transferred to your phone. Then let Magisk do its thing.
11. Once it's done, on your PC, go to Your Phone/Internal Store/MagiskManager, and transfer the file 'patched_boot.img' to your Minimal ADB folder.
12. Turn off your phone and get to fastboot mode. You know how to do it now, don't you ?
13. In the same command prompt on your PC, type :
Code:
fastboot flash recovery_ramdisk patched_boot.img
It should take around 5 seconds. Now you can reboot and BAM, you're rooted. But Safetynet will still trigger (if it doesn't, tell me). You'll have to follow E. SAFETYNET.
-------------------E. SafetyNet-------------------
Magisk may be installed, but with a Treble Rom, SafetyNet should trigger anyway. So you'll have to do a few things.
1. In Magisk Manager, go to the Downloads tab and search for 'MagiskHide Props Config'. Install it, then reboot your phone.
2a. Once your phone is rebooted, download Terminal Emulator on the Play Store
--- OR ---
2b. Go to developer options and enable 'Local Terminal'.
3. Open your terminal, then type :
Code:
su
(Accept root request)
Code:
props
Things should appear. Woah.
4. Type 1 (Edit device fingerprint), then f, then choose a vendor and a model by typing the right number, then press y. Don't reboot yet (press n)
5. Type 6 (Script settings), then 1, then y. Now you can reboot (press y). Once it's done, make sure that 'boot stage' is 'currently post-fs-data'. Otherwise SafetyNet will still trigger.
THERE YOU GO ! Your phone should pass SafetyNet. You can check this by trying to search for the Netflix app on the Play Store or going into the Play Store settings and making sure your device is Certified'.
If you have any question/bug, do ask/report all of dem to me.

I haven't rooted or done anything with this device since I've bought it coming from all Samsung devices previously. This guide is awesome! Nice work!

About Firmware Finder:
You don't need to install this as a desktop app:
http://pro-teammt.ru/firmware-database/
The page itself is in Russian, but Chrome usually offers to automatically translate, and it's not terribly complex anyway.
There is also the Firmware Finder app in Google Play. Either work.
(This also makes it accessible to those of us who don't run windows as a primary desktop.)
--
If you're not on Windows (Linux, Mac, BSD):
The following GitHub repo contains a Perl script for extracting the contents of UPDATE.APP:
https://github.com/marcominetti/split_updata.pl
Run:
splitupdate UPDATE.APP
The full image will be extracted into a subdirectory "output".

i install Havoc via fastboot ok
but i return stock huawei , install system.img of update.app ok
but now after install stock huawei system my phone lost language portuguese Brazil ...no more all languages

irony_delerium said:
About Firmware Finder:
You don't need to install this as a desktop app:
http://pro-teammt.ru/firmware-database/
The page itself is in Russian, but Chrome usually offers to automatically translate, and it's not terribly complex anyway.
There is also the Firmware Finder app in Google Play. Either work.
(This also makes it accessible to those of us who don't run windows as a primary desktop.)
--
If you're not on Windows (Linux, Mac, BSD):
The following GitHub repo contains a Perl script for extracting the contents of UPDATE.APP:
https://github.com/marcominetti/split_updata.pl
Run:
splitupdate UPDATE.APP
The full image will be extracted into a subdirectory "output".
Click to expand...
Click to collapse
Yup, I'm aware of the Play Store app, but IMO, having everything directly on your PC is more convenient. Also what you said is useful for people not running Windows, so kudos to you for that.

aureliomilitao said:
i install Havoc via fastboot ok
but i return stock huawei , install system.img of update.app ok
but now after install stock huawei system my phone lost language portuguese Brazil ...no more all languages
Click to expand...
Click to collapse
Huh, that's a strange issue. I'd suggest you do this :
- If you don't care about all you data being lost (you got a backup), get to Huawei eRecovery by rebooting your phone and holding volume up button for 3 seconds on the screen saying your bootloader has been unlocked. Then follow the indications on screen, by choosing 'Download latest version'
- The fact that you can't choose any language is odd, as all languages are included in system.img. So you probably got a... kind of faulty system.img from your update.app, which is also strange.

Deytron said:
Huh, that's a strange issue. I'd suggest you do this :
- If you don't care about all you data being lost (you got a backup), get to Huawei eRecovery by rebooting your phone and holding volume up button for 3 seconds on the screen saying your bootloader has been unlocked. Then follow the indications on screen, by choosing 'Download latest version'
- The fact that you can't choose any language is odd, as all languages are included in system.img. So you probably got a... kind of faulty system.img from your update.app, which is also strange.
Click to expand...
Click to collapse
i extract system.img in update.app ...and lost Brazil language

aureliomilitao said:
i extract system.img in update.app ...and lost Brazil language
Click to expand...
Click to collapse
Well... I'm sorry, but I can't help you on that one. It just doesn't make sense. You can't "lose" a language. As I said, try to use Huawei eRecovery to completely restore your phone.

Solved

How to dump your own image

First, to clarify, the last time I rooted anything was a Galaxy S3 back in the day. I'm by no means an expert, I just figured I'd help out folks like me that haven't touched all these new tools, well, ever.
Just did this myself earlier today attempted to get Magisk root, but alas, I got stuck in a boot loop. Luckily I had muddled through getting the image first, otherwise I'd still be stuck in said boot loop. I figured I'd post this for anyone else trying to root these things just to make sure you have a backup you can trust (I generally don't trust rando images that folks post online). All of the instructions below are assuming you're on Windows 10 and using PowerShell just because that's the default these days. Without further adieu.
Download ADB/fastboot (on your Windows machine)
I downloaded adb/fastboot from google directly: https://developer.android.com/studio/releases/platform-tools
Just extract and browse to the platform-tools directory in Windows Explorer until you can see adb.exe and a bunch of other tools
Download the latest SP Flash Tool
I just grabbed it from here: https://spflashtools.com/
Please let me know if there's an "official" place to find SP Flash Tool, cause everything surrounding all the download sites seems a bit sus...
Enable USB Debugging (on the tablet)
Go to settings -> About tablet
Tap the Build number 10 times (until debugging mode unlocks)
Hit back and go to System
Click Advanced and then Developer Options
Enable USB Debugger
I also enabled OEM unlocking because the whole point of this is for me to run either AOSP or Lineage someday. I honestly don't know if unlocking the bootloader is needed for dumping your own images, but I highly suspect it's not.
Plug the tablet into your computer
You'll likely see a prompt on your tablet about allowing your computer to debug your tablet. I just checked the box and hit accept so I wouldn't see it again.
Get your scatter file (on your Windows machine)
I tried several things to get the scatter file (I guess this is like a partition table based on the contents I saw) but in the end, by far the easiest way was to just download the scatter file from the file system.
In the Windows Explorer window from before (platform-tools), hold down shift while left clicking and click on Open PowerShell window here
Now type the following to get a shell on your:
.\adb.exe shell
This will get you into the shell environment. Now type the following to verify your scatter file is there:
ls -al /system/data/misc/
In here you should see something like:
-rw-r--r-- 1 root root 13893 2008-12-31 19:00 MT8168_Android_scatter.txt
Now that we have the name, just type exit to get out of the shell
Download the scatter file
.\adb.exe pull /system/data/misc/MT8168_Android_scatter.txt
Open up the scatter file in your favorite text editor (for me, Notepad++)
Now you can see the partition layout, offsets, etc, etc
Dump your image(s) (on your Windows machine)
Now open SP Flash Tool (flash_tool.exe)
On the Download tab, make sure the Download-Agent is MTK_AllInOne_DA.bin
Now click Choose for the Scatter-loading file and browse to the scatter file you just downloaded
This should be in your platform-tools folder unless you moved it
Once the scatter file is loaded, the partition table should fill up with a bunch of partitions
Click on the Readback tab
Click Add
Double-click on the new entry
Navigate to where you want to save your image, and give it a name (in this case I'm starting with boot.img)
Remember how you opened the scatter file in a text editor? Search in the scatter file for boot.img
Make sure the region matches (should be EMMC_USER) between the scatter file and SP Flash Tool
Copy/paste the value for start_addr in the scatter file to Start Address in SP Flash Tool
Copy/paste the value for partition_size in the scatter file to Length in SP Flash Tool
Now do the same thing for recovery.img and any other images you'd like
If you want a full ROM backup, name the file something like ROM_0, then use Start Address of 0x0 and length as the start_addr for the second-to-last entry in the scatter file (in my case, it was 0xc1a80000, just make sure it doesn't start with f's)
Note: I don't know for sure if this is accurate or not, I'm still playing with it, but so far it appears to be. Probably?
Poking around in WwR MTK 2.51, it looks like for this particular device (100011885) I wanted a total dump of 0x73A000000. It looks like this number is derived from the first 8Mb of the EMMC_USER dump, so I'm not sure of an easier way than throwing WwR MTK at it for the moment.
Once you've got all the entries for what you'd like to dump, make sure to disconnect the tablet from your computer and power it off
Now click on Download in SP Flash tool
Once things grey out, then plug the tablet in. After a few seconds, you'll see the images start dumping.
Congrats, you have a boot.img (and whatever other images you wanted). Like I said, from here I tried using Magisk to patch the boot file, but when I flashed it in fastboot, after enabling OEM unlocking in Developer Options, it just kept popping up the initial Onn graphic along with the Orange State warning without getting to the "fancy" Onn graphic and the rest of the boot process. I was able to flash the original boot.img back and it once again booted properly again.
Also, for anyone interested, I've posted my dumped files for the 100011885 in my google drive: https://drive.google.com/drive/folders/17LtLtjKg4JJU9EJdIXPsyNjen0H-ilMX?usp=sharing
Maybe someone will have pity on me and figure out why Magisk isn't working?
Whenever I get a moment, I'll dump my 100003562 as well.

First, thanks a ton for this. I have been trying to pull a full system dump since I bought the tablet and had resorted to single pulls by name(very long and involved) I don't know if this will work for you, but on both of my 7 inch Gen 2 tablets, I just sideloaded Magisk Manager and then opened it (this was after unlocking the tablet) When I first opened MM it just said it needed to download some additional files for my environment. I clicked okay, it downloaded and installed the additional files. Once it rebooted, I open MM again and clicked install Magisk. On the next screen, I clicked direct install and let it do it's thing. After rebooting, root checker showed I had root, but I still can't get it to pass safetyNet. Root access does work as I have installed a few modules and busy box.

Which Custom Rom will work on J5

Ive made a terrible mistake of not installing DevInfo before wiping my UK unlocked Samsung J5 and now i dont know what model number it was or what cpu i had arm32/64 or x86 I have tryed 3 different Linageos 17 and i keep getting this error on all of them.
I cant get my J5 to work through USB PC (Adb) so have to use another samsung phone which has a SD card so that i can put the rom on that and then transfer that sd card to the j5, also i never backed up my OS so theres nothing on there apart from TWRP
Theres no way in TWRP to get any info on the make or model, is there a safe universal rom to install via TWRP so that i can just check my model number cpu hardware etc, so i can then install the right lineageos 17 afterwards
{
"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"
}

68EC000 said:
Ive made a terrible mistake of not installing DevInfo before wiping my UK unlocked Samsung J5 and now i dont know what model number it was or what cpu i had arm32/64 or x86 I have tryed 3 different Linageos 17 and i keep getting this error on all of them.
I cant get my J5 to work through USB PC (Adb) so have to use another samsung phone which has a SD card so that i can put the rom on that and then transfer that sd card to the j5, also i never backed up my OS so theres nothing on there apart from TWRP
Theres no way in TWRP to get any info on the make or model, is there a safe universal rom to install via TWRP so that i can just check my model number cpu hardware etc, so i can then install the right lineageos 17 afterwards
View attachment 5405063
Click to expand...
Click to collapse
Some sensitive info was overlapped, for this reason this ROM is not recognizing your device as a candidate. If you are totally sure that this ROM work for your device, just delete from the zip path /META-INF/com/google/android/updater-script something like assert failed: getprop("ro.product.device... and try again.
Regard to know the exact model you could flash a stock recovery (converting it in tar) from any of the LTE models; G/F/FM and booting to it, you will see the build number and the exact model it is.

Many thanks for your help.... Ive managed to find out that its a J5 SM-J530F 2017 (16gb) and with the IMEI number it has a ARM Cortex A53, Samsung Exynos 7870.
I loaded up a stock rom J530FXWS7CTF1 in Odin3_v3.10.5 everything went ok but when its starts up it goes into a loop on restart
Loaded up the Rom and everything went ok
Everything looked good
looks like its failed....

68EC000 said:
Many thanks for your help.... Ive managed to find out that its a J5 SM-J530F 2017 (16gb) and with the IMEI number it has a ARM Cortex A53, Samsung Exynos 7870.
I loaded up a stock rom J530FXWS7CTF1 in Odin3_v3.10.5 everything went ok but when its starts up it goes into a loop on restart
View attachment 5405703
Loaded up the Rom and everything went ok
View attachment 5405705
Everything looked good
View attachment 5405709
View attachment 5405711
looks like its failed....
Click to expand...
Click to collapse
From what I understood, you flashed the official stock firmware through Odin, but then you did try to root it.
If this is the case after to flash the Samsung firmware you should to reboot to system and redo all the process to can flash something custom on it, I mean USB debugging, OEM unlock and this stuff, only starting from there you should go further with.
And one more thing, when you return completely to stock is always recommendable:
- Wiping all and formatting data through stock recovery
- Then go to bootloader (Odin mode)
- When flashing use the CSC_... different from the CSC_HOME this will wipe completely the preferences, and you can start freshly from there.
Why you don't use Magisk instead of SuperSu.

again thank you for your time, i feel a bit embarrassed as im digging my self into a deeper situation and dont know what to do.
Since i dont have a OS installed am either stuck with download mode or twrp and even using magisk i cant get anything to work it seems that the custom lineageOS keeps saying its the wrong version for any of them.
.
.
magisk
anything else i could try if its salvageable, thanks again.

68EC000 said:
again thank you for your time, i feel a bit embarrassed as im digging my self into a deeper situation and dont know what to do.
Since i dont have a OS installed am either stuck with download mode or twrp and even using magisk i cant get anything to work it seems that the custom lineageOS keeps saying its the wrong version for any of them.
View attachment 5408207
.
View attachment 5408209
.
magisk
View attachment 5408211
anything else i could try if its salvageable, thanks again.
Click to expand...
Click to collapse
Some insights about:
- Don't try to flash 3 files at once, flash one by one.
- did you do the right editing from the updater-script as indicated? Can you upload here just this file?
- Did you change the system partition through TWRP I mean did you do "repair file" ?
- It seems that TWRP is not finding the route to misc partition, have your ROM this file? Unpack the stock ROM and search for it in case you didn't do a backup from.
- And as a final resource the PIT repartitioning could work too but, we have to see other reasons why your device got this.

hi thanks again for your patient i cant seem to find the line
META-INF/com/google/android/updater-script something like assert failed: getprop("ro.product.device...
this is from the rom lineage-17.1-20210202-UNOFFICIAL-j5y17lte.zip (569 Mb)

68EC000 said:
hi thanks again for your patient i cant seem to find the line
META-INF/com/google/android/updater-script something like assert failed: getprop("ro.product.device...
View attachment 5409557
this is from the rom lineage-17.1-20210202-UNOFFICIAL-j5y17lte.zip (569 Mb)
Click to expand...
Click to collapse
You have to delete all the lines above, edit it with Notepad++, and let it from "ui_print........" then save it, you don´t need to unpack the zip, just open it, edit it and save, WinRar or 7zip will update the zip with the changes.

I used 7zip to edit the \META-INF\com\google\android\updater-script and saving editied file without unzipping.
then i put the edited lineage-17.1-20210202-UNOFFICIAL-j5y17lte.zip (569 Mb) file back onto microSDcard and tried again.

68EC000 said:
I used 7zip to edit the \META-INF\com\google\android\updater-script and saving editied file without unzipping.
View attachment 5410597
then i put the edited lineage-17.1-20210202-UNOFFICIAL-j5y17lte.zip (569 Mb) file back onto microSDcard and tried again.
View attachment 5410601
Click to expand...
Click to collapse
You shortened too much the file, from your original updater-script uploaded some days ago you didn't leave the most important scripts.
I don't recommend using a simple Notepad to edit it, you should use Notepad++ or other tool like Sublime.
Can you upload the original-updater script? I will check it, and will upload it again, this way we can discard if this is the culprit or something is wrong with your file system.

yes i deleted too much from the script file... i installed Notepad++ and re-done the script.
redited script saved
starts off good.
i dont know if it failed or if something did work as it asks if you want install twrp again

68EC000 said:
yes i deleted too much from the script file... i installed Notepad++ and re-done the script.
View attachment 5411271
redited script saved
View attachment 5411273
View attachment 5411275
starts off good.
View attachment 5411277
View attachment 5411279
i dont know if it failed or if something did work as it asks if you want install twrp again
Click to expand...
Click to collapse
The ROM you are trying to flash is this? https://forum.xda-developers.com/t/...or-the-galaxy-j5-pro-j530-02-02-2021.4227945/ if not, provide a link.

@68EC000 you should use the latest orange fox recovery for your device, This error was also faced by mt j5, I flashed orange fox recovery and I didn't get any error, With the old version of TWRP I was unable to flash android 10 lineage os on it​

I was also getting this same error 7 with old twrp

[OFFICIAL][TWRP][J530X] OrangeFox Recovery Project [R11.0]
DISCLAIMER I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it...
forum.xda-developers.com
flash this recovery and then try to flash lineage os

Hi
Thanks again for your input and help.....so i tryed the Rom from https://forum.xda-developers.com/t/...or-the-galaxy-j5-pro-j530-02-02-2021.4227945/
edited the updater script
Spoiler: Screen shots
error 7 again...
So i tryed hasangillani66 method installing OrangeFox and adb then copying recovery.img to the adb directory but im getting some error when typing device, also everytime a connect the j5 to the pc via usb i hear the usb connection sound but cant see anything in my computer.
Spoiler: Screen shots

68EC000 said:
Hi
Thanks again for your input and help.....so i tryed the Rom from https://forum.xda-developers.com/t/...or-the-galaxy-j5-pro-j530-02-02-2021.4227945/
edited the updater script
View attachment 5412179
View attachment 5412181
error 7 again...
So i tryed hasangillani66 method installing OrangeFox and adb then copying recovery.img to the adb directory but im getting some error when typing device, also everytime a connect the j5 to the pc via usb i hear the usb connection sound but cant see anything in my computer.
View attachment 5412187
View attachment 5412189
View attachment 5412197
View attachment 5412203
Click to expand...
Click to collapse
TBH, I don't understand what you are trying to do with ADB,
Odin works while the device is in download mode, you should power off the device and then either reboot via recovery to bootloader mode or directly by pressing the key combo to download mode.
Extract the image from Orange Fox recovery (usually it comes into a zip with add-ons), compress the recovery image into a tar using 7zip, uncheck in Odin "Auto reboot" option and after to flash it, reboot manually to the new recovery, transfer the Orange zip file to your SDCard and flash the zip to have all the scripts and add-ons integrated.
That's all regards Orange Fox recovery.

Thank you again for your helping a low tech savvy person like myself, well i managed to get somewhere this time as the photos will explan
turned zip to tar
flash passed
starts up with orangefox
now when you say
transfer the Orange zip file to your SDCard and flash the zip to have all the scripts and add-ons integrated.
does that mean turn these files in the photo below in one zip file and transfer to SD card & flash
thanks again for being so patient.

68EC000 said:
Now when you say
transfer the Orange zip file to your SDCard and flash the zip to have all the scripts and add-ons integrated.
does that mean turn these files in the photo below in one zip file and transfer to SD card & flash
Click to expand...
Click to collapse
Download Ofox zip from their website. Your device can be found here Orange Fox J5 2017
The XDA thread for orange fox for your device can be found here

68EC000 said:
Thank you again for your helping a low tech savvy person like myself, well i managed to get somewhere this time as the photos will explan
View attachment 5412943
turned zip to tar
View attachment 5412947
flash passed
View attachment 5412949
starts up with orangefox
now when you say
transfer the Orange zip file to your SDCard and flash the zip to have all the scripts and add-ons integrated.
does that mean turn these files in the photo below in one zip file and transfer to SD card & flash
View attachment 5412963
thanks again for being so patient.
Click to expand...
Click to collapse
Oh Man, I hope you didn't brick your device, the recovery image must be targeted to the AP slot, not to the BL.
If you encountered some issue with a normal boot flash back again the BL file supposed to be in the stock Samsung firmware, extract it from there and compress it as tar with 7zip.
The Orange Fox zip is the same from which you extract it the recovery image, as you could see it contains other files that can't be flashed through fastboot method (for other devices) or download mode (for Samsung) and the zip have to be flashed through Orange Fox to permanently have those files in your SD card in the Fox path directory. Again, is the same zip where you did get the recovery image from.