Database Info

[DUMP]Transformer Android 2.2 System Dump

[Background]
A few users have gotten Transformers with Android 2.2 installed with diagnostic tools included. So far there have been 3 confirmed users who have gotten these units.
These units are shipped rooted from Asus
Unfortunately, t0dbld has confirmed that the sbk is locked on these devices
[Photos]
{
"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"
}
[System Dump]
System Archive:
http://db.tt/p3p14Ez
MD5 for Archive:
http://db.tt/DWpL8U7
Or
85c584c6f425fbd6ab111b9f73251fe0
[Reference Thread]
http://forum.xda-developers.com/showthread.php?t=1054120
[Credits]
mmsson - Took time to provide system dump
t0dbld - Helping with users with 2.2 TF and confirming sbk is locked
Welshiren - Currently taking his time to provide more details on his 2.2 TF
*I did not create the system dump or the photographs, and i take no credit for it

Placeholder For Later Or For Important Temporary Information

The MD5 link might be broken.
FYI it should be:
85c584c6f425fbd6ab111b9f73251fe0

Roach2010 said:
The MD5 link points to the system dump.
FYI it should be:
85c584c6f425fbd6ab111b9f73251fe0
Click to expand...
Click to collapse
Yup just realized that lol, corrected the link, thanks

Just some findings i found that i thought where interesting
in \system\lib\hw\wlan\ there are specific broadcom files
bcm4329.ko
fw_bcm4329.bin
fw_bcm4329_apsta.bin
fw_bcm4329_mfg.bin
The Broadcom 4329 supports FM according to specs
http://www.broadcom.com/products/Blu...utions/BCM4329
and look what i found in the app folder
FMTesttool.apk
Interesting...
The FMTesttool.apk wont run for me
I dont know if it is a honeycomb issue or a issue with it being disable in the Broadcom bin files
One user told me when he ran it it displayed radio frequencies but everything was in Chinese, and there was no audio output or any type of RF noise coming from the TF

Do any of these users have root access, a system dump is nice but we could use alot more than that.. we need to see if there partitions are hidden etc we need to see if they have an available partition map or at least a blkid command, next we should dd these partitions etc, the best we could gain from this is to see if the partitions still match up the same as in hc builds and than know where to look to unlock our devices

t0dbld said:
Do any of these users have root access, a system dump is nice but we could use alot more than that.. we need to see if there partitions are hidden etc we need to see if they have an available partition map or at least a blkid command, next we should dd these partitions etc, the best we could gain from this is to see if the partitions still match up the same as in hc builds and than know where to look to unlock our devices
Click to expand...
Click to collapse
I am unsure since the 3 known users who have gotten these units seem to be regular end users, the dump that was acquired was done through a walkthrough by another member on xda from what i was told
If you want to contact welshiron and walk him through the steps in doing a dd image of the partitions and go over any other things you want to know about the device
(dont know if he is familiar with linux, maybe have him do it through a live CD if he is up to it, or maybe use Cygwin to run DD if it even supports it)
Im still an Android noob so i cant really help him too much
If he is the trusting type he might let someone remote in via teamviewer, logmein, etc. lol
Anyways, my theory is these are shipping mistakes because of the limited supply, and once supply increases we may never see any of these test units again

You Dont need linux for a DD, we need root and that is all, also if they are on 2.2 and linux kernel .32 than super one click should work for a quick root and unroot when done. after than we need to get them to open an adb shell,
C:\ adb shell
$ su
# blkid
this will get us some output that we can go on from there also there maybe be a partition map on the tab... i wont get mine till tuesday so i can only guess on where it is . either way we would want to start dd the partitions he has or tha came up for example from the same adb shell with su
C:\ adb shell
$ su
# dd if=/dev/block/mmcblk0p1 of=/sdcard/mmcblk0p1.img

t0dbld said:
You Dont need linux for a DD, we need root and that is all, also if they are on 2.2 and linux kernel .32 than super one click should work for a quick root and unroot when done. after than we need to get them to open an adb shell,
C:\ adb shell
$ su
# blkid
this will get us some output that we can go on from there also there maybe be a partition map on the tab... i wont get mine till tuesday so i can only guess on where it is . either way we would want to start dd the partitions he has or tha came up for example from the same adb shell with su
C:\ adb shell
$ su
# dd if=/dev/block/mmcblk0p1 of=/sdcard/mmcblk0p1.img
Click to expand...
Click to collapse
Didnt know dd was built into android shell, thats cool
Can you contact him and walk him through it, i contacted asking him if he ever used ADB before, haven't gotten a response yet

SlimDan22 said:
Just some findings i found that i thought where interesting
in \system\lib\hw\wlan\ there are specific broadcom files
bcm4329.ko
fw_bcm4329.bin
fw_bcm4329_apsta.bin
fw_bcm4329_mfg.bin
The Broadcom 4329 supports FM according to specs
http://www.broadcom.com/products/Blu...utions/BCM4329
and look what i found in the app folder
FMTesttool.apk
Interesting...
The FMTesttool.apk wont run for me
I dont know if it is a honeycomb issue or a issue with it being disable in the Broadcom bin files
One user told me when he ran it it displayed radio frequencies but everything was in Chinese, and there was no audio output or any type of RF noise coming from the TF
Click to expand...
Click to collapse
new roms have the same bcm4329 files, look in /system/vendor in any rom (prime for example).
and lol i'm stupid, dd is the obvious answer for the boot.img.
We could theoretically make a cool testing rom with that.

also, if a wipe/factory reset got rid of testing apps, that means they were in /data, so we need a dump of that too, almost for sure. you see, i've never had a factory reset that so much as TOUCHED system partition, so if the apps disappeared after a reset, they were in data, not /system.

Hi!
Sorry if it has been posted already .
There is another guy who has received a 2.2 TF, and he cannot post in this thread.
I beg any master please go to this link (look in the pages 19 and 20) and help this man before he returns his TF tomorrow. Maybe there is still time to get something useful.
http://forum.xda-developers.com/showthread.php?t=1054120&page=20
Regards.

CalvinH said:
Hi!
Sorry if it has been posted already .
There is another guy who has received a 2.2 TF, and he cannot post in this thread.
I beg any master please go to this link (look in the pages 19 and 20) and help this man before he returns his TF tomorrow. Maybe there is still time to get something useful.
http://forum.xda-developers.com/showthread.php?t=1054120&page=20
Regards.
Click to expand...
Click to collapse
Are you talking about mmsson, if so he already returned it, he is the one who provided the partial system dump
But if you are talking about welshiron then i am in contact with him, it seems that no one has contacted him yet which is disappointing, i am trying my best to help him but i am not as experienced as other users in the community
Im working on showing how how to check for root

Yes I was talking about welshiron.
Thank you for your efforts. I would like to be able to do something by myself, but can't do much (well, apart from annoy you really expert guys by posting here and there).
Good luck.
Regards.

