[HELP] Find 7 X9077 WIFI and Bluetooth error - Oppo Find 7 and 7a

Hi, yesterday I did try flash CM11s Oneplus rom but end up bricking my phone.
I did it by flashing each files thru fastboot flash from CM11s, the phone was stucked.
Now, I returned to ColorOS 1.20, then tried 1.2.1i. WIFI and Bluetooth are not working. Both MAC address show unavailable.
I tried many ways to get it back, but still no luck.
/persist folder is empty now.
Please anybody I really appreciate for the help..

I'm having the exact same issue. No matter how many times I flash different roms (color os, cm, etc) my bluetooth and wifi are not available. Hope someone can post a solution soon. My Find 7a is model x9007.

find 7
have both of you guys tried a factory reset...and then flashed the rom after...also clear cache data twice before flash
also Cm11 is not ready for the find 7 X9077 QHD as they have not worked out the 2k screen for it yet

Thanks for the suggestion. Unfortunately I did try this method a few times without luck. I'm going to hunt down find 7 kernel and try flashing that on its own. Fingers crossed.

droidan - did you manage to find an answer? I'm still stuck.

No, now my phone is in even worst.
I mistakenly flashed 4.2 modem without erasing bootloader(aboot, tz, rpm, sbl1, and kernel) from find 5.
(Solution for wifi/bt not working in find 5)
It is bricked now.
I am waiting Engineer if they may send me the recovery tools.
Addel and Well-E from Oppo at oppoforums.
I will share as soon as my phone got a second chance back from the dead.

I'm also having trouble with my Oppo Find 7a. Yesterday I tried to flash CM11s, sadly I got a boot loop, i managed to go back to ColorOS 1.2.1i, but now my Wifi and Bluetooth is broken. Do you have any suggestions?

Guys be careful, as far as I know cm11s does NOT work at all for the find 7 even though it has similar hardware. Coldbird had it somewhat working but stopped development.
Try using the driver fix for broken wifi and Bluetooth from this thread.
http://www.oppoforums.com/threads/tutorial-unified-storage-layout-for-oppo-find-7a.17952/
And guys, read and understand before flashing any random rom. You could run the chance of fully bricking your phone and not recovering it at all. It almost happened to me but aut0mated helped and taught me a thing or two. Good luck, play it safe. Make sure you're flashing ROMs for your phone model only, unless you want a pretty paperweight
Sent from my Find7u running Unified Gummy using Tapatalk Pro

i am having issue with the usb tethering, i am able to ping out to 8.8.8.8 and other destination but unable to browse. any idea on this?

droidan said:
No, now my phone is in even worst.
I mistakenly flashed 4.2 modem without erasing bootloader(aboot, tz, rpm, sbl1, and kernel) from find 5.
(Solution for wifi/bt not working in find 5)
It is bricked now.
I am waiting Engineer if they may send me the recovery tools.
Addel and Well-E from Oppo at oppoforums.
I will share as soon as my phone got a second chance back from the dead.
Click to expand...
Click to collapse
try this here if you have no mac address or wifi
Here is a complete unbrick procedure also here is the link to the forum post

Related

[Q] SM-T217s - my first ever brick.

