Clockwork mod recovery has been updated via rom manager
{
"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"
}
Sent from my Nexus S using Tapatalk 2
Delete..........
Might want to add that the touch-version (6.0.0.6) still suffers from broken usb-mount. It's fixed in current non-touch (6.0.0.7).
having trouble flashing the crespo4g recovery.img with fastboot...anyone else?? I ran
Code:
$ fastboot devices
my phone's there & connected. when I run
Code:
$ fastboot flash recovery recovery.img
I get error: cannot load 'recovery.img'
any help?
hp420 said:
having trouble flashing the crespo4g recovery.img with fastboot...anyone else?? I ran
Code:
$ fastboot devices
my phone's there & connected. when I run
Code:
$ fastboot flash recovery recovery.img
I get error: cannot load 'recovery.img'
any help?
Click to expand...
Click to collapse
Check if the .img you have downloaded is named recovery.img :]
madd0g said:
Check if the .img you have downloaded is named recovery.img :]
Click to expand...
Click to collapse
+1, also, remove the $ the command i've always used is fastboot flash recovery recovery.img if recovery isn't saved as recovery.img either replace that w/ actual file name or rename img file... or you could cheat & update through rom manager app
Sent from my Nexus S 4G using xda premium
i tried updating mine through rom manager. after that, it shows successfully flashed recovery and its v6007. i reboot into recovery and its still v5020...*sadface*
Related
Hi all
I have used unrevoked tool about half a year ago,with almost no problems.The only problem I am (still) facing is the off mode charging one.I lived happily with it for some months but now i want to flash a new recovery image to fix the off mode charging thing.I download the image,and use unrevoked to flash it.The problem is it fails at "waiting for root, firmware too new?" eaven though the phone is allready rooted and running cyanogenmod 7.How can I flash a new recovery?
tnx in advance
Well, 3xeno helped me when I had this problem, so I will quote him:
1.) Install Android SDK, and use the Fastboot option.
2.) Get the Recovery.IMG file of the Clockworkmod version you want to flash.
3.) Place this in the SDK's Tools folder.
4.) Reboot your phone in the bootloader mode.
5.) Enter Fastboot mode (Press Power button on Fastboot).
6.) Open Command Prompt on Windows.
7.) cd (browse) to the SDK's tools folder.
8.) Type the following command: "fastboot flash recovery recovery.img". (Without quotes.)
Done.
Screenshot below:
{
"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"
}
Hit thanks if I helped you.
You will need S-OFF by AlphaRev X to use the guide above posted. Else, it wont work. Also, you might want to use an older version of Unrevoked, if you are not interested in getting S-OFF at the moment.
Unrevoked 3.14 is said to work pretty well. Just search around in the forum a bit, many members have uploaded it to various file hosts.
Thank you both!
Unrevoked v3.14 worked like a charm
hi guys,
yesterday i wanted to install vanir rom after having the latest nightly of PA. i accidentally wiped the system partition and now obviously have no zip on my phone to install. i am now at recovery level.
i have tried using adb sideload but received a message
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and afterwards have tried to use this thread http://forum.xda-developers.com/showthread.php?t=1667929
but received these messages (the first is while on recovery, the second is after pressing on adb sideload in the recovery
right now only the data partition is mounted but i am not sure whether it's suppose to be like this, and i still don't have zip inside my phone.
the recovery is team win recovery project v2.6.2.0
please help as i am getting crazy. i wouldn't mind using the toolkit if i knew which option to chose.
thank you
Hi, to install a 4.4+ rom you need to update your recovery to 2.6.3.3 and then try sideload again.
P.s you wiped the user data partition.
well i was already noted it is something like this but i also cannot install the PA RC2 via the adb sideload.
is there a previous version available, as i didn't find any?
and how can update the recovery in such a state?
Download the recovery img not zip!
Copy the img to adb folder boot to bootloader , open cmd and type: fastboot flash recovery file_name.img .
link : http://techerrata.com/browse/twrp2/mako
Thanks it worked! I installed the factory img of kitkat I'll try installing vanir later!
Hi fellows,
I've just screwed up my leeco stock system by deleting accidentally all system files. TWRP is fortunately still working, but now I can't copy a new rom file to the internal storage, as I can't use any file explorer app.
I've tried to do this by using minimal adb fastboot 1.4.1 portable:
{
"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"
}
Even though I followed all the steps, It didn't work.
Any suggestions?
Thank you.
Dioniso said:
Hi fellows,
I've just screwed up my leeco stock system by deleting accidentally all system files. TWRP is fortunately still working, but now I can't copy a new rom file to the internal storage, as I can't use any file explorer app.
I've tried to do this by using minimal adb fastboot 1.4.1 portable:
Even though I followed all the steps, It didn't work.
Any suggestions?
Thank you.
Click to expand...
Click to collapse
Try this : https://forum.xda-developers.com/moto-g/general/tutorial-solution-file-transfer-twrp-t3180926
It worked for me
bayad said:
Try this : https://forum.xda-developers.com/moto-g/general/tutorial-solution-file-transfer-twrp-t3180926
It worked for me
Click to expand...
Click to collapse
Thank you for your answer, but it didn't work for me, but thanks to that driver I could push some little files (1kb) to my mobile phone:
BUT I couldn't repeat the process with big files (like the stock rom), because the transfer gets stuck by the 1%.
The issue has been solved!
I could push the file by using Minimal ADB and Fastboot (Version 1.4.2 with installer) in recovery mode.
I needed a new computer without any old adb drivers and I used the driver suggested by bayad: https://forum.xda-developers.com/mot...-twrp-t3180926 with windows 10 in safe mode.
Thank you very much.
This is the Pixel 3a's TOOL ALL IN ONE Discussion Thread more info and download go to the Original Thread
TOOL ALL IN ONE
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ADVANCED OPTIONS
FUNCTIONS
Install Drivers
Install Drivers
Unlock Bootloader
Lock Bootloader (use carefully)
Flash TWRP Recovery
Flash Stock Recovery
Flash Stock Factory Image
Automatic ROOT
Install APKs
Uninstall APKs
Take a Screenshot
Take a Screen Reocrd
Flash Partitions
Erase All Data (This function can decrypt the phone)
Reboot Phone
Update the Tool to latest version
Update Adb and Fastboot to latest version
Set Adb and Fastboot priviliges in system wide
Install Zip directly from PC (Required TWRP on phone)(These functions work perfectly on my pc but i have perfect adb drivers on my pc and perfect TWRP on my phone)
Flash Fastboot ROM
Delete downloaded files
ADB File Manager
DEVICE LIST
If you want you can send a request to add a new device here:
New Device Request Form
Device List
DOWNLOAD
Original Thread
DONATE LINK
If you want to support the project please consider making a donation, thanks.
Nice! Always keep this on my windows PC!
Sent from my Pixel 3a XL using Tapatalk
If rooted via this tool, can the Pixel 3a still get OTA updates?
Reboot to EDL mode from FASTBOOT!
No more Test Point Method needed
Technical Details:
Redmi Note 3 support rebooting to EDL in Android Bootloader aboot module (the "reboot-edl" command) but fastboot utility doesn't recognize "reboot-edl" in the command line and refuses to sent the command to the device. Since FastBoot command protocol is simple and text-based, it is enough to send a packet containing "reboot-edl" text over USB. The simplest way to do that is to patch Windows fastboot.exe file, replacing "reboot-bootloader" text with "reboot-edl". As "reboot-bootloader" string is found in the command line, fastboot.exe sends the same constant string to the device. So if "reboot-bootloader" is replaced with "reboot-edl", you can specify "reboot-edl" in the command line and the same text will be sent to the device.
New Update: Fastboot updated to latest version.
Tutorial:
1. Download the Fastboot_to_EDL from : https://www.mediafire.com/file/yr7csyo64e97vbu/Fastboot_to_EDL.zip/file
2. Extract the zip in your desktop
3. Open the folder and double Click on Reboot.bat
{
"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"
}
4. Reboot your device to Fastboot Mode by pressing
Vol Down + Power button and connect your device with PC and Press Enter.
5. Your Device will be rebooted to EDL!
6. Now flash your Fastboot Rom with Mi Flash Tool to Unbrick your Mi Note 3.
Proof:
saved my ass
thanks a lot ahmed.....
i bricked my phone.. went to flash twrp without unlocking bootloader and it bricked..
this tool saved the phone else mom was gonna whoop my ass..
peace:good: