So I had the RR-N-v5.8.5-20170926-n7100 custom os installed on my GTn7100 phone. Yesterday, the battery was drained. I had the wifi on and it was consuming battery very fast. So when I charged it to nearly hundred percent, the phone lagged crazily. I even noticed that the arrangements of the icons of my apps were changed. Then it hanged for about 5 seconds (the screen was on home) and then it went off. I was really confused as to what just happened. And turned it on, the phone is not booting anymore. It's just stuck on the "samsung galaxy gt n7100" boot screen (it's not on loop). I thought it's just some random bug and went to restart it again but to no avail. I had the TWRP 3.0.2-0 installed and thankfully it's still working after pressing the combination. At the start, there is a prompt about 'unmodified system partition...' and I thought factory resetting the device might resolve it, but to no avail again. The process was succesful but in the terminal, there are errors in blue line that says that there is no storage to wipe or something like that. And there is also a prompt that the device has no os installed. Even in the mount settings, when i select a storage, the prompt says that the 'Internal storage (0mb)'
What to do?
I recommend flashing the latest stock ROM with Odin as a first step. If the phone boss properly, then you know it was a software problem.
Related
So, it's been a fun couple of days.
I was 'tabling' away, as usual, and my tablet suddenly reboots (if it matters, I was just opening FPSE, as I'd done dozens of times before; Skype was on background; every other process was finished). 'Ok', I thought, 'that's weird'. When the tablet's done rebooting, the lockscreen shows up, and when I try to unlock it, the scren just freezes. Couldn't turn off the screen, nothing. So, I force a shutdown by pressing the power button.
When I try to turn it on again, it just stays stuck at the Google logo screen. I tried going in through recovery, but the result is the same. Select recovery, Google logo shows up, little android with exclamation point doesn't.
I tried formating through fastboot -w, but the process just keeps endlessly deleting, while doing nothing at all. I have to quit command line, shut down tablet or unplug the USB cable with a command line message showing up (I once left it while I went for a coffee; two hours of deleting nothing at all). Same thing with trying to unlock bootloader to maybe going to recovery after flahsing a custom recovery.
I don't mind losing everything I had. All pictures are recuperable and the rest is either in the cloud or in my phone/PC. The most annoying thing would be to set up the whole thing again, wich is no trouble at all (that and going through PvZ2 and TD Bloons 5 from the start :crying: ).
I was using Android 4.4 (KRT16S), everything stock.
Is it bricked, soft-bricked, did the aliens get it? I am e-mailing with someone from the store I bought it from, hoping for a solution or (worst case scenario) RMA, but I would rather solve this without having to.
Try flashing system.img, recovery.img, and boot.img, by hand.
Your emmc likely got corrupted
How do I do that with a locked bootloader and no access to recovery? Is it possible?
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!
Its been a long time since I booted my Galaxy Note-II (GT-N7100) as I use an iPhone and Nexus 5 as my daily drivers.
The phone wont boot past the Samsung Galaxy Note II GT-N7100 logo. I am able to access the recovery and download mode as well, and I have flashed the latest stock rom from Sammobile using the Odin. The flashing was successful. however the phone doesn't boot past the logo. Also the phone will not power up unless connected to a PC, it wont power up even when connected to a charger and will immediately shut down when the USB cable is disconnected from the PC. I flashed TWRP 3.0.2 Custom Recovery using the Odin and tried installing CM 13 based Rom through the mem card, however the log reads patching image unconditionally and also that "Failed to mount /system" (invalid argument). The phone when restarted into recovery can no longer mount the /system partition. However on flashing the stock rom using Odin, the /system partition is available for mounting. The recovery log also shows MTP enabled, but my PC doesn't detect the phone when in recovery, it only detects the phone in Download mode. I have the Samsung drivers installed. Since the phone is not being detected in recovery I am unable to use the adb.
I am out of ideas and request your suggestions other than approaching a service centre.
If I can somehow access the phone via ADB, I might be able to check the memory partitions for corrupt units, and possibly create a custom PIT file to repartition and suit the available memory units.
Try this: open Odin, uncheck everything except f.reset time. Connect phone and flash stock ROM. When you see the word reset in the status window, remove USB cable, remove battery for a few seconds, replace battery, immediately boot the phone into recovery mode, factory wipe, and boot the phone.
Could the battery be defective or dead?
audit13 said:
Try this: open Odin, uncheck everything except f.reset time. Connect phone and flash stock ROM. When you see the word reset in the status window, remove USB cable, remove battery for a few seconds, replace battery, immediately boot the phone into recovery mode, factory wipe, and boot the phone.
Could the battery be defective or dead?
Click to expand...
Click to collapse
Thanks a lot.
Tried your method and finally the phone has booted into the OS.
Had to replace the battery with another spare one in the process.
However the phone is still not being detected by the PC unless it's in Fastboot/ Download mode.
When connected to a computer, does anything appear on the phone screen? If you're using Windows, nothing new appears in device manager?
sorry to jump in this thread but i am having a similar problem
my completely stock tmobile note 2 is stuck on the samsung logo
i have never flashed it or done anything to it
my phone was working really slow, freezing up and battery draining fast
so i did a hard reset and it fixed the problem of running slow and freezing up for a week or so but battery drained fast
so i bought a replacement battery from ebay and installed it and the next day i restarted my phone and it froze on the samsung logo
i tried turning it off and on and still the same thing
any suggestions or should i start a new thread?
fyi i am a noob
Hello, I would like to first tell you the story my LG G4 has gone through and then I tell you the error.
So, at first my phone was working absolutely properly. I accidentally deleted some pictures and to do a recovery, I had to root it. And rooting would be useful for later so why not do it?
So I first unlocked the bootloader through the code from the LG site. After unlocking, the phone reset (because it would be just too good to make some memory changes and nothing more.) But allright. Then I was ready to root. I just booted the phone, everything was fine. I unlocked the developer mode and opened ADB. I rebooted to recovery through
Code:
adb reboot recovery
I was expecting to see some menu with buttons (but that would be just too good). However, I saw just android with a red triangle in the middle. Nothing more. No response to buttons, nothing.
So I thought. Allright, let's boot into recovery using hardware buttons (vol down + power) at startup. Unfortunatelly, it seemed like there is no such mode System just normally booted (and that was just after bootloader unlocking. Recovery mode goodbye.).
I tried to send commands to the phone using diagnostic port. Unfortunately, it responded by FAIL to every command.
I reboot to bootloader and booted an image: "boot-em.img" (from here: google: how-to-root-lg-g4-on-android-6-0-marshmallow-20a20b-firmware. I'm a newbie here. thx for understanding.)
After that the console uploaded the image and booted successfully. Then, however, system started to boot up and was endlessly booting (LG boot animation) till the battery was critical.
I was able to access the EMI number through volume-down button and volume-up button pressed simultaneously.
I was also able to access some factory-reset dialog by holding volume-down and pressing power-button several times. I choosed to reset everything and then accepted it with one more 'are you sure dialog'. System rebooted and was stucked in the LG boot animation.
Then I got to download mode, since recovery mode was lost in hell. Through LG-UP I flashed the original KDZ firmware and everything got back to normal, but recovery mode was still inaccessible through the hardware buttons. I got through the process of setting everything up, getting developer, rebooting to bootloader and I booted TWRP.
TWRP loaded and it responded to double-tap on screen to wake it up. I just checked the menus and let the phone sleep.
After several hours I went back to the phone and double-tapped on display. Nothing. Phone was not responding. I pressed the power button and the phone restarted (I think. It either restarted into the system or was not responding to power button.)
So I got to the system and again rebooted to the TWRP (through fast-boot). I tried to back-up one partition to the disk. During the process phone had turned the display off. So I double tapped. Nothing. I removed the SD card and the phone woke, saying that back-up process was not able to complete. Suddenly it stopped responding to double-tap. It woke up through an interrupt. I re-inserted the card, successfully backed-up the partition to the SD-card and I left the phone laying on the bed plugged in the charger. It stayed that way for 4 hours or so, doing nothing. All of a sudden, a yellow screen was there, (and that's a screen of absolute death that was never supposed to come. Little I knew.) saying that an unexpected critical error happened and to do a memory dump, insert a cable, set up some communication (I don't remember what it was, didn't take a picture of it.) and it could send the memory dump to PC or somewhere. I thought to myself. So, the application is not so stable after all. It said that to reboot just press the power button or something.
And now the problem comes:
The first start: Bootloader booted, LG animation went on and finished. The starting up apps dialog came rolling. Then, system restarted.
The restart: Bootloader booted, LG animation went on and freezed. Then, the phone restarted.
Second restart: The same thing as the first one.
Fourth restart up till now: Bootloader tries to boot and restarts before the LG animation.
I got to download mode and it restarted even there. After re-inserting the batterry I can sometimes get to the Firmware Update window and communicate. There I flashed the official firmware again.
No success, as if I didn't even do it. It restarts before the animation.
Can I do anything with the phone? Hopefully I can. No hardware problem occured (except for a situation where the error could fry the wires inside the mighty System On Chip.)
For the software state I cannot even tell but I might say it's cooked just wrong. That's why I came here.
I know I did some pretty stupid steps. But the error was not done by me. It worked fine and after the yellow screen which came by itself, it just (some bad words).
Thanks for replies.
Phone: LG-G4 H815, European market
Solution
So, I was looking around and believe it or not, this problem disconnected the pins on the motherboard's snapdragon 808.
I think this happened: The device, although it was heated many times during its life, it withstood that so far.
However, a longer run of the TWRP had finished it off. Memory got disconnected while running and it threw a yellow-screen.
Pins got disconnected and from then on it was just a standard common LG bootloop issue.
The continuous process of dying (First it partially loaded, then only animation, then nothing) is explained by this fact that the pins were so-so there and a couple of reboots just got it totaled.
Temporary fix:
Pre-heated the memory chip to 250°C using Hot-Air gun. After 18 seconds at this temperature I pressed the memory on top of the snapdragon down to the board while cooling.
Then I added a little metal square on the metal part that is covering the system on chip. This part is over the SOC where before there was just some tape.
This can work for several days in sleep mode or a couple of 'heat-demanding' operations on the phone.
Permanent solution should be to reball the memory chip on the snapdragon. That's my next step.
I'm really anxious and nervous about this so I'll simplify this as much as I can; recently my phone was turned on on top of my desk and randomly restarted. I thought little of it, as it quickly went through the OnePlus logo (it began to take longer the second time I restarted it) and Android splash screen, but then stopped on the circles animation and remained looping there. I have very important data on it that I'd like to recover and WILL NOT factory reset (flash) my phone.
The battery icon and percentage still show up when I plug in the device. I still have access to Recovery Mode, Fastboot, and Sideload through their key shortcuts. I previously had USB Debugging enabled but can't authorize ADB since I can't check the confirmation dialogue box (shows up as "unauthorized" in command prompt). I had very little storage (less than 250mB) for the last few days. I don't have root access, custom recovery, or an unlocked bootloader.
I already tried clearing my cache; if I restart after doing so it only takes a few seconds to pass the OnePlus logo as opposed to the ~20 seconds it previously took. This delay raises every few restarts. I've tried waiting many hours to see if anything would happen or if ADB would start functioning. I also tried fully draining my battery overnight and nothing happened. My files are not deleted/fully corrupt since I could still see them when flashing through internal storage from Recovery Mode. OnePlus chat support said I have to flash my phone and Twitter support refused to respond. Local data recovery centers said I could get my phone shipped to them for a free diagnostic, should I do so or is there a way to unbrick or recover my data at home?
Is there anything I can do? Thank you very much!... for now I'll just remain depressed...
TL;DR - My phone's stuck at the circles boot animation and I want to recover my files or fix the soft-brick without resetting. I don't have root access, custom recovery, or an unlocked bootloader.
UPDATE: I boot into Recovery Mode and "Reset System Settings"- my phone rebooted with 112 gigabytes of storage already taken up and all of my Android/data folders empty! I lost very little as I set my save folders to other locations! It looks like the error was not having enough storage! OnePlus chat support said that I had to factory reset my phone, DO NOT listen to them! MY PHONE IS UNBRICKED!
Check out other responses:
https://www.reddit.com/r/Oneplus5T/comments/ahfabg/data_recovery_for_softbricked_oneplus_5t/
https://forums.oneplus.com/threads/data-recovery-for-soft-bricked-oneplus-5t.986096