[Q] Did something very bad! OPPO FIND 7 - Oppo Find 7 and 7a

I was going about flashing my Oppo Find 7 not 7A, succesfully rooted, flashed TWRP, booted into Cyanogenmod 11 successfully. I then went on and attempted to flash cyanogenmod 11s(one plus one system dump) on my Find 7, rebooted, One plus one was split into two on each side of screen, when attempting to go into recovery it was not there anymore and screen was just black. I tried putting back original recovery no luck and tried reflashing with TWRP but still no luck and phone does not boot into anything when turning on. Any help would be deeply appreciated since I can no longer use my new phone.

When completely off, hold power and up, that should put it in fastboot. Can you confirm whether this works or not?
Sent from my Find7 using XDA Premium 4 mobile app

Hey Chewbyte thanks for the response, I have managed to get CWM recovery on it but since I tried flashing CM 11s which wasnt made for the Find7, upon boot the screen is split and it says one plus and nothing occurs. I even tried reflashing cyano 11 but still nothing happens when i try to reboot. My fastboot is also the cyano little guys face. I am not sure what to try next

coscos17 said:
Hey Chewbyte thanks for the response, I have managed to get CWM recovery on it but since I tried flashing CM 11s which wasnt made for the Find7, upon boot the screen is split and it says one plus and nothing occurs. I even tried reflashing cyano 11 but still nothing happens when i try to reboot. My fastboot is also the cyano little guys face. I am not sure what to try next
Click to expand...
Click to collapse
Even if the graphics are messed up in fastboot, it still could work fine.
Download the AndroidSDKSlimCustom here https://www.dropbox.com/s/41p7peig4wt5kav/AndroidSDKSlimCustom.zip
Navigate into platform-tools, hold shift anywhere in that directory and right click while holding shift. Click 'Open command window here'
Turn off your phone completely, take the battery out to be sure, and hold power and volume up until you see something appear on the screen.
Connect the phone via usb, go back to the command window that opened and type
Code:
fastboot devices
If you're lucky you'll get something like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This means you can then flash TWRP, get into that recovery, wipe everything and ADB sideload a fresh CM nightly (actually made for the find 7!) which you can find here:
http://download.cyanogenmod.com/?device=find7
Let me know how you get on.

I had done that before but still same result, even in recovery the screen looks like it was shifted.

GOT EM! SOLVED!
For anyone else who has this problem use this!
I cant post links cause i am a noob
but in oppo forums look for these
threads/find-7-x9076-bricked-need-help.18112/
/threads/brick-my-oppo-find-7-x9076-doesnt-load-any-recovery.17906/
com/threads/stock-recovery-for-find-7-7a.17397/
and when in stock recovery i flashed X9006&X9076ColorOS_V1.2.1i_full.zip
and BOOM it worked!
Once again thank you Chewbyte for taking the time to answer and try to help me I appreciate it!!

No problem friend, I'm glad you managed to fix it.
Sent from my Find7 using XDA Premium 4 mobile app

just one more thing i need some help with. When i struggled with the recoverys I think i wiped everything. So now when I open the camera it says storage unavaible? any ideas?

coscos17 said:
just one more thing i need some help with. When i struggled with the recoverys I think i wiped everything. So now when I open the camera it says storage unavaible? any ideas?
Click to expand...
Click to collapse
I googled your issue around a bit. Try factory reset/clear cache.

Related

Need help. this one has me stumped!!

