Related
As Lg optimus net have not proper section and as it is successor of o1. I think its right place to post this thread.
After searching and trying many forums over 2-3weeks i m able to root my phone successfully. As there is not a single forum here to root this phone i want to make one, to help those searching for this.
i thanks to "g0mezz " whose method for rooting another phone worked for mine too
First of all there are a couple of things that you have to consider before starting to root.
1. Be sure that you have installed the original V20B o v10c version software on rom. I have tested on these two.
2. If you have it installed and tried different methods to root on it do a factory reset before trying this one.
3. Be absolutely sure that you have all the drives installed when working with the phone in USB debugging mode, if not install them.
4. Download SuperOneClickv1.9.5-ShortFuse or later version( i used 1.9.5) , after download extract the files into a folder with the same name as the archive.
5. After you extracted the files, go to C:\Windows\System32 and copy the cmd.exe to the ADB folder where you extracted the files, in my case C:\Users\myuser\Desktop\SuperOneClickv1.9.5-ShortFuse\ADB.
6. Enable USB Debugging mode (Enter the phone settings menu>Application> Development and tick the USB debugging mode) and then connect phone to pc via usb cable. (DONT PRESS USB STORAGE) .
7. right click on cmd.exe from the ADB folder, Run as administrator, than write:
adb devices (press enter)(after this command you should see your device id)
adb shell (press enter) (after this command you should see $)
$ echo 1 > /data/local/lge_adb.conf, (press enter)
Do not close the window, live it like that.
8. Start SuperOneClick.exe, leave the settings to the SuperOneClick as they are when it opens, click on ROOT and wait, it will say Starting ADB server..., than it will do it's job and than it will appear Waiting for device... it will say ok and that if it freezes while running psneuter do the following:
a. Turn USB Debugging OFF(DO NOT DISCONNECT CABLE) wait until it will appear in the window again Starting ADB server... after that
b. Turn USB Debugging ON and after this trick it will start rooting.
After this it will ask you to reboot the phone, DO NOT FORGET, and after the reboot click on the SuperUser icon in the phone's menu. it will aks you if you allow or deny it's access. click allow. After this you must connect to the internet via Wireless or a apn, click on the superuser icon again if you exit it, go to settings, scroll down and you will see Su Binary v.XXXX, click on that to update it, than go to market and search the super user app and update it.
Also update busy box.
IF this doesn't work do a factory reset and again repeat these steps.
if this guide works for you do post replies and ...... dont forget to press thanks button
Doesn't seem 2 work. Keeps getting stuck at the point "Running psneuter" and gets stuck. Tried closing debugging and all that but it still gets stuck. Reset it 3 times still no result.
---------- Post added at 02:38 AM ---------- Previous post was at 02:13 AM ----------
Did it!! Yes!! For those who might not be able its very important that in the cmd u write like this:
adb shell (enter)
$ echo 1 > /data/local/lge_adb.conf
Give the exact spaces!! And it worked!!! (Space between echo 1 > /data ... like that)
Chowder93 said:
Doesn't seem 2 work. Keeps getting stuck at the point "Running psneuter" and gets stuck. Tried closing debugging and all that but it still gets stuck. Reset it 3 times still no result.
---------- Post added at 02:38 AM ---------- Previous post was at 02:13 AM ----------
Did it!! Yes!! For those who might not be able its very important that in the cmd u write like this:
adb shell (enter)
$ echo 1 > /data/local/lge_adb.conf
Give the exact spaces!! And it worked!!! (Space between echo 1 > /data ... like that)
Click to expand...
Click to collapse
Yep you have to follow these instruction correctly i have metioned these spaces so .. if u r having problem rooting by this method afrer following these steps correctly then rply.. and also post your rply if u successfully rooted using this....
.
thanks for the guide...i did it...but there is one thing i needed most..this so called tun.ko module to be needed in connecting vpn..is there any one have tried this???
Did u install any custom roms?
Sent from my Optimus Net using XDA Premium.
vicfirth_23 said:
thanks for the guide...i did it...but there is one thing i needed most..this so called tun.ko module to be needed in connecting vpn..is there any one have tried this???
Click to expand...
Click to collapse
no i didnt tried it.....
Chowder93 said:
Did u install any custom roms?
Sent from my Optimus Net using XDA Premium.
Click to expand...
Click to collapse
i didnt find any cw mod recovery for this phone so i didnt tried to install any other rom... but i think cwm recovery of optimus one will also work for this phone... i will try it later on...
I haven't tried installing custom roms in my phone.. some forums said that cfw have stock tun.ko module, a module needed to run the vpn application.
I saw a optimus net CWM installation process.
Sent from my Optimus Net using XDA Premium.
Found it:
http://forum.xda-developers.com/showthread.php?t=1354387
Sent from my Optimus Net using XDA Premium.
still waiting for any feedbacks thanks to TS
LlewoR said:
still waiting for any feedbacks thanks to TS
Click to expand...
Click to collapse
It worked man!! It worked on mine
What exactly is meant by
"Be absolutely sure that you have all the drives installed when working with the phone in USB debugging mode, if not install them."
It means the adb drivers.
is there any development on this like custom rom?im planning to root my phone using this method
is there any development on this like custom rom?im planning to root my phone using this method
Click to expand...
Click to collapse
Yep! There are Custom Roms. I have already flashed one
You Can find em here:-
http://www.androidworld.it/forum/lg-optimus-net-p690-187/
There are only a few but there will be more soon.
thanks for reply mate
thank you sir it works
Did It work??
Chowder93 said:
Did It work??
Click to expand...
Click to collapse
chowder where did you get you custom rom and kernel?maybe you can share it too and its that the best rom for you?thanks in advance
please do keep in touch with this thread hehehe
This tool will root your device based on my qemu local.prop root method.
Just download and unzip everything into a directory; then run RootQemu.bat from that directory (if you do not currently have the device drivers for your device, they are attached to this post, please install them, please use them to install your device before attempting the process).
A video with how to do this is available here http://forum.xda-developers.com/showthread.php?p=31728742
Neither ADB nor the SDK need to be installed as all needed files are included in the attachments below (though it won't hurt anything if they are).
Helpful tip:
Make sure no other Android device is connected to your PC
Latest Supported Versions:
v7.1.5
Recent user reported supported version
v7.2.1
Awesome, want to try it when I receive my HD 7 this week...
Wrong thread sorry about that
Works perfectly. Thank you!
Sent from my KFTT using XDA Premium HD app
sparkym3 said:
This tool will root your device based on my qemu local.prop root method.
Just download and unzip everything into a directory; then run RootQemu.bat from that directory (if you do not currently have the device drivers for your device, they are attached to this post, please install them, please use them to install your device before attempting the process).
A video with how to do this is available here http://forum.xda-developers.com/showthread.php?p=31728742
Neither ADB nor the SDK need to be installed as all needed files are included in the attachments below (though it won't hurt anything if they are).
Helpful tip:
Make sure no other Android device is connected to your PC
Click to expand...
Click to collapse
Hi sparkym3!
Thanks for your tools!
I love your tools in TF300 and TF700!
One questions about TF300, do you know anything about the APX mode and useful tools in APX mode?
---------- Post added at 06:41 PM ---------- Previous post was at 06:05 PM ----------
sparkym3 said:
This tool will root your device based on my qemu local.prop root method.
Just download and unzip everything into a directory; then run RootQemu.bat from that directory (if you do not currently have the device drivers for your device, they are attached to this post, please install them, please use them to install your device before attempting the process).
A video with how to do this is available here http://forum.xda-developers.com/showthread.php?p=31728742
Neither ADB nor the SDK need to be installed as all needed files are included in the attachments below (though it won't hurt anything if they are).
Helpful tip:
Make sure no other Android device is connected to your PC
Click to expand...
Click to collapse
Hello, sparkym3!
Is there some mistake in the tool? Both the step 3 and step 5 are the same...
Code:
Step3:Checking for access...
type isroot | adb shell | find "#"
if %errorlevel% == 1 goto NOTROOT
Code:
Step5:Checking superuser...
type isroot | adb shell | find "#"
if %errorlevel% == 1 goto NOTROOT
padest.com said:
Hi sparkym3!
Thanks for your tools!
I love your tools in TF300 and TF700!
One questions about TF300, do you know anything about the APX mode and useful tools in APX mode?
---------- Post added at 06:41 PM ---------- Previous post was at 06:05 PM ----------
Hello, sparkym3!
Is there some mistake in the tool? Both the step 3 and step 5 are the same...
Code:
Step3:Checking for access...
type isroot | adb shell | find "#"
if %errorlevel% == 1 goto NOTROOT
Code:
Step5:Checking superuser...
type isroot | adb shell | find "#"
if %errorlevel% == 1 goto NOTROOT
Click to expand...
Click to collapse
Both of those lines are checking for the "#" instead of the "$" to ensure that it has root access.
reverendkjr said:
Both of those lines are checking for the "#" instead of the "$" to ensure that it has root access.
Click to expand...
Click to collapse
Thanks.
I get it.
ADB is unresponsive
androitri said:
Awesome, want to try it when I receive my HD 7 this week...
Click to expand...
Click to collapse
I picked up the downloads for the Qmenuroot. Installed the ADB drivers referred to in the OP. In my Win7 system's devices manager, I see the ADB driver for the Kindle Fire HD listed as working correctly. Also, the USB driver is in & working, and I can transfer files to/from the kindle. (though I had to re-install the USB driver after I installed the ADB driver)
The problem now is that when I type "ADB devices", it tells me that there are no devices available. Unplug/plug in the USB connection, wait for a bit, "ADB kill-server", "ADB devices" and still no devices available. I have a CMD prompt open in the correct directory. Tried rebooting the kindle, unplug/plug in the USB connector, all kinds of combinations.
I'd like to root this, in anticipation of a JB build for it, (or even ICS) but without ADB, I don't see how.
Has anyone had an issue like this that they have solved? I haven't mastered ADB in any sense, though I've used it to good effect before to un-brick my TF101.
TIA;
Patrick
---------- Post added at 09:35 AM ---------- Previous post was at 08:39 AM ----------
PMcHargue said:
I picked up the downloads for the Qmenuroot. Installed the ADB drivers referred to in the OP. In my Win7 system's devices manager, I see the ADB driver for the Kindle Fire HD listed as working correctly. Also, the USB driver is in & working, and I can transfer files to/from the kindle. (though I had to re-install the USB driver after I installed the ADB driver)
The problem now is that when I type "ADB devices", it tells me that there are no devices available. Unplug/plug in the USB connection, wait for a bit, "ADB kill-server", "ADB devices" and still no devices available. I have a CMD prompt open in the correct directory. Tried rebooting the kindle, unplug/plug in the USB connector, all kinds of combinations.
I'd like to root this, in anticipation of a JB build for it, (or even ICS) but without ADB, I don't see how.
Has anyone had an issue like this that they have solved? I haven't mastered ADB in any sense, though I've used it to good effect before to un-brick my TF101.
TIA;
Patrick
Click to expand...
Click to collapse
got it. My file,
"C:\Users\<your username>\.android\adb_usb.ini"
now hjas the line in it,
"# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x1949"
And that allowed ADB to see the KFHD7
PMcHargue said:
I picked up the downloads for the Qmenuroot. Installed the ADB drivers referred to in the OP. In my Win7 system's devices manager, I see the ADB driver for the Kindle Fire HD listed as working correctly. Also, the USB driver is in & working, and I can transfer files to/from the kindle. (though I had to re-install the USB driver after I installed the ADB driver)
The problem now is that when I type "ADB devices", it tells me that there are no devices available. Unplug/plug in the USB connection, wait for a bit, "ADB kill-server", "ADB devices" and still no devices available. I have a CMD prompt open in the correct directory. Tried rebooting the kindle, unplug/plug in the USB connector, all kinds of combinations.
I'd like to root this, in anticipation of a JB build for it, (or even ICS) but without ADB, I don't see how.
Has anyone had an issue like this that they have solved? I haven't mastered ADB in any sense, though I've used it to good effect before to un-brick my TF101.
TIA;
Patrick
---------- Post added at 09:35 AM ---------- Previous post was at 08:39 AM ----------
got it. My file,
"C:\Users\<your username>\.android\adb_usb.ini"
now hjas the line in it,
"# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x1949"
And that allowed ADB to see the KFHD7
Click to expand...
Click to collapse
Interesting, I don't even have that file. I assume it is used to block devices so you could have one plug in for charging and ADB would just ignore it if it is not in the list.
Thanks, sparkym3
After I verified that ADB could see the KFHD7, I ran the 'RootQemu.bat' that was part of what you published. While it took a bit of time (about 1 minute) between reboots, it worked flawlessly. The Kindle Fire HD 7" I have is now rooted. I'll be looking next to replace the launcher, (probably Apex) and scrape the ads off of this.
Pat
Thanks
Thank you so much for this... really makes it easy and fast. However i was worried during the installation haha my device kept rebooting and it warning me to reconnect so i thought i was doing it wrong.
Well it seems that I messed up. Big time.
I got to step 3, and that's where all hell breaks loose. I get message on the cmd window which reads Cannot find specified file, and everything goes downhill from there. There's no more updating whatsoever. But that's not the bad part, I tried messing around with my kindle, and everything is now incredibly slow. The lag is unbearably bad. I'm in process of resetting everything to factory default at this moment.
EDIT: Just reset to factory default, everything is smooth again, but be careful when trying this exploit, things can go wrong!
I'm thinking there was something I did wrong, if this seems unfamiliar I'll list the steps I took in trying to manage everything. But I know you're thinking I did this on impulse, hence my low post count, but I have been lurking the kfhd subforum for a very long time now and have tried my best to educate myself. Sorry.
Vespus said:
I tried messing around with my kindle, and everything is now incredibly slow. The lag is unbearably bad.
Click to expand...
Click to collapse
That’s the result of the entry in /data/local.prop. If you remove that file and reboot, it will fix the lag.
I tried running the tool and it kept getting hung up on step 3, telling me something along the lines of file not found. I was able to root using the manual method though.
nvrmore100 said:
That’s the result of the entry in /data/local.prop. If you remove that file and reboot, it will fix the lag.
Click to expand...
Click to collapse
I suppose my method fixed it regardless
I'm thinking the reason my root backfired is because I wasn't as systematic as I should have been. Rooting my samsung vibrant allowed me to be a little more sloppy since there are backups and flashing is a cinch.
EDIT: This my 3rd time trying to get this thing to work, I get stuck on Step 3 "The system cannot find the file specified."
I really can't see how I'm managing to screw up this badly. Must be something stupid on my part.
EDIT2: Turns out I was using a crumby network directory the whole time, but even still it did not work. Fellows: Put the QemuRoot folder somewhere on your desktop, it's easier there. But after that the prompt would close immediately after step 4, so that took me a while to circumvent. Anyway, I ended up skipping to step 4 to get the superuser to work. I'm fairly sure everything DOES work, but it's hard to test right now.
PMcHargue said:
I picked up the downloads for the Qmenuroot. Installed the ADB drivers referred to in the OP. In my Win7 system's devices manager, I see the ADB driver for the Kindle Fire HD listed as working correctly. Also, the USB driver is in & working, and I can transfer files to/from the kindle. (though I had to re-install the USB driver after I installed the ADB driver)
The problem now is that when I type "ADB devices", it tells me that there are no devices available. Unplug/plug in the USB connection, wait for a bit, "ADB kill-server", "ADB devices" and still no devices available. I have a CMD prompt open in the correct directory. Tried rebooting the kindle, unplug/plug in the USB connector, all kinds of combinations.
I'd like to root this, in anticipation of a JB build for it, (or even ICS) but without ADB, I don't see how.
Has anyone had an issue like this that they have solved? I haven't mastered ADB in any sense, though I've used it to good effect before to un-brick my TF101.
TIA;
Patrick
---------- Post added at 09:35 AM ---------- Previous post was at 08:39 AM ----------
got it. My file,
"C:\Users\<your username>\.android\adb_usb.ini"
now hjas the line in it,
"# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x1949"
And that allowed ADB to see the KFHD7
Click to expand...
Click to collapse
That's right! I have tested!
This is needed!!!
Thank you for work and contribution.
Thanks for the tip
"C:\Users\<your username>\.android\adb_usb.ini"
now hjas the line in it,
"# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x1949"
worked!
KF HD has Superuser but no root access
sparkym3 said:
This tool will root your device based on my qemu local.prop root method.
Just download and unzip everything into a directory; then run RootQemu.bat from that directory (if you do not currently have the device drivers for your device, they are attached to this post, please install them, please use them to install your device before attempting the process).
A video with how to do this is available here http://forum.xda-developers.com/showthread.php?p=31728742
Neither ADB nor the SDK need to be installed as all needed files are included in the attachments below (though it won't hurt anything if they are).
Helpful tip:
Make sure no other Android device is connected to your PC
Click to expand...
Click to collapse
Hi sparkym3
Thanks for all your hard work! I tried it though and it went through all the motions as if it was doing its job, like expected. But at the end of the rooting, I have superuser on the kf HD but no root access! ES explorer and Titanium have no root access. Tried rebooting several times. Still no root access. What could have gone wrong?
Cheers, mate!
Hello,
I bought a used galaxy nexus S that is on version 2.3.6.
It does not seem to be reading any sim cards and the baseband version is listed as unknown.
I think it may be on a custom rom because of this. I want to flash it back to a stock rom but have no idea where to start. I downloaded 4.1.1
the google site. which I can`t link to because I am new here..
my nexus s is I9020A so i downloaded that version of jellybean but have no idea where to go from here.
Are there any easy to follow guides? And am I even on the right track here?
sackling said:
Hello,
I bought a used galaxy nexus S that is on version 2.3.6.
It does not seem to be reading any sim cards and the baseband version is listed as unknown.
I think it may be on a custom rom because of this. I want to flash it back to a stock rom but have no idea where to start. I downloaded 4.1.1
the google site. which I can`t link to because I am new here..
my nexus s is I9020A so i downloaded that version of jellybean but have no idea where to go from here.
Are there any easy to follow guides? And am I even on the right track here?
Click to expand...
Click to collapse
just follow this tutorial (need drivers, 5 min, and bootloader unlocked):
http://forum.xda-developers.com/showthread.php?t=1572307
to get fastboot working and learn some simple commands (just do the install drivers part):
http://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s-or-nexus-s-4g-new/
video showing it works:
http://www.youtube.com/watch?v=K4DePKyRgvU&list=UUTsL8yOHOK7IUQl2tsKId5A&index=1&feature=plcp
if this worked hit thanks
Cascabreu said:
just follow this tutorial (need drivers, 5 min, and bootloader unlocked):
http://forum.xda-developers.com/showthread.php?t=1572307
to get fastboot working and learn some simple commands (just do the install drivers part):
http://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s-or-nexus-s-4g-new/
video showing it works:
http://www.youtube.com/watch?v=K4DePKyRgvU&list=UUTsL8yOHOK7IUQl2tsKId5A&index=1&feature=plcp
if this worked hit thanks
Click to expand...
Click to collapse
Thank you. I am already confused at step 5 of installing the SDK though. which is:
5 - Once you're finished go to your SDK installation "extras\google\usb_driver" dir
Where exactly is the folder extras?
sackling said:
Thank you. I am already confused at step 5 of installing the SDK though. which is:
5 - Once you're finished go to your SDK installation "extras\google\usb_driver" dir
Where exactly is the folder extras?
Click to expand...
Click to collapse
Never mind found the folder.
Now I am not sure what the step turn of SNS means?
sackling said:
Thank you. I am already confused at step 5 of installing the SDK though. which is:
5 - Once you're finished go to your SDK installation "extras\google\usb_driver" dir
Where exactly is the folder extras?
Click to expand...
Click to collapse
got to local disk (root of your dirver) and u will see: android-sdk-windows
click and u will see extras
i will make a couple of screen captures to show you how to set it up the foloders and commands. wait a couple of minutes
Cool thanks!
I still don't understand what SNS stands for?
Google says social networking services... but step 8 is: Make sure the SNS is connected to the PC via the USB cable
So I doubt that..
here they are
read carefully the last image (i wrote some tips in the command window)
looks like SNS just means the phone somehow..
sackling said:
Cool thanks!
I still don't understand what SNS stands for?
Google says social networking services... but step 8 is: Make sure the SNS is connected to the PC via the USB cable
So I doubt that..
Click to expand...
Click to collapse
stop after installing google sdk, just plug your nexus in fastboot mode (turn off device, vol+ and power). then go to device manager (type in the search box, windows 7 or 8). and u will see android 1 (with exclmation mark). right click, update drivers, browse my pc, go to file nexussrootnew or got to sdk-extras-usb drivers, click "let me pick from a list...", chose all devices and install "adb android ...." dont know the right name. then u can go forward to the commands and install sotck images
Cascabreu said:
stop after installing google sdk, just plug your nexus in fastboot mode (turn off device, vol+ and power). then go to device manager (type in the search box, windows 7 or 8). and u will see android 1 (with exclmation mark). right click, update drivers, browse my pc, go to file nexussrootnew or got to sdk-extras-usb drivers, click "let me pick from a list...", chose all devices and install "adb android ...." dont know the right name. then u can go forward to the commands and install sotck images
Click to expand...
Click to collapse
Ok So when updating the driver, and I click all devices I have a huge list with a ton of manufacturers.
Which manufacturer do I choose?
sackling said:
Ok So when updating the driver, and I click all devices I have a huge list with a ton of manufacturers.
Which manufacturer do I choose?
Click to expand...
Click to collapse
samsung XD or google (best)
but dont choose all devices go back and check for android deivce
edit: step by step pics uploading!
Cascabreu said:
samsung XD or google (best)
but dont choose all devices go back and check for android deivce
edit: step by step pics uploading!
Click to expand...
Click to collapse
I don't see either... When I choose the USB_driver dirctory when I browse for driver software, it doesnt seem to really "go to that folder" posted the picture..
Right after i choose that folder I click the let me pick from a list of devices below.. Is that correct?
sackling said:
I don't see either... When I choose the USB_driver dirctory when I browse for driver software, it doesnt seem to really "go to that folder" posted the picture..
Right after i choose that folder I click the let me pick from a list of devices below.. Is that correct?
Click to expand...
Click to collapse
YES SIR! u are a good student lmao!
edit: pics are almost finished (sorry but im using my tethering network=slow)
Don't forget to hit thanks, you're getting a great tutorial
some pics step by sptep to help!!!! (at the 6 step it appear asus android device but dont care about that, just search for the words android devices, nexus devices are universal they work with all drivers)
never mind clicked have disc after clicking all devices! Now I have a list of 3
I installed ADB one..
What do you mean go forward with the commands?
sackling said:
never mind clicked have disc after clicking all devices! Now I have a list of 3
I installed ADB one..
What do you mean go forward with the commands?
Click to expand...
Click to collapse
wait 5 min a i will post some pics with step by step to install jellybean via fastboot (=command prompt) OKI?
Cascabreu said:
wait 5 min a i will post some pics with step by step to install jellybean via fastboot (=command prompt) OKI?
Click to expand...
Click to collapse
That would be extremely helpful!
Thanks so much.
-put phone on fastboot mode (turn off, vol+ and power)
-plug to pc
-put your nexussrootnew folder in root of your driver (mine is: local disk(C: ) ) and in there put the images downloaded from here:
https://developers.google.com/android/nexus/images (be carefull to download the right image for your phone!!!!!!)
-unzip one time (in that unzip folder u should have a radio file, a bootloader file, a zip folder,and 2 more files that u dont need)
- put the unzip folder on: (C: ) / nexusstooneew
-open a command prompt (click "windows key+r" then type "cmd")
-check the pics and the commands
help understanding pics:
1: win+r and type cmd
2: "cd.." means go back in the previous folder and "cd" means open folder, hit enter to make the command work
now type:
-fastboot oem unlock (will erase all your data) to get your bootloader unlocked and the nexts steps working
- fastboot flash bootloader (drag and drop bootloader.img file)
-fastboot reboot-bootloader (wait 5 secs)
-fastboot flash radio (drag and drop radio.img)
-fastboot reboot-bootloader
-fastboot -w update (drag and drop the zip file wich is in the main folder of the android image that u downloaded) (see 4 pic, the file is hightlighted) ("-w" means full wipe = clean install)
Hey guys,
I try to root my OpO with the XDA Toolbox. When I try to install TWRP or other Recovery I get in the cmd the error:
error: cannot open 'C:/Users/Martin/Documents/Opo'
Click to expand...
Click to collapse
I hope someone can help me.
SirMrMartin
My suggestion is to not use any toolkit and follow the step by step guides available on XDA instead.
Look for timmaaa thread in general section
Step 1 backup everything you want to keep
Step 2 is unlock boot loader (which will wipe your phone clean, that's why step 1 is backup everything lol)
Continue from there using the guide
This way you learn proper commands and the method instead of not knowing wtf you're doing and not knowing how to fix things if you come across any problems.
Cheers
---------- Post added at 07:41 PM ---------- Previous post was at 07:37 PM ----------
Also make sure you know where the files are that you downloaded. My suggestion is desktop make a folder called opo and download everything in there
Google and download "15 second adb installer" that will install the required drivers. So this way you just open command window in the folder (hold shift+ctrl+right click > choose open command prompt here) with all your files and don't need to put files in the SDK folder etc.
Forget the toolkit, they're more trouble than they're worth. Plus, you'll gain valuable experience by doing it yourself, experience that you're gonna need when something goes wrong in future. Check out my guide here:
http://forum.xda-developers.com/showthread.php?t=2839471
Code:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DISCLAIMER
I am not responsible for bricks, cats being both alive and dead, heat death of the universe, etc. I've attempted to minimize the chance of damage, but you will use this guide at your own risk.
Thanks to [mention]ejwith9953[/mention] for getting TWRP working correctly
Thanks to [mention]forgottonhacker[/mention] for proofreading and formatting
ABOUT
WINDOWS ONLY GUIDE
THIS GUIDE IS FOR THE PEOPLE SEEKING TO INSTALL TWRP AND OBTAIN A FIX FOR SOFT-BRICKED DEVICES
STEP 1
On a DESKTOP:
Download CURE_4 and extract to desktop (or a folder to your preference).
[Download Links at Bottom of Post]
On your PHONE:
Go to Settings > About phone > tap build number, till it says your a developer.
Go to Settings > Developer Options and enable OEM unlock, and USB debugging
Reboot Device
STEP 2
Connect Device to PC
Open your extracted folder and run START_HERE.bat
Let it run, it will copy files, execute temp root exploit, and open a new CMD window.
In the new window, copy/paste commands individually.
Code:
adb shell
run-as -s1
su
dd if=/data/local/tmp/twrp.img of=/dev/block/mmcblk0p25
When you see the following:
Code:
26404+0 records in
26404+0 records out
Get ready to pull out the battery ( reboot recovery does NOT work )
Put the battery back in and hold the PWR and VOL UP at the same time, when you see Alcatel splash let go of power but continue to hold volume up.
Say hello to TWRP!
STEP 3
Now we are going to install SuperSU it’s easy from here don’t fret!
IMPORTANT
BACKUP /SYSTEM PARTITION IN TWRP AND MAKE A COPY ON YOUR PC
Now that you have a backup go back and tap install. Tap on "up a level" then sdcard.
Find SuperSu.zip and swipe to install!
Reboot system! (this may take a few minutes so don’t freak out)
Verify that SuperSu got installed.
Go back to the extracted folder on your computer and run CLEANUP.bat
SOFT FIX
Boot up to custom recovery tap wipe > advanced wipe
Select Dalvik cache and Cache, then SWIPE to wipe
Go back to the Home Screen
Tap Advanced > fix permissions and Swipe
REBOOT AND ENJOY
If this fix did not work for you please do contact me as I have another method, I will be putting up a debloated version of the ROM soon.
I will be adding more to the guide, so make sure to turn on your notifications!
DOWNLOADS
Stock-ish ROM EXTRACT FROM ZIP FIRST! then flash as /system
password: fax
Dropbox Google Box.net Mega
EDIT: On payday going to buy another one of these phones for stock firmware.
Reserved
Broken Download Link
The Link to download the Code-4 package is broken, and it makes me oh-so-sad!!! Help!
WowTheDog said:
The Link to download the Code-4 package is broken, and it makes me oh-so-sad!!! Help!
Click to expand...
Click to collapse
try now. also "cure-4" XD
Cure-4 download link not working.
I tried to say...
faxanidu said:
try now. also "cure-4" XD
Click to expand...
Click to collapse
The cure-4 thing is missing again, can we get a hold of that?
Omg everyone flagging as malware give me a bit
Hey, it all worked, I had a soft bricked phone, and its booting now. I did the commands in OSX, I just opened the START_HERE.bat and saw your adb commands. The only hangup was that I couldn't push Supersu.zip to /sdcard/ because it wasn't writable for some reason, but I just pushed it to the tmp path from the other commands instead.
Thanks so much!
Good brother my problem is that I have my soft brick phone and I do not know what to do to revive it, do you have any idea how to repair it?
ericcorp said:
Hey, it all worked, I had a soft bricked phone, and its booting now. I did the commands in OSX, I just opened the START_HERE.bat and saw your adb commands. The only hangup was that I couldn't push Supersu.zip to /sdcard/ because it wasn't writable for some reason, but I just pushed it to the tmp path from the other commands instead.
Thanks so much!
Click to expand...
Click to collapse
Odd it pushes supersu automatically. Might had something to do with the soft brick. Your welcome though! Spread the word!
sanpuyon said:
Good brother my problem is that I have my soft brick phone and I do not know what to do to revive it, do you have any idea how to repair it?
Click to expand...
Click to collapse
Follow guide fixes soft brick also just reboot it. let it sit awhile then plug it in. Should be a able to get ADB shell
faxanidu, I just tried on my dead device and I got twrp :good: but won't complete boot after fixing permission tho. Hey that's good enough for me, congrats on what you did! Just gonna wait till a rom gets put up.
To get started I did have to do some steps in oem recovery like I said from the other thread, otherwise my device shows as unauthorized tho, enable adb, then rock volume back and forth till I get mounted /system, then hit reboot. It seems I've tried just doing one or the other but it would still be unauthorized. Just sayin, and again like I told you I don't really know what I'm doing
Thanks again, and if you have any further advice or tips, I'm all ears
edit: I didn't have supersu show up either but I put it on an sdcard and installed it that way.
i am too afraid to try this, is this safe? if i brick my phone, how do i flash stock firmware
---------- Post added at 03:24 AM ---------- Previous post was at 02:59 AM ----------
faxanidu said:
Good news everyone! I have built a massive guide for the alcatel ideal! install custom recovery and more now! also fix for soft bricked phones! just follow this guide.
WIndows only
Thanks to ejwith9953 with getting TWRP working correctly, he is the bomb!
So dont forget to thank him!
STEP 0
DISCLAIMER! I am not responsible for bricks, cats being both alive and dead, heat death of the universe, etc. Ive minimized the chance of damage as much as possible, but still use this guide at your own risk.
STEP 1Goto settings > about phone > tap build number, till it says your a developer.
Goto settings > developer Options. slide on OEM unlock, and USB debugging
Download CURE_4 to your computer and extract folder to desktop (or somewhere).
Reboot phone.
Links are at bottom!
STEP 2Open your extracted folder, run START_HERE.bat
Let it run, it will copy files, execute temp root exploit, and open a new CMD window.
In the new window type in these codes from top to bottom letting each one finish. ( or copy/paste )
Code:
adb shell
run-as -s1
su
dd if=/data/local/tmp/twrp.img of=/dev/block/mmcblk0p25
When you see:
26404+0 records in
26404+0 records out
your ready to pull out the battery ( reboot recovery does NOT work )
Put the battery back in and hold the PWR and VOL UP at the same time, when you see alcatel let go of power but continue to hold volume up.
Welcome to custom recovery my friends!
STEP 3Now we are going to install SuperSU its easy from here dont fret! but first!
click backup, under partitions uncheck everything EXCEPT system. Now swype to backup.
Now that you have a backup go back and click install. click "up a level" then sdcard.
scroll down and click SuperSu.zip. Swipe to install! Now Reboot system! (this may take a few minutes so dont freak)
check that SuperSu installed, did it? great! go back to the extracted folder on your computer and run CLEANUP.bat
STEP 4 -SOFTFIX ONLYBoot up to custom recovery click wipe > advanced wipe
checkmark Dalvik cache and Cache, the SWIPE to wipe ( sounds dirty )
now click BACK all the way to main screen. now click advanced.
click fix permissions And Swipe. Now REBOOT. hopefully that will boot your phone if not let me know. i dont
have an extra one to purposfully softbrick to test. but ill have a debloated pre rooted ROM for you
to use soon regardless
More to the guide will be coming, for now this is the basics. im going to bed see you all later!
LINKS!
password: fax
Dropbox Google Box.net Mega
EDIT: 4 links encrypted
Click to expand...
Click to collapse
faxanidu said:
Click to expand...
Click to collapse
Thank you! i am now happily running twrp, though with some mods, i rooted with kingroot first then ran the commands
Now we wait for lineage os or cm13
For some reason I can't do this on my working phone. when it comes to the "getting uid" screen, everything that runs says "missing second argument" then I try entering the commands it says "run-as: Package '-s1' is unknown"?
scohut said:
For some reason I can't do this on my working phone. when it comes to the "getting uid" screen, everything that runs says "missing second argument" then I try entering the commands it says "run-as: Package '-s1' is unknown"?
Click to expand...
Click to collapse
What the? Never had that problem can't reproduce plz send screenshot
faxanidu said:
Good news everyone! I have built a massive guide for the alcatel ideal!
Click to expand...
Click to collapse
Thank you so much for this.
I started and misread the text as a lowercase "L" instead of the number one for the "run-as -s1" part of the code. I wasn't sure how to correct it when I got an error, so I started over and ran the START_HERE.bat again. When the new cmd window opens, I can't type anything. It reads:
# Device:Alcatel_4060A
-Getting uid 0->Ok.
-Checking permissive run-as.->Ok
# turn off/on the bluetooth.....................................................
..............←[s←[0;34m
[email protected]:/data/local/tmp #
Click to expand...
Click to collapse
I'm not sure how to start over to get back on track for the adb shell code.
I know, it's pretty bad that I didn't get past the first part of Step 2. Any help is appreciated.
faxanidu said:
What the? Never had that problem can't reproduce plz send screenshot
Click to expand...
Click to collapse
this..
Rush-O-Matic said:
Thank you so much for this.
I started and misread the text as a lowercase "L" instead of the number one for the "run-as -s1" part of the code. I wasn't sure how to correct it when I got an error, so I started over and ran the START_HERE.bat again. When the new cmd window opens, I can't type anything. It reads:
I'm not sure how to start over to get back on track for the adb shell code.
I know, it's pretty bad that I didn't get past the first part of Step 2. Any help is appreciated.
Click to expand...
Click to collapse
That happens rarely just reboot and start again
faxanidu said:
That happens rarely just reboot and start again
Click to expand...
Click to collapse
And it reads what?
scohut said:
this..
Click to expand...
Click to collapse
Looks like exploit.sh for corrupted or something plus if you have any mods like exposed might interfere with it. The script dumps info it need to patch see policy then creates run-as with info.
Edit: I'm basically using dirty cow exploit. Works on everything