Related
EDIT:
I was trying to reflash JB 4.3 because of storage issues but unfortunately I accidentally deleted and formatted internal and sd storage, so Im left with no OS on my Gnex but I can boot on recovery and fastboot. Also before I deleted the internal I did not enable usb debugging yet at that time. Is there a way I can flash a stock image by just using toolkit? ty
I tried pushing through fastboot mode but it says error: device not found. I only have the platform tools on my pc.
UPDATE:
Finally got the file pushed into the sd card doing via recovery. Since I am using TWRP recevery it was not too obvious how to do it unlike CWRM which I used to use. I spent more than 24 hours looking for the right solution that would work for me and funny thing was I finally got the right way to one of the first threads i looked into but just didnt pay much attention to it which was here http://forum.xda-developers.com/showthread.php?t=1667929
"Boot your phone into Recovery and select the "Mounts & Storage" screen
- Plug your phone into your computer using USB Data Transfer Cable
- Ensure in Recovery that your phone shows "Unmount /sdcard/" and "Unmount /system/" (If they do not show this automatically, just press each one once respectively as pressing just toggles Mount and Unmount)
- Open Command Prompt on your computer by doing Start -> Run -> cmd
- In Command Prompt, type "cd c:\AndroidSDK\tools" replacing AndroidSDK\tools with wherever your adb and ROM are located.
- This is probably the most important part - Still in Command Prompt, type "adb push ROM.zip /sdcard/ROM.zip" replacing ROM with the EXACT name of the ROM file and including the .zip piece on both ends. This may take a minute or two...or four, but you will see a message in Command Prompt saying something like <12345678kb to 1234567kb>. That is just telling you that the file was pushed properly. (I did not include that message in the picture below)"
lastforone said:
Instead of using a toolkit, just push a rom to ur sdcard using adb and flash it via recovery.. Or you can download the official image, boot into fastboot and flash it..
-
L4.1
Click to expand...
Click to collapse
You were right on spot unfortunately I didnt know how to do it. Thank you anyways...:highfive::highfive::highfive:
Ty for all those who tried to help me, thank you for the effort, well it was indeed a learning experience... ahihihihi
Instead of using a toolkit, just push a rom to ur sdcard using adb and flash it via recovery.. Or you can download the official image, boot into fastboot and flash it..
-
L4.1
lastforone said:
Instead of using a toolkit, just push a file to ur sdcard using adb and flash it... Or you can download the official image, boot into fastboot and flash it..
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
well then i need to download sdk first ty anyways
lolobabes said:
well then i need to download sdk first ty anyways
Click to expand...
Click to collapse
You do not need the whole sdk package. Just the adb + fastboot and few required files ... You can find the zip in erants guide..
Sent from my Galaxy Nexus using xda app-developers app
when i tried to push error device not found lol
lolobabes said:
when i tried to push error device not found lol
Click to expand...
Click to collapse
Use adb sideload from twrp and send the zip from your PC to your phone.
Sent from my Galaxy Nexus using xda app-developers app
lolobabes said:
when i tried to push error device not found lol
Click to expand...
Click to collapse
Go into your device manager if you have windows, and see if you have any errors.
If you do, you might have an exclamation mark for the device: Galaxy. You can manually install the drivers from here, point it to your toolkit, I guess, since you downloaded it already.
If he reads efrant's "android 101" -which is STICKIED ON GENERAL forum- just the first post, he'll know everything and downloaded everything he needs to know and have to interact with his device.
a manta wrote this.
Beauenheim said:
Go into your device manager if you have windows, and see if you have any errors.
If you do, you might have an exclamation mark for the device: Galaxy. You can manually install the drivers from here, point it to your toolkit, I guess, since you downloaded it already.
Click to expand...
Click to collapse
When I am on recovery yes theres an exclamation on samsung mtp device but in fastboot mode the samsung mtp does not appear but when I do fastboot devices there appears a device number so I thought I can do it on fastboot. thank you.
beekay201 said:
If he reads efrant's "android 101" -which is STICKIED ON GENERAL forum- just the first post, he'll know everything and downloaded everything he needs to know and have to interact with his device.
a manta wrote this.
Click to expand...
Click to collapse
I have read that already however I was hoping to just flash a file to the sdcard if is even possible considering I have formatted both internal and sdcard. I am very new to adb so its an easier way for me. But it seems then I will ave to do it the hard way. Thanks
PS
Not sure if this has any bearing but when I accidentally formated internal and sdcard it was a fresh 4.3 install and so android debugging was not enabled. Thanks
lolobabes said:
PS
Not sure if this has any bearing but when I accidentally formated internal and sdcard it was a fresh 4.3 install and so android debugging was not enabled. Thanks
Click to expand...
Click to collapse
Doesn't matter because if you reboot in bootloader you can use fastboot(if drivers are installed properly), fastboot always works, you don't need to enable anything for it.
sui785 said:
Doesn't matter because if you reboot in bootloader you can use fastboot(if drivers are installed properly), fastboot always works, you don't need to enable anything for it.
Click to expand...
Click to collapse
So meaning I can use fastboot to just push file to sdcard right? Tried to look for the right command but I cant seem to find the right one that works for me. Thank you.
tried doing this in fastboot "adb push romname.zip /sdcard/ROM/" had this error: device not found
lolobabes said:
tried doing this in fastboot "adb push romname.zip /sdcard/ROM/" had this error: device not found
Click to expand...
Click to collapse
Take it out of a USB 3.0 port.
lolobabes said:
tried doing this in fastboot "adb push romname.zip /sdcard/ROM/" had this error: device not found
Click to expand...
Click to collapse
lolobabes said:
So meaning I can use fastboot to just push file to sdcard right? Tried to look for the right command but I cant seem to find the right one that works for me. Thank you.
Click to expand...
Click to collapse
no, there's no ADB interface on FASTBOOT interface. You'll never be able to push anything through ADB in FASTBOOT interface. Please read the thread i talked about earlier, and this one too -> http://forum.xda-developers.com/showthread.php?t=1626895 - Just the first post of each will do.
Beauenheim said:
Take it out of a USB 3.0 port.
Click to expand...
Click to collapse
*EPIC*
*facedesk*
*grows more white hair*
xD I actually had this issue a few days ago, had issues for 4 hours, realized I had my cord plugged in a 3.0 port.
Really dumb noob moment.
UPDATE:
Finally got the file pushed into the sd card doing via recovery. Since I am using TWRP recevery it was not too obvious how to do it unlike CWRM which I used to use. I spent more than 24 hours looking for the right solution that would work for me and funny thing was I finally got the right way to one of the first threads i looked into but just didnt pay much attention to it which was here http://forum.xda-developers.com/showthread.php?t=1667929
"Boot your phone into Recovery and select the "Mounts & Storage" screen
- Plug your phone into your computer using USB Data Transfer Cable
- Ensure in Recovery that your phone shows "Unmount /sdcard/" and "Unmount /system/" (If they do not show this automatically, just press each one once respectively as pressing just toggles Mount and Unmount)
- Open Command Prompt on your computer by doing Start -> Run -> cmd
- In Command Prompt, type "cd c:\AndroidSDK\tools" replacing AndroidSDK\tools with wherever your adb and ROM are located.
- This is probably the most important part - Still in Command Prompt, type "adb push ROM.zip /sdcard/ROM.zip" replacing ROM with the EXACT name of the ROM file and including the .zip piece on both ends. This may take a minute or two...or four, but you will see a message in Command Prompt saying something like <12345678kb to 1234567kb>. That is just telling you that the file was pushed properly. (I did not include that message in the picture below)"
lastforone said:
Instead of using a toolkit, just push a rom to ur sdcard using adb and flash it via recovery.. Or you can download the official image, boot into fastboot and flash it..
-
L4.1
Click to expand...
Click to collapse
You were right on spot unfortunately I didnt know how to do it. Thank you anyways...:highfive::highfive::highfive:
Ty for all those who tried to help me, thank you for the effort, well it was indeed a learning experience... ahihihihi
lolobabes said:
UPDATE:
Finally got the file pushed into the sd card doing via recovery. Since I am using TWRP recevery it was not too obvious how to do it unlike CWRM which I used to use. I spent more than 24 hours looking for the right solution that would work for me and funny thing was I finally got the right way to one of the first threads i looked into but just didnt pay much attention to it which was here http://forum.xda-developers.com/showthread.php?t=1667929
"Boot your phone into Recovery and select the "Mounts & Storage" screen
- Plug your phone into your computer using USB Data Transfer Cable
- Ensure in Recovery that your phone shows "Unmount /sdcard/" and "Unmount /system/" (If they do not show this automatically, just press each one once respectively as pressing just toggles Mount and Unmount)
- Open Command Prompt on your computer by doing Start -> Run -> cmd
- In Command Prompt, type "cd c:\AndroidSDK\tools" replacing AndroidSDK\tools with wherever your adb and ROM are located.
- This is probably the most important part - Still in Command Prompt, type "adb push ROM.zip /sdcard/ROM.zip" replacing ROM with the EXACT name of the ROM file and including the .zip piece on both ends. This may take a minute or two...or four, but you will see a message in Command Prompt saying something like <12345678kb to 1234567kb>. That is just telling you that the file was pushed properly. (I did not include that message in the picture below)"
You were right on spot unfortunately I didnt know how to do it. Thank you anyways...:highfive::highfive::highfive:
Ty for all those who tried to help me, thank you for the effort, well it was indeed a learning experience... ahihihihi
Click to expand...
Click to collapse
I'm glad you sorted it out, that's the thing instead of teaching you step by step just left a hint on what you should do, helps you learn to do it on your own..
Peace,
L4.1
Thanks
Thanks for this. Was stuck with no factory image because had to wipe data because of encryption. Then was in dilemma of how to load the ZIP to sdcard without having to reflash the stock all over. This saved me the time. Thanks again
I've cracked the kindle code for ADB Sideload / Push In TWRP recovery! :highfive:
If you have access to TWRP and nothing else, this is for you.
Like many, I foolishly formatted my internal storage on my Kindle Fire 2 while in TWRP. with no Zips to flash I was stuck trying everything I could think of to get a file onto my Device. Read up on ADB Sideload.. But my PC would not recognize ADB Sideload AT ALL, and I Couldn't Find the Drivers.
Read up on Mounting.. No drivers no mount. Updated my Android SDK, drivers there didn’t work. Almost threw my kindle in the river.
But then I Found A certain set of Drivers from Amazon's support section. (See Attached)
So here's how to get your kindle back: :fingers-crossed:
Download and Extract the driver files. Run the Kindle Drivers. Once the Drivers are finished plug in your kindle fire 2, windows will not recognize it and we need to install the driver manually.
Go to My Computer icon. Right click and select Properties. Open Device manager in the top left.
Your Kindle will show as a yellow triangle Kindle or Kindle Fire Device (or in some cases it will have the wrong driver installed, {right click and uninstall current driver, your PC will have to restart.})
Right Click on Kindle Fire Device> Click Update Driver Software..> Click Browse my computer for Driver software> Click Let Me pick from a list of device drivers on my computer>
NOW {Kindle} will show up on the list a few times, find the one that has: ADNROID COMPOSITE ADB INTERFACE and install this driver for your kindle. If everything worked your kindle fire will now be recognized and install.
NEXT STEP!
Sideload will not work for this, so don’t even try. No SDK is required for this process just the ADB Files (Attached)
Make sure you extract the ADB.zip right onto your C:/ drive to make this easy.
Download any Kindle Fire 2 Rom (Found in Kindle Fire 2 Android Development section, preferably a Small File Size like CM 10.1),
Rename this ZIP to kindle.zip (or another short name)
Download the Gapps File for the version of ROM you just downloaded from Goo.im,
Rename this ZIP to gapps.zip (or another short name)
Place both ZIPs directly into the C:/ADB folder
Open a command prompt by going to Start > Run > CMD and hit enter. A DOS Command prompt will open.
First line will say
C:\USERS\YOURNAME>
Type> CD C:\ADB Now it will change your Directory to the C:\ Drive ADB folder
Ok on your Tablet now in TWRP, Tap MOUNT> next check [x]DATA and [x]System and tap MOUNT USB SYSTEM
Windows will not notify you of the change so don’t freak out.
ADB needs to be at least Version 1.0.29, you can check by typing the command: ADB version
Next type> ADB devices
Will now say>
LIST OF DEVICES ATTACHED:
123456789ABCDEF RECOVERY
(IF it doesn’t say anything under list of devices you will have to uninstall and reinstall the driver in step 1)
Next TYPE> adb push kindle.zip \sdcard\kindle.zip
Wait about 30-40 seconds without touching anything, it will be sending the file.
IT WILL SAY>
3589 KB/s (128302247 bytes in 34.908s) or something similar.
Next Type> adb push gapps.zip \sdcard\gapps.zip
Wait about 30-40 seconds without touching anything, it will be sending the file.
IT WILL SAY>
3262 KB/s (57280392 bytes in 17.143s) or something similar.
BAM! Files are on your device!
BACK TO THE TABLET!
Tap Unmount and click the home icon in the top right.
Click INSTALL and tap (UP A LEVEL) to get to the root of the kindle fire.
Your files should be there Labeled Kindle.zip and Gapps.zip!
Install normally! AND Don’t forget to Wipe your Dalvik/Cache! :good:
All this info is available in the forums here but I'm really glad you did this. It should prevent a lot of redundant questions. Very well written, simplified and explained.
Kudos!
-> Sent from my mind to your screen.
Give a man a fish and you feed him for a day. Teach a man to fish and you feed him for a lifetime.
hi, i am using Chinookgod's method to push the kindle.zip and gapps.zip to my kindle successfully
but when i try to 'swip to confirm flash', it shows 'Failed' ,
and E:Mount: Unable to find partition for path '/\sdcard\kindle.zip'
Error flashing zip '/\sdcard\kindle.zip'
Updating partition details..
below is the screen cap
hxxp://imgur.com/ecjcZZF (please change hxxp to http)
what should i do? plz help :crying:
below is my cmd.exe screen cap, please note that it still shows
LIST OF DEVICES ATTACHED:
123456789ABCDEF RECOVERY
hxxp://imgur.com/WJs4ABY (please change hxxp to http)
Easy.
bon1025hk said:
hi, i am using Chinookgod's method to push the kindle.zip and gapps.zip to my kindle successfully
but when i try to 'swip to confirm flash', it shows 'Failed' ,
and E:Mount: Unable to find partition for path '/\sdcard\kindle.zip'
Error flashing zip '/\sdcard\kindle.zip'
Updating partition details..
below is the screen cap
hxxp://imgur.com/ecjcZZF (please change hxxp to http)
what should i do? plz help :crying:
below is my cmd.exe screen cap, please note that it still shows
LIST OF DEVICES ATTACHED:
123456789ABCDEF RECOVERY
hxxp://imgur.com/WJs4ABY (please change hxxp to http)
Click to expand...
Click to collapse
Thats easy. You can fix this by doing a system wipe then do a factory data reset to prep the system.
Will it work for me?
I got backup of my rom in my sdcard but having the same problem when try to restore. stuck with no OS. Help
My Phone Lg lu6200
Still need help
Chinookgod said:
Thats easy. You can fix this by doing a system wipe then do a factory data reset to prep the system.
Click to expand...
Click to collapse
I tried following your instructions and the directory came up. I then tried entering "adb shell" as a command and got the following:
Doesn't work for my Kindle HD 8.9...any help please?
I get an error closed closed
Chinookgod said:
Thats easy. You can fix this by doing a system wipe then do a factory data reset to prep the system.
Click to expand...
Click to collapse
hi,
i have Kindle Fire HD 7" after some issues i try to flashing, voip all data and delete backup etc, my WTRP V.2.7.8.0 changed to v.2.6.3.1 and stuck in kindle fire logo and not connected to pc or not show storage in my computer.
please help me and restore my kindle fire tate. thanks a lot (i am using Ubuntu 14.04 LTS)
I am not sure if this is the correct forum for this. Moderators, Please feel free to remove it or relocate it
First of all thanks to all amazing people on this forum ( thecubed,777jon,Dees_Troy, chainfire, supernoman, crashfocus, etc)
This is not my work . It is a compilation of what it worked for me from the work made by others. It is directly toward newbie users.
Instructions
1- Make sure you install LG G3 drivers in your computer( you can get them attached on this thread). Connect phone to the PC using USB cable. Make sure the phone is recognized when you plug it in with the usb cable
Also phone shall be connected as Media device (MTP), if it is in Charge Phone change it to MTP.
Scroll down this post. You will find the correct usb drivers attached. Install them in your pc.
2- Enable Developer options in your phone on Setting > General> About phone > Software information > and click seven times Build number until it enables it
3- Enable USB debugging on your LG G3 from your phones Settings > Developer options > tick ‘USB debugging’ check box. A window should pop up in your phone display to allow USB debugging. Select Allways Allow from This Computer and hit OK.
It will also be convenient to Enable installation of apps from Unknown Sources: Open phone’s Settings » select Security » Tick the “Unknown sources” check box (under Device administration section)
4- Download and unzip
- Pupledrake-Lite at http://downloads.codefi.re/thecubed/lg_g3/purpledrake/PurpleDrake-Lite_R03.tar.gz Thanks to Codefi.re
- Download and unzip the attached ADB LOCAL READY with TWRP recovery.img
Thanks to @Dees_Troy & TeamWin - for TWRP Touch recovery
ATTACHMENT IS HERE- JUST CLICK HERE
5- Download -Latest SuperSu at http://download.chainfire.eu/641/SuperSU/UPDATE-SuperSU-v2.40.zip Thanks to Chainfire
6- Transfer UPDATE-SuperSU-v2.40.zip to the internal sdcard
7- Open Purpledrake-Lite and Run purpledrake_windows.bat. It should detect your devices if it is not, you need to check if the drivers were installed properly and unplug-plug back your phone.
Hit Enter as instructed on the computer screen until it gains temporary root.
IMPORTANT : READ AND DO NOT CONTINUE TO PERMANENT ROOT INSTRUCTIONS DISPLAYED. FOLLOW INSTRUCTIONS TO CONTINUE WITH ADB INSTEAD.
Hit Ctrl+C to exit to use adb.
This process takes a few seconds and The phone start on download mode and it will stay on it.
8- Open ADB LOCAL READY folder you downloaded and hit Start Here.bat
Type "adb devices" to ensure that your phone is connected and it accept adb commands . On list of devices attached it should show LGD851........
Unplug it and plug it back if it is not .
NOTE: SOME PEEPS HAVE REPORTED PROBLEM WITH ADB NOT WORKING PROPERLY ON USB 3.0 PORTS. PLEASE USE USB 2.0 PORTS
9- Type "adb push recovery.img /temp"
You will see that it pushes the data. it should take a few seconds
Note: you may need to push it a few times if you do not find the recovery file on the /temp folder when you do step 12.
Some members stated that they need to push it ..5 times.
rubbamade tip
" This does work. If after you do the "adb push....", Hit the up key on your keyboard. What you just typed " adb push...." will appear again. Hit enter. It will "push" again. Hit up again. Hit enter. Do this at least 5 times. Now proceed with next step "adb shell"..... Should work now"
For some reason others user needed to push it more than 5 times, i assume that it is due to the file size of the image and your operating system and pc settings(i used win7). It is recommended to verify if it was pushed on step 12.
10- Type "adb shell" and it should go to shell command $
11- Then type "/temp/fakesu". This will put you in a superuser shell on your device. It should show su command line # .
12- Type "ls /temp" to make sure that recovery.img and fakesu are in /temp folder . If it is not, then you did not complete correctly the above instructions..repeat it
13- Type "dd if=/temp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery". it will take a few seconds to complete and install TWRP recovery.
14- Type type "reboot recovery" It should boot onto TWRP Touch recovery. it could take a few but it should
15- Once in TWRP, select install,go to the SD card directory, select UPDATE-SuperSU-v2.40.zip and install it. Reboot the phone once complete. Do not panic, it should take a while to cook and update applications, but it will, be patient.
16- Your device is rooted and with TWRP custom recovery. IF you do not see SuperSu in your application drawer, do not panic, just install it from the Play Store.
17- Now you are ready to install custom Roms, any application that requires root, or enjoy root features.
Quick References
How to Boot into TWRP(Recovery Mode)
1.Turn off your phone
2.Now, press and hold Power and Volume down buttons at the same time.
3.When the LG logo appears, release the keys.
4.Immediately press Power and Volume Down buttons again until the Hard Reset menu will be displayed.
5.Press volume down to Select "YES" on reset data. Do not panic, it will not . Select "yes" again . It will boot into TWRP recovery mode.
If you do not like hardware method you can use Quickboot or TWRP Manager applications from the Play store
How to Boot LG G3 Download Mode
-Disconnect your phone from PC.
-Power off your G3 and wait 4-5 seconds after lights go off.
-Hold the Volume Up button on phone, and while holding it, connect the phone to PC using a USB cable
If you get the "Windows cannot find '.\assets\windows\bin\mintty.exe'." error..on purpledrake temproot step 7.
Try just double-clicking on the .bat instead of running as admin.
Also make sure the script is extracted properly first before running
Disclaimer: It worked for me, but I am not responsible for any damages to your phone.
Your experience is very interesting vcurbel!
I was under the impression there was no way to root untouched stock 10R.
It would appear you have found a way! :good: Thanks for your contribution.
I am curious if anyone else has replicated this?
thank you so much had a little trouble but successfully rooted my device
Where was this guide yesterday?
Last week I just thought rooting build R was impossible as of yet, got fed up, and 5 minutes ago ran the LG Update tool to revert my phone back to stock/ Build C and root that way.
vcurbel said:
I am not sure if this is the correct forum for this. Moderators, Please feel free to remove it or relocate it
13- Type "dd if=/temp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery". it will take a few seconds to complete and install TWRP recovery.
Click to expand...
Click to collapse
dd if=/temp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
This command doesn't work for me. It shows, "cannot open for read: no such file or directory".
Can you help?
Edit: Nevermind, had to repush recovery. Didn't go through properly the first time. Thank you
Everything worked great. Thank you for the guide! Rooted on 10r!
NO GO
- Type "ls /temp" to make sure that recovery.img and fakesu are in /temp folder . If it is not, then you did not complete correctly the above instructions..repeat it
AT THIS POINT I AM GETTING "NOT FOUND". DID THE STEPS ABOVE SEVERAL TIMES.
I saw 8xxxkb data pushed after 'push'
==========================================================================================
C:\Users\nick\Downloads\ADB LOCAL READY>c:\windows\system32\cmd.exe
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Users\nick\Downloads\ADB LOCAL READY>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
LGD851xxxxxxxx recovery
C:\Users\nick\Downloads\ADB LOCAL READY>adb push recovery.img /temp
9716 KB/s (11245568 bytes in 1.130s)
C:\Users\nick\Downloads\ADB LOCAL READY>adb shell
[email protected]:/ $ /temp/fakesu
/temp/fakesu
# Is /temp
Is /temp
/temp/fakesu: Is: not found
#
=========================================================================================
sharkoparko said:
- Type "ls /temp" to make sure that recovery.img and fakesu are in /temp folder . If it is not, then you did not complete correctly the above instructions..repeat it
/temp/fakesu: Is: not found
#
=========================================================================================
Click to expand...
Click to collapse
try to redo step number 7. But, you are getting into su command line which is #
after you do the ls/temp on su #, you should get the list of files in your temp folder.....check if recovery and fakesu are there
then continue to step 13
vcurbel said:
try to redo step number 7. But, you are getting into su command line which is #
after you do the ls/temp on su #, you should get the list of files in your temp folder.....check if recovery and fakesu are there
then continue to step 13
Click to expand...
Click to collapse
Thanks. I did it several times, I did number 7 also. Phone is found, it says creating permaroot....Once I click CTRL C screen disappears then I go to ADB file and follow procedures. IT STILL DOES NOT WORK
===================================================================================
Welcome to PurpleDrake!
Please ensure your phone is connected, powered on, and USB debugging is properly enabled.
Your phone should be showing your homescreen with no other apps open. This is to ensure a clean state.
When you're ready, press [enter]...
Press [enter] to continue...
Waiting for device... Found device!
Your phone is a [ LG-D851 ] on [ TMO ] running SW version [ V10r ] ...
Alright. We're ready to go. We're going to temproot your phone first. Press enter when you're ready!
Press [enter] to continue...
Rebooting phone...
Waiting for device... .... Found device!
Found device, checking if vulnerable...
Yep, performing temproot...
Waiting for system to settle...
Temproot worked, all done here. Moving on...
Alright, now that you're temprooted, you can press CTRL-C here and get
a temproot prompt through 'adb shell /temp/fakesu' if you're so inclined...
However, if you'd like to permaroot, let's continue.
Press [enter] to continue...
===============================================================================================
DO I NEED TO RE-ROOT?
sharkoparko said:
Thanks. I did it several times, I did number 7 also. Phone is found, it says creating permaroot....
DO I NEED TO RE-ROOT?
Click to expand...
Click to collapse
Here is the problem. You pressed to continue (enter) to create permanent root after temporary root was created
You need to press CTRL C instead , then it will exit......then continue to next step with ADB LOCAL READY.
Ill clarify this better on step 7.
Sent from my SAMSUNG-SM-N900A using XDA Free mobile app
vcurbel said:
Here is the problem. You pressed to continue (enter) to create permanent root after temporary root was created
You need to press CTRL C instead , then it will exit......then continue to next step with ADB LOCAL READY.
Ill clarify this better on step 7.
Sent from my SAMSUNG-SM-N900A using XDA Free mobile app
Click to expand...
Click to collapse
Once I click CTRL C screen disappears then I go to ADB file and follow procedures. IT STILL DOES NOT WORK
That's what I do. I clicked enter first time rooting following purple instructions. Then I realized it does not work with January update. I run purple drake again (after I found this "fix") and, as I said, I DO NOT PROCEED WITH ENTER. I use CTRL C. The window closes and I open ADB, then click start hereand follow the rest of the procedures. So YES I did click enter once initially (because purple drake post is not updated that it does not work with JAN 15 update).
sharkoparko said:
Once I click CTRL C screen disappears then I go to ADB file and follow procedures. IT STILL DOES NOT WORK
That's what I do. I clicked enter first time rooting following purple instructions. Then I realized it does not work with January update. I run purple drake again (after I found this "fix") and, as I said, I DO NOT PROCEED WITH ENTER. I use CTRL C. The window closes and I open ADB, then click start hereand follow the rest of the procedures. So YES I did click enter once initially (because purple drake post is not updated that it does not work with JAN 15 update).
Click to expand...
Click to collapse
Ok....lets do it one at a time
Once you open and run ADB LOCAL READY. When you type adb devices, is it show your device?
Let me know on which step you got stuck.
Ill try to help you
Sent from my LG-D851 using XDA Free mobile app
Just got home with a Craigslist buy.
rooted in 15min thanks vcurbel !
now to find CM12 for this baby
hi sorry for the newbiness but for some reason i donload everything i need, basically preperation is done to the T, but as soon as i click on purpledrake_windows.bat it goes into dos window and complety exits out in less then a second, so fast that i can barely read whats on that lil black screen, im pretty sure i can make out "command not found" at the end of it..any help would be greatly appreciated
tomez206 said:
hi sorry for the newbiness but for some reason i donload everything i need, basically preperation is done to the T, but as soon as i click on purpledrake_windows.bat it goes into dos window and complety exits out in less then a second, so fast that i can barely read whats on that lil black screen, im pretty sure i can make out "command not found" at the end of it..any help would be greatly appreciated
Click to expand...
Click to collapse
Did you run it as Administrator?
Did you install LG drivers and the device is being recognized as Media device?
Sent from my LG-D851 using XDA Free mobile app
all drivers are installed, the device is recognized, and nothing, when i do run it as administrater i get a whole different error msg
vcurbel said:
Did you run it as Administrator?
Did you install LG drivers and the device is being recognized as Media device?
Sent from my LG-D851 using XDA Free mobile app
Click to expand...
Click to collapse
---------- Post added at 08:43 AM ---------- Previous post was at 08:38 AM ----------
windows cannot find '.\assets\windows\bin\mintty.exe'. Make sure you type the name correctly and try again...thats the error i get when trying to run as administrator
tomez206 said:
all drivers are installed, the device is recognized, and nothing, when i do run it as administrater i get a whole different error msg
---------- Post added at 08:43 AM ---------- Previous post was at 08:38 AM ----------
windows cannot find '.\assets\windows\bin\mintty.exe'. Make sure you type the name correctly and try again...thats the error i get when trying to run as administrator
Click to expand...
Click to collapse
It seems your windows os is missing the default mintty.exe terminal...
Google it and you will find a solution to manually install it.
Or use other pc
Sent from my LG-D851 using XDA Free mobile app
tomez206 said:
hi sorry for the newbiness but for some reason i donload everything i need, basically preperation is done to the T, but as soon as i click on purpledrake_windows.bat it goes into dos window and complety exits out in less then a second, so fast that i can barely read whats on that lil black screen, im pretty sure i can make out "command not found" at the end of it..any help would be greatly appreciated
Click to expand...
Click to collapse
If I recall if the PD batch file/script is closing on you or giving you trouble, then you can run the script manually.
See link below to thecubed PD lite thread and read the 5th grey portion down of the OP, it is titled:
"But, what if I don't want to run your script to root?"
If you must use command line because the PD batch file/script is closing immediately just be sure to STOP after gaining temporary root!
From OP step 7:
IMPORTANT : READ AND DO NOT CONTINUE TO PERMANENT ROOT INSTRUCTIONS DISPLAYED. FOLLOW INSTRUCTIONS TO CONTINUE WITH ADB INSTEAD. [/FONT]
lagvoid said:
dd if=/temp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
This command doesn't work for me. It shows, "cannot open for read: no such file or directory".
Can you help?
Edit: Nevermind, had to repush recovery. Didn't go through properly the first time. Thank you
Everything worked great. Thank you for the guide! Rooted on 10r!
Click to expand...
Click to collapse
Hello,
I am also having the same issue. I tried the above steps a couple times and am not sure if I am doing something wrong (more than likely I am). What did you mean by repush recovery?
Try step 9 again
9- Type "adb push recovery.img /temp"
You will see that it pushes the data. it should take a few seconds
vcurbel said:
Ok....lets do it one at a time
Once you open and run ADB LOCAL READY. When you type adb devices, is it show your device?
Let me know on which step you got stuck.
Ill try to help you
Sent from my LG-D851 using XDA Free mobile app
Click to expand...
Click to collapse
-------------------------------------------------------------------------------------------------------------------------------------
C:\Users\nick\Downloads\ADB LOCAL READY>c:\windows\system32\cmd.exe
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Users\nick\Downloads\ADB LOCAL READY>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
LGD851xxxxxxxx recovery
C:\Users\nick\Downloads\ADB LOCAL READY>adb push recovery.img /temp
9682 KB/s (11245568 bytes in 1.134s)
C:\Users\nick\Downloads\ADB LOCAL READY>adb shell
[email protected]:/ $ /temp/fakesu
/temp/fakesu
# Is /temp
Is /temp
/temp/fakesu: Is: not found
# dd if=/temp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/temp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
/temp/recovery.img: cannot open for read: No such file or directory
#
--------------------------------------------------------------------------------
Yes, The phone is recognized and the file as you see was pushed (see script above). I think there is some issue with this method, as other people are reporting problems following the procedure in post #1??!! I guess it work for some and it does not for others.
i tried search everywere and im sorry if im opening a new topic.
Aniway my OPO3 just arived , the only issue is its stuck at 3.1.3 oxygenOS and if i try search for updates it says, the device is updated......... so i wanted to try sideload atleast the 3.2.0 update but when i enter the command adb sideload < zip name > the resoult is
loading: 'zipname'
* cannot read 'zipname' *
can someone figure it out better than me?
thank you everyone
athais said:
i tried search everywere and im sorry if im opening a new topic.
Aniway my OPO3 just arived , the only issue is its stuck at 3.1.3 oxygenOS and if i try search for updates it says, the device is updated......... so i wanted to try sideload atleast the 3.2.0 update but when i enter the command adb sideload < zip name > the resoult is
loading: 'zipname'
* cannot read 'zipname' *
can someone figure it out better than me?
thank you everyone
Click to expand...
Click to collapse
Try to sideload the whole rom instead. That worked for Me. Did you forget to add the ”zip" at the End?
markusviktorius said:
Try to sideload the whole rom instead. That worked for Me. Did you forget to add the ”zip" at the End?
Click to expand...
Click to collapse
nono i do type the filename.zip
also im new of the android
athais said:
nono i do type the filename.zip
also im new of the android
Click to expand...
Click to collapse
Are you connected to adb? Have you checked that you are connected by writing adb devices?
markusviktorius said:
Are you connected to adb? Have you checked that you are connected by writing adb devices?
Click to expand...
Click to collapse
yup i do those steps: put the oneplus in sidelode mode, open adb and typing : adb devices then i do adb sideload oneplus.zip and after
saying: loading oneplus.zip
cannot read oneplus.zip
Print screen when typing adb devices?
markusviktorius said:
Print screen when typing adb devices?
Click to expand...
Click to collapse
there isnt much to print screen, simply he found my device with his serial number and say its connected thats all i just can't understand why adb can't read the zip
Cant you just write adb sideload and then drag the file Into the commandline?
markusviktorius said:
Cant you just write adb sideload and then drag the file Into the commandline?
Click to expand...
Click to collapse
tried this also but if i try drag the zip nothin happen, laso i tried extract the zip and it say the image is damaged
Download from another link then?
don't ask me how but seem adb sideload have managed to work ^^. aniway ty for some tip mark
I have the same problem.
If I do the update it's erase all my data?
Sent from my ONEPLUS A3000 using Tapatalk
Download a vpn and use uk's sever then search for update. It will show you an update available. Disable vpn and download and install the update normally
I try to do this but it's not work
Sent from my ONEPLUS A3000 using Tapatalk
Did you make it work, I'm stuck with 3.1.3. I dont know how to make the adb sideload.
I rename the zip file to oneplus.zip and then type "sdb sideload oneplus.zip" and say cannot read oneplus.zip.
I know I got the download right because I can open the zip file.
I've used the tablet for 6 years now and suddenly ... The battery drained to 0 so after charging and powering up .. it got stuck at boot loop, as it gets to the word android after the 5 dots animation. then the android is starting - optimizing app x of 37...
I've tried disconnecting the battery cable and reconnecting them again.
Wiping cash several times.
Usb debuging is enabled.
No root or custom recovery.
The question is .. if I can solve this problem without factory reset as I would resort to that if there's nothing else ... I have some important data That I'd like to backup if I can. even IF I can backup the data then factory reset it .. that would be fine.
corabict said:
I've used the tablet for 6 years now and suddenly ... The battery drained to 0 so after charging and powering up .. it got stuck at boot loop, as it gets to the word android after the 5 dots animation. then the android is starting - optimizing app x of 37...
I've tried disconnecting the battery cable and reconnecting them again.
Wiping cash several times.
Usb debuging is enabled.
No root or custom recovery.
The question is .. if I can solve this problem without factory reset as I would resort to that if there's nothing else ... I have some important data That I'd like to backup if I can. even IF I can backup the data then factory reset it .. that would be fine.
Click to expand...
Click to collapse
if ok connect to computer then you can move files to computer
jjgvv said:
if ok connect to computer then you can move files to computer
Click to expand...
Click to collapse
jjgvv said:
if ok connect to computer then you can move files to computer
Click to expand...
Click to collapse
I can't choose file transfer as USB mode .. so I can't see the files .. even though I hear the sound of USB connecting but I can't see the device.
corabict said:
I can't choose file transfer as USB mode .. so I can't see the files .. even though I hear the sound of USB connecting but I can't see the device.
Click to expand...
Click to collapse
reboot recovery and adb pull sdcard
corabict said:
No root or custom recovery.
Click to expand...
Click to collapse
If your hardware/eMMC is not faulty, then...
If it is unlocked, flash/boot TWRP and get your data.
If it is locked, get RESTOCK and try SAFE UNLOCK...
"Unlock your device without data loss. MiFlash is described in the Unbricking Guide:
https://forum.xda-developers.com/showpost.php?p=75360854&postcount=199
Do not proceed unless you have read the unbricking guide and downloaded all components."
jjgvv said:
reboot recovery and adb pull sdcard
Click to expand...
Click to collapse
Thank you so much for your help.
I tried to do that and it returns an error
adb: error: remote object '\sdcard' does not exist
I tried to make sure the device is recognized so I used Adb devices and it returns:
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
057f2788 device
But that when it's stuck on the animation optimization loop.
If I'm in bootloader ore recovery mod ... it returns
List of devices
And it's empty. So what do you suggest.
k23m said:
If your hardware/eMMC is not faulty, then...
If it is unlocked, flash/boot TWRP and get your data.
If it is locked, get RESTOCK and try SAFE UNLOCK...
"Unlock your device without data loss. MiFlash is described in the Unbricking Guide:
https://forum.xda-developers.com/showpost.php?p=75360854&postcount=199
Do not proceed unless you have read the unbricking guide and downloaded all components."
Click to expand...
Click to collapse
Thank you so much for your help.
I used restock 1 and it downloaded the stock but after that ... I get that
Can't install .inf
because it is not better than the current drivers.
INFO: Returning with code 0x100
Device not found...
1. disconnect it from PC
2. reboot to bootloader again
3. reconnect it to PC
Press any key to continue . . .
And I can't get past that.
corabict said:
Thank you so much for your help.
I tried to do that and it returns an error
adb: error: remote object '\sdcard' does not exist
I tried to make sure the device is recognized so I used Adb devices and it returns:
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
057f2788 device
But that when it's stuck on the animation optimization loop.
If I'm in bootloader ore recovery mod ... it returns
List of devices
And it's empty. So what do you suggest.
Thank you so much for your help.
I used restock 1 and it downloaded the stock but after that ... I get that
Can't install .inf
because it is not better than the current drivers.
INFO: Returning with code 0x100
Device not found...
1. disconnect it from PC
2. reboot to bootloader again
3. reconnect it to PC
Press any key to continue . . .
And I can't get past that.
Click to expand...
Click to collapse
maybe the posts in this thread can help you
[Q] How to mount internal storage through ADB?
A few days ago I cracked my phone screen and I can't see anything, but I want to access the internal storage, can I do this through ADB command?if possible, HOW? Please! can someone help me! Thanks!
forum.xda-developers.com
on boot loop screen of course
jjgvv said:
maybe the posts in this thread can help you
[Q] How to mount internal storage through ADB?
A few days ago I cracked my phone screen and I can't see anything, but I want to access the internal storage, can I do this through ADB command?if possible, HOW? Please! can someone help me! Thanks!
forum.xda-developers.com
on boot loop screen of course
Click to expand...
Click to collapse
Sorry for bothering you ... but really I Don't know what to do.
I used ADb shell then ls ... and listed all the files and sdcard is one of them but when I try to access it it returns this error
cd: /sdcard: No such file or directory
Then tried ..
>> Adb shell ls /sdcard/sdcard
it returns the same message.
>> c:\Adb>adb shell ls /mnt
asec
expand
media_rw
obb
runtime
sdcard *******************
secure
user
c:\Adb>adb shell ls /mnt/sdcard/
/mnt/sdcard/: No such file or directory
So why this error??
Do I need root or what. ??
and if so can I flash twerp and do backup ..if you have any links,
THank you very much for your help.
corabict said:
Sorry for bothering you ... but really I Don't know what to do.
I used ADb shell then ls ... and listed all the files and sdcard is one of them but when I try to access it it returns this error
cd: /sdcard: No such file or directory
Then tried ..
>> Adb shell ls /sdcard/sdcard
it returns the same message.
>> c:\Adb>adb shell ls /mnt
asec
expand
media_rw
obb
runtime
sdcard *******************
secure
user
c:\Adb>adb shell ls /mnt/sdcard/
/mnt/sdcard/: No such file or directory
So why this error??
Do I need root or what. ??
and if so can I flash twerp and do backup ..if you have any links,
THank you very much for your help.
Click to expand...
Click to collapse
adb pull /
and see What happened
avoid adb shell as it needs root.
jjgvv said:
adb pull /
and see What happened
avoid adb shell as it needs root.
Click to expand...
Click to collapse
Yes I tried that and returns this
>>c:\Adb>adb pull /
* daemon not running; starting now at tcp:5037
* daemon started successfully
adb: warning: stat failed for path /proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/222/task/1208/fd/15: Protocol not available