First time flashing a ROM using adb/fastboot (help) - General Questions and Answers

So I'm trying to flash a ROM that will grant me root access and the person who made the ROM doesn't explain how to flash it.
I've heard of ADB and Fastboot before but I have no idea where to even start. This is the contents of the .zip:
{
"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"
}
This is the original thread: http://www.needrom.com/download/infocus-m512
Thanks

I tried searching for a guide on how to flash a ROM with adb/fastboot but I'm not even sure if im searching for the right things

Anyone?

Before you flash a custom ROM, make sure you have a custom recovery installed. This is the part where ASB/FastBoot comes in.
The custom recovery may be CWM or TWRP, or anything at all which supports your device, look on the website of the recovery you want to use if they support your device or seach the XDA forums for one.
After downloading the recovery image, you can optionally rename it to recovery.img.
You can use the zip file you curently have, but I'll advice to use the adb installer which I've included as attachment.
Once you have ADB installed with the installer you can omen op a command promt (cmd.exe).
Make sure your device is turned on and USB debugging is enabled!
After ADB sees your device (with the command: adb devices), boot into fastboot using adb reboot bootloader.
After your phone has rebooted into the bootloader(fastboot), use the command: fastboot flash recovery (path/filename to recovery).img
Following these steps should allow you to install a custom ROM through the recovery you justs installed. if you also want to include superSU(if it's not included into the ROM you're using), flash the SuperSU2.02 falshable zip from chainfire.
But before you do anything of this, make sure you've got a compatible recovery and ROM!

Khatarian said:
Before you flash a custom ROM, make sure you have a custom recovery installed. This is the part where ASB/FastBoot comes in.
The custom recovery may be CWM or TWRP, or anything at all which supports your device, look on the website of the recovery you want to use if they support your device or seach the XDA forums for one.
After downloading the recovery image, you can optionally rename it to recovery.img.
You can use the zip file you curently have, but I'll advice to use the adb installer which I've included as attachment.
Once you have ADB installed with the installer you can omen op a command promt (cmd.exe).
Make sure your device is turned on and USB debugging is enabled!
After ADB sees your device (with the command: adb devices), boot into fastboot using adb reboot bootloader.
After your phone has rebooted into the bootloader(fastboot), use the command: fastboot flash recovery (path/filename to recovery).img
Following these steps should allow you to install a custom ROM through the recovery you justs installed. if you also want to include superSU(if it's not included into the ROM you're using), flash the SuperSU2.02 falshable zip from chainfire.
But before you do anything of this, make sure you've got a compatible recovery and ROM!
Click to expand...
Click to collapse
Thanks for your help, I got it working. Much appreciated

Related

Nexus can't get into recovery. Doesn't boot.