Hi friends. Long time lurker here.
I've had many Samsung phones and many other android devices, but this is my first brick.
I had flashed the rooted SM-T217s rom, and the wifi wasn't working, so I tried to reflash it, at which point everything went wonky. I searched the forums and found some threads on bricked 217s's, but nothing specific to my situation.
The tablet went to the emergency firmware update screen, and I haven't been able to get Kies to even recognize it. I try to Odin back to the latest stock (B8) but it fails at 'Get PIT for mapping.' My google-fu tells me this is not a good thing.
Am I hosed here? What else can I try?
Thanks XDA, you're my only hope.
joshuaerda said:
Hi friends. Long time lurker here.
I've had many Samsung phones and many other android devices, but this is my first brick.
I had flashed the rooted SM-T217s rom, and the wifi wasn't working, so I tried to reflash it, at which point everything went wonky. I searched the forums and found some threads on bricked 217s's, but nothing specific to my situation.
The tablet went to the emergency firmware update screen, and I haven't been able to get Kies to even recognize it. I try to Odin back to the latest stock (B8) but it fails at 'Get PIT for mapping.' My google-fu tells me this is not a good thing.
Am I hosed here? What else can I try?
Thanks XDA, you're my only hope.
Click to expand...
Click to collapse
Good news, I guess. I was able to flash TWRP recovery and the stock rooted rom from another computer, but now Wifi is borked and there's no network connection. HALP.
joshuaerda said:
Good news, I guess. I was able to flash TWRP recovery and the stock rooted rom from another computer, but now Wifi is borked and there's no network connection. HALP.
Click to expand...
Click to collapse
Okay well I fixed it.
Turns out, the problem was that I was using Odin on a VM on my Mac. I had tried to use a PC, but I think the USB controller was too old, so that failed too. I had to use Heimdall to flash each of the partitions from the B8 zip manually. It worked, and I'm back in business, though not rooted. I suppose I'll wait until there's a better way to root before I try it again.
254336992952
​
joshuaerda said:
Okay well I fixed it.
Turns out, the problem was that I was using Odin on a VM on my Mac. I had tried to use a PC, but I think the USB controller was too old, so that failed too. I had to use Heimdall to flash each of the partitions from the B8 zip manually. It worked, and I'm back in business, though not rooted. I suppose I'll wait until there's a better way to root before I try it again.
Click to expand...
Click to collapse
You should have made a backup. I used twrp recovery flashed a rom same thing wifi wouldnt work so I restored back. If you get it working again make a backup imo. Goodluck.
IAMRUDYT said:
​
You should have made a backup. I used twrp recovery flashed a rom same thing wifi wouldnt work so I restored back. If you get it working again make a backup imo. Goodluck.
Click to expand...
Click to collapse
same here, I have the rom, but hesitated on the firmware, waiting to see if someone gets the wifi working, not to many developers here for this tablet.
sm t217s
Ok guys. Heres my deal with this TAB. Ive rooted... Unrooted. wipe wipe wipe wippty wipe . WiFi not working. Fixed it with NB8. So here now I sit with:
----NB8 Wifi works---
----TWRP-----
Yup, pathetic i know. I cant even get the supersu to flash. TWRP wont move it over to flash off external sd card. Im not hip to abd plus i heard you leave yourself wide opento visitors when using that.
Ive eye hustled a thread on here that some friends are getting back together to rock it on a custom rom so my fingers are crossed. This tab is so neglected i mayjust go get the 210r. But i really dont want to. So my question is....
Can someone please give me links to files that work with the NB8 stock firmware. Some of the links are outdated after sprint uploaded the new bootloader. We are a small community on this tab so lets stick together on this. I dont think cynogen isgoing to do anything for it. As they concentrate on thier new phone which looks pretty sweet by the way. K im done. Going to wait for help and play with this htc one s
thats been collecting dust.
Rooted
Sent from my SM-T217S using XDA Premium 4 mobile app

Blu Advance 4.0 L A010U ROMs

