Develop Bugs

Issues after possible root?

Someones help would be greatly appreciated.
I spent about 8 hours trying to root my phone last night.....the first time I ran the 4-step root, it went flawlessly. After that however, I downloaded Rom Manager and clockwork wouldn't download (repeated error). I then downloaded Titanium Backup and the program said I didn't have root access.
Fast forward 6 hours later and many additional attempts to re-root (each time hanging up at step 4)........I decided to try and see if my phone was rooted already.
I did a search and based on that search I typed cmd in the search bar (vista), then typed adb shell.....hit enter......and got #.
If I understand right, this means that I'm rooted.
So, 1) Am I rooted?
2) If yes, why can't I proceed from here?
3) How do I proceed from here (In noob terms)?
4) Did I screw anything up or do I need to delete some files as a result of trying to re-root over and over?
Assistance would be greatly appreciated, and I'll be sure to do the same once I have this figured out.

Few more questions.
1) If I'm rooted and all, do I need to install a rooted rom before Rom Manager (clockworkmod) and Titanium Backup will work? I was trying to use Rom Manager to perform a backup before I flashed any ROMS.
2) Is there some superuser file that needs to be downloaded and could that be my problem?
Thanks again.

Just a hunch, but your probably running the pre-release software build. You need to flash the latest rooted software version 147
651.1. The thread is in the development forum.
Sent from my PC36100 using XDA App

BrianBusby2038 said:
Just a hunch, but your probably running the pre-release software build. You need to flash the latest rooted software version 147
651.1. The thread is in the development forum.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
No sure what you mean, but I originally had 147 before attempting root and now I have 1.17.651.1. If I need to flash the software you are referencing could you please provide the link to the forum....I've looked but I'm not entirely sure of what I should be looking for.

I don't know the link but the thread is in the Android Development section and is titled fully rooted stock version 147.651. 1 no adb. Will probably be on page 2nd of the forum. After running the 2 files linked in that thread you'll be all set to run a customer rom.
Sent from my PC36100 using XDA App