I flashed the 4.1.1 OTA and after that I installed the Chainfire3D driver. After the reboot the phone didnt boot anymore. I pulled the battery and tried to boot into recovery but I couldn't.
The phone show this when I try to boot into recovery.
{
"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"
}
Then I tried to flash the recovery again via fastboot. Thing is
Code:
fastboot devices
doesn't list the phone as being connected. I tried 4 different usb ports on my machine.
Also, my phone is listed as unknown device in the device manager although the USB drivers are installed.
Is it dead?
No your phone isn't dead. If it still has root installed, you can download ROM manager from the play store and flash CWM from there. However it won't stick and you will have to flash it again after every reboot. But I think there is a fix somewhere. Just search the forums.
Sent from my Nexus S using xda premium
If not even get goo manager beta from market and install twrp recovery and then u should be good to go
Sent from my PG86100 using xda premium
steven.truong said:
No your phone isn't dead. If it still has root installed, you can download ROM manager from the play store and flash CWM from there. However it won't stick and you will have to flash it again after every reboot. But I think there is a fix somewhere. Just search the forums.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
You just have to rename the recovery script in /system/etc, reboot into fastboot and flash CWM and it'll stick.
Smh. The op said the phone WONT BOOT! He can't go to the market....
Op your phone is fine. That picture you posted is the stock recovery. Which is useless for you at the moment.
Boot the phone into the bootloader. Use fastboot on a computer to do one of these things. Flash or boot a custom recovery/do a full wipe and flash a full ROM with it. If you want to return to stock ics flash the factory images with fastboot.
Accepted solution
kkk this is my problem. sorry my english is very bad. next link is read and your problem solution.
http://forum.xda-developers.com/showthread.php?t=1572307
Next is my step. Very good.
On Windows:
1) copy the ecxtracted files (two times with 7zip) on android-sdk/platform-tools/ (this is important, if you dont unzip it, dont complain about "radio couldnt be loaded")
2) run a cmd and moves in "platform-tools" folder
3) write those command:
4A) If you are coming from a custom rom, this wipe your data/cache:
adb reboot bootloader
fastboot flash bootloader bootloader-crespo-********.img
fastboot reboot-bootloader
fastboot flash radio radio-crespo-********.img
fastboot reboot-bootloader
fastboot -w update image-********.zip
I install my nexus s i9023 and android JB 4.1.1 then Chainfire3d installed. But not reboot again. I re-flash ICS and update JB. Chainfire is not running JB.
1) You first re-flash your ICS rom
2) Install CWM 6.0.1
3) Updade ICS to JB 4.1.1
3) Re-install CWM 6.0.1
4) Simple root install.
5) Not install again Chainfire3D. kkk it is not compatible JB.

[MOD][addon.d] ADB and Fastboot Host for Android

These mods install adb and fastboot binaries for ARM processors. This enables you to use an Android device as the host machine rather than a PC or laptop to run adb and fastboot commands on a connected device. Some devices like the Nexus 7 and Nexus 5 come with adb, but not fastboot. You can check for these binaries in /system/bin/. I have made separate zips in case your device already has adb. These mods also includes addon.d scripts.
{
"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"
}
What is addon.d?
On some ROMs, like Cyanogenmod, there are scripts in /system/addon.d that run during a ROM update or flash. They can backup and restore system apps (like Gapps), or perform many other functions. This mod includes an addon.d script, so the mod is not lost during a ROM update! If your ROM doesn't support addon.d, this mod should still flash properly, but you won't benefit from addon.d.
Tested and Confirmed to work on:
Nexus 5
Nexus 7
It should work on many devices. Let us know if it works!
Note:
You will need OTG support to get any benefit from this, so your device can act as host when another device is attached. Be sure to use the su command before adb or fastboot.
Install Instructions:
- Boot into recovery
- Flash Install zip
- Reboot
Downloads:
Install-ADB-1.0.zip
Install-Fastboot-1.0.zip
Changelog:
Code:
1.0 - 02/13/14
- Initial release
Credits and Thanks:
chamatht - fastboot binary
DISCLAIMER:
This mod involves editing system files. Use at your own risk! Also please don't forget, before you report ROM related bugs in the ROM developer thread, you should remove this mod to make sure the issue is not caused by this mod!
Recovery missing
Can you help me because my recovery mode is missing. It happend when i tried to flash clockwork recovery mode that isn't meant for my phone. Mine is a Karbonn A108. If I could only install fastboot then I could Flash my phone. When i try to get in fastboot it says fastboot is missing.. please help I'm in a crisis. :crying:
Is this safe to use in Lineage 17.1?
Is it installable using exposed framework?
Does it solve this problem:
I have a TV box Scishion V99 Hero. It's rescue Adb mode presumes a USB connection. I cannot find how to set tcpip access in rescue mode. Yet the box has only female USB ports. The big flat connector. So I can't connect it to a PC but only to my phone.
I want to use my phone as an Adb host when installing ROM into the Scishion box.

[ROOT] Install Magisk on ZC551KL Guide "FINALLY"