Hey guys,
I really need to find at least the stock ROM for the new-ish Blu Advance 4.0L (model A010U), because the most recent OTA update unforgivingly bricked mine. Now I want to try to re-flash the stock ROM, but I am also open to custom ROMs, if there are any available. Please help me out! Thanks in advance
I am really surprised no one has replied yet, but again I am facing the same problem and I've been searching the Internet for one month now and I found absolutely nothing for this phone (specifically for version A010U).
So I am going to post a different question in the hopes that someone will read it and help us out:
I have two Blu Advance 4.0 L A010U phones, which are identical except for the color (white and green). They were manufactured a month apart one in 10/2015 and one in 9/2015.
Unfortunately after only a couple of months of light use and for no apparent reason (did not drop it, or wet it, etc) it started going through a boot loop. It will start, show the "bold like us" logo then restart again without making it to the operating system at all. Like I said I've been looking for over a month to find a ROM (stock or modded) to reflash but with no luck. Then I had an idea. Since I have the other identical phone that's working fine, is there a trick I can do using the working phone to create a ROM that I can use in my broken one. By the way, the non working phone will allow me to get into the recovery menu, but unfortunately nothing happens if I wipe the cache or even if I reset to factory defaults.
Anyone knows what's causing that "boot loop", how to fix it and where to find a ROM or even "extract" or "create" one using a working Advance 4.0 L ???
Thank you very much!
Man I wish I knew. I'm kinda a novice. I have the same phone with a similar problem... I downloaded the recent ota update and the first time it said it couldn't unzip it. I tried again and it seemed to work but when it rebooted into recovery it said there was an error... So it won't boot up, it just goes to the screen that says "no command". I'm pretty sure the there's a way to make a copy of the working ROM but since I don't use a PC for anything I've never taken the time to learn the method.
Deuler93 said:
Hey guys,
I really need to find at least the stock ROM for the new-ish Blu Advance 4.0L (model A010U), because the most recent OTA update unforgivingly bricked mine. Now I want to try to re-flash the stock ROM, but I am also open to custom ROMs, if there are any available. Please help me out! Thanks in advance
Click to expand...
Click to collapse
I just got ahold of a couple of these devices myself and am in the process of going through all the in's and out's of them....I'm a Samsung nerd so I haven't messed with something like these in a while but I got one (that was supposedly dead bricked per the lady friend of mine I got them from) at least able to boot into factory mode and recovery via ADB and just as I'm posting this I'm in adb shell going through the device's internal memory.....so we'll see what all I find and can pull out of this one and possibly know enough to post an intelligible reply with solutions next time
The boot looping sounds like a common problem with these and when I get to that point I'm going to get rid of the stock bootanimation.zip ASAP and try something else. I get the idea that these things aren't exactly power houses built for much so the littlest thing or small bug in their coding could lead to this kind of crap happening.
Hopefully you figure yours out before I toss these out the window! lol
Cheers y salud!
---------- Post added at 02:27 AM ---------- Previous post was at 02:20 AM ----------
good.m. said:
Man I wish I knew. I'm kinda a novice. I have the same phone with a similar problem... I downloaded the recent ota update and the first time it said it couldn't unzip it. I tried again and it seemed to work but when it rebooted into recovery it said there was an error... So it won't boot up, it just goes to the screen that says "no command". I'm pretty sure the there's a way to make a copy of the working ROM but since I don't use a PC for anything I've never taken the time to learn the method.
Click to expand...
Click to collapse
Forgot to add a couple things about your post, sorry! I beleive (and I just started digging into this phone) that the no command part is the locked bootloader these phones appear to have. I think it was a combo of holding both volume buttons down from a powered off state then pressing power button on that came up with the option for factory mode or recovery (which led to the sad 'no command' droid), i went into factory mode and theres an option for Tp Upgrade which Im assuming is F/W or something similar but I just hooked up to the PC and in that mode it's reading the internal and external memory of the phone and that's about where I'm at so far.
Wow! I'm surprised this thread is still going.
Anywho, I found a repository that is storing the default ROM for the 4.0L. The files were just added recently. I would have liked to have seen a custom Lollipop ROM made by now, but this device is far too irrelevant to get any attention, unfortunately. Just root and forget, I guess.
I can't wait to try it, thank you! And btw, were you able to get root successfully and if so, how?
Deuler93 said:
Wow! I'm surprised this thread is still going.
Anywho, I found a repository that is storing the default ROM for the 4.0L. The files were just added recently. I would have liked to have seen a custom Lollipop ROM made by now, but this device is far too irrelevant to get any attention, unfortunately. Just root and forget, I guess.
Click to expand...
Click to collapse
Hey Deuler93 -
You have my respect for digging out that BLU ROMs link and sharing with the rest of us. I downloaded the one for my Advance and used SP flash tool to flash the phone that was stuck on a boot-loop. Of course first I had to download and install the MediaTeK drivers for USB connectivity with my PC. Everything worked flawlessly, no glitches what so ever. All these links are easily found and widely available online if anyone is interested I can share here too. I just hope that this boot-loop was due to some software glitch and not hardware failure. Everything seems to work fine for now, keepint my fingers crossed it will NOT happen again.
Well, one less headache to worry about. By the way we're not that far, if you're ever in the Chicago area, I owe you a beer or something. Thank you!
Hi guys !
Thank you very much for the Advance 4.0L Roms.
I have successfuly recovered my phone, but the IMEI got lost.
So, I need to root it in order to recover the IMEI, but I just can´t get success on any method :
Kingroot
Framaroot
Towelroot
is there another way to root it ?
Thank you very much.
I got temporary root using the kingroot apk. But it messed things up and I don't trust it anymore. None of the other mentioned methods worked for me either, maybe try the PC kingroot method
well this helps one thing
good.m. said:
Man I wish I knew. I'm kinda a novice. I have the same phone with a similar problem... I downloaded the recent ota update and the first time it said it couldn't unzip it. I tried again and it seemed to work but when it rebooted into recovery it said there was an error... So it won't boot up, it just goes to the screen that says "no command". I'm pretty sure the there's a way to make a copy of the working ROM but since I don't use a PC for anything I've never taken the time to learn the method.
Click to expand...
Click to collapse
umm. . . when the no command option comes up just press the power button and the rest of options will appear. doesnt exactly solve your problem however unless you have the ZIP file to install, which is what I'm looking for.
What might happen if a ROM is used for another blu phone. ??
A similar phone as well.
Plz advise.
Damn! This thread just keeps going!
I haven't even looked here in a while, so I will bunch my commentary here. I'm also salaried now, so I bought into a OnePlus X (onyx), a more expensive cheapo device, so I do not use the 4.0L anymore.
As for rooting tools, I used the Kingroot APK successfully in the stock environment. I never tried flashing something SuperSU myself, but it could work. Is flashing a SU app possible from the fastboot interface?
And to Steve's question - it is technically possible to flash a ROM for a different device onto your own device, but is considered a bad idea due to the possibility of introducing incompatibilities and missing proprietary requirements. I feel like this would hold especially true to stock ROMs because the manufacturer probably has no interest in supporting anything more than the device that they are manufacturing for. Doing so removes many possible "compatibility" issues from even having to be considered, but I digress. In short, try to find a ROM made for your device and your device only.
Did you find the zip file for the recovery
Marya Wynter said:
umm. . . when the no command option comes up just press the power button and the rest of options will appear. doesnt exactly solve your problem however unless you have the ZIP file to install, which is what I'm looking for.
Click to expand...
Click to collapse
i root my blu advance 4.0l a010u with the kingoroot PC apk, but i got some issues with the lock screen and some apps, so, i need some advice..
i was looking for a zip to use it via recovery but i can't find any..
Recover IMEI
srspinho said:
Hi guys !
Thank you very much for the Advance 4.0L Roms.
I have successfuly recovered my phone, but the IMEI got lost.
So, I need to root it in order to recover the IMEI, but I just can´t get success on any method :
Kingroot
Framaroot
Towelroot
is there another way to root it ?
Thank you very much.
Click to expand...
Click to collapse
You dont need root to recover imei all you have to do is type *#*#84666364#*#* in your dialer and you will be entered in EngineerMode then go into connectivity ,CDS information and radio information phone 1 or 2 then you will see AT+ type something eg.A then backspace and select the first thing you see. Put a space after AT+ and then put you imei code here "IMEI" between these "" You can find your imei by removing your battery it willl be there. After sending command reboot and imei is back.
links are down....check this instead
Hey guys, links here seems to be down .
Maybe this link would be useful for you all... stock firmware can be downloaded and useful help on videos is available too... Enjoy

