help!!! opeplus 5 bricked - OnePlus 5 Questions & Answers

i bricked my oneplus 5 device then deleted the os and now i am stuck. i am unable to copy files to my internal storage.
adb and fastboot are not working too

pramod6472 said:
i bricked my oneplus 5 device then deleted the os and now i am stuck. i am unable to copy files to my internal storage.
adb and fastboot are not working too
Click to expand...
Click to collapse
Use the MSM tool, and you will be fine. Just have patience mate.

pramod6472 said:
i bricked my oneplus 5 device then deleted the os and now i am stuck. i am unable to copy files to my internal storage.
adb and fastboot are not working too
Click to expand...
Click to collapse
These might be helpful https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706 https://forum.xda-developers.com/oneplus-5/how-to/op5-collection-unbrick-tools-t3898870. Regarding on adb and fastboot if you are using windows disable EUFI Secure boot on windows https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/ there are also tutorials on youtube.

Related

[Q] Rooting help needed!

I am trying to root my new Nexus 4 and I am stumped. I am trying to follow efrant's instructions: http://forum.xda-developers.com/showthread.php?t=2010312
I successfully completed part D and now am trying to work through part E. I am stuck at step 3 of E: I downloaded SuperSU v 0.98 (is that really the one to get?) and I'm supposed to put that in /sdcard. Where is /sdcard? There is no SD Card in a Nexus 4. Is this a hidden folder somewhere? Do I have to make it? How can I see that folder? I am using a Mac and the Android File Transfer program window shows no sdcard folder anywhere.
Also: Why does another unlock guide talk (http://forum.xda-developers.com/showthread.php?t=2018179) about pressing "Build Number" seven times? Why doesn't efrant's guide mention this?
I don't follow this part at all. How do I put that damn file where it needs to be?
Just download the N4 toolkit. Will do everything you want.
Toolkit
Doggonit said:
I am trying to root my new Nexus 4 and I am stumped. I am trying to follow efrant's instructions: http://forum.xda-developers.com/showthread.php?t=2010312
I successfully completed part D and now am trying to work through part E. I am stuck at step 3 of E: I downloaded SuperSU v 0.98 (is that really the one to get?) and I'm supposed to put that in /sdcard. Where is /sdcard? There is no SD Card in a Nexus 4. Is this a hidden folder somewhere? Do I have to make it? How can I see that folder? I am using a Mac and the Android File Transfer program window shows no sdcard folder anywhere.
Also: Why does another unlock guide talk (http://forum.xda-developers.com/showthread.php?t=2018179) about pressing "Build Number" seven times? Why doesn't efrant's guide mention this?
I don't follow this part at all. How do I put that damn file where it needs to be?
Click to expand...
Click to collapse
When you plug the phone into the computer /sdcard is the folder that comes up. Just place it in there.
Sent from my Nexus 4 using xda app-developers app
DO NOT USE TOOLKITS. Especially if you're new to modding.
That's like saying, I want to overclockmy computer. Just give me a toolkit where I can one click and overclock my computer.
Read more here http://forum.xda-developers.com/showthread.php?t=1469909
Do it the proper way and download ADB drivers
http://forum.xda-developers.com/showthread.php?t=1514942 (enable USB debugging)
set up ADB environment
adb reboot bootloader
fastboot oem unlock
unlock bootloader on phone
download clockwork recovery or TWRP (i suggest TWRP)
put the .img file of recovery into your /platform-tools/
fastboot flash recovery <name-of-file>.img
then boot into recovery and there you can flash your ROM, gapps, kernel.
In the long run, IT WILL PAY OFF because eventually YOU will be faced with a problem with your phone and you won't be able to recover your phone because you dont know basic fastboot or adb commands all simply because you wanted to use a toolkit. People are already asking on how to use adb / fastboot in Q&A, we can reduce the clutter by not having people use toolkits and actually learning how adb / fastboot works when it isn't a very complicated thing to do at all
As stated in my original post, I am using a Mac. Not a PC. Therefore I don't use ADB, nor any other drivers. I also do not see, as stated before, any sdcard folder. I don't, I repeat, don't see it.
Doggonit said:
As stated in my original post, I am using a Mac. Not a PC. Therefore I don't use ADB, nor any other drivers. I also do not see, as stated before, any sdcard folder. I don't, I repeat, don't see it.
Click to expand...
Click to collapse
you dont need drivers on mac then... you can still ADB connect using mac.
simple: google search..... http://lmgtfy.com/?q=mac+adb first link
Doggonit said:
Where is /sdcard? There is no SD Card in a Nexus 4. Is this a hidden folder somewhere?
Click to expand...
Click to collapse
On the Nexus 4, /sdcard is the same as /storage/emulated/0. As mentioned earlier in the thread, this is the default location for native USB file transfer.
Sent from my Nexus 4

USB Mount via. Clockworkmod

Hello,
I managed to soft-brick my nexus 4 and want to reinstall a ROM, but I wiped the internal memory and there are no files on the Nexus 4. I cannot go anywhere but recovery and I have clockworkmod installed. Where do I go so I can copy and paste the ROM file on my Nexus 4?
Thanks
gokuman56 said:
Hello,
I managed to soft-brick my nexus 4 and want to reinstall a ROM, but I wiped the internal memory and there are no files on the Nexus 4. I cannot go anywhere but recovery and I have clockworkmod installed. Where do I go so I can copy and paste the ROM file on my Nexus 4?
Thanks
Click to expand...
Click to collapse
Try using TWRP, and use ADB to push your flashable ROM zip into your /sdcard directory. You can then use the recovery to flash it onto your phone.
The command to push files from your local desktop to your Nexus 4's internal memory is:
Code:
$ adb push flashable-rom-zip.zip /sdcard
You can try doing the same thing with CWM, but in my experience it doesn't work that well. With TWRP, on the other hand, ADB push commands work flawlessly.
So there is no other way to mount my Nexus to the computer?
gokuman56 said:
So there is no other way to mount my Nexus to the computer?
Click to expand...
Click to collapse
Not in recovery
gokuman56 said:
So there is no other way to mount my Nexus to the computer?
Click to expand...
Click to collapse
You cannot mount an MTP device as USB in recovery. Some devices have an app but they also have removable storages.
Sent from my Nexus 4 using Tapatalk 2
gokuman56 said:
Hello,
I managed to soft-brick my nexus 4 and want to reinstall a ROM, but I wiped the internal memory and there are no files on the Nexus 4. I cannot go anywhere but recovery and I have clockworkmod installed. Where do I go so I can copy and paste the ROM file on my Nexus 4?
Thanks
Click to expand...
Click to collapse
If I had that problem, I would probably flash back to stock Android. Google (finally) put the Nexus 4 factory images back online. I can't post links here just yet, but a quick Google search for "nexus factory images" should get you there.
Just run:
Code:
adb reboot bootloader
And then run flash-all for your OS.
It's easier if all those files are in the folder with fastboot and adb from the Android SDK. I'm trying to clear up confusion between the codenamed "mako" and "occam", both linked with the Nexus 4. I think "mako" is the hardware and "occam" is the software, but if they are actually two slightly different phones, and you make your problem worse, I can't take responsibility.

Phone now has no OS!

Had LG G2 2 hours
Rooted, TWRP installed. Downloaded new ROM and copied to storage (whilst phone was running). Booted in to recovery wiped Rom (stupidly) then went to install new Rom which is not there. So I have no OS...
Unless it's in a weird directory I need to copy it across again however Mount under TWRP settings does not bring up windows explorer to allow me to copy it again (USB Drivers all installed I thought after root process). Had it got an SD card slot I could have burnt it to that in my PC and then put it in the phone.
Any ideas please
jamesbond_28_007 said:
Had LG G2 2 hours
Rooted, TWRP installed. Downloaded new ROM and copied to storage (whilst phone was running). Booted in to recovery wiped Rom (stupidly) then went to install new Rom which is not there. So I have no OS...
Unless it's in a weird directory I need to copy it across again however Mount under TWRP settings does not bring up windows explorer to allow me to copy it again (USB Drivers all installed I thought after root process). Had it got an SD card slot I could have burnt it to that in my PC and then put it in the phone.
Any ideas please
Click to expand...
Click to collapse
"adb sideload" -> please type into the searchbox. Would help you a little more but busy currently. however this will help you.
So you wiped your complete storage? lol.
Try to sideload your rom.
http://android-revolution-hd.blogspot.de/2013/12/ow-to-use-adb-sideload.html
ckyy said:
So you wiped your complete storage? lol.
Try to sideload your rom.
http://android-revolution-hd.blogspot.de/2013/12/ow-to-use-adb-sideload.html
Click to expand...
Click to collapse
Yes nightmare. And ADB doesnt look for the faint hearted either. is there no way of mounting in TWRP?
jamesbond_28_007 said:
Yes nightmare. And ADB doesnt look for the faint hearted either. is there no way of mounting in TWRP?
Click to expand...
Click to collapse
I wouldn't bother trying to get it to work. Sideloading is way faster.
http://forum.xda-developers.com/showthread.php?t=2588979
1. Download and install it. Put the rom inside ADB folder. Put twrp in sideload mode.
2. Open your adb folder and shift-right click. Select open command propt here.
3. This is what you type in your CMD -> adb sideload flash.zip (flash.zip is obviously replaced by your rom name).
ckyy said:
I wouldn't bother trying to get it to work. Sideloading is way faster.
http://forum.xda-developers.com/showthread.php?t=2588979
1. Download and install it. Put the rom inside ADB folder. Put twrp in sideload mode.
2. Open your adb folder and shift-right click. Select open command propt here.
3. This is what you type in your CMD -> adb sideload flash.zip (flash.zip is obviously replaced by your rom name).
Click to expand...
Click to collapse
Thanks. 'device not found'...
jamesbond_28_007 said:
Thanks. 'device not found'...
Click to expand...
Click to collapse
Have you installed all drivers?
Gesendet von meinem LG-D802 mit Tapatalk
jamesbond_28_007 said:
Thanks. 'device not found'...
Click to expand...
Click to collapse
Ok. Needed google universal ADB driver by Koush (as windows 8). So it reached 100% but phone back on LG flashscreen...
jamesbond_28_007 said:
Ok. Needed google universal ADB driver by Koush (as windows 8). So it reached 100% but phone back on LG flashscreen...
Click to expand...
Click to collapse
All good. Thanks for all the help and apologies for being such a muppet.

Help with F2FS and getting files onto a wiped tablet

I am trying to get the F2FS file structure and I can't find the SlimKat Rom or GAPPS files on my tablet. All I have is a laptop with Win8, which has copies of the needed files on there. Is there a way that I can get the .ZIP files onto my tablet, or make my laptop work like an OTG-USB? I'm not in the US and I don't know if I can get an OTG cable any time soon.
Thanks.
steve626 said:
I am trying to get the F2FS file structure and I can't find the SlimKat Rom or GAPPS files on my tablet. All I have is a laptop with Win8, which has copies of the needed files on there. Is there a way that I can get the .ZIP files onto my tablet, or make my laptop work like an OTG-USB? I'm not in the US and I don't know if I can get an OTG cable any time soon.
Thanks.
Click to expand...
Click to collapse
So is your situation:
Tablet is wiped
Partitions are formatted to f2fs
Recovery still functioning
If that is the case, then just use the sideload function. For TWRP, its under the advanced menu. Start sideload mode in TWRP, then on the PC open a command window in the directory where the files are (google to see how to add that function to the windows right click menu...really handy). Then:
adb sideload yourfilenamehere
Do it for both files.
Done.
brizey said:
So is your situation:
Tablet is wiped
Partitions are formatted to f2fs
Recovery still functioning
If that is the case, then just use the sideload function. For TWRP, its under the advanced menu. Start sideload mode in TWRP, then on the PC open a command window in the directory where the files are (google to see how to add that function to the windows right click menu...really handy). Then:
adb sideload yourfilenamehere
Do it for both files.
Done.
Click to expand...
Click to collapse
Even Recovery was stuck in a loop. I used a toolkit to flash back to all stock, it's working. Maybe I'll mess around with it again. Thanks.

[Guide] [Unbrick] How to revive a hard bricked Moto G5

This guide is for hard bricked Moto G5 Cedric
Hard bricked means a device which can not enter bootloader mode normally
This method has now been confirmed working
Works with XT1672 XT1670 XT1671 XT1675 XT1676 XT1677 (and most likely all others and if you ask if it will work on your version I will just copy & paste this to you!)
Smaller Image
Thanks to Luka Panio, Omega, and nift4 we now have a smaller image size
Goto This github page and under assets download mmcblk0.img.gz
Extract mmcblk0.img from the zip file to PC
Previous Larger Images
Mega
Download mmcblk0.zip image from Mega
Create your own mega account and import the file into your mega account. Log into your account and download it from your own account
Extract mmcblk0.img from mmcblk0.zip to PC
Or for those of you who can't use mega or have unstable Internet I've split the large file size into smaller multiple zip files. You must download each part and then extract using an unzip tool like winrar or 7zip
Android File Host
Download mmcblk0.zip mmcblk0-part1.zip and mmcblk0-part2.zip from Android File Host
Extract mmcblk0.z01 from mmcblk0-part1.zip
Extract mmcblk0.z02 from mmcblk0-part2.zip
Extract mmcblk0.img from mmcblk0.zip (If prompted point to mmcblk0.z01 and mmcblk0.z02 but it shouldn't ask if all files are in the same folder)
Requirements
Freshly formatted microSD card 16gb if using the smaller image or at least 32gb if using the previous larger images (It needs to have at least 31.3gb free after formatting - if it displays as less you will need to buy a 64gb microSD card or use the smaller image)
7zip
Linux mint live usb/dvd
USB card reader
Method
The BEST method to flash the sdcard with mmcbk0.img file is to use LINUX!
Windows users have no need to install Linux on their PC, you can run Linux from a bootable usb-stick that is at least 8gb or a dvd
Do not run Linux as a virtual machine on Windows! Use the live USB/DVD
0) Put the Moto g5 on mains charge until you have finished flashing the sdcard so it's fully charged ready for the boot test!
1) Run Linux, preferably cinnamon or mate versions of Linux Mint
2) Insert the sdcard in pc or card reader and open "Disks" app
3) In "Disks" app select sdcard and you will see the sdcard partitions
4) Press "-" to delete the partition (delete all partitions if there is more than one)
5) Press "+" to create a new one and name it mmcblk0, set FAT(FAT32) file format and press "CREATE"
6) Press "Play" button to mount the sdcard, look to see what path the sdcard has (/dev/sd??) and then close the "Disks" app
7) Go to Desktop, open "Computer" and navigate to the location where the img file is extracted (mmcblk0.img)
8) Open the window where img file is with root (right click on window and select "open as root")
9) In root window open the Terminal (right click on window and select "open terminal")
no need to type "su" in terminal, it has root already (see notes if using Linux live usb/dvd)
10) Type in terminal the command written below and don't forget to eliminate that "1" from the sdcard path,
that "1" can make the difference between the phone booting or not!!!!!
Things to note
Linux Live dvd doesn't have open as root so just open in terminal and add sudo to the start of the commands
I've included this in the commands below
If you get a status error just remove status=progress from the terminal command below
Terminal comands
- if your sdcard is seen like " /dev/sdb1"
in terminal apply this command:
Code:
sudo dd bs=4M if=mmcblk0.img of=/dev/sdb status=progress oflag=sync
-if your sdcard is seen like " /dev/mmcblk0p1"
in terminal apply this command:
Code:
sudo dd bs=4M if=mmcblk0.img of=/dev/mmcblk0 status=progress oflag=sync
and the flashing process should start
When it finishes, test the sdcard in the phone and it should boot!
If you get a size error of the sdcard in terminal you have to change the sdcard and try again!
Thanks to @vaserbanix for the original version of this guide
Re-flash Stock Firmware
Once the phone is in bootloader mode you can flash stock firmware via fastboot
Note that in order to flash gpt the firmware MUST be the same or newer than the version currently on your phone
Firmware can be download from Here
Once you have firmware that is the same or newer than your current version you can remove the sd card and run these commands (assuming you have fastboot all setup on your pc)
If you get a security downgrade error when you try to flash gpt.bin or bootloader.img then the firmware you are trying to flash is too old!
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
I might consider doing this if you explained what this loader.img is?
Is it something one would flash to recover their G5?
Exanneon said:
I might consider doing this if you explained what this loader.img is?
Is it something one would flash to recover their G5?
Click to expand...
Click to collapse
Potentially - its used to boot off the sd card so those with a bricked phone can access the bootloader through booting it off their sd card & then flash the firmware via fastboot
See
https://www.aryk.tech/2017/02/how-to-unbrick-debrick-qualcomm-android.html?m=1
I hope the solution is achieved soon
Here you go:
https://cloud.wdata.de/index.php/s/JK2by8YBQCSrsof
Device Info:
Cedric XT1676 Retail
LineageOS 14.1
TWRP 3.2.1 (32bit)
staffe said:
Here you go:
https://cloud.wdata.de/index.php/s/JK2by8YBQCSrsof
Device Info:
Cedric XT1676 Retail
LineageOS 14.1
TWRP 3.2.1 (32bit)
Click to expand...
Click to collapse
Thanks for uploading it
Hello, I followed all the steps of the link, using a 16gb card and the file here hung and nothing, the phone does not start.
In my case it is an xt1676 which only turns on the led and blinks when I connect it to the pc by usb or the wall charger.
takoa said:
Hello, I followed all the steps of the link, using a 16gb card and the file here hung and nothing, the phone does not start.
In my case it is an xt1676 which only turns on the led and blinks when I connect it to the pc by usb or the wall charger.
Click to expand...
Click to collapse
I take it the programme wrote the loader image successfully to sdcard
So either the person who uploaded the Loader.img interrupted the extract & so its corrupted or this phone can't boot off the sd card with this method
It does say it may take a while to boot but who knows
If anyone else can upload a Loader.img using the methods in the first post so there's a comparison please do
Yeah right.
What is strange to me, although maybe it is, is the size of the file hung here, 165 mb.
the 16gb card is formatted in fat32, is it correct?
Does the DiskImageRev2 program automatically create the card to be bootable?
Why install the qualcomm drivers if the phone does not have to be connected to the PC? It is assumed that the phone will boot in bootloader mode and there only need the adb / fastboot controllers.
I do not mind to keep trying since the phone I give for lost at the moment.
Can someone return to the first post with an xt1676?
Thank you.
TheFixItMan said:
I'm trying to work on a solution for guys with a hard bricked moto g5 but as I no longer own this device anymore I need someone to provide the following
Requirements
Rooted moto g5
Busybox installed
Terminal emulator installed
What I need
In terminal emulator type su and grant superuser access
Then type
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/Loader.img bs=1024 count=168960
Wait for the command prompt to return (it may take a few mins)
Post the Loader.img file created on the root of sdcard here
Click to expand...
Click to collapse
https://drive.google.com/file/d/1H2Qkc1XKbr7Is46n5xdCFlgiuIH1m-vE/view
Device : XT1677
takoa said:
Yeah right.
What is strange to me, although maybe it is, is the size of the file hung here, 165 mb.
the 16gb card is formatted in fat32, is it correct?
Does the DiskImageRev2 program automatically create the card to be bootable?
Why install the qualcomm drivers if the phone does not have to be connected to the PC? It is assumed that the phone will boot in bootloader mode and there only need the adb / fastboot controllers.
I do not mind to keep trying since the phone I give for lost at the moment.
Can someone return to the first post with an xt1676?
Thank you.
Click to expand...
Click to collapse
I presume it's needed for some devices who use different methods of flashing stock firmware
Someone else has uploaded an image file so you can try that one from a xt1677
Yes formatted fat32 - you should just have to select the drive the sdcard card is assigned to on your pc in the program eg f: and then select image file & then write - and accept the warning
It should make it bootable
Iv no idea if this method will work with this device
then it does not work in this model or the file posted here is wrong. Because I have done it as here is exposed and nothing.
I'm going to try the one from xt1677
TheFixItMan said:
So either the person who uploaded the Loader.img interrupted the extract & so its corrupted or this phone can't boot off the sd card with this method
It does say it may take a while to boot but who knows
Click to expand...
Click to collapse
Hmm, there haven't been any error messages on my side. I pulled the image again with above dd-command. I also tried with adb shell instead of terminal emulator but it's always the same file with the exact same file size.
staffe said:
Hmm, there haven't been any error messages on my side. I pulled the image again with above dd-command. I also tried with adb shell instead of terminal emulator but it's always the same file with the exact same file size.
Click to expand...
Click to collapse
I assume the file is correct - it's probably more the case of this phone doesn't support this method
If I get my hands on this device again in the future I can properly test things but at the moment all I can do is throw out ideas for people to try
Think I'll leave it now as without the device there's not a lot I can do
nothing, it does not work. it does not start :crying:
As I said, only the LED flashes when connected by USB or charger.
I recommend using rufus for flashing it to the sd card, it has never failed me yet, and supports up to 16gb.
Edit: I have the XT1675, if anyone would find it useful for me to post this variant's bootloader then I'd be happy to do so.
Edit again: Isn't dd used for writing an image to flash storage for later booting rather than extracting it?
takoa said:
nothing, it does not work. it does not start :crying:
As I said, only the LED flashes when connected by USB or charger.
Click to expand...
Click to collapse
It seems, some qualcomm devices need a full mmcblk0 dump to be able to boot from sdcard (e.g. LG G5)¹. I don't know if thats the case for our device but you can give it a try:
Loader_XT1676.zip Uncompressed filesize: ~4GB
¹ "The Loader method requires a full ROM Dump also known as a full blk0 backup of a working LG G5 H850 correctly flashed or written on a pretty good and fast class 10 SD Card."
Source: https://www.aryk.tech/2018/03/lg-g5-h850-unbrick-solutions.html
Exanneon said:
Edit again: Isn't dd used for writing an image to flash storage for later booting rather than extracting it?
Click to expand...
Click to collapse
dd basically clones/copies the source-data block by block to another disk, partition or (img-)file.
staffe said:
It seems, some qualcomm devices need a full mmcblk0 dump to be able to boot from sdcard (e.g. LG G5)¹. I don't know if thats the case for our device but you can give it a try:
Loader_XT1676.zip Uncompressed filesize: ~4GB
¹ "The Loader method requires a full ROM Dump also known as a full blk0 backup of a working LG G5 H850 correctly flashed or written on a pretty good and fast class 10 SD Card."
Source: https://www.aryk.tech/2018/03/lg-g5-h850-unbrick-solutions.html
dd basically clones/copies the source-data block by block to another disk, partition or (img-)file.
Click to expand...
Click to collapse
Thanks for the info - if someone can try this full Loader.img & let me know if it works I'll write up a guide
Iv added the guide to the first post if people want to test
Like Iv said before I no longer own this device - I have not tested this & it may not work
Feel free to add potential solutions to help those with bricked devices

Categories

Resources