what exactly are the advantages of a 2.2 dump? will you be able to make older apps work?

I wonder if they have a different bootloader.. Is the partition layout the same? Thats a different tegrastats than my gtab.. Has anyone confirmed that this rom is not already rooted.. certainly seems like it would be. I really hope I get one of these treats.

Update:
The dev units do have root access!, welshiron has confirmed it and was able to run the su command to enable root privileges via adb
i need help from other experienced members here, i am going to have him run the blkid command, but after that i am unable to reliably walk him through and dumps through dd, due to lack of experience

I seem to have permission to post here now, how do I run the blkid command and what will that tell us?
Just a reminder, Android and Linux are alien to me so I will need help with the syntax

welshiron said:
I seem to have permission to post here now, how do I run the blkid command and what will that tell us?
Just a reminder, Android and Linux are alien to me so I will need help with the syntax
Click to expand...
Click to collapse
Im not sure either, i cant run it on my rooted phone with cyanogen
Im really surprised there is not a lot of activity or help, maybe its a slow day lol

I'm no expert but on my Desire I do this...
Download Mini ADB.
Have mine if ya need Link!
Run the Runme.Bat file
In the pop-up box type: adb shell
when it gets a console type: blkid
EDIT: Just in case it wasn't obvious, connect your Transformer to PC with USB and enable USB Debugging.
EDIT2: I think it's possible you will need to push Busybox to your device.

Files can't be deleted any more

Hi,
I hope it is o.k. to post this question in the Xoom forum!?
In the download folder of my Motorola Xoom there are several files that I can't delete any more.
These files are pdf- and/or mp3-files that originally had a German umlaut in their file name. By copying/pasting these files into the download directory, they were somehow damaged. Now, the filenames are showing some strange characters and the file sizes are 0 kB.
As soon as I try to delete one of those files, my Xoom shows a message, that the file can't be deleted.
I already tried out to use several different file explorers which didn't work.
Unfortunately, even "MyPhoneExplorer" can't delete the files by connecting the Xoom to the PC. There, the files don't show up.
Renaming of the files doesn't work either and overwriting the files using a new file with the same name also doesn't work.
Can somebody of you help me with this problem?
How can I get rid of these 0kB files?
Thanks a lot!

