yashsingh1/xdaforums huggingface dataset:
[LG Revolution] brad6360:
Can you use Root Explorer to check and make sure adb is pushing the image file to your phone? Look in this directory: /data/local/tmp/cwmrecovery.img

You could always do this manually using adb. Here's how.

1. Open the ZV8CWMRecovery folder on your PC.

2. Double click the 'Files' folder to go into that directory.

3. Highlight/select and copy the address of your current folder location on your PC. It will look something like this:

C:\Documents and Settings\username\My Documents\Downloads\ZV8CWMRecovery\Files

4. Click Start>Run>type 'cmd' and hit enter/return to open your command prompt.

5. Type 'cd', hit your spacebar, then paste your address which you copied in step 3 into your command prompt, hit enter/return.

6. You should now be positioned in the folder containing the adb and CWMRecovery files.

7. Type the following to copy the CWMRecovery image to your phone:

adb devices
adb remount
adb push cwmrecovery.img /data/local/tmp/cwmrecovery.img
adb shell dd if=/data/local/tmp/cwmrecovery.img of=/dev/block/mmcblk0p14 bs=4096
adb shell "rm /data/local/tmp/* 2>/dev/null"
adb shell rm /system/etc/install-recovery.sh
adb shell rm /system/recovery-from-boot.p
adb shell rm /data/local.prop
adb reboot

Phone should reboot. Try and boot into CWMRecovery after it reboots.
[LG Revolution] mrand1:
idk if I'm not doing something right or wrong. I have usb debugging and internet connection, and I'm getting "remount failed: operation not permitted".
[LG Revolution] HighLimit:
I had the same issue but following these instructions helped me, what finally helped me was typing a wrong command wich gave me a help menu with all the commands, the important one being "adb reboot [Recovery:Bootlaoder]"

adb reboot recovery did the trick, then wiped flashed broken out and sooo happy to be done with it.

after pushing CWM in command prompt of course
[LG Revolution] slimzim:
I'm also getting "remount failed: operation not permitted" when trying adb remount in the command prompt just as mrand1 apparently did.

I (perhaps noobishly) skipped that step and did adb push cwmrecovery.img /data/local/tmp/cwmrecovery.img but after trying the next step got cannot open for write: Permission denied.

I'm trying to get back to Broken Out 1.1 - when it first came out I successfully downgraded to zv7 by flashing the .tot and then doing the OTA update, but now when I try to do that I can't seem to get the OTA to start downloading. I flashed zv8 tot in order to test the latest root method (which works) I just can't get CWM on there now - I don't seem to have any recovery at all actually. Any help would be appreciated. :confused:
[LG Revolution] asauber:
I did the same thing, flashed to zv8 tot, was able to root but was unable to flash cwm recovery. I tried manually doing it and running MT's AIO. It's telling me permission denied on all of the steps except the push cwmrecovery.img. It appears I do not have any recovery either. Trying to get to Broken Out! Any help is appreciated, thanks guys!
[LG Revolution] slimzim:
For what it's worth I also tried that with the same results. :(
[LG Revolution] slimzim:
I finally got this to work much more easily thanks to a quick talk with mtmichaelson. Here's the method:

1) Get to ZV8 (I got there via LGNPST)

2) Root using the tool found here: http://xdaforums.com/showthread.php?t=1621625

3) Open a Terminal Emulator

4) Type: su

5) Hit enter

6) Type: echo 'ro.kernel.qemu=1' > /data/local.prop

7) Press enter

8) Reboot

9) Use the ZV8CWMRecovery.bat found here: http://xdaforums.com/showthread.php?t=1583023

Good luck! ;)
[LG Revolution] asauber:
Man, that was too easy! :D

Thanks for posting this slimzim. This worked straight away for me, I'm installing Broken Out as I type! I'm actually a little glad this happened because now I'm a little more familiar with terminal emulator and what local.prop does. Never had to use it in the past. This is exactly the second phone I've ever rooted and am usually able to just use AIOs.

And of course, thanks to mtmichaelson for chatting with you about it and doing all the hard work in the first place! :)
[LG Revolution] da_morales:
So far not working...repeating process now...
[LG Revolution] asauber:
If you've done all steps exactly it should work. I went through a ton of other "fixes" that didn't work, I believe the key here is when you use the terminal emulator directly on the phone to create local.prop. I was trying to create local.prop in every way but that, and until I did it directly on the phone did I have success.

