Related
>>GUIDE<<
This guide will work to root the stock ROM. None of that automated stuff where you don't know what's going on. This guide will explain it step by step and you will actually know what's going on when you root a ROM
If you want to boot into a recovery image, simple use:
fastboot boot recovery.img
Note: You'll have to find the correct recovery.img file for your phone!!
Ok i unlocked the bootloader but when I input step 2 It says error: device not found? Everything worked normally?? What gives?
kp432 said:
Ok i unlocked the bootloader but when I input step 2 It says error: device not found? Everything worked normally?? What gives?
Click to expand...
Click to collapse
Make sure you have the correct drivers installed and you have USB debugging enabled.
If you are on Win 7 x64, hook up your phone to your computer, boot into the bootloader, and check out Device Manager (right click My Computer, Properties, Device Manager).
If you see in "Other Devices" a device called Android 1.0 (I can't remember off the top of my head), right click it, update drivers. Tell Windows you want to browse for the drivers, click to see the list of drivers you already have installed, and scroll down to find the Samsung Android Phone or whatever it's called.
kp432 said:
Ok i unlocked the bootloader but when I input step 2 It says error: device not found? Everything worked normally?? What gives?
Click to expand...
Click to collapse
your drivers probably arent installed properly. download PDA net and use it on your computer and it should install the drivers for you
Can't gain root after unlocking bootloader
xx
kp432 said:
Ok i unlocked the bootloader but when I input step 2 It says error: device not found? Everything worked normally?? What gives?
Click to expand...
Click to collapse
Same here. And I did install PDAnet prior to attemping this so that I would have the correct drivers.
I have tried this on 2 different computers and I keep getting the same error. When I try to do "adb root" it will start daemon and then it will fail.
It keeps saying "Error: Device Not Found"
same error as everyone else..
"adbd cannot run as root in production builds"
I noticed my bootloader says unlocked...is that good?
DenzelChurchill said:
Hey guys,
I can't seem to boot straight into boot.cdma.img. Soon after this command, the phone boots (doesn't make it to the ROM boot animation), then reboots, then goes into the ROM. When I try "adb root" I get the "production" error message. I have a Verizon CDMA/LTE Galaxy Nexus and I'm connecting it to Mac OS X. Thoughts?
Detailed explanation below for those curious...
Thanks everyone!
1. Boot phone into bootloader
2. Terminal: fastboot oem unlock (say yes to prompt, then return to bootloader)
3. Terminal: fastboot boot.cdma.img
4. Phone reboots, but doesn't make it to the ROM boot animation before it reboots again (I know this because it goes black for a second and vibrates slightly)
5. Phone boots into stock ROM, where I quickly dismiss all prompts and move to the settings menu to enable USB debugging
6. Terminal: adb root (Error message: "adbd cannot run as root in production builds")
7. I confirm that I don't have root by loading up Superuser and attempting to update binaries, where I'm told that it has failed the "Gain root..." step.
EDIT: Added phone / computer details.
Click to expand...
Click to collapse
remember, that command is supposed to be
fastboot boot boot.cmda.img
xx
hello I have unlocked the boot loader and rooted, installed cwm, my only problem is I do not have any 4g connectivity , I checked to see if its on lte cdma it is , powered off phone , battery pull ,reboot phone 4g shows up but will not stay connected. dont know if this has anything to do with root or what but my t-bolt has had 4g all day and nexus is right beside it. any ideas, thanks
Seaman24 said:
hello I have unlocked the boot loader and rooted, installed cwm, my only problem is I do not have any 4g connectivity , I checked to see if its on lte cdma it is , powered off phone , battery pull ,reboot phone 4g shows up but will not stay connected. dont know if this has anything to do with root or what but my t-bolt has had 4g all day and nexus is right beside it. any ideas, thanks
Click to expand...
Click to collapse
I know their network was down from around 6am EST to Noon EST. And last night on some cities on the west coast.
I actually lost 3g data for that time as well.
DenzelChurchill said:
Hey guys,
1. Boot phone into bootloader
2. Terminal: fastboot oem unlock (say yes to prompt, then return to bootloader)
3. Terminal: fastboot boot boot.cdma.img
4. Phone reboots, but doesn't make it to the ROM boot animation before it reboots again (I know this because it goes black for a second and vibrates slightly)
5. Phone boots into stock ROM, where I quickly dismiss all prompts and move to the settings menu to enable USB debugging
6. Terminal: adb root (Error message: "adbd cannot run as root in production builds")
7. I confirm that I don't have root by loading up Superuser and attempting to update binaries, where I'm told that it has failed the "Gain root..." step.
Click to expand...
Click to collapse
I had the exact same problem where the phone reboots before it loads into boot.cdma.img, followed by the "production builds" error (as in your steps 4-6)
What worked was going back to bootloader, and running "fastboot boot boot.cdma.img" again
It loaded very quickly. When i ran "adb root" it actually said that the device was already rooted or something similar. The proceeding steps went very smoothly.
Hope this helps
---------- Post added 22nd December 2011 at 12:05 AM ---------- Previous post was 21st December 2011 at 11:59 PM ----------
aznxk3vi17 said:
Make sure you have the correct drivers installed and you have USB debugging enabled.
If you are on Win 7 x64, hook up your phone to your computer, boot into the bootloader, and check out Device Manager (right click My Computer, Properties, Device Manager).
If you see in "Other Devices" a device called Android 1.0 (I can't remember off the top of my head), right click it, update drivers. Tell Windows you want to browse for the drivers, click to see the list of drivers you already have installed, and scroll down to find the Samsung Android Phone or whatever it's called.
Click to expand...
Click to collapse
I can confirm this. You need to be in bootloader to see the device driver error. It will show a Android 1.0 with an exclamation mark over it. I believe the device is a labeled as a storage drive or something similar (its not under "Android Phone")
Follow the above instructions to apply the SAMSUNG drivers
Just wanted to say thanks for this. I am fairly new to this but this seemed a lot less complicated.
Just one thing, I couldn't figure out why I couldn't run the adb root command until reading some more and finding that I had to enable USB debugging then reboot again. Hope that helps someone.
Thanks again all.
Also, how do you unroot the phone after using this method?
How to do on mac
I am new to doing this on Mac. I know that it is kind of the same but what is different when I am doing this on a Mac as apposed to a PC?
numbskill said:
I had the exact same problem where the phone reboots before it loads into boot.cdma.img, followed by the "production builds" error (as in your steps 4-6)
What worked was going back to bootloader, and running "fastboot boot boot.cdma.img" again
It loaded very quickly. When i ran "adb root" it actually said that the device was already rooted or something similar. The proceeding steps went very smoothly.
Hope this helps
Click to expand...
Click to collapse
any idea why this happens? I rooted 3 phones with this method. The first one went smoothly. The second two went through the reboots. In one case, I actually loaded an odin to get it back to the boot animation, otherwise I was stuck on the unlocked Google screen. Would be nice to know what I might be doing before I root someone else's phone.
xx
Does following this guide erase your phone? When it says boot the CDMA.img, I'm thinking it's going to replace the already installed image with a stock version that has root.
Or am I completely missing the mark here? I read what the guide wrote, but it doesn't really say if it's going to replace my stock image or what's going to happen.
BUMP?
The file linked on that thread is 404'd. Also, does this work on 4.0.4? I want to root but learn at the same time so I want to avoid using the toolkit. Does the toolkit work on 4.0.4? Thanks.
i ran into a little problem idk what it is this is the first time i run into this problem. i enter the first command prompt into terminal i think its
./fastboot-mac oem unlock and all it says is:
./fastboot-mac: operation not permitted
i don't know what I'm doing wrong help??
Hey there
I want to start off by saying I have very little experience with rooting, but am very familiar with jailbreaking apple devices so I figured i could manage.
I have a htc one m8 on rogers network locked. I rooted it and had super user and all that jazz, then flashed AOKP. Then I thought i actually liked the stock HTC sense better, so I tried to "get things back to normal"...lol.
Now im at the point where if i turn my phone on it goes straight to the fastboot screen(?) with all the "fast boot, recovery, factory reset, etc". Since I'm super new to all of this is there anybody that can write some instructions on how to get my phone back to stock? I would really appreciate it after panicking over this for 3 days.
Edit: In the fastboot screen at the top it says ***Tampered*** ***Relocked*** ***security warning**
also when i try to press recovery it shows the htc screen for 1 second then back to the same menu
i found this http://forum.xda-developers.com/showthread.php?t=2710735 but i cannot even get into recovery
haydenrbm said:
Hey there
I want to start off by saying I have very little experience with rooting, but am very familiar with jailbreaking apple devices so I figured i could manage.
I have a htc one m8 on rogers network locked. I rooted it and had super user and all that jazz, then flashed AOKP. Then I thought i actually liked the stock HTC sense better, so I tried to "get things back to normal"...lol.
Now im at the point where if i turn my phone on it goes straight to the fastboot screen(?) with all the "fast boot, recovery, factory reset, etc". Since I'm super new to all of this is there anybody that can write some instructions on how to get my phone back to stock? I would really appreciate it after panicking over this for 3 days.
Click to expand...
Click to collapse
While being an expert with rooting and flashing custom recoveries on Samsung devices, I am also new to the world of HTC. Out of curiosity, what happens when you hit factory reset?
Unlock the boot loader again then install twrp recovery then head over to the stock backup thread and flash one of the nandroids for your cid.
MattMJB0188 said:
While being an expert with rooting and flashing custom recoveries on Samsung devices, I am also new to the world of HTC. Out of curiosity, what happens when you hit factory reset?
Click to expand...
Click to collapse
When i hit factory reset it the screen changes to the HTC in green for 1 second then back to where i started
ashyx said:
Unlock the boot loader again then install twrp recovery then head over to the stock backup thread and flash one of the nandroids for your cid.
Click to expand...
Click to collapse
I would...but when im trying to use ADB devices it isn't found
haydenrbm said:
When i hit factory reset it the screen changes to the HTC in green for 1 second then back to where i started
I would...but when im trying to use ADB devices it isn't found
Click to expand...
Click to collapse
Do fastboot devices ... adb commands itself won't work in bootloader, it has to be fastboot commands.
now you have a locked bootloader which means you cant do anything.. so your first step is to unlock it again then flash a custom recovery (TWRP) after that flash the stock rom+ boot.img ( to be safe) make sure it boots. RELOCK the bootloader then flash your firmware.zip.. hope it helps
mushages said:
now you have a locked bootloader which means you cant do anything.. so your first step is to unlock it again then flash a custom recovery (TWRP) after that flash the stock rom+ boot.img ( to be safe) make sure it boots. RELOCK the bootloader then flash your firmware.zip.. hope it helps
Click to expand...
Click to collapse
How can I unlock the bootloader again without the device showing in adb?
haydenrbm said:
How can I unlock the bootloader again without the device showing in adb?
Click to expand...
Click to collapse
i think you have your unlock token. start from here
http://www.htcdev.com/bootloader/unlock-instructions/page-4/
haydenrbm said:
How can I unlock the bootloader again without the device showing in adb?
Click to expand...
Click to collapse
If it's in bootloader it should show in command prompt when you type fastboot devices after connecting it to PC. If it doesn't then there is a driver problem perhaps. Check to make sure you have HTC drivers installed, or reinstall them. Might as well make sure adb is up to date as well, can do that through the Android SDK Manager. Another possibility might be that the usb cable isn't working correctly, try another cable. Fact of the matter though is, if it's in bootloader and you connect it to the PC adb/fastboot SHOULD pick it up.
So check and fix those things. Also make sure you use the correct commands, in bootloader mode, it'll be fastboot commands, not "adb devices" but "fastboot devices" ... "fastboot reboot" etc etc. Also make sure you're running the commands from within the adb/fastboot folder path(just for in case yeah...)
mushages said:
i think you have your unlock token. start from here
Click to expand...
Click to collapse
Okay it is unlocked, but now it just stays on the AOKP boot screen
Thank you for the help btw, it must be very painful.
haydenrbm said:
Okay it is unlocked, but now it just stays on the AOKP boot screen
Thank you for the help btw, it must be very painful.
Click to expand...
Click to collapse
Press Volume UP + Power button, once the screen goes dead, press Volume DOWN + Power button to get back into bootloader. Then flash a custom recovery (Like TWRP) and start flashing the Stock nandroid backups, can be found from here Collection of Stock backups
BerndM14 said:
Press Volume UP + Power button, once the screen goes dead, press Volume DOWN + Power button to get back into bootloader. Then flash a custom recovery (Like TWRP) and start flashing the Stock nandroid backups, can be found from here Collection of Stock backups
Click to expand...
Click to collapse
Okay i have got into the bootloader now, thanks.
I cannot put the rom into the internal storage because my computer wont detect the phone
haydenrbm said:
Okay i have got into the bootloader now, thanks.
the adb devices will show it if i have it in recovery mode but not bootloader, why is that ?
Click to expand...
Click to collapse
You didn't read any of my posts about that, did you? lol
I already stated adb commands like "adb devices" "adb reboot" etc will NOT work in bootloader, it'll work in the system and yes, it'll work in recovery for sideloading etc, but NOT in bootloader. For bootloader you HAVE to use fastboot commands, "fastboot devices" "fastboot reboot" "fastboot oem lock" "fastboot oem get_identifier_token" "fastboot flash unlocktoken Unlock_code.bin" etc etc
BerndM14 said:
You didn't read any of my posts about that, did you? lol
I already stated adb commands like "adb devices" "adb reboot" etc will NOT work in bootloader, it'll work in the system and yes, it'll work in recovery for sideloading etc, but NOT in bootloader. For bootloader you HAVE to use fastboot commands, "fastboot devices" "fastboot reboot" "fastboot oem lock" "fastboot oem get_identifier_token" "fastboot flash unlocktoken Unlock_code.bin" etc etc
Click to expand...
Click to collapse
Sorry I skipped past your first response, that makes sense now.
So I need to put the rom on my internal storage then go into recovery and install the zip using TWRP..but when I plug my phone into the computer the internal storage wont show up.
I do have sync manager installed also, and it wont show up in that either
haydenrbm said:
Okay i have got into the bootloader now, thanks.
I cannot put the rom into the internal storage because my computer wont detect the phone
Click to expand...
Click to collapse
With that adb devices command again in bootloader? Did you flash TWRP yet? If so, Got to Advanced >>> ADB Sideload >>> Swipe to start sideload.
Place the ROM.zip file in your adb folder then:
Connect phone to PC, while still in recovery mode type adb devices to make sure your device gets picked up, should show you the serial number for device AS WELL as "sideload" next to it, if so then you are hooked up right. Next type adb sideload name_of_zip.zip wait until fully finished.
If sideload fails for one or other reason you can also try to push it. Reboot to recovery again, type adb devices to make sure device gets picked up, type adb push name_of_zip.zip /data/media/0/ or adb push name_of_zip.zip /sdcard/ flash as per usual then.
Yet somehow I don't think you even need to go to these steps
BerndM14 said:
With that adb devices command again in bootloader? Did you flash TWRP yet? If so, Got to Advanced >>> ADB Sideload >>> Swipe to start sideload.
Place the ROM.zip file in your adb folder then:
Connect phone to PC, while still in recovery mode type adb devices to make sure your device gets picked up, should show you the serial number for device AS WELL as "sideload" next to it, if so then you are hooked up right. Next type adb sideload name_of_zip.zip wait until fully finished, once done reboot back into recovery and flash rom.
If sideload fails for one or other reason you can also try to push it. Reboot to recovery again, type adb devices to make sure device gets picked up, type adb push name_of_zip.zip /data/media/0/ or adb push name_of_zip.zip /sdcard/ flash as per usual then.
Yet somehow I don't think you even need to go to these steps
Click to expand...
Click to collapse
haha..thank you for baby steps
The sideload completed and i rebooted then went back into recovery and install but there isn't a zip file anywhere
Edit: wow..some how i reset it and it turned on and got into the phone... and now it connects to the computer so i should be able to follow the other tutorial now...man you are a life saver thank you so much
haydenrbm said:
haha..thank you for baby steps
The sideload completed and i rebooted then went back into recovery and install but there isn't a zip file anywhere
Edit: wow..some how i reset it and it turned on and got into the phone... and now it connects to the computer so i should be able to follow the other tutorial now...man you are a life saver thank you so much
Click to expand...
Click to collapse
I made a small mistake with the sideload though, it actually installs automatically as such you don't have to go back into recovery to flash, as it did it already, sorry. Edited post to fix.
Well as long as you can get into phone now to copy the nandroid backup to the phone all should be in order, can flash back stock from the nandroid then.
Glad it worked out then.:good:
BerndM14 said:
I made a small mistake with the sideload though, it actually installs automatically as such you don't have to go back into recovery to flash, as it did it already, sorry. Edited post to fix.
Well as long as you can get into phone now to copy the nandroid backup to the phone all should be in order, can flash back stock from the nandroid then.
Glad it worked out then.:good:
Click to expand...
Click to collapse
Hello BerndM14, thank you for this baby steps. Mine m8 is a gpe version, it's 4.4.2 google rom, rooted, cwm recovery, s-on. I was trying to flash the full google 4.4.3 zip rom under recovery, however, after that, my m8 automaticlly enter recovery everytime reboot. And I can manually enter the bootloader, my pc can find the m8 both in recovery and bootloader. I searched this post, and do it accordingly, I download the gpe stock backup KOT49H.H16 - 1.16.1700.16 - CWM Philz touch and use adb sideload gpe3.zip to the cell phone sucessfully, then the recovery automaticlly starts installing rom, then, I got below message:
-- Erasing & formatting /system as ext4 (Unmounted system)
system partition formatted!
-- Mounting system partition for writing
Writing rom system to system partition
Rom system written successfully!
@symlinking and permissions
--Creating toolbox symlinks
--creating additional symlinks
Symlinks Set!
--installing busybox
Set_perm: some changes failed
E:Error in /tmp/update.zip
(status 7)
installation aborted.
Install from sideload complete.
then, I reboot it manually. problem still there, still enter the recovery automaticlly.
do you have any comments on this? please.
thanks,
I have read many different methods on how to restore a phone back to original OEM specifications but seem unable to complete the process.
I downloaded the Nandroid for my CID, copied the files to the SDCARD but the installation failed with TWRP. Not sure if someone has a good tutorial on how to get the device back to factory specs. Doesn't HTC have an application that can restore a phone? When I worked at Motorola years ago we had a home grown utility that could restore a device entirely including firmware, software, boot images and such.
I am new to HTC devices and appreciate assistance with this. Thank you.
Run the official ATT ruu bro. Give me a sec and I'll edit this post with the link. Quick question, can you tell me if the phone is still unlocked or relocked?
InflatedTitan said:
Run the official ATT ruu bro. Give me a sec and I'll edit this post with the link. Quick question, can you tell me if the phone is still unlocked or relocked?
Click to expand...
Click to collapse
It is still unlocked. When I boot to recovery it shows tampered, unlocked, s-on.
Ok hopefully you know how to execute fastboot commands. You'll need to simply boot into boot loader, fire up command prompt and enter this command.
fastboot oem lock
Once locked you need to download this and run it as any other program on your computer.
http://dl3.htc.com/application/RUU_M...5_signed_2.exe
InflatedTitan said:
Ok hopefully you know how to execute fastboot commands. You'll need to simply boot into boot loader, fire up command prompt and enter this command.
fastboot oem lock
Once locked you need to download this and run it as any other program on your computer.
http://dl3.htc.com/application/RUU_M...5_signed_2.exe
Click to expand...
Click to collapse
I know fastboot and adb very well. The URL you provided does not resolve:
404 - File or directory not found.
The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable.
ngerasimatos said:
I know fastboot and adb very well. The URL you provided does not resolve:
404 - File or directory not found.
The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable.
Click to expand...
Click to collapse
Sorry brother it was a direct dl link and I wanted to try my luck with copy and pasting lol. Here's the link to the thread instead. http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
Now mind you I'm not sure if you planning on hacking it or not, but if you do that ruu the only way to s-off is to pay $25 for the sunshine app.
InflatedTitan said:
Ok hopefully you know how to execute fastboot commands. You'll need to simply boot into boot loader, fire up command prompt and enter this command.
fastboot oem lock
Once locked you need to download this and run it as any other program on your computer.
http://dl3.htc.com/application/RUU_M...5_signed_2.exe
Click to expand...
Click to collapse
Yeah you copied and pasted directly instead of right clicking on the link and selecting "copy link address"
http://dl3.htc.com/application/RUU_...20.51A.4198.01L_F_release_387305_signed_2.exe
InflatedTitan said:
Sorry brother it was a direct dl link and I wanted to try my luck with copy and pasting lol. Here's the link to the thread instead. http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
Now mind you I'm not sure if you planning on hacking it or not, but if you do that ruu the only way to s-off is to pay $25 for the sunshine app.
Click to expand...
Click to collapse
Honestly., the phone is going to be a gift and the last thing I wanted was them to panic when they booted it and saw the red HTC disclaimer at the bottom of the screen, or if they have issues with the device and AT&T gives them grief that the ROM is not factory.
It seems to be currently running Android Revolution HD 11.2 and the ROM doesn't really have any issues that I have seen, but in the end its not going to be my device to support to I want to keep it simple for the user who is technologically challenged (ex iPhone user)
That's perfect then. Just run that ruu and it'll be like a fresh device.
InflatedTitan said:
That's perfect then. Just run that ruu and it'll be like a fresh device.
Click to expand...
Click to collapse
Awesome. Just finished and it is like brand new again. Thanks!
Hi, i played around with my new OP3, and i wanted to root it. Since i'm noob at rooting, it went wrong. (i did it with twrp)
So first it just went in to bootloop, then i was still able to get to rcovery and stuff, but i followed a guide to fix bootloop, and that ****ed it even more up. The guide i followedet told me to use "OnePlus3_Unbrick_Tool"
After using "OnePlus3_Unbrick_Tool", i now cant even go into recovery anymore, the only thing i can do is go to bootloader, but when i'm in bootloader now, it wont connect proberly, so that i can use "flash twrp", so that i can use twrp recovery.
Also when i try to boot it, it because of "OnePlus3_Unbrick_Tool" goes into something, where it says "md5 checksum failed", and then restarts and does it again and again.....
I hope it's not bricked forever, pls help ))
have you tried re-flashing the stock or twrp recovery with adb sideload command?
if not give it a shot, it might work.
bonham1988 said:
have you tried re-flashing the stock or twrp recovery adb sideload command?
Click to expand...
Click to collapse
And how do you say I do that? I have tried using the "tool all in one", where you han flash both stock and twrp, but it doesnt seem to do anything, when i press them (and the device is in bootloader)
Godeske said:
And how do you say I do that? I have tried using the "tool all in one", where you han flash both stock and twrp, but it doesnt seem to do anything, when i press them (and the device is in bootloader)
Click to expand...
Click to collapse
Just boot into bootloader mode and through command prompt check if your phone is detected by typing fastboot devices. If its detected then you flash a new recovery again. Forget the toolkit, just look for instructions on how to install a custom recovery.
Sent from my OnePlus3 using XDA Labs
bonham1988 said:
Just boot into bootloader mode and through command prompt check if your phone is detected by typing fastboot devices. If its detected then you flash a new recovery again. Forget the toolkit, just look for instructions on how to install a custom recovery.
Sent from my OnePlus3 using XDA Labs
Click to expand...
Click to collapse
Okay i've tried that now, and it wont allow me unlock my bootloader from command prompt, and i cant do the flash while it's locked.. what to do?
Godeske said:
Okay i've tried that now, and it wont allow me unlock my bootloader from command prompt, and i cant do the flash while it's locked.. what to do?
Click to expand...
Click to collapse
In fastboot mode, did you manage to find your device on the computer? On Linux this is "sudo fastboot devices", on Windows it should be roughly similar.
simthadim said:
In fastboot mode, did you manage to find your device on the computer? On Linux this is "sudo fastboot devices", on Windows it should be roughly similar.
Click to expand...
Click to collapse
When im in fastboot mode in the bootloader, i can only find it in "device manager" as "marshall london device -> marshall london bootloader interface"
Godeske said:
When im in fastboot mode in the bootloader, i can only find it in "device manager" as "marshall london device -> marshall london bootloader interface"
Click to expand...
Click to collapse
Might seem a silly question but what phone are you using? If it is a OnePlus3 have you installed the correct drivers?
ghostofcain said:
Might seem a silly question but what phone are you using? If it is a OnePlus3 have you installed the correct drivers?
Click to expand...
Click to collapse
Pretty sure i have, but i have booked a session with oneplus costumer service now, so that they do it for me live lololol
bonham1988 said:
have you tried re-flashing the stock or twrp recovery with adb sideload command?
if not give it a shot, it might work.
Click to expand...
Click to collapse
Hey bonham,
The same thing happened to me but when I try to sideload it says I need 1.0.32 or higher to sideload this device
What should I do?
gavintoronto2016 said:
Hey bonham,
The same thing happened to me but when I try to sideload it says I need 1.0.32 or higher to sideload this device
What should I do?
Click to expand...
Click to collapse
Adb version is outdated. Just download the latest ones.
Sent from my OnePlus3 using XDA Labs
Hey guys, if there are some of you, who knows a lot about this, would you like to answer this comment? Idk maybe we could use teamviewer to help me or something
simthadim said:
In fastboot mode, did you manage to find your device on the computer? On Linux this is "sudo fastboot devices", on Windows it should be roughly similar.
Click to expand...
Click to collapse
Ohh i think i understand your question. YEs in command prompt I am able to find the device, it is connected.
(do you know a lot about this, maybe you could teamview me to help?))
Godeske said:
Ohh i think i understand your question. YEs in command prompt I am able to find the device, it is connected.
(do you know a lot about this, maybe you could teamview me to help?))
Click to expand...
Click to collapse
Hey!
I'm not the expert but I have played with my 1+3 enough to have some knowledge.
First of all, do not use "all in one tools", those do not put you in control.
Cool, so fastboot is detected, though you can't get into the recovery?
Step 1) make sure you have the latest version of "fastboot" and "adb" (Android Debug Bridge) and unlock the bootloader. This tread should be helpfull: http://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733
You need to do this, because otherwise we will not be able to proceed (i.e. the phone is to be 'unlocked' for what we are about to do).
Step 2) If you are ready than let's flash a new recovery (TWRP):
This is also step 2 in the thread mentioned above. Very important: "Once the flash has completed, Don't use the "Fastboot Reboot" Command Instead Unplug Your phone then Manually boot it into recovery by keeping Power + Volume Down button pressed."
So once you have flashed a new recovery using fastboot, than you should reboot your phone into the new recovery!
step 3)
Once in the new recovery (TWRP) go to advanced and to ADB sideload. Make sure your computer detects your device with the command "adb devices" and flash a new ROM. Just for simplicity use the official OOS 3.2.4.
This should do the trick. Before you go and try make sure you understand EVERYTHING I have written. Let me know if you have questions.
simthadim said:
Hey!
I'm not the expert but I have played with my 1+3 enough to have some knowledge.
First of all, do not use "all in one tools", those do not put you in control.
Cool, so fastboot is detected, though you can't get into the recovery?
Step 1) make sure you have the latest version of "fastboot" and "adb" (Android Debug Bridge) and unlock the bootloader. This tread should be helpfull: http://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733
You need to do this, because otherwise we will not be able to proceed (i.e. the phone is to be 'unlocked' for what we are about to do).
Step 2) If you are ready than let's flash a new recovery (TWRP):
This is also step 2 in the thread mentioned above. Very important: "Once the flash has completed, Don't use the "Fastboot Reboot" Command Instead Unplug Your phone then Manually boot it into recovery by keeping Power + Volume Down button pressed."
So once you have flashed a new recovery using fastboot, than you should reboot your phone into the new recovery!
step 3)
Once in the new recovery (TWRP) go to advanced and to ADB sideload. Make sure your computer detects your device with the command "adb devices" and flash a new ROM. Just for simplicity use the official OOS 3.2.4.
This should do the trick. Before you go and try make sure you understand EVERYTHING I have written. Let me know if you have questions.
Click to expand...
Click to collapse
Thank you, but i have not enabled "allow oem unlocking" in the developer settings when the phone worked, so i get a error message "FAILED (remote: oem unloc is not allowed)
What to do to unlock it then?
Bro, download 3.2.4 oos rom zip file from official link. Its around 1.3 GB. Just connect ur OP3 to computer. It will detect as MTP device.Im my computer it was in the name of RAIN Transfer the zip file to internal storage. Wipe cache. And select install option in TWRP and select the zip file u pushed and flash it. Best of luck..
jaganmohans said:
Bro, download 3.2.4 oos rom zip file from official link. Its around 1.3 GB. Just connect ur OP3 to computer. It will detect as MTP device.Im my computer it was in the name of RAIN Transfer the zip file to internal storage. Wipe cache. And select install option in TWRP and select the zip file u pushed and flash it. Best of luck..
Click to expand...
Click to collapse
Bro, if just it were that simple, but it's not.. It doesn't find the phone in my computer...
simthadim said:
Hey!
I'm not the expert but I have played with my 1+3 enough to have some knowledge.
First of all, do not use "all in one tools", those do not put you in control.
Cool, so fastboot is detected, though you can't get into the recovery?
Step 1) make sure you have the latest version of "fastboot" and "adb" (Android Debug Bridge) and unlock the bootloader. This tread should be helpfull: http://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733
You need to do this, because otherwise we will not be able to proceed (i.e. the phone is to be 'unlocked' for what we are about to do).
Step 2) If you are ready than let's flash a new recovery (TWRP):
This is also step 2 in the thread mentioned above. Very important: "Once the flash has completed, Don't use the "Fastboot Reboot" Command Instead Unplug Your phone then Manually boot it into recovery by keeping Power + Volume Down button pressed."
So once you have flashed a new recovery using fastboot, than you should reboot your phone into the new recovery!
step 3)
Once in the new recovery (TWRP) go to advanced and to ADB sideload. Make sure your computer detects your device with the command "adb devices" and flash a new ROM. Just for simplicity use the official OOS 3.2.4.
This should do the trick. Before you go and try make sure you understand EVERYTHING I have written. Let me know if you have questions.
Click to expand...
Click to collapse
Hey i have the same problem but this fix does not work for me.
So I have the bootloader unlocked and I can enter the bootload and my computer detects my device which is nice.
when I flash twrp on my phone trough CMD it doesnt work, my PC tells me that everything is okay but my phone will not boot into twrp and instead it will give me weird errors.
---------- Post added at 03:31 PM ---------- Previous post was at 02:56 PM ----------
this fix worked for me,
On the screen when the phone failed to md5 checksum, you've got several partition failed right? in red text.
- download this : https://www.androidfilehost.com/?fid=24591000424942573
and then extract.
- download platform tools attached below. extract in the same folder with first file you've downloaded.
- Boot your phone to fastboot mode, plug your usb, make sure adb and fastboot driver are installed.
- on the folder, hold shift and right click, click open command here
- type fastboot devices
- make sure your serial number appear.
- now flash the img of the missing file according to the partition in red text on your ms5 checksum failed one by one.
- e.g. "fastboot flash boot_aging boot_aging.img.
- make sure you flash all the missing partition.
- type fastboot reboot.
this will boot you to oos 3.1.2.
unfortunately I couldn't extract the newest oos dat. data. but you could always take the OTA
goodluck mate. sorry for my english
Godeske said:
Bro, if just it were that simple, but it's not.. It doesn't find the phone in my computer...
Click to expand...
Click to collapse
Hmm bad try installing all op3 drivers and see whether phone is detected or not. I was in the same situation previously. Pushing zip through adp terminal is painful process. I got device offline first,after solving that i got service not recognized issue. For solving that usb debugging needs to be enabled i stuck in that step.
can you enter recovery trough fastboot mode? I.e. if you are in fastboot mode you van use the volume keys to select recovery.
100% sure you can't enter recovery?
you can try Fast and pro's option. let us know!
So I tried to flash another rom by flashing TWRP and unlocking the bootloader, which worked and I then had installed Freedom Os. Then I locked the Bootloader to get the Message away, but know when you charge it or turn it on it is in an boot loop which repeats the Oneplus Logo what you normally see, but very short and after that it bobrates turns the screen off and it atart again. Or I can go into fastboot mode, but when I try to go into the recovery, it goes into the Boot Loop again. Is there a way to get the Original OS back? Ive already dopwnloaded it but I cant get in on there. Can you tell me how to fix it on my own?
[GUIDE] Mega Unbrick Guide for A Hard Bricked OnePlus 3 > METHOD 1
If you can access fastboot mode, connect the phone to a PC, then go to ADB and erase recovery using the command " fastboot erase recovery" and install TWRP 3.0.4-1 using the command " <fastboot flash recovery <recovery.zip/img> again.
Once you do that, boot into TWRP, go to wipe and wipe everything. Once you do that, transfer the stock OOS into the internal memory using copy-paste , then go to install , select the transferred file to install the OS or else go to advance setting in TWRP and select adb sideload and use the command "adb sideload <filename.zip>".
This should install the OS on the phone.
If you want to go complete stock, then you also need to install the stock recovery. Search the forum to get the relevent files or else you can download it from the OnePlus website and later on update to latest OS via OTA.
NEVER EVER LOCK THE BOOTLOADER , IF YOU'RE USING ANY ROM OTHER THAN STOCK OS AND STOCK RECOVERY
anup807 said:
If you can access fastboot mode, connect the phone to a PC, then go to ADB and erase recovery using the command " fastboot erase recovery" and install TWRP 3.0.4-1 using the command " <fastboot flash recovery <recovery.zip/img> again.
Once you do that, boot into TWRP, go to wipe and wipe everything. Once you do that, transfer the stock OOS into the internal memory using copy-paste , then go to install , select the transferred file to install the OS or else go to advance setting in TWRP and select adb sideload and use the command "adb sideload <filename.zip>".
This should install the OS on the phone.
If you want to go complete stock, then you also need to install the stock recovery. Search the forum to get the relevent files or else you can download it from the OnePlus website and later on update to latest OS via OTA.
NEVER EVER LOCK THE BOOTLOADER , IF YOU'RE USING ANY ROM OTHER THAN STOCK OS AND STOCK RECOVERY
Click to expand...
Click to collapse
Can you tell me how to go to adb? When doing it while being in fastboot I get the error "remote: Partition erase is not allowed"
revedar said:
Can you tell me how to go to adb? When doing it while being in fastboot I get the error "remote: Partition erase is not allowed"
Click to expand...
Click to collapse
Download Universal ADB software, download the latest version and install it.
TWRP 3.0.4-1
Official Oxygen OS 4.0.3
Official Recovery
Connect your phone to the PC and then navigate to installed folder, right click holding SHIFT key and select "Open command window here"
Inside command window type
adb devices
If all the drivers are installed properly, you should see you're device ID here.
then type
adb reboot bootloader
your phone will enter fastboot mode.
then type
fastboot devices
again you should see you're device ID here.
then follow the instruction , i've given earlier.
anup807 said:
Download Universal ADB software, download the latest version and install it.
TWRP 3.0.4-1
Official Oxygen OS 4.0.3
Official Recovery
Connect your phone to the PC and then navigate to installed folder, right click holding SHIFT key and select "Open command window here"
Inside command window type
adb devices
If all the drivers are installed properly, you should see you're device ID here.
then type
adb reboot bootloader
your phone will enter fastboot mode.
then type
fastboot devices
again you should see you're device ID here.
then follow the instruction , i've given earlier.
Click to expand...
Click to collapse
So i've downloaded the software, installed the driver and typed in cmd adb devices "adb devices List of devices attached" is returned, so it seems like there is going something wrong. Is it because the Driver is installed wrong or because "target reported max download size of 440401920 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.528s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.551s"
This is returned when trying to flash. Do I have to be in fastboot mode or something else to be able to follow your instructions? In Fast Boot is written that the Device State is locked and Secure Boot is enabled. I messaged Oneplus and hope they have a solution which can just unlock the Bootloader when being in fastboot mode, so everything is fine again. I hope you can help me, but I still wanna say thank your for now
Errr... fastboot can unlock the bootloader. fastboot oem unlock
emuandco said:
Errr... fastboot can unlock the bootloader. fastboot oem unlock
Click to expand...
Click to collapse
Thank you, but it dont works because i forgot to re-enable the oem modification and usb debugging in freedom os, maybe there is an option to do this without having this enabled but I didnt found it. So I wait for a helpful answer from somebody here or from Oneplus, I consider sending my smartphone to oneplus to let them repair it if I cant do it. Just saying that modding an S3, Asus transformer pad and nvidia shield is way easier.
never ever relock your bootloader while you in custom OS
oopstairs said:
never ever relock your bootloader while you in custom OS
Click to expand...
Click to collapse
Thank you for not helping me
revedar said:
Thank you for not helping me
Click to expand...
Click to collapse
Yeah I'm sorry I can't help you in your case. I'm just stating the fact. Sorry if I offended you.
Shouldn't it still be possible to reflash the properly signed official updates? TBH I never had such a problem and thus never had to cope with it. Same with recovery: http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img Try flashing this one with fastboot. It's the official one. By flashing this one you might fix your stuff over adb sideloading the official full update zips.
Try the unbrick guide provided in the 2nd post to your query. It should definitely help. Better contact OnePlus tech2 support and they'll flash your phone for you. They're really helpful.
emuandco said:
Shouldn't it still be possible to reflash the properly signed official updates? TBH I never had such a problem and thus never had to cope with it. Same with recovery: http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img Try flashing this one with fastboot. It's the official one. By flashing this one you might fix your stuff over adb sideloading the official full update zips.
Click to expand...
Click to collapse
I already tried to do this, but the console returns something like permission denied.
anup807 said:
Try the unbrick guide provided in the 2nd post to your query. It should definitely help. Better contact OnePlus tech2 support and they'll flash your phone for you. They're really helpful.
Click to expand...
Click to collapse
The MSM Software disconnects the smartphone while the process works
U cannot flash in adb while the bootloader is locked, u can not unlock the bootloader unless u can access ur OS, I am not sure y people was trying to get u to flash via fastboot the answer was provided to u in the 2nd post
^^^ This!
It's pretty much obvious fastboot flash will not work with a locked bootloader.
It's pretty obvious unlocking the bootloader will not work, while one can not access the OS.
Unbrick tool is the only option to bring it back to life, or sending it for RMA. If unbrick tool fails, try using different drivers and make sure it is connected with the stock cable (I've only tried with a Nilkin cable besides the stock one, which always failed at different stages during the process).
Not even sure drivers must be installed manually, I've never done that myself on Windows 10, as they were automatically installed (3 different's PC's, both on x86 and x64).
Which version of stock firmware did you last have? If it was 4.0.1 or earlier, then you can use
Code:
fastboot oem 4F500301
to issue a flash command even without unlocking the bootloader. If you are on that, then use that command and flash stock recovery and then flash stock zip.
rk2612 said:
Which version of stock firmware did you last have? If it was 4.0.1 or earlier, then you can use
Code:
fastboot oem 4F500301
to issue a flash command even without unlocking the bootloader. If you are on that, then use that command and flash stock recovery and then flash stock zip.
Click to expand...
Click to collapse
I had the most recent update installed. Is there a similar command at the moment?
revedar said:
I had the most recent update installed. Is there a similar command at the moment?
Click to expand...
Click to collapse
Don't think so.