Need Rom for Alcatel 4037a

Good day my friends. This is my first post but i read these forums very often. I own a Digicel Dl750 (alcatel 4037a) which i would really appreciate some help with. I tried to flash my phone some time ago using a tutorial i found online since i couldn't find anything useful here (my go to source for these things). However, after trying to flash the rom and failing, i am stuck with a phone that won't respond to any input. COnnecting it with a usb simply gives me a white light on the phone, and device manager reads a "MTK usb port" device. it won't boot or anything else. Been trying to install some kind of recovery but i've had no luck so far. Is anyone here able to provide me with a backup of a working phone so i can fix mine please.
Edit Note1: After a bit more testing, I have pretty much confirmed that it is a problem with the preloader as the phone seems to completely skip the preloader when you connect it to the pc, and after a few seconds goes to the bootrom(?) instead. I am making this call based on the hardware ids show in device manager.
#BUMP I also need a stock firmware for the DL750 4037A
kingofkrunck said:
#BUMP I also need a stock firmware for the DL750 4037A
Click to expand...
Click to collapse
Well i was able to get an OSP dump which solved my problem. Not sure it would be of use to you though
Where can I get this dump at Denis?

SW3 may need partition repair

My sw3 has been stuck on the 4 dots/symbols for some time now. I have tried XC (even though it ran with success, it did not fix the watch), by way of fastboot, adb and twrp I have run, installed, pushed various files such as recovery, roms, .simg, etc to no avail. I had a thread going on the 4 dots that describes each of these functions with the 4 dot thread title if you care to see what has been done and the results.
The last entry of that thread suggested there may be an issue with my partitions. So, I wondering if anyone knows either how to check/compare and better yet, repair if needed?
Edit: I found this post http://forum.xda-developers.com/smar...rsion-t2988087 and I was able to get the watch working again. I still cannot use XC to repair or update, but at least it is working with LP.
golfnut22 said:
My sw3 has been stuck on the 4 dots/symbols for some time now. I have tried XC (even though it ran with success, it did not fix the watch), by way of fastboot, adb and twrp I have run, installed, pushed various files such as recovery, roms, .simg, etc to no avail. I had a thread going on the 4 dots that describes each of these functions with the 4 dot thread title if you care to see what has been done and the results.
The last entry of that thread suggested there may be an issue with my partitions. So, I wondering if anyone knows either how to check/compare and better yet, repair if needed?
Edit: Edit: I found this post http://forum.xda-developers.com/smar...rsion-t2988087 and I was able to get the watch working again. I still cannot use XC to repair or update, but at least it is working with LP.
Click to expand...
Click to collapse
Same issue here
Hi,
I have the exact same issue with my sw3, stuck on the four symbols. Like you I managed to flash TWRP and mount the SWR50-LWX48P-repacked ROM. This doesn't do the trick unfortunately because firstly I cannot update the ROM and worst of all the watch will not connect to my smartphone. Like you I suspect there to be an issue with the partitions but I haven't got a clue really. Hope for some help on this.
baronimus said:
Hi,
I have the exact same issue with my sw3, stuck on the four symbols. Like you I managed to flash TWRP and mount the SWR50-LWX48P-repacked ROM. This doesn't do the trick unfortunately because firstly I cannot update the ROM and worst of all the watch will not connect to my smartphone. Like you I suspect there to be an issue with the partitions but I haven't got a clue really. Hope for some help on this.
Click to expand...
Click to collapse
Yes, I still have not been able to update to MM. Mine does connect to my smartphone with no issues. Although, the last time I did have an issue where it kept cycling and trying to connect to the internet via the phone. So, I went thru the steps again to basically get it back to the ROM you noted above and it is working. One thing I have noticed once I get it going with the steps I used, I cannot boot to twrp via fastboot. I have to go to XC and let it try and repair, which it says it does, but doesn't. I get the 4 dots again, and from there when I fastboot, I can fastboot twrp.img and adb push stuff to install. However, I have noticed that I need to use the flash commands and flash the .simg file noted in my thread in order for the above ROM to actually work. I also noticed when that ROM is installing, it does mention working on partitions...so, it must be doing something to some of them.
I would love to be able to get MM working on this, but I think I have run out of ROMs to try. I'm probably not sequencing something right, but have not clue as to what is wrong. I am an newbie at this.
If you get MM to finally update on your watch, it would be much appreciated if you would share your detailed process in achieving that success.

