General :: Flashed ClockWorkMod Recovery Before Unlocking Bootloader LG 4XHD
Mar 23, 2014
I have a problem with my LG optimus 4XHD. I didn't like the 4.1.2 lg skinned android so i wanted to install a custom rom. I started by rooting my phone that worked but then i flashed clockworkmod recovery without unlocking the bootloader. Now i can't enter my recovery anymore but i can still boot into android. Now my question is: Can i still unlock the bootloader now without bricking my phone?
since I own a Neo V which is locked, and the service menu in the phone says that the Bootloader cannot be unlocked. if I unlock my SIM lock(probably with TurboSIM, since thats the cheapest solution), would that enable me to unlock my bootloader, and start the real modifying of my phone?
i want to know if it's possible to root an Android without unlocking the bootloader. My problem is I don't want anything wiped off the phone. I'm trying to get past the lock screen, because I found this phone in the street, so I want to get the numbers in it to try and return it. I've heard you can bypass the lockscreen if it's rooted. It's a Samsung Galaxy S Mesmerize, (or Fascinate).
I successfully unlocked the bootloader on my xperia x8 via flashtool put on custom kernel nAa 14 and miniCM7 Yay.Everything is fine apart that I want to change network because they have much better deals etc.I went to the 3 network shop and tried to put in the Sim, it took it in loaded but wouldnt register with the network , in fact I tried last week when I was on stock kernel and gingerxperia and it asked for ''unlock code'', today it didn't ask for unlock code took it in but wont register.I guess there must be some sim lock or something.
Maybe it is unlocked but something to do with Radio pehaps nonetheless my current Network works fine.here's my S1 LOG if any good. after unlocking BL of course
Welcome to S1 identify tool 16/09/2012 17:16:15 16/09/2012 17:16:15 TO CONNECT NEXT PHONES [code]....
I recently rooted my Motorola Droid and I am trying to run Rom Manager by clockworkmod and when i attempt to Flash Clockworkmod Recovery I get an error saying, "An error occurred while attempting to run privileged commands!" Can someone offer me some help on what to do, I have tried uninstalling and turning the phone off.
[How-To] ROOT Your Nexus One without Unlocking the Bootloader. ALL ROM'S! - Google Nexus One Owners | Google Groups. Ok, I posted this on my Google Groups page where I was able to Tidy it up and update it easier. Sources credited and applied. I did this on 2 N1's. No wiping, no data loss, both T-Mobile with FRF91. No data loss, no wipes, no nothing. The only reason you will have to wipe or anything is if you want to put a custom recovery on it and a custom ROM.
I done a backup using Clorkwork Mod before I flashed a new ROM onto my phone. Now when i am trying to restore the backup onto the phone using CWM it completes the task but whenever I reboot the phone it gets passed the first samsung screen but hangs at the second SAMSUNG screen where the text is pulsing.
I have tried Wipe / Data factory reset, Wipe Cache, Wipe Dalvick and fix permissions. None of these seem to make any difference. The only thing that has worked in flashing a new ROM but I do not want to lose any of my apps /configs.
I'm on a Galaxy S2 running Gingerbread 2.3.4, my baseband version is I9100XXKI1 and my kernel version is 184.108.40.206-I9100XWKH4-CL487028root@DELL136 #2
Using Odin3 v1.85 and S2 Root. (Superoneclick kept freezing on me)
My aim is to install Cyanogenmod 7.1.
So far I started off by trying to flash it with XWKDD Insecure, which I believe is wrong? However after rooting it, I installed ClockworkMod Recovery, downloaded the ROM and tried installing it - which is where the problem started - I kept getting the error in recovery mode 'Invalid whole-file signature'.
It just wouldn't boot in to ClockworkMod Recovery.
So after some digging around I managed to find a file to flash to my device for the CWM Recovery mode, tried it, and it worked. However, I still couldn't install Cyanogenmod from my SDcard.
I tried it a few times, wiped/formatted a few times and ended up getting my device stuck in a bootloop.
So, I've managed to get it out of the boot loop, and started fresh...
I flashed it with XWKH4 Insecure, unrooted, rerooted etc. I've downloaded CWM again, downloaded the Cyanogenmod again, tried installing it, and once again it's gone back into Androids recovery and failed to install because of the 'whole-file signature' and failing to verify it.
I did post this in Q&A as well, however it doesn't seem to be as popular a forum as this one, I'm not really looking to wait for days for a response.
randomly yesterday my phone shut off and rebooted itself. Well, it became stuck on the Samsung boot screen. So I reset it again, and again, and again. Eventually I went into recovery mode and clicked the wipe data/factory reset button. Actually, at first I clicked the wipe cache button. So I rebooted it, and now everytime it boots it goes straight to recovery mode (Volume Up, Home, Power). So i began looking for solutions and decided it would be best to restore to a stock Rom. Well I downloaded one, and attempted to look for it in the internal SD card but all it said was "unable to mount sd". Did some more research, and found something called odin. I went into download mode and odin was able to recognize my device. Loaded up my stock rom (pda, .md5) and it would say this:
<ID:0/003> Added!! <OSM> Enter CS for MD5.. <OSM> Check MD5.. Do not unplug the cable.. <OSM> Please wait.. <OSM> KIES_HOME_I317UCAMA4_I317ATTAMA4_578342_REV04_user _low_ship.tar.md5 is valid. <OSM> Checking MD5 finished Sucessfully.. <OSM> Leave CS.. <ID:0/003> Odin v.3 engine (ID:3).. <ID:0/003> File analysis..
Not entirely sure why it stopped at recovery.img. I installed the Samsung Drivers from the website and still nothing. Uninstalled odin and went to an older one, still same message. Installed a newer one, still same message.
Galaxy 3:I5801 with firmware upgraded to 2.2 , was rooted already..I had been trying to upgrade to 2.3.7 with cyanogen 7.2..Clockwork mode recovery was not installed and instead in the normal recovery mode a zip file ,containing the files:META-INF,System and zimage, was renamed as "update.zip"
It did accept the zip and displayed "Welcome to android 2.3.7" but then was stuck displaying "I5801" logo.I am still able to enter the download mode (Vol - | power | home combo) and the "Forced upload by key pressing(vol + | power | home)". I tried usng ODIN to flash , it is flashing and displaying "pass" but no change in the phone .
I have a chinaphone and I'm trying to install a custom recovery so I can make/restore backups if anything messes up the phone, but it hasn't got an official clockwork mod recovery.
I've read that you can build a custom recovery using the ClockworkMod Builder website with the original recovery img extracted from the device,I tried using this method to extract the recovery: http:[url]....
Then I used an App called Online Nandroid Backup which has successfully created a recovery img for me, I ran it through the ClockworkMod Builder website but it says no changes were made.
I accidentally flashed the wrong recovery onto my LG Optimus V. The phone is stuck in a boot loop and I am unable to make a selection in recovery. How can I flash the correct version of clockwork mod without doing it through the phone?
i have a velocity micro cruze t510 running eken a90 firmware nicely but i cant get cwm recovery to work i have flashed 3 different versions and all three have the same problem. emmc will not mount so im unable to back up. find a custom recovery for the t510
I make root at one LG e510, after I put Rom manager and install custom recovery clockworkmod recovery. Everything fine till here, but after try to acces recovery, spears only stock recovery and not custom recovery.
When i first got this phone a few months ago i did something stupid. I flashed the wrong cwm recovery with rom manager even though its not supported on my phone. I keep trying to flash a different recovery using the terminal emulator, but to no Avail. Still cant boot into recovery.