I have downloaded and installed from market ROM Manager, made update.zip. I have rebooted in native recovery, have executed install:update.zip. It has been installed ClockworkMod Recovery, now it is possible to install zips from a flash card, stable CyanogenMod has installed successfully. However after reboot in recovery mode it is started native recovery, instead of ClockworkMod. It is necessary to install each time Clockwork to install any zip (for example, update-cm-7.1.0-Legend-signed.zip). Why is ClockworkMod installed "for once time"?
I understood my misake
ClockworkMod is executed, but not installed bacause my HTC Legend has S-ON protection. And I have to "install" (not install, but execute) ClockworkMod each time when I want to flash some zip.
Related
Hi, i received HTC sense 3.0 and android 2.3.5 update. I tried to update it but it stuck on boot screen. Restarting didn't help. So I wiped all the data but later realised I no longer have clockworkmod installed.
I go to hboot and try to put recovery on sdcard through adb, but adb cant find my device.
Is there anything I can do? My phone is pretty messed up now, and I don't know what to do RUU also doesn't work, because my phone can't be found.
// #1 OK I managed to install clockworkmod through the Android Flasher. I've downloaded BeatMod BlissSense Hybrid v2.1.zip but I cant install it through the clockworkmod. It says:
"E:Error in /sdcard/BeatMod BlissSense Hybrid v2.1.zip
(Status 1)
Installation aborted."
// #2 sorry to bother.. I disabled the verification check in clockworkmod, installed su-2.3.6.3-efgh-signed.zip and then custom ROM.. everything now works fine. Of course with the help of tutorials on xda and great people over here.
This was the worst 4 hours in my live as I thought my phone is bricked.
good for u man
Adidas108 said:
good for u man
Click to expand...
Click to collapse
+1
You don't appear alone with problem, so thanks for re-editing the thread post to provide updates, if you have the time and could try to add any URLs and links to the files that you used to resolve your issues, then that would be great!
I've already several threads where it appears the update has put others in the same position, so your update could prove to be a useful resource assisting the recovery of others!
Cheers.
Downloads:
Android Flasher: http://forum.xda-developers.com/showthread.php?t=794638 (different versions for different phones)
HTC Desire S Recovery: http://downloads.saga-lbc-mod.de/recovery-images/PG88IMG-RECOVERYIMG-3.2.0.0.zip (unzip and use only recovery.img)
SU (root): http://www.mediafire.com/?q3ujsx1m4uq1662
ROM (I used this): http://dev-host.org/80uvbx4wgf4l/BeatMod_BlissSense_Hybrid_v2.1.zip
----
Install ClockworkMod:
What you need to do is get the phone to fastboot and connect it to the PC via USB.
Launch and update Android Flasher. Choose your phone and browse for recovery image (recovery.img that you have unzipped)
Click finish and wait. Clockworkmod should by installed.
Get files on the phone:
Go to recovery
Mounts and storage menu
Mount USB storage
Then copy files (custom ROM you want to install and su-2.3.6.3-efgh-signed.zip) from PC to SD card
Install Root:
Go to recovery
Install zip from SD card
Toogle signature verification (disable it)
Choose zip from card and install su-2.3.6.3-efgh-signed.zip
Choose zip from card and install custom ROM
Optional steps? (right after installing clockworkmod)
Go to recovery
Wipe data
Go to advanced
Mounts and Storage menu
Format /sdcard
That's it. Hope it helps.
I need the M98 Google 4GS+ ClockWorkMod Recovery.
i installed the Rom Manager 5.0.1.3 on the phone...when i click on Flash ClockworkMod Recovery it search for the phone and it finds Android
asking me if this is my phone..
my question is.. is it possible to install the ClockworkMod Recovery? safely...
(the default recovery is Android Sytem Recovery <3e>)
can someone help?
i noticed that in the update.zip file there is a folder called recovery and a file "recovery-from-boot.p"
I started experimenting with my old P3113 last night and ran into a bit of a problem. I successfully rooted using Odin 3.09, verified with root checker. I also successfully flashed TWRP 2.8.7.0 via Odin. All root and TWRP install/flashes were successful via Odin.
Following these instructions: http://forum.xda-developers.com/gal...m-dhollmen-lollipop-5-0-2-2015-02-02-t3020849
I downloaded the Dhollmen-P31xx-Kernel_20150215.zip and saved to the Download folder on the tab. From TWRP I ran a wipe and installed the .zip. I reboot the device and I am returned to TWRP recovery. TWRP tells me that the installation was successful however the log says "no MD5 file found". Does this have anything to do with why my device isn't booting properly? I've rooted other devices and flashed ROM's before but I don't understand what I missed on this one. Do I just need to try a different ROM? For reference I am still able to access download menu.
Any help would be appreciated!
Well, the "no MD5 file found" just means TWRP cannot verify the MD5 hash of the ZIP file - that's actually a security meassure to ensure the ZIP file didn't get damaged during download or transfer onto the tab.
Now ... once you flashed TWRP (which you obviously already successfully did) and flashed the Kernel (which you obviously also already successfully did) it would be about time to flash the actual Dhollmen ROM that goes along with the Kernel ... I doubt the Kernel will boot up your vanilla Samsung stock ROM.
In short (haven't read the ROM thread nor did I ever use Dhollmen, so check back to make sure it's about right): Download the ROM, download the GApps package for the ROM and download the Superuser package (if not already included in the ROM) of your choice. Put the files onto either a FAT32 formatted SD card (if you can't put them into the NAND "SD card" partition at the moment) or onto a FAT32 formatted USB stick (given you have a USB-OTG cable), plug it in (if you use a USB stick make sure your tablet is CHARGED!), boot into recovery and flash the files in one go ... ROM, Gapps, SU.
Run a wipe (Data and Cache) when everything is flashed to nuke any left-overs from the Stock ROM and reboot to system.
Keep in mind the first boot can take quite some time ... don't panic if the boot animation "just sits there" for 5<->15 minutes.
Easiest way would be to actually use a ROM that doesn't require a extra Kernel ... like Android-Andi's CyanogenMod 12.1 or Omni ROM 5.1 (use the 3110 versions for your 3113).
Hello everyone. I have come up with a lazy way to install custom ROM (such as Cyanogenmod) in *most* phone (I tried this on S3mini and Galaxy MEGA). Please note that this method moght not work on your phone and I am not responsible for bricking your phone.
Things you need:
-Your phone, fully charged
-Your precious time (About 30-60minutes)
-One click root app (I use Kingroot, download it with apk) (You may use other apps, of course)
-TWRP manager from playstore
-ZIP file of TWRP in latest version (V3?)
-ZIP file of the custom ROM matching the version of your device
-ZIP file of GApps matching the version of the custom ROM (Google for gapps and download it)
Steps:
1. Backup your personal information
Copy your personal information such as music, photo, documents out of your phone (e.g.: Cloud drive, USB, SD card). Safety first.
2. Root your phone
Download Kingroot and install the apk with package installer. Run the app and follow the instruction in the app to root.
3. Install TWRP manager
After rooting, install TWRP manager. In the app, install TWRP that match your device.
4. Create a backup for your phone
Boot your phone into recovery (Every phone have different method, so please google about this). In TWRP, press 'Backup' to create the backup.
5. Flash the latest version of TWRP
As the TWRP manager does not offer the latest version of TWRP, you have to flash the latest version by installing ZIP. The latest version of TWRP can install ROM with higher success rate.
To do this, press 'Install' in TWRP. Find the ZIP file of TWRP in latest version and install it.
6. Reboot your device to Recovery mode
7. Wipe your device
In TWRP, press 'Wipe'. Select Cache, Dalvik Cache, System and Data partition and wipe them.
8. Flash custom ROM
In TWRP, press 'Install'. Select the Custom ROM ZIP and install it.
9. Flash GApps
Most custom ROM does not have Google apps such as play stote, so you have to install it.
In TWRP, press 'Install'. Select the GApps ZIP and install it.
10. Wipe Cache and dalvik cache
In TWRP, press 'Wipe'. Select Cache and Dalvik Cache partition and wipe them.
11. Reboot your device
Now the ROM should be properly installed. First boot might take longer, so please wait patiently.
Shall you brick your phone, try to recover by using backup created in step 4.
PS: I am a newbie here and this is my first guide
While you have to wipe your device to flash the custom rom, it will wipe your data, including the actual Gapps and rom. This shows that your method won't work.
downloaded factory image from googles website
copied latest platform tools to the same directory as the extracted contents of the zip from google.
run the batch file, can boot into android just fine.
reboot to bootloader, use fastboot boot twrp-3.2.3-0-walleye.img
install the twrp zip
android boots fine and i can use my phone normally.
install magisk apk, reboot to recovery, install magisk 16.7 zip, android wont boot
everything was fine until i made a backup last night within twrp. ive repeated the above process idk how many times. any help would be appreciated
EDIT: https://forum.xda-developers.com/pixel-2/how-to/guide-unlock-flash-root-pixel-2-walleye-t3702417 is the guide i was using.
EDIT 2: now when i install TWRP and try to reboot to system, it just reboots back to TWRP...
EDIT 3: looking at the contents of my twrp zip, theres a file called magiskboot so what im going to do is reinstall the factory image using the bash script included in the download directly from google, then just flash twrp-pixel2-installer-walleye-3.2.3-0.zip, then install the magisk manager and see what happens. if that doesnt work ill redo the factory image, boot from twrp-3.2.3-0-walleye.img, install magisk, and see what happens without installing twrp.