Hi all,
I've been combing this forum to try and find the answer to my specific question, and I can't seem to find the answer.
I'm in the process of rooting/flashing a custom ROM to my KFHD7. I've gone through all the steps up until installing a ROM via TWRP. I've been following Seokhun's guide located here.
I downloaded Hashcode's CM 10.2 ROM here.
Once I booted into TWRP, I realized that somehow I had accidentally flashed /sdcard and I had no bootable ROM. Thus, I followed Seokhun's steps to sideload a ROM file:
6. Wiped /sdcard, can't reboot from recovery: You thought you had the ROM file on the sdcard, but you didn't, and wiped everything, so without a ROM image, you can't boot into system.
Solution: Put the ROM file where your ADB binary is (usually inside platform-tools folder in Android SDK directory) and rename it rom.zip. On the device, boot into TWRP, select Advanced, then ADB Sideload. Connect device to PC. From here, run "adb" and hit Enter to check for your binary version, if it's anything lower than 1.0.3.0, you need to update the binaries by re-installing the latest Android SDK. Once the device is in sideloading mode and is connected to the PC, type "adb sideload rom.zip" and hit Enter. Now you'll find the ROM on the sdcard, flash, and you're done.
Click to expand...
Click to collapse
I checked my ADB version:
{
"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 then moved Hashcode's CM 10.2 ROM from "downloads" to the folder where my ADB exe is located and renamed it "rom.zip" as the guide instructed:
Next, I boot into TWRP -> Advanced -> ADB Sideload via my fastboot cable
On that screen i see "Wipe Dalvik Cache" and "Wipe Cache" as check boxes along with "Swipe to Start Sideload" slider.
From there, i enter the command "adb sideload rom.zip" into the CMD prompt and it returns this:
UPDATED:
After thinking about it, I went in and changed the zipped folder name to "rom" realizing that the ".zip" should be understood as the file extension and not a part of the actual file name.
So, after changing the name, I went into TWRP -> Advanced -> ADB Sideload -> Swipe to begin sideload
I enter the command "adb sideload rom.zip" and it shows that Daemon starts successfully but then returns this error message:
and my KFHD7 does not download the ZIP file successfully.
So, after all of that, any ideas from the XDA community? Sorry this was so long. I'm new to the forums and wanted to make sure I was very specific to my individual problem. Thanks for the help in advance!
UPDATED:
I was able to find a solution here
I ran "adb usb" before running "adb sideload rom.zip" and it worked like a charm.
My KFHD7 is now successfully flashed with Hashcode's CM 10.2 mod!
I decided not to delete this thread in case anyone else had this very specific issue. However, if one of the mods feel it necessary to delete, then please do so.
for anyone else that comes along to this thread seeking salvation after a moment of forgetfulness and / or misguided recklessness, you can use Restore2Stock. took me a good while to find it but eventually stumbled across is and it solved everything, an exe that can fix everything as long as you can boot to TWRP:
http://n2aos.com/forum/restore2stock-r2s/890-kindle-fire-hd-7-wiped-operating-system.html
the above link is a brief explanation of how to use it. the download link is on the main page.
happy restoring
Related
Hi guys,
I'm a little stuck. I have a HTC One HBOOT 1.44 with TWRP 2.7.0.0 installed. I can flash recoveries (CWM or TWRP) but I cannot for the life of me sideload a ROM. I just did a factory reset so I can't exactly turn it back on. Any ideas?
guywithdesire1992 said:
Hi guys,
I'm a little stuck. I have a HTC One HBOOT 1.44 with TWRP 2.7.0.0 installed. I can flash recoveries (CWM or TWRP) but I cannot for the life of me sideload a ROM. I just did a factory reset so I can't exactly turn it back on. Any ideas?
Click to expand...
Click to collapse
save your rom in the same folder where you have adb and fastboot. Boot your phone in twrp recovery main menu. Open a cmd prompt from your fastboot folder.
type:
Code:
adb devices
it should output your phone s/n and ''recovery'' beside.
Code:
adb push <name_of_rom>.zip /sdcard/
wait for the file transfer, it might take up to 5-10 mins.
after the file transfer completed, Hit ''install'' and select the rom.zip.
alray said:
save your rom in the same folder where you have adb and fastboot. Boot your phone in twrp recovery main menu. Open a cmd prompt from your fastboot folder.
type:
Code:
adb devices
it should output your phone s/n and ''recovery'' beside.
Code:
adb push <name_of_rom>.zip /sdcard/
wait for the file transfer, it might take up to 5-10 mins.
after the file transfer completed, Hit ''install'' and select the rom.zip.
Click to expand...
Click to collapse
ROM is in directory and opened CMD prompt from fastboot folder. ROM is named 'rom' for simplicity. Sitting on the TWRP main screen and typing adb devices results in this. Can't see any devices attached.
E:\HDD Downloads\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-
131030\sdk\platform-tools>adb devices
List of devices attached
E:\HDD Downloads\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-
131030\sdk\platform-tools>
guywithdesire1992 said:
ROM is in directory and opened CMD prompt from fastboot folder. ROM is named 'rom' for simplicity. Sitting on the TWRP main screen and typing adb devices results in this. Can't see any devices attached.
E:\HDD Downloads\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-
131030\sdk\platform-tools>adb devices
List of devices attached
E:\HDD Downloads\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-
131030\sdk\platform-tools>
Click to expand...
Click to collapse
Your drivers a probably not installed correctly. Start by following these instruction from nkk71's guide (faq #2):
originally from @nkk71: [GUIDE] [02-MAR-2014] nkk71's SuperGUIDE to returning 100% back to stock
2) Q: I'm using Windows 7 what should I worry about
A: when you issue the command "fastboot boot CWM.img" (now only in CWM/TWRP restore method) there's a high chance drivers won't correctly install
{
"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"
}
follow the below instructions to fix
Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install that
just in case, HTC Drivers can be found here: [Drivers] HTC Drivers for Windows - Several Versions (credits to @mdmower)
though you should already have them since you have been using your phone anyways​
for those who like a visual guide:
okay so I did a fastboot boot command, and as you can see it didnt install correct driver
Open "Device Manager"
there's the culprit
right click and Update Driver Software
select Browse my computer for driver software
select Let me pick from a list of device drivers on my computer
select Android USB Devices
select My HTC ... (if you have more than one version, choose the latest)
warning, select Yes
successful installation
now it looks better
and can confirm:
Code:
C:\ADB3>[B]adb devices[/B]
List of devices attached
HTxxxxxxxxxx recovery
-------------------------------------------------------------------------------------------------------------------------------------------
Hi all. I've try to install today Android Revolution Google Edition 6.1.
So, my phone is S-OFF, i've install but after boot my phone all time restart. Not open, so, i don't have another rom in my SD card and now, i can't login my sd card for copy. So, i've try too many time from diffrent computer (windows 7 64bit, windows 8 64bit) from cmd and "adb" and i've receive all the time "device not found" error. So, i can flash recovery but "adb" is not work. I've install SDK and install everything but still not show. Any idea?
By the way so sorry for my bad English. Please help me.
soundeluxe said:
Hi all. I've try to install today Android Revolution Google Edition 6.1.
So, my phone is S-OFF, i've install but after boot my phone all time restart. Not open, so, i don't have another rom in my SD card and now, i can't login my sd card for copy. So, i've try too many time from diffrent computer (windows 7 64bit, windows 8 64bit) from cmd and "adb" and i've receive all the time "device not found" error. So, i can flash recovery but "adb" is not work. I've install SDK and install everything but still not show. Any idea?
By the way so sorry for my bad English. Please help me.
Click to expand...
Click to collapse
can you check my guide http://forum.xda-developers.com/showthread.php?t=2541082 under FAQ #2 if that's the problem with Windows Device Manager.
you can disregard the guide only check FAQ #2
nkk71 said:
can you check my guide http://forum.xda-developers.com/showthread.php?t=2541082 under FAQ #2 if that's the problem with Windows Device Manager.
you can disregard the guide only check FAQ #2
Click to expand...
Click to collapse
Thanks for you reply. Actually my drivers looks like ok. Please check 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"
}
"flash" command its ok, but adb still not work :S I've try too many time reinstall driver.
soundeluxe said:
Thanks for you reply. Actually my drivers looks like ok. Please check image;
"flash" command its ok, but adb still not work :S I've try too many time reinstall driver.
Click to expand...
Click to collapse
fastboot commands work in bootloader
adb commands work in custom recovery (eg TWRP) or booted up ROM (with USB debugging enabled)
so if you need adb then enter custom recovery, check your device manager again, because it changes depending on where you are (bootloader, TWRP ... even version matters, or ROM)
once in TWRP, and device manager is good, adb devices should return you serial number and "recovery" -> then you can use adb commands
24945626 720
nkk71 said:
fastboot commands work in bootloader
adb commands work in custom recovery (eg TWRP) or booted up ROM (with USB debugging enabled)
so if you need adb then enter custom recovery, check your device manager again, because it changes depending on where you are (bootloader, TWRP ... even version matters, or ROM)
once in TWRP, and device manager is good, adb devices should return you serial number and "recovery" -> then you can use adb commands
Click to expand...
Click to collapse
Finally. Thank you very much for your help dear @nkk71, i've lost the adb command just work on custom recovery
I've install driver and now everythings its ok, i'm try adb sideload rom.zip
NOTE: This post was firstly added to the Xperia Z2 Forum and I decided to post it here as well thinking it might help someone else.
https://forum.xda-developers.com/xperia-z2/general/magisk-stock-xperia-z2-d6503-safety-net-t3700786
Firstly, I do not take any responsability in case anything happens to your device or your files. You decided to follow this guide at your own risk.
THIS WORKED FOR ME FOR MAGISK v14.3
ALSO WORKS ON MAGISK v14.5
I highly not recommend to use this guide for a different device other than the Xperia Z2 D6503.
All that aside, I managed to install magisk on my Stock Xperia Z2 and still keep ctsProfile and basicIntegrity: true.
HIGHLY RECOMMEND TO BACK EVERYTHING UP BEFORE PROCEEDING
You will need:
(OPTIONAL)Marshmallow FTF Firmware Here
(OPTIONAL)Flashtool Here
Magisk Manager Here
Rootkernel_v4.31_Windows_Linux.zip Here
ADB and Fastboot Here
Advanced Stock Kernel Here
TWRP Sirius Here
(OPTIONAL BUT HIGHLY RECOMMENDED) Use flashtool to flash the modified version of the stock ROM from above. It worked on this version but I can't really guarantee it will work on others. Can't really guarantee it will work on this either.(after you select the file there are 2 versions. pick the modified one).
1) Extract the Rootkernel_v4.31_Windows_Linux.zip and extract from the advanced stock kernel the boot.img (Rename it from boot.img to Old_boot.img)
2) Open cmd and use cd to reach the folder in which you extracted rootkernel.
Use the command "rootkernel Old_boot.img New_boot.img"
Say Yes to everything except installing TWRP.
3) Install Magisk Manager on your phone and copy "New_boot.img" to the phone.
4) Go to Magisk Manager settings , scroll to Update Channel and select Beta
5) Select install Magisk and select modify boot image. Select "New_boot.img" from the folder you copied it to
6) Extract adb to a folder
7) After patching the boot image at step 6, copy "patched_boot.img" from internal storage/MagiskManager to the folder in which you extracted adb
8) Copy TWRP to the adb folder and rename it to TWRP.img
9) Open cmd and use cd to navigate to the folder in which you copied adb. Type in the console "fastboot flash boot New_boot.img". Turn off your phone and then hold Volume Up whil plugging it into your pc(booting it into fastboot).
10) While still in fastboot, type "fastboot flash recovery TWRP.img"
11) Disconnect your phone from the pc. Wait a few seconds and then boot into TWRP (hold power button and Volume Down). A notification will pop up and select to "Keep System Readonly" (I think something like that). Reboot into system.
If everything worked as intended, a safetynet check will reveal everything in green, allowing you to both have root access and also run apps like Netflix and Android Pay
NOTE: Magisk Modules should be flashed via TWRP. For some reason, Magisk Manager is unable to install them.
EDIT: I tried to install xposed systemlessly but Safetynet was triggered. Don't think I can figure this out.
This worked for me but I can't guarantee it will work for you. (Photos at the end)
Did this guide help you? If you need any help, I will do my best to answer your questions.
I am not a developer and I do not really understand why or how everything works. I came across this method that worked for me and I thought I'd share it since I couldn't find a guide for my xperia phone when I needed it.
IN CASE SAFETY NET IS TRIGGERED, the only way to restore to everything in green is to reflash the stock rom (you don't have to format everything).
Did it work out for you? Just leave a reply saying that so I can figure out if everything works.
{
"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"
}
.
hi
Does it work for Magisk18?
I am trying to flash 11.0.0 (RD2A.211001.002, Oct 2021) factory image in windows using the flash-all bat file. I updated my fastboot drivers in windows update and downloaded the latest platforms tools from google's website. I get this error while running the bat file.
FAILED (remote: Failed to write to partition Not Found)
finished. total time: 3.254s
Press any key to exit...
Any idea as to why?
Do you have your platform-tools folder in your PATH Variables?
kingofnice said:
Do you have your platform-tools folder in your PATH Variables?
Click to expand...
Click to collapse
I'm sorry what are the PATH Variables? Are you talking about the directory of my platform tools folder and my factory image?
On Windows 10, type in the search bar "system environment variables" and open that settings menu.
{
"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"
}
Click on Environment Variables...
Edit
Add the location to your folder. Press Ok and Apply if you need.
Now try your adb and fastboot commands from a new command prompt window. They should be working from any directory you are using command prompt in.
I think that is why your flash failed, though I don't know. It sounds like it couldn't connect because it couldn't utilize fastboot to find a device/partition.
Test "fastboot devices" and if you see your device try flashing again. Also, "fastboot -w update image-xxx-xxx.zip" is in the flash-all bat. remove "-w" to stop it from wiping data. That's your call as you might need a fresh install.
Klimon5 said:
I'm sorry what are the PATH Variables? Are you talking about the directory of my platform tools folder and my factory image?
Click to expand...
Click to collapse
Did that help at all?
kingofnice said:
Did that help at all?
Click to expand...
Click to collapse
I ended up using Windows 10 to adb sideload the most recent android 11 OTA zip from google. I performed a factory data reset in recovery after I booted into the update first. I then was able to unlock the bootloader, re-enable the oem unlocking setting in dev options, & install the official lineage os recovery and rom for barbet. I will try your steps and see if I can flash a factory image. When I had my nexus 6p, I removed the -w prefix and immediately rebooted into recovery to factory data reset. It then booted just fine. For me I think that my platforms tools for Ubuntu are out of date.
I ran this command on my ubuntu machine.
$ adb version
Android Debug Bridge version 1.0.39
Version 1:8.1.0+r23-5ubuntu2
The lineage os installation instructions warns about issues with out of date platform tools.
Install LineageOS on barbet | LineageOS Wiki
wiki.lineageos.org
"Note: Outdated fastboot releases dropped legacy A/B support, so it might attempt to flash to boot__a / boot__b rather than boot_a / boot_b if you try to flash boot. In this case, you must update fastboot to a release newer than or equal to 31.0.2. Alternatively, you can manually specify which slot to flash to based on what slot fastboot failed to flash to. For example, if fastboot fails to flash to boot__a, you must flash to boot_a.
I want to try this on linux manjaro on my laptop. The platform tools built in are the latest version from google. I'll have to do some experimenting to see what works.
Klimon5 said:
For me I think that my platforms tools for Ubuntu are out of date.
The platform tools built in are the latest version from google. I'll have to do some experimenting to see what works.
Click to expand...
Click to collapse
This is the problem. Using outdated Platform Tools causes problems. Latest release is 31.0.3, Aug '21. Many other users have run into similar problems because they were using outdated Platform Tools.
Requirements:
Your device's bootloader must be unlocked.
Prerequisites:
Ubuntu/Debian/Ubuntu-Based Distros:
Open terminal
Type sudo apt install adb
Once that is installed.
Type sudo apt install fastboot.
Done.
Fedora:
Open terminal.
Type sudo dnf install android-tools.
Let it install and done.
OpenSUSE:
Download this official package from here according to your version :
https://software.opensuse.org/download.html?project=hardware&package=android-tools
(Use either one the add repository and install manually or grab binary packages directly options.)
Click to expand...
Click to collapse
MIUI 12 (Weekly And Stable)
{
"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 to the sourceforge link of the rom and see the date of your rom. In this case it's alioth.
See the date of your rom . Now go to xiaomiformwareupdater.com and select your device. Then click download.
New page will appear. Type fastboot in the searchbar of the page. Now see global rom the date closest to the release of the xiaomi.eu rom and download.
Unzip the rom file to the root of home directory and connect your device to fastboot mode and open a terminal in the rom folder and run the command:
./flash_all.sh
A terminal window will popup and close after 15-20 min approx when flashing is done.This will delete your data.
Let the device boot into MIUI.
Once it boots power it off . Then press the vol down + power button until fastboot in orange letters appear.
TWRP method:
Flash twrp using fastboot.
Boot into twrp.
Go to wipe and format data.
Then factory reset in wipe.
Do not wipe anything in advanced wipe !
Copy the zip file to a fat32 formatted sdcard or usb.
Connect sdcard or usb to device.
Go to install , select storage , sd/usb, select rom zip and flash.
Once flashing done , wipe dalvik.
Reboot to recovery.
Reboot to system.
Done.
Fastboot:
Unzip rom file to root of home directory.
Go into folder.
Run fastboot installation script in folder
Open terminal window in the folder
If updating from older rom.
Run command in terminal:
./linux_fastboot_update_rom.sh
Done.
If installing first time.
Run command in terminal:
./linux__first_install_with_data_format_.sh
NOTE(For Stable And Recovery ROMs):
CHECK THE XIAOMI.EU THREAD FOR KNOWING IF YOUR ROM IS FASTBOOT OR RECOVERY.
Alternatively If you want you can flash india , eea , turkey , etc variants of stock rom instead of global , then flash xiaomi.eu according to the instructions above. But keep in mind that the release date of stock rom that you are flashing should be closest to the release date of xiaomi.eu weekly rom.
Install magisk after first boot and reboot after installing magisk to get rid of system lags.