This is a messy post, do as you please with it. I am not responisble for ang damage to your device. Additionally, I dont take any credits for any of this, I just put everything together here.
Tags zc551kl Asus Zenfone 3 Laser z01bdc
Tools Needed:
Asus Bootloacker Unlock Tool - http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZC551KL/UnlockTool_Android_M_0706_signed1.apk
You current boot.img version which can be downloaded from here [Its packaged in the update file]- https://www.asus.com/us/Phone/ZenFone-3-Laser-ZC551KL/HelpDesk_BIOS/
ADB and Fastboot from here [Credits to Snoop05] - https://www.dropbox.com/s/mcxw0yy3jvydupd/adb-setup-1.4.3.exe?dl=0
Magisk Manager - https://tiny.cc/latestmanager
Prep:
Install the Asus Unlocker on your phone and unlock it.
Install Magisk Manager on your phone but dont run it yet.
Enable USB Degugging on your phone.
Install ABD and Fastboot on your PC. It will be installed to c:/adb/
Download the update that matches your phone version to your pc. [Mine was version "WW-32.40.106.41"]
Open the update file on your pc with your favorite zip manager and extract the boot.img .
Put the boot.img onto your phones internal storage.
Follow this guide [Credits to Dhananjay @ thecustomandroid.com]
» Non-rooted devices
Magisk 14.0 introduces a new and neat method to install on non-rooted Android devices. This new process doesn’t require your device to be rooted, nor does it require a custom recovery like TWRP. But for this method to work, your device must have the stock boot.
But for this method to work, your device must have the stock boot.img dump placed in the internal storage.
Make sure that you enable USB debugging and setup ADB access first, you will need it later in the guide.
Download Magisk Manager 5.3.0: Link
When the APK has been downloaded, use a file manager to install it. Now run the app from the app drawer.
Go to the app settings and tap on “Patched Boot Output Format”. You can select “.img.tar” if you will be using ODIN to flash the file or else simply select “.img” for the rest of the devices.
{
"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"
}
Go back to the app main screen and tap on the “Install” button. Go to INSTALL > PATCH BOOT IMAGE FILE.
Navigate through the storage and select the stock boot.img file. As soon as you select the stock boot.img file, the app will download the installer to patch the image.
Once the process is complete, you can tap on the “CLOSE” button.
Your new and patched boot image now include root and support for modules. So the last step is to grab this boot file and flash it your device via fastboot or ODIN (Depending on the output format you chose in step #4).
Connect your device to the PC via USB cable and navigate to the Magisk Manager folder inside the storage. Your “patched_boot.img” file will be present right there. So copy it to your PC.
Move the “patched_boot.img” file to C:/adb folder. And type in the following command to boot your phone into bootloader/fastboot mode:
adb reboot bootloader
Once your phone enters the bootloader/fastboot mode, enter the command to flash the file:
fastboot flash boot patched_boot.img
Finally, reboot your device:
fastboot reboot
That’s all, you have just installed one of the most trending mod out there and especially on your non-rooted device without any need of a custom recovery. Isn’t it great? Tinker around with the app and see what all things you could do.
I can confirm this is working! Thank you!
Reporting working on Android O (8.0), I download update from Asus and patch boot image. Thanks
kamo84 said:
Reporting working on Android O (8.0), I download update from Asus and patch boot image. Thanks
Click to expand...
Click to collapse
I know it's been some time since this was discussed, but I am trying to go through this process. Can you confirm that you unlocked the bootloader on 8.0 with the Asus tool? Or did you install magisk without unlocking the bootloader (if that's possible)?
thanks
I don't think the unlocker tool works anymore.

[TOOL][PIXEL 3 XL] TOOL ALL IN ONE (Drivers|Unlock|TWRP|Factory Image|Stock Recovery)

