Related
I'm trying to root my Nexus S 2.3.4 and so far I have unlocked it but when trying to flash Recovery Clockwork in the Command Prompt I get the error mesage "signature verification failed".
Any help would be appreciated.
XCarBoneX said:
I'm trying to root my Nexus S 2.3.4 and so far I have unlocked it but when trying to load Recovery Clockwork I get the error mesage "signature verification failed".
Any help would be appreciated.
Click to expand...
Click to collapse
How are you trying to flash your recovery?
krohnjw said:
How are you trying to flash your recovery?
Click to expand...
Click to collapse
I'm using [GUIDE] Step by Step ROOT Nexus S via ClockworkMod Recovery image (i9020/T only)
http://forum.xda-developers.com/showthread.php?t=895545
XCarBoneX said:
I'm using [GUIDE] Step by Step ROOT Nexus S via ClockworkMod Recovery image (i9020/T only)
http://forum.xda-developers.com/showthread.php?t=895545
Click to expand...
Click to collapse
You're getting Signature verification failed using fastboot flash recovery filename.img?
If so ensure a few things - 1.) you've got the correct file name and 2.) you have a good download of the img.
Filename is correct and img seems OK.
Boot Nexus S into Recovery Mode with USB debugging on
Command prompt:
fastboot flash recovery recovery-clockwork-3.0.2.4-crespo.img
error: cannot load 'recovery-clockwork-3.0.2.4-crespo.img
Win 7 64-bit SP1
Android 2.3.4 GRJ22 unlocked
Device Manager:
ADB Interface
Android Original ADB Interface
fastboot devices in Command shows:
33332EFE0C9300EC
XCarBoneX said:
Filename is correct and img seems OK.
Boot Nexus S into Recovery Mode with USB debugging on
Command prompt:
fastboot flash recovery recovery-clockwork-3.0.2.4-crespo.img
error: cannot load 'recovery-clockwork-3.0.2.4-crespo.img
Win 7 64-bit SP1
Android 2.3.4 GRJ22 unlocked
Device Manager:
ADB Interface
Android Original ADB Interface
fastboot devices in Command shows:
33332EFE0C9300EC
Click to expand...
Click to collapse
The error message did not say anything about signature verification failed. The problem is fastboot cannot find the file you specify in the command line.
SOLUTION: you have to go into the folder that you saved the "recovery-clockwork-3.0.2.4-crespo.img" (for example, if you saved the file in C:\android\) using the following commands:
Code:
c:
cd android
fastboot flash recovery recovery-clockwork-3.0.2.4-crespo.img
I have already set Path variables in Windows for the Andriod tools folder which contains Fastboot and the Recovery image file.
Could the problem be with the Android driver or Android 2.3.4 GRJ22?
XCarBoneX said:
I have already set Path variables in Windows for the Andriod tools folder which contains Fastboot and the Recovery image file.
Could the problem be with the Android driver or Android 2.3.4 GRJ22?
Click to expand...
Click to collapse
No - Fastboot can't find the file.
c:\Downloads>fastboot flash recovery fakefile.img
error: cannot load 'fakefile.img'
This takes place before checking if your device is connected, if you are unlocked to write the recovery, etc.
You're sure the cwd of the cmd prompt is the directory you downloaded the file to? Alternatively provide the full path to the recovery image.
Edit: Rereading your post above you have the recovery file in the directory as the tools. This won't resolve via the path. You either need to cd into that dir or provide the full path. Fastboot takes a local img file as the argument (local to your cwd unless you specify the full path).
Got it!!
Firmly rooted in Mother Earth.
You were absolutely correct with the cd\ command.
Running Cyanogen 7.02
Thanks so much!!
To fix hanging on cyanogen screen:
Factory data reset
wipe cache
advanced
wipe dalvik
All's good in Roots Reggae land.
XCarBoneX said:
Not quite done yet.
On reboot it hangs on the cyanogen screen.
Click to expand...
Click to collapse
You can either try reflashing or hook it up via adb and run a logcat - it will show you what it's hanging on or waiting on. Unless it's stuck *very* early on you should be able to adb shell and then run logcat.
Same problem here - Fastboot repeatedly returns "error: cannot load recovery.img" when trying to load CWM
Tried this solution:
suksit said:
SOLUTION: you have to go into the folder that you saved the "recovery-clockwork-3.0.2.4-crespo.img" (for example, if you saved the file in C:\android\) using the following commands:
Code:
c:
cd android
fastboot flash recovery recovery-clockwork-3.0.2.4-crespo.img
Click to expand...
Click to collapse
but I get "The system cannot find the path specificed." when "cd android" is entered.
- ";C:\Program Files (x86)\Android\android-sdk\platform-tools;C:\Program Files (x86)\Android\android-sdk\tools" is the path
EDIT: Fixed.
1) Moved .img file to root in C:
2) c:
3) cd\
4) fastboot flash recovery recovery.img
Got it finally.
Hi All.
Hopefully someone is able to help me. I'll try to give as much information as I can.
I have followed the following guide to root my nexus 5.
I have rooted it successfully last month.
However, I have accidentally installed a OTA update from google this week (Android 4.4.3).
Just a while earlier, I have decided to flash a custom rom.
So, as usual, I reboot my phone into recovery.
However, the recovery shows the android with a red triangle, stating "no command".
I have read the forums and read that this is actually not an error but it is the default recovery for android. (Edit: Ok. Maybe its not the default recovery. Anyone able to give me advice on this?)
I guess that my recovery was returned to the stock recovery after the OTA update.
So I tried to flash CWM recovery using ROM manager, but it states "An error occured while flashing your recovery".
I decided to restart my phone and to try it again, now it stucks at 100% on ROM Manager.
I have also tried to flash recovery.img using fastboot. However, it didn't work too.
It returns with an error: "cannot open recovery.img"
May I know if anyone can help me with this problem?
More info on the current status of my phone:
Bootloader unlocked. (Checked by trying to unlock it again. System states that process has failed as it is already unlocked)
ADB Device: Detect-able.
Fastboot Device: Detect-able.
It is indeed the stock recovery. OTA returned it. It also removed root so rom manager won't work, but you shouldn't use rom manager anyway.
You'll need to download a recovery and flash it using fastboot .
Please describe the exact steps you took to get the fastboot error. Screenshot of cmd would be very helpful too please
Sent from my Nexus 5 using Tapatalk
rootSU said:
It is indeed the stock recovery. OTA returned it. It also removed root so rom manager won't work, but you shouldn't use rom manager anyway.
You'll need to download a recovery and flash it using fastboot .
Please describe the exact steps you took to get the fastboot error.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
What I did is to check if the boot loader is unlocked.
And yes. It is unlocked.
So I carried onto checking if fastboot detects my devices by doing "fastboot devices". And my nexus5 gets detected.
Then I moved on to trying to flash recovery using " fastboot flash recovery recovery.img ".
But the error appears at this point. And I'm stuck.
Is this sufficient?
Do note that I did change the file name to recovery and not recovery.img as most files do not include the file type in the file name.
Try flashing the recovery using dd (You need root)
Boot the phone normally and push the recovery.img using adb and flash it:
Code:
adb push *Path to recovery.img* /data/media/0/
adb shell
# dd if=/data/media/0/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
I hope this helps.
You would be better served setting windows not to hide known file types to be honest.
A screenshot of your fastboot flash attempt and error would be most useful please
Sent from my Nexus 5 using Tapatalk
---------- Post added at 05:40 PM ---------- Previous post was at 05:28 PM ----------
chblg said:
Try flashing the recovery using dd (You need root)
Boot the phone normally and push the recovery.img using adb and flash it:
Code:
adb push *Path to recovery.img* /data/media/0/
adb shell
# dd if=/data/media/0/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
I hope this helps.
Click to expand...
Click to collapse
He hasn't got root. Fastboot is his only option
Sent from my Nexus 5 using Tapatalk
Well FWIW for anyone else reading, my assumption was going to be that the OP didn't put the full path to the recovery OR didn't put the recovery in the location the cmd prompt was running from.
Would have been nice to have seen this through to conclusion, but I cannot monitor forever so I'm unsubscribing due to lack of replies.
eg:
Code:
c:\Users\Administrator>fastboot flash recovery recovery.img
If there is no path to recovery image as above, then the asumption to cmd is that the recover image is in c:\users\administrator (Which it probably isnt)
If it is on the administrators desktop you would:
Code:
c:\Users\Administrator>fastboot flash recovery c:\users\Administrator\Desktop\recovery.img
Nukyi said:
Hi All.
Hopefully someone is able to help me. I'll try to give as much information as I can.
I have followed the following guide to root my nexus 5.
I have rooted it successfully last month.
However, I have accidentally installed a OTA update from google this week (Android 4.4.3).
Just a while earlier, I have decided to flash a custom rom.
So, as usual, I reboot my phone into recovery.
However, the recovery shows the android with a red triangle, stating "no command".
I have read the forums and read that this is actually not an error but it is the default recovery for android. (Edit: Ok. Maybe its not the default recovery. Anyone able to give me advice on this?)
I guess that my recovery was returned to the stock recovery after the OTA update.
So I tried to flash CWM recovery using ROM manager, but it states "An error occured while flashing your recovery".
I decided to restart my phone and to try it again, now it stucks at 100% on ROM Manager.
I have also tried to flash recovery.img using fastboot. However, it didn't work too.
It returns with an error: "cannot open recovery.img"
May I know if anyone can help me with this problem?
More info on the current status of my phone:
Bootloader unlocked. (Checked by trying to unlock it again. System states that process has failed as it is already unlocked)
ADB Device: Detect-able.
Fastboot Device: Detect-able.
Click to expand...
Click to collapse
rootSU said:
Well FWIW for anyone else reading, my assumption was going to be that the OP didn't put the full path to the recovery OR didn't put the recovery in the location the cmd prompt was running from.
Would have been nice to have seen this through to conclusion, but I cannot monitor forever so I'm unsubscribing due to lack of replies.
eg:
Code:
c:\Users\Administrator>fastboot flash recovery recovery.img
If there is no path to recovery image as above, then the asumption to cmd is that the recover image is in c:\users\administrator (Which it probably isnt)
If it is on the administrators desktop you would:
Code:
c:\Users\Administrator>fastboot flash recovery c:\users\Administrator\Desktop\recovery.img
Click to expand...
Click to collapse
Hi. Sorry for late reply. Was at work. I'll try out the full path. What I was told is to just put the recovery IMG into the same folder as fastboot and it should do the trick. Will post screenshots after trying out.
Nukyi said:
Hi. Sorry for late reply. Was at work. I'll try out the full path. What I was told is to just put the recovery IMG into the same folder as fastboot and it should do the trick. Will post screenshots after trying out.
Click to expand...
Click to collapse
Hi All,
Here's the screenshot of my cmd.
Please kindly assist and advise on what should I do.
Thank you.
Nukyi said:
Hi All,
Here's the screenshot of my cmd.
Please kindly assist and advise on what should I do.
Thank you.
Click to expand...
Click to collapse
Ok thanks.
Did you turn off "Hide known file types"? can you screenshot in Windows explorer, the location of the recovery image with hide turned off and in "details" view please?
rootSU said:
Ok thanks.
Did you turn off "Hide known file types"? can you screenshot in Windows explorer, the location of the recovery image with hide turned off and in "details" view please?
Click to expand...
Click to collapse
Yes. I did. Here are the images.
I'm using windows8. So it may look a little different.
Nukyi said:
Yes. I did. Here are the images.
I'm using windows8. So it may look a little different.
Click to expand...
Click to collapse
If I gave you a few steps to try and rule out some variables to narrow down the fault are you happy to do them?
My first thing to suggest would be to take a copy of the "platform-tools" folder and drop it on the root of c: (meaning ensure c:\platform-tools exists)
Then right click Computer > Properties > Advanced System Settings (A System Properties pop up will be shown, in the advanced tab)
In the pop-up, press "Environment Variables" and in the bottom window, called "System variables" scroll down to the entry called "Path" and press edit.
Scroll to the very end of the line of text. Add the following to the end of the line with no spaces (and no quotes obviously)
";c:\platform-tools" and click OK to all windows and pop-ups. Just to break that down, it is a semi colon ; followed by the path to the platform-tools folder.
Give yourself a restart.
What this does, is gives you the ability to call the fastboot command from anywhere. So instead of typing Desktop\adt-bundle......\platform-tools\fastboot flash blah blah, you can literally just type "fastboot flash" because like other commands, it is now a system variable.
Then put the recovery.img in the directory that cmd opens up to which appears to be be "c:\users\blah"
Then open cmd and do the basic command with no paths.... fastboot flash recovery recovery.img
Let me know,
Thanks
rootSU said:
If I gave you a few steps to try and rule out some variables to narrow down the fault are you happy to do them?
My first thing to suggest would be to take a copy of the "platform-tools" folder and drop it on the root of c: (meaning ensure c:\platform-tools exists)
Then right click Computer > Properties > Advanced System Settings (A System Properties pop up will be shown, in the advanced tab)
In the pop-up, press "Environment Variables" and in the bottom window, called "System variables" scroll down to the entry called "Path" and press edit.
Scroll to the very end of the line of text. Add the following to the end of the line with no spaces (and no quotes obviously)
";c:\platform-tools" and click OK to all windows and pop-ups. Just to break that down, it is a semi colon ; followed by the path to the platform-tools folder.
Give yourself a restart.
What this does, is gives you the ability to call the fastboot command from anywhere. So instead of typing Desktop\adt-bundle......\platform-tools\fastboot flash blah blah, you can literally just type "fastboot flash" because like other commands, it is now a system variable.
Then put the recovery.img in the directory that cmd opens up to which appears to be be "c:\users\blah"
Then open cmd and do the basic command with no paths.... fastboot flash recovery recovery.img
Let me know,
Thanks
Click to expand...
Click to collapse
Alright. I'll do it and get back to you shortly.
Thank you.
Really hope this fixes the problem.
rootSU said:
If I gave you a few steps to try and rule out some variables to narrow down the fault are you happy to do them?
My first thing to suggest would be to take a copy of the "platform-tools" folder and drop it on the root of c: (meaning ensure c:\platform-tools exists)
Then right click Computer > Properties > Advanced System Settings (A System Properties pop up will be shown, in the advanced tab)
In the pop-up, press "Environment Variables" and in the bottom window, called "System variables" scroll down to the entry called "Path" and press edit.
Scroll to the very end of the line of text. Add the following to the end of the line with no spaces (and no quotes obviously)
";c:\platform-tools" and click OK to all windows and pop-ups. Just to break that down, it is a semi colon ; followed by the path to the platform-tools folder.
Give yourself a restart.
What this does, is gives you the ability to call the fastboot command from anywhere. So instead of typing Desktop\adt-bundle......\platform-tools\fastboot flash blah blah, you can literally just type "fastboot flash" because like other commands, it is now a system variable.
Then put the recovery.img in the directory that cmd opens up to which appears to be be "c:\users\blah"
Then open cmd and do the basic command with no paths.... fastboot flash recovery recovery.img
Let me know,
Thanks
Click to expand...
Click to collapse
I have tried it. Still doesn't work. (Screenshot as attachment)
Could there be a problem with the phone instead of with the path/common errors?
Did you check if the MD5 of the recovery file is correct? (to rule out a bad download)
jj14 said:
Did you check if the MD5 of the recovery file is correct? (to rule out a bad download)
Click to expand...
Click to collapse
Re-downloaded it many times. Checked all of the md5.
Downloaded not only CWM recovery. But also other custom recovery.
Nukyi said:
I have tried it. Still doesn't work. (Screenshot as attachment)
Could there be a problem with the phone instead of with the path/common errors?
Click to expand...
Click to collapse
Now try and run cmd as an administrator if you are not doing
Nukyi said:
I have tried it. Still doesn't work. (Screenshot as attachment)
Could there be a problem with the phone instead of with the path/common errors?
Click to expand...
Click to collapse
no. the recovery.img is not in c:\users\username\
put that file there, then retry your command
OR
fastboot flash recovery c:\entire\path\to\recovery.img
Nukyi said:
Re-downloaded it many times. Checked all of the md5.
Downloaded not only CWM recovery. But also other custom recovery.
Click to expand...
Click to collapse
are you sure you downloaded the image and not the zip??
samersh72 said:
are you sure you downloaded the image and not the zip??
Click to expand...
Click to collapse
Pretty sure it is the image. Downloaded from the website itself. They only comes in .img and not in zip.
Nukyi said:
Pretty sure it is the image. Downloaded from the website itself. They only comes in .img and not in zip.
Click to expand...
Click to collapse
Ah. It just worked suddenly. No idea why. But I guess @rootSU 's suggestion works well.
And maybe also @Zepius 's suggestion.
Here's what I did to help others who have the same problem.
I did what rootSU asked me to do (changing the "path" part).
Then took Zepius suggestion and duplicated the recovery img in a few folders (the original folder i'm using, on desktop, on C drive root folder)
I screwed up trying to restore and now it says the phone is not rooted and has no OS installed on it. I still have access to the custom recovery if that helps. I have tried using ADB and Fastboot but it does not seem to be working. I need to know asap because it is for my dad and he travels a lot. He needs a phone. Please any help is appreciated.
1.Flash twrp
2. Go to adb sideload
3. In the terminal type adb sideload filename.zip
The ROM will flash and that's it.
If you need it back to stock just google "nexus 5 factory image" then download the latest one and follow the instructions given by google.
Also are you running linux (which distro) or windows just so I know what to tell you if that doesn't work
First of al: It's best to not use Windows 8 since there have been some driver incompatibilities and I'm not sure if they have been completely fixed yet.
Install 'Universal Naked Driver' and 'Minimal ADB and fastboot'. Both can be found here on xda.
Download the latest factory image for hammerhead from Google website. Extract the downloaded file twice and copy over everything to your 'Minimal ADB and fastboot' install dir.
Double click the flash-all.bat while your phone is in bootloader mode.
This will COMPLETELY reset your phone (all personalbdata will be wiped). Only the bootloader will stay unlocked.
awsumatt said:
1.Flash twrp
2. Go to adb sideload
3. In the terminal type adb sideload filename.zip
The ROM will flash and that's it.
If you need it back to stock just google "nexus 5 factory image" then download the latest one and follow the instructions given by google.
Also are you running linux (which distro) or windows just so I know what to tell you if that doesn't work
Click to expand...
Click to collapse
When trying step 3, it says cannot read sideload.
The command is not "sideload filename.zip" but
"adb sideload filename.zip"
Did you enter it correctly?
What does the terminal say as an error? And are you running Linux, Mac, or windows?
experience7 said:
The command is not "sideload filename.zip" but
"adb sideload filename.zip"
Did you enter it correctly?
Click to expand...
Click to collapse
Yes that is exactly how i entered it but with the file name of course. Although I did try your method but i don't see any file called flash-all.bat.
So just gonna ask again, what message did you get in the terminal?
Did you extract it twice? There should be a tgz file at some point... this one can be extracted as well (using 7-zip for example)
experience7 said:
The command is not "sideload filename.zip" but
"adb sideload filename.zip"
Did you enter it correctly?
Click to expand...
Click to collapse
okay nevermind my last comment. Now it says fastboot is not recognizable internal or external command. Press any key to exit
After you copied all the files into the Minimal ADB and fastboot folder the flash-all.bat should be in the same directory as fastboot.exe. Is this the case?
Try adb kill-server then (I'm a little rusty with windows) su adb start-server
experience7 said:
Did you extract it twice? There should be a tgz file at some point... this one can be extracted as well (using 7-zip for example)
Click to expand...
Click to collapse
Okay after I run the flash-all.bat, it just hangs at waiting for device
Install the 'Universal Naked Driver', reboot your computer and try again.
Again: The phone has to be in bootloader mode (you have to see the green android)
experience7 said:
Install the 'Universal Naked Driver', reboot your computer and try again.
Again: The phone has to be in bootloader mode (you have to see the green android)
Click to expand...
Click to collapse
I've decided to take the loss on this one. I just do not have time for this. I'll just go get it replaced. Thank you so much for the help. I'll definitely use XDA for more of my android problems in the future. Thank you again and to everyone who replied to this thread.
sbecerra407 said:
I've decided to take the loss on this one. I just do not have time for this. I'll just go get it replaced. Thank you so much for the help. I'll definitely use XDA for more of my android problems in the future. Thank you again and to everyone who replied to this thread.
Click to expand...
Click to collapse
Install this(fastboot + adb): http://forum.xda-developers.com/showthread.php?t=2588979
Download the file for Nexus 5: https://developers.google.com/android/nexus/images
Extract the file
Connect phone to pc in bootloader mode
Double click in flash all script
Wait for it to finish
sbecerra407 said:
When trying step 3, it says cannot read sideload.
Click to expand...
Click to collapse
ofc... you need to ENABLE sideload on twrp itself..
Thread cleaned.
Let's keep it on topic guys,
TWRP 3.0.2 for Acer Predator 8 ported by Ruben. - If you like my work please donate here, it will also give me a boost to make more things for this device : https://www.paypal.me/RubenCraveiro
----------- -----------
IMPORTANT NOTE ABOUT ROOTING AND UNLOCKING BOOTLOADER:
After flashing TWRP 3.0.2, use the SuperSU 2.46 flashable zip, do NOT use latest version or will result in a bootloop. Good Luck and have fun with rooting. Unlocking bootloader will delete all your data, so please make a backup first. Thank you.
----------- -----------
CREDITS
And also, before anything i would like to say thanks to @arjaylzo for telling me the name of a device with TWRP which helped making this update possible.
REQUIREMENTS
1- Fastboot/ADB Drivers and ADB folder
For drivers: http://adbdriver.com - Download ADB Driver Installer (universal) from the website, extract it, connect device it should detect device(if not, enable USB Debugging and reconnect), and press install, it should install drivers.
For ADB Folder: download this and extract to your main drive(C:/): https://goo.gl/ZTrfBb
2- Unlocked Bootloader (you need requirement 1 to do this)
Instructions for Unlocking bootloader: Go on settings, about device, press build version several times till it says your a developer, go back to settings, press Developer Options, and enable OEM Unlocking. Power off, then press at same time Power and Vol+ button, then connect to pc and open a cmd and write cd c:\\adb and write fastboot oem unlock, then accept the prompt it will give on tablet, and follow the rest of the steps.
----------- -----------
New TWRP bugfix update! Now you can flash stock rom on TWRP without bricking! Download Page updated!
----------- -----------
BUGS:
1- adb shell command needs to be sent before system partition is mounted or it will give an error, after doing adb shell you can mount system and do all the modifications you need.
2- You cant flash any img on twrp it gives an error, im trying to fix.
3- Backups do work, but everytime twrp restarts, the device name seems to change (which means that on /TWRP/BACKUPS/devicename/backupsinside/ changes every reboot so you have to go get the backup inside the old devicename folder and put on the new devicename folder).
----------- ADITIONAL NOTES -----------
Im leaving an unsecured boot image because system seems not want to boot android if anything seems changed. So please if system does not boot after flashing twrp/rooting, flash the unsecured boot img on fastboot
----------- -----------
Steps TO INSTALL TWRP AND ROOT
1. Download and extract the files: https://drive.google.com/file/d/0BxzG5iupOOSKNTdlRC1Wd0VmTlk/view?usp=drivesdk
2. Power off the tablet.
3. Enter fastboot mode by pressing the power button while holding down Vol -
4. Open up command prompt and navigate to the directory where fastboot.exe is located.
5. Pass the following commands:
fastboot flash boot unsecuredboot.img
fastboot flash recovery TWRP.img
6. Reboot into recovery (TWRP) and install SuperSU v2.46.zip
----------- -----------
Acer Predator 8 Support website(sourcecode, manuals, drivers, stockrom):
http://www.acer.com/ac/en/US/content/support-product/6400?b=1
----------- -----------
SCREENSHOTS:
http://imgur.com/s7CgJPR
I stuck at step 4.
is this the directory where fastboot.exe is located -> C:\adb... I have 4 files there and 1 of them is named fastboot.
Also the files i downloaded and extracted from step 1 , do i need to put them in my device or they need to stay on my pc.
goleoldark said:
I stuck at step 4.
is this the directory where fastboot.exe is located -> C:\adb... I have 4 files there and 1 of them is named fastboot.
Also the files i downloaded and extracted from step 1 , do i need to put them in my device or they need to stay on my pc.
Click to expand...
Click to collapse
C:\adb is where my adb and fastboot commands are.. on the downloaded files from Step 1 only the SuperSU zip is needed on the tablet so that you can flash it later on with twrp, the rest you leave on pc and use fastboot to flash TWRP, unsecured boot image, etc...
Ruben Craveiro said:
C:\adb is where my adb and fastboot commands are.. on the downloaded files from Step 1 only the SuperSU zip is needed on the tablet so that you can flash it later on with twrp, the rest you leave on pc and use fastboot to flash TWRP, unsecured boot image, etc...
Click to expand...
Click to collapse
Ok so in "C:\adb" i put all files i downloaded from step 1 then I opened cmd in that folder , then i typed "fastboot flash boot unsecboot.img" and it said that i cant load or open unsecboot.img
Any idea why or where is my mistake ????
goleoldark said:
Ok so in "C:\adb" i put all files i downloaded from step 1 then I opened cmd in that folder , then i typed "fastboot flash boot unsecboot.img" and it said that i cant load or open unsecboot.img
Any idea why or where is my mistake ????
Click to expand...
Click to collapse
make sure you didnt put a folder inside the adb folder instead of the actual file and make sure your writing the right name of the file..
goleoldark said:
Ok so in "C:\adb" i put all files i downloaded from step 1 then I opened cmd in that folder , then i typed "fastboot flash boot unsecboot.img" and it said that i cant load or open unsecboot.img
Any idea why or where is my mistake ????
Click to expand...
Click to collapse
also its not unsecboot, the name i added on this thread was just so it would be faster, the name is unsecuredboot.img and not unsecboot.img i guess ill have to edit that in order for people following the tutorial by line dont make these mistakes..
how do i flash the stock rom came from Acer Predator 8 Product Support Page.
can i just flash this Android 5.1 Lollipop Image via TWRP???
TIA
xdadevelopers13 said:
how do i flash the stock rom came from Acer Predator 8 Product Support Page.
can i just flash this Android 5.1 Lollipop Image via TWRP???
TIA
Click to expand...
Click to collapse
yes
thanks. will i have to flash the stockboot.img and P8AcerRecovery.img via fastboot?
tried flashing the stock rom via TWRP but to no avail.
still cant pass the boot logo
xdadevelopers13 said:
thanks. will i have to flash the stockboot.img and P8AcerRecovery.img via fastboot?
tried flashing the stock rom via TWRP but to no avail.
still cant pass the boot logo
Click to expand...
Click to collapse
If you flash stock rom, i think you have to reinstall stock recovery, the rom itself already brings stock boot.. after flashing stock recovery it should boot since no modifications have happend
Wow good job! Now i have a recovery where i can flash my custom rom for the Predator 8.
p8tgames said:
Wow good job! Now i have a recovery where i can flash my custom rom for the Predator 8.
Click to expand...
Click to collapse
no custom roms yet
How to enter the command ?
Hi i am not so sure how to execute those info in my head and act on it so can anyone teach me ? how to root my Predator 8 GT-810 Android 5.1
i saw the instruction i dk how do i Unlock Bootloader (Fastboot) i search all over google and i dont really got the solution to the question so anyone can teach me ? and "4. Open up command prompt and navigate to the directory where fastboot.exe is located." do i extract the whole file i downloaded into my Acer predator 8 or ?... im stupid sorry ...
ZaineJJ said:
Hi i am not so sure how to execute those info in my head and act on it so can anyone teach me ? how to root my Predator 8 GT-810 Android 5.1
i saw the instruction i dk how do i Unlock Bootloader (Fastboot) i search all over google and i dont really got the solution to the question so anyone can teach me ? and "4. Open up command prompt and navigate to the directory where fastboot.exe is located." do i extract the whole file i downloaded into my Acer predator 8 or ?... im stupid sorry ...
Click to expand...
Click to collapse
On step 4 You need the fastboot files, (adb & fastboot) just search how to install adb and fastboot drivers, choose the directory where to install them and place the needed files inside that folder and open a command prompt on that folder so you can flash the files.
Ruben Craveiro said:
On step 4 You need the fastboot files, (adb & fastboot) just search how to install adb and fastboot drivers, choose the directory where to install them and place the needed files inside that folder and open a command prompt on that folder so you can flash the files.
Click to expand...
Click to collapse
ir I tried finding how to install fastboot driver on Google all showed me downloads links must do survey or download or purchase item to unlock the download files ... So I don't trust it so I kept searching "how to unlock fastboot Acer predator 8"
So for ADB I can search on Google and install it on my tablet ?
ZaineJJ said:
ir I tried finding how to install fastboot driver on Google all showed me downloads links must do survey or download or purchase item to unlock the download files ... So I don't trust it so I kept searching "how to unlock fastboot Acer predator 8"
So for ADB I can search on Google and install it on my tablet ?
Click to expand...
Click to collapse
no, Search how to unlock bootloader, it should show the method that works for most devices and give necessary drivers..
Ruben Craveiro said:
no, Search how to unlock bootloader, it should show the method that works for most devices and give necessary drivers..
Click to expand...
Click to collapse
http://gsmusbdriver.com/acer-predator-8
Does this work ?
Or
https://www.howtogeek.com/239798/how-to-unlock-your-android-phones-bootloader-the-official-way/
ZaineJJ said:
http://gsmusbdriver.com/acer-predator-8
Does this work ?
Or
https://www.howtogeek.com/239798/how-to-unlock-your-android-phones-bootloader-the-official-way/
Click to expand...
Click to collapse
Yes, and after you unlock the bootloader, you put the necessary files in adb folder and flash them according to the stepts
Ruben Craveiro said:
C:\adb is where my adb and fastboot commands are.. on the downloaded files from Step 1 only the SuperSU zip is needed on the tablet so that you can flash it later on with twrp, the rest you leave on pc and use fastboot to flash TWRP, unsecured boot image, etc...
Click to expand...
Click to collapse
Hi Ruben Craveiro is this the correct way ? i plugin usb cable into Predator 8 but it says its waiting for device is it the correct way ? after typing those Commands i go over to recovery mode to install SU from there then restart and its rooted ?
ZaineJJ said:
Hi Ruben Craveiro is this the correct way ? i plugin usb cable into Predator 8 but it says its waiting for device is it the correct way ? after typing those Commands i go over to recovery mode to install SU from there then restart and its rooted ?
Click to expand...
Click to collapse
That means adb drivers arent corrently installed, but i can see you have the folder with adb, all you have to now is download this(drivers): http://dl.adbdriver.com/upload/adbdriver.zip
Extract and open the software eith the tablet plugged in, it should tell of drivers is installer properly or not, and if not you can install, after installing it should work on the cmd the commands..
Hello there. I updated my Nubia Z20 global ROM to android 11. I lost Google services in the process.
So I install the necessary drivers on my PC and used minimal adb and fastboot to unlock bootloader on my phone. But my problem is that I can't install TWRP recovery on the phone itself.
I used the Twrp recovery for nubia z20.exe to get the phone into fastboot mode but I cannot proceed any further.
Once the phone enters into fastboot mode, the computer wont detect my phone anymore.
Please help
Are you able to extract the .exe with something like 7zip to get the twrp.img file?
Then you could fastboot flash recovery twrp.img
SMcC2 said:
Are you able to extract the .exe with something like 7zip to get the twrp.img file?
Then you could fastboot
Click to expand...
Click to collapse
Thanks so much. I will use 7zip to get the twrp.img file.
After that, what do I do next?
do I open minimal adb and fastboot then type the command "fastboot recovery twrp.img"?
Mr Sparks said:
Thanks so much. I will use 7zip to get the twrp.img file.
After that, what do I do next?
do I open minimal adb and fastboot then type the command "fastboot recovery twrp.img"?
Click to expand...
Click to collapse
If you're able to extract it, yes. I tried searching for a copy of that file, but they all appear to be removed from the forums.
SMcC2 said:
If you're able to extract it, yes. I tried searching for a copy of that file, but they all appear to be removed from the forums.
Click to expand...
Click to collapse
Been working a 12 hour shift all day. I will definitely do this when I close and then give you a feedback
SMcC2 said:
Are you able to extract the .exe with something like 7zip to get the twrp.img file?
Then you could fastboot flash recovery twrp.img
Click to expand...
Click to collapse
Hello again. I tried to extract using 7zip but I couldn't get the .img file. It gave me an error message
Can you share the link you used to download TWRP and copy the error message you are getting?
SMcC2 said:
If you're able to extract it, yes. I tried searching for a copy of that file, but they all appear to be removed from the forums.
Click to expand...
Click to collapse
I found this image file. Is it the one?
https://forum.xda-developers.com/attachments/recovery-nubia-img.5368983/