Good luck!
[LG Revolution] conefree:
local.prop missing

I used the Easy ZV8 All in One Rooting Tool, and have no sound at all like a couple of other users. One of the suggestions was to rename the local.prop file in the /data folder to local.prop.bak.

I assume this is the /data folder in the internal folder? When I did the steps for the all in one rooting tool (coming from rooted zv7), there is no local.prop file in my /data folder to rename, yet I still have no audio for ringtones, phone calls, etc. except for the boot up sound on the splash page.

Any ideas why my local.prop file isn't even there? I even tried copying the one from the mtmichelson zip file into there, still no avail. Thanks!
[LG Revolution] erhlich123:
I have the same issue. I used the echo command in term emulator and the local.prop file was there. rebooted and the file is gone. I have root but cannot install cw recovery. I have tried AIO, adb, and terminal emulator but nothing makes it stick. Any help would be greatly appreciated

Rob
[HTC Rezound] undone98:
so i recently flashed cleanrom 1.2 but i forgot to wipe everything so i restored from a previous recovery. but i think something went wrong because now none of my recovery's have network access (no voice text or data) anyone have any idea as to what i should do? i was thinking of reinstalling a previous kernel
[HTC Rezound] deadheartsbeat:
I had this happen to me once. I had to just wipe all data and reflash the ROM. That fixed this issue for me.
[HTC Rezound] caryzub:
Is your battery cover on? i had the same issue for like 2 hrs, put the cover back on and boom issue fixed. apparently the antenna is part of the battery cover.
[HD2 Android Q&A, Help & Troubleshooting and Genera] miller-might:
Gents,

I am hoping someone can help me with an odd problem.

I have spent a fair few hours reading through the various threads and found a few similar issues, but nothing quite the same.

I have tried the various suggestion on those posts, but have unfortunately not getten very far.

Thought that perhaps the best option is to start a-fresh with a new thread that describes my issues with the HD2.

Needless to say I have a HD2. Originally came with WinMob6.5.

Last year I decided to flash with Android and flashed with UltimateDroid Rom which I very much loved. As it had SPL 3.03 0000. I read a few posts, and had no problem changing the SPL to (HSPL) 2.08.HSPL and MGLDR1.13.

I recently got myself a Desire HD and thought as I have two phones, it may be worth flashing one of the ICS Roms to the HD2 and have a play and see what it is like.

I flashed one of the ICS Roms and was fairly pleased with it, but did have a few bugs, and decided to flash back to a different Android Rom. I thought that the best way would be to first flash it back to the original HTC Stock Rom before I start.

I downloaded the file from the HTC website and flashed it. Ever since then It will not do anything other that boot and stay in the Bootloader screen.

I tried to flash it again with the HTC rom - it goes through the flashing procedure just fine, but when it reboots, yet again, all I get is the Bootloader screen.

I read a few threads and found suggestions that I flash it using the SD. I did that, and yet again, all it would do is boot to the Bootloader screen and do nothing else. The only issue I found with flashing from the SD is that it changed the SPL back to 3.03 0000.

I had no issue using the HSPL4 and changing it back to 2.08.HSPL. But yet again, will allow me to do nothing else.

Ive tried a veriety of suggestion like using task 29 and HD2ToolKit4.2.0.1 etc and I am getting absolutely nowhere.

The really frustrating thing is that when I run the RUU flasher, it detects the phone, and goes through the flash gets to 100%, tells me it is successfull, restarts the phone and I am back where I started - the continues Bootloader screen.

So, any advice and help would be very very much appreciated.

The Bootloader info:

PB81100 HX-BC

SPL-2.08.HSPL 8G XE

0X05

CotullaHSPL 0X30

Thanks.
[HD2 Android Q&A, Help & Troubleshooting and Genera] samsamuel:
Faulty voldown button, perhaps? Registering permanently pressed?
[HD2 Android Q&A, Help & Troubleshooting and Genera] Nigeldg:
To test this if you have reflashed stock WinMo, hold volume up whilst it's booting and it might ask you if you want to hard reset. If this happens, then samsamuel is correct. If you're lucky, it might just bootup normally as well :)
[HD2 Android Q&A, Help & Troubleshooting and Genera] miller-might:
Thanks for the reply, but unfortunately, not worked.

Holding the vol up button, does nothing.

It just boots right back to the bootloader screen.

