Database Users

[Q] Did I brick it or not?

I tried to root my 3G XOOM (MZ606) last night and eventually I did brick it but I am not sure. I did definitely dl the wrong img file (as I didnt read here before Anyway everything of the procedure went fine till I had to type the commands (like adb remount) after reboot. Actually the XOOM does not seem to connect to my wireless hotspot anymore (is that due to a missing key?) and it remains in the boot up screen (just the MOTO logo)
Is there any solution to get the XOOM reconnected may be? Can anyone push me into the right direction? Do I really need those certain cable (someon mentione in any thread here)?
--
thanx a lot for your help
Michael

if you have ANY type of screen coming up, its not bricked. Depending on your situation, you just need someone whos good with ADB/Fastboot to get things back to where they need to be.
---------- Post added at 01:19 PM ---------- Previous post was at 01:17 PM ----------
go into recovery and wipe Everything/ factory reset, wipe cache, and go into advanced and wipe dalvik cache. then flash any rom available here in the DEV section.

hmmm I found out how to do that
>go into recovery and wipe Everything/ factory reset, wipe cache
but what means
>and go into advanced
? There is no advanced option at the recovery menu. So may be thats an otion once I choose 'reboot system now'?
And just for my understanding, that
>then flash any rom available here in the DEV section
is not necessary just may be in my interest, right?
--
Thanx anyway, great help
Michael

It might help us if you tell us what model your Xoom is...3g/wifi - us/uk - all the specifics.
Hopefully you knew this before you installed the wrong image.
Then we can help you get back to where you need to be.
And 'flashing any ROM here in the development section' is what got you here in the first place so I wouldnt do that.

Hola,
well I will definitely be more careful now. Actually I did read about those issue with the Wifi only device before but... So what specifications I could deliver?
So far I saw on the screen also printed on its backside its an MZ606 purchased from MOTOROLA china directly. I possibly wouldnt have tried to lunlock and root if those gadget could at least connect to the google market... sorry for complaining but the cn.MOTOROLA market does have very few and mainly chinese apps only. Further on before the procedure I stuck in now the OS has been Android 3.1
Hope those background information allows some more conclusions but
right now I am still trying to figure what kenfly ment by mentioning
>go into advanced and wipe dalvik cache
If I understand for example those guys http://forum.xda-developers.com/showthread.php?t=560207 right (hopefully it is allowed to put that link here) it seems to be a procedure before flashing a new ROM. What I am asking myself is do I right now not have a working one anymore? May be I misunderstood in the past but so far I thought the sequence is unlock> root> custom rom... and so far I think I am not successfully rooted yet so I wouldnt be supposed to flash a new ROM. So I think what I need to do now is to get my device successfully rooted before wiping the 'dalvik cache', am I wrong?
--
Cheers Michael

[email protected] said:
Hola,
well I will definitely be more careful now. Actually I did read about those issue with the Wifi only device before but... So what specifications I could deliver?
So far I saw on the screen also printed on its backside its an MZ606 purchased from MOTOROLA china directly. I possibly wouldnt have tried to lunlock and root if those gadget could at least connect to the google market... sorry for complaining but the cn.MOTOROLA market does have very few and mainly chinese apps only. Further on before the procedure I stuck in now the OS has been Android 3.1
Hope those background information allows some more conclusions but
right now I am still trying to figure what kenfly ment by mentioning
>go into advanced and wipe dalvik cache
If I understand for example those guys http://forum.xda-developers.com/showthread.php?t=560207 right (hopefully it is allowed to put that link here) it seems to be a procedure before flashing a new ROM. What I am asking myself is do I right now not have a working one anymore? May be I misunderstood in the past but so far I thought the sequence is unlock> root> custom rom... and so far I think I am not successfully rooted yet so I wouldnt be supposed to flash a new ROM. So I think what I need to do now is to get my device successfully rooted before wiping the 'dalvik cache', am I wrong?
--
Cheers Michael
Click to expand...
Click to collapse
Did you flash the ClockworkMod recovery before rooting [after unlocking], and if so, which version?
If you don't have that installed, you wouldn't see the advanced option in the recovery menu.
You have a wifi model and I think the wifi hardware is all the same so you could flash the US Xoom system image and that should solve your access and updates problem, But since it's a HongKong Xoom, there may be some differences, so try it out but use caution.

hey guys looks as I dont get the message. I am still stuck at the recovery screen. I did
>go into recovery and wipe Everything/ factory reset, wipe cache
but whats next? Rebooting does not change anything, still the same logo screen only. So am I supposed to apply a proper image by 'apply update...'?
--
Cheers

You say you have a 3G Xoom - but the MZ606 is WiFi only.
Do you remember what image you applied to mess things up in the first place?

sure, the name is rootboot.img
It should be the one from 3*w.addictivetips.com, '/?attachment_id=45936'. I separated the link as I dont wanna mislead anyone here but I hope its still possible to follow up
--
Thanx for your help
-sorry for the 3G thing, no idea why I did type that. It definitely is a WiFi only
-and i idd not do any clockworld thing before or what ever. It has been just an ordinary MZ606 automatically updated to the 3.1 android version, but unlocked. For unlocking I used the android.sdk and typed the command to do so, thats everything I did before getting stucked with those rooting procedure

Hey guys dont leave me alone. I may tend to do another stupid thing ... well I am capable to find former posts about how to recover so on but as U asked some more details it seems to be depending on which exact device I have and what exactly I did before. So I hope U could still guide me to the harbor

hey.ur on 3.1 right?
I assume you have knowoedge on fasboot.
Find the appropriate boot.img for ur device then flash it via fasboot.
Maybe u flash the wrong boot.img
---------- Post added at 07:15 AM ---------- Previous post was at 07:11 AM ----------
Or go back to stock. http://developer.motorola.com/products/software/

well the problem (after data/factory reset and wiping cache) is the application (android.sdk) still cant find the device... I assume thats due to device still stuck at the M logo and I cant tpe in the WiFi password for example.
So how could I flash another ROM to the device without having the OS working on it properly?

[email protected] said:
well the problem (after data/factory reset and wiping cache) is the application (android.sdk) still cant find the device... I assume thats due to device still stuck at the M logo and I cant tpe in the WiFi password for example.
So how could I flash another ROM to the device without having the OS working on it properly?
Click to expand...
Click to collapse
Do you have the proper drivers installed? Make sure you get them from Motorola.
Your device should be seen if ADB and Fastboot are set up correctly.
Once you can see the device I would use fastboot to reinstall the proper image (again from Motorola - they will have the correct Image for your Chinese Xoom)

yes I do have the proper drivers from M and they worked perfectly before once I flashed the wrong image. May be my problem is too simple for U guys or as I am not capable to deliver appropriate information to get some help.
For my understanding it is obvious why my pc can't get the device as the device obciously cant get an wireless IP without knowing the WPA2 key and I cant type in the wireless key as the OS (on that device) does not fully start up. Which wireless device works without any basic configuration? So does mine I guess even though I am not expert... but even I deactivated any security measures on my router it still the device didn't connect (check only at the routers active device list)
Once again my question: How could I flash another ROM to the device without having the OS working on it properly? I think the OS is (part of) those wrong IMG i did flash before, so I assume I will never get it working
--
Regards

Can u go to fastboot?
When the xoom bootup press vol down immediately.it says starting fastboot etc.
If your pc can detect it then flash the correct images to ur xoom.
Btw lets talk on yahoo msgr. Pm me ur email.im free this time.

princenoob said:
Can u go to fastboot?...[/UOTE]
I keep he decvice at the recovery menu for 2 days now but yes I can "go to fastboot" too but again that doesnt change anything regarding connecting my device to the wireless router. Why none of U guys replies on those obvious fact? The XOOM like all other devices I know will not connect to any wireless hotspot without any confirmation (may be a password) on its UI and as I cant get into the UI...
May be its the wrong directory for thes question. Is it possible to shove to Q&A?
Click to expand...
Click to collapse

No no.why would you connect it on wireless router in the first place.connect it on ur pc! So if the pc detected it.then flash thru adb.

oh thanx for that hint. I thought it works only connected via wifi. Well now the SDK states a number instead of the device name or MZ606. I hope its not my HTC Desire but I did deactivate the wireless on there.
So if it really is the MZ606 (I can take the battery off the HTC just to make sure should I go back to the original image first, then install clockworld, then root?
--
thanx in advance

Sdk only detects devices connected to pc.so your phone has nothing to do with it.did u already download the firmware for ur xoom?the link i post awhile ago download the rom there.do you know how to flash it thru fastboot?.if yes then i think u can revive ur xoom.
---------- Post added at 10:30 AM ---------- Previous post was at 10:25 AM ----------
if you have ur original copy of ur boot.img then flash it.if not better flash from stock.the use this tutorial to root. http://forum.xda-developers.com/showthread.php?t=1242241
Please hit thanks if i help you in anyway.

[email protected] said:
oh thanx for that hint. I thought it works only connected via wifi. Well now the SDK states a number instead of the device name or MZ606. I hope its not my HTC Desire but I did deactivate the wireless on there.
So if it really is the MZ606 (I can take the battery off the HTC just to make sure should I go back to the original image first, then install clockworld, then root?
--
thanx in advance
Click to expand...
Click to collapse
[email protected], you seem to be lacking some very basic understanding of how all of this works on the Xoom. No wonder you felt frustrated.never in a million years would I guess you would try to flash an update or recover your Xoom via a wireless connection.
That said, hopefully you are now on the right track. I wish you good luck.

[GUIDE] How to install Oxygen OS

ive been seeing enough and more posts asking about flashing OxygenOS. I'll try and explain in simple terms. read carefully and only then try it.
I TAKE NO RESPONSIBILITY IF YOU SPOIL YOUR DEVICES. YOU ARE DOING THIS AT YOUR OWN RISK!
if you have a custom recovery skip to step 7
1. Your devices needs a custom recovery. to install one you need to be rooted. to root u need an unlocked bootloader. OnePlus claims that you wont loose warranty on rooting and unlocking so your safe there unless u do something wrong. so be cautious.
2.for unlocking rooting and flashing i recommend using Bacon Root Toolkit. even though i know to do it the Oldschool way. this is much more simple and u really cant go wrong with the toolkit its NoobFriendly. download the toolkit from the following link and install it along with the drivers. http://www.wugfresh.com/brt/
3. once installed choose the version of CM you are running. the toolkit will automatically download all required files. once in u will have to set up the drivers. the instructions for that are well explained in the toolkit please follow it there.
4. after the drivers are set up first u need to unlock. REMEMBER UNLOCKING WILL CLEAR ALL DATA!. so backup all required data.for the internal SD card u can connect the phone to the computer as an MTP device and copydata, for the apps you can backup using Helium and copy the helium folder to the computer. please do not post comments telling that you lost all data there is NO WAY to recover that data once you unlock.
5.press UNLOCK in the toolkit, it will guide you through the process. after unlock when you switch on the phone itll be as good as new you will have to go through the procedure of logging into google etc. once done head over to settings enable developer options and tick ADB. DONT FORGET TO DO THIS
6. Now you need to root your device. by default the toolkit uses SUPERSU to root and TWRP as custom recovery its perfectly fine unless you intend on changing it later on stick to these two. remember to tick CUSTOM RECOVERY under the root option. press root and follow the steps. it pretty much does everything u jut have to keep confirming.
7. Hoping that right now your rooted and have a custom recovery, if not please go through the previous steps.
now we need to download the oxygenOS head over to the forum and download or use this link https://oneplus.net/oxygenos, once downloaded check the size it should be 705MB incase its not the download again may be the download got corrupted.
8. IMPORTANT STEP FOR NEWBIES
once u download u have ONE .zip file named "oxygenos_1.0.0.zip" extract that file and u will get a folder named "oxygenos_1.0.0" leave it there DONT EXTRACT ANY FURTHER!. the folder will contain two files "oxygen_1.0.0_flashable.zip" "oxygen_1.0.0_flashable.md5" leave them as they are. preferably copy this folder containing the two files to the root of the phone. in simple terms put it in your phone memory without putting it into any other folder.
9. Now you have your files ready you need to head over to the recovery. two ways of doing it. you can go to settings developer options and tick advance reboot. now when u press reboot u get an option to reboot recovery and bootloader. choose recovery.
another way of getting to recovery is shut down the phone hold the buttons POWER+VOLUME DOWN once the phone comes on leave the power button and hold VOLUME DOWN till the recovery shows up.
10. Once your in TWRP u have an option to backup your rom. You could do this as a precaution if anything goes wrong u can restore from this backup file. fro backing up press backup and choose the partitions you want to backup and swipe to backup. the backup should be around 2-3gb i think. once backed up copy the file from the TWRP folder on your phone to the computer.
11. since you are changing the ROM completely you need to factory reset once before flashing. in TWRP press WIPE and swipe to factory reset. and go back to home dont reboot device.
12. FLASHING THE ROM: in TWRP press install in the list find the folder oxygenos_1.0.0. in that folder click on the file "oxygen_1.0.0_flashable.zip" and then swipe to flash. the flashing can take a while dont do anything while its in progress.
13.once flashed reboot system. the first reboot will take time let it happen do not get worried and try restarting just let it take its time it has to set up everything for u.
14. Now you should be having OXYGEN OS... use it appreciate it rather than criticizing it. incase u feel like customizing it try out XPOSED. though it is still in testing for L it shouldnt be too buggy. gravityBox is compatible with lollipop.
15. incase you feel like going back to CM.. head over to the toolkit connect the phone (remember to enable ADB) doesnt matter which build u set. press FLASH STOCK+UNROOT choose the CM build you want and let it do its work. follow the instructions.
some may point out that the toolkit has an option to flash the rom as well. yes it does but i wont dive into that now. this method is simple enough. but if u know how to do it that way u sure can
PS: KEEP YOU BATTERY FULLY CHARGED WHILE DOING ALL THIS. INCASE THE PHONE DIES WHILE FLASHING ITLL BE BRICKED.
please correct me if i went wrong anywhere.
hope this helps.

shoaib30 said:
ive been seeing enough and more .....
Click to expand...
Click to collapse
There is absolutely no need for this thread - it's all been covered before. Flashing OOS is no different to any other custom ROM.
You text/formatting is abysmal. You recommend using the toolkit, WTF? This device is the easiest ever created for unlocking/rooting and using a toolkit is a BAD idea as if it goes wrong you will end up confused and not knowing what to do next. Anyone who can't unlock / root / flash TWRP on this device should not be attempting to install a custom ROM anyway.
What you have posted is actually more confusing for a 'noobie' than what is already out there, I'd suggest this thread should probably be deleted and people with questions can simply search and find the useful instructions which already exist.

SimonTS said:
There is absolutely no need for this thread - it's all been covered before. Flashing OOS is no different to any other custom ROM.
You text/formatting is abysmal. You recommend using the toolkit, WTF? This device is the easiest ever created for unlocking/rooting and using a toolkit is a BAD idea as if it goes wrong you will end up confused and not knowing what to do next. Anyone who can't unlock / root / flash TWRP on this device should not be attempting to install a custom ROM anyway.
What you have posted is actually more confusing for a 'noobie' than what is already out there, I'd suggest this thread should probably be deleted and people with questions can simply search and find the useful instructions which already exist.
Click to expand...
Click to collapse
im sorry ill take it off. i had ppl asking me in person so i thought i can explain here and send the link to them. my bad

Please don't create duplicate threads. There are already threads open that cover this topic.
Thread closed.

No Os Installed!

I left my phone charging and came back to get it. It was stuck on the google logo, I am able to boot into recovery but it says No Installed.
Is their anything else I can do other than flash it again.
I was thinking maybe the wrong partititon was checked, but everything looks fine.

Krooked22 said:
I left my phone charging and came back to get it. It was stuck on the google logo, I am able to boot into recovery but it says No Installed.
Is their anything else I can do other than flash it again.
I was thinking maybe the wrong partititon was checked, but everything looks fine.
Click to expand...
Click to collapse
Assuming that the ROM is still there, you can dirty flash the ROM zip over it, and see if it works. There's no harm in trying that.
But "No OS Installed" simply means that your /system or /boot parition are not detected (means, they are empty). Now of course, the last resort is to flash the ROM all over again.

Krooked22 said:
I left my phone charging and came back to get it. It was stuck on the google logo, I am able to boot into recovery but it says No Installed.
Is their anything else I can do other than flash it again.
I was thinking maybe the wrong partititon was checked, but everything looks fine.
Click to expand...
Click to collapse
You need to provide more information. Are you on the stock ROM or a custom ROM? Stock recovery or TWRP? Had you made any changes to the device recently?

Someone please help. I just rooted my 6P. Did a little bit of doing. Phone would never boot just the round circles. So went into TWRP and tried to wipe to start fresh, not it says no OS installed. I have no ROMS's on the phone. No boot images. Been a while since I've done this. Really need help on this one. Thanks.

Download the dp3 , boot into bootloader, connect to PC run installer script after you unzip the factory image " flash all" sit back and wait for phone to reboot.
---------- Post added at 10:30 PM ---------- Previous post was at 10:29 PM ----------
It's that simple.

Hey thanks a lot. Couple things, and I apologize in advance for not knowing this already.
1) what's dp3
2) how do I run installer script?
I know I shift right click and open a cmd window within fastest - where I'll unzip the file - and I know how to get the phone into Bootloader.
Again, sorry for asking for simple explanations.

StormCell said:
Someone please help. I just rooted my 6P. Did a little bit of doing. Phone would never boot just the round circles. So went into TWRP and tried to wipe to start fresh, not it says no OS installed. I have no ROMS's on the phone. No boot images. Been a while since I've done this. Really need help on this one. Thanks.
Click to expand...
Click to collapse
Download any ROM ( like pure Nexus) and gapps
You can use USB otg to flash the ROM using twrp or transfer the ROM file from your PC to your phone in twrp (it supports mtp)
Simply flash ROM and gapps and viola
Sent from my Nexus 6P using XDA Labs

Ok, I'm gonna tackle this tomorrow. Any recommendations on a good ROM and Kernel (Verizon). I made nice donations long ago to Franco and ROM Manager.
Thank again, everyone!

StormCell said:
Someone please help. I just rooted my 6P. Did a little bit of doing. Phone would never boot just the round circles. So went into TWRP and tried to wipe to start fresh, not it says no OS installed. I have no ROMS's on the phone. No boot images. Been a while since I've done this. Really need help on this one. Thanks.
Click to expand...
Click to collapse
Download the required ROM and gapps, connect your phone to pc , type in google, Mini adb and fastboot, a page on XDA itself will come, download it, its small and install.
Then copy the ROM and gapps package to the location of the installation of the application.
Now open your recovery and tap on adb sideload, and swipe(twrp)
Go to your PC, open adb application a cmd will appear, type adb devices, it will start a daemon then will give you your device number, a number should appear. Then type
Adb sideload """"name of your ROM package""".zip
It will start installing, wait for few minutes.
Do the same for gapps
Adb sideload " name of gapps package ".zip
Then reboot
Its fixed
NOT Sent from my GT-N7100 using the XDA-developers mobile app

i42o said:
Download the dp3 , boot into bootloader, connect to PC run installer script after you unzip the factory image " flash all" sit back and wait for phone to reboot.
---------- Post added at 10:30 PM ---------- Previous post was at 10:29 PM ----------
It's that simple.
Click to expand...
Click to collapse
Why are you telling him to install the Developer Preview? He wouldn't want that unless he's actually asking for it, which he isn't.

StormCell said:
Ok, I'm gonna tackle this tomorrow. Any recommendations on a good ROM and Kernel (Verizon). I made nice donations long ago to Franco and ROM Manager.
Thank again, everyone!
Click to expand...
Click to collapse
Please continue the discussion in the other thread that you posted this question in, as I said, let's not create duplicate discussions.

StormCell said:
Hey thanks a lot. Couple things, and I apologize in advance for not knowing this already.
1) what's dp3
2) how do I run installer script?
I know I shift right click and open a cmd window within fastest - where I'll unzip the file - and I know how to get the phone into Bootloader.
Again, sorry for asking for simple explanations.
Click to expand...
Click to collapse
Developer preview 3 is a Android N preview and it is very fluid, battery life is good on stock and reason I recommend this because it is simple to do, gives you good options within the ROM and is good overall but that's just my opinion.
---------- Post added at 12:35 PM ---------- Previous post was at 12:32 PM ----------
Heisenberg said:
Why are you telling him to install the Developer Preview? He wouldn't want that unless he's actually asking for it, which he isn't.
Click to expand...
Click to collapse
Dude, I'm trying to help. Beats what you said, you going detective mode on him while I'm just giving him an easy solution. Read a book or something

i42o said:
Dude, I'm trying to help. Beats what you said, you going detective mode on him while I'm just giving him an easy solution. Read a book or something
Click to expand...
Click to collapse
Lol. Maybe you missed the title under my name.
The dev preview isn't what he asked for, it isn't an easy solution, it isn't easy to come back from if he doesn't like it, it isn't even remotely what he needs. What he's looking for is a simple way to get his phone booted up and working again (a very simple request), and what you're suggesting is he install a beta OS (a complicated "solution").
If you really have a problem with a moderator requesting that a member posts in one place at a time (as per our rules), then I'm gobsmacked. If you'd care to look at the advice I gave him in the guide thread where he also posted you'd notice that I gave two solutions that:
A) Actually address the simplicity of his problem.
B) Give two simple, easy to execute, solutions that are the most common solutions you'll ever see anyone give a member in his situation. Solutions that don't involve having to install a developer preview that he never asked for.
I get that you're trying to help him, but the "solution" you provided him isn't right for his situation at all. There was no need to become defensive and aggressive when this was pointed out.

Vishal Vignesh said:
Download the required ROM and gapps, connect your phone to pc , type in google, Mini adb and fastboot, a page on XDA itself will come, download it, its small and install.
Then copy the ROM and gapps package to the location of the installation of the application.
Now open your recovery and tap on adb sideload, and swipe(twrp)
Go to your PC, open adb application a cmd will appear, type adb devices, it will start a daemon then will give you your device number, a number should appear. Then type
Adb sideload """"name of your ROM package""".zip
It will start installing, wait for few minutes.
Do the same for gapps
Adb sideload " name of gapps package ".zip
Then reboot
Its fixed
NOT Sent from my GT-N7100 using the XDA-developers mobile app
Click to expand...
Click to collapse
I'm copying files over to my Nexus now using MTP from TWRP. Can't I just copy evrything over and flash that way? Man, this seems so much more complicated than back in the day. Thanks.
Crap, wrong thread! Sorry! Got confused.

