Related
Hi,
I was going to install a ROM on my Nexus, so I made a backup and wiped EVERYTHING. Including the SD card so now in clockworkmod
it can not mount the SD card, I cannot mount it to my computer... I am shaking and my hands are cold... I cant flash any rom HELP NOW!!!! ((((
thanks
No need to panic, its a nexus.
can you adb push a ROM zip to your sdcard?
if you can't then you can always flash a factory image with fastboot and you'll be back to normal in no time.
So take a deep breath and chill.
Sent from my Nexus 7 using xda premium
nodstuff said:
No need to panic, its a nexus.
can you adb push a ROM zip to your sdcard?
if you can't then you can always flash a factory image with fastboot and you'll be back to normal in no time.
So take a deep breath and chill.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I have a factory image please tell me how'd I do that in fastboot! (only if they had a begging at knees thing)
ok i will write you some step by step functions to follow in order to get yourself a rom onto your device
Info that is Needed!
Do You Already Have ADB functioning on your Computer
If Yes - Skip to Step 2
If No Proceed from Step 1
----STEP 1----
install the ADB drivers for your device
im going to assume you have a windows machine here so the followthrough will be for windows (i use Win7 but it should be the same)
BOOT YOUR DEVICE INTO RECOVERY WHILE PLUGGED INTO YOUR PC BUT DO NOT CLICK ON ANYTHING
1. Download These Google Drivers for Nexus Devices http://www.themoviedb.org/movie/15092-crank-ii-high-voltage
2. extract the folder
3. press the start button
4. right click on "Comptuer" or "My Computer (XP)
5. Click on Manage
6. in the new window press "Device Manager" on the left
you should see in the tree on the right (a device with a yellow exclamation mark ! probably called nexus)
7. right click it and press update driver software
8. press browse my computer for driver software
9. press let me pick from a list of device drivers on my computer
10. press have disk
11. press browse
12. on the new window navigate to the folder you extracted earlier and select the android_winusb.inf
13. press ok
14. there will either be 1 or 2 options to choose - click Android Composite ADB Interface and then press next
15. tick always trust software from google inc. and then install
your device should now have ADB capablilities
Proceed to step 2
----STEP 2----
this will use adb to push a file to your device while it is in recovery mode which you can then flash
1. Download This - http://www.mediafire.com/?50baad8rykng2j0
these are adb & fastboot binaries which will allow your pc to send files to your nexus via ADB
2. extract the downloaded archive to somewhere easy to remember ( i suggest C:\fastboot )
3. rename your downloaded custom rom to rom.zip (for simplicity) and copy it to the extracted directory (the one with adb.exe & fastboot.exe)
4. bring a command prompt to this directory
- in the directory you extracted (c:\fastboot) hold shift and right click in a blank area of the main window
- click "open command window here"
or
- Windows Key & R
- in the new box type cmd then press enter
- type cd c:\fastboot (where c:\fastboot is the directory where you extracted)
now to push it over
5. in the cmd window type adb devices and make sure your device is listed
your should see something like
list of attached devices
XXXXXXXXXXXXXXXX Recovery
where XXXXX is your devices serial number
6. in your cmd window type adb push rom.zip /sdcard/
this will take a while to complete but once it is down go back to your device and try to install a rom as you usually would
you should see the file in your internal memory to install now
^^ I was too slow!
First install the android SDK (Google it) then you need to put fastboot in your path you need to open my computer, system properties, advanced system settings, environment variables button at the bottom, then in the bottom window scroll down til you see find path and edit it and add the path to the android SDK and in particular the platform-tools folder.
So if you download the android SDK to your C drive, the path you will be adding will be like ";C:\android-sdk\platform tools" (note the semi colon at the start, important to separate entries)
Once the path is set up you can use fast boot in cmd just by typing fastboot xxxxx rather than typing C:\android-sdk\platform-tools fastboot xxxxx every time.
So next thing is to extract the images to somewhere.
Inside the zip is another zip called image-nakasi-jzo54k,
unzip that til you have .IMG files, system.img, boot.img etc.
then once they are extracted you use cmd to CD to that folder where you have the images and you can start to flash them.
fastboot flash system system.img
fastboot flash boot boot.img
You could just use flash-all.bat but and that will flash them all automatically but will wipe your internal SD.
Sent from my Nexus 7 using xda premium
If you JUST read that, I figured it out, and if I can flash all the partitons correctly, I will punch the thanks button.
cburk01 said:
yay new problem
Ok, so I unzipped it, extracted the thing inside, but it was it a weird format Windows recognized as "file". So, I added .zip to the end. WinRAR opened it, I saw the files, began to extract when an error popped up about the archive being damaged. WTF.
Click to expand...
Click to collapse
What was the name of the file that you had problems with?
the first one is a .tgz file then .tar but the one with the images inside that is .zip (looking at it now)
use 7-zip instead of winzip
Sent from my Nexus 7 using xda premium
nodstuff said:
What was the name of the file that you had problems with?
the first one is a .tgz file then .tar but the one with the images inside that is .zip (looking at it now)
use 7-zip instead of winzip
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Now I REALLY DO have a problem. I flashed boot.img, system.img, userdata.img, everything to the right partitons and still have a problem. Boot loop. Sticks on Google logo. Why? I did everything right. I even tried fastboot boot boot.img, no luck. I saw some people having boot loop problems, too on 4.1.2. So now, until you reply, I am going to try a custom kernel. Scratch that I'm using ToolKit to download and install 4.1.1.
If you flashed userdata.img that means your internal SD is wiped.
did you run flash-all.bat that is in the folder?
It would be no harm to do that now since everything is wiped already.
no matter what its still recoverable so don't worry.
Sent from my Nexus 7 using xda premium
nodstuff said:
If you flashed userdata.img that means your internal SD is wiped.
did you run flash-all.bat that is in the folder?
It would be no harm to do that now since everything is wiped already.
no matter what its still recoverable so don't worry.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
*facepalm* with the SD I already wiped that before I flashed. And I didnt run flashall.bat or what ever its called so I am going in to try that. Ran flashall got some weird radio flashing error so now continuing with ToolKit.
Flash-all.bat just automatically flashes all the images by running one command, it simplifies the process.
It just isn't ideal if you wanna keep your SD contents.
that's why you flash images separately, so you don't flash userdata.img but since you already wiped it then you're good to go.
Sent from my Nexus 7 using xda premium
WOOT!!!!!!!!!!!!!!!!!!!! Although I don't know if my backup will work, my tablet is now booted up into Android 4.1.1. Now I am going to root it, install a ROM, restore my data partition from TWRP, and (hopefully) have what I have been waiting for. A updated, functioning Nexus 7. *mashes thanks button*
Hey, should I update to 4.1.2 THEN root or root on 4.1.1 THEN flash the ROM?
cburk01 said:
WOOT!!!!!!!!!!!!!!!!!!!! Although I don't know if my backup will work, my tablet is now booted up into Android 4.1.1. Now I am going to root it, install a ROM, restore my data partition from TWRP, and (hopefully) have what I have been waiting for. A updated, functioning Nexus 7. *mashes thanks button*
Click to expand...
Click to collapse
Your backup is most likely gone, its stored on the SD card and that is wiped. Unless you have it on your computer, then you are all good.
Glad its back to life and now you know how to fix it if anything goes wrong.
What you learned today is very valuable to know.
It's nearly impossible to kill a nexus device (from a software perspective)
Sent from my Nexus 7 using xda premium
---------- Post added at 12:19 AM ---------- Previous post was at 12:18 AM ----------
cburk01 said:
Hey, should I update to 4.1.2 THEN root or root on 4.1.1 THEN flash the ROM?
Click to expand...
Click to collapse
Update first
Sent from my Nexus 7 using xda premium
Yes, I have my backup on my Macbook (running Windows 7). Thanks for all the useful advice. lol about the Nexus devices are hard to kill thing, I imagined a cockroach. And about the valuable lesson thing, I learned fastboot commands and adb stuff all when I was messing with (then soon after fixing) my HTC EVO 3D. Oh, I love XDA. Thanks again.
-cburk
As the title states, I am looking for a straight forward tutorial on how to take a factory image and make it rooted and flashable. The image is currently a tgz. I unzipped and it had recovery and bootloader as well as a few other img's, but those 2 will need to be deleted correct?
Sent from my HTC One X using xda app-developers app
dan.kels.r said:
As the title states, I am looking for a straight forward tutorial on how to take a factory image and make it rooted and flashable. The image is currently a tgz. I unzipped and it had recovery and bootloader as well as a few other img's, but those 2 will need to be deleted correct?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
There's a flash-all batch file in the (latest) factory image from Google. If you have Android SDK installed, I imagine running the batch file "should" just work (only thing needed on your end is to put the tablet in bootloader mode, and to make sure the driver is installed, which can also be acquired from Android SDK).
If the batch file doesn't run adb or fastboot on it's own even with the SDK installed, you might have to add the SDK's executable folder to PATH. There's a guide somewhere that explains it pretty well.
The above applies to Windows though. OS X and Linux would run the flash-all.sh file, but I have no idea on what's needed on either OS for the script to work.
Thanks for the reply. I am tracking that i have to run the .sh for linux. but what i want to accomplish is basically making it a stock rooted rom i can flash through custom recovery.
espionage724 said:
There's a flash-all batch file in the (latest) factory image from Google. If you have Android SDK installed, I imagine running the batch file "should" just work (only thing needed on your end is to put the tablet in bootloader mode, and to make sure the driver is installed, which can also be acquired from Android SDK).
If the batch file doesn't run adb or fastboot on it's own even with the SDK installed, you might have to add the SDK's executable folder to PATH. There's a guide somewhere that explains it pretty well.
The above applies to Windows though. OS X and Linux would run the flash-all.sh file, but I have no idea on what's needed on either OS for the script to work.
Click to expand...
Click to collapse
Hi everybody
When the factory images came out, I flash my N4 with the stock factory images that we used to find here : https://developers.google.com/android/nexus/images#occamkrt16s because it is now the KRT16S build
After a few days, when the KRT16S build came out, I was proposed in my phone to update it. I downloaded it, tried to flash it but nothing worked, I'm still on KRT16O and the OTA doesn't appear anymore... Then I remembered that I flashed a mod found here : http://forum.xda-developers.com/showthread.php?t=2527525 (that's a great mod btw) so I guessed that I could reflash the undo file available on the thread, flash the ota file dl mannually (I attached it in this thread) which I did through TWRP. Then I was able to see the problem, it told me that, from what I remember, Agenda.apk was missing (I think it's diary in english, not sure) then I remembered that I manually deleted some apps I never use (diary is one of them...)
So, what's next, shall I reflash the gapps to finally update my phone
Thanks for your help :laugh:
Are you using latest TWR? I did it ok
Sent from my Nokia 3210
howard bamber said:
Are you using latest TWR? I did it ok
Sent from my Nokia 3210
Click to expand...
Click to collapse
I run the 2.6.3.3 version I guess it's the latest because I flashed it a few days ago
I installed the few missing apps that i uninstalled and Calendar didn't create any error. This time it EmailGoogle.apk... I transformed it as a system application and I went to /system/app to change its name from com.google.android.apps.email or something to EmailGoogle.apk, didn't work... But I'm sure I'm on the way to achieve it :victory:
Here's the whole mesage :
Code:
Updating partition details...
Installing '/sdcard/Download/70f3bd408ca3d142509cd4bace2f2c7e3aa486c6.signed-occam-KRT16S-from-KRT16O.70f3bd40.zip'
Checking for MD5 file...
Skipping MD5 check : no MD5 dile found.
Verifying current system...
"/system/app/EmailGoogle.apk" has unexpected contents.
E:Error executing updater binary in zip '/sdcard/Download/70f3bd408ca3d142509cd4bace2f2c7e3aa486c6.signed-occam-KRT16S-from-KRT16O.70f3bd40.zip
Error flashing zip '/sdcard/Download/70f3bd408ca3d142509cd4bace2f2c7e3aa486c6.signed-occam-KRT16S-from-KRT16O.70f3bd40.zip'
Updating partition détails...
[CENTER][COLOR="Red"][SIZE="4"]Failed[/SIZE][/COLOR][/CENTER]
azertguigui said:
I run the 2.6.3.3 version I guess it's the latest because I flashed it a few days ago
I installed the few missing apps that i uninstalled and Calendar didn't create any error. This time it EmailGoogle.apk... I transformed it as a system application and I went to /system/app to change its name from com.google.android.apps.email or something to EmailGoogle.apk, didn't work... But I'm sure I'm on the way to achieve it :victory:
Here's the whole mesage :
Code:
Updating partition details...
Installing '/sdcard/Download/70f3bd408ca3d142509cd4bace2f2c7e3aa486c6.signed-occam-KRT16S-from-KRT16O.70f3bd40.zip'
Checking for MD5 file...
Skipping MD5 check : no MD5 dile found.
Verifying current system...
"/system/app/EmailGoogle.apk" has unexpected contents.
E:Error executing updater binary in zip '/sdcard/Download/70f3bd408ca3d142509cd4bace2f2c7e3aa486c6.signed-occam-KRT16S-from-KRT16O.70f3bd40.zip
Error flashing zip '/sdcard/Download/70f3bd408ca3d142509cd4bace2f2c7e3aa486c6.signed-occam-KRT16S-from-KRT16O.70f3bd40.zip'
Updating partition détails...
[CENTER][COLOR="Red"][SIZE="4"]Failed[/SIZE][/COLOR][/CENTER]
Click to expand...
Click to collapse
You can not install an apk in recovery. Use ES File Explorer to install the apk. In addition, to avoid the error, while you are in recovery, select "Mount" and uncheck the box "System" when flashing a zip file.
taodan said:
You can not install an apk in recovery. Use ES File Explorer to install the apk. In addition, to avoid the error, while you are in recovery, select "Mount" and uncheck the box "System" when flashing a zip file.
Click to expand...
Click to collapse
I did not installed it with TWRP, I did it by simply openning the apk while my phone is on, it installed the Email app...
But thanks anyway for the mount function, I'll give a try
azertguigui said:
I did not installed it with TWRP, I did it by simply openning the apk while my phone is on, it installed the Email app...
But thanks anyway for the mount function, I'll give a try
Click to expand...
Click to collapse
Simpler way to update without OTA package:
Download the factory image, and before running the flash-all script, open it with a text editor and change "fastboot -w update" to "fastboot update"
MameTozhio said:
Simpler way to update without OTA package:
Download the factory image, and before running the flash-all script, open it with a text editor and change "fastboot -w update" to "fastboot update"
Click to expand...
Click to collapse
You mean with the sdk? I don't know how to use it, when I flash something, it's with the recovery or the nexus root toolkit..
-From my Nexus 4-
UP
azertguigui said:
UP
Click to expand...
Click to collapse
**
azertguigui said:
UP
Click to expand...
Click to collapse
azertguigui said:
**
Click to expand...
Click to collapse
Not sure what you're trying to say here..
azertguigui said:
You mean with the sdk? I don't know how to use it, when I flash something, it's with the recovery or the nexus root toolkit..
-From my Nexus 4-
Click to expand...
Click to collapse
Try avoiding toolkits as they can lead to problems and leave you stuck with no idea what to do. Yes he is referring to the sdk. Only the platform-tools folder in the sdk is required so if you don't wanna bother downloading the complete file, just download the platform-tools from here and extract it to an appropriate location. Extract and move the Factory Image that you downloaded to your platform-tools directory. If you don't want your data to be erased, edit the flash-all script with a text editor and remove -w and save. Plug in your phone. Make sure you have the drivers installed. In the platform tools directory, press shift+right click> open command prompt here. Type adb devices. You will see "device <Serial Number>. If you don't, your drivers are faulty. Then type adb reboot bootloader. Once your phone has rebooted into bootloader, make sure that it is being detected by typing fastboot devices. You should see an output similar to adb devices. Now simply run the flash-all script and let it do its work. Reboot after flashing is completed.
Hope this helps!
try search any youtube on how to flash factory images to your device. I guess u'll find lots.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Words of advice, learn how to use ADB instead of relying solely on toolkits. It's very simple actually.
Now there's a simple way to update which is sideload. Oh and btw to sideload, you still need ADB though (this is why learning ADB is VERY important to us, the N4 users). Here is a video tutorial on how to perform adb sideload. All the links are attached in his youtube video.
Ibrahim.Rahman said:
Not sure what you're trying to say here..
Click to expand...
Click to collapse
:laugh: I quoted my own UP post but it told me that my post should have at least 2 letters, so I taped the spacebar twice and it wrote this
Ibrahim.Rahman said:
Try avoiding toolkits as they can lead to problems and leave you stuck with no idea what to do. Yes he is referring to the sdk. Only the platform-tools folder in the sdk is required so if you don't wanna bother downloading the complete file, just download the platform-tools from here and extract it to an appropriate location. Extract and move the Factory Image that you downloaded to your platform-tools directory. If you don't want your data to be erased, edit the flash-all script with a text editor and remove -w and save. Plug in your phone. Make sure you have the drivers installed. In the platform tools directory, press shift+right click> open command prompt here. Type adb devices. You will see "device <Serial Number>. If you don't, your drivers are faulty. Then type adb reboot bootloader. Once your phone has rebooted into bootloader, make sure that it is being detected by typing fastboot devices. You should see an output similar to adb devices. Now simply run the flash-all script and let it do its work. Reboot after flashing is completed.
Hope this helps!
Click to expand...
Click to collapse
Thanks, I'll give a try
saifulh2304 said:
try search any youtube on how to flash factory images to your device. I guess u'll find lots.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
arffrhn said:
Words of advice, learn how to use ADB instead of relying solely on toolkits. It's very simple actually.
Now there's a simple way to update which is sideload. Oh and btw to sideload, you still need ADB though (this is why learning ADB is VERY important to us, the N4 users). Here is a video tutorial on how to perform adb sideload. All the links are attached in his youtube video.
Click to expand...
Click to collapse
thanks guys, I'm gonna find tutorials on the web like the one you pointed to me
azertguigui said:
:laugh: I quoted my own UP post but it told me that my post should have at least 2 letters, so I taped the spacebar twice and it wrote this
Click to expand...
Click to collapse
Haha right!
Sent from my Nexus 4 using xda app-developers app
Okay guys first off sorry if there's a thread for this but XDA has become so over crowded and full of comments it's just to much to read through and try to remember. But anyway
Can anyone point me in the right direction or simply explain real quick how to properly root the T-Mobile variant. I'm running full stock (Obviously) I'm on H91810j and would like to debloat a little and use greenify. Any help is appreciated.
StonerSteve420 said:
Okay guys first off sorry if there's a thread for this but XDA has become so over crowded and full of comments it's just to much to read through and try to remember. But anyway
Can anyone point me in the right direction or simply explain real quick how to properly root the T-Mobile variant. I'm running full stock (Obviously) I'm on H91810j and would like to debloat a little and use greenify. Any help is appreciated.
Click to expand...
Click to collapse
There is literally speaking a thread dedicated just for the sake of rooting and twrp lol. Here:
https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
It should take about 3 to 5 minutes to complete the whole process if you know what you are doing. If you are a noob it might take sometime to figure out were to go from one step to another
Also, just remember, there is a search function on the v20 section's main screen. You can always use keywords and the function will search what you are looking for (if someone has posted something related to That). As French prople says... "Bon chance|"
P.s: yes. The rooting method by jcadduono works for 10j
jinkerz9430 said:
There is literally speaking a thread dedicated just for the sake of rooting and twrp lol. Here:
https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
It should take about 3 to 5 minutes to complete the whole process if you know what you are doing. If you are a noob it might take sometime to figure out were to go from one step to another
Also, just remember, there is a search function on the v20 section's main screen. You can always use keywords and the function will search what you are looking for (if someone has posted something related to That). As French prople says... "Bon chance|"
P.s: yes. The rooting method by jcadduono works for 10j
Click to expand...
Click to collapse
ive downloaded everything and when i extract the adb fastboot it extracts just fine but when i go to run it as administrator a box opens then closes immediately. what am i doing wrong
StonerSteve420 said:
ive downloaded everything and when i extract the adb fastboot it extracts just fine but when i go to run it as administrator a box opens then closes immediately. what am i doing wrong
Click to expand...
Click to collapse
Oh. The adb i used was from a pixel thread... The one posted in the rooting thread seems to either be missing a file called lib.... Something i forgot the name lol; or they did open and close immediately like it happened to you.
jinkerz9430 said:
Oh. The adb i used was from a pixel thread... The one posted in the rooting thread seems to either be missing a file called lib.... Something i forgot the name lol; or they did open and close immediately like it happened to you.
Click to expand...
Click to collapse
Can you link me to the adb you used. It just keeps opening and closing.
StonerSteve420 said:
Can you link me to the adb you used. It just keeps opening and closing.
Click to expand...
Click to collapse
Let me see if i can find it. If not i will zip it and send it to you
jinkerz9430 said:
Let me see if i can find it. If not i will zip it and send it to you
Click to expand...
Click to collapse
Thank you
StonerSteve420 said:
Thank you
Click to expand...
Click to collapse
Well. I couldnt find it. Anyway, i made a zip with all the files. Here:
View attachment 4070081
jinkerz9430 said:
Well. I couldnt find it. Anyway, i made a zip with all the files. Here:
View attachment 4070081
Click to expand...
Click to collapse
Still doing it. I must be the one person who's screwed lol
StonerSteve420 said:
Still doing it. I must be the one person who's screwed lol
Click to expand...
Click to collapse
Have you tried to run it in administrative mode?
jinkerz9430 said:
Have you tried to run it in administrative mode?
Click to expand...
Click to collapse
Right click run as administrator? Yes I have. Still can't get this to work. I'm using WinRar idk if that's the culprit or not. It's always been reliable.
Here, use this.
https://forum.xda-developers.com/showthread.php?t=2588979
Best for noobs.
It it asks about system wide say yes.
Then hit Windows key and R and type cmd. Then run your commands. The installer should also work.
StonerSteve420 said:
Right click run as administrator? Yes I have. Still can't get this to work. I'm using WinRar idk if that's the culprit or not. It's always been reliable.
Click to expand...
Click to collapse
Wait. I forgot to tell you. You cant double click the files. The files can be accessed only by using cmd. (command promt). So, extract the files into a folder, and use cd or pushd in dorect it to the directory where the files are. That is the proper way.
jinkerz9430 said:
Wait. I forgot to tell you. You cant double click the files. The files can be accessed only by using cmd. (command promt). So, extract the files into a folder, and use cd or pushd in dorect it to the directory where the files are. That is the proper way.
Click to expand...
Click to collapse
I know what you mean but how does the command go. I know I have to type something then add the file name sorry like I said I'm used to the old way maybe use adb for one step then the rest does it itself lol trying to catch up
StonerSteve420 said:
I know what you mean but how does the command go. I know I have to type something then add the file name sorry like I said I'm used to the old way maybe use adb for one step then the rest does it itself lol trying to catch up
Click to expand...
Click to collapse
For starter... Whats the directory where you downloaded and extracted adb fastboot? Assuming you are using the file i sent you. Was it on the downloads directory? If so open cmd (not in administratibe mode) and type pushd Downloads . Then ise all the start the adb server by using adb start-server to recognize your device. Or if you want to even see if your device is even present type adb devices
jinkerz9430 said:
For starter... Whats the directory where you downloaded and extracted adb fastboot? Assuming you are using the file i sent you. Was it on the downloads directory? If so open cmd (not in administratibe mode) and type pushd Downloads . Then ise all the start the adb server by using adb start-server to recognize your device. Or if you want to even see if your device is even present type adb devices
Click to expand...
Click to collapse
I have it in a folder on the desktop. So I type pushed Desktop/(folder name)? Or can it not be in a desktop folder. Sorry your spelling is confusing me with the second part how do I start adb server? Do I type adb start-server? Thanks for helping it's greatly appreciated
StonerSteve420 said:
I have it in a folder on the desktop. So I type pushed Desktop/(folder name)? Or can it not be in a desktop folder. Sorry your spelling is confusing me with the second part how do I start adb server? Do I type adb start-server? Thanks for helping it's greatly appreciated
Click to expand...
Click to collapse
You could use the desktop but it is more troublesome to type the directory. Thats why i suggest to put it on the downloads folder and asked you to not start the cmd as administrative. Because when you dont start it as administrative, cmd will start right from the users folder and then is only a matter of writting pushd Downloads. Focus on the first part first. Otherwise you will go nowhere lol.
jinkerz9430 said:
You could use the desktop but it is more troublesome to type the directory. Thats why i suggest to put it on the downloads folder and asked you to not start the cmd as administrative. Because when you dont start it as administrative, cmd will start right from the users folder and then is only a matter of writting pushd Downloads. Focus on the first part first. Otherwise you will go nowhere lol.
Click to expand...
Click to collapse
Thank you. I'll try that when I get home.
jinkerz9430 said:
You could use the desktop but it is more troublesome to type the directory. Thats why i suggest to put it on the downloads folder and asked you to not start the cmd as administrative. Because when you dont start it as administrative, cmd will start right from the users folder and then is only a matter of writting pushd Downloads. Focus on the first part first. Otherwise you will go nowhere lol.
Click to expand...
Click to collapse
Okay I got into the download folder using cmd (pushd download) i tried doing adb and hitting enter after and it brought up a bunch of lines after that. I did adb devices and it shows my phone but when I do fastboot oem unlock it just hangs at waiting for devices. USB debugging is on and so is OEM unlock.
StonerSteve420 said:
Okay I got into the download folder using cmd (pushd download) i tried doing adb and hitting enter after and it brought up a bunch of lines after that. I did adb devices and it shows my phone but when I do fastboot oem unlock it just hangs at waiting for devices. USB debugging is on and so is OEM unlock.
Click to expand...
Click to collapse
but are you in fastboot mode now? because after you have done the OEM unlock and then after that use usb debbugging then accept the prompt it shows about giving authorization to your computer, then after that you must go to fastboot mode to start the process of root
hello all you ph1 users [emoji2]. i just mine about a week ago (from ebay) and it is on android 9 despite the description saying it was on nougat.
so ; i would like to revert back to stock nougat. cant fond anything here on xda and have traversed www till my feet hurt and am more confused.
can anyone help out with directions , maybe even links if not too much trouble , and anything else that i need to know/be aware of?
it would be greatly appreciated [emoji8] ,
dave
mrrocketdog said:
hello all you ph1 users [emoji2]. i just mine about a week ago (from ebay) and it is on android 9 despite the description saying it was on nougat.
so ; i would like to revert back to stock nougat. cant fond anything here on xda and have traversed www till my feet hurt and am more confused.
can anyone help out with directions , maybe even links if not too much trouble , and anything else that i need to know/be aware of?
it would be greatly appreciated [emoji8] ,
dave
Click to expand...
Click to collapse
You can get Nougat 7.1 from here....
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
In struction is simple, just boot phone to boot loader and from unzip folder, issue command flashall.
mrrocketdog said:
hello all you ph1 users [emoji2]. i just mine about a week ago (from ebay) and it is on android 9 despite the description saying it was on nougat.
so ; i would like to revert back to stock nougat. cant fond anything here on xda and have traversed www till my feet hurt and am more confused.
can anyone help out with directions , maybe even links if not too much trouble , and anything else that i need to know/be aware of?
it would be greatly appreciated [emoji8] ,
dave
Click to expand...
Click to collapse
that would be good if i had a pc.
i do have a extra rooted phone that i use to run adb and fastboot commands. but the windows/linux command of "flash.all" or whatever wont work from my phone.
so i should of said , does any know of a .zip/file that i can adb sidwload , fastboot flash or flash with twrp that will revert me to android 7?
thanks for any ideas ,
dave
The flashall.sh script is just a shell script that executes the fastboot flash commands. You should be able to open the flashall.sh file in a text editor, and essentially copy and paste the commands to run them.
TDP95 said:
The flashall.sh script is just a shell script that executes the fastboot flash commands. You should be able to open the flashall.sh file in a text editor, and essentially copy and paste the commands to run them.
Click to expand...
Click to collapse
like with fastboot ;
fastboot flash /sdcard/copy/pasted flashall.sh?
The flashall.sh file will contain a list of fastboot commands. You need to open that file in a text editor, then in a terminal change to the directory all the files are extracted into and copy and paste the commands in the terminal. This will flash the various images to the PH-1.
well all the files will be on /sdcard/ in a folder with the .zip's name. so i'll give it a shot and report back.
thank you for your time and knowledgr.
i'm kinda behind on "new" devices coming from a galaxy s4. lol [emoji4]
You're welcome! The newer devices are certainly a change. What you'll do with the fastboot type zip is you'll extract it. As within that zip are the images and flashall.sh file. You'll just open that flashall.sh in a text editor as it will have a list of the fastboot commands. For example commands such as "fastboot flash boot_a name-of-file", "fastboot flash boot_b name-of-file", etc. You'll just run those commands from a terminal while in the extracted directory. That should flash the images to the device.
mrrocketdog said:
well all the files will be on /sdcard/ in a folder with the .zip's name. so i'll give it a shot and report back.
thank you for your time and knowledgr.
i'm kinda behind on "new" devices coming from a galaxy s4. lol [emoji4]
Click to expand...
Click to collapse
I remember you! ?
just make sure you understand how the A/B partions work using this method (I don't) so assuming it would be same as when using fastboot from PC
and i remember you also
thanks for chyming in. no , A/B is brand new to me but i will try everything i can think of in both slots.