Ok, so my friend has a galaxy nexus and its was working fine for him and then one day its was fuxzored. He told me the last thing he did was installed a cracked version of gta. the game worked so i dont think its a virus but thats the only thing fishy i know of that he did with his phone.
so, the state the phone is in is it goes into a boot loop when trying to start the thing, the google logo comes up and then there is a glitch in the screen for a second then back to google logo and then a restart.
i am able to get into the bootloader but when i try to go into recovery the android is lying on his back with a red exclamation point over him(most of the time i cant even get to that point. sometimes the screen goes black or glitches and it reboots.), so i press all three buttons and i have the option to wipe data or flash from cache, but there is nothing in the cache.
so i thought i might be able to use fastboot with the gnex toolkit to flash his recover to cwm. well the bootloader is unlocked but recovery is still messed up. nothing seems to work.
im out of ideas. please help!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://forum.xda-developers.com/showthread.php?t=1366806
brummie028 said:
http://forum.xda-developers.com/showthread.php?t=1366806
Click to expand...
Click to collapse
This won't help if he can't get into recovery mode.
rljetsetradio said:
...
i am able to get into the bootloader but when i try to go into recovery the android is lying on his back with a red exclamation point over him(most of the time i cant even get to that point. sometimes the screen goes black or glitches and it reboots.), so i press all three buttons and i have the option to wipe data or flash from cache, but there is nothing in the cache.
...
Click to expand...
Click to collapse
The droid with the exclamation mark is the stock recovery. If you push volume up + power you get the recovery menu. Maybe a factory reset there will bring a solution? (Only thing I can think off right now).
How about Odin?
Can you get into download mode?
dario3040 said:
How about Odin?
Can you get into download mode?
Click to expand...
Click to collapse
Yeah Odin would fix it.
Try this - http://goo.gl/sXXGN
'fastboot erase recovery'
'fastboot flash recovery cwm.img'
Try that
What bk201doesntexist said. As long as you can get into the bootloader, you are good to go.

[Q] Help please!

Hi guys... just flashed another ROM, as I have many times, but this time I'm stuck on the HTC screen. The phone doesn't boot past this and forcing a restart by holding the power key and volume down won't get the phone to boot into recovery. Does anyone know any way of forcing the device to boot into recovery. I've obviously cocked up somewhere. Any help would be much appreciated. Thank you.
grahamkdt said:
Hi guys... just flashed another ROM, as I have many times, but this time I'm stuck on the HTC screen. The phone doesn't boot past this and forcing a restart by holding the power key and volume down won't get the phone to boot into recovery. Does anyone know any way of forcing the device to boot into recovery. I've obviously cocked up somewhere. Any help would be much appreciated. Thank you.
Click to expand...
Click to collapse
have you flashed the boot.img!?!?!?!?!?!?!?!?!?!?!?!?!?!?!?!?!?!?!?!?!?!?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
god!! today i've repeated this step 100000 times!!! why fon't you read instead of asking every stupid single question explained in the rom thread!?
matt95 said:
have you flashed the boot.img!?!?!?!?!?!?!?!?!?!?!?!?!?!?!?!?!?!?!?!?!?!?
god!! today i've repeated this step 100000 times!!! why fon't you read instead of asking every stupid single question explained in the rom thread!?
Click to expand...
Click to collapse
Never mind... I've sorted it and YES I've flashed the boot image - I'm not a complete knob head... just partially!
grahamkdt said:
Never mind... I've sorted it and YES I've flashed the boot image - I'm not a complete knob head... just partially!
Click to expand...
Click to collapse
oh finally somebody that did it, in that case sorry for ma inpatience so, which rom are you trying to flash?
Did you erase the cache via fastboot to fix it? I had the same issue.
Sent from my HTC One X using xda premium
stebsgb1 said:
Did you erase the cache via fastboot to fix it? I had the same issue.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
No... I kept the power button and volume down pressed even after the device restarted, and it then restarted again and booted into recovery. Never had an issue before trying to access recovery so thought it was a bit strange. It was probably just a fluke case. I understand why people jump to the "Did you flash the boot image / clear the cache" reply, but I'm not a novice here. I've been flashing ROM's since 2007!
Thanks for the replies any way
grahamkdt said:
No... I kept the power button and volume down pressed even after the device restarted, and it then restarted again and booted into recovery. Never had an issue before trying to access recovery so thought it was a bit strange. It was probably just a fluke case. I understand why people jump to the "Did you flash the boot image / clear the cache" reply, but I'm not a novice here. I've been flashing ROM's since 2007!
Thanks for the replies any way
Click to expand...
Click to collapse
I always have to keep the power button and volume pressed down even after the device restarted, else it just goes over to start the rom automatically. Probably that was ur problem too.