The odd thing is that I can flash it just fine. Its detected by the pc, it flashes all the way through to the 100% and says it is successfull, but then on reboot, goes right back to the bootloader screen. Its well frustrating.

I am not sure if this makes any difference, but the phone was originally on the Virgin network and also Virgin branded software.

Thanks.
[HD2 Android Q&A, Help & Troubleshooting and Genera] Nigeldg:
I don't think there would be any difference, except that of course being on Virgin your connection would be sh*t :p My brother and mum are on Virgin and get really poor connection everywhere
[HD2 Android Q&A, Help & Troubleshooting and Genera] miller-might:
I am really at a loss. The obvious question now would be, is the phone bricked? Or is there a solution somewhere?

I have tried absolutely everything I can think of.
[HD2 Android Q&A, Help & Troubleshooting and Genera] elias2204:
Try to flash a Virgin network rom.
[HD2 Android Q&A, Help & Troubleshooting and Genera] miller-might:
I've tried.

The only one I can find is RUU_Leo_Virgin_Mobile_1.66.351.1_Radio_15.32.50.07U_2.07.51.22_2_Signed_LEO_Ship

I tried flashing it both via pc, and sd. Flashes fine, goes to 100% no issues, but on reboot, is back to the Bootloader screen.

Only noticible difference is that the SPL has changed to 1.42
[HD2 Android Q&A, Help & Troubleshooting and Genera] miller-might:
Anyone have any ideas?
[HD2 Android Q&A, Help & Troubleshooting and Genera] samsamuel:
try hassling virgin for a replacement would be my advice. Youve tried all the sopftware options (most noteably flashing the stock rom) so i gotta suspect a hardware fault, whether a faulty key, or whatever. So long as the spl line says 1.42.0000 1.66.0000 or 3.03.0000 then its valid for a return (of course warranty is probably gone by now, but worth a try)
[HD2 Android Q&A, Help & Troubleshooting and Genera] miller-might:
Thanks from the reply. I was starting to think that its bricked.

I've also tried as a last resort creating a goldcard, but to no avail.

Thanks for the suggestion with Virgin, I will give that a go.

Thanks again for the effort.
[HTC One X] tali3sin:
So, is anyone else having focusing issues when you get nice and close?

I've moved over from a Nexus S, which could get reasonably close to objects when taking photos and still manage to focus on them... but I'm finding the auto-focus on the One X simply refuses to latch onto the things I point it at.

Is it just me, a software issue, or can the camera on this thing not get that close?

A couple examples below. Red = where I touched, green = where it focused.

The remains of my SIM to micro-sim conversion.

My colleague's horrible banana (simultaneously less and more gross than you're expecting, but sfw)

Ugh, I'm not allowed to post outside links. Hopefully those images worked.

Edit: Score, they worked!
[HTC One X] jpascal:
I have the same problem with mine. I can't get the camera to focus on close objects, even when setting it on macro mode.

I hope it's only a software bug that can be fixed.

JP.
[HTC One X] tali3sin:
Macro mode?

Hmm. Maybe I should look for that.

Yeah, I'm hoping it's something that gets sorted out in 1.28... whenever that comes out. Soon, please.
[HTC One X] vsnlweb:
Me as well... Tried it today with no luck... It refuses to focus when I get really close... Tried turning on Macro "close up" mode and it still didn't focus...
[HTC One X] tali3sin:
I also just gave it a shot, no good. I'm going to be really sad if this is not a software issue :(
[HTC One X] shea-bird:
I've seen a ton of macro close-ups on the web shot with the x, look in the best pictures thread...there a bunch of nice macros...I agree though, the field of focus is rather small and inconsistent in some...others look fine. hopefully it does get worked out for all.
[HTC One X] terrycsw0117:
it should be due to the limitation of the F/2.0 lens
[HTC One X] tali3sin:
Are you saying the limitations with close-up shots is because of the F/2.0 lens?
[Galaxy S I9000 Q&A, Help & Troubleshooting] popotvin:
Before telling me to find the answer by myself, I just want to said that I have already done that.

I know there is a lot of guide and a great variety of rooting method but I just want to ask some questions because I don't have any experience on rooting nor flashing.

What would be the easiest and safest method to root a i9000M on 2.3.3?

I have read about SuperOneClick and also about Doomlord zergrush's method. Which one's the best?

Also, will I lost my files if I root?

