Hello everyone, today I present my new creation: we are talking about a tool that allows you to do many things , from the bootloader to flash the factory image , comfortably. Now you're probably asking: but there are already other tools available , why use it? I 'll explain it: this tool currently supports 13 devices of different companies and all the controls have been tailored to each device .
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
Unlock Bootloader
Lock Bootloader
Flash TWRP Recovery
Flash Stock Recovery
Flash Stock Factory Image
Reboot Phone
Update the Tool to last version
Delete downloaded files
DEVICE LIST
Oneplus 3T (Stock firmware not found for now)
Oneplus 3
Oneplus Two
Oneplus One
Oneplus X (Stock Firmware not found for now)
ZUK Z2 PRO (Stock firmware and recoveries not found for now)
ZUK Z2 (Stock firmware and recoveries not found for now)
ZUK Z1
Nexus 4
Nexus 5
Nexus 5X
Nexus 6
Nexus 6P
NOTE
I could not test all the controls, because they are really a lot, I did some tests and everything seems to work. I added a button "Delete File " in the case when downloading some files you have problems, you can delete the corrupted files directly from the tool instead of going to look for it manually.
Before using the tool, make sure that you have turned the oem unlocking, usb debugging and you reboot your device in Fastboot-Bootloader mode.
If you flash a Factory Image, all your data will be erased.
Use "Lock" only when you're certain that the Stock ROM functions properly.
If you have any problems during installation then first try to update the Microsoft Net freamwork to latest version:
https://www.microsoft.com/it-it/download/details.aspx?id=30653
HOW TO INSTALL
Download .zip file;
Extract all its contents into a folder;
Click on setup.exe;
Click on "Install";
Waiting for the end of the process;
Enjoy your tool
UPDATE
There will be no need to re-download the new tool, but just look for new updates directly from the tool.
In all cases I'll update the link in this thread and report it when there are new updates with its changelog. (If you have some problem during the update, press continue)
CHANGELOG
#1.0.0.7
Added official OPT recovery;
Added official ZZ1 recovery;
Solved some bug.
#1.0.0.9
Solved OPT bug on stock firmware;
#1.0.1.2
Add some download links
#1.0.1.3
Add new rom;
Solved some bugfix.
#1.0.1.5
Add OnePlus 3 support;
#1.0.1.6
Add new download links;
Add some new stock roms;
Add restore stock boot logo for ZUK Z1 ( you find it on "Flash stock fimrware").
#1.0.1.9
Add new "Advanced Options", i add a screen with all possible fuctions above;
I have changed some protocol (TWRP and Stock Recovery);
Add Oneplus 3 stock recovery.
#1.0.2.0
Add new "Generic" option to advanced settings (if you want to install a custom recovery or some else on an unsupported device you can try);
I have changed some protocol (Factory image and drivers);
Add Oneplus 3 Stock Faactory Image ( i have not tested it, if you test it please make me a fedback).
#1.0.2.1
Added official OnePlus 3 TWRp recovery;
Added last OnePlus One Factory Image;
Generic Bufix.
#1.0.2.2
Added Zuk z2 and zuk z2 pro.
#1.0.2.3
Added Zuk z2 and zuk z2 pro TWRP recovery;
Added new universal drivers;
General Bugfix.
#1.0.2.4
Added new Fastboot and Adb app (If zuk users have some problem try to unistall the tool and install the last through download link);
New UI;
General Bugfix.
#1.0.2.5
Added OnePlus 3T support;
Added OnePlus 3T TWRP;
General Bugfix.
#1.0.2.6
Added last ZUK Drivers;
Fixed Nexus Factory Image;
Fixed OnePlus Factory Image;
Fixed ZUK Z1 Factory Image;
Added newest Nexus Factory Image;
Added last OnePlus One Factory Image;
Added OnePlus 3 TWRP 3.0.2-1.28 recovery;
Added OnePlus 3T TWRP 3.0.2-0 recovery;
Added OnePlus 3T stock recovery;
General BugFix.
CONTACTS
If you think it necessary to add new features or other recovery or other Factory Image or you want to add a new device support please comments or send me a private message or send me an email to [email protected] (If you want to add support for additional device, please send me the link to download important files (recovery,factory image, ... ) or links to guides on the device(unlock bootloader) or anything that may serve me).
DOWNLOAD
TOOL ALL IN ONE
( Alternative Link )
DONATE LINK
If you want to support the project please consider making a donation, thanks.
DONATORS
- Alberto Petten�: 2.00 �
- Oliver E. : 3.50 �
- Tunde Alabi: 10.00 $
- Giovanni MacCelli: 5.00 �
- Cristian Godnik: 5.00 �
- Luca Milkovitsch: 5.00 �
- Nicol� Rossini: 2.00 �
- Luigi Pedrini: 1.00 �
- Oscar Davi: 5.00 �
- Claudio Orititi: 2.50 �
- James Goldsbury: 3.00 $
- Abel Varela Carou: 2.00 �
- Juan Carlos Cuevas Barreira: 5.00 �
- scooterofficina: 1.00 �
- Paul Moore: 3.00 GPB
- Mattia Colle: 1.00 �
- Maryan Komar: 2.00 �
- Luigi Ardizzone: 1.00 �
- Maximo76: 10.00 �
- Lo�c Payol: 13.37 �
- Antonio Rateni: 2.00 �
- Matteo Verzella: 0.50 �
- Lukas Heddendorp: 2.00 �
- Scott Dare: 5.00 �
- Leonardo F. : 3.00 �
- Andrea Tassotti: 5.00 �
- Stefano Franceschini: 1.00 �
- ??????? ???????: 1.00 �
- Stian Domben Bardsen: 20.00 �
- Kevin Dang: 2.00 $
- David Lebrun: 5.00 �
- James Hise: 15.00 �
- Daniele Barbana: 0.40 �
- Christophe Van B. : 2.50 �
- Robert M�ller: 10.00 �
- Johannes Fleischmann: 5.00 �
- Marco Rigoni: 10.00 �
- Pasquale Rivieccio: 2.00 �
- Jorge Toledo: 5.00 �
- ionel firuti: 10.00 �
- Argel Thulin: 2.00 �
- Tim Altmann: 1.00 �
- Christoph Hackl: 2.00 �
- Joel Vazquez: 10.00 $
- Tommaso Tautonico: 1.00 �
- Fabio Vannoni: 4.50 �
- Willy Andresen: 10.00 $
- Antonino Muscarella: 1.00 �
- ??????? ??????: 1.00 ?
- Pietro Brasile: 2.00 �
- Giorgio Frasca: 5.00 �
- Andrea Della Verde: 1.00 �
- RAFAL SZALKA: 2.00 GPB
- marco da silva: 2.00 �
- Jose Rodriguez Martinez Z: 1.00 �
- Francesco Rizzo: 1.00 �
- Lorenzo Stronati: 2.50 �
- Brian Salerno: 15.00 $
- Alois Seelwische: 4.50 �
- K & J Cooper Proper: 5.00 �
- Janis Jemeljanovs: 5.00 �
Really thanks to donators
is it having one plus three stock recovery?
rahulnegi1409 said:
is it having one plus three stock recovery?
Click to expand...
Click to collapse
No for now
Seems good. Let me try this after I buy Oneplus 3
And we're back. Zuk Z1, OnePlus 2 and now for the OnePlus 3. Thank you for your support
Planet X said:
And we're back. Zuk Z1, OnePlus 2 and now for the OnePlus 3. Thank you for your support
Click to expand...
Click to collapse
No problem :good:
rahulnegi1409 said:
is it having one plus three stock recovery?
Click to expand...
Click to collapse
If you have oneplus 3, you can extract stock recovery. do you want to help me?
mauronofrio said:
If you have oneplus 3, you can extract stock recovery. do you want to help me?
Click to expand...
Click to collapse
If I was not Having one why would I ask for it ??
Please help me I just need stock recovery
http://forum.xda-developers.com/oneplus-3/help/extract-stock-recovery-t3398950
I also made a post :|
my A3000 chinese version would arrived next wednesday. If someone provide a guide . Maybe i could help extract stock recovey or something from stock hydrogenos
Much appreciation!
thanhnvt194 said:
my A3000 chinese version would arrived next wednesday. If someone provide a guide . Maybe i could help extract stock recovey or something from stock hydrogenos
Click to expand...
Click to collapse
if you want i can prepare a zip and a guide to get stock recovery
Thanks, this wok flawlessly. My first time rooting on PC and the toolkit made it easy and fast.
mauronofrio said:
If you have oneplus 3, you can extract stock recovery. do you want to help me?
Click to expand...
Click to collapse
How do I extract the stock recovery from Linux? (Edit: I mean: with Linux - I've got no Windows box here)
UnnamedFile said:
How do I extract the stock recovery from Linux? (Edit: I mean: with Linux - I've got no Windows box here)
Click to expand...
Click to collapse
When you have unlocked your bootloader you can may be boot the twrp recovery by fastboot boot twrp_recovery.img and make a backup?
Planet X said:
When you have unlocked your bootloader you can may be boot the twrp recovery by fastboot boot twrp_recovery.img and make a backup?
Click to expand...
Click to collapse
Sorry, this doesn't work - after sending the command to the phone like this:
Code:
# fastboot boot twrp-recovery.img
downloading 'boot.img'...
OKAY [ 0.664s]
booting...
OKAY [ 0.368s]
finished. total time: 1.032s
It's just stuck at the fastboot screen. Also, I get a message of a failed MTP mount on my PC, and fastboot devices shows nothing. The phone only reacts to long-pressing the power button and reboots.
Good evening TWRP backup made with any file you want to stock recovery?
UnnamedFile said:
Sorry, this doesn't work - after sending the command to the phone like this:
Code:
# fastboot boot twrp-recovery.img
downloading 'boot.img'...
OKAY [ 0.664s]
booting...
OKAY [ 0.368s]
finished. total time: 1.032s
It's just stuck at the fastboot screen. Also, I get a message of a failed MTP mount on my PC, and fastboot devices shows nothing. The phone only reacts to long-pressing the power button and reboots.
Click to expand...
Click to collapse
there are another way, via adb, do you want to try?
mauronofrio said:
there are another way, via adb, do you want to try?
Click to expand...
Click to collapse
If you tell me how, I'll try.
UnnamedFile said:
If you tell me how, I'll try.
Click to expand...
Click to collapse
OK, enable debug usb and oem unlocking on your op3, then connect your phone (the phone must be switched on, not in fastboot-mode) to pc, you open a terminal on the adb-fastboot folder (if you are using linux open a normal terminal), write "adb shell" on windows or "sudo su" in linux and then write "cat proc/mtd" e launch de command. Please report what you see on terminal, then i can give you the right command to extract the recovery
mauronofrio said:
OK, enable debug usb and oem unlocking on your op3, then connect your phone (the phone must be switched on, not in fastboot-mode) to pc, you open a terminal on the adb-fastboot folder (if you are using linux open a normal terminal), write "adb shell" on windows or "sudo su" in linux and then write "cat proc/mtd" e launch de command. Please report what you see on terminal, then i can give you the right command to extract the recovery
Click to expand...
Click to collapse
So you say, I should tell you what the file /proc/mtd on my local PC contains? Somehow I don't understand how this would make sense (besides the fact that I have no such file in my /proc). So I guess that this command should be executed on the phone. However, when I set it up like you described (with USB debugging and OEM unlocking activated, and the phone fully booted up), 'adb devices' shows me nothing, just "List of devices attached" and then no device.
I am by no means a newbie on Linux or computers in general, but not a programmer either. This makes me wonder: Shouldn't the command 'cat /proc/mtd' be executed on the phone itself? I don't know much about adb, but shouldn't "adb shell" do the trick in that case? However, only if adb recognizes my phone, which mine doesn't (despite usb debugging and oem unlocking activated). I'd still like to help, but I'm stuck here, don't know what else to do. Does the phone need to have an unlocked bootloader for simple adb functionality? Because I did relock mine after the last try...
The phone itself mounts a second MTP device called OnePlus Drivers, which contains a file 'adb_config_linux_OSX.sh' with the following content:
Code:
#!/bin/sh
# adb configuration script
PATH=$PATH:/bin:/sbin:/usr/sbin
ANDROID_HOME=~/.android
ANDROID_CONFIG=~/.android/adb_usb.ini
CUST_VID="0x2a70"
if [ -e $ANDROID_HOME ] ; then
echo "android home is exist!"
else
echo "creat android home!"
mkdir $ANDROID_HOME
fi
grep $CUST_VID $ANDROID_CONFIG 2>/dev/null
if [ $? -eq 0 ] ; then
echo VID $CUST_VID is already configured..
echo "adb should be OK!"
exit 0
else
echo config adb ...
echo $CUST_VID >> $ANDROID_CONFIG
fi
adb kill-server
if [ $? -eq 0 ] ; then
echo "OK! You can use adb now!"
exit 0
else
echo "try sudo exec adb.."
sudo adb kill-server
if [ $? -eq 0 ] ; then
echo "OK! You can use adb now!"
exit 0
else
echo "Please do command \"adb kill-server\""
fi
fi
exit 0
I executed it, but that changed nothing.
UnnamedFile said:
So you say, I should tell you what the file /proc/mtd on my local PC contains? Somehow I don't understand how this would make sense (besides the fact that I have no such file in my /proc). So I guess that this command should be executed on the phone. However, when I set it up like you described (with USB debugging and OEM unlocking activated, and the phone fully booted up), 'adb devices' shows me nothing, just "List of devices attached" and then no device.
I am by no means a newbie on Linux or computers in general, but not a programmer either. This makes me wonder: Shouldn't the command 'cat /proc/mtd' be executed on the phone itself? I don't know much about adb, but shouldn't "adb shell" do the trick in that case? However, only if adb recognizes my phone, which mine doesn't (despite usb debugging and oem unlocking activated). I'd still like to help, but I'm stuck here, don't know what else to do. Does the phone need to have an unlocked bootloader for simple adb functionality? Because I did relock mine after the last try...
The phone itself mounts a second MTP device called OnePlus Drivers, which contains a file 'adb_config_linux_OSX.sh' with the following content:
Code:
#!/bin/sh
# adb configuration script
PATH=$PATH:/bin:/sbin:/usr/sbin
ANDROID_HOME=~/.android
ANDROID_CONFIG=~/.android/adb_usb.ini
CUST_VID="0x2a70"
if [ -e $ANDROID_HOME ] ; then
echo "android home is exist!"
else
echo "creat android home!"
mkdir $ANDROID_HOME
fi
grep $CUST_VID $ANDROID_CONFIG 2>/dev/null
if [ $? -eq 0 ] ; then
echo VID $CUST_VID is already configured..
echo "adb should be OK!"
exit 0
else
echo config adb ...
echo $CUST_VID >> $ANDROID_CONFIG
fi
adb kill-server
if [ $? -eq 0 ] ; then
echo "OK! You can use adb now!"
exit 0
else
echo "try sudo exec adb.."
sudo adb kill-server
if [ $? -eq 0 ] ; then
echo "OK! You can use adb now!"
exit 0
else
echo "Please do command \"adb kill-server\""
fi
fi
exit 0
I executed it, but that changed nothing.
Click to expand...
Click to collapse
Where can we talk? You have telegram? or Hanoguts? i explain you better
Related
New universal method of rooted for the Optimus 2x
After much programming and experimenting with another great part, already I can deliver my latest work.
So far have only made for Linux and Mac. (there are methods to not be as done in CMD)
Apparently it seems very simple, but it cheats, it is quite complex, since I've programmed detection of errors and possible solutions to the problems of communication.
The program is smart, detects the operating system that we are using, Linux or iOS, and detects the version of ROM installed to determine installation done.
Also installs the CWM Recovery, and also knows which install depending on the GB ROM or ICS, all automatic, without having to think that option used.
Before you root it will ask you if the CWM Recovery is installed and if it is not you can do it at that time.
The method used is not new, I already used it in earlier versions of GB, the difference with the other methods is that you don't have to copy anything to the SD and things of these, simple and clean installation.
Well I hope that you have Linux or a Mac can root without having to boot the "tedious" Windows.
CHANGELOG
V-0.5
-Implemented detecting permissions
-Implemented detection system 32/64b
-Fixed bug, was not working in Ubuntu 11.04 and higher
V-0.4
-Detection of new possible connection failures.
-Detection of errors in routines Android
-Optimized routines
V-0.3
-Fixed bug of execution, did not work on some current versions of Ubuntu and derivatives
-New start menu.
-New header
V-0.2
-Re-raise with correction error in English language, it only pulled in Spanish
-Includes English language
-Changing the graphic appearance
V-0.1
-Only in Spanish
Click to expand...
Click to collapse
DOWNLOAD
Toolkit_ICS-Root_Stock-v-0.5_LINUX-MAC_by_Homero.rar - 13.40 MB
Thank's Man...and have a nice year 2013!!!...
Nice, it should became sticked.
Also... your program must be also noob-proof
Great work, homero! Thank you.
Sent from my LG-P990 using xda app-developers app
Homero again back with a bang...you're hulk of lg optimus forum..you rock bro
Finally some Linux love.... :thumbup:
Sent from my LG-P990 using xda app-developers app
Thanks homero
Enviado desde mi O2X
I have committed an error, and the English version, and does not run.
You can download the new corrected version or edit and modify.
Edit the root file and look for this line:
Code:
if [ "$ANSWER" = 1 ]; then
tools/es.sh
elif [ "$ANSWER" = 2 ]; then
tools/es.sh
elif [ "$ANSWER" = "x" ] || [ "$ANSWER" = "X" ]; then
Changing this:
Code:
elif [ "$ANSWER" = 2 ]; then
tools/es.sh
why another:
Code:
elif [ "$ANSWER" = 2 ]; then
tools/en.sh
Save and ready, already operates the English version
Homero2 said:
I have committed an error, and the English version, and does not run.
You can download the new corrected version or edit and modify.
Edit the root file and look for this line:
Code:
if [ "$ANSWER" = 1 ]; then
tools/es.sh
elif [ "$ANSWER" = 2 ]; then
tools/es.sh
elif [ "$ANSWER" = "x" ] || [ "$ANSWER" = "X" ]; then
Changing this:
Code:
elif [ "$ANSWER" = 2 ]; then
tools/es.sh
why another:
Code:
elif [ "$ANSWER" = 2 ]; then
tools/en.sh
Save and ready, already operates the English version
Click to expand...
Click to collapse
Beware of #!/bin/sh ... read -n command is bash command, and it does not work well in /bin/sh ...
Confirmed on NetRunner (kubuntu 12.10 ).
You should use #!/bin/bash. That applies to all *.sh scripts.
asmerito said:
Beware of #!/bin/sh ... read -n command is bash command, and it does not work well in /bin/sh ...
Confirmed on NetRunner (kubuntu 12.10 ).
You should use #!/bin/bash. That applies to all *.sh scripts.
Click to expand...
Click to collapse
OK, that is the answer that was waiting, since neither worked in Ubuntu 12.04
EDIT:
Re-raise corrected v-0.3
Though your tool says that flashing the recovery worked successful, I can't boot into recovery. When pushing vol- and power I'm just stuck at the pink LG logo (it's in a boot loop while holding vol- and power). Since the system is not rooted, yet, I also cannot boot into recovery with the CWM app.
thorstenhirsch said:
Though your tool says that flashing the recovery worked successful, I can't boot into recovery. When pushing vol- and power I'm just stuck at the pink LG logo (it's in a boot loop while holding vol- and power). Since the system is not rooted, yet, I also cannot boot into recovery with the CWM app.
Click to expand...
Click to collapse
Don't worry in excess, can be retrieved very easily, but before answer to these questions.
Android version?
did CWM previously installed?.
Terminal type? (P990, P990, etc.)
on slackware 14.0, expanded in /opt:
two patches applied;
files are executables with right permissions;
dir 'tools' is accessible;
lg2x is connected via USB (on, off, MTP, PC Suite, without battery and vol -, ...?)
but same result
Terminal: P990 (EU)
ROM: ICS stock
Previous ver: CM 7.2 stable
Previous CWM: 5.0.2
Homero2 said:
Android version?
did CWM previously installed?.
Terminal type? (P990, P990, etc.)
Click to expand...
Click to collapse
Android 4.0.4 (official V30A)
CWM - well, under GB layout I could install it (I was on CWM5 first and later switched to CWM6), but this was my first try on ICS layout
Terminal type - you mean the shell? I'm using Ubuntu 12.10, so /bin/sh did not work and I replaced all /bin/sh with /bin/bash, that means I was running bash when I "bricked" my phone.
kanzy said:
on slackware 14.0, expanded in /opt:
two patches applied;
files are executables with right permissions;
dir 'tools' is accessible;
lg2x is connected via USB (on, off, MTP, PC Suite, without battery and vol -, ...?)
but same result
Terminal: P990 (EU)
ROM: ICS stock
Previous ver: CM 7.2 stable
Previous CWM: 5.0.2
Click to expand...
Click to collapse
Is about understands that this method of single rooted is for Stock ROM versions.
Clarified the issue, I see errors jump to run ADB.
Try with the latest version that I uploaded, the V-0.4
thorstenhirsch said:
Android 4.0.4 (official V30A)
CWM - well, under GB layout I could install it (I was on CWM5 first and later switched to CWM6), but this was my first try on ICS layout
Terminal type - you mean the shell? I'm using Ubuntu 12.10, so /bin/sh did not work and I replaced all /bin/sh with /bin/bash, that means I was running bash when I "bricked" my phone.
Click to expand...
Click to collapse
Not be what could happen...
Doing tests I found that if you are in Recovery, and the SYSTEM partition is not mounted, the program cannot determine partition type should be used.
That error is already fixed in the V-0.4.
It can reflash the Recovery with one of the many versions that we have in the Forum, one in Flash only recovery or All in one.
I say this because it is the only thing that could have happened, since the rooted is not harmful, only copy two files in the system.
Using V-0.4, and it does not work...
Homero2 said:
Is about understands that this method of single rooted is for Stock ROM versions.
Clarified the issue, I see errors jump to run ADB.
Try with the latest version that I uploaded, the V-0.4
Not be what could happen...
Doing tests I found that if you are in Recovery, and the SYSTEM partition is not mounted, the program cannot determine partition type should be used.
That error is already fixed in the V-0.4.
It can reflash the Recovery with one of the many versions that we have in the Forum, one in Flash only recovery or All in one.
I say this because it is the only thing that could have happened, since the rooted is not harmful, only copy two files in the system.
Click to expand...
Click to collapse
Same problem as on slackware, got booloop after flashing recovery. Cannot enter recovery
After this step:
INSTRUCTIONS
CWM will be installed for version ICS V-4.0.4 of Android
Nvflash started
rcm version 0X20001_____________________________________________________________
System Information:
chip name: unknownh Recovery CWM
chip id: 0x20 major: 1 minor: 4
chip sku: 0xf
chip uid: 0x045070c04120b4d7
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 17
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: tools/fastboot.bin
/ 1027184/1027184 bytes sent
tools/fastboot.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
sending file: tools/recovery_cwm-6_ics_opti.img
\ 7145472/7145472 bytes sent
tools/recovery_cwm-6_ics_opti.img sent successfully
everything went wrong, and my stock ICS got bootloop.
Using Kubuntu 12.10, stock ICS and V-0.4 of your tool.
Thank you mate! Gonna share it like a bee
asmerito said:
Same problem as on slackware, got booloop after flashing recovery. Cannot enter recovery
...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=921169
Fixed bug, now works in Ubuntu 11.04, 11.10, 12.04 and 12.10
An error has been detected by Jonki, Thank you!!
Homero2 said:
Fixed bug, now works in Ubuntu 11.04, 11.10, 12.04 and 12.10
An error has been detected by Jonki, Thank you!!
Click to expand...
Click to collapse
What was the problem?
Please help me guys
I have HTC one sprint mobile *unlocked
*S-On
*Hboot version-1.55.0000
*Twrp custom recovery installed
1.Can I able to install a custom ROM?? With this hboot version?? Suggest me any ROM please
2.can able to S-off it?? If possible please tell me how to do it through fastboot mode???
I stuck up in htc logo while updating stock ROM... then I unlocked the boot loader and custom recovery and installed....
Can't do anything please help me friends....
Thank you
gm_vel said:
Please help me guys
I have HTC one sprint mobile *unlocked
*S-On
*Hboot version-1.55.0000
*Twrp custom recovery installed
1.Can I able to install a custom ROM?? With this hboot version?? Suggest me any ROM please
2.can able to S-off it?? If possible please tell me how to do it through fastboot mode???
I stuck up in htc logo while updating stock ROM... then I unlocked the boot loader and custom recovery and installed....
Can't do anything please help me friends....
Thank you
Click to expand...
Click to collapse
1) Yes, hboot does not interfere with custom roms. I suggest you android revolution 51
2) Yes you can, google for Rumrunner
Can I do RumRunner through fast boot ??
Uxepro said:
1) Yes, hboot does not interfere with custom roms. I suggest you android revolution 51
2) Yes you can, google for Rumrunner
Click to expand...
Click to collapse
gm_vel said:
Can I do RumRunner through fast boot ??
Click to expand...
Click to collapse
1- ARHD 51.0 is NOT COMPATIBLE WITH SPRINT, use ARHD 31.6 which is compatible.
2- no rumrunner is either in booted up ROM (rooted + unsecured kernel + USB debugging etc), or you can take a look at http://firewater-soff.com/
Can I use firewater with windows 7 PC...
is it done it without booting up device?
gm_vel said:
Can I use firewater with windows 7 PC...
is it done it without booting up device?
Click to expand...
Click to collapse
Win7 should be fine for both firewater and rumrunner, but you need a booted up ROM (with USB debugging enabled)
[ROM] Android Revolution HD 51.0 | High Quality & Performance | Android 4.4.2 KitKat | HTC Sense 5.5 | 4.19.401.8 | Sense 5 Toolbox 2.7.1 | Sprint Support | T-Mobile Wi-Fi Calling
It is compatibile with sprint
So can I use any one of those Roms???
Do I install it by custom recover or some other methods???
gm_vel said:
So can I use any one of those Roms???
Do I install it by custom recover or some other methods???
Click to expand...
Click to collapse
Would you like my (personal) opinion?
can you give me your phone's model please: what shows up when you reboot to bootloader
M7_xxx -> as in M7_U or M7_UL or M7_WLS etc...
Tampered
Unlocked
M7 _WLS PVT SHIP S-ON RH
Radio 1.00.20.1100
gm_vel said:
Tampered
Unlocked
M7 _WLS PVT SHIP S-ON RH
Radio 1.00.20.1100
Click to expand...
Click to collapse
M7_WLS = Sprint, indeed
Here's a list of M7 variants: http://forum.xda-developers.com/showthread.php?t=2223236
So you can go ahead and flash anything that is compatible with Sprint, so if you're looking at recoveries:
TWRP is here: http://teamw.in/project/twrp2
and you'll see that M7 and M7_WLS are different: http://gyazo.com/df1eb00c8b329d2487310d9eda6acba5
As for the ROM, you are safe to flash ARHD 31.6, but NOT 51.0 (if you don't believe me just read a few of the last pages of the ARHD thread)
Hi thanks, could you please give the link of Arhd 31.6....
gm_vel said:
Hi thanks, could you please give the link of Arhd 31.6....
Click to expand...
Click to collapse
thread is here: http://forum.xda-developers.com/showthread.php?t=2183023
download is here: http://www.androidrevolution.nl/downloader/download.php?file=Android_Revolution_HD-One_31.6.zip
MD5: B4EDA0171BF3BFED779C2107EF6C6F76
Could you please tell me how to put custom ROM on virtual SD card in custom recovery
nkk71 said:
thread is here: http://forum.xda-developers.com/showthread.php?t=2183023
download is here: http://www.androidrevolution.nl/downloader/download.php?file=Android_Revolution_HD-One_31.6.zip
MD5: B4EDA0171BF3BFED779C2107EF6C6F76
Click to expand...
Click to collapse
gm_vel said:
Could you please tell me how to put custom ROM on virtual SD card in custom recovery
Click to expand...
Click to collapse
in custom recovery, either
adb push <name of rom>.zip /sdcard/
or
adb sideload <name of rom>.zip
Could you please tell me how to copy the ROM .zip file to mobile SD card from PC...
From SD card we can install the zip file by recovery.. but how can I copy from PC to mobile...
Can I able to copy the zip file in recovery mode... if possible please give me the suggestion
gm_vel said:
Could you please tell me how to copy the ROM .zip file to mobile SD card from PC...
From SD card we can install the zip file by recovery.. but how can I copy from PC to mobile...
Can I able to copy the zip file in recovery mode... if possible please give me the suggestion
Click to expand...
Click to collapse
Wow .. you don't usually see the question posted under the answer
he just told you
in custom recovery, either
adb push <name of rom>.zip /sdcard/
or
adb sideload <name of rom>.zip
Click to expand...
Click to collapse
Oh sorry my friend.. I didn't see that..
Thanks...
when am trying am getting this error!!!! please help me...
please tell me is that i mad any mistake!!!
C:\Android\fastboot-win>adb push SuperSU-v1.93.zip/sdcard/
Android Debug Bridge version 1.0.29
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this command with no additional arguments
will disconnect from all connected TCP/IP devic
es.
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] [--algo <algorithm name> --key <hex-encoded key> --
iv <hex-encoded iv>] <file>
- push this package file to the device and instal
l it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
('--algo', '--key', and '--iv' mean the file is
encrypted already)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb backup [-f <file>] [-apk|-noapk] [-shared|-noshared] [-all] [-system|-nosy
stem] [<packages...>]
- write an archive of the device's data to <file>
.
If no -f option is supplied then the data is wr
itten
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks
themselves
in the archive; the default is noapk.)
(-shared|-noshared enable/disable backup of the
device's
shared storage / SD card contents; the defau
lt is noshared.)
(-all means to back up all installed applicatio
ns)
(-system|-nosystem toggles whether -all automat
ically includes
system applications; the default is to inclu
de system apps)
(<packages...> is the list of applications to b
e backed up. If
the -all or -shared flags are passed, then t
he package
list is optional. Applications explicitly g
iven on the
command line will be included even if -nosys
tem would
ordinarily cause them to be omitted.)
adb restore <file> - restore device contents from the <file> backup
archive
adb help - show this help message
adb version - show version num
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.
C:\Android\fastboot-win>adb sideload SuperSU-v1.93.zip
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
C:\Android\fastboot-win>
nkk71 said:
in custom recovery, either
adb push <name of rom>.zip /sdcard/
or
adb sideload <name of rom>.zip
Click to expand...
Click to collapse
gm_vel said:
when am trying am getting this error!!!! please help me...
please tell me is that i mad any mistake!!!
C:\Android\fastboot-win>adb push SuperSU-v1.93.zip/sdcard/
Android Debug Bridge version 1.0.29
C:\Android\fastboot-win>adb sideload SuperSU-v1.93.zip
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
C:\Android\fastboot-win>
Click to expand...
Click to collapse
1- adb push SuperSU-v1.93.zip/sdcard/ <- missing space =>adb push SuperSU-v1.93.zip<space> /sdcard/
2- why are you installing SuperSU? you need to install the ROM downloaded earlier
adb push Android_Revolution_HD-One_31.6.zip /sdcard/
3- check your device is recognized by typing "adb devices" -> should come back with your serial number and "recovery" indicating you're in custom recovery
Hi all,
I am Marc and i'm new here on the forum..(and in installing custom roms). so i tried cyanogenmod for a couple of days , but then i decided to go back to stock rom. And somehow,i messed up at that moment. I now have a HTC One wich will only boot in bootloader mode,nothing else.
If i set the Phone to fastboot mode, i don't see it in windows..if it's in recovery mode i see the Phone in windows,but it is unaccessable...so i can't copy a new rom to the Phone and reinstall it with twrp recovery.(that is on the Phone)
HTC One is a international version. Here is the getvar info..
version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.21.3263.04
version-cpld: None
version-microp: None
version-main: 3.62.401.1
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__E11
battery-status: good
battery-voltage: 4291mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-bb768ae1
hbootpreupdate: 11
gencheckpt: 0
Confused as i was i formatted the system in recovery mode and now it looks like there's no partition anymore..
I'm desperate...can somebody help me?
marc1201 said:
Hi all,
I am Marc and i'm new here on the forum..(and in installing custom roms). so i tried cyanogenmod for a couple of days , but then i decided to go back to stock rom. And somehow,i messed up at that moment. I now have a HTC One wich will only boot in bootloader mode,nothing else.
If i set the Phone to fastboot mode, i don't see it in windows..if it's in recovery mode i see the Phone in windows,but it is unaccessable...so i can't copy a new rom to the Phone and reinstall it with twrp recovery.(that is on the Phone)
HTC One is a international version. Here is the getvar info..
version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.21.3263.04
version-cpld: None
version-microp: None
version-main: 3.62.401.1
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__E11
battery-status: good
battery-voltage: 4291mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-bb768ae1
hbootpreupdate: 11
gencheckpt: 0
Confused as i was i formatted the system in recovery mode and now it looks like there's no partition anymore..
I'm desperate...can somebody help me?
Click to expand...
Click to collapse
you must be using Windows 8.1
get yourself Windows 7 or Ubuntu
Sent from my One using Tapatalk
kamilmirza said:
you must be using Windows 8.1
get yourself Windows 7 or Ubuntu
Sent from my One using Tapatalk
Click to expand...
Click to collapse
I am using windows 7 pro
marc1201 said:
I am using windows 7 pro
Click to expand...
Click to collapse
in custom recovery use:
adb push <name of rom>.zip /data/media/0/
or
adb sideload <name of rom>.zip
to get a ROM onto your phone and install it.
nkk71 said:
in custom recovery use:
adb push <name of rom>.zip /data/media/0/
or
adb sideload <name of rom>.zip
to get a ROM onto your phone and install it.
Click to expand...
Click to collapse
When i use adb push i got the following:
C:\Users\Marc\Downloads\HTCOneRoot>adb push firmware 3.62.401.1.zip/data/media/0
/
error: closed
So it says error: closed
When i use adb sideload it says:
Android Debug Bridge version 1.0.31
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <specific device> - directs command to the device or emulator with
the given
serial number or qualifier. Overrides ANDROID_S
ERIAL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices [-l] - list all connected devices
('-l' will also list device qualifiers)
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this command with no additional arguments
will disconnect from all connected TCP/IP devic
es.
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] [--algo <algorithm name> --key <hex-encoded key> --
iv <hex-encoded iv>] <file>
- push this package file to the device and instal
l it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
('--algo', '--key', and '--iv' mean the file is
encrypted already)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb backup [-f <file>] [-apk|-noapk] [-shared|-noshared] [-all] [-system|-nosy
stem] [<packages...>]
- write an archive of the device's data to <file>
.
If no -f option is supplied then the data is wr
itten
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks
themselves
in the archive; the default is noapk.)
(-shared|-noshared enable/disable backup of the
device's
shared storage / SD card contents; the defau
lt is noshared.)
(-all means to back up all installed applicatio
ns)
(-system|-nosystem toggles whether -all automat
ically includes
system applications; the default is to inclu
de system apps)
(<packages...> is the list of applications to b
e backed up. If
the -all or -shared flags are passed, then t
he package
list is optional. Applications explicitly g
iven on the
command line will be included even if -nosys
tem would
ordinarily cause them to be omitted.)
adb restore <file> - restore device contents from the <file> backup
archive
adb help - show this help message
adb version - show version num
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb get-devpath - prints: <device-path>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.
C:\Users\Marc\Downloads\HTCOneRoot>
I don't know anymore...I'm really new in these things
Marc
marc1201 said:
When i use adb push i got the following:
C:\Users\Marc\Downloads\HTCOneRoot>adb push firmware 3.62.401.1.zip/data/media/0
I don't know anymore...I'm really new in these things
Marc
Click to expand...
Click to collapse
1- Why are you pushing a firmware?? you need to push a ROM
2- adb push <name of rom without spaces>.zip /data/media/0/ , you typed:
adb push firmware<space should not be here>3.62.401.1.zip<missing space>/data/media/0
nkk71 said:
1- Why are you pushing a firmware?? you need to push a ROM
2- adb push <name of rom without spaces>.zip /data/media/0/ , you typed:
adb push firmware<space should not be here>3.62.401.1.zip<missing space>/data/media/0
Click to expand...
Click to collapse
@ nkk71, isn't that the same?(rom or firmware) The file i downloaded is named firmware 3.62.401.1,wich should be the 4.3 rom with sense 5.5...
I guess i better left it Original..:crying:
Edit: when i do it like you said i still got the same error:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: closed
C:\Users\Marc\Downloads\HTCOneRoot>
marc1201 said:
isn't that the same?(rom or firmware) The file i downloaded is named firmware 3.62.401.1,wich should be the 4.3 rom with sense 5.5...
I guess i better left it Original..:crying:
Click to expand...
Click to collapse
NO, it is certainly not the same.
I think you should take a break (before you do something you'll really regret), and do some reading (no offense intended).... we were all where you are now, but start searching and reading.
nkk71 said:
NO, it is certainly not the same.
I think you should take a break (before you do something you'll really regret), and do some reading (no offense intended).... we were all where you are now, but start searching and reading.
Click to expand...
Click to collapse
I think i should do that yes.. I have another file called M7-3.4.10-g6ac477c This is the rom i think.(m7 is given in the file name)
But still got errors...:crying::crying::crying:
I think i just going to send it to HTC...No warranty then,but probably less cost then buying a new one
Another question..do i need to have S-OFF?? It's still on S-ON...
marc1201 said:
I think i should do that yes.. I have another file called M7-3.4.10-g6ac477c This is the rom i think.(m7 is given in the file name)
But still got errors...:crying::crying::crying:
I think i just going to send it to HTC...No warranty then,but probably less cost then buying a new one
Another question..do i need to have S-OFF?? It's still on S-ON...
Click to expand...
Click to collapse
While in fastboot USB, use the command "fastboot erase cache", and then push the ROM, not the firmware..... do what nkk71 wrote and you should be alright! Do not send the phone to HTC, you will get no refund or repair done
I am able to erase the cache but pushing the rom will not work here.. then somehowe the device is not recognized
C:\Users\Marc\Downloads\HTCOneRoot>fastboot erase cache
< waiting for device >
erasing 'cache'...
OKAY [ 0.065s]
finished. total time: 0.066s
C:\Users\Marc\Downloads\HTCOneRoot>adb push m7-3.4.10-g6ac477c.zip /data/media/0
/
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
C:\Users\Marc\Downloads\HTCOneRoot>adb devices
List of devices attached
C:\Users\Marc\Downloads\HTCOneRoot>adb devices
List of devices attached
FA35RW907658 recovery
C:\Users\Marc\Downloads\HTCOneRoot>adb push m7-3.4.10-g6ac477c.zip /data/media/0
/
cannot stat 'm7-3.4.10-g6ac477c.zip': No such file or directory
C:\Users\Marc\Downloads\HTCOneRoot>adb push m7-3.4.10-g6ac477c.zip /data/media/0
/
error: device not found
marc1201 said:
I am able to erase the cache but pushing the rom will not work here.. then somehowe the device is not recognized
C:\Users\Marc\Downloads\HTCOneRoot>fastboot erase cache
< waiting for device >
erasing 'cache'...
OKAY [ 0.065s]
finished. total time: 0.066s
C:\Users\Marc\Downloads\HTCOneRoot>adb push m7-3.4.10-g6ac477c.zip /data/media/0
/
error: device not found
error: device not found
Click to expand...
Click to collapse
you need to be in custom recovery for adb to work
bootloader => only fastboot commands
custom recovery => only adb commands
booted ROM with USB debugging enabled => only adb commands
I don't know where you got that file from (or if it is even a ROM, looks more like a kernel to me), but check my signature and use Clyde's index thread for a list of ROMs.
I'm on ARHD: http://forum.xda-developers.com/showthread.php?t=2183023
Recommended recovery (especially for 4.4 ROMs) is TWRP at the moment:
2.6.3.3: http://techerrata.com/browse/twrp2/m7
or 2.6.3.4: http://techerrata.com/browse/twrp2/m7ul
make sure to check MD5 to know it's not a corrupt download, that site doesnt work with download managers.
in bootloader:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
-> enter recovery
adb devices -> confirm it shows up
adb push Android_Revolution_HD-One_51.0.zip /data/media/0/ <- this will take about 5 mins, and will not show any progress until it's finished
in recovery select "install" and choose the ROM, go through the installation (and select wipe!!)
I hope that's clear
nkk71 said:
you need to be in custom recovery for adb to work
bootloader => only fastboot commands
custom recovery => only adb commands
booted ROM with USB debugging enabled => only adb commands
I don't know where you got that file from (or if it is even a ROM, looks more like a kernel to me), but check my signature and use Clyde's index thread for a list of ROMs.
I'm on ARHD: http://forum.xda-developers.com/showthread.php?t=2183023
Recommended recovery (especially for 4.4 ROMs) is TWRP at the moment:
2.6.3.3: http://techerrata.com/browse/twrp2/m7
or 2.6.3.4: http://techerrata.com/browse/twrp2/m7ul
make sure to check MD5 to know it's not a corrupt download, that site doesnt work with download managers.
in bootloader:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
-> enter recovery
adb devices -> confirm it shows up
adb push Android_Revolution_HD-One_51.0.zip /data/media/0/ <- this will take about 5 mins, and will not show any progress until it's finished
in recovery select "install" and choose the ROM, go through the installation (and select wipe!!)
I hope that's clear
Click to expand...
Click to collapse
nkk71,that's pretty clear,downloaded the Android_Revolution_HD-One_31.6.zip and followed all the steps you mentioned..But the Phone still won't cooperate.. I got a protocol failure..What is this?
C:\Users\Marc\Downloads\HTCOneRoot>fastboot flash recovery openrecovery-twrp-2.6
.3.3-m7.img
< waiting for device >
sending 'recovery' (9184 KB)...
OKAY [ 1.165s]
writing 'recovery'...
OKAY [ 0.716s]
finished. total time: 1.884s
C:\Users\Marc\Downloads\HTCOneRoot>fastboot erase cache
erasing 'cache'...
OKAY [ 0.058s]
finished. total time: 0.059s
C:\Users\Marc\Downloads\HTCOneRoot>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.043s]
finished. total time: 0.044s
C:\Users\Marc\Downloads\HTCOneRoot>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
FA35xxxxx sideload
C:\Users\Marc\Downloads\HTCOneRoot>adb push Android_Revolution_HD-One_31.6.zip /
data/media/0/
protocol failure
C:\Users\Marc\Downloads\HTCOneRoot>
At a second try i got this..:
C:\Users\Marc\Downloads\HTCOneRoot>adb push Android_Revolution_HD-One_31.6.zip /
data/media/0/
failed to copy 'Android_Revolution_HD-One_31.6.zip' to '/data/media/0/': Is a di
rectory
What does the sideload after the FA35XXX number? I tought it had to be FA35XXX Device...?
If device is in sideload then do adb sideload romname.zip
sent from my mobile device
marc1201 said:
nkk71,that's pretty clear,downloaded the Android_Revolution_HD-One_31.6.zip and followed all the steps you mentioned..But the Phone still won't cooperate.. I got a protocol failure..What is this?
C:\Users\Marc\Downloads\HTCOneRoot>fastboot flash recovery openrecovery-twrp-2.6
.3.3-m7.img
< waiting for device >
sending 'recovery' (9184 KB)...
OKAY [ 1.165s]
writing 'recovery'...
OKAY [ 0.716s]
finished. total time: 1.884s
C:\Users\Marc\Downloads\HTCOneRoot>fastboot erase cache
erasing 'cache'...
OKAY [ 0.058s]
finished. total time: 0.059s
C:\Users\Marc\Downloads\HTCOneRoot>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.043s]
finished. total time: 0.044s
C:\Users\Marc\Downloads\HTCOneRoot>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
FA35RW907658 sideload
C:\Users\Marc\Downloads\HTCOneRoot>adb push Android_Revolution_HD-One_31.6.zip /
data/media/0/
protocol failure
C:\Users\Marc\Downloads\HTCOneRoot>
Click to expand...
Click to collapse
you have to download a ROM. look here. http://forum.xda-developers.com/showthread.php?t=2183023 Download that rom and then do the above command.Just make sure you type in the correct name of the file in your command window. Firmware is not the same as a ROM. a ROM is a custom version of the operating system i.e. Android in this case. There are many ROMS to choose from. What you are attempting is not correct. This is why you must read.read .read and read BEFORE you attemp anything on a very expensive device. OK? Capeesh? Alright.
@ SaHiLzZ , sideload did the trick
Running the revolution HD-One 3.61 rom now...so back online hehe. Just pity that it isn't a stock rom...I rather had the Phone back in Original state..but that's a thing for later
Is there anyone out here who can help me find the Original stock rom...?
But for now, i am very happy that it runs again and i want to say a very big thank you to all that helped me !! THANK YOU !
Marc
marc1201 said:
@ SaHiLzZ , sideload did the trick
Running the revolution HD-One 3.61 rom now...so back online hehe. Just pity that it isn't a stock rom...I rather had the Phone back in Original state..but that's a thing for later
Is there anyone out here who can help me find the Original stock rom...?
But for now, i am very happy that it runs again and i want to say a very big thank you to all that helped me !! THANK YOU !
Marc
Click to expand...
Click to collapse
Why would you want to go back to stock ROM? ARHD is completely stock, just rooted and with improvements:
This is improved version of stock ROM - no visual changes!
Click to expand...
Click to collapse
nkk71 said:
Why would you want to go back to stock ROM? ARHD is completely stock, just rooted and with improvements:
Click to expand...
Click to collapse
Nkk71,this phone is only about 5 months old and i'm thinking about selling it. So to avoid warranty issues for the new owner and beeing able to update(via HTC) i want the phone back to original state.
Thus..again the question, who can help me with a stock rom?
Thanks again,
Marc
marc1201 said:
Nkk71,this phone is only about 5 months old and i'm thinking about selling it. So to avoid warranty issues for the new owner and beeing able to update(via HTC) i want the phone back to original state.
Thus..again the question, who can help me with a stock rom?
Thanks again,
Marc
Click to expand...
Click to collapse
modelid: PN0710000
cidnum: HTC__E11
Click to expand...
Click to collapse
if you want to sell it and/or return to 100% stock, you can follow my guide: http://forum.xda-developers.com/showthread.php?t=2541082
RUU.ZIP method, using this ruu.zip: http://www.htc1guru.com/dld/ruu-zip...1-27_10-31-1131-05_release_310878_signed-zip/
nkk71 said:
if you want to sell it and/or return to 100% stock, you can follow my guide: http://forum.xda-developers.com/showthread.php?t=2541082
RUU.ZIP method, using this ruu.zip: http://www.htc1guru.com/dld/ruu-zip...1-27_10-31-1131-05_release_310878_signed-zip/
Click to expand...
Click to collapse
I am going to read your guide from a to z to be sure i don't brick it again.
Thanks once more for the help, i really appreciate it !
Is the only way to go stock rom by changing mainboard?? htc malaysia sent "only way is changing the mainboard. Mainboard is too expensive for me. Is any idea to back stockrom??
Check this http://forum.xda-developers.com/showthread.php?p=51151301
Sent from my HTC One
Help this company said:
Is the only way to go stock rom by changing mainboard?? htc malaysia sent "only way is changing the mainboard. Mainboard is too expensive for me. Is any idea to back stockrom??
Click to expand...
Click to collapse
This is now your 4 thread for the same problem. Please quit making new threads and follow the advice folks have already given you for your issue.
Thread 1
Thread 2 <----------------- there were people who helped you here but you have not answered and you left
Thread 3 <----------------- there were people who helped you here but you have not answered and you left
I guess it will be the same thing here...
Back to stock.
Hi. I am Superpulla and i like go to stock from Maximus HD rom. i have 4.19.401.8 Version. I don't know witch ruu.zip i must download. all of them are meant to be on JB??!. If someone could help me with this, i be so thankfull.
I allready get my cid back to stock: HTC__Y13
HTC One m7_ul kitkat 4.4.2 Sense 5.5
Main guestions are: 1. What i do now?
2. Witch Ruu.zip i can flash
Superpulla said:
Hi. I am Superpulla and i like go to stock from Maximus HD rom. i have 4.19.401.8 Version. I don't know witch ruu.zip i must download. all of them are meant to be on JB??!. If someone could help me with this, i be so thankfull.
I allready get my cid back to stock: HTC__Y13
HTC One m7_ul kitkat 4.4.2 Sense 5.5
Main guestions are: 1. What i do now?
2. Witch Ruu.zip i can flash
Click to expand...
Click to collapse
U should repost in your own thread, it's easier to track.
Also post output from fastboot getvar all
A
alray said:
Thread 1
Thread 2 <----------------- there were people who helped you here but you have not answered and you left
Thread 3 <----------------- there were people who helped you here but you have not answered and you left
I guess it will be the same thing here...
Click to expand...
Click to collapse
I need Thread 1,2,3. Each thread different..
Help this company said:
I need Thread 1,2,3. Each thread different..
Click to expand...
Click to collapse
Why? Is it a different device?
Help this company said:
I need Thread 1,2,3. Each thread different..
Click to expand...
Click to collapse
Hmmmm no
To summarize:
Thread #2 (initial thread) -----> phone soft bricked, explained you how to install adb/fastboot/drivers to post a ''getvar all'', determined that you can not use your stock rom atm because of this. So I have suggested you to try this. You did not answered.
Thread #1 ------> phone soft bricked, you are asking again to flash your stock rom (adb sideload) even after reading this. no body answered in this thread.
Thread #3 --------> phone soft bricked, you are asking direction how to use adb sideload.
Thread #4 (here) ----> phone soft bricked you are asking how to return stock again.
Your issue is: Phone soft bricked. You don't have to create a new thread for each problem you encounter with un-bricking your phone. You could simply update the information in your initial thread so its easier for people to help and for YOU to understand. Now read back those threads and ask questions about what you don't understand (not in a new thread) and I'll (we) be pleased to help you.
---------- Post added at 07:23 PM ---------- Previous post was at 07:08 PM ----------
Help this company said:
Is the only way to go stock rom by changing mainboard?? htc malaysia sent "only way is changing the mainboard. Mainboard is too expensive for me. Is any idea to back stockrom??
Click to expand...
Click to collapse
So again, you can return to stock using a ''guru reset rom''. This is a stock rom that when installed will reset your phone back to stock (stock rom, stock recovery, stock radio). The rom is pushed to your sd card via TWRP or sideloaded via TWRP. The problem is the guru reset rom version you need have a bad file that will prevent you to get ota updates (discussed here)
this Reset ROM is supposed to install 3.63.707.4 software on the phone but it installs 3.63.707.3 instead , the software information under settings shows 3.63.707.3 while OS in "fastboot getvar all" shows 3.63.707.4. i went ahead and tried to OTA update it with this ROM but it gave variant error because of fw and sw number not matching
Click to expand...
Click to collapse
. So you will not be 100% stock because of this but at least your phone will boot.
Option 2 is to flash a custom rom like ARHD. It really looks and feels like the stock rom. This is a rock stable rom, always up to date. Again you'll need to push or sideload the rom
Option 3 is to go back to stock using a RUU. Unfortunately the only RUU for you phone version is DECRYPTED which means it required S-OFF to be flashed. So to use this RUU you'll need to S-OFF your phone which require to flash ARHD rom before.
Hope its clear, ask any questions if not, or choose which option you prefer and we will assist you but please for the love of god, no more threads :victory:
a
alray said:
Hmmmm no
To summarize:
Thread #2 (initial thread) -----> phone soft bricked, explained you how to install adb/fastboot/drivers to post a ''getvar all'', determined that you can not use your stock rom atm because of this. So I have suggested you to try this. You did not answered.
Thread #1 ------> phone soft bricked, you are asking again to flash your stock rom (adb sideload) even after reading this. no body answered in this thread.
Thread #3 --------> phone soft bricked, you are asking direction how to use adb sideload.
Thread #4 (here) ----> phone soft bricked you are asking how to return stock again.
Your issue is: Phone soft bricked. You don't have to create a new thread for each problem you encounter with un-bricking your phone. You could simply update the information in your initial thread so its easier for people to help and for YOU to understand. Now read back those threads and ask questions about what you don't understand (not in a new thread) and I'll (we) be pleased to help you.
---------- Post added at 07:23 PM ---------- Previous post was at 07:08 PM ----------
So again, you can return to stock using a ''guru reset rom''. This is a stock rom that when installed will reset your phone back to stock (stock rom, stock recovery, stock radio). The rom is pushed to your sd card via TWRP or sideloaded via TWRP. The problem is the guru reset rom version you need have a bad file that will prevent you to get ota updates (discussed here)
. So you will not be 100% stock because of this but at least your phone will boot.
Option 2 is to flash a custom rom like ARHD. It really looks and feels like the stock rom. This is a rock stable rom, always up to date. Again you'll need to push or sideload the rom
Option 3 is to go back to stock using a RUU. Unfortunately the only RUU for you phone version is DECRYPTED which means it required S-OFF to be flashed. So to use this RUU you'll need to S-OFF your phone which require to flash ARHD rom before.
Hope its clear, ask any questions if not, or choose which option you prefer and we will assist you but please for the love of god, no more threads :victory:
Click to expand...
Click to collapse
thank you. I want to go back perfect stock rom. So I have to s-off... But how to s-off??
And I don't want to use any custom rom.
Last, I have a question, Do I not to send htc malaysia center to change mainboard??
Now, I'll not use any fixing ways but i will use only ur ways. I believe you!!
*Information.
my hboot is 1.56. radio ; 4A.23.3263.28 OS; 4.20.707.6 S-ON TAMPERED UNLOCKED.
Help this company said:
thank you. I want to go back perfect stock rom. So I have to s-off... But how to s-off??
And I don't want to use any custom rom.
Click to expand...
Click to collapse
Help this company said:
my hboot is 1.56.
Click to expand...
Click to collapse
You can s-off your phone using rumrunner tool or firewater tool. However many users reported not being able to s-off on hboot 1.56. You'll have to try it. You'll need to use a custom even if you don't want. A working rom is needed to achieve s-off. If you can't s-off you'll have no choice using a custom rom or the guru reset rom
Help this company said:
Last, I have a question, Do I not to send htc malaysia center to change mainboard??
Click to expand...
Click to collapse
If you phone still able to boot in bootloader mode, you don't have to send the phone for repair.
A
alray said:
You can s-off your phone using rumrunner tool or firewater tool. However many users reported not being able to s-off on hboot 1.56. You'll have to try it. You'll need to use a custom even if you don't want. A working rom is needed to achieve s-off. If you can't s-off you'll have no choice using a custom rom or the guru reset rom
If you phone still able to boot in bootloader mode, you don't have to send the phone for repair.
Click to expand...
Click to collapse
adb reboot (<--- important!!!!)
adb wait-for-device push firewater /data/local/tmp
adb shell su
chmod 755 /data/local/tmp/firewater /data/local/tmp/firewater
Shoud I input that code at cmd??? For example adb reboot. And Why important "adb reboot"?
And Shoud I add the file "firewater" at existing adb folder??
Last, To use adb command, what I have to prepare? Stay twrp recovery or bootloader or fastboot??
I'm so sorry about my short root knowledge...
Help this company said:
adb reboot (<--- important!!!!)
adb wait-for-device push firewater /data/local/tmp
adb shell su
chmod 755 /data/local/tmp/firewater /data/local/tmp/firewater
Shoud I input that code at cmd??? For example adb reboot. And Why important "adb reboot"?
And Shoud I add the file "firewater" at existing adb folder??
Last, To use adb command, what I have to prepare? Stay twrp recovery or bootloader or fastboot??
I'm so sorry about my short root knowledge...
Click to expand...
Click to collapse
Do you have arhd rom installed on your phone?
a
alray said:
Do you have arhd rom installed on your phone
Click to expand...
Click to collapse
No, Could you write download link?? And 1st install arhd 2nd go back to stock rom??
How to s-off by using firewater?? I downloaded file, and just type "adb reboot (<--- important!!!!)*adb wait-for-device push firewater /data/local/tmp*adb shell su*chmod 755 /data/local/tmp/firewater /data/local/tmp/firewater" ????
Help this company said:
No, Could you write download link??
Click to expand...
Click to collapse
Easy to find on the forum. ARHD is the second thread listed under the ''ROMs'' tab or a simple search on google using ''ARHD'' and ''HTC ONE'' key words will brings you at the right place.
Help this company said:
And 1st install arhd 2nd go back to stock rom??
Click to expand...
Click to collapse
flash arhd first then if you can achieve s-off you'll be able to run the ruu to go back to stock. If you can't s-off then use arhd rom.
Help this company said:
How to s-off by using firewater?? I downloaded file, and just type "adb reboot''
Click to expand...
Click to collapse
Hmmmm, so your phone is softbricked which mean it can't boot. How can you reboot a phone that is not booted?! You need a working rom before. Then follow the guide I have posted above to s-off.
Honestly, making your phone boot should be your absolute priority. You are at step #1 -----> making your phone boot by flashing a rom. S-off is like step #10.
alray said:
Easy to find on the forum. ARHD is the second thread listed under the ''ROMs'' tab or a simple search on google using ''ARHD'' and ''HTC ONE'' key words will brings you at the right place.
flash arhd first then if you can achieve s-off you'll be able to run the ruu to go back to stock. If you can't s-off then use arhd rom.
Hmmmm, so your phone is softbricked which mean it can't boot. How can you reboot a phone that is not booted?! You need a working rom before. Then follow the guide I have posted above to s-off.
Honestly, making your phone boot should be your absolute priority. You are at step #1 -----> making your phone boot by flashing a rom. S-off is like step #10.
Click to expand...
Click to collapse
1. Should I check the radio,etc of ARHD ROM??
2. If I downloaded Arhd, Should I use "adb sideload arhdname.zip"??
3. I entered adb sideload and Swipe it, it shows me "Failed". What's the problem???
Thank U Mr.alray helping me. I'll do that at night(korea time).
Sincerely, I appreciate ur help.
Help this company said:
1. Should I check the radio,etc of ARHD ROM??
2. If I downloaded Arhd, Should I use "adb sideload arhdname.zip"??
3. I entered adb sideload and Swipe it, it shows me "Failed". What's the problem???
Thank U Mr.alray helping me. I'll do that at night(korea time).
Sincerely, I appreciate ur help.
Click to expand...
Click to collapse
1. just flash the rom
2. adb sideload it or adb push it.
3. Maybe a driver issue. When in twrp sideload mode, open a command prompt from your adb/fastboot folder and type ''adb devices''. What is the output?
a
alray said:
1. just flash the rom
2. adb sideload it or adb push it.
3. Maybe a driver issue. When in twrp sideload mode, open a command prompt from your adb/fastboot folder and type ''adb devices''. What is the output?
Click to expand...
Click to collapse
when I typed adb devices,it shows "my serial name sideload". and I did adb sideload arhd.zip. it shows 100% but I can't find the file.
also, I did adb push,this shows me this.↓
-a - directs adb to listen on all interfaces for a c
onnection
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <specific device> - directs command to the device or emulator with
the given
serial number or qualifier. Overrides ANDROID_S
ERIAL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
-H - Name of adb server host (default: localhost)
-P - Port of adb server (default: 5037)
devices [-l] - list all connected devices
('-l' will also list device qualifiers)
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this command with no additional arguments
will disconnect from all connected TCP/IP devic
es.
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward --list - list all forward socket connections.
the format is a list of lines with the followin
g format:
<serial> " " <local> " " <remote> "\n"
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb forward --no-rebind <local> <remote>
- same as 'adb forward <local> <remote>' but fail
s
if <local> is already forwarded
adb forward --remove <local> - remove a specific forward socket connection
adb forward --remove-all - remove all forward socket connections
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] [--algo <algorithm name> --key <hex-encoded key> --
iv <hex-encoded iv>] <file>
- push this package file to the device and instal
l it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
('--algo', '--key', and '--iv' mean the file is
encrypted already)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb backup [-f <file>] [-apk|-noapk] [-obb|-noobb] [-shared|-noshared] [-all]
[-system|-nosystem] [<packages...>]
- write an archive of the device's data to <file>
.
If no -f option is supplied then the data is wr
itten
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks
themselves
in the archive; the default is noapk.)
(-obb|-noobb enable/disable backup of any insta
lled apk expansion
(aka .obb) files associated with each applic
ation; the default
is noobb.)
(-shared|-noshared enable/disable backup of the
device's
shared storage / SD card contents; the defau
lt is noshared.)
(-all means to back up all installed applicatio
ns)
(-system|-nosystem toggles whether -all automat
ically includes
system applications; the default is to inclu
de system apps)
(<packages...> is the list of applications to b
e backed up. If
the -all or -shared flags are passed, then t
he package
list is optional. Applications explicitly g
iven on the
command line will be included even if -nosys
tem would
ordinarily cause them to be omitted.)
adb restore <file> - restore device contents from the <file> backup
archive
adb help - show this help message
adb version - show version num
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb get-devpath - prints: <device-path>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.
Help this company said:
when I typed adb devices,it shows "my serial name sideload". and I did adb sideload arhd.zip. it shows 100% but I can't find the file.
also, I did adb push,this shows me this.↓
Click to expand...
Click to collapse
You need to add the file name you want to push and its destination on the phone! Not only ''adb push''
Code:
adb push <name_of_rom>.zip /sdcard/
then your rom will be on your sdcard folder.
or
adb sideload using this command:
Code:
adb sideload <name_of_rom>.zip
Btw use the sideload command when in twrp sideload mode (''adb devices'' must output your s/n + sideload)
use adb push when in twrp recovery main menu (''adb devices'' must output your s/n + recovery)
---------- Post added at 07:06 PM ---------- Previous post was at 07:05 PM ----------
and the long text you posted is the help page. Every time you see that page means you did not typed a valid command.
-a - directs adb to listen on all interfaces for a c
onnection
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <specific device> - directs command to the device or emulator with
the given
serial number or qualifier. Overrides ANDROID_S
ERIAL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
etc etc etc.....
Click to expand...
Click to collapse
a
alray said:
You need to add the file name you want to push and its destination on the phone! Not only ''adb push''
Code:
adb push <name_of_rom>.zip /sdcard/
then your rom will be on your sdcard folder.
or
adb sideload using this command:
Code:
adb sideload <name_of_rom>.zip
Btw use the sideload command when in twrp sideload mode (''adb devices'' must output your s/n + sideload)
use adb push when in twrp recovery main menu (''adb devices'' must output your s/n + recovery)
---------- Post added at 07:06 PM ---------- Previous post was at 07:05 PM ----------
and the long text you posted is the help page. Every time you see that page means you did not typed a valid command.
Click to expand...
Click to collapse
WOW, Finally, I did !!!!!!! I hadn't supersu in my device. I was deleted it. I installed supersu by adb sideload today,It works well.!!!!!!!!
Thank U !!!! thank u very much(x100).!!!!!!!!!!!! U save my money and life.!!!!
Now, Should I s-off to go back to stock rom???
And If I clicked the Thanks, Can't I ask this inquiry???
Anyway Thanks Mr.alray. Ur perfert Guy!!!!!!:good:
WARNING: THIS IS EXPERIMENTAL BETA FOR TEST
Prerequisites:
The bootloader must be unlocked.
Install ADB and Fastboot Drivers -->https://www.mediafire.com/file/7pal74b7e734u5d/15_Second_ADB_Installer_v1.5.6.zip/file
Download the TWRP Image for Poco M3 Pro 5G --> https://www.mediafire.com/file/1h3ogmhij694mby/Twrp_-3.6.0_11_port_poco_m3pro_5g_Camellia.img/file
Installing FastBoot drivers:
if you encountered no file are copied then disable your anti virus and retry in Linux just type 'apt install fastboot' 'dnf install fastboot' 'pacman -S fastboot' based on your current linux distro
Installing TWRP:
Reboot the phone to fastboot (Power + Vol Down)
Connect the phone to the computer using an USB cable (Preferred to use original cable that came with the phone)
Extract the fastboot files and open CMD/Terminal there.
Paste the twrp.img in the same folder.
Type' fastboot boot file_name.img' without the apostrophes.
The phone will reboot in TWRP after that go to Advanced > Flash Current TWRP.
Done!
All Feautures Works
Send Feedbacks Here Please
Developer : SpoliatorDRKBIN
Great! Is touch working on this?
great!!!!!
SalmanSH1 said:
WARNING: THIS IS EXPERIMENTAL BETA FOR TEST
Prerequisites:
The bootloader must be unlocked. Click here for a tutorial.
Install ADB and Fastboot Drivers from here (Select the latest) --> https://androidmtk.com/download-minimal-adb-and-fastboot-tool )
Install drivers for Camellian --> https://droidfilehost.com/download/download-xiaomi-usb-driver-for-windows (For Windows Only!)
Download the TWRP Image for Poco M3 Pro 5G --> https://www.mediafire.com/file/1h3ogmhij694mby/Twrp_-3.6.0_11_port_poco_m3pro_5g_Camellia.img/file
Installing TWRP:
Reboot the phone to fastboot (Power + Vol Down)
Connect the phone to the computer using an USB cable (Preferred to use original cable that came with the phone)
Extract the fastboot files and open CMD/Terminal there.
Paste the twrp.img in the same folder.
Type' fastboot boot file_name.img' without the apostrophes.
The phone will reboot in TWRP after that go to Advanced > Flash Current TWRP.
Done!
All Feautures Works
Send Feedbacks Here Please
Developer : SpoliatorDRKBIN
Click to expand...
Click to collapse
Did you own m3 pro ?
mtk device wont boot with this method according to:
fastboot boot command is bugged on Xiaomi MTK devices · Issue #2356 · MiCode/Xiaomi_Kernel_OpenSource
The best practice for installing TWRP seems to be to inject ramdisk after using fastboot boot twrp.img command. But when this command is broken on the firmware side, I have to make new TWRP build e...
github.com
up864 said:
Did you own m3 pro ?
mtk device wont boot with this method according to:
fastboot boot command is bugged on Xiaomi MTK devices · Issue #2356 · MiCode/Xiaomi_Kernel_OpenSource
The best practice for installing TWRP seems to be to inject ramdisk after using fastboot boot twrp.img command. But when this command is broken on the firmware side, I have to make new TWRP build e...
github.com
Click to expand...
Click to collapse
i confirm, dont boot. i thik he didnt test before post
shi-no_tenshi said:
Great! Is touch working on this?
Click to expand...
Click to collapse
yes touch works
up864 said:
Did you own m3 pro ?
mtk device wont boot with this method according to:
fastboot boot command is bugged on Xiaomi MTK devices · Issue #2356 · MiCode/Xiaomi_Kernel_OpenSource
The best practice for installing TWRP seems to be to inject ramdisk after using fastboot boot twrp.img command. But when this command is broken on the firmware side, I have to make new TWRP build e...
github.com
Click to expand...
Click to collapse
yes m3 Pro 5G
i'm not Developer
wetito said:
i confirm, dont boot. i thik he didnt test before post
Click to expand...
Click to collapse
do you tested ?
use xiaomi Fastboot tools ?
i edited 1st topic
i'll send Video of this Work
fastboot boot Twrp_-3.6.0_11_port_poco_m3pro_5g_Camellia.img
Sending 'boot.img' (38034 KB) OKAY [ 1.423s]
Booting FAILED (Status read failed (No such device))
fastboot: error: Command failed
fastboot boot Twrp_-3.6.0_11_Camellia.img
Sending 'boot.img' (38034 KB) OKAY [ 1.423s]
Booting FAILED (Status read failed (No such device))
fastboot: error: Command failed
Not Booting Redmi Note 10 5G....
Please Fix
use xiaomi fastboot tools
SalmanSH1 said:
use xiaomi fastboot tools
Click to expand...
Click to collapse
Sir Twrp Not Booting On Redmi Note 10 5G
emhashmi said:
fastboot boot Twrp_-3.6.0_11_Camellia.img
Sending 'boot.img' (38034 KB) OKAY [ 1.423s]
Booting FAILED (Status read failed (No such device))
fastboot: error: Command failed
Not Booting Redmi Note 10 5G....
Please Fix
Click to expand...
Click to collapse
https://www.mediafire.com/file/7pal74b7e734u5d/15_Second_ADB_Installer_v1.5.6.zip/file
Use This ADB fastboot installer
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot Twrp_-3.6.0_11_port_poco_m3pro_5g_Camellia.img
< waiting for any device >
downloading 'boot.img'...
OKAY [ 0.957s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 9.357s
{
"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"
}
emhashmi said:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot Twrp_-3.6.0_11_port_poco_m3pro_5g_Camellia.img
< waiting for any device >
downloading 'boot.img'...
OKAY [ 0.957s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 9.357s
View attachment 5673465
Click to expand...
Click to collapse
change USB and first send:
fastboot reboot bootloader
then:
fastboot boot twrp.img
SalmanSH1 said:
WARNING: THIS IS EXPERIMENTAL BETA FOR TEST
Prerequisites:
The bootloader must be unlocked.
Install ADB and Fastboot Drivers -->https://www.mediafire.com/file/7pal74b7e734u5d/15_Second_ADB_Installer_v1.5.6.zip/file
Download the TWRP Image for Poco M3 Pro 5G --> https://www.mediafire.com/file/1h3ogmhij694mby/Twrp_-3.6.0_11_port_poco_m3pro_5g_Camellia.img/file
Installing FastBoot drivers:
if you encountered no file are copied then disable your anti virus and retry in Linux just type 'apt install fastboot' 'dnf install fastboot' 'pacman -S fastboot' based on your current linux distro
Installing TWRP:
Reboot the phone to fastboot (Power + Vol Down)
Connect the phone to the computer using an USB cable (Preferred to use original cable that came with the phone)
Extract the fastboot files and open CMD/Terminal there.
Paste the twrp.img in the same folder.
Type' fastboot boot file_name.img' without the apostrophes.
The phone will reboot in TWRP after that go to Advanced > Flash Current TWRP.
Done!
All Feautures Works
Send Feedbacks Here Please
Developer : SpoliatorDRKBIN
Click to expand...
Click to collapse
I got bootloop on MIUI 12.5.4 ID
This doesn't work
SalmanSH1 said:
change USB and first send:
fastboot reboot bootloader
then:
fastboot boot twrp.img
Click to expand...
Click to collapse
I tried USB 3 and USB 2
SalmanSH1 said:
change USB and first send:
fastboot reboot bootloader
then:
fastboot boot twrp.img
Click to expand...
Click to collapse
Already Change Usb And Change DATA Cable...But Doesn't work
SalmanSH1 said:
https://www.mediafire.com/file/7pal74b7e734u5d/15_Second_ADB_Installer_v1.5.6.zip/file
Use This ADB fastboot installer
Click to expand...
Click to collapse
i'm a linux user. my adb and fastboot driver are perfect
wetito said:
i'm a linux user. my adb and fastboot driver are perfect
Click to expand...
Click to collapse
I think he is trolling us. Or his phone is lucky one