This is the Pixel 3 XL's TOOL ALL IN ONE Discussion Thread more info and download go to the Original Thread
TOOL ALL IN ONE
{
"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"
}
ADVANCED OPTIONS
FUNCTIONS
Install Drivers
Install Drivers
Unlock Bootloader
Lock Bootloader (use carefully)
Flash TWRP Recovery
Flash Stock Recovery
Flash Stock Factory Image
Automatic ROOT
Install APKs
Uninstall APKs
Take a Screenshot
Take a Screen Reocrd
Flash Partitions
Erase All Data (This function can decrypt the phone)
Reboot Phone
Update the Tool to latest version
Update Adb and Fastboot to latest version
Set Adb and Fastboot priviliges in system wide
Install Zip directly from PC (Required TWRP on phone)(These functions work perfectly on my pc but i have perfect adb drivers on my pc and perfect TWRP on my phone)
Flash Fastboot ROM
Delete downloaded files
ADB File Manager
DEVICE LIST
If you want you can send a request to add a new device here:
New Device Request Form
Device List
DOWNLOAD
Original Thread
DONATE LINK
If you want to support the project please consider making a donation, thanks.
​
mauronofrio said:
This is the Pixel 3 XL's TOOL ALL IN ONE Discussion Thread more info and download go to the Original Thread
TOOL ALL IN ONE
ADVANCED OPTIONS
FUNCTIONS
Install Drivers
Unlock Bootloader
Lock Bootloader (use carefully)
Flash TWRP Recovery
Flash Stock Recovery
Flash Stock Factory Image
Install APKs
Uninstall APKs
Take a Screenshot
Flash Partitions
Erase All Data (This function can decrypt the phone)
Reboot Phone
Update the Tool to latest version
Update Adb and Fastboot to latest version
Set Adb and Fastboot priviliges in system wide
Install Zip directly from PC (Required TWRP on phone)(These functions work perfectly on my pc but i have perfect adb drivers on my pc and perfect TWRP on my phone)
Flash Fastboot ROM
Delete downloaded files
ADB File Manager
DEVICE LIST
If you want you can send a request to add a new device here:
New Device Request Form
Device List
DOWNLOAD
Original Thread
DONATE LINK
If you want to support the project please consider making a donation, thanks.
​
Click to expand...
Click to collapse
Great job!
Sent from my [device_name] using XDA-Developers Legacy app

Bootloop Ulefone armor 6

Hello everyone, I have a big problem with my device, it happens that the system started to fail and after that it turned off, when I turned on it stayed in a bootloop and I can only access the fastboot, the question is that my device does not have the OEM and I never did any modifications so it doesn't have recovery either.
So far I have tried to install for fastboot the boot.img and system.img from the original firmware but I get the error "remote: not allowed in locked state" because the bootloader is locked
Any recommendation?
Reflash original Stock ROM by means of ADB Sideload method
jwoegerbauer said:
Reflash original Stock ROM by means of ADB Sideload method
Click to expand...
Click to collapse
but I can't use recovery and it doesn't have TWRP installed either.
The truth is that I am quite new to this subject but it would help me a lot if you guide me through that process.
In addition, the stock rom offered by ulefone is in .tar.gz format
Both Stock Recovery and TWRP aren't needed to perform an ADB Sideload: both mentioned recoveries internally simply make use of this method.
Code:
adb devices
adb reboot sideload
adb sideload <STOCK-ROM-ZIP-FILE>
You at any time can convert a tar.gz archive to a zip archive. GIYF ...
jwoegerbauer said:
Both Stock Recovery and TWRP aren't needed to perform an ADB Sideload: both mentioned recoveries internally simply make use of this method.
Code:
adb devices
adb reboot sideload
adb sideload <STOCK-ROM-ZIP-FILE>
You at any time can convert a tar.gz archive to a zip archive. GIYF ...
Click to expand...
Click to collapse
How about, I was trying to access with ADB, however when I put adb devices, the device does not appear, perhaps because I did not have the USB debugging before the bootloop, I was trying with different commands and nothing happens, but it does appear in the device manager. I'm sure I have the correct drivers because I tried another device with USB debugging enabled and it works fine.
Attached 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"
}
It should be obvious to you that ADB can't work as expected if USB debug option isn't got enabled on Android.
how can the bootloop be solved if only fastboot is available?
And the manufacturer flashing tool doesn't recognize the phone?
I cannot reflash the phone.

Categories

Resources