Hey all,
Having a problem with my N7105 (international), in that it suddenly turned off for no reason at all and will not turn on at all. No red led, not sound, no display light or anything. Simply off and wont turn on.
I was web browsing and playing a game (stunt star) 20 mins prior to placing it into my pocket and walked outside to do something. Wanted to check the weather when I noticed that the phone was off.
Tried turning it back on with no success. Even tried download/recovery mode and still wouldn't turn on.
Tried placing it on charge for 15mins (no red led came on or battery display indicator) and turning it back on, no success. Tried a spare battery I had and that didn't work either.
Even tried a usb jig I had lying around and that had no effect.
The phone had been running on 4.1.2 ZHDMB1 (hashcheck hybrid v2.2 with Perseus Kernel 33alpha, so I can't see why it would be the SDS problem) with philz touch 5.06.1 CWM.
I had checked if it had the emmc bug issue with that emmc checker on the play store, and my device came up clean with no detectable problem.
I did notice triangleaway popping up tiny messages stating that it had been granted shell interactive access (something like that) during the game I was playing, but i figure that was related to it requesting root access from SuperSU; which it had done numerous times before with no issues
I did do a nandroid backup a few weeks ago so I do have most of the stuff backed up on the micro SD card, but there are a few files that remained on the phone that I would like to recover.
Even if the phone isn't recoverable, is there anyway for me to access that information with the phone still off?
Not sure why this is happening, but any advice/suggestion on how to resolve this would be much appreciated.
I would suggest you to remove SD card first and then try to boot it up without it.
If it's won't boot up even without SD card, and can't go into download or recovery mode, it's means that you have SDS issue.
Simonna said:
I would suggest you to remove SD card first and then try to boot it up without it.
If it's won't boot up even without SD card, and can't go into download or recovery mode, it's means that you have SDS issue.
Click to expand...
Click to collapse
Thanks for the suggestion.
Tried it without the micro sd card, still won't boot up or go into recovery/download mode.
From what I've read (briefly), most SDS cases involve the phone still emitting a red led when connected to the charger (I could be wrong).
Whereas my N7105 LED doesn't light up red at all; what's the likelihood that its something to do with the powerboard circuitry instead?
Related
So after an unsuccessful ROM flash my phone was stuck at bootloader for quite sometime...i had a micro SD card reader and inserted it into multiple computers running XP, vista and ubuntu...they all registered that i had plugged something in but wouldn't show it as a disk drive...now i've already figured out how to access it but i put a new ROM image on it and tried to reflash but after the flash when my phone booted up it simply switched itself off... when i switched it back on it went back to the bootloader and tried to reflash the ROM. mid flash it just switches itself off... I realize that this is probably due to the charge level of the phone so i plugged it it but it will be off and charging then it will suddenly decide its got enough battery power and boot up to the bootloader screen until it dies again...how do i stop this vicious loop
tlglegacy said:
So after an unsuccessful ROM flash my phone was stuck at bootloader for quite sometime...i had a micro SD card reader and inserted it into multiple computers running XP, vista and ubuntu...they all registered that i had plugged something in but wouldn't show it as a disk drive...now i've already figured out how to access it but i put a new ROM image on it and tried to reflash but after the flash when my phone booted up it simply switched itself off... when i switched it back on it went back to the bootloader and tried to reflash the ROM. mid flash it just switches itself off... I realize that this is probably due to the charge level of the phone so i plugged it it but it will be off and charging then it will suddenly decide its got enough battery power and boot up to the bootloader screen until it dies again...how do i stop this vicious loop
Click to expand...
Click to collapse
Something worth trying:
1.You could take out the battery for one minute or longer.
2.Now put the ROM's .nbh on your SD card [Make sure it is named "RHODIMG.nbh" (no quotes)].
3.Put the SD card and battery in and press/hold Power button and the Volume Down button at the same time.
4.That'll put you in Bootloader Mode, and it should ask you if you want to update your phone's image (something like that).
5.Follow the prompts and it should start flashing (you'll see the bar).
6.Soft reset after the flash says it's complete.
I once went through that and this is what I did. I was able to unbrick my phone.
However, (back in September/October) there was another instance of the same thing happening to someone, but he never got it fixed; he did get the stock ROM and SPL back on it, but had to return it to HTC because it still kept cycling into Bootloader.
Good luck!
When i enter recovery mode ADB will not list my phone, it lists it just fine however when my phone is on.. anyone have a idea?
I know it sounds stupid but make sure you have debugging mode on. Also when you mount your device (while its turned on) select the sync mode on your phone. I had to do that and then just play with it while loop is running pull the battery while usb is still plugged in and then power back on while holding volume down. I had to do that over and over and it eventually caught it.
I have debugging mode on, and while it is turned on and mounted as a disk drive ADB will recognize it. Ill try switching it to sync instead of disk drive.
Yeah it should recognize while in disk drive mode but it did not for me one time until I switched to sync. Could have just been a weird fluke but maybe not.
So you switched it to sync instead and while it was trying to sync you pull the battery out and hold the volumn down and the power button then put the battery back in? it will not catch it when i do this!
Not exactly. I switched it to sync and then let it do its thing for a minute. Then I powered off started running loop and powered back into recovery. Your computer shoukd make a little beep sound and the loop might hang up a bit when recovery loads. I then took the battery cover off and pulled the battery (loop still running and usb still plugged into phone) then hold vol down and put the battery back in. It will load into the boot loader from there you select recovery. I had to do that about a dozen times and finally it just caught on and showed my device in the loop as recovery.
Ill try this and post what happens thank you !
So far no luck, my computer will confirm that the phone is connected (by playing the sound confirmation) however it does not seem to be catching within windows or ADB
A thought occurred to me about this ... A couple people have said that it started working for them when they had a new/freshly installed microSD card in their phone. The card that comes pre-installed in the phone has doubletwist on it, including an autorun file. I noticed that until I removed these things from the memory card, Windows was identifying the card as "Media sync powered by doubletwist" or some crap like that. I took all that junk off and it started identifying it as just "Removable Disk." Now, I took off all this before I tried the rooting process, so I don't know if it would've caused any problems. Could it be that this has something to do with it? It doesn't seem likely to me, but I thought I'd mention it.
At any rate, try a new or freshly formatted SD card, see if that helps.
Restarting over and over again finally made it work. now have a fully rooted slide.
Just curious did you restart you phone or your computer over and over again?
Im Not sure exactly what happened here, I've been flashing for nearly a year now a variety of ROMs, and this last time seems to have been fatal.
I went from a custom ROM, did the routine task29 before loading a new ROM; the task29 completed, I returned to bootloader to load the new ROM, and it wouldnt load past 0%. I tried to task29 again, and then that wouldnt load past 0%.
I've since tried mtty and doing set 14 0, task 29, task 8, which restarts it, but now I can no longer manually power it on by pressing hardware keys anymore.. I have to leave it plugged into USB and wait for it to auto-turn itself on after about 5 mins, it loads to "Touch Pro 2" screen, then I can press the little reset button and hold down vol key to get to bootloader. However, it only lasts there about 10 second before turning itself off again, showing the orange light like it's charging. Sometimes I am quick enough to get any ROM or manual HardSPL to try and load at bootloader, but it still sits at 0%.
I have also tried to load a ROM from the SD card, which seems maybe the only option how; however, I have heard you need at least 50% battery, and I have no way to see how much battery I have left, or whether its even charging.
I tried to install from SD yesterday, and got to the gray "Loading" screen, and it just sat there.. I wasnt sure how long it normally takes at that screen, so i powered it off, checked my SD card and now that shows as corrupt and cannot even be formatted... pretty much burnt out as well now, it seems.
Did I do the SD card installation right, using my RHODIMG.nbh file at the root? How long does it normally sit at the Loading screen? I have an 8GB mini-sd I could load from, but I dont want it to burn out as well..
Are there any other options?? I cant even send back to warranty, I dont think, because I cant even load back on the stock ROM or relock it...
Moved to Rhodium General forum because not a cooking problem.
Someone please help... I just tried again to load stock ROM from SD card, as well as custom, it just sits on "Loading..." on the gray screen...
Just for the record, I can get into bootloader, but as of now nothing will load past 0%.
I tried mtty set 14 0, task 29 and task 8, no luck...
I'm certainly not an expert, but just thought I'd throw out a few ideas.
Have you tried charging the phone on the wall charger (not USB) for several hours (like overnight). The fact the phone is powering off by itself suggests that you may be low on battery. USB won't charge the battery sufficiently in some cases of extreme low battery. Try another battery or charge if possible.
Having the RHODIMG.nbh file in the root of your micro-SD card is the correct way to boot from the card. Normally, it doesn't matter if there are other files on the card. But formatting it can't hurt at this point.
Only other thing I can think of, is try to re-flash the radio first, and see it that helps. That's all I can offer up at this point. I was going to suggest trying to flash the stock ROM, but you've already thought of that in your latest post.
Good luck!
redpoint73 said:
I'm certainly not an expert, but just thought I'd throw out a few ideas.
Have you tried charging the phone on the wall charger (not USB) for several hours (like overnight). The fact the phone is powering off by itself suggests that you may be low on battery. USB won't charge the battery sufficiently in some cases of extreme low battery. Try another battery or charge if possible.
Having the RHODIMG.nbh file in the root of your micro-SD card is the correct way to boot from the card. Normally, it doesn't matter if there are other files on the card. But formatting it can't hurt at this point.
Only other thing I can think of, is try to re-flash the radio first, and see it that helps. That's all I can offer up at this point. I was going to suggest trying to flash the stock ROM, but you've already thought of that in your latest post.
Good luck!
Click to expand...
Click to collapse
Thanks for the response; I just tried that (flashing the radio) and it didnt work. Ive also tried flashing a variety of ROMs and nbh files over SD;
It always seems to freeze at the gray "Loading..." screen and get no further.
venomshot629 said:
Thanks for the response; I just tried that (flashing the radio) and it didnt work. Ive also tried flashing a variety of ROMs and nbh files over SD;
It always seems to freeze at the gray "Loading..." screen and get no further.
Click to expand...
Click to collapse
Try using a different USB cable to flash via the PC. If you try the SD route again, some users report that using a NON-SDHC card solves the flashing problem. Give that a shot and then report back. I can't really think of anything else offhand.
cajunflavoredbob said:
Try using a different USB cable to flash via the PC. If you try the SD route again, some users report that using a NON-SDHC card solves the flashing problem. Give that a shot and then report back. I can't really think of anything else offhand.
Click to expand...
Click to collapse
I have tried again using a 512 MB SD card and it still hangs at the "Loading..." screen.
Also, when flashing with any USB cable, I am still stuck at just 0%.. I can get into the bootloader, etc, but it just refuses to flash any image..
I was trying to flash the new version of EnergyROM and when i ran a task29 i accidently left my SIM card and SD card in. I loaded it to the bootloader screen and it was saying USB on the phone but my computer wasnt recognizing it so i went and bought a card reader and tried flashing from the SD card and now its stuck on a black screen with the red light in the corner always on. the phone wont turn on and the light only comes on when its plugged in. please please help me i just bought this phone 2-3 weeks ago and didnt get insurance.
Generally, if it is bricked, it won't turn on or just constantly reboot. You can access bootloader mode by hitting the down volume key while holding the soft reset button.
http://forum.xda-developers.com/showpost.php?p=7807988&postcount=3
that what it seems to be doing, ive run task 29 twice and tried to reinstall the ROM that worked earlier today and it just loads up to the BRGD ATT world phone screen and acts like it wants to boot up and then just goes back to the black screen any ideas on why?
Please help. This is a serious matter for me.
Started having this problem at February 14th, 02.10 AM.
Have been looking for the answers in the Oppo Forums too but still got no answers.
Okay, I have a habit, which is moving all of my applications from my internal storage to my external SD card, after I let those applications doing their functions and programs and features and so on for a while. It's not a big deal for me to set up my phone again after I restarted it, and usually it works perfectly. Just restart and I would get to operate my phone again. However, this time, I got a bad luck. The worst one, considering the fact that I'm all-around-gadget.
Here's the results I got from reading a lot of threads (not only from this forum and OPPO forums):
OPPO Swype Keyboard has stopped working? Really?
After restarting my un-rooted Find 7 (9076), I cannot type the password on my lock screen. Like any other Android devices, it would always come back to it's system or default applications, I knew that fact. But this time, when I touched the blank space to type my password, nothing came out. No OPPO Keyboard, which happened to be OPPO's default keyboard. No other keyboards. None at all.
So, I cannot do one single thing to my phone except just turn it on and stared at it like a complete idiot.
Then I decided to turn my phone off and turn it on again after a while.
But still, the same thing happened. No keyboards.
That time, I decided to turn off my phone again and pulled out the battery and my external SD card.
After putting the battery back (External SD Card was still outside), and turned it on again, the same thing still happened.
Sliding my fingers up and down, nothing happened. The touchscreen was still there, showing me my date and time even though I was sliding my fingertips up and down.
Not too long after, I felt my phone got warmer and warmer. I tried double-clicking the home button, which I already set to unlock the lock screen, was also useless. The screen was still black and locked. When it got over-heating, automatically I pulled out the battery without even turning off the phone.
That one was my fault. I knew, and well, honestly speaking, this is the first time I'm in this kind of situation. In the past, my Find 7 would just suddenly restarted itself then everything went back to normal, but not this time.
And here's the beginning of my Fastboot Loop.
Fastboot Loop on un-rooted device
After pressing the Power button and the Volume Up button at the same time, it would bring you to the Recovery Mode. When I did that to my Find 7, it brought me to a black backgrounded screen with cute OPPO mascot and some Hanzi (Chinese handwritings). Picture attached.
I tried to wait for 2-3 hours and found nothing happened.
Pulling the batter out and putting the batter back would do the same.
In other words, I am not able to gain access to my Recovery Mode.
Why didn't bring the phone to the service centre?
I thought about this already.
When I tried to connect my phone to my pc, it can detect the phone but cannot access the files because the phone was still locked with the password.
Usually, the service centre requires us to unlock the phone if there's a problem with it, right? In my cases, yes.
I was searching all night to find out the answers.
I found some threads about the Fastboot Loop thing and etc, but they are only for rooted devices.
I'm using:
OPPO Find 7 (9076)
Color OS 2.0.5i Beta
Android KitKat 4.4.2
Device is not rooted, still original.
Still dealing with the same problem until now (the time I post this thread).
Anyone has solved this problem and guide me step by step to finish this?
daiichi said:
Please help. This is a serious matter for me.
Started having this problem at February 14th, 02.10 AM.
Have been looking for the answers in the Oppo Forums too but still got no answers.
Okay, I have a habit, which is moving all of my applications from my internal storage to my external SD card, after I let those applications doing their functions and programs and features and so on for a while. It's not a big deal for me to set up my phone again after I restarted it, and usually it works perfectly. Just restart and I would get to operate my phone again. However, this time, I got a bad luck. The worst one, considering the fact that I'm all-around-gadget.
Here's the results I got from reading a lot of threads (not only from this forum and OPPO forums):
OPPO Swype Keyboard has stopped working? Really?
After restarting my un-rooted Find 7 (9076), I cannot type the password on my lock screen. Like any other Android devices, it would always come back to it's system or default applications, I knew that fact. But this time, when I touched the blank space to type my password, nothing came out. No OPPO Keyboard, which happened to be OPPO's default keyboard. No other keyboards. None at all.
So, I cannot do one single thing to my phone except just turn it on and stared at it like a complete idiot.
Then I decided to turn my phone off and turn it on again after a while.
But still, the same thing happened. No keyboards.
That time, I decided to turn off my phone again and pulled out the battery and my external SD card.
After putting the battery back (External SD Card was still outside), and turned it on again, the same thing still happened.
Sliding my fingers up and down, nothing happened. The touchscreen was still there, showing me my date and time even though I was sliding my fingertips up and down.
Not too long after, I felt my phone got warmer and warmer. I tried double-clicking the home button, which I already set to unlock the lock screen, was also useless. The screen was still black and locked. When it got over-heating, automatically I pulled out the battery without even turning off the phone.
That one was my fault. I knew, and well, honestly speaking, this is the first time I'm in this kind of situation. In the past, my Find 7 would just suddenly restarted itself then everything went back to normal, but not this time.
And here's the beginning of my Fastboot Loop.
Fastboot Loop on un-rooted device
After pressing the Power button and the Volume Up button at the same time, it would bring you to the Recovery Mode. When I did that to my Find 7, it brought me to a black backgrounded screen with cute OPPO mascot and some Hanzi (Chinese handwritings). Picture attached.
I tried to wait for 2-3 hours and found nothing happened.
Pulling the batter out and putting the batter back would do the same.
In other words, I am not able to gain access to my Recovery Mode.
Why didn't bring the phone to the service centre?
I thought about this already.
When I tried to connect my phone to my pc, it can detect the phone but cannot access the files because the phone was still locked with the password.
Usually, the service centre requires us to unlock the phone if there's a problem with it, right? In my cases, yes.
I was searching all night to find out the answers.
I found some threads about the Fastboot Loop thing and etc, but they are only for rooted devices.
I'm using:
OPPO Find 7 (9076)
Color OS 2.0.5i Beta
Android KitKat 4.4.2
Device is not rooted, still original.
Still dealing with the same problem until now (the time I post this thread).
Anyone has solved this problem and guide me step by step to finish this?
Click to expand...
Click to collapse
boot into recovery and format the phone, this should fix it. If you want to backup your data, just boot into fastboot, connect phone to pc, run fastboot command from sdk tool, push custom recovery, flash twrp, make nandroid backup, fomat phone along with all the storage and then flash oppo stock rom (you need to download) or any other custom rom with gapps. To restore use nandroid manager, do not restore system files if you are flashing custom rom.
treacherous_hawk said:
boot into recovery and format the phone, this should fix it. If you want to backup your data, just boot into fastboot, connect phone to pc, run fastboot command from sdk tool, push custom recovery, flash twrp, make nandroid backup, fomat phone along with all the storage and then flash oppo stock rom (you need to download) or any other custom rom with gapps. To restore use nandroid manager, do not restore system files if you are flashing custom rom.
Click to expand...
Click to collapse
Thank you for your help Sir.
But, my Find 7 already operated normally again since I left it for a few days uncharged and off.
Then I got into Recovery Mode by pressing Power button and Volume Down button (not Volume Up button) while in the middle of my fast-boot loop.
It worked. I could gain access to ColorOS Recovery Mode.
So, I reset my Find 7, then re-installed my applications and everything again.
Thank you for answering!