Hi there,
I noticed yesterday that there are still no download sources for fastboot binaries that actually work with tegra devices (at least I did not find any). I compiled fastboot for linux (see downloads). Also there seem to be a bunch of people having problems to get fastboot running. This thread will hopefully help them.
It is still WORK IN PROGRESS! If you have ideas/questions/etc. just post them.
1) Get adb working:
- Follow instructions on http://developer.android.com/sdk/installing.html
- create /etc/udev/rules.d/51-android.rules containing:
Code:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0955", MODE="0666"
2) Get the correct binary from the download section below.
3) Copy the binary to yout platform-tools folder /...PathToAndroidSdk.../platform-tools/ and do a "chmod +x /...PathToAndroidSdk.../platform-tools/fastboot"
4) Make sure /...PathToAndroidSdk.../platform-tools/ is in your $PATH
Get your Folio into fastboot mode:
1) Power on
2) On first boot screen press 3 times Power followed by VolumeUp
3) Connect USB
WARNING: NEVER PRESS 4 TIMES POWER FOLLOWED BY VOLUMEDOWN!!! THIS WILL BRICK YOUR DEVICE!!!
Now you are all set up. Here are the commands you will need:
Flashing syntax:
Code:
fastboot flash <partition> <image>
Code:
#fastboot flash linux boot.img
#fastboot flash system system.img
#fastboot flash system system.img -w (This will wipe data after flashing the image)
#fastboot flash recovery recovery.img
Booting an image (recovery.img or boot.img) to try before flashing:
Code:
fastboot boot <bootable_image>
Code:
#fastboot boot boot.img
#fastboot boot recovery.img
Also useful:
Code:
#fastboot reboot
#fastboot devices (lists ???????? if Folio is connected, outputs nothing if not)
#fastboot erase %PartitionToErase%
DOWNLOADS:
Fastboot for linux-x86 and 64
%reserved%
Moved to general as not development
Ok it sounds really easy... but what will do every step ??
Cleaned Folio100 dust
Thanks mblaster! I was around with a Folio100 trying to install Dexter_nlb FolioMod1.4
(http://forum.xda-developers.com/showthread.php?t=846199) but got stuck at the "Verification
Signature Failed" when trying to install the update.zip.
Your direct method ruled out all barriers! It is quite simple do be done from a unix command line.
Nevertheless, "booting an image (recovery.img or boot.img) to try before flashing" did not
work for me. Anyway I took the risk, flashed directly and it worked!
I am here in fastboot usb mode, and how can I locate a ROM filename? I don't know how to access my phone and its SD card with fastboot.
Many thanks,
Today i was finding the method to root My friend's Micromax Canvas 4 A210, i downloaded the many files and drivers for rooting but unable to do so, then i tried SP Tool too, but unable to flash recovery, the problem is with the drivers, Then i found that this device has fastboot mode, we just need a custom recovery for rooting any android phone then just install superuser or supersu via that custom recovery. then i boot this device is fastboot and flash the custom cwm recovery. so i just want to share this with all of you, because i didn't found this method anywhere.
Files Required:
1. Fastboot
2. CWM Recovery for canvas 4 (should be *.img format )
3. Superuser/Supersu zip
Google them and you will find them.
Steps:
1. Reboot the device in the fastboot mode.
2. Connect the device with PC
3. Copy the recovery.img in the fastboot folder.
4. The press SHIFT and right click in the folder and select open command prompt.
5. Now check whether PC is recognize the device or not by executing command :
Code:
Fastboot devices
6. Above command will show you the fastboot devices connected to the pc.
7. Now flash the recovery, by command:
Code:
Fastboot flash recovery Name_of_recovery.img
8. Now reboot the device in the recovery mode and install supersu.zip / superuser.zip via recovery.
below is the video i created, might be a little blurry.
https://www.youtube.com/LapoLdLSHN0
HELP
I think i flashed wrong twrp recovery on my micromax canvas 4 A210. Now the phone boots up but i cant access the storage, neither internal sd card nor external. The sim is also not getting detected. Please help.
I'M NOT RESPONSIBLE FOR PEOPLE NOT FOLLOWING INSTRUCTIONS OR HARD BRICKED PHONES.
To follow this guide you must at least be able to access TWRP or Download mode or Fastboot at least.
(This guide applies too if your phone boots but with the Secure Boot error 1003 <- this error doesnt let your phone charge powered off)
1. Download Unbrick.zip
2. Download LG root zvb method zip from HERE (thanks to AUTOPRIME & Team CODEFIRE)
2a. Extract unbrick zip and root zvb zip in the same location
2b. right click "open command prompt" inside the folder of extraction.
3. Have LG drivers installed (you can find them in the forums)
4. If you have access to download mode and no TWRP installed you must first nuke LAF
4a. use the command prompt window we opened on 2b. and nuke laf using dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
4b. type LEAVE (this will leave your G3 on fastboot)
5. On the same window we must flash TWRP. using fastboot flash recovery twrp.img
5a. then fastboot flash boot boot.img, fastboot flash aboot aboot.img, fastboot flash laf laf.img
5b. fastboot reboot should take you to twrp where you can flash any rom (I suggest FULMICS)
5c. If the rom you flash fails to boot or you keep getting secure boot error keep on with this guide.
6. Enter twrp and copy the boot, aboot and laf imgs to your internal storage
6a. open a cmd prompt and enter adb shell
6b. use dd command as follows:
dd if=/sdcard/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
dd if=/sdcard/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/boot
dd if=/sdcard/laf.img of=/dev/block/platform/msm_sdcc.1/by-name/laf
7. Reboot to recovery and flash any custom rom this should fix your Secure Boot error Sprint LG G3. :highfive:
Thanks to all devs who worked on root and roms for this amazing phone!
Thanks! I had a working phone but still got the boot error. I copied the unbrick.zip to my phone and used the terminal in TWRP to run the dd commands in step 6b and it fixed the error! Reinstalled a fresh fulmics and everything is working fine.
Hello Folks,
i just had the Problem that i flashed the wrong superSU wich resultet in a not bootable System.
In my case this was the Stock firmware 380 i flashed with trwp 3.0.2 and a Supersu 2.49 wich resultet in a Error 10 and 2 (No Boot.img / bootable system).
The Following helped me a lot and i think this will fix most destroyed Boot.img´s and Systems.
The Source was here on this German Page : http://www.android-hilfe.de/thema/honor-7-zerschossen-geloest.796550/
I thought ill translate here:
When the System will not find/has broken System or Boot.img do the following:
Get the Stock Rom or Update from ur current System (example B380 or any other wich u installed atm)
-> https://forum.xda-developers.com/honor-7/general/models-stock-firmware-packages-honor-7-t3448747
Get the Huawai Update Extractor:
-> https://forum.xda-developers.com/showthread.php?t=2433454
Then open ur downloaded Update.zip or Rom.zip and open the UPDATE.APP file with the Extractor and extract the following files:
-System.img
-Boot.img
-Recovery.img
Afterwards copy those into ur ADB files folder and open a CMD in that Window.
Connect ur H7 with ur PC and boot into the Fastboot (Vol- and Power)
Type the following into the CMD window previously opend:
1- fastboot devices (should list up ur H7)
2- fastboot flash boot boot.img (flashes the Honor7 boot.img to the H7)
3- fastboot flash system system.img (flashes the system wich maybe corrupted)
4- fastboot flash recovery recovery.img (flashes the stock recovery and removes trwp)
5- fastboot reboot
Your H7 should now reboot and boot in the system as u had it before.
TWRP will be removed and exchanged with stock recovery.
I hope i have spared some of u the time searching for help in the web.
All Credits to the devs and ppl wich provided the Info. This is just for translation.
Maze has finally published the Alpha Stock-Rom.
Download Link: https://goo.gl/9kCJiv :fingers-crossed:
The system.img file is incorrectly downloaded as a system 002.img file. It must be renamed. And then copy it to the folder "3. Maze_Alpha_V05_20170816 Official ROM".
Thanks!
Hope anyone can root this phone.
Hi!
I am in need of a new phone, and this one looks quite good at the price.. But what do you think can i expect from custom ROM scene here for it? I am a Xiaomi Fan, and my Mi4 was and is one of the best supported phones still. Do you think there will be a subforum for this device, custom ROMs (preferreable Lineage OS, or other close to AOSP ROMs? OFC nobody can know now, i understand, but what tells your experience of other new phones from new companys? It has created quite a buzz, so i think there will be a demand for sure..
Just am 2 afraid to get a phone without good custom ROM. Never had an Android in last 5 years with stock ROM. Total nightmare for me now to have to go back.
Root + TWRP 3.2.1
3 Methods to root MAZE Alpha
Note: Method II is the most universal and must works with almost any official ROM
I- Method 1 : flashing modified Magisk boot.img
1. make sure to have already installed the version 20170816
2. reboot the phone in fastboot mode (phone off -> Vol Up + Power or "adb reboot bootloader")
3. unlock the bootloader if not already done : fastboot flashing unlock (if not works, in android development setting set the unlock bootloader and then retry)
4. unzip and then flash the attached boot image : fastboot flash boot new-boot.img
5. reboot your phone: fastboot reboot
6. install the MagiskManager apk v14
7. Voila
I have used this Magisk guide to create it
I used old manual guide :
Code:
adb shell "rm -rf /data/local/tmp/*"
adb push META-INF/com/google/android/update-binary common magisk_inject boot.img /data/local/tmp
adb shell "cd /data/local/tmp/magisk_inject; mv ../common/* .; chmod 755 *; sh ../update-binary indep boot_patch.sh ../boot.img; mv ../bin/busybox busybox"
adb pull /data/local/tmp/magisk_inject/new-boot.img
adb shell "rm -rf /data/local/tmp/*"
II- Method 2 : using TWRP and Magisk.zip (External SDCARD or USB OTG cable needed)
1. reboot int bootloader mode : adb reboot bootloader
2. unzip and flash the the attached TWRP recovery : fastboot flash recovery recovery_maze_alpha_4G_twrp-321.img
3. In TWRP choose first "change language" then press the "cancel" button while asking you for decryption password for data
4. In your PC download the Magisk-v15.3.zip and put it in a USB key, or an SDCARD
5. Use an usb otg cable to connect the USB key to your phone running TWRP and install the Magisk-v14.zip from Usb-otg (or SDCARD)
6. bonus: do a complete backup of your phone : all partitions except cache and data to your Usb-otg (or SDCARD)
7. reboot and install the MagiskManager apk v14
III- Method 3 : using the phhusson modified boot image
1- flash the attached boot image, using fasboot (fastboot flash boot boot-super-bootimg-output-su-eng-r318.img) or SPFlashTools using the attached scatter, if you do not want to unlock your bootloader
2- reboot to Android then install from google play the phhsusson superuser
3- Voila
Important Notes:
1- In all case you can use SPFlashTools to flash boot image without unlocking bootloader.
2- windows SPFlashTools users : phone off, press VOL+ and connect it to your PC (running SPFlashTool and waiting for phone connetion)
3- linux SPFlashTools users : phone off and connected to PC , press VOL+ and POWER while your PC is running SPFlashTool (with sudo) and waiting for phone connetion.
Some useful tips
1- manual install of busybox :
a- root you phone with method II if not already done
b- stay in TWRP (or boot TWRP as in method II) then in advance->sideload slide the slider to confirm and after cancel that (we will not sideloading any thing, just to activate adb)
c- unzip and copy the attached busybox : adb push busybox /external_sd/
d- mount the system partition with the TWRP mount button
e- copy the busybox binary to /system/xbin : adb shell --> cp /external_sd/busybox /system/xbin/
f- make executable busybox and create links (the point at the end is a part of the command) : cd /system/xbin/; chmod 755 busybox; ./busybox --install -s .
g- umount the system partition in TWRP and reboot
2- manually install the OTA update.zip :
a- Google and download those 3 tools BlockImageUpdate, simg2img and img2simg.
b- In a terminal of your Linux PC do :
Code:
simg2img system.img system.raw.img # convert the sparse image to a normal raw (ext4) image
BlockImageUpdate system.raw.img system.transfer.list system.new.dat system.patch.dat # patch the newly created raw image
img2simg system.raw.img system.img # convert the patched raw image to a flashable sparse image
- system.img: you old system image (from 20170816 official rom)
- system.transfer.list, system.new.dat and system.patch.dat : inside the OTA update.zip
c- After that the original system.img will be patched and you will have an updated system.img.
d- Flash this patched system.img and also all .bin and .img files inside the update.zip (just replace old ones in the original 20170816 rom by those) and you will have the new official rom
3- Using supersu as root manager :
The last update at this time of supersu zip (2.82 SR5) works well, even it cannot update the su binary.
Credits to Magisk Devs, Phhusson and Jemmini
dreambo said:
Here how to root this phone.
1. make sure to have already installed the version 20170816
2. reboot the phone in fastboot mode (phone off -> Vol Up + Power or "adb reboot bootloader")
3. unlock the bootloader if not already done : fastboot flashing unlock (if not works, in android development setting set the unlock bootloader and then retry)
4. unzip and then flash the attached boot image : fastboot flash boot new-boot.img
5. reboot your phone: fastboot reboot
6. install the MagiskManager apk v13.6
7. Voila
I have used this Magisk guide to create it
Credits to Magisk Devs.
Click to expand...
Click to collapse
If I root my phone with this method, will I get further OTA Updates from Maze?
Following to see where this goes.
Cheers
CrashCrash123 said:
If I root my phone with this method, will I get further OTA Updates from Maze?
Click to expand...
Click to collapse
Yes.
You will only lost the root.
If the new update have the same kernel, the same methode with the same boot image can be used to root it again, othewise, we can follow the Magisk guide to create a new one.
I have tried this method. But it only works until the reboot. Then the root access is gone again.
SomeOneX said:
I have tried this method. But it only works until the reboot. Then the root access is gone again.
Click to expand...
Click to collapse
The root is permanent.
If you lost it, perhaps the first time we unlock the bootloader, the phone do a reset, and we lost the root (I suppose).
Just re-flash the new boot again, and it will be permanent : fastboot flash boot new-boot.img
Hi . I have locked the OEM lock but I can not install it through fastboot (remote: not allowed in lock state)
can we expect VOLTE on this device ?
and is there any chance of custom rom development for this device?
alfymon22 said:
can we expect VOLTE on this device ?
and is there any chance of custom rom development for this device?
Click to expand...
Click to collapse
It seems (take with a pinch of salt) that VoLTE is supported, but then most sites that announce that also make mistakes on other specs, so...)
As for custom ROMs, so far the square root of bugger all, but the consumer phones are just filtering in, so give it time.
dreambo said:
Here how to root this phone.
1. make sure to have already installed the version 20170816
2. reboot the phone in fastboot mode (phone off -> Vol Up + Power or "adb reboot bootloader")
3. unlock the bootloader if not already done : fastboot flashing unlock (if not works, in android development setting set the unlock bootloader and then retry)
4. unzip and then flash the attached boot image : fastboot flash boot new-boot.img
5. reboot your phone: fastboot reboot
6. install the MagiskManager apk v13.6
7. Voila
I have used this Magisk guide to create it
Credits to Magisk Devs.
Click to expand...
Click to collapse
it worked, but i have cts fail on safetynet check. how you fixed this?
PrimateaEu said:
it worked, but i have cts fail on safetynet check. how you fixed this?
Click to expand...
Click to collapse
install the universal safety net fix
Hey guys, does this root method wipe the data partition?
KilljoyTDA said:
Hey guys, does this root method wipe the data partition?
Click to expand...
Click to collapse
The flash of the boot image does not wipe the data, but unlocking the bootloader reset the phone and wipe the data.
If you phone is already unlocked, you will not loss the data, otherwise do a backup before.
Well, I don't remember unlocking it, unless Kingo's windows app does it without telling even when rooting fails, so I guess I'd better back up.
Thanks for the info
KilljoyTDA said:
Well, I don't remember unlocking it, unless Kingo's windows app does it without telling even when rooting fails, so I guess I'd better back up.
Thanks for the info
Click to expand...
Click to collapse
It is easy to know if your phone is locked or not : enter fastboot mode and then do : "fastboot getvar all".
Read the last lines of the output and you will know.
Thank you @dreambo for this method, but for me "fastboot flashing unlock" not work, "fastboot oem unlock" working for me, all ok
ps:excusez moi pour mon anglais
dreambo said:
It is easy to know if your phone is locked or not : enter fastboot mode and then do : "fastboot getvar all".
Read the last lines of the output and you will know.
Click to expand...
Click to collapse
Well I failed to back up for some reason anyways, so since I had almost nothing vital on the internal memory, I rooted (sucessfully) and now I'm reinstalling/reconfiguring my apps. Thanks anyways