[Q] I think my Oppo N1 is bricked, can you please help me?? - Oppo N1

Hi all,
I've been running PA 4.6 (KK 4.4.4) smoothly for a few weeks now, then suddenly a few days ago it started to reboot to the OPPO logo and is now stuck in a bootloop showing only OPPO logo. Only way to stop it is to power down. Sometimes it won't even power up, then after I leave it for a few hours, it'll power up, but again OPPO logo bootloop. I'm able to boot into fastboot (that's finicky, too - it happens if I'm lucky). When I do "adb devices", nothing shows up, but when I do "fastboot devices", I can see my device.
I tried to flash a recovery through fastboot, and it says flashed successfully, but when I try to reboot, it still does the OPPO logo bootloop. Can you please help me figure this out?
At one point, while I was pressing this button and that in the middle of doing fastboot stuff, somehow it booted up to my homescreen successfully, but after like 30 seconds, it rebooted, and it's been on OPPO logo bootloop ever since. Please help.:crying:

raddatt said:
Hi all,
I've been running PA 4.6 (KK 4.4.4) smoothly for a few weeks now, then suddenly a few days ago it started to reboot to the OPPO logo and is now stuck in a bootloop showing only OPPO logo. Only way to stop it is to power down. Sometimes it won't even power up, then after I leave it for a few hours, it'll power up, but again OPPO logo bootloop. I'm able to boot into fastboot (that's finicky, too - it happens if I'm lucky). When I do "adb devices", nothing shows up, but when I do "fastboot devices", I can see my device.
I tried to flash a recovery through fastboot, and it says flashed successfully, but when I try to reboot, it still does the OPPO logo bootloop. Can you please help me figure this out?
At one point, while I was pressing this button and that in the middle of doing fastboot stuff, somehow it booted up to my homescreen successfully, but after like 30 seconds, it rebooted, and it's been on OPPO logo bootloop ever since. Please help.:crying:
Click to expand...
Click to collapse
Are you unable to boot into recovery too? Try booting into recovery and factory resetting the phone.

Thank you for replying. Yes, unable to boot into recovery I can only boot into fastboot. From there, when I do the reboot to recovery command, it says successful in cmd, but the phone goes back into the OPPO logo bootloop.

Bump.. anyone, please?

Sounds like you're gonna have to download the N1 ADB drivers and fix your phone that way. There should be a tutorial for that on XDA here somewhere