Small problem when going from Philz Touch Recovery back to TWRP

Hello,
I recently tried out the latest version of "PhilZ-Touch Recovery 6.0" located in this thread: http://forum.xda-developers.com/showthread.php?t=2446393. I did this from my previously installed recovery (TWRP V2.6.3.0) and everything went and had no problems, but I decided to go back to TWRP anyway and installed the latest TWRP version for my phone (V2.6.3.1) and again everything went fine and I was back to using TWRP again. The only problem I noticed is that when I boot into TWRP recovery now, I see this blue logo on my screen before I am presented with the TWRP curtain screen that I was used to seeing before.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I did a little searching and discovered this logo is the CyanogenMod Logo and since I do not have CyanogenMod installed on my phone, I can only assume it was placed on my phone as part of the philz recovery install. My question is then, how do I get rid of this logo since I do not have CM installed and do not want it to show up when I boot into TWRP?
TIA,
Mtcell
P.S. I would have posted this in the thread above, but I am a newly registered member and was not able to post in that tread until I have accumulated 10 or most post. Instead of spamming the forum to get my post count up (and taking a change on getting my account suspended in the process), I felt it would be better to post this question here.
I have been running the PhilZ recovery since @CNexus made it available, it doesn't place that image on your phone.
What ROM are you running? TW or AOSP??
jdelano said:
I have been running the PhilZ recovery since @CNexus made it available, it doesn't place that image on your phone.
What ROM are you running? TW or AOSP??
Click to expand...
Click to collapse
I am totally stock, rooted, and have been since I got the phone back in June. This is what is confusing me. Please note, the icon only shows up when I boot into recovery. If I do a normal boot / reboot then I cannot see it.
Thanks again for any and all replies,
Mtcell
mtcellph said:
I am totally stock, rooted, and have been since I got the phone back in June. This is what is confusing me. Please note, the icon only shows up when I boot into recovery. If I do a normal boot / reboot then I cannot see it.
Thanks again for any and all replies,
Mtcell
Click to expand...
Click to collapse
Hmmm, booting into recovery from android or with the phone off?
I just updated to 6.0.5 and I went into recovery to flash that update, though it was via the power menu.
Let me try with the power off ... ah yes, there is a little blue guy there when I go to recovery that way. (its been so long since I've done that)
TWRP probably doesn't over right that part of the phone.
Maybe try normal CMW flash and then back to TWRP or do a nandroid restore from a previous backup.
Twrp added that as the logo in the last update prob was a mistake
Sent from my SPH-L710 using xda app-developers app
jdelano said:
Hmmm, booting into recovery from android or with the phone off?
I just updated to 6.0.5 and I went into recovery to flash that update, though it was via the power menu.
Let me try with the power off ... ah yes, there is a little blue guy there when I go to recovery that way. (its been so long since I've done that)
TWRP probably doesn't over right that part of the phone.
Maybe try normal CMW flash and then back to TWRP or do a nandroid restore from a previous backup.
Click to expand...
Click to collapse
Thanks for the confirmation. At least I know I did not mess something up. I mainly do all of my rebooting into recovery from within android using GooManager, but I tried it from TWRP as well and the same result happened and finally, I tried it from a cold boot using the power, home, volume up buttons and the same result each time.
As far as the logo goes, I am not really overtly concerned about it as long as it's not going to mess anything up, I will probably leave it unless I find some reason I should remove it.
Thanks again for your replies,
Mtcell
yeah nothing messed up at all, you just have a new blue pal
Your welcome; a sanity test now and again is a good thing (some - like me - need them more often)
Notorious said:
Twrp added that as the logo in the last update prob was a mistake
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Ahh, that makes sense now. As I said, I will keep it just as long as it's not going to mess with anything (which it hasn't) so no harm no foul.
Thx again,
MTCell

Can't enter bootloader

Two weeks back I tried to manually update my phone to 2.40.168, since i am missing the "system update" option in the settings. I installed a new recovery.img boot.img and droidboot.img and it update the recovery to WW-2.40.168 :good:. I still couldn't update the firmware though and decided to quit trying.
Now I want to put CM13 on it and wanted to change the recovery. BUT when i press Power Up + Volume Up, release the power up this shows up.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I can restart it by long pressing the power button but that is about it.
Also i searched for fixes but didn't find anything hence made a post.
Ok so basically what he is saying is that his phone does NOT even have recovery mode. Where we get the dead android guy he gets this and is thus unable to flash his phone with new recovery or system.
That happened to a friend of mine a long time ago but he threw away his phone ( sold it for cheap ) without trying much.
Are there any ACTUAL solutions ?
Again Power + vol up keys DO NOT bring up recovery mode/fastboot or however you want to call it.
Anyone ?
yeah - think this is just a soft brick afaik
you should be able to see the device as moorefied in windows and go from there
debully said:
yeah - think this is just a soft brick afaik
you should be able to see the device as moorefied in windows and go from there
Click to expand...
Click to collapse
"moorefied" ?? Can you explain ?
xRanker said:
"moorefied" ?? Can you explain ?
Click to expand...
Click to collapse
just read some soft/hard brick threads - download the shizzle, install it properly on your machine and follow the instructions.
you have a good chance.
Personally I have no chance as the device wont even turn on. Asus support are absolutely useless and I WILL NEVER, EVER BUY ANOTHER PRODUCT FROM THEM AGAIN - and I'd advise you to do the same. These forums are littered with soft/hard bricks.
debully said:
just read some soft/hard brick threads - download the shizzle, install it properly on your machine and follow the instructions.
you have a good chance.
Personally I have no chance as the device wont even turn on. Asus support are absolutely useless and I WILL NEVER, EVER BUY ANOTHER PRODUCT FROM THEM AGAIN - and I'd advise you to do the same. These forums are littered with soft/hard bricks.
Click to expand...
Click to collapse
That is mostly because people touch where they are not supposed to ^^
But um thanks for reply.
With respect, you don't know what you're talking about.
I've been flashing since the HTC canary. I've never once had a bad flash. Nor here. The phone is prone to hard bricking way in excess of the norm and you only need to look at these forums to see that.
But thanks, your response was greatly valued and added to the weight of knowledge.
debully said:
With respect, you don't know what you're talking about.
I've been flashing since the HTC canary. I've never once had a bad flash. Nor here. The phone is prone to hard bricking way in excess of the norm and you only need to look at these forums to see that.
But thanks, your response was greatly valued and added to the weight of knowledge.
Click to expand...
Click to collapse
Not so sure of that, I really think its more user error than anything else, especially when it comes to fastboot. Copy and paste isn't your friend and it seems most people overwrite their boot or fastboot partitions with system files because they use the same command but change the img file name.
Have never had an unrecoverable brick, and those soft bricks I've had were my fault by not reading properly or skipping through steps quickly.
XepouH said:
Two weeks back I tried to manually update my phone to 2.40.168, since i am missing the "system update" option in the settings. I installed a new recovery.img boot.img and droidboot.img and it update the recovery to WW-2.40.168 :good:. I still couldn't update the firmware though and decided to quit trying.
Now I want to put CM13 on it and wanted to change the recovery. BUT when i press Power Up + Volume Up, release the power up this shows up.
I can restart it by long pressing the power button but that is about it.
Also i searched for fixes but didn't find anything hence made a post.
Click to expand...
Click to collapse
Find your answer here

Can't flash twrp on redmi note 5 pro (whyred)

So i've been wanting to root this phone for a while now, and i just cant seem to flash twrp, yes its the correct file, yes its the correct command, yes im using SDK developer tools, but i just cant seem to flash it. heres the error btw
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
says its flashing but its not. ive left it on for like an hour or so. please help? anyone?
SzymcioYa said:
So i've been wanting to root this phone for a while now, and i just cant seem to flash twrp, yes its the correct file, yes its the correct command, yes im using SDK developer tools, but i just cant seem to flash it. heres the error btwView attachment 5920083
says its flashing but its not. ive left it on for like an hour or so. please help? anyone?
Click to expand...
Click to collapse
Hi, try using the
Code:
fastboot boot twrp.img
command instead
Jan Skokan said:
Hi, try using the
Code:
fastboot boot twrp.img
command instead
Click to expand...
Click to collapse
oh, i actually solved it actually. im running an amd ryzen 5 5600x and thats the issue. i fixed it using a regedit tweak, thanks tho
Jan Skokan said:
Hi, try using the
Code:
fastboot boot twrp.img
command instead
Click to expand...
Click to collapse
Also, i have a question. So i've rooted my xiaomi note 5 with magisk, and i wanted to do the same with my main phone, and now i cant unlock my phone because i dont want my data lost (the apps are the most important and i have all my other data backed up) and i came across mediatekbootloaderunlock and im just wondering is it patched or does it still work? because if it works then im definitely rooting my phone.
SzymcioYa said:
Also, i have a question. So i've rooted my xiaomi note 5 with magisk, and i wanted to do the same with my main phone, and now i cant unlock my phone because i dont want my data lost (the apps are the most important and i have all my other data backed up) and i came across mediatekbootloaderunlock and im just wondering is it patched or does it still work? because if it works then im definitely rooting my phone.
Click to expand...
Click to collapse
Hi, I'm sorry but I can't confirm or deny this because I don't own a Xioami device anymore You just have to try it 🫤
Jan Skokan said:
Hi, I'm sorry but I can't confirm or deny this because I don't own a Xioami device anymore You just have to try it 🫤
Click to expand...
Click to collapse
It actually worked, and now my phone is unlocked. So i flashed orangefox and i cant seem to boot into it. When i try the combination (power and volume+) it just vibrates and goes back to system. i tried fastboot boot but it didnt work.
SzymcioYa said:
It actually worked, and now my phone is unlocked. So i flashed orangefox and i cant seem to boot into it. When i try the combination (power and volume+) it just vibrates and goes back to system. i tried fastboot boot but it didnt work.
Click to expand...
Click to collapse
This has happened to me too. What I did was that after several attempts I managed to get into twrp and reboot the phone into fastboot via twrp. I know it sounds logical, but try to connect the phone to the computer and hold the power off button and click the volume up button several times. Try it several times, it always works. Via Orange Fox, reboot the phone into fastboot and install the stock rom when you are in fastboot mode. I hope it helps you.. good luck
Jan Skokan said:
This has happened to me too. What I did was that after several attempts I managed to get into twrp and reboot the phone into fastboot via twrp. I know it sounds logical, but try to connect the phone to the computer and hold the power off button and click the volume up button several times. Try it several times, it always works. Via Orange Fox, reboot the phone into fastboot and install the stock rom when you are in fastboot mode. I hope it helps you.. good luck
Click to expand...
Click to collapse
ill try and ill keep you updated
Jan Skokan said:
This has happened to me too. What I did was that after several attempts I managed to get into twrp and reboot the phone into fastboot via twrp. I know it sounds logical, but try to connect the phone to the computer and hold the power off button and click the volume up button several times. Try it several times, it always works. Via Orange Fox, reboot the phone into fastboot and install the stock rom when you are in fastboot mode. I hope it helps you.. good luck
Click to expand...
Click to collapse
nope, doesnt work, tried it tho

Categories

Resources