Ok, found it.
However, I have the file PC36IMG already on my SD card (it's zipped). Should I replace it with the one you're referring to, use it, or just leave it alone?

I've tried everything.
If someone wants to give me a hand getting all of this worked out and fresh flashed, I'll shoot them some $$ via paypal.
I'm almost 100% my phone is rooted, just can't make a backup, upgrade to the rooted 147 stock rom, download the SU, or flash a custom ROM.

First, remove any zip files you downloaded for rooting purposes from your sd card (place them on your computer for safekeeping). Then, power off your phone and power it back on while holding volume down. At the top it'll give you an HBOOT VERSION. Which version do you get?

Says 0.76.2000

kirk1978 said:
Says
Click to expand...
Click to collapse
Excellent..suggest you follow the "starting over" method by whitslack which can be found in the development section...very easy...

Success at last.
Thanks a ton!

kirk1978 said:
Success at last.
Thanks a ton!
Click to expand...
Click to collapse
Glad you resolved that. Feel free to seek any more help if you need it!

I have this same issue, however my hboot version is 0.79.0000. Suggestions?

aceintheh0l3 said:
I have this same issue, however my hboot version is 0.79.0000. Suggestions?
Click to expand...
Click to collapse
Your nand is still locked. Depending on your software version you will have to root then nand unlock. Let's see if I can help you. What version is your Software Number?
Menu->Settings->About Phone->Software Information->Software Number

Thanks for the response.
I've actually made a good amount of progress. I've followed toastcfh's post about unlocking my nand and it is currently reflashing.I'll give you my versions and suck when everything is said and done

New and Improved way to Unroot your device (much easier) [difficulty level 4]

So I am moving onto a new phone so I will not be supporting this thread anymore. Please help each other the best you can. Also if anyone wants to take over and support this thread feel free. Last but not least if anyone wants to use any of the items I put into this also feel free. Remember that android is made possible with contrbutions from viewers like you!
Check out my new guide its much easier and automated now!!
Sorry but I no longer have the files that were in the zip as my laptop that they were on no longer has a charger so I really don't have a way to pull them off until I come up with extra funds to buy a charger for that dinosaur!
I have updated the commands so everything will be working correctly.
Please note this a guide to unrooting your device and returning it to stock, if you have nothing stock and didn't back anything up i.e. modded rom, changed recovery, eng. bootloader.
If you didn't follow the ultimate guide then you will not need to follow steps 1-7. Just follow from 8 on.
Also keep in mind this was created assuming you followed the ultimate guide to permaroot turning radio s=off and changing cid thus unlocking phone.
I am not responsible for any damage to your phone blah blah blah.
Also if I am incorrect in any of these steps someone please let me know.
Also this is just a guide that I wrote using all the others. Please thank and donate to grankin01 for providing the original guide and also thank/donate to tiger013 for providing a stock nandroid. Also thank Football for providing new rom.
With that said here we go:
Download the PD15IMG file and rename it to PD15IMG.zip
1. Copy PD15IMG.zip and "part7backup-whatevernuberitscalled.bin" to the root of your sdcard
2. Connect your phone to your computer and navigate to your sdk folder then type adb push gfree /data/local
3. Open up terminal emulator or adb shell and type "su" press enter to get root privileges.
4. Type "cd /data/local" and hit enter
5. Type "chmod 777 gfree" and hit enter to make the program executable.
6. Now type "./gfree -f" press enter to run gfree again. It will disable wp on the emmc and remove the brq filter in the kernel. (as well as make another backup. delete this)
7. Now run the "dd if=/sdcard/part7backup-whatevernumberitscalled.bin of=/dev/block/mmcblk0p7" and it should show the output:
xxxx bytes in
xxxxbytes out
xxxxxxxxxx copied in xxxxxxxxxxx
8. Run "sync" and then reboot.
9. Let phone load then boot into bootloader again by holding volume down and pressing power
10. Let it load image and select yes to update.
11. Let it do its work it will reboot once this is normal.
And that should be it. Enjoy stock rom.

Great job! I un-rooted worked fine! Then I re-rooted worked fine also!
Sent from my HTC Glacier using XDA App

I assume this will not work if you have made a backup with clockwork? Also your instructions say apply nandroid backup, but there is no option in recovery for appy nandroid backup. There are options to update from update.zip and another one from a zip file. The folder inside you unroot package is not a zip file?

bobsbbq said:
I assume this will not work if you have made a backup with clockwork? Also your instructions say apply nandroid backup, but there is no option in recovery for appy nandroid backup. There are options to update from update.zip and another one from a zip file. The folder inside you unroot package is not a zip file?
Click to expand...
Click to collapse
Well like I said this was done using no backups made.
Under clockworks recovery theres an option for backups and restore - this is the nandroid restore.
Sent from my HTC Glacier using XDA App

where does the "part7backup-whatevernuberitscalled.bin" file in step 11 come from?

vw671 said:
where does the "part7backup-whatevernuberitscalled.bin" file in step 11 come from?
Click to expand...
Click to collapse
Its the file that was created when you followed the ultimate guide for permaroot
Sent from my HTC Glacier using XDA App

jjjackson56 said:
Its the file that was created when you followed the ultimate guide for permaroot
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
What if you don't have that file? Can you skip that step?
thanks.

vw671 said:
What if you don't have that file? Can you skip that step?
thanks.
Click to expand...
Click to collapse
I'm sure you can but you won't have true stock. I could also upload my copy but I'm not positive if it will work for your phone.
Sent from my HTC Glacier using XDA App

This is awesome! I'm getting a replacement mt4g in the mail soon, now I will be able to send my existing phone back 'unrooted'. Thank you!

Is this unroot like out of the box type deal. So that i can get future ota updates. I used ultimate guide to perm root. I am using stock rom. I am notsure if i should just do unroot.zip to unroot for future ota updates.
Sent from my HTC Glacier using XDA App

If performed correctly is should take you back to out of the box stock.
(in theory)

I'm guessing you can't do this strictly from terminal emulator?
Sent from my HTC Glacier using XDA App

hawaiian.monzta said:
I'm guessing you can't do this strictly from terminal emulator?
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
You may be able to but I don't know how nor do I care to figure it out. If someone wants to write instructions pm me them and I'll post them in the op
Sent from my HTC Glacier using XDA App

jjjackson56 said:
You may be able to but I don't know how nor do I care to figure it out. If someone wants to write instructions pm me them and I'll post them in the op
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
A guide for terminal emulator would be welcome.
I did S=off with it (plus radio) with root explorer and terminal emulator only. It was much easier and quicker.

gaww said:
A guide for terminal emulator would be welcome.
I did S=off with it (plus radio) with root explorer and terminal emulator only. It was much easier and quicker.
Click to expand...
Click to collapse
You could pm me the steps and I'll gladly post them in the op
Sent from my HTC Glacier using XDA App

quick question, does following this take you back to factory ROM? for exampe im on iced glacier 1.1.1, will it take me to factory ROM?

mrpanic7 said:
quick question, does following this take you back to factory ROM? for exampe im on iced glacier 1.1.1, will it take me to factory ROM?
Click to expand...
Click to collapse
Yes it will hence stock
Sent from my HTC Glacier using XDA App

so...?
I put the nandroid file on my sdcard, but in recovery when i go to restore there it says no files. What do I need to do to get this to work. I have a replacement coming to me so I need to figure this out.
Edit: Sorry I'm an idiot. I got it know. Thank you so much for posting this.
Edit2: Crap! Ok I have s=on now but i still have hboot 0.86.0000 Shouldn't I have the old one now?

Where is the "part7backup" located? Also, what is it?

this sucks... i followed everything perfectly but now my recovery is screwed up ugh this is so frustrating i have that stupid phone with a red triangle thing when i try to boot into recovery (yes im aware its supposed to be stock recovery not clockwork)

[Q] Problem with adb remount

OK I know this problem has been posted hundreds times before but i've read several of them but still can't find out what i did wrong. SO: I got my G2 rooted with S-OFF as i looked in the bootloader. I rooted the phone using rage method. So if i have my S-OFF that's obviously that i am rooted right?
And I definitely have my adb set up right cuz i could not root my phone if i didn't have adb set up. The question is Why every time I try to do adb remount, it will keep saying remount failed operation not permitted.
Even when I try doing adb shell and su it would say access denied too.
Just a little frustrating, What can i do to fix this?

wang1404 said:
OK I know this problem has been posted hundreds times before but i've read several of them but still can't find out what i did wrong. SO: I got my G2 rooted with S-OFF as i looked in the bootloader. I rooted the phone using rage method. So if i have my S-OFF that's obviously that i am rooted right?
And I definitely have my adb set up right cuz i could not root my phone if i didn't have adb set up. The question is Why every time I try to do adb remount, it will keep saying remount failed operation not permitted.
Even when I try doing adb shell and su it would say access denied too.
Just a little frustrating, What can i do to fix this?
Click to expand...
Click to collapse
I am not %100 if this is your problem but i think you need ENGINEERING HBOOT
to run adb commands ,you can do it by reading the wiki http://forum.xda-developers.com/wik...Z.2FG2.2FDHD.29_-_OPTIONAL_and_UNNECESSARY.21
But if you want to do it be very very carefull becasue if you do it wrong you will brick your phone and there is no way back

S-OFF is different from having your phone rooted, so it sounds like your rooting hasn't worked. If you have S-OFF and the eng hboot, you could use fastboot to flash Clockwork recovery and then install a custom pre-rooted ROM.
Or you will need to go through the rooting procedure again to see what has gone wrong.
Sent from my HTC Desire Z

If that's the case that my phone hasn't been rooted. My rom manager worked. I flashed clock work successfully and I did checked that I had it by rebooting into recovery. I even used n1 torch high brightness to make sure I was rooted. Then extra step was asking su in my terminal emulator too. But I still had hboot.img tho. Should I do an engineering hboot ?
Sent from my Nexus One using XDA App

steviewevie said:
Or you will need to go through the rooting procedure again to see what has gone wrong.
Click to expand...
Click to collapse
I did notice that while I was rooting. A command said no such file or directory. So I wonder if that was it? I thought it was supposed yo happen tho lol
Sent from my Nexus One using XDA App

wang1404 said:
If that's the case that my phone hasn't been rooted. My rom manager worked. I flashed clock work successfully and I did checked that I had it by rebooting into recovery. I even used n1 torch high brightness to make sure I was rooted. Then extra step was asking su in my terminal emulator too. But I still had hboot.img tho. Should I do an engineering hboot ?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
If you can boot into CWM recovery just flash a custon rom they all have root built into them.

joemm said:
If you can boot into CWM recovery just flash a custon rom they all have root built into them.
Click to expand...
Click to collapse
It's my wifes phone so I don't wanna do something too complicated for her. I mean the easier for her to use the phone the better. But will that fix the problem? Adb remount problem? If yes than hell yeah I would flash cyan right away lol.
Sent from my Nexus One using XDA App

wang1404 said:
It's my wifes phone so I don't wanna do something too complicated for her. I mean the easier for her to use the phone the better. But will that fix the problem? Adb remount problem? If yes than hell yeah I would flash cyan right away lol.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Should fix any problems with mounting, heres a link for a stock rooted rom, so she wont be able to tell the diffrence, also since you can boot into CWM recovery make a backup of your current rom before flashing this:
http://forum.xda-developers.com/showthread.php?t=836042

joemm said:
Should fix any problems with mounting, heres a link for a stock rooted rom, so she wont be able to tell the diffrence, also since you can boot into CWM recovery make a backup of your current rom before flashing this:
http://forum.xda-developers.com/showthread.php?t=836042
Click to expand...
Click to collapse
The ADB remount command requires the ro.secure property to be set to 0 (even if you are rooted). If you want to remain on the stock ROM, flashing the linked ROM will do it for you (and is way easier than doing it yourself manually). Most (if not all) of the custom ROMs will set this property for you if you wanted to try others as well.

Thank you guys very much. I never faced this problem before since my n1 was rooted and flashed rom using the phone not adb our anything related to computer.so thanks guys. Case closed. Happy me lol
Sent from my Nexus One using XDA App

Revolutionary Rooted but Not???

First I wanted to say hi to all of you. Evo 4G is my second Android phone. I'm still a noob in training but I'm getting by.
I'm having a bit of a issue with trying to use some apps for root only and keep getting that I need to be rooted. Yes S-Off is displayed but I'm still running into this issue no matter what. Did I miss something? I'm still searching the forum to find a answer but I haven't found anything as of yet.
Let me know what you guys think.
Thanks
Z3r0
Edit: I figured out what the problem was. Me being stupid and not reading enough. Mods go ahead and lock/delete this thread.

to double check, there is an app in the market called "root check" by joeykrim.
and for apps to gain access to the phone you should have the app "superuser" it gives other apps permission to access root.

As someone previously stated, you'll need an app called "superuser" to allow apps to use root permissions.

Greenfieldan said:
As someone previously stated, you'll need an app called "superuser" to allow apps to use root permissions.
Click to expand...
Click to collapse
This.
Running Revolutionary Roots your phone, but you need superuser to give programs root access. To give programs root access, you will need a rooted ROM with the superuser application or just download the superuser app.

oldwesterncowboy said:
to double check, there is an app in the market called "root check" by joeykrim.
and for apps to gain access to the phone you should have the app "superuser" it gives other apps permission to access root.
Click to expand...
Click to collapse
Yeah I figured that out after reading the sticky at the beginning. My fault for not paying attention. I'm now rooted and loving it.
Thanks for the reply's guys.

I really did it now!!!
Ok so I'm back to ask some questions due to a noob mistake. Now I have been reading many of the threads that are available to fix my actual issues that I'm dealing with. I'm going to be very detailed so I apologize in advance.
So like a dumb dumb I decided to unroot my Evo as I was sure/ uncomfortable using the rooted OTA update to up date. So now I did some more reading and I did not need to unroot. Sorry I dont' know what I was thinking.
I've tried to run Revolutionary but all it does is aborts the operation everytime. I tried to change the recovery from Clockwork to Amon RA as I read that it is better so I tried to do that too. Nope that doesn't work either.
I was able to update the root OTA update but that was all that was done. So now I'm here asking for more help as I did more reading how to fix the current issue I'm having and its not working.
PLEASE Help me or guide me in the right direction to fix this.
This is all I am trying to accomplish:
1. Figure out why and what happend and get my Evo rooted
2. Apply the Amon RA recovery
Now if I need to completely wipe my phone I will do it if that is what you think is needed to be done. I know how to back up my app/ contacts etc. So just assist this dumb dumb please!

Anyone have any ideas?
Sent from my PC36100 using xda premium

So are you s on or s off when you go into hboot?
Sent from my PC36100 using Tapatalk

revolutionary s-off
Another noob here.... Ok I used revolutionary.io to root my 2.3.3
Hboot says s-off, downloaded superuser app, and astro file
Why does it say can't delete file when I try to delete pre installed files like Amazon mp3, ect
Ran root checker app from market said
Root Access is not properly configured or was not granted.
Superuser.apk - com.noshufou.android.su - version 3.0.5 is installed!
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
The adb binary is set to default shell user access as a standard non-root user
Standard su binary location: ls -l /system/bin/su:
/system/bin/su: No such file or directory
Standard su binary location: ls -l /system/xbin/su:
/system/xbin/su: No such file or directory
Alternate su binary location:
/sbin/su: Permission denied
Alternate su type binary location:
/system/xbin/sudo: No such file or directory
SU binary not found or not operating properly

tommytomatoe said:
So are you s on or s off when you go into hboot?
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
s on which I know is not rooted. No matter what I try it refuses to accept the revolutionary root program. Should I try a different root method or is Revolutionary for 2.3.3 the only method? I've looked and can't find any other way.

z3r0t0l0rEnCe said:
s on which I know is not rooted. No matter what I try it refuses to accept the revolutionary root program. Should I try a different root method or is Revolutionary for 2.3.3 the only method? I've looked and can't find any other way.
Click to expand...
Click to collapse
What is your HBOOT version, when you go into Bootloader?

Last I checked revolutionary won't s-off anything besides hboot 2.15 & 2.16. Not even the revolutionary hboot 6.xx
tapatalk signature here. lovely.

2.16
Sent from my PC36100 using xda premium

z3r0t0l0rEnCe said:
2.16
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
First, I would flash an unrooted stock ROM - the latest, if possible (see this post).
Then, try rooting via Revolutionary again (revolutionary.io). Sometimes during the unrooting process, everything isn't completely restored to stock, so you might just need to flash a completely stock ROM to get back to the point where Revolutionary will work again.

Captain_Throwback said:
First, I would flash an unrooted stock ROM - the latest, if possible (see this post).
Then, try rooting via Revolutionary again (revolutionary.io). Sometimes during the unrooting process, everything isn't completely restored to stock, so you might just need to flash a completely stock ROM to get back to the point where Revolutionary will work again.
Click to expand...
Click to collapse
Thanks for the heads up on this info. Now with the Stock RUU being RUU_SuperSonic_GB_Sprint_WWE_4.53.651.1_Radio_2.15 .00.0808_NV_2.15_release, does the 2.15 represent the HBOOT? As mine is the 2.16 or does that not matter?

z3r0t0l0rEnCe said:
Thanks for the heads up on this info. Now with the Stock RUU being RUU_SuperSonic_GB_Sprint_WWE_4.53.651.1_Radio_2.15 .00.0808_NV_2.15_release, does the 2.15 represent the HBOOT? As mine is the 2.16 or does that not matter?
Click to expand...
Click to collapse
The file name has nothing to do with the HBOOT version. It doesn't matter. If the HBOOT version you currently have is newer than the version in the RUU, it will simply skip updating it.

Ok ill test it when I get home from work tonight.
Sent from my PC36100 using xda premium

z3r0t0l0rEnCe said:
I've tried to run Revolutionary but all it does is aborts the operation everytime. I tried to change the recovery from Clockwork to Amon RA as I read that it is better so I tried to do that too. Nope that doesn't work either.
Now if I need to completely wipe my phone I will do it if that is what you think is needed to be done. I know how to back up my app/ contacts etc. So just assist this dumb dumb please!
Click to expand...
Click to collapse
All you need to is flash another hboot for the evo. (Any of them will work. Doesn't really matter. Look around for the files and a guide is out there I'm sure. If not, PM me. Anyway, flash it. And then run revolutionary. It should work then.
I did not know that, tommytomatoe. But regardless, what I suggested would work if my thinking is correct.

IamNotSureX said:
All you need to is flash another hboot for the evo. (Any of them will work. Doesn't really matter. Look around for the files and a guide is out there I'm sure. If not, PM me. Anyway, flash it. And then run revolutionary. It should work then.
I did not know that, tommytomatoe. But regardless, what I suggested would work if my thinking is correct.
Click to expand...
Click to collapse
He said he has Hboot 2.16. If I'm not mistaken you cannot downgrade your Hboot version from something like 2.16 to 2.15 or 2.10. Either way, Revolutionary will be able to root 2.16 just fine. Seems like all he needs to do is follow Captain Throwbacks advice to get his phone out of "What the hell are you doing to me" mode.

I have yet to perform the flash. I got caught up at work late last night. I'll do it tonight for sure when I get off work.
Thank you all for the input and I'll let you all know if my Evo will let me get it out of ""What the hell are you doing to me" mode.

My phone's stuck on 2.3.6, can't upgrade or root

Hi everyone. I had a long journey trying to root my phone, I originally had ICS and tried following this tutorial: http://forum.xda-developers.com/showthread.php?t=2044645 It was able to get my phone rooted by step 7, but then I couldn't get into recovery mode, it kept giving me:
---------------
Secure booting Error!
Cause : boot certification verify
-------------------------
------------------------------
Enter the fastboot...
Enter the fastboot...
Long time no see!
-------------------------------------------------
So I thought perhaps this doesn't matter at this stage and so I continued on with the tutorial. Eventually (long story short) something happened and now I have downgraded to Android 2.3.6 but my phone is no longer rooted (I don't have 'super user' app and root checker says I'm not rooted). I tried upgrading back to at least ICS through software update but it gives me a "you are not registered" (or something like that) and won't update.
I have no idea what to do now. I honestly just want to get ICS back and give up on this whole rooting attempt. Any ideas/help appreciated.

You should have followed this guide :
http://forum.xda-developers.com/showthread.php?t=2044645
It's newer and much easier. Now for the problem at hand, run the v18f exe file from the above guide. That should fix the issue you have then be able to get to any rom from there. Make sure you follow the guide precisely.
Sent from my LG-P930 using xda app-developers app

Swetnes said:
You should have followed this guide :
http://forum.xda-developers.com/showthread.php?t=2044645
It's newer and much easier. Now for the problem at hand, run the v18f exe file from the above guide. That should fix the issue you have then be able to get to any rom from there. Make sure you follow the guide precisely.
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the reply. I actually was able to just use the LG update on it's own to get ICS back, though the phone isn't rooted anymore.
At some point I did try the tutorial you sent but it wouldn't let me get into recovery mode, it gave me the error I mentioned. I'm just wondering though, if I use that tutorial again, will it work with ICS and v20f? Also, by the end of it what will i get? a rooted phone with Gingerbread? (sorry if they're stupid questions, I'm still learning).

hellored said:
Thanks for the reply. I actually was able to just use the LG update on it's own to get ICS back, though the phone isn't rooted anymore.
At some point I did try the tutorial you sent but it wouldn't let me get into recovery mode, it gave me the error I mentioned. I'm just wondering though, if I use that tutorial again, will it work with ICS and v20f? Also, by the end of it what will i get? a rooted phone with Gingerbread? (sorry if they're stupid questions, I'm still learning).
Click to expand...
Click to collapse
You got that error because you tried to install CWM with the ICS boot loader still installed. The link I provided has you install v18f so it can be rooted and them use the program to keep root so you can downgrade to Gingerbread so CWM can be installed.
One more thing: if all you want is root but don't care about installing another ROM use this to root v20c and stay 100% stock other than root: http://forum.xda-developers.com/showthread.php?t=1886460
Sent from my LG-P930 using xda app-developers app

Swetnes said:
You got that error because you tried to install CWM with the ICS boot loader still installed. The link I provided has you install v18f so it can be rooted and them use the program to keep root so you can downgrade to Gingerbread so CWM can be installed.
One more thing: if all you want is root but don't care about installing another ROM use this to root v20c and stay 100% stock other than root: http://forum.xda-developers.com/showthread.php?t=1886460
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
Okay, I get it. I think I might've missed a step somewhere along the line or something. However, as you said, I really just want to root to give myself the super user ability/app since I find it helpful. I did try the link you provided before and now again but it won't work. First of all I have v20f not v20c (is that why?). Second, I choose normal mode, and then it tells me to look at my phone and click restore. My phone shows a window saying "Restore my data" and "Do not restore" but also asks for a password. Since I don't think I have a password I click on Restore my data (and leave those field blank). My phone says "Restore Starting"...then it says "Restore ended" (within a few seconds) but the Bin4ry bat file won't move on to the next step. It just stays at "Running..." Any ideas?

hellored said:
Okay, I get it. I think I might've missed a step somewhere along the line or something. However, as you said, I really just want to root to give myself the super user ability/app since I find it helpful. I did try the link you provided before and now again but it won't work. First of all I have v20f not v20c (is that why?). Second, I choose normal mode, and then it tells me to look at my phone and click restore. My phone shows a window saying "Restore my data" and "Do not restore" but also asks for a password. Since I don't think I have a password I click on Restore my data (and leave those field blank). My phone says "Restore Starting"...then it says "Restore ended" (within a few seconds) but the Bin4ry bat file won't move on to the next step. It just stays at "Running..." Any ideas?
Click to expand...
Click to collapse
Ok now we are getting somewhere. First of all v20(x) doesn't matter. If it hangs on you saying "running" just close the "command" window, and try again. The couple of times I have tried it it has always done that the first time but then worked the second or third time. It is at that point the phone is supposed to reboot. Good luck.
Sent from my LG-P930 using xda app-developers app

Swetnes said:
Ok now we are getting somewhere. First of all v20(x) doesn't matter. If it hangs on you saying "running" just close the "command" window, and try again. The couple of times I have tried it it has always done that the first time but then worked the second or third time. It is at that point the phone is supposed to reboot. Good luck.
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
First off, thanks for keeping up with me. Well, after like the fifth try, using a way of opening the bat file through cmd manually (not sure how it's any different) I actually got it to say "Successful" and it actually rebooted my device!!...However, it then said something like "Permission denied (are you root?)" or mount failed. So although the file said at the end that my root was successful, I realize it really wasn't and I even made sure; I don't have super user or anything and even root check doesn't say I'm rooted.
I tried it one more time after, but again, it wouldn't reboot. So I tried it again and this time after clicking Restore, I unplugged and plugged my USB. It did say "success" and rebooted my device, though again, the same "mount" error came up and my device isn't rooted.
Any ideas??

Two questions: first what version of windows? Second how are you launching the bat file?
Sent from my LG-P930 using xda app-developers app

I have Windows 7 64 bit and initially I just launched the bat file but double clicking it/opening it normally. However, as I mentioned, the one time it did work I opened the file using this method: youtube . com/ watch?v=7EpkrCq1gfM (all you do is launch the bat file 'manually' more or less by opening cmd prompt then directing it to the folder with the bat file, then running the bat file)

Okay I will thing you might try.... Copy the bat file along with the stuff folder to c:\. This is a wild stab in the dark but under Windows 7 the root folder has different permissions than sub folders and then just double click on the bat file from there.
If you are still having issues use this process: http://forum.xda-developers.com/showthread.php?t=2044645
Basically you get the ICS leak v18f use the tpsparky method to root then using the keep root method to keep root while you upgrade to v20f.
Sent from my LG-P930 using xda app-developers app

Tried moving it to c:\ but same error "cannot mount" or whatever.
Swetnes said:
...
Basically you get the ICS leak v18f use the tpsparky method to root then using the keep root method to keep root while you upgrade to v20f.
...
Click to expand...
Click to collapse
Does this mean you're suggesting I just do the whole guide all over again or do you mean I can just stop at some step?

hellored said:
Tried moving it to c:\ but same error "cannot mount" or whatever.
Does this mean you're suggesting I just do the whole guide all over again or do you mean I can just stop at some step?
Click to expand...
Click to collapse
You can follow the whole guide if you want to install CWM. However if you use v20f as your kdz file or any other ics kdz this will accomplish what you want.... Rooted ics. Do you have the kdz file for v20f? Or another way to look at it is the whole purpose of the before and after bat files is to maintain root when going from one rom to another. You don't have to go to Gingerbread only if you want to install CWM.
I just wish I knew why you were having to many issues.... Try this open a windows command prompt and go to the stuff folder and type the following command:
adb device
What do you get back in response?
Sent from my LG-P930 using xda app-developers app

Swetnes said:
You can follow the whole guide if you want to install CWM. However if you use v20f as your kdz file or any other ics kdz this will accomplish what you want.... Rooted ics. Do you have the kdz file for v20f? Or another way to look at it is the whole purpose of the before and after bat files is to maintain root when going from one rom to another. You don't have to go to Gingerbread only if you want to install CWM.
...
Click to expand...
Click to collapse
O, okay, I see. Well ya, at this point I just want rooted ICS...which I did have before, I just couldn't get into recovery mode as mentioned. But it seems I need to get gingerbread for that...is that right? That's why I got this error before:
---------------
Secure booting Error!
Cause : boot certification verify
-------------------------
------------------------------
Enter the fastboot...
Enter the fastboot...
Long time no see!
-------------------------------------------------
It meant that even though I had it rooted, because I had ICS it couldn't go into recovery?
As for V20f kdz, I found this thread which seems to give it to you: forum.xda-developers . com/showthread.php?t=2073620 (right?)
Swetnes said:
....
I just wish I knew why you were having to many issues.... Try this open a windows command prompt and go to the stuff folder and type the following command:
adb device
What do you get back in response?
...
Click to expand...
Click to collapse
It gives me the "List of devices attached:" and then under it my device code.

hellored said:
O, okay, I see. Well ya, at this point I just want rooted ICS...which I did have before, I just couldn't get into recovery mode as mentioned. But it seems I need to get gingerbread for that...is that right? That's why I got this error before:
---------------
Secure booting Error!
Cause : boot certification verify
-------------------------
------------------------------
Enter the fastboot...
Enter the fastboot...
Long time no see!
-------------------------------------------------
It meant that even though I had it rooted, because I had ICS it couldn't go into recovery?
As for V20f kdz, I found this thread which seems to give it to you: forum.xda-developers . com/showthread.php?t=2073620 (right?)
It gives me the "List of devices attached:" and then under it my device code.
Click to expand...
Click to collapse
I literraly had this exact error on my p930 2 days ago when a tried installing CWM for the first time. the only way i was able to unbrick the phone was following this guide.
http://forum.xda-developers.com/showthread.php?t=1784709&page=4
if you have any questions you can ask me, i just did it on my phone so i should be able to answer unless you run into a problem i didn't

At what stage do you get the secure boot error? Is it after v18f is rooted and you are doing the before and after bat files with. KDZ file?
Sent from my LG-P930 using xda app-developers app

Swetnes said:
At what stage do you get the secure boot error? Is it after v18f is rooted and you are doing the before and after bat files with. KDZ file?
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
if his problem happened the same as mine after trying to boot into cwm for the first time you get the error, becuase lg has a secure bootloader. after this i had to follow the unbrick guide, eventually you end up with at&t stock rom, then you are able to boot into cwm and install a custom rom like CM

One thing just occurred to me you need to stop at step 18 on the unbricking guide. If the KDZ that you are using is one of the v20(x)_00.kdz variants do not use adb to push the recovery.img file this WILL brick your phone and cause the secure boot error this is used to push recovery onto v10(x)_00.kdz only.
Sent from my LG-P930 using xda app-developers app

KronicSkillz said:
I literraly had this exact error on my p930 2 days ago when a tried installing CWM for the first time. the only way i was able to unbrick the phone was following this guide.
http://forum.xda-developers.com/showthread.php?t=1784709&page=4
if you have any questions you can ask me, i just did it on my phone so i should be able to answer unless you run into a problem i didn't
Click to expand...
Click to collapse
Okay thanks, I will try this guide once I get the chance and report back to you. Just a question though, I'm assuming this guide will still give me Gingerbread at the end of it, correct?
Swetnes said:
One thing just occurred to me you need to stop at step 18 on the unbricking guide. If the KDZ that you are using is one of the v20(x)_00.kdz variants do not use adb to push the recovery.img file this WILL brick your phone and cause the secure boot error this is used to push recovery onto v10(x)_00.kdz only.
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
Um, you mean stop at step 18 of the original guide you linked me or the one that KronicSkillz is suggesting? I honestly just use whatever the guide says/provides, I don't bring in any outside files. Previously I mentioned I might use another one because you suggested it would work well for me by keeping ICS. But originally I just follow the guides step by step.

hellored said:
Okay thanks, I will try this guide once I get the chance and report back to you. Just a question though, I'm assuming this guide will still give me Gingerbread at the end of it, correct?
Um, you mean stop at step 18 of the original guide you linked me or the one that KronicSkillz is suggesting? I honestly just use whatever the guide says/provides, I don't bring in any outside files. Previously I mentioned I might use another one because you suggested it would work well for me by keeping ICS. But originally I just follow the guides step by step.
Click to expand...
Click to collapse
At the end you'll end up with AT&T stock gingerbread. in the middle you'll be running a stock korean rom, but that is temporary.
as per your 2nd comment if you resintall stock ICS that will rebrick your recovery and CWM will cause another error if you ever try to run it.
this is the reason your phone had the errors you posted
Secure booting Error!
Cause : boot certification verify
-------------------------
------------------------------
Enter the fastboot...
Enter the fastboot...
Long time no see!
If the whole purpose behind this is you just want ICS why didn't you just run the LG update tool, STOCK ICS can be updated with their stock PC usb tool.
anyways its too late for that.
to save your phone you have to follow that guide to restore it to original AT&T Gingerbread. then you perform a backup with CWM and THEN you can flash whatever ROM you want on your phone be it custom or Stock ICS. I have a feeling flashing the stock ics might rebrick your recovery though. not 100% sure on if it will or not.
---------- Post added at 01:24 PM ---------- Previous post was at 01:22 PM ----------
as per your question about which guide, i think we both linked you the same guide, except the one i linked was the Sticky version that was a little more detailed (i think) but in either case you should pick one guide and stick to it don't read both of them and go back and fourth you could get easily confused even though like i said i think they are the same guide/method of unbricking. There is a reason though that the guide i linked is the TOP STICKY on the forums for this phone. Because it is the solution to unbrick all p930s who have gotten bricked, which is almost anyone who updated their phone since they bought it, a few ppl got lucky and had Roms old enough that LG hadn't locked their recovery yet and they didn't get the error you were seeing.

The only reason I suggested stopping at step 18 was because it seemed like the v20f kdz file was being installed instead of the v10f because of the secure boot error. V20f is ICS, there is no logical reason why v10f is generating the error. Which kdz file are you flashing during that step in the guide?
Sent from my LG-P930 using xda app-developers app