IAmOmicron said:
Sounds like you're gonna have to download the N1 ADB drivers and fix your phone that way. There should be a tutorial for that on XDA here somewhere
Click to expand...
Click to collapse
I know this is super late, but thank you for your reply. I did that and was able to flash the stock recovery via fastboot (cmd said Writing, then successful at 0.182 seconds), but when I reboot (doesn't reboot via buttons, had to do "fastboot reboot") the same problem returns - boot loop at Oppo logo. Any ideas please? Thanks again.

Related

[Q] Bricked Nexus 7 (stuck on google logo, can enter fast boot)

Have a nexus 7 in need of help. Hope can get some assistance here.
- Stuck on google screen when boot
- Can enter boot loader mode using power + vol down, and can use fastboot
- successful flash of recovery, rom, boot, boot loader partitions using cmd (fastboot) or wug's kit, but will not restart on its own.
- when tried to restart, it hangs again on google logo.
- Tried recovery mode with power + vol up after reboot, doesn't work. Cant get into recovery. NO "android robot with red !", stuck on google logo
- no access of ADB (since stuck before I can enter Android OS)
- wiped cache and wiped user data no change.
- cannot get into recovery so cannot do a hard reset
- pulled battery in hope of hard reset, same result
Any ideas? thanks in advance
BoredAtWork said:
Have a nexus 7 in need of help. Hope can get some assistance here.
- Stuck on google screen when boot
- Can enter boot loader mode using power + vol down, and can use fastboot
- successful flash of recovery, rom, boot, boot loader partitions using cmd (fastboot) or wug's kit, but will not restart on its own.
- when tried to restart, it hangs again on google logo.
- Tried recovery mode with power + vol up after reboot, doesn't work. Cant get into recovery. NO "android robot with red !", stuck on google logo
- no access of ADB (since stuck before I can enter Android OS)
- wiped cache and wiped user data no change.
- cannot get into recovery so cannot do a hard reset
- pulled battery in hope of hard reset, same result
Any ideas? thanks in advance
Click to expand...
Click to collapse
Did you tried flashing stock google image from wug's kit by clicking "Flash Stock+Unroot" option
Further info:
Tried different factory roms, same flash method, same result
4.2.0
4.4.x
4.5.0
all flash using fast boot command shows success on screen.
fastboot recognize device when using "fastboot devices"
supersaayuj said:
Did you tried flashing stock google image from wug's kit by clicking "Flash Stock+Unroot" option
Click to expand...
Click to collapse
thanks for quick reply.
Tried Wug's kit (latest version since it auto update), and tried with command line using fastboot drivers (win7 environment)
Same result
Wug's kit logging shows no problems.
BoredAtWork said:
Further info:
Tried different factory roms, same flash method, same result
4.2.0
4.4.x
4.5.0
all flash using fast boot command shows success on screen.
fastboot recognize device when using "fastboot devices"
Click to expand...
Click to collapse
Then it should boot man! Try flashing factory image using NRT(wug's toolkit) by "Flash Stock+Unroot" and ticking SoftBricked/Bootloop below that.. hope this works
supersaayuj said:
Then it should boot man! Try flashing factory image using NRT(wug's toolkit) by "Flash Stock+Unroot" and ticking SoftBricked/Bootloop below that.. hope this works
Click to expand...
Click to collapse
I have tried exactly that. "flash stock+ unroot" with the nexus in boot loader mode. After complete, the nexus will remain in boot loader mode until I restart it manually (press power button on nexus). Wug's toolkit would not reboot it after successful flashing. Is that normal?
After manual reboot, it still stuck on google logo.
BoredAtWork said:
I have tried exactly that. "flash stock+ unroot" with the nexus in boot loader mode. After complete, the nexus will remain in boot loader mode until I restart it manually (press power button on nexus). Wug's toolkit would not reboot it after successful flashing. Is that normal?
After manual reboot, it still stuck on google logo.
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=orZ_iBpkn_g
Get a look at this video... I can't further help... because this is a weird problem I haven't faced with my nexus 7. Mostly flashing stock would solve this kinda problem! :angel:
Reply back if you unbricked it!
Same problem here
I got the same problem here. First ElementalX kernel frozen touchscreen in 5.0, so I used ADB to flash stock image back. After that it get stucked at Google logo. Does anyone have solution?
Is there anyone can help?
micheldjerzinski said:
I got the same problem here. First ElementalX kernel frozen touchscreen in 5.0, so I used ADB to flash stock image back. After that it get stucked at Google logo. Does anyone have solution?
Click to expand...
Click to collapse
All of the above posts match my experience with the n7 2013...it has been a downwards spiral of malfunctions at the touchscreen department...ending at this...some time soon, i'm gonna pick up an axe or some other heavy-hitter tool and smash the f*****g thing to atoms!
yes, i have given up....hopefully you don't get to the same conclusion as i....good luck...
BoredAtWork said:
Have a nexus 7 in need of help. Hope can get some assistance here.
- Stuck on google screen when boot
- Can enter boot loader mode using power + vol down, and can use fastboot
- successful flash of recovery, rom, boot, boot loader partitions using cmd (fastboot) or wug's kit, but will not restart on its own.
- when tried to restart, it hangs again on google logo.
- Tried recovery mode with power + vol up after reboot, doesn't work. Cant get into recovery. NO "android robot with red !", stuck on google logo
- no access of ADB (since stuck before I can enter Android OS)
- wiped cache and wiped user data no change.
- cannot get into recovery so cannot do a hard reset
- pulled battery in hope of hard reset, same result
Any ideas? thanks in advance
Click to expand...
Click to collapse
I was experiencing this problem last night. However, I used WugFresh's NRT but when it asks to flash stock and unroot, make sure you check the box that says your nexus 7 is softbricked. Also, you may want to note what version of android it was last running before it was bricked. It worked for me and I was able to update to 5.0.1.
*Edit: The only thing you need to do is make sure fastboot is enabled, and you should be good to go.
P.S. DO NOT download the stock images from google to your computer, let the NRT automatically download it for you. It saves you time, storage and stress. Once done, also install the recovery from the NRT, that should be able to do the trick. Not sure why your device won't restart, you may have to flash again.
wugs
I had to use force flash in wugs, go to options and set it there and try a previous version. Best of luck.
It's fixed!
koymoy said:
All of the above posts match my experience with the n7 2013...it has been a downwards spiral of malfunctions at the touchscreen department...ending at this...some time soon, i'm gonna pick up an axe or some other heavy-hitter tool and smash the f*****g thing to atoms!
yes, i have given up....hopefully you don't get to the same conclusion as i....good luck...
Click to expand...
Click to collapse
Haha, I found the solution elsewhere in XDA. So if you haven't beaten your Nexus 7 so bad yet, TRY this: press and hold the power button for about 1 minutes. The slate turned off and on several times, and I found nothing. BUT after several minutes (while I was watching Youtube to see how to remove battery; that would be the last method before throwing 5 stories down to ground), the Nexus BOOTED BACK:good::good::good:. Good luck!:laugh:
And I'm using Glitch kernel and turn off flar2's double-tab-to-wake. It's a neat feature, but can get us into big troubles.
That still doesn't work for me. Pretty sure my eMMC is dead, so I'll need to replace the motherboard.
Anyone know if a 16GB motherboard works in a 32GB Nexus 7 2013? 16GB motherboards seem a fair bit cheaper, and less rare.

Can't boot into recovery, always fastboot (But OS working!)

Hey guys,
I don't really know, what i did with my device At the moment i have ColorOS 2.1.3 on it, i flashed before with TWRP. The ROM works fine, i also have LVM with no problems.
But now i can't boot anymore in my recovery Always when i want to boot in recovery, it vibrates and shows for one second the "OPPO / powered by ANDROID" screen. Then it turns off, vibrates again and fastboot screen appears. So there is no difference for me if i start my phone with POWER+Vol+ OR POWER+Vol-. It always ends up in fastboot mode, no recovery anymore.
In fastboot i can flash recovery but it doesn't matter which recovery i flash, i always can't reboot into it
Do you have any ideas? As said, OS is working, there i don't have any problems...
Thanks in advance for your help,
Joojoo
I will try this at home: http://forum.xda-developers.com/showthread.php?t=3195818
Don't know why I didn't found this before...
EDIT: It seems to be working now
My phone screen always blink after use the fastboot
Is this resolved now?

Help me get out of this bootloop!

Hey guys,
Don't usually have to post but after searching all day I can't find a way out of this loop. My 10 is currently flashing the white HTC splash and rebooting endlessly. That's no big deal, but I ALSO have no recovery or download mode access.
The ONLY thing I can do to interrupt the loop is access fastboot by holding Vol UP + Vol Down on restart. Unfortunately trying to "reboot to recovery" only flashes the dark HTC Logo then immediately restarts to the original bootloop. Attempting to "reboot to download mode" simply resumes the boot loop.
The device is recognized in fastboot on my PC but unfortunately I cannot flash or erase anything because I'm in S-ON, so practically none of the fastboot commands work. I have been using TWRP recovery and Viper10 Rom.
Any help getting out of this loop is greatly appreciated. I was going to give up and pay the deductible and replace it, until I found out that the phone is backordered until October and my alternative is an LG, which I can't stand.
S O S!
Currently experiencing the exact same thing myself:
http://forum.xda-developers.com/htc-10/help/htc-10-bootlooping-t3441710
Valandil11 said:
Currently experiencing the exact same thing myself:
http://forum.xda-developers.com/htc-10/help/htc-10-bootlooping-t3441710
Click to expand...
Click to collapse
The only difference being that I let mine loop for a solid hour and it didn't successfully boot at all. In the past I was having issues sometimes when I restarted, but I would just create a backup and restore from it and it would work, which made me think the boot file was just either corrupt or non existent. I've never been locked out of recovery AND download mode, however.

jem recovery/fastboot broken

Hi. I've got a jem, which was previously running CM11, which I finally got around to trying to update. In the process, I ended up with AICP installed. It won't fully boot; it hangs at the logo, but is responsive using adb (shell, logcat, etc).
Since their release notes mention a new recovery requirement, I tried to upgrade my recovery and it failed. Now, I can boot the AICP rom (which hangs at the logo), but all efforts to get into either the recovery or fastboot fail, and aicp still isn't booting completely (i let it sit overnight, and the logo was still spinning in the morning.
I'm hoping that since adb works, the tablet isn't a brick.
Can anyone suggest a path out?
thanks
bricklayer16 said:
Hi. I've got a jem, which was previously running CM11, which I finally got around to trying to update. In the process, I ended up with AICP installed. It won't fully boot; it hangs at the logo, but is responsive using adb (shell, logcat, etc).
Since their release notes mention a new recovery requirement, I tried to upgrade my recovery and it failed. Now, I can boot the AICP rom (which hangs at the logo), but all efforts to get into either the recovery or fastboot fail, and aicp still isn't booting completely (i let it sit overnight, and the logo was still spinning in the morning.
I'm hoping that since adb works, the tablet isn't a brick.
Can anyone suggest a path out?
thanks
Click to expand...
Click to collapse
To self-reply, for some reason, adb reboot bootloader wouldn't work, but adb reboot recovery got me into fastboot. I've managed to get things repaired.

can't boot my phone and also can't boot to the recovery!!

Hi, yesterday i was using my phone and suddenly it freezed then restarted and the lenovo logo stuck forever, i thought that the stuck firnware got crashed and needs to reinstall again, i had root in it and installed twrp on it, i tried to boot to the twrp through the fastboot but when i type " fastboot boot recovery.img" it works and says finish but the phone still stuck at the bootloader screen and freezes and i have to restart the phone again to access the bootloader again, then i tried to reinstall the stuck firmeware that i used before "P2a42_S048_161111_ROW_fastboot" but still after i reinstalled it and start the phone again, it still stuck at the lenovo logo forever" then i tried to boot to the stuck recovery mode using fastboot, and still freezes after i run the command on fastboot, i tried the blankflash it all works fine without no fail but still the problem exist, still cant boot my phone and cant boot to the recovery, this is the first time that something wierd like this happens to my phone, i tried all the solutions and none of them works! i even tried to relock the bootloader using fastboot oem lock but it fails! please help me guys.
Join the club, you're phone is now dead, no one recovered from this yet.

Categories

Resources