I flashed sammobil stock 7.0 FRC1 now it reboots randomly and keep getting a Diagmon fail.
Related
Hey,
I wanted to update my CM11 from the 28/8th nightly to the 29/9th nightly... so I downloaded the new version and new gapps (pa stock package). Then I flashed it as usual through TWRP and rebooted. The Tab just kept rebooting right in the unlock-screen after booting. Ok.. so I ended up doing a full wipe incl. system-wipe and flashed those two packages again. Reboot. Now what? Still rebooting, now directly in the laguage-selection screen from CM11, 2 secs after booting.
???
Ok... so I wanted to flash an original package through ODIN 3.09.
ODIN seems to be weird, too...
SECURE CHECK: fail
aboot.mbn FAIL(Auth)
.... aahhhhhh.... what's going on?!?!?!
I cannot seem to get this device back working right now.... plz - some1 help!
So i get some random reboots, then my phone started to freezing like 2-3 mins after reboot and going back to normal work only after reboot so i decided to flash new rom. When i try to wipe data/dalavik or whatever it keeps rebooting without doing anything. Any ideas?
@edit I flashed new rom from sammobile , only emergency calls , what should i flash now guys? i got AP ending with OB1 and i can't flash MJ5 bootloader
Copy all your valuable data, it might be SDS. Flash modem and bpotloader from androidwizard thread in android development section or restore EFS
HELP!! Was trying to upgrade my bootloader from BPA1 to CPD1 and got a boot loop. Now When I try to flash the stock Lollipop firmware in Odin, I get operation failed about two thirds of the way through. I also tried the Verizon repair assistant and it gets stuck at 83%. Please help.
Hi i was helping my friend to update his firmware. after doing so the phone is now stuck in a weird bootloop. i had seen my fair share of bootloops but this seems weirder than others. the n7100 logo would loop very quickly (sorta like flash) and keeps doing so. can't enter recovery mode at all, only download mode. plug it to odin and whatever i can throw at it i just got nand write start fail, be it twrp, multiple versions of stock rom. im at the end of my wits, so what should i try next? thank you for any input
What is the Odin error when trying to flash the latest stock ROM from sammobile.com? Tried different USB cables and USB ports?
I kinda have/had the same problem.
N7100 logo would bootloop quiet fast (doesn't get to the point where it should load the rom).
Can't enter recovery bc of that.
Only thing that works is download mode.
After trying to flash newest stock rom (4.4.2) it failed once (I think my cable gets too old...)
Next try it worked without a problem.
Problem persists.
Next step was flashing an older repair firmware (4.1.2) but it failed (I think bc of the 4.4.2 bootloader? IDK)
Then I tried to flash the newest stock again but with the pit file. Flashed without a problem but the problem was still there.
Last step I made was to flash the newest stock with the pit file and nand erase + update bootloader.
Tried it 2 times but it failed.
Now I'm stuck on the "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
Download mode got a red message also: "RPMB: INVALID RPMB DATA"
I don't know what to do now. Please help.
PS: It was a "new" motherboard from aliexpess, it had a chinese version of the stock 4.1.2 if I remember right and was already rooted when I installed it. I wanted to flash the newest 4.4.2 for the new modem and stuff and then upgrade to lineage. :/
Hi there, I have the above device with unlocked bootloader. It was rooted but I had a problem where the tablet kept rebooting but only after it loaded Android. No amount of following guides fixed it and Recovery and Fastboot were throwing g up problems whenever I tried to flash anything.
Eventually, I managed somehow to switch it on to Chinese update cycle I think and update the ROM with the latest official Chinese EMUI through multiple reboot loops (it downloaded about 10% of the update each time before crashing and getting the next chunk of download next time).
So I'm currently on the latest Chinese ROM running android 5.1.1 and it started working again. However the ROM came without gapps included so I flashed TWRP and installed gapps and I'm back to the reboot cycle. It lasted a long time before restarting again though so I'm guessing it's to do with gapps trying to update.
So I'm back to square one again. Any ideas? Is there any kind of log I can provide to help diagnose? I still have TWRP and have access to that without the bootloop starting again..
How did you rooted it?