Hi,
in fastboot mode on my device, the volume up key is not recognized but this key perfectly work in android OS.
I tried opening lk.bin with an hex editor and I can see all the fastboot commands and some variables (the file is very long...).
Is it possible to edit it for implement the volume up key (the volume down work perfectly) or delete the confirmation for the oem unlock ?
TY :good:
Have thee same problem and have same question
Is there anyone out there to help?
also need this for a figo gravity x55l
GREAT NEWS I MANAGED TO GET ROOT WITHOUT UNLOCKING THE BOOTLOADER ALL YOU NEED IS TO
1.download your firmware and extract it
2.extract the boot.img from the firmware and put it on your phone REMEMBER WHERE YOU PUT IT SINCE YOU WILL NEED THIS!
3download magiskmanager install it and open it.
4click install and choose the boot.img it will install magisk into it
5.put it back in your firmware folder on your pc
6 look for a file that says Checksum_gen and run it
7 once that completes use spflash tool and load your scatterfile and flash JUST THE BOOT.IMG wait for the reboot and you have root!
THANK YOU DEVELOPERS OF MAGISKMANAGER!
Related
Anyone know about any custom room or kernel or recovery that works on Asus Live (G500TG / Z00YD) ?
I searched everywhere and didn't found anything custom for this model.
Please help.
I need recovery image of this model. Could you provide me a copy of your recovery?
ralp5628 said:
I need recovery image of this model. Could you provide me a copy of your recovery?
Click to expand...
Click to collapse
I'm using all stock.
You can get it from http://dlcdnet.asus.com/pub/ASUS/ZenFone/G500TG/UL-G500TG_ASUS_Z00YD-WW-12.0.0.41-user.zip
I didn't find a recovery image within that file. The only thing I can access is fastboot. My recovery is broken, my system doesn't boot (bootloop). :crying: :crying:
personal HELLO I also need recovery.img Asus Live (G500TG) Z00YD
I've managed to extract the system files (and kernel) from the zip, but no luck in flashing it back using fastboot. I think the problem is in the conversion from raw image to sparse (that fastboot uses).
To extract system raw ext4 partition from zip:
http://forum.xda-developers.com/and...-conver-lollipop-dat-files-to-t2978952/page11
To unpack boot.img:
http://forum.xda-developers.com/showthread.php?t=443994
The idea now is trying to boot from a ramdisk in the pc, to start adb service.
Guys, I figured out how to reverse the situation of hard brick.
1) First you need to download the kernel source code on the asus website. The file name is: ASUS Live (G500TG) Kernel Code (V12.0.0.26). Here is:
http :// dlcdnet.asus .com/pub/ASUS/ZenFone/G500TG/G500TG_Kernel_V12_0_0_26.zip?_ga=1.213911127.1348745149.1467264204
Inside it there are the images of all partitions, including scatter file.
2) You will need to download a program called SP Flash tool. Here: http :// spflashtool .com/. I'm currently using v5.1628
3) Open the tool flash sp as administrator (on Windows) or administrator privileges (using sudo on linux).
4) Extract the downloaded file and select the scatter file in sp flash tool.
5) Select download only.
6) Leave the phone without the battery for 30 seconds before connecting it to your computer. Put the battery again. Holding the - button (lower volume) connect it to the computer. Wait a bit and release the button. Click download in flash tool sp.
7) Wait until all the transfer is completed. After finishing connect the phone and put it to charge on power supply.
no select format+download, possible DTV problem in upgrade for new version
Alguém saber fazer alguma modificação no asus live? Bota outra rom, qualquer coisa? Entre em contato cmg 75988302133
ralp5628 said:
Guys, I figured out how to reverse the situation of hard brick.
1) First you need to download the kernel source code on the asus website. The file name is: ASUS Live (G500TG) Kernel Code (V12.0.0.26). Here is:
http :// dlcdnet.asus .com/pub/ASUS/ZenFone/G500TG/G500TG_Kernel_V12_0_0_26.zip?_ga=1.213911127.1348745149.1467264204
Inside it there are the images of all partitions, including scatter file.
2) You will need to download a program called SP Flash tool. Here: http :// spflashtool .com/. I'm currently using v5.1628
3) Open the tool flash sp as administrator (on Windows) or administrator privileges (using sudo on linux).
4) Extract the downloaded file and select the scatter file in sp flash tool.
5) Select download only.
6) Leave the phone without the battery for 30 seconds before connecting it to your computer. Put the battery again. Holding the - button (lower volume) connect it to the computer. Wait a bit and release the button. Click download in flash tool sp.
7) Wait until all the transfer is completed. After finishing connect the phone and put it to charge on power supply.
Click to expand...
Click to collapse
I don't get it, Where i put the extracted folder from the kernel source?
You need to extract the G500TG_Kernel_V12_0_0_26_zip.zip file and with the SP Flash Tool point to the scatter file inside the extracted folder. It will load all the partitions you just extracted.
ralp5628 said:
I didn't find a recovery image within that file. The only thing I can access is fastboot. My recovery is broken, my system doesn't boot (bootloop). :crying: :crying:
Click to expand...
Click to collapse
You fixed it?
vitorMndC said:
You fixed it?
Click to expand...
Click to collapse
Yessssss!! A long time ago.
I have a Malata n501(KitKat) upgraded to Malata max4(lollipop),have tried to flash a ported custom recovery but all effort to boot into it has proven abortive.
I have found out that the problem is due to me having a locked bootloader,I have tried to unlock it using the command " fastboot OEM unlock" but when I am prompted to confirm the action on my phone's screen with my volume + button nothing happens and the dialog remains on it.
I found out here on xda that the problem is the volume button was not integrated in the bootloader so ii doesn't work when in fastboot mode. The solution was a window tool was created to automatically patch the lk.bin to disable the need for confirmation when using OEM unlock command,its just carries out the process.
Unfortunately it wasn't a universal tool it was made for a particular phone make,so I couldn't make use of it.
So here is my reason of making this thread:
Can anyone help me patch it(my bootloader) to disable the volume button need such as stated above??
Or create a tool to patch it,preferably for windows os.
Thanks for any help rendered in making me use a custom recovery on my locked bootloader
hi anyone know the name of that program?
GREAT NEWS I MANAGED TO GET ROOT WITHOUT UNLOCKING THE BOOTLOADER ALL YOU NEED IS TO
1.download your firmware and extract it
2.extract the boot.img from the firmware and put it on your phone REMEMBER WHERE YOU PUT IT SINCE YOU WILL NEED THIS!
3download magiskmanager install it and open it.
4click install and choose the boot.img it will install magisk into it
5.put it back in your firmware folder on your pc
6 look for a file that says Checksum_gen and run it
7 once that completes use spflash tool and load your scatterfile and flash JUST THE BOOT.IMG wait for the reboot and you have root!
THANK YOU DEVELOPERS OF MAGISKMANAGER!
Tested for myself working (Xperia 5II)
All of the stuff and tutorials which is needed is already explained in the thread from @Miustone (https://forum.xda-developers.com/t/...g-with-magisk-and-flashing-firmwares.4177209/).
At this point also a big thanks for his guide. This helped me alot.
Download the new firmware from XperiFirm
Drag the file boot_***.sin from the new firmware over the Unsin.exe to get a patchable boot.img for Magisk
Copy this boot.img to your phone and patch it through Magisk to get the magisk_patched.img and copy this to your platform tools folder
Now delete the "persist.sin" and "userdata.sin" in the firmware folder (so your userdata won't be deleted)
Copy the remaining files to the Newflasher folder
Shut down your phone - hold the volume down and connect your phone with your pc
Start Newflasher.exe and in the prompt press f,n,n - wait for installation and close prompt
(After the installation my phone didn't boot into fastboot mode so if you see still a green light on led notification on your phone after installation please unplug usb cable - press volume up and reconnect the usb cable - blue light for fastboot mode)
In fastboot mode install the magisk_patched.img file to slot a and b to maintain root
First startup from new firmware will take some time but for me it booted up and everything is working and all of my data still remain.
isn't it possible to update using the OTA updates if we relock the bootloader? (while still keeping magisk)
or maybe we need to relock, unroot then install updates and root again?
dgmortal said:
isn't it possible to update using the OTA updates if we relock the bootloader? (while still keeping magisk)
or maybe we need to relock, unroot then install updates and root again?
Click to expand...
Click to collapse
You can't boot If rooted and relocked. So this is the only way besides maybe having TWRP and Zips which do include the Firmware Parts Like Modem, Bootloader etc.
T3chDelicious said:
Tested for myself working (Xperia 5II)
All of the stuff and tutorials which is needed is already explained in the thread from @Miustone (https://forum.xda-developers.com/t/...g-with-magisk-and-flashing-firmwares.4177209/).
At this point also a big thanks for his guide. This helped me alot.
Download the new firmware from XperiFirm
Drag the file boot_***.sin from the new firmware over the Unsin.exe to get a patchable boot.img for Magisk
Copy this boot.img to your phone and patch it through Magisk to get the magisk_patched.img and copy this to your platform tools folder
Now delete the "persist.sin" and "userdata.sin" in the firmware folder (so your userdata won't be deleted)
Copy the remaining files to the Newflasher folder
Shut down your phone - hold the volume down and connect your phone with your pc
Start Newflasher.exe and in the prompt press f,n,n - wait for installation and close prompt
(After the installation my phone didn't boot into fastboot mode so if you see still a green light on led notification on your phone after installation please unplug usb cable - press volume up and reconnect the usb cable - blue light for fastboot mode)
In fastboot mode install the magisk_patched.img file to slot a and b to maintain root
First startup from new firmware will take some time but for me it booted up and everything is working and all of my data still remain.
Click to expand...
Click to collapse
Is this working from 10 to 11?
no app to do these steps? OxygenUpdater sort of..
Can you lock the bootloader if you remove the root? I only want root to modify one app (need call recording), after that I'd be more happy without root (compatibility, updates and potential for instability)
Hello everyone! This is my first post, I'm very very new here If I somehow missed a rule or two and shouldn't have posted here or etc DO TELL ME, Im open to anything and I appreciate it! To the point, I won't stretch the topic, I'll tell you how I rooted my Gionee x1 device, and the problems I faced and their solutions. You may ask yourselves or just come reply here, Who even owns that device, Well I own one and I wasn't able to root this device it was hard, so for the other mates out their having bought this piece of brick.
and, there's a reason to why Im writing this topic, do read to the end.
So, to start I first of all researched alot both on google and xda forums for any way of doing it, most of which either didn't work or were not supporting my device(f.e. One Click Root Methods didn't work at all).
1. This post has a reply by ZedLens, which is awesome but to my surprise it didn't work for me.
2. This post BusinessKid is a great tutorial for any MTK Device, but the 3rd step of "The Download Stuff:" I couldn't find the scatter for my device.
3. I've a strict download limit for my internet, so I couldn't download the Stock ROM, so I somehow had to extract it from my device, which I failed why? MTK Droid Tool wasn't able to recognize my device. I diagnosed for all possible reasons for this, bad USB check, bad device port check, wrong process check nothing worked, so at the end of the day I somehow managed to download the Stock ROM of Gionee X1 and EVERYONE HAS TO DO IT IN THE END, you'll really need it anyhow.
Now the rooting process,
Tools/Stuff I used:
1. SP Flash Tool(This thing here, is like your hand during examination)
2. MTK Drivers(Important)
3. Stock Gionee X1 ROM
4. Magisk Manager App
I'll attach the Magisk Patched boot.img here along with the scatter so that you can directly flash the boot img instead of wasting time to download the stock rom and etc etc. also you can reply down here if you need any other file, I'll send it to you somehow :3
NOTE: All the images, links, tools, programs and everything belong to their respective owners!! Everything you are doing with the steps above are STIRCTLY your responsibility, if you do it wrong and brick your device you can't charge me for bricking your device, only you and you will be held responsible for any damage/sucess/etc to your device.
Steps to install:
1. Get Stock boot img
2. Install Magisk Manager (DON'T DOWNLOAD IT FROM ANYWHERE use TopJohnWu's Github)
3. Somehow get the Stock boot img into your Internal Storage or anywhere, where Magisk Manager can find and Patch it, Use adb push, connect usb and copy it to the Internal Storage, ANYHOW.
4. After copying, Open Magisk Manager, you'll find two things on the main screen, one is Magisk which has status infos such as (Installed: ), (SAR: ), (A/B: ) and (RAMDISK: ). Within the same square which contains those status info you'll find a Install click on it.
4.1. After clicking on install you'll get a new menu, select next in the Options Square ignoring the choices there(Preserve AVB 2.0 blah blah) and click Next. Now you'll be in the Methods Square here, you select "Select and Patch a File", now locate to the Image and after successfully locating and selecting it click on Let's Go on the right cornor.
4.2. If your image is patched successfully your log in front of you will look something like this:
- Device platform: armeabi-v7a
- Installing: 23.0 (23000)
- Copying image to cache
- Boot image is signed with AVB 1.0
- Unpacking boot image
- Checking ramdisk status
- Stock boot image detected
- Patching ramdisk
- Repacking boot image
- Signing boot image with verity keys
****************************
Output file is written to
/storage/emulated/0/Download/magisk_patched-buildno_abcde.img
****************************
- All done!
Click to expand...
Click to collapse
4.3. You have your patched boot image!!
5. Now get the patched image back to your pc -.-
6. Prepare yourself to focus, Im not responsible for your bricked device!
7. Goto This XDA Post for Tutorial and Information about SP Flash Tool, MTK Drivers ADB Drivers, etc etc.
8. Download and Install MTK Drivers(Link Credit: Bovirus' this post)
1. You'll find a exe, just execute it and it'll be installed automatically.
Click to expand...
Click to collapse
9. Download and open SP Flash Tool and select Scatter-loading file.
10. Now After you've selected the scatter loading file you'll find there are various selections in front of you, Preloader, lk, boot, recovery and etc etc
10.1. DESELECT or UNSELECT (OR WHATEVER YOU CALL IT) every selection other than boot.
10.2. In the row of boot/bootimg, (remember the patched boot image?) click on LOCATION you'll get a explorer window to locate to the patched boot image, locate and select it. In the last it should look something like this:
https://imgur.com/a/WMbTTAC
10.3. Click on Download in SP Flash Tool and connect the device, see next step.
11. Power Off the device and Remove the battery(See 3. in Issues I faced).
12. Now while pressing the Volume UP and Down Button together, connect the M-USB to your device port. I can't explain this but, firstly connect the USB cable to your pc then to your device haha.
13. You'll hear the device connected sound of Windows(If windows user) and the flashing will start
14. Reboot to OS and Voila! Check your Magisk Manager, your device is now rooted! Do remember to install the Magisk App just below the Magisk Root Check!
Now, issues I faced:
1. Device wasn't connecting to the SP Flash Tool, I reinstalled the MTK Drivers but it didn't do any change.
2. FastBoot flashing didn't work, I opted for SP Flash Tool later.
3. Device was starting into Factory mode and/or Recovery mode whenever I pressed Volume UP/Down and then connecting the device through USB, removable battery came to my rescue. Removed the battery, pressed both volume Up and Down button and then connected the USB.
NOTE: Again, all the images, links, tools, programs and everything belong to their respective owners!! Everything you are doing with the steps above are STIRCTLY your responsibility, if you do it wrong and brick your device you can't charge me for bricking your device, only you and you will be held responsible for any damage/success/etc to your device.
Links for boot.img and scatter file: Here is the MediaFire link, I've scanned the files with my Quick Heal Total Security I'm not those multidadoffspring who likes to spread virus/malware etc. and Here is the VirusTotal Link.
Feel free to tell me my errors and mark how can I improve, I appreciate it
And also, if you need any other file from the Stock ROM of the same device, do tell me here or DM at my insta: heartwastaken
Sorry for my bad English.
Thank you!!
Have a great Day
-Vish
the phone reboots into recovery (I install the wrong recovery, that's why the bootloop), it does not enter the fastboot and when you enter the recovery it just turns off on the boot screen. I can't get into the system either. The bootloader is unlocked. I tried the SP flash tool and it gave me an error brom. And mtk-client, as I understand it, was fixed on miui 14. because there is also an error there. help me please
Hi, did you manage to solve this problem?
What have you tried with mtk client?
hi, I still haven't solved the problem. In mtkclent, I tried to flash the "boot.img" file through brom mode
If the boot flash was successful but you still cant access fastboot or recovery try reflashing the stock rom using brom mode
Step1: Setting up the files
Download the stock rom for your device (I prefer miuirom website)
Extract the downloaded rom
Check if Mediatek USB VCOM Drivers and UsbDK are installed correctly.
Set up mtkclient (follow official guide)
TIP:
After some research i found out that you can speed up the mtk process by modifying the mtk_daxflash.py file. (Source)
Open the file using notepad and search for this line:
Python:
dsize = min(length, 0x200)
And replace it with this:
Python:
dsize = min(length, 0x2004)
Step2: Fix your device
Open the command prompt in the mtk folder
Run this command WITHOUT your device plugged in:
WARNING! This will erase all data on the device
py -3 mtk wl <extractedrompath>\images\
(py -3 or python depending on the installed python version)
plug in your phone and put it in brom mode. the procedure should start immediately
This will flash all the files inside the images folder in the correct partitions (may take a while)
In the procedure you may see some partitions error but thats normal
When the first command is done run this second command:
py -3 mtk w boot_a "<extractedrompath>images\boot.img"
And this command:
py -3 mtk w boot_b"<extractedrompath>images\boot.img"
This will write the boot image to the boot_a and boot_b partition.
Now if everything succeded you should be able to boot into miui.
If not you should be able at least to boot into fastboot, try following step3
Step3: Flash the rom in fastboot (If required)
In the extracted rom path you should see a .bat and a .sh named flash_all.
Put your phone in fastboot mode and run the bat (Windows) or the sh (macOS/Linux) file.
If everything succeded you should have your phone working again .
Hope that your device will work again!
Tria13 said:
the phone reboots into recovery (I install the wrong recovery, that's why the bootloop), it does not enter the fastboot and when you enter the recovery it just turns off on the boot screen. I can't get into the system either. The bootloader is unlocked. I tried the SP flash tool and it gave me an error brom. And mtk-client, as I understand it, was fixed on miui 14. because there is also an error there. help me please
Click to expand...
Click to collapse
Please PM me if you want your device to be flashed using authorised Xiaomi Server.
I have the same device and I bricked it a while ago by flashing twrp and booting to recovery
From my understanding edl flashing can only be done with an authorized xiaomi account. I don't have one so I had to pay someone on telegram who had one and who could unbrick it. He used a modified version of SP Flash Tool. Although he struggled a bit he got it fixed the next day after I downgraded to windows 10. If you want to avoid bricking this device I recommend you don't use twrp altogether or be very cautious and only use twrp builds from the official telegram group. Compatibility depends on the kernel and android version. For now aosp-based roms have issues with the gpu anyways. (always under 100% load)
Also there is a mtk bootprotect magisk module which might help. (I don't think it will if you flash wrong twrp tho)
I hope these informations are somewhat useful
WolfnHex said:
If the boot flash was successful but you still cant access fastboot or recovery try reflashing the stock rom using brom mode
Step1: Setting up the files
Download the stock rom for your device (I prefer miuirom website)
Extract the downloaded rom
Check if Mediatek USB VCOM Drivers and UsbDK are installed correctly.
Set up mtkclient (follow official guide)
TIP:
After some research i found out that you can speed up the mtk process by modifying the mtk_daxflash.py file. (Source)
Open the file using notepad and search for this line:
Python:
dsize = min(length, 0x200)
And replace it with this:
Python:
dsize = min(length, 0x2004)
Step2: Fix your device
Open the command prompt in the mtk folder
Run this command WITHOUT your device plugged in:
WARNING! This will erase all data on the device
py -3 mtk wl <extractedrompath>\images\
(py -3 or python depending on the installed python version)
plug in your phone and put it in brom mode. the procedure should start immediately
This will flash all the files inside the images folder in the correct partitions (may take a while)
In the procedure you may see some partitions error but thats normal
When the first command is done run this second command:
py -3 mtk w boot_a "<extractedrompath>images\boot.img"
And this command:
py -3 mtk w boot_b"<extractedrompath>images\boot.img"
This will write the boot image to the boot_a and boot_b partition.
Now if everything succeded you should be able to boot into miui.
If not you should be able at least to boot into fastboot, try following step3
Step3: Flash the rom in fastboot (If required)
In the extracted rom path you should see a .bat and a .sh named flash_all.
Put your phone in fastboot mode and run the bat (Windows) or the sh (macOS/Linux) file.
If everything succeded you should have your phone working again .
Hope that your device will work again!
Click to expand...
Click to collapse
hello, thanks for the answer, but I already tried this and I got an error with kamakiri. In the git mtk client, the person was told that it was fixed for 14 miui.
Tria13 said:
hello, thanks for the answer, but I already tried this and I got an error with kamakiri. In the git mtk client, the person was told that it was fixed for 14 miui.
Click to expand...
Click to collapse
The thing is ---- Auth bypass is not yet available for your chipset type MT6895.
We have to wait until we can bypass auth to flash using SP Flash tool.
Tria13 said:
hello, thanks for the answer, but I already tried this and I got an error with kamakiri. In the git mtk client, the person was told that it was fixed for 14 miui.
Click to expand...
Click to collapse
im sorry to hear this
mvikrant97 is right. MT6895 is currently unsupported. you just have to wait
mvikrant97 said:
Please PM me if you want your device to be flashed using authorised Xiaomi Server.
Click to expand...
Click to collapse
Hi, sorry I didn't see your post earlier. Can you solve your phone problem with an authorized Xiaomi Server? You can write your telegram or something else by which I can write to you. Thanks for the answer