StormCell said:
I'm copying files over to my Nexus now using MTP from TWRP. Can't I just copy evrything over and flash that way? Man, this seems so much more complicated than back in the day. Thanks.
Crap, wrong thread! Sorry! Got confused.
Click to expand...
Click to collapse
Sure, this method is for those who do not wanna copy the zip package to the PC/don't have it
Sent from my GT-N7100 using XDA-Developers mobile app

[HELP] I would like to go into developer options but I can not

Hello to all,
first of all sorry for my English, i'm using google translate, I do not know if you can help me here.
I bought this jewel from Gearbest and arrived yesterday.
I would like to unlock the bootloader and root it following this wonderful guide , but I can not get into developer options, I get the error "the settings application crashed abnormally"
I wanted to do this via the toolkit, but in EDL mode the phone is not recognized, maybe because in developer options I have to select the OEM UNLOCK.
The only good thing is that it recognizes usb debugging mode (at least I think) because I see the debug notification icon.
I can not understand where it came from, I went into bootloader mode but did not release me information.
From the onscreen screen I can only provide these info:
model number zte a2017g
version android 6.0.1
kernel version 3.18.20
build number zte a2017gv1.0.0b11
baseband version th.2.0.c1.9-00050-m8996faaaanazm
The MiFlavor version is 4.0
The smartphone does not receive OTA updates. I downloaded the global version (b05) of Nougat, the update with Android started I did not find it (I renamed the rom file in update.zip and put in the root of the SD CARD). I tried through recovery mode but it does not do anything to me, it's as if the smartphone was locked in everything and for everything.
I'm doing well ? How do I update when I download the rom? Can you please help me? Is there any system to interact with this smartphone and unlock it? I do not want to keep a phone that I can not update and root it.
Thanks in advance to who will help.

