Database Develop

help with cyanogen recovery image

did the flash_image recovery /sdcard/cm-recovery-1.2.img part then my now my phone freezes every time i hit hold home and power does this mean i cant do updates or anything anymore

Did you thoroughly read before doing this? No issues here at all

Just reflash the recovery...
A frozen recovery is really really no brick.

g1201 said:
did the flash_image recovery /sdcard/cm-recovery-1.2.img part then my now my phone freezes every time i hit hold home and power does this mean i cant do updates or anything anymore
Click to expand...
Click to collapse
quickest fix, setup your system for ADB (if you haven't already). once done, copy cm-recovery-1.2.img to the root of your C:\, reboot your system to fastboot, run cmd prompt and type this:
Code:
PROMPT>fastboot flash recovery c:\cm-recovery-1.2.img
and reboot your phone

OP, would you mind re-naming this thread and not throwing the word "brick" around in such a cavalier manner?

op please read me
Ok, first you flashed the spl before you knew how to do it, so if you are truly bricked you did it not the spl, guns don't kill people, people killpeople with guns, see the metaphor?
But I think u should change the post title to: I jumped into the deep end before I learned to swim and now my phone is pooched, like somebody said don't bricked is a unrecoverable condition, and when you are flashing the spl,bootloader or recovery, you are messing with your failsafe, that you need to recover from a bad OS flash, so yes it is possible to brick your phone if you don't get a good flash, which is why all newcombers should take this story as a cautionary story, if you are new to writing flashes or just learning to "hack" htc devices, stick to OS and radio flashes only cause you always have your failsafe(bootloader or whatever u want to call it) to get things going again.
I've been "hacking"(4 lack of a better term) my phones and pda's for years, had my palm IIIx connected to the net wirelessly via a moto startac on sprints cdma in 1999 and I always read and reread everything I can find before I muck about with anything other than OS & Radio updates before I jump, look b4 u leap.
Even tho I'm guilty of flaming a bit, somebody should close this thread, if he is bricked there are threads for that already
Bhang

If you see any signs of life at all, it's not bricked
People who think they might have bricked thier phones may still be looking at this thread. If you get anything out of your phone at all, it's not bricked.
The last resort and fixall, afaik, is copy DREAIMG.nbh to your formatted to FAT32 sdcard.
Then go into bootloader mode by (from power off) holding down the camera key (until you're there) and powering up with the red power button. The nbh file should load automatically. Wait for this to finish, or you will brick your phone, likely.
One thing that's kind of confusing to newbies (anyone whos been avidly at this for less than a couple of months) is that there are three modes for your phone:
1. Bootloader (powering up with camera button held)
it runs/loads nbh files
2. Recovery (powering up with home button held)
it runs/loads update.zip files
3. The OS (just powering up)
I've only run img files from Telnet and Terminal Emulator (or the SDK adb.exe on my PC, but I don't mind the small keyboard)
If you have either Bootloader OR Recovery modes intact, you can recover the other, and the OS with either (the methods are different from each, though).
To many this will sound so insanely basic it shouldn't be posted. From what I've experienced on the WinMo fora, it will need to be posted over and over and over until someone stickies it so it can't be missed.
Please feel free to correct me on any of these points. HTH.

Denkai said:
quickest fix, setup your system for ADB (if you haven't already). once done, copy cm-recovery-1.2.img to the root of your C:\, reboot your system to fastboot, run cmd prompt and type this:
Code:
PROMPT>fastboot flash recovery c:\cm-recovery-1.2.img
and reboot your phone
Click to expand...
Click to collapse
thanx man im goin to do it now

Oh my god its all my fault!

cyanogen said:
Oh my god its all my fault!
Click to expand...
Click to collapse
naw it aint ya fault i was jus so mad last nite but im not blaming you
i have 2 quest.
1. can u help me get it back 2 normal
2. how can i change this title

you can also re-flash the recovery rom through terminal.
that way you don't have to run into getting 'stuck' by pressing home + power button.

g1201 said:
naw it aint ya fault i was jus so mad last nite but im not blaming you
i have 2 quest.
1. can u help me get it back 2 normal
2. how can i change this title
Click to expand...
Click to collapse
edit your first post, go advance, edit....

mrcrs said:
you can also re-flash the recovery rom through terminal.
that way you don't have to run into getting 'stuck' by pressing home + power button.
Click to expand...
Click to collapse
thats the 1st thing i tried
the thing is when i 1st did it it went threw i got the lil # symbol so i thought every thing was good but i power off and pressed home and power thats when i got stuck

g1201 said:
thats the 1st thing i tried
the thing is when i 1st did it it went threw i got the lil # symbol so i thought every thing was good but i power off and pressed home and power thats when i got stuck
Click to expand...
Click to collapse
what i would suggest is after flashing the next command you input is: reboot
instead of manually powering it down.

mrcrs said:
what i would suggest is after flashing the next command you input is: reboot
instead of manually powering it down.
Click to expand...
Click to collapse
ok im goin 2 try this bcuz the other 1 is not working 4 me
nope its not working i get not permitted

cyanogen said:
Oh my god its all my fault!
Click to expand...
Click to collapse
Of course it is your fault. You are a celebrity now.

g1201 said:
ok im goin 2 try this bcuz the other 1 is not working 4 me
nope its not working i get not permitted
Click to expand...
Click to collapse
how about.. download the file again.. rename it recovery.img and run those same commands
flash_image recovery /sdcard/recovery.img
sounds dumb.. i know..

Cyanogen is a great Dev!
It worked perfect for me as well and I am a rookie

g1201 said:
ok im goin 2 try this bcuz the other 1 is not working 4 me
nope its not working i get not permitted
Click to expand...
Click to collapse
you can not just type
Code:
$reboot
in the terminal. you have to
Code:
$su
#reboot
you have to have SuperUser privileges to reboot.

cyanogen said:
Oh my god its all my fault!
Click to expand...
Click to collapse
It's your God damned fault I <3 my phone so much. Arse.

No more recovery!!!!!!!

Hi everybody, I searched everywhere the forum but I can't find a solution... in the past i successfully rooted my G1, and I installed many Cyanogen roms... until the last one! I did a stupid reboot after flashing the HTC one, so... I had to root it again; no problem, I told myself... but NOW, after some steps (probably some wrong ones...) my phone boots correctly with a RC39 original T-mobile rom, and I can't change it!
If I try to boot into recovery, NO RECOVERY, I see the fastboot (like holding CAMERA button); if I hold the CAMERA button, I enter the fastboot. "Serial0", is displayed... if I try, from the fastboot, to select the typical "DREAIMG.nbh" file, after a quick "checking..." I get a "not allowed" message!!!!!!!
Really don't know where to start from... :-( HEEEEEEEEELP!!!!! :-( I miss my CG roms... :-(

tony_m78 said:
Hi everybody, I searched everywhere the forum but I can't find a solution... in the past i successfully rooted my G1, and I installed many Cyanogen roms... until the last one! I did a stupid reboot after flashing the HTC one, so... I had to root it again; no problem, I told myself... but NOW, after some steps (probably some wrong ones...) my phone boots correctly with a RC39 original T-mobile rom, and I can't change it!
If I try to boot into recovery, NO RECOVERY, I see the fastboot (like holding CAMERA button); if I hold the CAMERA button, I enter the fastboot. "Serial0", is displayed... if I try, from the fastboot, to select the typical "DREAIMG.nbh" file, after a quick "checking..." I get a "not allowed" message!!!!!!!
Really don't know where to start from... :-( HEEEEEEEEELP!!!!! :-( I miss my CG roms... :-(
Click to expand...
Click to collapse
have you tried fastbooting the recovery image again? you might have to reroot the phone

tony_m78 said:
Hi everybody, I searched everywhere the forum but I can't find a solution... Really don't know where to start from...
Click to expand...
Click to collapse
Start by asking in the Q&A section.
http://forum.xda-developers.com/forumdisplay.php?f=507

yeah try starting from rc29 and work your way up. it shouldnt take more then 20 mins rooting from rc29 to 1.6 donut/hero/blur

....right now I got a recovery, just had to flash it from TELNET!!!! ...I lost some hours, on that... thanks

[Q] Triangle of Death, Revisited

OK i've searched and read until my eyes crossed but even the most promising threads seem to peter out when people run out of ideas.
I'm clinging to the popular assertion that "if it boots it's not bricked", someone please help me prove it?
The trouble began when was i was starting over with the instructions here:
(Google - How To: Recover your G1 from a bring Bricked. - Project Hosting on Google Code, involving installation of RC29)
That's as far as i got. The flash seemed to go OK but then it booted to the white triangle with the exclamation point.
The only keys that work are ALT+L and ALT+S. I can't get an adb or fastboot connection. ALT+W doesn't do anything at all and it doesn't reboot from pressing Home+Back, i've got to remove the battery.
Message at the top of the recovery screen says "E:Can't open /cache/recovery/command.
Help?
Thanks
- joe

I don't think it is bricked as recovery is trying to run something ( and failing )
can you boot to the bootloader with power + cam?
what hboot version do you have?
is it 1.33.2005 ?
if it is have you got the newest adb drivers ( this is assuming you are using windows )
assuming the above is true, then get to fastboot mode with power + back ( or power + cam, then press back )
then try
Code:
fastboot erase cache
and try to get to recovery again ( reboot by pressing menu and then hold home )
if that doesn't work then supply the version numbers you get on the bootloader screen
it will help to workout what nbh files you can flash etc
also do you know what recovery version you have?

Effdee said:
can you boot to the bootloader with power + cam?
Click to expand...
Click to collapse
All i get from any button combination is the white triangle with the excalmation point and the dead phone, whatever all that is supposed to mean.
Effdee said:
what hboot version do you have?
is it 1.33.2005 ?
Click to expand...
Click to collapse
I'm sorry i don't know what that means. ALL i get is the triangle screen, i have to press ALT+L to toggle a log display with instructions for what the other button combinations (should) do. There are no numbers of any sort.
My drivers are all up to date and prior to this incident fastboot and adb both worked and i could tether my phone. But since i can't get a connection now and ALT+W (wipe) doesn't do anything, i seem to be limited to loading update.zips and watching the log as they fail to do anything helpful. Generally they fail (as, e.g., Ohsaka's Superwipe) with a "No Signature Verification Failed" or in the case of signed firmware updates, with a much longer and inscrutable error.
But thanks for the response, any advice or possibilities are appreciated.
- joe

passingthru said:
All i get from any button combination is the white triangle with the excalmation point and the dead phone, whatever all that is supposed to mean.
I'm sorry i don't know what that means. ALL i get is the triangle screen, i have to press ALT+L to toggle a log display with instructions for what the other button combinations (should) do. There are no numbers of any sort.
My drivers are all up to date and prior to this incident fastboot and adb both worked and i could tether my phone. But since i can't get a connection now and ALT+W (wipe) doesn't do anything, i seem to be limited to loading update.zips and watching the log as they fail to do anything helpful. Generally they fail (as, e.g., Ohsaka's Superwipe) with a "No Signature Verification Failed" or in the case of signed firmware updates, with a much longer and inscrutable error.
But thanks for the response, any advice or possibilities are appreciated.
- joe
Click to expand...
Click to collapse
so you are trying to flash custom zips with stock recovery?
you need to flash an official update ( with official signatures ) then you need to root and flash a custom recovery so that custom zips will work
http://forum.xda-developers.com/showthread.php?t=442480
flash the appropriate nbh as instucted
you didn't specifically say that powering on whilst holding the camera button doesn't work so I will assume that it does actually work
then follow
Rooting your RC29 or lower phone
using recovery.img from here http://forum.xda-developers.com/showthread.php?t=566669 )
that will give you RA1.7.0 , which you can then use to flash custom zips
but you will need to flash spl 1.33.2005 (danger), which is redundant , you want 2708 for extra 15mb which needs spl 1.33.0013d
http://forum.xda-developers.com/showthread.php?t=831139
read that post a few times, the bit you need is Flashing From a Stock SPL
( which will get you to this post http://forum.xda-developers.com/showpost.php?p=6510019&postcount=76 )
make sure you read all of those links a few times so you understand everything you need to do before you try to do it
Its a learning curve , but it is easy once you understand it
I did get lots of help from a couple of guys in a pub, Mike and Wil , especially Wil who pointed me here ( xda ) and told me who to trust ( ezterry ) and who to just ignore ( pretty much everyone else )

Effdee said:
so you are trying to flash custom zips with stock recovery?
Click to expand...
Click to collapse
Well in my initial ignorance, yes i did try to do that but it didn't work. So i tried e.g. an official signed RC30, which failed with aforementioned inscrutable error. I can try again if the specific error is relevant, but i've tried it at least a half dozen times, with different downloads and verifying same and formatting my SD card FAT32 and only putting the update on it and then safely ejecting the card and ensuring that the file is named update.zip and not update.zip.zip and etc and so on. I've been reading a lot...
Effdee said:
you didn't specifically say that powering on whilst holding the camera button doesn't work so I will assume that it does actually work
Click to expand...
Click to collapse
I said "any" button combination gives me the same result, i.e. the screen with the triangle and exclamation point. So specifically, no the camera button doesn't work, it would be great if it did. I don't think the button itself is broke though, because it had to work in order to get me into this mess.
The link you gave is approximately the process i was attempting, (as a new user i'm not permitted to post links yet), and it was directly after flashing to RC29 that my phone booted to this triangle screen.
So like i said, i am pretty much limited to flashing update.zips since that's all that this interface provides apart from wiping, which doesn't do anything. I was hoping someone could point me to an official signed firmware upgrade (or downgrade or anything really) which would give me some sort of starting point. Or, something. Anything... i'm really in a pickle without my phone.
Thanks again,
- joe
EDIT: Just for the sake of curiosity, i see that Windows recognizes my phone as a storage device only with "no media" so i wonder if that's an ext3 partition, which makes me wonder if i could mount it with a Mac and wipe it so i could try the RC29 flash again. I know very little of *nix or Macs, i'm just going "hmmm".

Something...
I managed to install the CRB43 cupcake update, or anyway according to the console the process completed. I was hoping it would make all my buttons work so i could start over but it booted right to the triangle again.
At the end of the upgrade process it wants me to use Home+Back to reboot but that doesn't work so i have to remove the battery... could this be the problem and if so is there anything else i can do instead?
Thanks,
- joe

So are we calling it a brick?
I don't mean to be impatient but i need to know if i should let go and move on, or if perhaps there is a more appropriate area of the forum to ask this particular question.
I need closure. Or maybe more importantly to all the folks in similar circumstances who are Googling like mad and seeing similar threads just sorta fade away, it would be nice to have a definitive expert opinion like e.g. "if the camera button doesn't work and you can't get an adb connection then it is a hopeless brick". Just for example.
Thanks
- joe

passingthru said:
So are we calling it a brick?
I don't mean to be impatient but i need to know if i should let go and move on, or if perhaps there is a more appropriate area of the forum to ask this particular question.
I need closure. Or maybe more importantly to all the folks in similar circumstances who are Googling like mad and seeing similar threads just sorta fade away, it would be nice to have a definitive expert opinion like e.g. "if the camera button doesn't work and you can't get an adb connection then it is a hopeless brick". Just for example.
Thanks
- joe
Click to expand...
Click to collapse
If you are in recovery (Ie alt-L gives you some options) you are in theory not bricked)
Depending on what is installed powering on with power+camera, pawer+back, power+send (send seems only on the 2000 series dreams and only with some bootloaders) you can access fastboot and at the least use an nbh to restore a working system.
In some cases however there is a stuck home button forcing the booting of recovery and a stock recovery.. or an issue with the misc partition failing to cleae the boot mode.. In these cases booting fastboot is hard and something needs to be done with the hardware issue. in particular if you have a stock recovery w/o test keys.
Last if you are not in a recovery (stock or otherwise) and can't boot to recovery, system, or fastboot; and niether fastboot or adb works, you are "bricked" however if you power on while holding the trackball and see the led turn blue the jtag methods can restore your phone as long as all hardware buttons are operational.
Most of us (including myself) have not been stuck in recovery where rebooting holding camera didn't switch us to fastboot.

passingthru said:
So are we calling it a brick?
I don't mean to be impatient but i need to know if i should let go and move on, or if perhaps there is a more appropriate area of the forum to ask this particular question.
I need closure. Or maybe more importantly to all the folks in similar circumstances who are Googling like mad and seeing similar threads just sorta fade away, it would be nice to have a definitive expert opinion like e.g. "if the camera button doesn't work and you can't get an adb connection then it is a hopeless brick". Just for example.
Thanks
- joe
Click to expand...
Click to collapse
you need a custom recovery, ( the triangle is stock recovery and is very limited )
to install a custom recovery you need root
to get root , read the links I gave

ezterry said:
...however if you power on while holding the trackball and see the led turn blue the jtag methods can restore your phone...
Click to expand...
Click to collapse
Thank you for that. I was panicked because i didn't have a phone but now i've gone out and got a shiny new HD2 and i have a G1 in my desk drawer, the JTAG thing looks like fun. I still want to resurrect my old phone because i still love it.
ezterry said:
...as long as all hardware buttons are operational.
Click to expand...
Click to collapse
Could a few drops of water, like from getting a little bit rained on, have permanently messed up my buttons?
Thanks much,
- joe
EDIT: Also, you said,
ezterry said:
...or an issue with the misc partition failing to cleae the boot mode..
Click to expand...
Click to collapse
If this were the case would i see an error to that effect in the recovery? I had hoped that "E:Can't open /cache/recovery/command" would be a major clue but all the Google returns on that error were people who could still access fastboot.

passingthru said:
If this were the case would i see an error to that effect in the recovery? I had hoped that "E:Can't open /cache/recovery/command" would be a major clue but all the Google returns on that error were people who could still access fastboot.
Click to expand...
Click to collapse
in the recovery log.. /tmp/recovery.log .. but if you have a stock recovery w/o test keys, or adb I'm not sure how to go about checking it. (without somehow getting a custom recovery installed)
misc is not cache.. so misc errors are not reported as cache errors.

ezterry said:
misc is not cache.. so misc errors are not reported as cache errors.
Click to expand...
Click to collapse
Understood, i was just trying to eliminate (or confirm) possible issues. So i wondered if the /misc error would be reported in the recovery console like my /cache error is, and/or if they might represent a similar sort of failure. Because you seemed to be classifying that (the misc error) as a hardware issue which would need dealt with apart from the JTAG procedure.
I was researching the process and it doesn't seem worth the money when i can get a broken G1 from eBay for $35, so maybe whether it's hardware or software, i'd be likelier to get it fixed by mixing and matching parts?
Thanks again.
- joe

How do I root manually?

Hello everyone!
I'm a new member from today but I have read (and read and read...) the threads here and on every forum I could find, in desperate search for an answer to my questions, but so far I have found none.
Don't shop my head of now but could someone please be so kind and help me root my LG Optimus 2x by giving me a step-by-step info AND include the correct files AND then tell me what to do to have them installed?
There seem to be all too many different alternatives and I am really confused!
Here's what I've done so far -
I had Gingerbread installed and got the phone rooted with SuperOnecClick.
Upgraded then the phone to Ice Cream Sandwish 4.0.4 with LG Support Tool and lost root.
Tried to root with SuperOneClick again but constantly got stuck at # 5 or # 7 (waiting for device).​
So, how do I root and where do I find the correct firmware for this?
Android
4.0.4
Bandwithversion
1035.21_20121130
Kernel-version
2.6.39.4
Version
IMM76L.LG-P990-P99030a.1211302332
Software
P99030a
Android SDK
Superuser (not rooted)
SuperOneClick

Hi there,
Since you upgraded to official ICS, you can't use SuperOneClick to get root access again, but fear not as there are alternatives. Here you will find three different methods to root your device. In your case, I believe you need to use either the second or third option listed there.
Be aware that the third option will wipe your device, including your internal SD card, so it'd be a good idea to backup first, just in case. All three methods are harmless, but you never know.

Thank you for your reply! Now I'm on and a step closer in fixing this.
So, my phone cannot be rooted because of Official ICS?! Oh!
- that was new news to me and it could have saved me countless of hours if I had found that information out sooner. A pity I did not write here weeks ago!
I have some more questions though and I think I'm going for the 2nd option in the link you gave me.
"Put your phone into nvflash mode". Do I need a tool for that? (Here I was linking to a nvflash-setup, but as I am a new memeber I am not allowed to post outside links yet). Or do I just hold down volyme + power in order to get into that nvflash mode?
By "unzipping attached archive" I assume it means zipping it on the PC and not on the SD card?
When doing this procedure, do I have the phone in Charging or Mass storage mode?
Just a few questions I hope you (someone) have to time to give me an answer to - Thank you!

MissLight said:
So, my phone cannot be rooted because of Official ICS?! Oh!
- that was new news to me and it could have saved me countless of hours if I had found that information out sooner. A pity I did not write here weeks ago!
Click to expand...
Click to collapse
You can get it rooted, only not with SuperOneClick ^^
MissLight said:
"Put your phone into nvflash mode". Do I need a tool for that? (Here I was linking to a nvflash-setup, but as I am a new memeber I am not allowed to post outside links yet). Or do I just hold down volyme + power in order to get into that nvflash mode?
Click to expand...
Click to collapse
To enter nvflash mode turn off your device, remove the battery, then press and hold Vol- and Power at the same time and plug your phone to your PC via USB. Then follow the rest of the instructions.
MissLight said:
By "unzipping attached archive" I assume it means zipping it on the PC and not on the SD card?
Click to expand...
Click to collapse
Yep ^^ you need to extract the files from the zip to your PC.

Ok, next question :
"boot into cwm and flash SuperSU Root.zip"
How am I suppose to flash anything when the telephone is black and I'm not into it and only work from the computer?
How do I do that?
I'm stuck with a black screen only on the phone.
I heared nothing or saw nothing that sais (sound) that the phone is connected through the USB, but I have followed each step and are now stuck at above question.
Greatful for more help!

MissLight said:
Hm. I have now read more closely on the linked site. Why am I to download ICS again, I already have the same ROM?
Or do you mean I have to change the official ROM to this one in order to root properly?
Click to expand...
Click to collapse
No, there's no need to reflash ICS. The second method listed there just flashes the unlocked bootloader + root + custom CWM, and it won't touch your data & settings.
MissLight said:
I tried Volume down + Power without battery. Nothing happened, the phone was stonedead even when plugged in with USB.
Click to expand...
Click to collapse
That's OK. When in nvflash mode, you won't see anything on screen. All you'll get is the sound it makes when connected to USB.
Don't worry, you're nearly there! Keep going!
Edit: just realized I made one small mistake. To enter nvflash mode, you need to press and hold both Vol+ & Vol- at the same time (this also requires removing the battery first). Sorry about that!

Edit: just realized I made one small mistake. To enter nvflash mode, you need to press and hold both Vol+ & Vol- at the same time (this also requires removing the battery first). Sorry about that!
Oh! That explains why. My next question was published above your question and still remains.
How do I "boot into cwm and flash SuperSU Root.zip"?
Edit : This procedure does somehow not work on XP so I changed to Windows7 and have now come a bit further. The only thing remaining now is that the computer sais that it cannot find the USB device.
I have downloaded the LG modem and USB firmware but maybe I need something else? Does the firmware in a folder on C: just as NvFlash and SU-folder.

Got OK with USB firmware and all set to go now.
But, in NVFlash Recovery it sais :
Please pick bootloader, or exit (1,X)? (I pressed 1)
Attempting to flash bootloader...
Nvflash started
USB device not found
Program will now exit​
So, I'm stuck.
The phone can be found both in Mass Storage mode and I got a OK that the drivers are installed.

MissLight said:
Got OK with USB firmware and all set to go now.
But, in NVFlash Recovery it sais :
Please pick bootloader, or exit (1,X)? (I pressed 1)
Attempting to flash bootloader...
Nvflash started
USB device not found
Program will now exit​
So, I'm stuck.
The phone can be found both in Mass Storage mode and I got a OK that the drivers are installed.
Click to expand...
Click to collapse
Alright, it sounds like you still need the APX drivers. I believe you can find it somewhere on the Development forum (find tonyp's threads, I'm sure he has posted it there). If you already did this, then remember to hold and press both Vol buttons when selecting option 1 so Nvflash can connect to your device and do all the magic.
Don't give up yet, you're a few seconds away from rooting your device (and learning stuff at the same time ^^).

Tried exactly as you said but still no luck. But I'm not giving up!
I found a APX driver. Installed and unziped in the same file as NvFlash. Rebooted PC and tried again.
Still no luck - "USB device not found".
What am I doing wrong?
BEFORE removing the battery from mobile, shall I have Mass Storage or Charging marked?
Do I need to have USB Debugging marked or not?

Latest Update :
I managed to install Nvidia usb boot recovery in the device manager and it's OK.
The device is now found and I got the phone into S/W Upgrade please wait while upgrading-mode.
And there I am - stuck. Nothing more happens. It has freeze.
What do I do next?
A question : How do I "boot into cwm and flash SuperSU Root.zip" - how do I do that?

Nice! Has nvflash finished flashing? If so, it should be safe to unplug the device now.
Put the battery back on, press and hold both Power and Vol- at the same time until the second LG logo appears to enter CWM. From there, select "Install zip from SD card" (or something similar) and select the SU zip file you previously stored onto your sdcard. CWM will then flash the necessary files to root your device! Once done, reboot and enjoy!

Hi again! It's not going as well unfortunately. Very mysterious. *laugh*
"until the second LG logo appears to enter CWM. From there, select "Install zip from SD card"
When pressing Volyme - + Volyme up + Power I get a black screen. Nothing more happens.
And after flashing the flash-boot in NvFlash the phone goes into s/w upgrade please wait while upgrading-mode.
And there it is. Stuck. Nothing more happens. I repeted the procedure for 5 times. I only get to the s/w-mode.
After 3 hours I unplugged it and will restart my search today for what's blocking it to continue.
Hm? Hmmmm....? Any suggestions in what might be wrong?

You have to push and hold only Vol- and Power this time ^^ That will get you into CWM if the flash-boot.bat went right.

Great, I'm in!
But I managed to place the SU zip on wrong device (internal, not external).
How do I get out from cwm-mode, there's no "exit" options?

There should be a Reboot option, use it and your phone will boot as usual. When you're done moving the SU zip file to the external SD card, power off your 2X and do as instructed above to enter CWM again ^^

Thank you for replying so quickly!!!!!
There is a reboot option BUT I unfortunately pressed adb sideload (hoping to install the SU.zip that way, but the device is not to be found on the PC at all in that mode so I can't reach it through cmd either!).
So, I'm completely STUCK at adb sideolad-mode.... (sorry). I'm starting to get grey hair.

Hahahah XD don't worry, just remove the battery and put it back again ^^

*BIG SMILE* Guess what? I have root access! *jumping up and down of joy*
THANK YOU! THANK YOU! THANK YOU so very much for your guidance!
I believe in passing knowledge forward and I will do my best to help others noobs with what you just learned me!​
For a stubborn noob like me I was not reflecting over some obvious things though. As that the SU.zip had to be placed on SD-card (and not being unzipped in C: )
And that I had to get the Nvidia APX in order to make NvFlash to work properly (and search through Google to find it and how to make it work).
And that when I'm stuck in CWM I can always remove the battery.
Once again. I'm very glad and THANK you and all credit to You!

You know, I decided to help you because of your will to learn and do stuff by yourself. Many come here and ask for help without trying anything by themselves first, so I actually enjoyed watching you learn ^^
See? It wasn't that hard. All it takes is a lot of reading and patience.
Good job, and welcome to XDA!

[Q] what am I doing wrong?

I followed the steps on this site droidviews com /2013/ root-htc-one-m7-and-install-clockworkmod-recovery-on-it to root my phone. but I get no on-screen instructions and your HTC One will be rooted in a few moments. it goes to the white screen saying this is for devs and then turns off after a few secs. the bootloader screen now says tampered and unlocked at the top but I am not rooted.

http://forum.xda-developers.com/showthread.php?t=2182792
Should have followed this, if you followed this step by step it's really simple and nothing goes wrong
Sent from my HTC One using xda premium

yvibes said:
http://forum.xda-developers.com/showthread.php?t=2182792
Should have followed this, if you followed this step by step it's really simple and nothing goes wrong
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Could I follow that now or am I screwed for trying what I did?

Don't think you have done anything wrong. It's perfectly normal the bootloader screen shows "Tampered Unlock", otherwise you may not be able to get into recovery mode.
need to be more specific though. Have you flashed the recovery using fastboot? erase cache after flashing recovery may be helpful.
pay attention to the top of the booting screen see if there's a line says entering recovery
having the bootloader unlocked is not the same thing as rooting the phone.

人云奕云 said:
Don't think you have done anything wrong. It's perfectly normal the bootloader screen shows "Tampered Unlock", otherwise you may not be able to get into recovery mode.
need to be more specific though. Have you flashed the recovery using fastboot? erase cache after flashing recovery may be helpful.
pay attention to the top of the booting screen see if there's a line says entering recovery
Click to expand...
Click to collapse
I know I can get into cwm touch I have that but thats all I have. I was reading the site he linked and it says I have to get cwm to flash either supersu or super user. I guess the thing I tried didnt put that in. I just want to be rooted so I can use usb thethering for free if I ever need to use it on my laptop. I thought I was smart enough to handle this but once I started I realize maybe I didnt do enough research and I don't want to break my phone.

Tsukiyohikage said:
I know I can get into cwm touch I have that but thats all I have. I was reading the site he linked and it says I have to get cwm to flash either supersu or super user. I guess the thing I tried didnt put that in. I just want to be rooted so I can use usb thethering for free if I ever need to use it on my laptop. I thought I was smart enough to handle this but once I started I realize maybe I didnt do enough research and I don't want to break my phone.
Click to expand...
Click to collapse
Easiest way is to flash TWRP here is a thread http://forum.xda-developers.com/showthread.php?t=2173870 or here is a ALL IN TOOLKIT http://forum.xda-developers.com/showthread.php?t=2183942 once you have team win recovery go to it and reboot it will ask you if you want to root.

nullkill said:
Easiest way is to flash TWRP here is a thread http://forum.xda-developers.com/showthread.php?t=2173870 or here is a ALL IN TOOLKIT http://forum.xda-developers.com/showthread.php?t=2183942 once you have team win recovery go to it and reboot it will ask you if you want to root.
Click to expand...
Click to collapse
I looked into that ALL IN TOOLKIT , so all I do is have it do cwm touch then do I press flash kernal and thats it or do I have to click on the perma root ?I feel like a moron asking this.

Tsukiyohikage said:
I looked into that ALL IN TOOLKIT , so all I do is have it do cwm touch then do I press flash kernal and thats it or do I have to click on the perma root ?I feel like a moron asking this.
Click to expand...
Click to collapse
We all have to learn somewhere. All you need to do is flash Team Win Recovery it should be the very last one in the list of recoveries. Do the touch version. Then reboot your phone into recovery once you are in Team win recovery select reset the recovery will then ask if you want to root. There are many other ways but I think this is about as easy as it gets.