Develop Bugs

[HELP] Can't Flash Recovery.

When I flash the recovery.
it's fail and hang.
{
"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"
}

Which recovery are you trying to flash?
Try redownloading it (and not renaming it before you flash)

Ti2 said:
Which recovery are you trying to flash?
Try redownloading it (and not renaming it before you flash)
Click to expand...
Click to collapse
THIS ONE recovery-clockwork-5.5.0.2-maguro-gsm

redownload it, reboot into fastboot mode
command: fastboot flash recovery recovery-clockwork-5.5.0.2-maguro.img
It should work

Ti2 said:
redownload it, reboot into fastboot mode
command: fastboot flash recovery recovery-clockwork-5.5.0.2-maguro.img
It should work
Click to expand...
Click to collapse
i'm download form http://galaxynexusroot.com/galaxy-nexus-recovery/how-to-install-clockworkmod-recovery-on-rooted-galaxy-nexus/
but it still not work , and my phone hang on logo of "GOOGLE" . cannot go to Android

Did you rename recovery-clockwork-5.5.0.2-maguro-gsm.img to 1.img?
And you flash it from your android-sdk/platform-tool folder where adb&fastboot are?

Have you searched on the forum?
If you did you found this thread: http://forum.xda-developers.com/showthread.php?t=1428414
Did you try the solution there?
(BTW: make sure you have the right drivers installed and that your device is recognised. Be aware that drivers in Android mode might not work in ADB/Fastboot mode)

Diger36 said:
Have you searched on the forum?
If you did you found this thread: http://forum.xda-developers.com/showthread.php?t=1428414
Did you try the solution there?
(BTW: make sure you have the right drivers installed and that your device is recognised. Be aware that drivers in Android mode might not work in ADB/Fastboot mode)
Click to expand...
Click to collapse
I have tried it..but also solve the problem of "too many link"

I have the same situation here.
I tried all tips at XDA topics about silimar problems and all they failed.
I don't have knowledge to say, but I think that its a hardware problem, specifically at memory, because everything I try to flash freeze the screen like the picture at first post.

nvm just saw the giant picture..
Sent From My Sprint Galaxy Nexus via XDA Premium

I had this same issue. I can't remember what I did though.. I'm pretty sure I deleted clockwork mod then I fixed permissions and then dl clockwork back from the play store and then it'll work.
Sent from my Galaxy Nexus

@op,
1- did you encrypt your phone?
2- are you running windows cli as administrator?
3- try to update your bootloader to the latest
4- what drivers are you using? Use 1wayjohnny's naked drivers (find them at dev forum)
Sent from my i9250

[Q] installation done but is going only to bootloader

try to change rom on my htc one x and the only thing now is going back to bootloader.
when i installed the rom says : installation done but is going only to bootloader.
what can i do?

celica553 said:
try to change rom on my htc one x and the only thing now is going back to bootloader.
when i installed the rom says : installation done but is going only to bootloader.
what can i do?
Click to expand...
Click to collapse
are you flash the boot.img via fastboot?

Thant said:
are you flash the boot.img via fastboot?
Click to expand...
Click to collapse
THANKS FOR YOUR ANSEWER. NO i dont know how to flash boot.img
i used the One_X_All-In-One_Kit_v2.3 but because im new i dont really kinow how to use it
can u help me pls?

celica553 said:
THANKS FOR YOUR ANSEWER. NO i dont know how to flash boot.img
i used the One_X_All-In-One_Kit_v2.3 but because im new i dont really kinow how to use it
can u help me pls?
Click to expand...
Click to collapse
Take the boot.img from your rom archive and place in your fastboot folder go in fastboot with the phoner then open cmd and runt the command fastboot flash boot boot.img
Why the hell you open two thread wit the same question it is difficult for the members to see what happend and the progress. Please fallow only one of your thread don't post it in two only in one

Thant said:
Take the boot.img from your rom archive and place in your fastboot folder go in fastboot with the phoner then open cmd and runt the command fastboot flash boot boot.img
Why the hell you open two thread wit the same question it is difficult for the members to see what happend and the progress. Please fallow only one of your thread don't post it in two only in one
Click to expand...
Click to collapse
REALLY THANKS, u just made my day

{
"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"
}

[Q] TWRP Update path for One M8

Hello everyone and have a Merry Christmas,
I'm trying to update my TWRP recovery because I want to go 100% stock. I'm still running TWRP 2.7.0.2. The most recent version of TWRP is 2.8.3.0.
I downloaded the TWRP manager app from the Play store and easily selected the last available version of the recovery to install.
After downloading the .img file, I get a pop up that looks like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The pop up says: "Be sure that the listed path is correct for your device. An uncorrect check may result in bricking your device. You can't flash a recovery directly on Android on some devices. If you can't flash through Android, please choose a different method".
It looks like a "routine" alert, but nonetheless it sounds very alarming. How can I say if the listed path is the correct one for my device (HTC One M8 unbranded GSM international version)?
Thank you for helping.

why update twrp ? twrp is not stock ! and you can also fastboot flash it. oldskool way

Because the procedure to go stock requires some flashing and it was adviced to have the latest version running.
I'm not such an expert, I'm more the type who tries to read as much as possible before trying anything, and upgrading TWRP was a sort of "pre-step".
Also I'm not very keen to use fastboot: I got that it is great, but it is not very straightfoward for beginners.
The tool from the Play store seemed to do the job pretty good and easily.

Mr Hofs said:
why update twrp ? twrp is not stock ! and you can also fastboot flash it. oldskool way
Click to expand...
Click to collapse
What if I flash a custom recovery over a custom recovery? Is it possible to simply flash it and overwrite an already existing custom recovery?

there is no other way, the recovery will always overwrite the old one. its impossible to run 2 recoveries

AT&T Note 5 Oem Unlock in Dev Settings

I don't normally post in the forums however I figured this may be important.
Lets hope that this time we may be able to get our bootloaders unlocked.
{
"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"
}

Saw same, subscribed to thread!
Searching for the exact phrase, not much out there I found other than a G4 question regarding the same...

Copied and pasted this from a source I found..
For those new to “OEM unlock,” just know that this is a part of the command used to unlock a Nexus phone’s bootloader. After installing the Android SDK, plugging your phone into a computer, opening adb, and rebooting to the bootloader, a simple command in adb of “fastboot oem unlock” will start the process of phone freedom.

It's a command used in fastboot unfortunately samsung phones don't have a fastboot they have a recovery that you can use adb in and they have odin mode that as far as I can tell fastboot doesn't work in. So I am unsure of how we would test this.
Sent from my SAMSUNG-SM-N920A using Tapatalk

My understanding is that this is hard built into the developer mode, so stock vanilla Google phones like nexus and I'm guessing probably the moto lines are the only phones for which this will work. Basically, you're telling the phone whether to ignore the command altogether or to actually execute the command when it's toggled on. Think of this like the following: oem unlock toggle : permit execution of 'oem unlock' command :: USB enabled toggle :: being able to use the adb command
As @51ngular1ty said above, Sam phones have a completely different recovery architecture, so they respond to different commands/software.

51ngular1ty said:
It's a command used in fastboot unfortunately samsung phones don't have a fastboot they have a recovery that you can use adb in and they have odin mode that as far as I can tell fastboot doesn't work in. So I am unsure of how we would test this.
Sent from my SAMSUNG-SM-N920A using Tapatalk
Click to expand...
Click to collapse
Fastboot is a commandline tool used through adb. You plug you phone in while its on and you can use adb commands but you have yo enable it in the dev settings

[GUIDE] Use TWRP through ADB Shell

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