Dear user, we hereby say that any damage or brick created by following this guide shall not give any fault on us. The requirements for this procedure are clarified and we take no responsibility for bad usage of this.
Click to expand...
Click to collapse
Dear XDA community,
Straight from the efforts of user @LastStandingDroid, here's a way to flash a zip file or some other operation in TWRP if you cant access some part of the touch screen due to it being broken and not detecting touch, for example.
Requirements:
A toaster wich can run Windows, MacOS or Linux. (joking on toaster part)
ADB Drivers (if needed, you can find something here) - this link is only for windows users.
TWRP installed (follow this guide for installation)
Minimal command knowledge
We will use as example, a flash of a zip file to get root on a Umidigi Z Pro:
Open command prompt;
From here, change directory to ADB Directory (cd path/to/adb)
Now type "adb shell twrp install path/to/zip", being the part path/to/zip the actuall path to the zip file you want to flash;
At this point, you should get a screen where every step of the flashing process will be shown, just like when flashing through TWRP. And that's it.
{
"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"
}
Credits:
All of them goes to @LastStandingDroid and @gersp for his tutorial thread.
Now lets heat up things...
atarii said:
Atarii:
that handy to know
Click to expand...
Click to collapse
And I certainly agree with his statement (telegram) while there was almost no info about how to flash zip trough adb and the echo update command did seem to fail. Or maybe I did wrong I don't know. I find this great if the echo command fails
This made my root come back when something broke it
Sent from my GT-I9505 using Tapatalk
I have access to a super primitive recovery mode, in which twrp doesn't seems to boot.
When I use
# twrp anycommand
I get:
TWRP does not appear to be running. Waiting for TWRP to start . . .
Press CTRL + C to quit.
Is there a way to "start" twrp from adb shell ?
It's worked on my PH-1,thank u so much
Related
OpenRUU - RUU Shell Script For Linux (See the post below for mac support)
This is a shell script to flash an official RUU from HTC.
I tested this on my device and it ran fine, it uses exactly the same commands as the RUU app.
You do not need root.
The script will:
Get your current ROM version
Get Your Current HBOOT Version
Get Your Battery %
Reboot into RUU Mode
Flash the ROM using fastboot
Reboot your phone
Enjoy!
DOWNLOADS:
2.73.405.5 Generic WWE (The one you need to root with flashrec)
TO INSTALL:
GUI Method:
Extract the zip > right click on the script > properties > permissions tab > Select 'Enable execution as a program' > OK > Double Click > Run in terminal
Terminal method:
Code:
Extract the zip
cd /path/to/files
chmod 755 OpenRUU-Hero-WWE-2.73.405.5.sh
./OpenRUU-Hero-WWE-2.73.405.5.sh
If you want me to add a ROM then please PM me with the rom.zip, see here for how to extract a rom.zip from an RUU.
If you can, please donate so I can afford better hosting, I also have some cool features to implement when I get proper hosting too. (If you can host a rom.zip, please PM me.)
- GBP
- Euro
- Dollars
Post here with any bugs/comments so my turkeys can get to work!
{
"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"
}
Mac Support
For Mac:
Download this,
Delete 'adb' & 'fastboot' from the folder you extracted the files too,
Rename 'fastboot-mac' to 'fastboot',
Copy it to the script folder,
Run the Script.
If you get errors then please put in a codebox the terminal output.
That's a nice idea. Something the community has been lacking for a while too
Hope it goes well
Reserved #2 - ^^ DOH! This 30secs thing really annoys me
well i had no problem what so ever making fastboot work, sadly though there are certain times were one has to use ADB! anyway, i have htc sync installed, and i know that the computer recognizes my device because of 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"
}
so obviously there is a problem that i do not understand, because when i check in my sdk (fastboot) folder by typing "adb devices", the list of devices is empty!
please help i really need this!
ADB detects your device while it's inside the OS (running) or in recovery mode. Make sure to install latest version of HTC Sync.
tomascus said:
ADB detects your device while it's inside the OS (running) or in recovery mode. Make sure to install latest version of HTC Sync.
Click to expand...
Click to collapse
so it cant detect my device while it's in fastboot mode? so it's impossible to use ADB if your bootloader is relocked right? cuz i am trying to follow this guide: http://www.flow-wolf.net/2012/10/install-jelly-bean-on-htc-one-x-maximus.html
however i cant find a way to successfully install PJ46IMG.zip !
That guide is extremely outdated and I don't suggest you use it. To flash the firmware zip package use the fastboot command 'fastboot oem rebootRUU' and then type 'fastboot flash zip (name of zip here)'
Sent from my HTC One X using xda app-developers app
tomascus said:
That guide is extremely outdated and I don't suggest you use it. To flash the firmware zip package use the fastboot command 'fastboot oem rebootRUU' and then type 'fastboot flash zip (name of zip here)'
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
yeah when i did that before i also got an error, cant remember actual wording, but the good new is i gave up on OrDroid and Maximus, decided to try out Jeffix and it worked, i am guessing it was an issue related to Hboot, but happily all my issues have been resolved, thanks for the help though!
This is the Xiaomi Redmi 5 Plus'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.
I want to specify that this tool can't bypass Xiaomi Bootloader Unlock procedure but all others function are working
Make this tool to enable diag port open without root permissions... My phones imei id is lost
not unlock bootloader my device. is redmi5plus.
[question]
So you are saying that this tool isnt compatible with other phones? Is the Device list updated over the years or what?
Please give us the tutorial and link of downloaded files that needed to flash in this Phone, I'm having a hard time to understand How this thing work
Good day to yall!
I've been trying to download the Pixel Experience ROM on my phone for the past few hours and I keep getting this error.
I've already used the ./adb kill-server; ./adb start-server commands on PowerShell and my device says I've given all the necessary permissions to the computer I'm performing the ROM installation on. But I keep getting the same error over and over again.
Any help would be appreciated!!
{
"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"
}
Chambuligu said:
Good day to yall!
I've been trying to download the Pixel Experience ROM on my phone for the past few hours and I keep getting this error.
I've already used the ./adb kill-server; ./adb start-server commands on PowerShell and my device says I've given all the necessary permissions to the computer I'm performing the ROM installation on. But I keep getting the same error over and over again.
Any help would be appreciated!!
View attachment 5478869
Click to expand...
Click to collapse
Guide: https://telegra.ph/Flashing-PEPPUI-09-09
Have you unlocked your bootloader?
Compass.
Compass Linux said:
Guide: https://telegra.ph/Flashing-PEPPUI-09-09
Have you unlocked your bootloader?
Compass.
Click to expand...
Click to collapse
I have. Otherwise I wouldn't be able to make use of the "XiaoMiTool_V2", which is the tool I'm using to install the ROM on my phone.
And after I kept on trying, I noticed that my main problem is that when I get to the phase in which my phone enters recovery mode, it unistalls TWRP, or more specifically, it deletes the image. And after that it just reboots and the process fails. However, I was not able to figure out how to solve the problem... Still would appreciate any help. Thanks in advance.
Chambuligu said:
I have. Otherwise I wouldn't be able to make use of the "XiaoMiTool_V2", which is the tool I'm using to install the ROM on my phone.
And after I kept on trying, I noticed that my main problem is that when I get to the phase in which my phone enters recovery mode, it unistalls TWRP, or more specifically, it deletes the image. And after that it just reboots and the process fails. However, I was not able to figure out how to solve the problem... Still would appreciate any help. Thanks in advance.
Click to expand...
Click to collapse
If you've managed to install TWRP properly you cannot boot into MIUI. MIUI removes TWRP if allowed to boot.
Follow the guide: https://telegra.ph/Flashing-PEPPUI-09-09
This guide is the official one and has more details on the installation process: https://wiki.pixelexperience.org/devices/begonia/install/
Compass.
I sincerely thank you. I was able to install everything properly with the help of the guide you linked.
Cheers!
So the issue you had was you had to select "ADB Sideload" on TWRP to make the tool detect it
also MIUI automatically replaces your recovery every time you boot to system
I would like to know how to enter fastbootd! mode???
Enable the USB debug mode in the Developer options, install adb (it's the part of Android Studio, or as a separate tool for Linux available in the official repos) and execute "adb reboot bootloader".
This is FastBootd! mode ??
{
"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"
}
Yes it is. In this mode the phone responds only to the commands of the fastboot CLI tool.
uluruman said:
Yes it is. In this mode the phone responds only to the commands of the fastboot CLI tool.
Click to expand...
Click to collapse
so I can install GSI by the dynamic partitions
PaulinoBaslio said:
so I can install GSI by the dynamic partitions
Click to expand...
Click to collapse
Probably. May be. From my experience it simply doesn't work. It sorta flashes something but may be it just takes forever to complete or it's really just stuck but there's no response whatsoever. Fastboot mode is absolutely minimalistic, it does not report anything, no progress, nothing, and I guess it's intended to be like that, because it boots before anything else and theoretically allows you to flash even the very first bootloader. Anyway, I tried something like fastboot flash system lir-v316-220325-arm64-bvZ.img and the CLI tool reported Sending 'system' and then nothing else happened for the next 15 minutes or so, after which I just hit Ctrl+C, ran fastboot reboot and observed that nothing changed, the old system booted just like it was, so I guess nothing was really flashed, even partially. I don't know really, may be it's unpacked internally only when the image is fully uploaded and I didn't give it enough time, but for that time Odin would already flash the whole set of firmware. What else is to try, besides waiting more time, is converting the image to/from Android sparse format using the img2simg & simg2img tools, and try other partition names, such as "system_root" but I am sure this latter thing is absolutely wrong. The GSI system partition is called system, it just must be called that, system_root is something else (I guess it's the system root of the recovery mode).