Today was the worst day ever. I rooted my phone, and it worked perfectly until today. What happened was that when I updated the Google Play Services, I lost connection anything Google related (No connection) I factory reset my phone 4 times, wiped the internal storage, and it still said that I couldn't connect to the Play Store (E.X Could not establish a reliable connection). So I went into recovery and went to Advanced Wipe, and without knowing so, I deleted my OS! Im so stupid..
I FORGOT I WASN'T AN IT...
For the past two days I've been trying to get back the OS (33R). Heres what I've done
1. Downloaded the XNPH33R OS from their website and tried to install it (says NO MD5 Verification)
2. Tried doing everything about resetting OS.
3. HUGEST PROBLEM : Whenever I try and do (e.g adb sideload <rom.>.zip, or flashing) It just says Error: Device not found
4. Downloaded ADB from the Android Debug Bridge, all of my cmd commands return the same thing.
3. Also a huge problem: When I try to flash, it says (device not unlocked) and then I unlock the bootloader (Im guessing what that is will unlock it) and then I go back to the Recovery and do it again on CMD, it repeats it.
ANY SUGGESTIONS?
(If you need more information I will gladly give it to you)
BlaHBlaH525 said:
Today was the worst day ever. I rooted my phone, and it worked perfectly until today. What happened was that when I updated the Google Play Services, I lost connection anything Google related (No connection) I factory reset my phone 4 times, wiped the internal storage, and it still said that I couldn't connect to the Play Store (E.X Could not establish a reliable connection). So I went into recovery and went to Advanced Wipe, and without knowing so, I deleted my OS! Im so stupid..
I FORGOT I WASN'T AN IT...
For the past two days I've been trying to get back the OS (33R). Heres what I've done
1. Downloaded the XNPH33R OS from their website and tried to install it (says NO MD5 Verification)
2. Tried doing everything about resetting OS.
3. HUGEST PROBLEM : Whenever I try and do (e.g adb sideload <rom.>.zip, or flashing) It just says Error: Device not found
4. Downloaded ADB from the Android Debug Bridge, all of my cmd commands return the same thing.
3. Also a huge problem: When I try to flash, it says (device not unlocked) and then I unlock the bootloader (Im guessing what that is will unlock it) and then I go back to the Recovery and do it again on CMD, it repeats it.
ANY SUGGESTIONS?
(If you need more information I will gladly give it to you)
Click to expand...
Click to collapse
Could you post the fastboot and adb commands and results you get from executing them in CMD?
abde27 said:
Could you post the fastboot and adb commands and results you get from executing them in CMD?
Click to expand...
Click to collapse
I've been struggling the hole day long with the same problem.
Maybe you could read my thread. : )
Link
abde27 said:
Could you post the fastboot and adb commands and results you get from executing them in CMD?
Click to expand...
Click to collapse
CMD
cd C:\Users\xxxx\Desktop\android-sdk-windows\platform-tools
adb sideload ROM33R.zip <When the ADB sideload is on>
<Output>
* daemon not running. Starting it now on port 5037 *
* daemon started successfully *
error: device not found
error: device not found
Maybe I should try installing ADB drivers?
BlaHBlaH525 said:
CMD
cd C:\Users\xxxx\Desktop\android-sdk-windows\platform-tools
adb sideload ROM33R.zip <When the ADB sideload is on>
<Output>
* daemon not running. Starting it now on port 5037 *
* daemon started successfully *
error: device not found
error: device not found
Maybe I should try installing ADB drivers?
Click to expand...
Click to collapse
Go into Device Manager, and make sure your OPO is listed as under ADB Interface while the OPO is in bootloader mode. If it's not there then yes install or reinstall the adb driver but make sure you don't have any other devices with a triangle next to it as that may be your OPO.
abde27 said:
Go into Device Manager, and make sure your OPO is listed as under ADB Interface while the OPO is in bootloader mode. If it's not there then yes install or reinstall the adb driver but make sure you don't have any other devices with a triangle next to it as that may be your OPO.
Click to expand...
Click to collapse
My phone is listed as
Fastboot Interface (Google USB id)
BlaHBlaH525 said:
My phone is listed as
Fastboot Interface (Google USB id)
Click to expand...
Click to collapse
Does your OPO get listed when you enter "fastboot devices" ? When you had originally rooted and unlocked your OPO had you done it through CMD or a toolkit?
abde27 said:
Does your OPO get listed when you enter "fastboot devices" ? When you had originally rooted and unlocked your OPO had you done it through CMD or a toolkit?
Click to expand...
Click to collapse
Ill give you a screen shot of it being in fastboot mode. I also had rooted and unlocked my phone thru CMD
BlaHBlaH525 said:
Ill give you a screen shot of it being in fastboot mode. I also had rooted and unlocked my phone thru CMD
Click to expand...
Click to collapse
Ok so let me get this straight:
You had originally unlocked your bootloader and rooted through the cmd: "fastboot oem unlock" ?
Did you use this guide by any chance?: http://forum.xda-developers.com/showthread.php?t=2788632
Now you have no installed os and whenever you try to sideload or push stock 33R through adb it gives an error of the device not being found to the adb shell? Or does it complain that the bootloader is unlocked? If the second is happening you might need to reset the unlock and tamper bits,
Sorry if I'm asking something you already stated. I just want to be clear before I recommend anything or try to pull someone who's more experienced in for help.
abde27 said:
Ok so let me get this straight:
You had originally unlocked your bootloader and rooted through the cmd: "fastboot oem unlock" ?
Did you use this guide by any chance?: http://forum.xda-developers.com/showthread.php?t=2788632
Now you have no installed os and whenever you try to sideload or push stock 33R through adb it gives an error of the device not being found to the adb shell? Or does it complain that the bootloader is unlocked? If the second is happening you might need to reset the unlock and tamper bits,
Sorry if I'm asking something you already stated. I just want to be clear before I recommend anything or try to pull someone who's more experienced in for help.
Click to expand...
Click to collapse
Yeah I used that guide. And yes, what you stated is true. But another thing is that when I install the ROM, it says No MD5 file, but when I check the zip file, it says that there is a file called md5sum-fastboot.md5, I think that that is what TWRP is saying.
Are you able to use adb to push a zip to your internal storage?
Transmitted via Bacon
---------- Post added at 07:13 AM ---------- Previous post was at 07:02 AM ----------
If you can, just push a recovery flashable version of CM11S from here to your phone and flash it with TWRP. No sideload required.
Transmitted via Bacon
timmaaa said:
Are you able to use adb to push a zip to your internal storage?
Transmitted via Bacon
Click to expand...
Click to collapse
I have not tried, but I was able to view the internal storage and place the ROMs inside /sdcard/
timmaaa said:
Are you able to use adb to push a zip to your internal storage?
Transmitted via Bacon
---------- Post added at 07:13 AM ---------- Previous post was at 07:02 AM ----------
If you can, just push a recovery flashable version of CM11S from here to your phone and flash it with TWRP. No sideload required.
Transmitted via Bacon
Click to expand...
Click to collapse
BlaHBlaH525 said:
I have not tried, but I was able to view the internal storage and place the ROMs inside /sdcard/
Click to expand...
Click to collapse
He is right. If you can actually see the internal storage, you should be able to flash a flashable version of stock 33R from TWRP.
Actually if you are on the latest TWRP you can probably use the MTP functions and copy the file over without having to adb push it.
If you don't have the latest TWRP you can download the .img and flash it via the fastboot command. The latest is 2.8.0.1
abde27 said:
He is right. If you can actually see the internal storage, you should be able to flash a flashable version of stock 33R from TWRP.
Actually if you are on the latest TWRP you can probably use the MTP functions and copy the file over without having to adb push it.
If you don't have the latest TWRP you can download the .img and flash it via the fastboot command. The latest is 2.8.0.1
Click to expand...
Click to collapse
I have the latest version anyways
So, anything else?
Recovery flashable version is the easiest solution.
Transmitted via Bacon
timmaaa said:
Recovery flashable version is the easiest solution.
Transmitted via Bacon
Click to expand...
Click to collapse
Is that what I should do? If so, could you tell me how? Please xD
BlaHBlaH525 said:
Is that what I should do? If so, could you tell me how? Please xD
Click to expand...
Click to collapse
You just flash it like you would flash any ROM, using the install feature in TWRP. Download it from the link I provided before.
Transmitted via Bacon
timmaaa said:
You just flash it like you would flash any ROM, using the install feature in TWRP. Download it from the link I provided before.
Transmitted via Bacon
Click to expand...
Click to collapse
Are these different from the ones I downloaded from the offical CyanogenMOD OnePlus One page? Because when I try to flash it, it says MD5 file not found an then puts an error...
BlaHBlaH525 said:
Are these different from the ones I downloaded from the offical CyanogenMOD OnePlus One page? Because when I try to flash it, it says MD5 file not found an then puts an error...
Click to expand...
Click to collapse
Without you being more specific about exactly which zip you got from the CM site it's impossible to say. What's the filename?
Transmitted via Bacon
timmaaa said:
Without you being more specific about exactly which zip you got from the CM site it's impossible to say. What's the filename?
Transmitted via Bacon
Click to expand...
Click to collapse
The URL is
https://cyngn.com/products/oneplusone/
The name is
cm-11.0-XNPH33R-bacon-signed-fastboot.zip with the MD5 Checksum of 2c5bcbb3230501f2b841b56cac392bcb
Related
Apparently while doing a factory reset I managed to delete almost everything from internal storage. I've used cwm for years and made the switch to twrp recently. I could have sworn I checked everything BUT internal storage though. My data partition was showing something insane like 7 terabytes used so I wasn't able to make a nandroid. I instead deleted the data partition and somehow this happened.
Now I have no nandroids, and no more ROM zips. I attempted the procedure I used in the "how to unlock bootloader etc" thread, but when I try to push the ROM zip via the push command, it says no device found. I used Odin back in the day. Is it usable for any phone? Anyone know how to go about fixing this?
Odin is Samsung only. So, you can't adb push anything to the device?
Transmitted via Bacon
timmaaa said:
Odin is Samsung only. So, you can't adb push anything to the device?
Transmitted via Bacon
Click to expand...
Click to collapse
I thought Odin was device specific. I was hoping I was wrong though. Adb push isn't working, it just says no device found twice in a row. I can see it if I do fastboot devices though. I'll try reinstalling the Adb drivers when I get home.
Euphoria64 said:
I thought Odin was device specific. I was hoping I was wrong though. Adb push isn't working, it just says no device found twice in a row. I can see it if I do fastboot devices though. I'll try reinstalling the Adb drivers when I get home.
Click to expand...
Click to collapse
You have to be in recovery mode to do adb.
Fastboot devices is only while in fastboot mode.
Just adb sideload and not adb push. You have to go into ADB sideload in TWRP
zephiK said:
You have to be in recovery mode to do adb.
Fastboot devices is only while in fastboot mode.
Just adb sideload and not adb push. You have to go into ADB sideload in TWRP
Click to expand...
Click to collapse
I feel pretty dumb now. That's what I get for getting all pissed about all my data getting deleted and not reading instructions properly.
Euphoria64 said:
I feel pretty dumb now. That's what I get for getting all pissed about all my data getting deleted and not reading instructions properly.
Click to expand...
Click to collapse
Its okay, we all have our days enjoy your phone now. But yeah to elaborate more,
Odin is Samsung specific.
All other phones for the most part use fastboot. Which is pretty much our version of "Odin" but it is much better than Odin. Easier to use and less problems in my opinion.
hello everybody,
so my phones speakers stopped working and I couldn't fix them so I went to twrp recovery and executed a factory reset. This resulted in the device hanging at the boot screen. I then spent half an hour trying to get the drivers working and when it finally saw the phone and I wanted to sideload the 33R zip it just gave me this long list with possible command (see screenshot attached).
in fastboot it's not seeing the phone for some reason
I have access to the following:
TWRP Recovery
Fastboot
Any idea on how to get my phone working again?
RacerBas said:
hello everybody,
so my phones speakers stopped working and I couldn't fix them so I went to twrp recovery and executed a factory reset. This resulted in the device hanging at the boot screen. I then spent half an hour trying to get the drivers working and when it finally saw the phone and I wanted to sideload the 33R zip it just gave me this long list with possible command (see screenshot attached).
in fastboot it's not seeing the phone for some reason
I have access to the following:
TWRP Recovery
Fastboot
Any idea on how to get my phone working again?
Click to expand...
Click to collapse
Do you have a backup or even a ROM zip on the phone you can install from TWRP?
bp328i said:
Do you have a backup or even a ROM zip on the phone you can install from TWRP?
Click to expand...
Click to collapse
If I had I wouldn't be here
RacerBas said:
If I had I wouldn't be here
Click to expand...
Click to collapse
First on your PC try typing adb devices it should return the device serial number in the command prompt.
If it does then in TWRP click advanced, ADB Sideload, then swipe the blue arrow.
Then on your PC command prompt type adb sideload "ROM/File Name.zip" without the quotes.
It should load from there.
bp328i said:
First on your PC try typing adb devices it should return the device serial number in the command prompt.
If it does then in TWRP click advanced, ADB Sideload, then swipe the blue arrow.
Then on your PC command prompt type adb sideload "ROM/File Name.zip" without the quotes.
It should load from there.
Click to expand...
Click to collapse
That's what I tried but it came up with what's shown in the screenshot
RacerBas said:
That's what I tried but it came up with what's shown in the screenshot
Click to expand...
Click to collapse
Ok try adb push "ROM/File.zip" /sdcard
That will put the rom zip on the root of your sdcard and you can flash from there.
bp328i said:
Ok try adb push "ROM/File.zip" /sdcard
That will put the rom zip on the root of your sdcard and you can flash from there.
Click to expand...
Click to collapse
I'm getting this now: error: closed
attached a screenshot of how the phone turns up in windows
RacerBas said:
I'm getting this now: error: closed
attached a screenshot of how the phone turns up in windows
Click to expand...
Click to collapse
After it shows my device id number it says recovery, yours says host? Are you doing this with TWRP booted?
Hold on it looks like you need to update your drivers...
bp328i said:
After it shows my device id number it says recovery, yours says host? Are you doing this with TWRP booted?
Hold on it looks like you need to update your drivers...
Click to expand...
Click to collapse
yea, I've been trying to get that working for a while, guess I got the wrong ones. That would explain everything though XD
RacerBas said:
yea, I've been trying to get that working for a while, guess I got the wrong ones. That would explain everything though XD
Click to expand...
Click to collapse
Try uninstalling the ones you have and installing this one.
https://github.com/koush/UniversalAdbDriver
Good luck man, I've got to get back to work.
I know the adb push "ROM/File.zip" /sdcard works because I tested on my phone prior to posting.
One last thought is your SDK might need to be updated as well.
bp328i said:
Try uninstalling the ones you have and installing this one.
https://github.com/koush/UniversalAdbDriver
Click to expand...
Click to collapse
Currently trying it on my laptop which has a fresh reinstall, removing the drivers completely will take too long.
Your driver saw it as a google galaxy nexus adb Interface, when I used adb devices it didn't see it.
EDIT: when I go to reboot it says that there is no os installed so yea...
Another Edit: I will try this driver when I get home and report back. OnePlus adb drivers windows
I managed to fix it using the oneplus one toolkit by manudroid
Long story short, I had an issue with my HTC One X that I received from a friend. It would load up and then immediately restart about 15 seconds after getting to lock screen. I was just stuck in a boot loop.
So I decided to flash a new rom onto the phone, but neither I nor my friend had created a backup so now my OS is wiped.
I can boot into recovery mode, though. I'm not sure what the first screen is called, but it's the one with the skating androids. It tells me:
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-1.14.0002
RADIO-0.19as.32.09.11_2
OpenDSP-v29.1.45.0622
eMMC-boot
Jun 11 2012,14:36:28
Click to expand...
Click to collapse
When I enter into recovery, it appears that I have TWRP v2.3.1.0.
In here, I cannot install any roms. They appear to fail. Installing says:
Zip Install Complete
Updating partition details...
Running boot script...
Finished running boot script.
Installing '/sdcard/pac.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Error flashing zip '/sdcard/pac.zip'
Updating partition details...
Click to expand...
Click to collapse
Failed
Click to expand...
Click to collapse
I had read somewhere that I need to upgrade my TWRP in order to properly install roms, but at the current moment, running adb devices in a command prompt pointed at my adt bundle folder does not work. It just has a blank list.
Attached is a photo with what I think are the most relevant things I've downloaded/installed so far.
It does look like I can connect my phone to the computer via Mount USB Storage, but sideloader does not work since adb devices is blank.
Any thoughts?
kpxexpress said:
Long story short, I had an issue with my HTC One X that I received from a friend. It would load up and then immediately restart about 15 seconds after getting to lock screen. I was just stuck in a boot loop.
So I decided to flash a new rom onto the phone, but neither I nor my friend had created a backup so now my OS is wiped.
I can boot into recovery mode, though. I'm not sure what the first screen is called, but it's the one with the skating androids. It tells me:
When I enter into recovery, it appears that I have TWRP v2.3.1.0.
In here, I cannot install any roms. They appear to fail. Installing says:
I had read somewhere that I need to upgrade my TWRP in order to properly install roms, but at the current moment, running adb devices in a command prompt pointed at my adt bundle folder does not work. It just has a blank list.
Attached is a photo with what I think are the most relevant things I've downloaded/installed so far.
It does look like I can connect my phone to the computer via Mount USB Storage, but sideloader does not work since adb devices is blank.
Any thoughts?
Click to expand...
Click to collapse
The first screen with the skating Androids is your bootloader, FYI. Adb commands aren't used for flashing a recovery, fastboot commands are used. You do indeed need to update TWRP, the version you currently have installed isn't compatible with any current ROMs. Click the guide link in my signature, there are instructions on anything you need to do there.
Transmitted via Bacon
timmaaa said:
The first screen with the skating Androids is your bootloader, FYI. Adb commands aren't used for flashing a recovery, fastboot commands are used. You do indeed need to update TWRP, the version you currently have installed isn't compatible with any current ROMs. Click the guide link in my signature, there are instructions on anything you need to do there.
Transmitted via Bacon
Click to expand...
Click to collapse
I think I have my phone on Fastboot right now. I have the white screen that has FASTBOOT USB written on it with
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWERDOWN
Click to expand...
Click to collapse
underneath the control options. I've attached a picture below.
I Shift + Right Clicked to open command prompt in the folder with fastboot.exe and my recoveryfilename.img file.
In the command prompt, I enter in the command
Code:
fastboot flash recovery "recoveryfilename.img"
and it just stays on
Code:
< waiting for device >
I still can't figure out how to update my TWRP without an OS.
kpxexpress said:
I think I have my phone on Fastboot right now. I have the white screen that has FASTBOOT USB written on it with
underneath the control options. I've attached a picture below.
I Shift + Right Clicked to open command prompt in the folder with fastboot.exe and my recoveryfilename.img file.
In the command prompt, I enter in the command
Code:
fastboot flash recovery "recoveryfilename.img"
and it just stays on
Code:
< waiting for device >
I still can't figure out how to update my TWRP without an OS.
Click to expand...
Click to collapse
What OS are you running on your PC? Did adb/fastboot work at any point?
timmaaa said:
What OS are you running on your PC? Did adb/fastboot work at any point?
Click to expand...
Click to collapse
I'm running Windows 8.1 Pro. ADB worked once. I was able to get it to detect in recovery. ADB Devices would give me the customary string of numbers followed by "RECOVERY" and then I rebooted the phone for some reason and it stopped working. Oh, during that time I was also able to move stuff to the phone via ADB Sideload, but I would get pretty much the same errors when installing, which I later found out was because my TWRP was too old. I can't seem to get it to connect via ADB/Fastboot anymore. I can, however mount via TWRP.
kpxexpress said:
I'm running Windows 8.1 Pro. ADB worked once. I was able to get it to detect in recovery. ADB Devices would give me the customary string of numbers followed by "RECOVERY" and then I rebooted the phone for some reason and it stopped working. Oh, during that time I was also able to move stuff to the phone via ADB Sideload, but I would get pretty much the same errors when installing, which I later found out was because my TWRP was too old. I can't seem to get it to connect via ADB/Fastboot anymore. I can, however mount via TWRP.
Click to expand...
Click to collapse
There's your problem. Windows 8.1 isn't compatible with fastboot. You'll need to get access to a PC with a lower version of Windows so you can update TWRP.
timmaaa said:
There's your problem. Windows 8.1 isn't compatible with fastboot. You'll need to get access to a PC with a lower version of Windows so you can update TWRP.
Click to expand...
Click to collapse
Oh, really? Will 8 or 7 work?
I used a Windows 7 laptop and was able to update my TWRP to v2.7.0.8!
Seem to still be unable to detect devices via adb devices command.
Ok. Had to update my drivers.
I'm following your instructions on How To Install A ROM with TWRP Recovery, and now my issue is that it is saying
Code:
error flashing zip '/sdcard/pac.zip'
I've included a picture below.
kpxexpress said:
Oh, really? Will 8 or 7 work?
I used a Windows 7 laptop and was able to update my TWRP to v2.7.0.8!
Seem to still be unable to detect devices via adb devices command.
Ok. Had to update my drivers.
I'm following your instructions on How To Install A ROM with TWRP Recovery, and now my issue is that it is saying
Code:
error flashing zip '/sdcard/pac.zip'
I've included a picture below.
Click to expand...
Click to collapse
You're gonna need to get s-off so you can update your firmware. In order to get s-off you'll need to flash the Kickdroid ROM. Once you've flashed Kickdroid you can go to the Rumrunner s-off site and get s-off. Then follow the instructions in my guide thread to update your firmware.
timmaaa said:
You're gonna need to get s-off so you can update your firmware. In order to get s-off you'll need to flash the Kickdroid ROM. Once you've flashed Kickdroid you can go to the Rumrunner s-off site and get s-off. Then follow the instructions in my guide thread to update your firmware.
Click to expand...
Click to collapse
Alright, so I managed to get the Kickdroid ROM working! So right now I at least have a working phone that I can use! Thanks a TON for getting me this far.
Rumrunnner seems to not be working right for me. I'm in ADB recovery and can confirm an ADB connection, but it's still displaying
Code:
ERROR: run rumrunner again and READ (no adb connection to device. Debugging on? Drivers?)
But it's a start. I'll have to make sure I'm following all instructions carefully.
Despite hours of searching, I cannot find someone with my exact problem and a solution.
I have a nexus 5
It started bootlooping for no reason
I tried to flash the stock image, everything flashed but it still won't boot.
I tried to download kitkat but I'm using easy tether and I can't use HTTPS and nobody has mirrors.
I've done both the long way by flashing each individual file at a time
I've tried flash all and both fail, I do not get any errors I was not told to ignore during those processes.
Now, I'm fed up and want a new phone anyway. So I want to set the tamper flag to false so I an take it back.
I start following a guide, tells me to download the bootunlocker script and flash it with TWRP.
I flash TWRP with no problems and open it up
Open adb sideload
Open cmd
Type ADB devices
Serial pops up with the active state
I type adb usb
Restarts in usb mode
Type Adb push filename <location> <remote>
Daemon started successfully on port 5037
Error: Closed
I am on windows 7 using adb version 1.0.32.
Can someone please help me?
Why are you using ADB thru TWRP?
If you can flash things your device is already unlocked.
Boot your N5 to bootloader mode and flash stock images from there.
I haven't read one guide that says to use TWRP and use ADB that way.
Flash stock images thru bootloader and use the guides provided here on XDA.
You might of messed up your devices by flashing that bootunlocker. I've never heard of that or heard of flashing something thru recovery to unlock your phone.
jayRokk said:
Why are you using ADB thru TWRP?
If you can flash things your device is already unlocked.
Boot your N5 to bootloader mode and flash stock images from there.
I haven't read one guide that says to use TWRP and use ADB that way.
Flash stock images thru bootloader and use the guides provided here on XDA.
You might of messed up your devices by flashing that bootunlocker. I've never heard of that or heard of flashing something thru recovery to unlock your phone.
Click to expand...
Click to collapse
I think you misunderstood. I haven't been able to flash bootunlocker yet because of the error with sideload.
I've already tried many times flashing the stock images in fastboot mode. My phone is unlocked but I just want to reset my tamper flag now, I'm not trying to fix it anymore.
RaggleFraggles said:
I think you misunderstood. I haven't been able to flash bootunlocker yet because of the error with sideload.
I've already tried many times flashing the stock images in fastboot mode. My phone is unlocked but I just want to reset my tamper flag now, I'm not trying to fix it anymore.
Click to expand...
Click to collapse
Why are you trying to flash bootunlocker?
jayRokk said:
Why are you trying to flash bootunlocker?
Click to expand...
Click to collapse
In the how to flash factory images guide, it tells me that's how you set you tamper flag to false
RaggleFraggles said:
In the how to flash factory images guide, it tells me that's how you set you tamper flag to false
Click to expand...
Click to collapse
I know that but are you planning to return the device? I should have been more clear.
Also when flashing stock images, are you wiping everything before/after flashing?
Also take note boot up time can be up to 10 minutes.
jayRokk said:
I know that but are you planning to return the device? I should have been more clear.
Also when flashing stock images, are you wiping everything before/after flashing?
Also take note boot up time can be up to 10 minutes.
Click to expand...
Click to collapse
Yes I want to return it and jump. And yes i wipe before and after flashing
Bump
You can simply reset the flag with the root app "bootunlocker"
rootSU said:
You can simply reset the flag with the root app "bootunlocker"
Click to expand...
Click to collapse
I can't boot. to android
Bump
Why are you using adb usb? Just boot the recovery then:
adb device
If it shows just choose sideload then:
adb sideload "bootunlocker".zip
I've never used an adb usb command on any device whether pushing or sideloading.
theesotericone said:
Why are you using adb usb? Just boot the recovery then:
adb device
If it shows just choose sideload then:
adb sideload "bootunlocker".zip
I've never used an adb usb command on any device whether pushing or sideloading.
Click to expand...
Click to collapse
That's because it doesn't exist, AFAIK.
I'm still very confused.
RaggleFraggles said:
I'm still very confused.
Click to expand...
Click to collapse
Don't type adb usb. Just use the push command. adb push bootunlocker.zip /sdcard/download
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Don't type adb usb. Just use the push command. adb push bootunlocker.zip /sdcard/download
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Just did and still getting error closed message. Do you have teamveiwer?
jd1639 said:
Don't type adb usb. Just use the push command. adb push bootunlocker.zip /sdcard/download
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Now my phone is saying "unable to find partition for path sdcard.
And unable to mount persist
RaggleFraggles said:
Just did and still getting error closed message. Do you have teamveiwer?
Click to expand...
Click to collapse
You don't need team viewer you need to read more. When you type adb devices what do you get?
theesotericone said:
You don't need team viewer you need to read more. When you type adb devices what do you get?
Click to expand...
Click to collapse
It shows me my serial number and the status of the device.
I unrooted phone to update to Android 5.0.1
Wiped data & cache and tried to reboot but phone won't load past boot animation
I have tried everything I can find online. Phone appears in Device Manager as Android Device, but does not connect to PC when in command prompt.
adb devices shows no devices
when I start phone in fastboot, then recovery mode, I can select to install a file via ADB
when I choose this, and run adb devices in command prompt, it then shows a sideload device
but when I go to load a file, it gives me the same error every time:
E:footer is wrong
E:signature verification failed
Is there anything I can do? Please help! Thanks.
pds6 said:
I unrooted phone to update to Android 5.0.1
Wiped data & cache and tried to reboot but phone won't load past boot animation
I have tried everything I can find online. Phone appears in Device Manager as Android Device, but does not connect to PC when in command prompt.
adb devices shows no devices
when I start phone in fastboot, then recovery mode, I can select to install a file via ADB
when I choose this, and run adb devices in command prompt, it then shows a sideload device
but when I go to load a file, it gives me the same error every time:
E:footer is wrong
E:signature verification failed
Is there anything I can do? Please help! Thanks.
Click to expand...
Click to collapse
What recovery have you got and what file are you sideloading?
All you have to do is restart the phone in bootloader and make a fresh install of factory image via fastboot.
rootSU said:
What recovery have you got and what file are you sideloading?
Click to expand...
Click to collapse
I'm not sure unfortunately... Is that something I can find out from the Fastboot menu?
I was trying to sideload a factory image 5.0 or 5.0.1
pds6 said:
I'm not sure unfortunately... Is that something I can find out from the Fastboot menu?
I was trying to sideload a factory image 5.0 or 5.0.1
Click to expand...
Click to collapse
You can't sideload a factory image. You must use fastboot.
zagorteney said:
All you have to do is restart the phone in bootloader and make a fresh install of factory image via fastboot.
Click to expand...
Click to collapse
How can I make my Acer read Nexus 5 to install factory image via command prompt?
It comes up in Device Manager, driver seems to be installed fine, as Android Device but does not connect properly (no devices listed in "adb devices")
You use fastboot in bootloader if you want to use factory images.
Read the following 2 threads in general > sticky roll-up
- adb and fastboot
- flashing factory images / save your nexus
rootSU said:
You can't sideload a factory image. You must use fastboot.
Click to expand...
Click to collapse
Oh okay, my bad. Do I have any options to sideload anything, or is there a way to make phone connect for fastboot? Again, it's visible in Device Manager w/drivers, but not in command prompt. Thank you
will try above suggestions and report back
rootSU said:
You use fastboot in bootloader if you want to use factory images.
Read the following 2 threads in general > sticky roll-up
- adb and fastboot
- flashing factory images / save your nexus
Click to expand...
Click to collapse
After downloading the recommended Driver file from adb and fastboot thread, I unzip it to a folder and attempt to install in Device Manager. I get error saying "the hash for the file is not present in the specified file log..."
pds6 said:
After downloading the recommended Driver file from adb and fastboot thread, I unzip it to a folder and attempt to install in Device Manager. I get error saying "the hash for the file is not present in the specified file log..."
Click to expand...
Click to collapse
Win 7?
rootSU said:
Win 7?
Click to expand...
Click to collapse
8.1
pds6 said:
8.1
Click to expand...
Click to collapse
Did you follow the correct windows 8 specific instructions to turn off driver signing etc?
rootSU said:
Did you follow the correct windows 8 specific instructions to turn off driver signing etc?
Click to expand...
Click to collapse
Yes uninstalled drivers through Device Manager & did the restart through the settings as outlined there.
Will try to download google usb driver from here http://developer.android.com/sdk/win-usb.html#top
Edit: this driver installed correctly. Device now appears in device manager as Android Bootloader Interface (phone is at Fastboot screen)
rootSU said:
Did you follow the correct windows 8 specific instructions to turn off driver signing etc?
Click to expand...
Click to collapse
Wow thank you, your thread suggestion was exactly what I needed. I did not know the difference between ADB & Fastboot.
Silly mistake but one that I couldn't solve through several hours of internet searches yesterday. Thanks for your time and insight, have a great day
Nexus 5 fixed
pds6 said:
Wow thank you, your thread suggestion was exactly what I needed. I did not know the difference between ADB & Fastboot.
Silly mistake but one that I couldn't solve through several hours of internet searches yesterday. Thanks for your time and insight, have a great day
Nexus 5 fixed
Click to expand...
Click to collapse
No probs. Glad you're sorted.