UPDATE:
I tried to manually install the downloaded ROM, but in recovery mode it does not flash the new rom ... the phone does not even try it !!!
It's as if the phone was locked in everything and I only have to keep the installed rom.
Some idea ?

SuDGLaD said:
UPDATE:
I tried to manually install the downloaded ROM, but in recovery mode it does not flash the new rom ... the phone does not even try it !!!
It's as if the phone was locked in everything and I only have to keep the installed rom.
Some idea ?
Click to expand...
Click to collapse
Hey I would recommend clearing the data for settings if you can. To do this go to your launcher, find the settings icon and either drag or hold down or do whatever it takes to get to the app info. I haven't used stock in a long time so idk. But then go into storage and clear data. Then go and try again.
I do have one question though. How did you get usb adb debugging enabled if you didn't get into developer options at all?
For the second half of your question you won't be able to flash anything without first unlocking the bootloader and flashing TWRP onto the device. For the devices recovery idk which one you meant, but it needs to be TWRP. Good luck!

JTruj1ll0923 said:
Hey I would recommend clearing the data for settings if you can. To do this go to your launcher, find the settings icon and either drag or hold down or do whatever it takes to get to the app info. I haven't used stock in a long time so idk. But then go into storage and clear data. Then go and try again.
I do have one question though. How did you get usb adb debugging enabled if you didn't get into developer options at all?
For the second half of your question you won't be able to flash anything without first unlocking the bootloader and flashing TWRP onto the device. For the devices recovery idk which one you meant, but it needs to be TWRP. Good luck!
Click to expand...
Click to collapse
Thanks to my friend, without doing anything, suddenly, he made me enter the developer options menu.
I've been able to do the rest.
Now I have the phone with unlocked bootloader, root and TWRP installed.
Do not ask me how I got the debug without going into the menu, I could not answer you ... it will remain a mystery !!!
I take advantage of your availability: can I flash the zip of the official ROM through TWRP? Or is there a risk that the phone goes into brick mode?

