Hi,
My phone is stuck in fastboot loop. I cant turn it off or restart to recovery. I've tried everything i could find on the web, but no result.
ADB is not recognizing the phone properly. The same as MiFlash. I've tried dozen of Miflash version and either they crash or have that message.
Pictures:
Miflash error
{
"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"
}
Fastboot and adb dont recognize the phone:
What are the other steps, what can i try? Is there a Miflash that works?
try this,
1) download platform tools folder
2) download fastboot rom 12.0.2 i.e .TGZ file
3) extract platform tools (u will find one folder inside named "platform tools"
4) extract TGZ file
5) copy all extracted tgz files in that "platform tools" folder.
6) connect device.
7) double click on "flash all.bat" file
8) done
rasik107 said:
try this,
1) download platform tools folder
2) download fastboot rom 12.0.2 i.e .TGZ file
3) extract platform tools (u will find one folder inside named "platform tools"
4) extract TGZ file
5) copy all extracted tgz files in that "platform tools" folder.
6) connect device.
7) double click on "flash all.bat" file
8) done
Click to expand...
Click to collapse
I've tried it, after clicking flash all, command prompt window flashes (too fast, i cant see the content of the window) and closes. Nothing changes...
Image of platform tools folder with fastboot rom inside:
1. Open command prompt.
2. Navigate to the directory which contains flashall.bat.
3. Now run flashall.bat from command prompt.
With this you can see the error.
Advise: Check your path and see if any folder has a space in the name. Remove the spaces from the folder names.
Related
when i try to make WORKING ROM folder of SWKTM.tar.md5 after changing it to .TAR using dsixda
i get this error
{
"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"
}
that means that your tar file doens't have the kernel in it (boot.img) you have to put the boot.img file inside of working folder also
Don't try to use the .tar.md5 file directly. Do this:
- Extract the .tar.md5 file to a folder, lets say "/home/yourname/Stock". You'll get these files:
Code:
amss arm11boot boot.img mibib oemsbl qcsbl recovery.img system.rfs
We'll need to mount the "system.rfs" one. Now, do the following:
- Under your home folder (/home/yourname/) create an folder and name it "mntandroid". Create another folder named "system";
- Open a terminal window, navigate to the folder where you extracted the .tar.md5 file and get root user rights (sudo su/your pass);
- Type the following commands:
Code:
mount -o loop system.rfs /home/yourname/mntandroid
(remember to change "yourname" to your username);
- A new window shold open, it is the "system.rfs" contents. Select everything and copy to the "system" folder you've previously created;
- On the file manager, unmount the "mntandroid" drive;
- Compress the "system" folder - not its contents - to a zip file. The name don't matter;
- copy this .zip file to the "original_update" folder;
- try again now, it should work;
You can make it even better if you download any kernel (like Battery Extender) and place it in the .zip you've compressed before. This way, your zip should look something like this:
Yes, without any "META-INF" dir. Leave it like this.
Also, don't use the kitchen install script, I've read somewhere that it doesn't works. Use the Stocklite or some other stock-based ROM script.
Tell me if it worked for you. At least, this is what I did
Oh, by the way, this thread is where I got the mount rfs thing. I've just simplified it for you.
Windows users should already have :
<<adb drivers>>
{
"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"
}
and
<<usb drivers>>
------------------------------------------------------------------------------------------------------------------------------------------------------
so u did root. u unlocked bootloader. u flashed a recovery and u installed a new rom. one day u start "digging" things to see if u can delete all the unwanted files so u make the phone faster and accidentally u deleted an important file and now it cant boot and it cant go into recovery. you are wondering what you CAN do now ! The answer is : Everything !
You can either go back to stock rom or
you can re-flash the recovery and then reinstall the rom.
1. Download the platform tools for your machine ( windows , linux or mac-os ). Here i have the adb fastboot for you.
2. Copy the recovery image to a location on your computer thats easier for you. The recovery image should have .img extension. If it is in a zip file, extract the .img file from it before proceeding.
3. Connect the phone to the pc and open cmd inside the fastboot folder you downloaded ( windows ). The others not on windows must use cd [path to their desktop,inside the platform tools where they see the adb file].
** If you are on a boot loop but the pc gets to recognize the phone even for a second then
4. Type
i) adb reboot-bootloader
ii) fastboot flash recovery recovery.img ( the command is: fastboot flash recovery [recovery image path/filename] )
5. When its done , reboot. Hold Volume down and power button to see if u get in recovery mode. :highfive:
Install the rom now the way you already know. There are many guides for that so i won't make a new.
cheers :good:
**Windows users can use this fastboot to unlock bootloader too. Lite fastboot commands guide provided here
**Linux users don't even need to download it , they can just directly download it from their terminal
I hope this thread helps a little those that dont know what to do when they delete an important file. *Pictures coming soon*
How to revert back to Kitkat from MIUI lollipop in easiest way
Requirements :
MIUI 7.1 KK Rom
MiFlash
Important :
Before flashing it is advised to take the backup of data and make sure that your phone battery is charged enough.
Steps :
1. Download ROM from the above link and extract it to Desktop.
Note: - Some users get error while extracting onDesktop Because there is space in the username of PC or the folder as shown.
{
"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"
}
The users should put the ROM In C Drive in a folder without spaces. E,g C:/ROM/MIUI
The Error shown when using space between foldername.
2. Download flashing tool from the above link and install it.
3. Once installation is complete, Run MiFlash application.
4. Click on browse
5. Select ROM folder from Desktop(From the location where ROM is saved)
Note: -The path of the ROM folder Should be like "C:\Users\zeus\Desktop\MIUI" Not "C:\Users\zeus\Desktop\MIUI\images"
The MIUI Rom folder should Contain the following files
6. Turn off the phone, press and hold the Volume Down key and the Power button at the same time to enter Fastboot mode, then connect the phone to a computer.
7. Press Refresh button to see you device in flashing tool.
After pressing refresh button you will see connected device.
Here You have 3 options to select.
Choose the options carefully as per your need:-
1. Flash_all:- Clears all the data of the built-in storage, clear all user data, please be careful!(Clean Install)
2. Flash_all_except_storaget:- Will erase all user data does not clear the built-in storage data.
3. Flash_all_except_data_storage:- Does not clear the built-in storage data does not clear user data
8. Click on Flash and it will start process
Device Mismatch error ? Don't worry, click below.
Steps :
1. Dowload Notepad++ from here. Go to folder where you have extracted the Rom
2 .Right Click on any of 3 Batch Files ( .bat extension) you want to choose and open it with Notepad++
3. Delete those 2 lines ( line no. 10 and 11 ) and then Save it using ctrl+s or file menu.
4. Done , now you can flash fastboot rom on your device using Mi flash tool without having that error
9. Once flashing process completes Device will automatically reboot. Reboot might take upto 5 minutes.
Done !
its working 100% thanks for ur guide
Prerequisites:
Bootloader unlocked (Unlock Guide, Video Tutorial)
Magisk Manager
ADB and Fastboot tools (Download, Setup Guide)
Steps:
For Rui 2.0
Goto TWRP (Download link and Install Guide) or any other custom recovery (ofox)
Rename Magisk-v25.2.apk to Magisk-v25.2.zip
Flash Magisk-v25.2.zip and reboot
For Rui 3.0
Get boot.img and vbmeta.img from export firmware (Download, Convert to SP tool guide)
Use magisk to patch the boot image:
{
"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"
}
Connect the device to the PC via USB Cable.
Now transfer the patched boot file(magisk_patched.img) and vbmeta.img from your device to the platform-tools folder on your PC.
Inside the same folder, right-click on an empty area while pressing the ‘Shift’ key.
Select the option ‘Open PowerShell window here.
Or you could also head over to the platform-tools folder on your PC, type in CMD in the address bar, and hit Enter. This will launch the Command Prompt.
Type in the below code to make sure the device is successfully connected (an alpha-numeric code suggests successful connection):
Code:
adb devices
Now type in the below code to boot your device to fastboot/bootloader mode:
Code:
adb reboot bootloader
Next, type the below code to flash the patched boot image file:
CSS:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot magisk_patched.img
fastboot reboot
Credits:
Thanks to @ManshuTyagi for TWRP and @topjohnwu for Magisk
PS: I have tested this on only RMX 3031, and it may work on GT neo(CN) (RMX 3357) without any edits. If it works for you, please let me know, will update the post accordingly.
and how to update RUI 3 afterwards without a full wipe?
good day, any guide on how to obtain the Boot.img and vbmeta.img file
Rooting the LG Stylo 2 (Verizon) VS835
credits to hovatek for mtksu, diplomatic for mtksu and suboot, & topjohnwu for Magisk
Needed...
1. Init.d Support Script apk
2. mtk-su_r23.zip
3. Magisk-v18.1.zip
4. MagiskManager-v7.1.1 apk
5. suboot.zip
6. magisk-update-block.txt
DISCLAIMER: I'm not at fault if you f&#$ your phone up.
I'm using a computer to do this procedure, if you want to rework this to be done without a PC be my guest. It is possible without a PC. I just seen people needed root for this device, I happen to own the device, and figured i'd be nice and give back to the same community that taught me android development for years...
STEP 1:
Connect to PC in file transfer (MTP) mode. and make a new folder on the device root directory called init.d
STEP 2:
Extract the suboot.zip file and locate suboot.sh you need to place this file inside init.d
Now you need to create another folder named bin (inside the first folder you made)
STEP 3:
Extract mtk-su_r23.zip and inside the arm folder is a file called mtk-su this file needs to go into the bin folder
Extract Magisk-v18.1.zip and inside the arm folder place ONLY magiskinit inside the same bin folder
if you did this correctly your files should look like this:
{
"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"
}
*note* you DO NOT need to put the magisk-update-block.txt inside the init.d folder. That's just where i placed it. You only need the URL for the next step.
STEP 4:
Now from the phone install MagiskManager-v7.1.1.apk DO NOT LET IT UPDATE
Open MagiskManager and goto settings > update channel > custom
and paste this URL from the magisk-update-block.txt or from below
https://raw.githubusercontent.com/topjohnwu/magisk_files/841e978604f989d04549013cd4dcc7e34aea5288/stable.json
Click to expand...
Click to collapse
Now you'll see that Magisk Manager thinks it is already up to date.
STEP 5:
Install the init.d scripts support apk provided.
* tick/checkmark on "Run scripts at boot time"
* Set Execution Delay to "No Delay"
* For Selected Folder set it the init.d folder you made, and then click save at the top right.
It will say 2 script files in this folder if done correctly
** NOW scroll down and click "Run scripts now"
It's free version so watch an ad... after 2 ads it will grant you pro access for 24 hours.
** Again click "Run scripts now"
You'll see "Show last execution results" appear below the "Run scripts now".
Your results should look like this.
Use root checker to confirm...
Thats it. Enjoy.