Wifi and whole bunch of sensors aren't working. Corrupt system?

So I've recently got my hands on a dirt cheap OP3 with problems (seller did warn me of those but I thought "how hard can it be to fix them?")
To start with: OP3 A3003, OOS3.1.2, TWRP and SuperSU. IMEI and Baseband are in tact, I can make calls and use LTE, so it's possible to live with it, but those couple problems ruins whole pleasant oneplus experience.
And problems are:
1. Wifi doesnt work. At all. It can't detect any networks and for MAC adress there is weird 02:00:00:00:00:00
2. None of the sensors shows any signs of life, checked with Sensor Box app and *#808#
There is a perfectly good explaination for both of those: root browsers shows /persist completely empty. So if there is any way to fix this lovely piece of modern tech - only this place can provide it. So help, please ;]
P.S. Soft/hard reset and reflashing aren't helping obviously, nor does deleting /persist - after reboot it appears in same state.
My OP3 has Wifi, GPS, Dialer works but none of the sensors work. I tried everything from flashing roms to using unbrick methods but nothing works too.
Spleanie said:
So I've recently got my hands on a dirt cheap OP3 with problems (seller did warn me of those but I thought "how hard can it be to fix them?")
To start with: OP3 A3003, OOS3.1.2, TWRP and SuperSU. IMEI and Baseband are in tact, I can make calls and use LTE, so it's possible to live with it, but those couple problems ruins whole pleasant oneplus experience.
And problems are:
1. Wifi doesnt work. At all. It can't detect any networks and for MAC adress there is weird 02:00:00:00:00:00
2. None of the sensors shows any signs of life, checked with Sensor Box app and *#808#
There is a perfectly good explaination for both of those: root browsers shows /persist completely empty. So if there is any way to fix this lovely piece of modern tech - only this place can provide it. So help, please ;]
P.S. Soft/hard reset and reflashing aren't helping obviously, nor does deleting /persist - after reboot it appears in same state.
Click to expand...
Click to collapse
Maybe contact OnePlus support, they may be able to fix it via a remote connection...
Did you try the second method discribed here ?
It will rewrite everything on every partitions if the device. https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
danecr7 said:
Did you try the second method discribed here ?
It will rewrite everything on every partitions if the device.
Click to expand...
Click to collapse
Ok, so I've pulled persist.img from the toolkit, flashed it right after "erase persist" and that revived all of my sensors! Yay! I guess that toolkit might help with wifi as well, tho no idea which part of it. I'd use whole procedure, but there is one problem here - it needs bricked phone to start with.
on my lg g2 days, when screwed pretty bad with something, there was a script for nuke laf partition to boot qsbulk mode (and also erase whole emmc for real clean start), dunno how/if there is such a scrip for op3
Sent from the grey stuff inside my skull
Spleanie said:
Ok, so I've pulled persist.img from the toolkit, flashed it right after "erase persist" and that revived all of my sensors! Yay! I guess that toolkit might help with wifi as well, tho no idea which part of it. I'd use whole procedure, but there is one problem here - it needs bricked phone to start with.
Click to expand...
Click to collapse
If you wanna brick your phone its easy. Install 4.0.2 and then root and make sure you have TWRP of course. Download the OTA to 4.0.3 the small one not the full zip. Flash that in recovery. You'll be bricked
Renosh said:
If you wanna brick your phone its easy. Install 4.0.2 and then root and make sure you have TWRP of course. Download the OTA to 4.0.3 the small one not the full zip. Flash that in recovery. You'll be bricked
Click to expand...
Click to collapse
Thanks for info, nice to know ;] Although I'd like to avoid such drastic measures. Better to pin a roach with a needle instead of nuking it, right?
had the same issue, OnePlus replaced motherboard for free.

Categories

Resources