SuDGLaD said:
Thanks to my friend, without doing anything, suddenly, he made me enter the developer options menu.
I've been able to do the rest.
Now I have the phone with unlocked bootloader, root and TWRP installed.
Do not ask me how I got the debug without going into the menu, I could not answer you ... it will remain a mystery !!!
I take advantage of your availability: can I flash the zip of the official ROM through TWRP? Or is there a risk that the phone goes into brick mode?
Click to expand...
Click to collapse
What rom are you trying to install? Usually you will be absolutely fine.

SuDGLaD said:
Thanks to my friend, without doing anything, suddenly, he made me enter the developer options menu.
I've been able to do the rest.
Now I have the phone with unlocked bootloader, root and TWRP installed.
Do not ask me how I got the debug without going into the menu, I could not answer you ... it will remain a mystery !!!
I take advantage of your availability: can I flash the zip of the official ROM through TWRP? Or is there a risk that the phone goes into brick mode?
Click to expand...
Click to collapse
JTruj1ll0923 said:
What rom are you trying to install? Usually you will be absolutely fine.
Click to expand...
Click to collapse
You can't flash an official zip through TWRP, it will just fail. No brick.
Edit: didn't read OP lol. If you want to update, you have to flash the stock recovery (there are stock recovery flashable zips on the Download Center) then install the update, then get TWRP again. Or you can install a custom ROM (I recommend one based on stock MiFavor 5.0, I think that the best one is ADM Team V3 (the one that's not based on B13), this way you can simply download, flash in TWRP, and you'll be done