Its perfectly OK to ask questions, no problem this is to be a source of information. It should however be in the Q&A section. That said
You can try to delete the file using "android terminal emulator" app
In there enter the following command substituting the file name for whatever u r trying to delete
Code:
rm /sdcard/yourfilename.whatever
If that does not work and u r rooted you can try the same command after have superuser permission. Do this
Open terminal and enter
Code:
su
Press enter after that and allow superuser, then enter the same command above.
Attached is a screen shot of what it should look like
{
"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 Galaxy Nexus using Tapatalk 2

runandhide05 said:
Its perfectly OK to ask questions, no problem this is to be a source of information. It should however be in the Q&A section. That said
You can try to delete the file using "android terminal emulator" app
In there enter the following command substituting the file name for whatever u r trying to delete
Code:
rm /sdcard/yourfilename.whatever
If that does not work and u r rooted you can try the same command after have superuser permission. Do this
Open terminal and enter
Code:
su
Press enter after that and allow superuser, then enter the same command above.
Attached is a screen shot of what it should look like
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Thanks for your idea! ...unfortunately it doesn't work
Problem seems to be the filename. It was corrupted while unpacking files from a packed archive. The original filename contained several so called"umlaute" (German special characters) which the system on the Xoom obviously can't handle correctly. These "umlaute" characters were replaced by some other curious characters during extraction.
Example: "11. ڵoԠ(ڢer-unter-ober-Գterreicher).mp3" is the filename after unpacking the file. Before, it was " 11. Üuoö (Über-unter-ober-österreicher).mp3"
As soon as I try to remove the file, a message appears, telling me that there is no such file. At the same time, the terminal shows the corrupted filename, but suppressing the corrupted characters.
No chance to delete :crying:
I hope, I could explain it so that you can understand what happens (or what doesn't happen). Any further ideas?
Thanks a lot!
PS: corrupted files are not only mp3 but also some pdf and doc files. All of them show up with a size of 0Byte on the Xoom, while the original file size is shown as soon as I connect the Xoom to my PC using MyPhoneExplorer (which, btw, also isn't able to delete)

deb10042 said:
Thanks for your idea! ...unfortunately it doesn't work
Problem seems to be the filename. It was corrupted while unpacking files from a packed archive. The original filename contained several so called"umlaute" (German special characters) which the system on the Xoom obviously can't handle correctly. These "umlaute" characters were replaced by some other curious characters during extraction.
Example: "11. ڵoԠ(ڢer-unter-ober-Գterreicher).mp3" is the filename after unpacking the file. Before, it was " 11. Üuoö (Über-unter-ober-österreicher).mp3"
As soon as I try to remove the file, a message appears, telling me that there is no such file. At the same time, the terminal shows the corrupted filename, but suppressing the corrupted characters.
No chance to delete :crying:
I hope, I could explain it so that you can understand what happens (or what doesn't happen). Any further ideas?
Thanks a lot!
PS: corrupted files are not only mp3 but also some pdf and doc files. All of them show up with a size of 0Byte on the Xoom, while the original file size is shown as soon as I connect the Xoom to my PC using MyPhoneExplorer (which, btw, also isn't able to delete)
Click to expand...
Click to collapse
Are the files located in a directory by them selves? If so u can try to remove the directory itself
Sent from my Galaxy Nexus using Tapatalk 2

runandhide05 said:
Are the files located in a directory by them selves? If so u can try to remove the directory itself
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Some of them are, others not. It makes no difference. If I try to delete an entire directory, containing one of those corrupted files, the whole directory can't be deleted. Anyway, "normal" files (uncorrupted) in the relevant directory can be removed individually... except those 0-Byte-files

No more ideas? ....anyone?
I can't believe, that it should really be impossible to delete corrupted files

Are u rooted? I just had the same problem. Simple boot into twrp and delete thru the built in file manager
Sent from my Galaxy Nexus using Tapatalk 2

runandhide05 said:
Are u rooted? I just had the same problem. Simple boot into twrp and delete thru the built in file manager
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Yes, I am rooted. but I have CWM on my Xoom. I found the thread about TWRP in the Nexus section. will it also work for the Motorola Xoom?
Can I install it instead of CWM without loosing all my apps and data?
Thanks!

deb10042 said:
Yes, I am rooted. but I have CWM on my Xoom. I found the thread about TWRP in the Nexus section. will it also work for the Motorola Xoom?
Can I install it instead of CWM without loosing all my apps and data?
Thanks!
Click to expand...
Click to collapse
Look at my signature, its twrp for our xoom
Sent from my Galaxy Nexus using Tapatalk 2

when using the terminal rm command you need to escape special characters ( i.e spaces, parenthese etc ) with a backslash or put the file name in quotes. so you file name in question can be removed by
Code:
rm 11.\ Üuoö\ \(Über-unter-ober-österreicher\).mp3
or
Code:
rm "11. Üuoö (Über-unter-ober-österreicher).mp3"
you can also do wildcard deletion based on fragements of the file name i.e
Code:
rm 11*.mp3
will delete all files that start with 11 with the mp3 externsion or you could start with a wildcard so a named example_file_name.txt can be deleted using
Code:
rm *file*.txt
obviously that will delete ALL files that have the word file in the filename and an extension of .txt so BE CAREFUL WHEN USING WILDCARDS but you get the idea ( hopefully )
If that doesn't delete them then you've got problems.
---------- Post added at 01:06 PM ---------- Previous post was at 12:54 PM ----------
A little tip, If you're not from the old school you won't know that it best to avoid spaces and special characters in filenames especially as your transferring between different filesystem types, obviously unicode characters are kinda inevitable if that's you native language but a demestorated here there's not 100% support for it, mostly due to westernized developers not taking into account internationalization!
TRIVIA: Early versions of MSDOS only allowed eight characters for a filename with a 3 characters extension. Imagine working with those constraints!

I had the same problem. The only solution is:
Install TWRP http://forum.xda-developers.com/showthread.php?t=1782235
Reboot in recovery. Explore the files and delete whatever you want..

he e
trevd said:
when using the terminal rm command you need to escape special characters ( i.e spaces, parenthese etc ) with a backslash or put the file name in quotes. so you file name in question can be removed by
Code:
rm 11.\ Üuoö\ \(Über-unter-ober-österreicher\).mp3
or
Code:
rm "11. Üuoö (Über-unter-ober-österreicher).mp3"
you can also do wildcard deletion based on fragements of the file name i.e
Code:
rm 11*.mp3
will delete all files that start with 11 with the mp3 externsion or you could start with a wildcard so a named example_file_name.txt can be deleted using
Code:
rm *file*.txt
obviously that will delete ALL files that have the word file in the filename and an extension of .txt so BE CAREFUL WHEN USING WILDCARDS but you get the idea ( hopefully )
If that doesn't delete them then you've got problems.
---------- Post added at 01:06 PM ---------- Previous post was at 12:54 PM ----------
A little tip, If you're not from the old school you won't know that it best to avoid spaces and special characters in filenames especially as your transferring between different filesystem types, obviously unicode characters are kinda inevitable if that's you native language but a demestorated here there's not 100% support for it, mostly due to westernized developers not taking into account internationalization!
TRIVIA: Early versions of MSDOS only allowed eight characters for a filename with a 3 characters extension. Imagine working with those constraints!
Click to expand...
Click to collapse
Thanks, but it doesn't work. No matter if I use the backslash- or the paranthesis method, the emulator always tells me that it could not deleze as there is no such file or directory.

deb10042 said:
he e
Thanks, but it doesn't work. No matter if I use the backslash- or the paranthesis method, the emulator always tells me that it could not deleze as there is no such file or directory.
Click to expand...
Click to collapse
Just use TWRP if your unlocked. It will take care of it. ( see link in my sig)

Success!!
runandhide05 said:
Just use TWRP if your unlocked. It will take care of it. ( see link in my sig)
Click to expand...
Click to collapse
Finally, I gathered all my courage and installed TWRP over my old CWM Recovery without doing any backups
And...yes, it did the trick!!
I was able to delete all the corrupted files and folders and everything else is still in place :good:
Thanks for your good help!

deb10042 said:
Finally, I gathered all my courage and installed TWRP over my old CWM Recovery without doing any backups
And...yes, it did the trick!!
I was able to delete all the corrupted files and folders and everything else is still in place :good:
Thanks for your good help!
Click to expand...
Click to collapse
Glad you got it working! Now would be a good time to make a backup with twrp because cwm backups will not work with twrp and vice versa

runandhide05 said:
Glad you got it working! Now would be a good time to make a backup with twrp because cwm backups will not work with twrp and vice versa
Click to expand...
Click to collapse
Oups! :cyclops:
Thanks, that was really a good hint! Didn't know that and will do it at once after coming home this evening
Will it be difficult, to go back to CWM? ...just in case...

[GUIDE][SCRIPT] How to root Android x86 4.3

As we all know, Android 4.3 brought with it some extra security features which caused some small issues with root. These have been solved by the likes of Chainfire and other developers, meaning we have root once more. This is their work, I've just botched it together to work on the Android x86 4.3 system, which works slightly differently
You will need:
A device with Android x86 4.3 on it
Optionals:
Another Linux based OS - this can be an OS on another partition on the device or a live disk/USB
Root permissions in that second OS and access to the terminal
Knowledge of which partition Android x86 is installed onto and which is its root folder (if you didn't mess with that, it tells you in the script)
Instructions:
On Android x86:
Download the attached zip and extract it using a file manager
Press Alt+F1 and use "cd" to change directory to where you extracted the zip
You should go as far in as the "README" and "install.sh" files
Run:
Code:
sh install.sh
Follow the instructions on-screen. It tells you the rest.
On a linux boot:
Download the attached zip and extract it to somewhere memorable
Open your terminal and use "cd" to change directory to where you extracted the zip. You should go as far in as the "README" and "install.sh" files
Run:
Code:
sh install.sh
Follow the instructions on-screen. It tells you the rest.
Reboot back into Android x86, it should have root now
Changelog:
v2:
Included version for Android x86 boot, through the Alt+F1 terminal
Made it a bit simpler
Screenshots
{
"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"
}
Credits
@Chainfire for SuperSU and all the files included that the script installs
The SuperSU thread, don't forget to thank on there
The Android x86 project for the OS itself and the init.sh file, which is patched as the install-recovery file is

Hello..
I try to run the install.sh but it said
"This script needs root. Enter your password to continue:
sh: 0: Can't open .install.sh"
I ran it with sudo permission. My Ubuntu is on sdb6 and and android is on sdb7.
Please assist.
Just wondering? Can I just copy the the system folder and let it overwrite (merge) the system folder in the android partition. Also what permission do I need to change for what folder if I were to do this manually.
Thanks minhgi

It hasn't extracted properly, the .install.sh file is in the zip with the install.sh
Just in case, for the next release (in testing now, can be run from the Android x86 boot itself), I made it ./.install.sh, which should work

Here comes version 2:
Changelog:
Included version for Android x86 boot, through the Alt+F1 terminal
Made it a bit simpler

Thanks Quinny,
It is working. Somehow when I downloaded the attachment the first time, the script folder was not there. So there was not script to run. Anyway, I did it through the Ubuntu terminal it is working for me.
---------- Post added at 02:49 PM ---------- Previous post was at 02:29 PM ----------
Opps..I said it to soo. I using an android build 4.3 from www.tabletx86.org and it use chainfire SU. It also seem like your rooting method use chainfire su. When I try to use root explorer to enable r/w permission, the app just force close. Also I try to launch chain su, it also force close. I am not sure if there is an incompatibiltiy issue there. I use the rom build from tabletx86 b/c it have broadcom wifi working for my laptop.
The android 4.3 from android-x86.org does not. Can you test the build from www.tabletx86.org? it was compile on 08-02-2013.
Thanks again.

minhgi said:
Thanks Quinny,
It is working. Somehow when I downloaded the attachment the first time, the script folder was not there. So there was not script to run. Anyway, I did it through the Ubuntu terminal it is working for me.
---------- Post added at 02:49 PM ---------- Previous post was at 02:29 PM ----------
Opps..I said it to soo. I using an android build 4.3 from www.tabletx86.org and it use chainfire SU. It also seem like your rooting method use chainfire su. When I try to use root explorer to enable r/w permission, the app just force close. Also I try to launch chain su, it also force close. I am not sure if there is an incompatibiltiy issue there. I use the rom build from tabletx86 b/c it have broadcom wifi working for my laptop.
The android 4.3 from android-x86.org does not. Can you test the build from www.tabletx86.org? it was compile on 08-02-2013.
Thanks again.
Click to expand...
Click to collapse
I'll have a go at some point, I'm on a slow connection currently so it might be a while

Quinny899 said:
I'll have a go at some point, I'm on a slow connection currently so it might be a while
Click to expand...
Click to collapse
not a problem. Please take you time. these builts are are preview version anyway.

minhgi said:
not a problem. Please take you time. these builts are are preview version anyway.
Click to expand...
Click to collapse
I looked this morning and it can't be run from the boot as it's got a broken superuser installed which means I can't mount the system. Don't see why it would force close though

So I tried doing the script via alt+f1 and it says its in root, then when the script runs it shows that it cant mount permission denied and it fails to remove old files and fails to chmod also. Any help would be appreciated. Thanks

wolfballz said:
So I tried doing the script via alt+f1 and it says its in root, then when the script runs it shows that it cant mount permission denied and it fails to remove old files and fails to chmod also. Any help would be appreciated. Thanks
Click to expand...
Click to collapse
If you're using TabletsX86's build, that's why, also, if you didn't allow /system to be mounted during install, then you're out of luck

Quinny899 said:
If you're using TabletsX86's build, that's why, also, if you didn't allow /system to be mounted during install, then you're out of luck
Click to expand...
Click to collapse
using latest build from android-x86.org and I didn't recall seeing anything about being able to mount /system during install.

wolfballz said:
using latest build from android-x86.org and I didn't recall seeing anything about being able to mount /system during install.
Click to expand...
Click to collapse
There is, right before you install.
Like so:
(Not my image)

Must have breezed right by it. Since i have it with windows how can i remove my current android install and start over? I ran the install again and i dont get that /system question at all.
So i tried installing on a virtual machine and i get the /system option now. Thanks for the help
Sent from my SCH-I535 using Xparent Blue Tapatalk 2

After installing on a virtual machine and mounting /system thw script ran without error. Rebooted but didnt see a superuser app so i installed supersu. Installed and opened root explorer and when trying to mount anything RW it hangs and then root explorer says not responding. Anything else i can try?
Sent from my SCH-I535 using Xparent Blue Tapatalk 2

Hello! I installed this, then a custom font. When I rebooted, I get stuck in a terminal. Any help?

Yoyodude1124 said:
Hello! I installed this, then a custom font. When I rebooted, I get stuck in a terminal. Any help?
Click to expand...
Click to collapse
Most likely the font. Did you set its permissions correctly?
Sent from my Galaxy Nexus using Tapatalk 4

Works perfect. I've used it twice now. Thanks.
If you get stuck in terminal you can type "start" to boot android.
Sent from my Lenovo Thinkpad Edge using Tapatalk 4

Unlockable bootloader/custom roms?
Is there any way to get custom recoveries on this, so we could install custom ROMs?

Yoyodude1124 said:
Is there any way to get custom recoveries on this, so we could install custom ROMs?
Click to expand...
Click to collapse
Nope. And there won't be ROMs like CM or the like, x86 is completely different to ARM and they're highly unlikely to make it compatible

I also only get the question whether to install /system as r/w with builds before 4.3. Using the boot image of 4.2 of course results in a mess but it takes me to the screen where I can choose to use system as r/w or read only.
Tried with a freshly fixed mbr and clean install.

ZTE Maven root (Z831)

Here's how I got my zte maven 2 (ATT) rooted.
Disclaimer: This method worked for me but may not work for others, I am not responsible if your device is bricked as a result of this. Also, this method does seem to be a bit finicky and inconsistent.
I rooted this phone twice, and it took about 15-20 tries each time for it to finally work. This is not a root you can do in 5 minutes (unless you are extremely lucky) Plan to set aside an hour or two, and a lot of patience, if you want this to work.
Credit to @madvane20 his post here helped me get root for this phone. He also got his phone rooted before I did, be sure to give him thanks.
Credit to @ZTE Girl for finding a way to remove ads from King root and keeping perm root.
With KingRoot you can get perm root, but personally I hate KingRoot, so at the end there is a method to replace KingRoot with SuperSu. Unfortunately SuperSu root resets on reboot, but a quick, 10 second adb command will reroot your phone with SuperSu
Edit: @ZTE Girl found that using lucky patcher to remove ads from King root worked for her and kept permroot.
Step 1: Enable USB debugging on your phone, and download adb and ZTE drivers to your PC.
2: Download KingRoot from KingRoot.net (download the apk for android)
3: Connect your phone to ADB, and run this command in terminal adb shell make sure you get no errors and accept any USB debugging requests.
4: Now type reboot disemmcwp This will reboot your phone without write protection.
5: When your phone reboots, run adb shell again, and install the kingroot APK. Google will give you a warning about this app being unsafe, install it anyways.
6: Now, here's the finicky part, sometimes KingRoot works, sometimes it doesn't, you just have to keep trying. Make sure your phone is still connected to the computer through adb shell, and then click try root in KingRoot. While KingRoot is attempting to get root: in adb shell keep typing su and pressing enter. Just spam this, It will keep giving errors, but eventually it (should) work. Make sure to accept any prompts on your device while you do this.
7: When you are able to successfully get into su, wait a bit, just to make sure your device doesn't restart
8: Now type getprop ro.product.name, the response should be Z831
9: Now type setprop persist.sys.k Z831, then type getprop persist.sys.k It should say Z831
10: Now type cd /dev/block/platform/soc.0/7824900.sdhci/by-name/
11: Then type dd if=recovery of=/sdcard/recovery.img This will backup your recovery, I highly recommend that you copy the backup to your computer in case something goes wrong.
12: Now type dd if=boot of=recovery, this will write boot to recovery. This part can be risky, it worked for me, but if it bricks your device, you can't say I didn't warn you with that said, don't let that scare you away from finally rooting this device and getting all the advantages that come with it
13: Now type this reboot recovery Your device my blackscreen and not boot after this, personally mine did, and I fixed it by removing the battery, and after puttting it back in, it booted normally.
14: When your phone boots up, type adb shell again, and then type su
15: Type id response should be "uid=0(root) gid=0(root) context=u:r:shell:s0" Note: I don't think my uid showed when I did this, if yours doesn't show, don't worry, it should work fine.
16: Now type setenforce 0
17: After that, type getenforce, it should respond back with "permissive"
18: To test if system is writable, type mount -o remount,rw /system, if you get no errors, everything is working , if you get an error, type reboot disemmcwp, and then try to mount system RW again.
19: I would recommend removing the update service now, so an update doesn't come and screw up your root.
20: Read this: Now you should have permroot with kingroot, however, as you will soon find, kingroot has a ton of ads, and can get very annoying. So, if you want SuperSu and no kingroot, keep reading. If you want to keep KingRoot, then you are done, have fun with your rooted Maven 2
Edit: @ZTE Girl found that you can use lucky patcher to remove ads from Kingroot while still keeping permroot.
21: Download the KingToSuperSu zip in attachments, I have modified it slightly from the original zip so it works better. You will see a folder inside the zip named "mrw" copy this folder to the root of your /sdcard (must be copied to the root of /sdcard)
22: Now go into adb shell again, and then type su
23: Type mount -o remount,rw /system
24: If you get no errors, simply type sh /sdcard/mrw/root.sh, you will see a lot of errors in the script, no need to worry, now you should have SuperSu. Note: sometimes you get a notification saying "com.eu.chainfireSuperSu has stopped" or something like that, run the command again, and it should work.
25: SuperSu will say binary needs to be updated, but the update always fails, however you can click no thanks, and it will work fine.
26: SuperSu root will go away after you reboot, however, to get root back, simply type adb shell (while connected to your computer of course) then su and then sh /sdcard/mrw/root.sh and just like that, you're rooted again. Note: I couldn't get this to work in a terminal emulator, and it would only work in adb shell for me.
Edit: If you want stock recovery back, run this command in adb shell with su dd of=recovery if=/sdcard/recovery.img. I haven't tested this, and it might unroot/brick your device. This is at your own risk.
This guide was long and complicated, sorry for that, if you need any help, just ask me and I will try to help the best I can.
If this guide helped, please clicks thanks, it means a lot to me
Proof: http://imgur.com/a/zecyU

btw easy way to get rid of ads diasbale the charging thing in king settings and adaway its what i did on the warp 7

carrier iq
this phone has carrier iq, i was able to get temp root without write using kingroot, so i was able to delete, disable apps, and also, remove carrier iq with the quide you can find on the: androidexplained website. i could not actually delete the files in the last two steps but it seemed to work anyway. this is my first post so i can't put links.
Question1: i don't like typing cause i make stupid mistakes, but im assuming i could put all your command in individual batch files ending with a pause on each, and prefixing all you commands with "adb.exe shell su". that way i could stop and see what happened and then continue.
Question2:
dd if=recovery of=/sdcard/recovery.img
seems to mean copy the boot partion to an image file on the internal sd card. am i correct?
and
dd if=boot of=recovery
seems to mean overwrite the boot partition with an image- (file)?
if so what image file?
sorry, im new to all this, i guess i probably don't have enough confidence to do this, my z831 works very well without all the bloat anyway. and yes i understand the risks if i do decide to proceed, anyway. i have 3 $10 and $20 phones that are not bricked but i forgot to reenable the system apps before i removed root and reset, so they might as well be bricked cause they cant do anything after they boot.
btw, you mentioned in one step to wait, to see if it reboots, to see if it is stable before continuing:
for me i remember that either having too many apps running or stopping too many system apps, seemed to make this z831 unstable and reboot, while it had temp root.
Question last: do i need to start the process as you said while kingroot is in the process of rooting, or can i wait till it is finished getting it's root?

duane2064 said:
this phone has carrier iq, i was able to get temp root without write using kingroot, so i was able to delete, disable apps, and also, remove carrier iq with the quide you can find on the: androidexplained website. i could not actually delete the files in the last two steps but it seemed to work anyway. this is my first post so i can't put links.
Question1: i don't like typing cause i make stupid mistakes, but im assuming i could put all your command in individual batch files ending with a pause on each, and prefixing all you commands with "adb.exe shell su". that way i could stop and see what happened and then continue.
Question2:
dd if=recovery of=/sdcard/recovery.img
seems to mean copy the boot partion to an image file on the internal sd card. am i correct?
and
dd if=boot of=recovery
seems to mean overwrite the boot partition with an image- (file)?
if so what image file?
sorry, im new to all this, i guess i probably don't have enough confidence to do this, my z831 works very well without all the bloat anyway. and yes i understand the risks if i do decide to proceed, anyway. i have 3 $10 and $20 phones that are not bricked but i forgot to reenable the system apps before i removed root and reset, so they might as well be bricked cause they cant do anything after they boot.
btw, you mentioned in one step to wait, to see if it reboots, to see if it is stable before continuing:
for me i remember that either having too many apps running or stopping too many system apps, seemed to make this z831 unstable and reboot, while it had temp root.
Question last: do i need to start the process as you said while kingroot is in the process of rooting, or can i wait till it is finished getting it's root?
Click to expand...
Click to collapse
i have a batch script i made for the warp 7 that i think will work for this phone but i never posted any of it cause he released the guide first so i told him to keep it and no the boot to recovery overwrites recovery with boot image from boot then after everything has perm root u can flash the recovery back to recovery. do we need a batch script no do we need to mess with other files risking a brick no kingroot is fine til we can find a way to get access to bootloader for fastboot as well as get a twrp built for the phone. theres ways to make kingroot not as annoying ad blocker disable notifications from kingroot and disable fastcharging lock screen. but u more than welcome to tamper just be aware u brick ur phone in the process theres no fix. as well if it makes it easier for people i will write a batch script that walks them through the process with the pauses shows them what it does so they can learn for future purpose but i m0ean the guides pretty simple
---------- Post added at 01:55 PM ---------- Previous post was at 01:51 PM ----------
wait is this thread maven or maven 2?

step 9 is different than yours, why?
Question for madvane20
XCnathan32's step 9: "Now type
setprop persist.sys.k Z831
BUT in your bat file:
adb.exe shell su
setprop ro.product.name Z831
of course swaping out ZTE_BEAM for Z831
is one better than the other or should they both be done?

yea i think i need to maybe fix the bat but im working on stuff atm got rl stuff im busy with but once im done i will finish a bat for the warp 7 and one for this phone. but yes u swap the name of the phone out for what phone u have.
---------- Post added at 03:26 PM ---------- Previous post was at 03:25 PM ----------
the warp 7 has different name etc so yea the warp 7 post is different im trying to work on everything as well keep working on my huawei ascend xt as well real life stuff

Question for madvane20, im sorry, i meant persist.sys.k OR setprop ro.product.name, this is the discrepancy in the two instructions.

did u read the guide for the zte maven 2 and also look at the guide for the warp 7 u will see the difference it just takes u to read them then u shouldnt have any questions

is this syntax correct, before i try it?
batch.txt:
https://dl.xda-developers.com/4/2/2/0/4/0/3/batchfiles.txt?key=NgPk58hMrJO5QXnvDcnCPw&ts=1500762566

if anyone wants to ask me questions just pm me or get ahole of me on hangouts im listed as dav ril or madvane20

I have used Wugfresh's NRT with my previous Nexus devices with stellar results and I downloaded ADB to try your guys method with a Z831 however, I need ti know if this guide is Android version specific? I recently went from 5.1.1 to 7.1.1 in like 3 OTA AT&T updates, so this device is running Nougat. Also, is PIE something new to 7.0 ? I read somewhere this affects the root process. Why do they have "Unlock bootloader" option in Dev settings ? Can I just run an ADB command to enable Write permission to delete 40-50 #/System/App .apk's?

Yo OP, I genuinely appreciate you sharing this. I found that everything has worked perfectly. I managed to get perm root and I just tried to install SU, gonna see if it worked. Thanks bro
Sent from my N9519 using Tapatalk

So, is it working? please let me know because i also want to root it.
---------- Post added at 04:36 AM ---------- Previous post was at 04:27 AM ----------
How to install adb and Zte drivers on your computer? please reply

379068 said:
So, is it working? please let me know because i also want to root it.
---------- Post added at 04:36 AM ---------- Previous post was at 04:27 AM ----------
How to install adb and Zte drivers on your computer? please reply
Click to expand...
Click to collapse
The ZTE drivers should be on your phone. One of the mount options, when you plug in your phone is to install drivers.

This method really works. You can copy your recovery back after, you do not loose root. You are also able to re-root and make it permanent again after a factory reset, it is just takes many more exploit attempts. You can also install Xposed through Xposed Installer.
Anybody bought and tried Super-Sume Pro with this phone yet?

can thsi be done on other mavens?
Can you do this on a Maven 3 running nougat?

Is the root method working with ZTE Maven 3?
Anyone tried this on ZTE Maven 3? Got 2 from Bestbuy, would like to have them rooted.
Thanks.
Logos Ascetic said:
Can you do this on a Maven 3 running nougat?
Click to expand...
Click to collapse

I recently dissected the partition index and firmware structure of the ZTE Maven 3, in hopes of discovering a viable root exploit. Because it ships with stock Android Nougat, systemless root via patched boot image would be preferable. But, because the bootloader does not appear to be unlockable by any known method or exploit, systemless root is not currently an option. Accordingly, I focused on the less desirable method of system-mode rooting, which injects the SU daemon and corresponding root binaries to the Android OS by way of the /system partition directly. Again, an obstacle ensued: the stock kernel of the ZTE Maven 3 is secured by AVB 2.0/dm-verity (device mapping), which checks the /system partition for any modifications whatsoever prior to allowing the OS to boot. So, if /system is modified in any way, or so much as mounted r/w, a perpetual boot loop will commence via dm-verity.
So, in short, due to the locked bootloader state and verified boot/device mapping, safely & effectively rooting the stock Android Nougat OS of the ZTE Maven 3 doesn't presently appear to be feasible.
Note: I realize that the OP designated this as a ZTE Maven 2 thread, and I apologize to the OP if I'm off topic. I only addressed the Maven 3 because of the number of questions in the thread.

I have the z831 through at&t. I'm pretty sure I unlocked the bootloader in developer options as nothing would root the phone until I turned it on. Everything worked, but is there a custom recovery or rom?

kingroot.net even if you choose english gives you a chinese app

[DEVELOPMENT][PATCH][FIX] Zenfone 3 Corrupt BASEBAND IMEI WIFI (ZE520KL | ZE552KL)

Hello Everyone. I am X.O here,
This thread is to catch attention to my fellow developers and contributors and even advanced users of this device Zenfone 3.
I've been seeing that a lot of users and developers of this device are getting their phones bricked and corrupting the BASEBAND, IMEI, WLAN/BT MAC, SERIAL NO. and so on just by using the official RAW firmwares available for this device.
Yet no one has the solution to the problems whatsoever.
I've browsed a lot and found no supportive files in order to fix the problems i was facing.
Let's get to the point now.
I need support of any user, developer or contributor who is currently using this phone and has ROOT in it.
Partition backup files are required in order to put a solve into the issues mentioned above.
PLEASE, IT IS A REQUEST TO ALL OF THE PEOPLE WHO ARE CURRENTLY SEEING THIS THREAD!!
--- UPLOAD THE REQUIRED FILES AND SUPPORT THIS COMMUNITY FOR PATCHES & FIXES ---
System Requirements:
-- ROOT
-- TERMINAL EMULATOR or A COMPUTER
-- Working Brain LOL!
PREPARATION:
-- Unlock Bootloader of your device.
-- ROOT your device.
~~ FOR ANDROID ~~
-- Download and Install Gboard (link)(Google Keyboard for typing into Terminal Emulator |OTHER KEYBOARD DO NOT WORK|
-- Download and Install Terminal Emulator (link)
-- Type "su" press Enter (Grant SuperSU permission)
-- Type the following commands accordingly.
Code:
dd if=/dev/block/mmcblk0p24 of=/sdcard/FSG
dd if=/dev/block/mmcblk0p26 of=/sdcard/MODEMST1
dd if=/dev/block/mmcblk0p27 of=/sdcard/MODEMST2
dd if=/dev/block/mmcblk0p56 of=/sdcard/PERSIST
dd if=/dev/block/mmcblk0p35 of=/sdcard/PERSISTENT
dd if=/dev/block/mmcblk0p21 of=/sdcard/SEC
dd if=/dev/block/mmcblk0p22 of=/sdcard/DEVINFO
dd if=/dev/block/mmcblk0p28 of=/sdcard/FACTORY
dd if=/dev/block/mmcblk0p25 of=/sdcard/FSC
dd if=/dev/block/mmcblk0p50 of=/sdcard/FSGCA
dd if=/dev/block/mmcblk0p44 of=/sdcard/MCFG
dd if=/dev/block/mmcblk0p37 of=/sdcard/MISC
dd if=/dev/block/mmcblk0p52 of=/sdcard/OEM
dd if=/dev/block/mmcblk0p43 of=/sdcard/SYSCFG
dd if=/dev/block/mmcblk0p23 of=/sdcard/SYSINFO
(You'll get something like this as output.)
{
"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"
}
-- Zip the files created in SDCARD, zip all the files and send as attachment to me at [email protected] or upload at any file sharing server such as MediaFIre
~~ FOR COMPUTER RUNNING WINDOWS ~~
-- Install Minimal ADB and Fastboot (link)
-- Open "Minimal ADB and Fastboot" window.
-- Type "adb shell" Press Enter.
-- Type "su" and grant SuperSU permission on phone.
-- Type the following commands accordingly. (You can copy and paste each line to the CMD window if you want.)
Code:
dd if=/dev/block/mmcblk0p24 of=/sdcard/FSG
dd if=/dev/block/mmcblk0p26 of=/sdcard/MODEMST1
dd if=/dev/block/mmcblk0p27 of=/sdcard/MODEMST2
dd if=/dev/block/mmcblk0p56 of=/sdcard/PERSIST
dd if=/dev/block/mmcblk0p35 of=/sdcard/PERSISTENT
dd if=/dev/block/mmcblk0p21 of=/sdcard/SEC
dd if=/dev/block/mmcblk0p22 of=/sdcard/DEVINFO
dd if=/dev/block/mmcblk0p28 of=/sdcard/FACTORY
dd if=/dev/block/mmcblk0p25 of=/sdcard/FSC
dd if=/dev/block/mmcblk0p50 of=/sdcard/FSGCA
dd if=/dev/block/mmcblk0p44 of=/sdcard/MCFG
dd if=/dev/block/mmcblk0p37 of=/sdcard/MISC
dd if=/dev/block/mmcblk0p52 of=/sdcard/OEM
dd if=/dev/block/mmcblk0p43 of=/sdcard/SYSCFG
dd if=/dev/block/mmcblk0p23 of=/sdcard/SYSINFO
(You'll get something like this as output.)
-- Now ZIP the mentioned files found on SDCARD and email at [email protected] or upload at any file sharing server such as MediaFIre
Here is an important note to everyone who will be curious to what i asked for in this thread. This is only for development and fixing purposes and i hold no grudge to destroy your privacy or private data including your personal IMEI, SN, MAC.
I will surely change all of the security data that are collected from your phone to 0s or 1s. You get to keep your super secret security info.
Click to expand...
Click to collapse
I WILL DEFINITELY MENTION THE NAME OF THE CONTRIBUTOR(S) WHO WILL SEND ME THE FILES.
Click to expand...
Click to collapse
And for the fixes, i will work on the files and make easy fixes available to everyone as soon as i get the files.
Click to expand...
Click to collapse
Thank you for your support.
Click to expand...
Click to collapse
​
Click to expand...
Click to collapse
Tags for your attention : @shakalaca @anhenrique @kyle_l88 @cdanthien @aswindivakar100 @OxYTooN @animaanimus @mdigiacomi @itsme.Ronjie @EypCnn @cdanthien

Xtreme.Ornob said:
Hello Everyone. I am X.O here,
This thread is to catch attention to my fellow developers and contributors and even advanced users of this device Zenfone 3.
I've been seeing that a lot of users and developers of this device are getting their phones bricked and corrupting the BASEBAND, IMEI, WLAN/BT MAC, SERIAL NO. and so on just by using the official RAW firmwares available for this device.
Yet no one has the solution to the problems whatsoever.
I've browsed a lot and found no supportive files in order to fix the problems i was facing.
Let's get to the point now.
I need support of any user, developer or contributor who is currently using this phone and has ROOT in it.
Partition backup files are required in order to put a solve into the issues mentioned above.
PLEASE, IT IS A REQUEST TO ALL OF THE PEOPLE WHO ARE CURRENTLY SEEING THIS THREAD!!
--- UPLOAD THE REQUIRED FILES AND SUPPORT THIS COMMUNITY FOR PATCHES & FIXES ---
System Requirements:
-- ROOT
-- TERMINAL EMULATOR or A COMPUTER
-- Working Brain LOL!
PREPARATION:
-- Unlock Bootloader of your device.
-- ROOT your device.
~~ FOR ANDROID ~~
-- Download and Install Gboard (link)(Google Keyboard for typing into Terminal Emulator |OTHER KEYBOARD DO NOT WORK|
-- Download and Install Terminal Emulator (link)
-- Type "su" press Enter (Grant SuperSU permission)
-- Type the following commands accordingly.
Code:
dd if=/dev/block/mmcblk0p24 of=/sdcard/FSG
dd if=/dev/block/mmcblk0p26 of=/sdcard/MODEMST1
dd if=/dev/block/mmcblk0p27 of=/sdcard/MODEMST2
dd if=/dev/block/mmcblk0p56 of=/sdcard/PERSIST
dd if=/dev/block/mmcblk0p35 of=/sdcard/PERSISTENT
dd if=/dev/block/mmcblk0p21 of=/sdcard/SEC
dd if=/dev/block/mmcblk0p22 of=/sdcard/DEVINFO
dd if=/dev/block/mmcblk0p28 of=/sdcard/FACTORY
dd if=/dev/block/mmcblk0p25 of=/sdcard/FSC
dd if=/dev/block/mmcblk0p50 of=/sdcard/FSGCA
dd if=/dev/block/mmcblk0p44 of=/sdcard/MCFG
dd if=/dev/block/mmcblk0p37 of=/sdcard/MISC
dd if=/dev/block/mmcblk0p52 of=/sdcard/OEM
dd if=/dev/block/mmcblk0p43 of=/sdcard/SYSCFG
dd if=/dev/block/mmcblk0p23 of=/sdcard/SYSINFO
(You'll get something like this as output.)
-- Zip the files created in SDCARD, zip all the files and send as attachment to me at [email protected] or upload at any file sharing server such as MediaFIre
~~ FOR COMPUTER RUNNING WINDOWS ~~
-- Install Minimal ADB and Fastboot (link)
-- Open "Minimal ADB and Fastboot" window.
-- Type "adb shell" Press Enter.
-- Type "su" and grant SuperSU permission on phone.
-- Type the following commands accordingly. (You can copy and paste each line to the CMD window if you want.)
Code:
dd if=/dev/block/mmcblk0p24 of=/sdcard/FSG
dd if=/dev/block/mmcblk0p26 of=/sdcard/MODEMST1
dd if=/dev/block/mmcblk0p27 of=/sdcard/MODEMST2
dd if=/dev/block/mmcblk0p56 of=/sdcard/PERSIST
dd if=/dev/block/mmcblk0p35 of=/sdcard/PERSISTENT
dd if=/dev/block/mmcblk0p21 of=/sdcard/SEC
dd if=/dev/block/mmcblk0p22 of=/sdcard/DEVINFO
dd if=/dev/block/mmcblk0p28 of=/sdcard/FACTORY
dd if=/dev/block/mmcblk0p25 of=/sdcard/FSC
dd if=/dev/block/mmcblk0p50 of=/sdcard/FSGCA
dd if=/dev/block/mmcblk0p44 of=/sdcard/MCFG
dd if=/dev/block/mmcblk0p37 of=/sdcard/MISC
dd if=/dev/block/mmcblk0p52 of=/sdcard/OEM
dd if=/dev/block/mmcblk0p43 of=/sdcard/SYSCFG
dd if=/dev/block/mmcblk0p23 of=/sdcard/SYSINFO
(You'll get something like this as output.)
-- Now ZIP the mentioned files found on SDCARD and email at [email protected] or upload at any file sharing server such as MediaFIre
​
Tags for your attention : @shakalaca @anhenrique @kyle_l88 @cdanthien @aswindivakar100 @OxYTooN @animaanimus @mdigiacomi @itsme.Ronjie @EypCnn @cdanthien
Click to expand...
Click to collapse
If you flash Official RAW (13.20.10.137) and the IMEI/Baseband/WiFi doesn't work, follow this thread
https://www.asus.com/zentalk/forum.php?mod=viewthread&tid=164531&page=1&extra=#pid675648
P.S: No root is needed

Brother, i need to make a fix for this device, in general words, the fix will solve the problem in a more easy way.
This also is for them who lost their baseband, tried to repair it and lost the original baseband data (modemst1,
modemst2, fsg etc).
I need the files to make patches for easier fixes, that's all. The original fsg, fsgCA of my phone is zeroed out brother. No returning of baseband from that. I hope you understand my theory.
ZenFoneThree said:
If you flash Official RAW (13.20.10.137) and the IMEI/Baseband/WiFi doesn't work, follow this thread
https://www.asus.com/zentalk/forum.php?mod=viewthread&tid=164531&page=1&extra=#pid675648
P.S: No root is needed
Click to expand...
Click to collapse

ZenFoneThree said:
If you flash Official RAW (13.20.10.137) and the IMEI/Baseband/WiFi doesn't work, follow this thread
https://www.asus.com/zentalk/forum.php?mod=viewthread&tid=164531&page=1&extra=#pid675648
P.S: No root is needed
Click to expand...
Click to collapse
His mean that he fix the issues not face that issues bro.

Xtreme.Ornob said:
Brother, i need to make a fix for this device, in general words, the fix will solve the problem in a more easy way.
This also is for them who lost their baseband, tried to repair it and lost the original baseband data (modemst1,
modemst2, fsg etc).
I need the files to make patches for easier fixes, that's all. The original fsg, fsgCA of my phone is zeroed out brother. No returning of baseband from that. I hope you understand my theory.
Click to expand...
Click to collapse
Bro, do you have QFIL files for ZF3? My friend hard-bricked his phone

[email protected]@ said:
His mean that he fix the issues not face that issues bro.
Click to expand...
Click to collapse
Bro, the link I posted also fix the issues. Not face the issue
---------- Post added at 01:15 PM ---------- Previous post was at 01:11 PM ----------
Xtreme.Ornob said:
Brother, i need to make a fix for this device, in general words, the fix will solve the problem in a more easy way.
This also is for them who lost their baseband, tried to repair it and lost the original baseband data (modemst1,
modemst2, fsg etc).
I need the files to make patches for easier fixes, that's all. The original fsg, fsgCA of my phone is zeroed out brother. No returning of baseband from that. I hope you understand my theory.
Click to expand...
Click to collapse
Oh, I thought flashing the RAW wiped out your modem. Sorry for misunderstanding.

I do have the problem for myself, i just want to help myself and the community as a lot of people are currently facing the hard bricks and unknown baseband. If anyone would be kind enough to upload the files to me, i will mention the contributor's name on my fix thread. Thank you.
[email protected]@ said:
His mean that he fix the issues not face that issues bro.
Click to expand...
Click to collapse

I can boot up your phone for sure. The files are in a very far sophisticated condition. Neither you nor anyone can use the method i have been developing. So you need to share screens for support. You need to be in TeamViewer in order to get it working.
Firstly, see if the device is detected in QDloader 9008 or HS-Diagnostics 900E port, then text me on facebook (link) or send an email to [email protected]
SaktisWRXSTi said:
Bro, do you have QFIL files for ZF3? My friend hard-bricked his phone
Click to expand...
Click to collapse

Do you think you can supply the files? If so, then it is highly appreciated.
ZenFoneThree said:
Bro, the link I posted also fix the issues. Not face the issue
---------- Post added at 01:15 PM ---------- Previous post was at 01:11 PM ----------
Oh, I thought flashing the RAW wiped out your modem. Sorry for misunderstanding.
Click to expand...
Click to collapse

@Xtreme.Ornob if you download an Asus firmware and open it you can find some files and folder. In firmware-update folder there are all 'other partition' files included qfil (but has a different name)
But if you wanna unbrick your hard bricked device (Qualcomm port 9008) you can't

Brother, i see that you are assuming me a newbie in this field. Don't just assume bro.
I have collected and patched some files. I will update the thread real soon.
Will open another thread for unbricking from QDloader 9008 and also from Diagnostics 900E.
God bless you.
ExperienceTesla said:
@Xtreme.Ornob if you download an Asus firmware and open it you can find some files and folder. In firmware-update folder there are all 'other partition' files included qfil (but has a different name)
But if you wanna unbrick your hard bricked device (Qualcomm port 9008) you can't
Click to expand...
Click to collapse

Hello Xtreme.Ornob,
If you have the files for QFIL Flashing, you should upload those files. Many of the users are facing hardbricks and it'll help them. Make a new thread for Qualcomm Flashing.

ra_si said:
Hello Xtreme.Ornob,
If you have the files for QFIL Flashing, you should upload those files. Many of the users are facing hardbricks and it'll help them. Make a new thread for Qualcomm Flashing.
Click to expand...
Click to collapse
I have QFIL for both ZE520KL & ZE552KL

Asus_x008D
Hi there! i have the same problem and i tried to follow the instruction. But i have this issue, my phone model ZC520TL is not in the asus Flash tool Model selection. What should i do? Thanks for the help

ZenFone_3 said:
I have QFIL for both ZE520KL & ZE552KL
Click to expand...
Click to collapse
That's good.
Why don't you make a new thread for QFIL files and make it available for all.

ra_si said:
That's good.
Why don't you make a new thread for QFIL files and make it available for all.
Click to expand...
Click to collapse
Thread is live now
https://forum.xda-developers.com/zenfone-3/development/unbrick-qfil-zenfone-3-t3759473

test point
Saktis_STi said:
Thread is live now
https://forum.xda-developers.com/zenfone-3/development/unbrick-qfil-zenfone-3-t3759473
Click to expand...
Click to collapse
Xtreme.Ornob said:
Brother, i see that you are assuming me a newbie in this field. Don't just assume bro.
I have collected and patched some files. I will update the thread real soon.
Will open another thread for unbricking from QDloader 9008 and also from Diagnostics 900E.
God bless you.
Click to expand...
Click to collapse
Test point picture
https://ibb.co/caTY9d.

I have a problem with the wifi, it does not start. Can you solve it?