Related
I was trying to flash a new kernel, and so i wiped the 2 caches and now im stuck on the Clockwork Recovery Screen. I try rebooting, and all it does is just go back to the Recovery screen. Please help, i want to use my nook color again.
Do you have previously created backup on your SD card ?
If so just restore.
Unfortunatly, i didnt. I just got it a couple days ago and am brand new to all these mods.
me too
This just happened to me as well. I even had a backup image and restored, but it would still loop. I used the following zip which removes clockwork recovery (thanks to the OP that originally posted this) and it then it worked.
Give it a shot
OMG, I LOVE YOU! No really, thank you so much!!! It works perfect!
Your welcome...........
Solidsnake726 said:
OMG, I LOVE YOU! No really, thank you so much!!! It works perfect!
Click to expand...
Click to collapse
I think this is beginning of beautiful relationship
Some additional info that may be relevant or not...
Some users have reported that after clearing the dalvik cache in CWR (as part of the process to flash a custom kernel), the screen locks up and they are unable to return to the main recovery screen.
This was resolved by 1) hook up your nook to the wall charger, 2) hold the power button which will force a reboot, 3) after your nook reboots to its normal screen, restart the kernel flash procedure from the beginning, 4) after you clear the dalvik cache, do not touch anything for at least 30 seconds
After step 4, CWR usually doesn't lock up and you should be able to navigate back to the main recovery screen to finish the kernel flash process. For some reason or another, the nook just needs a little time after clearing the dalvik cache before you can press any buttons.
yan2000kee said:
This just happened to me as well. I even had a backup image and restored, but it would still loop. I used the following zip which removes clockwork recovery (thanks to the OP that originally posted this) and it then it worked.
Give it a shot
Click to expand...
Click to collapse
I have had the same issue as the OP using ROM Manager to install 3.0.0.5 on 1.1.0 using Auto-Nooter 3.0.0. I was able to use the quoted method to break out (for the record I did so before reading this post ). However, I ran into the problem again after a full reroot and am still looking for a permanent solution to the problem.
yan2000kee said:
This just happened to me as well. I even had a backup image and restored, but it would still loop. I used the following zip which removes clockwork recovery (thanks to the OP that originally posted this) and it then it worked.
Give it a shot
Click to expand...
Click to collapse
Sorry for being a noob but what do I do with this file? Just put it on root and run it in CWR?
Moorfrost said:
Sorry for being a noob but what do I do with this file? Just put it on root and run it in CWR?
Click to expand...
Click to collapse
Yes. Boot into CWR and select the zip file from the SD card and flash.
eyecrispy said:
Yes. Boot into CWR and select the zip file from the SD card and flash.
Click to expand...
Click to collapse
Thanx a million, worked like a charm.
Thanks... But one other question...
Thanks for this got me out of the CWR bootloop, but now I'm stuck on the android splash screen.
UPDATE: Just tried to start all over and now it got me a bit further, but to a black screen with a white banner up top that says "Android System"...
Another noob question, sorry. Will this also restore the stock BN recovery? Regardless, thanks.
lekofraggle said:
Another noob question, sorry. Will this also restore the stock BN recovery? Regardless, thanks.
Click to expand...
Click to collapse
yes it does , just did it my self
Lifesaver! Thanks!
Maybe this should be linked to original thread.. So that things are made clear..
Sent from my HTC Desire using XDA App
Sorry to bump this thread, but OP's issue of being stuck in CWR happens to me every time I try to install the overclock kernel on my Eclair nook.
Any advice on what I can do to successfully overclock?
Anoxymoron said:
Sorry to bump this thread, but OP's issue of being stuck in CWR happens to me every time I try to install the overclock kernel on my Eclair nook.
Any advice on what I can do to successfully overclock?
Click to expand...
Click to collapse
I found a work around. Open cwr..flash recovery, exit recovery, reboot from quick boot . Once rebooted go back to cwr flash recovery, reboot into recovery, clear cache flash zip..reboot. This has worked numerous times for me.
bratliff said:
I found a work around. Open cwr..flash recovery, exit recovery, reboot from quick boot . Once rebooted go back to cwr flash recovery, reboot into recovery, clear cache flash zip..reboot. This has worked numerous times for me.
Click to expand...
Click to collapse
This is assuming that CWR is on internal memory.. if you are booting CWR from SD.. you need to take out the SD card then boot up.
Howdy y'all!
I just compiled a proper version of ClockworkMod recovery 5.5.0.4 off of the ICS branch of CyanogenMod.
It supports backing up boot images (I have heard that the image that is being flashed now doesn't support backing that up), and in the near future will support recovery chargemode.
This repository will hopefully contain in the near future a semi-working copy of CyanogenMod 9 also, but there's no guarantees on that one
So, without further ado:
What is this?
This is ClockworkMod Recovery 5.5.0.4 and the files necessary to build it yourself.
Click to expand...
Click to collapse
How do I use it?
You must first be unlocked with HTCDev.com (there is an excellent guide over there, just click on the Unlock Bootloader button and it'll walk you through)
Once you're unlocked, download the prebuilt image below, and do the following (in the same directory you used to unlock your phone):
Code:
fastboot flash recovery <path/to/prebuilt-image-you-downloaded.img>
You need to replace the stuff in brackets with the path to the img file you downloaded from here...
Alternate Installation Method (ph39img)
Much easier installation once unlocked with HTCDev...
Simply download the ph39img.zip I have linked to in the downloads section, and put it on your external SD card.
Reboot your phone into HBOOT, and allow the update. Then you've got clockwork installed super easy, no computer needed!
Click to expand...
Click to collapse
How is this different from the ClockworkMod image that's floating around here?
Truth be told, I haven't tried the other version yet-- but I have been told that it doesn't back up boot.img, and has a few other bugs.
Also, this version has /sdcard mapped to the external SD card as opposed to the internal SD card. This is a safety feature to prevent losing backups in case your device becomes inaccessible. All backups should be to an external storage medium (even on your desktop, it's a good practice to not backup your hdd to the same device )
I'm sure mine has bugs too, but I'm posting the source so y'all can laugh at me
Click to expand...
Click to collapse
The Goods: Where do I get it? -- Downloads:
recovery-beta2.img - https://github.com/downloads/thecubed/android_device_htc_holiday/recovery-beta2.img
Alternate installation method: ph39img.zip : https://github.com/downloads/thecubed/android_device_htc_holiday/PH39IMG-chargemode.zip
New! PH39IMG.zip for users with ICS OTA: http://goo-inside.me/private/iomonster/htcvivid/recovery/ph39img/hboot-1.85/PH39IMG.zip
Click to expand...
Click to collapse
recovery-take1.img - https://github.com/downloads/thecubed/android_device_htc_holiday/recovery-take1.img
Alternate installation method: ph39img.zip : https://github.com/downloads/thecubed/android_device_htc_holiday/PH39IMG.zip
Click to expand...
Click to collapse
The GitHub source is here:
https://github.com/thecubed/android_device_htc_holiday
Click to expand...
Click to collapse
Please don't mirror the files (hotlinking is okay!), just incase I need to take them down or quickly update them. Thanks!
Click to expand...
Click to collapse
Changelog
recovery-take1 : initial release
recovery-beta2 : now supporting charge mode in all forms just like stock recovery, and a few behind-the-scenes tweaks
Click to expand...
Click to collapse
Tips and Tricks (what works, and what doesn't)
Please read the following-- the HTCDev unlock comes with it's own disadvantages and risks...
The HTCDev unlock adds the word "**UNLOCKED**" to your HBOOT screen. Even if you put your phone to stock with a RUU and re-lock the phone, your phone will show "**RELOCKED**" when booted to the bootloader.
At this time, I am unsure if AT&T will refuse warranty claims if they see that text. Just remember: if you unlock, there may not be any way back to complete stock any time soon.
Another disadvantage of the HTCDev unlock: ClockworkMod recovery CANNOT flash kernels. You must use JoeyKrim's kernel flasher ( http://forum.xda-developers.com/showthread.php?p=20926830 )or fastboot to flash kernels. This includes Nandroid backups.
If you back up your phone and apply a new ROM and kernel, you will have to fastboot flash the old boot.img back or use JoeyKrim's kernel flasher before switching ROMs.
If you flash a ROM, make sure to read the instructions with the ROM. Every ROM developer has a different method of flashing the kernel-- some come with a script to run, and others just give you the files to flash. Please read what they have to say before posting here with a complaint
Not seeing your rom .zips on your SD card, or having trouble restoring a backup?
This version of ClockworkMod has the external SD card set as primary. This is to avoid the problem of "my phone died, and I can't access my backups".
To solve this issue, simply put your ROMs or whatnot on your external SD card. In the future, I may look into how hard it is to add a internal/external SD switcher to clockwork, but for now the safest default is the external SD.
Sorry about that!
Some rom.zip's don't work...
This may be because they're using an old version of the update-binary in their .zip file. Contact your ROM maintainer and ask for an updated version
If you are a ROM developer, here's the updated "update-binary". Drop it in your META-INF/com/google/android directory in your ZIP and update your format() commands properly...
update-binary.bin (rename to update-binary) - http://legacyschool.us.to/htcvivid/update-binary.bin
Click to expand...
Click to collapse
HELP! I CANT GET INTO RECOVERY! *new!
If you find yourself unable to get into CWM (i.e. the screen flashes some text, then reboots immediately), just boot to fastboot (hboot -> fastboot), then issue "fastboot erase cache" on your PC.
Then you should be able to boot into ClockworkMod. After you're in there, make sure to format /cache to fix the problem.
This issue will be fixed soon, I'll add some intelligence to the kernel to not bother rebooting to fsck a partition if it's marked 'dirty' or unmountable. Stock recovery is supposed to fsck the partitions if they're dirty/broken, but CWM doesn't bother, and the kernel gets easily confused.
Click to expand...
Click to collapse
How can I contact (chastise, praise, call names) you?
On IRC (Freenode) you'll find me hanging out in #htc-holiday when I'm available.
Just say my name "IOMonster" (or "IOMonster_desk") and if I'm around I'll answer.
I also will sometimes respond to PM's on XDA, but XDA's forum has a bad habbit of not emailing me when I get a new PM...
Click to expand...
Click to collapse
Standard "it might not work" clause
This software hasn't been thoroughly tested, and it might not work.
It might not backup things correctly, and it might not restore them right.
Please don't trust this software with anything sensitive or life-alteringly important.
I'd hate to say "I told you so!"
That's not to say this software doesn't work, it's just the standard disclaimer.
Click to expand...
Click to collapse
Donation Information
I love to develop. I don't do this for money, I do it just for the "thanks".
Please don't feel obligated to donate, but if you feel like it, you can click the button below to donate a small amount to me. Alternatively, consider donating to a charity of your choice-- there are so many good causes out there that could use your donation.
Thank you in advance!
Click to expand...
Click to collapse
Credits / Thank You's
IanWizard-cloud (testing, moral support )
Pirateghost (much needed debugging, testing, and flashing his phone no less than 20 times!)
joeykrim
toastcfh
fattire
BananaCakes (for getting clockwork built in the first place and enabling so many mods on day 1 of unlock!)
..and lots of others!
Click to expand...
Click to collapse
Thanks for giving this looong post a read!
Good luck!
Shoot I'll give it a shot. Flashing now. Will edit this post after its been tested.
Edit: Short glance review, I know a lot of this is already stated/known but just posting it anyways
So firstly, I'm still getting no confirmation when I flash images (whether it be recovery or kernal) but again, I think thats from me using a VM to do all the work.
Still boots into recovery when plugged in.
Maybe I'm just being an idoit, but I couldn't get out of the keytest, had to hold power button which booted the rom.
Of course the usb mount and such works.
Will try backup later when I'm not short on downtime.
already flashed... beautiful. will run through some tests tonight. and dont think you are getting rid of me on IRC now
Coming from the HTC EVO 3D land with the HTC unlock method for the last 6 months .. the following tips have been very helpful.
HTC Unlock method only allows kernel write access while in two modes, fastboot and standard android mode. HTC unlock method does NOT allow a kernel to be flashed from standard recovery mode. This includes a ROM .zip with a kernel inside. The ROM will load, but the kernel will not from standard recovery mode.
The ONLY way to flash a kernel whether by performing a full nandroid restore including the kernel or flashing a ROM with a kernel inside, is to use the following command to load the custom recovery:
fastboot boot <destination of recovery.img>
example on windows: fastboot boot c:\downloads\cwm-recovery.img
Everything else will work in the standard custom recovery mode EXCEPT the ability to flash a kernel. To flash a kernel through the custom recovery, fastboot mode must be used per HTC's unlock method.
Updated OP with simpler installation method (ph39img).
Much easier to use, and no mucking around in commandline!
well it most definetly worked. i jus downloaded the zip file and was able to back up my settings. Only problem i have is. ( which is a similiar problem i had before this. if i powered off the phone and plug it to charge it would automatically restart the phone.) When i power off now and plug it in to charge. It automatically goes to the clockworkmod set up. none the less my phone works and i have backed it up. But i still was wondering wat could cause these problems ?
Same issue here can't charge while off,
I not sure boot backups are working,
Was stock did back up, flashed RR betas and then restore to saved image, got bootloop, had flash boot thru fastboot
Sent from my HTC PH39100 using xda premium
Great start for this....from what i was told theres drivers needed in the recovery for it to charge while device is off and fastboot is unchecked...device charges while fastboot is checked and device is off....
WC
Recovery works great for me.
BTW, the offline charge issue is usually in the chargemon file.
for the new recovery, we will need to be using a new update-binary and when flashing a rom, your updater-script must contain 4 arguments in the format line, like this:
Code:
format("ext4", "EMMC", "/dev/block/mmcblk0p29", "0");
inside the attached zip you will find the update-binary
if you dont know what update-binary and updater-script is, then this isnt for you and you needn't concern yourself with it.
Just put your new recovery in the superguide and gave you credit. Keep up the good work!
There seems to be some issues pertaining to this CWM and flashing Telstra_boot image and attempting to install Run Runner ROM.
After flashing boot.img and attempting to wipe and isntall the rom i got an aborted error 1. After rebooting back into recov i was stuck at the HTC boot screen
The only way i could get back and working was relocking and flashing the RUU
Drew
drewdatrip said:
There seems to be some issues pertaining to this CWM and flashing Telstra_boot image and attempting to install Run Runner ROM.
After flashing boot.img and attempting to wipe and isntall the rom i got an aborted error 1. After rebooting back into recov i was stuck at the HTC boot screen
The only way i could get back and working was relocking and flashing the RUU
Drew
Click to expand...
Click to collapse
Did you not download the fix I provided in the Rom thread? This recovery works fine with the updated binary.
Sent from my HTC PH39100
Pirateghost said:
Did you not download the fix I provided in the Rom thread? This recovery works fine with the updated binary.
Sent from my HTC PH39100
Click to expand...
Click to collapse
I did notice your fix but i was already about half way through the "long way"
Needless to see im using the slightly older version of CWM and now on RR10
Drew
drewdatrip said:
I did notice your fix but i was already about half way through the "long way"
Needless to see im using the slightly older version of CWM and now on RR10
Drew
Click to expand...
Click to collapse
At that point it was too late for.the fix. It does work now though.
Sent from my HTC PH39100
Question has the flash able zip been updated so it will now work to flash rooms or is it the rom zip scripts that needed updating? Can I place this zip on my SD card and overwrite the old version ( if that's what was in fact wrong)
Sent from my HTC PH39100 using Tapatalk
I have a raider from rogers and tried putting the PH39IMG zip on my htc sd drive and get an error about wrong img (or something to that effect).
So is this for the at&t vivid only?
as I still have cwm from the original raider thread for rogers, bell, fido from here.
and this appears to be updated and backing up to the ext-sd, which is much better.
hackit said:
I have a raider from rogers and tried putting the PH39IMG zip on my htc sd drive and get an error about wrong img (or something to that effect).
So is this for the at&t vivid only?
as I still have cwm from the original raider thread for rogers, bell, fido from here.
and this appears to be updated and backing up to the ext-sd, which is much better.
Click to expand...
Click to collapse
no, just fastboot flash the new recovery img. the PH39 method isnt working right now for some reason.
Thanks will try now.
Pirateghost said:
no, just fastboot flash the new recovery img. the PH39 method isnt working right now for some reason.
Click to expand...
Click to collapse
---------- Post added at 09:01 PM ---------- Previous post was at 08:29 PM ----------
Worked like a charm, just finished my first nandroid backup as well.
off we go to start testing out a rom.....
wooo hoooo!
Pirateghost said:
no, just fastboot flash the new recovery img. the PH39 method isnt working right now for some reason.
Click to expand...
Click to collapse
ok i have a question, after using the phone for a full day know (still stock).
I have noticed I'm unable to keep my connection to rogers for data only.
I have checked and the apn is right.
I have cleared dalvic cache and fixed permissions.
Still when im away from wifi and using data, most of the time i have no connection.
Now before i updated to this version of cwm i had no issue's with my data connection.
anyone else having an issue with a raider on rogers?
Thanks
Hey, I bring to you the first Clockworkmod Recovery or commonly known as CWM for your N5100 and N5110. Giving your device the ability to flash your favourite custom ROMs, Kernels, Mods. *Now known as Advanced CWM or aCWM. Thankyou to 'xperiacle' and 'GSLEON3' for giving me the stock recoveries and kernels for N5100/10, so I could start off with my work.
Works perfectly now. OP will only be updated with stable releases, everything else will be floating around the thread.
I have provided the stock recovery if you encounter any issues, you can always flash back.
Featues:
Most things you would expect from stock CWM
EFS backup / restore
Removed option to: report error / show log / testkeys
More to come...
Downloads:
Use this if you are having problems with your SDCard. (Mount / Backup / Restore)
N5100 / N5110
Stable Release #1: ODIN | ZIP
Stock Recovery: http://d-h.st/tHx
N5120
Stable Release #1: ODIN
Stock Recovery: http://d-h.st/51H
Changelog:
Code:
[I][U]Stable Release #1[/U][/I]
Added reboot menu (rom, download, recovery)
Advanced CWM = aCWM
Code:
[I][U]Experimental #6[/U][/I]
Working EFS backup / restore under 'advanced' tab
Removed keytest / report error / show log options
Custom recovery, no more to be called 'stock' CWM, more device specific features to be added
N5120 support
Fix permissions now directed to /sdcard/.android_secure
Cleaned up some code for flashing zips
[I][U]Experimental #5[/U][/I]
[COLOR="Red"]REMOVED DUE TO ISSUES[/COLOR]
Touch recovery (reimplemented)
Universal for 5100 / 5110
Fixed up some mount lengths
Fixed up init.rc
[I][U]Experimental #4[/U][/I]
Display issues fixed
[I][U]Experimental #3[/U][/I]
Built again with fresh tree - n5110
(info: skipped for n5100)
[I][U]Experimental #2[/U][/I]
Touch Input excluded (temp)
kernel built from source with dancing cwm patch
[I][U]Experimental #1[/U][/I]
Public release
emwno said:
Hey, I bring to you, Clockworkmod Recovery or commonly known as CWM for your n5100. Giving your device the ability to flash your favourite custom ROMs, Kernels, Mods in the future. Thankyou to 'xperiacle' for giving me the stock recovery and boot.img. Flash with Odin
This has not been tested by me and is still experimental. I hold no responsibility for any
problems caused. YOU! Are trying this at your own risk. Don't blame me that I wasted your $$$.
Put a scare in you didn't I?
I have provided the stock recovery if you encounter any issues, you can always flash back.
Downloads:
CWM Recovery: http://d-h.st/rDv
Stock Recovery: http://d-h.st/tHx
Changelog:
Code:
[I][U]Release #1[/U][/I]
Public release
Click to expand...
Click to collapse
Thanks now we need one for the N5110.
rfb813 said:
Thanks now we need one for the N5110.
Click to expand...
Click to collapse
Just need to check if this works properly. If yes, then n5110 is up next
emwno said:
Just need to check if this works properly. If yes, then n5110 is up next
Click to expand...
Click to collapse
Thanks!
Thanks man, that was fast work
Sent from my GT-N5110 using Tapatalk HD
Southrice said:
Thanks man, that was fast work
Sent from my GT-N5110 using Tapatalk HD
Click to expand...
Click to collapse
Nothing to be credited for, until the device boots to CWM
How do you flash this custom recovery with ODIN?, what version?, thanks
I flash the file 2 times and it said pass but when reboot to recovery is stock so I don't know what went wrong
Speedy Gonzalez said:
I flash the file 2 times and it said pass but when reboot to recovery is stock so I don't know what went wrong
Click to expand...
Click to collapse
How did you flash, Odin?
brosenz said:
How did you flash, Odin?
Click to expand...
Click to collapse
I added the zip to the pda area and flash Odin v3.07
I installed the image with ADB.
put the recovery image on the sdcard mount or ext sdcard mount
ADB to the note 8.0
su to root
go to your image directory
dd if=xxx.img of=/dev/block/mmcblk0p6
switch back to the note and reboot directly to recovery (i used goomanager)
it does boot the first time - but it is jittery and in landscape mode.
after the first system boot- the device wipes it and goes back to stock recovery.
I have seen this with other stock android devices- sometimes there
is a script that gets triggered on boot to remove any custom recoveries.
I did clear the recovery check from CWM - but it was hard to see because of the
landscape mode and the screen jumping around.
It looks like the full backup is working- now I wonder what ROM will be close enough
to the 8.0 to try flashing.
Speedy Gonzalez said:
I added the zip to the pda area and flash Odin v3.07
Click to expand...
Click to collapse
Any idea why it didn't flash with Odin?
@xbill9
Code:
adb pull /tmp/recovery.log
for fixes
Speedy Gonzalez said:
I flash the file 2 times and it said pass but when reboot to recovery is stock so I don't know what went wrong
Click to expand...
Click to collapse
Found this Q&A in the Note 10.1 rooting guide in RootGalaxyNote.com:
Q: I don’t see ClockworkMod Recovery when I enter recovery, I see stock Android recovery.
A: With newer software updates, you may be encountering this error because it will overwrite ClockworkMod Recovery upon reboot. To get around this, simply boot into ClockworkMod Recovery right after flashing in ODIN. You can set auto-reboot off in ODIN then when done, just hold down Power and Volume Down straight to bootloader menu.
This may have been the problem.
To get it to stop resetting to stock recovery every time you reboot, under /system, there is a file named "recovery-from-boot.p". Rename it to .bak or whatever. That file is typically the culprit for custom recoveries not 'sticking'.
Also, we don't have a factory image yet, do we? I'm hesitant to mess too much with this stuff until we have a way to Odin ourselves out of a softbrick.
---------- Post added at 11:45 PM ---------- Previous post was at 11:42 PM ----------
Also, to the OP, thanks for doing this. I'm pretty familiar with adb if you'd like to do TWRP. Would love to have it instead of CWM!
rfb813 said:
Q: I don’t see ClockworkMod Recovery when I enter recovery, I see stock Android recovery.
A: With newer software updates, you may be encountering this error because it will overwrite ClockworkMod Recovery upon reboot. To get around this, simply boot into ClockworkMod Recovery right after flashing in ODIN. You can set auto-reboot off in ODIN then when done, just hold down Power and Volume Down straight to bootloader menu.
Click to expand...
Click to collapse
Those having issues, try that ^^^
jntdroid said:
To get it to stop resetting to stock recovery every time you reboot, under /system, there is a file named "recovery-from-boot.p". Rename it to .bak or whatever. That file is typically the culprit for custom recoveries not 'sticking'.
Also, to the OP, thanks for doing this. I'm pretty familiar with adb if you'd like to do TWRP. Would love to have it instead of CWM!
Click to expand...
Click to collapse
Yeah, But i'd like to keep, just incase something goes insanely wrong. The stock recovery.img is provided, you can always flash back it something goes wrong. And i am readying up TWRP, may need you to pull some logs if it doesnt boot
jntdroid said:
To get it to stop resetting to stock recovery every time you reboot, under /system, there is a file named "recovery-from-boot.p". Rename it to .bak or whatever. That file is typically the culprit for custom recoveries not 'sticking'.
Also, we don't have a factory image yet, do we? I'm hesitant to mess too much with this stuff until we have a way to Odin ourselves out of a softbrick.
---------- Post added at 11:45 PM ---------- Previous post was at 11:42 PM ----------
Also, to the OP, thanks for doing this. I'm pretty familiar with adb if you'd like to do TWRP. Would love to have it instead of CWM!
Click to expand...
Click to collapse
http://samsung-updates.com/device/?id=GT-N5100
http://samsung-updates.com/device/?id=GT-N5110
I will be releasing a full Note 8.0 Toolkit today or tomorrow with support to rename the stock recovery restore files so that custom recovery isnt overwritten after flashing. If anyone wants to help test please email me at [email protected]
Mark.
Attached is a tar of recovery.log pulled with ADB while booted to CWM.
The display goes to landscape on boot - and the fonts seem extra large.
When the vol up/down navigates the screen jumps and you can't see the
highlighted option.
It is usable with trial and error if you know the order of the CWM menus and
use the vol up/down and power to navigate.
emwno said:
@xbill9
Code:
adb pull /tmp/recovery.log
for fixes
Click to expand...
Click to collapse
Only thing I can judge by that are the missing mount types for the recovery.fstab. Ill fix that now. But someone, try keeping the device physically portrait and see if cwm works properly then, if not then physically landscape.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
P.S try using touch input, its a touch recovery, or so I built it
^thats why fonts are large
^thats why there are no indicators
I tried changing orientation before boot - it always goes to landscape.
I attached 2 images - one is the display after the first CWM boot.
The second is after pressing Vol Up to navigate to the 2nd menu option.
I have seen jumpy CWM presentation like this on some smaller screens like the
Sony Xperia 2011/2012 phones.
emwno said:
Only thing I can judge by that are the missing mount types for the recovery.fstab. Ill fix that now. But someone, try keeping the device physically portrait and see if cwm works properly then, if not then physically landscape.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
P.S try using touch input, its a touch recovery, or so I built it
^thats why fonts are large
^thats why there are no indicators
Click to expand...
Click to collapse
I have created Loki-enabled images for ClockworkMod Recovery and Touch Recovery.
Links to the images:
http://www.androidfilehost.com/?a=show&w=files&flid=8961
recovery-clockwork-6.0.4.4-vs980.lok
http://www.androidfilehost.com/?fid=23196940996968932
recovery-clockwork-6.0.4.4-vs980.lok.img
http://www.androidfilehost.com/?fid=23196940996968933
recovery-clockwork-touch-6.0.4.4-vs980.lok
http://www.androidfilehost.com/?fid=23196940996968931
recovery-clockwork-touch-6.0.4.4-vs980.lok.img
http://www.androidfilehost.com/?fid=23196940996968934
There is one set of images for CWM recovery and one for CWM Touch recovery. The loki images were created from the CWM images on clockworkmod.com using loki_flash.
Files ending in *.lok.img are identical (binary-same) to the corresponding *.lok files. Use these if using Flashify, since it doesn't allow flashing of files ending in *.lok. Or, just rename the *.lok files to *.img. Your choice.
These images should be flashed using the loki_flash method detailed here (use option 1):
http://forum.xda-developers.com/showthread.php?t=2449670
Just replace the name of the file specified in those instructions with the *.lok file you downloaded from the link above.
Or, as stated above, you can use Flashify.
Don't try to set up a custom CWM (or TWRP) recovery image from within CWM ROM Manager - you will end up with a non-working recovery mode. This is how I stumbled upon this issue and why I created the above loki images. If you are in a broken recovery state, just use the above images to get back to a working recovery state.
*** THESE IMAGES ARE ONLY VALID FOR THE VERIZON LG G2 VARIANT [vs980]! DON'T FLASH THEM ON ANY OTHER DEVICES ***
How is the cache wipe on this? Does it takee a long time (5-10 min) like TWRP? Thanks for the development
BriVG said:
How is the cache wipe on this? Does it takee a long time (5-10 min) like TWRP? Thanks for the development
Click to expand...
Click to collapse
There are instructions on how to make twrp do wipes faster in the 3rd post of the Cleanrom thread. It wipes everything in only a few seconds. Been using this method for a couple of weeks with no problems.
Cache wipe took 13 minutes... Just cache
Sent from my VS980 4G using Tapatalk
Originally Posted by BriVG
How is the cache wipe on this? Does it takee a long time (5-10 min) like TWRP? Thanks for the development
Click to expand...
Click to collapse
There are instructions on how to make twrp do wipes faster in the 3rd post of the Cleanrom thread. It wipes everything in only a few seconds. Been using this method for a couple of weeks with no problems.
Click to expand...
Click to collapse
Not sure this answered his question.
Thanks Devs. From my VZW G2.
trickster2369 said:
Not sure this answered his question.
Thanks Devs. From my VZW G2.
Click to expand...
Click to collapse
Just curoius is CWM has any benefits or downsides compared to TWRP?
Thank you
Evilmonstertruck said:
Just curoius is CWM has any benefits or downsides compared to TWRP?
Thank you
Click to expand...
Click to collapse
I havent run CWM yet on my g2 but thats all I ran in the past and it's really just personal preference. TWRP does have a bit more options and features and can be themed whereas CWM is pretty simple and plain. I think I like CWM a bit more though just because the layout is a bit nicer imo.
Evilmonstertruck said:
Just curoius is CWM has any benefits or downsides compared to TWRP?
Thank you
Click to expand...
Click to collapse
I've never used CWM touch, so I can't speak to that. I used CWM on my Incredible and Rezound, and they do the same things. The first time I used TWRP was on my Nexus 10, because CWM wasn't available as an option. Probably the biggest difference is the UI. TWRP can be themed also. Kind of like getting a new pair of shoes. The old ones are worn in and comfortable, and your used to them. The new ones look nice and clean, and work pretty much the same, but eventually grow on you. That's where I am with TWRP.
Thanks Devs. From my VZW G2.
I was curious about the wipe because I've heard that the - rm option was not wiping sufficiently for some people...
Just installed it and ran a backup. Seems to backup quicker than TWRP.
:good:
Because i'm not lazy
Here's the TWRP tip for faster wipes.
The Fix
locoface said:
Because i'm not lazy
Here's the TWRP tip for faster wipes.
The Fix
Click to expand...
Click to collapse
Yeah it's very fast but I've read in other posts of different forums that some people reported that this method left artifacts that possibly messed with subsequent flashes
any direct instructions for us noobs to adb on how to do this from just root with stock recovery?
HOWTO:install custom recovery with root and stock recovery
1) Download and install LG G2 Windows USB Driver, if you haven't already.
2) Download and install Flashify from the Google Play Store.
3) Download CWM Recovery or CWM Touch Recovery image file (*.img, not *.lok files). Either one - your choice.
4) Connect your phone to your PC via USB using Media sync (MTP) option.
5) Copy the appropriate *.img file, downloaded in step 3, to a location on your phone's SD card
6) Using Flashify, select Flash -> Recovery Image, and browse to the location on your phone's SD card where you copied the *.img file in step 5.
7) Select the file, and choose "Yup!"
Enjoy CWM Recovery goodness.
Viper76269 said:
any direct instructions for us noobs to adb on how to do this from just root with stock recovery?
Click to expand...
Click to collapse
kaczmar2 said:
1) Download and install LG G2 Windows USB Driver, if you haven't already.
2) Download and install Flashify from the Google Play Store.
3) Download CWM Recovery or CWM Touch Recovery image file (*.img, not *.lok files). Either one - your choice.
4) Connect your phone to your PC via USB using Media sync (MTP) option.
5) Copy the appropriate *.img file, downloaded in step 3, to a location on your phone's SD card
6) Using Flashify, select Flash -> Recovery Image, and browse to the location on your phone's SD card where you copied the *.img file in step 5.
7) Select the file, and choose "Yup!"
Enjoy CWM Recovery goodness.
Click to expand...
Click to collapse
Can't we just install CWM from Rom manager?
Unless the image available from within ROM manager has been updated, NO. You will end up with a broken recovery image. That is why I made the images above. I did this exact thing myself and that is how I found the issue and made these images.
The images on clockworkmod.com and in ROM manager didn't work for me until I created Loki versions.
However, you are welcome to try to see what results you get. If you boot into recovery and get an error, you can just flashify the images above to get back a working recovery.
Sent from my VS980 4G using Tapatalk
kaczmar2 said:
Unless the image available from within ROM manager has been updated, NO. You will end up with a broken recovery image. That is why I made the images above. I did this exact thing myself and that is how I found the issue and made these images.
The images on clockworkmod.com and in ROM manager didn't work for me until I created Loki versions.
However, you are welcome to try to see what results you get. If you boot into recovery and get an error, you can just flashify the images above to get back a working recovery.
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
Oh ok, i went ahead and did yours instead of Rom Manger before your reply anyway lol, works great. One big question though. what the heck is Loki in the phone world? I spent 2 years with galaxy nexus, rooting, zipping etc etc and never stumbled upon Loki stuff.
litobirdy said:
Oh ok, i went ahead and did yours instead of Rom Manger before your reply anyway lol, works great. One big question though. what the heck is Loki in the phone world? I spent 2 years with galaxy nexus, rooting, zipping etc etc and never stumbled upon Loki stuff.
Click to expand...
Click to collapse
same here, but to my understanding, Loki is a way to bypass the bootloader, or tricking the phone to thinking the bootloader is unlocked.
---------- Post added at 11:10 PM ---------- Previous post was at 10:42 PM ----------
i was looking for my buddy's phone on AT&T, and it says you have to be on TWRP in order to install there. is that the same for this? or can i use flashify and flash CWM while i have a stock recovery?
The LG G2 (and other devices, like the Samsung Galaxy S4) on Verizon and AT&T used locked bootloaders. These same devices on other carriers (T-Mobile, etc.) include an unlocked bootloader, which allows users to flash custom kernels and make other modifications to the software on their own devices, AT&T and Verizon branded devices ship with a locked bootloader that prevents these types of modifications.
Loki is effectively an exploit that fools the locked bootloader into loading an unsigned, modified (loki-fied) image. You can read more about how it works here and here, if you wish.
You can use Flashify and and flash CWM while you have a stock recovery if you use the images I posted and follow the instructions in a post above. My understanding is that the AT&T variant of the G2 has a locked bootloader, so these same instructions would apply to that device, I would assume. If you want to use TWRP instead of CWM, there is a Loki-enabled image of that floating around the XDA forums; you can use Flashify and flash TWRP if you wish.
Viper76269 said:
same here, but to my understanding, Loki is a way to bypass the bootloader, or tricking the phone to thinking the bootloader is unlocked.
---------- Post added at 11:10 PM ---------- Previous post was at 10:42 PM ----------
i was looking for my buddy's phone on AT&T, and it says you have to be on TWRP in order to install there. is that the same for this? or can i use flashify and flash CWM while i have a stock recovery?
Click to expand...
Click to collapse
anyone get a white screen asking you for a code to put in after hitting reboot system from CWM recovery? i just shut the phone off and back on and it was ok, but i'm just wondering if it was a fluke
OK. So I soft bricked my phone earlier, and just restored by flashing the RUU. Now that I'm trying to root back, I'm noticing that my file system is totally different from what it used to be. TWRP actually says no OS is installed, but the stock version of 4.4.2 is most certainly there and boots just fine. How can I rectify this?
UPDATED: There was actually no problem with the file system. It appears I likely had a bad download of TWRP so it wasn't recognizing the mount points.
MarkBell said:
OK. So I soft bricked my phone earlier, and just restored by flashing the RUU. Now that I'm trying to root back, I'm noticing that my file system is totally different from what it used to be. TWRP actually says no OS is installed, but the stock version of 4.4.2 is most certainly there and boots just fine. How can I rectify this?
Click to expand...
Click to collapse
What version of TWRP do you have installed? 2.7.1.1 wipes OS version from bootloader, but that doesn't affect anything. If you want OS to be shown flash TWRP 2.6.3.3. It's the most stable recovery and you won't have problems flashing ROMs with it. On the other hand, if your phone works fine, leave it as it is
Powered by non removable 2300 mAh battery
donkeykong1 said:
What version of TWRP do you have installed? 2.7.1.1 wipes OS version from bootloader, but that doesn't affect anything. If you want OS to be shown flash TWRP 2.6.3.3. It's the most stable recovery and you won't have problems flashing ROMs with it. On the other hand, if your phone works fine, leave it as it is
Powered by non removable 2300 mAh battery
Click to expand...
Click to collapse
It was actually tdhite's 2.7.1.3 that I flashed that really screwed up my phone.
I was using 2.7.1.1 fine before. I flashed back to 2.7.1.1 after getting my phone working again with the RUU. I have a full backup of my rooted phone saved to my computer and would love to be able to restore it back through TWRP. But the actual filing system in ES File Explorer looks different.
In TWRP, I can't even get to SuperSU to become root because of the way the file system is so different.
When I was soft bricked, I may have played around in the Mount function of TWRP and screwed it up that way.
MarkBell said:
It was actually tdhite's 2.7.1.3 that I flashed that really screwed up my phone.
I was using 2.7.1.1 fine before. I flashed back to 2.7.1.1 after getting my phone working again with the RUU. I have a full backup of my rooted phone saved to my computer and would love to be able to restore it back through TWRP. But the actual filing system in ES File Explorer looks different.
In TWRP, I can't even get to SuperSU to become root because of the way the file system is so different.
When I was soft bricked, I may have played around in the Mount function of TWRP and screwed it up that way.
Click to expand...
Click to collapse
I wanted to add, the only partition showing as mounted in TWRP is the Data. Can't mount cache or system. Going to restore shows my internal storage at 37 MB. Going to file manager shows I am in the folder "/." In this folder are a boot, cache, data, deve, etc, license, proc, recovery, res, root, sbin, sdcard, supersu, sys, system, tmp, usb-otg, default.prop, file_contexts, fstab.goldfish, fstab.qcom, init, init.rc, init.recovery.qcom.rc, property_contexts, seapp_contexts, sepolicy, ueventd.goldfish.rc, ueventd.rc. Most of these have nothing in them. SuperSu does have a Superuser.apk inside, but its not the SuperSu file I downloaded from Chainfire's page, and with only Data being mounted I'm afraid to flash the default one.
The other funny thing is that when I go to reboot system in TWRP, it says that no OS is installed, but like I said, the stock system boots just fine. I believe everything on my phone is installed to Data.
MarkBell said:
It was actually tdhite's 2.7.1.3 that I flashed that really screwed up my phone.
I was using 2.7.1.1 fine before. I flashed back to 2.7.1.1 after getting my phone working again with the RUU. I have a full backup of my rooted phone saved to my computer and would love to be able to restore it back through TWRP. But the actual filing system in ES File Explorer looks different.
In TWRP, I can't even get to SuperSU to become root because of the way the file system is so different.
When I was soft bricked, I may have played around in the Mount function of TWRP and screwed it up that way.
Click to expand...
Click to collapse
The file system has not changed since 4.1.2 to 4.2.2
was your old system 4.1.2 ?
You should also make it Clear you Have a Sprint HTC One
clsA said:
The file system has not changed since 4.1.2 to 4.2.2
was your old system 4.1.2 ?
You should also make it Clear you Have a Sprint HTC One
Click to expand...
Click to collapse
Yes. It's the Sprint HTC One m7. This is the most bizarre problem I have come across. And I was successfully rooted (SuperSU) with TWRP 2.7.1.1 installed prior to installing TDHITE's 2.7.1.3, which really seemed to mess things up for some reason. I used liquidsmooth custom rom, but ended up going back to the stock ROM and using Xposed framework because I do like a lot of the stock features, but I loved being able to tweak them with Xposed. Now I'm stuck on stock with a weird looking file system.
MarkBell said:
Yes. It's the Sprint HTC One m7. This is the most bizarre problem I have come across. And I was successfully rooted (SuperSU) with TWRP 2.7.1.1 installed prior to installing TDHITE's 2.7.1.3, which really seemed to mess things up for some reason. I used liquidsmooth custom rom, but ended up going back to the stock ROM and using Xposed framework because I do like a lot of the stock features, but I loved being able to tweak them with Xposed. Now I'm stuck on stock with a weird looking file system.
Click to expand...
Click to collapse
Flash recovery from here >> http://techerrata.com/browse/twrp2/m7wls
Start it choose wipe, choose format data, Reboot recovery
choose wipe / factory reset, reboot recovery
push/sideload this rom to your phone and flash it
http://forum.xda-developers.com/sprint-htc-one/development/rom-sense-6-4-4-3-stock-t2848102
Dude, we could really do some serious damage to your phone. As clsA said, you really should make it clear that it's Sprint version. Did you by any chance flash something that's not for Sprint phones? That could screw up your system.
Powered by non removable 2300 mAh battery
Is this possibly just a problem with TWRP? I actually notice in ES File Explorer that things arent' too different after all. I've got a / (Device) folder and a "0" folder which is my internal storage. It's just stuff isn't showing right in TWRP I guess, and TWRP seems to only be mounting my data partition.
MarkBell said:
Is this possibly just a problem with TWRP? I actually notice in ES File Explorer that things arent' too different after all. I've got a / (Device) folder and a "0" folder which is my internal storage. It's just stuff isn't showing right in TWRP I guess, and TWRP seems to only be mounting my data partition.
Click to expand...
Click to collapse
Go back to post 7 and do what I ask
clsA said:
Flash recovery from here >> http://techerrata.com/browse/twrp2/m7wls
Start it choose wipe, choose format data, Reboot recovery
choose wipe / factory reset, reboot recovery
push/sideload this rom to your phone and flash it
http://forum.xda-developers.com/sprint-htc-one/development/rom-sense-6-4-4-3-stock-t2848102
Click to expand...
Click to collapse
This did it. Maybe I just had a bad TWRP image flashed before? Thanks for your help!
MarkBell said:
This did it. Maybe I just had a bad TWRP image flashed before? Thanks for your help!
Click to expand...
Click to collapse
Flashing that TWRP is what got it working. I didn't follow any of the other steps. Thanks so much! Now to load my backup and restore! Thank you. Thank you. Thank you! Making a stock backup first of course. I love these forums. Seriously. Anything is possible with the fine people of XDA.
MarkBell said:
Flashing that TWRP is what got it working. I didn't follow any of the other steps. Thanks so much! Now to load my backup and restore! Thank you. Thank you. Thank you! Making a stock backup first of course.
Click to expand...
Click to collapse
Go back and hit the thanks button, it helps so others know my reputation. and you can edit your first post title to include [solved]
clsA said:
Go back and hit the thanks button, it helps so others know my reputation. and you can edit your first post title to include [solved]
Click to expand...
Click to collapse
I did the thanks, but I can't seem to edit the title of my first post. Title box doesn't show up when I hit edit.
MarkBell said:
I did the thanks, but I can't seem to edit the title of my first post. Title box doesn't show up when I hit edit.
Click to expand...
Click to collapse
Advanced Edit
clsA said:
Go back and hit the thanks button, it helps so others know my reputation. and you can edit your first post title to include [solved]
Click to expand...
Click to collapse
Your reputation is one of the highest here :good: :good:
MarkBell said:
I did the thanks, but I can't seem to edit the title of my first post. Title box doesn't show up when I hit edit.
Click to expand...
Click to collapse
to edit the main thread title to include [SOLVED] (go to 1st post click EDIT, at the bottom of the edit window click GO ADVANCED, then you can edit the main title)