JTruj1ll0923 said:
What rom are you trying to install? Usually you will be absolutely fine.
Click to expand...
Click to collapse
Thanks :good:
Choose an username... said:
You can't flash an official zip through TWRP, it will just fail. No brick.
Edit: didn't read OP lol. If you want to update, you have to flash the stock recovery (there are stock recovery flashable zips on the Download Center) then install the update, then get TWRP again. Or you can install a custom ROM (I recommend one based on stock MiFavor 5.0, I think that the best one is ADM Team V3 (the one that's not based on B13), this way you can simply download, flash in TWRP, and you'll be done
Click to expand...
Click to collapse
Thanks mate !!
I installed the rom that you suggested to me, I find it very good, but this phone has very poor support (MiFavor).

SuDGLaD said:
Thanks :good:
Thanks mate !!
I installed the rom that you suggested to me, I find it very good, but this phone has very poor support (MiFavor).
Click to expand...
Click to collapse
Very poor support? It's going to get Android O, and it's got at least 1 update per month (officially). It's unclear whether that ROM you installed will be updated since it's based on an older version, but the latest (B13) breaks a bunch of stuff like Google Play Games, Maps, the GPS works awfully...

Choose an username... said:
Very poor support? It's going to get Android O, and it's got at least 1 update per month (officially). It's unclear whether that ROM you installed will be updated since it's based on an older version, but the latest (B13) breaks a bunch of stuff like Google Play Games, Maps, the GPS works awfully...
Click to expand...
Click to collapse
No no ... do not get me wrong.
My reference is to rom, MiFlavor is really bad. I come from 3 Xiaomi smartphones and I can assure you is another world.
The smartphone is really nice and well balanced (apart from the just enough battery) and I would replenish it a thousand times. :fingers-crossed::good:

HardBricked OP5, plz help! :(

Hi, guys.
Today, my OP5 decided to troll me. I was using normally him, when suddenly it started to lags pretty bad. I restarted and he continued to lags and freeze. I made a wipe cache via stock recovery (i didnt made any change at all in it, no unlocked bootloader, no root). That's when my nightmare begins. It begins to bootloop. Sometimes i was able to start the boot animation, but then it just restarts to the beginning. I tried a lot of tips, wiping cache, system, etc. Then, i left it charging. When i tried to turn on again, it worked like nothing ever happened to him. I made a backup of my personal data fast, scared to him suddenly restart again. After that, i decided to made a Factory Reset, clean up everything. When i did it, he started the lag and freezes again. I was at lost. That's was when i decided to use the official unbrick tool, to make the cleanest OP5 ever possible. I grabbed the archives from this link and followed this tutorial. When i was executing the programa, in the userdate.img, he showed a error. When i saw it, i just stopped and closed the program. Now, my OP5 is hardbricked. The only sign of life that i get from him is when i connect him at the PC. I can identify it as qualcoom 9008, but when i try to run the program, he just fail and show me error 258.
Plz, i need some orientations. I have been read things for about 10 hours and didnt found a solution. I live abroad for any oneplus tech center, and i believe, for the other posts that i read, that online tech support wouldn't help me a lot. I really don't like to make this kind of post but i am kind of desesperate. I dont have money to afford another phone
Again, sry to disturb you all. Sry if i broke some rule of the forum too. And sry for my bad english, i hope that i was able to communicate right.
EDIT: I just tried in another computer. Same error appears. :'(

Hummm why follow a Unbrick Topic with tools for ...3T ?
Maybe you have a encryption problem, all your Tools/Topic are so old for the actual versions (Oreo 8.X OOS / 8.1 OOS)
I advise to you (in the first time), to flash this TWRP (using fastboot, very simple) just follow this guide : here
If you can flash TWRP, your phone is not bricked, you will boot in TWRP:
- Format Data > tape "yes" > Reboot in TWRP
- Copy/Past xXx 10.0 ROM to test, install and xXx Rom will fix/install for you the best OOS Custom ROM for your OP5 with a great Aroma Installer.
If TWRP with this rom work perfectly, you wil able to restore a official stock OOS for sure, just flash original/stock recovery (fastboot), wipe all data/partitions, install your OOS rom and it's fine

I think @cidsantiago says they bootloader isn't unlocked.
He needs to know that unlock the bootloader implies lost all /sdcard data and also installed apps and settings) before start the TWRP install process...
Pho3nX said:
Hummm why follow a Unbrick Topic with tools for ...3T ?
Maybe you have a encryption problem, all your Tools/Topic are so old for the actual versions (Oreo 8.X OOS / 8.1 OOS)
I advise to you (in the first time), to flash this TWRP (using fastboot, very simple) just follow this guide : here
If you can flash TWRP, your phone is not bricked, you will boot in TWRP:
- Format Data > tape "yes" > Reboot in TWRP
- Copy/Past xXx 10.0 ROM to test, install and xXx Rom will fix/install for you the best OOS Custom ROM for your OP5 with a great Aroma Installer.
If TWRP with this rom work perfectly, you wil able to restore a official stock OOS for sure, just flash original/stock recovery (fastboot), wipe all data/partitions, install your OOS rom and it's fine
Click to expand...
Click to collapse

Pho3nX said:
Hummm why follow a Unbrick Topic with tools for ...3T ?
Click to expand...
Click to collapse
I used the tools for 5. Just the procedure that i get from this topic. :T I am gonna try the method that you gave me now brb.
EDIT: Just tried this. My cellphone cant be recognized in fastboot devices. As a said, i am not getting any response for him, just when i plug it in the PC. So i wasn't able to unlock bootload or anything like that. I tried just to plug it and see if fastboot was able to identifying it, but it wasn't.