Thank you very much for your answers :)
[Galaxy S I9000 Q&A, Help & Troubleshooting] EMnEL:
I have use the SuperOneClick method several times without any problems and have never lost my data. However, I would recommend backing-up all the data before proceeding.
[Galaxy S I9000 Q&A, Help & Troubleshooting] ulysse75:
flash a root kernel (like cf root, to begin) with Odin for me is really simple and safe!
[Galaxy S I9000 Q&A, Help & Troubleshooting] deeplulz:
Realy, man, flash in Odin root-kernel - it's time-tested.
[Galaxy S I9000 Q&A, Help & Troubleshooting] popotvin:
Is there any chance to make the phone not working if I do it wrong? Or will the software just send an error message?
[Nook Touch General] Ambulate:
I've basically all but given up.

The issue essentially is that I have received a bricked nook from my brother.

The only way for it to turn on is to insert a bootable sd, but when cwm appears, I

get the error "can't mount cache/recovery/command" "can't mount cache/recovery/log" "can't open cache/recovery/log". I try accessing the sd card to install a zip, but I keep getting the error "can't mount /sdcard".

I've tried using adb, I've tried pushing recovery and boot files to the sd card, but to no avail. I've tried various versions of cwm using two seperate sd cards, 2&8 gig respectively, but it hasn't helped. Any advice would be immensely appreciated.

(I did find one guide online mobileread/forums/showthread.php?t=120098 that advised using nookie froyo as it partitions the sd card, but I can't exactly see if it works as all the download links to the image are no longer functioning).
[Nook Touch General] XSmoky:
I am also having this problem, i have tried every recovery from bricked method I can find just to get this thing to show something besides the cwm boot menu with its list of errors, but the only thing that looks like it might possibly work has a dead link to the needed scripts.zip to make the sdcard complete.

But I have the added issue of my computer won't recognize the NC connected to it despite having all the latest and even older drivers installed. Right now i am looking at the cwm screen with usb connection to this machine and the device manager isn't showing it. adb doesn't recognize the NC either.

Following guides everywhere (even other forums) i can't seem to get past the errors:

E:Can't mount /cache/recovery/command

E:Can't mount /cache/recovery/log

E:Can't open /cache/recovery/log

E:Can't mount /cache/recovery/last_log

E:Can't open /cache/recovery/last_log

and the worst, most discouraging is:

Error mounting /sdcard!

this has been very frustrating to me. I saw a post where one person was able to run the OS from the sdcard, but if you can't mount the sdcard, that seems to be a wasted effort. nevertheless, i will try to do this as a temp solution and report back what i did in detail.
[Nook Touch General] persichini:
unfortunately i don't have a nook color but i am very versed in screwed up Android devices and fixing them. If all else fails I'll offer my services to fix it. So when you throw your hands up send it down to me and I'll fix it up and send it back.
[Nook Touch General] jreap72:
Im having the same problem. It seems that everything is wiped on it. I can get into CWM but there isnt anything on the emmc and nothing will mount in CWM so any recovery that I put on there doesnt show because the card wont mount.
[Nook Touch General] straygecko:
You've tried to revive a year old thread that was in the wrong forum in the first place. This is the Nook Touch forum. Try posting for help on the Nook Color forum for help and you're likely to get more help.
[Nook Touch General] jreap72:
I figured it was worth a try. This was the only post that was relatively close to my issue. Everything i was able to find was old and outdated.
[Nook Touch General] asawi:
Surely outdated advice for the right device must be better than fresh advice for the wrong one. And nothing fresh here anyway, so head over to the right section!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] softballjunkee13:
I always got an error trying to download from sites like dev-host or dropbox from my phone. Downloads always errored out and wouldn't start up. Found androzip file manager on the market. Since then downloads start and finish without a problem. Noticed some people were having problems downloading to their phone. Hope this helps a few.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] droid512:
Stock twiz blocks downloads if I'm not mistaken you should try a different browser or rom... There was an apk floating around called downloader that bypassed this issue
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] SimPup:
Works fine with dolphin hd
[Samsung Epic 4G Touch] habitformer:
I recently realized the value of reading up on any idea I have for my phone.I cant seem to be satisfied with a single rom.ive recently jumped to a ics blend mini.I nearly failed.fortunately I saw a few posts on how to go back to gb without bricking.thank you to those that failed and posted about it.thanks to those who replied to help.your errors and advice saved me...thanks for my positive outcome...it does pay to do research.those that are new to xda,all I can saw is its not as overwhelming as it appears. If you screw up and ask for help be prepaired to get your a$$ chewed for not reading up....
[Asus  Eee Pad Transformer Prime] radici:
I have a nandroid stock backup that I would like to restore to, however system restores but boot image is stuck at "Restoring boot image..." and goes back to the main CWM screen with reboot system now etc.