bartito said:
I think @cidsantiago says they bootloader isn't unlocked.
He needs to know that unlock the bootloader implies lost all /sdcard data and also installed apps and settings) before start the TWRP install process...
Click to expand...
Click to collapse
Yes, it should not be unlocked. But at the moment, i am taking anything, really. I just want to use my phone.

cidsantiago said:
Yes, it should not be unlocked. But at the moment, i am taking anything, really. I just want to use my phone.
Click to expand...
Click to collapse
Wipe your device data from the stock recovery.
You loss the settings and downloaded apps but not requires to unlock the bootloader.

bartito said:
Wipe your device data from the stock recovery.
You loss the settings and downloaded apps but not requires to unlock the bootloader.
Click to expand...
Click to collapse
I can't access recovery anymore, as i said. The only sign of life that i get is when i connect it in the PC.

I guess i have to do something to restore the basics partitions of my cellphone. Like recovery, boot, etc. But i just have the official tool to do that. There is another way? Like transfering directly by the COM port?

Have you tried following this guide? https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706
---------- Post added at 01:30 PM ---------- Previous post was at 01:26 PM ----------
I had the same exact problem with my old One plus One. Spent like 4 days trying to unbrick it. That msm tool did the fix for me. Also, in that link to the guide you provided, doesn't it flash the Chinese version of the OS? If that's the case, I don't think it was a good idea to do so lol

Mash1ro said:
Have you tried following this guide? https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706
---------- Post added at 01:30 PM ---------- Previous post was at 01:26 PM ----------
I had the same exact problem with my old One plus One. Spent like 4 days trying to unbrick it. That msm tool did the fix for me. Also, in that link to the guide you provided, doesn't it flash the Chinese version of the OS? If that's the case, I don't think it was a good idea to do so lol
Click to expand...
Click to collapse
In one of the links, it had the OOS and the HOS. I tried to use the msm tool in one of them, but it didnt worked I'm gonna try the archives in this link that you gave me. It may work brb with updates.

Don't worry though, it happens to plenty of people. It happened to me as well, and everyone eventually fixes it. It is unlikely that it is a hardware problem, so just following the correct steps should get it working. Keep trying stuff out, it's very good that your computer recognizes it as a qualcomm port, as far as I know that's all you need to flash the necessary things in order for it to boot.

I am getting the same error 258 in this post. :T I posted there to see if the OP can help me. But thx for your help @Mash1ro

Mash1ro said:
Don't worry though, it happens to plenty of people. It happened to me as well, and everyone eventually fixes it. It is unlikely that it is a hardware problem, so just following the correct steps should get it working. Keep trying stuff out, it's very good that your computer recognizes it as a qualcomm port, as far as I know that's all you need to flash the necessary things in order for it to boot.
Click to expand...
Click to collapse
Thx for your support! I will continue to try stuff

Try reading the comments from this post as well https://forum.xda-developers.com/oneplus-3t/help/hard-bricked-op3t-t3574720/page2
2 of the people had the same error as you, and one of them solved the issue by changing the USB port.
---------- Post added at 02:26 PM ---------- Previous post was at 02:23 PM ----------
But don't use the same files and all that stuff, since that's for the 3T. Try to pick out the things that might help but use the files for the OnePlus 5 only

After try the unbrick procedure in 3 different PCs, using about 10 different USB ports, i still getting the same error in the same step. When downloading cache.img, he stuck in about mid bar, and shows me the warning: SendProgramCommand Failed, Error: 258". Besides that, he turns on the green led and stop being recognize by the PC. Then i have to hold power and turn off the green led. :T Maybe i can use a linux to access the partitions?

cidsantiago said:
After try the unbrick procedure in 3 different PCs, using about 10 different USB ports, i still getting the same error in the same step. When downloading cache.img, he stuck in about mid bar, and shows me the warning: SendProgramCommand Failed, Error: 258". Besides that, he turns on the green led and stop being recognize by the PC. Then i have to hold power and turn off the green led. :T Maybe i can use a linux to access the partitions?
Click to expand...
Click to collapse
it seems like a hardware problem, i was facing this on different phone ( 5X )

Apayah said:
it seems like a hardware problem, i was facing this on different phone ( 5X )
Click to expand...
Click to collapse
yeah... But it is kind of weird. He was running smoothly, until suddenly started lag and freeze. He didn't fall or any of that... I think is just a defective phone. Doesn't find another explanation to that.

I think your best option is to RMA the device through OnePlus. Since you haven't rooted it or anything, they should repair it for you.

david19au said:
I think your best option is to RMA the device through OnePlus. Since you haven't rooted it or anything, they should repair it for you.
Click to expand...
Click to collapse
I already contact the store that i bought to get my warranty. Unfortunately, i didn't bought it in oneplus.net, bcs they don't deliver in my country. I am hoping that everything work out

Guys, in the end, i RMA my device back to the seller and gonna have a refund Thank you for your help. So sad that this phone came faulty :T
Best regards to you all!