in dire need of assistance, can't get out of CWM recovery and when trying to adb the Prime now has an error exclamation mark on it. I have CWM 5.8.1.8
[Asus  Eee Pad Transformer Prime] Doktaphex:
Did you make the backup in 5.8.1.8 or did you make it back in the old 5.5.0.4 version? If you made it back then, then you will not be able to restore boot as that version did not back it up in the first place.

If however you made the backup with your current version of CWM, then I am at a bit of a loss. I have had no issue whatsoever restoring any and/or all of my backups.

When you say that when trying to use ADB the Prime now has an error exclamation mark, please elaborate as to where you are seeing this exclamation mark. Is it in the terminal/command prompt?
[Asus  Eee Pad Transformer Prime] radici:
I made the backup in the old 5.5.0.4 version. I'm using naked drivers which fixed the exclamation mark in pc's device manager however still can't push anything to Prime as adb reports "device not found"
[Asus  Eee Pad Transformer Prime] goodintentions:
You're screwed. You have no backup.
[Asus  Eee Pad Transformer Prime] Doktaphex:
He said in the post above yours that it was fixed. He should probably add that to the Thread title and also detail how he fixed it for other folks who find themselves in a similar situation.
[Asus  Eee Pad Transformer Prime] inspeckta_dek:
Please I need help with similar situation. I'm using cw 5.5.0.4 n tried installing a Rom but doesn't go past ee pad screen. I don't see my back up. How do i use the USB while in recovery?
[Asus  Eee Pad Transformer Prime] Doktaphex:
OK, we need to do a couple of things here. Number one can your computer see your device with ADB? If you are unfamiliar with using ADB read this thread http://xdaforums.com/showthread.php?t=1427008 and then come back here.

If your comp can see your device, we can push a new ROM to your sdcard by making sure you have the ROM in your ADB directory on the computer, and then in a terminal/command prompt you will need to type "adb push *ROM.ZIP* /sdcard" replacing *ROM.ZIP* with the actual name of the ROM (also omit the *s) This will take a while but have patience and eventually you will have a message telling you that it completed successfully.

Now we need to get you a new CWM image onto your Prime. There are 2 methods you could use both detailed in my thread here http://xdaforums.com/showthread.php?t=1576937

If you've followed all of this so far, then give yourself a pat on the back, you are no longer the noob that you were when you set out on this quest. :D We're almost done.

Reboot into CWM the usual way and wipe all partitions. Flash your ROM and it should flash everything including boot.

After verifying that you can get into a working OS, reboot into recovery and make a new backup immediately.

I wish you luck my friend.
[Asus  Eee Pad Transformer Prime] inspeckta_dek:
I have a win 7 pc... When I connect the prime in device manager it comes up as all android on emulator..with yellow exclamation.
[Asus  Eee Pad Transformer Prime] Doktaphex:
Have you tried the naked drivers from here http://xdaforums.com/showthread.php?t=1426502

I would follow that guide, and then see if you can get it working.
[Asus  Eee Pad Transformer Prime] inspeckta_dek:
Nope will check it when I get home. Is it suppose to see it in recovery? Will def try it
[Asus  Eee Pad Transformer Prime] inspeckta_dek:
ok i tried the new driver zip and it installed. its says asus android device and then samsung galaxy nxus.. does that mean its connected?
[HTC Sensation] nakolas69:
I want to go back to cm9 and i have the 3.32 firmware.

Revolutionary

S-OFF

so do I get Ko-oar or watevers 1.17 firmware and take the same steps that I used to get ICS?
[HTC Sensation] HyDRo1X:
Going to a custom rom I.e Cm9 doesn't require downgrading...

Galaxy Nexus GSM with XDA Premium
[HTC Sensation] nakolas69:
ahhhhh mistype cm7 my bad
[HTC Sensation] sshede:
http://xdaforums.com/showthread.php?t=1459767

Download version 1.17 that applies for you and flash that in the bootloader (white screen accessed by holding Vol Down and Power while the phone is off).

Make sure it's on the root folder of the SD card and delete it when your done flashing it. Then boot into the Recovery and flash your CM7.